You don't need to be first, biggest, or cheapest to win a positioning fight. You need to be the obvious best choice for a specific set of buyers who already care about what you're good at. Positioning against competitors starts with picking the comparison you win, not the comparison everyone defaults to.
Most founders skip this and let the market pick the comparison for them. That's how a genuinely good product ends up looking like a worse, smaller version of the category leader.
What positioning against competitors actually means
Positioning is not a tagline. It's the answer to one question: compared to what, and why does that comparison favor you?
Every buyer already has a frame of reference in their head before they land on your site. If you don't set that frame, they'll pick one themselves, usually the most obvious competitor, and you'll lose by default because you didn't choose the fight.
April Dunford's positioning framework, laid out in "Obviously Awesome," starts with listing your true competitive alternatives, not your category peers. For an early-stage SaaS founder, the real alternative is often a spreadsheet, a manual process, or "doing nothing," not the funded competitor with the bigger marketing budget.
This is also why positioning problems get misdiagnosed as product problems. A founder sees stalled deals and confused prospects and assumes the product is missing something, when the real issue is that buyers were never told which comparison to make. We've seen this pattern repeatedly with early-stage teams: the product was fine, the frame around it wasn't.
The mistake: positioning against features
Founders default to a feature comparison table because it feels objective. It backfires for three reasons. First, the market leader has more resources to add features faster, so a feature race is a race you lose over time. Second, buyers don't evaluate 40 rows of checkmarks, they evaluate one or two things they actually care about. Third, a feature table implicitly puts the bigger competitor's product at the center of the comparison, reinforcing that they're the standard and you're the alternative.
HubSpot didn't out-feature Salesforce to win the small-business CRM market. It repositioned the comparison entirely around ease of use and price for a buyer Salesforce was structurally too complex and expensive to serve well. Figma didn't out-feature Adobe on day one, it won by making browser-based, real-time collaboration the thing that mattered, a dimension Adobe's desktop architecture couldn't match. Toast didn't try to be a better general-purpose POS than the incumbents, it became the restaurant POS, narrowing the market instead of fighting for all of it.
The 4-step framework for positioning against competitors
- List your true competitive alternatives. Not "who's in our category" but "what would this specific customer use if we didn't exist." Often that's a spreadsheet, a competitor, or a manual workaround, and each implies a different comparison.
- Find the attribute your true alternative structurally can't match. Not a feature you built faster, but something baked into how you're built. Speed of implementation, a specific integration, pricing model, or a workflow your architecture makes possible and theirs doesn't.
- Confirm someone actually cares. An attribute nobody values isn't a differentiator, it's trivia. Pull this from the same customer interviews you'd run for ICP work: what did they say made them choose you, unprompted, in their own words.
- Write the comparison down in one sentence you can defend in a sales call. "For [specific buyer], unlike [true alternative], we [attribute] so you [outcome]." If a rep can't say it in one breath without hedging, it's not positioning yet, it's a wish.
Real examples: how three companies won without being first
Toast wasn't the first restaurant POS system, but it built specifically around restaurant workflows (menu changes, tip pooling, tableside ordering) while general POS vendors treated restaurants as one vertical among many. The narrower frame became the advantage.
HubSpot entered a market Salesforce already dominated and won a different segment by repositioning around a buyer Salesforce's own complexity excluded: small businesses without a dedicated RevOps function. Same category, different true alternative, different fight.
Figma's real early alternative wasn't just Sketch, it was designers emailing files back and forth and losing version control. Positioning around collaboration, not just design tools, made the comparison about a workflow problem competitors' desktop-first architecture couldn't solve.
None of these three were positioned as "better X." They were positioned as the right choice for a buyer the incumbent structurally couldn't serve as well. Notice what they didn't do: none of them waited until they had feature parity with the market leader before claiming a position. They claimed the position first, then built into it.
That order matters more than most founders assume. Positioning isn't a victory lap after the product is done, it's a bet you make early about which buyer you can serve better than anyone else, and then you build to make that bet true.
Your first 30 days move
Interview five customers who chose you over a specific alternative and ask exactly what tipped the decision, in their own words, not yours. Write down the true alternative they compared you to (not your official competitor list), the one attribute that mattered, and the exact phrase they used. That's your positioning statement's first draft, and it's more reliable than anything a strategy session produces from scratch.
Frequently asked questions
What's the difference between positioning and messaging?
Positioning is the strategic decision about which comparison you win and for whom. Messaging is how you communicate that decision in words, on a landing page, in a sales deck, or in an email. Get positioning wrong and no amount of messaging polish fixes it.
How do I position against a competitor with 10x my funding?
Don't compete on their terms. Find the buyer segment their size and architecture make it hard for them to serve well, and make the comparison about that segment's specific needs instead of a general feature race.
Do I need a different positioning for every buyer persona?
Usually one core positioning with persona-specific proof points, not a fully separate positioning per persona. If your true competitive alternative changes dramatically by persona, that's often a sign you're serving two different markets, not one product with several angles.
How often should positioning be revisited?
Quarterly at minimum, and immediately after a new well-funded competitor enters, a core customer segment shifts, or win rates against a specific competitor start dropping. Positioning decays as the market moves, it isn't a one-time document.
Can positioning fix a product-market fit problem?
No, and this is the most common founder mistake in this category. Weak positioning and weak product-market fit look identical from the outside (confused buyers, stalled deals), but the fixes are different. If customers who buy are happy and retain well, it's a positioning problem. If they buy and still churn fast, it's product-market fit.
What if we genuinely don't have a unique attribute yet?
Then positioning work doubles as a product roadmap signal. The customer interviews in the 30-day move above will show you what buyers wish existed, which is usually a better prioritization input than an internal feature debate.
Positioning against competitors is a decision you make once you know which comparison you can actually win, then defend everywhere from the homepage to the first sales call.