Product Positioning Statement: A Step-by-Step Guide
Picture a prospect finishing a demo, nodding along the whole time, and then asking: “so is this more like a CRM, or more like a project tool?” That kind of question kills deals that should have closed. The product wasn’t the problem. Nobody on the team had ever forced themselves to write a single, testable sentence answering what the product actually is, who it’s for, and why it beats the alternative someone would otherwise reach for. A product positioning statement isn’t a marketing nicety, it’s the sentence that determines whether a prospect spends the rest of the call evaluating your product on your terms or theirs.
Most product teams treat positioning as a marketing deliverable that happens after the product ships, if it happens at all. That’s backwards. Positioning is a product decision as much as a marketing one, because it determines which features you build next, the ones that reinforce your claimed differentiation, or a scattered list of parity features chasing whatever the last lost deal complained about. A PM who understands positioning makes sharper roadmap calls than one who treats it as someone else’s department.
What a Product Positioning Statement Actually Does
Positioning is not messaging, and it’s not a tagline. Messaging is what you say once positioning is already decided; a tagline is a compressed, polished output of messaging. Positioning is the strategic decision underneath both: what market category you’re claiming, who specifically cares most about your unique value, and what you’re being compared against in the buyer’s head whether you name it or not. Skip this step and your messaging team writes clever copy for a category nobody agreed on, and every subsequent word choice is downstream of a decision nobody actually made on purpose.
This tends to go wrong in a specific, recurring way: a product team assumes their category is obvious because it’s obvious to them, then discovers in a win-loss review that prospects were quietly comparing them against a completely different set of alternatives than the ones the sales deck argued against. If competitive battlecards are fighting the wrong opponent, no amount of feature velocity fixes that, the positioning was wrong before the first line of the deck was written.
The Five Inputs You Need Before You Write a Sentence
The framework here, adapted from April Dunford’s widely-cited positioning method, works through five inputs in order, and the order matters, because each one depends on the one before it. Dunford’s own writeup of the process makes the case that skipping straight to a fill-in-the-blanks positioning statement without doing this groundwork first produces generic, forgettable positioning, and it usually produces positioning a sales team won’t trust enough to actually use on a call.
| Input | The question it answers | Common mistake |
|---|---|---|
| Competitive alternatives | What would the customer do if your product didn’t exist? | Naming only direct competitors, ignoring “do nothing” or spreadsheets |
| Unique attributes | What can you do that alternatives genuinely can’t? | Listing features everyone in the category also has |
| Value themes | What outcome do those unique attributes actually enable? | Stopping at the feature instead of the customer’s actual payoff |
| Target market characteristics | Who cares the most about that specific value? | “Everyone” — the default answer that means no one |
| Market category | What frame makes your value obvious without explanation? | Choosing the biggest category instead of the clearest one |
The target market row is where product teams tend to disagree most, and it’s worth fighting about. It’s tempting to define the best-fit customer broadly to keep the total addressable market number impressive in a board deck, but broad targeting produces positioning nobody recognizes themselves in. A narrower, sharper answer, “seed-stage B2B SaaS founders doing their own sales” instead of “startups”, is what actually makes a prospect think “that’s us” in the first five seconds of a landing page.
The competitive alternatives row causes almost as much friction, usually for the opposite reason: teams under-name it. Positioning workshops regularly end with a team listing exactly one direct competitor and stopping, when the real alternative set included two adjacent tools and, more often than anyone wants to admit, a spreadsheet. Naming “do nothing” or “a spreadsheet” as a legitimate alternative isn’t an admission of weakness, it’s usually the most common thing you’re actually competing against, and pretending otherwise means differentiation gets built against the wrong opponent.
Writing the Actual Statement
Once the five inputs are settled, the statement itself is almost mechanical. The classic Geoffrey Moore structure still holds up: For [target customer] who [need/problem], [product name] is a [market category] that [key benefit]. Unlike [primary alternative], we [key differentiator]. The mistake most teams make here isn’t the template, it’s filling it in before doing the five-input work above, which produces a grammatically correct sentence built on inputs nobody validated against real prospects.
A filled-in example, for a hypothetical expense-management tool: For finance teams at 50–200 person companies who are drowning in manual receipt reconciliation, [Product] is an expense automation platform that closes the books three days faster every month. Unlike generic accounting suites, [Product] is built exclusively for the reconciliation workflow, not bolted onto a broader finance product nobody in the workflow actually opens. Notice what that statement is doing: it names a specific alternative (generic accounting suites), a specific value (three days faster close), and a specific audience (finance teams at a defined size band), not “businesses of all sizes.”
Reforge’s library of real positioning artifacts from operators at companies of varying stages is worth a look here, seeing how a Series B SaaS company actually filled in this template, warts and all, tends to be more useful than another abstract framework explainer once you understand the underlying logic.
A Worked Example: Repositioning a Mid-Market Analytics Tool
Picture a 60-person analytics company that had been positioning itself as “the easiest analytics platform for growing teams” for two years, with flat conversion on their pricing page and a sales cycle that kept stalling at the same objection: “how is this different from [larger competitor]?” Running the five-input exercise surfaces the actual problem: their real competitive alternative isn’t the larger competitor sales kept fighting, it’s teams building ad hoc dashboards in spreadsheets and BI tools, because their actual buyer is a data-literate ops lead, not a PM comparing dedicated analytics platforms.
They reposition around that insight: from “easiest analytics platform” to “the analytics layer for ops teams who’ve outgrown spreadsheets but don’t have a data team.” The market category shifts from “analytics platform” (a crowded, feature-comparison category) to “ops team analytics” (a narrower category where they’re unambiguously the best-fit choice). Sales cycle length drops by roughly three weeks over the next two quarters, not because the product changed, but because prospects stop comparing them against an enterprise competitor they were never going to beat on feature count. The team also rewrites exactly one page, the homepage hero and the top of the pricing page, before running this positioning through a full site redesign, deliberately, so they can validate the new frame against real pipeline before investing in a bigger creative overhaul that might need to change again.
Where This Breaks
The most common failure is treating positioning as a one-time exercise instead of something that gets revisited when the market shifts. A category that made sense at your Series A can quietly become the wrong frame by Series C, once competitors have crowded in or your actual customer base has drifted from who you originally targeted. Recovery: revisit positioning any time you notice sales consistently fighting objections that don’t match your battlecards, or win-loss data showing a competitor nobody expected.
The second failure is writing positioning in a room with no customer input, then discovering the “unique attributes” the team was proud of don’t actually register as unique to buyers. Internal enthusiasm about a feature is not evidence that customers weight it the way you do. Recovery: validate the value themes against your voice-of-customer program data before finalizing the statement, not after it’s already in the sales deck.
The third is confusing positioning with pricing, or trying to fix a positioning problem with a pricing change. Teams sometimes drop price to compete with an alternative that was never actually in the customer’s consideration set to begin with; the discount doesn’t move the deal because the real objection was category confusion, not sticker shock. Recovery: fix the story before you touch the number; our guide to writing a pricing strategy document only works once positioning is settled, not as a substitute for it.
The fourth failure, more specific to growth-motion companies, is positioning that never accounts for how differentiation actually gets perceived at the moment of delight versus the moment of purchase. The Kano model is a useful gut-check here: a “unique attribute” that customers expect as table stakes won’t do any positioning work for you, no matter how proudly it’s listed, because delight-driving differentiation and baseline-expectation features aren’t the same axis. Teams routinely lead their positioning with SSO support, genuinely proud of the engineering effort behind it, without noticing that every serious competitor in their category shipped SSO two years earlier, it was table stakes, not a differentiator, and leading with it signals to sophisticated buyers that the team doesn’t know its own market as well as it claims to.
Product Positioning Statement vs. Vision Statement vs. Messaging
These three get conflated constantly, and mixing them up is its own failure mode. A product strategy document is the broadest of the three, it’s the multi-quarter plan for how the product wins, and positioning is one input into that plan, not a replacement for it. Messaging is downstream of positioning: once you know your category, audience, and differentiator, messaging is the specific language, proof points, and objection handling built on top of that foundation for different channels and buyer personas. If you’re building a go-to-market motion around a product-led growth strategy specifically, positioning has to do more work with less human explanation available, see how to build a product-led growth strategy that works for how self-serve buyers form category judgments in the first ninety seconds, with nobody in the room to correct a wrong first impression.
Positioning also isn’t static once you expand beyond your original market. A statement built around “seed-stage US SaaS founders” doesn’t automatically translate when you expand into new geographies with different competitive alternatives and buyer expectations, see how to localize a product for international markets for what actually needs to be re-examined, not just translated, when positioning crosses a border.
Write the five inputs down this week, even roughly. The sentence itself takes ten minutes once the inputs are real, that’s really all a product positioning statement is: ten honest minutes built on top of work most teams skip. What takes longer, and what most teams skip, is being honest about which alternative buyers are actually comparing you against, not the one the sales deck was built to fight.
