How to write a software specification a vendor can actually quote
Why quotes for the same project differ wildly, the seven sections a quotable specification needs, and how much detail is enough for fixed price vs T&M.
A quotable specification answers seven questions: what business outcome the software serves, who uses it, what it must do (as a prioritized feature list), what it must connect to, what non-functional constraints apply (volumes, performance, security), what already exists, and what is explicitly out of scope. One to five pages covering those seven beats fifty pages of prose - and the difference shows up directly in the price, because vendors bill you for ambiguity whether you notice or not. Here is the structure, section by section, with the level of detail each engagement model needs.
Why do quotes for the same project differ by 3×?
Because they are not quotes for the same project. Send a vague brief to five vendors and each fills the gaps differently: one assumes senior engineers and real QA, another assumes juniors and a smoke test; one includes the ERP integration you mentioned in passing, another lists it as “phase 2”. The totals differ wildly, the cheapest wins, and the gaps surface later as change requests - the expensive way to write a specification.
The fix is not writing more; it is writing the right things. Ambiguity you resolve on paper costs an hour. The same ambiguity resolved in change requests costs a meeting, a re-estimate and a delay - every time.
The seven sections of a quotable specification
1. Business goal - one paragraph. What outcome justifies the spend (“reduce quote-to-policy time from days to minutes”). This is the section that lets a vendor challenge your solution intelligently - the most valuable thing a good one does.
2. Users and main flows. Who uses the system and for what, as short scenarios: “A field agent photographs a delivery note; the system extracts the order number and matches it against the ERP.” A dozen sentences like that beat any feature matrix.
3. Functional scope - a prioritized list. Features as bullets, each with one or two lines, marked must / should / later. The priorities are load-bearing: they let a vendor quote a smaller first release instead of pricing your entire wishlist as if it all mattered equally.
4. Integrations. Every system the software must talk to, with what data flows in which direction, and what interface exists today (API, files, database, nothing). This is the section buyers skip and the single biggest source of quote divergence - an integration with a documented API and one with a legacy system that has no interface at all differ by an order of magnitude.
5. Non-functional requirements. Only the ones that are real: expected users and data volumes, performance expectations where they matter, security and compliance constraints (GDPR, PDPA, industry rules), availability needs. Numbers, not adjectives - “3,000 concurrent users at month-end” prices; “must be fast and scalable” doesn’t.
6. What already exists. Current systems, code that must be kept or replaced, data to migrate, design assets, previous attempts and why they stopped. Vendors price the unknown defensively; showing the terrain removes the defense premium.
7. Exclusions. What you are not buying: “no mobile app in this phase”, “reporting stays in the current BI tool”. Two lines here prevent the classic end-of-project dispute.
How much detail does each engagement model need?
| Engagement | Specification level | Why |
|---|---|---|
| Fixed price | Full: flows, edge cases, acceptance criteria per feature | The vendor prices delivery risk; gaps become risk premium or disputes |
| Time & materials | Sections 1–7 at outline level, detail per sprint | Direction set up front, detail emerges as you steer |
| Dedicated team | Sections 1, 2, 6 plus a living backlog | You are buying capacity; the spec is continuous |
| Discovery phase | Sections 1 and 2 honestly attempted | The phase’s job is producing the rest |
The corollary buyers dislike but vendors respect: if you cannot write the fixed-price level of detail, you cannot buy fixed price yet. Buy a one-to-three-week paid discovery phase instead - the deliverable (spec, architecture outline, real estimate) is yours to take to any vendor, and it is the cheapest de-risking a large project can buy.
How to use the specification in vendor selection
Send the same document to every vendor and require three things back: a quote, the assumptions behind it in writing, and the questions they asked. Then read the questions as carefully as the prices. A vendor who interrogates section 4 and challenges section 1 is showing you what working together will feel like; a vendor who returns a confident total against a vague brief has priced something - you’ll find out what after signing. It is the same signal-reading that applies in a pilot, one step earlier and one step cheaper.
In short
- Quotes diverge because specs leak assumptions - vendors price the gaps differently, and you pay either way.
- Seven sections make a spec quotable: goal, users/flows, prioritized features, integrations, non-functionals, what exists, exclusions. One to five pages.
- Integrations and non-functionals are where the money hides - give them numbers, not adjectives.
- Match detail to model: full spec for fixed price, outline for T&M, living backlog for a dedicated team - and buy a paid discovery phase when you can’t get there alone.
- Compare vendors on written assumptions and the quality of their questions, not totals.
AD System Asia quotes with assumptions stated in writing, and runs paid discovery phases whose deliverables are yours to keep - whoever you then choose. Send us what you have today, even if it’s two paragraphs, and we will respond with the questions that turn it into a specification.
Frequently asked questions
What should a software specification include for an accurate quote?
Seven things: the business goal, the users and their main flows, functional scope as a feature list with priorities, the systems to integrate with, non-functional requirements (volumes, performance, security, compliance), what already exists, and explicit exclusions. One to five pages is usually enough to start.
How detailed does a specification need to be for a fixed-price quote?
Detailed enough that two reasonable people would build roughly the same thing: every feature described with its main flow and edge cases, integrations specified, acceptance criteria stated. If you cannot reach that level yet, buy a paid analysis phase first or contract time & materials instead.
Why do vendor quotes for the same project differ so much?
Because each vendor fills your specification's gaps with different assumptions - about seniority, testing depth, project management, integrations and edge cases. Tighter specifications converge quotes; for the rest, ask every vendor to state their assumptions in writing and compare those, not just the totals.
What is a discovery or analysis phase and is it worth paying for?
A short paid engagement - typically one to three weeks - where the vendor analyzes requirements with you and produces the specification, an architecture outline and a real estimate. If the project is worth months of development, paying for its definition is the cheapest risk reduction available; the deliverable is yours to take to any vendor.
Should I specify the technology stack in my specification?
State constraints that are real: systems to integrate with, platforms your team can maintain, compliance requirements. Beyond that, describe the problem and let vendors propose - a stack mandate copied from a blog post narrows your options without adding safety.