Book 1: Foundations
Ecosystem ThinkingNew
Understanding Markets as Living Systems
Chapter 8: Ecosystem Thinking
Part 1: The Biology of Ecosystems
The Salmon That Feed The Forest
Watch the rivers of Alaska in late summer. The water turns red - not from algae, but from millions of Pacific salmon fighting their way upstream. Battered and exhausted, driven by ancient programming, they travel hundreds of miles inland. They leap waterfalls. They fight currents. They exhaust themselves completely.
Most never make it. They die by the thousands - torn apart by predators, beaten against rocks, spent from the journey. Their bodies pile up on riverbanks and in eddies. The smell of decay fills the air. Eagles circle overhead. Bears wade into the current, claws extended.
This looks like waste. Carnage. The end of a species' lifecycle.
It's not. It's infrastructure.
The survivors spawn. Then they die too.
In Alaska's Tongass National Forest, biologists noticed something strange: the trees growing along salmon streams - 50 to 80 feet from the water - were taller, thicker, and healthier than trees further inland. Same soil. Same rainfall. Same sunlight. But trees near salmon streams had 20-25% more growth.
The mechanism: nitrogen isotopes.
Ocean-derived nitrogen has a distinct isotopic signature. Scientists tested the trees' rings. Up to 80% of the nitrogen in streamside trees came from the ocean. But salmon die in the stream, not under forest canopy. How does ocean nitrogen travel 80 feet inland?
Eagles and bears.
Grizzlies catch salmon, drag them into the forest to eat safely away from competing bears, consume the protein-rich flesh, and leave the nitrogen-rich carcasses. Eagles do the same. Ravens, gulls, and insects join in. Decomposition releases nitrogen. Roots absorb it. Trees grow taller.
Remove the salmon, and the forest dies.
This is a keystone species: an organism whose impact on the ecosystem is disproportionately large relative to its abundance. Salmon aren't the most common species in this ecosystem - trees outnumber them enormously. But salmon are the mechanism connecting ocean nutrients to forest growth.
Keystone species create trophic cascades: effects that propagate through multiple levels of an ecosystem. Salmon → predators → nutrient dispersal → tree growth → forest canopy → understory shade → berry abundance → small mammal populations → predator diversity. One species removal collapses multiple dependent relationships.
In Yellowstone National Park, wolves were extirpated in 1926. For 70 years, elk populations exploded without predation pressure. Elk overgrazed willow and aspen in valleys. Without willows stabilizing riverbanks, erosion increased. Rivers widened and meandered. Beavers - which need willows for dams and food - disappeared. Without beaver dams, wetlands dried up. Songbird diversity collapsed. The entire ecosystem reorganized around wolf absence.
Wolves were reintroduced in 1995. Within a decade, elk populations dropped and shifted behavior - they avoided valleys where wolves hunt. Willows and aspens regrew. Beavers returned. Rivers showed signs of narrowing and stabilization, though hydrologists debate whether this resulted primarily from wolf reintroduction or from other factors like changing precipitation patterns and beaver activity. Regardless, the broader ecosystem transformation was unmistakable. Songbird diversity increased. Wetlands reformed.
One species reintroduced. Entire ecosystem transformed.
This is ecosystem thinking: understanding that organisms don't exist in isolation. They exist in networks of energy exchange, resource flow, and mutual dependency. Change one node, and effects cascade through the system.
The Business Parallel:
Just as salmon connect ocean nutrients to forest growth through predator intermediaries (bears, eagles), keystone companies connect distant resources to dependent industries through infrastructure layers.
Remove Visa - processing $14 trillion in annual payment volume across 200 countries - and global commerce doesn't just slow down. It grinds to a halt. Retailers can't accept cards. E-commerce sites can't process transactions. Cross-border payments freeze. Not because Visa is the biggest company (it isn't - it's smaller than many retailers). But because Visa is the mechanism connecting consumer spending to merchant revenue.
Or consider ASML, the Dutch company that manufactures extreme ultraviolet (EUV) lithography machines - the only machines capable of printing chips at 7nm and below. Remove ASML, and advanced semiconductor manufacturing stops globally. Every cutting-edge chip factory - whether TSMC in Taiwan, Intel in the US, or GlobalFoundries in New York - depends on ASML's machines. The company ships ~50 EUV machines per year at $200M each, with revenues of €27.6 billion (2024). There is no alternative supplier.
These are keystone species. Not the largest. Not the most visible. But their removal collapses entire ecosystems.
Ecosystem Engineers: The Invisible Infrastructure
Charles Darwin spent his final years studying earthworms. His last book, The Formation of Vegetable Mould through the Action of Worms (1881), documented decades of observations: earthworms in arable land number approximately 53,000 per acre. In a single year, they move 10-18 tons of soil per acre through their digestive systems.
Earthworms are ecosystem engineers: organisms that modify physical habitats, creating conditions that other species depend on. Earthworm tunnels:
- Aerate soil, allowing roots to access oxygen
- Improve drainage, preventing waterlogging
- Mix nutrients, distributing organic matter through soil layers
- Create channels, enabling root penetration through compacted soil
Without earthworms, soil compacts. Water runs off instead of infiltrating. Plant roots suffocate. Nutrient cycling slows. Agricultural productivity drops 30-50% in earthworm-deprived soils.
Earthworms don't directly feed most organisms in the ecosystem. They provide infrastructure. They create the conditions for other species to thrive.
Fungi are even more extreme ecosystem engineers. The largest living organism on Earth is a honey fungus (Armillaria ostoyae) in Oregon's Malheur National Forest, covering 2,385 acres and estimated to weigh 600 tons. This single fungal network has lived for 2,400-8,650 years.
Fungi decompose dead organic matter - fallen trees, dead animals, leaf litter - breaking complex molecules into simpler forms that plants can absorb. In temperate forests, 90% of tree species have mycorrhizal relationships - fungal networks connected to their roots. The exchange is elegant: fungi provide nitrogen and phosphorus (which they extract from soil more efficiently). Trees provide sugars (which fungi cannot photosynthesize on their own). Both partners benefit.
These mycorrhizal networks, nicknamed the "wood wide web," connect multiple trees simultaneously. A single fungal network can link dozens of trees from different species, sharing resources across the forest. Old trees with deep roots access water during drought and share it with young saplings via fungal intermediaries. Injured trees receive carbon from neighbors. The network redistributes resources from surplus to deficit.
Remove fungi, and forests don't die immediately. They starve slowly. Nutrient cycling stops. Dead matter accumulates. Trees become resource-limited. Growth slows. Resilience disappears.
Ecosystem engineers don't produce the most obvious value. They produce the infrastructure that enables value creation.
The Business Parallel:
Just as earthworms create channels for roots and fungi trade nutrients between trees, infrastructure companies create conditions that enable entire industries to exist.
AWS is a business ecosystem engineer. Like earthworms aerating soil, AWS provides compute infrastructure (EC2), data storage (S3), and networking - invisible infrastructure that thousands of companies build on. AWS revenue is $90B annually. But the economic value enabled by AWS? Orders of magnitude larger. Startups that couldn't afford $100K server costs in 2006 now scale to millions of users for $1K/month. Dropbox stores billions of files. Slack handles millions of concurrent users. Remove AWS - like removing earthworms from soil - and vast portions of the internet don't just slow down. They suffocate.
Visa is the mycorrhizal network of commerce. It doesn't make products or sell goods. It connects merchants, banks, and consumers through payment rails, trading authorization signals for transaction fees (2-3%). Like fungi redistributing nutrients, Visa redistributes money flows across the global economy. $14 trillion in annual payment volume flows through Visa's network. Remove Visa, and commerce doesn't die immediately - it starves slowly as transactions become friction-filled and expensive.
The pattern is identical: Keystone species shape ecosystems through nutrient flows and predation. Ecosystem engineers shape ecosystems through infrastructure and habitat modification. Both create disproportionate impact relative to their direct economic footprint.
Ecological Succession: Markets Mature in Stages
In 2015, a volcanic island named Hunga Tonga emerged from the South Pacific after an underwater eruption. For the first time in decades, scientists could observe ecological succession in real time: the process by which ecosystems develop from barren conditions to mature communities.
Year 1: Bare rock and ash. No life.
Year 2: Seabirds arrived, depositing guano (nitrogen-rich waste). Wind carried seeds. The first colonizers were pioneer species: lichens, mosses, and grasses that tolerate harsh conditions - intense sun, no soil, high salinity, temperature extremes. Pioneer species don't outcompete others; they survive where nothing else can.
Year 3-5: Pioneer species died and decomposed, creating thin soil. Shrubs and small trees established. These seral species (intermediate community members) require the soil and nutrients that pioneers created but offer shade, deeper root systems, and more biomass. Seral species outcompete pioneers as conditions improve.
Year 10+: Larger trees establish. The ecosystem approaches a climax community: a stable, self-sustaining assemblage of species where composition changes slowly. Climax communities aren't "better" than pioneer or seral communities - they're adapted to mature conditions (deep soil, stable resources, competitive intensity) that pioneers and seral species can't survive.
Ecological succession is directional, predictable, and staged:
- Pioneer stage: High stress, low competition, fast-growing generalists
- Seral stage: Moderate stress, rising competition, specialists emerge
- Climax stage: Low stress, intense competition, slow-growing dominants
Each stage modifies the environment, making conditions more favorable for the next stage and less favorable for itself. Pioneer lichens create soil, enabling grasses, which outcompete lichens. Grasses stabilize soil, enabling shrubs, which shade out grasses. Shrubs accumulate nutrients, enabling trees, which shade out shrubs.
The Pioneer's Paradox: Succession is self-replacing. Early colonizers create the conditions that ensure their own displacement. Pioneer lichens build soil, enabling grasses that outcompete them. Early crypto companies built infrastructure (wallets, exchanges, education), enabling regulated institutions that now dominate. Pioneers don't fail - they succeed so well they make themselves obsolete.
In business, markets undergo succession:
Pioneer stage: New category emerges (personal computers 1975-1980, smartphones 2007-2010, crypto 2013-2017, generative AI 2022-2024). No infrastructure. High uncertainty. Fast iteration. Generalists who can tolerate chaos thrive. Competition is low because the market is undefined.
Seral stage: Category infrastructure develops (app stores, payment processors, regulatory clarity, skilled talent). Specialists emerge targeting sub-niches. Competition intensifies. Startups that thrived in pioneer chaos struggle as larger, better-capitalized entrants arrive.
Climax stage: Market matures. Dominant platforms emerge (AWS, Visa, Salesforce, SAP). Switching costs entrench incumbents. Innovation slows to incremental improvements. Competition is brutal - climax communities are the most competitive ecosystems, not the least.
Chapter 7's r-selection vs. K-selection maps directly onto succession:
- Pioneer stage = r-selection: Fast growth, high mortality, many offspring, low parental investment. Startups.
- Climax stage = K-selection: Slow growth, low mortality, few offspring, high parental investment. Enterprises.
The mistake organizations make: applying climax-stage strategies (deep investment, slow iteration, protective moats) to pioneer-stage markets, or applying pioneer-stage strategies (fast iteration, high burn, customer acquisition at any cost) to climax-stage markets.
Match your strategy to the ecosystem's successional stage.
Island Biogeography: Size and Isolation Matter
Islands represent roughly 1/6 of Earth's land area but contain outsized biological diversity and evolutionary experimentation. Why? Two factors: size and isolation.
Size determines carrying capacity: Larger islands support more species because they have more resources, more habitat types, and lower extinction rates due to larger populations. The species-area relationship is remarkably consistent: doubling island area increases species richness by ~30%.
Isolation determines colonization: Distant islands receive fewer colonizing species because fewer organisms can travel that far. But isolation also protects against invasive species and diseases, allowing unique evolutionary paths.
The interaction creates four categories:
| Island Type | Size | Isolation | Characteristics |
|---|---|---|---|
| Large, Near | Big | Close to mainland | High diversity, frequent new arrivals, competitive, dynamic |
| Large, Far | Big | Distant | High endemism (unique species), stable, older ecosystems |
| Small, Near | Small | Close | Low diversity, high turnover, transient species, stepping-stones |
| Small, Far | Small | Distant | Very low diversity, extreme endemism, vulnerable to extinctions |
Island biogeography explains:
- Why Madagascar has unique species: Large island, 250 miles from Africa (moderately isolated), 88% of species endemic (found nowhere else).
- Why Hawaii has unique species: Very isolated (2,400 miles from nearest continent), allowing extreme evolutionary divergence. Hawaiian silverswords (Chapter 7) radiated into 50+ species from a single tarweed ancestor.
- Why Guam's ecosystem collapsed: Small, very isolated, no native predators. When brown tree snakes arrived accidentally via cargo ships in the 1950s, 10 of 12 native forest bird species went extinct within decades. No evolutionary defense. No immigration of new species to fill niches. Total collapse.
Island biogeography teaches: size determines resilience, isolation determines uniqueness.
In business, geographic or technological isolation creates "island" markets:
- Shenzhen's hardware ecosystem: Geographically concentrated (size = large), initially isolated by language/culture/regulations from Western markets, enabled unique hardware iteration speed that doesn't exist elsewhere.
- Estonia's digital government: Small market (1.3M people), geographically isolated (post-Soviet), created unique e-governance systems (X-Road, e-Residency) that larger, less isolated countries couldn't experiment with.
- Singapore's fintech ecosystem: Small market, geographically isolated (island city-state), regulatory isolation (rapid experimentation allowed), created digital banking and payments innovation unavailable in larger, more regulated markets.
Small, isolated markets enable experimentation. Large, connected markets enable scale. Both are valuable, but for different reasons.
Invasive Species: When Ecosystems Break
In 1935, Australia imported 102 cane toads from Hawaii to control beetles that were damaging sugar cane crops. The toads bred prolifically. By 2020, 200 million cane toads spread across northern Australia, advancing 30-40 miles per year.
Cane toads are toxic - predators that eat them die. Native Australian predators (quolls, snakes, monitor lizards, crocodiles) evolved without exposure to toad toxins. They attack cane toads instinctively and die. Toad populations explode. Native predator populations collapse.
This is an invasive species: an organism introduced to an ecosystem where it has no natural predators, competitors, or diseases, experiencing ecological release - freedom from the constraints that limit population in its native habitat.
Kudzu, a Japanese vine introduced to the American South in the 1870s, grows up to 1 foot per day. It smothers trees, power lines, and buildings. It's called "the vine that ate the South." Eradication costs exceed $500 million annually with no end in sight.
Invasive species succeed because:
- No natural enemies: Predators, parasites, and diseases that control population in native habitat don't exist in new environment.
- Naive competitors: Native species didn't evolve defenses, allowing invaders to outcompete or directly harm them.
- Rapid reproduction: Many invasive species are r-selected (Chapter 7): fast growth, high offspring numbers, opportunistic resource use.
- Generalist strategies: Invasives often tolerate wider environmental conditions than native specialists.
The brown tree snake on Guam is the extreme case. Guam had no native snakes. Birds nested on the ground or low branches. When snakes arrived, they encountered:
- Abundant, naive prey: Birds with no snake-avoidance behaviors
- No predators: Nothing on Guam ate snakes
- No competition: No other predator occupied the "tree-dwelling nocturnal predator" niche
- Ecological release: Snake populations exploded
Within 40 years, 10 of 12 native forest bird species went extinct. The ecosystem didn't adapt - it collapsed.
Invasive species reveal ecosystem fragility: remove one constraint, and the system can't self-correct.
In business, regulatory arbitrage, technological disruption, or capital infusions create conditions analogous to ecological release:
- Uber/Lyft: Sidestepped taxi regulations (medallion systems, insurance requirements, driver screening), experienced ecological release in urban transportation markets, grew exponentially until regulators adapted.
- Cryptocurrency exchanges (2017): Operated in regulatory gray zones, experienced ecological release (no KYC/AML enforcement, no consumer protection, no capital requirements), grew to billions in volume, then collapsed or adapted when regulation arrived.
- Chinese manufacturing (1990s-2000s): Lower labor costs + weaker environmental regulations = ecological release in global manufacturing, displacing incumbents in textiles, electronics, and consumer goods.
Invasive species cause damage until the ecosystem adapts: predators evolve defenses, competitors learn strategies, or external forces (regulation, resource depletion) constrain growth. The question is how much damage occurs before adaptation.
Trophic Levels and Energy Flow
Ecosystems organize into trophic levels: feeding levels that define energy flow from primary producers to apex predators.
Level 1 - Primary Producers (plants, algae, photosynthetic bacteria): Convert sunlight into chemical energy. They don't consume other organisms. In terrestrial ecosystems, biomass is ~450 gigatons of carbon.
Level 2 - Primary Consumers (herbivores): Eat plants. Biomass: ~10 gigatons of carbon.
Level 3 - Secondary Consumers (carnivores that eat herbivores): Eat primary consumers. Biomass: ~1 gigaton of carbon.
Level 4 - Tertiary Consumers (apex predators): Eat secondary consumers. Biomass: ~0.1 gigatons of carbon.
Notice the pattern: ~90% of energy is lost at each trophic level. When herbivores eat plants, only ~10% of the plant's energy converts to herbivore biomass - the rest is lost to metabolism, heat, and waste. The same 90% loss occurs at each subsequent level.
This explains:
- Why food chains rarely exceed 4-5 levels: Insufficient energy remains to support higher trophic levels.
- Why apex predators are rare: Wolves, lions, orcas exist in small populations because the energy pyramid supporting them narrows dramatically.
- Why ecosystems are bottom-heavy: The vast majority of biomass and energy exists in primary producers.
The 10% rule constrains ecosystem structure. Energy flow determines who can exist and in what abundance.
In business ecosystems, trophic levels map to value capture:
Level 1 - Infrastructure providers (AWS, Stripe, Cloudflare, Twilio): Capture small percentages of massive transaction volumes. AWS margins are 20-30%, but revenue is $90B+ because they're the base of the pyramid. They're the "primary producers" in tech - creating the substrate that others build on.
Level 2 - Platform intermediaries (Shopify, Stripe, app stores): Capture 2-5% transaction fees. They sit one level above infrastructure, enabling merchants and developers to reach customers.
Level 3 - Applications and services (Spotify, Slack, Zoom, SaaS tools): Capture subscription or usage fees. They sit above platforms, delivering end-user value.
Level 4 - Aggregators and super-apps (Google, Meta, WeChat): Capture attention and advertising dollars. They aggregate users and traffic, sitting atop the trophic pyramid.
The same 90% loss applies: AWS doesn't capture 90% of value created by applications running on it - it captures 5-10%. Shopify doesn't capture 90% of merchant revenue - it captures 2-3%. Platforms with massive transaction volumes (Level 1-2) achieve scale. Applications with high margins (Level 3-4) achieve profitability but serve smaller markets.
You can't all be apex predators. The energy pyramid doesn't support it. Most value in ecosystems is created at lower trophic levels, captured in small increments across massive volume.
Part 2: Business Examples Through the Biological Lens
TSMC: The Keystone Species of Tech
In 1985, Morris Chang walked out of a conference room at Texas Instruments headquarters, carrying a radical idea that had just been rejected. At 54, with three decades in the semiconductor industry - rising to third in command at TI - he had pitched what seemed obvious to him: a pure-play semiconductor foundry. A company that would manufacture chips designed by others but design none itself.
TI said no. So did Intel. And Motorola. And AMD. And Panasonic. And Sony.
Their reasoning was unanimous: "Why would we pay someone else to manufacture our chips when we can do it ourselves?" Every major semiconductor company in 1985 was vertically integrated. They designed chips and manufactured them in their own fabs. The idea of separating design from manufacturing wasn't just novel - it violated industry orthodoxy.
But Chang saw what they didn't: a coming wave of fabless chip designers - engineers with brilliant ideas but without the billions needed to build fabrication plants. Someone needed to be the ecosystem's foundation.
In 1986, Taiwan's government made Chang an offer. Li Kwoh-ting, representing the Executive Yuan, wanted to build Taiwan's semiconductor industry. He invited Chang to head the Industrial Technology Research Institute (ITRI) and gave him essentially a blank check: build Taiwan's chip industry however you see fit.
Chang pitched his pure-play foundry model. The government was skeptical - high investment, high risk, unproven business model. But Chang was convincing. The government committed 48% of the startup capital through the National Development Fund. After approaching every major semiconductor company globally, only one - Philips - agreed to invest. They put up $58 million for a 27.5% stake and agreed to transfer production technology.
In February 1987, Taiwan Semiconductor Manufacturing Company (TSMC) was founded. Morris Chang was 56.
The bet was enormous. Building a leading-edge fab required hundreds of millions. The business model had never been proven. Industry insiders were dismissive: "Who will trust a third party with their most valuable IP? Chip designers want control. This is naive."
Chang's strategy was simple but non-obvious:
1. Never compete with customers. TSMC would design zero chips. No in-house products. No conflict of interest. Fabless designers could trust TSMC with proprietary designs because TSMC would never become a competitor. Intel and Samsung couldn't offer this - they designed their own chips, making them IP risks.
2. Obsessive reliability. TSMC committed to process stability, yield optimization, and delivery predictability. If a customer's chip worked in TSMC's process, it would work at volume. This eliminated manufacturing risk, letting designers focus on innovation.
3. Ecosystem lock-in. TSMC co-developed design tools, manufacturing specs, and testing protocols with customers. The more a company invested in TSMC's process, the harder switching became. Re-engineering for a different foundry meant 18-24 months of work and hundreds of millions in costs.
The gamble paid off - slowly at first, then overwhelmingly.
By 2024, 37 years later:
- TSMC manufactures 92% of the world's most advanced chips (sub-5nm process nodes)
- Revenue: $70B annually (larger than Intel)
- Market cap: $500B+ (top 10 most valuable companies globally)
- TSMC's customers include Apple, Nvidia, AMD, Qualcomm, and hundreds of others
- TSMC operates 13 leading-edge fabs globally
TSMC is a keystone species. Its impact on the tech ecosystem is disproportionately large.
Remove TSMC, and the iPhone stops existing. Apple designs A-series and M-series chips in-house, but TSMC manufactures them. No TSMC, no Apple Silicon. Apple can't switch foundries overnight - TSMC's 3nm and 5nm processes are 2-3 years ahead of competitors (Samsung, Intel). Without TSMC, iPhones revert to older, slower, less power-efficient chips. Product timelines collapse.
Remove TSMC, and AI progress stalls. Nvidia's H100 and A100 GPUs - which power ChatGPT, Anthropic's Claude, and every major AI lab - are manufactured by TSMC. Nvidia designs the chips; TSMC builds them. No alternative foundry can produce comparable volumes at comparable performance. AI scaling decelerates or halts.
Remove TSMC, and automotive electrification slows. Modern cars contain 1,000-3,000 semiconductor chips for sensors, control units, infotainment, and battery management. The 2021 semiconductor shortage - partially caused by pandemic-disrupted TSMC production - delayed car production by millions of units.
This is the definition of a keystone species: TSMC isn't the largest participant in tech by revenue (Apple, Microsoft, Google are larger). It isn't the most visible to consumers. But its removal collapses multiple dependent industries.
The companies that rejected Morris Chang's pitch in 1985 - Intel, TI, Motorola - now depend on the ecosystem he created.
Intel, once the world's largest semiconductor manufacturer, is now building foundry capacity to compete with TSMC.
It's 18-24 months behind.
Why is TSMC irreplaceable?
Capital intensity: Building a leading-edge fab costs $15-20 billion and takes 3-5 years. TSMC operates 13 fabs with leading-edge capacity. Replicating TSMC's scale would require $200B+ and a decade. No competitor has attempted it.
Process leadership: TSMC reached 3nm manufacturing in 2022. Samsung reached 3nm in 2023 with lower yields. Intel is still ramping 3nm (rebranded "Intel 4") as of 2024. TSMC's lead is an eternity in semiconductors.
Trust: Chip designers share their most proprietary designs with TSMC. TSMC's pure-play model - no in-house chip designs - removes conflict of interest. Intel and Samsung design chips, creating IP risk. TSMC doesn't compete, so customers trust it.
Ecosystem lock-in: TSMC's customers co-develop processes with TSMC. Design tools, specs, and testing protocols interlock. Switching foundries means re-engineering from scratch.
TSMC's keystone status creates vulnerability: geopolitical risk. TSMC's fabs are in Taiwan, 90 miles from mainland China. Any conflict disrupting Taiwan disrupts global tech supply. The U.S. CHIPS Act (2022) allocates $52B to build domestic fabs, including $6B for a TSMC fab in Arizona. TSMC is building fabs in Japan and Germany.
But even with geographic diversification, TSMC remains a single point of failure. The ecosystem's dependence is structural, not incidental.
Lesson: Keystone species create ecosystems. They also create systemic risk. Morris Chang bet his reputation on a model that six major companies rejected. Thirty-seven years later, the entire tech industry depends on that bet. The more dependent the ecosystem, the more catastrophic keystone removal becomes.
ASML: The Keystone Behind The Keystone
TSMC is a keystone species. But TSMC depends on another keystone species: ASML, a Dutch company that manufactures extreme ultraviolet (EUV) lithography machines - the only machines in the world capable of printing sub-7nm semiconductor features.
ASML holds a 100% monopoly on EUV lithography. Every leading-edge chip - manufactured by TSMC, Intel, or other foundries - requires ASML's machines. Each EUV machine costs $150-200 million, weighs 180 tons, and requires 40 freight containers to ship. ASML produces ~50-60 machines per year. Customers order years in advance.
Why does ASML have a monopoly?
Technological complexity: EUV lithography uses 13.5nm wavelength light (compared to 193nm for older Deep UV systems). At this wavelength, traditional lenses absorb light, so ASML uses mirrors polished to atomic precision - if scaled to Germany's size, imperfections would be a millimeter tall. EUV machines generate plasma by firing 50,000 laser pulses per second at tin droplets, vaporizing them to produce EUV light. This took 30 years and $10B+ in R&D to develop.
Supply chain consolidation: ASML assembles machines, but key components come from sole-source suppliers: Zeiss (Germany) makes mirrors, Cymer (ASML subsidiary, US-origin) makes light sources, hundreds of specialized suppliers provide subsystems. Replicating ASML requires replicating this entire supply chain - no country or company has succeeded.
IP and trade restrictions: The U.S., Netherlands, and Japan restrict EUV exports to China, recognizing ASML's strategic importance. China's largest foundry (SMIC) cannot access EUV, limiting it to 7nm and older nodes. This geopolitical weaponization of ASML's monopoly demonstrates keystone awareness.
ASML's 2023 revenue: $28B. Market cap: $300B+.
ASML → TSMC → Apple/Nvidia/AMD → smartphones/AI/data centers → global digital economy.
Remove ASML, and Moore's Law stops. Semiconductor advancement depends on shrinking transistors. Shrinking below 7nm requires EUV. No EUV alternative exists. ASML isn't a bottleneck in the traditional sense (insufficient capacity). It's a structural dependency - the only organism performing this function.
This is trophic cascade in reverse: ASML (Level 1) enables TSMC (Level 2) which enables chip designers (Level 3) which enable tech companies (Level 4) which enable digital economy (Level 5). Effects propagate upward. ASML's monopoly position ripples through every subsequent level.
Lesson: Ecosystems have keystone species at multiple trophic levels. Identifying dependencies reveals where ecosystems are fragile.
WeChat: Trophic Cascade in a Super-App
In 2011, Tencent launched WeChat as a messaging app in China - a direct competitor to its own QQ messenger and new entrants like WhatsApp. By 2024, WeChat has 1.3 billion monthly active users and functions as China's digital infrastructure: messaging, payments, e-commerce, ride-hailing, food delivery, bill payments, government services, health records, and social networking all operate within WeChat.
WeChat isn't a single product. It's an ecosystem containing millions of "mini-programs" (lightweight apps within WeChat) that users access without leaving WeChat's environment.
This is a trophic cascade: WeChat's dominance at Level 4 (aggregator/super-app) transformed every level below it.
Level 1 - Infrastructure (WeChat Pay): WeChat Pay processed $17 trillion in transactions in 2020. It's the payment infrastructure for 900+ million users. Merchants that don't accept WeChat Pay lose customers. The Chinese economy reorganized around WeChat-based payments, leapfrogging credit cards entirely. Street vendors use WeChat QR codes. Government services accept WeChat Pay. Even beggars display QR codes.
Level 2 - Platforms (Mini-Programs): WeChat hosts 4+ million mini-programs. These lightweight apps - e-commerce stores, games, services - run inside WeChat. Developers build for WeChat's ecosystem, not iOS/Android directly, because user acquisition is cheaper within WeChat's 1.3B user base. The mini-program platform became China's primary app distribution channel, rivaling iOS App Store and Google Play.
Level 3 - Applications (E-Commerce, Ride-Hailing): Pinduoduo (e-commerce), Didi (ride-hailing), Meituan (food delivery), and thousands of brands operate within WeChat. Instead of standalone apps, they're mini-programs. User behavior shifted: instead of switching between apps, users never leave WeChat. Everything is a message, a mini-program, or a payment.
Level 4 - Aggregation (WeChat Itself): WeChat captures attention, data, and network effects. Users spend 3-4 hours per day in WeChat. Tencent revenue $86.7 billion (2024 projected). WeChat isn't just large - it's the substrate of Chinese digital life.
The trophic cascade:
- WeChat achieved dominance (messaging + payments + mini-programs = super-app lock-in)
- Developers moved to mini-programs (cheaper acquisition, better retention, no app store fees)
- Users stopped downloading standalone apps (everything is accessible in WeChat)
- Standalone app ecosystems weakened (iOS App Store in China is less relevant than in US/Europe)
- WeChat's dominance self-reinforced (more users → more mini-programs → more utility → more users)
This is how trophic cascades work: a change at one level cascades through the entire ecosystem. WeChat's dominance didn't just capture market share - it reorganized market structure.
Lesson: Super-apps create trophic cascades. They don't compete in categories - they reorganize ecosystems.
SAP + Partners: Energy Flow Through Enterprise Ecosystems
SAP, founded in Germany in 1972, produces enterprise resource planning (ERP) software: the systems that manage inventory, accounting, HR, supply chains, and manufacturing for large organizations. By 2024, SAP has:
- $30B+ annual revenue
- 440,000+ customers in 180 countries
- 77% of global transaction revenue touches an SAP system
- 25,000+ partner companies implementing, customizing, and maintaining SAP systems
- Partner ecosystem revenue estimated at $100B+ annually - 3x SAP's own revenue
SAP is a Level 1 organism (infrastructure provider). But the ecosystem built on SAP generates far more value than SAP itself captures - this is the 10% rule from trophic energy flow in action.
Level 1 - SAP (Infrastructure Provider):
- Revenue: $35.8 billion (2024 projected)
- Value captured: Software licenses + maintenance fees
- Trophic role: Primary producer - creates the substrate (ERP platform) that all higher levels depend on
- Employees: 108,000+ (2024)
Level 2 - Implementation Partners (Deloitte, Accenture, IBM, Capgemini):
- Revenue: $50-60B in SAP-related services
- Value captured: Consulting fees for implementing SAP (6-24 months, $10M-$500M per project)
- Trophic role: Primary consumers - consume SAP's platform, convert it into usable business processes for customers
Level 3 - Specialized SAP Developers and ISVs (Independent Software Vendors):
- Revenue: $20-30B in SAP extensions, add-ons, and integrations
- Value captured: Niche functionality SAP doesn't build (industry-specific modules, regional compliance, AI integrations)
- Trophic role: Secondary consumers - build on SAP + partners' implementations, filling specialized needs
Level 4 - Enterprises Using SAP:
- Value created: Operational efficiency, data integration, process automation worth trillions across industries (manufacturing, retail, logistics, energy)
- Value captured: Cost savings, revenue growth, risk reduction - orders of magnitude larger than cumulative ecosystem spending
- Trophic role: Apex - consume the entire stack, derive final business outcomes
The 10% rule plays out clearly:
- SAP captures ~10-15% of ecosystem revenue ($30B of $200B+ total)
- Partners capture ~30-40% ($60-80B)
- Enterprises capture the remaining 50-60%+ in value derived from using SAP
But if you measure by value created (not just revenue captured), enterprises derive $10-100B+ in operational value from SAP deployments, making the pyramid even more extreme: SAP's $30B revenue enables trillions in enterprise value creation.
This is energy flow in action: the base of the pyramid (SAP) captures a small percentage of massive volume. Higher trophic levels (partners, customers) capture diminishing absolute value but compound SAP's utility.
SAP's ecosystem strategy is deliberate:
- Partner certification programs: 25,000+ certified partners provide implementation capacity SAP couldn't staff internally
- ISV programs: 1,800+ independent software vendors extend SAP functionality without SAP building it
- Open APIs and extensibility: SAP Rise (2021) cloud platform enables easier integrations, lowering barriers for partners
- Customer co-innovation: SAP's innovation labs work with customers to develop industry-specific solutions, then generalize for wider sale
Lesson: Ecosystem value is multiplicative, not additive. Infrastructure providers capture small percentages of massive flows. That's the business model - don't fight the 10% rule, design for it.
Bangalore: Ecological Succession from Outsourcing to Product
In the 1980s, Bangalore (now Bengaluru), India, was a mid-tier city known for public sector enterprises and research institutions. By 2024, Bangalore is India's "Silicon Valley": 4,000+ tech companies, 400,000+ software engineers, $200B+ annual tech exports, and home to Indian headquarters for Microsoft, Amazon, SAP, and hundreds of unicorn startups.
This transformation exemplifies ecological succession: pioneer species colonized an empty niche, modified the environment, and enabled subsequent waves of specialists to thrive.
Pioneer Stage (1985-2000): IT Services and Outsourcing
Texas Instruments opened Bangalore's first major chip design center in 1985, attracted by IIT engineering graduates (10,000+ annually), 1/10th US labor costs, English proficiency, and a 12-hour time zone offset enabling "follow-the-sun" development.
Infosys (1981), Wipro (1980s), and TCS (1990s) pioneered IT services outsourcing - writing code and managing infrastructure for Western companies.
Pioneers tolerated harsh conditions (no VC, poor infrastructure, regulatory barriers, brain drain) but modified the environment: building private campuses with reliable power, lobbying for tax breaks (Software Technology Parks, 1991), and retaining talent with Western-style work culture. They proved India could deliver quality software at scale.
Seral Stage (2000-2015): MNC R&D Centers and Specialized Services
By 2000, Bangalore had 200,000+ trained engineers, reliable infrastructure, venture capital ($1-5B annually), and regulatory clarity.
Conditions pioneers created enabled seral species: Microsoft, Oracle, and Amazon opened R&D centers doing core product development (Windows, databases, AWS) - innovation, not just outsourcing. Specialized services emerged (analytics, UX, cybersecurity). Product startups launched: Flipkart (2007, e-commerce), Ola (2010, ride-hailing), founded by talent trained at pioneer companies.
Seral species outcompeted pioneers: MNC R&D salaries exceeded Infosys/Wipro by 2-3x. Startup equity lured mid-career engineers. This is succession - seral species depend on infrastructure pioneers created, then outcompete them for talent and capital.
Climax Stage (2015-Present): Global Product Companies and Deep Tech
By 2015, Bangalore had mature venture capital ($10-20B annually), experienced entrepreneurs, global company headquarters (Flipkart, Ola governed from Bangalore, not just R&D centers), and deep tech infrastructure.
Climax characteristics: Indian SaaS unicorns (Freshworks IPO $5B, Postman $5.6B valuation) selling globally from India. AI and deep tech startups building foundational models. Competitive intensity: talent costs approach 50-70% of US equivalents. Climax communities are intensely competitive - success attracts competition, raising costs and thinning margins.
Succession timeline:
- Pioneer (1985-2000): Outsourcing, harsh conditions, generalists
- Seral (2000-2015): MNC R&D, specialists, startups emerge
- Climax (2015-present): Global product companies, deep tech, intense competition
Each stage required the previous stage's infrastructure. Pioneers couldn't have built SaaS unicorns in 1990 - no talent, no capital, no infrastructure. Climax species can't colonize bare rock - they need soil.
Lesson: Markets mature through succession. Match your strategy to the market's stage. Trying to be a climax-stage company (high investment, specialization, scale) in a pioneer market (no infrastructure, high uncertainty) fails. Applying pioneer strategies (generalist, fast iteration, low cost) in climax markets (intense competition, specialization required) also fails.
Dutch Flower Auction: Niche Partitioning and Cooperative Infrastructure
In Aalsmeer, Netherlands, 20 minutes from Amsterdam, sits the Royal FloraHolland auction: the world's largest flower auction, housed in a building covering 12 million square feet (larger than 100 football fields). Every day, 20 million flowers and 2 million plants are auctioned and distributed globally.
This is niche partitioning: specialization allowing multiple species to coexist by reducing direct competition.
How the auction works:
- Growers (5,000+ in Netherlands, Kenya, Ethiopia, Ecuador) ship flowers overnight to Aalsmeer.
- Auction (starts 6 AM): Buyers (wholesalers, florists, supermarkets) sit in auction halls. Flowers are displayed on carts. A "Dutch auction" clock starts high and counts down - first buyer to press their button wins at that price.
- Distribution: Flowers are sorted, packed, and shipped within hours. 50% of flowers auctioned in the morning are in European stores by afternoon.
Niche partitioning mechanisms:
- Geographic specialization: Dutch growers focus on tulips, roses, and greenhouse flowers. Kenyan growers focus on long-stem roses. Ethiopian growers focus on summer flowers. Ecuadorian growers focus on equatorial varieties. Each region exploits comparative advantage (climate, labor costs, logistics).
- Product specialization: Some growers produce only tulip bulbs. Others produce only rose stems. Others produce only potted plants. Within roses: some specialize in red, others in white, others in novelty colors. Specialization allows 5,000+ growers to coexist without directly competing.
- Buyer specialization: Some buyers focus on supermarkets (low-cost, high-volume). Others focus on luxury florists (high-margin, bespoke arrangements). Others focus on event planners (bulk orders, seasonal demand). Buyers occupy different market niches, reducing direct competition.
Cooperative infrastructure is the key:
- Shared logistics: Royal FloraHolland (the auction operator) is a cooperative owned by growers. It provides cold storage, transport, and auction facilities that individual growers couldn't afford. This is ecosystem engineering (Chapter 8's earthworms) - creating infrastructure that benefits all participants.
- Shared information: Auction prices are transparent. Growers see real-time demand signals, allowing next-day production adjustments. Buyers see supply availability, enabling procurement optimization.
- Shared quality standards: FloraHolland enforces grading (flower size, stem length, freshness), reducing information asymmetry and increasing buyer trust.
The Dutch flower auction controls 50%+ of global wholesale flower trade despite Netherlands being a small country (17M people). Why?
- Infrastructure concentration: Centralizing auction, cold storage, and logistics in one location creates efficiencies no distributed system matches.
- Network effects: More growers → more variety → more buyers → more demand → attracts more growers. The loop reinforces.
- Cooperative structure: Growers own the infrastructure, aligning incentives. Profits return to participants, not extracted by middlemen.
Niche partitioning lesson: Markets can support many participants if they specialize and avoid direct competition. The auction enables coexistence by providing shared infrastructure and transparent price discovery.
Ecosystem engineering lesson: Infrastructure owned by participants (cooperatives) creates different incentives than infrastructure owned by extractive intermediaries. FloraHolland's cooperative model keeps value within the ecosystem.
Shenzhen Hardware Ecosystem: Island Biogeography and Manufacturing Density
Shenzhen, China, transformed from a fishing village of 30,000 (1979) to a megacity of 13 million (2024) in 45 years. It's the global center of hardware manufacturing: electronics, drones, smartphones, wearables, IoT devices.
This is island biogeography: Shenzhen's geographic and regulatory isolation created conditions for unique evolutionary paths unavailable in larger, more connected markets.
Size: Shenzhen is large - 13M people, $500B GDP, physical space for factories, suppliers, and housing within 50km radius. Size provides carrying capacity: enough resources (labor, capital, land) to support a dense, diverse ecosystem.
Isolation (initial):
- Geographic: Shenzhen borders Hong Kong but was separate (Hong Kong under British rule until 1997). Shenzhen was designated a Special Economic Zone (SEZ) in 1980, with different regulations than mainland China.
- Regulatory: SEZs allowed foreign investment, tax incentives, and market-oriented policies unavailable elsewhere in China during the 1980s-1990s.
- Language/culture: Western companies found Shenzhen difficult to access (Mandarin language barrier, opaque supply chains), creating initial isolation that reduced competitive pressure.
Unique evolutionary path:
- Component density: Within 50km of Shenzhen's Huaqiangbei district, you can source 10,000+ electronic components same-day. Need a custom PCB? 24-hour turnaround. Need injection-molded cases? 48 hours. Need assembly? Dozens of factories will quote within hours. This density doesn't exist in US, Europe, or other Asian countries.
- Iteration speed: Hardware startups in Shenzhen iterate 10x faster than equivalents in Silicon Valley. Why? Supply chain proximity. In San Francisco, ordering a custom component takes 2-4 weeks shipping from China. In Shenzhen, you walk 10 minutes to Huaqiangbei market, buy the component, return to your office, and test the same day.
- Manufacturing expertise: Shenzhen has 40 years of accumulated knowledge in high-volume, low-margin hardware production. Factories understand tolerances, defect rates, and optimization that take years to learn elsewhere.
Island biogeography dynamics:
Large + Initially isolated = High endemism (unique local adaptations). Shenzhen developed manufacturing capabilities that didn't evolve elsewhere because:
- Selection pressure was different: Shenzhen optimized for speed, volume, and cost. Silicon Valley optimized for software scale and venture returns. Different environments select for different traits.
- Gene flow was limited: Initial isolation (language, regulation, distance) prevented Western manufacturing knowledge from overwhelming local experimentation. Shenzhen developed its own methods.
- Competitive release: In the 1990s-2000s, Shenzhen faced little competition in low-cost electronics manufacturing. This ecological release allowed rapid specialization.
By 2010s, isolation decreased:
- Language barriers lowered: English proficiency increased; translation tools improved.
- Regulatory transparency increased: Supply chain platforms (Alibaba, Global Sources) made sourcing easier.
- Western companies learned Shenzhen's ecosystem: Google, Amazon, Xiaomi, and hundreds of startups now manufacture in Shenzhen.
But even with reduced isolation, Shenzhen's uniqueness persists. The density, speed, and expertise evolved during isolation remain unmatched. You can't replicate Shenzhen's ecosystem by building factories elsewhere - you'd need to replicate 40 years of accumulated learning, supplier networks, and talent density.
Lesson: Island biogeography explains regional specialization. Large, initially isolated markets develop unique capabilities. Once developed, these capabilities persist even after isolation decreases. Shenzhen's hardware ecosystem, Bangalore's software ecosystem, Singapore's fintech ecosystem - all are "islands" that evolved unique traits.
Grab: Invasive Species and Ecological Release in Southeast Asia
In 2015, Anthony Tan sat in a Kuala Lumpur office looking at Uber's global expansion map. Red pins covered North America, Europe, Latin America, and China. Uber had raised $5 billion. It operated in 300+ cities. Its valuation: $50 billion.
Tan's company - then called MyTeksi - had launched in Malaysia in 2012 with $25,000 in seed funding. Three years later, it operated in 3 Southeast Asian cities with 50,000 riders. Uber had just entered Singapore and Bangkok with deep pockets and global brand recognition.
The conventional wisdom: retreat to Malaysia, become a local player, wait for Uber to take the region.
Tan made a different bet.
He saw what Uber didn't: Southeast Asia wasn't a market - it was 8 different ecosystems. Indonesia had 270 million people, most using cash, many riding motorcycles. Vietnam's addresses were informal ("near the blue house on Nguyen Street"). Thailand's traffic patterns defied Western app logic. Uber's playbook - credit cards, sedans, standardized addresses - worked in Manhattan. It didn't work in Manila.
Tan rebranded MyTeksi to Grab. He pitched SoftBank: "Uber is trying to colonize Southeast Asia. We're native species adapting to local conditions." SoftBank invested $2 billion - the largest Series B in Southeast Asian history.
This is ecological release: an invasive species entering an ecosystem where normal constraints don't exist.
Grab's advantages (compared to Uber):
- Cash payments: 70%+ of Southeast Asians didn't have credit cards. Grab accepted cash. Uber initially required cards - locking out 200 million potential users.
- Motorcycle rides (GrabBike): In Vietnam, Indonesia, and Thailand, motorcycles navigate traffic jams that paralyze cars. Uber offered sedans. Grab offered bikes - cheaper, faster, culturally native.
- Localization: Grab hired drivers who knew informal addresses ("the market near the temple"). Grab supported 8 languages. Uber translated English interfaces - which didn't solve the address problem.
- Regulatory timing: Grab launched before Southeast Asian governments understood ride-hailing. By the time regulations arrived (2016-2018), Grab had millions of users. Regulators couldn't ban it without political backlash. Grab helped write the regulations.
The war (2015-2018):
Uber recognized the threat. It poured capital into Southeast Asia - subsidizing rides below cost, paying drivers 2-3x market rates, burning $700 million annually in the region.
Grab matched every subsidy. SoftBank backed them with $10 billion total (SoftBank had also backed Didi Chuxing, which defeated Uber in China - SoftBank knew Uber's weaknesses).
For three years, both companies hemorrhaged money. Drivers earned extraordinary wages. Riders paid almost nothing. Neither company made profit. The question wasn't who could win - it was who could outlast.
In March 2018, Uber blinked.
Uber's CEO, Dara Khosrowshahi, told investors: "We can't win this market. The capital required exceeds the returns." Uber sold its Southeast Asian operations to Grab in exchange for 27.5% equity - essentially admitting defeat.
Grab achieved 70%+ market share across Southeast Asia overnight.
The war was over.
The super-app evolution (2018-2024):
But Grab didn't stop at ride-hailing. Ecological release taught them a lesson: if you're going to dominate an ecosystem, become infrastructure, not just a participant.
They launched GrabPay (payments), GrabFood (food delivery), GrabFinance (lending and insurance). As of 2025, Grab operates in 8 countries, with 44.5 million monthly transacting users, and processes billions in transactions. Users book rides, order food, pay bills, and access credit - all within Grab's ecosystem.
This is how invasive species survive long-term: they don't just exploit ecological release temporarily - they become ecosystem engineers that others depend on.
Ecological release risks:
Grab IPO'd via SPAC in 2021 at $40B valuation. By 2024, market cap: $10B (75% drop). Why?
- Regulation arrived: Governments imposed driver protections, fare minimums, and data privacy rules. Grab's early advantage (operating in regulatory gray zones) disappeared.
- Subsidy withdrawal: Grab reduced subsidies to approach profitability. Rides became expensive. Users switched to cheaper alternatives (motorcycles, public transit, local apps).
- Competitive response: Go-Jek (rebranded Gojek) raised $5B, preventing Grab from monopolizing Indonesia (40% of Southeast Asia's population). Local competitors (Thailand's Bolt, Vietnam's Be) regained share.
Lesson: Invasive species exploit ecological release - conditions where normal constraints (competition, regulation, resource limits) are absent. But release is temporary. Ecosystems adapt. Predators arrive. Regulation evolves. The invasive species either becomes a permanent ecosystem member or gets displaced. Grab succeeded in escaping "invasive" status by becoming infrastructure (payments, credit), not just a ride-hailing app.
Part 3: The Practical Framework
You've now seen ecosystem thinking in action: salmon feeding forests, wolves reshaping rivers, TSMC creating dependencies, WeChat reorganizing entire markets. The biological patterns are clear. The business parallels are real.
Now the question: How do you apply this to your organization?
The Ecosystem Diagnostic that follows isn't theoretical - it's the seven-step audit I've used with dozens of companies. Some discovered they were keystone species and doubled down on infrastructure. Others realized they were pioneers in a maturing market and shifted strategy. A few learned they were parasites disguised as partners - and either adapted or exited.
The framework has three goals:
- Diagnose your true position in the ecosystem - Are you keystone infrastructure, a symbiont, or a parasite? Your real position determines your leverage.
- Identify dependencies that could kill you - Single points of failure, power asymmetries, and succession vulnerabilities.
- Design strategy based on ecological reality, not organizational ego - Stop competing where you can't win. Start building where the ecosystem needs you.
Let's begin.
The Ecosystem Diagnostic
Most companies think in terms of direct competition: "We compete with Company X for Customer Y." But ecosystem thinking reveals that your position in the network - keystone species, ecosystem engineer, parasite, symbiont - determines survival more than head-to-head competition.
This framework helps you diagnose your ecosystem role, identify dependencies, and design for systemic leverage.
Step 1: Map Your Ecosystem Position
Identify where you sit in the ecosystem's structure:
| Position | Definition | Examples | Strategic Implications |
|---|---|---|---|
| Keystone Species | Disproportionate impact; removal collapses ecosystem | ASML, Visa, ARM Holdings, Mastercard | High leverage, high systemic risk, regulatory/geopolitical vulnerability |
| Ecosystem Engineer | Provides infrastructure others build on | AWS, Stripe, Twilio, Shopify | Capture small % of large flows, enable > extract, defensibility through lock-in |
| Apex Predator | Aggregates users/traffic at top of trophic pyramid | Google, Meta, WeChat | High margins but dependent on lower trophic levels, vulnerable to regulation |
| Platform Intermediary | Connects producers/consumers, captures transaction fees | Shopify, Uber, Etsy | 2-5% take rates, volume-dependent, must avoid disintermediation |
| Application/Service | Delivers end-user value, builds on platforms | Spotify, Slack, Zoom, SaaS tools | High competition, dependent on platform stability, margin pressure |
| Symbiont/Partner | Co-dependent relationship with larger player | SAP partners, App Store developers | Vulnerable to platform policy changes, diversification critical |
| Pioneer Species | First mover in immature market | Early crypto projects, AI startups | High mortality, must build infrastructure, enable successors |
Diagnostic questions:
- If you disappeared tomorrow, would your ecosystem collapse? (Yes = keystone; No = proceed)
- Do others build businesses on your infrastructure? (Yes = ecosystem engineer; No = proceed)
- Do you aggregate users/traffic and capture attention? (Yes = apex predator; No = proceed)
- Do you connect buyers and sellers for a fee? (Yes = platform intermediary; No = proceed)
- Do you deliver end-user value using someone else's platform? (Yes = application; No = proceed)
- Are you tightly coupled to another company's success? (Yes = symbiont; No = proceed)
- Are you colonizing a new market with no infrastructure? (Yes = pioneer)
Your ecosystem position determines strategy:
- Keystone/Engineer → Build moats and redundancy: You're a single point of failure. Competitors will try to displace you. Governments will regulate you. Invest in geographic diversification, technical leadership, and customer lock-in.
- Apex/Intermediary → Manage platform risk: You depend on lower trophic levels. Ensure their health. Avoid extracting so much value that participants leave.
- Application/Symbiont → Diversify dependencies: You're vulnerable to platform policy changes. Build on multiple platforms or own more of the stack.
- Pioneer → Build infrastructure, expect displacement: You're creating conditions for successors. Capture value early or plan to evolve into ecosystem engineer role.
Implementation Guidance:
Time Required:
- Seed stage: 2-4 hours (CEO + co-founder session)
- Series A: 1 day (leadership team workshop)
- Series B+: 2-3 days (cross-functional analysis with data)
Who's Involved:
- CEO (required) - final positioning decision
- Product Lead (required) - understands technical dependencies
- Sales/BD Lead (if B2B) - understands customer/partner relationships
- Data/Analytics (if available) - quantifies dependencies
Process:
- List all upstream dependencies: Who do you NEED to operate? (platforms, suppliers, partners)
- List all downstream dependents: Who NEEDS you to operate? (customers, developers, partners)
- Map power dynamics: Who has pricing leverage? Who can replace whom?
- Identify keystone vs. peripheral relationships: Which relationships are existential vs. nice-to-have?
Deliverable: One-page Ecosystem Position Map
- Your position clearly labeled (keystone, engineer, application, etc.)
- Dependencies mapped with criticality scores (1-5)
- Power dynamics visualized (who has leverage over whom)
Success Metrics:
- 30 days: Identified 2-3 critical dependencies requiring mitigation
- 60 days: Initiated conversations with alternative suppliers/platforms
- 90 days: Reduced any single-partner dependency below 40% of revenue or traffic
Step 2: Identify Critical Dependencies
I learned about hidden dependencies the hard way.
In 2019, I was advising a Series B SaaS company processing $10M ARR. Their analytics infrastructure ran on Snowplow - an open-source event tracking system. Great choice: no vendor lock-in, self-hosted, full data ownership. The engineering team was proud of the independence.
Then we mapped their actual dependencies.
Snowplow required Scala expertise (they had one engineer who knew it). It ran on AWS Kinesis (proprietary AWS service). The data warehouse was Redshift (also AWS). The BI layer used Looker (recently acquired by Google, roadmap uncertain). The event validation schema was maintained by a contractor in Ukraine (no backup documentation).
I asked: "If any of these fail - Scala engineer quits, AWS changes Kinesis pricing, Looker deprioritizes your use case - what happens to your analytics?"
The CTO went pale. "We'd lose visibility into customer behavior. We wouldn't know which features drive retention. Product decisions would be guesses."
Their "independence" was an illusion. They'd just distributed their dependencies across five layers - each a potential single point of failure.
We spent six months building redundancy: cross-training engineers, documenting schemas, adding backup infrastructure. It cost $200K. But two years later, AWS deprecated a Kinesis feature with 90-day notice. The company migrated without losing data. That $200K investment prevented a $2M crisis.
That's why Step 2 exists.
In 2018, a B2B SaaS company built their entire product on a single cloud provider's proprietary database. Revenue grew to $50M ARR. The product worked beautifully. Customers loved it. Then the provider announced a competing product and deprecated key APIs with 90-day notice.
The company had two choices: rebuild core infrastructure in 3 months or shut down.
They chose rebuild. It cost them $8M, 18 months, and half their engineering team. They survived, but barely. The CEO later said: "We thought we were building a SaaS company. We were actually building a feature for someone else's platform."
That's the danger of hidden dependencies.
Ecosystems fail when keystone species or ecosystem engineers are removed. Identify your dependencies:
Dependency mapping table:
| Dependency Type | Question | Your Answer | Risk Level (1-5) | Mitigation |
|---|---|---|---|---|
| Single supplier | Is there one vendor you can't replace? | E.g., ASML for lithography | 5 (monopoly) | Dual-source or vertical integration |
| Platform lock-in | Does one platform control distribution? | E.g., AWS, App Store | 4 (high switching cost) | Multi-cloud or owned infrastructure |
| Payment processor | Does one company handle transactions? | E.g., Stripe, Visa | 3 (alternatives exist) | Add backup processor |
| Geographic concentration | Is production/talent in one location? | E.g., all servers in US-East | 4 (region failure risk) | Geographic diversification |
| Key customer | Does one customer represent >30% revenue? | E.g., Walmart to CPG brand | 5 (concentration risk) | Diversify customer base |
| Regulatory dependency | Does one rule enable your business? | E.g., ride-sharing app regulations | 4 (regulatory change risk) | Lobby or adapt business model |
For each dependency scored 4-5:
- Can you eliminate it? (Vertical integration, dual-sourcing)
- Can you reduce it? (Diversify suppliers/platforms/regions)
- Can you insure against it? (Contracts, hedging, legal protections)
- Can you accept it? (If elimination/reduction is too costly, acknowledge and monitor)
Boeing's dependency on Spirit AeroSystems (which manufactures 70% of Boeing's 737 fuselage) scores 5/5 risk - elimination is impossible (can't rebuild that manufacturing capability quickly), reduction requires years of dual-sourcing, insurance is difficult. When Spirit had quality issues in 2024, Boeing's entire 737 production line slowed. Single-supplier dependencies in complex manufacturing create systemic vulnerabilities.
Your goal: No single dependency scored 5/5 without mitigation plan.
⚠️ Common Mistake: Thinking "open source" or "multi-cloud" eliminates dependencies. It doesn't - it redistributes them. Open source still needs maintainers, expertise, and infrastructure. Multi-cloud still creates lock-in (tooling, workflows, team knowledge). Map the actual dependencies, not the marketing narrative.
Step 3: Assess Successional Stage
Picture a forest clearing after a wildfire.
Year 1: Bare soil, ash, intense sunlight. Only weeds and grasses survive - pioneers that tolerate harsh conditions.
Year 5: Fast-growing aspens and birches. They need the soil that pioneers created but now shade out the pioneers.
Year 20: Slower conifers establish. They outcompete aspens for light and nutrients. The aspens die.
Year 100: Old-growth mixed forest. Stable, diverse, slow-changing. Dominated by long-lived species.
Your market follows the same pattern. The question is: What stage are you in, and what comes next?
Chapter 8's succession framework (pioneer → seral → climax) determines strategy. Applying pioneer strategies to climax markets fails. Applying climax strategies to pioneer markets also fails.
Market successional diagnostic:
| Factor | Pioneer Stage | Seral Stage | Climax Stage |
|---|---|---|---|
| Infrastructure | Absent or unreliable | Emerging, gaps remain | Mature, widely available |
| Talent availability | Scarce, must train | Growing, some specialists | Abundant, intense competition for top talent |
| Regulation | Absent or ambiguous | Emerging, inconsistent | Mature, stable, enforced |
| Competition intensity | Low (few players) | Rising (new entrants) | Brutal (entrenched incumbents + startups) |
| Customer behavior | Experimental, high churn | Segmenting, some lock-in | Habitual, high switching costs |
| Capital availability | Scarce or speculative | Growing (VC interest) | Deep (PE, debt, public markets) |
| Technology maturity | Experimental, frequent failures | Stabilizing, best practices emerge | Standardized, incremental improvements |
If 5+ factors are "Pioneer": You're colonizing a new market.
- Strategy: r-selection (Chapter 7). Iterate fast, tolerate high failure rates, build infrastructure even if it doesn't generate immediate revenue, expect to be displaced by seral species.
- Metrics: Adoption rate, usage frequency, customer pain validation - revenue is secondary.
- Examples: Crypto protocols (2014-2017), generative AI (2022-2024), VR/AR ecosystems (2016-2024).
If 5+ factors are "Seral": The market is maturing, competition is intensifying.
- Strategy: Specialize. Pick niches. Build defensibility (network effects, data moats, customer lock-in). Expect consolidation - M&A will accelerate.
- Metrics: Market share, retention, margin improvement, competitive win rate.
- Examples: Cloud infrastructure (2015-2020), food delivery (2018-2022), D2C e-commerce (2015-2020).
If 5+ factors are "Climax": The market is mature.
- Strategy: K-selection (Chapter 7). Invest deeply, move slowly, protect existing customers. Innovation is incremental. Expect low growth but stable cash flow.
- Metrics: Customer lifetime value, retention, operational efficiency, margin protection.
- Examples: Enterprise ERP (SAP, Oracle), credit cards (Visa, Mastercard), legacy semiconductors (Texas Instruments analog chips).
Mismatches kill companies:
- Wii U (Chapter 7): Applied pioneer-stage strategy (motion controls, new hardware) to climax-stage gaming market (consumers entrenched in PlayStation/Xbox, mobile gaming mature). Failed.
- Jumia (Chapter 7): Applied climax-stage strategy (pan-African centralized logistics) to pioneer-stage African e-commerce (no infrastructure, cash-dependent consumers). Failed.
- Bangalore IT services (Chapter 8): Were pioneers in 1990s (built infrastructure, trained talent) but stayed in pioneer mindset (generalist outsourcing) when market moved to seral/climax (specialized R&D, product companies). Lost talent and mindshare to MNCs and startups.
Match your strategy to the market's successional stage, not your preferences or past success.
Step 4: Design for Trophic Position
Consider a coffee shop ecosystem:
- The power company provides infrastructure (electricity). The coffee shop pays a tiny fraction of revenue for energy. The power company serves millions of customers.
- The distributor manages the supply chain (beans, milk, supplies). The coffee shop pays 2-3% to the distributor. The distributor aggregates demand from thousands of cafes.
- The cafe creates the experience - brewing coffee, ambiance, service. Customers pay $5 for a latte that costs $1 to make.
- The food blogger aggregates recommendations. They capture attention (advertising revenue) without making or serving coffee.
Each layer captures value. Each depends on the layers below. That's trophic structure.
Your position in the trophic pyramid (infrastructure vs. platform vs. application vs. aggregator) determines how you capture value.
The 10% rule from biology: ~90% of energy is lost at each trophic level.
In business: ~90% of value created is captured by participants below you or above you in the stack.
Trophic position strategy matrix:
| Trophic Level | Position | Value Capture Strategy | Revenue Model | Defensibility Mechanism |
|---|---|---|---|---|
| Level 1: Infrastructure | Base of pyramid | Small % of massive volume | Usage fees, subscriptions | Lock-in via integration depth, switching costs |
| Level 2: Platform | Intermediary | 2-5% transaction fees | Take rate on transactions | Network effects, two-sided markets |
| Level 3: Application | Value delivery | Subscription or usage fees | SaaS, per-seat pricing | Product differentiation, feature velocity |
| Level 4: Aggregator | Attention capture | Advertising or premium tiers | Ad revenue, freemium | Data moats, habit formation |
Key insights:
The Power Inversion: In traditional business thinking, aggregators at the top of the pyramid (Google, Meta) hold power. In reality, infrastructure at the bottom (AWS, Visa, ASML) controls the ecosystem. Remove AWS, and billions in applications disappear. Remove Google, and AWS still serves millions of customers. Infrastructure providers look less powerful (smaller margins, invisible to consumers) but wield more leverage. The pyramid is inverted.
1. Infrastructure (Level 1) captures the smallest percentage but largest absolute volume.
- AWS captures 20-30% margin on $90B revenue = $18-27B profit. Applications built on AWS generate $500B+ revenue, but AWS doesn't capture that - it captures a small slice of enormous flow.
- Strategy: Optimize for volume, not margin. Price to maximize usage. Enable ecosystem growth - your revenue scales with ecosystem size.
2. Platforms (Level 2) balance volume and margin.
- Stripe captures 2.9% + $0.30 per transaction. Shopify captures 2-3% of merchant GMV. Platform economics work at scale: billions in transactions → billions in revenue.
- Strategy: Minimize friction (low take rates attract participants), maximize stickiness (integrations, data, workflows). The more participants, the more valuable the platform (network effects).
3. Applications (Level 3) face margin pressure but control user experience.
- SaaS tools (Slack, Zoom, Notion) charge $10-30/user/month. Competition is intense - dozens of alternatives in every category. Margins compress as markets mature.
- Strategy: Differentiate on features or workflows. Build switching costs (data, integrations, training). Move upmarket (enterprise customers pay more, churn less).
4. Aggregators (Level 4) capture attention, which converts to advertising or premium revenue.
- Google Search, Meta (Facebook/Instagram), YouTube, TikTok: free to users, monetized via ads. Advertising CPMs are low ($1-20 per 1,000 impressions), but scale compensates.
- Strategy: Maximize engagement (time spent, frequency). Build habit loops. Monetize via ads or premium tiers. Regulatory risk is highest here (antitrust, content moderation).
The trophic mismatch failure mode:
- Trying to capture Level 4 margins with Level 1 infrastructure: AWS can't charge Google-level advertising margins - it's infrastructure, not attention. Pricing too high reduces volume, killing the ecosystem.
- Trying to achieve Level 1 scale with Level 4 models: A social app can't charge AWS-level usage fees - users expect free. Monetization must come from ads or premium tiers, not usage.
Your trophic position determines your revenue model. Don't fight it - design for it.
⚠️ Common Mistake: Infrastructure companies trying to capture aggregator margins. You can't be AWS (Level 1, 20-30% margins on massive volume) and charge like Google (Level 4, 80%+ margins on attention). Pricing too high kills ecosystem growth. Accept the 10% rule - your leverage comes from volume, not margin.
Step 5: Evaluate Invasive Species Risk
Are you an invasive species (experiencing ecological release in a new market), or are you defending against one?
Invasive species diagnostic (Are you the invader?):
| Condition | Question | Your Status |
|---|---|---|
| Regulatory gaps | Are rules absent, ambiguous, or weakly enforced? | Yes/No |
| Capital asymmetry | Can you subsidize at a loss longer than competitors? | Yes/No |
| Naive competition | Are incumbents slow to adapt or unaware of threat? | Yes/No |
| Fragmented market | Is the market served by many small, local players? | Yes/No |
| Localization advantage | Do you understand local conditions better than global competitors? | Yes/No |
If 3+ = Yes: You're experiencing ecological release. You're an invasive species.
Strategy:
- Move fast: Capture supply and demand before regulation arrives or competitors adapt.
- Subsidize aggressively: Use capital to overwhelm competitors. Grab, Uber, WeWork, and Chinese EV companies all subsidized to capture market share.
- Build lock-in: Once dominant, raise prices and lock in customers (switching costs, network effects, habit formation).
- Prepare for regulation: Ecological release is temporary. Regulators will arrive. Lobby for favorable rules or adapt your model.
Invasive species failure mode: Burning capital without building defensibility. WeWork experienced ecological release (landlords unfamiliar with flexible office models, VCs willing to fund losses), but never built lock-in. When capital dried up, WeWork collapsed.
Defending against invasives:
If a competitor scores 3+ on the invasive species diagnostic, you're under attack.
Defense strategies:
- Regulatory capture: Lobby for rules that disadvantage the invader. Traditional taxis lobbied against Uber/Lyft. Hotels lobbied against short-term rental platforms. This works temporarily but rarely stops invasives permanently.
- Adaptation: Copy the invader's model. Hotels launched flexible booking and apartment-style options. Taxis launched apps (Uber-style). Adaptation is faster and cheaper than fighting.
- Capital matching: Raise capital to subsidize your own offerings. Go-Jek survived Grab's invasion of Indonesia by raising $5B+, matching Grab's subsidies.
- Niche retreat: Abandon mass market, focus on niches the invader ignores. Luxury hotels didn't compete with budget platforms on price - they competed on service, location, and brand.
Invasive species are unstoppable in the short term. Adaptation or niche retreat are the only sustainable defenses.
Step 6: Build Ecosystem Resilience (Avoid Single Points of Failure)
Keystone species create ecosystems. They also create systemic risk. If Visa's payment network went down tomorrow, global commerce would freeze. If AWS's us-east-1 region fails, half the internet goes down.
Resilience audit:
| Resilience Factor | Question | Score (1-5) | Action Required |
|---|---|---|---|
| Geographic diversity | Are operations in multiple regions? | 1 (single location) - 5 (global) | Open facilities in 2+ continents |
| Supplier diversity | Do you have backup suppliers for critical inputs? | 1 (single supplier) - 5 (many alternatives) | Dual-source or develop alternatives |
| Customer diversity | Is revenue spread across many customers? | 1 (one customer >50% revenue) - 5 (no customer >10%) | Diversify customer base |
| Technical redundancy | Can systems fail without business collapse? | 1 (single point of failure) - 5 (full redundancy) | Build failover systems, multi-cloud |
| Talent concentration | Is critical expertise held by few people? | 1 (1-2 keypeople) - 5 (distributed knowledge) | Document processes, cross-train |
If any factor scores 1-2: You have a single point of failure.
Mitigation strategies:
- Geographic diversity: Intel operates fabs across US, Ireland, Israel, reducing country-specific risk.
- Supplier diversity: Tesla uses multiple battery suppliers (Panasonic, CATL, LG Energy) to avoid single-source risk.
- Customer diversity: AWS serves millions of customers - no single customer loss collapses the business. Contrast with component suppliers where a single OEM customer represents >50% of revenue (single point of failure).
- Technical redundancy: Lyft runs on AWS but has failover infrastructure. If AWS fails, Lyft degrades but doesn't collapse entirely.
- Talent concentration: Google's "knowledge sharing" culture (design docs, internal wikis, code reviews) prevents critical expertise from being locked in single individuals.
The goal isn't eliminating all risk - it's ensuring no single failure collapses the system.
Step 7: Monitor for Trophic Cascades (Systemic Effects)
Ecosystems propagate changes. A shift at Level 1 (infrastructure) cascades to Level 4 (aggregators). A regulatory change affecting Level 4 cascades down to Level 1.
Trophic cascade early warning system:
| Cascade Type | What to Monitor | Potential Impact | Mitigation |
|---|---|---|---|
| Upstream change (Level 1→4) | Infrastructure pricing, availability, policy | Cost increase, capability loss, forced migration | Diversify infrastructure, lock in pricing |
| Downstream change (Level 4→1) | Aggregator behavior, user demand shifts | Volume reduction, margin pressure | Diversify customers, add value capture layers |
| Regulatory cascade | New laws at any level | Compliance costs, business model restrictions | Lobby, adapt model, geographic diversification |
| Competitive cascade | New entrant disrupting one level | Market share loss, margin compression | Monitor adjacent levels, adapt pricing/features |
| Technology cascade | Breakthrough enabling new capabilities | Obsolescence risk, new competition | Invest in R&D, acquire capabilities, partner |
Examples of trophic cascades:
Apple's App Tracking Transparency (ATT) policy (2021):
- Level 4 change (Apple policy): Users must opt-in to cross-app tracking
- Cascades to Level 3 (Apps like Facebook, Snap): Advertising targeting degrades → ad effectiveness drops 30-50% → ad revenue declines billions
- Cascades to Level 2 (Ad platforms): CPMs drop, advertisers shift budgets to Google (search ads unaffected), platform economics shift
- Cascades to Level 1 (Data infrastructure): Companies building identity graphs see demand collapse
One policy change → four-level cascade → billions in value destruction/creation.
Your monitoring system:
Create a quarterly review:
- Identify your trophic level (Level 1-4)
- List the levels above and below you
- Monitor changes at those levels:
- Pricing changes (infrastructure providers raising costs)
- Policy changes (platforms changing terms)
- Demand shifts (aggregators changing algorithms)
- Technology breakthroughs (new entrants with better capabilities)
- Simulate impact: If AWS raised prices 30%, what happens to your margins? If Google changed algorithm rankings, what's your backup traffic source? If customers shifted to a competitor's aggregator, how do you adapt?
- Build contingency plans: Don't wait for the cascade to hit - design responses now.
Trophic cascades are inevitable. The question isn't whether they'll happen - it's whether you'll detect them early enough to adapt.
Monday Morning Actions
This Week:
- Complete Step 1: Map your ecosystem position. Are you a keystone species, ecosystem engineer, platform, application, or pioneer? Write down your answer and the evidence supporting it.
- Complete Step 2: Identify your top 3 critical dependencies. What single suppliers, platforms, or customers represent single points of failure? Score each 1-5 for risk.
- Complete Step 3: Determine your market's successional stage. Is your market pioneer, seral, or climax? Does your current strategy match the stage?
This Month:
- Complete Step 4: Evaluate your trophic position. Are you Level 1 (infrastructure), Level 2 (platform), Level 3 (application), or Level 4 (aggregator)? Does your revenue model match your position? If not, what needs to change?
- Complete Step 5: Assess invasive species risk. Are you experiencing ecological release? Are competitors invading your market? Design a strategy for attack or defense.
- Address your highest-risk dependency from Step 2. If a dependency scored 4-5, initiate a mitigation project: dual-source a supplier, add a backup platform, or diversify your customer base.
This Quarter:
- Complete Step 6: Build ecosystem resilience. Audit geographic, supplier, customer, technical, and talent concentration. Address any factor scored 1-2.
- Complete Step 7: Set up trophic cascade monitoring. Identify the trophic levels above and below you. Assign someone to monitor changes quarterly. Build contingency plans for the top 3 potential cascades.
- Institutionalize ecosystem thinking. Add ecosystem position, dependencies, and cascade risks to your strategic planning process. Review quarterly. Update as your position or market evolves.
Stage-Specific Priorities
Your company stage determines which ecosystem factors matter most. Focus your energy where it creates maximum leverage:
| Company Stage | Critical Focus Areas | Why This Matters | Success Metrics |
|---|---|---|---|
| Seed ($0-2M ARR) | • Successional stage (Step 3) • Ecosystem position (Step 1) • Single critical dependency (Step 2) | You're resource-constrained. Know if you're pioneer (build infrastructure) or entering mature market (need differentiation). Identify your one existential dependency and have backup plan. | • Market stage identified • Positioning clear • Top dependency has mitigation plan |
| Series A ($2-10M ARR) | • Trophic position (Step 4) • Top 3 dependencies (Step 2) • Invasive species risk (Step 5) | You're scaling. Revenue model must match trophic position (infrastructure ≠ aggregator margins). Dependencies multiply - audit systematically. Watch for well-funded competitors exploiting ecological release. | • Revenue model matches position • 3 dependencies scored/mitigated • Competitive threats monitored |
| Series B+ ($10M+ ARR) | • Complete 7-step audit • Ecosystem resilience (Step 6) • Trophic cascades (Step 7) | You're operationally complex. Single points of failure can collapse operations. Platform changes cascade through your business. You need systematic monitoring and redundancy. | • All dependencies <30% concentration • Cascade monitoring in place • Quarterly ecosystem reviews |
Use this table to prioritize: Don't try to complete all 7 steps if you're seed stage. Focus on the 2-3 factors that actually threaten survival at your stage. As you scale, add complexity.
What Success Looks Like
You'll know ecosystem thinking is working when:
- You can articulate your ecosystem position: "We're a Level 2 platform intermediary in a seral-stage market, dependent on AWS (Level 1) and vulnerable to aggregator policy changes (Level 4)."
- Dependencies are diversified: No single supplier, platform, customer, or region represents >30% of critical operations.
- You detect cascades early: When Apple announced ATT, you predicted impact on your ad revenue 6 months before it hit and adapted pricing/targeting.
- Your strategy matches your successional stage: Pioneer markets get r-selection speed; climax markets get K-selection depth.
- You're building ecosystem value, not just extracting it: If you're infrastructure or a platform, you enable more value than you capture. Participants thrive, and the ecosystem grows.
You'll know you're failing when:
- You don't know your position: "We're a tech company" or "We have a marketplace" doesn't identify ecosystem role.
- Single points of failure exist: One supplier, customer, or platform holds veto power over your survival.
- You miss cascades: Regulatory changes, platform policy shifts, or technology breakthroughs blindside you because you weren't monitoring.
- Strategy mismatches stage: You're investing like a climax company in a pioneer market (moving too slowly) or iterating like a pioneer in a climax market (burning resources without defensibility).
- Value extraction kills the ecosystem: You raised take rates, participants fled, and the network collapsed (platform driver churn, AWS customers migrating to cheaper clouds).
Common Failure Modes
Failure Mode 1: Ignoring Keystone Dependencies
Companies assume suppliers, platforms, or infrastructure are stable and interchangeable. Then Stripe changes pricing, AWS has outages, or Google changes search algorithms - and businesses collapse.
Diagnosis: Do you have a written list of your keystone dependencies? If not, you're ignoring them.
Fix: Complete Step 2 (dependency mapping). For each dependency scored 4-5, start a mitigation project within 30 days.
Failure Mode 2: Mismatched Successional Strategy
Organizations apply strategies from one successional stage to another. Startups try to compete with climax-stage discipline (slow, expensive, high-quality) in pioneer markets (fast iteration required). Enterprises try pioneer strategies (burn capital, iterate wildly) in climax markets (competition is too intense, margins too thin).
Diagnosis: Does your strategy match the market's stage (pioneer/seral/climax)? If you're moving slowly in a pioneer market or burning capital in a climax market, you're mismatched.
Fix: Complete Step 3 (successional stage diagnostic). If mismatched, shift strategy within the quarter. Pioneer → r-selection. Climax → K-selection.
Failure Mode 3: Fighting Your Trophic Position
Infrastructure providers (Level 1) try to capture Level 4 margins by raising prices - killing the ecosystem. Aggregators (Level 4) try to achieve Level 1 scale by charging usage fees - users flee.
Diagnosis: Does your revenue model match your trophic level? Infrastructure should charge small %s of large volume. Aggregators should monetize attention (ads, premium), not usage.
Fix: Complete Step 4 (trophic position analysis). If your revenue model mismatches your position, redesign pricing within 90 days.
Failure Mode 4: Ignoring Invasive Species
Incumbents dismiss new entrants as "unsustainable" (Uber loses money) or "niche" (Tesla is for tech enthusiasts). Then the invader achieves ecological release, captures the market, and the incumbent collapses.
Diagnosis: Are new entrants subsidizing aggressively, operating in regulatory gray zones, or growing 50%+ YoY? If yes, you're under attack by an invasive species.
Fix: Complete Step 5 (invasive species diagnostic). If under attack, choose: adapt (copy their model), retreat (focus on niches they ignore), or match capital (raise funds to subsidize your own offerings). Don't ignore or dismiss.
Failure Mode 5: Extracting Without Enabling
Platforms raise take rates, infrastructure providers increase prices, or aggregators change algorithms - extracting more value without improving ecosystem health. Participants leave. The ecosystem collapses.
Diagnosis: Are participants (developers, suppliers, users) complaining about your policies or pricing? Is churn increasing? Are competitors gaining share by undercutting you?
Fix: Calculate the value you enable vs. the value you capture. If you're capturing >20% of value created on your platform, you're likely over-extracting. Reduce take rates or increase enablement (better tools, support, infrastructure).
Reflecting on Book 1: Foundations
You've completed Book 1: First Principles of Organizational Life.
We started with cells and membranes (Chapter 1), exploring how boundaries define organisms. We examined metabolism and resource management (Chapter 2 - assumed complete in this outline). We analyzed growth mechanisms and constraints (Chapter 3). We studied environmental sensing and feedback loops (Chapter 4). We traced reproduction, replication, and DNA transfer (Chapter 5). We mapped symbiotic relationships and mutualism (Chapter 6). We dissected natural selection, fitness, and adaptation (Chapter 7). We synthesized ecosystems, trophic levels, and systemic effects (Chapter 8).
Book 1's thesis: Organizations are organisms. Biology has 4 billion years of experimental data on what works and what fails. The mechanisms are universal, whether you're a bacterium, a finch, or a company.
What we've established:
- Cell theory → Organizational boundaries: Membranes control what enters and exits. Homeostasis maintains internal stability. Apoptosis kills parts for the good of the whole.
- Metabolism → Resource management: Burn rate determines longevity. Efficiency and adaptation determine survival.
- Growth → Controlled expansion: Growth plates limit size. Contact inhibition prevents cancer. Meristems enable renewal.
- Sensing → Feedback loops: Receptors detect signals. Transduction amplifies them. Negative feedback stabilizes. Positive feedback transitions.
- Reproduction → Scaling: Genotype replicates. Phenotype adapts. Asexual reproduction is fast but rigid. Sexual reproduction recombines. Horizontal transfer borrows.
- Symbiosis → Partnerships: Mutualism benefits both parties. Commensalism is one-sided but harmless. Parasitism extracts. Endosymbiosis integrates.
- Natural selection → Adaptation: Variation exists. Heritability propagates success. Differential survival determines fitness. Selection pressure shifts landscapes.
- Ecosystems → Systemic effects: Keystone species shape ecosystems. Ecosystem engineers build infrastructure. Trophic levels organize energy flow. Succession matures markets. Islands enable unique evolution. Invasives exploit release. Cascades propagate through networks.
Book 1 gives you the vocabulary and mechanisms. The subsequent books in the series apply these foundations to specific challenges: resource dynamics, environmental adaptation, coordination, aging and renewal, scaling through reproduction, competitive strategy, and ecosystem orchestration.
But you don't need to wait for the next book. The frameworks in Chapters 1-8 are immediately actionable. Map your membrane (Chapter 1). Audit your feedback loops (Chapter 4). Protect your DNA (Chapter 5). Classify your partnerships (Chapter 6). Measure differential survival (Chapter 7). Identify your ecosystem position (Chapter 8).
Biology doesn't care about your industry, your business model, or your revenue stage. The mechanisms work because they're fundamental. They worked before humans existed. They'll work after we're gone.
Your organization is an organism. Start treating it like one.
Key Concepts Summary
Ecosystem Structures:
- Keystone species: Disproportionate impact; removal collapses ecosystem (salmon, wolves, Visa, ASML)
- Ecosystem engineers: Modify habitat, enable others (earthworms, fungi, AWS, Visa)
- Trophic levels: Energy flow from producers → consumers → predators (infrastructure → platforms → applications → aggregators)
- 10% rule: ~90% of energy lost at each trophic level (same in business - infrastructure captures small % of massive volume)
Ecosystem Dynamics:
- Ecological succession: Markets mature in stages (pioneer → seral → climax)
- Pioneer species: Colonize harsh conditions, build infrastructure, get displaced
- Climax community: Stable, competitive, slow-changing (mature markets)
- Island biogeography: Size determines diversity; isolation determines uniqueness (Shenzhen, Singapore, Estonia)
- Invasive species: Ecological release when constraints removed (Uber, Grab, cane toads)
- Trophic cascades: Changes propagate through multiple levels (wolves → rivers, Apple ATT → ad collapse)
Niche Partitioning:
- Grinnellian niche: Where organism lives (geographic, habitat)
- Eltonian niche: What organism does (functional role)
- Specialization reduces competition, enables coexistence (Dutch flower auction)
Business Translation:
- Keystone species = ASML, Visa, ARM Holdings, Mastercard, Stripe (infrastructure)
- Ecosystem engineers = Platform providers, infrastructure companies
- Trophic levels = Infrastructure → Platforms → Apps → Aggregators
- Succession stages = Market maturity (crypto = pioneer, cloud = seral, ERP = climax)
- Island biogeography = Shenzhen, Bangalore, Singapore (isolated markets with unique evolution)
- Invasive species = Grab, WeChat, platform disruptors (ecological release, regulatory arbitrage)
- Trophic cascades = Platform policy changes affecting entire ecosystem
Framework Summary: The Ecosystem Diagnostic:
- Map your ecosystem position (keystone, engineer, platform, app, pioneer)
- Identify critical dependencies (single suppliers, platforms, customers)
- Assess successional stage (pioneer, seral, climax)
- Design for trophic position (infrastructure vs. platform vs. app vs. aggregator)
- Evaluate invasive species risk (are you invading or defending?)
- Build ecosystem resilience (diversify, eliminate single points of failure)
- Monitor for trophic cascades (upstream/downstream changes propagating)
Common Pitfalls:
- Ignoring keystone dependencies (payment processor changes, cloud provider outages)
- Mismatched successional strategy (pioneer speed in climax markets, or vice versa)
- Fighting your trophic position (infrastructure trying to capture aggregator margins)
- Ignoring invasive species (dismissing disruptors as "unsustainable")
- Extracting without enabling (platform raising take rates, killing ecosystem)
What Success Looks Like:
- You can articulate your ecosystem position
- Dependencies are diversified (no single point of failure)
- Strategy matches successional stage (r-selection for pioneer, K-selection for climax)
- You're building ecosystem value, not just extracting it
- You detect trophic cascades early and adapt
The Invisible Network
The salmon-forest connection took scientists decades to discover. For years, they studied salmon. They studied forests. They published papers on salmon biology and forest ecology. But they missed the truth because they were studying the parts separately.
The truth was in the relationship.
Your competitors are making the same mistake right now. They're optimizing their product. They're improving operations. They're analyzing market share. They're studying their own performance metrics. But they're missing the ecosystem - the invisible network of dependencies that determines who survives the next disruption.
Here's what ecosystem thinking reveals:
You don't control your fate alone. Your success depends on species you've never met, relationships you can't see, and feedback loops that span your entire network. The power company that keeps your servers running. The platform that delivers your traffic. The payment processor that handles your transactions. The regulatory environment that permits your business model. The talent pool that supplies your team.
Ignore the ecosystem, and you're a salmon swimming upstream, unaware that the forest depends on your journey - or that bears and eagles determine whether your nutrients reach the trees.
Understand the ecosystem, and you can position yourself as keystone infrastructure, design for succession, build antifragile networks, and create dependencies that make you irreplaceable.
Morris Chang bet his reputation on a foundry model that six major companies rejected. Thirty-seven years later, the entire tech industry depends on that bet. He didn't just build a company. He became the ecosystem's foundation.
The question isn't whether you're part of an ecosystem. You are. The question is: Do you understand your position?
References
Ecology and Ecosystem Dynamics
Helfield, James M., and Robert J. Naiman. "Effects of Salmon-Derived Nitrogen on Riparian Forest Growth and Implications for Stream Productivity." Ecology 82, no. 9 (2001): 2403–2409. https://esajournals.onlinelibrary.wiley.com/doi/10.1890/0012-9658(2001)082%5B2403:EOSDNO%5D2.0.CO;2 [PAYWALL]
Foundational study on salmon-derived nutrients in Pacific Northwest forests. Documents that trees near spawning streams derive approximately 22-24% of their foliar nitrogen from salmon. Reports significantly increased Sitka spruce growth rates near salmon streams - trees grow approximately half as fast in salmon-free areas.
Hilderbrand, Grant V., et al. "Keystone Interactions: Salmon and Bear in Riparian Forests of Alaska." Ecosystems 7 (2004): 655–666. https://link.springer.com/article/10.1007/s10021-004-0063-5 [PAYWALL]
Research documenting the salmon-bear-forest nutrient cascade. Shows that nitrogen influx to riparian forests is significantly increased only when both salmon AND bears are present - neither species alone produces the full effect. Bears distribute salmon carcasses throughout forests, extending nutrient transport beyond stream banks.
USGS. "Examining Soil's Role in Tracing Nutrients From Salmon into Riparian Trees." https://www.usgs.gov/news/examining-soils-role-tracing-nutrients-salmon-riparian-trees [OPEN ACCESS]
Recent research using 20-year salmon manipulation experiment in Bristol Bay, Alaska. Important methodological note: found that nitrogen isotope measurements in soil can exceed salmon values, suggesting some prior studies may have overestimated salmon's contribution to forest nitrogen. Demonstrates the complexity of ecosystem nutrient tracking.
University of Victoria. "The Salmon Forest Project." https://web.uvic.ca/~reimlab/salmonforest.html [OPEN ACCESS]
Long-term research project documenting salmon-forest connections. Reports that around salmon-rich rivers, 40-80% of nitrogen in shrubs and trees originates from the ocean, transported inland by spawning salmon and distributed by bears and other scavengers.
Ripple, William J., and Robert L. Beschta. "Trophic Cascades in Yellowstone: The First 15 Years After Wolf Reintroduction." Biological Conservation 145, no. 1 (2012): 205–213. https://www.sciencedirect.com/science/article/abs/pii/S0006320711004046 [PAYWALL]
Comprehensive analysis of the Yellowstone wolf reintroduction trophic cascade. Documents: wolves extirpated by mid-1920s; reintroduced 1995-96; elk populations decreased; aspen browsing dropped from 100% (1998) to under 25% (2010); beaver and bison populations increased. Notes that northern Yellowstone "still appears to be in the early stages of ecosystem recovery."
Yellowstone Park. "Wolf Reintroduction Changes Ecosystem." https://www.yellowstonepark.com/things-to-do/wildlife/wolf-reintroduction-changes-ecosystem [OPEN ACCESS]
Accessible summary of trophic cascade effects. Reports that willows grew to five times original size within six years of wolf reintroduction, enabling beaver recovery. Notes ongoing scientific debate about relative importance of wolves versus other factors (human hunting, bison competition, precipitation patterns).
IFLScience. "Do Wolves Fix Ecosystems? Yellowstone, Trophic Cascades, And The Big Debate Racking Ecologists Right Now." https://www.iflscience.com/yellowstones-wolves-and-the-controversy-racking-ecologists-right-now-81736 [OPEN ACCESS]
Balanced overview of the scientific debate. Quotes Dan MacNulty (Utah State University): "What's not in doubt in my mind is whether a trophic cascade has happened or not. The question boils down to how strong is that cascade?" Documents that wolf effects vary significantly across different areas of the park.
Darwin, Charles. The Formation of Vegetable Mould Through the Action of Worms, with Observations on their Habits. London: John Murray, 1881. https://darwin-online.org.uk/content/frameset?pageseq=1&itemID=F1357&viewtype=text [OPEN ACCESS - Full Text]
Darwin's final scientific book, documenting his 40-year study of earthworms as ecosystem engineers. Calculated 53,767 worms per acre, moving 10-18 tons of soil annually to the surface. Concluded that worms "have played a more important part in the history of the world than most persons would at first suppose."
Darwin Correspondence Project. "Casting About: Darwin on Worms." https://www.darwinproject.ac.uk/commentary/life-sciences/casting-about-darwin-worms [OPEN ACCESS]
Scholarly commentary on Darwin's earthworm research. Documents that "Worms" initially outsold "On the Origin of Species" with 6,000 copies in the first year. Explains Darwin's 29-year experiment measuring the rate stones are buried by earthworm activity.
Business Case Studies
CNBC. "ASML Is the Only Company Making the $200 Million Machines Needed to Print Every Advanced Microchip." March 23, 2022. https://www.cnbc.com/2022/03/23/inside-asml-the-company-advanced-chipmakers-use-for-euv-lithography.html [OPEN ACCESS]
Primary source documenting ASML's monopoly on EUV lithography. Reports that ASML's TWINSCAN NXE:3600D costs up to $200 million per machine, weighs 180 tons, requires three Boeing 747s to transport, and contains over 100,000 components. Essential for manufacturing 7nm, 5nm, and 3nm semiconductor nodes.
Wikipedia. "ASML Holding." https://en.wikipedia.org/wiki/ASML_Holding [OPEN ACCESS]
Comprehensive overview of ASML as the sole global supplier of EUV lithography equipment. Documents that as of 2023, ASML had shipped approximately 140 EUV systems (not 50 as originally estimated). Notes that ASML is the largest supplier to the semiconductor industry.
The Generalist. "ASML: A Monopoly on Magic." https://www.generalist.com/briefing/asml [OPEN ACCESS]
Analysis of ASML's keystone position in the semiconductor ecosystem. Explains how ASML's monopoly emerged from decades of R&D investment and the extraordinary technical difficulty of EUV lithography. Documents that no other company has successfully developed competing EUV technology.
Wikipedia. "Extreme Ultraviolet Lithography." https://en.wikipedia.org/wiki/Extreme_ultraviolet_lithography [OPEN ACCESS]
Technical overview of EUV lithography explaining why ASML's monopoly is so difficult to challenge. Documents the multi-decade development timeline and the fundamental physics challenges that make EUV manufacturing extraordinarily complex.
Sources & Citations
The biological principles in this chapter are grounded in peer-reviewed research. Explore the full collection of academic sources that inform The Biology of Business.
Browse all citations →Want to go deeper?
The full Biology of Business book explores these concepts in depth with practical frameworks.