Buyer Guides · 7 MIN

How to write a software project brief vendors can quote from

What to send a software vendor before you ask for a quote, with a fill-in project brief outline covering goals, users, scope, constraints, budget and how you will decide.

By NactorePublished 12 Nov 2026All articles

Three vendors read the same two-line email ("we need an app like X, how much?") and send back three quotes that differ wildly, because each one guessed a different project. A software project brief fixes that. It is a short document, usually two to four pages, that tells a vendor the problem, the users, what must be in the first release, the constraints, and how you will choose. Send it before you ask for a price, and the quotes you get back become comparable. Below is what to include, what to leave out, and an outline you can fill in today.

Key takeaways
  • A brief describes the problem and the outcome, not the technical solution. Vendors should propose the how.
  • The sections that change a quote most are scope (what is in and out), integrations, constraints, and a budget range.
  • A written "out of scope" list prevents more disputes than any other line in the brief.
  • Sharing a budget range is not weakness. It lets vendors propose what fits instead of guessing.
  • Send the same brief to every vendor and ask the same questions, so answers can be compared side by side.
  • Nactore is a technology and growth company that builds, ships, ranks and grows products, and we reply to a good brief with a written scope and plan, not a guess.

Why does a vague request get you a useless quote?

A quote is a price for a set of assumptions. When the request is vague, every vendor fills the gaps differently. One assumes a simple website with a login. Another assumes an admin panel, payments and a mobile app. The numbers are not wrong, they are answers to different questions.

A brief also filters vendors. A good one reads it and comes back with sharp questions about your users and edge cases. A weak one sends a price almost immediately. That difference tells you more than the price itself.

What should a software project brief include?

Nine sections cover almost every project. Keep each one short and concrete.

SectionWhat to writeWhy it changes the quote
1. BackgroundWho you are, what the business does, why this project nowContext for every later decision
2. Problem and goalThe problem in one paragraph, and what success looks likeSeparates must-haves from nice-to-haves
3. UsersEach user type and the main job they need to doEvery user type adds screens and permissions
4. Core featuresThe few things the first release must do, as user actionsThe biggest driver of effort
5. Out of scopeWhat the first release will not doStops vendors pricing things you do not want
6. Integrations and dataSystems it must connect to, data you already haveIntegrations are where estimates usually slip
7. ConstraintsDeadline reason, compliance, hosting, languages, devicesRules out options early
8. Budget rangeA range, and whether it covers launch only or ongoing workLets vendors size the proposal honestly
9. How you will decideCriteria, decision makers, timeline for choosingShows vendors what to put in their reply

How do you describe features without writing a spec?

Write features as things a person does, not as technology. "A customer can book a slot, pay, and get a confirmation email" is far more useful than "booking module with payment gateway integration". The first describes the outcome and lets the vendor see every step. The second hides the questions that matter, such as cancellations, refunds and time zones.

A simple format works well:

  • Who. The user type, for example a customer, an admin or a partner.
  • Does what. The action, in plain words.
  • So that. The reason, which helps a vendor suggest a simpler route.
  • Unless. The known exceptions, such as a sold-out slot or a failed payment.

Mark each feature as "must have for launch" or "later". If everything is a must-have, the vendor cannot tell you where the cost sits.

Pro tip

Add two or three screenshots of products you like and say exactly what you like about each one. "The checkout on this site, because it has one page" is clearer than any paragraph you could write.

Which details do founders most often leave out?

These gaps cause the most rework once a project starts:

  • Who owns the accounts. Say that the code, hosting and domain must live in your accounts. Our guide to technical setup for non-technical founders explains why.
  • Existing data. If you have customer lists, spreadsheets or an old system, say so. Moving data is real work.
  • Admin needs. Someone has to manage users, content and refunds. That back office is often half the build.
  • Compliance. Payments, health data, children's data and personal data in some countries all add requirements.
  • Life after launch. Say whether you want ongoing development, support only, or a handover to your own team.

A fill-in outline you can copy

Copy this into a document and answer each line in plain sentences. Leave out the choice of language, database or framework unless you have a real reason, because prescribing the technology narrows the proposals you get.

  1. About us. Company, market, team size on the project, and the person who will make decisions.
  2. The problem. What is broken or missing today, and what it costs you.
  3. The goal. What will be true when this works. Name one or two measures you will check.
  4. Users. List each user type and their main task.
  5. Must-have features for launch. Written as "a user can..." statements.
  6. Later features. Things you want eventually but will not pay for now.
  7. Out of scope. What this project will not include.
  8. Integrations and data. Systems to connect, data to move, accounts you already have.
  9. Constraints. The reason behind any deadline, plus required devices, languages, hosting or compliance rules.
  10. Budget range. Your range, and what it should cover.
  11. What we want back. Approach, scope with exclusions, team, price model, timeline and assumptions.
  12. How we will decide. Criteria, who decides, and when.

Item 11 matters more than it looks. When every vendor answers the same headings, you can lay the replies side by side. Then use our questions to ask a vendor before signing to test the ones you shortlist.

What should happen after you send it?

Expect questions, and welcome them. Good vendors ask about edge cases, volumes and who will use the admin side. Some will suggest a short paid discovery step before a fixed price, which is reasonable for complex work. The UK government's own service manual describes discovery as the stage for understanding users, constraints and how success will be measured, and it advises against building anything during it.

When proposals arrive, compare scope and assumptions before price. A cheaper quote that excludes the admin panel is not cheaper. If you are weighing a fixed price against paying for time, our comparison of fixed scope vs time and materials covers when each fits.

Frequently asked questions

How long should a software project brief be?

Short enough to read in one sitting. Two to four pages usually covers it. If yours is much longer, you are probably writing a specification, which a vendor can help you produce later.

Should I include a budget in the brief?

Yes, as a range. Without one, vendors guess at the size of solution you want. A range lets them propose something that fits, or tell you honestly that it does not.

Do I need an NDA before sending a brief?

Not for most briefs. Describe the problem at a level you are comfortable sharing, and sign an NDA with the shortlist before you share sensitive details.

What if I do not know which features I need?

Say so, and describe the problem and users in detail. Ask vendors to propose a first release. How they narrow it down is a useful test of their judgment.

Write the brief before the first call

A few pages written up front save long scope arguments later, and it turns a pile of mismatched quotes into a real comparison. Nactore is a technology and growth company that takes a brief through scope, build and launch, then helps the product rank and grow, all under one partner.

Have a brief, or half of one? Send it over on a free 30-minute call and we will tell you what is missing.

Want to apply this to your business?

Book a free 30-minute call. We will tell you what we would do first.