Emergent | Fullstack App

A bad content brief is a hostage note written by someone who has seen SEO from a moving train.

It says things like:

“Write 2,000 words.”
“Use the keyword 14 times.”
“Make it engaging.”
“Rank on Google.”
“Please have this done by Thursday.”

Then everyone acts surprised when the draft reads like a polite robot trapped in a keyword factory.

A good brief does not micromanage a writer into creative paralysis. It gives them the information required to make good decisions without forcing them to reverse-engineer your business, audience, product, search intent, and internal politics from a spreadsheet cell.

The goal is simple: create a brief that makes a capable writer think, “Ah, excellent. I know what I’m doing,” rather than, “I am apparently being paid to guess the password to a locked room.”

Start with the job, not the keyword

Keywords are useful. They are not a strategy, a thesis, or a personality.

The first line of any content brief should answer a far more important question:

What job should this piece do for the business and the reader?

That job might be to:

Help a prospective customer understand a painful problem.
Capture high-intent searchers comparing solutions.
Teach existing customers how to get more value from your product.
Build credibility in a category where trust matters before purchase.
Support sales conversations with a useful, non-salesy resource.
Earn relevant links because it is genuinely more helpful than the pages already ranking.

A keyword tells you what someone typed. It does not fully explain what they need, what they believe, or what would make them trust you.

A weak brief versus a useful one

Weak:

Keyword: “employee onboarding software”
Word count: 2,500
Mention our product three times.

Useful:

Primary job: Help HR leaders evaluating onboarding software understand the practical capabilities they need before booking demos.
Reader: HR or People Operations leaders at 50–500 person companies. They are likely replacing spreadsheets, shared docs, and manual reminder systems.
Search intent: Commercial investigation. They want a buying framework, not a history of onboarding.
Business role: Introduce our product as one option after the reader understands the evaluation criteria.
Desired outcome: The reader saves the checklist, shares it internally, or requests a demo because the article clarified a messy decision.

The second version gives the writer something invaluable: a reason for the article to exist.

Founders especially benefit from this discipline. When you are close to the product, every article can feel like it should explain everything. It should not. A page with six jobs usually completes none of them. Give each piece one primary mission and perhaps one secondary mission. The rest can have their own pages and their own little birthday parties.

Define the reader like a person, not a demographic casserole

“Small business owners” is not an audience. It is a large, anxious continent.

A founder running a seven-person agency, an operations manager at a 150-person logistics firm, and a finance lead at a 900-person SaaS company may all be “small business owners” in somebody’s slide deck. They do not have the same vocabulary, buying process, budget, or tolerance for jargon.

Your brief should identify the reader in enough detail that the writer can make sensible choices about examples, tone, depth, and objections.

Include the reader’s context

A useful audience section covers:

Role and level of expertise: Are they a technical practitioner, a department head, or a first-time buyer?
Trigger event: What made them search today?
Current workaround: What are they doing instead?
Constraints: Budget, time, compliance, team size, implementation complexity, internal approval.
Emotional state: Curious, skeptical, overwhelmed, in a hurry, or trying to avoid looking unprepared in a meeting.
Decision stage: Learning, comparing, selecting, implementing, or troubleshooting.

For example:

Reader context: A marketing manager at a growing B2B company has been asked to “do more with content” after organic traffic stalled. They may have a freelance writer or agency but no reliable process. They are not looking for a lecture on what a content brief is; they want a template that stops revision loops and makes output more consistent.

Notice how this changes the article. You would use practical templates, examples of revision problems, and plain language. You would not open with a grand historical overview of editorial workflows, unless you enjoy watching readers close tabs with the speed of a startled cat.

Add the objections the writer needs to handle

Writers cannot address objections they have not been told about.

Include three to five likely reader thoughts, such as:

“This sounds expensive to implement.”
“We are too small to need a formal process.”
“Our writers already know our industry.”
“Will this make content sound generic?”
“Can we do this without hiring a content strategist?”

These objections become useful sections, transitions, examples, and FAQ material. More importantly, they prevent the article from becoming a cheerful monologue that ignores the reader’s actual concerns.

Give search intent the respect it deserves

Search intent is the difference between bringing someone a map and handing them a coupon when they asked where the bathroom is.

Before writing the brief, review the search results for the primary query and a handful of close variants. You are not looking to copy competitors’ headings like a student peering over during an exam. You are looking to understand what Google appears to reward because it aligns with what searchers want.

Review:

The dominant page type: guide, tool, category page, product page, comparison, template, or list.
The recurring subtopics.
The freshness of the results.
Whether results are beginner-friendly or expert-level.
Whether readers appear to want a direct answer, a workflow, examples, downloadable assets, or product comparisons.
Related questions and search refinements, where relevant.

Translate the SERP into editorial direction

Do not dump a pile of URLs in the brief and call it research. Explain the implication.

Unhelpful:

Competitors:
[ten links]

Useful:

SERP pattern: Most ranking pages offer content brief templates and general definitions. Few explain how a founder should adapt a brief for a freelance writer versus an in-house subject-matter expert.
Opportunity: Differentiate with a “minimum viable brief” framework, a completed example, and advice on what not to prescribe.
Must cover: Purpose, audience, search intent, angle, structure, source expectations, product mentions, and acceptance criteria.
Avoid: Generic lists of “SEO best practices” without showing how they affect the writer’s work.

This is evidence-aware without pretending search results are sacred tablets. The SERP is a demand signal, not a commandment. If every result is bland, your obligation is not to join the beige parade.

Use keywords as ingredients, not handcuffs

Your brief can include:

Primary query: The central topic.
Secondary queries: Closely related searches worth answering naturally.
Concepts and entities: Tools, frameworks, standards, terminology, or use cases readers expect to see.
Language to avoid: Outdated terms, misleading claims, or phrases your market does not use.

Avoid keyword-density targets. They encourage writing that sounds like a tax form trying to flirt.

Instead, tell the writer:

Use the primary phrase where it is natural and make sure the article answers the question implied by it. Cover related concepts when they help the reader make a decision.

That is both better writing advice and better search advice.

Set the angle so your article has a pulse

Most content fails not because it is wrong, but because it is interchangeable.

If a competitor could replace your logo with theirs and publish the same article tomorrow, you have produced content-flavored packing foam.

A strong brief gives the writer an angle: a specific, defensible point of view that makes the piece more useful than a generic explainer.

Choose one central promise

The angle should answer:

Why should someone read this version rather than the other 27 articles on the same topic?

Examples:

“A practical buyer’s guide built around implementation risks, not feature checklists.”
“An explanation for non-technical founders who need to make a competent decision without becoming database administrators.”
“A template-driven guide for teams with one marketer and zero appetite for extra meetings.”
“A contrarian but reasonable argument: you do not need more content ideas; you need better content operations.”

For this article, the central promise might be:

Show founders how to create briefs that protect quality and search performance without turning writers into button-pressing text dispensers.

That promise informs everything: tone, examples, template fields, and what gets cut.

Provide a clear “do not write” list

Writers appreciate boundaries. They are not a failure of trust; they are a way to avoid discovering your hidden preferences after 1,800 words.

Include notes such as:

Do not begin with a dictionary definition unless it earns its keep.
Do not claim that a process “guarantees rankings.”
Do not make the product the hero of every section.
Do not pad the article to meet a word count.
Do not repeat obvious advice without an example.
Do not write for SEO beginners if the audience is experienced practitioners.

This is the editorial equivalent of marking where the wet paint is. Everyone gets to keep their sleeves clean.

Give structure without writing the article in advance

There is a fine line between a useful outline and a brief that has already drafted the article badly.

Writers need a map. They do not need a box of IKEA instructions translated from Swedish by a haunted fax machine.

A good outline identifies the questions that must be answered, the order in which the reader needs them answered, and any necessary evidence or examples.

Build an outline around reader decisions

Instead of this:

Introduction
What is X?
Benefits of X
How to use X
Conclusion

Try this:

Why the current approach creates a specific problem.
What the reader needs to understand before acting.
The practical framework or steps.
Common mistakes and how to avoid them.
A completed example.
What to do next.

The second structure has momentum. It helps the reader move from recognition to understanding to action.

Specify requirements at the right level

Here is the sort of direction that helps:

Section requirement: Include a completed mini-brief for an imaginary B2B software company. Show the difference between “keyword + word count” and a brief with audience, intent, angle, and source notes.
Reason: Founders need to see the operational difference, not just hear that details matter.

And here is the sort that does not:

In paragraph four, say “content strategy” and include a sentence about Google.

Unless you are commissioning legal copy, precise claims, or regulated material, leave room for the writer to do the thing you hired them to do: think.

Make evidence and brand knowledge easy to use

A brief should not merely demand “credible sources.” It should make credibility possible.

Writers often face a choice between spending half their budget on research or filling gaps with confident-sounding mush. Your briefing process should remove that choice.

Supply the raw materials

Provide links or access to:

Product documentation and current feature pages.
Customer research, interview notes, support tickets, and sales-call themes.
Subject-matter experts available for questions.
Internal data that can be responsibly cited.
Approved case studies and testimonials.
Brand voice guidance.
Prior content worth linking to.
Competitor positioning notes, if appropriate.

Be clear about what is verified, what is an opinion, and what must be reviewed by legal, product, or compliance.

For example:

Approved claim: Customers can automate reminder emails based on onboarding milestones.
Do not claim: The platform “ensures employee retention.”
Subject-matter expert: Head of People Operations can verify implementation examples.
Required source standard: For factual industry claims, use primary sources, official documentation, reputable research organizations, or clearly attributed expert commentary.

This matters because factual precision is not decoration. In B2B, health, finance, legal, and technical categories especially, one breezy unsupported claim can turn a useful article into a sales liability wearing a clean blazer.

Tell writers how the brand should appear

The brief should state:

Whether and where to mention the product.
Which features are relevant.
What competitors may or may not be named.
The preferred call to action.
Tone boundaries: direct, technical, warm, irreverent, cautious, etc.

A useful rule: the product should appear where it resolves a problem the article has already earned the right to discuss. If it barges in during the introduction wearing a branded sash, readers can smell the ambush.

Define “done” before revisions become wildlife

The most writer-friendly thing you can do is define acceptance criteria. The second most writer-friendly thing is actually use them.

Without a definition of done, feedback often arrives as a fog bank:

“Can we make it more strategic?”
“This doesn’t feel quite right.”
“Could it be punchier but also more comprehensive?”

These are not comments. They are mood rings.

Use a simple quality checklist

Add a checklist to every brief:

Also name the decision-maker. Nothing makes a writer secretly hate a brief faster than seven stakeholders, each adding contradictory notes as if content review were a group escape room.

One owner should consolidate feedback. That person can collect perspectives, but they must resolve conflicts before sending revisions. “Make it more beginner-friendly” and “assume the reader already knows the basics” cannot both win. They can, however, both generate a very expensive second draft.

The minimum viable brief for busy founders

You do not need a 14-page document for every 800-word article. A brief should be proportional to the stakes.

For a straightforward supporting article, a one-page brief may be perfect. For a flagship guide, regulated topic, or comparison page, invest more.

Here is a practical minimum viable format:

Content goal

What should this page achieve for the reader and business?

Audience

Who is searching? What triggered the search? What do they already know?

Search intent and primary query

What does the searcher expect? What is the central query and related concepts?

Angle

What makes this piece more useful or distinctive than existing results?

Required structure

Key sections, questions to answer, examples, tables, or templates.

Evidence and inputs

Approved sources, product docs, SMEs, claims to avoid, internal links.

Brand and conversion notes

Product mention rules, CTA, tone, competitor references.

Definition of done

Length range, sourcing expectations, reviewer, deadline, acceptance checklist.


That is enough to create alignment without building a small municipal government around one blog post.

The prescription

Before commissioning your next article:

Write the page’s single primary job in one sentence.
Describe the reader’s trigger, workaround, and objections.
Review the search results and state the intent and content opportunity.
Give the writer a clear angle, not just a keyword.
Supply approved sources, product facts, and one person who can answer questions.
Define “done” with a checklist and appoint one final decision-maker.
Ask your writer one final question: “What is missing from this brief that would help you produce the best version?”

That last question costs nothing, prevents a remarkable amount of nonsense, and may be the most efficient content-operations upgrade available to humanity.