Websites11 min read

Web App RFP Specification 2026: Scoping a Custom Build the Right Way

Mohamed Bah·Fondateur, Kolonell
September 7, 2026
Share:
Web App RFP Specification 2026: Scoping a Custom Build the Right Way

Web App RFP Specification 2026: Scoping a Custom Build the Right Way

Websites

The verdict in three sentences

A clear RFP specification is the most profitable tool in a custom-app project: it turns incomparable quotes (25,000 to 90,000 EUR) into aligned offers. The essential sections are user stories, roles and permissions, integrations, volume, GDPR and acceptance criteria. Prioritize with MoSCoW and score vendors on a weighted grid, or you will choose on gut feel.

The essential sections of a 2026 RFP

An RFP that skips one of these sections produces quotes that later diverge into change orders. Each section removes an uncertainty zone that the vendor would otherwise over-price out of caution.

SectionWhat it framesImpact if missing
User storiesThe what, from the user's viewVague scope, overpricing
Roles and permissionsWho sees/does whatSecurity underestimated
Integrations (ERP/CRM)Data flows, APIsThe most underestimated item
VolumeUsers, data, peaksUnfit architecture
GDPR and securityPersonal data, hostingLegal risk
Acceptance criteriaDefinition of "done"Endless UAT

Integrations are the most often forgotten and most costly item: connecting an existing ERP can represent 20 to 35 percent of the total budget.

MoSCoW and budget by complexity

Prioritize each feature as Must / Should / Could / Won't. This protects the budget: deliver the Musts, negotiate the Shoulds, defer the Coulds. Here are the 2026 ranges by complexity.

ComplexityDescriptionBudgetTimeline
SimpleCRUD, 2-3 roles, 1 integration25,000-40,000 EUR3-4 months
MediumWorkflows, 4-6 roles, 2-3 integrations40,000-65,000 EUR4-6 months
HighReal time, multi-tenant, ERP + billing65,000-90,000 EUR6-9 months
Very highAI, large volumes, strong compliance90,000 EUR+9 months+

A well-specified "medium" app often costs less than a poorly-scoped "simple" one that drifts: the RFP is an investment, not a formality.

Vendor scoring weights

Need a professional website?

Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.

Prefer a call back?

Leave your WhatsApp number and a Kolonell expert will get back to you within 1 business day. Free, no strings attached.

Score each quote on a weighted grid rather than on price alone. A balanced 2026 example: needs understanding 25 %, technical competence 20 %, comparable references 15 %, price 20 %, timeline 10 %, maintenance/support 10 %.

Mini case study

Elodie, operations director of an 80-person logistics SME, had to consult 4 vendors for a route-tracking app. Without an RFP, her first verbal quotes ranged from 30,000 to 85,000 EUR, incomparable. She wrote a 14-page RFP (user stories, 5 roles, TMS integration, volume of 300 routes/day, GDPR, 40 acceptance criteria). The new quotes tightened between 48,000 and 62,000 EUR, a 14,000 spread instead of 55,000. Thanks to the weighted grid, she chose a 54,000 EUR vendor scoring better on references, and the project held its 5-month timeline with no major change order.

FAQ

Who should write the RFP? Ideally the business owner with help from a neutral technical scoper. Letting the responding vendor write the RFP creates a conflict of interest: they specify what they can do.

How many pages for a good RFP? Between 10 and 25 pages for an SME business app. Too short leaves too many gray areas; too long freezes details that should stay agile.

Should I price the project myself in the RFP? State a target budget or a range: it avoids off-topic offers and lets vendors calibrate scope. Hiding the budget lengthens the back-and-forth.

What are acceptance criteria for? They define "done" testably (e.g. "a driver sees their route in under 2 seconds"). Without them, UAT drags on and each party has its own definition of finished.

Does GDPR change the budget? It adds requirements (consent, EU hosting, logging, right to erasure) worth 5 to 12 percent of the budget depending on data sensitivity. Better to scope it than discover it in UAT.

Let's scope your project. Send us your main user stories, your integrations and your volume: we help you structure a priced RFP and a scoring grid. Detailed quote within 48 h. WhatsApp +221 77 596 93 33.

Tags:#app RFP specification#web app RFP#software specification#user stories#MoSCoW#software tender#project scoping#business app budget
Share:

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.