Most positioning statements get written once, saved to a Google Doc, and forgotten. They don't change anything, they don't show up on the homepage, and the sales team doesn't quote them. They exist only because somebody once said the company needed one.
That's a participation trophy, not a positioning statement.
A positioning statement in marketing is supposed to do real work. It's the internal artifact that forces the team to make hard decisions, in writing, in a format anyone can argue about. It isn't a tagline and it doesn't belong on the homepage, because it's the source document everything else translates from.
Below, I'll cover what a positioning statement actually is, how it differs from positioning and from a tagline (three things people constantly mush together), the framework I use, five real examples, and the mistakes that kill positioning statements before they ship.
Three things that get confused
Marketers say "positioning," "positioning statement," and "tagline" like they're synonyms, but they aren't.
Positioning is the strategic claim about who you serve, what category you live in, and why someone should pick you. It's a decision rather than a sentence, and it informs everything from product roadmap to hiring to fundraising.
A positioning statement is the written internal articulation of that decision, in a structured format. It's roughly forty words and never customer-facing, and it exists so the team can stop arguing and start executing.
A tagline is the customer-facing line, three to seven words that sit on a homepage or a billboard. It's the translation of positioning into something a buyer will actually read.
These are different artifacts with different jobs and audiences, so if you confuse them you'll write a tagline when the team needed a positioning statement, or you'll try to put a forty-word positioning statement on a homepage and bury the buyer.
The Geoffrey Moore framework, and what I do with it
The standard template is Geoffrey Moore's, from Crossing the Chasm:
For [target customer] who [statement of need or opportunity], the [product name] is a [product category] that [statement of key benefit (that is, compelling reason to buy)]. Unlike [primary competitive alternative], our product [statement of primary differentiation].
It's been used by thousands of B2B companies and it still works. Most of the criticisms of it are wrong (it's "too rigid", but that's the point, since the rigidity forces decisions).
What I change when I use it with B2B clients:
The "need" line gets sharper. Most teams write a vague pain, so I push for the specific situation that makes a buyer go look for a solution. Instead of "they need better support tools," I'd want something more like "they're getting paged at 3am for noise their on-call rotation hates." Specific situations sell, and vague needs don't.
The "competitive alternative" gets named. Moore's template lets you write "alternative," and teams use that to avoid naming a competitor, but I require a name, meaning the actual product the buyer is comparing you to in a spreadsheet. If you can't name one, you don't know the market well enough to position in it.
The "differentiator" gets one line. Not three, because teams will negotiate three differentiators in to avoid picking. So pick.
The full framework, my version, is in the brand positioning template. The template and the positioning statement are the same artifact written two ways, where the template is the fill-in-the-blank version and the positioning statement is the paragraph that comes out of it.
Five positioning statement examples (with commentary)
Some of these are reverse-engineered from public homepages and sales materials, so they aren't necessarily the exact statements the companies use internally, but they're plausible and they show what a good one looks like.
Example 1: Linear
For product teams at high-growth software companies who are tired of Jira's complexity, Linear is project management software that's purpose-built for shipping product. Unlike Jira, we ship opinionated defaults instead of unlimited configuration, so your team spends time building instead of customizing tickets.
What works here is that the buyer and the competitor are both named, the differentiator is one specific thing (opinionated defaults vs. configuration), and the outcome ("time building instead of customizing tickets") is verifiable in week one of using the product.
Example 2: Stripe (circa 2014)
For developers at internet businesses who need to accept payments but don't want to spend two months integrating a legacy payment processor, Stripe is payments infrastructure designed to be live in an afternoon. Unlike Authorize.net or traditional merchant accounts, we ship clean APIs and documentation built for engineers instead of compliance officers.
What works here is that the buyer is named (developers, not "businesses"), the alternative is specific, and the differentiator is concrete. This was the positioning Stripe rode for its first six years, and most of the company's growth came from this being clear internally.
Example 3: A hypothetical B2B SaaS
For heads of customer support at B2B SaaS companies with 5-50 support agents who are drowning in repetitive tickets, Helpdesk Co is customer support software that auto-resolves 40% of incoming tickets with AI before a human sees them. Unlike Zendesk, we ship the AI workflows pre-built, so you don't need a six-week implementation to see results.
What works here is a tight ICP (segment size, role, situation), a measurable outcome (40%), a named competitor, and a real differentiator (pre-built vs. configurable).
Example 4: A bad one (anonymized real example)
For modern enterprises seeking digital transformation, [Company] is a leading platform that delivers innovative solutions across the customer journey. Unlike traditional providers, we leverage AI to unlock business value.
Every line is a failure mode. "Modern enterprises" names nobody and "Leading platform" is unverifiable, while "Innovative solutions" is the word teams use to avoid saying what the product is. "Traditional providers" doesn't name a competitor, and "Leverage AI to unlock business value" is the sound of a marketing team that hasn't been told what the product does. It's a real example, lightly altered, from a real $40M company.
Example 5: Figma (early days)
For design teams at software companies who are tired of emailing Sketch files back and forth, Figma is design software that lives in the browser. Unlike Sketch, we run multiplayer by default, so your team designs together instead of merging conflicts.
What works here is that the buyer's pain is the specific situation (emailing files), the differentiator is one thing (multiplayer by default), and the implication is clear (Sketch is single-player). This was Figma's positioning for years, and it compounded because the team didn't keep rewriting it.
Positioning strategy in marketing: where the statement fits
A positioning statement is one artifact inside a broader positioning strategy. The strategy has four moving parts:
The decision. This is who you serve, what category you're in, and what claim you make, and the CEO has to own it. See why CEOs are the keepers of positioning.
The statement. This is the internal forty-word artifact, in the Moore-style format, that captures the decision in writing.
The translations. These are the homepage, the sales deck, the cold email, the LinkedIn page, and the pitch deck, and each one is a translation of the same underlying positioning into the medium and audience.
The pollination. This is getting every touchpoint aligned and every employee able to repeat the positioning, and it's the work most teams skip after writing the statement, which is why most positioning statements don't do anything.
If you have a statement but no pollination, you have a document, and if you have translations without a statement, you have inconsistency. If you have a statement without a decision behind it, you have a fiction.
The mistakes that kill positioning statements
Writing for the audience instead of for the team. A positioning statement is internal, so it's allowed to be longer and more specific than the homepage. Teams that try to make the statement "feel inspiring" produce a tagline by accident and lose the strategic clarity.
Using "leading platform." If your positioning statement contains the words "leading" or "platform," the team hasn't decided yet, since "leading" is unverifiable and "platform" is a category dodge. Both are tells.
Three differentiators. Pick one, because a statement with three differentiators is a team that negotiated, and the buyer doesn't remember three things. They remember one, if you're lucky.
No named competitor. "Unlike traditional solutions" is the cowardly version, because the buyer is comparing you to a specific product, by name, so name it back.
Everything-and-nothing scope. A statement that could describe any company in your space describes none of them. "For businesses seeking growth" is the worst version. "For heads of customer support at B2B SaaS companies with 5-50 agents" is the version that does work.
Jargon as positioning. "End-to-end," "best-in-class," "next-generation," "world-class," "enterprise-grade." These words appear when the team didn't want to commit to anything specific, so strip them out and see if the statement still says anything. Usually it doesn't, which is the diagnosis.
Never revisiting it. A positioning statement has a shelf life of two years, maybe three, because the competitive landscape changes, your product changes, and buyer language changes. Companies that wrote a statement in 2022 and haven't touched it since are positioning for a market that no longer exists.
What to do this week
Three concrete moves:
- Find your current positioning statement, if you have one. Read it out loud and ask whether it names a buyer specifically, whether it names a competitor, and whether it has one differentiator or three.
- If the statement is fuzzy or doesn't exist, write a draft using the Moore template, without workshopping it, by having one person write it and then circulate it.
- Show the draft to three customers and three salespeople. Ask if it sounds like the company, because the gap between what you wrote and what they say back is the next round of work.
If the gap is big, the Pipeline Story Sprint is the structured version of closing it. It runs ninety days and includes customer interviews, a competitive teardown, a positioning statement the team can repeat, and the rewritten homepage that translates from it.