From first call
to handover.
Every engagement follows the same shape, sized to the problem. You always know the current step, the next step and the cost.
- 01 Before any fee
Brief & first call
You tell us the problem in a short brief. We read it and reply in writing. If the work is a fit, we book a short call. On that call we agree the diagnostic scope. We confirm the fee before work starts. If the work is not a fit, we say so in the reply.
- A written reply to your brief
- A short call, if the work is a fit
- The diagnostic scope and fee, confirmed before work starts
- 02 2–4 weeks, fixed scope
Diagnostic
We run the Ship Audit against your data, your infrastructure, and your team. The scope and the fee are fixed before we start. You get a written report and a scoped pilot plan. If the honest finding is 'not ready,' the report says so.
- A written readiness report
- A risk register with severity and mitigations
- A scoped pilot plan
- A KPI framework to judge success against
- 03 Per phase, shipping weekly
Phased build
We build in phases, against the pilot plan from the diagnostic. We price each phase before it starts. We build directly in your environment, against your data. Every week you see working software. Where it's sensible, pieces reach production well before the engagement ends. That means 'does this actually work' gets a real answer early, before anyone has to argue about it.
- Weekly working demos against real data
- A staging environment you can poke at
- Early production slices where feasible
- Running eval results alongside the code
- 04 ~1 week
Handover
The engagement ends with your team able to run the system without us in the room. We write the documentation we would want if we inherited it cold. We hand over the eval suiteAn eval suite is a versioned set of test cases that measures whether outputs are good. that proves it still works after you change something. We walk your engineers through the runbooks until they own the failure modes as well as the happy path. After production, the evals and roadmap retainer is available.
- Documentation and architecture write-up
- Runbooks for on-call and common failures
- Eval suite handed over and explained
- A team briefed to own the system outright
What we hold ourselves to on every engagement.
These aren't values-page filler. They're the commitments that shape how each stage above actually runs, especially the last one: you leave owning the system outright. Your team can run and extend it on its own.
- 01
Build to ship.
Every project leaves you with a system running in production.
- 02
Boring infrastructure wins.
We use models like contractors use power tools. The interesting work is the system around them.
- 03
Eval-driven development.
If we can't measure it, we don't claim it. Every release rides on a test suite that mirrors the work.
- 04
Hand it back, properly.
Documented, observable, owned by you. You can run and extend it on your own.