Every request becomes a sized ticket
An engineer turns your request into tickets, one per feature, and sizes each one: small, medium or large. You approve each ticket in your client portal, the Front Desk, at that size. Nothing is worked before you approve it, and a ticket whose size changes needs your approval again.
Every feature gets built. Sometimes, while working on a ticket, we find a problem in its specification: a case nobody described, two rules that contradict each other, a choice only you can make. We then close that ticket with the reason and open a new one with the corrected specification; the engineer sizes it again and you approve it before work starts. A closed ticket uses no credits.
Where the work happens
The work on a ticket runs in two phases.
- The build. Our AI production line writes the feature, its tests and its documentation, and runs the tests that concern it. This runs on our infrastructure at Amazon Web Services.
- The gate. On our own machines in Thailand, your latest main branch is merged into the work first. Then your whole app is built and its whole test suite runs, old tests and new, on that merged tree.
Only a green gate goes further. A red gate never reaches your repository.
What it looks like while it runs
This is the dashboard of our production line, on an example project. Each ticket shows its size and its credits, where it stands — build, merge of your main branch, gate, delivered — and what it did last. Below them: the ticket waiting for your decision, the ones delivered with their pull requests, and one closed, then re-specified.