The verdict in three sentences
A web application quote is only as reliable as its specification: on a 60,000 EUR project, a vague need commonly turns into 30 to 60% drift. The most robust method in 2026 relies on three tools: user stories in the "As a, I want, so that" format, testable acceptance criteria, and MoSCoW prioritisation. With 25 to 40 well-written stories, three vendors can price the same project and you finally compare like with like.
The template for an estimable user story
A user story describes a need from the user's point of view, not a technical solution. It should be buildable and testable in 1 to 5 days. Beyond that, split it.
| Element | Expected content | Example |
|---|---|---|
| Identifier | Unique code per module | US-SAL-04 |
| Role | Who acts | As a field sales rep |
| Need | What they want to do | I want to create a quote from my phone |
| Benefit | Why | So that I can send it during the meeting |
| Acceptance criteria | 3 to 6 testable conditions | The quote is generated as a PDF in under 5 seconds |
| MoSCoW priority | Must, Should, Could, Won't | Must |
| Estimate | Points or days | 3 days |
| Dependencies | Related stories or systems | US-CAT-01 product catalogue |
Acceptance criteria ideally follow the Given / When / Then format: "Given an existing customer, when I select 3 products and confirm, then a numbered PDF is created and emailed". Each criterion becomes a test case.
30 typical user stories for a business application
For a classic B2B application (customers, quotes, orders), the 30 stories break down as follows:
| Module | Number of stories | Examples | Dominant priority |
|---|---|---|---|
| Authentication and roles | 4 | Login, forgotten password, admin and user roles | Must |
| Customer management | 5 | Create, search, merge duplicates, import a CSV | Must |
| Catalogue | 4 | Products, prices, variants, archiving | Must |
| Quotes and orders | 7 | Create a quote, convert to order, send reminders | Must and Should |
| Notifications | 3 | Confirmation email, reminder, threshold alert | Should |
| Reporting | 4 | Dashboard, Excel export, date filters | Should and Could |
| Integrations | 3 | Accounting, email, e-signature | Could |
A good MoSCoW split for a first release: about 60% Must, 20% Should, 20% Could. If everything is a Must, nothing is, and the vendor will price the maximum.
Why a vague spec blows up the quote
| Symptom in the spec | Consequence at the vendor | Typical drift |
|---|---|---|
| "User management" with no detail | High assumption or risk provision | +15 to 25% on the module |
| No acceptance criteria | Disputes at acceptance, rework | +10 to 20% of total |
| Integrations listed without documented API | Technical audit mid-project | +5,000 to 15,000 EUR |
| No prioritisation | Everything priced and delivered in one block | +20 to 30% on timeline |
| Implicit business rules | Discovered during demos | +10 to 25% in change orders |
| No mockups | UX back-and-forth | +5 to 10% |
Combined, these gaps explain the 30 to 60% range observed between the initial quote and the final invoice. A 3 to 5 day scoping workshop, billed 2,500 to 5,000 EUR, almost always costs less than the drift it prevents.
Mini case study
Nadia, head of operations of a 12-branch equipment rental network in Nantes, is running her first application project. Her first needs memo is two pages long: the three quotes she receives range from 48,000 to 96,000 EUR excl. VAT.
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
- She funds a 4-day scoping workshop: 3,600 EUR excl. VAT.
- Result: 34 user stories, 20 of them Must, with acceptance criteria and mockups.
- New quotes: 58,000 to 64,000 EUR excl. VAT, the spread falling from 100% to 10%.
- Project delivered at 61,500 EUR, against an estimated 40% drift on the 72,000 EUR median quote.
Estimated gain: about 39,000 EUR, more than 10 times the cost of scoping.
FAQ
How many user stories does a web application need?
A business MVP usually has 25 to 40 stories, a complete application 80 to 150. Beyond 50 Must stories for a first release, the scope is probably too broad.
Who should write the specifications?
The business owner knows the needs, the vendor knows the technical constraints. The ideal is a joint 3 to 5 day workshop, followed by a client-side review within 1 week.
Do user stories replace the requirements document?
They are its core. Add context, constraints (GDPR, hosting, accessibility), integrations and volumes, about 5 to 10 pages on top of the stories.
What if a new need appears mid-project?
Write a new story, estimate it, then drop a Could story of the same size or accept a priced change order. This mechanism keeps the budget within plus or minus 10%.
Do I need a tool?
Not to start: a spreadsheet is enough up to 50 stories. Jira, Linear or Notion become useful beyond that, for 0 to 10 EUR per user per month.
Let's scope your project. Send us your needs, even as rough notes, and we will run a scoping workshop and deliver estimated user stories with an indicative budget and schedule. 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.
