How to brief a B2B copywriter so the first draft actually works

A brief is not a document. It is a decision. Every line in a brief moves the writer toward one specific draft and away from a hundred plausible alternatives. When the brief is vague, the writer has to guess. When the writer guesses, the founder gets a draft that "isn't quite right" — and the second round becomes a rewrite, not a polish.

We have seen the same three gaps wreck briefs at companies ranging from a Series A SaaS to a four-person services firm. Close those gaps and the first draft tends to land.

Gap 1: who, exactly, is the reader

"VPs of engineering" is not an audience. "VPs of engineering at 100-to-500-person fintech companies who have already deployed an internal developer platform but are now stuck on cost attribution" is an audience.

The first version is a job title. The second is a person with a problem. A copywriter can write to the second version because there is something specific to push against — a status quo, a half-finished project, a known frustration. The first version forces the writer to invent the reader, and invented readers produce generic copy.

When we ask a new client for the reader, we look for three concrete signals:

• Where they are in their journey. Are they evaluating? Implementing? Stuck after rollout? Each maps to different angles.
• What they have already tried. "We use Notion for docs but it falls apart at 50 people" is a useful artifact. The next post lives in the gap that observation created.
• The internal vocabulary. Do they call it "platform engineering" or "DevX"? "Customer success" or "post-sales"? The wrong term in the first paragraph is a tell that you do not work in their world.

You do not need a 40-page persona doc. Three or four sentences will do, as long as they describe a real person at a real company.

Gap 2: what the reader is supposed to do next

A blog post can do many things. It can rank for a keyword. It can move a prospect from "I read your post" to "I joined your newsletter." It can drive a free-trial signup. It can earn a backlink from a peer publication. It cannot do all of those at once.

The brief should name one outcome. We write the outcome at the top of every Contyra brief and refer back to it whenever we make a structural decision. If the outcome is "rank for postgres connection pooling," the structural decisions favor depth, technical specificity, and on-page SEO conventions. If the outcome is "convert engineers reading the docs to demo-bookers," the structure favors a short opening, a concrete failure mode, and a single CTA at the right moment.

Two outcomes is the upper bound. Three means the brief does not have a goal, it has a wishlist.

Gap 3: the proof you already have

The single largest difference between a Contyra draft and a generic AI draft is that ours contains things only your team could know.

Founders consistently underestimate how much usable proof they already own. They think proof means published case studies and named customers. In practice, proof is anything specific:

• A line from a sales call that captured a buyer's actual fear
• The graph you sent investors that shows churn dropped after a feature shipped
• A support ticket from a customer that maps exactly to the problem you are now writing about
• The internal Slack message where your CEO described what the company is doing in plain English

A brief that says "feel free to use customer examples" produces a draft with placeholder examples. A brief that says "here is a 90-second clip of our biggest customer describing why they switched to us — please use a transcribed quote in section three" produces a draft you can sign your name to.

If you do not yet have any proof artifacts to share, that is itself a useful signal. The first piece of work probably should not be a blog post. It should be a customer interview, an internal review of last quarter's lost-deal notes, or a sales transcript. Real copy needs real material to stand on.

What a complete brief looks like

The brief we use at Contyra fits on one page. It has six fields:

1. Reader — a four-sentence description of the actual person we are writing to.
2. Outcome — one or two business outcomes the piece is responsible for, in order.
3. Length and format — word count range, structural conventions, whether it lives on a blog, a sales page, or an email.
4. Proof inventory — three to seven specific artifacts the writer can quote, paraphrase, or build sections around.
5. Voice constraints — what we do not say, and how we are not allowed to sound. ("Never call ourselves a 'leader.' Never use the phrase 'in today's fast-paced world.'")
6. Deadline and approval — when the draft is due and who has the final yes.

When we ask a client to fill that out, the brief is usually faster to write than the draft would have been to revise after a bad first version.

The brief is the work

A writer's job in a B2B engagement is not to invent your positioning. It is to compress it into language that a buyer can act on. The brief is where the founder hands over enough material that compression is possible.

If you cannot describe your reader in four sentences, name a single outcome, and list five proof artifacts, the copy is not the bottleneck. The thinking behind the copy is.

That is the cheap, unsexy answer most copy advice avoids — and the one that decides whether the first draft works.