The verdict in three sentences
A well-structured requirements document is the best insurance against budget creep: it turns vague expectations into verifiable acceptance criteria. In London in 2026, a business analysis engagement to draft it costs between GBP 3,000 and GBP 10,000 depending on complexity. That spend pays for itself in the first quarter through avoided change requests — often 20 to 40 % of the initial project cost.
Why a vague spec costs money
Most web budget overruns don't come from a weak technical team but from poorly defined scope. Every unwritten feature becomes a mid-project change request negotiated at premium rates. A precise spec sets the reference price and shifts the burden of proof: it's up to the vendor to show a request falls outside scope.
| Item | No clear spec | Clear spec | Delta |
|---|---|---|---|
| Change requests (share of budget) | 25-40 % | 5-12 % | -20 to -40 % |
| Clarification meetings | 12-18 | 4-6 | -60 % |
| Acceptance testing time | 4-6 weeks | 2-3 weeks | -50 % |
| Delivery disputes | frequent | rare | -- |
| Upfront analysis cost | GBP 0 | GBP 3,000-10,000 | investment |
| Net ROI (GBP 40,000 project) | -- | +GBP 6,000 to 12,000 | positive |
The essential sections
A solid B2B requirements document isn't just a list of pages. It describes the business context, the user journeys, business rules and acceptance conditions. Here is the template structure we recommend to our London clients.
| Section | Expected content | Drafting time |
|---|---|---|
| Context & objectives | Business goals, target KPIs, competition | 1-2 days |
| Functional scope | Prioritised user stories (MoSCoW) | 3-5 days |
| Acceptance criteria | Testable conditions per story | 2-3 days |
| Technical specs | Stack, integrations, hosting, SEO | 2-3 days |
| SLA & maintenance | Uptime, fix turnaround | 1 day |
| Legal constraints | GDPR, accessibility WCAG, notices | 1-2 days |
| Timeline & milestones | Sprints, acceptance, go-live | 1 day |
| Budget & terms | Range, milestone-based payment | 1 day |
Mini case study
Julien, digital project manager at an industrial SME in London, is preparing the redesign of his B2B site (technical catalogue + reseller portal). Target budget: GBP 40,000. Without a spec, his previous project generated GBP 11,000 in change requests (28 %). This time he invests GBP 6,500 in a 3-week analysis. Result: change requests fall to GBP 3,200 (8 %), saving GBP 7,800. Net analysis ROI: +GBP 1,300, not counting 3 weeks of testing saved.
FAQ
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
How long does it take to write a requirements document?
Between 1 and 3 weeks for a B2B site, depending on the number of journeys and integrations. A simple brochure site is scoped in 5 days; a platform with a client portal needs 2 to 3 weeks of workshops and drafting.
Can I write the spec myself without an analyst?
Yes, but you risk skipping acceptance criteria and SLAs — the very sections that prevent disputes. A GBP 3,000-10,000 analysis pays off as soon as the project exceeds GBP 25,000.
Does a spec block all project evolution?
No. It sets a reference, not a straitjacket. Changes go through priced, tracked change requests, which protects both parties instead of negotiating under pressure.
What's the difference between a spec and an RFP?
The spec describes the need; the RFP is the competitive procurement process built on that spec. You write the spec first, then circulate it to bidders with an evaluation grid.
Should I include GDPR and accessibility?
Yes, essential in 2026. Accessibility (WCAG) and GDPR drive costable development items: omitting them guarantees change requests and legal risk.
Let's scope your project. Tell us your scope, indicative budget and target timeline: we frame your B2B requirements document in 1 to 3 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.
