How to Write a Positioning Statement (Template + Examples)
Here's how to write a positioning statement.
If your team has spent a meeting arguing over adjectives – “powerful” versus “seamless” versus “intuitive” – you don’t have a positioning problem, you have a missing positioning statement. A positioning statement is a one- or two-sentence internal document that names who your product is for, what market category it competes in, and why it beats the specific competitive alternative that buyer would otherwise pick. It’s not a tagline and it’s not homepage copy – it’s the internal brief that your headline, your sales deck, and your onboarding emails all get written from.
Most teams get two things wrong here. They write something broad enough to describe five competitors, or they write it once in a workshop and never find out whether anyone outside that room agrees with it. This guide covers the format, a fill-in-the-blank template, real examples by company stage, and a concrete way to test whether your positioning statement actually holds up with your target audience – the part most positioning guides skip entirely.
What Is a Positioning Statement?
A positioning statement defines the specific gap your product fills in a buyer’s mind relative to the next-best alternative they’d consider – a named competitor, a manual process, or doing nothing. It’s written for your team, not your customers. Nobody outside the company should ever read the sentence itself; they should just feel its effects in the homepage copy, the sales pitch, and the onboarding flow that get written from it.
It’s easy to confuse this with three other things:
A brand positioning statement covers the whole company’s identity and market role rather than one product’s spot against one alternative – if you’re not sure which one you need, brand positioning vs. product positioning breaks down when each applies.
Market positioning is broader still – it’s where your entire category sits relative to adjacent categories, not where one product sits relative to one alternative; see what market positioning covers if that’s the layer you’re actually working on.
And it’s not an elevator pitch – an elevator pitch is spoken, persuasive, and improvised for the room; a positioning statement is written, internal, and fixed until your team deliberately revisits it.
Positioning Statement vs. Value Proposition: What’s the Difference?
A positioning statement and a value proposition solve different problems, and mixing them up is the most common reason positioning work stalls out in committee. A related term worth untangling here too: a unique selling proposition (USP) is usually just the single differentiating claim, pulled out of the full positioning statement and sharpened into copy – it’s a fragment of the statement, not a replacement for it.
| Element | Positioning Statement | Value Proposition |
|---|---|---|
| Audience | Internal – your team, not the buyer | External – the buyer reads this directly |
| Format | Fixed template (for / who / unlike / because) | Flexible – a headline, a subhead, a pitch line |
| Job it does | Aligns the team on the competitive alternative you’re claiming to beat | Persuades a specific buyer to act on it |
| Where it lives | Brand brief, sales enablement doc, onboarding for new hires | Homepage, ad copy, first slide of a pitch deck |
In practice, the positioning statement comes first, and the value proposition gets drafted from it – often several versions of it, tested against different segments.
If you haven’t nailed down the value prop piece yet on its own, our post on value proposition covers that in more depth.
What’s the Standard Positioning Statement Format?
Most positioning statements you’ll see in the wild trace back to a positioning framework popularized by Geoffrey Moore in Crossing the Chasm, and it’s held up because it forces six decisions you can’t skip:
For [target customer] who [has this need or trigger event], [product name] is a [product category] that [key benefit – the reason to buy]. Unlike [primary competitive alternative], [product name] [the one differentiator you can defend].
Every bracket is a decision, not a slot to fill with adjectives. If you can swap in a competitor’s name and the sentence still reads true, one of those six decisions hasn’t actually been made yet.
Worth knowing before you lean on this too hard: April Dunford, whose book Obviously Awesome is probably the most cited modern text on this exact topic, has argued that a single fill-in-the-blank sentence can lock in your team’s internal assumptions rather than market truth, and that it’s easy to mistake “we wrote the statement” for “we’re done positioning.” Her point isn’t that the template is useless – it’s that the sentence is a compression of a decision-making process, not a substitute for having made the decisions. More from her on this if you want the fuller argument. That critique lines up with the validation step further down: the sentence is only as good as what it’s tested against.
How to Write a Positioning Statement: A Step-by-Step Framework
Step 1: Name the target customer specifically
“Product managers” is a job title with millions of people in it, not a target customer. “Product managers at 20-50 person B2B SaaS companies shipping a feature every two weeks with no dedicated researcher” is a target customer – close enough to a real ideal customer profile (ICP) that a buyer persona could be built from it. Specificity here is what makes every later decision easier.
Step 2: Name the real competitive alternative
This is the step teams skip most often, usually because it feels safer to talk about the whole market than one named alternative. But “unlike doing nothing” and “unlike hiring a research agency” produce completely different sentences – and completely different products. Pick the alternative your actual last five deals were competing against, not a generic stand-in like “traditional solutions.”
Step 3: Pick the market category you want to be judged in
Category shapes buyer expectations before a single feature gets mentioned. Calling yourself “AI research software” invites a different bar than calling yourself “a synthetic user testing platform.” Choose the category where your strengths are the default expectation, not the exception you have to argue for.
Step 4: Name one differentiator you can defend with a fact
Not three. One. If it can’t survive a follow-up question – “how much faster,” “compared to what,” “says who” – it’s a claim, not a differentiator yet. This bar gets higher in regulated categories: a healthcare product’s differentiation claims need to hold up to legal and compliance review, not just a skeptical buyer, so the fact behind the claim matters even more there.
Step 5: Draft it, then cut
Write the full six-part sentence first. Then remove every word that isn’t doing the job of naming the buyer, the category, or the differentiator. Adjectives like “innovative,” “powerful,” and “comprehensive” almost never survive this pass, because they don’t name anything.
Step 6: Test it before you trust it
Covered in detail below – this is the step that turns a positioning statement from a guess the team likes into something you actually know works, and it’s usually where product-market fit signal shows up first, before it shows up in the pipeline numbers.
What’s a Good Positioning Statement Template?
| Field | What it captures | Fill in |
|---|---|---|
| Target customer | Job title, company type, and the trigger that makes this urgent | For [ ] |
| Need or opportunity | The specific problem, not the category of problems | who [ ] |
| Product + category | What you are, in the buyer’s own vocabulary | [Product] is a [ ] |
| Key benefit | The reason to buy, stated as an outcome, not a feature | that [ ] |
| Competitive alternative | The specific thing they’d use instead – name it | Unlike [ ] |
| Differentiator | The one claim you can defend with a fact | [Product] [ ] |
If a single sentence feels too cramped to argue through as a team, expand this into a full positioning canvas first – a worksheet with the same six fields given room to debate, with the compressed sentence written only once the team agrees on each field. Same inputs, more elbow room.
What Do Positioning Statement Examples Look Like at Different Stages?
These are illustrative, made-up companies – the structure is what matters, not the names.
Early-stage SaaS (pre-PMF, small team):
For solo founders validating a new feature before they build it, Pilotly is a lightweight feedback tool that turns a rough idea into a clear build-or-skip signal in a day. Unlike posting in a founder Slack group and hoping for honest answers, Pilotly structures the question so the feedback is comparable across responses.
Mid-market B2B tool (established category, named alternative):
For revenue operations teams at 100-500 person companies losing deals to messy handoffs, Routewell is a lead-routing platform that assigns and escalates leads in under 60 seconds. Unlike the built-in routing rules bundled into most CRMs, Routewell handles multi-territory and multi-product logic without a consultant.
Agency or service business:
For marketing agencies pitching rebrands to clients who don’t trust a single creative opinion, Framecraft is a concept-testing service that shows how target audiences actually react to three directions before the pitch. Unlike presenting concepts on gut feel alone, Framecraft gives the agency a data point to put next to the moodboard.
DTC consumer brand:
For a skincare brand selling direct to consumer, the positioning statement might read: for people with sensitive skin who’ve been burned by “gentle” claims that weren’t, Calmroot is a fragrance-free serum line dermatologist-tested at the exact concentration on the label. Unlike mass-market “sensitive skin” lines, Calmroot publishes the concentration, not just the claim.
Consumer goods and ecommerce brands have their own positioning quirks – retail shelf context, DTC checkout page, marketplace listing – worth its own look if that’s your situation.
Notice none of these lean on adjectives to do the differentiating. Each one names a specific competitive alternative and a claim you could ask “how do you know?” about. For a wider set of examples across formats and industries, see product positioning examples.
How to Know If Your Positioning Statement Actually Works
Here’s the test most guides never give you: write the statement, then find out if it’s true in someone else’s head, not just yours.
Show the positioning statement to eight to ten people who match your target audience. Let them read it once, then take it away. A day later – not immediately, memory under pressure isn’t the point – ask them to describe the product back to you in their own words, without looking at the statement again.
Score the answers against three things: did they name the right market category, did they identify who it’s for, and did they mention the differentiator specifically, rather than a generic “it’s good” or “it’s fast.” If fewer than half the group hits two of the three, the positioning hasn’t landed. The fix is almost never wordsmithing – it’s usually that the differentiator you picked isn’t the one that actually stuck, which sends you back to step four of the framework above, not to the thesaurus.
Rounding up ten people for this the traditional way means scheduling calls and waiting on availability, which is exactly the kind of friction that makes teams skip the test and ship the statement on faith.
Articos runs this same repeat-back test against synthetic personas built from your actual ICP, and it’s one way to get a first directional read in under 30 minutes instead of a week of calendar tetris. AI-run user research covers the full statement, concept testing is the closer fit if you’re validating alongside a broader product idea, and a narrower message test works better if you just want a read on the differentiator line or a homepage headline pulled from it.
None of this replaces real conversations before a high-stakes rebrand or an enterprise repositioning – the nuance of an actual sales call still catches things a synthetic pass won’t.
What Does a Real Positioning Statement Test Actually Show?
We ran this exact process on our own two leading positioning candidates before committing spend to either one: “User research. Simplified.” – the broad-simplicity direction – against a speed-led alternative built around “30 minutes, not 8 weeks.”
Eight synthetic personas, two each across four archetypes chosen to include skeptics, not just people inclined to like us: a pre-seed founder who’d never done research before, a Series B PM with an in-house researcher who distrusts synthetic data on principle, a price-sensitive agency owner who’d already tried UserTesting, and a methodologically rigorous UX designer wary of AI shortcuts.
The interview script itself did the actual repeat-back work: first-click reaction, one-sentence interpretation of what the product does, what raises skepticism, and – the question that mattered most – whether they’d forward it to a teammate and what they’d say when they did.
Neither candidate won outright. The panel trusted specific, scoped claims – “fast, but scoped to one step” read as a believable workflow acceleration – over both the broad simplicity claim and the unqualified speed claim, which read as overpromising once anyone looked past the headline. The single biggest trust signal wasn’t speed or simplicity at all: it was whether a participant could picture forwarding the claim to a boss or client without their name looking attached to something oversold. As one persona put it, they’d default to whichever headline sounded “most bounded and least magical.”
Worth being direct about what this test was and wasn’t. It was a synthetic-panel read, not a human one – eight AI-run interviews across four archetypes, useful for a fast, directional signal on which framing to carry into a smaller round of real conversations, not a replacement for having them. That’s the two-step process from the section above, in practice: synthetic pass first to cut two candidates down to a defensible direction, human round next before locking anything into a launch.
What’s the Cheapest (or Free) Way to Test a Positioning Statement?
You don’t need a paid tool for a first pass. Email the statement to five to eight existing customers or warm prospects and ask them to describe the product back a day later, using the same repeat-back scoring above. Post the differentiator line (not the full statement – it’s an internal doc) in a community where your target audience actually hangs out, framed as a genuine question rather than a pitch, and see what language comes back. Both are free and both are better than no test at all.
The tradeoff is reach and objectivity: five people you already have a relationship with will be kinder to you than a cold audience, and a Slack poll won’t tell you whether a specific stranger in your ICP gets it on first read. Paid panel tools solve for that – Wynter, for instance, is built specifically for B2B message testing against a verified, targeted professional audience rather than whoever happens to see your post. Worth reaching for once the free version has told you the statement is at least directionally solid and you’re deciding whether to build a launch around it.
Should You Combine Synthetic and Human Research, or Just Choose One?
Combine them – pick one over the other only when time or budget genuinely force the choice. Synthetic testing, or a quick free version with people you already know, is the right tool for the fast iteration loop. You’ll likely go through two or three versions of the differentiator before one sticks, and scheduling human interviews for each pass isn’t practical.
Once the statement is passing the repeat-back test consistently, a smaller round of real conversations with actual prospects – not existing customers, who are already sold – is worth the extra time before you commit a launch budget or a rebrand to it. The synthetic pass tells you the statement is coherent; the human pass tells you it survives contact with someone who has no reason to be polite to you.
What Are the Most Common Positioning Statement Mistakes?
- Leading with features instead of the competitive alternative. A list of capabilities doesn’t tell anyone what they’re choosing you over.
- A differentiator that’s actually a category expectation. “Easy to use” isn’t a differentiator in software anymore – it’s table stakes buyers assume by default.
- No named alternative at all. “Unlike traditional solutions” describes nothing. Name the actual thing your last lost deal chose instead.
- Testing only with people who already like you. Existing customers and your own team both have a reason to be generous with a “does this make sense” question. That’s what the human-research step above is for – different people, later in the process.
- Writing it once and treating it as settled. Positioning drifts as the market and the product both move. A statement nobody has re-tested in a year is a guess wearing last year’s confidence.
How to Choose the Right Positioning for Your Product
Start from the competitive alternative your best-fit customers are actually walking away from, not the whole category. Pick the one differentiator you can prove, not the one that sounds the most impressive in a deck. Write the six-part sentence, cut every word that isn’t load-bearing, then hand it to real target customers and see what comes back in their own words before you build a go-to-market plan around it.
