· 6 min read
How to write a software project brief: a template
How to write a software project brief an agency can quote from: what to include, what to leave out, and a copyable template you can fill in in an afternoon.
Updated

A good software project brief is the difference between three quotes you can compare and three guesses you cannot. Agencies price what they can picture. When the brief is vague, each one fills the gaps with its own assumptions, and the numbers that come back differ by a factor of three for reasons nobody can explain.
In short: a software project brief is two to four pages that say who the product is for, what they do with it, the kinds of user, the main journey, the features in three groups, the platforms, the integrations, and your budget and launch date. Send the same brief to every agency, and judge each one by the questions that come back.
You do not need technical knowledge to write a useful brief. You need to describe who the product is for, what they do with it, and what you already know. This guide walks through each section, then gives you a template to copy.
What a brief is for
A brief has one job: to let someone who has never met you understand the product well enough to ask good questions and give a realistic price. It is not a specification, and it is not a pitch deck.
Two to four pages is enough. Longer briefs are rarely read in full, and a short one forces you to decide what matters. If you have already done the work in our guide on how to scope an MVP, most of the brief is written.
What to include in a software project brief
The product in two sentences
Who it is for and what it lets them do. If you cannot say it in two sentences, the agency will not be able to either.
The problem and the first user
Describe the person with the problem, what they do today instead, and why that is painful. Be specific: "a landlord with two or three flats" is more useful than "property owners". Research on users does not have to be formal. The GOV.UK Service Manual has a clear, practical guide to learning about users and their needs that works just as well for a startup.
What you need to learn
List the two or three things that must be true for the business to work. This tells the agency which features are central and which can wait, and a good team will use it to suggest cuts.
The kinds of user
Every role that needs a screen: customers, suppliers, staff, and your own team running the admin panel. Each new role adds screens, permissions and testing, so this list affects the price more than almost anything else. MealMentor, a meal-planning platform we built, has two portals: one for chefs, who share recipes, and one for users, who plan meals.
The main journey
Walk through the product step by step, from the first visit to the moment the job is done. Numbered steps are fine. Rough sketches on paper, photographed on a phone, are even better.
The feature list, in three groups
Sort every feature into must launch, launch if cheap and version two. Agencies can then price the first group firmly and give you rough numbers for the rest.
Platforms
A web app, an iPhone app, an Android app, or a combination. If you are unsure, say so and ask for a recommendation. Our post on whether to build a web app or mobile app first may help you decide.
Integrations and existing systems
Name every outside service the product needs to talk to: payments, maps, email, accounting, a CRM, an existing database or app. Each one has its own setup and testing, and some need approval from the provider. VSSTA, a portal we built for collision-repair shops, has ten integrations, including Stripe billing and QuickBooks sync.
Content and data
Who will write the text, take the photos, set the prices and supply any starting data? Content that arrives late is one of the most common reasons launches slip.
Products you like, and why
Two or three links to products whose feel or flow you admire, with a sentence on what you like about each. This saves hours of design conversation.
Constraints
Your budget range, your target launch date and why it matters, and any rules your market imposes, such as data protection law or industry regulations. A budget range is not a negotiating weakness. It lets an agency propose what fits, rather than quoting for everything.
Ownership and after launch
State that the code, the designs and every account must be in your company's name. Say what you expect after launch: a support period, ongoing work, or a hand-over to your own team.
How decisions get made
Who approves designs and answers questions, and how quickly. Agencies plan around this, and slow answers cost weeks.
What to leave out
- Technical choices you have not had a reason to make. Unless you have a team that must maintain a particular stack, describe the outcome and let the agency recommend the tools. Ask them to explain why.
- Long market analysis. One paragraph on the market is plenty. The agency needs to understand the user, not your funding pitch.
- Every idea you have ever had. Put them on the version-two list. A brief that tries to describe the whole future product gets a quote for the whole future product.
- Secrets you do not need to share yet. Most briefs can describe the product without revealing anything sensitive. If something must be shared, ask for a confidentiality agreement first.
A copyable software project brief template
Copy this into a document, fill in each line, and delete the hints.
The same template, with a filled-in example, is free to copy from our project brief template on GitHub. To fill it in by hand, download the template as a PDF: two pages, no sign-up.
PROJECT BRIEF: [product name]
1. Summary
Who it is for and what it lets them do, in two sentences.
2. The problem
The first user, what they do today, and why it is painful.
3. What we need to learn
Two or three things that must be true for the business to work.
4. Users and roles
Every kind of user who needs a screen, including our own admin team.
5. Main journey
Step by step, from first visit to job done. Attach sketches if you have them.
6. Features
Must launch:
Launch if cheap:
Version two:
7. Platforms
Web / iPhone / Android / not sure, please recommend.
8. Integrations and existing systems
Payments, maps, email, accounting, existing apps or data.
9. Content and data
What we will supply, and by when.
10. Products we like
Links, with one sentence each on why.
11. Constraints
Budget range, target launch date and why, legal or industry rules.
12. Ownership and support
Code, designs and accounts in our company's name.
What we expect after launch.
13. Decisions
Who approves work and answers questions, and how quickly.
Contact: name, email, best times for a call.
How to use the brief
Send the same brief to every agency on your shortlist, so you are comparing like with like. Then pay attention to the replies. The best ones will come back with questions, point out what is missing, and suggest something to cut. A reply that is only a number, with no questions, tells you the brief was not really read.
Ask each agency to break the quote down by the three feature groups, and to say what is excluded. Our comparison of fixed price vs hourly lists what a fixed quote should include, and our guide on how to choose an MVP development agency lists nine questions to ask alongside it.
What happens after you send it
A brief starts the conversation. It does not finish the scope. At Tesvo, a brief is what we read before the first call. The first week of the project, the blueprint, turns it into a full feature list, a map of every screen and a fixed quote, before any design starts. You can see how that week fits into the rest of the build on our MVP development page.
If you have a software project brief ready, or half ready, send it to us. We will reply with our questions and tell you what we would need to give you a fixed price.
- Planning
- Startups
- Hiring
Building a first version of your product?
We scope it in a week and launch it in 8–12, for a fixed price. Tell us what you want to build.
Keep reading

· 8 min read
How to hire MVP developers: where to look and what to ask
How to hire MVP developers for a startup: the skills a first version needs, where to find developers, what to ask, a paid trial task and what to put in writing.
Read the guide
· 8 min read
MVP development for non-technical founders: a plain guide
MVP development for non-technical founders: what you decide, what to leave to the team, how to check progress without reading code, and what to own from day 1.
Read the guide
· 7 min read
Agency, freelancer or in-house team: who should build your MVP?
Agency vs freelancer vs in-house for your MVP: cost, speed, risk and who manages the work, with a side-by-side table and a simple way to decide.
Read the guide