Positioning Statement

positioning-statement

positioning is the answer to "who is this for, what does it do, and why pick it over alternatives?" written in a way the team uses to make decisions.

the canonical structure

for [target audience]
who [specific need or job-to-be-done]
[product name] is [category]
that [primary benefit or differentiator]
unlike [primary alternative]
[product name] [key reason to believe]

each line has rules.

target audience

• specific enough to be a single ear (not "businesses")
• defined by situation or job, not just by role
• bad: "marketers"
• good: "head of marketing at a 50-200 person b2b software company in the first year of demand generation buildout"

if you can't be that specific, you don't know your audience well enough yet.

need or job

• written in the user's terms
• ties to a moment, not a vague desire
• bad: "wants better analytics"
• good: "needs to know which marketing campaigns produced pipeline that closed last quarter"

category

• a word the audience already uses
• not a category you're inventing (yet — that comes later)
• bad: "ai-powered insights platform"
• good: "marketing attribution tool"

inventing a new category is a bigger play. if you do it, you have to teach the category before you sell the product.

benefit or differentiator

• what's actually different about this product, in user-facing terms
• one thing, not three
• bad: "the most comprehensive solution"
• good: "models multi-touch attribution without requiring engineering work"

alternative

• name it. either a competitor, a category, or a workaround
• "doing nothing" or "spreadsheets" is often the real alternative

reason to believe

• the specific thing about how you built it or who you are that backs the differentiator
• bad: "industry-leading expertise"
• good: "we built the attribution engine while running it inside the marketing team at a public software company"

the test

after writing the positioning, ask:

• would a competitor say the same thing?
• could you sell it to one person without explaining the category?
• does it suggest what we say no to?

if the answer to the first is yes, the positioning isn't differentiating. if the answer to the second is no, the audience or category is too abstract. if the answer to the third is no, the positioning isn't sharp enough to guide tradeoffs.

output

positioning statement (single paragraph in canonical structure)

audience deep dive
  who they are (situation, role, sophistication)
  what triggers their need
  what they try today
  why current options fall short

category
  the word the audience uses
  why we're using this category vs. an adjacent one
  the bet: if we redefine the category later, here's the angle

differentiator
  the one thing
  why it matters to the audience
  why it's hard to copy

alternatives map
  alternative 1: [name] — [why they choose this today]
  alternative 2: [name] — [why they choose this today]
  do-nothing: [the cost of doing nothing today]

reason to believe
  the specific evidence (capability, team background, customer outcome, technical fact)

what to avoid

• positioning the product against itself (no contrast)
• listing all the features as the differentiator (it's almost never all of them)
• audiences who don't exist as a coherent group
• categories that don't appear in customer language
• benefits the audience can't tell apart from competitors'