The verdict in three sentences
A substantial MVP web app usually ships in 4 to 6 months in Berlin in 2026, not in "a few weeks". The schedule breaks down into scoping, design, development sprints, acceptance and go-live, each with its own risks. Announcing a launch date without a sprint-based timeline is the surest way to miss your go-live.
The five phases and their timings
A serious app project runs through five phases. Compressing them is possible on a narrow scope, but design and acceptance always get paid for, sooner or later.
| Phase | Indicative duration | Key deliverable |
|---|---|---|
| Scoping & specs | 2-3 weeks | Prioritised backlog, wireframes |
| UX/UI design | 3-4 weeks | Final mockups, design system |
| Development (sprints) | 8-16 weeks | Testable increments |
| Acceptance & fixes | 3-4 weeks | Signed acceptance report |
| Go-live | 1-2 weeks | App online, monitoring |
Added up, an ambitious MVP fits in 18 to 26 weeks, i.e. roughly 4.5 to 6 months. A simple internal tool can drop to 10-12 weeks; a complex platform exceeds 8 months.
Sprints, velocity and milestones
Development is run in two-week sprints. Velocity (points delivered per sprint) stabilises after 2-3 sprints. A team of 2-3 developers commonly delivers 20 to 35 points per sprint.
| Backlog size (points) | Velocity/sprint | Number of sprints | Dev duration |
|---|---|---|---|
| 120 | 30 | 4 | 8 weeks |
| 180 | 30 | 6 | 12 weeks |
| 240 | 30 | 8 | 16 weeks |
| 320 | 40 | 8 | 16 weeks |
Contractual milestones should target functional increments ("auth + dashboard delivered in sprint 3") rather than abstract dates. Plan a 15 to 20 % buffer for the unexpected: third-party integration, acceptance feedback, business availability.
| Delay factor | Typical impact | Countermeasure |
|---|---|---|
| Incomplete specs | +2-4 weeks | Reinforced scoping |
| Business unavailability | +1-3 weeks | Dedicated referent |
| Third-party API integration | +1-2 weeks | Upfront POC |
| Late acceptance | +2-3 weeks | Continuous acceptance |
| Scope change | +2-6 weeks | Freeze the MVP scope |
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, founder of a B2B startup in Berlin, wants to launch her SaaS platform for the autumn. Her backlog is 200 points. With a team of 3 developers at 32 points/sprint, dev fits in 7 sprints, i.e. 14 weeks.
Adding 3 weeks of scoping, 4 of design, 3 of acceptance and 1 of go-live, she gets 25 weeks, exactly 6 months. Adding an 18 % buffer, she communicates a launch window rather than a hard date: "end of Q3, start of Q4". So she kicks off in February for a calm go-live in September, without promising the impossible to her first pilot customers.
FAQ
Can you speed up by adding developers? Not linearly. Going from 2 to 4 developers raises velocity by 40-60 %, not 100 %, because of coordination. Beyond 5, returns fall.
How long for a simple internal tool? A narrow-scope business tool ships in 10 to 14 weeks, scoping and acceptance included, for 20,000 to 40,000 EUR HT.
Can acceptance be cut short? It can be continuous rather than final, but rarely removed. Always count 15 to 20 % of project time to test seriously.
Ship all at once or in batches? Incremental batch releases reduce risk and let you get value from the app earlier. It is almost always better than a big bang.
Is a 3-month timeline realistic? Yes for a very focused MVP (1-2 key journeys). For a complete multi-role business app, 3 months is a warning sign about scope depth.
Let's scope your project. Give us your target date and priority journeys: we build a sprint-based timeline with milestones and a realistic buffer. 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.
