The verdict in three sentences
An 8 to 15 page specification is enough to consult three serious vendors, as long as it describes usage rather than screens. MoSCoW-prioritised user stories bring the spread between quotes down from 1 to 3 to roughly 1 to 1.5 on average. If your need is still fuzzy, fund a 3,000 to 8,000 EUR discovery phase before committing an application budget of 30,000 to 80,000 EUR.
The template in 9 sections, page by page
The operations director of a technical services SME does not need a 60 page document. They need a text that three agencies will read the same way. Here is the structure we recommend, with the target length of each section.
| Section | Expected content | Pages | Common mistake |
|---|---|---|---|
| 1. Context and goals | Business, headcount, 3 measurable goals (e.g. -20% re-keying) | 1 | Vague goals like improving efficiency |
| 2. Users and roles | 3 to 6 profiles, volumes (e.g. 40 technicians, 5 planners) | 1 | Forgetting admin and customer profiles |
| 3. MoSCoW user stories | 25 to 60 stories, each with an acceptance criterion | 3 to 5 | Describing buttons instead of needs |
| 4. Data and integrations | ERP, accounting, SSO, existing APIs, volumes | 1 to 2 | Hiding the spreadsheet that runs the company |
| 5. Technical constraints | Hosting, GDPR, mobile, offline, browsers | 1 | Imposing a tech stack with no business reason |
| 6. Non-functional requirements | Response time, availability, backups | 1 | Demanding 99.99% for an internal tool |
| 7. Deliverables and acceptance | Mockups, source code, documentation, test sets | 1 | Not planning who tests, or when |
| 8. Budget and timeline | Indicative range, go-live date | 0.5 | Hiding the budget, which skews every offer |
| 9. Selection criteria | Weighting of price, method, references, maintenance | 0.5 | Choosing on price alone |
Stating a budget range feels risky. In practice, it is what lets vendors propose a realistic scope instead of guessing. Without a budget, quotes for the same need range from 25,000 to 95,000 EUR.
MoSCoW: what actually makes quotes converge
The MoSCoW method ranks each need as Must, Should, Could or Won't (excluded from version 1). This tells the vendor what to price firmly and what to list as options.
| Indicator (2026 order of magnitude) | Vague spec | Precise MoSCoW spec |
|---|---|---|
| Gap between lowest and highest quote | x2.5 to x3 | x1.3 to x1.6 |
| Number of vendor questions | 30 to 50 | 8 to 15 |
| Consultation duration | 6 to 10 weeks | 3 to 5 weeks |
| Change requests during the project | 15 to 35% of budget | 5 to 10% of budget |
| Recommended share of Must stories | undefined | 50 to 60% |
| Time to deliver a V1 | 5 to 9 months | 3 to 5 months |
A good user story fits on one line: As a planner, I want to reassign a job by drag and drop so I can handle an absence in under 2 minutes. Add a measurable acceptance criterion and you avoid half the arguments during acceptance testing.
Paid discovery or an in-house spec?
| Option | Cost (excl. VAT) | Duration | Relevant when |
|---|---|---|---|
| In-house writing | 5 to 10 days of manager time | 3 to 6 weeks | Stable process, available sponsor |
| Short discovery workshop | 3,000 to 4,500 EUR | 1 to 2 weeks | Clear need, priorities to arbitrate |
| Full discovery with mockups | 5,000 to 8,000 EUR | 3 to 4 weeks | Several departments, budget over 50,000 EUR |
| Owner-side consultant | 600 to 900 EUR per day | 4 to 8 weeks | Formal tender, contractual stakes |
| Discovery credited to the build | 0 to 50% refunded | variable | Same vendor delivers the build |
A full discovery produces a specification, clickable mockups and a feature-level estimate. It can be reused with any vendor: check that the contract transfers ownership to you.
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.
Julien, operations director of a 70-employee industrial maintenance SME, receives three quotes based on a 4 page brief: 28,000, 52,000 and 84,000 EUR. Impossible to compare. He funds a 6,000 EUR discovery: 42 user stories, 24 of them Must. New consultation: 46,000, 51,000 and 58,000 EUR. He picks the 51,000 EUR offer for its testing method. Final change requests reach 3,500 EUR, or 7% of budget, versus 25% on his previous project (about 12,000 EUR avoided). The discovery paid for itself twice.
FAQ
How long should a web application specification be?
Between 8 and 15 pages for a 30,000 to 80,000 EUR application. Beyond 25 pages, vendors skim and answers lose precision.
Should I state my budget in the specification?
Yes, as a range (e.g. 40,000 to 60,000 EUR). It narrows the gap between quotes and lets agencies adapt the V1 scope.
What is MoSCoW prioritisation?
It ranks needs as Must, Should, Could and Won't. Aim for 50 to 60% Must stories to keep a V1 deliverable in 3 to 5 months.
Is a paid discovery phase worth it?
From a 30,000 EUR budget, yes: 3,000 to 8,000 EUR of discovery routinely avoids 10 to 25% of change requests. Require ownership of the deliverables.
How many vendors should I consult?
Three is enough. Beyond five, analysis takes over 6 weeks and good vendors often decline overly broad consultations.
Let's scope your project. Send us your specification or notes and we will return a prioritised scope, an indicative budget aligned with our price grid and a delivery timeline. 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.
