How to Write a Project Brief That Gets Accurate Quotes
What to put in a project brief so development companies quote the same project: the nine sections to include, vague lines rewritten, why quotes still differ and an outline you can copy.

Send the same two-line request to three development companies and the quotes will be far apart, because each company filled the gaps with its own assumptions. One priced a template site, one priced a custom build with a design phase, and the third guessed somewhere between. A project brief fixes that. Two to four pages, written before you contact anyone, are enough to get quotes you can compare line by line.
What a project brief has to do
A brief stops well short of a specification, which describes every field on every screen. Its job is narrower: give a stranger enough to estimate the work, spot the risks and decide whether they are the right team. The detailed requirements can be written later, often together with the vendor you choose. We cover that longer document in how to write a software requirements document.
Write for someone who knows nothing about your company. Internal names for systems, teams and processes need a sentence of explanation each.
Nine things to include
- Background and problem. Who you are, what is not working today and why you are acting now.
- Goals. What should be different once the project is live, stated so it can be checked: more inquiries from the site, orders processed without retyping, staff trained before a set date.
- Users and roles. Everyone who will log in or visit, and what each kind of person must be able to do.
- Scope. The features you must have, described as outcomes for a user, and a separate list of what is out of scope for this phase.
- Existing systems. The current site or application, hosting, payment gateway, CRM, accounting package and anything else the new work has to talk to, each by name.
- Content and data. Who writes the content, and what has to be moved: how many pages, products, users or records, from which system, in what format.
- Design. Whether you have brand guidelines, finished designs, rough wireframes or nothing yet.
- Constraints. Devices and browsers, languages, an accessibility target such as a level of WCAG, privacy or security obligations in your sector, and any hosting requirement.
- Budget, timing and decision. A budget range, the deadline and the reason for it, who decides and by when, and what you expect after launch.
Vague lines and what to write instead
Most of the spread between quotes comes from sentences that sound complete and are not. Compare:
| Vague | Estimable |
|---|---|
| Users can log in. | Customers register with email and password. Staff accounts are created by an admin. Two staff roles: agent and manager. |
| Integrate with our CRM. | Each quote request creates a lead in our CRM with name, email, phone and product. One direction only. The CRM's API documentation is attached. |
| Admin dashboard with reports. | A manager sees orders per day and revenue per product for a chosen date range and can export both as CSV. |
| Migrate the old content. | Around 400 blog posts and 60 pages move from the current WordPress site. Existing addresses are kept or redirected. |
| Must be fast and mobile friendly. | Key pages meet the Core Web Vitals thresholds on mobile. No native app in this phase. |
| Payments. | One-time card payments through our existing gateway account. No subscriptions, no stored cards. |
You do not need this precision for every feature. Apply it to the handful that carry most of the cost: accounts and permissions, payments, integrations, data migration, reporting and search.
Why quotes for the same brief still differ
A good brief narrows the range. It does not make quotes identical, and the remaining differences are useful information.
- What is included. Design, testing, project management, content entry, deployment and a period of fixes after launch are in some quotes and absent from others.
- The build approach. One vendor configures an existing platform and extends it. Another writes everything from scratch. Both can be valid, with very different costs now and later.
- Who does the work. Seniority, team size and location all move the number.
- How unknowns are handled. Some vendors pad for risk. Others quote low and rely on change requests. The better ones name the unknowns and propose a short discovery phase to remove them.
To compare fairly, ask every vendor for the same three things alongside the price: a list of assumptions and exclusions, a breakdown by feature or milestone, and what they will need from you and when. Put the answers side by side. The cheapest quote often turns out to be the one that left the most out. Our article on how software estimates work explains what sits behind the figures.
State your budget and your deadline
Buyers hide the budget because they expect quotes to rise to meet it. What happens in practice is worse: vendors guess, and you receive proposals for three different projects. A range lets a vendor design to it, tell you plainly that the scope does not fit, or offer a smaller first phase that does.
If you truly have no figure, ask for two options: the smallest version that solves the problem and the fuller one. For the deadline, give the reason. "Before the trade show in spring" tells a vendor what can slip and what cannot. A date with no reason invites either padding or a promise nobody intends to keep.
A brief outline you can copy
PROJECT BRIEF: [project name]
Contact: [name, role, email] Date: [date]
1. About us and the problem we want solved
2. Goals and how we will measure them
3. Users and roles
4. Must-have features (as user outcomes)
5. Out of scope for this phase
6. Existing systems and integrations (named)
7. Content and data to migrate (volumes, sources)
8. Design: what exists, what is needed
9. Constraints: devices, languages, accessibility,
performance, security, hosting
10. Budget range
11. Deadline and the reason for it
12. Decision process and date
13. After launch: support and changes we expect
14. What we want in your reply: price breakdown,
assumptions, exclusions, team, timeline
Attach what you have: a sitemap or list of screens, a sample export of the data, access to a staging copy of the current system, and two or three reference sites with a note on what you like about each.
Mistakes that raise the price or lose the good vendors
Prescribing the solution and hiding the problem. "We need a React front end with microservices" removes the vendor's chance to suggest something simpler. Say what you need to achieve and list any technology you are tied to.
A feature list with no priorities. Sixty items of equal weight get priced as sixty must-haves. Mark each one as needed for launch, wanted soon or nice to have.
"Like this well-known app, but for our industry." That app took years and a large team. Name the two or three behaviors you want from it.
Stakeholders who appear late. If legal, IT or a regional office has a say, collect their requirements before the brief goes out.
Sending it to fifteen companies. You will get templated replies. Shortlist three to five that have built something similar and offer each a call.
When to write the brief yourself and when to ask for help
For a website, a store, a defined integration or a first product version, you can write the brief yourself with the outline above. It takes an afternoon and improves every conversation that follows. Most vendors, ourselves included, will give a free consultation and quote against it, and you can send us yours as it is.
Get help with the brief itself when the project replaces a system nobody fully understands, when several departments want conflicting things, or when the first decision is a technical one you are not placed to make. A short paid discovery phase, with any capable vendor, produces a scope you own and can put out to tender.
If what you have is a moving roadmap more than a single build, the brief still earns its keep: it becomes the starting backlog for a dedicated development team. For one build with a firm scope, it is the document a custom software development quote is based on.
Frequently asked questions
How long should a project brief be?
Two to four pages for most projects. Shorter than that and vendors must guess. Much longer and you are writing a specification, which is better done after you have chosen a vendor and can work through the details together.
Do I need wireframes before asking for a quote?
No, though they help. A list of screens with a sentence on what each one does is enough for an estimate. If the interface is the heart of the product, expect a design phase as the first milestone, priced separately.
What is the difference between a project brief and an RFP?
A brief describes the project. A request for proposal wraps a brief in a formal buying process with submission rules, scoring criteria and deadlines. Small and mid-sized projects rarely need the formality, and a brief plus a clear list of what you want in the reply does the same job.
Should vendors sign an NDA before they see the brief?
If the brief contains sensitive figures, customer data or an unreleased idea, ask for one. Established companies sign without fuss, and we sign NDAs on request. For a typical website or store, an NDA at this stage mostly slows things down.
Add worldwincoder.com as a preferred source on Google, or open this article in your AI assistant to use it as a source.
