The verdict in three sentences
In 2026, a custom business platform ships in 4 to 7 months in Dublin, split into scoping, design, development sprints and acceptance testing. The schedule isn't linear: 80 % of slippages come from rushed scoping or a scope that balloons mid-project. A plan with payment milestones tied to deliverables protects both client and vendor.
Project phases and their durations
Each phase has a goal, a deliverable and a duration. Scoping and acceptance are often underestimated, yet they determine the project's success.
| Phase | 2026 duration | Deliverable | Payment milestone |
|---|---|---|---|
| Scoping & workshops | 2 – 3 weeks | Prioritized backlog, firm budget | 20 % |
| UX/UI design & architecture | 3 – 4 weeks | Mockups, data model | 15 % |
| Development sprints | 6 – 12 weeks | Features in acceptance | 45 % (per sprint) |
| Acceptance & fixes | 2 – 4 weeks | Validated version | 15 % |
| Go-live & training | 1 – 2 weeks | Platform online | 5 % |
| Total | 4 – 7 months | Operational platform | 100 % |
A simple project (1 process, few roles) fits in 4 months. A project with third-party integrations, approval workflow and data migration pushes to 6-7 months.
Where schedules slip and how to prevent it
Delays have recurring, avoidable causes. Naming them upfront already defuses them.
| Slippage cause | Typical impact | Countermeasure |
|---|---|---|
| Insufficient scoping | +3 to 6 weeks | Workshops + backlog validated before dev |
| Scope creep | +20 to 40 % of budget | Scope management, change orders |
| Slow client decisions | +1 to 3 weeks | A single decision-maker |
| Dirty data to migrate | +2 to 4 weeks | Data audit during scoping |
| Late acceptance | Bugs in production | Continuous acceptance per sprint |
Golden rule: no coding without a validated backlog and firm budget. Agile sprints deliver testable features every 2 weeks, rather than a multi-month "tunnel effect".
Mini case study
Julien, operations director of a 60-person logistics firm in Dublin, wanted a route-tracking platform. A 3-week scoping settled the perimeter (tracking + proof of delivery, the rest in phase 2). Design 3 weeks, then 5 two-week sprints, acceptance 3 weeks. Total: 5.5 months and EUR 68,000, paid in 5 milestones. By delivering the core first (routes) and deferring secondary modules, he put V1 into service 2 months earlier than the initial "all-in-one" plan, and avoided an estimated EUR 18,000 scope slippage.
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
FAQ
How long does a business platform project take?
As a 2026 order of magnitude, count 4 to 7 months. A simple scope fits in 4 months; with integrations, approval workflow and data migration, plan 6 to 7 months.
Why does scoping take 2 to 3 weeks?
Because that's where scope, backlog and firm budget are set. Rushed scoping is the leading cause of slippage: investing 2-3 weeks often avoids 6.
What is a payment milestone?
It's a payment tied to a validated deliverable (scoping, mockups, sprints, acceptance). It shares the risk: you pay as value is delivered, not upfront on nothing.
Can the project be accelerated?
Yes, by trimming the V1 scope and deferring secondary modules to phase 2. Adding developers doesn't speed things up linearly: past a team size, coordination slows down.
What happens during acceptance testing?
The client tests each feature against the acceptance criteria set at scoping. Fixes are integrated, then the version is validated before go-live. Count 2 to 4 weeks.
Let's scope your project. Give us your perimeter, target deadline and integrations, and we'll draw up a phased plan with payment 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.
