What's the right cadence for auditing whether your pricing model is still fit-for-purpose — annual, quarterly, or event-triggered — and how does that sync with comp planning cycles in 2027?

The $4M-to-$25M company that never scheduled the audit

Picture a B2B SaaS business that set its pricing at roughly $4M ARR — three tiers, per-seat, list prices ending in 9, a 15% discount ceiling for reps. It works. Deals close. Nobody touches it. Five years later the company is at $25M ARR and the pricing model has never been formally reviewed, because reviewing it was never anyone's job on any calendar.

Then a quarter misses by 12%. The panic review that follows finds four separate problems that all surfaced at once. The ideal customer profile moved upmarket two years earlier — the average deal is now 340 seats instead of 40 — but the price-per-seat curve still flattens at 100 seats, so every enterprise deal is priced as though it were a mid-market deal. The product tripled in scope: two new modules and an API shipped, and because nobody re-opened the packaging question, both are bundled free into the mid tier. Average discount-off-list drifted from 11% to 27% over eleven quarters, one individually-reasonable approval at a time. And a competitor moved to consumption pricing eighteen months ago, which is why the company keeps losing the deals where the buyer wants to start small.

None of that is new information. It is three to five years of silent drift arriving simultaneously, because the drift was never scheduled to be looked at. The damage is not just the money left on the table — though on a $25M book, closing a 16-point discount gap is roughly $4M of realized revenue. The real damage is that the correction is now a single, enormous, high-risk reset executed under crisis pressure, touching every customer and every rep at once, instead of four or five modest annual adjustments nobody would have noticed.

The comp consequence is worse and it is what makes the cadence question urgent rather than academic. That crisis review concludes in February. Comp plans for the year were locked in November. Quotas were built on the old effective-price assumption of 73% of list. If pricing changes mid-year — new floors, a repackaged mid tier, a usage component — every quota built on the old assumption is now wrong, every accelerator threshold is calibrated to a deal size that no longer exists, and the company either eats a year of misaligned incentives or reissues comp plans mid-year, which is the single most reliable way to lose good reps. Pricing and comp are the same system observed from two ends. Auditing one on a schedule that ignores the other guarantees this outcome.

How the four-layer cadence actually works

The reason "annual or quarterly or event-triggered?" has no single answer is that the question collapses four genuinely different activities into one. Pricing problems move at four different speeds, and a single-interval review will always be too slow for the fast ones or too heavy for the slow ones.

Layer 1 — continuous signal monitoring. Not a meeting. A dashboard, reviewed monthly by RevOps, tracking five leading indicators: average and distribution of discount-off-list on closed-won; price-objection rate in both won and lost deals; list-to-effective-price ratio across the book; deal-desk exception volume as a percentage of closed deals; and the correlation between your value metric and actual product usage. Layer 1 catches operational drift in weeks. Its output is never a pricing change — it is a threshold breach that escalates to Layer 2.

Layer 2 — the quarterly pulse. Sixty to ninety minutes, once a quarter, four agenda items: walk the Layer 1 dashboard for threshold breaches; log any competitor pricing move this quarter; review packaging requests stacking up from sales and CS; and decide what escalates. The discipline is restraint. A quarterly pulse that produces a pricing change every quarter is not a pulse — it is the change-too-often failure wearing a calendar. A good pulse ends in "all within tolerance" or "two items flagged for the annual audit, one escalated now."

Layer 3 — the annual deep audit. Three to six weeks of elapsed work with a core team of RevOps, Finance, and Product, reviewed by the CRO and CEO. Six questions: is the value metric still right; do the tiers match how customers actually segment; is list anchored correctly against willingness-to-pay; where is discounting concentrated; what does qualitative win/loss say about price; what are competitors actually charging now. This is the only layer with enough depth to catch structural drift.

Layer 4 — event triggers. No calendar. A written list, agreed in advance, of events that force an off-cycle review: a new product line (not a feature — a product); entry into a new segment or geography; a competitor entering on a different pricing *architecture*; an M&A event on either side; a material cost-to-serve change; a fundraise that resets the growth mandate from efficiency to land-grab or the reverse. Writing the list down in advance removes the judgment call in the moment — when a competitor launches a free tier, nobody debates whether it counts.

The layers hand off to each other. The dashboard feeds the pulse; the pulse flags items for the annual audit; the annual audit resets the thresholds the dashboard watches. Auditing frequency is high; *changing* frequency stays low — ideally once a year, deliberately, on a planned date. Decoupling the cadence of looking from the cadence of acting is the whole trick.

mermaid flowchart TD A[Audit cadence question] --> B{How fast does the<br/>problem move?} B -->|Weeks| C[Layer 1 dashboard<br/>detect only, never change] B -->|A quarter| D[Quarterly pulse<br/>triage and escalate] B -->|A year or more| E[Annual deep audit<br/>decide and change] B -->|Discontinuity| F[Event trigger<br/>scoped off-cycle audit] E --> G{Change lands<br/>before comp kickoff?} G -->|Yes| H[Fold into quotas, rate tables,<br/>accelerators for the new year] G -->|No| I{Can it wait<br/>one cycle?} I -->|Yes| J[Queue for next annual cycle<br/>monitor in the interim] I -->|No| K[Grandfather existing comp plans<br/>apply new pricing to new logos only] F --> I </parameter> </invoke>

Where the value metric quietly stops measuring value

The deepest thing the annual audit examines — and the one most worth the three-to-six-week investment — is whether the unit you charge for still tracks the value the customer receives. Everything else in pricing sits on top of this. Clever tiering and disciplined discounting cannot rescue a model that is metering the wrong thing.

The classic drift is seat-based pricing in a product whose value migrated to automation. You chose per-seat because, at launch, the product was a tool humans operated, and more humans meant more value. Then you added workflow automation, an API, and features that do work with no human in the loop. Now the value is in the work the product performs, and a customer can get several times the value while *reducing* seats. Your revenue from your best customer falls as their outcomes rise. Worse, the meter actively punishes the behavior you want: customers ration licenses, share logins, and avoid rolling the product out broadly, because the meter taxes adoption.

The test method is mechanical. Take a representative sample across segments. For each account, measure realized value using the best proxy you have — outcomes delivered, usage intensity, business results the customer will attest to — and plot it against the value metric they are billed on. A healthy metric produces a tight positive correlation. A broken one produces scatter, a flat line, or the alarm case: a negative slope where your highest-value customers are among your lowest payers. Then examine behavior. Are customers batching API calls, restructuring accounts to stay under tier thresholds, or sharing the billing unit? Customers optimizing against your meter are telling you the meter is wrong.

Changing a value metric is the highest-stakes pricing change there is — it touches every customer, every quote, every renewal, and the entire comp structure, since a shift from seats to consumption changes what a "deal" even is and how commission is earned on expansion. That is precisely why the fit test belongs in the deliberate annual audit and never in the quarterly pulse. Catching the drift while it is still a tilt rather than a full decoupling is the single highest-leverage thing the annual audit does.

Adjacent to it, the packaging review asks whether the tier architecture still does its job: segmenting by willingness-to-pay, creating a motivated upgrade path, and making the decision easy. Look for the arbitrage case — where a lower tier plus add-ons costs less than the next tier up while delivering comparable value, so sophisticated buyers reconstruct the premium tier at a discount you are funding. Look at where customers actually land: if the overwhelming majority cluster in one tier, or if base-tier customers consistently bolt on add-ons until they have rebuilt the middle tier, the architecture does not match how the market segments. And prune. Packaging accretes — an add-on here, a segment bundle there — until the offer is a sprawl no buyer can hold in their head and no rep can quote cleanly.

The pitfalls that kill the cadence

The audit-to-action gap is the number one failure. The audit runs, it is thorough, it produces a sharp deck of findings, everyone nods, and nothing changes. Next year's audit finds the same problems slightly worse. The audit has become a ritual that documents drift instead of correcting it. The cause is that audits end in findings rather than decisions. "Discounting is too deep in mid-market" commits no one. "We raise the mid-market floor 12% effective the new fiscal year; pricing owner is named; sales enablement owner is named; live date is set" commits someone. Fix it by design, before the audit starts: mandate that every issue resolve into exactly one of three states — change (decision, owner, date), monitor (the specific threshold that would trigger action, and who watches it), or accept (an explicit decision not to act, and why). Nothing is allowed to end in "noted."

Over-scoping produces paralysis. An audit that surfaces fifteen problems is overwhelming, so the organization freezes and does none of them, when it could have done three. Force prioritization inside the audit itself: pick the two or three changes that matter most and commit fully.

Scheduling the audit downstream of planning institutionalizes the gap. This is the pitfall specific to the comp question. If findings land after the revenue plan and comp plans are locked, even excellent decisions cannot be funded or staffed for twelve months. The fix is a calendar rule, written down and owned: the deep audit finishes before comp kickoff, every year, without exception.

Letting sales own pricing. Sales is an essential input — the field sees the deals, hears the objections, and knows exactly where the price book breaks. But sales is measured on closing, and lower prices close more, so a pricing process owned by sales drifts every time toward discounting and toward whatever makes this quarter easier. That is an incentive, not a character flaw, and the fix is structural: RevOps, Finance, and Product own the working process, sales is a heavily weighted input, and the CRO and CEO approve. Balance the incentives at the ownership level rather than hoping goodwill overcomes them.

Discovering the data is not ready, and treating that as a reason to postpone. Most companies attempting a first real audit find that discount and list price are not cleanly captured in the CRM, win/loss reason codes are inconsistent free text, billing and product usage are never joined, and competitive intelligence is folklore assembled from a few memorable deals. That discovery is not a delay — it is the audit's first and most valuable finding, and instrumenting it is what makes every subsequent cycle faster and sharper.

Turning the quarterly pulse into a redesign. If the pulse keeps wanting to become a redesign, that is a signal — real issues are accumulating and either the deep audit needs to happen or an event trigger needs calling. But the pulse itself stays light, or it stops happening.

Never surfacing pricing health to the board. Pricing decay shows up in net revenue retention flattening, realized price drifting down, gross margin eroding by segment, and discount tails fattening — usually *before* it shows up in headline growth. Reporting the audit's findings and decisions once a year creates the accountability that stops the cadence from quietly lapsing, because next year someone will ask what happened to last year's decisions.

Related questions

Should the pricing audit and comp planning be run by the same team?

No — but they must share a calendar and a data set. RevOps typically sits in both, which is the connective tissue. Keep the pricing decision with RevOps/Finance/Product and comp design with Sales Comp/Finance, with an explicit handoff of the decision log.

What if an event trigger fires in March, mid-comp-year?

Scope the audit narrowly to the affected dimension, and grandfather existing comp plans — apply the new pricing to new-logo business only, or add a targeted SPIF rather than reopening quotas. Mid-year quota reissues are the fastest way to lose good reps.

Does a quarterly audit cadence ever make sense?

Yes, in genuinely high-velocity transactional businesses with sub-30-day cycles and self-serve or low-touch motions, where quotas are already set quarterly. For enterprise sales with six-month cycles, quarterly pricing changes destroy the rep's ability to work a stable target.

How long should the annual deep audit actually take?

Three to six weeks of elapsed time with a small core team — not full-time. Most of the calendar goes to pulling and cleaning data, running win/loss interviews, and building the competitive teardown. The analysis and decision sessions are a fraction of it.

FAQ

Is annual, quarterly, or event-triggered the right answer?

All three, at different layers. Continuous monitoring runs always, a light pulse runs quarterly, the deep audit runs annually, and event triggers fire off-cycle. Each catches a different speed of drift. The mistake is picking one interval and expecting it to catch everything.

How far ahead of comp planning should the pricing audit finish?

Three to four months ahead of comp plans going live, and at least two to four weeks ahead of comp planning kickoff. For a calendar fiscal year with October comp kickoff, that means the deep audit runs July through September.

What are the event triggers that should force an off-cycle audit?

A new product line, entry into a new segment or geography, a competitor entering on a different pricing architecture, an M&A event, a material change in cost-to-serve, and a fundraise that resets the growth mandate. Write the list down in advance so nobody debates it in the moment.

How often should we actually change pricing, as opposed to auditing it?

At most once a year for most B2B businesses. Audit frequently, change rarely. A sales organization can absorb and execute one meaningful pricing change well per year; two or three leaves the team permanently half-fluent in the current model.

Who should own the pricing audit?

RevOps, Finance, and Product as the working core, with the CRO and CEO as approvers and sales as a heavily weighted input. Sales should not own it outright — the incentive to discount is structural, and ownership should balance it rather than concentrate it.

What is the single most common reason pricing audits fail?

They end in findings rather than owned decisions. Require every issue to resolve into change, monitor, or accept — each with a named owner and, where applicable, a date and a threshold. Nothing ends in "noted."

Sources

• https://hbr.org/2018/06/a-quick-guide-to-value-based-pricing
• https://www.mckinsey.com/capabilities/growth-marketing-and-sales/our-insights/pricing-the-next-frontier-of-value-creation
• https://openviewpartners.com/blog/saas-pricing-strategy/
• https://www.bain.com/insights/is-your-pricing-strategy-keeping-up/
• https://www.priceintelligently.com/blog/value-metric
• https://www.gartner.com/en/sales/topics/sales-compensation
• https://hbr.org/2015/04/motivating-salespeople-what-really-works
• https://www.bcg.com/publications/2021/pricing-strategy-in-b2b
• https://a16z.com/pricing-your-saas-product/
• https://www.forrester.com/blogs/category/pricing/

Related on PULSE

• How do you set sales quotas when your pricing model is changing mid-year?
• What signals tell you a value metric has stopped tracking customer value?
• How should discount authority thresholds be structured across rep, manager, and deal desk?
• What belongs in a competitive pricing teardown, and how often should it be refreshed?
• How do you migrate existing customers to new pricing without triggering churn?
• Who should own pricing in a growth-stage RevOps organization?