Founder Playbook

How to position your startup (and tell if it's working)

How do I know if my SaaS positioning is working?

Ask three of your best users to describe what you do to a colleague. If you get three different answers, the positioning isn't working — even if the product is fine.

What are the signs of bad SaaS positioning?

Three early signals appear before traffic is large enough for A/B testing to be useful: inconsistent customer descriptions, interchangeable category, and inability to name the buyer + trigger event in one sentence.

Is my problem positioning or product?

Run three diagnostics. Do retained users use the product as intended (if yes → positioning, if no → product)? Do three customers name the same alternative they considered (if no → positioning hasn't placed you in a category)? Can a stranger read your homepage and say who it's for in 10 seconds (if no → positioning is upstream of any product fix)?

How do I test positioning without enough traffic to A/B test?

Use qualitative signals first: customer interviews, the 10-second homepage test on strangers, and how customers describe the problem in their own words. April Dunford's five-question framework produces a testable positioning statement before you have the volume for statistical comparisons.

Positioning is the act of placing your product in a category, against specific alternatives, for a specific customer who values a specific outcome. Most founders skip this and write copy hoping for the best — then six months later, growth stalls and they start blaming the product. This guide walks the five questions you have to answer in order to position a startup, applies them to a worked example, then shows how to test whether your answers actually work in the market.

Why positioning is upstream of everything you do next

Positioning isn't a marketing artifact. It's the strategic choice that determines which competitors you're compared to, which customers find you, what price they expect, and which features they think are table stakes. Get this wrong and every downstream choice — copy, channels, sales calls, even some product decisions — runs at a discount. One r/SaaS founder posted this in February 2026 after going through the exercise:

"It made me question whether positioning is upstream of distribution. If the positioning is sharp, distribution channels seem to work better. If it is vague, no channel performs well."

The founder had originally positioned their product as "an AI-powered automation platform." Cold outreach fell flat. Conversations required too much explanation. Then they narrowed to a specific user with a specific pain — the product itself barely changed — and inbound, sales-call efficiency, and community engagement all improved. The positioning was the lever.

The data behind this:

63% of analyzed startup postmortems died from positioning-related failures — Also-Ran (40%), Premature Generalizer (9.2%), Capability Trap (7.3%), Category Creator (5.1%), Language Mismatch (1.6%).

Klarion analysis of 1,041 startup postmortems, sourced from Failory Cemetery + Loot Drop, May 2026 snapshot.

12.5% died from no-market-need and 14.7% from execution failure — combined, less than half the share that positioning takes. Positioning isn't the most exciting problem to fix. It's the most fatal one to ignore.

Klarion analysis of 1,041 startup postmortems, sourced from Failory Cemetery + Loot Drop, May 2026 snapshot.

The five questions, in order

The most operationally grounded positioning framework available is April Dunford's Obviously Awesome (2026 edition out earlier this year). It works through five questions in a specific order — and the order matters. Most founders start at the end (naming a category) and work backwards. Dunford's argument, backed by years of repositioning work for B2B SaaS, is that the category you belong in only becomes clear once you know what you're really being compared to.

1. Competitive alternatives

What would customers do if your product didn't exist? This is the starting input — not a check at the end. The answer is often not a direct competitor. It's "do nothing," "hire someone," or "build it ourselves with a spreadsheet."

2. Differentiated capabilities

What do you have or do that those alternatives don't? Real, verifiable features — not "we're more focused" or "we care more." Limit to 1–2 or they lose credibility.

3. Differentiated value

"AI-powered automation" is a capability. "Deploy in 4 minutes without touching a YAML file" is the value it unlocks. Customers buy the value, not the capability — write the outcome, not the mechanism.

4. Best-fit customers

Who cares most about that specific value — not in general, but given the competitive alternatives you named in step 1? The answer is usually narrower than founders expect.

5. Market category

Which category should you be placed in? This is a strategic choice — not a description. The category you claim sets the assumptions customers bring: which competitors to compare, what price to expect, what features are table stakes. Choosing the wrong category makes everything harder. Choosing the right one makes your differentiation obvious.

The order matters. Most founders start by naming their market category and work backwards. Dunford's argument — backed by her work repositioning dozens of products — is that you have to start with competitive alternatives first. The category you belong in only becomes clear once you know what you're actually being compared to.

A worked example

Suppose you've built a survey tool for product teams. Apply the five questions in order:

  1. Competitive alternatives. Not just Typeform and SurveyMonkey. Most product teams are using a hacked-together combination of Slack polls, Notion docs, and the analytics tool they already have. "Do nothing" is also a real alternative — many teams just guess.
  2. Differentiated capabilities. The thing those alternatives can't do: you tie each survey response to a specific event in the product (a feature usage spike, a churn risk flag) so the team can see which users said what without manual joining.
  3. Differentiated value. Product teams stop guessing whether feature feedback comes from power users or first-week users. Decisions about what to build next get sharper because the data is segmented automatically.
  4. Best-fit customers. Mid-stage SaaS product teams (Series A–B, 5–20 person product orgs) where the head of product owns both qualitative and quantitative feedback and currently runs both manually.
  5. Market category. Not "survey tool" — that frames you against Typeform and the buyer compares price-per-response. The right category is closer to "product analytics survey" or "in-product feedback platform." That category sets the right alternatives, the right price band, and the right feature expectations.

The category in step 5 only became obvious after working through 1–4. If you'd named the category first ("we're a survey tool for product teams"), you'd have positioned against Typeform and lost — because every prospect would have asked why you cost more for fewer integrations.

How to tell if your positioning is working

Once you've worked through the five questions, you need to know whether what you produced is actually doing its job in the market. These three behavioral signals tell you before you have enough traffic to A/B test.

Can't repeat it back

Ask three paying users to explain your product to a colleague. If you get three different answers, your messaging is ambiguous enough that each person projects their own frame onto it.

Wrong competitors

Track the alternatives mentioned in sales calls and cancellation reasons. If the same "wrong" competitor keeps appearing, your market frame is off — not your sales execution.

Objections aren't changing

Early objections are almost entirely positioning-driven: "I don't understand what this does." If you've shipped five updates and the objections are the same, features aren't the problem.

Signal 1 in detail — the repeat-back test

Good positioning is repeatable without coaching. Ask your best users — people who've paid and stayed — to describe you to a skeptical colleague. Don't give them talking points.

The bar: If a customer who came in six months ago describes you in roughly the same words as one who came in last week, you have a positioning foundation. If descriptions diverge by persona or use case — you have a category problem.

Signal 2 in detail — competitor frame

Positioning lives in the frame of reference you occupy. Which competitors prospects name in sales calls tells you which category they've placed you in — and whether that's the right one.

BROKEN

Prospects name tools built for a different buyer. You spend calls re-educating about category.

WORKING

Prospects name exactly the tools you'd name as alternatives. The competitive conversation is already set up.

Real case — Rdio: Rdio built a product most reviewers considered superior to Spotify. But prospects kept comparing them to iTunes — a content ownership product, not a streaming service. That's a category frame problem, not a sales execution problem. Rdio was playing in the wrong frame of reference, and no amount of feature work fixed it. Spotify's free tier and clearer "streaming" framing captured the market before Rdio could correct course.

Signal 3 in detail — objection evolution

Objections shift as positioning improves. Track which stage you're at:

Stage 1 — Clarity objections

"I don't understand what this does." Positioning is broken.

Stage 2 — Timing objections

"I get it but I'm not sure I need it right now." Positioning is working; timing is the gap.

Stage 3 — Price objections

"I understand it and want it but the price is high." Strong positioning; now it's a value conversation.

Is it positioning or product?

When growth stalls, founders default to blaming the product. Sometimes the product is the problem. Sometimes positioning is. Run these checks to separate them:

POSITIONING PROBLEM

Signs to look for

  • Users describe your product differently from each other
  • High drop-off before activation, not after
  • Churn surveys mention confusion, not missing features
  • Wrong competitors keep appearing in sales calls
  • Referrals are rare even from happy customers
PRODUCT PROBLEM

Signs to look for

  • Users understand the product but stop using it
  • Activation is fine but retention is poor
  • Churn surveys consistently mention a specific missing feature
  • Right competitors, but users prefer them for a specific reason
  • Engaged free users who won't pay

Common mistakes

Work through your positioning with the Strategy Wizard

Klarion walks through all five questions with live market data — competitive alternatives founders in your space actually face, which buyer segments care about which capabilities, what categories pull in the right kind of traffic.

Open Strategy Wizard