Week 0: cut scope until it hurts
The single highest-leverage move is scoping. Find the one workflow that proves the value and cut everything else — settings pages, edge cases, the second feature. On a payroll product I shipped a deliberately narrow single-bank, monthly slice first: legally valid, genuinely useful, and months faster to revenue than 'all of payroll'. The smallest valuable slice is a discipline, not a compromise.
Decide the load-bearing parts early
Speed later depends on getting a few things right now: the tenancy model (how customers are isolated), the data schema, the auth model, and the async boundaries. These are the expensive-to-change decisions. Everything else — components, copy, most endpoints — is cheap to change, so you move fast there and don't over-think it.
The MVP is minimal on features and rigorous on foundations. Ship few features, but make tenancy, data model and billing correct — that's what lets success mean 'add features', not 'rewrite'.
A four-week shape
- Week 1: architecture + skeleton — auth, tenancy, data model, deploy pipeline, a walking skeleton in production.
- Week 2: the core workflow — the one thing that proves value, end to end.
- Week 3: billing + the rough edges — subscriptions, the empty states, the errors that matter.
- Week 4: hardening + launch — a production-readiness pass (observability, security, the obvious failure modes) and ship.
Ship weekly, steer with reality
Every week ends with something deployed you can put in front of a user. Feedback beats planning at this stage — a real user clicking through the core workflow tells you more than a month of roadmap debate. Weekly demos keep you honest and let you cut or re-prioritize before you've over-invested.
What 'production-grade' means at MVP
Not gold-plated — but not a prototype either. It has real auth, tenant isolation, error monitoring, a deploy you trust, and the security basics (secrets out of the repo, input validated, no obvious injection). Prototypes skip these; MVPs that survive traction don't.
Key takeaways
- Scope to the smallest valuable slice — cut features until it almost hurts.
- Get tenancy, data model, auth and async boundaries right up front; move fast on the rest.
- Work in weekly shippable increments and steer with real user feedback.
- Production-grade at MVP means real auth, isolation, monitoring and security basics — not gold-plating.