The short answer
- Describe the work done by hand today, who does it and what it costs, rather than a list of features.
- Ask who will build it, who owns the code, and what happens after launch.
- Ask to see software the agency runs, not only software it delivered.
What to put in the brief
- The work. What is done by hand today, step by step, and by whom.
- The cost. Hours a week, mistakes, missed payments, lost jobs. A rough number is enough.
- The people. Who will use the software, where they are, and what they use now.
- The rules. Approvals, tax, regulations, deadlines. Anything that must be right.
- The systems. Accounting, payments, email and anything else it must connect to.
- The timing. Any date that genuinely matters, and why.
Leave out the feature list if you can. Agencies are good at turning problems into features, so give them the problem.
Five questions to ask any agency
- Who will actually build it? Will you speak to them, or to an account manager?
- Who owns the code and the accounts? The answer should be you, from day one.
- How often will we see working software? Every week or two is healthy. A big reveal at the end is a risk.
- What happens after launch? Who fixes it at 8am on a Monday, and what does that cost?
- What do you run yourselves? Software an agency runs for paying customers tells you more than a portfolio of screenshots.
Warning signs
- A price before anyone has asked how the work is done today.
- No mention of data, permissions or what happens when something fails.
- Code and app store accounts held in the agency's name.
- AI added to the proposal with no cost per use and no review step.
Ready to write yours? Our brief builder asks these questions for you.