You probably have a pricing decision sitting in your pipeline right now.

A buyer wants more seats, a custom package, or a discount that feels just a little too generous. Sales says take it. Finance says be careful. Product says that segment could be strategic. You look at the contract value and still can't tell if the deal is smart or just flattering.

Most SaaS teams fall short in this aspect. We talk about growth, but we don't force ourselves to answer a harder question. What is the next sale worth?

That's the heart of marginal revenue economics. It sounds academic. It isn't. I use it as a filter for pricing, packaging, expansion, and churn signals. If you run SaaS, you need this mental model. Not because it's elegant, but because it stops you from confusing motion with profit.

That Pricing Question You Can't Answer

You're in the middle of a normal week. Pipeline is uneven. A rep pings you with a "big opportunity." The prospect wants a larger seat block, but only if you bend on price. On paper, it looks attractive. Bigger logo. More users. More revenue.

But the real question isn't whether the deal is bigger.

The fundamental question is whether this deal improves the business, or teaches the market to pay less for the same thing.

Most founders answer that with instinct. I've done it too. We look at the headline contract, compare it to this quarter's target, and tell ourselves we'll clean up the pricing later. Then later never comes. The discount becomes precedent. The custom plan becomes baggage. The cheap customer becomes the one asking for the most support.

That's not a sales problem. That's an economics problem.

Gut feel breaks fast

SaaS pricing gets messy because one change rarely affects only one customer. A lower-priced offer can reshape what future buyers expect. It can trigger downgrades. It can attract a segment that loves low price and hates commitment. If you're not careful, the "extra revenue" from a deal is lower than it looks.

That's why I don't think founders should treat pricing as branding with numbers attached. It's operating math.

If you're still choosing between flat pricing, usage pricing, seat pricing, or hybrid packages, this guide on SaaS pricing models is a useful companion. But whatever model you choose, the same question remains. What does the next sale add?

Your company doesn't get paid on theory. It gets paid on the economics of the next customer, the next seat, and the next concession.

The hidden logic behind sustainable growth

The companies that stay disciplined don't chase "more customers" in the abstract. They chase the right customers at the right price, with terms that preserve expansion and retention later.

That's why marginal revenue economics matters. It gives you a way to evaluate pricing moves without hand-waving. Not by asking, "Will revenue go up?" Revenue can go up for dumb reasons. Ask instead, "What does the next unit of demand contribute, and what does it cost us elsewhere?"

Founders who learn to think this way stop getting impressed by volume alone. Good. Volume is easy to buy. Profit is harder.

What is Marginal Revenue and Why Should a Founder Care

Marginal revenue is the extra cash you get from selling one more unit.

Not your list price. Not your average revenue per customer. Not the total value of the whole account. It's the change in total revenue caused by the next sale.

If you sell coffee, marginal revenue is the revenue from the next cup. If you sell SaaS, it's the revenue from the next seat, add-on, workspace, usage block, or plan upgrade.

Founders should care because pricing mistakes usually happen when we confuse those three things: total revenue, average revenue, and marginal revenue.

The cleanest example

A simple example from Wikipedia's marginal revenue entry uses a software-style sale. Selling 10 seats at $500 produces $5,000 in revenue. Selling 11 seats, with the last seat priced at $480, brings total revenue to $5,480. The change in revenue is $480 for one additional unit, so the marginal revenue of the 11th seat is $480.

That example matters because it shows something founders miss all the time. The new unit's marginal revenue can be lower than the average price across the earlier units.

Why that changes decisions

If you only look at the average, you fool yourself.

A founder sees "our seat price is $500" and assumes the next seat is worth $500 too. Not necessarily. The next seat might be worth less because you discounted it, bundled it, or needed extra concessions to close it.

Here's the practical split:

Total revenue tells you how much you've made overall.
Average revenue tells you what you made per unit on average.
Marginal revenue tells you whether the last sale was worth doing.

That's why marginal revenue economics is useful in SaaS. Our pricing isn't static. We negotiate. We segment. We run promos. We create annual discounts. We sell enterprise terms to some buyers and self-serve plans to others. In that world, the next unit often has different economics than the previous one.

The founder rule that actually matters

Microeconomics teaches a simple rule. Keep expanding output until marginal revenue equals marginal cost. Profit is highest at that point. If the next sale brings in more than it costs to serve, keep going. If it doesn't, stop forcing growth.

For SaaS operators, that means the next seat, customer, or package only helps if its incremental revenue beats its incremental cost.

If you're trying to connect this to valuation logic, customer lifetime value helps. But I would not start there. Start with marginal revenue. Lifetime value gets fuzzy fast when your pricing discipline is weak.

Practical rule: Never approve a pricing change because the total contract sounds good. Approve it because the incremental revenue is worth the incremental cost and the downstream pricing signal.

Why Your SaaS Isn't a Lemonade Stand

A lot of bad pricing advice comes from pretending SaaS works like a commodity market.

It doesn't.

In a perfectly competitive market, sellers don't control price. They're price takers. If everyone sells the same thing, the next unit sells at the market price, and marginal revenue stays tied to that price. That's the lemonade stand version of economics. Fine for textbooks. Useless for most software.

Your SaaS business probably has some pricing power. Not infinite power, but some. Brand, workflow fit, integrations, switching costs, niche positioning, product depth. Those give you room to charge differently across segments.

Why SaaS looks more like an imperfect market

Once you have pricing power, demand usually slopes downward. To win more demand, you often need to make the offer more attractive. Sometimes that means a lower price. Sometimes it means a cheaper tier, more generous limits, or a softer entry point.

The problem is simple. The more aggressively you chase extra demand, the less each additional unit may contribute.

The most useful treatment of this idea for operators is in this PandaDoc explanation of marginal revenue. The core point is that marginal revenue does not stay constant under downward-sloping demand. It falls as you push for more quantity, and in some cases it can even turn negative.

That isn't just classroom theory. It's exactly what happens when founders keep loosening pricing to achieve growth.

The consequence founders underestimate

If your market isn't perfectly competitive, marginal revenue is usually less than price.

That's the line to remember.

Why? Because the next sale often requires a concession. A discount. A cheaper plan. A broader package. Some signal to the market that your old price wasn't firm. Even if total revenue still rises, the additional revenue from the next unit can fall.

Here's how I think about it in SaaS:

Situation	What founders focus on	What they should focus on
Discount request	New contract value	Revenue added by the discounted unit
New cheaper tier	Top-of-funnel volume	Volume minus downgrades and lower willingness to pay
Expansion offer	Account size	Incremental revenue versus incremental support burden

The lemonade stand model says price is price. SaaS says every pricing move changes buyer behavior.

If your product has any real differentiation, you are not a price taker. Act like it.

That also means you need discipline. Pricing power is great until you waste it by training customers to wait for the cheaper option.

The Most Important Chart You Never Learned in School

Most founders never see the chart that would fix half their pricing mistakes.

It has two lines. A demand curve and a marginal revenue curve. The demand curve slopes down. The marginal revenue curve sits below it and falls faster.

That's the visual version of a brutal truth. The next unit of demand is often worth less than the headline price attached to it.

What the picture means in plain English

The demand curve tells you what buyers are willing to pay at different quantities. The marginal revenue curve tells you what the next unit adds to revenue as you move down that demand curve.

For a founder, that means this:

More volume can come with weaker economics
Lower prices can pull in buyers who are worse fits
Each additional customer can add less than the previous one

This is why I don't trust revenue projections that only model "more signups" or "more seats sold." If the next wave comes from a lower-intent segment or a weaker offer, the revenue quality changes too.

Where founders get hurt

The chart also shows a point where marginal revenue hits zero. Past that point, chasing more quantity reduces total revenue.

You don't need to build the graph every week to use the lesson. You just need to recognize the symptoms:

A cheaper plan brings signups, but paid expansion weakens
Discounts close deals, but renewal conversations get ugly
Entry pricing expands reach, but support load rises faster than account quality

If you want a financial lens that complements this, run rate can help you see how current revenue maps forward. Just don't confuse forward-looking revenue with healthy marginal revenue. Those are different questions.

The chart is not telling you to stop growing. It's telling you to stop assuming every extra unit of growth is equally valuable.

Using Marginal Revenue in SaaS Pricing Decisions

Marginal revenue economics ceases to be mere theory and begins to function as a playbook.

Every pricing decision in SaaS changes the economics of the next unit. A plan launch. A discount band. An annual prepay offer. A usage threshold. None of these should ship without asking what they do to marginal revenue.

When you're thinking about a cheaper tier

A cheaper tier is not automatically smart. It can open the funnel, yes. It can also become a downgrade path for people who were willing to pay more.

I push teams to answer two questions before launch:

Will this bring in customers we currently miss?
Will this give current customers a reason to pay us less?

If the second effect is stronger than the first, your new tier doesn't create growth. It redistributes revenue downward.

A good framing for this sits inside value-based pricing. Your low-end tier should map to a genuinely smaller value case, not just a lower willingness to pay from the same use case.

When sales asks for a discount

I like discounts less than most founders do.

Not because discounts are always bad. Sometimes they're rational. But too many teams approve them using only top-line thinking. "It's a big logo." "It's annual cash." "It gets us into the account."

Fine. Now answer the harder part.

Does the discounted unit still have strong incremental economics?
Does the deal create pricing precedent for similar buyers?
Does it attract a segment that is harder to retain later?

If you can't answer those, you don't have a pricing policy. You have a mood.

Expansion revenue is often your cleanest revenue

The best marginal revenue in SaaS often comes from expansion inside a healthy account.

An extra seat for a team that already trusts the product usually carries less sales friction than a net-new logo. The buyer already understands the workflow. Support patterns are known. The account has context. That's usually cleaner revenue than bending your whole pricing model to win a colder prospect.

That doesn't mean every expansion is good. It means founders should stop treating all revenue as interchangeable.

Usage pricing needs marginal revenue discipline

Usage-based pricing can be excellent because it aligns price with value. It can also get sloppy fast.

If you're charging on usage, you should know what the next unit of usage means for both revenue and delivery cost. If the next chunk of usage brings in little incremental revenue while support, infrastructure, or success load rises, the model is drifting.

I like a simple decision screen here:

Pricing move	Good sign	Bad sign
Cheaper tier	Brings a distinct segment	Cannibalizes higher tiers
Discounting	Wins a strategic fit without changing market expectations	Trains buyers to negotiate every renewal
Expansion pricing	Adds seats or usage in proven accounts	Creates complexity without real revenue lift
Usage model	Price grows with delivered value	Cost grows faster than revenue

My default recommendation

If you're unsure, be conservative.

Protect your willingness-to-pay signals. Add complexity only when you can explain exactly how it improves the economics of the next unit. Most SaaS pricing damage comes from adding exceptions faster than the company can understand them.

How Churn Becomes a Trust Diary for Pricing

Teams often treat churn as a dashboard number. That's too shallow.

A cancellation is a trust event. It tells you where your pricing, promise, onboarding, or product fit broke down. If you read churn that way, every cancellation becomes part of a trust diary you can use to sharpen pricing decisions.

"Too expensive" is not a complaint to ignore

When someone cancels and says price was the issue, don't roll your eyes. Don't toss it into a generic churn bucket.

They're telling you something precise. Maybe the value wasn't clear. Maybe onboarding didn't get them to outcome fast enough. Maybe your cheapest plan still overshoots what that segment needs. Maybe your packaging created friction long before your product did.

That's useful pricing intelligence.

If you want a broader set of practical retention ideas, Receiver's list of 10 actionable SaaS retention tactics is worth reading. The useful part isn't the idea count. It's the reminder that retention work usually starts with understanding why customers lose confidence.

Read churn like a pricing operator

I want founders to review churn feedback with three lenses:

Value gap. The product may be good, but the customer didn't reach the outcome they thought they were buying.
Segment mismatch. You may have sold into a customer type whose willingness to pay was weak from the start.
Packaging friction. Your plan structure may have forced people into the wrong price-value tradeoff.

Those are not support issues. They're pricing inputs.

If you're tracking cancellation rate, don't stop at the rate itself. Read the reasons. The number tells you how much churn happened. The trust diary tells you why your marginal revenue assumptions were wrong.

A cancellation reason is not just feedback. It's evidence about demand, willingness to pay, and where your offer stopped feeling fair.

The teams that learn faster don't merely count churn. They mine it for pricing truth.

Three Steps to Start Thinking in Marginal Revenue

You don't need a finance team or an economics degree to use this. You need better habits.

Step one, model the next deal instead of admiring it

The next time someone asks for a discount, don't start with total contract value. Start with the incremental revenue from the discounted unit and the likely cost of serving it.

Then ask one more question that founders skip. What market behavior does this discount encourage if it spreads? The immediate deal math matters. The precedent matters too.

Step two, treat new tiers as portfolio decisions

A new plan should never be judged only by what it might add. Judge it by what it could displace.

If you launch a cheaper package, write down the downgrade risk before launch. Force the team to state which customers should buy it, which customers should never buy it, and what behavior would prove cannibalization is happening.

For a useful companion read on this broader retention side of the equation, Suby's guide to understand and reduce SaaS churn is solid. It helps teams connect pricing choices to customer loss, which is exactly where marginal revenue thinking gets practical.

Step three, use churn feedback as pricing data

Read your cancellations every week. Not just the count. The words.

Look for repeated signs that customers felt overcharged, under-onboarded, mismatched to the plan, or disappointed in the speed to value. That's your trust diary. That's where your demand curve gets real.

My strong view is simple:

Don't guess at willingness to pay
Don't launch pricing changes without downgrade thinking
Don't treat churn as a metric-only problem

Do those three things and your pricing gets sharper fast. Not perfect. Sharper.

If you want a fast read on what your own trust diary is saying, try RetentionCheck. You can run your cancellation and feedback data through it for free, no signup, and quickly see whether pricing friction is driving churn.

Marginal Revenue Economics: A SaaS Founder's Guide