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
The Year Without Pants

The Year Without Pants

WordPress.com and the Future of Work
He closed 252 support tickets; his colleague handled 1,810. What did the gap reveal?
by Scott Berkun 2013 258 pages
3.81
2k+ ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Make work location-independent, but tie accountability to shipped value.

Results over rituals. Scott Berkun joined Automattic, the company behind WordPress.com, as an outsider asked to lead a small team. Around sixty employees worked from wherever they chose, with few fixed schedules, little email, and no conventional office routine. The test was not whether someone looked busy at a desk. It was whether useful work reached customers. The title’s joke about working without pants points to a serious experiment: remove rules about where and when work happens, then judge the results rather than the ritual.

Freedom needs capable people. Automattic could work this way because it hired self-directed people and trusted them to solve problems. The approach was not a plug-in that any company could install. It depended on shared purpose, strong communication, and people who could organize their own days.

Analysis

What's distinctive is the pairing of autonomy with visible contribution. In motivation research, autonomy tends to support engagement when people also have competence and a clear sense of purpose. Remove the office rule without supplying those conditions, and freedom can become abandonment. The company’s model also relied on selecting people already suited to independence, which limits how easily another organization can copy it. The useful test for managers is not whether remote work feels modern, but whether employees have the tools, goals, and authority to deliver good work wherever they are.

Work the support queue before claiming to understand customers.

Start at the front line. New Automattic employees spent their first days answering customer support requests, a role the company called Happiness Engineering. Berkun expected repetitive complaints and found the work harder than he imagined. A vague ticket such as a report that a blog was broken required careful questions and translation from the customer’s experience into a technical diagnosis. Even the form’s prompts, asking what the customer did, saw, and expected, could not guarantee a useful answer.

The numbers humbled him. During roughly a month of support work, Berkun closed 252 tickets. A skilled colleague, Anthony Bubel, handled 1,810 in about the same period. The tour gave new hires product knowledge, contact with customers, and relationships with coworkers through actual work, not a generic orientation session.

Analysis

Front-line work functions as organizational sensing. Customer-facing employees encounter confusion that dashboards and executive summaries often flatten into categories. Requiring product makers and managers to experience that work can improve judgment, especially when support feedback flows back into design decisions. But the ticket count also shows a danger: exposure is not the same as expertise. A short tour cannot reproduce the practiced speed or emotional load of a specialist’s job. The strongest version of this practice treats support colleagues as skilled professionals, not as temporary guides for more prestigious employees.

Build culture through repeated behavior, not borrowed management rituals.

Values began in practice. WordPress grew from Matt Mullenweg and Mike Little continuing an abandoned blogging project called b2 or Cafelog. Its open-source license let others use, change, and carry on the software. As contributors joined, public discussion, respect for useful contributions, and concern for the project’s survival became habits. Berkun describes these as transparency, meritocracy, and longevity. Automattic inherited that culture, rather than creating it through a retreat or a slogan.

Hiring reinforced the pattern. Candidates generally demonstrated their ability through a real trial project instead of relying only on interviews and résumés. The company also tried to hire people with broad capabilities and strong initiative. Berkun warns that copying a method without the people and values that make it work resembles a cargo cult: the visible ritual is reproduced, but the conditions behind its success are missing.

Analysis

Culture is a selection effect as much as a training effect. People notice which behaviors earn trust, then either adapt or leave, gradually making the organization more consistent. That can create powerful alignment, but it can also make a culture hard to enter for people who do not already know its unwritten rules. Public processes and practical work samples may reduce some hiring theater, yet fairness still depends on what the trial rewards and who can afford the time to complete it. Copying a culture requires examining incentives and access, not merely adopting its vocabulary.

Ship small improvements, then let real use correct your assumptions.

Launch to learn. WordPress.com could change its live service frequently, so teams often released modest improvements instead of waiting for a large, polished launch. Before building a feature, a team drafted its customer announcement and considered what evidence would show whether the feature helped. The announcement tested whether the idea could be explained clearly; usage data offered a way to assess its effects.

A small feature found an audience. Berkun’s team added email notices when someone liked or subscribed to a blog. Within two days, the system was sending about 18,000 notices daily, while few users disabled them. The result gave the team more than an opinion about whether the feature was useful. Small launches also made mistakes easier to investigate and fix, though fast release still required people to watch for problems.

Analysis

Short feedback loops are valuable because they replace prediction with observation. They resemble experimental design: state what the change is meant to improve, collect relevant evidence, and revise based on what happens. The discipline lies in measuring the intended benefit rather than merely celebrating activity. A quick launch is not automatically a good experiment, particularly when users bear the cost of defects or when effects take time to emerge. Small releases work best when reversibility, monitoring, and a credible way to learn accompany the speed.

Use plans to guide movement, not to pretend the future is certain.

Alternate scale and speed. Berkun uses the contrast between cathedral-style planning, where a large structure is designed in advance, and bazaar-style development, where a product grows through many small contributions. Software can often benefit from the second approach because changes can be released and revised. Automattic’s teams could move quickly, but that freedom also made it easy for separate features to accumulate without a coherent whole.

Big work still needs maps. The team’s effort to unify WordPress.com’s commenting systems, nicknamed Highlander, stalled when the work proved harder to divide than expected. Berkun’s team then mapped work into smaller chunks, made a plan for the larger project, and adjusted as it learned. A map of the next few steps limits wasted effort, while occasional longer-range thinking helps ensure those steps point toward a product that fits together.

Analysis

The planning debate is not really a choice between control and improvisation. It is a question of where uncertainty is most expensive. A small website change can often be tested cheaply; a safety-critical system or tightly coupled platform may demand deeper analysis before release. The team’s difficulty with legacy code illustrates a further point: incremental work can still be strategically blind if every increment optimizes one component. Effective planning distinguishes reversible decisions from costly commitments, and gives teams permission to revisit assumptions as evidence changes.

Treat metrics as evidence, because every scoreboard reshapes behavior.

Numbers can mislead. During support training, Berkun did not know that ticket totals were tracked. Once he learned he was far behind experienced colleagues, he pushed his count upward, then grew tired and frustrated. A measure intended to describe work had also become a pressure to produce more of it. The book makes a similar point about counting lines of code: more output does not necessarily mean better software, and a simple target can reward the wrong behavior.

Use data to see, not decree. Automattic had MissionControl, a reporting tool for activity on WordPress.com, such as posts published and comments made. The information helped teams investigate what users did, but it could not explain why they did it or decide what mattered. Berkun favors data-informed judgment: compare incoming problems with fixes, examine user patterns, and then use human interpretation to choose what deserves attention.

Analysis

A metric changes the system it measures. Once a number becomes a target, people sensibly direct effort toward improving that number, sometimes at the expense of unmeasured quality. This is why a balanced dashboard should combine outcome measures, diagnostic signals, and qualitative evidence rather than collapse performance into one score. Data is especially useful for challenging confident assumptions, but it cannot settle questions of value by itself. A chart may show that users stopped using a feature; it cannot tell a team whether the feature was unnecessary, confusing, or poorly explained.

Replace missing office context with deliberate, human communication.

Text carries less context. Automattic relied heavily on internal blogs called P2s, group chat through IRC, and private Skype messages. P2 discussions were searchable and available to colleagues who had missed them, unlike email threads trapped in inboxes. The trade-off was ambiguity: silence might mean agreement, distraction, or that someone never saw the post. A detailed conversation could also drift into a side debate while its original question went unanswered.

Distance requires initiative. Remote coworkers could not easily read a colleague’s mood or notice when someone was struggling. Berkun found that private conversations helped him build trust, while periodic team meet-ups restored connection and made collaboration easier. His team eventually spread across time zones so widely that one person joined meetings at 2 a.m. Remote work expanded hiring options and personal freedom, but it did not eliminate the need to manage relationships.

Analysis

Written channels create durable records and make participation less dependent on being in a room at the right moment. They also remove tone, timing, and the informal cues people use to repair misunderstandings. A useful communication system is therefore multimodal: public writing for shared context, private conversation for sensitive or narrow issues, and voice or video when nuance matters. Remote teams should not treat frequent messages as a substitute for belonging. Nor should in-person contact be romanticized: office proximity can produce interruptions and exclusion too. The goal is to make connection intentional.

Add enough friction to finish difficult work without burying makers.

Too little structure has costs. Automattic avoided many schedules, approval layers, and formal processes. That made it easy for Berkun’s team to change direction, but it also made long, unpleasant projects easy to postpone. IntenseDebate, an acquired commenting product, took far longer to improve than the team expected. The absence of a deadline or a clear breakdown of tasks did not make the hard parts disappear.

A deadline changed the work. For Jetpack, a tool connecting WordPress sites to features hosted by WordPress.com, the team committed to launch around the SXSW event. They brought in extra designers and programmers, divided tasks, tracked assignments and estimates in a shared spreadsheet, and tested the product across hosting services. The structure was not a universal process imposed on every project. It was added because this project had a public date and compatibility risks.

Analysis

Creative work benefits from both freedom and constraint. A deadline can focus attention and force decisions, but arbitrary pressure can also narrow exploration or encourage hidden quality problems. The relevant question is whether a constraint resolves a real coordination need. Public commitments, release checklists, or short review points can help a team complete work without recreating a bureaucracy. The Jetpack example is strongest because structure was tied to identifiable demands: a launch date, new contributors, and many hosting environments. Friction should serve the work, not simply reassure managers that they are managing.

Protect product coherence, not just the steady production of features.

More features can make products worse. WordPress accumulated options and interface elements built at different times, often without considering how they looked together. Berkun called the cluttered collection of sharing and rating tools below blog posts NASCAR, because each element seemed to compete for attention. A side project to simplify that area required weeks of work, despite seeming small at first.

Look for the user’s blocked step. More than half of WordPress.com blogs never published a post. Berkun argued that the problem was not simply a shortage of features. Many users got stuck before publishing, or received little encouragement after doing so. In another example, a designer moved the home page’s sign-up bar to the left and simplified the page; the change increased sign-ups by 10 percent. Small improvements can matter when they address a key user action.

Analysis

Product coherence is a systems property. Each feature can be defensible in isolation while the combined interface becomes harder to learn, much like a city that keeps adding roads without considering how people move through it. Teams need ways to examine complete user journeys, not just the code assigned to their own feature. At the same time, low activity does not automatically mean a design flaw: some people create blogs without a durable intention to write. Good product analysis separates user confusion from weak underlying demand before prescribing a redesign.

Make succession part of leadership, not an exit-day scramble.

A team should outlast its lead. After deciding to leave Automattic, Berkun discussed potential successors with Mullenweg and chose Mike Adams to take over the team. He spoke with Adams, informed Beau and the rest of the group, and used their Hawaii meet-up to make the handoff visible. Mullenweg joined a team conversation to signal support for the transition. Berkun then stepped back into an individual contributor role rather than leaving the team immediately.

Develop people before departure. Earlier, Berkun had involved Adams and Beau in broader decisions, hiring trials, and mentoring newer teammates. At meet-ups, he scheduled private conversations about what was working and what needed to change. These habits gave others experience and created channels for honest feedback. The handoff was not only a replacement decision; it was the result of gradually sharing responsibility.

Analysis

Succession is a practical test of whether authority has been distributed or merely delegated. If a group collapses when its leader leaves, the leader may have been centralizing decisions even while encouraging autonomy. Developing a successor requires more than naming someone capable; it means transferring context, relationships, and permission to act. There is also a risk in choosing the most technically impressive person by default. Leadership includes listening, prioritization, and conflict management, so organizations should offer prospective successors real opportunities to demonstrate those abilities before a vacancy makes the choice urgent.

Choose work whose purpose matters beyond the salary.

Purpose shaped the bargain. WordPress began with the ambition to make publishing available to anyone, and Automattic’s free service carried that mission into a business. Revenue came from paid upgrades, advertising, premium hosting, and partnerships, but leaders resisted turning every opportunity into an immediate sales push. Berkun found that employees valued the freedom, the product, and the company’s purpose alongside their pay.

Meaning has a cost. Berkun stayed longer than he planned, then left to return to the writing career he cared about most. His decision makes the book’s lesson personal: a good workplace can still be the wrong place for a particular ambition. The company’s humor, team dinners, and trips mattered because work was not treated as a joyless transaction. Yet remote independence suited some temperaments better than others, and people in places with few alternative employers could have less freedom to leave.

Analysis

Purpose can make effort feel worthwhile, but it should not become a tool for excusing poor conditions or underpayment. A mission is credible when it shapes decisions, including how revenue is earned and how workers are treated. The book’s account also reveals the importance of personal fit: one person’s freedom to work alone may feel isolating to another, and a meaningful project may still conflict with a long-term career goal. Purpose is therefore not a company slogan to impose. It is a relationship between the work, the worker, and the life each hopes to build.

Analysis

The book’s most useful insight is not that remote work is superior, but that work arrangements reveal what an organization trusts people to do. Automattic’s distributed model made output, written communication, and self-management unusually visible, while hiding much of the emotional context that an office supplies. Its tools mattered, but they worked because employees shared a product, a mission, and habits inherited from open-source collaboration. The account also resists a simplistic celebration of autonomy. Berkun’s early support-tour struggle, the stalled IntenseDebate work, and the difficulty of improving WordPress’s accumulated interface show that freedom does not automatically produce focus, quality, or coherence.

The strongest tension is between local speed and system-wide direction. Small releases let teams learn quickly, but years of independent feature decisions created interface clutter and left difficult maintenance work unattended. The organization could change course with little bureaucracy, yet ambitious, uncomfortable work still needed a leader to prioritize it, recruit help, and impose a useful deadline. This suggests that autonomy is not the absence of management. It changes management’s job from supervising presence to clarifying goals, connecting teams, and deciding where constraints are needed.

The evidence is vivid but bounded. This is a participant’s account of one company during a particular period, and Automattic selected for people willing to work this way. Its success cannot establish that the model suits every occupation, personality, or scale. Nor does high retention alone prove universal satisfaction, especially where remote employees may have few local alternatives. Still, the narrative offers a valuable diagnostic: instead of importing a fashionable method, ask which behaviors a workplace rewards, which problems it notices, and whether its structure helps skilled people finish work customers value. The answer is less a blueprint than a disciplined invitation to experiment.

Summary in 30 Seconds
Remote work depends on self-directed people, clear goals, and deliberate communication, not simply the removal of office rules. Direct customer support builds product knowledge, while small releases let real usage expose flaws and demand. Metrics can distort behavior when treated as targets, so numbers need human interpretation. Autonomy still needs structure for difficult projects, and rapid feature growth requires attention to product coherence. Leadership means building trust and preparing others to take responsibility.
Contains spoilers

Last updated:

Report Issue

Review Summary

3.81 out of 5
Average of 2k+ ratings from Goodreads and Amazon.

The Year Without Pants receives mostly positive reviews, with readers praising its insights into remote work and Automattic's unique culture. Many found it inspiring and thought-provoking, appreciating Berkun's candid observations and writing style. Some readers felt the book dragged in places or lacked depth in certain areas. Overall, reviewers valued the book's exploration of alternative work models and its potential impact on the future of work, though opinions varied on its broader applicability beyond Automattic's specific context.

Your rating:
4.32
153 ratings
Want to read the full book?

Glossary

P2

Internal project blog

A WordPress-based internal blog used at Automattic for team and company communication. Employees could post questions, plans, updates, and ideas, then discuss them in comments. Posts remained searchable and available to coworkers who were not online at the time, making P2 a persistent alternative to many email conversations.

Happiness Engineer

Customer support specialist

Automattic’s title for a customer support employee. Happiness Engineers responded to users’ problems with WordPress.com, helping translate a customer’s account of what seemed wrong into a diagnosis or explanation. New employees spent an initial training period doing support work, gaining direct experience with the product and its users.

continuous deployment

Frequent live software releases

A software practice in which completed changes are released to the live service frequently, rather than being held for a large scheduled launch. At WordPress.com, teams could update the product in small increments and observe how customers responded. The method depends on the ability to monitor releases and respond when defects appear.

The Cathedral and the Bazaar

Two contrasting development styles

A distinction associated with software writer Eric Raymond and used by Berkun to discuss how products are made. Cathedral-style work emphasizes advance planning and centralized design. Bazaar-style work grows through smaller contributions, experimentation, and revision. Berkun treats the contrast as a useful tension rather than an absolute choice, since many projects need both direction and iterative development.

T-shaped

Deep skill, broad capability

A description of people who have deep expertise in one area and useful working ability across several others. Berkun saw this kind of range among Automattic employees, who could often move beyond narrow job boundaries to help complete a project. The breadth supported self-sufficiency and collaboration, though it did not eliminate the need for specialist expertise.

Creative Abrasion

Productive creative disagreement

A term attributed in the book to designer Jerry Hirschberg for the useful tension that helps creative work improve. Too much friction, such as excessive approvals and meetings, obstructs progress. Too little leaves ideas unchallenged and can allow blind spots to persist. The concept asks leaders to create enough constructive resistance to sharpen work without smothering initiative.

e-mailopathy

Dysfunctional email overload

Berkun’s name for a pattern in which people overwhelmed by email skim messages carelessly and reply hastily. Those rushed messages create confusion and invite further waves of replies, deepening the overload. The term emphasizes that communication problems often arise from habits and workplace culture, not simply from the email software itself.

Matt bombing

Founder’s late discussion intervention

A phrase used at Automattic for moments when founder Matt Mullenweg entered a team’s online discussion late, suggested a different direction, and then was not immediately available to clarify. Because his authority made it unclear whether a comment was advice or an instruction, team leads sometimes had to follow up privately and explain the implications to the group.

FAQ

What's The Year Without Pants about?

  • Author's Experience: The book chronicles Scott Berkun's journey as a team lead at Automattic, the company behind WordPress.com, exploring its unique remote work culture.
  • Future of Work: It discusses the evolving nature of work, challenging traditional workplace structures with insights into remote work and autonomy.
  • Cultural Reflections: Berkun reflects on company culture, transparency, and balancing creativity with structure to achieve success.

Why should I read The Year Without Pants?

  • Unique Perspective: Offers an insider's view of a successful remote company, providing insights relevant to today's work environment.
  • Practical Lessons: Provides actionable advice on managing teams, fostering creativity, and navigating modern work complexities.
  • Humor and Honesty: Berkun's candid storytelling, infused with humor, makes complex topics accessible and engaging.

What are the key takeaways of The Year Without Pants?

  • Results Over Tradition: Emphasizes that results should trump outdated workplace traditions, which often hinder productivity.
  • Empowerment and Autonomy: Highlights the importance of hiring self-sufficient, passionate people who thrive in an autonomous environment.
  • Continuous Learning: Advocates for a culture of continuous learning and experimentation, encouraging risk-taking and learning from failures.

What are the best quotes from The Year Without Pants and what do they mean?

  • “Real Artists Ship”: Emphasizes the importance of completing and delivering work rather than getting lost in perfectionism.
  • “Trust is everything”: Highlights that trust is foundational for effective teamwork and collaboration.
  • “The future is here, it's just not evenly distributed”: Reflects the idea that some organizations embrace new work models while others remain traditional.

How does Scott Berkun describe the culture at Automattic?

  • Transparent and Collaborative: Values transparency and collaboration, fostering a sense of community and shared purpose.
  • Results-Driven: Prioritizes results over rigid processes, encouraging innovation and responsiveness.
  • Empowerment of Employees: Employees are empowered to make decisions and take ownership of their work, leading to higher job satisfaction.

What challenges did Scott Berkun face as a team lead at Automattic?

  • Navigating Remote Work: Adapting to leading a remote team, which presented challenges in communication and team cohesion.
  • Building Trust: Establishing trust with his team was crucial, focusing on transparency and open communication.
  • Managing Expectations: Balancing team expectations with company goals required careful prioritization and clear communication.

What methods does Scott Berkun suggest for effective team management?

  • Regular Check-Ins: Emphasizes the importance of regular team meetings and status updates to maintain alignment and accountability.
  • Encouraging Autonomy: Advocates for empowering team members to take ownership of their work and make independent decisions.
  • Fostering a Culture of Feedback: Encourages creating an environment where feedback is welcomed and valued for continuous improvement.

How does Scott Berkun address the concept of innovation in the workplace?

  • Embracing Experimentation: Believes innovation thrives in environments that encourage experimentation and risk-taking.
  • Balancing Structure and Flexibility: Emphasizes the need for flexibility while maintaining structure to achieve organizational goals.
  • Learning from Data: Highlights using data to inform decisions but cautions against over-reliance on metrics.

How does Scott Berkun view the future of work based on his experiences at Automattic?

  • Shift Towards Remote Work: Predicts remote work will grow in popularity, requiring cultural adaptation by companies.
  • Focus on Results and Autonomy: Envisions organizations prioritizing results and empowering employees to work autonomously.
  • Emphasis on Continuous Learning: Advocates for a culture of continuous learning and adaptation to thrive in the future.

What is the significance of the Highlander project in The Year Without Pants?

  • Unifying Comments System: Aimed to unify the commenting system across WordPress.com, improving user experience.
  • Team Collaboration: Exemplifies the collaborative spirit at Automattic, with various teams contributing to its success.
  • Iterative Development: Serves as a case study in iterative development, showcasing adaptability and continuous improvement.

How does Scott Berkun address the concept of remote work in The Year Without Pants?

  • Trust and Autonomy: Emphasizes that remote work relies heavily on trust and autonomy between employees and management.
  • Challenges of Communication: Discusses potential pitfalls, highlighting the need for effective tools and practices.
  • Work-Life Balance: Explores how remote work can enhance work-life balance, leading to increased job satisfaction.

What role does humor play in the workplace according to Scott Berkun?

  • Building Team Morale: Highlights humor as vital for fostering camaraderie and strengthening relationships.
  • Encouraging Open Communication: Suggests humor can break down barriers and facilitate open communication.
  • Enhancing Creativity: Argues that humor stimulates creativity, allowing teams to explore new ideas without fear of judgment.

About the Author

Scott Berkun is an accomplished author with four popular books to his name, covering topics such as project management, innovation, public speaking, and critical thinking. His writing has been featured in prominent publications like The Washington Post, New York Times, and Wired. Berkun's work extends beyond writing, as he is also a speaker whose insights have been shared on various media platforms, including CNBC, CNN, and National Public Radio. He maintains an active online presence through his blog and Twitter account, where he continues to share his ideas and engage with his audience. Berkun's diverse experience and ability to communicate complex ideas have established him as a respected voice in the fields of technology, business, and creativity.

Download PDF

To save this The Year Without Pants summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.43 MB     Pages: 21

Download EPUB

To read this The Year Without Pants 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: 27
Want to read the full book?
Follow
Listen1 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 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...