How to write a positioning statement your sales team will use

How do you write a positioning statement your sales team will actually use?

Write it from the sales conversation backward. Start with the alternative a buyer would choose if you did not exist, name what you do that the alternative cannot, and say why that matters to a specific kind of customer. Then test it in real calls. If reps paraphrase it naturally, it works. If they skip it, rewrite it.

Most positioning statements fail for a boring reason. They are written for a slide, not for a conversation. They sound good in a strategy offsite and fall apart the first time a prospect asks, "So how is this different from what I already use?"

I care about this because positioning sits upstream of everything I build for B2B SaaS teams. The homepage, the outbound sequences, the comparison pages, and the lead scoring rules all depend on a clear answer to who this is for and why it wins. When positioning is fuzzy, every downstream system inherits the fuzz.

What is a positioning statement, and what is it not?

A positioning statement is an internal sentence or short paragraph that defines who your product is for, what it replaces, and why it wins for that buyer. It is not a tagline, not a mission statement, and not homepage copy. It is the source those things are written from, and it should be specific enough to exclude people.

The classic template comes from Geoffrey Moore's book Crossing the Chasm. It runs roughly: for a target customer who has a specific need, the product is a category that delivers a key benefit, and unlike the main alternative, it offers a clear difference. Many teams still use some version of it.

The template is fine. The problem is how teams fill it in. They write "for growing businesses" instead of a real segment. They write "unlike legacy solutions" instead of naming what buyers actually use today. A statement filled with safe words gives sales nothing to say.

Why do most positioning statements never reach a sales call?

They never reach a sales call because sales was not part of writing them. Marketing drafts the statement alone, optimizes it for elegance, and hands it over. Reps then ignore it because it does not match the objections they hear every day. A statement that ignores real objections is a statement reps will route around.

Another reason is length. Reps need a version they can say out loud in fifteen seconds. If the positioning only exists as a dense paragraph in a doc, it will not survive contact with a live call.

The third reason is vagueness about competition. Buyers always compare you to something, even if that something is a spreadsheet. If the positioning does not name the comparison, every rep invents their own, and the story drifts from call to call.

What should go into the statement first?

Start with competitive alternatives, not your features. April Dunford, whose positioning framework many SaaS teams use, lists competitive alternatives first among her five components. Her guiding question is what a customer would do if your offering did not exist. Often the honest answer is a spreadsheet, a manual process, or doing nothing.

Dunford's five components are competitive alternatives, differentiated features or capabilities, value for customers, target customer segmentation, and market category. The order matters. Each step depends on the one before it. You cannot know what is differentiated until you know what you are being compared with.

Starting with alternatives changes the tone of the whole statement. Instead of "the leading platform for X," you end up with something like "teams that run X in spreadsheets switch to this product when the sheet breaks at a certain size." That second version gives a rep a story, a trigger, and a reason to call.

How do you make the statement specific enough to use?

Make it specific by naming real things: the actual tools or habits buyers use today, the job titles that feel the pain, and the moment the pain becomes urgent. If a sentence would fit any competitor's website, it is not positioning yet. Specific statements feel slightly risky, because they leave buyers out. That is the point.

A simple test helps. Read the statement aloud and ask: could a rival paste this onto their site unchanged? If yes, you have described the category, not your place in it. Keep cutting until the statement could only belong to you.

Another test: does it name a trigger? A good statement hints at when someone should buy. "When your second sales rep starts" or "when your SOC 2 audit is three months away" is the kind of detail that turns positioning into pipeline, because outbound and content can be aimed at that moment.

I made a related argument about homepage copy in what makes a SaaS homepage headline specific. The same discipline applies here, one level upstream.

How should sales help write it?

Sales should supply the raw material, not just review the draft. Ask reps for the three objections they hear most, the alternative prospects mention most, and the phrase customers use when they finally say yes. Build the statement from those answers. Then let reps rewrite it in their own words and keep what they keep.

Call recordings are the best source if you have them. Listen for the moment a prospect explains why they took the meeting. That sentence, in the buyer's own words, is often better positioning than anything a team writes from scratch.

I also like to run one short session where marketing and sales argue about the target customer. The disagreement is useful. It usually shows that the company is quietly selling to two different segments with two different reasons to buy, which is worth knowing before writing anything.

Positioning also shapes the first call itself. I covered what that conversation should accomplish in what a first sales call should establish.

How do you test whether the positioning works?

Test it in live conversations for two to four weeks, then look at what changed. Do prospects nod faster? Do fewer calls stall on "how are you different?" Do reps repeat the core idea without reading it? Those signals matter more than whether the leadership team likes the wording.

You can also test it in writing. Put the core claim into a short outbound sequence to the exact segment it names. If replies mention the problem you described, the positioning is landing. If replies are confused or generic, the statement is still too broad.

Keep a simple log of reactions during the test period. A few lines per call is enough. Patterns appear quickly when you write them down, and they give you something concrete to bring to the next revision.

How often should you revisit positioning?

Revisit positioning when something real changes: a new competitor wins deals against you, your best customers shift to a new segment, or the product gains a capability that changes what you replace. Otherwise, leave it alone for a while. Rewriting positioning every quarter confuses reps and resets everything built on it.

A light review every six months is a reasonable rhythm for most early-stage SaaS teams. Ask sales whether the alternatives buyers mention have changed. If they have, the positioning probably needs to move too.

Bigger changes, like moving from one category to another, deserve more care. I wrote about that decision in whether to create a category or enter one, because it is a positioning choice with long consequences.

What should you do next?

Book thirty minutes with your top two reps. Ask what buyers use today instead of you, which objections come up most, and what customers say when they finally buy. Draft a positioning statement from those answers, starting with the alternative. Then have reps say it out loud and keep only what they naturally repeat.

Once the statement holds up in calls, use it as the source for your homepage headline, your outbound first lines, and your comparison pages. Everything downstream gets easier when the source is clear.

If you want help turning positioning into a homepage, outbound sequences, and the systems that run them, let's chat. This is the part of go-to-market I enjoy most, and I am happy to look at where you are and tell you honestly what I would change.