The verdict in three sentences
A requirements specification of 15 to 30 pages brings the gap between three business app quotes down from 60% to about 20%, which finally makes offers comparable. For a Toronto SME, a scoping workshop of 2 to 5 days costs EUR 2,000 to 6,000 (about CAD 3,000 to 9,000) in 2026 and prevents most change orders mid-project. The document must contain prioritised user stories, acceptance criteria and a clear clause on code ownership.
The template outline in 9 sections
A good spec describes the need, not the technical solution. It leaves technology choices to the developer while setting what the application must do, for whom and under which constraints.
| Section | Expected content | Pages |
|---|---|---|
| 1. Context and goals | business, problem, 3 to 5 measurable success indicators | 1 to 2 |
| 2. Users and roles | profiles, headcount, permissions, mobile or desktop use | 1 to 2 |
| 3. Current processes | workflow diagram, existing tools, pain points | 2 to 4 |
| 4. Prioritised user stories | 30 to 80 stories ranked MoSCoW | 5 to 12 |
| 5. Data and integrations | volumes, legacy data migration, ERP, accounting, APIs | 2 to 3 |
| 6. Non-functional constraints | performance, security, PIPEDA privacy, hosting, accessibility (AODA) | 1 to 2 |
| 7. Acceptance criteria | validation conditions for each critical story | 2 to 3 |
| 8. Timeline and indicative budget | milestones, deadline, budget range | 1 |
| 9. Contract terms | code ownership, maintenance, reversibility, warranty | 1 to 2 |
Stating a budget range (for example EUR 40,000 to 60,000) does not weaken your position: developers calibrate their answer instead of guessing, and you get genuinely comparable offers.
User stories and MoSCoW prioritisation
A user story follows the form "As a [role], I want [action] so that [benefit]". The MoSCoW method ranks each story as Must, Should, Could or Won't (out of scope for this version). It lets you split the project into a first version shipped quickly, followed by enhancements.
| Priority | Share of stories | Example for a field service app | Budget effect |
|---|---|---|---|
| Must | 50 to 60% | the technician enters the report and customer signature on mobile | V1 core |
| Should | 20 to 25% | the customer receives the PDF report by email automatically | V1 if budget allows |
| Could | 10 to 15% | profitability dashboard per job | V2 |
| Won't (this version) | 5 to 10% | native iOS app | excluded, avoids misunderstandings |
Mistakes that blow up quotes
The 60% gap between quotes almost always comes from a vague document: each developer pictures a different scope. Here are the costliest mistakes seen in 2026.
| Mistake | Consequence | Typical cost | Fix |
|---|---|---|---|
| Need described in 2 pages | quotes from EUR 25,000 to 70,000 for the same project | 60%+ gap | 15 to 30 structured pages |
| No prioritisation | everything is "essential" | +30 to 50% budget | MoSCoW |
| Data migration forgotten | mid-project change order | EUR 3,000 to 12,000 | volumes and formats in section 5 |
| No acceptance criteria | dispute at sign-off | 2 to 6 weeks delay | verifiable conditions per story |
| Code ownership unspecified | locked to the developer | switching impossible | written IP assignment |
| Maintenance not priced | surprise after delivery | 15 to 20% of build per year | ask for an annual package |
On ownership, require a written assignment of intellectual property in the custom code, the code in a Git repository in your name and deployment documentation. Open source components stay under their original licence.
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.
Karim, owner of an HVAC maintenance SME in Toronto, consults three developers with a 2-page brief. He receives EUR 28,000, 45,000 and 72,000: impossible to compare.
He pays for a 4-day scoping workshop at EUR 4,800, which produces a 24-page spec and 52 user stories, 30 of them Must. New round: EUR 46,000, 51,000 and 55,000, a gap reduced to 20%. He picks the EUR 51,000 offer with a V1 in 12 weeks. The workshop saves him an estimated EUR 8,000 data migration change order and a false start: scoping pays for itself before the first line of code.
FAQ
How many pages should a business app spec have?
Between 15 and 30 pages for an application in the EUR 30,000 to 150,000 range. Below 10 pages, quotes diverge by 50 to 60%.
How much does a scoping workshop cost?
Budget EUR 2,000 to 6,000 (about CAD 3,000 to 9,000) for 2 to 5 days with a project manager and a senior developer. The deliverable is a spec any developer can work from.
Should the budget appear in the spec?
Yes, a range is enough. It lets developers adapt the V1 scope and narrows the gap between offers.
What is the MoSCoW method?
It ranks each feature as Must, Should, Could or Won't. In practice, 50 to 60% of stories as Must is enough for a first version shipped in 10 to 14 weeks.
How do I secure code ownership?
Include a written IP assignment for the custom code, a Git repository in your name and delivery of documentation. Without a written clause, the developer generally keeps the copyright.
Let's scope your project. Tell us about your business, your users and your pain points: we offer a scoping workshop between EUR 2,000 and 6,000 and a spec delivered in 1 to 2 weeks. 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.
