How we work
Projects in phases, with a decision at each step.
Each phase has a duration, a deliverable and a decision point. You assess the result before authorising the next one.
01
Discover
1 week
Conversations with the people who feel the pain and the people who maintain the system. What exists, what already failed, and why.
- Deliverable
- Problem map, constraints and risks
- Decision
- You decide whether the project goes ahead.
02
Define
1 to 2 weeks
Scope cut down until it fits a first useful increment. Acceptance criteria written before any estimate.
- Deliverable
- Scope, acceptance criteria and estimate
- Decision
- A closed proposal, with price and timeline.
03
Design
1 to 2 weeks
Architecture, data contracts and measurement plan. The design is reviewed with your team before it becomes code.
- Deliverable
- Architecture, contracts and measurement plan
- Decision
- Your team signs off on the design before it becomes code.
04
Deliver
2-week cycles
Releases to production every cycle, rather than a single switch-over at the end. Problems surface early, while they are still cheap to fix.
- Deliverable
- Software in production, with tests and observability
- Decision
- You assess the result at every cycle.
05
Transfer
2 weeks
Onboarding for your team, an operations runbook and documentation. The stated goal is that the operation runs without depending on us.
- Deliverable
- Operations runbook, documentation and an autonomous internal team
- Decision
- Your team operates it with our support alongside.
Why we work this way
Short phases reduce risk on both sides. You assess concrete results before increasing the investment, and we work from clear scope instead of assumption. The engagement grows as the project proves itself.
Get in touch