The verdict in three sentences
Announcing a go-live date without a milestone plan is promising your committee a delay. In 2026, a brochure redesign fits in 6-10 weeks, a corporate site in 12-18 weeks, a group site in 20-30 weeks. The real risk is not the tech but content delivery: when late, it extends a project by 22% on average.
The timeline by phase and tier
Phases partly overlap (design and content run in parallel). Here is the typical 2026 split in weeks.
| Phase | Brochure | Corporate | Group |
|---|---|---|---|
| Discovery & specs | 1-2 wks | 2 wks | 2-3 wks |
| UX/UI design | 2 wks | 3-4 wks | 4-6 wks |
| Development | 2-3 wks | 4-6 wks | 8-12 wks |
| Content & migration | 2 wks | 3-5 wks | 4-8 wks |
| UAT & accessibility | 1 wk | 2-3 wks | 3-5 wks |
| Go-live | 0.5 wk | 1 wk | 1-2 wks |
| Realistic total | 6-10 wks | 12-18 wks | 20-30 wks |
Content (the most underestimated phase) is the top drift factor: it starts too late and blocks acceptance testing.
Where delays hide
A credible project manager prices the risk, not just the ideal duration. Here are the 2026 delay causes and their average impact.
| Delay cause | Frequency | Timeline impact |
|---|---|---|
| Late content delivery | Very common | +22% |
| Slow internal approvals | Common | +10-15% |
| Scope creep | Common | +15-30% |
| Heavy data migration | Medium | +5-10% |
| Unplanned accessibility UAT | Medium | +1-2 wks |
| ERP/CRM integration | Varies | +2-4 wks |
2026 rule: add a 15% safety margin to the theoretical plan before you communicate a date to the committee.
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
Thomas, digital project manager at a 600-employee logistics mid-cap in Nantes, must announce a go-live date for a 40-page EN/FR corporate site. The theoretical plan gives 14 weeks. He applies the 15% margin (+2 weeks) and sets a content-delivery deadline at week 6. Result: content delivered on time, accessibility UAT cleared in 2 weeks, go-live at week 16 as announced. Compared with his previous rebuild (announced at 12 weeks, delivered at 19), he saves 3 weeks of drift and, above all, his credibility with the board.
FAQ
Can a corporate site ship in under 12 weeks? Rarely without sacrificing UAT or content. Below 10 weeks you are describing a brochure site, not a governed institutional one.
Why does content delay projects so much? Because it depends on internal teams (legal, HR, leadership) not dedicated to the project. Delivered late, it extends the project by 22% on average.
Is development the longest phase? No for a brochure site, yes for a group. On a group site, development runs 8-12 weeks due to multi-subsidiary integrations.
How do I hold the date announced to the committee? Three levers: a 15% margin, a content deadline, and a scope freeze after discovery. Scope creep alone adds 15-30%.
How long for UAT and accessibility? From 1 week (brochure) to 5 weeks (group). Plan the accessibility audit from discovery to avoid a +1-2 week hit at the end.
Let's scope your project. Tell us the target tier (brochure, corporate, group) and your deadline and we will build a realistic milestone plan and the matching 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.
