A competitive slide is not a competitive strategy.
Most battlecards describe features, pricing, and objection handling. Useful, but insufficient. GTM strategy needs a theory of how the company enters the market, wins early, survives response, and builds durable advantage.
The real competition is not always the named competitor. It may be an incumbent suite, an internal team, a spreadsheet, an agency, a services firm, a workflow habit, or the buyer's decision to do nothing.
Start with the wedge
A wedge is the narrow entry point where the company can win despite limited resources.
Good wedges have several traits:
- painful problem for a specific segment
- clear reason incumbents under-serve it
- fast path to proof
- buyer who can act
- expansion path after initial value
- defensibility that improves with use, data, workflow depth, or ecosystem position
A wedge is not just a small feature. It is an entry strategy.
Bad wedge: "We are cheaper." That may get attention, but it is rarely durable unless the cost structure is fundamentally different.
Better wedge: "We solve a high-urgency workflow inside a segment incumbents treat as an edge case, and each deployment creates data and process depth that supports expansion."
Incumbents have incentives
Do not assume incumbents are stupid. Ask why they have not solved the problem already.
Possible answers:
- the segment is too small for their current model
- the use case threatens their existing economics
- their architecture makes the workflow hard to support
- they sell to a different buyer and ignore the user pain
- their roadmap is optimized for large accounts, not speed
- the problem requires services or domain depth they do not have
- they could solve it, but not without confusing their positioning
This matters because it predicts response.
If an incumbent can neutralize the wedge with a simple feature and stronger distribution, the wedge may be weak. If solving the wedge would force the incumbent to change architecture, pricing, buyer, or business model, the wedge may be more durable.
Substitutes are often more important than competitors
Buyers rarely compare exactly the way vendors want.
They may compare you against:
- doing nothing
- hiring another person
- outsourcing to an agency
- building internally
- using spreadsheets
- extending an existing system
- changing the process instead of buying software
These substitutes shape positioning and sales design.
If the real alternative is an internal analyst with spreadsheets, feature comparisons against software competitors will miss the point. The sales case should address speed, accuracy, resilience, and opportunity cost. If the alternative is an agency, the argument may be control, scalability, and institutional learning. If the alternative is doing nothing, urgency matters more than differentiation.
The competitive response memo
Before scaling a wedge, write a memo:
1. Current wedge
Where do we enter, with which buyer, against which pain?
2. Alternatives
What does the buyer do today? Include substitutes, not just vendors.
3. Why alternatives fail
What is structurally weak about the current approach?
4. Why we win now
What proof, capability, distribution, or timing makes us credible?
5. Incumbent response
How could incumbents respond? Feature copy, bundling, pricing, partner pressure, roadmap acceleration, narrative attack.
6. Durability
What gets stronger as we win? Data, workflow depth, integrations, references, network, switching cost, ecosystem position.
7. Countermoves
What should we build, message, or distribute before response arrives?
8. Exit criteria
What evidence would show the wedge is too weak or too expensive?
This memo is more valuable than a feature matrix because it forces the team to think in time.
Competitive strategy affects sequencing
If the wedge is easy to copy, speed and distribution may matter more. If the wedge requires deep implementation knowledge, services design may be strategic. If the wedge depends on a neglected buyer, positioning should emphasize that buyer's specific problem. If the wedge threatens an incumbent's economics, expect aggressive response only after the market becomes visible.
Sequence accordingly.
Sometimes the right move is to stay narrow longer and build proof density before announcing a bigger category. Sometimes the right move is to expand quickly before incumbents notice. Sometimes the right move is to partner with ecosystem players before a suite vendor closes the door.
Competitive strategy is not separate from GTM. It shapes the order of moves.
Do not confuse differentiation with durability
Differentiation explains why the buyer should choose you now. Durability explains why the advantage can persist.
A company can be differentiated but not durable:
- better UX that can be copied
- cheaper pricing that can be matched
- narrow feature advantage that incumbents can add
- sharper message that larger competitors can adopt
A durable advantage usually comes from harder-to-copy systems:
- proprietary data
- workflow depth
- switching costs from embedded process
- ecosystem relationships
- trusted community access
- implementation expertise
- compounding customer proof
- product architecture that supports the use case better
GTM strategy should know which one it has. Pretending a feature gap is a moat creates false confidence.
Example: when the incumbent will not chase
A startup sells software for a narrow operational workflow in regional logistics companies. Large enterprise platforms technically could build the feature. But their sales motion targets global accounts, their implementation model is too heavy, and their roadmap is shaped by large enterprise requests.
The startup's wedge is not that incumbents are incapable. It is that incumbents are misaligned.
The GTM should exploit that:
- focus on regional operators who are ignored by enterprise vendors
- use implementation speed as proof
- build references inside the regional network
- avoid enterprise roadmap commitments too early
- expand into adjacent workflows once embedded
The wedge is durable only if the startup keeps strengthening the advantages incumbents do not want to copy.
Example: when the incumbent does respond
A startup sells usage-based workflow automation to mid-market finance teams. It wins because setup takes days, the product handles messy departmental approvals, and finance operators can prove savings before IT gets involved.
An incumbent suite notices. It copies the visible feature, bundles it free into a broader contract, tells procurement the startup creates vendor risk, and pressures implementation partners to avoid recommending it.
The countermove is not to argue feature parity. The startup should move the fight back to the wedge:
- publish time-to-value proof from comparable mid-market finance teams
- arm champions with switching-risk and implementation-speed evidence
- deepen workflow templates the suite cannot easily support without services work
- cultivate independent advisors who care about the neglected mid-market use case
- package expansion around adjacent finance workflows after the first proof point
The incumbent is trying to reframe the decision as suite consolidation. The startup has to reframe it as speed, operator adoption, and proof in a workflow the suite treats as secondary.
The competitive test
Competitive strategy should answer four questions:
- What narrow fight can we win now?
- Why are alternatives weak for this buyer?
- How will competitors respond if we are right?
- What gets stronger every time we win?
If the answer is only "we have a better product," keep working.
Better products lose all the time when distribution, buyer trust, economics, and incumbent response are misunderstood.
