Escape Velocity by Geoffrey Moore — Cliff Notes Summary

The outcome you should expect

Readers who work through Escape Velocity should expect a specific, falsifiable outcome rather than a vague strategic mood: a company that applies the Hierarchy of Powers correctly can identify, within a single budgeting cycle, exactly which 10-20% of its operating expense, headcount, and executive hours are trapped servicing mature-product gravity instead of funding the next category. That is the "escape velocity threshold" Moore names directly — not a metaphor but a measurable reallocation target. The expected outcome is not instant transformation; it is a diagnosis sharp enough that leadership can no longer pretend the current portfolio reflects the stated strategy.

Concretely, a team that runs Moore's resource allocation audit typically discovers that 70-80% of spend is funding Execution Power and Offer Power inside businesses that are already mature — polishing a product line, protecting a sales motion, defending a support SLA — while Category Power, the only tier capable of compounding at 30%+ annually, receives 5-10% or less. That gap is the book's entire diagnostic payoff. Once a leadership team sees the gap in their own numbers, the Escape Velocity framework predicts a second outcome: resistance. Moore calls these organizational "antibodies," and he is explicit that seeing the gap and closing the gap are two different projects requiring two different kinds of effort.

The outcome also depends on role. A CEO or board member should expect a capital-allocation lens that reframes strategy as a portfolio decision — Horizon 1 (core), Horizon 2 (adjacent), Horizon 3 (new category) — rather than a plan. A CFO should expect friction, because Moore's prescribed allocation deliberately funds Horizon 3 bets that cannot yet produce an ROI projection, which is the exact kind of spend finance organizations are built to reject. A sales or GTM leader should expect clarity about why their pipeline behaves the way it does: a legacy product line in a 2%-growth category will never generate the deal velocity of a Horizon 3 bet in a 30%-growth category, no matter how good the reps are, because Category Power sits above Execution Power in the hierarchy and caps what execution alone can achieve.

The long-run outcome Moore is actually selling is organizational: a company that repeats this audit annually, tracks its percentage allocation against the 70/20/10 revenue target and the 45/30/25 attention target, and defends Horizon 3 with a separate P&L and separate leadership stops losing its future by accident. Companies that skip the audit don't choose to under-invest in the next category — they drift there, one quarter of political budget negotiation at a time, and Escape Velocity's core promise is that the drift is visible and reversible the moment someone measures it.

What drives that outcome

What actually produces the outcome above is the Hierarchy of Powers itself — a strict ranking Moore insists most executives get backwards. The five tiers, from highest leverage to lowest, are Category Power, Company Power, Market Power, Offer Power, and Execution Power, and the mechanism driving the whole book is that most companies invest in inverse proportion to this ranking: heaviest at the bottom (Execution), lightest at the top (Category).

Category Power is the growth rate, size, and durability of the market category itself. It drives the outcome because it is the only tier that can compound for a decade — Moore's example is Apple choosing to enter smartphones, a fast-growing category, rather than continuing to defend Mac share in a mature one. Company Power is relative position inside that category, captured in Moore's taxonomy from Inside the Tornado: Gorilla (dominant, high switching costs), Chimp (credible #2 or #3), Monkey (commodity follower on price). Market Power is geographic or segment dominance — a company can be Gorilla in one vertical and Monkey in another with the identical product. Offer Power is specific product superiority, which Moore deliberately ranks fourth because a superior offer without the tiers above it is "Betamax territory": technically better, commercially irrelevant. Execution Power — operational excellence, sales productivity, supply chain — sits last because it is the most measurable, the most defensible quarter over quarter, and therefore the most over-funded tier in every mature company Moore studied.

The driving mechanism is that capital allocation decisions get made politically — by whoever has the most headcount, the loudest quarterly numbers, or the most tenured leader — rather than by where market power structurally lives. Moore's fix is to force every allocation decision through the hierarchy as a filter: before funding a request, ask which tier it serves, then ask whether that tier is even the right one to be fighting in. A request to improve Execution Power inside a Monkey-position, 2%-growth category should lose to a Category Power bet almost automatically, yet in practice it rarely does, because Execution requests come with clean ROI math and Category bets don't. That asymmetry in how easy each tier is to justify on paper — not any actual disagreement about strategy — is what keeps gravitational pull in place long after leadership intellectually agrees with Moore's argument.

Benchmarks and realistic ranges

Moore supplies concrete numbers throughout the book, and they are the part practitioners actually use once they put the Cliff Notes version down. On margin: Gorillas earn roughly 4-8x the margin of Chimps in the same category, and Chimps earn roughly 2-3x the margin of Monkeys — a spread that explains why Company Power alone, independent of product quality, drives most of the profit variance inside a mature category. On timeline: Moore's prescription is that if a business cannot become a Gorilla or a credible Chimp within 3-5 years of entering a category, the right move is to exit and redeploy the capital rather than keep funding Execution Power improvements that cannot change the underlying position.

On the resource allocation audit itself, the realistic range Moore documents across established companies is that 70-80% of operating expense, headcount, and executive time ends up funding Execution and Offer Power inside already-mature lines, while Category Power bets receive 5-10% or less — and he notes that leadership teams are consistently and genuinely surprised by this ratio when they map it for the first time. The target Moore recommends to correct it is roughly 70/20/10 by revenue and capital across Horizon 1 (core), Horizon 2 (adjacent), and Horizon 3 (new category), but — and this is the benchmark most readers miss — management attention and best-people deployment should run closer to 45/30/25, because new categories need disproportionate leadership even when they don't yet need disproportionate dollars.

The "escape velocity" threshold itself is defined as the 10-20% of total company resources that must be deliberately redirected from past-product gravity to future-category investment to achieve a genuine next-category breakout; below that range, Moore's position is that the bet is underfunded theater rather than a real Horizon 3 commitment. These ranges are not laboratory-precise — Moore is working from consulting engagements and case pattern-matching, not a controlled study — but they function well as sanity-check benchmarks: if your own audit shows Category Power funding under 5% or Horizon 3 attention under 30%, you are solidly inside the pattern Moore wrote the book to correct, and if your Gorilla-position margins aren't outperforming your Chimp-position lines by multiple times, your Company Power claim probably doesn't match reality.

Risks, edge cases, and failure modes

The most common failure mode is the one Moore spends two full chapters on: organizational antibodies. The CFO who demands an ROI projection from a Horizon 3 bet before it has customers, the head of sales who wants quota relief on the legacy product line instead of a reallocation of selling resources, and the board that questions why margins compressed this quarter are not villains in Moore's telling — they are rational actors responding to the incentives and metrics the company already has in place, and those incentives will kill a Horizon 3 investment through a thousand small budget cuts unless it is structurally protected. Moore's prescribed defense requires all four elements together — a separate P&L, a separate leadership team, separate leading-indicator metrics instead of revenue, and direct CEO air cover — and the recurring edge case is a company that implements only two or three of the four and then is confused when the antibodies still win.

A second failure mode is misapplying Offer Power as if it were Category Power — building a genuinely superior product inside a category with no growth and no clear Company Power path, which Moore's Betamax example captures precisely: technical superiority that never becomes commercial relevance because the tiers above it were never secured. A third, subtler failure mode affects the diagnosis itself: a company can correctly identify that it is over-invested in Execution Power and still misallocate the fix by moving capital into Offer Power (a "better" version of the mature product) rather than Category Power (an actual new market), because Offer Power improvements are easier to scope, staff, and measure than a genuine category bet.

There is also a buyer-side edge case worth naming for sales leaders specifically: an enterprise account whose own CFO is fully allocated to Execution Power in mature lines has no budget line for a Horizon 3 transformation pitch, so a vendor selling a category-defining story into that account is selling into a buyer who structurally cannot say yes — the correct move is to reframe as a Horizon 1 efficiency or cost-reduction sale instead, matching the pitch to the buyer's actual hierarchy position rather than the seller's preferred narrative. Finally, the modern-era risk Moore's framework surfaces but the 2011 text couldn't name is platform cannibalization risk — a company funding its own disruptive category (an AI feature line, for instance) inside the same P&L as its legacy cash cow almost always under-funds the new bet, which is exactly why Moore's antibody defense insists on a separate P&L in the first place.

A practical rollout plan

Moore's own chapters sequence into a usable rollout, and the practical version practitioners run looks like this. First, conduct the resource allocation audit: map every dollar of operating expense, every headcount, and every executive hour to one of the five hierarchy tiers — Category, Company, Market, Offer, Execution — without regard to which department currently claims the spend. Second, classify the same spend into the three horizons: Horizon 1 core, Horizon 2 adjacent extension, Horizon 3 new category. Third, compare the resulting percentages against the 70/20/10 revenue-and-capital benchmark and the 45/30/25 attention benchmark, and treat any large gap as the finding, not a problem to explain away. Fourth, for whichever Horizon 3 bet the company intends to fund seriously, stand up all four antibody defenses simultaneously — separate P&L, separate leadership, separate leading-indicator metrics, and explicit CEO air cover — because Moore's case evidence is that partial protection fails at the same rate as no protection. Fifth, revisit the audit on a fixed cadence, ideally annually tied to the planning cycle, since gravitational pull reasserts itself every budget season if nothing is actively holding the reallocation in place.

Moore's own cited example of this rollout working at enterprise scale is Lou Gerstner's turnaround of IBM in the 1990s, which he frames explicitly as a portfolio-rebalancing exercise rather than a strategy exercise — the strategy didn't change nearly as much as the allocation did. The modern parallel readers will recognize immediately is Microsoft funding Copilot at the expense of legacy Office margins under a structure that matches Moore's prescription almost exactly: a separate P&L, dedicated leadership, and visible CEO air cover from Satya Nadella. Google's defense of Search against its own AI Overviews, and Salesforce's Agentforce push against its legacy per-seat CRM model, are both the same Category-Power-versus-Company-Power tension playing out in real time, which is the strongest evidence that Moore's 2011 rollout sequence still works unchanged in the AI era — the only thing that has changed is which category companies are racing to escape into.

Related questions

Where does Escape Velocity sit in Geoffrey Moore's six-book arc?

It's the fifth of six: Crossing the Chasm (1991) → Inside the Tornado (1995) → Living on the Fault Line (2000) → Dealing with Darwin (2005) → Escape Velocity (2011) → Zone to Win (2015). It introduces the capital-allocation discipline that Zone to Win later operationalizes.

How is Escape Velocity different from Crossing the Chasm?

Crossing the Chasm is about getting one new product adopted by a mainstream market. Escape Velocity is about an already-successful company deciding how much capital to pull away from that mature product to fund the next one.

Does the book apply to startups or only incumbents?

It's written for mature companies with gravitational pull to escape, but the Hierarchy of Powers is equally useful for startups choosing which category to enter in the first place.

What's the fastest way to apply this without reading the whole book?

Run the five-tier resource allocation audit on last year's budget and headcount, then compare the result to the 70/20/10 and 45/30/25 benchmarks — that single exercise captures most of the book's practical value.

FAQ

What is the single most important idea in Escape Velocity? The Hierarchy of Powers: Category beats Company beats Market beats Offer beats Execution. Most companies default to funding Execution and Offer because they're the easiest to measure, even though Category and Company are where real competitive advantage actually lives.

Why does Moore rank Execution Power last in the hierarchy? Because it's the most over-funded and most easily replicated tier in a mature company. Operational excellence inside a declining category is, in Moore's words, rearranging deck chairs — necessary but never sufficient on its own.

What's the actual 70/20/10 split used for? It's the recommended revenue-and-capital allocation across Horizon 1 (core mature business), Horizon 2 (adjacent growth), and Horizon 3 (new category bets). Management attention should skew further toward Horizon 3, closer to a 45/30/25 split, because new categories need leadership more than dollars.

Is Escape Velocity still relevant for AI-era companies? Yes — arguably more relevant now. The framework predicts the Microsoft Copilot versus legacy Office tension, Google Search versus AI Overviews, and Salesforce Agentforce versus seat-license CRM almost exactly, decades before any of them existed.

Should I read Escape Velocity or Zone to Win first? Read Escape Velocity first if you're a CEO, CFO, or board member focused on portfolio and capital allocation. Read Zone to Win first if you're a COO or business-unit leader focused on operating cadence — they're complementary halves of the same strategy.

What company examples does Moore use to make the argument concrete? Cisco, SAP, Microsoft, and Hewlett-Packard as incumbents wrestling with gravitational pull; Apple's smartphone entry and Lou Gerstner's IBM turnaround as successful portfolio rebalancing; Oracle as a database-era Gorilla.

Sources

• https://en.wikipedia.org/wiki/Geoffrey_Moore_(author)
• https://www.harpercollins.com/products/escape-velocity-geoffrey-a-moore
• https://en.wikipedia.org/wiki/Crossing_the_Chasm
• https://www.mckinsey.com/capabilities/strategy-and-corporate-finance/our-insights/enduring-ideas-the-three-horizons-of-growth
• https://en.wikipedia.org/wiki/The_Innovator%27s_Dilemma
• https://en.wikipedia.org/wiki/Louis_V._Gerstner_Jr.
• https://www.goodreads.com/book/show/9961796-escape-velocity
• https://hbr.org/topic/subject/strategy

Related on PULSE

• Zone to Win by Geoffrey Moore — Cliff Notes Summary
• Inside the Tornado by Geoffrey Moore — Cliff Notes Summary
• Crossing the Chasm by Geoffrey Moore — Cliff Notes Summary
• What is the Hierarchy of Powers in RevOps strategy?