How to write a B2B positioning document: the template PMMs actually use

Most positioning documents are an explanation of benefits.

The envelope shows up five weeks after the appointment. Procedure codes, allowed amount, plan paid, applied to deductible. Every line on that page is accurate.

You still can't tell what happened to you or what you owe. Near the bottom it says this is not a bill.

That's the deck sitting in a shared drive at most B2B companies. A two-by-two that somehow puts us in the top right, and a hero statement written the week before the last rebrand.

Nobody reads it. Nobody uses it. Nobody has the heart to say so.

It matters because everything customer-facing sits downstream of it. When the positioning is wrong, the landing page and the talk track and the campaign brief are all wrong in the same direction, and we feel it in the rep who freelances a pitch because the approved language collapses three minutes into a demo.

---

Written to be approved

Two habits produce the unusable version.

We write from the inside out. The document starts with what the product does, then reverse-engineers a customer problem it happens to solve. Accurate, and unmoved by anything a buyer has ever said out loud.

We also write for consensus. Sales wants language that works in every deal. Legal wants the whole thing hedged.

Positioning means claiming that some things are true and others aren't. A draft that cleared review without an argument usually didn't claim anything.

---

The crown quote

The dentist doesn't hand you the chart.

She says there's a crack under the old filling, that the tooth will split the next time you bite something hard, that a crown runs about fourteen hundred dollars and the plan covers half, and that waiting turns it into a root canal.

Four sentences. You book it on the way out.

Call that the crown quote. The problem in the patient's own words, what happens if they wait, what it costs, and why this option instead of the cheaper one.

A positioning document works when someone can read it back that way. Most can't, because they were built to survive an internal review rather than to be used in front of a buyer.

---

The parts of the page

Six sections. Each does a job none of the others can.

The problem, in their words

Start here. The product comes later.

Category-level pain doesn't count. "GTM teams struggle to align product, marketing, and sales" describes a conference track, not a person having a bad quarter.

The version that works sounds like a VP of marketing talking to a peer over coffee. Months of selling time lost to messaging sales quietly ignored, and a win rate nobody has traced back to it.

That language comes from win/loss interviews and recorded customer calls. If the problem statement doesn't sound like something a customer actually said, we wrote it ourselves.

Who, and what just changed

"Enterprise B2B SaaS companies" isn't a target customer. "Marketing teams" is worse.

Name the buyer who signs, the champion who lives with the problem daily, the company profile that predicts fit, and the trigger event.

The trigger is the underused one. Most documents describe who buyers are, and far fewer describe what happened to make them buyers.

A company that has lived with this problem for three years isn't in market. A company whose CFO asked for pipeline predictability numbers in last week's board meeting is.

The frame of reference

What is this, and what will buyers compare it to?

There's the category a buyer files us under today, based on the website, the analyst write-ups, and how sales opens the first call. And there's the category they'd file us under if they understood what we actually help them do.

Write down both. Then write what we're doing to close the distance.

Claim a category too narrow and the buyers who needed us never look. Too broad and the differentiation dissolves into a crowded shelf.

Claims that survive contact

The hardest page to write.

Differentiation means we do something the alternatives can't copy without becoming a different company. "We're better" doesn't qualify.

For each claim, write the claim in one plain sentence, the structural reason a competitor can't easily match it, and the proof that it's true.

Then run the relevance test, which kills most first drafts. "We have 99.99% uptime" is true and boring, because everyone on the shortlist says it. "We're the only vendor that connects to the three systems your ops team already runs without a custom API build" is specific, relevant to someone who has already spent money on a stack, and expensive to copy.

Three to five claims, not twelve. Twelve is a feature list wearing a suit.

Proof with a job

Customer outcomes carry the most weight. A named result with a timeframe attached beats any adjective we could write.

Analyst placements, certifications, and audit results back the claims a customer story can't reach.

The mistake is proof that floats. A "customers love us" section does no work. Every proof point should be sitting directly under a claim, answering the question a buyer is too polite to ask.

The sentence that travels

One sentence. The thing a buyer repeats to a colleague after we've left the room.

A tagline is a different artifact and belongs somewhere else.

Test it by reading it to someone who doesn't know the product and asking what they heard. If they hand back different words for the same idea, we have it. If they hesitate, we don't.

---

Reading it back

Read the draft to two reps who close. They find in ten minutes what an internal review misses in a month, because they're the ones standing in front of the objection.

Send the problem statement to two customers who like us. Ask whether it sounds like how they'd describe what they hired us to fix. The best customers are the best editors.

Run every differentiated claim past a competitor's website. If they can say the same thing with equal credibility, it's table stakes, and it moves out of the differentiation section.

Then put the CEO, the head of sales, and the head of product in one room with the draft. Disagreement in that room is cheap. Disagreement that surfaces later, when sales has quietly stopped using the document, is not.

---

The fields at the bottom

A document nobody maintains is a filing cabinet.

Four lines keep it alive. Last reviewed and by whom, next review no more than a quarter out, known risks, and version history with what changed and why.

Known risks earns its space. It forces us to think adversarially, so that when a competitor ships the capability we've been claiming as differentiation, the next claim is already written instead of scrambled together the morning of their launch.

---

Six sections, one page, read again every quarter.

Nobody ever kept an explanation of benefits.

---

What to do next

If the document exists and nobody uses it, the problem sits upstream of the writing. Start with the audit. Five diagnostic questions that find which element is broken before we lock in the wrong answer.

Download the Free Positioning Audit. The first conversation after it is free.

If you're building this for the first time, the positioning workshop framework covers how to get the right voices in the room before anyone writes a word. And this deep dive on why B2B positioning fails covers the structural patterns that show up when positioning cracks under competitive pressure.

For the wider picture, including how positioning connects to messaging, ICP, and GTM, see the B2B SaaS Positioning Guide.

---