← Blog
Posts

A content brief should start with a question a prospect asked

Six fields to copy into a doc, all pulled from a recorded sales call, plus the rule for which questions earn a post.

13 Nov 2026 · 6 min read

For about a decade, we saw the content brief as a keyword, a target word count and a list of headings lifted from whatever ranked on page one. We saw agencies sell briefs in that format by the thousand, and the posts that came back sounded like they were assembled from them.. A writer handed a keyword can only produce the average of everything already published under it. We think a brief should open somewhere else, with a question a prospect asked on a sales call, quoted word for word from the transcript. If you came here for a template to fill in, it sits further down, and we explain each of its six lines in the sections above it.

Open with the question in the buyer's words

We think the prospect's exact wording carries more than the topic does. When a prospect asked a question out loud, they also told the rep what they were afraid of, what they had assumed and roughly which words they would type into a search box later that night. Tidy that into a three-word topic and all of it disappears. So the first field is a quote, copied from your recording with the buyer's grammar, hedges and half-finished clauses left in. Resist the urge to turn it into a headline at this stage. You can write the headline later, and it comes out better when the original question sits at the top of the page.

Then the answer the rep gave

On the call, someone answered. That answer became the version of the truth the buyer carried out of the meeting, and the post has to agree with it or say plainly why it changed. The second field is the rep's answer, pasted from the transcript in full, including the parts that wandered. Writers tend to skip this step, and then the post contradicts the sales team in public. We built Propaganda on the view that a company's site, deck and calls drift apart, and much of that drift started in a moment like this one, when a rep improvised and nobody wrote it down. A writer who has read the rep's answer knows what the buyer already heard. The post can start one step further along.

Mark the part the rep fumbled

Easy questions rarely get fumbled. The fumble showed where the company's thinking ran out: a pause, a "let me check on that", an answer that circled twice and landed somewhere vague. The third field names that exact part, with the timestamp if the transcript has one. We have said before that a fumbled answer on a sales call is a blog post nobody has written yet, and this field is where that post starts. The writer's job is to answer the fumbled part better than the rep managed with a buyer waiting on the other end. Often that means finding the fact the rep didn't have, or finishing the argument the rep half-remembered. When the rep answered everything cleanly, the brief is weaker for it, and the post risks repeating what the call already did well.

Say where the deal stood

The deal stage shows the writer who will read the post. A prospect comparing tools wanted something different from one trying to get a purchase signed off, even when both asked the same question. The comparer was scanning for differences, for the places a product fits worse, and for a reason to keep it on the shortlist. The person chasing sign-off needed the price, the exit terms, the risk and a paragraph they could forward to whoever holds the budget without rewriting it. Write the stage in one line, using the names your sales team already uses, and add a sentence on what had been decided before the question came up. A writer who knows the stage writes for one reader. Without it, you get a post written for both readers that bores each of them.

Count the calls it came up on

The fifth field is a number, and it settles whether a question gets written up at all. When a question comes up on more than one call, it earns a brief. If one prospect asked it once, it goes on a list for later and stays there until somebody else asks it too. We hold this line for a dull reason, because a single buyer's question might be a quirk of their company, their market or their mood that afternoon, and a post written for it reaches an audience of one person who has already bought or left. Once a second prospect asks the same thing, though, the repetition is the evidence that the next buyer will ask it as well. Counting keeps volume honest too. Our product caps proposed posts relative to what a company published the quarter before, so counting calls is the cheapest way to enforce the same discipline by hand.

List every fact and where it came from

The sixth field lists each company fact the post will state, with its source beside it: the pricing page, the changelog, a line the founder said on a named internal call. Prices, plan names, integrations, what has shipped and what is still planned all go here. A human writer missing a price will usually stop and ask. An AI tool tends to keep going. Language models fill gaps with whatever sounds plausible, and when we have left a price out, we have seen ChatGPT supply one that looks right and isn't.. If you hand briefs to an AI tool, treat this as the field that matters most. Our own entry would name the plan, the price, and the page where it is published, and a writer with that line has nothing left to guess. We keep a company's facts as hundreds of short claims, each with its source and quote, for the same reason.

The template to copy

Six fields, short enough to paste into a doc:

  1. The question (quoted from the transcript):

  2. The answer the rep gave (pasted in full):

  3. The part the rep fumbled (with timestamp):

  4. Deal stage when it was asked:

  5. Number of calls it came up on:

  6. Company facts the post will state, each with its source:

Fill them in that order when you review a recording. The first three come straight from the transcript, and the last three take a few minutes of checking. If field five shows a one, stop there and file the question.

One brief laid out the way Pitches does it

Propaganda's Pitches module, which is in beta, lays out every idea as an angle, an audience, an outline, sources and a reason. That shape fits a call-based brief, with the six fields feeding it. We meant to fill this one in from a real call question, and we don't have one we can print yet, so below we list what belongs in each slot.

  • The question is the prospect's words, quoted from the transcript.

  • What the buyer heard is the rep's answer, in full.

  • The fumbled part is the sentence where the answer went vague, with its timestamp.

  • Stage and count is whether the call compared tools or sought sign-off, and how many calls it came up on.

  • The angle is the one claim the post makes that the rep couldn't make on the call.

  • The audience is the buyer at that stage, described by the decision in front of them.

  • The outline answers the fumbled part first, then the rest of the question, in the order a buyer would ask the follow-ups.

  • Sources list each company fact with where it came from, plus any outside research the argument leans on.

  • The reason is the goal this post moves.

The reason line is the one founders skip, and we think it earns its place. No reason, no pitch. A post with no goal behind it is a hobby, and hobbies belong on weekends.

Keep the question and drop who asked it

So you keep the question in the brief and drop the person who asked it. Names, companies, budgets and the vendor the prospect was leaving stay out of the brief, since leaving them out there is the surest way to keep them out of the post. That is one of the house rules under every voice we write in, and it is also plain manners. When a prospect mentioned a budget, they told one rep, in confidence, so they could get a straight answer. Long after the deal closed or died, you still owe them that confidence. The question itself, though, belongs to every buyer who will ask it next, and those buyers are who the post was written for all along.