How to brief a developer on one page (a software brief any owner can write)
Short answer: developers quote what you describe. A vague brief gets a vague, expensive quote, and a job you can’t check. So before you ask anyone for a price, write one page: what it does and who for, how the job runs by hand today, what done looks like, what’s left out, where it lives and who owns it, and your budget ceiling and deadline. Send the same page to every developer, and you can compare the quotes line by line.
Why the brief matters more than the developer
I spent two years selling offshore development to businesses in Australia and Japan. The quotes that went wrong mostly went wrong at the start, when the owner described what they wanted in a meeting and nobody wrote it down on one page.
Here’s what happens. You tell three developers “we need an app for bookings and quotes”. One hears a simple booking form. One hears a full job management system. One hears a customer app in the app store. You get three prices, A$8,000, A$40,000 and A$120,000, and no way to tell which one is right, because they’re quoting three different things.
The fix isn’t finding a better developer. It’s a better page.
Problem 1: you describe the idea, not the job
Most briefs describe software. “An app with a dashboard, logins and notifications.” That’s the developer’s language, and it invites them to fill in the gaps with more features.
The fix: describe the job the software does in your business, in your words. Who uses it, what they do today, and what changes when it works. Customers buy the outcome, not the app. So do you.
Problem 2: nobody wrote down what done looks like
If the brief doesn’t say how you’ll check the work, you’ll find out at the end whether it does what you meant. By then you’ve paid most of the invoice.
The fix: for each thing it must do, write one line on how you’ll check it yourself. No code needed. “A customer books a Tuesday 9am slot on their phone, and it shows in our calendar within a minute” is something you can test on the spot.
Problem 3: the brief is too big
Owners write down everything they might want one day. The developer quotes all of it. The quote comes back too big, and the first version takes six months instead of six weeks.
The fix: only what someone will use or pay for this month. Park the rest. Write the parked list down too, under “not in this version”, so nobody quotes it by accident.
The one-page brief: six parts
Keep it to one page. If it won’t fit, the first version is too big.
1. What it does, and who for. Two sentences a stranger would understand. Who uses it (your staff, your customers or both) and what it does for them.
2. How it runs by hand today. The steps, in order, as they happen now. Who does each step, and roughly how long it takes each week. This is the most useful part for a developer, and the part most briefs leave out. Every manual step you repeat is a feature someone has already paid for. It tells the developer what to build first.
3. What done looks like. For each thing it must do, how you’ll check it yourself. Plain language, one line each.
4. What’s not in this version. Everything you’ve parked. Admin screens, reports, an app store app, payments, other locations. If it’s not on the page, it’s not in the quote.
5. Where it lives, and who owns it. The tools it has to work with (your job software, Xero, Microsoft 365 or Google Workspace, your website). And one line: the code, hosting, domain and accounts will be set up in your business’s name. If a developer or agency holds the keys, you don’t own what you paid for.
6. Budget ceiling and deadline. The most you’ll spend on this version, and when you need it. A ceiling isn’t a target. It tells a good developer what to cut, and it tells you quickly who’s quoting something else.
A made-up example
Here’s a brief for an imaginary physio clinic with four practitioners. It’s made up, to show the shape.
What it does, and who for: new patients fill in their intake form on their phone before the first visit, and it lands in the patient file. It saves front desk staff typing it in, and patients filling in paper in the waiting room.
How it runs by hand today: reception emails a PDF form after booking. About half come back. The rest fill in paper on arrival. Reception types each one into the practice software, around 15 minutes per new patient, about 30 new patients a week.
What done looks like: a test patient gets a link after booking, fills it in on a phone, and the answers show in their file without anyone typing. If the form isn’t done 24 hours before, they get one reminder.
Not in this version: online payments, a patient app, changes to the booking system, reports.
Where it lives: our current practice software and our Microsoft 365. All accounts in the clinic’s name. Patient health information, so the developer must say where the data is stored and who can see it.
Budget ceiling and deadline: [the clinic’s own number], live before the new year.
Before sending even this, the clinic should check whether the practice software already has online intake forms. Many do. The AI you’re already paying for is the same idea: switch on what you have before you pay for something new.
For tradies
The same six parts work for a trade business. A made-up example: a plumbing business wants customers to send photos of the job before the quote. Today, the office texts back and forth and the photos end up on someone’s phone. Done looks like: the photos land in the job in your job software, every time, without anyone forwarding them. Not in this version: online pricing, booking, a customer app.
Check your job software first. If it does 80% of this already, you don’t need a brief. You need an afternoon switching it on.
Before you send it
- Read it as a stranger. Hand it to someone outside the business. If they can’t say back what it does in one sentence, rewrite part 1.
- Send the same page to everyone. Two or three developers, same brief, same questions. Two quotes for different scopes tell you nothing.
- Ask what they’d leave out. A good developer suggests something smaller, or something you could buy. Be careful if the answer to everything is yes. These questions to ask a developer help here.
- Check the quote against the brief. When it comes back, every line on your page should be in the quote, and nothing from your “not in this version” list. Then run it through the 12 quote checks before you sign.
- Start small. Ask whether one small paid piece of work can come first, before the big job.
If you’re still deciding whether to build at all, start with build, buy, wait or stop. A brief is for once you’ve decided to build. It’s not a way to decide.
I can introduce Sazae, a development partner. I’m paid a commission if you go with them, and you’re free to use anyone you like. The same brief works for any developer.
FAQ
What should a brief for a software developer include? What it does and who for, how the job runs by hand today, what done looks like, what’s not in this version, where it lives and who owns it, and your budget ceiling and deadline. One page.
Do I need to be technical to write a software brief? No. You’re describing the job in your business and how you’ll check the work. The developer turns that into the technical plan. If they can’t explain their plan back to you in plain English, that’s your answer.
Should I tell the developer my budget? Give a ceiling. It’s not a target. It tells a good developer what to cut, and shows you quickly who is quoting something bigger than you asked for.
How long should a developer brief be? One page. If it won’t fit, the first version is too big. Move the extras to “not in this version”.
Can I use AI to write the brief? Yes, to tidy your words. Talk it through or type rough notes, then ask it to put them under the six headings. Check every line yourself. It doesn’t know your business, and it will happily add features you never asked for. Leave client details out.
General guidance, not legal or IT security advice. If the software will hold health, financial or other sensitive personal information, get advice for your industry.