Founder clarity resource

Startup Positioning Framework

A working framework for defining target customer, context, alternative, differentiated value, proof, category, and reason to believe — built to survive scrutiny, not just sound good.

Target question: How do I position my startup clearly?

Last updated

Available as Markdown

Positioning is the internal reference a founder-led team should agree on before writing a single external sentence. This framework breaks positioning into components you can define once, argue over deliberately, and reuse consistently across sales, marketing, and investor materials.

What positioning actually is

Positioning is a working description of who you serve, what they use instead of you today, and why your alternative is better for them specifically. It is not a tagline, an ad headline, or a pitch deck slide. Those are compressions of positioning for a specific audience — they come after positioning is settled, not instead of it.

Because it is internal, positioning should be argued over. A founder, a salesperson, and a marketer should be able to read the same positioning statement and describe the company the same way to three different audiences without contradicting each other.

The seven components

Target customer
The specific buyer or user segment the positioning is written for — not everyone who could theoretically benefit.
Context
The situation the target customer is in when the problem shows up — what triggers the need, and how often.
Alternative
What that customer actually does today instead of using your product — a competitor, a manual process, or doing nothing.
Differentiated value
The specific outcome only you deliver relative to that named alternative, stated in terms the customer would recognize.
Proof
Evidence you can currently support that backs the differentiated value claim — not evidence you hope to have later.
Category
The mental shelf you want buyers to place you on, which sets their default expectations before they read anything else.
Reason to believe
The underlying explanation for why your differentiated value is true — a mechanism, a design choice, or a constraint you accepted that a copycat would not.

Defining the target customer

A target customer definition that could describe half the market is not a definition. It should be specific enough that you could look at a list of companies or job titles and sort them into 'yes' and 'no' with a colleague and mostly agree.

  • Name a role or buying context, not just an industry (e.g. 'the operations lead approving vendor tools at a 20–100 person service business', not 'small businesses').
  • Include the trigger that makes them start looking — a hire, a missed deadline, a failed audit, a manual process that broke.
  • Exclude adjacent segments explicitly, even if they could technically use the product, if they are not who you are building and selling for right now.

Context and the real alternative

The alternative is rarely 'no solution.' It is almost always something already in place: a spreadsheet, a shared inbox, a manual handoff between two people, a competitor's tool, or simply a lower-priority task that keeps getting deferred. Positioning that ignores the real alternative sounds strong internally and falls flat externally, because the buyer is comparing you to something specific whether you name it or not.

  • Status quo alternative: an internal process, spreadsheet, or workaround the team already tolerates.
  • Competitive alternative: a named or category of existing vendor the buyer is also evaluating.
  • Deferred alternative: the problem is real but not urgent enough to act on yet — your positioning needs to address why now.

Differentiated value, not general value

General value statements — 'saves time,' 'reduces cost,' 'improves visibility' — are true of nearly every B2B product and therefore prove nothing. Differentiated value has to be stated in a way that would be false or irrelevant if said about the named alternative.

  • Weak: 'Our tool helps teams work faster.'
  • Stronger: 'Unlike a shared spreadsheet, schedule changes here update every downstream calendar automatically, so no one is working from a stale version.'
  • Test: could a competitor's team read this sentence and immediately agree it also describes them? If so, it is not differentiated value yet.

Choosing a category

Category tells a buyer what to expect before they read anything else. Choosing an existing, understood category borrows the buyer's existing mental model of pricing, evaluation criteria, and use case — at the cost of getting compared on those established terms. Inventing a new category can avoid unwanted comparisons, but it requires far more explanation before a buyer understands why they should care at all.

Reason to believe

Reason to believe is the mechanism behind the claim — why the differentiated value is true, and why it would be hard for a competitor to casually replicate. This is where positioning connects directly to proof: a claim without a reason to believe reads as marketing; a claim with one reads as a fact about how the product works.

How to build a positioning statement

  1. Write the target customer and the context that triggers their need in one sentence each.
  2. Name the real alternative this customer uses today — status quo, competitor, or deferred task.
  3. State the differentiated value in terms that would be false if applied to that named alternative.
  4. Attach at least one piece of proof you can currently support for the differentiated value claim.
  5. Assign a category that sets the buyer's expectations correctly before they read further.
  6. Combine the pieces into one statement, then run it against the review tests below before treating it as approved.

Worked example

Example for an early-stage B2B scheduling tool sold to service businesses: target customer — operations leads at 20–100 person service businesses; context — staff schedules change several times a week and updates are communicated by message; alternative — a shared spreadsheet and a group chat; differentiated value — schedule changes update every connected calendar automatically, so no one works from a stale version; category — team scheduling software; reason to believe — the schedule is the single source that every calendar reads from, rather than a document that has to be manually copied.

Draft your positioning statement

  • Prompt: Target customer: who specifically, and in what role?
  • Prompt: Context: what situation makes this problem show up?
  • Prompt: Alternative: what do they actually use instead of you today?
  • Prompt: Differentiated value: what is true of you that is not true of that alternative?
  • Prompt: Proof: what evidence can you currently support for that claim?
  • Prompt: Category: what shelf do you want buyers to place you on?
  • Prompt: Reason to believe: why is the differentiated value true?

Positioning vs. slogans

A slogan is a short, memorable compression meant for an external audience in a specific moment — a homepage headline, an ad, a booth banner. Positioning is the reasoning underneath the slogan. Writing a slogan before positioning is settled produces something catchy that no one on the team can actually defend or explain consistently when asked a follow-up question.

Positioning vs. feature lists

A feature list describes what the product does. Positioning explains why that matters to a specific buyer, relative to what they use instead. Teams that lead with feature lists often produce accurate but unpersuasive materials, because a feature is only meaningful once it is connected to the alternative it replaces and the outcome the buyer actually cares about.

Tests to review your positioning

  • A stranger can repeat the differentiated value in their own words after one read.
  • The alternative named is specific, not 'nothing' or 'the market.'
  • A competitor's team would disagree with this description of us, rather than nodding along.
  • Every claim in the statement is something we can currently support with real proof.
  • The category sets accurate expectations rather than borrowed hype language.
  • Sales, marketing, and the founder would describe the company the same way if asked separately.

Common failures

  • Target customer defined so broadly that the positioning could apply to almost any business.
  • Leading with features instead of the outcome relative to the named alternative.
  • No named alternative, which makes differentiated value impossible to state precisely.
  • Borrowing language from a category leader instead of describing your own reason to believe.
  • Proof or reason-to-believe claims that outpace what the product can currently support.
  • Every team member describing the company slightly differently because positioning was never written down and approved in one place.

Keeping positioning consistent across teams

Positioning decays quietly. A founder updates it in a pitch conversation, a salesperson simplifies it on a call, and a marketer writes copy from an old draft — and within a few months, three audiences are hearing three different companies described. Positioning only holds value as a shared reference if there is one current, approved version everyone is working from.

TrueCompanyOS helps founders maintain one approved version of this positioning so sales, investor, marketing, and team communication do not drift.

FAQ

Is positioning the same as messaging?

No. Positioning is the underlying reasoning about target customer, alternative, and differentiated value. Messaging is how that reasoning is expressed for a specific audience and channel — a homepage, a cold email, an investor deck. Messaging should change by audience; positioning should not change every time someone writes new copy.

How often should positioning be reviewed?

Review it after a meaningful shift — significant customer feedback that contradicts an assumption, a roadmap change that alters differentiated value, or new competitive activity that changes the relevant alternative. Positioning does not need a fixed review calendar, but it does need an owner who notices when reality has moved past the current statement.

Do I need customer interviews before I can write this?

You can draft a first version from what you already know, but treat it as a hypothesis rather than a finished statement. Directional signal from a handful of real conversations with the target customer is usually enough to sharpen context and alternative; the statement should keep updating as you learn more, not lock in permanently on day one.

Looking for the product that puts this into practice? See pricing or return to the homepage.

Startup Positioning Framework | TrueCompanyOS