How to run an annual SaaS pricing and packaging review

Start with the evidence already in the building. Pull every closed-lost and churn record from the last four quarters and filter for the deals where pricing or packaging was called out as a primary or secondary reason. Read the notes, not just the dropdown. A deal lost on price is sometimes a value-communication problem, a packaging problem, or a procurement timing problem wearing a price label, and the review has to separate those before any list price moves. Rank the themes by frequency and by deal size so a cluster of small deals does not drown out a smaller count of large losses that actually bend the forecast. The output of this step is a one-page theme summary, not a conclusion.

• Pull closed-lost and churn records with pricing or packaging tagged as a reason in the last four quarters
• Read the notes field for every record, not just the dropdown value, and reclassify where the real reason differs
• Group losses into themes: list price too high, bad fit between tiers, missing add-on, surprise overage, procurement friction
• Rank themes by frequency and by lost ARR so one large deal does not get buried under a cluster of small ones

Quant data tells you what happened. Qualitative interviews tell you what people would have paid, and that signal does not exist anywhere in the CRM. Line up ten to fifteen conversations across new wins, recent losses, expansion accounts, and churned logos so the sample covers every direction a dollar can move. Use a Van Westendorp or Gabor-Granger style structure if the team has the muscle, but even a disciplined open interview beats a survey. Ask what the buyer would have paid at the ceiling, what price would have felt like a steal, what price would have made them pause, and what price would have been an obvious no. Record every call. The transcripts become the raw material the pricing and packaging decision gets argued from, and anchored quotes carry more weight in the exec review than a bar chart.

• Build an interview roster that spans new wins, recent losses, expansion accounts, and churned logos
• Pick a structured method such as Van Westendorp or Gabor-Granger and prep a tight 30-minute script
• Ask ceiling, bargain, pause, and no-go price points, plus which features would move each point
• Record and transcribe every call so quotes can be lifted into the exec readout verbatim

The value metric is whatever the plans are priced per. Seats, API calls, contacts, messages, workflows, revenue tracked. The audit question is whether that unit still tracks the value the customer feels. Pull the usage distribution per customer per metric and look at three things: how skewed the distribution is, how correlated the metric is to expansion revenue, and how closely it moves with the customer outcome the product promises. A value metric that saturates fast, that most accounts never breach, or that penalizes power users is dragging on both acquisition and retention. If the current metric is broken, the fix is not always a new metric; sometimes it is a tier change or an add-on. Decide what the data says before deciding what to do about it.

• Pull the usage distribution for the current value metric across every active customer
• Measure correlation between the metric and both expansion revenue and gross retention
• Test two or three candidate alternative metrics against the same accounts to see which tracks value best
• Document the audit finding as a yes-keep, yes-change, or yes-supplement with a new add-on, with evidence

With the win-loss themes, the interview quotes, and the value-metric audit on the table, redraw the packaging. The pressure test has three questions. First, do the tiers map to buyer segments that actually exist in the pipeline, or are they a hangover from the first version of the product. Second, is anything in the top tier buried that belongs lower, or anything in the bottom tier bloating the entry point. Third, are the add-ons priced and positioned as real optionality, or are they workarounds for packaging that does not fit. Sketch two or three alternative packaging layouts and walk them through a cross-functional group that includes sales, CS, product marketing, and finance. The goal of this step is not to pick a winner yet; it is to narrow the field to the layouts that survive adversarial review.

• Map current tiers to the segments in the live pipeline and flag tiers that no segment actually buys
• List every feature per tier and challenge each placement against buyer willingness-to-pay data
• Treat add-ons as a separate design question and decide which belong in the base tier and which stay optional
• Walk two or three alternative packaging layouts through sales, CS, product marketing, and finance

Narrow the field to three to five scenarios and model each one end to end against the P&L. Each scenario needs a list-price change, a packaging change, a value-metric change, a grandfathering treatment, and a modeled impact on new-logo win rate, average contract value, expansion rate, and churn. Use the win-loss data to estimate win-rate sensitivity, the interview data to estimate ACV uplift, and the usage audit to estimate how the value-metric change will shake out across the base. Model the pessimistic, base, and optimistic case for each scenario. The exec review should see a short list of scenarios with the tradeoffs made explicit, not a single recommendation with the alternatives hidden.

• Define three to five scenarios that span safe, aggressive, and repackaged options
• Model each scenario against win rate, ACV, expansion rate, and churn with pessimistic, base, and optimistic cases
• Score every scenario against the operational cost of rolling it out, including sales retraining and CS communication load
• Pick the two scenarios worth presenting to the exec team with the losing scenarios documented and the rejection reason recorded

The exec review is where pricing changes die on the vine or ship with teeth. Walk in with the two short-listed scenarios, the modeled P&L impact, the win-loss and interview evidence underneath the recommendation, the grandfathering plan, and the proposed go-live date. Decide the open questions in the room: effective date, discount envelope, grandfathering duration, treatment of mid-term renewals, treatment of expansion inside grandfathered accounts, and the kill criteria that would reverse the change. Capture every decision in writing in a single memo circulated the same day. Verbal exec sign-off that lives in a Slack thread evaporates the first time a sales leader needs to invoke it against a complaining regional VP.

• Present two scenarios with modeled P&L, evidence, grandfathering plan, and go-live date in one deck
• Decide effective date, discount envelope, grandfathering duration, and mid-term renewal treatment in the room
• Define the kill criteria: the win-rate, churn, or NRR movement that triggers a rollback or a pause
• Capture every decision in a signed memo circulated the same day and stored where sales and CS can find it

The communication plan has three audiences and each one needs a tailored message. Prospects see the new pricing on the website and in the sales conversation. Existing customers get a direct note from their account owner that leads with the grandfathering treatment and the renewal timeline, not with the price change. Partners, resellers, and anyone with a quote outstanding need the transition rules in writing before the change goes live. Grandfathering is not a courtesy; it is a retention lever. Hold existing accounts at their current price for a defined window, typically through their next renewal, and document the terms the renewal will convert on. A clean grandfathering plan is often the difference between a pricing change that lifts NRR and one that lifts churn.

• Write three message tracks: prospects, existing customers, and partners or resellers with outstanding quotes
• Lead the existing-customer note with the grandfathering treatment, the renewal timeline, and a named point of contact
• Give sales and CS a shared objection-handling doc covering the top ten questions each team has already predicted
• Freeze outbound discounts outside the new envelope for the first thirty days so field pressure does not immediately re-break the model

Pricing changes are won or lost in the first ninety days after launch. Lock a measurement cadence before the change goes live and run it on the schedule even when early signals look fine. Track new-logo win rate against the pre-change baseline, average contract value, expansion rate on grandfathered and ungrandfathered cohorts separately, churn and downgrade rate on existing accounts, and discount depth against the new envelope. Pair the numbers with a running feedback log from sales and CS so qualitative signal does not get lost between dashboards. If the modeled kill criteria trigger, invoke them. If the numbers come in ahead of plan, document what worked so the next annual review starts from evidence instead of memory.

• Lock a weekly measurement cadence for ninety days covering win rate, ACV, expansion, churn, and discount depth
• Report grandfathered and ungrandfathered cohorts separately so the real impact on the new base is visible
• Keep a running sales-and-CS feedback log and tag every entry to the specific pricing or packaging decision it touches
• Compare the ninety-day result to the modeled base case, invoke kill criteria if triggered, and write the postmortem for next year