How we work
No surprises, including the price.
Every engagement opens with a paid discovery sprint that ends in a real scope and a real number. If the right answer is that you should not build it, that is what the sprint will say.
Delivery
Four phases, every time.
- 01
Discover
1–2 weeks
A fixed-price sprint that ends in a scoped plan, a cost and a decision — not a proposal to be chased.
- 02
Design
2–3 weeks
Process mapping and architecture. We work out how your business should run before we configure anything.
- 03
Build
6–12 weeks
Implementation in two-week increments you can see and react to, against a schedule you can plan around.
- 04
Operate
ongoing
Hypercare, training, and the agent layer that keeps paying for itself after go-live.
Engagement models
Five ways to work with us.
Discovery Sprint
1–2 weeks · fixed priceStarting anything. You leave with a scope, a cost and a decision — useful even if you stop there.
Shared after the scoping call
- Process mapping with the people doing the work
- Architecture and systems assessment
- Fixed-price scope for the build
- An honest recommendation, including 'not yet'
Fixed-scope Build
6–16 weeks · fixed priceWork that discovery has scoped properly and that will not change much in flight.
Shared after the scoping call
- Two-week increments with a demo at each
- Preview environment you can click through
- Scope changes estimated before they are built
- Documentation and handover
Dedicated Pod
monthly · rollingWork where the scope will genuinely evolve, or when you need capacity alongside your own team.
Shared after the scoping call
- Named senior engineers, not a rotating bench
- Joins your standups and your repository
- Monthly rolling, 30 days' notice
- Priorities you set each sprint
ERP Implementation
10 weeks – 6 months · packagedOdoo or SAP, packaged by product and company size rather than quoted from scratch.
Shared after the scoping call
- Configuration, migration and integration
- Key-user training
- Hypercare through your first close
- Admin access and documentation from day one
AI Retainer
monthly · rollingKeeping agents working after launch, as models change and your processes move.
Shared after the scoping call
- Evaluation suite maintained and re-run
- Model and prompt updates with measured results
- Cost and latency monitoring
- A monthly report you can take to a board
What we don’t do
The work we turn down.
- Staff augmentation by the headcount, with no say in how the work is done
- Fixed-price contracts on scopes nobody has investigated
- AI features whose only purpose is to be announced
- Rebuilds we recommended because rebuilding is what we get paid for
- Lock-in: you own the repository, the documentation and the admin access

