The verdict in three sentences
Discovery workshops turn fuzzy business needs into a priceable scope: for a medium-sized application they produce 60 to 150 user stories with priorities. Discovery costs EUR 3,000 to 10,000 excl. VAT in 2026, while rushed discovery lets 20 to 30% of the budget leak into mid-project changes. The MoSCoW method is the simplest tool to decide what goes into the first release.
A typical workshop sequence
The client-side project manager plays a central role: gathering the right people, settling disagreements and signing off deliverables. Effective discovery fits into 3 to 6 half-day workshops.
| Workshop | Participants | Duration | Deliverable |
|---|---|---|---|
| 1. Goals and KPIs | Management, sponsor, project manager | 3 h | 3 to 5 measurable goals |
| 2. Current process mapping | Key users from each team | 3 to 4 h | Flow diagram, quantified pain points |
| 3. Writing user stories | Users, analyst, project manager | 2 x 3 h | 60 to 150 user stories |
| 4. MoSCoW prioritisation | Sponsor, project manager, tech team | 3 h | Approved V1 scope |
| 5. Technical constraints and integrations | IT, vendor | 2 to 3 h | List of APIs, ERP, SSO, data |
| 6. Readout and estimate | Everyone | 2 h | Quote, schedule, risks |
Between workshops, the analyst writes up and sends deliverables within 48 h for written sign-off. That signed document is what later protects the client from scope creep and unjustified extra costs.
MoSCoW prioritisation in practice
MoSCoW sorts each user story into four categories. The golden rule: Must items should not exceed 60% of estimated effort, otherwise V1 has no buffer for surprises.
| Category | Definition | Recommended share of effort | Example for a field service app |
|---|---|---|---|
| Must have | Without it the app is useless | 50 to 60% | Create and assign a job |
| Should have | Important, can be worked around for a few weeks | 20% | SMS notifications to the customer |
| Could have | Nice to have, added if budget allows | 15 to 20% | Customisable dashboard |
| Won't have (this time) | Out of V1, logged for later | 0% | Offline mobile app |
Each user story follows the format "As a [role], I want [action] so that [benefit]", with testable acceptance criteria. A story without acceptance criteria will be disputed at sign-off testing.
What discovery costs and what it saves
| Discovery format | 2026 budget (order of magnitude) | Duration | Suited to |
|---|---|---|---|
| Single 1-day workshop | EUR 1,500 to 3,000 excl. VAT | 1 week | Small internal tool, under 30 stories |
| Short discovery (3 workshops) | EUR 3,000 to 6,000 excl. VAT | 2 to 3 weeks | Medium app, 60 to 100 stories |
| Full discovery (6 workshops and mock-ups) | EUR 6,000 to 10,000 excl. VAT | 3 to 5 weeks | 100 to 150 stories, ERP integrations |
| Discovery with clickable prototype | EUR 8,000 to 15,000 excl. VAT | 4 to 6 weeks | Multi-team project, adoption critical |
| No discovery | EUR 0 upfront | None | 20 to 30% overrun is common |
For reference, Kolonell custom applications range from 2,500,000 to 4,000,000 FCFA (EUR 3,810 to 6,100) for a simple app, 4,000,000 to 7,000,000 FCFA (EUR 6,100 to 10,670) for a medium app and 7,000,000 to 15,000,000+ FCFA (EUR 10,670 to 22,870+) for a complex one. Discovery is what tells you which category your project falls into.
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.
Illustrative scenario: Julien, project manager at a maintenance company in Nantes, must launch a field service app estimated at EUR 60,000 excl. VAT. Management hesitates to pay for EUR 7,000 excl. VAT of discovery.
Without discovery, a 25% overrun would push the budget to EUR 75,000, an extra EUR 15,000. With discovery, Julien gets 110 user stories, classes 62 as Must and moves the offline module, estimated at EUR 12,000, to V2. V1 comes to EUR 48,000 excl. VAT, plus EUR 7,000 for discovery, so EUR 55,000, with a 10% contingency. The saving versus the no-discovery scenario approaches EUR 20,000.
FAQ
How many user stories for a medium business app?
Between 60 and 150 in 2026 depending on the number of roles and processes. Above 150, split the project into several separately delivered releases.
Can discovery be credited against the development quote?
Often yes: many vendors credit all or part of the EUR 3,000 to 10,000 excl. VAT if they win the build. Negotiate this before signing the discovery.
Who should attend the workshops on the client side?
The decision-making sponsor, the project manager and 2 to 4 key users who do the work every day. Without frontline users, 20 to 30% of real needs often go missing from the scope.
Does MoSCoW suit a fixed-price project?
Yes, it locks V1 content and makes trade-offs explicit. Keep Must items under 60% of effort to absorb surprises without change orders.
What if a need appears after discovery?
Write it as a new story, estimate it and swap it for a Could story of equal effort. This trade keeps the budget flat instead of growing it by 20 to 30%.
Let's scope your project. Share your processes and target users: we run the discovery, deliver prioritised user stories and a firm estimate for V1. 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.
