Play Bigger by Ramadan, Peterson, Lochhead, Maney — Cliff Notes Summary

Two ways to grow: compete inside a category, or design one

Every go-to-market plan eventually resolves to one of two strategies, and Play Bigger's entire argument is that most companies pick the first one by accident rather than by decision.

Option A — compete inside an existing category. You accept the market's existing definition of the problem, the existing vocabulary, the existing buying criteria, and the existing analyst quadrant. Your job becomes relative: be faster, cheaper, better-supported, easier to deploy than the incumbents. This is the default for roughly 90% of B2B software companies. The playbook is well-understood — competitive battlecards, feature parity matrices, displacement plays, aggressive pricing, land-and-expand. It is also comfortable, because the buyer already has a budget line for what you sell. The buyer knows what "CRM" is, what "MDM" is, what "APM" is; you are arguing about which vendor fills the slot.

Option B — design a new category. You reject the existing definition of the problem and teach the market a new one. Instead of arguing that you are a better CRM, Salesforce argued that on-premise enterprise software itself was the problem — the famous "End of Software" campaign, complete with protest-style theatrics outside a Siebel conference. The buyer had no budget line for what Salesforce sold, so Salesforce created the line. That is the hard part and the whole game: category design requires you to fund the education of the market before you can harvest demand from it.

The trade-off is honest and worth stating plainly. Option A has a shorter time-to-first-revenue, a known buyer, and a predictable sales motion; its ceiling is the 17% and 7% share bands. Option B has a longer runway to revenue, requires a buyer who does not yet know they have the problem, and burns money on evangelism that will not convert this quarter; its ceiling is the 76% band plus a valuation multiple that prices the whole category rather than your ARR.

A third path exists in practice, and the book acknowledges it obliquely: category extension. You enter an existing category to establish credibility and cash flow, then use that beachhead to condition a new adjacent category. Amazon's arc — retail, then AWS, then Marketplace, then Prime — is the canonical example. Each new category orbited the original and reused the same operational spine. This path is slower than pure category design but far less binary, because a failed category attempt does not kill the company.

The choice is not aesthetic. It determines your hiring plan, your budget split between demand-gen and evangelism, your analyst relations strategy, your pricing model, and whether your CEO spends time on product reviews or on stage.

How to decide which strategy your company should run

The decision hinges on four questions, and the book's most useful diagnostic is deceptively simple: write down the problem your company solves in one paragraph, without naming your product or your category. Then read it back. If it sounds like a problem the market already has a name for — "our data is siloed," "our reps don't follow the process," "our uptime is bad" — you are not designing a category. You are competing inside one, and you should stop pretending otherwise and run the Option A playbook properly.

If the paragraph describes a problem people are working around with spreadsheets, headcount, or resignation — a problem with no vendor category attached to it — you may have a category on your hands.

Four practical gates to run before committing:

1. Is there a genuinely new problem, or just a new answer to an old one? The authors' distinction is between a *different answer* and a *different question*. Faster observability is a different answer. "Your engineers cannot reason about a system nobody fully understands" is a different question. Only the second one supports category design.
2. Can you fund three to five years of conditioning? Category creation is front-loaded spend. If your runway assumes payback in four quarters, you cannot run this strategy honestly, and attempting it half-funded produces the worst outcome — you educate the market and a better-capitalized fast-follower harvests it.
3. Does your CEO want the job? The book is emphatic that category design is a leadership discipline, not a marketing function. It proposes a Chief Category Officer — usually the CEO, sometimes a dedicated CMO — who owns the category as a P&L line. If the CEO delegates the point of view to a product-marketing manager, the category will not form.
4. Is the timing right? Categories form when a technology shift, regulatory change, or behavioral shift makes the old workaround untenable. Cloud made "End of Software" credible in 2000 in a way it would not have been in 1995.

One caveat worth naming: the diagnostic above is a filter, not a guarantee. Plenty of companies write a genuinely novel problem paragraph and still fail, because the problem is real but not urgent, or because the buyer who feels the pain has no budget authority. The book's framework tells you whether category design is *available* to you. It does not tell you whether the category is *big enough* to be worth designing.

The numbers behind each path

The book's headline number is the 76/17/7 split, drawn from the authors' analysis of public-company market capitalization across new categories over roughly a 25-year window ending in the mid-2010s. The Category King captures approximately 76% of the market cap created inside the category. The second-place player captures about 17%. Everyone from third place down splits the remaining ~7%.

Sit with what that implies. Being the clear #2 in a large category is worth roughly a fifth of being #1. Being #4 is worth almost nothing on a ten-year horizon, regardless of how good the product is. The strategic conclusion the authors draw is that it is better to be #1 in a smaller, newly defined category than #5 in a large established one — because the #1 position comes with a market-cap multiplier that revenue alone does not explain.

That multiplier is the second number that matters, and it is qualitative rather than precise. Category Kings command valuation multiples above comparable-revenue peers because public investors are pricing the option value of the entire category, not the current revenue run-rate. The book cites VMware in server virtualization, LinkedIn in professional networking, Tableau in self-service BI, ServiceNow in IT service management, and Workday in cloud HCM as companies that traded at premiums their revenue scale alone did not justify. In the decade after publication, the same pattern showed up in Snowflake, Datadog, and Atlassian — each of which named its category and became the reference implementation of it.

Costs on the category-design side are real and rarely modeled honestly:

• The point of view document. The book specifies a manifesto-style essay in the range of 8–15 pages. The writing itself costs weeks of senior time, not dollars. The expensive part is the organizational alignment behind it — every exec has to actually agree.
• The Lightning Strike. A concentrated launch moment consumes a large share of an annual marketing budget in a single quarter — event production, content, analyst briefings, press, partner co-marketing, paid amplification. The book's argument is that this concentration is the point; the same money spread across twelve months produces no imprint at all.
• Evangelism headcount. Category conditioning needs people whose job is teaching, not closing. That headcount does not carry a quota and will look like waste on a standard sales-efficiency dashboard for the first several quarters.
• Opportunity cost. Every dollar and every executive hour spent teaching the market a new problem is a dollar not spent on competitive displacement in a category that already has budget.

Against those costs, the Option A numbers are more modest but far more predictable: a known buyer, existing budget, a shorter sales cycle because the buying committee already understands the category, and a lower cost of first revenue. What you are buying with that predictability is a permanent cap on your share of the outcome.

A word of caution on the 76% figure itself. It is a finding from a specific dataset over a specific window, presented by authors who also run a consulting practice built on the conclusion. The directional claim — that category leadership is worth vastly more than category participation — is well supported by ordinary observation of winner-take-most technology markets. The precise decimal should be treated as a strong heuristic rather than a physical constant, and any board deck that cites "76%" as if it were a law of nature is over-reading the source.

Building the category: sequence, artifacts, and the Lightning Strike

The book's operating sequence is four moves, and the ordering matters more than any individual step.

Discover the problem. Not the solution. The exercise described above — the product-free problem paragraph — is the entry point. Teams routinely skip it because they already believe they know the problem, and they routinely discover on the second or third rewrite that what they had was a feature complaint dressed up as a market thesis.

Frame the From / To. Articulate the old broken world and the new designed world in a single sentence. Salesforce: *from on-premise enterprise software → to no software.* Birchbox: *from buying full-size cosmetics blind → to a monthly curated discovery box.* Slack: *from internal IM as an IT utility → to team chat as the place work happens.* The From/To is what gives a customer permission to switch — it reframes their current setup as a legacy state rather than a working system.

Write the point of view document. The POV is the source code of the category: 8–15 pages naming the problem, the From/To, the new world, the category's name, and the company's role in it. It is explicitly not a pitch deck. Every downstream artifact — press release, sales script, hiring pitch, board narrative, analyst briefing — should be derivable from it. Benioff's "End of Software" and Aaron Levie's "cloud content management" framing at Box are the textbook examples. When a company's messaging drifts, the fix is usually that nobody re-read the POV, not that the copywriter failed.

Build company and category in parallel. The most common and most expensive error the authors identify is building the company first and retrofitting a category story onto it later. Org design, hiring, and ops need to be built alongside the point of view, evangelism, and language — from the start. A sales org hired to sell against a feature comparison will not sell a category, and retraining it later is harder than hiring for it initially.

Then the Lightning Strike. This is the book's most distinctive contribution and its most quotable line: slow and steady loses to bold and sudden. Rather than launching softly and iterating toward awareness, category designers concentrate budget, content, partnerships, press, and product into a single coordinated moment that imprints the category on customers, analysts, employees, and investors simultaneously. The reference case is Apple's January 2007 iPhone keynote — one hour that redefined what "smartphone" meant and left Nokia, BlackBerry, and Palm arguing about a category that no longer existed as they understood it.

Operationally, the Lightning Strike is executed through a Mission Day with three components: a massive content drop (the POV, customer cases, analyst briefings landing together), a public anchor moment (keynote, founder interview, press blitz), and a post-event activation engine (sales sequences, partner co-marketing, follow-up content that converts the attention into pipeline). Dreamforce and INBOUND are recurring Lightning Strikes — annual re-conditioning of the category rather than one-time launches.

Two adjacent workflows deserve mention because they change how this sequence runs in practice.

Product-led growth complicates the launch-day model. Notion, Linear, and Figma conditioned their categories substantially through bottom-up adoption — the product itself did the teaching, one team at a time, before any keynote existed. That is a genuine amendment to the 2016 framing. What is notable is that the Lightning Strike pattern tends to reassert itself once a PLG company crosses a certain scale and needs to reach buyers who will never discover it organically. Figma's Config is a Lightning Strike by any reasonable definition. The honest reading is that PLG changes the *sequence* — conditioning before the strike rather than the strike as conditioning — not the underlying need for a defining public moment.

Defense is a different discipline than creation. Once you are the King, the book prescribes three defensive moves: ecosystem building (developers, integrators, partners — AppExchange is the reference case), standards capture (defining the metrics, certifications, and job titles the market expects, which is what HubSpot's inbound certification accomplished), and continuous extension into adjacent categories. The most dangerous moment for a Category King is not a competitor shipping better features — it is a competitor beginning to condition a *different* category around your customers. That is a signal to move the roadmap toward narrative and ecosystem, not toward feature parity.

Where the book sits in the canon, and what to read alongside it

Play Bigger belongs to a clear lineage, and reading it in isolation makes it seem more original than it is — and less useful than it can be.

Ries and Trout's *Positioning* (1981) and *The 22 Immutable Laws of Marketing* (1993) established that the battle is fought in the customer's mind and that being first in a category beats being better. Geoffrey Moore's *Crossing the Chasm* (1991) supplied the adoption-curve mechanics — the gap between early adopters and the pragmatist majority, and the beachhead strategy for crossing it. Seth Godin's *Purple Cow* (2003) argued that remarkability, not advertising spend, is what makes something spread.

Play Bigger's contribution on top of that inheritance is operational. It takes positioning — historically a marketing deliverable that produced a messaging document and then sat in a shared drive — and converts it into a company-wide operating system with named artifacts (the POV document), named events (the Lightning Strike, Mission Day), a named owner (the Chief Category Officer), and a quantified prize (the 76% band). That translation from concept to operating cadence is why the book stuck with founders in a way that pure positioning theory did not.

Christopher Lochhead's follow-on *Niche Down* (2018) and his *Follow Your Different* podcast extended the discipline for a broader audience, including personal and professional-services positioning, where the same "different, not better" logic applies with far less capital required.

For a practitioner assembling a reading stack, a reasonable order is: *Crossing the Chasm* for adoption mechanics, *Positioning* for the mental-real-estate argument, *Play Bigger* for the operating system, and Benioff's *Behind the Cloud* as a first-person account of the canonical Lightning Strike being executed in real time. Frank Slootman's *Amp It Up* is a useful counterweight — it is far more focused on operational intensity and raising standards than on narrative, and reading the two together prevents the failure mode where a team writes a beautiful POV and never ships anything against it.

The most common misreading of this book is treating category design as permission to invent a category name and put it on a website. Naming is the last step, not the first. A category that nobody outside your marketing team uses is not a category — it is jargon, and analysts and buyers punish it. The market has to adopt the language for the language to be worth anything, and adoption comes from conditioning over years, not from a rebrand.

What has aged, and what has held up

Held up. The core economic claim has aged well. The winner-take-most dynamic in software has, if anything, intensified since 2016. Snowflake in cloud data warehousing, Datadog in observability, Figma in collaborative design, Linear in modern issue tracking, Notion in the workspace category — each named the problem, ran a multi-year conditioning campaign, and captured a disproportionate share of the value created in its category. The POV document is now a standard founder artifact, taught in accelerator programming and product-marketing curricula. The From/To construct in particular has proven durable because it is cheap to test: if the "from" state does not sound broken to a buyer, the category is not ready.

Aged. Three things.

First, the case studies skew heavily pre-2015 and heavily enterprise-software, which makes the book feel dated to readers working in AI, developer tools, or consumer subscription. The frameworks transfer; the examples require translation.

Second, the launch-day emphasis undersells slow-burn category formation. Some categories formed without any single defining moment, accumulating instead through developer adoption and word of mouth. The book's rhetorical insistence that slow-and-steady always loses is stronger than the evidence supports.

Third, the book was written before generative AI collapsed the cost of producing category content. Drafting a POV, generating variant framings, and producing supporting content is dramatically cheaper now — which means the *artifact* is no longer the bottleneck and no longer a differentiator. The scarce input is founder judgment about what the new problem actually is, and that has not gotten cheaper. If anything, the flood of cheap, competently-written category manifestos raises the bar on genuine strategic clarity.

The practical Monday-morning takeaway from this Summary of Ramadan, Peterson, Lochhead, and Maney's work is unchanged: write the one-paragraph problem statement without naming your product, read it honestly, and if it sounds like a problem the market already has a name for, either commit to the displacement strategy properly or go back and find a different question.

Related questions

Is category design only for venture-backed startups?

No. The capital-intensive Lightning Strike is, but the underlying logic — define a problem the market has not named, own the language for it — works at any scale. Lochhead's *Niche Down* applies it to consultancies and individuals, where the required spend is time and consistency rather than budget.

Can you design a category without a big launch event?

Yes, though the book underweights this. Product-led companies conditioned categories through bottom-up adoption first. The pattern that holds is that a defining public moment eventually becomes necessary to reach buyers who will never find you organically — it just arrives later in the sequence.

How do you know if your category is actually forming?

Watch the language. When customers, analysts, and job postings start using your term without you prompting them, the category is forming. When only your own marketing uses it, you have jargon. Analyst category creation and dedicated job titles are the strongest lagging indicators.

What happens if two companies try to create the same category?

Usually one wins the language and the other becomes the 17% player, because the market resolves toward a single reference implementation. The losing company's best move is typically to re-frame into an adjacent sub-category it can own outright rather than fight for a name it has already lost.

Does the 76% rule apply outside of software?

Directionally, in markets with strong network effects, ecosystem lock-in, or winner-take-most dynamics. In fragmented markets with high switching costs and regional constraints — construction, professional services, most physical retail — leadership is worth a premium but nothing close to that concentration.

FAQ

What is the single most important claim in Play Bigger?

That the Category King captures roughly 76% of the market capitalization created inside its category, with the #2 player taking about 17% and everyone from #3 down splitting the remainder. The strategic consequence is that competing for second place inside someone else's category is a structurally capped strategy over a ten-year horizon.

How is category design different from positioning?

Positioning locates your product in the customer's mind relative to competitors inside a category that already exists. Category design creates the mental map itself — it conditions the market to accept a new problem, a new vocabulary for that problem, and a new leader who solves it. Positioning is a marketing deliverable; category design is a company-wide operating discipline owned by the CEO.

What exactly is a Lightning Strike?

A concentrated, coordinated launch moment — event, content drop, press, analyst briefings, partner activation — engineered to imprint a category on customers, analysts, employees, and investors at the same time. The argument for concentration is that category conditioning requires a critical mass of simultaneous attention that a spread-out rollout never reaches.

What goes in a point of view document and how long should it be?

Typically 8–15 pages: the new problem, the From/To contrast between the old world and the new one, the category name, and the company's role in it. It is a manifesto, not a pitch deck. Every press release, sales script, hiring pitch, and investor narrative should be derivable from it without contradiction.

Should a company competing in an existing category read this book?

Yes, but with a specific purpose: to decide honestly whether to keep competing or to find a different question. The book's most useful output for an Option A company is the diagnostic — the product-free problem paragraph — which either confirms you should run the displacement playbook properly or reveals a category worth designing.

Who are the authors and what is their background?

Al Ramadan, Dave Peterson, Christopher Lochhead, and Kevin Maney are the partners behind Play Bigger LLC. The operator credentials come from Apple, Adobe, and Quokka Sports; Maney is a longtime technology journalist and author. The book combines that operating experience with the authors' analysis of market-cap concentration across new technology categories.

Sources

• https://www.harpercollins.com/products/play-bigger-al-ramadandave-peterson
• https://www.lochhead.com/
• https://www.goodreads.com/book/show/25733988-play-bigger
• https://www.penguinrandomhouse.com/books/318318/positioning-the-battle-for-your-mind-by-al-ries-and-jack-trout/
• https://www.harpercollins.com/products/crossing-the-chasm-3rd-edition-geoffrey-a-moore
• https://seths.blog/
• https://www.wiley.com/en-us/Behind+the+Cloud%3A+The+Untold+Story+of+How+Salesforce.com+Went+from+Idea+to+Billion+Dollar+Company+and+Revolutionized+an+Industry-p-9780470521168
• https://www.wiley.com/en-us/Amp+It+Up%3A+Leading+for+Hypergrowth+by+Raising+Expectations%2C+Increasing+Urgency%2C+and+Elevating+Intensity-p-9781119836117
• https://hbr.org/2016/05/positioning-your-startup-is-vital-heres-how-to-do-it-right
• https://www.salesforce.com/company/news-press/

Related on PULSE

• [Conversations That Win the Complex Sale by Erik Peterson and Tim Riesterer — Cliff Notes Summary](/knowledge/bs0294)
• [The 12 Week Year by Brian Moran and Michael Lennington — Cliff Notes Summary for Sellers](/knowledge/bs0319)
• [Contagious by Jonah Berger — Cliff Notes Summary for Sellers](/knowledge/bs0313)