Start free trial
Trending New Genres Authors
EnglishEnglish
EspañolSpanish
简体中文Chinese
繁體中文Chinese (Traditional)
FrançaisFrench
DeutschGerman
日本語Japanese
PortuguêsPortuguese
ItalianoItalian
한국어Korean
РусскийRussian
NederlandsDutch
العربيةArabic
PolskiPolish
हिन्दीHindi
Tiếng ViệtVietnamese
SvenskaSwedish
ΕλληνικάGreek
TürkçeTurkish
ไทยThai
ČeštinaCzech
RomânăRomanian
MagyarHungarian
УкраїнськаUkrainian
IndonesiaIndonesian
DanskDanish
SuomiFinnish
БългарскиBulgarian
עבריתHebrew
NorskNorwegian
HrvatskiCroatian
CatalàCatalan
SlovenčinaSlovak
LietuviųLithuanian
SlovenščinaSlovenian
СрпскиSerbian
EestiEstonian
LatviešuLatvian
فارسیPersian
മലയാളംMalayalam
தமிழ்Tamil
اردوUrdu
Searching...
SoBrief
Running Lean

Running Lean

Iterate from Plan A to a Plan That Works
Test demand, pricing, and retention before spending a year building the wrong product.
by Ash Maurya 2012 367 pages
4.10
20k+ ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Make customer adoption, not product completion, your first proof of progress.

Build less, learn sooner. The book opens with two founders. Steve spends a year building a polished product, runs short of money, and struggles to recruit or raise investment. Larry begins by testing whether customers care, then builds toward a solution people will pay for. The difference is not talent but the order of work. Traction means evidence that customers are engaging with a business model and that it captures value, not simply that a product exists.

Follow the evidence. Lower building costs mean more competing products, so being first to launch matters less than being adopted. Larry earns early customers through a narrow offer and personal attention, then uses what he learns to improve the product. The book’s core move is to treat the business model, not the software, as the thing under development.

Analysis

The contrast makes a useful distinction between making an artifact and reducing uncertainty about a market. In fields such as science and engineering, progress is often measured by what a test rules out, not by how much material has been produced. That lens helps explain why a working product can still represent little business progress. Adoption, however, is not automatically proof of a durable model. Early customers may be unusually enthusiastic or expensive to serve, so traction needs to be interpreted alongside retention, revenue, and the cost of acquiring customers.

Interview around painful existing workarounds before designing your solution.

Start with the old way. The book calls the founder’s tendency to interpret every problem as support for a favored solution Innovator’s Bias. Its antidote, the Innovator’s Gift, is to look for problems created or exposed by current solutions. People tolerated cassette tapes until CDs made finding a song easier; later, digital downloads and streaming changed what listeners expected. The opportunity was not an abstract demand for new technology, but a familiar frustration that made switching worthwhile.

Name the real competition. A collaboration product competes not only with similar software, but perhaps with email or spreadsheets. Ask what customers use now, where that approach frustrates them, and what outcome they want instead. A new product must offer a meaningful reason to switch, not merely a different feature set. The author suggests that a dramatic improvement can help, but interviews should reveal whether customers experience the problem as important.

Analysis

This approach resembles the jobs-to-be-done perspective: people adopt a product to make progress in a situation, not to collect features. Looking at workarounds also reduces a common interview error, asking people to applaud a hypothetical idea rather than describe actual behavior. Still, retrospective accounts can be unreliable, and expressed frustration does not always predict payment. Strong discovery therefore pairs stories about past choices with observable commitments, such as time spent, money spent, or willingness to try an offer.

Put Plan A on one page, then split it into testable bets.

Make assumptions visible. The Lean Canvas is a one-page sketch of a business model, including customers, problems, a value proposition, a proposed solution, channels, costs, revenue, measures of progress, and possible defenses against imitation. It is not a polished forecast. The author recommends drafting a first version quickly, even leaving uncertain sections blank, so a team can see what it is assuming rather than mistake guesses for facts.

Stay specific, explore broadly. One canvas should tell one coherent business story. Steve initially lumps software developers and several industries into a broad AR/VR platform idea. Splitting it into separate versions for developers, construction, and retail makes the customer and value proposition clearer. The exercise balances focus with exploration: generate several distinct models, then prioritize them, rather than forcing every possibility into one vague plan.

Analysis

A compact model works like a map: it cannot reproduce the territory, but it can make disagreements and missing information visible. Asking teammates to draft their own canvases before comparing them is especially valuable because early group discussion can create premature consensus. The one-page limit also forces prioritization. Its risk is false neatness: boxes can make uncertain relationships appear settled. A canvas is most useful when each claim is treated as provisional and linked to a concrete way of checking it.

Reject ideas that cannot clear your three-year success bar on paper.

Set a minimum before forecasting. Minimum Success Criteria means the smallest outcome that would make a project worthwhile after three years. The author favors a rough target, often annual revenue, over an elaborate five-year spreadsheet. A Fermi estimate is a quick, approximate calculation built from a few key inputs. It helps expose whether a model’s assumptions can plausibly reach the stated goal.

Let the arithmetic challenge ambition. Steve sets a $10 million annual recurring revenue target and initially considers a $50 monthly subscription. That implies about 16,667 active customers. Assuming a four-year customer lifetime, he estimates roughly 2.08 percent monthly churn, or around 347 customers to replace each month at that scale. At a 1 percent paid conversion rate, that replacement rate requires about 34,700 leads monthly. The estimate does not predict the future. It reveals which assumptions, such as price or conversion, deserve testing.

Analysis

The method is a form of sensitivity analysis: instead of decorating a forecast with precision, it identifies which inputs have enough leverage to change the decision. It also forces founders to consider whether the scale of the business matches the life they want to build. The arithmetic is only as sound as its assumptions. Churn, conversion, and pricing can vary sharply by market and customer type, so a rough calculation should guide experiments, not serve as a verdict. Its value is often in showing where ignorance is concentrated.

Test desire and revenue potential before debating whether to build.

Stress-test three kinds of risk. The book organizes early business uncertainty around desirability, viability, and feasibility: do customers want the offer, can the business capture enough value, and can the team build it? Founders often rush toward feasibility because building is familiar and emotionally satisfying. But a technically impressive product can still fail if the intended customer does not care or the economics cannot work.

Prioritize the fragile assumptions. Steve imagines a broad AR/VR platform, but the deeper question is whether developers, retailers, or architects have a pressing problem that warrants paying for it. The order matters: first sharpen the customer and problem story, then test whether the business could support the desired outcome, then investigate the technical work. This is not a claim that engineering risk disappears. It is a way to avoid spending heavily on a solution before the market case is credible.

Analysis

The three-part lens prevents a common category error: treating a successful technical demonstration as evidence of customer demand. It also encourages teams to make risk explicit rather than letting the most powerful function, often engineering, define the agenda. In practice, the categories interact. A technical constraint can change the price or customer, while a customer’s requirements can reshape feasibility. The framework works best as a prioritization aid, not a rigid sequence that forbids technical prototypes when technical uncertainty is genuinely the largest threat.

Sell a small, valuable promise before building the product behind it.

Define before you develop. A minimum viable product, or MVP, is the smallest solution that creates, delivers, and captures customer value. It is not simply a rough release or a reduced feature list. The book warns that launching an untested solution and watching analytics can trap a team: numbers may show that users leave, but not explain why.

Test an offer first. Mary describes a different path for her company: sketch possible models, interview about two dozen customers, make a demo, and present an offer to prospects before building the full product. The team secured five paying customers who then wanted delivery. The sequence reduces the chance of building the wrong thing. Steve’s reference app attracts signups but little return use because he has not spoken with users or established that the problem matters.

Analysis

A demo or offer is a low-cost probe into willingness to act, which is often more informative than asking whether someone likes an idea. This resembles experimental design: isolate the riskiest proposition and test it with the least expensive instrument available. Yet pre-selling has limits. A compelling pitch can create expectations the eventual product cannot meet, and a handful of customers cannot establish broad demand. The promise must be honest, the target segment clearly defined, and the result treated as evidence for another test rather than proof of product-market fit.

Charge early enough to learn whether the value is real.

Price is evidence. The author argues that if a business intends to charge, it should test pricing from the start. A free signup can be easy to obtain but may reveal little about whether customers value the offer enough to pay. Price also shapes who responds and what quality or positioning they infer from the product.

Anchor on customer value. Steve initially chooses $50 a month without much grounding. His later model suggests that a tool saving developers many hours could justify a substantially higher price, depending on the value of that time. The relevant comparison is not simply what the software costs to build. It is what customers spend on current alternatives and what the promised outcome is worth to them. A payment is an early commitment, though not proof of lasting satisfaction.

Analysis

Charging early connects product discovery to revealed preference: behavior involving a real cost can be more informative than stated enthusiasm. It can also expose a mismatch between the target customer and the product’s economics. Price is not a neutral measurement, however. A high price can deter learning, while a low one can attract customers who would never support the intended model. Testing a range of prices and explaining the offer clearly helps distinguish weak value from poor positioning or the wrong segment.

Track customers who return and pay, not signups that merely rise.

Measure the customer journey. The Customer Factory is the book’s model of how a business turns unfamiliar prospects into satisfied paying customers. It tracks five steps: acquisition, activation, retention, revenue, and referral. Each step asks a different question. Did people arrive? Did they experience the promised value? Did they return? Did they pay? Did they bring others?

Choose meaningful signals. A cumulative signup total tends to rise over time and can disguise weak engagement. Retention is more revealing because it shows whether customers continue to find value; revenue shows whether that value supports a business. A flower shop illustrates the sequence: attract someone from the street, deliver a good first visit, earn a return visit, make a sale, and prompt a recommendation. Metrics locate where the process breaks, while customer conversations help explain why.

Analysis

The funnel is useful because it turns the vague question of growth into a diagnostic one. A drop between activation and retention suggests a different problem than a failure to attract prospects. This logic resembles process control: measure the stages of a system, then investigate bottlenecks instead of celebrating aggregate output. But a funnel can oversimplify businesses with long sales cycles, multiple decision-makers, or infrequent use. Metrics should reflect the customer’s actual path to value, not force every company into identical event definitions.

Run small team experiments against the assumption most likely to break you.

Place modest, informative bets. The book recommends short team cycles, called Lean Sprints, to align on goals and assumptions, generate possible tests, and choose experiments based on evidence rather than seniority or enthusiasm. The aim is not to run many random tests. It is to target the assumption whose failure would most damage the business model, then learn quickly and adjust.

Keep discovery alive. Customer discovery means learning what customers struggle with before treating a proposed solution as proven. Validation asks whether a specific offer or model works. Teams can get stuck if they skip discovery and repeatedly refine a weak starting idea. In Steve and Larry’s contrast, learning is not a separate phase before work begins; it is the work. Small course corrections help avoid a single costly launch built on untested beliefs.

Analysis

This process combines portfolio logic with team learning: several low-cost experiments can reveal more than one large commitment, while diverse perspectives increase the range of ideas considered. The strongest version makes failure informative by stating in advance what result would change the team’s mind. Otherwise, teams can reinterpret every outcome as success and turn experimentation into theater. Small bets are not automatically wise if they test trivial questions; their value comes from connecting a clear test to a consequential business assumption.

Tell customers, investors, and advisers the story each needs to hear.

Change the frame, not the facts. Customers want to understand the problem and outcome; investors look for a credible business model and signs of traction; advisers can help expose risks. A useful customer pitch makes the customer the protagonist, presents the current obstacle, and shows how the offer changes the outcome. The product plays a supporting role rather than claiming the spotlight.

Keep the pitch testable. The book suggests a short overview supported by a one-page model and a concise slide deck. For investors, the story includes the market, revenue logic, progress, team, and a clear request. For advisers, the founder should present the current model, then listen rather than defend every assumption. Advice is input, not instruction: compare competing suggestions and test the ones that seem most promising.

Analysis

Audience-specific communication is not spin when it selects relevant facts without changing their meaning. It is closer to translation: the same business can be described through a customer’s desired outcome or an investor’s concern about returns. The narrative structure also helps people remember an unfamiliar idea because it gives the information a sequence. The danger is letting a polished story outrun the evidence. A pitch should clarify what is known, what remains uncertain, and what decision or help is being requested.

Analysis

Running Lean is a practical guide to making entrepreneurship less faith-based. Its central claim is not that planning is useless, but that plans should be compact, revisable, and organized around assumptions that can be tested. The opening contrast between Steve and Larry gives this argument a human shape: one treats the product as the work, the other treats customer learning as the work. That distinction carries through the canvas, the rough financial model, the offer, and the pitch.

The strongest contribution is the insistence that founders test the customer and economic story before allowing technical momentum to dictate the project. The Lean Canvas makes assumptions discussable; the Fermi estimate asks whether the model can plausibly support the founder’s stated ambition; interviews and paid offers then expose whether the hypothesized problem matters. Together, these practices create a feedback system rather than a promise of certainty. The value lies less in any single template than in repeatedly connecting a claim to evidence and choosing the next test accordingly.

The approach also has boundaries. Early customers are not necessarily representative, an offer that sells does not establish retention, and a simple acquisition model may miss complex buying processes. The book’s quick calculations are useful for discovering fragile assumptions, but their outputs depend on estimates that can be wrong by large margins. Moreover, a relentless focus on traction can privilege easily monetized outcomes over public value or long-term capability. The author acknowledges that impact-driven organizations still need revenue, but revenue is a means, not a complete measure of impact.

The most productive reading is therefore neither as a recipe nor as a license to pivot whenever a metric disappoints. It is a discipline for deciding what to believe provisionally, what evidence would challenge that belief, and what limited action can obtain that evidence. A founder should preserve ambition while making each step answerable to customers and arithmetic. The method cannot guarantee a business that works; it can make wasted certainty harder to sustain.

Summary in 30 Seconds
Treat the business model as the main object of development, and use customer evidence to revise it. Interview people about current workarounds, then test whether the problem matters and whether customers will pay before building. Estimate the customer volume, price, and churn needed to meet a three-year goal. Track acquisition, activation, retention, revenue, and referrals, and run small experiments against the assumptions most likely to fail.
Contains spoilers

Last updated:

Report Issue

Review Summary

4.10 out of 5
Average of 20k+ ratings from Goodreads and Amazon.

Running Lean is praised as a practical guide for entrepreneurs, offering step-by-step instructions on developing and testing business ideas. Readers appreciate its focus on customer feedback, lean methodology, and risk reduction. Many consider it essential reading for startups, complementing other lean business books. The book's emphasis on rapid iteration, MVP development, and systematic testing resonates with entrepreneurs. Some readers find it particularly useful for tech startups, while others see its applicability in various fields. A few criticisms mention its focus on B2C examples and potential overlap with other lean startup literature.

Your rating:
4.46
1030 ratings
Want to read the full book?

Glossary

Lean Canvas

One-page business model

A one-page tool for describing a business model through its main assumptions, including customers, problems, value proposition, solution, channels, costs, revenue, measures, and potential advantage. It is meant to be drafted quickly and revised as evidence changes, rather than treated as a complete business plan or a prediction of the future.

Minimum Viable Product (MVP)

Smallest value-delivering solution

The smallest solution that creates, delivers, and captures customer value. In this book, an MVP is not simply a rushed beta or a minimal collection of features. Its purpose is to solve a meaningful customer problem well enough to support a business, after the customer, problem, and offer have been investigated.

Traction

Rate of captured value

Evidence that a business model is capturing value from customers, expressed as the rate at which that value is being captured. It is not any metric that happens to increase, such as cumulative signups. Meaningful traction is connected to customer engagement and monetization, and can help founders assess whether the model is working.

Innovator’s Bias

Solution-driven problem framing

The tendency to interpret customer needs selectively so they justify a solution the innovator already wants to build. It can lead founders to invent or exaggerate problems, ignore contradictory evidence, and treat every customer as a potential user. The book counters it by asking founders to explain customer problems through existing alternatives, without relying on their proposed solution.

Innovator’s Gift

Problems revealed by old solutions

A way of finding worthwhile innovation opportunities by examining the limitations and frustrations of existing solutions. Rather than beginning with a novel technology and searching for a use, the innovator identifies an old way customers already use, then investigates what prevents it from delivering their desired outcome. A new offer becomes compelling when it gives customers a reason to switch.

Minimum Success Criteria

Three-year success threshold

The smallest outcome that would make a project worthwhile three years from the present. The book recommends setting this target independently of the proposed idea, often in terms of annual revenue, then checking whether the business model could plausibly reach it. It constrains the search by clarifying what scale or result would justify the investment of time.

Fermi estimate

Rough model viability calculation

A quick, approximate calculation that uses a small set of assumptions to estimate whether a business model can reach a target. In this context, founders estimate inputs such as price, customer lifetime, and conversion, then calculate the customers and leads required. Its purpose is to reveal fragile assumptions and decision-relevant levers, not to produce a precise forecast.

Customer Factory

Customer value conversion process

A model of the business as a process that turns unaware prospects into satisfied paying customers. It tracks five stages: acquisition, activation, retention, revenue, and referral. Each stage has corresponding behaviors to measure, helping a team locate where customers stop progressing. Conversations with customers are still needed to understand the reasons behind the numbers.

Lean Sprints

Short team learning cycles

Short, recurring work cycles in which a team aligns on goals and assumptions, proposes possible approaches, and selects small experiments based on the strength of evidence. The cycles focus attention on uncertain parts of the business model and help teams learn together rather than splitting into disconnected product and sales efforts.

FAQ

What's "Running Lean" about?

  • Iterative Process: "Running Lean" by Ash Maurya is about iterating from an initial business idea (Plan A) to a plan that works by systematically testing and validating business models.
  • Lean Canvas: The book introduces the Lean Canvas, a one-page business model that helps entrepreneurs deconstruct their ideas into key assumptions and test them.
  • Mindset Shift: It emphasizes a shift from a build-first approach to a traction-first approach, focusing on customer problems rather than solutions.
  • Continuous Innovation: The book outlines a framework for continuous innovation, helping entrepreneurs adapt and refine their business models in response to real-world feedback.

Why should I read "Running Lean"?

  • Practical Guidance: The book offers practical, step-by-step guidance for entrepreneurs looking to validate and refine their business ideas.
  • Avoid Common Pitfalls: It helps readers avoid common entrepreneurial pitfalls, such as building products that nobody wants or failing to secure stakeholder buy-in.
  • Proven Framework: Ash Maurya provides a proven framework for systematically testing business models, which can increase the odds of success.
  • Real-World Examples: The book includes real-world examples and case studies that illustrate the application of its principles.

What are the key takeaways of "Running Lean"?

  • Business Model as Product: Treat your business model as a product that needs to be tested and validated, not just your solution.
  • Focus on Traction: Traction is the ultimate goal, and it involves demonstrating that your business model works by achieving market adoption.
  • Prioritize Risks: Identify and prioritize the riskiest assumptions in your business model and test them first.
  • Iterative Learning: Use a cycle of modeling, prioritizing, and testing to continuously learn and adapt your business model.

What is the Lean Canvas, and how is it used in "Running Lean"?

  • One-Page Business Model: The Lean Canvas is a one-page business model that helps entrepreneurs capture their ideas quickly and clearly.
  • Key Assumptions: It breaks down a business idea into key assumptions, such as customer segments, problems, solutions, and revenue streams.
  • Dynamic Model: Unlike traditional business plans, the Lean Canvas is a dynamic model that can be updated and refined as new information is gathered.
  • Focus on Risks: It helps entrepreneurs focus on identifying and testing the riskiest parts of their business model first.

How does "Running Lean" define traction?

  • Monetizable Value: Traction is defined as the rate at which a business model captures monetizable value from its customers.
  • Evidence of Demand: It serves as evidence that there is demand for your product and that your business model is working.
  • Investor Interest: Traction is crucial for attracting investors, as it demonstrates that your business has potential for growth and profitability.
  • Customer Engagement: It involves customer engagement and adoption, indicating that your product is solving a real problem.

What is the "Innovator's Bias" mentioned in "Running Lean"?

  • Solution-Centric Thinking: Innovator's Bias refers to the tendency of entrepreneurs to focus too much on their solution rather than the customer's problem.
  • Inventing Problems: Entrepreneurs may unconsciously invent problems to justify their solution, rather than identifying real customer needs.
  • Overcoming Bias: The book suggests overcoming this bias by focusing on customer problems and existing alternatives to uncover real problems worth solving.
  • Innovator's Gift: The Innovator's Gift is the realization that new problems worth solving come from old solutions, guiding entrepreneurs to frame problems in terms of existing alternatives.

What is the "Traction-First Approach" in "Running Lean"?

  • Focus on Market Adoption: The Traction-First Approach emphasizes achieving market adoption before building a complete product.
  • Customer Validation: It involves validating customer demand and securing early adopters before investing heavily in product development.
  • Avoiding the Build Trap: This approach helps avoid the build trap, where entrepreneurs spend too much time perfecting a product without validating demand.
  • Iterative Development: It encourages iterative development, where entrepreneurs build, test, and refine their product based on customer feedback.

How does "Running Lean" suggest testing business model assumptions?

  • Prioritize Risks: Identify the riskiest assumptions in your business model and prioritize testing them first.
  • Small Experiments: Use small, fast experiments to test assumptions and gather evidence to support or refute them.
  • Customer Interviews: Conduct customer interviews to validate assumptions about customer segments, problems, and solutions.
  • Iterative Process: Continuously iterate on your business model based on the results of your tests and experiments.

What are the "Nine Mindsets" in "Running Lean"?

  • Model Mindsets: Treat your business model as a product, love the problem not the solution, and focus on traction.
  • Prioritize Mindsets: Take the right action at the right time, roll out in stages, and place many small bets.
  • Test Mindsets: Make evidence-based decisions, prioritize discovery before validation, and recognize that breakthroughs require unexpected outcomes.
  • Continuous Innovation: These mindsets support the continuous innovation framework, helping entrepreneurs adapt and refine their business models.

What is the "Minimum Viable Product" (MVP) according to "Running Lean"?

  • Smallest Solution: An MVP is the smallest solution that creates, delivers, and captures customer value.
  • Customer Validation: It is used to validate customer demand and gather feedback before building a complete product.
  • Avoid Overbuilding: The MVP approach helps avoid overbuilding by focusing on delivering just enough value to test assumptions.
  • Iterative Refinement: Entrepreneurs can iterate and refine their MVP based on customer feedback and learning.

How does "Running Lean" address the "Catch-22" of startups?

  • Traction vs. Resources: The Catch-22 refers to the challenge of needing traction to secure resources, but needing resources to achieve traction.
  • Traction-First Approach: The book suggests a traction-first approach, where entrepreneurs focus on achieving market adoption before seeking investment.
  • Customer Engagement: By engaging customers early and validating demand, entrepreneurs can demonstrate traction and attract resources.
  • Iterative Learning: Continuous learning and adaptation help entrepreneurs navigate the Catch-22 and build a sustainable business model.

What are the best quotes from "Running Lean" and what do they mean?

  • "Your business model is the product." This quote emphasizes the importance of treating the business model as a product that needs to be tested and validated, not just the solution.
  • "Love the problem, not your solution." It highlights the need to focus on customer problems rather than being attached to a specific solution.
  • "Traction is the goal." This quote underscores the importance of achieving market adoption and demonstrating that the business model works.
  • "Breakthrough requires unexpected outcomes." It suggests that innovation often comes from unexpected insights and learning, encouraging entrepreneurs to embrace uncertainty.

About the Author

Ash Maurya is an experienced entrepreneur who has spent over a decade seeking better ways to build successful products. He discovered and applied principles of Customer Development and Lean Startup, pioneered by Steve Blank and Eric Ries. Maurya began sharing his experiences and insights through his blog, which eventually evolved into a book. His work has expanded to include a series of products designed to help entrepreneurs increase their chances of success. Maurya's mission is centered on assisting entrepreneurs in creating viable businesses and avoiding wasted effort on products that lack market demand. His approach emphasizes practical application and rigorous testing of lean startup principles.

Download PDF

To save this Running Lean summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.25 MB     Pages: 21

Download EPUB

To read this Running Lean summary on your e-reader device or app, download the free EPUB. The .epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.
Download EPUB
File size: 1.35 MB     Pages: 27
Want to read the full book?
Follow
Listen8 mins
Home
Swipe
Library
Get App
Try Full Access for 3 Days
Listen, bookmark, and more
Compare Features Free Pro
📖 Read Summaries
Read unlimited summaries. Free users get 3 per month
🎧 Listen to Summaries
Listen to unlimited summaries in 40 languages
—
❤️ Unlimited Bookmarks
Free users are limited to 4
—
📜 Unlimited History
Free users are limited to 4
—
📥 Unlimited Downloads
Free users are limited to 1
—
Risk-Free Timeline
Today: Get Instant Access
Listen to full summaries of 26,000+ books. That's 12,000+ hours of audio!
Day 2: Trial Reminder
We'll send you a notification that your trial is ending soon.
Day 3: Your subscription begins
You'll be charged on Nov 24,
cancel anytime before.
Consume 2.8× More Books
2.8× more books Listening Reading
Our users love us
600,000+ readers
Trustpilot Rating
TrustPilot
4.6 Excellent
This site is a total game-changer. I've been flying through book summaries like never before. Highly, highly recommend.
— Dave G
Worth my money and time, and really well made. I've never seen this quality of summaries on other websites. Very helpful!
— Em
Highly recommended!! Fantastic service. Perfect for those that want a little more than a teaser but not all the intricate details of a full audio book.
— Greg M
Save 62%
Yearly
$119.88 $44.99/year/yr
$3.75/mo
Monthly
$9.99/mo
Start a 3-Day Free Trial
3 days free, then $44.99/year. Cancel anytime.
Unlock a world of fiction & nonfiction books
26,000+ books for the price of 2 books
Read any book in 10 minutes
Discover new books like Tinder
Request any book if it's not summarized
Read more books than anyone you know
#1 app for book lovers
Lifelike & immersive summaries
30-day money-back guarantee
Download summaries in EPUBs or PDFs
Cancel anytime in a few clicks

Why one summary?

Scanner
Find a barcode to scan

⭐
⭐
⭐
We have a special gift for you
Open
38% off
DISCOUNT FOR YOU
⭐
⭐
⭐
$79.99
$49.99/year
Only $4.16 per month
Continue
2 taps to start, super easy to cancel
Settings
General
Widget
Loading...