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
Accelerate

Accelerate

Building and Scaling High Performing Technology Organizations
Make software releases faster and safer by redesigning how teams build, test, and learn.
by Nicole Forsgren 2018 288 pages
4.05
8k+ ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Treat software delivery as a core business capability, not an IT utility

Software shapes competitiveness. Banks, retailers, and public agencies increasingly deliver value through digital services. The book argues that the ability to change those services quickly and reliably affects customer response, regulatory adaptation, and business results. Across the 2017 study, high performers deployed code 46 times more often than low performers, moved changes from commit to production 440 times faster, restored service 170 times faster, and had one-fifth their change failure rate.

Build capabilities, not a finish line. The authors favor ongoing improvement over maturity models that assign teams a fixed level or prescribe the same sequence of tools. Teams differ in constraints and goals, so improvement should target the capabilities that matter to their outcomes. The research covered more than 23,000 responses from over 2,000 organizations, including legacy systems and regulated industries.

Analysis

The important shift is from treating software as a support department to treating delivery capacity as a strategic option. A firm that can alter its service rapidly can test assumptions and respond to events with less delay. The performance gap is striking, but it should not be read as a guarantee that adopting a named practice creates the same gains everywhere. The figures compare groups, not a controlled intervention. Their strongest practical use is to make the cost of slow delivery visible and motivate specific experiments.

Track speed and recovery together, not code volume or team busyness

Measure outcomes across the system. The book rejects lines of code, team velocity, and utilization as productivity measures. More code can mean more maintenance; velocity is local to each team and can be gamed; and near-total utilization leaves no room for interruptions or improvement. Instead, assess delivery through four outcomes: how often production changes ship, how long changes take to reach production, how quickly service recovers from an incident, and what share of changes cause failure or remediation.

Speed is not the enemy of stability. The authors found that high performers did better across all four measures. Deployment frequency also serves as a practical proxy for batch size: more frequent releases generally mean smaller changes. Together, these measures encourage developers, testers, and operations staff to optimize one shared system rather than protect separate departmental scorecards.

Analysis

This is a systems view of productivity: output matters only insofar as it produces useful outcomes without making the next change harder. Queueing theory helps explain the warning about utilization. As a system approaches full capacity, small interruptions can create disproportionate waits because no slack remains to absorb them. The four measures are more balanced than a single speed target, but they still need context. A service with strict safety obligations may choose a different acceptable risk profile than a consumer app, even while monitoring the same underlying dimensions.

Shrink batches and automate checks to make frequent releases safer

Make change routine. Continuous delivery is the capability to keep software ready for release and to deliver changes safely when needed. It relies on practices such as versioning code and configuration, integrating changes often, running dependable automated tests, and automating deployment. Small batches make problems easier to locate and give teams feedback sooner. The research links these technical practices not only with better delivery performance, but also with fewer failed changes, less deployment anxiety, and less burnout.

Quality consumes less time when built in. High performers reported spending 49% of their time on new work and 21% on unplanned work or rework. Low performers spent 38% on new work and 27% on unplanned work or rework. That difference suggests how recurring repair work can crowd out useful development. Testing must be reliable, though: a flaky test suite teaches developers to distrust the very feedback meant to protect releases.

Analysis

Small batches are a risk-control mechanism as much as a speed technique. When changes are narrow, failures are easier to trace, and teams can learn from real use without betting the whole release on one large package. Automation moves repetitive verification to machines, leaving human attention for design and diagnosis. The caveat is that automation can encode poor assumptions just as efficiently as good ones. A fast pipeline is valuable when its tests represent meaningful quality and when teams routinely revise those tests as the product and its risks change.

Design systems so teams can test and deploy without negotiating dependencies

Independence enables flow. High-performing teams could test most of their work without assembling a shared environment and release their services without coordinating every dependency. The book calls the underlying property loose coupling: components can be changed, tested, and deployed independently. Its importance was not limited to new systems. The age or category of a system generally did not predict performance; mainframes were a challenge for some low performers, but integrating with a mainframe alone was not a reliable explanation for poor results.

Structure teams around the system. Cross-functional teams with the skills to design, build, test, deploy, and operate their service need fewer handoffs. The authors connect this to Conway's observation that organizations tend to build systems reflecting their communication structures. In their analysis, high performers could increase deployments per developer as engineering teams grew, while low performers' deployment frequency fell.

Analysis

The useful architectural question is not whether an organization uses microservices, containers, or a fashionable platform. It is whether teams can make and validate changes without waiting on a chain of other teams. This reframes architecture as an organizational design problem as well as a technical one. Decoupling is not free: service boundaries can multiply operational complexity and obscure end-to-end behavior. The goal is not maximal independence, but boundaries that reduce routine coordination while preserving clear ownership of shared reliability and customer outcomes.

Build a culture where bad news travels before failures grow

Information flow predicts performance. The book uses Westrum organizational culture, a model that distinguishes environments by how they handle information, responsibility, and failure. In a generative culture, people cooperate, share risks, and treat failure as a reason to investigate the system. In a fear-driven culture, messengers may be blamed or information withheld; rule-bound cultures can protect departmental turf. The authors found that a more generative culture predicted stronger software delivery, organizational performance, and job satisfaction.

Change routines, not slogans. Culture can be influenced by the work practices people experience every day. Shared goals, visible problems, collaboration across functions, and blameless investigation can make it safer to surface risks. When a complex system fails, blaming the last person to touch it can conceal the conditions that made the failure possible. Inquiry should begin with the error, then examine the process and information that shaped it.

Analysis

A useful test of culture is what happens to inconvenient information. If bad news arrives early, teams can respond while the cost of correction is low; if it is punished, the organization may receive reassuring reports instead of accurate ones. This connects the book's cultural model to psychological safety, the shared belief that speaking up will not invite humiliation or retaliation. Safety does not mean avoiding accountability. It means distinguishing deliberate misconduct from ordinary human action in a complex environment, then learning from both the system and the choices made within it.

Put customer feedback and decision rights inside the delivery team

Learn while building. Lean product management combines small batches with visibility into the flow of work, frequent customer feedback, and authority for teams to adjust specifications. A minimum viable product is a limited version of a product designed to test assumptions and support learning, not simply a smaller finished product. Small releases can expose whether a feature solves a real problem, while techniques such as A/B testing compare responses to alternatives.

Feedback needs authority. A team that hears from customers but cannot change its plans has information without agency. The research found that Lean product practices predicted delivery and organizational performance, while delivery performance also predicted stronger product practices. The two can reinforce one another: reliable delivery makes smaller experiments practical, and useful feedback helps teams choose which changes deserve to be built.

Analysis

This is a compact model of organizational learning: formulate an assumption, expose it to users, observe what happens, and revise the work. The loop only produces value when the team can act on evidence rather than route every adjustment through a distant approval chain. Yet customer feedback is not automatically representative. Vocal users may not reflect the broader population, and short-term engagement can conflict with long-term usefulness. Good product judgment combines observed behavior with research, accessibility, strategic intent, and attention to people who are less visible in the data.

Move security into daily work, and replace approval theater with evidence

Find risks early. Shifting security left means involving security expertise during design, demonstrations, and testing, rather than treating it as a final gate. Developers should have accessible, preapproved libraries and tools, and security checks should be part of routine delivery. In the study, high performers spent 50% less time remediating security issues than low performers. The federal cloud.gov example illustrates the leverage of shared platforms: the platform addressed 269 of 325 controls for a moderate-impact system, reducing the remaining compliance burden for hosted systems.

Review changes close to the work. External change approval boards were associated with slower delivery and did not improve change failure rates. The authors recommend peer review and an automated deployment pipeline that records changes, tests, and approvals. This supports oversight without asking a distant committee to understand every technical detail.

Analysis

The argument is not that security or governance should be weaker. It is that controls work better when they are built into the path developers already use. A reusable secure platform can turn repeated compliance work into a shared capability, while automated records make the process inspectable. Still, not every risk is reducible to a test or preapproved package. High-impact decisions may require independent scrutiny. The distinction is between informed review aimed at managing risk and ritual approval that adds waiting time without adding relevant knowledge.

Improve the work system before asking exhausted engineers to cope better

Stress often has operational causes. Deployment pain describes the fear, disruption, or uncertainty people feel around releases. The book links painful deployments with poorer delivery performance, culture, and organizational performance. Manual production changes, configuration drift, brittle systems, and handoffs all make releases harder. At Microsoft, one cited team reported that work-life-balance satisfaction rose from 38% to 75% after adopting continuous delivery practices.

Burnout is not just an individual problem. The authors draw on research identifying risks such as overload, lack of control, weak rewards, poor community, unfairness, and conflicting values. Their findings connect lower burnout with technical and Lean practices, stronger leadership, and supportive culture. High-performing teams were also 2.2 times more likely to have employees recommend their organization as a place to work. Tools, autonomy, and meaningful work are part of the operating system of performance, not workplace decoration.

Analysis

The most actionable implication is to treat recurring stress as diagnostic information about work design. If every deployment requires a late-night rescue, exhortations about resilience are unlikely to fix the source. The book's approach aligns with occupational health research that locates burnout partly in demands, control, fairness, and social support, rather than in personal weakness alone. Still, technical improvements cannot resolve every source of distress. Pay, discrimination, caregiving pressure, and value conflicts may require organizational remedies beyond the delivery pipeline.

Turn leadership into visible routines that make learning part of delivery

Leaders enable the conditions. The book describes transformational leadership through vision, motivating communication, intellectual challenge, personal support, and recognition. Such leadership is associated with stronger delivery practices and employee loyalty, but leaders cannot substitute for technical capability. Their role is to provide resources, remove barriers, align work with purpose, and give teams room to experiment.

ING made learning concrete. In the bank's Netherlands operation, leaders used visual strategy rooms, short team check-ins, and a communication rhythm that carried obstacles between squads and senior managers. Teams displayed work and problems, while managers asked what they were learning and how they could help. The structure changed through experimentation rather than being copied as a fixed template. Teams could prioritize quality under pressure because their leader backed the decision not to release work that was not ready.

Analysis

The ING story makes an abstract leadership claim observable: priorities, obstacles, and learning appear in recurring practices, not just in speeches. Visual displays can shorten the distance between strategy and frontline reality, while regular check-ins create a channel for upward information. But a meeting ritual is not itself a learning culture. If leaders punish the problems surfaced on the board, the display becomes theater. The test is whether visible evidence changes resource decisions, removes impediments, and lets teams revise their approach without losing ownership.

Use metrics to guide improvement, never to rank people into silence

Measurement shapes behavior. The authors favor measures tied to outcomes and caution that numbers become dangerous when used as control. High utilization, story points, or deployment counts can encourage gaming if people are rewarded for the measure instead of the result. Metrics should help teams find bottlenecks and test whether changes improve delivery, quality, and work conditions.

Know what the evidence can say. The book's findings draw on repeated surveys, statistical checks of measurement quality, and predictive analyses. Its data came from more than 23,000 participants, but the sample was recruited through technology networks and referrals, not random selection of every software organization. The studies were cross-sectional rather than experiments tracking the same teams over time. Therefore, the reported relationships are useful evidence about patterns and predictions, not definitive proof that a practice alone caused an outcome.

Analysis

Measurement is a social intervention, not a neutral camera. Once a number affects status or compensation, people adapt their behavior to protect the number, sometimes at the expense of the underlying goal. The book's insistence on shared, system-level indicators helps reduce that risk, but does not eliminate it. A disciplined improvement cycle asks what a measure reveals, checks whether it has been distorted, and pairs quantitative signals with practitioners' accounts of the work. The research is unusually explicit about measurement quality, while its sampling and observational design still call for replication.

Analysis

Accelerate's distinctive contribution is not simply a list of software practices. It builds a chain of explanation: technical design and management routines shape information flow and work conditions; those conditions influence delivery; and delivery capacity is associated with organizational outcomes. This makes its recommendations more than a toolbox. Teams can inspect where delays, handoffs, defects, or fear enter the system, then select capabilities that address those constraints. Its most important conceptual move is to reject the false opposition between speed and reliability. Small batches, automated tests, and fast recovery make change safer by reducing how much each change can damage and how long a failure can persist. The empirical foundation is substantial for an industry study, especially its large, multi-year sample and explicit validation of survey measures. However, predictive regression on cross-sectional, self-reported data is not equivalent to a randomized causal experiment. Teams with strong leadership, investment, and technical practices may also differ in unmeasured ways. Recruitment through DevOps-oriented networks may underrepresent organizations furthest from these practices. The findings should therefore guide testable improvement efforts rather than serve as universal effect sizes.

The book's deeper management lesson is that measurement can either strengthen learning or suppress it. This resembles the problem associated with Goodhart's law: once a measure becomes a target, it can stop representing the outcome it was meant to track. The best safeguard is not abandoning metrics, but combining balanced measures with local judgment, transparent definitions, and a culture where bad news is usable. A deployment rate is informative when paired with failure and recovery data; a culture score matters when it prompts inquiry rather than a ranking exercise. High performance is less a destination than an organizational ability to notice reality, change the system, and learn again.

Summary in 30 Seconds
High-performing organizations deploy 46 times more often, move changes to production 440 times faster, recover from incidents 170 times faster, and have one-fifth the change failure rate of low performers. Small batches, reliable automated tests, and loosely coupled systems make frequent releases safer. Cross-functional teams need customer feedback and authority to act on it. Measure delivery speed alongside failures and recovery, using metrics to find system bottlenecks rather than rank individuals. Blameless learning and supportive leadership help teams improve without burning out.
Contains spoilers

Last updated:

Report Issue

Review Summary

4.05 out of 5
Average of 8k+ ratings from Goodreads and Amazon.

Accelerate receives mixed reviews, with ratings ranging from 1 to 5 stars. Positive reviews praise its research-backed insights on DevOps practices and organizational performance. Critics find it repetitive, dull, and lacking in new information. Many readers appreciate the book's scientific approach but find the writing style dry and academic. Some consider it essential reading for tech leaders, while others feel it's best suited for those new to DevOps concepts. The book's structure and content organization are points of contention among reviewers.

Your rating:
4.45
557 ratings
Want to read the full book?

Glossary

Software delivery performance

Speed and recovery outcomes

A measure of how effectively a team moves software changes into production and restores service when something goes wrong. The book assesses it through deployment frequency, lead time from code commit to production, and mean time to restore service. Change failure rate is treated as a closely related quality measure, although it is not part of the validated three-measure construct.

Continuous delivery

Release-ready software capability

A set of technical and organizational capabilities that keeps software in a state where it can be released safely when needed. It depends on practices such as version control, frequent integration, automated testing, and automated deployment. Teams use rapid feedback to detect problems and prioritize restoring the system to a releasable state.

Westrum organizational culture

Culture measured through information flow

A model of organizational culture developed by sociologist Ron Westrum, based on how information, responsibility, and failure are handled. It distinguishes pathological, bureaucratic, and generative patterns. The book uses survey items to measure trust, cooperation, cross-team connection, openness to ideas, and whether failure prompts blame or investigation.

Lean product management

Customer-informed product learning

A product development approach that makes work visible, breaks features into small batches, regularly incorporates customer feedback, and allows teams to adjust specifications. It aims to test assumptions early and improve products through evidence rather than relying entirely on large plans formed before development begins.

Deployment pain

Stress around releasing software

The fear, disruption, or difficulty that technical staff experience when software is deployed. It can indicate brittle systems, manual work, poor coordination, or a disconnect between development and operations. The book measures it through reported deployment experiences and finds that greater pain is associated with weaker delivery and organizational outcomes.

Trunk-based development

Frequent integration into shared code

A development practice in which code changes are integrated into the main development line frequently, with few active branches and short branch lifetimes. The book associates branches lasting less than a day and the absence of lengthy code freezes with stronger delivery performance. The purpose is to reduce integration delays and keep feedback close to the work.

Transformational leadership

Leadership that enables higher performance

A leadership model in which leaders support performance and organizational change through a clear vision, motivating communication, intellectual challenge, personal support, and recognition. In the book's account, leaders affect software outcomes mainly by enabling teams to adopt effective technical and management practices, rather than by substituting for the work of those teams.

Latent construct

Unobservable quality measured indirectly

A concept that cannot be measured directly, such as organizational culture or job satisfaction. Researchers represent it through multiple observable indicators, often survey items, and test whether those indicators reliably measure the same underlying concept. Using several indicators can provide a fuller measure than relying on a single question or proxy.

Work in progress (WIP) limits

Limits on unfinished work

A management practice that restricts how much work a team handles at once. Limiting unfinished work can expose bottlenecks and reduce overload, but the book emphasizes that limits matter most when teams use the resulting visibility to remove obstacles and improve the flow of work.

FAQ

What's "Accelerate: Building and Scaling High Performing Technology Organizations" about?

  • Focus on DevOps and Performance: The book explores how DevOps practices can improve software delivery performance and, in turn, organizational performance.
  • Research-Based Insights: It is based on rigorous research, including surveys and data analysis, to identify key capabilities that drive high performance in technology organizations.
  • Continuous Improvement: The authors emphasize the importance of continuous improvement and learning within organizations to remain competitive.
  • Cultural and Technical Practices: It covers both cultural and technical practices that contribute to high-performing teams and organizations.

Why should I read "Accelerate: Building and Scaling High Performing Technology Organizations"?

  • Evidence-Based Practices: The book provides evidence-based practices that have been proven to improve software delivery and organizational performance.
  • Comprehensive Framework: It offers a comprehensive framework for understanding and implementing DevOps and Lean management practices.
  • Actionable Insights: Readers will gain actionable insights into how to transform their organizations into high-performing technology teams.
  • Broad Applicability: The principles and practices discussed are applicable to organizations of all sizes and industries.

What are the key takeaways of "Accelerate: Building and Scaling High Performing Technology Organizations"?

  • Importance of Software Delivery Performance: High software delivery performance is critical for organizational success and can be a competitive advantage.
  • Role of Culture: A generative, performance-oriented culture is essential for high performance and can be influenced by implementing DevOps practices.
  • Continuous Delivery Practices: Implementing continuous delivery practices leads to better software delivery performance and reduces deployment pain and burnout.
  • Leadership and Management: Transformational leadership and Lean management practices are crucial for supporting high-performing teams.

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

  • "You can act your way to a better culture by implementing these practices in technology organizations." This quote emphasizes that culture change can be achieved through deliberate actions and practices.
  • "High performers understand that they don’t have to trade speed for stability or vice versa." It highlights that with the right practices, organizations can achieve both speed and stability in software delivery.
  • "The goal of a loosely coupled architecture is to ensure that the available communication bandwidth isn’t overwhelmed by fine-grained decision-making." This underscores the importance of designing systems that allow teams to work independently and efficiently.

How does "Accelerate" define and measure software delivery performance?

  • Four Key Metrics: The book defines software delivery performance using four key metrics: lead time, deployment frequency, time to restore service, and change fail rate.
  • Cluster Analysis: It uses cluster analysis to categorize organizations into high, medium, and low performers based on these metrics.
  • No Trade-Offs: The research shows that high performers excel in both speed and stability, debunking the myth that these are trade-offs.
  • Impact on Organizational Performance: High software delivery performance is linked to better organizational outcomes, such as profitability and market share.

What role does culture play in "Accelerate"?

  • Westrum's Typology: The book uses Westrum's typology to model organizational culture, focusing on information flow and trust.
  • Generative Culture: A generative, performance-oriented culture is linked to better software delivery and organizational performance.
  • Influencing Culture: Culture can be influenced by implementing DevOps practices, which improve collaboration and information flow.
  • Measuring Culture: The book provides a framework for measuring culture using Likert-type questions to assess team dynamics.

What are the continuous delivery practices discussed in "Accelerate"?

  • Key Principles: Continuous delivery involves building quality in, working in small batches, and automating repetitive tasks.
  • Technical Practices: It includes version control, deployment automation, continuous integration, and test automation.
  • Impact on Performance: These practices lead to faster, more reliable software releases and reduce deployment pain and burnout.
  • Cultural Influence: Implementing continuous delivery practices positively impacts organizational culture and employee satisfaction.

How does "Accelerate" address leadership and management?

  • Transformational Leadership: The book emphasizes the importance of transformational leadership in driving high performance.
  • Five Dimensions: Transformational leaders exhibit vision, inspirational communication, intellectual stimulation, supportive leadership, and personal recognition.
  • Role of Managers: Managers play a critical role in connecting strategic objectives to team actions and creating a supportive work environment.
  • Leadership's Indirect Impact: Leadership indirectly influences performance by enabling technical and Lean practices.

What is the significance of Lean management in "Accelerate"?

  • Lean Practices: Lean management practices include limiting work in progress, visualizing work, and using monitoring tools for decision-making.
  • Impact on Culture: These practices contribute to a generative culture and reduce burnout.
  • Lightweight Change Management: The book advocates for a lightweight change approval process based on peer review rather than external boards.
  • Continuous Improvement: Lean management supports continuous improvement and aligns team efforts with organizational goals.

How does "Accelerate" suggest organizations handle information security?

  • Shift Left on Security: The book recommends integrating security into the software delivery process rather than treating it as a separate phase.
  • Infosec Involvement: Information security teams should be involved throughout the development lifecycle, providing feedback and tools.
  • Reducing Security Remediation: High performers spend less time on security remediation by building security into their processes.
  • Rugged DevOps: The book introduces the concept of Rugged DevOps, emphasizing the importance of security in DevOps practices.

What does "Accelerate" say about employee satisfaction and engagement?

  • Employee Net Promoter Score (eNPS): High-performing organizations have better employee loyalty, as measured by eNPS.
  • Identity and Values Alignment: Employees who identify with their organization's values are more engaged and satisfied.
  • Impact on Performance: Employee satisfaction and engagement are linked to better organizational performance and reduced burnout.
  • Tools and Resources: Providing employees with the right tools and resources is crucial for job satisfaction and performance.

How does "Accelerate" address diversity and inclusion?

  • Importance of Diversity: The book highlights research showing that diverse teams achieve better performance and business outcomes.
  • Current State: It provides statistics on the representation of women and minorities in DevOps teams.
  • Inclusion: Diversity alone is not enough; organizations must also foster an inclusive environment where all members feel valued.
  • Resources for Improvement: The book suggests resources like Anita Borg Institute and Project Include to support diversity initiatives.

About the Author

Nicole Forsgren PhD is an expert in DevOps and IT organizational performance. She is known for her work on the annual State of DevOps Report and her research on high-performing technology organizations. Forsgren has a background in management information systems and is recognized for her ability to apply rigorous research methods to practical business problems. Her work focuses on using data to drive decision-making and improve software delivery and organizational outcomes. Forsgren has collaborated with other prominent figures in the DevOps community and has contributed to several influential books in the field. Her research and insights have been widely cited and have helped shape modern software development practices.

Download PDF

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

Download EPUB

To read this Accelerate 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.43 MB     Pages: 28
Want to read the full book?
Follow
Listen9 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
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...