.png)
Frameworks, core principles and top case studies for SaaS pricing, learnt and refined over 28+ years of SaaS-monetization experience.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
What Is a Pricing Revamp? Understanding When and How to Overhaul Your SaaS Pricing Strategy
Most SaaS companies call for a pricing revamp when growth slows, win rates fall, or gross margin comes under pressure. The usual response is quick: raise list prices, add a tier, or ask sales to hold firmer on discounts. Those moves can help, but they rarely repair the problem that caused the pressure.
A true revamp asks a harder question: does the way we charge still fit the customers we serve, the product they buy, and the economics we must sustain? That question matters because pricing touches every commercial decision at once - product access, sales coverage, billing, renewals, expansion, and the buyer’s sense of risk.
Monetizely’s position is clear: a SaaS company should overhaul pricing when the fault lies in the architecture, not merely in the rate card. The work must proceed from business goal and customer segment to package, meter, price, and operating model - in that order.
A pricing revamp begins when a rate problem is actually a design problem
A pricing revamp is a coordinated redesign of what customers buy, how they are charged, and how the company runs the model after contract signature. It is not a synonym for a price increase.
Consider a workflow platform that sells one $50-per-user plan to a 20-person startup and a 5,000-person bank. The startup may need simple collaboration and quick setup. The bank may need security controls, audit records, a service-level agreement, procurement support, and deployment help. Raising both customers to $60 per user does not solve the underlying mismatch. The smaller buyer still sees too much product, while the larger one still sees too little commercial separation.
The distinction matters because the wrong intervention can make a weak model worse. A rate change on top of poor packaging often drives more discounting. A new usage charge without clear measurement can create billing disputes. A new enterprise tier with features nobody values can add complexity without increasing average selling price.
The following comparison helps leaders decide which type of action they actually need.
| Decision | What remains intact | What changes | Best use case | Warning sign |
|---|---|---|---|---|
| Rate adjustment | Segments, packages, meter, billing process | List price, discount guidance, commit levels | Customers understand the offer and the unit of value | Sales still needs custom exceptions to close routine deals |
| Package revision | Core segment strategy and primary meter | Feature access, service levels, add-ons, plan boundaries | Buyers want different levels of capability or support | Customers buy the highest plan for one feature, then ignore the rest |
| Pricing revamp | Nothing is presumed correct | Segments, offer design, meter, rates, contracts, billing, migration | Growth, margin, and customer fit have moved out of alignment together | No one can explain why a customer pays what it pays |
The practical implication is straightforward: do not begin with the price sheet. Begin by deciding whether the price sheet is the symptom or the cause.
Pricing architecture ages. A company may keep the same model long after its customer base, product depth, or cost base has changed. The signals are often visible in operating data before they show up in an annual planning deck.
A useful leadership review scores each signal from zero to two. A total of six or more should trigger a formal revamp decision rather than a routine annual repricing.
A high score does not mean every element needs replacement. It does mean leaders should stop treating pricing as a sales enablement project. The root problem may sit in segmentation, product packaging, the billing unit, or the systems that connect them.
Several patterns deserve particular attention:
Your largest customers buy exceptions instead of offers. When every enterprise deal needs a custom order form, the company has not built an enterprise package. It has built a negotiating process.
Your lowest-price plan becomes the default for valuable customers. That pattern suggests the price fence between plans is weak. Customers see little reason to move up.
Your highest-usage accounts are your least profitable accounts. The problem may be an unpriced cost driver, such as data volume, transactions, support intensity, or compute.
Your buyers ask for a forecast before they agree to use the product. A forecast request can be healthy. Repeated confusion about what will be billed signals that the meter is too distant from a customer’s planning process.
The scoring table does not replace judgment. It forces the leadership team to distinguish a localized problem from a system-wide one.
Monetizely’s 5-Step Pricing Framework treats pricing as a chain of decisions rather than a choice of number. The sequence begins with Goals and Segmentation, then moves through Packaging, Pricing Metric, Price Points, and Operationalization. Each step narrows the next: business priorities and customer groups shape the offers; offers determine which unit can be charged for; the unit makes a price test meaningful; and the final design must work in contracts, product controls, billing, and invoices. The logic is developed in Monetizing Agentic AI[^1], but it applies equally to mature SaaS products whose existing model no longer reflects how customers buy.
Starting at step four is the common error. Leaders compare competitor prices, select a number, and then attempt to justify the package and meter around it. That process produces a price, but not a strategy.
The sequence explains why a revamp is demanding. Every shortcut shifts unresolved work into sales negotiations, customer success escalations, or finance reconciliations later.
Goals must be specific. “Grow ARR” is not enough because every pricing change seeks more revenue. A company may instead prioritize faster adoption in a new segment, higher gross margin, larger annual commitments, lower churn among mid-market customers, or better expansion from existing accounts. Two goals can coexist, but one must govern trade-offs.
Segmentation also requires more discipline than labels such as SMB, mid-market, and enterprise. A 500-person company buying a monitoring tool for a small engineering team may behave more like an SMB buyer than a global manufacturer buying the same tool for a regulated production environment. The segment is defined by the job, stakes, buying process, and willingness to pay - not only employee count.
Strong pricing models charge for the source of value customers can see
The pricing metric is often the hardest decision in a revamp because it changes the customer’s mental model of the product. A seat is familiar and predictable. A usage meter can follow value and cost more closely. An account fee can fit a platform that serves a whole business unit. None of those units is inherently superior.
Our view is that every SaaS company should select a primary meter that buyers can predict before purchase, monitor during use, and connect to business value after adoption. Secondary charges can be appropriate, but they should protect a clear cost driver or unlock a distinct use case. They should not compensate for uncertainty about what the product is worth.
Four established SaaS companies show the discipline behind that choice.
Company and public model What the model measures What it teaches a company considering a revamp Atlassian Jira Users, with monthly billing based on the exact number of users and annual billing based on the nearest user tier A seat remains effective when access and team adoption are the main sources of value, and when users can readily forecast the count. As of September 7, 2026, Jira also separates plans through automation, support, security, and administrative capabilities.[^3] HubSpot Marketing Hub Seats and marketing-contact capacity, with plan-level feature and onboarding differences One user count may not capture the economic scale of the product. As of September 7, 2026, HubSpot’s Marketing Hub combines seats with included marketing-contact levels, linking part of the price to the reachable audience rather than only to operators.[^4] Datadog Hosts, containers, events, metrics, and other monitored resources Usage pricing works when the activity is measurable, central to the product’s value, and close to the buyer’s operating reality. Datadog also distinguishes between stable usage and variable usage through commitment and hourly overage structures.[^5] Snowflake Compute credits, storage, and data transfer Deep consumption pricing fits products where customers directly control resource use and costs can vary materially with workload. As of September 7, 2026, Snowflake describes compute, storage, and transfer as separate elements of its consumption model.[^6] The lesson is not to copy any one company. Jira, HubSpot, Datadog, and Snowflake charge differently because the customer value and cost structure differ. A pricing revamp should reach the same level of clarity about the company’s own product.
A customer relationship platform, for example, should not adopt a host meter because Datadog uses one. A collaboration product should not move to credits merely because consumption pricing is fashionable. Buyers will accept a new unit only when it makes commercial sense in the work they already do.
Packaging is where strategic intent becomes visible to a customer. A good package answers a buyer’s practical questions: What can our team do? What support do we receive? What controls do we need? What happens as we grow?
Three package patterns recur in SaaS:
Market condition Package architecture Primary design aim Common failure Broad market with similar needs Simple plans with limited feature differences Speed and low buying friction Creating too many plans before customer needs truly diverge Distinct segments with predictable needs Tiered plans mapped to customer maturity, scale, or risk Clear upgrade paths Putting every advanced feature into one expensive tier Diverse use cases with different value drivers Core plan plus focused modules Higher fit for complex accounts Selling a collection of add-ons with no coherent base offer The critical test is whether each package maps to a real buying reason. Security, governance, advanced workflow controls, regional hosting, and premium support can justify a higher tier when they solve problems that matter to a defined segment. A random collection of features cannot.
HubSpot’s current Marketing Hub structure illustrates the point. Its public pricing separates starter, professional, and enterprise offers through included seats, contact capacity, features, and onboarding requirements. As of September 7, 2026, Professional starts with three Core Seats and 2,000 marketing contacts, while Enterprise includes five Core Seats and 10,000 marketing contacts.[^4] The design does more than charge a higher rate. It marks a transition from basic use toward larger-scale marketing operations.
Every company should pressure-test packages against three questions:
- Can a buyer explain why one plan exists without reading a feature matrix?
- Does each plan solve a distinct problem for a defined segment?
- Does moving up create more customer value than simply more product access?
If the answer to the third question is no, the company is likely charging for artificial scarcity. That may work briefly, but it rarely produces durable expansion.
A well-designed future model can still fail through a poor transition. Existing customers have contractual expectations, established budgets, and internal champions who defended the original purchase. A revamp must respect those realities without permanently preserving a model the company has decided to retire.
The following transition choices make the trade-offs explicit.
The synthesis is simple: grandfathering should protect commitments, not preserve confusion indefinitely.
Migration communication must describe what changes, why it changes, when it takes effect, and how the buyer can control spend. A customer who receives an unexplained invoice change will assume the company is extracting more value. A customer who sees a clearer path to scale, better fit, and predictable choices has a reason to engage.
Pricing governance keeps the new model from decaying on contact with the field
Pricing revamps fail when the launch ends. Sales then creates exceptions, product adds features without package rules, finance patches invoices manually, and customer success makes renewal promises outside the model. Within a year, the company has recreated the problem it set out to solve.
Governance does not require a large committee. It requires clear ownership and a regular operating rhythm. Product should own entitlement logic. Finance should own billing integrity and margin visibility. Sales should own field feedback and deal-quality data. A designated executive should resolve trade-offs when those functions disagree.
The leadership team should review a short set of evidence every quarter:
- Package mix by segment and sales channel
- Discount levels by package and deal size
- Expansion and churn by original package
- Gross margin by customer cohort and usage band
- Manual billing adjustments, credit requests, and invoice disputes
Those measures reveal whether the pricing model is doing what it was designed to do. A growing number of manual credits, for example, is not only a billing issue. It may signal that customers cannot predict their charges or that the package is missing a needed allowance.
A pricing revamp is justified when the old model no longer gives customers a fair, understandable path to buy and expand while giving the company a reliable path to grow. It should not be launched to create a short-term lift in list price alone.
The strongest SaaS pricing architectures make a visible choice. They identify the buyer groups that matter, create offers those buyers recognize, charge on a unit connected to value, set rates that serve a stated business goal, and build the systems needed to enforce the design. Complexity is warranted only when it reflects a real difference in customer need or cost.
Leaders should now take five concrete actions:
Set a two-year commercial destination. Decide what share of future ARR should come from each target segment, package, and primary meter before approving any new price card.
Give one executive authority to resolve pricing trade-offs. Product, finance, and sales should contribute evidence, but one accountable leader must decide when growth, margin, simplicity, and customer continuity conflict.
Create a standing pricing data set. Combine product use, contract terms, realized price, discounts, support intensity, cost to serve, and renewal outcome at the account level.
Make pricing changes part of product planning. Review package effects whenever the roadmap adds a major capability, changes implementation needs, or materially alters cost to serve.
Measure the cost of legacy complexity. Track the revenue, support work, billing effort, and approval time attached to old plans and exceptions. Retire what no longer earns its place.