How to write a project brief a developer can quote from

Faizan Ali Arshad
Updated , 7 min read
Short answer
A good project brief explains the problem you're solving, who will use the product, the one thing it must do well, what's a must-have versus what can wait, what already exists, what it connects to, your timeline and a budget range. It doesn't need to be long. One or two clear pages gets you more accurate quotes than a 30-page feature list.
If you’ve ever sent the same idea to three developers and got three wildly different quotes, the brief was probably the reason. When details are missing, every developer fills the gaps with their own guesses. One assumes simple, one assumes everything, and you can’t compare them.
A good brief fixes that. It doesn’t need to be technical or long. It needs to be clear about the parts that change the price.
Here’s what to include, plus a template you can copy.
What to include
1. The problem, in one paragraph
Start with why, not what. Who has the problem, what it costs them today, and how they deal with it now. This one paragraph helps a good developer suggest a simpler way to get what you need.
2. Who will use it
List the types of users, such as customers, staff and admins, and what each one needs to do. Every extra type of user with its own permissions adds work, so this is one of the biggest factors in a quote.
3. The one thing it must do well
If your product could only do one thing on launch day, what would it be? This is your core workflow, and it’s where most of the effort should go.
4. Must-haves and later
Split your feature list into two columns: what has to be there for launch, and what can wait. Be honest. Most first versions launch with far less than the founder’s original list, and do better for it.
5. What already exists
Do you have designs, a logo, an existing app, a spreadsheet you’ve been running the business on, or customer data that needs moving across? Existing data is often more work than people expect, so mention it.
6. What it needs to connect to
Payments, your CRM, email, calendars, accounting software or AI models. List them, and say whether you already use them.
7. Examples you like, and ones you don’t
Links or screenshots of products that feel right are worth a page of description. Saying what you don’t like helps just as much.
8. Timeline, and what’s driving it
When do you need it, and why? “Before our trade show on 3 March” is useful. “As soon as possible” isn’t. If the date is fixed, say so, because the scope can then be adjusted to fit it.
9. Budget range
You don’t have to share an exact number. A range helps a developer suggest what fits, instead of quoting for everything and leaving you to cut it down.
10. What success looks like
In three months, how will you know it worked? More sales calls, fewer support emails, or 50 paying customers? This keeps everyone focused on the result, not just the feature list.
11. What you’re unsure about
List the questions you can’t answer yet. Good developers will help with these, and it shows them where they can add the most value.
Phrases that cause bad quotes
These sound clear, but each one can mean a day of work or a month:
| Vague | More useful |
|---|---|
| Users can log in | Users log in with email and password, or Google. No company accounts for now. |
| An admin panel | Admins can see all bookings, refund a payment and block a user. |
| It should use AI | AI drafts a reply to each support email, and a person checks it before it’s sent. |
| Like Uber, but for dog walkers | Owners book a walker for a time slot. Walkers accept, then get paid after the walk. |
| It needs to scale | We expect about 200 users in the first three months. |
| Reports and analytics | A weekly summary of bookings and revenue, emailed to the owner. |
The template
Copy this into a document and fill it in. Short answers are fine.
PROJECT BRIEF
1. The problem
Who has it, what it costs them, and how they handle it today:
2. Users
Each type of user, and what they need to do:
3. The one thing it must do well:
4. Features
Must have for launch:
Can wait:
5. What already exists
(designs, current tools, spreadsheets, data to move across)
6. Connections
(payments, CRM, email, calendar, AI and so on)
7. Examples
Products I like, and why:
Products I don't like, and why:
8. Timeline
When I need it, and what's driving that date:
9. Budget range:
10. Success in three months looks like:
11. Things I'm unsure about:
How to compare the quotes you get
When the quotes come back, don’t just compare the totals. Ask each developer to list:
- What they’ve assumed. For example: “We assumed email login only.”
- What’s not included. Hosting, content, app store fees and ongoing support are common gaps.
- How changes are handled. What happens when you want to add something halfway through?
- What you’ll own at the end. The code, the accounts and the data should be yours.
A higher quote with clear assumptions is often better value than a low one full of gaps, because the gaps come back later as extra charges.
Ready to send it?
You can send your brief through my project form, even if half of it says “not sure yet”. I’ll read it myself and reply with my honest take. If you’d rather talk it through first, book a free scoping call. For the earlier planning stage, see how to build an MVP for your startup.
Common questions
How long should a project brief be?
One or two pages is usually enough for a first quote. Clear and specific beats long. A developer can always ask questions, but a vague brief forces them to guess.
Should I share my budget with a developer?
It helps. Even a rough range lets a developer suggest what fits, rather than quoting for everything you listed and leaving you to cut it down. You're not committing to spend it all.
Do I need wireframes or designs before getting a quote?
No. Rough sketches or screenshots of apps you like are helpful, but a clear description of what users need to do matters more.
Why are my quotes so different from each other?
Usually because each developer filled in the gaps in the brief differently. Ask each one to list their assumptions and what's not included, then compare those, not just the totals.
Got a question this guide doesn’t answer? Email me.
hi@faizanali.dev