1–2 weeks
Discovery
Brief, research, scope and a written estimate.
Result
- Product brief
- scope
- estimate
Process
How a product gets built.
Five phases with fixed decision points. You always know what is being built, what it costs and what comes next.
From brief to release.
1–2 weeks
Discovery
Brief, research, scope and a written estimate.
Result
- Product brief
- scope
- estimate
2–4 weeks
Design
Interface, design system and a clickable prototype.
Result
- Design system
- prototype
4–12 weeks
Build
Iterative development with weekly releases to staging.
Result
- Working product on staging
1 week
Launch
Hardening, performance, data migration and release.
Result
- Production release
ongoing
Evolve
Support, measurement and the next iterations.
Result
- Roadmap
- monthly releases
The first release usually lands 2–4 months after kick-off. After that, the product keeps growing with you.
Questions
Before we start.
Who owns the code and designs?
You do, from the first day. Repositories, design files and accounts are created in your name or transferred on request.
How do you estimate?
After discovery we write a scope with priorities and an estimate range. Anything outside the scope is estimated separately before it is built.
How do we stay in touch?
A weekly demo of working software, a shared board with every task and decision, and a direct channel with the people doing the work.
Can you work under NDA?
Yes. We are happy to sign a mutual NDA before you share details of the product.
What happens after launch?
Most products continue as a partnership: monitoring, fixes and monthly releases. You can also take the product in-house — it is documented for that.
Do you work with existing products?
Yes. We start with a short technical and design review, then agree what to improve first.