How to Brief a Studio: What to Share So You Get What You Want

Most disappointing projects were not badly built. They were badly briefed: the studio delivered what was asked for, which was never quite what was meant. A good brief fixes that first.

A brief is not a form, a contract or a technical document. It is the clearest possible answer to one question: what are we making, for whom, and how will we know it is right? You do not need design vocabulary or a finished plan — you need honesty about the problem and a few specifics a studio cannot guess.

Here is what to share, in the order that matters most. None of it takes long, and every part of it protects you: a studio working from a clear brief has nowhere to hide.

1. Start with the outcome, not the deliverable

"We need a new website" is a deliverable. "Customers keep asking questions the site should answer, and inquiries are going to businesses that explain themselves better" is an outcome. The difference matters, because the outcome is what lets a studio make good decisions when you are not in the room.

Describe what should be different when this is done: what people will be able to do, understand or feel, and what problem in the business gets quieter. If the honest answer is "we are not sure yet, we just know the current thing is not working," say exactly that. A vague outcome honestly stated is far more useful than a precise-sounding one invented to fill the page.

2. Say who it is for

Every design and content decision changes depending on the audience, so name yours as concretely as you can: who they are, what they already know, what they are comparing you against, and what would make them trust you — or walk away. "Small business owners" is a start; "owners who have been burned by a cheap website before and now check everything twice" is a brief a studio can actually design for.

If you serve more than one kind of customer, say which one matters most for this project. A site, a brand or a system built for everyone ends up speaking clearly to no one.

3. Show examples — including what you dislike

Words like "modern," "clean" and "premium" mean something different to every person in the room. Examples do not have that problem. Share a handful of websites, brands, videos or products you like — and, just as important, say what you like about each one. It might be the calm layout or the plain language — the studio needs the reason, not just the link.

Examples of what you dislike are worth as much. Knowing "anything that looks like this feels wrong for us" early prevents the most expensive kind of revision: discovering opposite tastes after the work exists. There is no wrong answer here — taste stated early is information; taste revealed late is a restart.

4. Separate must-haves from nice-to-haves

Every project has two lists hiding inside it: the things the work genuinely fails without, and the things that would be lovely if everything goes well. Trouble starts when the two are mixed together and everything is described as essential — because then the studio cannot tell what to protect when a trade-off appears, and trade-offs always appear.

So split them openly. Must-haves are few and non-negotiable: the inquiry form has to work, the tool has to handle this one report, the brand files have to cover these formats. Nice-to-haves are everything else, in rough order of how much you want them. A good studio will build the must-haves first and treat the second list as a queue, not a promise.

5. Share what already exists

Studios lose more time hunting for materials than building with them. Gather what you have before the first call: your current website and how it is hosted, logo and brand files in whatever form they exist, photos, videos and written content, and the accounts the project will touch — domain, hosting, social profiles, tools you already pay for. If some of it is missing or messy, say so — knowing on day one is what counts.

This is also where an honest look at your brand materials helps. If your logo only exists as a low-resolution image inside an old document, say so — rebuilding it properly may need to be part of the work. Our guide to what a small business brand actually includes shows what a complete set looks like, so you can check what you have against it.

6. Be honest about the constraints

Every project has constraints; the only question is whether the studio learns about them at the start or halfway through. Two matter most. The first is budget. You do not need to hand over a precise figure to be helpful — but be honest about the shape of it: whether this is a careful small step or a serious investment, and what would make it feel expensive rather than worthwhile. A studio that knows the shape can propose the right-sized solution instead of guessing wrong in either direction.

The second is time. Say which deadlines are real — tied to an event, a launch, a season, something that will not move — and which are simply when you would like it done. Real deadlines change how a project should be structured; flexible ones just set a rhythm. Hiding a hard one, or dressing up a soft one, ends in the same place: a rushed decision nobody wanted.

7. Name one decision-maker

Projects rarely stall on the work. They stall on decisions waiting for a person — or worse, on feedback arriving from several people, in several directions, with no one able to settle the disagreement. Before work starts, name the one person who reviews, gathers input from everyone else who needs a say, and gives the studio a single, settled answer.

This is not about shutting anyone out. It is about making sure that when the studio asks "is this right?", the answer they act on is the answer the business actually means. One voice, clearly chosen, keeps the project moving.

8. What a good studio sends back

A brief is a two-way street, and what comes back tells you a lot about who you are hiring. Expect two things. First, questions — about your answers, your examples, your constraints. A studio that asks nothing has either understood everything perfectly (unlikely) or is planning to guess (common, and dangerous). Second, a written scope: what will be made, what will not, what it depends on, and what happens if you want to change it later. Plain language, in writing, before money moves.

If what comes back is only enthusiasm and a number, the brief did not fail — it did its job, and showed you the studio was not listening. Walk away politely and brief the next one.

A brief is just the first piece

None of this needs to be long. A page of honest answers to the questions above is a better brief than a thick document of assumptions. And it slots into a bigger picture: the website, brand, content and systems a business runs on work as one connected whole — which is why we wrote about how a small business grows online as a system, not a shopping list. The brief is where that system starts: with the problem, stated plainly, by the person who knows it best — you.