How to Brief a Developer So You Get What You Actually Want

Almost every unhappy software project traces back to the same root cause, and it is rarely the code. It is the brief. When a developer builds the wrong thing, it is usually because they were told what to build in features, but never why, for whom, or what "done" actually looks like. A clear brief is the cheapest quality control you will ever buy — an hour of your time up front routinely saves weeks of rework later.

You do not need a twenty-page specification. You need to answer five questions well.

1. The outcome, not the feature list

Start with the result you are paying for, in business terms: "customers can book and pay for an appointment without phoning us." That single sentence tells a good developer more than a list of screens ever will, because it lets them suggest a simpler or better way to reach the same outcome. Features are how; the outcome is why. Lead with why.

2. Who it is actually for

A site for busy tradespeople checking prices on a phone is a different product from one for procurement managers comparing suppliers on a desktop. Name the real people who will use it and the one thing each of them needs to do quickly. Vague audiences produce vague products.

3. What you already have

List your existing pieces: brand assets, written content, a logo, an existing domain, current hosting, any accounts that already exist. Missing content is the single most common reason projects stall — decide early who is writing it. If it is you, that is fine, but say so.

4. Your real constraints

Give a budget range and a genuine deadline, and separate your must-haves from your nice-to-haves. A developer who knows the budget can design something that fits it; one who is guessing will either over-build or cut the wrong corner. Honesty here is not weakness — it is what lets someone scope the work properly.

5. Who decides

Name one person who can approve decisions and give feedback. Projects slow to a crawl when feedback arrives from four people who disagree with each other. One clear decision-maker keeps momentum, even if they gather opinions before deciding.

Put those five answers on a single page and you have a brief that most agencies would be delighted to receive. It will not just get you a better quote — it will get you a better product, because the person building it finally understands what success means to you.