The verdict in three sentences
A web MVP ships in 8 to 16 weeks and a full platform in 4 to 9 months, including discovery, development, testing, UAT and go-live. Project owners systematically underestimate the invisible phases: scoping, UAT, data migration and post-launch fixes. The remedy is incremental delivery: instead of a 9-month big bang, you go live every 2-3 weeks to validate early and reduce risk.
The typical phase-by-phase schedule
A well-run project splits into clear phases, each with its deliverables. The percentages below apply to total duration, not budget.
| Phase | Share of timeline | Key deliverables |
|---|---|---|
| Discovery & scoping | 10 – 15% | Prioritized backlog, mockups, architecture |
| UI/UX design | 10 – 15% | Design system, approved screens |
| Development | 45 – 55% | Features in 2-week sprints |
| Testing & QA | 10 – 15% | Automated tests, fixes, security |
| Client UAT | 5 – 10% | Business validation, adjustments |
| Deployment & stabilization | 5 – 10% | Go-live, data migration, monitoring |
Timeline ranges by project type
These 2026 durations assume a dedicated team and a client available for UAT. A client slow to validate can add 20 to 40% to the schedule.
| Project type | Realistic timeline | Nb of sprints | Time-to-first-value |
|---|---|---|---|
| Advanced landing / brochure site | 3 – 6 weeks | 2 – 3 | 3 weeks |
| Application MVP | 8 – 16 weeks | 4 – 8 | 6 – 8 weeks |
| Internal business tool | 3 – 5 months | 6 – 10 | 8 weeks |
| Full client application | 4 – 7 months | 8 – 14 | 10 weeks |
| Multi-module platform / SaaS | 6 – 9 months | 12 – 18 | 12 weeks |
What stretches timelines
Delays rarely come from the code itself. The big culprits are slow client-side validation (+20-40%), scope creep mid-project (+15-30%), unforeseen third-party integrations (+2-6 weeks) and underestimated data migration (+2-8 weeks). Fixing scope per milestone and naming a single decision-maker on the client side are the two most effective levers.
Mini case study
Aminata, COO of a fintech in Dakar, wants to launch a web client portal. As a big bang, the estimate was 7 months before any value. By opting for incremental delivery, the first module (balance and history view) goes live in 8 weeks, then one module every 3 weeks. Result: business value arrives 4 months earlier, user feedback corrects course from sprint 2, and the migration budget is smoothed instead of a final spike. Time-to-market drops from 7 months to 2 months for the first useful feature.
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
FAQ
Why does my real timeline always exceed the estimate?
Because the invisible phases (scoping, UAT, migration, fixes) are forgotten in naive estimates. They weigh 30 to 40% of the total schedule.
Can we speed up by adding developers?
Rarely beyond a point: past 5-6 developers on the same module, coordination cancels the gain. Better to parallelize independent modules.
How long to a first go-live?
With an incremental approach, 6 to 8 weeks are enough to ship a first useful function. It is the best way to de-risk the project.
What is the impact of changing scope?
Each unplanned addition stretches the timeline by 15 to 30%. A prioritized backlog and a budget per milestone absorb changes without overrun.
Should everything be tested before launch?
You test continuously, not at the end. Automated tests and UAT per increment avoid tunnel effect and nasty go-live surprises.
Let's scope your project. Describe your scope and target date: we propose a sprint-based schedule with a first go-live within 8 weeks. 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.
