Run an end-to-end pricing and packaging redesign for a live B2B SaaS product as a governed change project — from the mandate to reprice, through value-metric and tier design, willingness-to-pay validation, and a controlled migration of the existing base.
Establish why you are repricing now, who decides, and the guardrails the redesign must respect — so the project is a governed change, not a pricing committee free-for-all.
Name the triggers forcing a repricing, set quantified goals, and lock the non-negotiable guardrails before any design work starts.
Document the repricing triggers and the cost of inaction
A repricing is expensive and risky, so it must be justified by specific triggers, not a vague sense that you are leaving money on the table. The 2025 context is unusually…
Set quantified goals and the guardrail set
A repricing with no numeric target drifts into a feature-bundling debate. Convert the mandate into 2-3 quantified goals and an explicit guardrail set that bounds the design space,…
Stand up the pricing council and decision rights
Pricing dies in committee when nobody owns the call. Stand up a small pricing council with explicit decision rights using a RACI so the project moves at sprint pace instead of…
Frame the project as a time-boxed change initiative with a charter, a risk register, and a cadence that keeps it moving.
Write the repricing project charter
The charter is the contract between the council and the company. It freezes scope, timeline, and success criteria so that mid-project, when someone proposes adding a fourth tier…
Build the repricing risk register
Repricing failures are predictable, which means they are mitigable. Build a risk register up front so the council manages risks deliberately instead of discovering them in a churn…
Set the project cadence and stakeholder map
A repricing touches finance, product, sales, CS, legal, and billing — and any one of them can stall it. A clear operating cadence and a stakeholder map keep the dependencies…
Diagnose how the current model actually performs in the wild — where price and value have decoupled, and where revenue is leaking through discounts and legacy plans.
Map the current model as designed versus as sold, and find where the value metric has stopped tracking value.
Map current packaging as-designed vs. as-sold
The published price book and the deals that actually close are usually two different products. The first audit step is to reconcile design against reality across your full deal…
Diagnose value-metric mismatch
A value metric is the single measure that correlates with the value a customer receives — products with at least one grow 10-25% stronger through organic expansion. The diagnosis…
Benchmark against competitive pricing
Your pricing does not exist in a vacuum — buyers anchor on what peers charge. With B2B software prices up 11.4% in 2025 and peers re-rating 10-15%, a competitive benchmark tells…
Quantify the revenue draining out through discounting, grandfathered plans, and contract-usage gaps.
Quantify discounting and contract leakage
Subscription businesses lose 3-9% of revenue to leakage, varying by model: 2-4% for flat-rate, 3-6% for tiered, 4-9% for usage-based. At a 7x revenue multiple every $1 of annual…
Audit grandfathered and legacy plans
Legacy discounts are the most devious leak: aggressive early-adopter pricing meant to expire at renewal was never captured as structured data, so two years later that customer is…
Synthesize the leakage and opportunity baseline
The audit modules produce a lot of evidence; the council needs one baseline number the new model is accountable to beating. Consolidate packaging gaps, value-metric mismatch, and…
Design the new monetization model from the value metric outward: the metric, the Good/Better/Best tiers, the fences that separate them, and the add-ons that monetize expansion.
Select the value metric and shape the Good/Better/Best editions around how distinct segments actually use the product.
Select the new value metric
The value metric is the most consequential decision in the redesign — it precedes tiers, fences, and price levels. The 2025 Monetization Monitor shows outcome- and usage-based…
Design the Good/Better/Best tier architecture
Good/Better/Best (GBB) is packaging, not pricing: it describes how capabilities bundle into editions. The standard enterprise architecture is three to four editions with clear…
Define fences between tiers
Fences are the boundaries that keep customers from buying a cheaper tier than their willingness to pay justifies. A tier architecture without fences collapses — everyone buys…
Finalize the packaging logic and the add-on layer that monetizes expansion beyond the base tiers.
Design the add-on and overage layer
Add-ons monetize the customers who want more without forcing a full tier jump, and a usage rider captures growth automatically. The design goal is a clean base tier plus modular…
Assemble the new price book
The price book is where the redesign becomes operational: a single artifact Sales can quote from without inventing configurations. It consolidates the value metric, GBB tiers,…
Model the financial impact across scenarios, then validate willingness to pay with real research before committing price levels.
Model revenue, margin, and base impact across scenarios with sensitivity on the riskiest assumptions.
Build the repricing financial model
The financial model translates the design into a P&L story across scenarios. Model base, bull, and bear cases so the council sees the full distribution of outcomes, not a single…
Run sensitivity on key assumptions
A scenario model hides which assumptions actually drive the result. Sensitivity analysis isolates the two or three variables that swing the outcome, so the council knows exactly…
Model the impact on the existing base
The new-logo math is the easy part; the existing base is where repricings succeed or implode. Unprotected legacy increases trigger 10-15% churn spikes, so you must model, customer…
Validate willingness to pay and packaging preference with research before committing to price levels.
Run a Van Westendorp price sensitivity study
The Van Westendorp Price Sensitivity Meter (PSM), developed in 1976, uses four questions — too expensive, expensive but would consider, bargain, too cheap to trust — to map…
Validate packaging with conjoint and MaxDiff
Van Westendorp validates price; conjoint and MaxDiff validate packaging. The standard SaaS approach pairs MaxDiff (rank a long feature list by importance) with choice-based…
Validate demand with fake-door and closed-lost evidence
Surveys reveal stated preference; fake-door tests and closed-lost analysis reveal revealed preference. Before committing, validate that the new model attracts real clicks and…
Move the existing base onto the new model deliberately — cohorting, grandfathering policy, notice periods, and the customer communications that protect retention.
Decide grandfather-vs-migrate per cohort and design the phased rollout that limits churn.
Set grandfathering vs. forced-migration policy
Every existing customer needs a decision: grandfather (keep legacy pricing), time-limited protection (legacy holds for a defined window, commonly 12 months, then transitions), or…
Design the phased rollout and cohorting plan
Never migrate the whole base at once. The proven pattern is to roll out in stages — 10%, then 50%, then 100% — monitoring at each gate so a problem surfaces on a small cohort…
Build segmented notice, comms, and FAQs that explain the change and preserve trust.
Build the segmented communication plan
Documented communication plans cut pricing-change churn by up to 60%. The mechanism is segmentation: a grandfathered customer, a customer whose price drops, and a customer facing…
Prepare backlash and escalation playbook
The 2025 price surge produced real community backlash, and high-value accounts will escalate. A pre-staged playbook means the team responds calmly and consistently instead of…
Write the notice timeline and per-cohort sequencing
Surprise — not the increase itself — is the churn driver, so the notice timeline is as important as the message. Sequence communications so top accounts hear from a human before…
Equip Sales and CS to execute the change, launch the new model, and run the post-launch monitoring loop that locks in the gains.
Arm the revenue teams with calculators, objection handling, and save plays for the new model.
Build the value calculator and ROI tooling
Only 23% of pricing objections are truly about budget — the other 77% mask doubts about value. A value calculator that lets a prospect input their own numbers and see personalized…
Equip objection handling and save plays
The enablement gap is real — only 29% of enablement teams can tie programs to revenue. For a repricing, that means scripted, practiced responses to the predictable objections,…
Roll out discount governance and CPQ guardrails
The audit found discount drift leaking 1-3% of ARR; the redesign only holds if that drift cannot quietly rebuild. Encode the approved discount bands from the price book directly…
Execute a clean launch and run the monitoring loop that confirms the model hit its goals.
Run the launch go/no-go and billing readiness check
The most common avoidable failure is launching before the billing system can actually model the new plan — a risk flagged in the register. Run a formal go/no-go that confirms…
Stand up the post-launch monitoring dashboard
The sensitivity analysis named the assumptions that matter most — the monitoring dashboard watches exactly those, as leading indicators, so you catch a problem in week two, not at…
Run the optimization and continuous-pricing loop
Repricing is not a one-time event — best-in-class SaaS treats pricing as a standing cadence, not a project that ends at launch. The post-launch loop converts live evidence (the…
