Discovery
Every engagement starts with a fixed-length discovery phase, usually one to three weeks. We interview the people who do the work, map the systems and data involved, and write a plain-language description of what will change. Discovery ends with a document you own: the current state, the proposed state, the scope of the first build, and a fixed price for it. You can stop after discovery and keep the document.
Build
Build runs in increments of two to three weeks. Each increment has a fixed scope agreed at its start and ends with something your team can use, on a staging environment from the first increment and in production as soon as the first complete version exists. We demo at the end of each increment and re-plan the next one together. Scope changes are welcome between increments and are priced before they are accepted.
Run
We do not consider a system finished when it is deployed. Every engagement includes a hypercare period, documentation written for your team, and a handover session. After that, you choose: run it yourselves, keep us on a retainer for changes and support, or embed one of our engineers with your team.
Engagement models
Fixed scope. A defined outcome, a fixed price, and a fixed timeline. Best for solutions and well-understood builds.
Retainer. A monthly allocation of engineering time for ongoing changes, support, and small projects. Best after a system is live.
Embedded team. One or more of our engineers working inside your team, on your tools and priorities, for a defined period. Best for large programs and for building your own capability.
What you can expect from us
- A named lead who is accountable for the engagement from discovery to handover.
- Written scope before work, written change requests during it, and a written handover at the end.
- Weekly progress notes in plain language.
- Honest advice, including when the right answer is "do not build this."