This piece sits in Polymorph’s series on the seven fundamentals of great products. We’re on the fourth one: you are always competing, even when the slide deck says you’re “category creating.”
Your competitor is often inertia, not another business with a sharper product. That changes how you map alternatives, price risk, and forecast adoption.
I first wrote this as the 4th fundamental on LinkedIn. “We have no competition; this idea is totally new” is almost always wrong. People already manage the problem somehow: a spreadsheet, a hack, an old tool, or doing nothing because change feels riskier than the pain.
You’ve validated value in product validation before build. Competitive analysis asks the next hard question: what are you actually displacing, and why would anyone move now?
TL;DR: CB Insights highlights bad timing or macro conditions in 29% of analysed shutdowns and unsustainable unit economics in 19%. Markets and budgets can say no even when the demo sparkles. 70% cite running out of capital, framed as the terminal event, not the root cause. Competitive analysis has to explain why the world says no, not only which vendor you dislike.
Who are you really competing against?
Five rivals show up in almost every B2B build we’ve seen. Named logos are only one of them.
- DIY hacks: Spreadsheets, email threads, tribal knowledge. Ugly. Often “free” in the budget sense. Paid for in attention and error rates.
- Partial tools: Legacy systems stitched together with scripts and patience. “Good enough” wins until pain crosses a threshold someone will fund.
- Named vendors: The logos on your battlecard. Real. Incomplete if this is all you map.
- Adjacent solutions: Free tools, open-source scripts, niche vertical platforms. Buyers compare you to work, not to your favourite competitor slide.
- Non-consumption and inaction: The job isn’t getting done well, or isn’t getting done at all. Doing nothing is rational when onboarding risk, change management, and reputational risk feel larger than the pain.
Clayton Christensen and co-authors put nonconsumption at the centre of Jobs to Be Done: successful innovations help people make progress while dealing with the anxieties and inertia holding them back. In the Harvard Business School write-up of the framework, Christensen notes that somewhere between 75% and 85% of new products fail financially because they don’t target a job people are actually trying to get done (HBS Online).
That’s the competitive frame we use: you’re not only beating Vendor B. You’re competing for a job that already has a hired solution, including “hire nobody.”
Mapping questions that keep you honest
For each of the five rivals above, answer these before you ship another feature matrix.
- What does the buyer do today when this problem shows up?
- What does that cost them in time, risk, or political capital?
- What would they have to give up to switch (habits, integrations, face)?
- Who gets blamed if the switch goes badly?
- Why would this quarter be different from the last three “we’ll revisit” cycles?
- If we disappeared, what would they hire instead, including nothing?
If you can’t answer those with artefacts from discovery and behavioural research, your competitive analysis is still a logo collage.
How do you map competition beyond a feature matrix?
Alternative workflows
Journey-map the current process end to end. Where does work actually happen? Who owns the exceptions? The spreadsheet handoff is usually more important than the vendor row.
Adjacent solutions
List free and niche tools with the same honesty you’d give a Series B rival. Buyers don’t care that you don’t put them on the slide.
Non-consumption
Sometimes the job is half-done. Sometimes it waits. Both are competitive realities. Christensen’s SNHU example in the HBR Jobs to Be Done piece is blunt: the online programme wasn’t only competing with other colleges. It was competing with nothing: nonconsumption, which made the market look small until they designed for the job of the nonconsumer.
Illustration
In research for a consumer app aimed at busy parents, most users agreed the problem was real. When asked to commit twenty minutes a day, many said they didn’t have the bandwidth after childcare, meals, and everything else. The product wasn’t losing to “another app” first. It was losing to time and energy. That is competition too.
Why do timing and economics keep showing up next to PMF?
CB Insights lists poor product–market fit in 43% of cases, bad timing / macro in 29%, and unsustainable unit economics in 19%. Founders often cite more than one. The lesson for competitive analysis: adoption is not only “we beat vendor B.” It is “we beat wait.”
Budgets freeze. IT capacity fills up. Champions leave. Macro conditions make “good enough” look wise. Your feature table doesn’t update for any of that unless you put calendar and risk on the map.
When capital runs out, it’s tempting to blame fundraising alone. CB Insights frames the 70% “ran out of capital” figure as the terminal event. PMF, timing, and economics explain why runway disappeared. Competitive analysis that ignores those forces is incomplete on purpose.
What does honest competitive mapping change in the room?
It reframes sales and product conversations. You stop asking only “why would they pick us over X?” and start asking “why would they change at all, and now?”
That question connects straight back to validation and forward to differentiation. Your wedge has to beat inertia, not just a rival’s checklist.
Example
A team selling workflow automation kept losing to “we’ll revisit next quarter.” When they mapped the account, the real rival wasn’t Vendor B. It was IT capacity: no onboarding slots for nine months. Naming that shifted the pitch from feature parity to a pilot sized to the calendar, and the champion could finally explain why now to leadership.
We’ve found that the teams who win these deals usually shrink the ask until it fits the buyer’s risk budget. Bigger vision. Smaller first step. Same job.
A practical artefact for the next sales or product review: one page with five columns (DIY, partial tools, named vendors, adjacent, nonconsumption). For each column, one sentence on “how they win today” and one on “what would have to be true for us to displace them this quarter.” If a column is blank, you’re not done.
What failure modes show up when teams ignore non-logo competition?
- Surprise losses to “no decision.” Pipeline looks healthy until everything stalls without a competitor win.
- Discounting as a crutch. Price cuts try to compensate for unclear switching value.
- Parity roadmaps. You chase Vendor B while Excel and inaction still own the workflow.
- Battlecards without switching costs. Features listed. Risk to the buyer ignored.
- Category creation theatre. “No competitors” on the slide, then six months of losses to wait.
If your competitive review never mentions spreadsheets, capacity, or “do nothing,” you’re reviewing vendors. You’re not reviewing reality.
CB Insights reports 70% of analysed shutdowns involved running out of capital, often as a terminal event, alongside poor product–market fit (43%), bad timing or macro (29%), and unsustainable unit economics (19%). Christensen’s Jobs to Be Done work treats inertia and nonconsumption as central to why people hire (or refuse) a product. For new products, competitive analysis should treat budget cycles, risk appetite, and status quo workflows as first-class competitors, not afterthoughts behind named rivals.
Where next?
Sharpen your wedge in product differentiation strategy. If scope is fighting you, read minimum viable scope and roadmaps. Full loop: seven fundamentals.
If you want competitive mapping tied to why customers change, talk to Polymorph: we work with founders, product leads, and executive teams to validate, build, and improve software that earns its place in the business.
FAQ
Is Excel really a competitor?
Often, yes, because it’s trusted, flexible, and already paid for in attention. Feature parity with Vendor B doesn’t displace a spreadsheet people already trust.
How do we research inertia without a lab?
Look at sales stages: stalled pilots, “revisit next quarter,” and champion turnover. Qualitative stories plus pipeline patterns beat guessing.
What is the biggest mistake in competitive battlecards?
Feature parity tables without switching costs and risk to the buyer. The card should answer why change is rational now.
How does this link to differentiation?
You can’t differentiate credibly until you know what you must beat, including nothing. That’s the bridge into product differentiation strategy.
What should we read next?
Product differentiation strategy.
