The verdict in three sentences
A good requirements document for a business application runs 20 to 40 pages, not 120. It describes 15 to 25 prioritised user stories, the data handled, integrations and measurable acceptance criteria. A vague document inflates quotes by 30 to 80% because every vendor prices in its own risk.
The 8-section template
The project manager of a 400-employee company writing a first requirements document for an internal application (purchase requests, maintenance tracking, scheduling) can follow this outline. Volumes match a project of EUR 40,000 to 120,000 (about USD 43,000 to 130,000).
| Section | Expected content | Recommended length |
|---|---|---|
| Context and objectives | Current problem, target metrics (lead time, errors, hours) | 2 to 3 pages |
| Users and roles | Profiles, headcount, rights, frequency of use | 1 to 2 pages |
| Prioritised user stories | 15 to 25 stories ranked with MoSCoW | 6 to 12 pages |
| Data and business rules | Business objects, fields, calculations, statuses | 3 to 6 pages |
| Integrations | ERP, HRIS, directory, APIs, sync frequency | 2 to 4 pages |
| Non-functional requirements | Performance, security, GDPR, accessibility, hosting | 2 to 4 pages |
| Acceptance criteria | Quantified test scenarios per user story | 3 to 5 pages |
| Project constraints | Indicative budget, target date, governance, deliverables | 1 to 2 pages |
State an indicative budget. Vendors will not overcharge because of it: they will propose a fitting scope instead of pricing blind.
The most expensive mistakes
| Common mistake | Consequence | Observed overrun (2026 order of magnitude) |
|---|---|---|
| Describing screens instead of needs | Frozen solution, poor technical choices | 10 to 20% |
| No prioritisation | Everything is "essential", maximum quote | 30 to 50% |
| Integrations named without detail | Discovered mid-project | 15 to 30% |
| Verbal business rules | Successive change orders | 20 to 40% |
| No acceptance criteria | Disputes over "done" | 2 to 6 weeks of delay |
| Copying another project's document | Useless requirements | 10 to 25% |
Combined, these mistakes explain the 30 to 80% quote gaps seen between two tenders for the same need.
Writing a useful user story and acceptance criterion
Format: "As a purchasing manager, I want to approve a request above EUR 5,000 in one tap from my phone, so that approval lead time drops." Matching acceptance criterion: "Approval takes under 3 seconds, the request moves to Approved status, the requester is notified within one minute." A quantified criterion settles debates during acceptance testing.
If the internal team lacks time, a 2 to 5 day scoping workshop with the vendor costs EUR 2,000 to 6,000 and produces this document, with mockups and an estimate.
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.
Sophie, project manager at a 400-employee manufacturer, consults three vendors with an 8-page document. Quotes range from EUR 62,000 to 110,000. She funds a EUR 4,500 scoping workshop: the document grows to 28 pages and 21 user stories, 8 of them moved to phase 2. New quotes: EUR 54,000 to 66,000. Taking the middle of the range, savings reach about EUR 26,000 against the initial median quote of EUR 86,000, nearly 6 times the workshop cost.
FAQ
How many pages should a requirements document have?
Between 20 and 40 pages for an application of EUR 40,000 to 120,000. Beyond 60 pages, the document is rarely read in full and slows the tender.
Should we share our budget with vendors?
Yes, a range is enough. It brings comparable proposals and avoids quote gaps of 30 to 80%.
How many user stories should we plan?
Target 15 to 25 priority stories for V1, ranked with MoSCoW. The rest go to a phase 2 backlog.
Who should write the document?
The internal project manager, with 3 to 5 key users interviewed for 1 hour each. An external scoping workshop at EUR 2,000 to 6,000 speeds up the work.
How long does it take to write?
Plan 3 to 6 weeks internally, or 1 to 2 weeks with a facilitated scoping workshop.
Let's scope your project. Send us your draft requirements, even incomplete, and we will review it, flag risk areas and propose a scoping workshop between EUR 2,000 and 6,000. 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.
