You're building in a category where there's a category leader so dominant they define the space. Notion in tools-for-thought. Stripe in payments. Figma in design. Linear in issue tracking. When this happens, most founders default to one of two positioning strategies, both of which usually fail.
The first failed strategy: imitation. Adopt the leader's visual language, copy the conventions they established, position as "the [leader] for [smaller niche]." Customers respond with "why would I use the imitation when the original exists?"
The second failed strategy: contrarianism. Define yourself entirely against the leader. "Unlike [leader], we believe..." Customers respond with "if your whole identity is opposition, you're not telling me what you actually are."
There's a third path that actually works. Here's the framework.
What the leader's brand is doing for them
Before you decide how to position against the leader, understand what the leader's brand is doing for the leader. Three jobs:
1. Authority. The leader is recognized as the default. New entrants in the space are evaluated relative to the leader. The leader doesn't have to prove their seriousness; everyone else does.
2. Convention-setting. The leader's visual language, terminology, and conventions become the category's. If Notion calls something a "page," everyone else either calls it a page or has to explain why they don't.
3. Trust amplification. Customers researching the category find the leader first, evaluate them, and use them as a baseline. The leader benefits from the work of making customers educated.
You can't replicate any of these. They're earned through scale and time. But you can position in ways that turn each of them into a constraint that benefits you, rather than a wall.
The third path: be a meaningful "and"
The framework: don't position against the leader. Position alongside them, but for a use case or customer that the leader can't serve well. The implicit message: "You probably use [leader] for X. We're for the thing where [leader] doesn't quite fit."
Examples of this working:
- Linear vs. Jira: Linear didn't position as "anti-Jira." It positioned as "issue tracking that respects the engineering team's pace." Jira customers who were tired of slowness adopted Linear. Jira customers who were comfortable stayed. Both can coexist.
- Figma vs. Sketch: Figma didn't position as "Sketch but better." It positioned as "design that works because everyone's in the same file." Sketch users with collaboration pain moved. Solo designers without that pain stayed on Sketch (for a while).
- Notion vs. Google Docs: Notion didn't position as "the document tool to replace Docs." It positioned as the workspace where documents, databases, and notes all live together. Docs users with that consolidation need migrated. Docs users without it stayed on Docs.
The pattern: each of these challengers carved out a specific dimension where they were structurally better, without claiming to be a wholesale replacement.
The 3 axes of meaningful "and"
The dimensions on which you can position alongside (rather than against) a leader fall into three categories:
Axis 1: Customer segment. The leader serves a broad market. You serve a specific subset of it that has needs the leader can't (or won't) serve as well. Examples: leader serves enterprises; you serve startups. Leader serves designers; you serve founders. Leader serves established brands; you serve pre-launch brands.
The criteria: your segment has to be specific enough that the leader doesn't optimize for it, large enough to support a business, and identifiable so customers self-select.
Axis 2: Use case. The leader is built for general use within the category. You're built for a specific use case that the general tool handles awkwardly. Examples: leader does CRM in general; you do CRM specifically for outbound sales teams. Leader does email in general; you do email specifically for transactional triggers.
The criteria: the use case has to be common enough to support a business, distinct enough that purpose-built tooling produces a noticeably better experience, and structural enough that the leader can't bolt on a feature to fix it.
Axis 3: Philosophy. The leader has a worldview baked into their product (often invisibly). You have a different worldview that produces different decisions. Examples: leader optimizes for power features; you optimize for simplicity. Leader optimizes for individual productivity; you optimize for team alignment.
The criteria: your philosophy has to be visible in your product decisions, not just in marketing copy. Customers need to feel the difference, not just read about it.
What to copy and what to avoid
Some things you should copy from the leader. Some things you shouldn't.
Do copy: Category-standard terminology where it serves customers. If everyone in the space calls something a "workspace," your customers will type "workspace" when they search. Renaming it doesn't help you.
Don't copy: Visual identity. If you look like the leader, you'll feel derivative. Take the opposite visual direction so customers can immediately distinguish you.
Do copy: Onboarding patterns that the leader has established as the standard. Customers know how SaaS onboarding works; reinventing it confuses them.
Don't copy: The leader's pricing model exactly. Pricing should reflect your specific positioning. If the leader is per-seat and you're better suited to flat-rate (or vice versa), price for your model.
Do copy: The leader's commitment to quality. The leader earned authority through hundreds of small details done well. Your version of those details should be at the same standard.
Don't copy: Their entire brand voice. Customers should hear your brand and immediately not mistake it for the leader's.
The positioning statement template
Here's a structured way to write down your positioning against a leader:
For [specific segment / use case / philosophy match],
who currently uses [leader] but is frustrated by [specific limitation],
we're [your brand] ,
the [category] that's built specifically for [your differentiator].
Unlike [leader], we [structural difference, not feature difference].Fill it in. Read it out loud. Does it actually distinguish you, or does it sound like you're describing a feature improvement to the leader? Feature improvements aren't positioning; structural differences are positioning.
What to do when your positioning isn't landing
If customers can't tell what makes you different from the leader, three diagnostics:
1. Is your differentiator specific enough? "Faster than [leader]" isn't positioning. "10x faster for engineering teams with more than 50 issues per week" is positioning. Specificity makes the difference visible.
2. Is your differentiator structural? If the leader could ship the same feature in a sprint, your differentiator is too shallow. Structural differences come from architecture, philosophy, or business model. Things the leader can't change without disrupting their core.
3. Is your differentiator visible in the product? Marketing copy is cheap; product experience is expensive. Customers should feel your positioning in the first 60 seconds of using your product. If they don't, your positioning is a marketing claim, not a product reality.
Positioning against a category leader is the hardest brand problem most founders will solve. Done well, it's a competitive moat. Done badly, it's a permanent identity crisis. Spend the time to get the positioning right before you commit to the brand identity that expresses it. The brand follows the positioning; the positioning is the harder work.
Your brand kit, ready in 10 minutes.
Five quick taps. Free preview before you pay.
Start building free →