Why We Refuse to Start Work Without a Complete Brief
A client asks us to write a landing page for their new product.
We say: “Great. What’s the conversion goal? Who’s the audience? What’s the key message? What form fields do you need? What integrations are required? What does success look like?”
They say: “Uh… just make it good?”
And here’s the thing — that’s not a bad client. That’s a normal client. That’s every client, at some point. They know what they want in their head. They haven’t translated it into a brief because that’s not their job. That’s ours.
The old way we handled this: say yes, start work, ask questions over email as they come up, receive partial answers, make educated guesses, deliver something we thought was right, get three rounds of revisions, end up somewhere in the middle of what we built and what they meant, both parties vaguely unsatisfied.
Garbage in, garbage out.
We don’t do it that way anymore.
Why We Were the Problem
I want to be clear about something. The incomplete brief isn’t the client’s fault. It’s the agency’s fault.
Agencies are incentivized to start fast. Billable work starts when execution starts, not when planning starts. Nobody gets excited in a pitch by saying “we’ll spend the first two weeks on discovery.” Fast response, fast delivery, fast invoice — that’s the rhythm the industry runs on.
And clients have been trained by agencies to expect this. They don’t know what questions to expect. They don’t know what information is actually required to produce good work. They’ve never seen a complete brief because most agencies never ask for one. So they describe what they want in the most natural way they know how, which is vague and incomplete, and the agency runs with it and hopes for the best.
Three rounds of revisions later, everyone’s exhausted and nobody’s entirely happy and somehow this is described as “the creative process.”
It’s not the creative process. It’s the consequence of starting without sufficient context.
We got tired of it.
What We Built
The Brief System is simple in principle: work doesn’t start until the brief is complete. No exceptions. Not even for quick jobs. Especially not for quick jobs, because “quick” work delivered on incomplete information becomes slow work when the revisions land.
Here’s how it works in practice.
When a new job comes in, we create a brief. The brief type depends on the deliverable — a landing page brief asks different questions than an article brief or a LinkedIn post brief. That matters. Generic briefs that ask the same questions regardless of what you’re building are almost as useless as no brief at all. The question set has to be calibrated to the specific output being created.
But here’s the bit that changed everything for us: about 60% of the brief auto-populates from what we already know about the client.
Every client we work with has a set of context files. Personas (who their audience is). Messaging (what their positioning is). Editorial guidelines (how they write and what they won’t say). Offerings (what products and services actually exist). Voice DNA (how their founder or brand sounds).
Before we ask a single question, all of that context is loaded. The writer doesn’t need to ask “who’s the audience?” because the personas are already there. The strategist doesn’t need to check the messaging framework mid-brief because it’s pre-loaded.
What’s left — the 40% that changes per job — gets covered in a focused ten-minute conversation. Conversion goal. Form fields. Integration requirements. Success metric. Timeline. Specific constraints.
Ten minutes. Complete brief. Work starts with confidence.
Before and After (Real Example)
Here’s what the old process looked like for a landing page build.
Client sends the request. We say “yes” and assign a writer. Writer starts with the headline and then realizes they don’t know what the conversion goal is, so they email the client. Client responds two days later — they want email captures, not demo requests. Writer revises the hero. Then realizes they don’t know what form fields are needed, so they email again. Client responds after a day — they need name, company, phone, and LinkedIn. Writer asks about integrations. Client needs to check with their developer, three days later it’s HubSpot. Two weeks of email thread. Writer now has 70% of the information and makes educated guesses about the rest.
Landing page delivered. Client says “this isn’t quite right — we’re targeting enterprise buyers, not SMBs.” Writer assumed the wrong persona. Back to revision.
Three rounds and two weeks of email tags later, you have something acceptable. Not great. Acceptable.
Here’s what the new process looks like for the same job.
Client sends the request. We say “let’s create a brief — this will take ten minutes.” We load the client context. System pre-populates audience, messaging framework, voice guidelines. We ask ten focused questions in one session. Client answers all of them. Brief generated: complete, documented, filed. Writer starts with 100% of the required context.
Landing page delivered. Client says “perfect, exactly what we needed.”
Revision rounds: zero.
Time from brief to delivery: faster than the old process including the revisions.
The brief session feels like slowing down. It’s actually the fastest path through.
What the Brief Does to the Client Relationship
Something unexpected happened when we started doing this consistently. Clients started changing.
Not all at once. But across a few months, clients who’d worked with us through the Brief System started briefing us better. First brief, they’d say “I didn’t realize you needed all this.” Second brief, they’d say “Oh, I see why you ask these questions.” Third brief, they’d start volunteering the information before we asked.
The brief session trains clients to think like marketers. It teaches them that “just make it good” isn’t a brief — not because it’s a bad thing to want, but because “good” without specified criteria is unverifiable and therefore unachievable. It shows them the actual inputs that go into quality output. And it builds their confidence, because they leave the brief session understanding what’s being built and why each decision was made.
Fewer surprises at delivery. Higher satisfaction scores. Less revision churn. Longer relationships.
The brief isn’t just operational hygiene. It’s a client development tool.
What It Does for Institutional Knowledge
There’s a less obvious benefit that compounds over time.
Every brief we create is a documented artifact. Stored, searchable, traceable. A year from now, when a client asks “how did we approach the last landing page?” — we have the answer. When we’re onboarding a new team member on a client, they don’t have to piece together context from a trail of Slack messages and email threads. They read the briefs.
Which conversion goals worked. Which personas responded to which messaging. Which assumptions turned out to be wrong. All of it documented, not lost in someone’s inbox.
Most agency knowledge lives in the heads of individual team members. When those people leave or are unavailable, the knowledge disappears. The Brief System makes knowledge structural. It lives in the files, not the people.
That’s a competitive advantage that compounds with every brief you complete.
How to Start Doing This
You don’t need a system like ours to implement this principle. You need three things.
The first brief you run this way will feel slow. The tenth will take ten minutes and produce better work than three revision rounds on the old approach.
“Slow down to speed up” sounds like a platitude. In this case it’s just arithmetic.
Start your next project with a complete brief. Time the whole process including revisions. Compare it to the last project you started without one.
You’ll run the Brief System forever after.
