Chapter 11: Deep Dive - Pricing Architectures

Economic Value to Customer (EVC)

In Chapter 4, we established that value-based pricing is superior to cost-plus or competitor-based pricing. But how do you actually quantify the "value" you deliver? The Economic Value to Customer (EVC) framework provides a rigorous methodology for calculating exactly what your product is worth to a specific customer segment.

EVC starts with a simple premise: the maximum price a rational buyer will pay for your product is equal to the total economic benefit they receive from it, minus the costs and risks of switching. The formula looks like this:

Calculating EVC: A Worked Example

Consider a project management SaaS tool targeting marketing agencies. The agency's current solution is a combination of spreadsheets, email, and a basic project tracker costing $500 per month for the team.

This is a dramatically different number than what most founders would arrive at by looking at competitor pricing or adding a margin to their hosting costs. The EVC framework reveals what the product is actually worth, not what similar-looking products happen to charge. The agency in this example would happily pay $1,946 per month because they are still capturing $2,687 per month in net economic value.

Designing Pricing Tiers That Maximize Revenue

Most SaaS companies offer three pricing tiers. This is not arbitrary -- it is grounded in behavioral economics. Three tiers exploit a cognitive bias known as "extremeness aversion," where people tend to avoid the most expensive and least expensive options and gravitate toward the middle. Your job is to design the tiers so that the middle tier is the one you want most customers to choose.

The Value Metric: What You Charge Per

The "value metric" is the unit you charge per -- per user, per transaction, per GB of storage, per API call. Choosing the right value metric is as important as choosing the right price. The ideal value metric has three properties:

• It scales with the value the customer receives. As the customer gets more value, they naturally consume more of the metric and pay more. Per-seat pricing works for collaboration tools because more seats means more people getting value. Per-transaction pricing works for payment processors because more transactions means more revenue for the customer.
• It is easy to understand. Customers should intuitively grasp what they are paying for. "Per user per month" is simple. "Per API call with a 0.003 cent surcharge above the 95th percentile of monthly utilization" is not.
• It allows customers to start small and grow. The value metric should not create a cliff where a small increase in usage triggers a massive price jump. The best value metrics scale gradually, allowing customers to grow into higher tiers naturally.

Usage-Based Pricing: The Rising Trend

Usage-based pricing (also called consumption-based or pay-as-you-go pricing) has surged in popularity, driven by companies like Snowflake, Twilio, and AWS. In this model, customers pay based on how much they actually use the product, rather than a fixed monthly fee.

The appeal is clear: customers only pay for what they use, which lowers the barrier to adoption. For the company, usage-based pricing creates natural expansion revenue -- as customers succeed and grow, their usage (and your revenue) grows with them. Snowflake's entire business model is built on this principle: the more data a customer processes, the more they pay, and since data volumes tend to grow over time, revenue per customer expands organically.

However, usage-based pricing introduces revenue unpredictability. Your monthly revenue depends on customer behavior, which can fluctuate. Many companies mitigate this by combining a base subscription fee with usage-based overage charges, creating a hybrid model that provides revenue stability while preserving the alignment benefits of usage-based pricing.

Expansion Revenue and Negative Churn

One of the most powerful concepts in SaaS pricing is "negative churn" -- the state where revenue from existing customers (through upsells, cross-sells, and usage expansion) exceeds the revenue lost from customers who cancel. When you achieve negative churn, your revenue grows even if you stop acquiring new customers entirely.

Designing for expansion revenue requires deliberate pricing architecture. Your tiers, value metrics, and packaging must create natural upgrade paths. The customer should encounter a moment of friction -- a usage limit, a feature gate, or a team size constraint -- at precisely the point where they have received enough value to justify the higher price. Too early, and they churn. Too late, and you have been giving away value for free.

When and How to Raise Prices

Most startups are underpriced. This is partially because founders undervalue their own product and partially because they fear customer backlash. But the data is clear: price increases, when handled thoughtfully, rarely cause significant churn and almost always increase revenue.

Signs You Are Underpriced

• Your LTV:CAC ratio is above 5:1 (you can afford to acquire customers much more expensively than you currently do, which means you could also charge more)
• Customers rarely push back on price during sales conversations
• Your close rate is above 40% (if almost everyone says yes, your price is too low)
• Customers frequently say your product is "a bargain" or "great value"
• Competitors with inferior products charge significantly more

How to Raise Prices Without Losing Customers

Freemium vs. Free Trial: The Strategic Choice

The question of whether to offer a free tier (freemium) or a time-limited free trial is one of the most consequential pricing decisions you will make. Each model has distinct implications for your growth engine, unit economics, and product strategy.

Pricing Experiments: How to Test Without Destroying Trust

Pricing is one of the few areas where A/B testing can backfire. If customers discover you are charging different people different prices for the same product, the trust damage can be severe. Here are approaches that allow you to test pricing without this risk:

• Test across time, not across users. Charge one price this month and a different price next month. Compare conversion rates and revenue per customer across the two periods.
• Test across geographies. Charge different prices in different markets. Geographic pricing differences are expected and accepted.
• Test packaging, not price. Instead of changing the dollar amount, change what is included at each tier. Add or remove features from the mid-tier and see how it affects upgrade rates.
• Use "willingness to pay" surveys. The Van Westendorp method (covered in Chapter 4) lets you estimate optimal pricing without actually charging different prices to different customers.