The verdict in three sentences
A poorly scoped spec document (SRS) is the number-one cause of budget overruns on a custom web platform: vendors price the uncertainty, and the quote climbs 30 to 50%. By locking in your prioritised user stories (MoSCoW), your non-functional requirements and your acceptance criteria before any consultation, you get comparable quotes and a realistic budget of EUR 60,000 to 120,000. This guide gives the exact structure to hand vendors.
The spec structure that prevents over-quoting
A good spec clearly separates the functional (what the platform does) from the non-functional (how it must behave). MoSCoW prioritisation (Must / Should / Could / Won't) is the most effective tool to contain the budget: it lets you negotiate scope without renegotiating price.
| Spec section | Expected content | Impact on the quote |
|---|---|---|
| Context & goals | Business problem, target KPIs | Frames the ROI |
| Functional scope | 30-60 MoSCoW user stories | Cuts risk padding by ~30% |
| User journeys | 3-5 personas, wireflows | Avoids UX rework |
| Non-functional reqs | Perf, security, uptime | Directly quotable |
| Integrations | Third-party APIs, SSO, ERP | EUR 4,000-18,000/connector |
| Acceptance criteria | Acceptance tests | Secures final payment |
| Timeline & lots | Sprints, milestones | Smooths cash flow |
A well-written user story follows the format: *As a [role], I want [action] so that [benefit]*, completed by testable acceptance criteria. This level of detail turns a "wide range" estimate into a fixed-price quote.
Non-functional requirements and 2026 framing budget
Non-functional requirements are often forgotten yet account for 20 to 35% of the effort. Here are 2026 ballpark figures for a B2B custom platform in Western Europe.
| Item | Typical 2026 requirement | Indicative budget |
|---|---|---|
| Discovery & detailed spec | Workshops + specs | EUR 5,000-12,000 |
| MVP (Must have) | 15-25 user stories | EUR 35,000-60,000 |
| Should have (v1) | 15-20 user stories | EUR 20,000-40,000 |
| 99.5% uptime | Monitoring + redundancy | EUR 3,000-8,000 |
| Security & GDPR | RBAC, audit logs, registry | EUR 4,000-9,000 |
| Integrations (per API) | REST + webhooks | EUR 4,000-18,000 |
| Acceptance & go-live | Tests, training | EUR 4,000-9,000 |
A realistic timeline runs over 3 to 4 sprints of 3 weeks for an MVP, i.e. 3 to 5 months including acceptance. Requiring a staging environment separate from production is non-negotiable: that is where you validate acceptance criteria before paying the balance.
Mini case study
Thomas, COO of a logistics SME, wants a route-tracking platform. Without a spec, he receives three quotes of EUR 70,000, 95,000 and 140,000: incomparable. After drafting 42 MoSCoW user stories (22 Must, 12 Should, 8 Could) and setting uptime at 99.5%, he gets three quotes in a band of EUR 78,000 to 92,000. By deferring the 8 "Could" to phase 2, he starts at EUR 64,000 and spreads the rest over the next fiscal year. Scoping saved him the EUR 45,000 gap between the initial quotes.
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
FAQ
How long does a good spec take to write?
Allow 2 to 4 weeks with 3 to 5 business workshops. A guided discovery costs EUR 5,000 to 12,000 but saves 20 to 40% on the build by removing uncertainty.
Should everything be specified to the pixel?
No. Specify business rules and acceptance criteria; leave detailed UX to mockups. Over-specifying freezes choices that will change; under-specifying inflates quotes.
MoSCoW or a simple priority list?
MoSCoW forces decisions: a documented "Won't have (this time)" is an immediate saving. A list without a "Won't" category leaves everything open and vendors price for the worst case.
How do I guarantee 99.5% uptime in the spec?
Write it as a measurable requirement (monthly uptime, maintenance window, penalties) and require monitoring. 99.5% allows roughly 3.6 hours of downtime per month: fine for an internal tool, insufficient for critical real-time systems.
Is the EUR 60,000-120,000 budget firm?
It is a 2026 ballpark for a medium-complexity custom platform. The firm quote depends on the number of Must user stories, integrations and security requirements.
Let's scope your project. Send us your scope (number of users, integrations, target uptime) and we'll frame an actionable spec with an indicative budget. 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.
