From Idea to MVP in 12 Weeks: How We Scope the First Release
Most products fail in scope, not in code. The discovery, milestones and trade-offs that let a compact senior team ship a usable first version in three months.
By Solomiia Kots
CEO at Mirko
Discovery is where the schedule is won
A two-week discovery phase defines the user, the core job to be done and the one metric that proves the product works. Everything that does not serve that metric moves to the backlog. The output is a fixed scope with milestones, so delivery dates are visible before development starts.
The 12-week rhythm
A typical plan
- Weeks 1-2: discovery, architecture, UX flows and clickable prototype.
- Weeks 3-8: core features in two-week sprints with demos every Friday.
- Weeks 9-10: integrations, payments, analytics and admin tools.
- Weeks 11-12: QA, performance, security review and launch.
A trading community platform with TradingView charts, instrument-based chat rooms and authentication reached its first release in 12 weeks on exactly this rhythm. The chat had to handle hundreds of messages per minute, which is why throughput was designed in week one, not optimised in week eleven.
Trade-offs that keep the date
Buy, do not build, anything that is not the product: auth, payments, email, analytics. Ship one platform first when mobile and web are both wanted. Prefer a boring, proven stack over the newest framework. These decisions are reversible later; a missed launch is not.
