The Content Brief: How to Give Writers Everything They Need to Sound Like You

The most common complaint about outsourced content is that it doesn't sound right. Too generic. Too formal. Not the way we talk. Missing the specific angle that would have made it useful.

Almost every one of these complaints traces back to the same root cause: a bad brief — or no brief at all.

A content brief is the document you give a writer before they start. Done well, it transfers enough context that the output sounds like it came from inside your company. Done poorly, it produces content that reads like it was written by someone who Googled your industry for 20 minutes.

The good news: writing a strong brief doesn't take long. It takes knowing what to include.

Why Most Briefs Fail

The typical content brief looks like this: a title, a target keyword, and maybe a note about word count. Sometimes there's a competitor link for reference.

That brief tells a writer almost nothing about what actually matters. What's the specific argument? Who's the reader and what do they already know? What's the tone — direct and opinionated, or measured and educational? What conclusion should the reader reach? What's the one thing they should do after reading?

A writer who doesn't know the answers to these questions will make them up. They'll default to safe, generic choices that technically fulfill the brief but don't produce the result you wanted.

The brief's job is to make the right choices obvious so the writer doesn't have to guess.

The Core Elements of a Strong Brief

Target keyword and intent. The keyword tells the writer what query this post should rank for. The intent tells them what the reader actually wants. "Project management software for law firms" is a keyword. The intent is a buyer who's evaluated generic PM tools and concluded they don't fit legal workflows — so they're now searching for something built for their specific context. That distinction changes what the post should say and how it should frame its argument.

The specific angle. Two posts can target the same keyword and make completely different arguments. The angle is your specific take — the non-obvious insight, the contrarian position, the experience-based perspective that makes your post worth reading instead of the ten already ranking for the same term. This is the hardest thing for a writer to invent without your input, and the most important thing to specify.

"Write a post about content briefs" produces one result. "Write a post arguing that most content brief advice focuses on SEO structure and completely ignores the voice and angle transfer problem — which is why ghostwritten posts consistently fail to sound like the founder" produces a completely different result. The second brief produces the post you actually wanted.

Reader context. Who is this post for, specifically? Not just "B2B marketers" — what do they already know? What have they already tried? What's the frustration that brought them to this post? A post for first-time content managers reads differently than one for founders who've hired and fired three content agencies. Specify the reader at the level of detail that would let you describe them to a colleague.

Voice and tone notes. If you've published other content, point the writer to two or three posts that nail the tone you want. If you haven't, describe it: direct or conversational? Opinionated or balanced? Technical or plain-language? Do you use contractions? Do you write in the first person? Are industry terms used casually or explained carefully?

Voice transfer is one of the hardest parts of ghostwriting. Good brief writers don't just say "write in my voice." They give examples, describe the texture of the tone, and flag the things that consistently feel wrong (overly formal openings, excessive hedging, listicle formats when you prefer prose).

The specific outcome. What should the reader think, feel, or do after finishing this post? This is different from the CTA. The CTA is a button or a link. The outcome is the shift in perspective or understanding that makes the CTA feel natural. If the reader finishes the post and thinks "huh, I hadn't considered that angle" before clicking to learn more, the post worked. If they finish and feel vaguely informed but unchanged, it didn't.

What to avoid. Almost as useful as specifying what to include is specifying what to leave out. Common avoid-lists include: particular framings that have been used to death in your industry, competitor companies that shouldn't be named, jargon your audience finds alienating, or specific angles that seem relevant but don't serve your audience.

What a Usable Brief Actually Looks Like

You don't need a ten-page document. A strong brief for a 1,000-word blog post is usually one page. Here's a working structure:

Post title (working): The Content Brief: How to Give Writers Everything They Need to Sound Like You

Target keyword: content brief template / how to write a content brief

Search intent: Someone who is about to start working with a freelance writer or ghostwriting service and wants to know how to set the engagement up for success. They've probably had a bad experience with outsourced content before.

The angle: Most content brief advice focuses on SEO structure. The real failure point is the voice and argument transfer. This post argues that the brief's most important job is reducing the amount of guessing the writer has to do about what you actually think.

Reader context: Founder or marketing lead at a B2B company. Has tried outsourcing content before. The posts came back technically fine but felt generic and were quietly shelved.

Tone: Direct. Opinionated. Prose-first, not listicle. Sounds like advice from a senior colleague, not a content marketing textbook.

Outcome: Reader should feel equipped to write a brief tomorrow that produces meaningfully better content than what they've gotten before.

Avoid: Jargon around "content strategy." Excessive hedging. Any framing that implies briefing is complicated or time-consuming — it shouldn't feel that way.

That brief is enough. A skilled writer can build a strong post from it. An inexperienced writer has enough guardrails to avoid the common failure modes.

The Brief as Voice Documentation

There's a second use for a good brief that most companies miss. Over time, a series of well-written briefs becomes a documentation of your voice, your angles, your recurring perspectives, and your content standards.

When you onboard a new writer, those briefs are the training material. When a writer goes on leave and you bring in someone temporary, the brief history is the fastest way to get them calibrated. When you want to audit whether your content has drifted from its original voice, the briefs are the reference point.

Treat your briefs as living documents, not throwaway task assignments. Keep them in a shared folder with the finished posts. The collection of your briefs — and the posts they produced — is the most specific documentation of your content standards that exists.

When to Invest More in the Brief

Not every post requires the same brief depth. Short supplemental posts on well-established topics can work from a lighter brief. High-stakes posts — your pillar content, your most competitive keywords, your cornerstone thought leadership — deserve a more thorough brief.

Also invest more brief time in the first three to five posts with any new writer. Early in a relationship, the brief is doing the heavy lifting of voice and style transfer. As the writer learns your patterns, the brief can get shorter because they're filling in the gaps from experience rather than guessing.

The investment in early briefs pays back across every post that follows. A writer who truly understands your voice after five well-briefed posts will produce better work with shorter briefs than a writer who gets a one-line task and has to invent the rest.

The Bottom Line

Content quality problems — posts that feel generic, miss the mark, or don't sound like you — are rarely the writer's fault alone. They're usually a brief failure.

The brief is where you transfer what's in your head to someone else's hands. Get it right, and the output reflects your perspective, your voice, and your specific argument. Get it wrong, and you get content that's technically about the right topic but doesn't say what you would have said.

Write the brief. Make it specific. Point to examples. Define the angle before the writer has to invent one.

That single habit is the difference between outsourced content that works and outsourced content that gets quietly discarded.