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 Pricing Roadmap

The Pricing Roadmap

How to Design B2B SaaS Pricing Models That Your Customers Will Love
Turn SaaS pricing into a growth engine without giving away value or alienating customers.
by Ulrik Lehrskov-Schmidt 2023 296 pages
5.00
1 ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Stop pricing the software; design different offers for different buyers

The product is not the purchase. SaaS is expensive to build and cheap to deliver, so production cost offers little guidance about what each customer should pay. A transcontinental railroad faced the same puzzle: one journey could serve affluent travelers who valued comfort and immigrants who mainly needed an affordable passage. Different classes of service captured those different priorities without changing the destination. The practical lesson is to design a structure that lets distinct buyers choose different value, not to hunt for one perfect number.

A €100 million insurtech company accepted a €1 million annual contract without negotiating. Its customer was considering a €30 million internal build, plus €5 million a year in upkeep, that could deliver far less. The vendor later raised prices about 60 percent without losing the customer. A single price point had hidden the opportunity; the offer structure had not captured the buyer’s alternatives.

Analysis

The railroad analogy makes price discrimination concrete: different prices can reflect different preferences rather than arbitrary favoritism. That distinction matters for both trust and strategy. A well-designed menu lets customers select the trade-off they actually want, much like airline seating or cloud-service tiers. But segmentation can become unfair or reputationally risky when its boundaries are concealed or unrelated to value. The strongest designs make differences legible, defensible, and tied to genuinely different needs.

Build pricing around the scale advantage your business can actually sustain

Scale is not one thing. A SaaS company can improve its economics through lower delivery costs, higher product value as participation grows, or cheaper customer acquisition as users attract more users. Each advantage faces different market dynamics: a marketplace may need critical mass before it becomes useful, while a tool that saves time can create value from its first customer. Low delivery costs alone are not a lasting moat, since a competitor can often offer similar software cheaply.

The book’s CUPID model examines how users become paying customers, contribute to a product sold to someone else, or help distribute the product, and what repeated use creates. Be My Eyes, for instance, connected visually impaired users with volunteers, then sold companies tools for serving those users. The aim is a repeatable path from use to revenue, with pricing and packaging supporting each step.

Analysis

This framework usefully asks where value travels, not merely where a company records revenue. It connects pricing to platform economics and customer acquisition: a free user base is an investment only when there is a credible route to paying demand. Yet network effects are often invoked too casually. Marketplaces can stall below critical mass, and customers can use several complementary products at once. Scale plans therefore need evidence about the shape of growth and the competitive structure, not just a large addressable market.

Package around buyers' active jobs, not your feature roadmap

Demand has a direction. A problem can be serious without becoming something people actively seek to solve. The book contrasts an app intended to reduce students’ isolation with window-cleaning services: the first addressed a real problem, but students were not looking to buy that solution; the second met an existing, plainly expressed demand. Packaging should name the outcome customers already want, not the technical stages used to produce it.

Separate fundamentally different buyers with clear, stable fences. A laboratory software company created distinct offers for food labs and pharmaceutical labs, whose willingness to pay and service expectations differed sharply; the pharma offer cost five times more. Within each group, a product ladder can guide customers from an urgent first purchase toward a next job that becomes relevant after the first is solved. Begin with the easiest job to sell, then make each upgrade a believable next step.

Analysis

Jobs-based packaging translates product language into the buyer’s own reason to act, which can reduce the interpretive burden on sales teams. It also creates cleaner feedback for product development: teams can ask whether the job is being solved rather than accumulate disconnected feature requests. The useful caveat is that demand is not always pre-existing and obvious. Education, regulation, or a new workflow can create purchasing intent. The distinction is best used to test whether a buyer has a credible path from need to action.

Charge on metrics customers want to grow, can measure, and find fair

A metric shapes behavior. A useful pricing metric must be measurable in practice, connected to customer demand, acceptable as a basis for payment, and consistent enough in value across its units. An AI platform charged banks for both users and models in production. Banks wanted more models, but wanted as few users as necessary, since users were an input cost rather than the desired outcome. Charging on the wrong metric encouraged customers to minimize adoption.

The book calls perceived fairness expectation to pay: customers are more comfortable with familiar charges, transparent costs, or fees resembling something they already buy. Metric density describes how evenly value is distributed across units. Charging per patient can be awkward if a few patients generate most of the value while most generate none. A better metric may align with a more uniform value unit, but it must still be operationally definable and accepted by buyers.

Analysis

Pricing metrics are incentive systems, not neutral bookkeeping devices. A charge on inputs can suppress experimentation, while a charge on outcomes can align vendor and customer interests. That resembles mechanism design, where the rules of exchange influence the behavior they are meant to measure. Still, moving the fee closer to the outcome is not automatically better: customers may dispute attribution or feel the vendor is charging for value they created themselves. The best metric balances alignment, controllability, measurement, and legitimacy.

Use layered pricing to protect value as customer size and needs diverge

Complexity can earn its keep. A single per-user price is easy to calculate but may overcharge small customers and invite enormous discounts from large ones. Pricing architecture can combine recurring metric charges with fixed fees, setup work, services, or usage charges. These components should correspond to something the customer chooses, values, or recognizes as a cost, rather than exist merely to make a quote look sophisticated.

For a large customer, a vendor might retain a core user price while separately charging for an enterprise feature package, enhanced support, storage, or heavy API use. This gives the customer a visible volume discount while protecting cost recovery and making the offer more relevant to a complex deployment. The central rule is not to add every possible fee. Add only the components that help distinguish customer needs, capture value, or cover meaningful delivery costs.

Analysis

Layered pricing resembles a nonlinear tariff: the buyer’s total bill reflects both what is valuable and what is expensive to provide. It can also make negotiations less arbitrary by distinguishing a negotiable value charge from predictable infrastructure costs. That structure is helpful only when customers can understand the logic. Excessive line items create audit work and suspicion, while a fee presented as cost recovery should not be far removed from the buyer’s reasonable cost reference. Clarity is part of the product.

Map your quote to the budgets that already pay for each cost

Enterprise buyers share the bill. A large software purchase is often approved by several stakeholders, each with a separate budget and veto power. The book calls this group the Wallet. The primary buyer pays for the business result; IT, compliance, or human resources may pay for infrastructure, reporting, security, or training that fits their own responsibilities.

A European insurtech provider stored enormous volumes of insurance-claim records. Charging the whole service to claims management meant its costs could eventually overwhelm customer margins. By asking insurers’ IT departments to co-pay for storage and related infrastructure, the company raised prices about 50 percent without losing customers. The method is to inventory what the service delivers, identify who owns each budget, and assign charges where there is both a recognizable cost or expectation to pay and a sensible reference price.

Analysis

Wallet structuring recognizes that organizational willingness to pay is distributed across departments, much like internal transfer pricing in large firms. It can make a purchase easier by matching costs to the teams that understand them, rather than forcing one champion to defend every line item. However, the organizational map is not permission to invoice every stakeholder. Each charge still needs a clear owner and rationale, and fragmented billing can create coordination costs or internal conflict. The buyer’s process is part of the pricing design.

Set prices against buyers' reference points, then test actual choices

Price is always relative. Buyers judge a quote against competition, their knowledge of the category, past spending, and what they believe the solution is worth. In an experiment described in the book, students’ willingness to pay for familiar goods varied by roughly two to three times depending on random numbers they had first written down. Yet their relative ranking of the goods stayed remarkably similar. The point is not to copy that anchor, but to recognize how little an isolated price means.

The Behavioural Pricing Matrix maps competitive pressure against customer sophistication. A knowledgeable buyer facing many substitutes may push toward cost-based pricing; a buyer in a crowded but unfamiliar category may compare niche alternatives; a unique offer to an uninformed buyer depends on perceived value; and a unique offer to a well-informed buyer can support a fair exchange of value. Use judgment and research to form a hypothesis, then test prices with real prospects and sales outcomes.

Analysis

The anchoring example captures a durable insight from behavioral economics: estimates are constructed from context, not read directly from an internal willingness-to-pay meter. That makes reference points central to pricing communication and negotiation. It also limits what surveys can establish. Stated willingness to pay is not the same as a purchase under budget constraints, procurement rules, and competing priorities. The matrix is most useful as a guide to the buyer’s likely comparison, not as a rigid classification of markets.

Diagnose each lost sale before changing the price

A no is evidence, not an answer. A prospect may reject the product’s capability, the customer category you placed them in, the package, the charging metric, the price level, or simply the way the offer was explained. Those causes require different fixes. If a customer dislikes a per-project fee because projects are hard to define, lowering that fee will not solve the structural problem.

The book recommends listening especially to people who do not buy. In interviews, show the package first, then the charging model, and only then the price, so feedback can be tied to the right decision. Three to five conversations can reveal where buyers lose confidence. In market tests, sales teams should record why deals are lost and review the patterns with product and pricing teams. Quantitative conversion data shows where performance changed; the quality of the no helps explain why.

Analysis

This is a strong application of diagnostic reasoning: separate the cause before prescribing the remedy. It also counters a familiar organizational bias in which sales teams treat every objection as a price problem and product teams interpret every request as a feature gap. A caveat is that customer explanations can be incomplete or socially softened. Qualitative feedback should be compared with observed behavior, such as adoption, conversion, and churn, rather than treated as a transparent report of motive.

Pre-design volume discounts so sales cannot bargain away the margin

Discounts need rules. Large customers expect lower unit prices at higher volumes, but leaving every adjustment to individual salespeople can produce inconsistent deals and permanent underpricing. Structural discounts are predetermined volume breaks; sales discounts are case-specific concessions. A published schedule can show that price declines as volume rises, while limiting the extra discretion required to close a deal.

The discount curve should extend beyond the largest customer currently in discussion, so that buyer can see where its volume fits and what a still-larger purchase would earn. Discounts can apply only to units above a threshold, or to all units once a threshold is reached. The latter can encourage customers to expand when they control the metric. For sales concessions, prefer temporary offers or better terms before permanent price cuts, and ask for something in return, such as annual payment.

Analysis

The argument reflects a principal-agent problem: an individual salesperson may value closing a deal more than the company values preserving its margin, especially when compensation rewards bookings. Transparent discount rules reduce that misalignment and give buyers a credible frame for negotiation. Yet central rules should not eliminate informed discretion. A schedule based on outdated assumptions can block strategically valuable business. Governance works best when exceptions are visible, reviewed, and used to improve the next version of the pricing structure.

Keep evolving products monetizable without trapping customers in rigid contracts

Product change demands pricing change. New functionality should join an existing package when it helps solve that package’s job; genuinely distinct jobs can justify new offers. Otherwise, companies risk a Hydra, where every feature becomes another add-on, or a monolith, where a growing product delivers more value without a matching increase in price. Both can raise costs or weaken sales clarity.

The book recommends recurring contracts that allow the product catalog and prices to change without renegotiating the entire relationship. A pricing cohort is a group of customers on a particular commercial version, making it possible to test new terms with new buyers, then roll them out to existing customers deliberately. Changes can be phased by customer group or revenue share, with limited grandfathering when appropriate. Clear notice and a credible option to leave help preserve trust as prices evolve.

Analysis

This is an argument for treating pricing as an operating capability, not a one-time launch decision. Cohorts make the learning loop practical: test, observe, and update without confusing every customer record. The contract recommendation is commercially powerful, but flexibility must not become unilateral surprise. In many buyer relationships, trust depends on advance notice, stable expectations, and meaningful exit rights. Transparent change policies can preserve the vendor’s ability to adapt while limiting the sense that the rules move only in its favor.

Analysis

The book’s central contribution is to reposition SaaS pricing from a numerical optimization exercise to a design problem. A price is not a free-standing signal of value. It is the output of choices about which buyer is served, what job is packaged, which behavior is measured, whose budget is charged, and how the relationship can evolve. This systems view explains why a seemingly precise debate over a unit price can be futile when the package or metric is wrong.

Its most useful discipline is sequencing. Define the market boundaries and customer jobs before choosing a metric; choose the metric before fine-tuning price points; validate the structure before interpreting a rejection as price resistance. This reduces category errors. A discount cannot repair absent demand, and a survey cannot make an ill-defined metric operationally sound. The book’s emphasis on customer refusals also turns commercial failure into a source of product information, though buyers’ explanations remain imperfect evidence and need comparison with actual behavior.

The framework also reveals pricing as governance. Discount authority, contract design, and customer cohorts determine whether an organization can learn consistently or accumulates exceptions that become commercial debt. Pricing therefore links strategy to organizational routines, not just to revenue models. Yet the same tools carry risks. Complex fees may distribute costs rationally while making bills harder to predict; dynamic contracts may preserve adaptability while weakening perceived commitment. In both cases, legibility and reciprocal safeguards matter.

The sharpest strategic question is not simply how much a customer might pay, but what pricing encourages both parties to do. A fee on inputs can suppress adoption; a charge on outcomes can create disputes over attribution; a free tier can build distribution or merely subsidize nonbuyers. Good pricing design must therefore align customer incentives, vendor economics, and operational reality. The book offers a practical vocabulary for making those trade-offs explicit, while leaving room for market testing to decide which design actually works.

Summary in 30 Seconds
SaaS pricing depends less on delivery cost than on the value different buyers receive and the alternatives they face. Build offers around customer jobs, and charge on measurable metrics that reward desired use. Layer fees only when they reflect distinct value or real costs, and align charges with the budgets that benefit. Test packages, metrics, and prices with prospects; diagnose lost sales before changing terms. Set discount rules in advance and evolve prices transparently.
Contains spoilers

Last updated:

Report Issue
Want to read the full book?

Glossary

CUPID

Maps users to revenue

An acronym for Customers, Users, Product, Iteration, and Distribution. The framework examines how people using a SaaS product become paying customers, contribute to something sold to another buyer, or help bring in buyers. It also asks what repeated use creates and whether pricing and product design support that path.

Fencing

Separates customer categories

The division of a market into distinct customer groups that can receive different product and pricing approaches. A useful fence is clearly defined, stable, understandable, and valuable enough to justify the additional complexity. Examples include separating food laboratories from pharmaceutical laboratories or business customers from consumers.

Laddering

Structures customer progression

A product structure that guides customers from an initial package toward further purchases as their needs develop. Unlike a set of unrelated tiers, a ladder gives each step a reason to follow the previous one. Each package should address a customer job, and the next step should solve a need that becomes more pressing after the first.

Jobs to Be Done

Defines the outcome buyers seek

A way of understanding products through the progress customers are actively trying to make, rather than through the product’s features or the mere existence of a problem. A problem may matter without generating purchase intent. Packaging is stronger when it names a sought outcome for which customers already show a path to action.

Point of first demand

Identifies the easiest first sale

The job or use case with the clearest and most accessible existing demand. In a product ladder, it is often the best place to begin because customers already know they want the outcome. Choosing this entry point can make initial sales easier and create a foundation for later packages.

Wallet structuring

Aligns charges with budgets

The design of pricing so that charges align with the separate budgets and responsibilities of stakeholders involved in an organizational purchase. The primary buyer usually pays for the core business value, while other departments may pay for recognized costs or services such as infrastructure, compliance, or training.

Expectation to pay

Signals whether a fee feels fair

A customer’s sense that a particular item is a legitimate thing to be charged for. It can depend on familiar payment habits, visible costs, or similarity to an established purchase. A feature may be valuable yet still provoke resistance if customers do not expect to pay for it separately.

Metric density

Measures value consistency per unit

The degree to which the value represented by a pricing metric is similar across its individual units. A metric has low density when a small number of units account for most of its value, making the average charge feel excessive for many cases. More consistent unit value can make pricing easier to accept and monetize.

Behavioural Pricing Matrix

Maps price reference points

A framework that combines competitive pressure with customer sophistication to predict how buyers are likely to judge a price. Depending on those conditions, buyers may focus on costs, niche alternatives, perceived product value, or a fair sharing of value. It is a guide to likely reference points, not a formula for an exact price.

Structural discounts

Predetermined volume reductions

Discounts defined in advance, often according to purchase volume, rather than improvised for each customer by a salesperson. A visible schedule lets buyers understand how unit prices change as they buy more. It can capture expected volume differences while reducing inconsistent concessions and excessive negotiation.

Hydra

Add-on sprawl

A product that becomes increasingly complicated because each new feature is sold as a separate module or add-on, whether or not the distinction suits the customer’s job. This can increase acquisition, delivery, and development costs while multiplying product configurations and the burden of supporting them.

Monolith

One expanding, underpriced package

A product that continually accumulates functionality inside one broad offering without adequate packaging or price changes. Customers may feel they are paying for features they do not need, while sales becomes harder because the offer is difficult to explain in terms of specific jobs. The vendor can end up delivering increasing value for stale prices.

Pricing cohort

Tracks a pricing version

A group of customers who began with the same product and pricing arrangement. Cohorts let a company test new prices with new buyers, record which customers use which commercial terms, and decide when to move existing customers to updated pricing. They provide a practical structure for managing changes over time.

FAQ

What's "The Pricing Roadmap" about?

  • Focus on B2B SaaS Pricing: "The Pricing Roadmap" by Ulrik Lehrskov-Schmidt is a comprehensive guide on designing effective pricing models for B2B SaaS companies.
  • Customer-Centric Approach: The book emphasizes pricing the customer rather than the product, advocating for a structure that aligns with customer value and willingness to pay.
  • Strategic Frameworks: It provides frameworks and methodologies to create pricing models that are both profitable and appealing to customers.
  • Practical Insights: The book includes real-world examples and case studies to illustrate successful pricing strategies.

Why should I read "The Pricing Roadmap"?

  • Improve Pricing Strategy: It offers actionable insights to enhance your pricing strategy, crucial for maximizing revenue in B2B SaaS.
  • Understand Customer Value: The book helps you understand how to align pricing with the value perceived by customers, leading to better customer satisfaction and retention.
  • Avoid Common Pitfalls: It highlights common mistakes in pricing and provides solutions to avoid them, such as avoiding the creation of hydra products or monoliths.
  • Comprehensive Guide: With detailed chapters on various aspects of pricing, it serves as a complete resource for anyone involved in pricing decisions.

What are the key takeaways of "The Pricing Roadmap"?

  • Price the Customer: Focus on pricing the customer, not the product, to better capture value and differentiate pricing across customer segments.
  • Use of Complexity: Contrary to popular belief, complexity in pricing models can be beneficial for price discrimination and aligning with customer value.
  • Dynamic Contracts: Implement dynamic contracts that allow for price adjustments without renegotiation, ensuring pricing keeps pace with product value.
  • Iterative Process: Pricing should be an ongoing process, with regular reviews and adjustments based on customer feedback and market conditions.

What are the best quotes from "The Pricing Roadmap" and what do they mean?

  • "Pricing is more a 'design' job than an 'Excel' job." This highlights the importance of creativity and strategic thinking in pricing, rather than relying solely on data and spreadsheets.
  • "Price your customer, not your product." This quote encapsulates the book's central philosophy of aligning pricing with customer value and willingness to pay.
  • "The money is in the pricing structure—not the price point." It emphasizes the importance of having a well-thought-out pricing structure that can adapt to different customer needs and market conditions.
  • "With great profits come great competition." This underscores the need for a sustainable competitive advantage in pricing to maintain profitability.

How does "The Pricing Roadmap" suggest pricing the customer?

  • Fencing and Laddering: Use fencing to separate customers into distinct categories and laddering to structure pricing within those categories.
  • Jobs to Be Done: Align pricing with the specific jobs customers are trying to accomplish, ensuring each package addresses a clear customer need.
  • Wallet Structuring: Map pricing onto the organizational structure of the customer, ensuring each stakeholder's budget is considered.
  • Dynamic Adjustments: Regularly adjust pricing based on customer feedback and changes in product value.

What is the CUPID model in "The Pricing Roadmap"?

  • Acronym Explanation: CUPID stands for Customers, Users, Product, Iteration, and Distribution, a framework for designing SaaS product ecosystems.
  • Value Path Focus: It emphasizes understanding the value path from user to customer, ensuring that each user interaction contributes to revenue.
  • User Roles: Users can be customers, products, or distributors, each playing a role in the value creation and monetization process.
  • Iterative Design: The model supports iterative design and scaling, allowing for continuous improvement and adaptation to market changes.

How does "The Pricing Roadmap" address scale economics?

  • Three Types of Scale: The book identifies cost, product, and distribution as the three types of scale that can drive profitability.
  • Scale Dynamics: It discusses critical mass, diminishing returns, and linear scaling as dynamics that affect how scale is achieved.
  • CLTV/CAC Ratio: Emphasizes the importance of the customer lifetime value to customer acquisition cost ratio in measuring profitability.
  • Strategic Alignment: Aligns pricing strategy with business strategy to achieve sustainable high-profit margins through scale.

What are the nine building blocks of SaaS pricing architecture in "The Pricing Roadmap"?

  • Transactional Nonrecurring Fees: Includes setup fees, ad-hoc one-offs, and exit fees, which are not perpetual or recurring.
  • Flat Fees: Comprises flat base, flat add-on, and flat non-optional fees, which do not fluctuate based on metrics.
  • Metric-Based Fees: Consists of metric-based license fees, consumption and usage-based metrics, and credit-based metrics, which are recurring and tied to specific metrics.
  • Complexity as a Tool: The book advocates using these building blocks to create a pricing model that can effectively price discriminate and align with customer value.

How does "The Pricing Roadmap" suggest handling discounts?

  • Structural Discounts: Predetermined discounts that are openly shown to customers, helping to manage expectations and negotiations.
  • Sales Discounts: Used as a communication tool to reassure customers they are getting the best deal, offered reluctantly and strategically.
  • Post-Sales Discounts: Includes grandfathering and proactive/reactive price reductions to prevent churn and maintain customer relationships.
  • Discount Management: Centralize discount decisions to ensure they align with overall pricing strategy and organizational goals.

What is the Behavioural Pricing Matrix in "The Pricing Roadmap"?

  • Framework Purpose: It maps the influence of competitive pricing pressure and customer sophistication on how prices are evaluated.
  • Four Pricing Scenarios: Includes cost-based, niche-based, perceived-value, and fair-value pricing, each determined by market conditions and customer knowledge.
  • Customer Sophistication: Considers factors like frequency, insight, data, and priority to assess information asymmetry between the company and customer.
  • Strategic Application: Helps determine the appropriate pricing strategy based on the competitive landscape and customer understanding.

How does "The Pricing Roadmap" recommend raising prices?

  • Regular Increases: Suggests raising prices at least annually, if not quarterly, to keep pace with product value increases.
  • Dynamic Contracts: Advocates for contracts that allow for price adjustments without renegotiation, ensuring flexibility and alignment with product development.
  • Avoiding Pitfalls: Warns against becoming a hydra or monolith by maintaining packaging integrity and focusing on customer jobs to be done.
  • Communication Strategy: Recommends clear and simple communication of price changes, with options for staged rollbacks and time-limited grandfathering to manage customer reactions.

What is the role of validation in "The Pricing Roadmap"?

  • Four Validation Methods: Includes conceptual sense, customer interviews, surveys, and market testing to ensure pricing models are effective.
  • Customer Feedback: Emphasizes the importance of listening to customers, especially those who don't buy, to refine pricing strategies.
  • Quality of the No: Encourages understanding the reasons behind customer rejections to identify issues with demand, structure, or communication.
  • Iterative Improvement: Validation is part of an ongoing process to continuously improve pricing models and align them with customer needs and market conditions.

Download PDF

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

Download EPUB

To read this The Pricing Roadmap 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.34 MB     Pages: 28
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 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...