Geoffrey Moore's Positioning Statement Framework

What it is

A structured template designed to clearly articulate a product's or company's market position by defining six core elements: target customer, their specific need or opportunity, product category, primary benefit, main competitive alternative, and key differentiation. Originating from Moore's 1991 book Crossing the Chasm, it provides a concise, focused way to communicate unique value to a specific audience. The template forces discipline: because it must be completed as a single, tightly worded paragraph, it is very hard to hide behind vague claims or unresolved internal debates about who the product is actually for. Although it originated in enterprise technology marketing, the format has since spread well beyond software; consumer brands, professional services firms and even non-profits use variations of it to force the same discipline before spending money on campaigns.

The standard template structure is:

"For [target customer] who [statement of need or opportunity], the [product name] is a [product category] that [statement of key benefit]. Unlike [primary competitive alternative], our product [statement of primary differentiation]."

When to use it

• Clarifying internal strategic positioning before developing marketing materials
• Aligning cross-functional teams (product, marketing, sales, support) around a unified value message
• Defining positioning for new products, markets, or market segments
• Testing and refining value propositions in early-stage product development
• Creating a definitive positioning claim that guides all external communications
• Ensuring a product can pass the "elevator test" for clear, concise communication
• Briefing a new sales hire or agency partner who needs a single reference point for how the company talks about itself
• Resolving a naming or category dispute by forcing the team to agree on the "unlike X" comparison first, before arguing about wording

Ownership

At a scaled company with a specialised PMM team, a Head of Product Marketing owns the final wording and sign-off, drafting it with input from sales leadership, who validate it against live deals before it ships. A solo or founding PMM owns the statement outright, working directly with the founder or head of sales rather than a dedicated review committee. Execution, pulling call recordings, running the reps' pressure-test, updating the sales deck, sits with the PMM at either stage; only the final sign-off moves up to a Head of PMM or CMO once the team grows.

How to apply it

1. Define target customer: Identify a specific, underserved customer segment (not "everyone"). Go beyond a job title: describe the situation that makes them ready to buy now, for example company size, team structure, or a trigger event such as a recent funding round or a failed vendor relationship. If you cannot picture one real, named prospect who fits the description, the segment is still too broad.
2. State the need/opportunity: Articulate the problem they face or the opportunity they seek, phrased from their perspective, ideally in their own words. Pull language directly from sales call notes, support tickets, or customer interviews rather than inventing it internally; language borrowed from your own product roadmap tends to read like a feature list, not a felt need.
3. Name the product category: Choose a frame of reference that helps customers immediately understand what the product is. An unfamiliar or invented category (for example "revenue orchestration platform") requires extra education before a buyer can evaluate you at all, so weigh the appeal of category creation against the cost of explaining a term nobody is searching for yet.
4. Identify key benefit: Focus on the primary outcome or value the customer gains, not just features. Ask "so what?" of every feature at least twice: a feature produces a capability, a capability produces an outcome, and it is the outcome that belongs in the statement.
5. Identify primary competitor: Specify what customers would use instead (could be a competitor, manual process, or status quo). Be honest here: naming a weaker competitor than the one you actually lose deals to produces a positioning statement that wins arguments internally but falls apart in a live sales conversation.
6. Articulate differentiation: Explain the compelling reason why your solution is better. Be specific about the way you reduce risk, deliver value, or serve the customer that competitors don't; a claim only counts as differentiation if a competitor could not credibly make the same claim about themselves.
7. Test for clarity: Ensure the statement is simple enough to be conveyed via word-of-mouth and understood in a brief interaction. Read it aloud to someone outside the company and ask them to repeat it back in their own words; if they cannot, simplify further.
8. Pressure-test with real deals: Run the statement past three to five active sales opportunities and ask the rep whether it matches what actually persuaded the buyer to move forward. Revise before rolling it out company-wide; a statement that only sounds good in a workshop is not yet proven in the field.