Most SaaS pricing problems arrive as one pressing question: should we charge for usage, can we raise prices at renewal, what do we do with the AI features. We help B2B software leadership teams answer that question with evidence, then carry the answer through billing, sales, and the installed base.
Software companies rarely call a pricing advisor because their prices are wrong in general. They call because a specific decision has become expensive to get wrong and uncomfortable to own. In our work with SaaS and B2B XaaS companies, the same five decisions come up again and again, usually in this order of urgency:
Each of these is covered below as a decision: the options, how we choose between them, and what we hand over. A company rarely needs all five at once. Knowing which one to resolve first is often the most valuable output of the first two weeks. For the broader picture of SaaS pricing models and how AI is changing them, see our SaaS pricing strategy guide.
The value metric is the unit your price scales with. It matters more than the price level, because it decides whether revenue grows when customers get more value, or only when they add headcount. A product priced per seat whose customers automate away the seats is shrinking its own revenue with every successful deployment.
We compare candidate metrics on five criteria, scored against the product’s actual usage data and a round of customer interviews. The scorecard below is an illustrative example for a mid-market workflow product that has added AI features which do work previously done by users.
Per seat
Tracks customer value2
Predictable for the buyer5
Easy to meter and bill5
Grows with expansion2
Hard to share or game2
Total (out of 25)16
Per active user
Tracks customer value3
Predictable for the buyer3
Easy to meter and bill4
Grows with expansion3
Hard to share or game4
Total (out of 25)17
Usage unit (workflows run)
Tracks customer value4
Predictable for the buyer2
Easy to meter and bill3
Grows with expansion5
Hard to share or game4
Total (out of 25)18
Outcome (share of cost saved)
Tracks customer value5
Predictable for the buyer1
Easy to meter and bill1
Grows with expansion4
Hard to share or game3
Total (out of 25)14
Platform fee plus usage
Tracks customer value4
Predictable for the buyer4
Easy to meter and bill3
Grows with expansion4
Hard to share or game4
Total (out of 25)19
Illustrative scores. Real scores come from your usage data, billing constraints, and buyer interviews.
Three things usually decide the outcome. First, the outcome metric looks best in theory and loses on predictability and billing: finance teams at the buyer cannot budget for it, and your billing system cannot invoice it without manual work. Second, per seat wins on simplicity, which is why so many products keep it long after it stops tracking value. Third, the hybrid of a platform fee plus a usage component usually scores best, because the fee gives the buyer a number to budget and the usage component lets revenue follow adoption. The weighting is a leadership choice, not a formula. A company preparing for a sale may weight predictability higher than a company chasing expansion.
What we deliver for this decision: the recommended metric with the evidence behind it, the metering and billing requirements it creates, and how each current plan maps onto it.
As a SaaS pricing and packaging consultant, the question we ask first is not how many tiers you should have. It is what makes a customer move up. Every plan structure has an upgrade trigger, whether anyone designed it or not. It is either a capability the customer needs (single sign-on, audit logs, an integration), a limit they hit (records, workspaces, usage), or a service level they want (support response, uptime commitments).
Product analytics usually shows which trigger is working. We look at three things in the data:
Limit hits by plan.
If 60% of lower-plan customers hit a limit within six months, the limit works. If almost nobody hits it, the upgrade must come from features worth paying for.
Feature adoption by plan.
Features that the higher plan pays for but its customers do not use are not driving upgrades; they are decoration on the price, and candidates to move into an add-on.
Where discounting concentrates.
When most discounts are granted to move a customer from the middle plan to the top plan, buyers are telling you the step up costs more than it delivers.
You receive a packaging recommendation with the fence between each plan named explicitly, the upgrade trigger for each step, and the add-ons that sit outside the plans. General principles for building tiers and fences are on our pricing and packaging page; this engagement applies them to your product and your data.
Price increases are the decision SaaS leaders postpone longest, because the downside is visible and the upside is not. The arithmetic helps. It tells you how much churn an increase can absorb before it destroys value.
Illustrative example. A company has $12 million of ARR renewing over the next 12 months and is considering an 8% increase. If every customer renews, the increase adds $960,000 of ARR. The increase still breaks even if customers holding up to 7.4% of that ARR leave because of it, about $889,000, since 8% divided by 108% is 7.4%. Below that level of increase-driven churn, the company is ahead.
That calculation is a ceiling, not a plan. In practice the increase is rarely uniform. We segment the base and set a different treatment for each group:
Gross revenue retention tells you what the increase cost in lost customers. Net revenue retention tells you whether the base, taken as a whole, is worth more afterwards. Both belong on the dashboard for at least two quarters. More on sequencing increases is in our guide on how to increase prices.
The timeline below is the one we typically work to for an increase on annual contracts.
| When | What happens | Who owns it |
|---|---|---|
| T-120 days | Segment the base, set the increase by segment, model ARR and churn scenarios | Pricing lead, finance |
| T-90 days | Brief customer success and sales; agree the exception rules and who approves them | Revenue leadership |
| T-60 days | Written notice to customers, with the reason stated in terms of the product’s development | Customer success |
| T-30 days | Account-level conversations for strategic and at-risk accounts, each with its written rationale | Account owners |
| T-0 | New prices take effect at each renewal date, with approved exceptions applied | Billing |
| T+30 to T+90 days | Track net revenue retention, gross revenue retention, and exception volume against the plan | Finance, pricing lead |
A new metric or a new set of plans only pays back once the existing base is on it. Migration is where SaaS repricing projects most often stall: the new pricing launches for new customers, the old plans live on for years, and the company runs two pricing systems at once.
We plan migration by cohort, and every cohort gets one of four paths:
| Path | Who it suits | Watch-out |
|---|---|---|
| Move now | Customers who will pay the same or less, or gain features | Revenue can fall if the new plan is cheaper for heavy users; model it first |
| Move at renewal | Most customers, with notice and a clear comparison | Renewal dates spread the move over 12 months, so reporting must track both models |
| Grandfather with a sunset | Long-tenured or sensitive customers who need more time than one renewal cycle | Grandfathered pricing without an end date becomes permanent, and so does the second pricing system |
| Keep on legacy terms | A small number of contracts where moving costs more than it earns | Document the reason and review annually, or the exception quietly becomes the norm |
The common mistakes are predictable. Migrating perpetual-license customers to subscription without crediting the maintenance they already pay feels like a double charge. Moving seat-based customers to usage without showing them a like-for-like bill based on their own last six months of usage invites a negotiation over every account. Launching the change before billing can invoice it produces manual credits for months.
What we deliver for this decision: the cohort map, a bill comparison for each cohort, the customer communication, and the sales and success talk tracks.
In SaaS, list price is rarely what erodes first. The erosion comes through deal structure: a 20% multi-year discount, three free months at the start, a ramp that begins at half price, an uncapped usage allowance thrown in to close before quarter end. Each concession is defensible alone. Together they can put effective price well below list without anyone having approved a discount of that size.
We write deal rules that treat these structures as discounts and measure them the same way: effective annual price over the contract term, compared with list. The rules name who can approve what, which concessions need a reason code, and when a ramp or free period must end. Where those rules need to be applied at the point of quote, PricePro© enforces them inside the tools your team already uses and flags deals that fall outside policy before they are signed.
Our SaaS work covers the transitions software companies go through as they grow: from founder-led pricing to a deliberate pricing strategy, from seats to usage, from freemium to an enterprise motion, from perpetual licenses to subscription, and the monetization of new features, AI capabilities, and product lines. The senior people who scope the work are the ones who do it, and Tariq Usmani brings deep experience in AI monetization and enterprise deal governance to these engagements. Our published case studies come from distribution, manufacturing, and services businesses, so we describe our SaaS work here by its method rather than by client results.
Among SaaS pricing consultants, the difference that matters most is what happens after the recommendation. Our engagements include the billing requirements, the migration plan, the sales enablement, and the first review of results, because a pricing decision that stops at a slide has not been made.
Tell us which of the five decisions is in front of you. We will tell you what evidence it needs, how long it takes to resolve, and whether it is worth resolving now.
Start with a small number of segments defined by something the buyer cannot easily change, such as company size, deployment scale, or regulatory needs, and price each on its value metric. Segment prices can sit far apart if the fences between them are real. They collapse when a large customer can buy the small-business plan and get the same product.
It depends on what the feature costs to run and how evenly usage is spread. Features with low running cost that most customers use belong in the plans, where they defend the price. Features with meaningful compute cost and very uneven use are better priced through credits or a usage component. Our SaaS pricing strategy guide covers the decision in detail.
Smaller than most people fear, and larger than most companies run. For a conjoint or trade-off study, a few hundred qualified respondents is typical; for B2B products with a narrow buyer population, 15 to 30 structured interviews per segment often give more reliable direction than a thin survey. Our pricing research page explains how we choose.
They are usually the constraint on timing. A new metric may need new meters, new invoice logic, and new product records in CPQ. We specify those requirements early, in the language your systems team uses, so the launch date is set by readiness rather than by optimism.
Agree the measures before the change: net and gross revenue retention for the installed base, win rate and average contract value for new business, and discount depth on new deals. Compare each against the baseline for at least two quarters. A single quarter of good bookings says little about whether the change will hold.
Yes, frequently. Sponsors often start the conversation because pricing is in the value creation plan. The work runs from a rapid pricing assessment before the deal, through a post-acquisition 100-day plan, to preparing the company for exit. The work links into the broader private equity value creation agenda, and the contract sits with the portfolio company.
