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
Joy, Inc.

Joy, Inc.

How We Built a Workplace People Love
What if better work came from changing how teams share knowledge, make choices, and learn?
by Richard Sheridan 2013 288 pages
4.07
1k+ ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Define joy by what your work changes, not how cheerful it feels

Joy is purposeful accomplishment. Sheridan distinguishes joy from momentary happiness. At Menlo, joy means building something that reaches its intended users, works well for them, and gives the team a sense of worthwhile achievement. A demanding project can be frustrating day to day and still be joyful if it produces a valuable result. Menlo helped create software for cancer and AIDS research, and for organ transplant systems, work that mattered beyond the company itself.

A career can lose its spark. Sheridan began programming as a teenager, then rose to executive success while enduring failed projects, poor quality, and work that crowded out family life. He chose to change how work was organized rather than abandon the field. Menlo was founded in 2001 to make useful products and to share a better way of working. The point is not cheerfulness as a perk, but meaningful work made achievable.

Analysis

The distinction between joy and cheerfulness protects the idea from becoming a demand for constant positivity. In organizational psychology, meaningful work is often understood as a connection between daily effort and a consequence that matters to someone. That connection can sustain effort through difficulty without pretending the difficulty feels good. The framing also raises a practical question: who defines a valuable outcome? A team may feel proud while users remain frustrated. Menlo’s emphasis on adoption and user delight offers a needed external check on internal morale.

Design the workplace to make useful collaboration the easiest move

Space makes behavior visible. Menlo replaced private offices and cubicles with a bright, flexible open room. Lightweight tables can be rearranged when projects change, and the CEO sits among the team rather than behind a status-signaling office door. The space is noisy, but the noise is mostly pairs discussing actual work. The aim is not to make an office look playful. It is to lower the barriers to asking questions, sharing information, and noticing what others are learning.

Movement creates ownership. Teams rearrange tables to fit projects, and sometimes change the layout simply to refresh their perspective. At one former workplace, a weeklong experiment in an open factory space produced more learning, energy, and progress than the old offices. Yet this approach has limits: Menlo acknowledges that guests can find the noise difficult, and remote work can help people manage serious family needs. The design principle is to support interaction, not to mandate one layout everywhere.

Analysis

The room is part of the operating system: it changes who can overhear, interrupt, ask for help, or join a decision. This resembles distributed cognition, the idea that thinking can be supported by people, tools, and surroundings rather than residing only in an individual mind. Still, open offices can impose noise and social costs, especially on people doing concentrated work or those with sensory needs. Menlo’s lesson is better read as a design challenge: make collaboration easy while preserving legitimate ways to concentrate and recover.

Pair people to spread skill, judgment, and responsibility

Two people learn through the work. At Menlo, pairs share a computer and work on the same task. Partners change weekly, so knowledge travels across the team instead of staying with one expert. A person who learns a client’s domain one week teaches the next partner, deepening the first person’s own understanding while bringing another colleague up to speed.

Redundancy creates resilience. Pairing helps people get unstuck, exposes errors, and makes vacations possible because no single person owns an essential piece of knowledge. Sheridan describes a former company’s dependence on one programmer whose expertise made him indispensable and trapped him in a narrow role. Regularly changing pairs makes such towers of knowledge harder to build. It also means people must contribute: a team member who never retains or shares what they learn is quickly visible. Menlo treats pairing as a learning and coordination system, not simply two people doing one person’s job.

Analysis

Pairing turns knowledge transfer from a special event into ordinary production. That is a powerful design choice: organizations often depend on documentation and training precisely because expertise has already become isolated. Shared work can also expose assumptions sooner, much as code review and peer checking do in other technical fields. The tradeoff is real. Pairing demands sustained attention, and personalities or tasks may not always match. Its success depends on deliberate rotation, respectful collaboration, and work that benefits from frequent exchange.

Study users in context before deciding what they need

Observe the work itself. High-Tech Anthropology is Menlo’s method for understanding users in their real environments, through observation and conversation rather than relying only on a client’s assumptions. The team creates user profiles called personas, then selects one primary persona to guide design. A persona is a research-based representation of a key user, including goals and circumstances, not a claim that every user is identical.

Small details change adoption. While observing a bus mechanic, Menlo’s team noticed he wore gloves. The proposed touch screen would not work with them, so the design changed before development went too far. In another project, a medical instrument company initially focused on lab directors. Discussion revealed that making the tool easy enough for their assistants to use could open a much larger user group. The team then tested rough paper or cardboard prototypes with real users, watched them try tasks, and revised the design based on what happened.

Analysis

Observation corrects a familiar bias: people designing a system tend to treat their own habits and vocabulary as universal. Contextual research can reveal constraints users rarely mention because those constraints have become routine. Personas help teams keep a user present during design debates, but they can also flatten differences if treated as facts rather than hypotheses. The best safeguard is the one Menlo uses alongside them: return to real users, test a concrete task, and revise the profile when evidence does not fit.

Make change cheap enough that teams can learn in public

Small trials lower the stakes. Menlo’s principle of making mistakes faster means trying low-cost experiments, learning from the result, and changing course without turning every trial into a permanent commitment. Sheridan first tested paired work with one pair, then tried it with a larger group for a week. The experiments made the new approach tangible before the company committed to changing its daily work.

Fear makes failure expensive. When people expect punishment, they hide bad news, protect existing plans, and may continue a failing project because too much has already been invested. Sheridan cites Ford’s canceled Everest project, which had consumed $400 million before cancellation, as an example of how costly delayed recognition can become. Menlo’s practical response is to run small tests, make it safe to report problems, and allow enough repetition to judge an experiment fairly. Cheap failure is not carelessness. It is a way to avoid large, slow failures.

Analysis

This approach resembles experimental design: isolate a change, observe its effects, and update action rather than defend a prediction. Its organizational value depends on psychological safety, meaning people can disclose uncertainty or mistakes without expecting humiliation or retaliation. Safety alone is not sufficient, however. Experiments need clear questions and a willingness to stop practices that do not work. Otherwise, constant trial can feel chaotic. Menlo’s emphasis on small scope, visible results, and reversible decisions helps distinguish learning from novelty for its own sake.

Put priorities where everyone can see what is chosen and refused

A card turns a request into work. Menlo requires client tasks to be written on story cards, estimated by the people doing the work, prioritized with the client, and assigned to pairs. A task not selected for the plan is not authorized. This blocks hallway requests from quietly joining an already full workload. The team also uses a Work Authorization Board, a visible grid showing which pair owns each task during the week and the task’s status.

Rituals replace status theater. Daily standups take about thirteen minutes, with pairs sharing current work and requests for help. In weekly Show & Tell sessions, clients handle and review the work rather than merely hearing a progress report. Menlo’s weekly planning process forces tradeoffs: adding one priority means making room by removing another. The system is deliberately simple and paper-based, with copies kept for records. Its purpose is shared clarity, so people can act without repeatedly asking what matters or who decided.

Analysis

Visible work reduces the hidden coordination tax of meetings, private conversations, and conflicting recollections. A shared board makes priorities inspectable and helps a team distinguish an approved commitment from an idea someone mentioned in passing. It also shifts authority toward the people doing and sponsoring the work. The method is not automatically democratic: whoever controls prioritization can still dominate. Its fairness depends on access to the planning conversation, genuine client participation, and permission to challenge estimates without retaliation.

Hire for teachability and collaboration, then let the team decide

Show candidates the real culture. Menlo begins recruiting with a tour, so applicants can see the open, paired work style and decide whether it suits them. Its group interview has candidates work together on practical exercises while employees observe how they share, listen, and solve problems. Rather than hiring solely for a narrow set of current technical skills, Menlo looks for curiosity and the ability to learn.

A job starts before day one. Candidates who pass the group exercise can spend a paid day on real work, followed by a paid three-week trial. The people who pair with the candidate help assess fit. Sheridan contrasts this with a traditional hire who arrives to find no equipment, no clear assignment, and a job unlike the one described in the interview. The process is designed to let both sides discover a mismatch early. Menlo also tries to let people leave with dignity, and some later return.

Analysis

A realistic work sample can reveal collaboration habits that polished interviews conceal, while giving candidates a meaningful chance to assess the employer. Peer input is especially relevant when future colleagues bear the daily costs of a hiring decision. Yet culture fit can become a gatekeeping phrase that rewards similarity or penalizes unfamiliar communication styles. Menlo’s emphasis on learning and varied backgrounds helps counter that risk, but any team-led process still needs transparent criteria and attention to whose voices carry weight.

Replace blame with honest estimates, rigorous checks, and visible results

Accountability must run both ways. Menlo asks teams to estimate their own work, then protects those estimates from managerial pressure. If a task takes longer than expected, the pair reports the problem early, and the client decides whether to continue or shift priorities. The point is not that estimates are always right; it is that people can tell the truth when a miss carries no automatic punishment. The client, project manager, team, and leader all have responsibilities.

Discipline protects pride. Menlo combines this trust with quality practices: pairs review work, programmers write automated tests before code, and the team integrates work continuously rather than waiting until project end. Clients see working results each week. Sheridan compares these routines to hand washing in medicine and read-back checks in a deli: small repeated safeguards can prevent consequential errors. The process is not a substitute for judgment. It creates dependable conditions in which judgment, learning, and candor can improve the result.

Analysis

The model distinguishes accountability from punishment. In a punitive system, people have incentives to pad estimates, conceal delays, or claim completion prematurely. In a trustworthy system, accurate information is useful rather than dangerous. That is a strong foundation for operational learning. The qualification is that customer-billed overruns may be unacceptable in fixed-price or safety-critical settings, so the exact contract matters. The transferable principle is to align incentives with truthful reporting, explicit tradeoffs, and quality checks that catch errors before they spread.

Protect recovery and build teams that can scale both ways

A sustainable pace is a business choice. Menlo sets a standard forty-hour workweek, begins employees with four weeks of vacation, and expects people to disconnect while away. Pairing provides coverage, so a vacation does not leave one colleague as the only person who can keep a project moving. Sheridan argues that a team that is technically present but exhausted is not fully available to do creative work.

Flexibility makes capacity usable. Because people share knowledge and learn across roles and projects, Menlo can add or remove people without relying on a single expert. It treats scaling down as seriously as growth, and maintains some slack through internal work, subcontractors, and adjustable client arrangements. Its account of flexibility is not universal: it favors a shared physical workspace, while making exceptions for family crises. The underlying aim is to respond to changing demand without converting every surprise into overtime.

Analysis

The link between recovery and resilience is more than a morale argument. Organizations that depend on constant overtime consume the very attention needed to catch errors and adapt. Redundancy through shared knowledge also makes the system less brittle, much as backup capacity does in engineering. Still, a single location and a forty-hour norm may not fit every workforce or task. Menlo’s more general lesson is to make coverage, recovery, and workload adjustment part of the operating design, not favors granted after people are already depleted.

Make your public promise match the daily experience inside

Alignment begins with honesty. Sheridan argues that a company’s external reputation, employees’ lived experience, and leaders’ actual behavior should point in the same direction. Menlo makes its culture visible to visitors and candidates rather than selling an idealized version of work. It also declines some contracts when their terms or procurement processes conflict with how it believes useful software should be built.

Risk makes the promise credible. Through a leveraged play, Menlo sometimes accepts part of its fee as equity or royalties in a client’s product. This aligns some of its financial reward with whether the product succeeds, though the book notes that several investments failed and many remained uncertain. The Accuri Cytometers project, which Menlo helped build, was sold for $205 million. The broader point is not that every company should take equity. It is that values become believable when they shape contracts, hiring, customer choices, and the distribution of rewards.

Analysis

Alignment is a practical defense against cynicism. If a company advertises care while rewarding overwork, employees learn to trust the incentives, not the slogans. A visible match between promise and practice can also make recruiting and customer relationships more coherent. However, public transparency alone cannot guarantee ethical conduct, and financial alignment can create conflicts if a vendor’s upside differs from a user’s needs. The useful test is whether the company’s incentives, daily routines, and claims reinforce the same outcome for the people affected.

Analysis

Joy, Inc. is part memoir, part management argument, and part operating manual. Sheridan’s central claim is concrete: a company can deliberately organize work so that people enjoy the process, users value the output, and the business remains viable. His credibility comes less from abstract theory than from a career reversal. He moves from early enthusiasm for programming, through executive success and burnout, toward a set of experiments that eventually become Menlo Innovations.

The book’s strongest contribution is its insistence that culture is built into workflow. Open space matters because it changes access to information. Pairing matters because it distributes knowledge. Written cards, estimates, and demonstrations matter because they make commitments observable. These practices reinforce one another: shared work creates learning, visible priorities support autonomy, and rapid client feedback keeps internal pride answerable to external usefulness. Joy is not treated as a mood employees must perform. It is an outcome supported by systems. The account also makes a persuasive case against hero-centered organizations. A specialist who alone understands a critical process may look indispensable, but that arrangement transfers risk to the person and the company. Menlo’s rotation, teaching, and cross-training make resilience part of ordinary work. Similarly, the book exposes how fear corrupts data: if people are punished for missed estimates, they learn to distort estimates. Trust becomes operationally valuable because it improves the information on which decisions depend.

The evidence, however, is largely a successful company’s own experience. Menlo’s practices are not controlled comparisons, and some claims about open offices, remote work, or pairing cannot be universalized from one workplace. The book is most useful as a source of design principles and testable practices, not a blueprint to copy wholesale. Leaders should preserve the logic while adapting the form to different tasks, accessibility needs, regulations, and labor arrangements. Its enduring challenge is to measure success in more than speed or employee sentiment: does the work reach users, serve them well, and remain sustainable for the people who make it?

Summary in 30 Seconds
Work systems shape culture: open spaces, rotating pairs, and shared task boards make questions, knowledge, and priorities visible. Teams learn faster when they test ideas cheaply, invite users to try rough prototypes, and treat problems as information rather than grounds for blame. Pairing spreads expertise and provides coverage. A 40-hour week and four weeks of starting vacation support recovery. Honest estimates, regular quality checks, and weekly demonstrations keep work accountable to clients.
Contains spoilers

Last updated:

Report Issue

Review Summary

4.07 out of 5
Average of 1k+ ratings from Goodreads and Amazon.

Joy, Inc. receives mixed reviews, with many praising its innovative approach to workplace culture and software development. Readers appreciate the focus on employee happiness, paired programming, and transparency. However, some question the practicality of implementing these methods in other industries. Critics argue that the book feels self-promotional and lacks discussion of potential downsides. Overall, reviewers find the concept of prioritizing joy in the workplace intriguing, even if they're skeptical about universal application.

Your rating:
4.52
192 ratings
Want to read the full book?

Glossary

High-Tech Anthropology

User research through observation

Menlo’s approach to learning how people actually work with products and services. Researchers observe users in their everyday settings, ask questions, and use what they learn to shape and test designs. The method treats user behavior and context as evidence, rather than assuming that a client’s description or a focus group captures all relevant needs.

High-Tech Anthropologist

User researcher and designer

A Menlo team member who studies users and translates observations into design decisions. High-Tech Anthropologists work in pairs, create user profiles and rough prototypes, and watch people attempt real tasks. The role is not limited to software specialists; Sheridan describes people entering it from fields such as teaching, journalism, and operations.

persona

Research-based user profile

A written representation of a significant user type, assembled from observations and conversations with real people. It describes a user’s circumstances, goals, and concerns so a team can evaluate design choices from that person’s perspective. Menlo asks clients to choose one primary persona rather than designing vaguely for everyone.

Extreme Interviewing

Collaborative hiring assessment

Menlo’s hiring process begins with a group of candidates completing paired exercises while employees observe how they collaborate. Candidates who advance can work a paid day on a real project and then enter a paid trial period. The process exposes applicants to the actual work style and lets the team assess learning and interpersonal fit.

Planning Origami

Paper-based work sizing

A technique for representing estimated work by folding copies of story cards to different sizes. The folded cards are placed on planning sheets with a defined capacity, making time and budget limits visible. Clients choose which tasks fit, so adding work requires a concrete tradeoff rather than an informal request.

Work Authorization Board

Visible weekly task assignments

A wall display that shows the tasks assigned to each pair for the week, along with project and status information. It gives team members, managers, and visitors a shared view of who is responsible for what. In Menlo’s process, a task reaches the board only after it has been written, estimated, and authorized.

Show & Tell

Weekly client work review

A recurring meeting in which clients interact with the work completed during the previous week and explain what they see. Menlo’s team listens, answers questions, and identifies mismatches between expectations and the product. The practice replaces abstract progress reporting with direct feedback on a tangible result.

High-Speed Voice Technology

Direct spoken communication

Sheridan’s playful name for in-person conversation using speech, facial expression, body language, and tone. Menlo uses direct conversation instead of relying on email for ordinary communication. The term highlights how a short spoken exchange can resolve a question without scheduling a formal meeting or creating a long written thread.

Make Mistakes Faster

Learn through small experiments

Menlo’s principle of testing new ideas through quick, inexpensive, and limited experiments. A team begins with a small trial, observes what happens, and adjusts or stops the practice based on evidence. The goal is not to celebrate errors, but to find problems early, before they become costly commitments.

leveraged play

Fee partly exchanged for upside

A Menlo business arrangement in which the company defers some cash payment in exchange for equity in a client company or royalties from a product it helps develop. The arrangement ties part of Menlo’s compensation to the product’s commercial outcome. It can create significant returns, but it also exposes the company to projects that may fail.

FAQ

What's Joy, Inc.: How We Built a Workplace People Love about?

  • Focus on Joy: Joy, Inc. by Richard Sheridan explores creating a workplace centered around joy, positioning it as a core business strategy rather than just a feel-good concept.
  • Menlo Innovations: The book details the practices and culture at Menlo Innovations, a software company known for its joyful work environment.
  • Transformational Change: Sheridan shares his journey from corporate disillusionment to establishing a joyful workplace, offering insights for similar organizational changes.

Why should I read Joy, Inc.: How We Built a Workplace People Love?

  • Practical Insights: The book provides actionable advice and real-life examples from Menlo Innovations, valuable for leaders aiming to improve organizational culture.
  • Revolutionary Approach: It challenges conventional management by advocating for joy as a primary driver of productivity and employee satisfaction.
  • Inspiration for Change: Readers will find inspiration in Sheridan's journey and transformative practices, encouraging a rethink of workplace dynamics.

What are the key takeaways of Joy, Inc.: How We Built a Workplace People Love?

  • Joy as Strategy: Joy can lead to better business outcomes, including increased productivity and employee engagement.
  • Environment Matters: Physical workspace design impacts morale and collaboration, with open, flexible spaces fostering communication.
  • Pair Programming: Pairing employees enhances learning, collaboration, and accountability, a key practice at Menlo Innovations.

How does Joy, Inc.: How We Built a Workplace People Love define joy in the workplace?

  • Joy vs. Happiness: Joy is a deeper, more meaningful state from fulfilling work and achieving shared goals, distinct from happiness.
  • Collective Experience: Joy enhances teamwork and collaboration, leading to a more engaged workforce.
  • Tangible Outcomes: A joyful workplace results in improved productivity and employee retention.

What is the significance of "High-Tech Anthropology" in Joy, Inc.: How We Built a Workplace People Love?

  • User-Centric Design: High-Tech Anthropology ensures software is designed with the end user in mind, focusing on usability and experience.
  • Observation and Empathy: It involves observing users in their environments to understand needs and challenges, leading to better design.
  • Creating Personas: User personas guide design decisions, ensuring software meets actual user needs.

What are some specific practices mentioned in Joy, Inc.: How We Built a Workplace People Love for fostering joy?

  • Daily Standups: Team members share progress and challenges, fostering open communication and support.
  • Show & Tell: Weekly rituals allow teams to present work to clients, ensuring alignment and celebrating achievements.
  • Flexible Workspaces: Open office layouts encourage interaction and creativity, contrasting with traditional setups.

How does Joy, Inc.: How We Built a Workplace People Love address fear in the workplace?

  • Eliminating Fear: Creating a safe environment where employees can experiment and make mistakes without fear of retribution is crucial.
  • Cultural Shift: The book advocates for moving away from blame towards collective problem-solving and learning from failures.
  • Empowerment through Safety: A culture of safety encourages risk-taking and innovation, leading to greater joy and productivity.

What is the "Planning Game" in Joy, Inc.: How We Built a Workplace People Love?

  • Collaborative Estimation: Teams collaboratively estimate task time, ensuring alignment on priorities.
  • Visual Management: Visual aids like story cards facilitate discussions and decision-making, clarifying task progress.
  • Empowerment: Involving the entire team in planning empowers employees and fosters shared responsibility.

What is the Planning Origami method mentioned in Joy, Inc.: How We Built a Workplace People Love?

  • Visual Planning Tool: Uses folded index cards to represent tasks and time estimates, aiding workload management.
  • Combating Scope Creep: Helps prevent scope creep by prioritizing tasks and managing new requests.
  • Collaborative Process: Fosters collaboration among team members and clients during planning, ensuring alignment.

How does Joy, Inc.: How We Built a Workplace People Love address the concept of leadership?

  • Leadership as Empowerment: True leadership is about empowering team members rather than exerting control.
  • Vulnerability in Leadership: Leaders should admit mistakes and seek team input, building trust and open communication.
  • Growing Leaders: Develop leaders at all levels, not just those with formal titles, emphasizing empathy and collaboration.

What role do clients play in the Menlo Innovations culture described in Joy, Inc.: How We Built a Workplace People Love?

  • Client Inclusion: Clients are included in daily standups and planning, fostering transparency and collaboration.
  • Feedback Loop: Show & Tell sessions provide structured feedback, aligning expectations and enhancing satisfaction.
  • Building Relationships: Involving clients builds trust and mutual understanding, leading to better outcomes and partnerships.

How does Joy, Inc.: How We Built a Workplace People Love suggest handling mistakes and failures?

  • Embrace Mistakes: Mistakes are seen as learning opportunities, not failures, leading to growth and improvement.
  • Make Mistakes Faster: Encourages quick mistakes to learn and adapt, allowing iteration without fear of repercussions.
  • Reflect and Adjust: Teams reflect on setbacks and adjust strategies, fostering a continuous improvement mindset.

About the Author

Richard Sheridan is the CEO and co-founder of Menlo Innovations, a software company in Ann Arbor, Michigan. He is known for his unique approach to creating a joyful workplace culture. Sheridan's background includes experience as a computer prodigy and successful early career in IT management. Disillusioned by the industry's norms, he started Menlo Innovations with a mission to spread joy through software work. Sheridan is passionate about leadership, workplace culture, and innovative business practices. He frequently speaks about these topics and hosts visitors at Menlo to showcase their unique work environment.

Download PDF

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

Download EPUB

To read this Joy, Inc. 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.33 MB     Pages: 26
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 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...