Military & Conflict
Section 1
Core Idea
Crippling means targeting the critical capability that an opponent depends on — not to destroy them outright, but to degrade their ability to compete effectively. In military terms, it's hitting supply lines, communications, or key infrastructure rather than engaging the main force directly. In business, it's attacking a competitor's core dependency: their distribution channel, their key supplier relationship, their talent pipeline, or their unit economics. The core idea: you don't need to defeat an opponent everywhere — just disable the one thing they can't function without.
Free playbook
Get The Business Model Playbook
58 business models, one visual page each: how the money flows, the metrics that matter, and who runs it. Free when you join the Faster Than Normal email.
Free. No spam. Unsubscribe anytime.
Section 2
How to See It
Competitive Strategy
You're seeing Crippling when a company targets a competitor's most critical dependency — signing an exclusive deal with their key supplier, poaching their core engineering team, or undercutting the single product that funds everything else.
Platform & Ecosystem
You're seeing Crippling when a platform changes terms or access in a way that breaks the business model of companies built on top of it. The platform doesn't compete directly — it disables the dependency.
Section 3
How to Use It
Identify your competitor's critical dependencies — the one or two things without which their model breaks. Ask: what would happen if they lost this supplier, this channel, this talent pool, this regulatory status? Then consider whether you can ethically and legally weaken that dependency. Defensively, identify your own critical dependencies and diversify or protect them.
Decision filter
"What is the one thing our competitor can't function without? Can we weaken or remove it? And what is that one thing for us — and how exposed are we?"
As a founder
Map your own critical dependencies and your competitors'. Protect yours through diversification and redundancy. When competing, look for the leverage point where a single move degrades an opponent's ability to function — that's the crippling move.
Section 5
Founders & Leaders
Jeff BezosFounder, Amazon
Bezos systematically crippled competitors not by attacking their products but by undermining their cost structures and distribution advantages. Amazon's investment in logistics, Prime membership, and AWS gave it structural cost advantages that competitors couldn't match. When Amazon entered a category with lower prices and faster delivery, it didn't need to outperform on product — it crippled the competitor's unit economics and customer acquisition. Founders can apply this by identifying the structural advantage their competitor depends on and finding ways to neutralise it. Don't fight on their terms; remove the foundation their model stands on. The most effective competitive moves often target the dependency, not the product.
Section 7
Connected Models
Reinforces
Choke Point
A choke point is a narrow dependency through which value must flow. Crippling is the act of targeting that choke point. Together they describe both the vulnerability and the attack.
Reinforces
Theory of Constraints
Every system has a bottleneck that limits throughput. Crippling targets that bottleneck in a competitor's system. Use theory of constraints to identify where the crippling blow would have the most impact.
Leads-to
Decapitation
Crippling degrades capability; decapitation removes leadership or the decision-making centre. Crippling often precedes decapitation — weaken the system first, then remove its ability to adapt.
Section 8
One Key Quote
— B.H. Liddell Hart"The profoundest truth of war is that the issue of battle is usually decided in the minds of the opposing commanders, not in the bodies of their men."
Section 11
Summary & Further Reading
Crippling means targeting the critical dependency an opponent can't function without. Identify the choke point in their model — supply, distribution, talent, economics — and weaken it. Defensively, map and protect your own critical dependencies. You don't need to win everywhere; just disable the thing they can't replace.