Four stages, no surprises.
The same sequence whether the engagement runs eight weeks or two years. Predictability is a feature.
- 01
Technical discovery
Week 1We read the code, trace the hot paths, and interview the people who get paged. You get a written assessment of what is actually in the way — including the parts you did not ask about.
You receive: Assessment + risk register
- 02
Architecture & plan
Weeks 2–3Target architecture, migration sequence, delivery plan, and a fixed commercial shape. Enough detail to decide with your eyes open, and cheap enough to walk away from.
You receive: ADRs + sequenced roadmap
- 03
Build in increments
Weeks 4–16Two-week increments, each deployed behind a flag and demonstrable in your environment. You see running software, not slides about running software.
You receive: Deployed increments + CI
- 04
Handover & on-call
OngoingRunbooks, architecture decision records, and a rota sized to how much of it you want to own. We answer the pager until you would rather we didn't.
You receive: Runbooks + SLOs + rota
What we commit to.
Fixed scope, fixed price
The plan stage produces a number. That number does not move unless you change the scope, and we tell you what a change costs before it starts.
Your repo from commit one
Everything lands in your version control and your cloud accounts. There is no staging ground we control and you cannot see.
Weekly written updates
What shipped, what slipped, what we are worried about. In writing, every Friday, whether or not there is good news.
An exit that works
Runbooks, ADRs, and a pairing period. We consider the engagement successful when your team stops needing to call us.
Tell us what is breaking.
Send the problem, not a polished brief. A principal engineer reads every enquiry and replies within two working days with a real technical opinion.
- Reply from an engineer, not a salesperson
- Fixed scope and price before any build starts
- Your code, your cloud, your repo — from day one