The verdict in three sentences
In 2026, an MVP web app goes live in 10-16 weeks with a team of 2-3 developers on two-week sprints. The critical path is not the code: scoping (1-2 weeks) and QA (1-2 weeks) decide the launch date. Third-party integrations (payments, GDPR, partner APIs) are the top stretch factors, often +2 to +4 weeks.
The typical MVP plan
An MVP is steered by milestones, not one deadline. Here is a realistic sequence for a raise-ready product.
| Phase | Duration | Deliverable | Who |
|---|---|---|---|
| Scoping & user stories | 1-2 wks | Prioritised backlog, MVP scope | PO + founder |
| UX/UI design | 2-3 wks | Clickable Figma mockups | Designer |
| Dev sprint 1-2 | 4 wks | Foundation + auth + core module | 2-3 devs |
| Dev sprint 3-4 | 4 wks | Remaining features + integrations | 2-3 devs |
| QA & fixes | 1-2 wks | Tested app, blockers cleared | QA + PO |
| Deployment | 3-5 days | Go-live, monitoring | DevOps |
With a velocity of about 40 points per sprint, a 150-160 point MVP fits in 4 sprints.
What stretches (or shortens) the timeline
The same scope can vary twofold depending on these factors. Anticipate them at scoping.
| Factor | Timeline impact | Countermeasure |
|---|---|---|
| Payment integration (Wave/OM/Stripe) | +1 to +3 wks | Start API access very early |
| GDPR compliance / register | +1 to +2 wks | Scope data during design |
| Slow client decisions | +2 to +4 wks | One decider, weekly reviews |
| Scope creep | +variable | Freeze MVP scope in writing |
| Existing data migration | +1 to +3 wks | Audit data quality upfront |
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
Maeve, founder of a B2B startup in Dublin, targets a raise in 5 months and must show traction. We lock an MVP at 145 points: onboarding, dashboard, one business module, Stripe payment. At 40 points/sprint over 3 devs, dev fits in 4 sprints (8 weeks); with 1.5 weeks scoping, 2.5 design and 1.5 QA, go-live lands at ~13.5 weeks. By freezing scope and using one decider, she secures a product demo 6 weeks before her first investor meeting.
FAQ
Can an MVP ship in 6 weeks? Rarely from scratch: 6 weeks suits an ultra-reduced scope (1 module, no heavy integration). Below 10 weeks, you mostly cut QA, which costs you later.
Must design be finished before coding? Not fully: you deliver mockups for sprint 1 screens, then design runs in parallel with dev. Waiting for 100 % design needlessly freezes the calendar.
How many developers are optimal? 2-3 for an MVP: beyond that, coordination costs more than it returns. Adding a developer does not halve the timeline.
Can GDPR delay launch? Yes if discovered late: scoping personal data and the register during design avoids 1-2 weeks of rework before launch.
What happens after the MVP? You enter continuous iteration: usage measurement, fixes, new features in two-week sprints, usually under a maintenance or T&M contract.
Let's scope your project. Give us your target launch date and the 3-5 must-have features, and we return a dated plan and an MVP 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.
