How to Write a Positioning Statement That Sales Uses

PMMs write positioning statements. Sales ignores them.

This is the most common failure in B2B SaaS product marketing. A positioning statement gets workshopped for three weeks, blessed by the executive team, and published to Confluence. Six months later, you sit in a demo and watch a rep pitch the product using completely different language — their own instinct, their own framing, their own angle. The positioning statement never made it out of the document.

There are two reasons this happens. First, most positioning statements are written for internal alignment, not external use. They read like strategy documents rather than sales frameworks. Second, they are written at a level of abstraction that a rep cannot translate under pressure in a live call.

A positioning statement that sales actually uses is one they can turn into a sentence under fire. It answers the buyer's question — "why you?" — in terms the buyer recognises as their own problem, not your product category. This guide shows you how to write one.

The Purpose of a Positioning Statement

A positioning statement is not your pitch. It is the strategic foundation that your pitch is built on. It defines:

• Which buyers you are for (and implicitly, who you are not for)
• What problem you solve, described in buyer language
• What alternative they are currently using and why it is not good enough
• What you do that the alternative cannot
• Why buyers should believe that claim

When these five elements are clear, every piece of downstream content — website copy, pitch decks, email sequences, battlecards — becomes easier to write and more consistent. When they are unclear, every team re-invents the story from their own perspective, and the buyer sees a different version of you in every interaction.

The Positioning Statement Formula

There are several positioning statement formats. The most useful for B2B SaaS comes from April Dunford's work on positioning, adapted for practitioner use:

For [specifically defined buyer], who [specific problem or trigger], [product name] is a [category frame] that [specific capability]. Unlike [named alternative], we [specific differentiator], which means [concrete outcome for the buyer].

This is an internal document, not a tagline. It is written in plain language. It is specific enough to be wrong — which is how you know it is specific enough to be useful.

Filling in Each Element

The buyer: be brutally specific

"For B2B SaaS companies" is not a buyer. "For heads of revenue at B2B SaaS companies between 50 and 300 employees, in the first 90 days of a new sales leadership hire" is a buyer.

The specificity matters because it tells sales who to qualify in and who to qualify out. A positioning statement that covers everyone covers no one. Every qualifier you add makes the positioning more useful to the rep — not less.

Common dimensions to specify:

• Company size (employees or revenue range)
• Industry or vertical
• Role or buying committee composition
• Trigger event (funding round, hire, failed project, compliance requirement)
• Stage of awareness (does the buyer already know they have this problem?)

The problem: use their language, not yours

The problem statement should sound like something a buyer would say in a 1:1 with their manager, not a line from your product website.

Too generic: "who struggle with sales efficiency"

Too product-focused: "who lack visibility into their pipeline data"

Right: "who cannot give the CFO a straight answer on which deals will close this quarter"

The difference is specificity and stakes. The right version describes a situation the buyer has experienced and that has a consequence they care about. Pull this language directly from your positioning research interviews — the exact phrases buyers use when describing their problem are your raw material.

The category frame: where you sit in the buyer's mental map

The category frame tells the buyer how to think about you — which drawer to put you in. It is not your product description. It is the reference frame that makes your differentiation legible.

Getting this wrong is expensive. If you position yourself in the wrong category, buyers compare you to the wrong alternatives and your differentiation disappears. A security tool that positions as "compliance software" will be compared to audit platforms. A compliance platform that positions as "risk reduction software" gets compared to insurance. Same product, wildly different competitive context.

Category options to consider:

• Name an existing category you fit within (fastest orientation for the buyer)
• Define a new category that frames the problem in a way existing categories do not (higher upside, much harder to execute)
• Use a functional description that tells the buyer what it does without requiring them to map it to a category they may not know

For most B2B SaaS companies at growth stage, naming a category that already exists in the buyer's head — and then differentiating within it — is the lower-risk choice.

The alternative: name what they are using today

The alternative is not always a competitor. It is whatever the buyer is using right now to manage the problem. This might be:

• A direct competitor ("Unlike Competitor X...")
• A category of tools ("Unlike point solutions that...")
• The status quo ("Unlike managing this in spreadsheets...")
• A manual process ("Unlike coordinating this across email threads...")

Naming the alternative forces honesty in the positioning. If you cannot articulate what you are better than, your differentiation is a claim without a comparison point — which means buyers cannot evaluate it.

The differentiator: what you do that they cannot

The differentiator must be three things simultaneously: real (you actually have this capability), relevant (the buyer cares about it), and defensible (the alternative cannot easily replicate it).

Most positioning statements fail here because the differentiator is one of three things:

• A table stake: "We have a great user interface." Every vendor says this. It is not a differentiator.
• A feature, not an outcome: "We have an AI-powered insights engine." The buyer does not care about the engine. They care about what the engine produces.
• A claim without a proof point: "We have the most accurate data." Says who? Based on what?

A good differentiator is stated as a capability with a measurable or observable outcome: "We are the only tool in this category that shows pipeline risk at the deal level without requiring reps to manually update forecast fields — which means sales leaders have an accurate pipeline view on any given day, not just on the day after a pipeline review."

The proof: why they should believe you

The proof element is sometimes omitted from positioning statements because it is harder to formulate. Include it. It is the difference between a claim and a credible claim.

Proof types for B2B SaaS positioning:

• Customer outcomes: "Our median customer reduces sales cycle length by 18 days in the first quarter" — realistic figure based on actual data
• Technical specifics: "Because we instrument at the API layer, not the UI layer, data capture does not depend on rep behaviour"
• Customer reference: "Companies like [recognisable name in the buyer's vertical] rely on us for..."
• Third-party validation: "Named a Leader in the [relevant] category by [credible analyst]"

A Worked Example

Here is a positioning statement built using this formula for a hypothetical B2B SaaS company selling sales intelligence software:

For heads of revenue at B2B SaaS companies between 100 and 500 employees, who cannot give their board an accurate forecast because pipeline data is out of date within 48 hours of any pipeline review, [Product] is a revenue intelligence platform that automatically captures deal activity and surfaces risk signals at the deal level. Unlike CRM-native tools that require reps to manually update every stage change, we instrument pipeline data at the source — every email, meeting, and document interaction — which means forecast accuracy does not degrade between pipeline reviews. Our customers typically see their pipeline data currency improve from 60% to 95% within the first month of deployment.

This positioning statement is specific enough to be useful and wrong. "60% to 95%" is a claim that can be tested. "Heads of revenue at 100–500 employee companies" is a segment that can be qualified against. "Within 48 hours of any pipeline review" is a trigger that a rep can listen for in discovery. That specificity is what makes it actionable.

Testing Whether Your Positioning Statement Works

A positioning statement is a hypothesis. You test it in three ways:

Test 1: The sales rep read-back test

Give the positioning statement to three sales reps. Ask each one to turn it into a 30-second opening for a discovery call — without looking at the document. If they can do it in a way that sounds natural, the statement is specific and usable. If they struggle or default to their own language, the statement is either too abstract or too complex.

Test 2: The buyer recognition test

Share the problem framing element with five recent customers. Read it to them verbatim: "We hear from a lot of [your ICP] that [your problem statement]. Does that match your experience?" Aim for immediate recognition — "yes, that is exactly it" — from at least four of five. If you are getting "kind of" or "not quite," the problem framing needs refinement.

Test 3: The landing page conversion test

Run the positioning statement's core claim as a hero message on a landing page with paid traffic. Measure demo request or email capture rate against a control. A meaningful uplift (20%+) is signal that the positioning is resonating at scale, not just in conversations.

Common Positioning Statement Mistakes

• Writing for the board, not for sales: A positioning statement that uses strategic language ("we accelerate revenue velocity") is an internal strategy document. A positioning statement that sales can use sounds like something a customer would say.
• Solving for consensus, not clarity: When positioning statements get workshopped by committees, they get softened until nobody objects. Soft positioning is useless positioning. The statement should make some people uncomfortable — the people who think you are wrong about your ICP or your differentiator.
• Changing it every quarter: Positioning consistency creates cumulative brand trust. Changing it too frequently signals internal confusion to buyers and resets the reference frame that sales has learned to use. Validate before you change, and change deliberately.
• Confusing the positioning statement with the messaging: The positioning statement is the internal foundation. The message is what goes on the website, in the pitch deck, in emails. They should be consistent, but they are not the same document. See our positioning vs messaging guide for the distinction.

From Positioning Statement to Enablement

Once the positioning statement is finalised and tested, it becomes the source document for every downstream asset:

• Website hero copy: Translates the problem framing and differentiator into the language of the homepage.
• Pitch deck narrative: The opening problem slide should mirror the problem statement in the positioning document.
• Email sequences: The subject lines and opening hooks reference the trigger event and problem framing.
• Battlecards: The alternative and differentiator elements feed directly into competitive comparison content.
• Qualification criteria: The buyer definition informs the ICP scoring used in sales qualification.

When all these assets trace back to a single positioning statement, messaging becomes consistent across the buyer journey. When they do not, every rep is running a slightly different pitch and buyers get a fragmented experience.

Implementation Checklist

1. Run six to eight positioning research interviews before drafting. Use the problem statement and alternative elements from what buyers say verbatim.
2. Draft the positioning statement. Apply the formula. Keep it to one paragraph.
3. Run the sales rep read-back test. Revise based on what they find hard to translate.
4. Run the buyer recognition test with five recent customers. Revise the problem framing if recognition is less than 80%.
5. Lock the statement for 90 days minimum before reconsidering.
6. Update all downstream assets to align within 30 days of finalising.
7. Review quarterly: has the ICP shifted? Has the competitive landscape changed? Has the category moved? Update only if the answer to one of these is yes with evidence.