The verdict in three sentences
In Toronto in 2026, a custom web application ships in 8 to 14 weeks for an MVP and 4 to 9 months for a full version, after 2 to 4 weeks of discovery. QA and acceptance take 15 to 20% of total time and it is the phase optimistic plans sacrifice first. A week of delay costs USD 4,300 to 13,000 depending on team size: the date you announce to customers must include a buffer, not a wish.
Timeline benchmarks by phase and project type
Duration depends less on the number of screens than on the number of business rules, integrations and decision makers. A customer portal with five roles and an ERP sync takes longer than a twenty-screen consumer app with no complex back office.
| Phase | MVP (2026 order of magnitude) | Full application | Expected deliverable |
|---|---|---|---|
| Discovery and workshops | 2 weeks | 3 to 4 weeks | Prioritized backlog, key mockups, estimate |
| UX/UI design | 2 to 3 weeks | 4 to 6 weeks | Validated clickable prototype |
| Development | 5 to 8 weeks | 3 to 6 months | Increments delivered every 2 weeks |
| Integrations (ERP, payments, SSO) | 1 to 2 weeks | 3 to 8 weeks | Connectors tested on real data |
| QA and fixes | 2 weeks | 4 to 7 weeks | Signed acceptance report |
| Go-live and hypercare | 1 week | 2 to 3 weeks | Monitoring, reinforced support |
| Total | 8 to 14 weeks | 4 to 9 months | Phases partly run in parallel |
Design and development overlap in agile delivery: the first validated screens go into development while the next ones are designed. That overlap is what makes a 10-week MVP possible instead of 16.
Why projects slip, and what a week costs
In the projects we take over, three causes explain most delays. Scope creep, often 20 to 40% without formal trade-offs. Slow approvals on the client side: a screen waiting ten days for a decision blocks two developers. Late-discovered integrations: an undocumented ERP API can add three weeks on its own.
| Team size | Typical makeup | Cost per week (USD) | Cost of a one-month delay |
|---|---|---|---|
| Small team | 1 full-stack dev + PM at 30% | 4,300 - 6,000 | 17,000 - 24,000 |
| Standard team | 2 devs + designer at 50% + PM | 7,000 - 9,200 | 28,000 - 37,000 |
| Reinforced team | 3 devs + QA + designer + PM | 9,700 - 13,000 | 39,000 - 52,000 |
| Client delay (pending approval) | Team partly idle | 50 to 70% of weekly cost | Often billed time and materials |
| Unmanaged scope change | Rework on delivered features | +15 to 30% effort | Varies |
| Underestimated ERP integration | Developer blocked | 1 to 3 weeks added | 4,300 - 39,000 |
On top of the direct cost comes the opportunity cost: customers notified, marketing campaign pushed back, contracts starting later. For a B2B SaaS targeting USD 16,000 in monthly revenue, a one-month slip means USD 16,000 lost on top of the team cost.
How to announce a reliable date
Announce a date only after discovery, never based on a first quote. Add a 15 to 20% buffer to the agency's plan. Appoint a single decision maker on the client side committed to answering within 48 hours. Split features into must-have and nice-to-have: if the plan slips, the nice-to-haves leave release 1, the date does not move. Finally, require a demo every two weeks on an accessible environment: it is the best indicator of real progress.
Mini case study
Julien, CEO of an electrical equipment distributor in Toronto, wants to launch a B2B ordering portal for 600 trade customers before the September trade show. A 3-week discovery leads to an 11-week MVP with a standard team at USD 8,100 per week, about USD 89,000 of development. He adds 2 weeks of buffer and starts on March 2 for a target delivery on June 15.
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
The integration with his Sage ERP ends up taking 2 weeks longer than planned. Thanks to the buffer and moving the quote feature to release 2, the portal goes live on June 29, two months before the show. Without a buffer, he would have paid a 2-week reinforcement at USD 10,300 per week, i.e. USD 20,600 extra, or announced a delay to his customers.
FAQ
Can an MVP ship in under 8 weeks?
It is possible for a very focused scope, 5 to 8 screens with no heavy integration, in 5 to 6 weeks. Beyond that, compressing the plan mostly degrades QA and increases production bugs by 30 to 50%.
Is discovery really needed if I already have a specification?
Yes, but it can shrink to 1 or 2 weeks. It confronts the specification with technical constraints and produces a committed estimate within 15% rather than 50%.
Fixed price or time and materials: which protects the timeline better?
Fixed price locks the budget but makes every change costly and slow to negotiate. Fixed price per 6 to 8 week release combines budget visibility and flexibility.
Does adding developers speed up a late project?
Rarely in the short term: a new developer needs 1 to 2 weeks to become productive. Reinforcement only helps if at least 8 weeks of development remain.
How much time should I plan after go-live?
Plan 2 to 4 weeks of hypercare with an available team, then maintenance of 8 to 15% of the initial budget per year.
Let's scope your project. Share your target date and scope: we will build a realistic plan with discovery, MVP and buffer, for an indicative budget of USD 43,000 to 130,000 depending on the team. 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.
