Playbook
Pricing your MVP before you build
Fixed-price scoping: how we estimate MVPs without scope creep eating the margin.
Fixed-price MVPs only work when scope is honest. Here's how we estimate before signing.
Start with one workflow
We ask: "What's the one thing a user must be able to do on day one?" Everything else goes on a "not in v1" list.
Count integrations
Auth, payments, email, and AI each add a day. We price them explicitly, not as surprises mid-sprint.
Buffer for unknowns
We add 10–15% buffer for integration quirks, but we eat overruns on fixed-price work, not the client.
The proposal
Every estimate ships as a written doc: scope, deliverables, timeline, price, and what's explicitly out of scope.
Related
- 01
Async client communication that actually works
Daily updates, Loom walkthroughs, and decision logs. How we run projects without daily standups.
Guide · 5 min read - 02
The scope creep antidote
One core workflow, written success metrics, and a 'not in v1' list. Our sprint scoping ritual.
Playbook · 5 min read
Want this built for you?
Fixed-scope MVP sprints and AI integrations. Same stack as this guide.