The verdict in three sentences
A requirements document structured in 12 sections is the only fair way to compare three vendors for a custom business application. SMEs that issue a vague brief receive quotes ranging from one to three times each other, while a precise framework brings the spread down to under 30%. Plan 2 to 4 weeks of writing for a EUR 20,000 to 80,000 project, a small investment compared with the risk of a EUR 15,000 change order halfway through.
The 12 sections of the template
The template below covers what a serious vendor needs to know to price the work. Each section answers a question they would ask you in a scoping meeting anyway.
| No. | Section | Expected content | Typical length |
|---|---|---|---|
| 1-2 | Context and goals | Business, current problem, 3 quantified success indicators | 1 to 2 pages |
| 3-4 | Users and roles | Profiles, number of users, permissions per role | 1 page + matrix |
| 5 | Prioritized user stories | 30 to 80 stories ranked with MoSCoW | 4 to 8 pages |
| 6 | Data and migration | Volumes, sources (Excel, ERP), history to import | 1 page |
| 7 | Integrations | ERP, accounting, email, SSO, third-party APIs | 1 page |
| 8 | GDPR and hosting requirements | Personal data, EU location, retention periods | 1 page |
| 9 | Non-functional requirements | Performance, availability, browsers, mobile | 1 page |
| 10 | Acceptance criteria | Test scenarios, threshold for blocking defects | 1 to 2 pages |
| 11 | Schedule and budget | Budget range, target date, milestones | 0.5 page |
| 12 | Tender rules | Response format, scoring grid, calendar | 0.5 page |
Overall, a good SME requirements document runs 15 to 25 pages. Longer, and vendors skim it; shorter, and they extrapolate and inflate their risk margin.
Prioritize with MoSCoW to control the budget
The MoSCoW method ranks each user story as Must, Should, Could or Won't (out of scope this time). It lets vendors price a core scope plus options, which makes offers comparable line by line.
| Priority | Share of stories | Share of budget (2026 order of magnitude) | Example for a field service app |
|---|---|---|---|
| Must | 40 to 50% | 55 to 65% | Technician scheduling, mobile job sheet |
| Should | 25 to 30% | 20 to 25% | Customer signature on tablet, accounting export |
| Could | 15 to 20% | 10 to 15% | Executive dashboard, SMS notifications |
| Won't | 5 to 10% | 0% | Customer portal, full offline app |
Write each story as « As a [role], I want [action] so that [benefit] », with a testable acceptance criterion. Example: « As a technician, I want to close a job from my phone so that nobody re-types it at the office; criterion: closing in fewer than 3 taps, synced in under 10 seconds ».
GDPR, hosting and acceptance: the forgotten sections
Sections 8 and 10 are the ones SMEs rush, and they are the ones that trigger change orders. State whether the app handles personal data of employees or customers, require hosting within the European Union (OVHcloud, Scaleway, Outscale or an EU region of a US cloud), a retention period per data type and an up-to-date record of processing. If health data is involved, the host must be HDS-certified.
| Requirement | Wording to reuse | Estimated budget impact |
|---|---|---|
| Data location | EU-only hosting, backups included | 0 to 5% |
| Authentication | MFA for administrator roles | EUR 1,500 to 3,000 |
| Logging | Access and change traceability over 12 months | EUR 2,000 to 5,000 |
| Right to erasure | Deletion or anonymization on request within 30 days | EUR 1,000 to 2,500 |
| Acceptance testing | 2 cycles, zero blocking defects, fewer than 5 major ones | Included if required from the start |
| Warranty | 3 months of defect fixes after go-live | Included, to negotiate |
For acceptance, write 15 to 30 test scenarios derived from the Must stories. A vendor who knows your scenarios at tender stage prices accurately.
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.
Claire, CFO of a 60-employee industrial maintenance SME in Lyon, consults three vendors for a field service application. First attempt with a 4-page memo: quotes of EUR 28,000, 52,000 and 91,000, impossible to compare. She invests 3 weeks (about 6 working days, or EUR 3,600 of internal time) in a 22-page requirements document with 48 MoSCoW stories.
Second round: EUR 46,000, 54,000 and 59,000, a 28% spread. She picks the EUR 54,000 offer, with a EUR 34,000 Must core. With no major change order during the project, versus EUR 12,000 to 18,000 of typical change orders on a poorly scoped project, the return on the EUR 3,600 invested is roughly 3 to 5 times.
FAQ
Should you state your budget in the requirements document?
Yes, a range is enough, for example EUR 40,000 to 60,000. Without it, you receive offers built on incomparable scopes, and 1 vendor in 3 proposes an oversized solution.
How many vendors should you consult?
Three is the right number for an SME. Beyond 4, analysis takes more than 5 days and the best vendors decline overly open tenders.
Can a vendor write the requirements document for you?
Yes, through a scoping engagement billed EUR 3,000 to 8,000. Make sure the deliverable belongs to you and can be used to consult other vendors.
How much contingency should you reserve?
Keep 10 to 15% in reserve. With MoSCoW stories, you can also move Could items to Won't to absorb an overrun without extra budget.
How long does the tender itself take?
Allow 3 weeks for responses, 1 week for presentations and 1 week for negotiation. Development therefore starts 6 to 9 weeks after you begin writing.
Let's scope your project. Send us your requirements document or needs memo: we price the Must core and the options, for a business application between EUR 20,000 and 80,000 delivered in 3 to 6 months. 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.
