Coopetition
Coopetition, popularized by Adam Brandenburger and Barry Nalebuff in their 1996 book 'Co-opetition,' is the practice of cooperating with competitors in some dimensions while competing in others. The framework's key tool is the Value Net: you simultaneously have customers, suppliers, competitors, and complementors, and the same firm can occupy multiple roles. Apple competes with Samsung in smartphones AND buys $10B+/yr of Samsung components. Microsoft competes with Salesforce in enterprise CRM-adjacent territory AND integrates Salesforce into Teams. The strategic question coopetition forces is no longer 'who is my competitor?' but 'in which dimension is this firm a competitor and in which is it a complementor — and what posture should I take in each?' The KnowMBA POV: coopetition only creates value when both parties have a credible BATNA (best alternative to negotiated agreement). Without one, 'cooperation' is just managed dependence.
The Trap
The trap is asymmetric coopetition without acknowledging the asymmetry. When one party desperately needs the relationship and the other doesn't, 'partnership' is a polite word for 'leverage waiting to be applied.' The smaller party builds infrastructure on top of the larger party's platform, the relationship hums for two or three years, and then the larger party either acquires the smaller (if it's worth it) or unilaterally changes terms (if it isn't). Coopetition without a credible BATNA — your ability to walk away — is just dependence. The discipline is to invest in your BATNA continuously, not just at the negotiation table.
What to Do
Map every important commercial relationship using the Value Net: in which dimensions is this firm a customer, supplier, competitor, complementor? Then for each, ask three questions: (1) What's our BATNA in this relationship — could we replace them in 6 months? (2) What's their BATNA — could they replace us? (3) Where the BATNAs are asymmetric, who's holding the leverage? Build coopetitive relationships only where both BATNAs are credible. Where they're not, either invest to create one (build the alternative) or accept the relationship is dependence and price-protect accordingly.
In Practice
Apple and Samsung is the textbook coopetition case. Samsung Display and Samsung Semiconductor have, in some years, supplied an estimated $7-10B+ in OLED panels, NAND flash, and DRAM to Apple — even as Samsung Mobile's Galaxy line is the iPhone's most direct global competitor. Both firms benefit: Apple gets best-in-class component supply at scale, Samsung's component businesses get a massive anchor customer that funds R&D. Both firms are also constantly investing in their BATNAs — Apple has aggressively second-sourced OLEDs to LG Display and BOE specifically to reduce Samsung-Display dependence, and Samsung Mobile competes with iPhone on its own merits without component-cross-subsidies. The coopetition works because each side has a credible exit. Source: widely reported industry analysis (Apple supplier disclosures, Counterpoint Research, DSCC).
Pro Tips
- 01
Coopetition agreements should always specify what happens when the cooperative dimension and the competitive dimension collide. The contract drafted in the honeymoon phase, when everyone's optimistic, is the one you'll live by during the divorce — when the two firms' interests diverge for the first time.
- 02
The most stable coopetition is between two firms whose competitive overlap is small relative to their complementary overlap. Microsoft + Salesforce is more stable than Microsoft + Google because the competitive surface area is smaller relative to the cooperative one.
- 03
Treat every coopetition relationship as an option, not a marriage. Build switching capability for everything you depend on; encourage your partner to invest in their independence too. Healthy coopetition runs on mutual ability to walk, not on lock-in.
Myth vs Reality
Myth
“Coopetition is a soft, win-win strategy that avoids the harshness of pure competition.”
Reality
Coopetition is harder than pure competition because it requires you to simultaneously hold two contradictory postures toward the same firm without confusing the organization. Sales teams must compete against firms that engineering must integrate with. Most companies fail at coopetition because they can't sustain the cognitive dissonance and the relationship collapses into either pure competition or naive partnership.
Myth
“If both firms benefit, coopetition is sustainable.”
Reality
Mutual benefit at signing tells you nothing about sustainability. Coopetition collapses when one side's competitive position deteriorates and they unilaterally change the terms. The KnowMBA test isn't 'do both benefit today?' — it's 'does each side have a credible exit if the other becomes hostile tomorrow?'
Try it
Run the numbers.
Pressure-test the concept against your own knowledge — answer the challenge or try the live scenario.
Knowledge Check
Your B2B SaaS company has been approached by Microsoft to deeply integrate your product into Teams as a featured app. The deal would 10x your distribution. Microsoft also has a small internal team building competitive functionality. Which condition would make this coopetition genuinely valuable rather than a slow acquisition trap?
Decision scenario
The Platform Embrace
You're CEO of a $90M ARR vertical SaaS company in field-service management. Microsoft has approached you about a deep strategic partnership: featured Teams app, Microsoft 365 marketplace prominence, joint enterprise sales motions, and a 15% minority equity investment at a generous valuation. The catch (not contractual but obvious): Microsoft has a small internal Dynamics 365 team building adjacent functionality. The partnership would 4x your enterprise pipeline within 18 months but make you visibly dependent on a competitor.
ARR
$90M
Enterprise Pipeline (current)
$140M
Microsoft-channel pipeline (projected w/ deal)
+$560M over 18mo
Your BATNA today
Multi-channel: AWS Marketplace, direct, partner network
Decision 1
Your CFO and Head of Sales want to sign immediately — the pipeline impact is enormous and the equity investment validates the company. Your CTO is uneasy: the architecture work to deeply integrate with Teams is significant and creates technical lock-in. Your Head of Strategy notes the Microsoft Dynamics adjacency. You have one negotiation cycle to set the terms.
Sign the deal as proposed. Take the equity, integrate deeply with Teams, accept that >50% of revenue will route through Microsoft within 24 months. Microsoft 'doesn't compete in field-service today' so the risk feels manageable.Reveal
Counter-propose: accept the partnership, accept the equity, but with explicit BATNA-preserving terms — (a) cap Microsoft-channel revenue commitments so you're contractually free to invest in alternative channels, (b) maintain a parallel deep integration with at least one major non-Microsoft platform (e.g., Salesforce or ServiceNow), (c) preserve product roadmap independence in writing, (d) Microsoft equity is non-voting and cannot block strategic alternatives. Walk if Microsoft refuses these terms.✓ OptimalReveal
Related concepts
Keep connecting.
The concepts that orbit this one — each one sharpens the others.
Beyond the concept
Turn Coopetition into a live operating decision.
Use this concept as the framing layer, then move into a diagnostic if it maps directly to a current bottleneck.
Typical response time: 24h · No retainer required
Turn Coopetition into a live operating decision.
Use Coopetition as the framing layer, then move into diagnostics or advisory if this maps directly to a current business bottleneck.