---
name: content-brief-writing
slug: content-brief-writing
description: This skill should be used when the user asks to "write a content brief", "create a content brief", "design a content brief template", "brief a writer", "outline a content piece", "create a writing brief", "build a content brief for SEO", "write a brief for a blog post", or any variation of writing, designing, or templating content briefs for B2B SaaS content production.
category: general
---

# Content Brief Writing

A content brief is the single document that determines whether a content piece succeeds or fails. A good brief eliminates ambiguity: the writer knows exactly what to produce, who it's for, what question it answers, and what "good" looks like. A bad brief — or no brief — produces content that misses the target and requires multiple revision cycles.

Every piece of content gets a brief. No exceptions. Even a 500-word glossary page gets a brief. The brief doesn't need to be long — it needs to be specific.

## The Content Brief Template

Every brief must contain these sections. Skip a section and the output suffers.

### Section 1: Target definition

| Field | What to specify | Example |
|-------|----------------|---------|
| Primary query | The single most important query this page answers | "What is revenue intelligence?" |
| Secondary queries | 2-3 related queries the page should also address | "How does revenue intelligence work?", "Revenue intelligence vs conversation intelligence" |
| AI search query | How a user would ask this in ChatGPT/Perplexity | "What is revenue intelligence software and which tools are best for B2B sales teams?" |
| Search intent | Problem-aware, solution-aware, product-aware, or purchase-ready | Solution-aware |
| Target audience | Specific role, company stage, context | VP Sales at a B2B SaaS company ($5-50M ARR) evaluating revenue intelligence tools |

### Section 2: Content specification

| Field | What to specify | Example |
|-------|----------------|---------|
| Page type | Definition, comparison, how-to, listicle, case study, etc. | Definition page |
| Target word count | Specific range based on page type | 1,500-2,000 words |
| Required H2s | The specific H2 headers the piece must include | "What is revenue intelligence?", "How does revenue intelligence work?", "Who needs revenue intelligence?", "Best revenue intelligence tools" |
| Required elements | Tables, lists, FAQ section, schema type | Comparison table of tools, FAQ section with 6-8 questions, FAQPage schema |
| CTA | What action the reader should take | Demo request (soft — end of page only) |

### Section 3: Content requirements

| Field | What to specify | Example |
|-------|----------------|---------|
| Angle / thesis | The specific point of view or argument the piece should make | "Revenue intelligence is replacing standalone conversation intelligence and deal management tools" |
| Key points to cover | 3-5 specific points the piece must make | 1) Define RI distinctly from CI, 2) Name top 5 tools, 3) Include pricing, 4) Cover integration requirements |
| Competitors to mention | Which competitors to include and how to position them | Name Gong, Clari, and Chorus. Be balanced — include their strengths. Position our product as best for teams with 20-50 reps |
| Data / stats to include | Specific data points or where to find them | Include G2 satisfaction scores, Forrester Wave positioning if available |
| Internal links | Pages on our site to link to from this piece | Link to /vs/gong-vs-clari, /pricing, /integrations |

### Section 4: AEO requirements

| Field | What to specify | Example |
|-------|----------------|---------|
| First 50 words | Draft or specify what the opening must contain | Must include a clean definition of revenue intelligence in the first sentence |
| Extractable answer | The sentence an AI engine should be able to lift | "Revenue intelligence is a category of sales software that captures buyer interaction data to surface deal insights and improve forecast accuracy." |
| Schema type | Which structured data to apply | FAQPage + Article |
| FAQ questions | Specific questions for the FAQ section | "What is the difference between revenue intelligence and conversation intelligence?", "How much does revenue intelligence cost?" |

### Section 5: Reference and context

| Field | What to specify | Example |
|-------|----------------|---------|
| Competitor pages | URLs of competitor pages ranking for the target query | [URL 1], [URL 2] — note what they do well and where they fall short |
| Internal reference | Existing content, sales decks, customer interviews to reference | Q4 sales deck (slide 12-15 on market positioning), customer interview with [Company] |
| Style reference | An existing published piece that matches the desired quality | "Write in the style of our /vs/hubspot-vs-salesforce page" |
| What NOT to do | Explicit constraints | Don't write a product pitch. Don't gate the content behind a form. Don't use jargon without defining it |

---

## Brief Writing Rules

### Be prescriptive about structure

The most common brief failure is leaving structure to the writer. Specify every H2. The writer fills in the content; the strategist defines the skeleton.

**Bad brief:** "Write a blog post about revenue intelligence. ~2,000 words."

**Good brief:** "Write a definition page answering 'What is revenue intelligence?' Structure: H2s for definition, how it works, who needs it, top tools, pricing comparison, FAQ section. 1,500-2,000 words. First sentence must be a clean definition. Include a comparison table of top 5 tools with pricing."

### Specify the angle, not just the topic

Every piece needs a point of view. Without an angle, the writer produces generic content identical to every other page on the topic.

| Topic only | Topic + angle |
|-----------|---------------|
| "Write about lead scoring" | "Write about how most lead scoring models are broken because they weight demographic data over behavioral signals. Argue for behavior-first scoring" |
| "Write about CRM data hygiene" | "Write about how dirty CRM data costs the average SaaS company $30K/year in lost deals, with a step-by-step cleanup process" |
| "Write about ABM" | "Write about why ABM fails at companies with fewer than 3 SDRs, and what to do instead" |

### Include the extractable answer

For AEO, the brief should draft the exact sentence you want AI engines to extract. The writer builds the page around this anchor.

**Example:**
> **Extractable answer:** "Revenue intelligence is a category of sales software that captures buyer interaction data — calls, emails, meetings — to surface deal insights and improve forecast accuracy. Leading revenue intelligence platforms include Gong, Clari, and Chorus."

This sentence appears in the first 50 words of the published page.

### Reference the competition

Always include 2-3 competitor URLs that rank for the target query. Note what they do well and where they fall short.

| Competitor page | Strength | Weakness |
|----------------|----------|----------|
| [Competitor A URL] | Comprehensive feature table, good H2 structure | No pricing info, dated (2024) |
| [Competitor B URL] | Current data, good FAQ section | One-sided (only promotes their product) |

This tells the writer what to match and where to differentiate.

---

## Briefs by Content Type

### Comparison page brief additions

| Extra field | What to specify |
|------------|----------------|
| Products to compare | Exact products. "Compare X and Y" not "compare tools in the category" |
| Comparison dimensions | Features, pricing, integrations, best use case, limitations |
| Verdict | What verdict to reach. "X is better for [use case]. Y is better for [other use case]" |
| Table structure | Columns and row headers for the comparison table |

### How-to guide brief additions

| Extra field | What to specify |
|------------|----------------|
| Steps | Exact number of steps and what each covers |
| Tools needed | Specific tools the reader needs |
| Prerequisites | What the reader must have before starting |
| Expected outcome | What "done" looks like |
| Schema | HowTo schema required with `totalTime` |

### Case study brief additions

| Extra field | What to specify |
|------------|----------------|
| Customer name | Named or anonymized? If named, get approval |
| Challenge | The specific problem (in the customer's words if possible) |
| Solution | What was implemented and how |
| Results | Specific metrics (before/after numbers required) |
| Interview source | Who to interview and what to ask |

---

## Brief Quality Checklist

Score every brief before handing to the writer:

| Criterion | Check |
|-----------|-------|
| Primary query defined | Could the writer search this exact query and understand the target? |
| Target audience specified | Would the writer know who they're writing for? |
| Page type chosen | Would the writer know whether to write a listicle, comparison, or guide? |
| H2s prescribed | Could the writer build the page skeleton without guessing? |
| Angle stated | Does the brief have a point of view, not just a topic? |
| Extractable answer drafted | Is the first-sentence answer pre-written? |
| Competitor pages linked | Can the writer see what to match and beat? |
| Word count specified | Does the writer know the target length? |
| AEO requirements listed | Will the writer know to add tables, FAQ, schema? |
| What NOT to do | Are common mistakes explicitly called out? |

**If any criterion is missing, the brief is incomplete.** A writer receiving an incomplete brief will either guess wrong or ask 5 clarifying questions — both waste time.

---

## Pre-Handoff Checklist

Before giving a brief to a writer:

- [ ] Primary and secondary queries defined
- [ ] AI search query variant included
- [ ] Search intent classified
- [ ] Target audience described (role, company size, context)
- [ ] Page type selected
- [ ] Word count range specified
- [ ] All H2s listed in order
- [ ] Angle / thesis articulated in 1-2 sentences
- [ ] Key points to cover listed (3-5)
- [ ] Extractable answer sentence drafted
- [ ] FAQ questions listed (if applicable)
- [ ] Competitor pages linked with strength/weakness notes
- [ ] Internal links specified
- [ ] Schema type assigned
- [ ] Style reference provided

---

## Anti-Pattern Check

- Brief is a one-liner: "Write about X" → This produces generic content. Add structure (H2s), angle, audience, and AEO requirements. A 15-minute brief saves hours of revision
- No competitor reference → Without seeing what ranks, the writer operates blind. Include 2-3 competitor URLs with notes on strengths and weaknesses
- Brief prescribes the topic but not the angle → "Write about lead scoring" produces the same generic article as every competitor. "Write about why behavior-first scoring outperforms demographic scoring" produces something distinctive
- No AEO requirements in the brief → If AEO isn't in the brief, it won't be in the content. Include the extractable answer, required schema, and FAQ questions in every brief
- Brief is 5 pages long → Briefs should be scannable. Use the template with short, specific field values. If the brief takes 30 minutes to read, it needs editing
- Writer has to guess the H2 structure → Prescribe every H2. The strategist controls structure; the writer fills content. When writers choose structure, every piece is structured differently