How we work.
Short cycles, early prototypes and transparent artifacts. Cheaper mistakes, faster launches.
Four cycles
Each cycle ends with an artifact that can be discussed and handed over.
- 01 Research
We unpack the task, users and constraints. Success criteria and scope are fixed.
Artifact: Brief and success criteria
- 02 Prototype
Flows and a clickable prototype. The key path is validated before engineering.
Artifact: Prototype and structure
- 03 Build
Iterations, demos and feedback. Tests and docs along the way, not at the end.
Artifact: Working increments
- 04 Launch and support
Release, monitoring, handover and a roadmap.
Artifact: Release and runbook
How decisions are made
- One product owner on the client side
- A demo every iteration, not at the end
- Scope changes are recorded in writing
- Code and access stay with the client
- Contested decisions are raised immediately
What can be checked
- Brief
- Prototype
- Architecture
- Repository
- Tests
- Runbook
- Roadmap
Discuss a product.
Tell us about the task — we will propose a format, team and first step.