How to position your startup against much bigger competitors (and win)

The competitor has ten times the headcount and a brand budget we can't see the top of, and the instinct is to fight on features.

Add more. Ship faster. Price under them.

That instinct will kill us.

Incumbents win feature wars. They have the engineering bench, the integration library, and the sales team to out-execute anyone in a straight comparison.

But their size isn't a wall to climb. It's a stack of commitments they already made, in writing, to somebody else.

Their pricing, their implementation process, their support model, and their roadmap were all shaped by their largest accounts. Those choices are load-bearing now. They can't quietly reverse one of them for us.

So there are things we can say honestly that they can't say back. Call those structural claims. A structural claim is one the incumbent could only match by dismantling the business they've spent a decade building.

Three of them are available to almost any smaller company.

---

The customer they can't keep

Large vendors are built for large customers. That's a real choice with real consequences, and it leaves a gap behind it.

The people in that gap are our market.

Targeting "the SMB segment" is just a demographic with a nicer name. What we want is the specific trigger that makes a buyer a bad fit for the incumbent, and then the whole position built on that one trigger.

So we ask who buys the big player and churns inside eighteen months. Who never gets through the trial because setup assumes an IT team. Who keeps choosing us anyway, and what all of them have in common.

That pattern is the ICP, and the ICP is the anchor.

Intercom did this against Salesforce. Companies that talk to their users in real time need something different from companies managing enterprise pipelines, and Salesforce's architecture was never going to serve the first group well.

Notion did it against Confluence. Confluence was built for IT and engineering teams who wanted structure and permissions, and Notion argued that most teams want a workspace that bends to them instead.

Different buyer. Different trigger. A completely different company.

The work is two sets of interviews. Twenty customers who left the incumbent, asked what they kept trying to configure that never worked.

Then twenty of our best customers, asked what they used before and why they gave us a shot at all. Somewhere in those forty conversations is one thread.

Describe the situation, not the demographic. "Series A companies with a product-led motion" is a segment anyone can buy a list of. "Companies where everyone logs into the product and two people hold the budget" is a situation, and situations are what generate positioning.

---

Size as the liability

Incumbents sell scale as a strength. More integrations, a larger support org, proven at the top of the market.

Every one of those is also a cost the buyer pays, and for a wrong-fit customer it's the only thing they'll remember.

Long implementation timelines. Roadmaps that move at the speed of enterprise consensus.

Tiered support queues. Pricing built around their cost structure rather than ours.

That's structural rather than spin, which is exactly why we're allowed to say it out loud.

The frame that works is a claim about fit. Built for how your team works, rather than how a five-thousand-person company works.

Fit is the one thing an incumbent can't offer the wrong segment no matter how good the product gets.

Language that survives a reference call sounds like this:

• "Most teams are live in two weeks. Enterprise platforms take a quarter."
• "You get an onboarding call instead of a ticket queue."
• "When the product changes, you feel it inside a sprint."
• "Your team chose this. Their team was told to use it."

Each one describes the experience of being our customer. The experience is where the wedge goes.

The discipline is to never overstate. "We move faster" is available to anyone with a keyboard. "Teams are operational in fourteen days because we stripped out the configuration layers they don't need" is a structural claim, and it holds up when a prospect calls a reference to check.

Ask a buyer to tell the vendors in a category apart and most can't. The ones who break through said something specific about who they're for and who they aren't.

---

Naming the problem

The hardest version of this is category design. We stop competing inside their category and name a problem that doesn't have a good name yet.

Gong stepped out of the CRM comparison and put Revenue Intelligence on the table. Every sales tool then had to answer whether it was that or not, and Gong got to answer first. Drift did the same thing to contact forms with Conversational Marketing.

It works because a comparison needs a shared frame. When a buyer says they're evaluating us against a named incumbent, the frame is already loaded, and the only move left is to change it before the evaluation starts.

The practical version is short. Find the problem our best customers have that no category names, give it a name that makes the solution obvious, and then write about the problem instead of the product until the name sticks.

The trap is picking a jargon term for what we already do. Category design needs a real problem with no word attached, and the test is whether buyers say "yes, that's the thing I've been trying to describe."

When it lands, we stop having to win comparisons, because we've become the thing everyone else is compared against.

---

One move at a time

Most early companies shouldn't run all three.

Own the underserved customer when we're early and need a beachhead to dominate before we expand. Turn size into a liability when we're already winning some deals and losing the narrative in others, because that's the stage where we have proof to point at. Design a category when we can fund a long story, which takes years rather than quarters and needs sustained content and customer evangelism behind it.

Running all three at once funds none of them properly.

---

The claim that holds

Everyone says "purpose-built." The phrase is worn through.

A structural claim has to pass two questions. Could a competitor say this honestly? If yes, it's too vague.

Do three customers say it back to us in their own words? If not, it's an aspiration wearing positioning clothes.

And then a third question, the one most companies fail. Does the claim make clear who we're not for?

Good positioning excludes somebody. Positioning that works for everyone works on nobody.

Run the current positioning through those. Most early companies fail at least two, which is ordinary and entirely fixable.

The incumbent can outspend us on every channel there is. They can't be honest about who they're not built for, because they told those buyers yes years ago.

Make the claim they'd have to take themselves apart to copy.

What to do next

If we're losing deals to a bigger name and the answer keeps coming back as "more features," the problem sits upstream of the roadmap. A positioning audit finds the claim only we can make honestly, and a messaging sprint gets it into the website and the sales conversation before the next quarter starts.

If that's where you are, start here. The first conversation is free.

For a complete overview of B2B SaaS positioning strategy, including frameworks, common failure patterns, and how positioning connects to messaging, ICP, and GTM, see the B2B SaaS Positioning Guide.