The verdict in three sentences
A client portal is scoped in 2-3 weeks, reaches a deliverable MVP in 8-12 weeks through two-week sprints, and a full version in 4-7 months. The agile method (sprints, fortnightly demos) secures the timeline provided a client-side product owner is available 20-30% of their time. The two main delay factors are incomplete specs (+30%) and third-party integrations (+2 to 4 weeks).
The phase-by-phase plan
A portal project breaks into phases with clear deliverables. Each phase ends with a milestone that triggers billing and validates moving to the next. Here is a typical 2026 plan for a medium-complexity portal.
| Phase | Duration | Deliverable | Billing milestone |
|---|---|---|---|
| Scoping / discovery | 2-3 weeks | Prioritised backlog, specs | 30% at order |
| UX/UI design | 2-3 weeks | Approved mockups, design system | included |
| Development (sprints) | 6-14 weeks | Functional increments | 40% in progress |
| UAT | 2-3 weeks | Acceptance report, fixes | included |
| Go-live | 1 week | Deployment, training | 30% at delivery |
An MVP covering authentication, documents and notifications fits the low end of the range (8-12 weeks end to end). A full version with invoicing, messaging and dashboards spreads over 4-7 months depending on effort and business-team availability.
Agile or waterfall, and the delay factors
The methodology choice drives flexibility and timeline control. Agile now dominates for portals, but waterfall still makes sense for very fixed scopes.
| Criterion | Agile (2-week sprints) | Waterfall (V-model) |
|---|---|---|
| Progress visibility | Demo every 2 weeks | Delivery at project end |
| Scope flexibility | High, reorderable backlog | Low, frozen at start |
| Required PO availability | 20-30% | 10-15% |
| Tunnel-effect risk | Low | High |
| Suited to | Evolving scope | 100% stable specs |
The most frequent delays are quantifiable: incomplete specs lengthen the project by +30% on average (back-and-forth, rework), third-party integrations (ERP, SSO, payment) add 2 to 4 weeks, and an unavailable product owner can double UAT time. Anticipating these three factors at scoping is the best lever for hitting deadlines.
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
Elodie, project director of an SME, must deliver a client portal before a trade show in 5 months. The vendor proposes a 10-week MVP then 2 enrichment sprints. By dedicating an internal product owner to 25% of their time (about 1.25 days/week) and locking specs at scoping, she avoids the 30% overrun tied to vague specs, i.e. about 14,000 EUR saved on a 46,000 EUR budget, and hits the show date with 3 weeks of margin.
FAQ
How long for a client portal MVP? Count 8 to 12 weeks end to end, scoping included, for a scope centred on authentication, documents and notifications.
How much product owner availability is needed? 20 to 30% of their time, i.e. 1 to 1.5 days a week, to validate increments and answer questions without blocking sprints.
What are the main delay factors? Incomplete specs (+30%), third-party integrations (+2 to 4 weeks) and unavailable approvers during UAT.
Agile or waterfall for a portal? Agile dominates because it gives visibility every 2 weeks and absorbs adjustments. Waterfall is only justified on a 100% frozen scope.
Can I speed up without sacrificing quality? Yes, by reducing the MVP scope (fewer modules) rather than compressing UAT, and by putting two developers in parallel on independent workstreams.
Let's scope your project. Give us your target date and priority modules, and we'll build a realistic agile plan with billing milestones. 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.
