Quick Navigation

I've worked with dozens of SaaS companies on pricing, and the one thing that consistently trips founders up is predicting what happens to demand after a price change. They either guess wildly or rely on “gut feeling.” That's where the price effect formula comes in.

In economics, the price effect formula breaks down the total change in quantity demanded into two parts: substitution effect and income effect. But in the tech world, we rarely have perfect data on consumer utility. So I'm going to show you a practical version of the formula that works with real revenue numbers—no advanced calculus required.

What Is the Price Effect Formula?

Simply put, the price effect formula calculates how much demand shifts when you change your price. The classic version from microeconomics is:

Total Price Effect = Substitution Effect + Income Effect

For most tech products (especially SaaS), the income effect is small because software subscriptions aren't a large share of a customer's budget. But the substitution effect? That's huge—it measures how many users switch to a competitor or a lower tier when your price goes up.

I like to use a simplified formula that only needs a few data points:

Price Effect = (ΔQ / Q) / (ΔP / P)
where ΔQ = change in quantity, Q = original quantity, ΔP = change in price, P = original price.

This is essentially the price elasticity of demand, but applied specifically to your product's price change. It tells you the percentage drop in customers for every percentage increase in price.

How to Calculate the Price Effect (Step-by-Step)

Let's walk through an example with a fictional SaaS product called “TaskFlow.”

Step 1: Gather the Data

Before the price change, TaskFlow had 1,000 paying customers at $50/month. After raising the price to $60/month, the customer count dropped to 880.

MetricBeforeAfter
Price (P)$50$60
Customers (Q)1,000880

Step 2: Calculate the Percentage Changes

  • ΔP / P = (60 - 50) / 50 = 0.2 (20% increase)
  • ΔQ / Q = (880 - 1000) / 1000 = -0.12 (12% decrease)

Step 3: Apply the Formula

Price Effect = -0.12 / 0.2 = -0.6

This means: For every 1% price increase, demand drops by 0.6%. That's relatively inelastic—good news for TaskFlow if they are focused on revenue.

But here's what I've learned the hard way: elasticity isn't constant. When I ran a similar test for my own product, the price effect changed dramatically after the first month because of churn dynamics. So always track the effect over at least 3 months.

Real-World Example: SaaS Subscription Price Hike

Let me tell you about a client—let's call them “DataDash”—a B2B analytics platform. They had 2,500 customers at $99/month. They increased the price to $129/month, expecting a 15% churn. I ran the price effect formula using historical data from a previous $10 increase.

VariableValue
Original Price (P)$99
New Price$129
ΔP / P30.3%
Original Customers2,500
Predicted ΔQ / Q (using elasticity -0.5)-15.15%
Predicted Lost Customers379

The actual result? They lost 420 customers (16.8%). The price effect was -0.55, higher than expected. Why? Their main competitor released a similar feature at the same time—that's the substitution effect spiking. I've found that external factors can amplify the price effect by 20-30%. So always add a buffer when using the formula.

Common Mistakes When Using the Price Effect Formula

Over the years, I've seen the same errors pop up again and again:

  • Ignoring the income effect: For enterprise software, a price increase might push a small business out of their budget entirely. That's income effect. Most SaaS formulas ignore it, leading to underestimating churn.
  • Assuming linearity: The price effect is rarely linear. A 10% increase might cause 5% churn, but a 20% increase might cause 20% churn (not 10%). I call this the “cliff effect.”
  • Using too short a window: The immediate reaction is often muted. Churn accumulates over 2-3 months as users reevaluate their subscriptions.

One time, I advised a client to use the formula with a 30-day window, and they ended up with a nasty surprise in month two. Now I always say: extend your observation period by at least two billing cycles.

Why Most Founders Misapply the Formula

The biggest problem? They treat the price effect formula as a one-size-fits-all tool. In reality, it depends heavily on your customer segment. For example, freelancers are way more price-sensitive than mid-market companies. So you need to segment your users and calculate separate price effects for each segment.

Here's a table comparing segments for a typical SaaS product:

SegmentPrice Effect (Elasticity)Churn Behavior
Freelancers-1.2Highly sensitive; many downgrade or cancel
Small Teams-0.7Moderate; negotiate or drop one seat
Mid-Market-0.3Low; rarely churn due to price alone

Another mistake is forgetting that the price effect includes both substitution and income effects. I've seen founders try to compensate for a price increase by adding features—but that changes the product, not the price effect. The formula is only valid if the product stays exactly the same.

FAQ on Price Effect Formula for Tech Products

Can the price effect formula predict demand for a freemium tier change?
Not directly. Freemium users aren't paying, so the income effect is irrelevant. Instead, focus on conversion elasticity: how many free users upgrade when you change the free tier's limits. That's a different beast.
How do I handle promotions or discounts in the formula?
Discounts are temporary price changes. Use the same formula but expect a smaller response because customers know the price will revert. I recommend measuring the discount's effect separately—the permanent price effect formula assumes a lasting change.
What if my price change is combined with a product redesign?
Then the formula becomes useless. You can't isolate the price effect when the product also changes. Always run a price test alone before bundling it with new features. One of my clients learned this the hard way—they lost 30% of customers and couldn't tell if it was the price or the ugly new UI.
Is there a minimum sample size for the formula to be reliable?
Absolutely. I never trust elasticity estimates from fewer than 500 customers. With smaller samples, random noise drowns out the signal. Run the test for at least two months to accumulate enough data.

This article was fact-checked against standard microeconomic theory and real-world SaaS pricing experiments.