How do you position against a bigger competitor?
Competing against a larger player is winnable, but only if you stop trying to beat them at their own game. The move is to identify what the incumbent is structurally overlooking—because of their size, their business model, or the customers they've already optimized for—and build precisely there. A crowded market with a big player in it is actually a green signal: it confirms demand exists and that no one has fully solved the problem yet.
A crowded market is evidence, not a warning
Most founders treat the presence of a well-funded incumbent as a reason to pivot. That instinct is backwards. A dominant competitor proves there's a real market—people are already paying for a solution, even an imperfect one. The question is never 'can I beat them on every dimension?' but 'what dimension are they ignoring because of who they are?'
Paul Graham's observation about startup ideas is instructive here: the best entry point isn't 'we'll make a better version,' it's being able to articulate precisely what the incumbent is overlooking—and why. That 'why' matters. If they're overlooking something because it's genuinely unprofitable or technically impossible, that's a dead end. But if they're overlooking it because their existing customer base, their revenue model, or their organizational incentives make it hard to address, that's your opening.
Incumbents often can't follow you into that space even if they see you coming. A company with 10,000 enterprise customers can't suddenly rebuild its product for a developer audience without alienating its existing base. That structural constraint is your moat, at least in the early stage.
Find what they didn't have the courage to follow through on
Big competitors frequently understand the direction a market is heading before small players do—they just can't act on it. Their existing business creates drag. They've made architectural decisions, pricing commitments, and sales org structures that make certain moves politically or economically impossible internally. The sharpest positioning isn't 'we're different,' it's 'we're what they would have built if they'd followed their own logic all the way.'
This reframe changes how you talk to customers. Instead of asking prospects to bet on an unknown challenger, you're telling them: 'The big player saw this problem. They just couldn't solve it without breaking something else.' That's a much more convincing story than a feature comparison. It also means you don't have to manufacture differentiation—you just have to execute on the gap the incumbent created by compromising.
Garry Tan's approach to positioning gstack in the developer tools space illustrates this in practice. Rather than trying to match established players across every feature, the design language—monospace fonts, utilitarian density, CLI-first aesthetics—signals to a specific developer audience: this was built by someone who thinks like you. That kind of authentic alignment with a specific user's identity is something a general-purpose product can't fake.
Own a specific customer segment completely, not the whole market partially
The biggest mistake in competing against incumbents is trying to be a horizontal alternative. You can't out-resource them across the whole market. The move is vertical dominance: own one specific segment so completely that the incumbent can't justify the engineering and sales cost to come after you. When you're the obvious best choice for a narrow, high-value slice of the market, you build revenue and reputation that lets you expand later.
In developer tools, this looks like: don't build 'an AI tool for developers.' Build the best possible solution for the specific workflow where a specific type of developer wastes the most time. Garry Tan's diagnostic framing is useful here—push yourself to name the exact task, the exact user, and the current cost of not solving it. Vague positioning against a big competitor gives the incumbent room to say 'we do that too.' Precise positioning makes that claim implausible.
The goal in year one isn't to be on everyone's radar. It's to become indispensable to a small group who will evangelize for you. That word-of-mouth within a tight community is something no marketing budget can replicate, and it's disproportionately available to focused startups.
Make your constraints your brand
Startups often hide their smallness. That's a mistake. Customers who are frustrated with large vendors are often frustrated because of scale—slow support, generic features, bureaucratic roadmaps. Your smallness means you move faster, care more about individual customers, and can build things that don't fit the incumbent's product strategy. That's not a weakness to apologize for; it's the core of your positioning.
The design philosophy visible in Garry Tan's gstack project captures this instinct well: 'CLI heritage IS the brand.' The product isn't trying to look like an enterprise SaaS tool—it leans into the aesthetic and values of its specific user base. That authenticity is only possible when you're small and focused. The moment you try to look like the incumbent, you lose the one advantage you actually have.
Practically, this means: in your sales conversations, acknowledge the competitor directly. Tell prospects what you don't do, and why that makes you better for them. Customers who need the full incumbent suite will self-select out—and that's fine. The ones who stay are your real market. Clarity about who you're not for is as important as clarity about who you are for.
“You don't need to worry about entering a crowded market so long as you have a thesis about what everyone else in it is overlooking.”
— Paul Graham, source
The one thing to do
Write one sentence that names exactly what your biggest competitor is structurally unable to do for your specific user—and use that as your positioning anchor for every sales conversation this week.
Frequently asked questions
Should I mention competitors by name in my positioning?
Yes, selectively. Naming the incumbent validates that the market is real and positions you as a credible alternative rather than a side project. Be specific about the gap you're filling, not just that they're 'big and slow'—that's too generic to be convincing.
What if the big competitor just copies what we're doing?
If you've chosen your segment well, copying you hurts them. A large B2B SaaS vendor can't rebuild for a developer-first audience without confusing its existing enterprise buyers. Pick a position that's structurally uncomfortable for the incumbent to occupy, and their size becomes a liability.
How do I know if my differentiation is real or just a story I'm telling myself?
Talk to customers who tried the incumbent and left—or stayed despite frustration. If they describe the same gap you're solving, the differentiation is real. If they've never heard of the problem you're solving, you may be telling yourself a story.
Is it better to compete on price against a bigger player?
Rarely. Price competition against a well-capitalized incumbent is a race you'll lose unless your cost structure is fundamentally different. Compete on fit—being the exact right tool for a specific user—not on being cheaper at a general solution.
Sources
- gstack: DESIGN.md — Garry Tan
- The Origins of Wokeness — Paul Graham
- Quotes — Paul Graham
- Defining Property — Paul Graham
- How to Get Startup Ideas — Paul Graham