Hacking Growth

Hacking Growth is the founding document of the modern growth function — written by the person who arguably invented the term 'growth hacker.' Sean Ellis coined the phrase in a 2010 blog post, ran growth at Dropbox, LogMeIn, and Eventbrite during their inflection years, and then co-wrote this book with Morgan Brown in 2017 to document the process he'd developed across those companies.

Its central contribution is the operating system for growth teams: a weekly cadence of hypothesis generation, prioritization (using the ICE framework — Impact, Confidence, Ease), structured experimentation, and post-experiment learning loops. The book formalizes what most successful growth teams had been doing informally since 2012, and the operating cadence it describes is now standard practice at most growth-stage SaaS and consumer companies.

Timing was central. The book came out in 2017, mid-cycle in the growth-hacking era. By then, growth as a function had matured from clever-trick tactics (the early Hotmail signature footer era) to a proper discipline with experimentation infrastructure, attribution, and cross-functional teams. Ellis's book documented what that maturation looked like operationally, which is why it has aged better than most growth books of its era. The tactics in the book are dated; the operating system isn't.

The most common misreading is fixating on the experiment examples (the Dropbox referral, the Airbnb professional photography, the LinkedIn email gravity loop) and missing that those examples are illustrations of a process rather than tactics to copy. Founders who try to copy specific growth tactics typically fail because the tactics were calibrated to a specific product, audience, and channel environment that no longer exists. The book's actual value is the framework for generating and testing your own growth hypotheses, not the historical examples.

Its limitation is that it assumes a mature analytics stack, a dedicated growth team, and product flexibility to ship experiments quickly. Early-stage startups without analytics infrastructure or without engineering capacity to ship A/B tests on a weekly cadence often find the book aspirational rather than operational. There's an implicit minimum company size (probably Series A and beyond, 30+ employees, real revenue and active users) below which the framework is more theatre than substance.

For Indian product teams, this book pairs particularly well with the data-rich, high-volume consumer apps that have become the default in Indian product. Indian apps like Cred, Meesho, Dream11, and Zerodha have growth teams operating exactly on the cadence this book describes — and the book has been visibly influential in how Indian growth teams structure their weekly experiment cycles. The ICE framework specifically is the most common prioritization framework in Indian growth team rituals.

Pair with Traction for the channel-discovery layer (Weinberg's Bullseye comes before Ellis's experiment cadence — you need to know which channel to optimize before you start optimizing it) and Product-Led Growth for the product-led variant of the same operating model.