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 system customers accept, sales teams can defend, and growth can sustain.
by Ulrik Lehrskov-Schmidt 2023 278 pages
4.49
183 ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Design the offer around who buys, not what the software costs.

The product is the wrong unit. SaaS takes substantial investment to build but can cost very little to serve one more customer. That makes cost-plus pricing a poor guide: customers with different needs and budgets can value the same software very differently. The book’s railroad story makes the point. All passengers might reach California, but some will pay more for comfort, while others chiefly want an affordable journey. The commercial task is to create offers that let different customers pay different amounts for distinct value, rather than hunt for one ideal price for everyone.

Structure comes first. A €100 million insurtech company accepted a €1 million annual deal without negotiating, despite the customer facing a €30 million alternative build and €5 million in yearly maintenance. A later redesign enabled a price increase of about 60 percent without churn. The sequence matters: distinguish customer groups, shape the offer, choose how to charge, then set price points.

Analysis

This reframes pricing as product design and market segmentation, not spreadsheet optimization. In economics, price discrimination can expand access and capture value when customers have different willingness to pay. The practical challenge is designing distinctions that customers recognize as legitimate, such as different use cases or service levels, rather than arbitrary barriers. The railroad metaphor also has an ethical edge: removing safety from a low-cost option makes the lesson memorable, but it is not a model for software. A sound pricing structure differentiates optional value and service, not basic safety, reliability, or the minimum capability needed to do the job.

Find scale in customer value or distribution, not just cheap delivery.

Cheap delivery is not a moat. SaaS can serve each added account at low marginal cost, but competitors can often do the same. The book identifies three paths to stronger economics: reduce delivery costs, increase the product’s value as participation grows, or lower customer acquisition costs through distribution. The last two can help protect profits when competitors arrive. Growth may be steady, require a critical mass before it takes off, or level off as a market saturates. A marketplace, for instance, may be nearly useless with a handful of buyers and sellers, then become more useful as a local network fills in.

Trace the value path. The CUPID model examines customers, users, product, iteration, and distribution. Users may pay directly, become an asset sold to another customer, or help bring paying customers. Be My Eyes, for example, built a free community connecting visually impaired people and volunteers, then sold businesses a way to provide accessible customer support through that community. Repeated use should strengthen revenue, product value, or acquisition efficiency.

Analysis

The useful strategic move is to ask what each additional user changes, rather than treating user growth as inherently valuable. This connects to platform economics: a user can be a buyer, a contributor, or a channel, and the business model depends on which role creates value for whom. Yet network effects are not automatic, and a large user base does not guarantee defensible profits. The book’s distinction between linear growth, tipping points, and saturation helps prevent a common error: assuming a freemium or land-and-expand strategy will work simply because serving another user is cheap.

Package jobs customers already intend to solve, then ladder the next job.

A problem is not always demand. Customers may suffer from a problem without actively looking for a solution. A package has a stronger commercial footing when it addresses a job they already intend to get done. The book contrasts an app meant to ease students’ isolation, which students were not seeking to buy, with a window-cleaning service that could find customers already searching for cleaners. Demand was visible before the product arrived.

Separate and sequence offers. Fencing means dividing customers into clear groups that can receive different products or pricing. A lab-monitoring company, for example, created distinct offers for food laboratories and pharmaceutical labs, which had different expectations and willingness to pay. Within a group, a product ladder should start with the easiest job to sell, then offer the next job that becomes important once the first is solved. For logistics software, predictive maintenance was the initial need; operational efficiency could follow. Each step should make sense as a customer journey, not merely as a new set of features.

Analysis

Jobs-to-be-done thinking is powerful because it shifts product language from internal capabilities to the customer’s desired outcome. It also helps teams avoid mistaking technical sequence for buying sequence: a feature may be the first thing engineers build without being the first thing customers want to purchase. The distinction between a problem and a job is especially useful for products that require behavior change. Its limit is that latent demand can sometimes be cultivated, but that takes education, time, and resources. A new market may need more than a package that simply waits for existing demand to appear.

Choose a pricing metric customers want more of, trust, and you can measure.

The meter shapes behavior. A pricing metric is the unit that makes a customer’s purchase determine what they pay. It should be measurable and billable, connect to value, and feel fair to the buyer. In the book’s AI-platform example, customers wanted more models in production because those models represented progress toward business outcomes. They did not want more user licenses for their own sake, so initial deals repeatedly stopped at eight users. Charging for an input that customers try to minimize can slow adoption and expansion.

Test the value distribution. A metric can track value yet still be a poor way to charge if each unit varies wildly in worth. An insurer’s patients, for example, generated highly uneven repayment opportunities: many had little value, while a few were exceptionally valuable. That made a uniform fee feel unfair. Slack’s active-user measure is a cleaner fit than charging for every account created, because inactive accounts produce little of the product’s value. The book also distinguishes licenses, usage-based charges, and prepaid credits, which suit different usage patterns.

Analysis

A pricing metric is more than a billing convenience. It is an incentive embedded in the product: charging for users can discourage broad adoption, while charging for outputs can align the vendor with results but may make customers feel they are paying for work they helped create. This resembles mechanism design, where rules shape participants’ choices as well as divide rewards. The best metric therefore balances value alignment with perceived fairness and operational clarity. The book’s preference for dense metrics, where units have similar value, is sensible, though a less uniform metric can still work when tiers, caps, or carefully designed bundles address its variability.

Make each enterprise budget pay for the part it recognizes.

Enterprise buying has many owners. A software purchase may involve a business sponsor plus IT, compliance, procurement, legal, or HR. Each can block the deal, and each may control a different budget. The book calls this group the Wallet. Its advice is to match charges to the costs or value each budget owner understands. The primary buyer pays for the business outcome; supporting departments may pay for familiar items such as security, cloud infrastructure, reporting, or training.

Unbundle the bill intelligently. A European insurtech provider stored large volumes of claims documents for insurers. Those storage costs threatened to erode margins over time. Rather than loading everything onto the head of claims, the provider asked IT to co-pay for infrastructure. Prices rose about 50 percent with no churn, while the primary buyer’s budget took less of the burden. A useful starting exercise is to list what the service delivers, group it by likely budget owner, and check whether each charge has a credible reference price.

Analysis

Wallet structuring recognizes that organizational purchasing is a coalition problem, not a single buyer’s calculation. The approach can make costs legible to departments already responsible for similar spending, while giving the business sponsor a more manageable business case. That is a strength, but cost allocation must not become decorative line-item inflation. A charge tied to a cost proxy can be defensible even when it does not cause that cost, but the proxy should be stable, explainable, and reviewed as the service changes. Transparent allocation builds internal agreement; opaque allocation can turn a sensible pricing model into a procurement dispute.

Treat every price as relative, and investigate what anchors the buyer.

There is no universal price reference. Customers judge prices against something: a competitor, an existing solution, a budget, or their estimate of value. In a study described in the book, students whose social-security-number endings were high were willing to pay about $198 for six familiar items, compared with about $67 among those with low endings. The items’ relative rankings stayed similar, suggesting that an arbitrary starting point can shift the overall price level. The book’s Behavioural Pricing Matrix connects a buyer’s sophistication with competitive pressure to predict whether cost, a niche alternative, perceived value, or fairness will anchor the decision.

Learn from refusals. Validation should separate rejection of the job, package, pricing metric, price level, or explanation. In interviews, show the offer in stages: package, charging method, then price. If a customer objects to the metric, their reaction to its price cannot yet be interpreted cleanly. Ask why they said no, and look for the specific source of friction. A compliment without a purchase may be politeness, not evidence of demand.

Analysis

Anchoring research explains why a price can feel reasonable or outrageous without any change in the product itself. The practical implication is not to manipulate buyers with arbitrary anchors, but to discover the reference points already shaping their judgment. The book’s insistence on listening to refusals is similarly strong: conversion data reveals what happened, while a careful conversation can suggest what to change. A useful caution is that customer explanations are not perfect causal evidence. Buyers may rationalize decisions after the fact, so interviews are most valuable when combined with observed purchasing behavior and tested changes to the offer.

Replace improvised discounts with visible volume rules and controlled concessions.

Discounting needs a design. Large customers often expect lower unit prices as volume rises, but leaving every decision to individual salespeople can produce wildly inconsistent deals. The book recommends structural discounts: predetermined volume rates that make the expected price curve visible before negotiation. A schedule should extend beyond the largest likely customer, so a buyer can see where its purchase fits and what greater volume would unlock. A threshold discount applies the lower rate to all units after a volume level is reached; a waterfall discount applies it only to units above that level. The former can encourage adoption when customers control the metric.

Trade, do not simply concede. Sales discounts can reassure a buyer that the offer has reached its limit, but should be reluctant and exchanged for something useful, such as upfront payment or a longer commitment. The book prioritizes temporary discounts, then better terms, then added product, with a permanent price cut as a last resort. Central rules protect both margins and reps from pressure to close every deal at any price.

Analysis

A public discount curve reduces uncertainty for buyers and limits the scope for a negotiation to become an improvised contest of leverage. This is related to commitment devices: a company can make its own behavior more predictable by setting rules before a high-pressure deal arrives. Still, transparent discount schedules can create strategic gaming if customers split purchases or delay adoption to cross thresholds. They also need to reflect real cost or value differences, not reward scale reflexively. Discount governance works best when the rules are simple enough for sales teams to use and flexible enough to handle genuinely different customer economics.

Raise prices with product value, using contracts built for change.

Software changes after the sale. A contract that freezes price indefinitely can leave a company charging the same amount while its product improves, or force every new feature into a separate add-on. The book names these failure modes the monolith, where expanding the core product leads to undercharging and confused packaging, and the Hydra, where every new feature becomes another paid module, adding sales and service complexity. New functionality should join an existing package when it improves the same job, and form a new offer when it solves a distinct one.

Make updates manageable. The author recommends contracts that preserve an ongoing relationship while allowing product catalogs and prices to change, with customer purchases listed separately. Pricing cohorts track which customers have which commercial terms, making it easier to test new prices with new customers before moving existing ones. The book advises frequent review of prices as value changes. Any flexible contract should still state changes clearly and give customers meaningful notice and a practical option to leave.

Analysis

The central tension is real: a subscription product evolves, but customers need predictability and protection from arbitrary changes. The book’s distinction between a monolith and a Hydra gives teams a useful way to diagnose two opposite errors, under-monetizing a bundled product or fragmenting it into an unmanageable catalog. Dynamic contracts can support ongoing product development, but they also shift bargaining power toward the vendor. Clear notice, documented price logic, and a fair exit path are not cosmetic concessions; they are conditions for preserving trust when one party can change the terms of an ongoing relationship.

Analysis

The book’s most important contribution is a change in the object of pricing. Instead of treating price as a number attached to a product, it treats the commercial offer as an engineered interface between a customer’s job, budget, usage, and willingness to pay. That explains why packaging, metrics, contract terms, and discount rules are not administrative details. Together, they shape what customers adopt, what they perceive as fair, and which parts of a vendor’s value become revenue.

Its practical sequence is also a strength. First identify distinct customer groups and the jobs they need done. Then build packages, select metrics, map charges to budgets, and only afterward test price levels. This is a useful defense against false precision: optimizing a price for a badly structured offer produces a precise answer to the wrong question. The repeated attention to sales behavior and customer refusals further connects pricing design to organizational learning, not merely market research.

The argument is strongest when it explains mechanisms through cases, such as users who resist being charged for an input or uneven metric units that make a fee feel unfair. It is less conclusive when it generalizes from advisory experience to claims about what nearly all SaaS companies should do. A practice that works for large enterprise vendors may be excessive for a small self-serve product, and pricing outcomes depend on sector, regulation, competitive position, and customer trust. The proposed frameworks are best treated as diagnostic tools, not universal laws.

A second tension concerns fairness. The book shows how to capture value and defend prices, but a technically defensible model can still impose hidden complexity or shift risk onto buyers. Strong pricing design should therefore ask not only whether the seller can charge, but whether the customer can understand, forecast, and contest the charge. The enduring lesson is architectural: price design is a cross-functional capability that coordinates product, sales, finance, and customer expectations. Its quality is measured not by elegance on a slide, but by durable adoption, sustainable economics, and an exchange both sides can explain.

Summary in 30 Seconds
Price the customer’s job and perceived value, not the software’s marginal cost. Separate buyers by needs and budgets, package work they already intend to fund, and charge by a measurable unit customers want to increase. Align enterprise charges with the departments that recognize their value. Use clear volume tiers and trade concessions for commitment. Review prices as the product improves, with contracts that allow changes customers can understand and plan for.
Contains spoilers

Last updated:

Report Issue

Review Summary

4.49 out of 5
Average of 183 ratings from Goodreads and Amazon.

The Pricing Roadmap receives high praise from readers, with an average rating of 4.55/5. Reviewers commend its comprehensive coverage of B2B SaaS pricing, practical frameworks, and real-world examples. Many find it informative, insightful, and well-structured, appreciating its depth and applicability. Product managers and pricing professionals particularly value its actionable strategies and clear explanations. Some readers note its usefulness as a reference guide, while a few mention certain chapters being more engaging than others. Overall, it's widely recommended for anyone involved in or interested in SaaS pricing.

Your rating:
4.7
195 ratings
Want to read the full book?

Glossary

CUPID

User-to-revenue map

A framework for tracing how a SaaS business turns user activity into revenue and scale. It considers whether users pay directly, become part of a product sold to another customer, or help distribute the offer, and how repeated cycles can strengthen product value or reduce acquisition costs.

Fencing

Customer-group separation

The division of a market into distinct customer categories that can receive different products, services, or pricing. A useful fence should be easy to define, stable, understandable to customers, and worthwhile for the company. It differs from flexible marketing segmentation because it establishes durable commercial boundaries.

Laddering

Progression across offers

A product structure that guides a customer from an initial purchase toward further jobs, products, or levels of value. In a land-and-expand strategy, each step should fit the next need that arises after the previous job is solved. A ladder is not simply a set of feature tiers aimed at different customer types.

Jobs to Be Done

Customer outcome framework

A way to understand demand by identifying the outcome a customer is actively trying to achieve. A problem alone may not create a market if customers have no intention or plan to solve it. Packaging around a job makes an offer easier to connect to customer priorities, budgets, and existing demand.

Metric density

Consistency of unit value

The degree to which individual units of a pricing metric represent similar value to the customer. High density means one unit is much like another, making a common per-unit fee easier to accept. Low density means a few units may carry most of the value, while many others are worth little, creating fairness and adoption problems.

Expectation to pay

Perceived fairness of a charge

A customer’s sense that a particular item or activity is something they reasonably expect to pay for. It is shaped by familiar payment habits, visibility into the costs involved, and similarity to known pricing arrangements. A metric can track substantial value yet still face resistance if buyers do not consider it a fair basis for payment.

Wallet structuring

Pricing across buyer budgets

The design of charges to fit the different budgets and responsibilities represented in an enterprise buying group. The primary business sponsor pays for the central outcome, while supporting departments may pay for costs or services they recognize, such as infrastructure, compliance, or training. The method aims to align the price with the customer’s internal budget structure.

Behavioural Pricing Matrix

Price-reference framework

A framework for assessing how competitive pressure and customer sophistication affect the reference points buyers use to judge a price. Depending on these conditions, customers may focus on supplier costs, niche alternatives, perceived product value, or a fair division of value. It helps explain why the same price can be evaluated differently across markets.

Structural discounts

Predetermined volume reductions

Discounts built into a pricing schedule before individual negotiations, usually tied to purchase volume or another defined condition. They make price differences more predictable for customers and reduce the need for salespeople to invent discounts deal by deal. Threshold and waterfall schedules are two ways to apply them.

Pricing cohort

Customers on shared terms

A group of customers acquired under the same product and pricing arrangement. When a company changes its offer, tracking cohorts shows which customers have which terms and when they may move to new pricing. Cohorts support controlled testing and organized price updates while identifying customers who need separate treatment.

FAQ

1. What is "The Pricing Roadmap" by Ulrik Lehrskov-Schmidt about?

  • B2B SaaS Pricing Design: The book is a comprehensive guide to designing pricing models for B2B SaaS companies, focusing on creating structures that customers will love and that maximize business value.
  • Shift from Product to Customer: It argues that pricing should be about "pricing your customer" rather than just your product, using tools like product packaging and pricing models to achieve price discrimination.
  • Strategic, Not Just Tactical: The book positions pricing as a strategic design process, not just a financial or Excel-driven exercise, and provides a step-by-step framework for building effective pricing architectures.
  • Practical Frameworks and Examples: Lehrskov-Schmidt uses real-world SaaS examples, historical analogies (like trains), and actionable frameworks (like CUPID and the Behavioural Pricing Matrix) to illustrate his points.

2. Why should I read "The Pricing Roadmap" by Ulrik Lehrskov-Schmidt?

  • Solve Pricing Confusion: The book addresses the common confusion and paralysis SaaS founders and executives face when setting prices, offering clarity and actionable steps.
  • Unlock Growth and Profit: It shows how the right pricing structure can dramatically improve customer acquisition, retention, and profitability, often more than product or sales improvements alone.
  • Avoid Common Pitfalls: Lehrskov-Schmidt highlights and helps readers avoid frequent SaaS pricing mistakes, such as oversimplification, under-monetization, and misaligned discounting.
  • Applicable to All Stages: Whether you’re a startup or a scaling SaaS business, the frameworks and advice are relevant and adaptable to different company sizes and market positions.

3. What are the key takeaways from "The Pricing Roadmap" by Ulrik Lehrskov-Schmidt?

  • Price the Customer, Not the Product: The most important insight is to focus on pricing different customers according to their willingness to pay, using packaging and pricing models as tools.
  • Structure Over Price Point: The value is in the pricing structure (fencing, packaging, metrics), not just the specific price points you set.
  • Scale Drives Strategy: Understanding and designing for scale—cost, product, and distribution—is essential for sustainable SaaS profitability.
  • Iterative Validation: Pricing should be validated through customer interviews, surveys, and real market testing, always listening to the "quality of the no."
  • Dynamic, Not Static: Pricing and contracts should be dynamic, allowing for regular updates as your product and market evolve.

4. How does "The Pricing Roadmap" define and use the concept of "pricing your customer" in B2B SaaS?

  • Move Beyond Cost-Plus: Instead of setting prices based on costs or arbitrary markups, the book advocates for understanding what different customers are willing to pay.
  • Use Fencing and Packaging: Segment customers into distinct groups (fences) and create tailored packages (ladders) that match their specific jobs to be done and value perceptions.
  • Price Discrimination as a Tool: By differentiating offerings (like first, second, and third class on trains), you can capture more value from customers with higher willingness to pay.
  • Metrics and Structure: Select pricing metrics and structures that align with customer value, fairness, and operational viability, ensuring each customer pays appropriately.

5. What is the CUPID model in "The Pricing Roadmap" and how does it help SaaS companies design for scale?

  • CUPID Framework: CUPID stands for Customers, Users, Product, Iteration, and Distribution—a model for mapping how value flows from users to paying customers.
  • Three User Roles: Users can be customers (paying), the product (aggregated and sold to others), or distributors (helping acquire more customers).
  • Design for Scale: The model helps SaaS companies identify and leverage cost, product, and distribution scaling opportunities, such as network effects and viral loops.
  • Strategic Product Ecosystem: CUPID guides companies to build product ecosystems that maximize CLTV/CAC ratios and create sustainable competitive advantages.

6. How does "The Pricing Roadmap" approach product packaging and the "jobs to be done" theory for SaaS?

  • Jobs to Be Done Focus: Each product package should solve a specific job that customers are actively seeking to accomplish, not just offer a bundle of features.
  • Packaging Drives Pricing: By aligning packages with clear jobs, pricing becomes easier to justify and sell, and customers can immediately see the value.
  • Laddering and Fencing: Use ladders (tiers) to promote upselling and expansion, and fences to separate fundamentally different customer groups for tailored offerings.
  • Storytelling in Packaging: The product ladder should tell a compelling story that encourages customers to ascend, making expansion sales more natural.

7. What are the nine building blocks of SaaS pricing architecture according to "The Pricing Roadmap"?

  • Three Main Categories: The nine blocks are grouped into transactional nonrecurring fees, flat recurring fees, and metric-based recurring fees.
  • Transactional Nonrecurring Fees: Setup fees, ad-hoc one-offs, and exit fees—charged at onboarding, during, or at the end of the customer relationship.
  • Flat Recurring Fees: Flat base fees (core subscription), flat add-on fees (optional extras), and flat non-optional fees (e.g., compliance charges).
  • Metric-Based Fees: License-based (e.g., per user), consumption/usage-based (e.g., API calls), and credit-based (prepaid usage)—these are the core of SaaS monetization.

8. How does "The Pricing Roadmap" recommend selecting and evaluating pricing metrics for SaaS?

  • Four Key Criteria: Metrics should be operationally viable, aligned with customer value and demand, perceived as fair (expectation to pay), and have high metric density (uniform value per unit).
  • Value Chain Position: The best metrics are close to the customer’s value output, but must also be something customers expect to pay for.
  • Metric Density Matters: Avoid metrics where most units have little or no value (low density), as this leads to discounting and poor monetization.
  • Iterative Testing: Use internal scoring, customer feedback, and market validation to refine and select the best metrics for your pricing model.

9. What is "wallet structuring" in "The Pricing Roadmap" and how does it improve enterprise SaaS pricing?

  • Committee Buying Reality: Enterprise software is bought by a group (the "wallet"), each with their own budget and priorities.
  • Map Pricing to Budgets: Structure your pricing so that each stakeholder pays for the aspects of your solution they care about and expect to pay for (e.g., compliance, IT, training).
  • Cost-Plus and Value Pricing: Combine value-based pricing for the primary buyer with cost-plus elements for auxiliary stakeholders, improving alignment and reducing negotiation friction.
  • Maximize Co-Pay: By tapping multiple budgets, you can increase ACV, defend margins, and make your solution more attractive across the organization.

10. How does "The Pricing Roadmap" advise SaaS companies to set and validate price points?

  • Relative, Not Absolute: Prices are always evaluated relative to something else—competition, customer sophistication, or perceived value—not in isolation.
  • Behavioural Pricing Matrix: Use this framework to understand whether your market is cost-based, niche-based, perceived value, or fair value, and set prices accordingly.
  • Validation Methods: Combine internal expert judgment, price experimentation (with discounts), customer interviews/surveys, and statistical prediction models to find optimal price points.
  • Listen to the "Quality of the No": Focus on feedback from lost sales to identify whether issues are with demand, structure, or price, and iterate accordingly.

11. What is the recommended approach to discounts and raising prices in "The Pricing Roadmap"?

  • Discounts as Tools: Use structural discounts (predefined, volume-based) to manage large deals, and sales discounts (case-by-case) as communication tools, not as default negotiation levers.
  • Prioritize Discount Types: Favor time-limited and terms-based discounts over permanent ones, and always require something in return (quid pro quo).
  • Raising Prices Regularly: SaaS products should have dynamic pricing that is reviewed and increased at least annually, if not quarterly, to reflect added value.
  • Contract Frameworks: Use dynamic contracts that allow for price and product changes without renegotiation, and manage customer cohorts to handle price updates smoothly.

12. What are the most important quotes from "The Pricing Roadmap" by Ulrik Lehrskov-Schmidt and what do they mean?

  • "Don’t price your product. Price your customer." – The core philosophy: focus on customer segmentation and willingness to pay, not just product features or costs.
  • "The money is not in the price point. It’s in the price structure." – Emphasizes that how you structure pricing (tiers, metrics, fences) matters more than the specific numbers.
  • "Strategy is your plan to get and keep a competitive advantage." – Pricing is a strategic lever, not just a tactical one, and should align with your business’s path to sustainable profits.
  • "Customers want you to have good pricing." – Customers appreciate fair, transparent, and logical pricing models that make sense for their needs and budgets.
  • "If you and your team are debating $119 vs. $149, you’ve already lost." – Focusing on minor price tweaks misses the bigger opportunity: designing a structure that captures value across your customer base.

About the Author

Ulrik Lehrskov-Schmidt is the author of "The Pricing Roadmap," a highly-regarded book on B2B SaaS pricing. While specific biographical information is limited in the provided content, Lehrskov-Schmidt's expertise in pricing strategies is evident through his work. Readers praise his experience and the practical examples he provides in the book. His writing style is described as informative, entertaining, and devoid of unnecessary anecdotes or self-promotion. Lehrskov-Schmidt's approach to explaining complex pricing concepts has been compared to the engaging style of classic thriller authors. His book is considered a valuable resource for both newcomers and experienced professionals in the field of SaaS pricing.

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.38 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: 29
Want to read the full book?
Follow
Listen
Home
Swipe
Library
Get App
Try Full Access for 3 Days
Listen, bookmark, and more
Compare Features Free Pro
📖 Read Summaries
Read unlimited summaries. Free users get 3 per month
🎧 Listen to Summaries
Listen to unlimited summaries in 40 languages
—
❤️ Unlimited Bookmarks
Free users are limited to 4
—
📜 Unlimited History
Free users are limited to 4
—
📥 Unlimited Downloads
Free users are limited to 1
—
Risk-Free Timeline
Today: Get Instant Access
Listen to full summaries of 26,000+ books. That's 12,000+ hours of audio!
Day 2: Trial Reminder
We'll send you a notification that your trial is ending soon.
Day 3: Your subscription begins
You'll be charged on Nov 25,
cancel anytime before.
Consume 2.8× More Books
2.8× more books Listening Reading
Our users love us
1M+ readers
Trustpilot Rating
TrustPilot
4.6 Excellent
This site is a total game-changer. I've been flying through book summaries like never before. Highly, highly recommend.
— Dave G
Worth my money and time, and really well made. I've never seen this quality of summaries on other websites. Very helpful!
— Em
Highly recommended!! Fantastic service. Perfect for those that want a little more than a teaser but not all the intricate details of a full audio book.
— Greg M
Save 62%
Yearly
$119.88 $44.99/year/yr
$3.75/mo
Monthly
$9.99/mo
Start a 3-Day Free Trial
3 days free, then $44.99/year. Cancel anytime.
Unlock a world of fiction & nonfiction books
26,000+ books for the price of 2 books
Read any book in 10 minutes
Discover new books like Tinder
Request any book if it's not summarized
Read more books than anyone you know
#1 app for book lovers
Lifelike & immersive summaries
30-day money-back guarantee
Download summaries in EPUBs or PDFs
Cancel anytime in a few clicks

Why one summary?

Scanner
Find a barcode to scan

⭐
⭐
⭐
We have a special gift for you
Open
38% off
DISCOUNT FOR YOU
⭐
⭐
⭐
$79.99
$49.99/year
Only $4.16 per month
Continue
2 taps to start, super easy to cancel
Settings
General
Widget
Loading...