The verdict in three sentences
A Toronto SMB asking for a quote on a business web application without a requirements document gets proposals that vary by a factor of four, because each vendor imagines a different scope. A 12-section requirements document, MoSCoW-prioritised user stories and clickable prototypes (6,000 to 12,000 CAD) bring that gap under 25 %. Development then lands between 60,000 and 180,000 CAD, over 3 to 6 months.
The 12 essential sections
A good requirements document runs 15 to 30 pages. It describes the need, not the technology: proposing the architecture is the vendor's job.
| No. | Section | What it must contain |
|---|---|---|
| 1 | Context and goals | Business, current problem, 3 measurable goals (e.g. -50 % manual data entry) |
| 2 | Users and roles | Profiles, headcount, permissions (owner, sales, accounting, customer) |
| 3 | Functional scope | Module list, what is in and explicitly out |
| 4 | Prioritised user stories | 'As a…, I want…, so that…', ranked MoSCoW |
| 5 | Key journeys | 3 to 5 end-to-end scenarios step by step |
| 6 | Data and migration | Volumes, existing spreadsheets to import |
| 7 | Integrations | QuickBooks or Xero, ERP, Stripe or Moneris, SMS, email |
| 8 | Technical constraints | Canadian hosting, browsers, mobile, offline |
| 9 | Security and compliance | PIPEDA and Ontario rules, backups, audit logs |
| 10 | Languages and accessibility | English, French if serving Quebec, AODA and WCAG 2.1 AA |
| 11 | Deliverables and acceptance | Prototypes, source code, documentation, acceptance criteria |
| 12 | Budget, timeline and maintenance | Indicative envelope, milestones, expected support, exit terms |
Section 12 is often skipped. Stating an envelope, even a wide one, avoids proposals out of reach and lets vendors make sensible trade-offs.
Prioritise with MoSCoW and price each level
MoSCoW ranks each user story as Must (needed at launch), Should (important but can wait), Could (nice to have) and Won't (out of scope for this release). It lets you ask vendors for a price per level and compare like for like.
| Item | Without requirements | With requirements and prototypes |
|---|---|---|
| Gap between quotes | Factor of 4 (e.g. 45,000 to 180,000 CAD) | Under 25 % |
| Preparation cost | 0 CAD | 6,000 to 12,000 CAD for prototypes, plus 5 to 10 internal days |
| Change orders during project | 25 to 40 % of initial budget | 5 to 10 % |
| Development timeline | Often 50 % over | 3 to 6 months held within 10 % |
| Development budget (2026 order of magnitude) | Unpredictable | 60,000 to 180,000 CAD |
| Acceptance | Disputes over 'what was agreed' | Written acceptance criteria |
| Exit terms | Rarely planned | Source code and documentation delivered |
Clickable Figma prototypes, built in 2 to 4 weeks, are the best investment in the project: they surface gaps before the first line of code.
How to compare the three quotes
Send the same pack to three vendors with a mandatory response grid: price per MoSCoW level, milestone plan, assigned profiles, support and exit terms. Score each response out of 100, for example 40 for understanding of the need, 30 for price, 15 for timeline and 15 for maintenance. Be wary of the lowest quote if it does not address your user stories one by one.
Mini case study
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
Ryan, owner of an industrial parts distributor in Toronto, first asked for three quotes based on a one-page brief: 45,000, 110,000 and 180,000 CAD. He then invested 9,000 CAD in clickable prototypes and wrote a 22-page requirements document with 46 user stories, 28 of them Must. The new quotes came in at 95,000, 105,000 and 116,000 CAD. He chose the second, scored best on understanding of the need. By keeping change orders around 8 % instead of the usual 30 %, he avoided about 23,000 CAD of overrun, 2.5 times the prototype cost.
FAQ
How much does writing a web app requirements document cost in Toronto?
Written in-house, it takes 5 to 10 days of work. With vendor help and clickable prototypes, expect 6,000 to 12,000 CAD in 2026.
How much does development then cost?
Between 60,000 and 180,000 CAD for an SMB, depending on modules and integrations. Timelines run 3 to 6 months.
Should the document specify the technology?
No, unless there is a real constraint such as an existing ERP or mandated hosting. Describing the need lets 3 vendors propose their best solution at equal budget.
What is MoSCoW?
It ranks each feature as Must, Should, Could or Won't. In practice Musts are 50 to 60 % of user stories and are enough for a launch in 3 to 4 months.
What legal requirements apply in Ontario?
PIPEDA governs personal data and AODA requires accessible web content for organisations with 50+ employees. Plan for backups, access logs and an exit clause in the contract.
Let's scope your project. Send us your need, even on one page, and we will help structure the requirements, price the prototypes and estimate development in CAD. 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.