Interactive ToolDecision Tree6 min

Should You Change Your Pricing Model?

A seven-criterion decision tree on pricing model changes — usage-based, subscription, perpetual, enterprise. Output: a reasoned recommendation plus the two risks most worth pressure-testing.

Who it’s for: Founders, CFOs, and CMOs debating a pricing model shift — usage-based, seat-based, tier-based, or hybrid — with a live book of business at stake.

Question 1 of 7
01

What does your current pricing model look like?

How to read your result

Read it honestly, not charitably.

Three outcomes, not a binary. Change means the preconditions are in place and the cost of waiting exceeds the cost of moving. Not yet is the most common honest answer — the case exists but the ground is unready. Stay and sharpen means the perceived pricing problem is actually a packaging problem, and changing the meter will not fix it.

If your output is “change” with a narrow margin, treat it as “not yet.” A pricing model shift with the team 60% ready goes badly. Pricing model shifts with the team 90% ready go well.

What to do next

Three moves you can make this week.

  1. Talk to five current customers. Tell them you’re thinking about a change. Their reaction will tell you more than this wizard can.
  2. Model the revenue dip honestly. Build the quarterly revenue view under two scenarios — current model vs. new model. If the five-quarter crossover point is more than 18 months out, the thesis is weaker than it felt.
  3. Write the three-paragraph customer email before you decide. If you cannot write a calm, honest note explaining the change to a skeptical long-term customer, the change is not ready.
The thinking behind it

Why these questions, in this order.

Seven questions because pricing decisions fail at any of seven points: the current model’s structural fit, the signal you can actually meter, customer complaint patterns, competitive movement, your revenue risk tolerance, base readiness, and GTM readiness. A “go” decision that fails on two of those seven usually blows up in execution.

The weights are asymmetric on purpose. A single “blindsided customer base” or “team not ready” answer alone should be enough to move the recommendation to not yet — even if every other signal screams change. The cost of a botched pricing transition is higher than the cost of a one-quarter delay.