Pricing and Packaging Audit: A Practical Guide for B2B SaaS
A pricing and packaging audit is a structured review of what you charge, what each plan includes, and what customers actually pay once discounts, exceptions and billing rules are applied. For a B2B tech company, the goal is simple: find where the price list and reality have drifted apart, then fix the few gaps that cost you the most revenue. Do it with sales, finance, product and marketing in the same room, and measure it against real deal and billing data, not opinions.
Real talk: most teams don’t have a pricing problem. They have a packaging problem, a discounting problem, or a handoff problem between sales and finance that shows up as a pricing problem. This guide shows you how to tell which one you have.
People use “pricing” and “packaging” as one word, but they are two different levers.
Pricing is the number and the metric behind it: per seat, per usage unit, per account, flat platform fee. Packaging is what sits behind each number: which features, limits, services and support levels go into which plan, and who each plan is built for.
A pricing audit, in the broad sense, assesses how a subscription business sets prices to make sure they’re consistent across similar accounts, profitable, and in line with how other companies in the space do it, as SaaS Mag describes it. The packaging half asks a different question: does each plan make sense to the buyer it targets?
A 2026 checklist from AI Biz Hub breaks the work into five dimensions:
That list is a good skeleton. The rest of this article turns it into a working process.
You don’t need to audit everything at once. Your pipeline data already hints at where the problem lives. SaaSmentic’s 2026 guidance maps common symptoms to likely causes:
| What you see | What it may mean |
|---|---|
| High win rate, low ACV | You may be underpriced |
| Heavy discounting | Packaging or value communication isn’t landing |
| Low expansion | The value metric may not grow with customer usage |
| Long enterprise cycles | Procurement or packaging friction |
Treat these as hypotheses, not verdicts. A 70% win rate can mean you’re cheap, or it can mean your reps only chase easy deals. The audit exists to tell the difference.
Here’s the quick version of how we read them:
Before you open a spreadsheet, agree on the source of truth. A pricing audit needs a reference that defines the current price, packaging, limits, billing rules and exceptions. DiffHook suggests this can be a pricing operations spreadsheet, product catalog, billing system, CPQ configuration or an approved pricing memo, and notes that without one the audit becomes subjective.
In practice, we find three versions of “the price” in most B2B tech companies:
If those three don’t match, you’ve found your first finding. Write down every mismatch. Plan names, included limits, annual vs. monthly terms, and add-on prices are the usual suspects.
Good audits compare list price against effective price. Here is the data set worth assembling:
From CRM and CPQ
From billing
From the market
From customers
A word on win-loss. Fairview cites Primary Intelligence data showing sales teams blame price for losses 48% of the time, while buyers name price as the real primary factor 23% of the time. That gap is a reason to interview buyers rather than accept the CRM’s “lost on price” field at face value. The statistic comes from a vendor’s citation of the original research, so use it as a reason to ask, not as a benchmark for your own numbers.
For each paid plan, calculate gross margin and CAC payback at the price customers actually pay. If a tier doesn’t clear the floors you’ve set, either the price, the included scope or the sales motion for that tier has to change. This is also where you check the spacing between tiers. A big cliff between plans makes buyers stall at the lower one.
Rank your discounts by depth, frequency and rep. Then ask:
Billing gaps add another layer. A billing-software vendor, Lago, puts billing-gap leakage at 1% to 5% of ARR, according to the AI Biz Hub checklist. That’s a vendor estimate, so size your own leakage from your invoices instead of borrowing the range. The same source makes a useful point about the upside: at a 10% operating margin, a 1% price increase that holds volume raises operating profit by 10%.
Elasticity asks how demand responds to price. You rarely get a clean answer from history alone, so use deal data plus a controlled test: a new price on new quotes for one segment, with the rest unchanged. Watch conversion and cycle length, not just the price accepted.
This is where the confusing-page problem usually lives. PricingCanary’s April 2026 write-up says a pricing page that looks clean but still confuses buyers usually has a packaging problem, not a visual one. Ask:
If your reps have to explain the plans on every call, the packaging isn’t doing its job.
Check the pricing page, the quote, the order form and the renewal notice. The question is the same at each step: does the buyer see the same offer, in the same words, with the same terms? Also check where each plan sends the buyer: self-serve checkout, demo request or sales conversation. A mismatch between plan and path is a quiet conversion killer. If demo requests are where you lose people, our look at demo conversion rate shows how to find a booking leak.
Pricing audits fail when one function owns them. SaaS Mag recommends a pricing committee drawn from sales, finance, product and marketing, with a coordinator who drives the research and strategy. The committee reviews current packages, incentives, segments, competitors, bundles and tiers using team interviews, distribution channels, competitive benchmarking and historical data, then identifies weaknesses and plans how to strengthen them.
Our take: name one owner with the authority to say no. A committee without a decision-maker produces a long list and no change.
An audit that ends with 40 observations is a report, not a plan. Rank each finding on three things:
Pick the top three to five. Typical first moves are tightening discount approvals, fixing a plan that misses the margin floor, clarifying plan names and limits, and aligning the website, CPQ and billing to one price book. If your CPQ is part of the fix, the implementation guidance from Streams Solutions lays out a sequence: discovery and governance, design, incremental configuration, thorough testing, then launch with a governed improvement backlog.
This is where good audits get undone. Stripe’s usage-based pricing guidance recommends launching a new model for new signups first and watching it for at least 60 to 90 days. Measure conversion, average spend and bill-shock complaints before you touch existing customers. For the installed base it suggests opt-in migration, a segment-by-segment rollout, honoring existing annual pricing through renewal, transition credits for materially affected customers, and a firm cutoff with 90-, 60- and 30-day reminders.
The principle underneath is learn on new buyers first, then move the base. It exposes confusion early and limits contract and retention risk.
If you’re raising prices on existing accounts, check the notice rules in the states and countries where your customers sit. Automatic-renewal and consumer-protection rules vary, and your counsel should confirm what applies to your contracts. Don’t let a customer hear about a change from anyone but you.
After launch, watch these weekly for the first 8 to 12 weeks, per SaaSmentic: conversion by plan, demo bookings, trial-to-paid, sales cycle length, win rate, discounting, ACV, churn and downgrades, expansion, upgrades and pricing-confusion support tickets. Our RevOps metrics guide covers how to set formula, source, cadence and owner for numbers like these so nobody argues about definitions later.
At minimum, annually or after a meaningful product or market change. Wes Bush of ProductLed says best-in-class companies adjust pricing and packaging frequently, often quarterly. Most teams don’t need to go that far. They do need a calendar slot, an owner and the data ready, so the review doesn’t wait for a crisis.
| Week | Focus | Output |
|---|---|---|
| 1 | Reference point and data pull | One agreed price book, 12 months of deal and billing data |
| 2 | Analysis | Tier margin check, discount ranking, mismatch list |
| 3 | Customer and buyer input | Win-loss and customer interviews, competitor snapshot |
| 4 | Prioritization | Ranked change list, owner, rollout plan and metrics |
Thirty days is enough to find the big leaks. Testing and rollout take longer, and they should.
Pricing rarely breaks alone. Discount creep often traces back to weak qualification or loose approval rules. Plan confusion often traces back to unclear messaging. If buyers can’t repeat your value in their own words, no plan structure will rescue the deal, which is why we pair this kind of audit with work on SaaS value proposition messaging. If reps are working around the quote tool, a sales tech stack audit shows where the workflow is breaking.
If the audit points at problems that reach beyond the price list, such as inconsistent sales process, unclear roles or weak pipeline governance, we can look at the full revenue system with you. Our Revenue System Diagnostics and Sales Workflow Audit are built to show where revenue gets lost between ICP, process and execution. See the consulting services we offer and pick the starting point that fits.
For a deeper look at how the pieces fit, read our guide on the ops-first sales operating model.
Here’s what we see again and again. A founder or Head of Sales senses that pricing is off, so the team changes the numbers. Three months later the discounting is the same, the plans are still confusing, and a new price list now sits next to three old ones.
The number was never the whole story. Pricing and packaging live inside a revenue system: who you sell to, how reps qualify, how deals get approved, how quotes are built, how billing follows the contract. Fix one piece and the rest pulls it back.
That’s why we approach it as practitioners, not theorists. We treat the audit as a way to see the end-to-end system: ICP, roles, process, pipeline and performance governance. Then we rebuild what’s actually broken, in an order that sticks. Real talk: a price change that nobody can execute consistently is just a new set of exceptions.
If you want hero reps closing around a messy price book, that works until they leave. If you want predictable results, build the structure first.
Antony
It’s a structured review of your prices, plans, discounts and billing against what customers actually pay. It checks whether tiers hit your margin and payback targets, whether discounting is controlled, and whether buyers understand what each plan includes. The output is a ranked list of changes, not a general report.
A pricing audit looks at the numbers and the price metric: levels, discounts, margins and billing. A packaging audit looks at what each plan contains and who it’s built for. In B2B SaaS you want both together, because a pricing symptom like heavy discounting often has a packaging cause.
A focused internal audit can find the main leaks in about a month if the CRM and billing data are accessible. Testing a new model and rolling it out takes longer. Stripe’s guidance suggests observing a new model on new signups for at least 60 to 90 days before touching existing customers.
A small group from sales, finance, product and marketing, with one coordinator and one decision-maker. Sales knows how deals are really priced, finance knows what gets invoiced, product knows what each plan delivers, and marketing owns how the offer is communicated.
At least once a year, and after major product launches, market shifts or a spike in discounting. Some fast-moving companies review quarterly. Pick a cadence you will keep.
Subscribe to our Insights: Expert productivity tips in your inbox
You'll receive 1-3 emails per month. Your data stays private, always.
CRO & Co-Founder with Sales Label Consulting
Watch our Sales Mates Podcast
November 10, 2026 - 9 min read
Read article Read articleNovember 8, 2026 - 10 min read
Read article Read articleNovember 7, 2026 - 10 min read
Read article Read articleNovember 6, 2026 - 10 min read
Read article Read article