Hypothesis-Led Pricing: The 3-Step Framework That Finds the Leak

Your pricing strategy is either compounding your annual recurring revenue (ARR) growth or quietly eroding it. Most SaaS teams do not know which one is happening.

The reason is simple: pricing decisions get made at the deal level, by reps under quota pressure, without a shared hypothesis about what value actually justifies the number on the page. You end up with a pricing strategy in name only.

The Financial Exposure

Pull your last 90 days of closed-won deals. Sort by discount percentage. The range is probably wider than you expect.

In a typical B2B SaaS business at $25M to $75M ARR, the spread between the highest and lowest discount on identical product configurations runs 15 to 35 percentage points. That gap is not a sales execution problem. It is a pricing architecture problem. Every point of unnecessary discount flows directly through to earnings before interest, taxes, depreciation and amortization (EBITDA).

A company at $50M ARR with a 19% average discount rate that tightens to 8% through structural governance adds roughly $5.5M in realized revenue. Same product. Same quota. No new logos.

The cost of inaction compounds differently than most finance teams model. It is not a static drag. It trains your buyer to negotiate harder every renewal cycle, because they learned that your first number is not your real number.

The Playbook

Step 1: Name the hypothesis driving your current pricing.

Write it down. Not "we price based on value" but something specific: "Our enterprise tier is priced at $2,400 per seat per year because we believe procurement teams have a $200/seat/month ceiling." That is a testable statement. Vague pricing beliefs cannot be validated or disproved.

Step 2: Run a pocket price waterfall on the last 12 months.

Map every transaction from list price to realized revenue. Include multi-year discounts, free implementation, extended pilots, and support tiers you waive during close. Most teams find 4 to 7 distinct leakage points they were not tracking. Each one is a separate hypothesis about buyer behavior.

Step 3: Redesign one tier with guardrails before touching the others.

Do not overhaul your entire packaging in one sprint. Take your highest-volume tier, set a floor discount with a clear escalation path, and run it for 60 days. Track win rate, deal velocity, and average contract value in parallel. That is your evidence base for the next iteration.

The Breakdown

A vertical SaaS business at $32M ARR engaged a traditional consultancy for a pricing overhaul. They received a 90-page deck recommending three new tiers and a value metric shift from seats to workflow automations.

The deck was well-reasoned. The rollout was not.

Sales leadership was not involved in the pricing hypothesis. When the new tiers launched, reps defaulted to the old mental model and manually reconstructed the equivalent of the previous pricing through custom deal structures. Win rate dipped 11 points in Q1. The CFO rolled back two of the three new tiers within 90 days.

Before restructure: $32M ARR, 26% average discount, 14-month average sales cycle for enterprise. After proper implementation (12 months later): $41M ARR, 9% average discount, 11-month average cycle.

The difference was not the pricing model. It was that the second attempt started with a testable hypothesis the sales team co-authored.

Your Week Ahead

Pull your pocket price waterfall. If you do not have one, ask finance to export every closed-won deal in the last six months with list price, invoiced price, and any credits or concessions applied post-close. That single dataset will surface your highest-impact hypothesis to test.

Is your pricing strategy actually being executed, or is it being quietly negotiated away at the deal level every quarter?

Assess Your Commercial Health to get a structured view of your pricing architecture.