Skip to content
Software DevelopmentCompany USA

Planning

How to Write a Software Requirements Document Your Vendor Can Actually Estimate

Vague requirements produce vague estimates. Here is how to describe your project so that vendor quotes are comparable, realistic and grounded in the same assumptions.

By the Software Development Company USA engineering team · · 9 min read

Why most requirements documents fail

Most requirements documents fall into one of two traps. Some are a single paragraph — “an app like X, but for our industry” — which forces every vendor to invent assumptions, so their quotes differ wildly. Others run to eighty pages of feature specifications written before anyone has spoken to users, locking in decisions that should have been tested first.

A useful requirements document sits between those extremes. It explains the problem and the constraints precisely, describes how people will use the system, and leaves room for the delivery team to propose solutions. Vendors can then estimate the same thing, and you can compare their thinking instead of guessing what each one assumed.

The structure that works

Eight sections, usually 6–15 pages in total for a mid-sized business application.

  1. 01

    Background and problem

    What happens today, why it is a problem, and what it costs in time, errors or lost revenue.

  2. 02

    Goals and success measures

    The two or three outcomes that matter, phrased so you can tell later whether they were achieved.

  3. 03

    Users and roles

    Each type of user, roughly how many there are, and what they need to accomplish.

  4. 04

    Key workflows

    Step-by-step descriptions of the most important journeys, written as user stories or simple narratives.

  5. 05

    Data and integrations

    What data the system owns, what it reads from or sends to other systems, and how those systems can be accessed.

  6. 06

    Non-functional requirements

    Security, compliance, performance, availability, accessibility and browser or device support.

  7. 07

    Constraints

    Budget range, deadlines, required technologies or hosting, and internal resources available.

  8. 08

    Out of scope

    What this release will not do. This section prevents more disputes than any other.

Write workflows, not feature lists

“User management” is a feature. It tells a vendor almost nothing. “An office manager invites a new technician by email, assigns them to one region, and the technician can see only jobs in that region” is a workflow. It reveals roles, permissions, notifications and data scoping — the things that actually drive effort.

A good test: could a designer sketch the screens from your description? If not, add the steps a person takes, what they see, and what decision they make at each point.

Use acceptance criteria for the important parts

For your most critical workflows, add acceptance criteria — short statements that must be true for the feature to be considered done. For example: “Given a job is marked complete, the customer receives an emailed invoice within five minutes.” Criteria like this make estimates sharper and give everyone a shared definition of done.

Integration details vendors need

Integrations are the most common source of estimate surprises. For each connected system, include:

  • The system name and version, and whether it is cloud-hosted or on-premises
  • Whether it has a documented API, and a link to the documentation if available
  • Which data moves in which direction, and how often (real time, hourly, nightly)
  • Approximate data volumes
  • Who owns the system and can grant test access
  • Known limitations, such as rate limits or missing fields

Prioritize with MoSCoW

Label every requirement so vendors can price an initial release and show what each additional tier costs.

PriorityMeaningExample
Must haveRelease is not viable without itTechnicians can view and update assigned jobs on mobile
Should haveImportant, but a workaround existsCustomers receive SMS appointment reminders
Could haveValuable if time and budget allowRoute optimization across multiple jobs
Won’t have (this time)Explicitly deferredInventory management for parts

What to leave out

Don’t prescribe screen layouts in detail unless you have already tested them with users — that is what the design phase is for. Avoid choosing technologies unless there is a real constraint, such as an existing Azure environment or an in-house team that knows .NET. And resist adding speculative features “in case we need them later”; they inflate every estimate and rarely survive contact with real users.

FAQ

Questions about this topic

How long should a software requirements document be?

For a typical business application, 6–15 pages is usually enough if it covers goals, users, workflows, integrations, non-functional requirements, constraints and what is out of scope.

Do I need technical knowledge to write requirements?

No. Describe the business problem, users and workflows in plain language. Technical decisions are the delivery team’s job, though you should note any real constraints such as required hosting or existing systems.

Should requirements be fixed before development starts?

The goals, constraints and core workflows should be clear. Detailed requirements usually evolve during design and development, which is why most teams use an iterative process with a prioritized backlog.

Have a software project in mind?

Share a few details and we’ll respond within one business day with questions, a suggested approach and an estimate range.