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
Necessary But Not Sufficient

Necessary But Not Sufficient

An ERP company hits a growth ceiling: can its leaders make technology pay off for customers?
by Eliyahu M. Goldratt 2000 231 pages
4.10
500+ ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Change operating rules, or technology will preserve the old limits.

Old habits outlast new tools. BGSoft’s early MRP software could perform material calculations overnight, work that had once taken many employees days. Yet many customers still ran the calculation only monthly, as they had before computers. Their technology had removed a bottleneck, but their routines kept it in place. The book’s central argument is that installing a capable system does not guarantee its potential benefits. The organization must also reconsider the rules and habits built around its former limitations.

Information needs a new use. ERP systems made information easier to share and retrieve, but companies often kept managing departments as separate silos and rewarding local efficiency. Those practices could cancel out the system’s broader advantages. The challenge is not simply to digitize work, but to ask which old rules no longer fit the new capabilities.

Analysis

What's striking is the book's insistence that technology and organizational practice are complements, not substitutes. That idea echoes socio-technical systems research, which treats tools, roles, and incentives as a connected design problem. It also explains why software adoption can disappoint despite successful installation. The argument is persuasive, but not every inherited rule should be discarded: routines may protect safety, reliability, or accountability. A useful test is whether a rule still serves the current constraint, rather than whether it is old.

Over 80% of large buyers already had ERP; growth needed a new engine.

Growth hid a ceiling. BGSoft had grown annual sales from about $900 million to $1.37 billion, roughly 40 percent, and investors valued it at more than 100 times annual profit. The market treated rapid growth as normal, making a missed forecast dangerous. Yet more than 80 percent of large companies in its main market had already purchased an ERP system. Large firms supplied over 85 percent of BGSoft’s revenue, while mid-sized sales took six to eighteen months and brought in much less per deal.

A bigger market was not enough. The mid-sized market was far larger in number of companies, but selling into it with the existing product and sales process could not support the same economics. Scott’s challenge was to find a way to change both the value offered and the market served, rather than assume that more selling effort would overcome saturation.

Analysis

The story captures a familiar strategic trap: a company can mistake a favorable market phase for a permanent growth capability. In strategy terms, demand saturation is not merely a sales problem; it can expose a mismatch between the business model and the next customer segment. The stock-price threat adds urgency, though the novel’s dramatic estimates should be read as scenario-specific rather than universal market behavior. The broader lesson is to examine the source and durability of growth before making it the organization’s baseline expectation.

Treat each requested feature as a complexity cost, not a free upgrade.

Features accumulated faster than understanding. BGSoft’s ERP system kept expanding to meet customer requests. Lenny, its lead developer, found that even after rejecting many proposals, the number of features added in one year was three times the previous year’s total. The growing codebase became harder to understand, test, and repair. A change in one area could create defects elsewhere, and support staff struggled to identify the real cause of problems.

Service revealed the hidden price. KPI Solutions, BGSoft’s implementation partner, saw average support response time rise from about three days to nearly ten. More than 10 percent of issues took over three weeks to resolve. The system’s complexity also made new features slower to build. Requests may express genuine needs, but each addition can make the whole product less maintainable.

Analysis

This is a useful corrective to the assumption that customer responsiveness means saying yes to every request. In software design, complexity is cumulative: each added interaction can increase testing and maintenance burdens beyond the code written for the feature itself. The book’s account resembles technical debt, the future cost created when design choices make later changes harder. Still, declining requests is not sufficient; modular architecture, clear product boundaries, and evidence about recurring customer needs can preserve responsiveness without allowing every account to reshape the core system.

Translate faster data into cash, sales, or working capital.

Boards ask what changed financially. At Pierco, an ERP project costing $320 million was on time and on budget, but the CEO could not defend it with phrases such as better visibility. The system had shortened the financial close from over 45 days to about 10. That was useful, but the board wanted a bottom-line case. A lower processing cost per invoice did not count as cash saved if Pierco kept the same employees.

Follow effects to money. KPI’s assessment estimated that faster invoicing could release about $80 million in cash, worth roughly $7 million in profit at Pierco’s borrowing costs. It also projected $30 million in annual material savings, $45 million in inventory carrying-cost savings, and about $50 million in annual profit from a conservative sales increase. These were estimates based on early results, not all proven outcomes.

Analysis

The distinction between an accounting rate and a cash saving is essential. Process improvement creates capacity or time, but financial gains depend on what management does with them, such as reducing spending, serving more demand, or freeing working capital. This is closely related to benefits realization in project management: expected gains need owners, measures, and follow-through. The book rightly demands a traceable causal chain, though estimates should be stress-tested. A projected sales lift, for example, can be obscured by market changes unrelated to the system.

Design value around the customer's constraint, not their company size.

Company size is a poor proxy. BGSoft’s leaders initially reasoned that mid-sized firms would gain less from features designed for sprawling corporations. They had fewer plants and distribution centers, so consolidated purchasing and faster movement of information across a large network might yield smaller benefits. That made the mid-market look unattractive for the existing product.

Specific bottlenecks change the picture. Stein Industries, a manufacturer that grew from about $50 million to over $200 million in sales, was not buying software to look modern. Its customers valued fast delivery, and long production lead times threatened sales. The company’s case showed that a smaller firm could gain substantial value when a system addressed a constraint that mattered directly to its customers. The right question is not simply how large the buyer is, but what limits its performance.

Analysis

This is a strong argument for segmenting customers by the structure of their problem, not just by revenue or headcount. A small firm with a severe delivery bottleneck may value a targeted operational improvement more than a large firm values broad integration. That perspective aligns with jobs-to-be-done thinking, which asks what progress a customer is trying to make. One caution: an exceptional success story cannot establish that a segment is broadly attractive. Repeatable results across different firms are needed before a company redesigns its entire offer.

Release work to the bottleneck's pace, not the factory's appetite.

Earlier release created queues. At Stein Industries, ERP helped reduce preproduction work from two weeks to two days and eased material shortages. Yet orders still took about ten weeks to complete. The company had simply released work earlier, filling the factory with more jobs and congestion. A Theory of Constraints approach focuses improvement on the factor that limits the whole system. Drum-Buffer-Rope is its production-control method: the bottleneck sets the pace, protective time buffers absorb disruption, and work release is controlled so the shop floor is not flooded.

Later release shortened delivery. Stein delayed releasing work until seven weeks before its due date and began delivering reliably in that time. The improvement supported nearly 20 percent more sales. The company then offered four-week delivery for a premium and built a way to handle urgent orders without repeatedly disrupting the normal production plan.

Analysis

The counterintuitive insight is that starting more work can make a factory finish less work on time. Queueing theory helps explain why: when resources are heavily loaded, waiting time can rise sharply even if no machine becomes slower. The constraint-focused approach is a practical way to manage that effect. Its success depends on identifying the true bottleneck and maintaining buffers thoughtfully. A fixed bottleneck can move as demand or equipment changes, so the method requires observation and adjustment rather than faith in a static schedule.

Keep routine disruptions from rewriting the whole production schedule.

Whole-system optimization can destabilize work. Advanced Planning and Scheduling, or APS, software calculates production plans while accounting for capacity limits. Lenny found that these systems could reshuffle many orders when a small disruption occurred. A revised schedule might fix one late order while making another late, and frequent replanning could spread local disturbances through the factory.

Focus planning on the constraint. The book argues for using sophisticated scheduling where it is most useful, especially when the bottleneck involves several unlike machines, repeated visits, or difficult setup sequences. The schedule should not invite constant changes to every work center. Buffer-Management is the execution practice that directs attention to work most at risk, helping teams respond to meaningful problems without treating every fluctuation as a reason to reorganize the entire plant.

Analysis

The distinction between planning and execution is important in any complex operation. A plan is a model of likely conditions; execution requires deciding which deviations deserve intervention. Control theory warns that excessive correction can amplify noise, a pattern familiar in organizations that react to every short-term metric change. The book’s approach offers a disciplined alternative. Its claim should not be mistaken for a rejection of APS: the concern is not computation itself, but using global replanning in ways that generate instability without improving the system’s true limiting performance.

Pull stock from plants after actual sales instead of pushing forecasts downstream.

More capacity exposed a distribution flaw. After Pierco’s plants improved production, inventory rose by over $150 million in two months, while shortages persisted. Regional warehouses were replenished toward four-month targets established when replenishment was slower. Meanwhile, forecasts for individual products in individual regions were unreliable. Cutting the targets sharply could reduce stock, but it also forced plants into tiny production runs and costly setups.

Move the buffer upstream. Scott proposed holding more finished goods near the plants, where demand information aggregated across regions was more reliable, and replenishing regional warehouses daily according to actual sales. This pull approach aimed to reduce total inventory while improving availability. It was a proposed solution at the meeting, not a result already demonstrated there. Its logic was to let real customer demand trigger movement through the network, rather than let uncertain forecasts push excess stock outward.

Analysis

This section shows how a local improvement can create system-wide trouble when connected policies remain unchanged. Faster production did not automatically reduce inventory because replenishment targets still reflected the old lead time. Supply-chain design often faces this coordination problem: safety stock protects service, but its location and level determine how much uncertainty the network carries. The proposed upstream buffer is compelling, yet it shifts rather than eliminates risk. Its performance depends on reliable transport, good visibility, and clear responsibility for inventory across organizational boundaries.

Replace local efficiency targets with measures that reward complete customer flow.

Measures shape daily behavior. Pierco’s plants and warehouses had often blamed one another because each was judged by different local goals. The book introduces throughput-dollar-days to measure the value of late shipments multiplied by how late they are. Inventory-dollar-days measures inventory value over the time it remains under a manager’s responsibility. Together, these measures make delivery and inventory visible in both dollars and time.

Autonomy needs accountability. Managers could set inventory targets themselves, but they were also responsible for the resulting service and stock levels. That replaced a narrow focus on keeping every machine busy with attention to the flow of goods to customers. The changes required education, because employees had to understand why lower local utilization could support better overall performance.

Analysis

The principle is closely related to Goodhart’s law: when a measure becomes a target, people may optimize the measure instead of the underlying purpose. Local efficiency measures can encourage work that is busy but unnecessary, while flow-based measures push attention toward outcomes customers experience. The paired measures also recognize a genuine tradeoff between availability and inventory. Their value depends on consistent definitions and transparent data; otherwise, departments can dispute the numbers or shift costs onto one another rather than improve the whole system.

Turn software sales into a supply-chain service tied to final-customer results.

Extend accountability beyond one firm. Pierco’s CEO argued that improving his company was not enough if products still reached end customers no faster. He proposed coordinating vendors, Pierco, and clients as one supply chain. Under that approach, a shipment between two companies would not count as a true sale until the final customer bought the product. Shared inventory and delivery measures would help judge whether partners were moving goods effectively.

Change who carries the technology burden. Craig also proposed paying BGSoft and KPI to manage computer-related logistics as a continuing service, rather than buying software and implementation outright. His proposed payment was a percentage of revenue, eventually one percent annually. The arrangement was not yet adopted. It offered a way to make advanced systems accessible to smaller partners while tying the provider’s income to ongoing service.

Analysis

The proposal pushes the book’s logic from operational integration toward business-model design. A recurring service relationship can lower the upfront barrier for smaller firms and make software providers responsible for sustained performance, not just installation. But tying payment to revenue does not automatically align every incentive: firms may disagree over attribution, data access, or risk allocation. The model also demands trust and governance across companies. Shared metrics can support collaboration, but only if partners accept that transparency and fair distribution of gains are part of the deal.

Analysis

The book’s central contribution is a shift in what counts as a technology problem. BGSoft initially sees its crisis as two separate challenges: an ERP market approaching saturation and software becoming too complex to maintain. The story’s solution emerges when the leaders connect product value to operating practice. A system matters when it relaxes a real constraint, and the gain disappears if established rules continue to behave as though the constraint remains. That argument gives the novel a coherent through-line, from monthly MRP calculations to production scheduling, distribution inventory, and intercompany supply chains.

The business novel form makes abstract systems reasoning concrete. Managers discover why seemingly sensible fixes fail: earlier work release creates queues, local efficiency targets reward unneeded output, and improved production can flood warehouses when replenishment policy stays untouched. The repeated pattern is diagnostic rather than merely inspirational. Ask what limits total performance, what behavior the current measures encourage, and what other part of the system will absorb the consequences of a local improvement.

The argument is strongest as a management lens, not as a universal proof. Pierco’s results depend on executive sponsorship, motivated managers, and a workforce willing to learn new operating rules. The financial case combines measured early effects with estimates and extrapolations, so projected gains should not be confused with independently verified outcomes. The book also privileges monetizable results. Reliability, employee experience, resilience, and other public or organizational benefits may matter even when they are difficult to translate into immediate profit.

Its most enduring lesson is therefore not that one software architecture or scheduling method fits every company. It is that technology, measures, incentives, and daily decisions must be designed together. The final supply-chain service proposal extends that principle boldly, but leaves its risks unresolved. That open ending suits the argument: systems thinking identifies a promising direction, while implementation still has to prove the economics and earn cooperation.

Summary in 30 Seconds
Software maker BGSoft has grown rapidly by selling ERP systems to large companies, but that market is nearing saturation and its expanding product is becoming harder to maintain. CEO Scott and developer Lenny confront the limits of adding features without changing how customers work. At Pierco, an expensive ERP installation improves financial processing, yet executives want measurable financial returns. A manufacturing client, Stein Industries, discovers that releasing jobs earlier only clogs production; controlling work around its bottleneck improves delivery and supports sales growth. Pierco's improved production then swells inventory, so Scott proposes moving stock closer to plants and replenishing regional warehouses from actual sales. The leaders also challenge local efficiency targets and consider coordinating suppliers, manufacturers, and retailers as one supply chain. The book ends with a proposal to sell ongoing logistics services tied to revenue, not a proven result. Its promised gains remain estimates awaiting implementation.
Contains spoilers

Last updated:

Report Issue

Review Summary

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

Necessary But Not Sufficient receives mostly positive reviews, with readers praising its insights into Theory of Constraints (TOC) and its application in software and manufacturing. Many appreciate the business novel format, finding it engaging and easy to read. Some criticize the book for being less gripping than Goldratt's earlier works and lacking concrete practical tools. Readers value the book's perspective on implementing new technologies and changing organizational mindsets. Overall, it's recommended for those interested in TOC, ERP systems, and business improvement strategies.

Your rating:
4.49
229 ratings
Want to read the full book?

Glossary

Necessary But Not Sufficient

Technology needs changed rules

The book’s central principle that a technology can remove a practical limitation without producing its full benefit. Organizations may keep using routines and measures that were created to cope with the old limitation, effectively preserving it. To realize the technology’s potential, managers must also change the relevant rules, incentives, and operating practices.

Theory of Constraints

Improve the system's limiting factor

A management approach that improves overall performance by identifying the factor that currently limits the system, then organizing decisions around it. In the book, this logic applies to production bottlenecks, distribution, and projects. It rejects the assumption that maximizing each department or resource independently will necessarily improve the performance of the organization as a whole.

Drum-Buffer-Rope

Control work around a bottleneck

A production-control method associated with the Theory of Constraints. The bottleneck sets the production pace, time buffers protect the planned flow against disruption, and the release of new work is controlled to avoid flooding the factory with excess jobs. The method aims to improve reliable delivery by managing the constraint rather than maximizing activity everywhere.

Buffer-Management

Prioritize work at risk

An execution approach that uses buffer status to identify where attention is most needed. Rather than repeatedly rewriting the entire plan whenever a small disturbance occurs, workers and support teams use the buffer information to prioritize threatened orders and respond to meaningful delays. In the book, it complements production planning and helps direct improvement efforts.

Advanced Planning and Scheduling (APS)

Capacity-aware production scheduling

Software that calculates production schedules while considering resource capacity and other operational constraints. The book examines APS systems that optimize plans across many work centers. It argues that frequent whole-system rescheduling can create instability, and that such software is most useful when carefully applied to the actual production constraint and supported by an effective execution method.

Throughput-dollar-days

Value-weighted lateness

A delivery measure that combines the dollar value of an order with the number of days it is late. It distinguishes a small, briefly delayed order from a valuable order delayed for a longer period. Pierco considers it as a way to measure delivery performance while giving plants autonomy over inventory and operating decisions.

Inventory-dollar-days

Value-weighted inventory time

A measure that combines the dollar value of inventory with the time it remains under a manager’s responsibility. It makes both the amount of stock and how long that stock is held visible. In the book, the measure is proposed to hold plant and warehouse managers accountable for inventory without requiring headquarters to dictate every target level.

Critical Chain

Constraint-focused project management

A Theory of Constraints application to project environments, including software development and engineering. The book identifies it as a way to manage multiple concurrent projects and improve the likelihood of finishing them on time without reducing their content. BGSoft tests project-management software based on this approach in its development centers.

local optima

Department-level performance goals

A condition in which a department or resource is managed to improve its own results, even when those actions harm the organization’s overall flow. Examples in the book include maximizing the efficiency of every work center or producing large batches to reduce setups, despite the resulting delays and excess inventory. The Theory of Constraints emphasizes system-wide performance instead.

FAQ

What's Necessary But Not Sufficient about?

  • Theory of Constraints: The book is a business novel that explores the Theory of Constraints (TOC) through a software company's challenges, illustrating how addressing constraints can improve performance.
  • Business Dynamics: It delves into business growth, market saturation, and aligning product offerings with customer needs, emphasizing strategic thinking in managing complexity and demands.
  • Character-Driven Story: The narrative follows characters like Scott Duncan, the CEO, making it relatable and engaging for readers interested in business management.

Why should I read Necessary But Not Sufficient?

  • Practical Insights: Offers valuable insights into managing a business, especially in the tech industry, focusing on market dynamics and customer needs.
  • Engaging Format: Uses a business novel format to present complex concepts in an engaging way, making lessons easier to digest and apply.
  • Focus on Constraints: Highlights the Theory of Constraints, providing a framework for identifying and addressing bottlenecks to improve efficiency and profitability.

What are the key takeaways of Necessary But Not Sufficient?

  • Understanding Constraints: Emphasizes identifying and managing constraints to drive growth and efficiency, aligning decisions with business goals.
  • Market Awareness: Stresses the need for companies to adapt strategies to maintain growth amidst market saturation, encouraging innovation and market exploration.
  • Value Creation: Illustrates the importance of delivering real value to customers, focusing on product impact rather than just features or technology.

What specific methods or concepts are discussed in Necessary But Not Sufficient?

  • Theory of Constraints (TOC): Central to the book, TOC posits that every organization has constraints limiting performance, which can be addressed for improved efficiency.
  • Drum-Buffer-Rope: Introduced as a scheduling method to manage production processes, synchronizing production with demand to minimize delays.
  • Buffer Management: Discussed as a means to protect against variability, strategically placing buffers to absorb disruptions and maintain operational flow.

What are the best quotes from Necessary But Not Sufficient and what do they mean?

  • "Be paranoid.": Reflects the need for constant awareness of potential threats, emphasizing proactive planning and risk management for sustained growth.
  • "The better it is, the worse it becomes.": Highlights the paradox of increased challenges with success, warning against complacency.
  • "Technology is a necessary condition, but it's not sufficient.": Encapsulates the theme that technology must be accompanied by process changes to realize its full potential.

How does Necessary But Not Sufficient address the challenges of growth in a competitive market?

  • Market Saturation: Discusses challenges when primary markets become saturated, emphasizing the need for innovation and market exploration.
  • Sales Strategies: Highlights the importance of understanding customer needs and delivering value, adapting approaches to remain competitive.
  • Operational Efficiency: Illustrates improving efficiency through TOC, streamlining processes, and addressing constraints to enhance performance.

What role do the characters play in conveying the book's messages?

  • Scott Duncan: As CEO, Scott embodies leadership challenges in a changing market, reflecting the importance of strategic thinking and adaptability.
  • Jay Johnstone: Represents the sales perspective, highlighting effective communication and understanding of customer needs in a competitive environment.
  • Lenny Abrahms: Emphasizes technical challenges in product development, aligning technology with business goals, central to the book's themes.

How does Necessary But Not Sufficient illustrate the application of TOC in real businesses?

  • Fictional Narrative: Uses characters and scenarios to demonstrate TOC principles in various business contexts, making concepts relatable and actionable.
  • Case Studies: Presents case studies of companies implementing TOC, showcasing challenges and solutions to overcome limitations.
  • Practical Examples: Shows how organizations can shift focus from local efficiencies to overall system performance for improved results.

What challenges do characters face in Necessary But Not Sufficient when implementing TOC?

  • Resistance to Change: Characters encounter resistance from employees hesitant to adopt new processes, crucial for successful TOC implementation.
  • Complexity of Operations: Existing operational complexity poses challenges in identifying and addressing constraints effectively.
  • Balancing Goals: Characters struggle to balance immediate needs with long-term goals, complicating TOC implementation and business performance.

How does Necessary But Not Sufficient address the relationship between technology and organizational culture?

  • Cultural Shift Required: Emphasizes that adopting new technology requires a cultural shift, with employees embracing new ways of thinking and working.
  • Alignment of Values: Illustrates the importance of aligning organizational values with technology goals to achieve desired outcomes.
  • Role of Leadership: Leaders play a crucial role in fostering a culture that supports change, encouraging collaboration, and understanding technology's value.

How can organizations ensure successful implementation of TOC as suggested in Necessary But Not Sufficient?

  • Engage All Stakeholders: Involve all relevant stakeholders to ensure buy-in and collaboration across departments.
  • Provide Education and Training: Offer training on TOC principles to equip employees with the knowledge needed for effective implementation.
  • Monitor and Adjust: Continuously monitor the process and be willing to adjust based on feedback and results for ongoing success.

What future trends does Necessary But Not Sufficient suggest for businesses?

  • Integration of Technology: Suggests businesses will increasingly integrate advanced technologies with TOC principles to enhance decision-making and efficiency.
  • Focus on Value Creation: Organizations will shift focus from selling products to creating value, emphasizing understanding customer needs.
  • Collaboration Across Supply Chains: Predicts a trend towards collaboration across supply chains, optimizing performance and achieving shared goals.

About the Author

Eliyahu M. Goldratt was a renowned thinker, educator, and business leader best known for developing the Theory of Constraints (TOC). He authored several influential books, including the bestseller "The Goal," which introduced TOC concepts through a business novel format. Goldratt's work focused on ongoing improvement processes and leveraging system constraints to achieve goals. He developed various TOC-derived tools and thinking processes throughout his career. Born in Israel in 1947, Goldratt held advanced degrees in science and made contributions to fields beyond business management, including education and technology. He passed away in 2011, leaving a lasting impact on business thinking and practices worldwide.

Download PDF

To save this Necessary But Not Sufficient summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.45 MB     Pages: 21

Download EPUB

To read this Necessary But Not Sufficient 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.44 MB     Pages: 27
Want to read the full book?
Follow
Listen
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 25,
cancel anytime before.
Consume 2.8× More Books
2.8× more books Listening Reading
Our users love us
1M+ 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...