Process · four stages, each gating the next
The expensive commitments come last, after the risky assumptions have been tested against your real data.
We sit with the people who do the work today and write down the actual path: every tool, every handover, every place someone re-types something. The output is a written scope with a fixed price and a definition of done, and it is yours whether or not you continue with us.
The riskiest part is built first, thin but real. If the AI step cannot reach an acceptable accuracy on your data, or the integration you were promised does not expose what you need, you find out here, in days rather than after a quarter of development.
Weekly releases to an environment you can use. Code review, types end to end, and tests on the paths that touch money or customer data. You see progress as working software, and you can change your mind while that is still cheap.
Monitoring, error alerts and a named person to call. If you want to take it in-house, we hand over documentation and walk your team through the code rather than making ourselves permanently necessary.
What we build
The stages change from job to job; the spine does not. The last loop, where a correction becomes a test case, is the difference between an automation that degrades and one that improves.
Terms
Fixed scope
A defined deliverable, a fixed price, a date. Best when the outcome is clear: a site, an integration, a tool.
Monthly
A standing block of capacity for continuous improvement, support and the work that keeps arriving after launch.
Per engineer
Our people in your stand-ups, your board and your repository, reporting to your leads for a set term.
| Item | Project | Retainer | Embedded |
|---|---|---|---|
| Price | from $4,500 | from $2,500 / month | from $7,000 / engineer / month |
| Fixed scope and price | ✓ | – | – |
| Monthly capacity | – | ✓ | ✓ |
| Works inside your team | – | – | ✓ |
| Monitoring and alerting | via a retainer | ✓ | your process |
| Minimum term | the project | one month's notice | three months |
| Code in your repository | ✓ | ✓ | ✓ |
Before any of this, we want to know whether the problem is worth solving. That part is free and usually takes one call.