The verdict in three sentences
A web app MVP ships in 10 to 12 weeks in 2026 for a well-scoped set of 15 to 25 user stories. The timeline holds if the team keeps a velocity of 20 to 30 points per sprint and the backlog is frozen before the first sprint. Every week of delay costs roughly 4,500 EUR in mobilized team plus the lost revenue of a later launch.
The typical sprint calendar
An MVP is not run on gut feel: it is broken into measurable phases. Here is the reference plan for a Toronto product director who wants a reliable launch date.
| Phase | Duration | Deliverable | Indicative cost |
|---|---|---|---|
| Scoping | 1 week | Prioritized backlog, personas, non-goals | 3,500 EUR |
| UX/UI design | 2 weeks | Clickable mockups, design system | 7,000 EUR |
| Sprint 1 | 2 weeks | Auth + data foundation | 9,000 EUR |
| Sprint 2 | 2 weeks | Core feature part 1 | 9,000 EUR |
| Sprint 3 | 2 weeks | Core feature part 2 + dashboard | 9,000 EUR |
| QA + go-live | 1 week | Tests, fixes, deployment | 4,500 EUR |
| Total | 10 weeks | MVP in production | 42,000 EUR |
This Gantt plan holds for 15 to 25 user stories. Beyond 25, add a sprint (2 weeks and ~9,000 EUR) rather than compress.
Velocity, budget and the cost of delay
Velocity is the backbone of the timeline. A team delivering 25 points per sprint absorbs a 75-point backlog in 3 sprints; at 15 points, it takes 5. Here is the impact.
| Velocity/sprint | Sprints for 75 pts | Dev time | Dev budget | Risk |
|---|---|---|---|---|
| 30 points | 3 sprints | 6 weeks | 27,000 EUR | low |
| 25 points | 3 sprints | 6 weeks | 27,000 EUR | low |
| 20 points | 4 sprints | 8 weeks | 36,000 EUR | medium |
| 15 points | 5 sprints | 10 weeks | 45,000 EUR | high |
| Backlog not frozen | +1 to 2 sprints | +2 to 4 wk | +9 to 18,000 EUR | very high |
One week of delay ties up the team (1 lead + 1 dev + 0.5 UX) for about 4,500 EUR, before counting deferred revenue. Freezing the backlog before sprint 1 is the best anti-slippage insurance.
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
Mini case study
Sophie, product director of a SaaS scale-up in Toronto, plans an MVP of 22 user stories (72 points). At a velocity of 24 points/sprint, she wraps dev in 3 sprints. With scoping, design and QA, her launch date lands at 10 weeks for 42,000 EUR. She had first left the backlog open: two story additions mid-way would have added a sprint — 9,000 EUR and 2 weeks. By freezing scope and pushing those stories to post-MVP, she held the date and saved that 9,000 EUR.
FAQ
Can you ship an MVP in under 8 weeks? Rarely without sacrificing quality: below 8 weeks you cut QA or design, which costs more later. 10 to 12 weeks remains the 2026 standard for a serious MVP.
What blows up the timeline? An unfrozen backlog, vague acceptance criteria and slow client sign-offs. These three causes easily add 2 to 4 weeks and 9,000 to 18,000 EUR.
How many user stories in an MVP? 15 to 25 stories for one core feature. Beyond that, every 25-point chunk adds a two-week sprint and about 9,000 EUR.
What is velocity and why track it? It is the number of points delivered per sprint. Knowing it lets you estimate sprint count, hence date and budget: 20 to 30 points/sprint is a realistic 2026 range.
What does a week of delay really cost? Around 4,500 EUR in mobilized team, plus the lost revenue of a later launch. That is why freezing the backlog is the priority.
Let's scope your project. Send us your user story list and target date, and we return a sprint plan with a firm budget. Detailed quote within 48 h. WhatsApp +221 77 596 93 33.
Mohamed Bah
Fondateur, Kolonell
Passionate about digital and entrepreneurship in Africa, Mohamed has been helping Sénégalese businesses with their digital transformation since 2020. Founder of Kolonell, he believes every SME deserves a professional and accessible online présence.
