The most uncomfortable version of competitive analysis is the one where the competitor is genuinely better on the obvious axes. They have more domain expertise. They have deeper integrations with the tools the customer already uses. They have institutional credibility that takes years to build. The instinct is to find some feature they don’t have and lean on it, or to invoke pricing, or to claim a vague differentiation around “focus” or “agility.” None of these usually win.

The move that does win, when it works, is to compete on an axis the competitor cannot structurally occupy. Not a different feature — a different shape of the product entirely. The enterprise SaaS platform cannot ship as a desktop tool without rebuilding its delivery model. The cloud-multi-tenant agentic system cannot run locally without breaking its architecture. The sales-led product cannot reach the individual professional without rewriting its go-to-market. These are not features the competitor is missing. They are constraints baked into what the competitor is.

This is the framework for finding the narrower wedge. List the competitor’s strengths honestly. Then list the constraints that come with those strengths — the things they had to give up to get the strengths. The constraints define the wedge. A platform that integrates deeply with enterprise systems cannot also be the lightweight thing the individual practitioner installs in five minutes. A tool with sales-led pricing cannot also serve the buyer who would never enter a procurement process. A cloud SaaS cannot also be the tool that runs on documents the user refuses to upload anywhere.

The narrower wedge is not smaller in any way that matters. It is the same job, done for a structurally different user, in a structurally different shape. The work the tool does — extracting data from documents, normalizing inputs, producing structured output — can be identical. What differs is who can reach it, how they pay for it, where it runs, and what social context the adoption happens in. A user who cannot or will not adopt the competitor is a user the competitor cannot serve. That user has the same problem and is worth the same money to solve it.

The strategic discipline is to stay in the wedge and resist the temptation to grow toward the competitor. Every time the wedge tool adds a feature that moves it closer to the competitor’s territory, it gives up some of the structural distinction that made it viable. The cloud sync feature seems harmless until it becomes the reason the privacy-conscious buyer leaves. The enterprise SSO seems harmless until it becomes the reason the procurement process now applies. The integrations seem harmless until they make the tool indistinguishable from the platform it was supposed to be the alternative to.

The narrower wedge also has unexpected leverage in distribution. The pre-qualified communities that use the alternative tools recognize the structural distinction instantly. They don’t need a long explanation of why this is different from the platform. They see “runs locally, in Claude Desktop, on documents that never leave your machine” and the entire pitch is delivered. The competitor’s marketing budget is irrelevant to that conversation because the distinction is not a feature the marketing could communicate around — it’s the shape of the product.

The deeper observation is that a narrower wedge against a much larger competitor is often a stronger position than a broader product against a smaller field. The strength comes from the impossibility of the competitor following. The wedge tool wins not because it has more resources, but because the competitor’s resources are pointed in a different direction by their own architecture.

+++