How to Write a B2B Positioning Document: The Template PMMs Actually Use

Most B2B companies do not have a positioning document. They have a deck.

It lives in a folder somewhere. It has slides about "our vision," a two-by-two with competitors mapped in ways that conveniently put the company in the top right, and a hero statement written in a week before the last rebrand.

Nobody reads it. Nobody uses it. And nobody has the heart to say it is useless.

A real positioning document is different. It is the infrastructure underneath every piece of marketing and sales content your company produces. When it is right, everything downstream gets easier: the messaging framework, the sales talk track, the campaign brief, the landing page copy. When it is wrong, you feel it everywhere, in the deals you keep losing, in the sales rep who freelances their pitch because the official messaging does not hold up in a real conversation.

This post gives you the complete template, how to write each section, how to validate it before it goes live, and how to keep it alive.

---

Why Most Positioning Documents Fail

Before the template, the diagnosis.

Positioning documents fail for three reasons.

They are written inside-out. The team starts with what the product does, then works backward to find a customer problem it solves. This produces positioning that is accurate but unmoved by what buyers actually care about. The antidote is voice-of-customer research before you write a single word. What language do your best customers use to describe the problem you solve? That language should be in the document.

They are written for consensus, not for truth. Positioning requires a point of view. It means claiming some things are true and others are not. Most positioning documents try to include every stakeholder's pet message and end up standing for nothing. A VP of Sales wants a message that works for every deal. A VP of Product wants language that reflects the roadmap, not just current functionality. Legal wants everything hedged. The result is positioning that is safe and forgettable.

They are finished once. Markets move. Competitors ship new features. Buyer language evolves. A positioning document that is not updated becomes the marketing equivalent of a 2019 business plan: technically a document, practically useless.

If you recognize your company in any of these patterns, this guide is for you.

---

The Six-Component Positioning Document

A B2B positioning document has six sections. Each one does a specific job. Together, they answer the question every buyer is asking before they get on your demo: "Is this actually for me, and does it actually work?"

Section 1: The Problem Statement

Start here, not with the product.

The problem statement describes the specific pain your target customer is experiencing. Not the category of pain. The specific version of it, in the language buyers use.

Weak: "GTM teams struggle to align product, marketing, and sales."

Strong: "Series B SaaS companies lose an average of four months of productive selling time every year to GTM misalignment. Messaging created by marketing is ignored by sales. Positioning approved by the exec team collapses in the first three minutes of a demo. The cost shows up in win rates, not in any meeting."

The difference is specificity and buyer language. The strong version sounds like something a VP of Marketing would say to a peer over coffee, not like something someone wrote in a conference room.

Where does this language come from? Win/loss interviews. Customer calls. The exact phrases your buyers use when they describe the problem they hired you to solve. If your problem statement does not sound like something your customer said, rewrite it.

Section 2: The Target Customer

Be precise. Not "enterprise B2B SaaS companies." Not "marketing teams."

Name the role, the company stage, the problem context, and the trigger event that makes them ready to buy.

A useful format:

Primary buyer: Who signs the contract and cares most about the outcome. Champion: Who lives with the problem daily and drives internal advocacy. Company profile: Size, stage, industry, or structural characteristics that predict fit. Trigger event: What changes in their world that makes solving this problem urgent now.

The trigger event is the most underused element. Most positioning documents describe who buyers are. Fewer describe what happens to make them buyers. A company that has been living with a problem for three years is not in market. A company where the CFO just asked for pipeline predictability numbers in a board meeting is. Understanding the trigger sharpens everything downstream: the content strategy, the outbound targeting, the ad copy.

Section 3: The Market Frame of Reference

This section answers the question: what is this, and what would buyers compare it to?

This is the category claim. It is also the most strategically consequential decision in positioning.

Claim the wrong category and you lose to alternatives that are not actually your competition. Define it too narrowly and you miss buyers who did not know your solution existed. Define it too broadly and your differentiation disappears.

Two questions to work through:

What category does the buyer place you in when they first encounter you? This is not your ideal answer. It is the factual answer based on how you are described on your website today, in analyst reports, and in how sales introduces the product in the first call.

What category should they place you in, given what you actually help them do? This is the opportunity. If there is a gap between the first and second answer, you have a positioning problem to solve.

Document the answer to both. Then explain what you are doing to close the gap.

Section 4: The Differentiated Claims

This is the hardest section to write well.

Differentiation is not "we are better." It is "we do something specific that the alternatives cannot replicate without changing what they are."

For each differentiated claim, write:

1. The claim itself (one sentence, plain language)
2. Why the alternative cannot easily replicate it (the structural reason, not the marketing reason)
3. The proof point that substantiates it

The claim needs to meet three tests. Is it true? Is it relevant to the target buyer? Is it defensible against the alternatives they are actually considering?

The relevance test eliminates most first drafts. Companies claim differentiators that are true and not interesting to the buyer. "We have 99.99% uptime." Great. So does everyone the buyer is considering. "We are the only vendor that integrates with the three systems your RevOps team already runs, without a custom API build" is a differentiated claim. It is specific, it is relevant to a buyer who has already invested in a tech stack, and it is not easily replicated without significant engineering work.

Aim for three to five differentiated claims. If you have more than five, you do not have differentiation. You have a feature list.

Section 5: The Proof Points

Every claim needs evidence. This section pairs evidence to each differentiated claim.

Proof points fall into four categories:

Customer outcomes. Specific, measurable results from named or anonymized customers. "Customers reduce RFP evaluation time by 50% in the first 90 days." Numbers with context.

Third-party validation. Analyst recognition, award placements, independent reviews. "G2 Leader for three consecutive quarters in the enterprise segment" carries weight that self-reported claims do not.

Technical substantiation. Architecture decisions, certifications, audit results. Useful when the differentiation is a capability claim.

Social proof at scale. "Trusted by 1,200 enterprise teams in 40 countries." Volume signals risk reduction for conservative buyers.

The mistake is having proof points that are not connected to a specific claim. A generic "customers love us" section is not useful. A proof point that directly corroborates "our implementation takes three weeks, not six months" is doing work.

Section 6: The Key Message

One sentence. The thesis statement of the whole document.

This is what you want a buyer to remember if they forget everything else. It should be the answer to the question "what does this company actually do?"

It is not a tagline. It is not a value proposition statement in the traditional sense. It is the clearest possible articulation of the specific value you create for a specific type of buyer.

Test it by reading it to someone who does not know your product and asking: "What did you hear?" If their answer matches what you intended, you have it. If they look confused or use different words to describe what they understood, rewrite it.

---

The Validation Process

Do not publish a positioning document without running it through these four checkpoints.

Checkpoint 1: The sales rep test. Read the document to two or three of your best sales reps. Ask them: does this match how you pitch? Where does it break down? What do buyers push back on that this does not address? The reps who live in deals will find the gaps that internal reviewers miss.

Checkpoint 2: The customer mirror test. Send the key message and problem statement to two or three customers you have strong relationships with. Ask them: does this sound like how you would describe the problem you hired us to solve? Where is it off? The best customers are the best editors.

Checkpoint 3: The competitive check. Run each differentiated claim through your competitive intelligence. Can the competitor make the same claim with equal credibility? If yes, it is not a differentiated claim. It is a table-stakes claim. Remove it from the differentiation section. You can keep table-stakes claims as proof points in other sections, but they should not be presented as the reason to choose you.

Checkpoint 4: The executive alignment session. Present the final draft to your CEO, head of sales, and head of product in the same room or the same meeting. Disagreements that surface here are better resolved before the document goes live than after sales starts ignoring it. This is not a consensus-seeking exercise. You are presenting a recommendation backed by research. The goal is to surface fundamental objections, not to make everyone happy.

---

How to Keep It Alive

A positioning document that is only updated when someone complains about it is not a working artifact. It is a filing cabinet.

Build a maintenance system into the document itself.

At the bottom of every positioning document, include:

Last reviewed: Date and reviewers. Next review date: No more than one quarter out. Known risks: What could invalidate a claim in the next quarter. A competitor announcement. A product release. A shift in buyer priorities. Version history: What changed and why.

The known risks section is the most important. It forces the positioning team to think adversarially. If a competitor ships the feature you are claiming as differentiation, you need a new claim before they announce it at their next event. The known risks section is where that scenario lives until it resolves.

Review it quarterly. Update it immediately when something material changes.

---

Common Mistakes to Avoid

Writing around the controversial claim. Most positioning documents hedge the parts that matter most. The differentiated claim that will make a competitor uncomfortable is the one most worth making explicit. If your positioning does not say anything your competition would dispute, it is not positioning. It is a description.

Confusing positioning with messaging. Positioning is the strategic foundation. Messaging is the words on top of it. A positioning document should explain the logic and the evidence. A messaging framework translates that into specific language for specific audiences and channels. Do not put taglines and ad copy in a positioning document.

Skipping the problem statement. Most positioning documents start with the product. They describe what it does and who it is for, without establishing the urgency of the problem it solves. The problem statement is what makes the rest of the document matter. Without it, the differentiated claims are features without stakes.

Listing every differentiator. If you have twelve differentiated claims, you have zero. Prioritization is positioning. Pick the three to five claims that are most true, most relevant to the buyer, and most defensible against alternatives. The others belong in your competitive intelligence database, not your positioning document.

Never updating it. A positioning document written before your last major competitive shift is actively misleading your sales team. Build the review cadence into the document itself. Make the update process a calendar event, not a reaction to a crisis.

---

The Template, Condensed

Use this as your starting structure.

Problem Statement: [What the buyer is experiencing, in their language, with specifics]

Target Customer:

• Primary buyer: [Role, company stage, trigger event]
• Champion: [Role, daily pain point]
• Company profile: [Size, stage, structural characteristics]
• Trigger event: [What changes to make this urgent]

Market Frame of Reference: [The category you occupy today, and the category you are claiming]

Differentiated Claims:

1. [Claim] / [Why alternatives cannot replicate it] / [Proof point]
2. [Claim] / [Why alternatives cannot replicate it] / [Proof point]
3. [Claim] / [Why alternatives cannot replicate it] / [Proof point]

Proof Points by Type:

• Customer outcomes: [Specific results, with numbers]
• Third-party validation: [Analyst, awards, review sites]
• Technical substantiation: [Architecture, certifications, audits]
• Social proof: [Scale, logos, industries]

Key Message: [One sentence. The thesis. What a buyer remembers if they forget everything else.]

---

Positioning Is Infrastructure

Every other PMM deliverable is downstream of the positioning document. The messaging framework, the sales pitch, the campaign brief, the landing page, the battlecard. If positioning is wrong, everything built on top of it is slightly wrong in the same direction.

Most PMMs know this. Most companies still treat positioning as a one-time project, not as the ongoing operating system for how they communicate.

The companies that win on positioning treat it as infrastructure. They invest in it before a launch, not after a loss. They update it when the competitive landscape shifts, not when sales starts freelancing. They validate it with real buyers, not just internal stakeholders.

One page. Six sections. Quarterly review. That is the difference between a document that sits in a folder and infrastructure that wins deals.

If you are building this for the first time or rebuilding it after a period of positioning drift, the positioning workshop framework is a good companion to this guide. It covers the facilitation process for getting the right voices in the room before you write a word.

And if you want to understand the most common structural mistakes that cause positioning to fail under competitive pressure, this deep dive on why B2B positioning fails addresses the patterns that show up in almost every repositioning engagement.

The template is straightforward. The discipline to use it consistently is where most companies fall short.

---

Before You Write the Document

If you're building a positioning document for the first time, start with the audit. Five diagnostic questions that identify exactly which element of your positioning is broken before you invest time writing a document that locks in the wrong answer.

Download the Free Positioning Audit — the starting point for any positioning document worth building.

---

For a complete overview of B2B SaaS positioning strategy, including frameworks, common failure patterns, and how positioning connects to messaging, ICP, and GTM, see the B2B SaaS Positioning Guide.