MVP
The first product, in ten weeks, without technical debt
Not a prototype to launch and throw away: an MVP that holds the first thousand users and the growth that follows.
An MVP is not a half-finished product: it is a product with the right features and the rest excluded with judgement. Our job is working out what to exclude, and building in a way that adding the rest later does not cost a rewrite.
- 10
- weeks from brief to release
- 1
- sprint every two weeks
- 0
- hidden costs at project end
The problem
The gap between idea and launch
The gap between idea and launch
If validating an idea takes a year, the idea dies before it is tested. And meanwhile the market moves.
The prototype does not hold
The code written to demonstrate the idea collapses at the first real user. And then everything gets rewritten.
Unpredictable costs
A team that scales with the company, but that also scales with cloud spend and the unexpected.
Nobody in the team knows how it works
The product lives in one person's head. When that person goes on holiday, the project stops.
What changes with us
Scope negotiated, not inherited
Scope negotiated, not inherited
We start with a hypothesis about scope and revisit it every sprint. Anything that does not serve user testing does not enter.
Architecture that grows
A modular monolith with clear boundaries: it splits when it has to, not before. The product stays understandable.
The team learns to do it alone
Pairing, documentation and working in your repository: the goal is that you will not need us.
Metrics from day one
Events, funnels and cohorts wired from the first release, so every later decision is based on data.
How we work
Week 1: the objective
- 01
Week 1: the objective
We define the hypothesis to test and the signal that would confirm or refute it.
- 02
Weeks 2-3: prototype
The main flow, navigable, not yet pleasant. It is there to understand, not to impress.
- 03
Weeks 4-9: build
Development in sprints with backend, auth, payments and whatever the test actually needs.
- 04
Week 10: launch
Release, monitoring and measurement. From there you decide whether and how to invest further.
Frequently asked questions
What is the difference between an MVP and a prototype?
What is the difference between an MVP and a prototype?
Do you accept equity instead of fees?
What if the test fails?
How do you know what it will cost?
Let's talk
Thirty minutes and an honest assessment. If working together makes no sense, we will say so.
Tell us the hypothesis you want to test. We reply with a scope and a plan, or with honest advice.
Related services
Custom software