The verdict in three sentences
A 9-section requirements specification lets a New York SMB get comparable quotes and shrink the gap between bids from 1:3 to under 30 %. Professional discovery costs 3,000 to 8,000 USD for 2 to 4 days, and it typically prevents 15 to 25 % of overruns on a 40,000 to 150,000 USD project. The useful document is not long: 12 to 20 pages, focused on business rules and acceptance criteria.
The 9 sections of the template, annotated
Take a 45-person company in the New York area (precision machining subcontractor) that runs quotes, shop scheduling, inventory, non-conformances and timesheets in 5 Excel workbooks. Here is what each section must contain and the trap to avoid.
| Section | Expected content | Common mistake |
|---|---|---|
| 1. Context and goals | Current problem, 3 measurable goals (e.g. quote in 2 hours instead of 2 days) | Vague goals like 'be more efficient' |
| 2. Users and roles | Profiles, headcount, permissions (12 users, 4 roles) | Forgetting occasional users like accounting |
| 3. User journeys | 5 to 10 key journeys described step by step | Describing screens instead of tasks |
| 4. Business rules | Calculations, statuses, approvals, exceptions | Leaving them 'to be defined': that is where overruns start |
| 5. Data | Entities, volumes, history to migrate (e.g. 8,000 rows) | Underestimating Excel data migration |
| 6. Integrations | ERP, accounting, email, e-signature | Not listing available formats and APIs |
| 7. Security | Authentication, audit logging, privacy | Pasting a generic clause unrelated to actual data |
| 8. Hosting | US cloud region, backups, target uptime | Not setting a service level |
| 9. Acceptance criteria | Test scenarios, performance thresholds, sign-off conditions | Missing, which makes any handover disputable |
Examples of well-written user stories
A user story follows the form 'As a [role], I want [action] so that [benefit]', plus acceptance criteria. Three examples for the New York company:
- As a sales engineer, I want to generate a quote from an existing bill of materials so that I can respond in under 2 hours. Criterion: the quote pulls material cost, machine time and a default 22 % margin.
- As a shop foreman, I want to see load per machine over 4 weeks so that I can decline or reschedule an order. Criterion: alert above 90 % load.
- As a quality manager, I want to log a non-conformance from a tablet so that it is recorded in under 3 minutes. Criterion: photo, lot number and corrective action required.
A serious specification includes 25 to 60 stories for this type of application, ranked as must-have, should-have and nice-to-have.
How much the application costs by complexity
The ranges below are market prices observed in the New York area in 2026 (agencies and boutique dev shops), excluding licenses and hosting.
| Complexity level | Example scope | Market budget | Timeline |
|---|---|---|---|
| Simple | 1 module, 2 roles, no integration | 40,000 to 60,000 USD | 6 to 8 weeks |
| Intermediate | 3 modules, 4 roles, accounting export | 60,000 to 90,000 USD | 10 to 14 weeks |
| Advanced | 5 modules, Excel migration, ERP connection | 90,000 to 120,000 USD | 4 to 5 months |
| Complex | Multi-site, offline mobile, third-party APIs | 120,000 to 150,000 USD | 5 to 7 months |
| Discovery only | Workshops, writing, estimate | 3,000 to 8,000 USD | 2 to 4 days |
| Annual maintenance | Fixes and minor changes | 15 to 20 % of initial budget per year | Ongoing |
For comparison, the Kolonell grid for custom applications, built remotely, is 2,500,000 to 4,000,000 FCFA (3,810 to 6,100 EUR) for a simple app, 4,000,000 to 7,000,000 FCFA (6,100 to 10,670 EUR) for a medium app and 7,000,000 to 15,000,000 FCFA and up (10,670 to 22,870 EUR and up) for a complex app.
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.
Rachel, head of operations at a machining subcontractor near New York, spends with her team about 14 hours a week re-entering data across the 5 Excel files. At 70 USD per loaded hour, that is 980 USD a week, or about 45,000 USD a year over 46 weeks. She invests 6,000 USD in 3 days of discovery, then picks a 90,000 USD bid. If the application removes 80 % of re-entry, savings reach about 36,000 USD a year and the project pays back in about 2.7 years. Without discovery, the 3 quotes she received ranged from 45,000 to 160,000 USD and could not be compared. This example is illustrative, not a Kolonell client.
FAQ
How long should a business application specification be?
12 to 20 pages is enough for an SMB, plus an appendix of 25 to 60 user stories. Beyond 40 pages, vendors rarely read the document in full.
Should discovery be paid or requested for free?
Serious discovery over 2 to 4 days is worth 3,000 to 8,000 USD. Free discovery is usually capped at 2 hours and produces an estimate that is off by plus or minus 40 %.
How do you avoid change orders?
Write the business rules and acceptance criteria before signing. Also keep a 10 to 15 % budget reserve for new requests, approved one by one.
Should the specification impose a technology?
Only if your in-house team will maintain the application afterwards. Otherwise, ask for a justification of the stack and full source code handover at delivery.
How many bids should you compare?
Three bids on the same specification are enough. Compare days per module and the day rate, often 1,000 to 1,600 USD in New York.
Let's scope your project. Send us your current Excel files and user list, and we will estimate discovery and the application with an indicative budget and a phased plan. 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.
