How to Raise Prices Without Losing Customers
In practice that means churn holds near your baseline and the accounts that leave were already leaving. Your sponsor or your board expects a price increase this year, and the number is probably already in the plan. What is not in the plan is the churn you are afraid of, and the sales team that will discount the increase away before it reaches your P&L.
Why Most Price Increases Miss Their Target
The number is rarely the problem. A 7% increase and a 9% increase land the same way when the notice reads like a billing notification. Price increases fail because of communication, governance, and segmentation, not because of the price.
Three things go wrong, usually together. The message leads with your costs instead of the customer's outcomes, so the customer reads it as an extraction. Nobody wrote the exception policy before the announcement, so the deal desk writes it one escalation at a time. And the same increase goes to every account, undercharging the customers who would have absorbed more and pushing the fragile ones into a vendor review.
Then there is the lens problem. You probably measure the increase at list. The customer pays the pocket price: what is left after the renewal discount, the multi-year concession, and the services somebody waived to keep the peace. The pocket price is the only price that matters. Everything above it is a story you are telling yourself. Announce 12% and realize 3.8% at pocket, and you did not raise prices 12%. You raised them 3.8% and spent the political capital of 12%. That is what an automated notice and an unbriefed CS team produce: 40% of enterprise accounts call within a week, and reps end the calls by cutting individual deals, so some accounts pay the full increase, some pay half, and some get an extension at the old price. The price waterfall concept page has the mechanics.
Do the math for your own business. McKinsey's The Power of Pricing puts the operating profit lift from a 1% improvement in realized price at roughly 11% for the average company. On $80M of revenue, every point you announce and fail to realize is $800K of top line and a much larger share of your EBITDA. Sponsor-backed, the multiple compounds it: 8% on a $50M base is $4M of ARR at near-zero incremental cost and $40M of enterprise value at 10x. Run badly, the same 8% churns 6% of the base and costs $3M of ARR before a dollar of the increase arrives. That gap is real money, your money, and it goes missing between the announcement and the invoice.
The sequence below closes that gap: decide, segment, confirm you are ready, set, communicate, prepare, measure.
Decide Whether You Should Raise Prices at All
A sponsor request is a reason to look, not a reason to act. Simon-Kucher's State of Pricing 2025 found that only 65% of companies truly possess pricing power, so roughly one in three does not, which makes your sponsor's number a hypothesis about your pricing power, not a fact. Check four signals first. Two or more, and the increase is earned. One, and you are betting on goodwill. No read at all on where the ceiling sits for your segments? Willingness to pay research comes before this step.
Value delivered has grown
Translate the ship log since the last price change into outcomes the customer would name unprompted, not features from a release note. If the product does more for the same customer than it did at the last price, their reference price is out of date.
Usage or adoption is high
Depth, not logins. Integrations built, workflows that route through you, seats that expanded without a sales call. High adoption means high switching cost, and switching cost is what an increase is priced against.
Competitors have moved
If the two vendors you lose to most often raised list in the last 18 months, your price is now the cheap option in a category that just got more expensive. A signal, not a mandate. Confirm the buyer overlap before you follow.
Your cost basis has moved
The weakest of the four, because customers do not buy your costs. Rising cost justifies the increase to your CFO and never to the customer. Size the number with it, then keep it out of every sentence the customer reads. If margin is the real question, EBITDA margin improvement ranks a list increase against the levers that come before it.
Two situations where you fix packaging first
Your tiers are not differentiated
If two-thirds of your revenue sits in one tier and buyers cannot say why they would move up, a price increase raises the price of confusion. Fix the ladder, then reprice the rungs. Packaging beats pricing; the SaaS pricing strategy guide covers the rebuild, and good-better-best pricing covers the tier design.
Your value metric is disconnected from value
If you charge per seat and the customer's value grows with records processed, an increase pushes the seat price further from the thing they value. The objection writes itself. Change the metric first; the increase often disappears into the new model.
Segment Before You Set the Number
Segment by usage and value realized, not by size. Size tells you how much an account is worth to you. Usage and value realized tell you how much you are worth to them, which is what the increase is priced against. A $60K account with three integrations and a monthly executive readout will absorb more than a $400K account that uses one module and negotiated 30% off at signing.
The install base is where the money is. The High Alpha and OpenView SaaS Benchmarks Report puts roughly 60% of new ARR at companies above $50M ARR as coming from existing customers, so a price increase is an install-base event first. Build three cohorts from data you already hold: adoption depth, integrations, expansion, original discount, renewal history, champion stability.
Embedded: full increase
Deep adoption, integrated, expanding, clean renewals. They can take the full increase and most will not comment. The risk here is undercharging, not churn.
Moderate: standard increase with a narrative
Real usage, some negotiation history, one champion. They take a standard increase when it arrives with a narrative built from their outcomes and a CSM who can hold a commercial conversation. Without either, pushback becomes an exception.
Low adoption: intervene first, increase last
Sporadic use, no integrations, champion turnover, or a support history that reads like a slow goodbye. A price increase is the wrong commercial motion here. Intervene first: an adoption plan, a business review, a re-onboarding. Apply the increase last, if at all. Raising price on an account that has half-decided to leave does not lose you the increase. It loses you the account.
Grandfathering rules, written before the notice
Grandfathering is a discount with a longer name. Contract terms are pricing promises you make to yourself, so write the rules first:
- •Who qualifies: a named criterion, never a rep’s judgment
- •What is protected: a rate or a percentage cap, never “current pricing indefinitely”
- •When it expires: a date or a renewal, written into the notice
- •What ends it early: a tier change, a scope expansion, a change of control
Halvorsen Freight Software, 290 people, $71M ARR, 14 months into a hold. The sponsor asked for 8%. Cohort scoring put 46% of ARR in embedded accounts, 38% in moderate, 16% in low adoption. The team ran 11% on embedded, 7% on moderate, and held the low-adoption cohort for a 90-day adoption program before applying 4%. Announced: 8.4% blended. Realized at pocket after two quarters: 7.3%. Churn from the increase: under 1% of ARR, all low adoption. The blanket 8% they nearly sent would have realized less and lost more of the wrong accounts.
Internal Readiness Before the First Notice
Most revenue leaders ask how to communicate the increase. The question underneath it is whether the company is ready to raise prices at all. Communication is a craft problem. Readiness is an infrastructure problem, and solving the first without the second is how a defensible increase becomes an avoidable churn event.
The visible churn is the smaller cost. An account that feels blindsided runs an ROI review it had never run and a trust review it cannot unrun, and the ones that stay open every later renewal defensively: procurement joins calls the champion used to handle alone, and the expansion you modeled stops. That does not show up at 90 days. It shows up as NRR compressing over the next two or three years.
Notice length is not the lever either. Ninety days with no preparation produces the same escalations as thirty; the notice period helps only because of the preparation it makes room for. Five things are done before a date goes on the calendar:
- •A value inventory per cohort, in outcomes the customer would name unprompted; if you cannot produce one, run a quarter of outcome-tracking business reviews first
- •One completed sentence: “Our customers will accept this increase because [value delivered] has grown by [amount], and [named cohort] will find it most compelling”; blanks you cannot fill mean a billing event, not a strategy
- •Pricing documentation with no ambiguity about what the new price includes
- •The exception policy and the grandfathering rules from Step 2, written and signed off
- •Sales, CS, and support in the room from day one; a price change handed to marketing 48 hours before launch is a finance memo, not a commercial launch
Then the three-minute test: ask your most junior CSM to explain, without notes, why the new price is fair for one of their accounts. If they cannot, you are not ready, whatever the sponsor's deck says. Any item still open at day 30 moves the announcement date, not the standard.
Tessaro Workflow, $35M ARR, planned 15% across its mid-market base. Finance sent a billing notification 30 days out; the CS team found out the same day customers did. Within two weeks: 22 requests for executive calls, 14 for pricing holds, 6 RFPs. With no data and no script, CSMs defaulted to concessions, and the increase realized at 6%. Eighteen months later the same 15% went out behind 90 days of preparation and held 96% of the book at the full rate. Same number. Different starting point.
Set the Increase and the Glidepath
One increase or phased
One increase when the value story is strong and the base is mostly embedded: a single, well-argued step is easier to defend than three small ones. Phased when you are correcting years of no increases. A 25% correction in one step breaks the fairness norm no matter how good the product got, because, as Kahneman's Thinking, Fast and Slow explains, customers judge a new price against a reference point and losses against it loom larger than equivalent gains. Two or three steps over 18 to 24 months, each tied to a release, move the reference point without tripping the alarm. When prices feel expensive covers the behavioral ceiling.
Anchor to product velocity
Announce in the same window as a meaningful release, and name it in the notice, so the customer judges the increase against the product they use today rather than the one they bought three years ago. Nothing shipping in the window? That is a timing problem, not a pricing problem. Move the date. Two weeks' notice on an 18% increase is the case in the volatile-market section below: the price was justifiable and the sequencing destroyed it.
Write the exception policy before the announcement
Every exception you grant after the announcement is a precedent, and your reps will learn the precedent faster than the script. The policy answers four questions: who can grant an exception, under what documented condition, up to what amount, and what the customer gives in return. Trade the discount: a lower step for a multi-year term, a removed termination-for-convenience clause, or a tier upgrade. A concession with nothing coming back is not a negotiation. It is a rollback with paperwork.
The discount authority matrix protects the increase from your own reps
Discounting is usually a symptom, and it flares during a price increase because reps are paid to protect renewals and the fastest way to do that is to give the increase back. Set bands, not caps: the reason a discount is allowed, the range, the approver, the sunset date. Tighten the bands during the window. Anything above band routes to a named leader with a 48-hour service level, and the exception log is reviewed weekly. The discount governance guide has the full band and lane design, and the deal desk page covers the routing and the service level.
Raising Prices in a Flat or Volatile Market
In a flat economy your customers are under the same margin pressure you are, their procurement teams have been told to find savings, and an 8% increase landing without context is an invitation to reopen a competitive bid. Volatility does not create the pricing problem. Sequencing does. Four adjustments.
The fairness test
Customers apply a fairness test to every price change, and the research Thaler describes in Misbehaving is consistent: passing through a cost the customer can see reads as fair; exploiting a captive position reads as extraction. The rule in Step 4 below stands, costs stay out of the notice, with one exception: a visible shock that hit your whole category, where one sentence naming the driver passes the test. Never show the data, never ask for sympathy. And if your rationale sounds like “we have been underpriced relative to the market,” rewrite it: it tells the customer everyone else overcharged them and you are correcting it at their expense.
Sequence it before the invoice changes
Announce before the billing change, never on it. Add something alongside the increase that the repriced cohort has asked for, an early roadmap feature, a longer support commitment, a services credit, and keep it only if they would have paid for it separately. Then give long-tenured accounts 60 to 90 days to renew at current rates on a longer term. That turns the accounts most likely to expect special treatment into advocates, and it is fairness that scales rather than an exemption that compounds.
Sableridge Supply Chain Software, $22M ARR, raised 18% across the board while its customers' own freight costs were spiking. The notice went by email two weeks before billing: no window, no addition, no rationale. Quarterly churn went from 6.2% to 14.8% and NPS from 47 to 29. The next quarter went to reacquiring churned accounts at $1.3M of CAC against $1.1M of new ARR from the increase. A later competitive review showed 18% was justifiable. The price was right. The sequence cost more than it earned.
Trade the discount, do not waive it
When a powerful buyer refuses the increase, the untrained rep waives it, which tells the buyer your price has no floor. Trade instead, and every trade has two legs: a 12-month hold for a two-year extension with no termination for convenience; the current rate on contracted seats for automatic billing on every seat above them; a one-time hold for a public reference. You give on price and take something structural, and any account above 2% of revenue is negotiated by a named executive, not the account manager paid on the renewal.
CPI escalators: the increase you never have to announce
Contract terms are pricing promises you make to yourself, so every new contract from now on carries a 3 to 5% annual adjustment tied to CPI or a fixed rate, whichever is higher. The increase becomes contractually expected rather than negotiated fresh, margin is protected against inflation without a project, and a sophisticated buyer reads governed pricing. Retrofitting escalators into the installed base is hard. Writing them into new paper costs nothing and compounds over a hold.
Communicate It
Notice windows first. Treat these as planning rules, not statistics. Enterprise procurement needs 60 to 90 days to route a budget change through finance; 90 is the safer planning rule. Mid-market needs 60. SMB needs 30. Fourteen days' notice to an enterprise account produces an escalation, not a decision, because objecting is all procurement can do in fourteen days. Announce right after a quarter closes with the effective date at the start of the next one. The white paper 8% Approved, 2% Realized goes deep on this layer.
Inside the window, stage three touches rather than one notice: a value recap from the CSM at 90 days, the formal notice at 60 that references it, and a renewal conversation from the account owner at 30. Fenwick Analytics (illustrative), $18M ARR, sent its first 10% increase as one automated email 45 days out and churned 19% of the cohort, $980K captured against $1.7M lost. The same 10% the next year, behind three touches and a written concession protocol, churned 4% and netted $1.3M.
The message structure
Value first
What this customer has received since the last price point, in outcomes, ideally with their own numbers. Value first, price second, justification never. Arbor Content Systems (illustrative), $19M ARR, sent the same 60-day CEO email citing platform investment costs through three increases and churned 9%, 11%, and 10%, calling it average. Segmented, value-led notices on the same percentage produced 4.3%.
What is changing
The new rate, stated plainly, as a fact. One sentence. No hedging, no “modest.”
When
The effective date and how it maps to their renewal.
What stays the same
Contract terms, the support model, the things they were quietly worried about losing. This paragraph prevents half the pushback.
Tiered outreach by account value
Top 20% of ARR: a call, then the letter
The executive who owns the relationship calls before anything arrives in writing. The call is a statement, not a request. The written notice follows within days.
The middle: a personal email and an offer to talk
From the account manager, not a marketing tool. The four paragraphs above, ending with a named person and a date.
The long tail: a template that sounds like a person
A notice that reads like a billing system generates churn a human-sounding note would have avoided. Spend the thirty minutes.
Whatever the tier, the notice goes to the champion with finance copied, never the other way round; the billing contact's job is to say no. Marlowe Enterprise Software (illustrative), $47M ARR, sent a 9% notice from the CFO to customer finance contacts three weeks out, citing operating costs: 31 escalations in a week, the full 9% on 58% of the base, flat renewals for 28%, and 14% churned. Redesigned with 90 days' notice, a value case per account, and a trained CS team, the next cohort landed 8.5% with two escalations.
Which conversation each account needs is already in your CRM. The blanket notice tax is the deeper read on messaging: five signals that predict whether an account will accept, push back, or quietly open a vendor review.
When a customer pushes back
Acknowledge, restate value, hold, offer a trade. “I understand. Here is what has changed for your team since the last price. The new rate stands. If timing is the problem, we can look at a multi-year term at a lower step.” Then stop talking. The first person to fill the silence usually concedes.
What never goes in the notice or the call
No apology: it signals the price is wrong, and the customer negotiates the apology instead of the number. No costs: your inflation is not their problem, and “rising costs” invites a request to see them. No pre-concession: “let us know if this is a problem” invites one.
Prepare Sales and CS Before the Customer Hears a Word
Your message lands on your team before it lands on your customers, and your team is more afraid of it. Jeb Blount's Selling the Price Increase is built on that observation: reps fear the conversation more than customers fear the increase. Untrained, they delay the notice, soften the number, and hint that an exception is available. Enablement is the difference between a price increase and a price suggestion.
Two weeks before the first customer hears anything, every rep and CSM gets the value narrative by cohort, a value summary for their top accounts, the script, the objection playbook, the exception policy, and a rehearsal on the three hardest accounts on their list. If they cannot hold the line in a room with you, they will not hold it on the phone.
The objection playbook
- •“We did not budget for this” is a timing objection: point to the notice window, then trade a lower step for a longer term
- •“Your competitor is cheaper” is a switching-cost conversation: what the move costs them in rebuilt workflows and retraining, not what the competitor charges
- •“We are not using half of it” is an adoption conversation that belonged before the notice: route it to CS, do not discount your way out
- •“We will have to go to RFP” is a test: acknowledge it without flinching and ask what they would need to avoid one
The escalation path
Rep to manager to deal desk to the executive who owns the relationship, with a time limit at each step. Any account above 2% of revenue goes straight to the executive tier: a churn event at that size is an EBITDA event, not a sales event.
Comp alignment
Deal governance protects margin; sales comp alignment keeps it. If reps are paid on renewal rate or bookings, every point of the increase is headroom they can give back at no cost to themselves. During the window, tie a component of variable comp to pocket price realization against the announced increase, by account, and review it weekly by rep. The reps who discount through the increase are the ones who need coaching. Sales compensation alignment covers the plan design, clawbacks included. 8% Approved, 2% Realized covers why the deal desk threshold tightens, not loosens, during the rollout.
Measure It at Pocket Price
Announced is not realized. Five numbers, tracked from the day the first notice goes out:
- •Realized versus announced increase, at pocket price, by cohort and by rep
- •Churn and downgrades by cohort at 30, 60, and 90 days, and again at the next renewal
- •Discount rate drift: the average discount by cohort before, during, and after the window
- •Exception rate: the share of accounts granted any concession, and its average size
- •The pocket price waterfall before and after, on comparable renewal samples
The waterfall is the instrument. Marn and Rosiello introduced the pocket price waterfall in “Managing Price, Gaining Profit” in the Harvard Business Review in 1992, and it is still the cleanest way to see where an increase went. Run it on your last 50 to 100 renewals as a baseline, then on the renewals that close after the notice. If list moved up 8 points and pocket moved up 3, the other 5 sit in a waterfall category with a name, and the name tells you whether the fix is a script, a band, or a rep. The pocket price waterfall guide shows how to build it by channel.
The four-component ROI, built before you set the percentage
Immediate churn and incremental ARR are two of four components. The other two are where an increase quietly goes negative:
- •Incremental ARR: the book at the new rate minus the starting book, after expected churn by cohort
- •Churn cost: ARR lost plus the CAC to replace it; ten $50K accounts at a $15K CAC is $650K gone, not $500K
- •Process cost: executive, CS, finance, and sales time on the program at loaded rates
- •Expansion impact: the expansion rate in the two quarters after the window against the two before; a slowdown here usually costs more than the churn did
Set the net target before the percentage. If the program costs $80K and you want it back five times over, you need $400K of net new value, which at $20M ARR is a 2% net realized increase after churn and concessions. Run the model at several percentages and it often shows a 5% increase with 4% churn and few concessions beating a 15% increase with 12% churn and a deal desk full of exceptions. Report the 90-day result to the board and keep the 18-month result for yourself; that is the number that says whether to do it again.
How to read the results
Realized within a point of announced, churn flat to baseline, discount rate flat: you are done. Realized well below announced with churn flat: a governance problem, and your reps are giving it back. Churn up in the embedded cohort: a communication problem, so re-read your own notice as a customer. Churn up in the low-adoption cohort only: expected, and probably cheaper than keeping them.
When to pause
Pause the rollout for unaffected segments if churn in any cohort runs above your baseline within the first 30 days, or if exception requests exceed the share you planned for. A pause is not a rollback. Rolling back for accounts that already accepted teaches the whole base that accepting was the wrong move. Fix the script, the tier, or the timing, then resume.
Watch the slow leak too. An increase can produce acceptable churn, a satisfied board, and a quietly compressing NRR because expansion stopped. Failure case five below is what that looks like on a P&L, and the net revenue retention guide covers how to decompose it once you see it.
Five Ways This Playbook Fails
I have seen each of these more than once and have made at least one of them myself. The names are invented. The patterns are not.
1. The blanket, cost-justified increase
The approach. Meridian Field Services, 240 people, $58M ARR, eleven months post-close. The sponsor asked for 9%. The CFO sent one email to every account, 30 days out, explaining that infrastructure and labor costs had risen.
Where it broke. Enterprise procurement could not route a budget change in 30 days, so it escalated instead. Low-adoption accounts, which nobody had scored, took the email as the prompt to run the evaluation they had been putting off. The three largest accounts asked to see the cost data.
Consequences. Announced 9%. Realized 3.1% at pocket after two quarters. $2.6M of ARR churned or downgraded within 90 days, most of it already at risk. The deal desk processed more than 60 exceptions in a quarter planned for none.
The corrected approach. Score the base first, hold the low-adoption cohort, give enterprise 90 days, and lead with value. The same 9% on the embedded and moderate cohorts alone would have realized more with a fraction of the churn.
2. Usage segmentation on a product where low usage is the point
The approach. Corbett Compliance, 130 people, $34M ARR, sells audit-readiness software to regulated manufacturers. The team segmented by login depth and feature adoption, exactly as written above.
Where it broke. The product is used heavily for six weeks a year. The stickiest customers, whose auditors ask for Corbett's reports by name, showed the lowest login counts. The model tagged them as low adoption and held them back, then pushed hardest on frequent users who were quietly evaluating a competitor.
Consequences. Announced 8%, realized 4.7%. The held-back cohort was 31% of ARR and would have absorbed the full increase without comment. The cohort scored as embedded produced two of the three churn events.
The corrected approach. Segment on value realized: outcomes delivered, integration depth, renewal history, champion stability. Usage is a proxy, and you check the proxy against the product's real rhythm before you score anything.
3. Grandfathering with no expiry and no exception policy
The approach. Northlake Revenue Software, $88M ARR, raised list 12% and grandfathered “strategic accounts” at current pricing, with the definition of strategic left to the reps.
Where it broke. No expiry, no criterion, no trade. Within two quarters, 44% of ARR was strategic. New customers paid 12% more than old ones for the same product, and reps closed new logos by quietly promising the legacy rate at first renewal.
Consequences. Realized 2.9% on a 12% announcement. At exit three years later, the buyer's diligence team found two price books, discounted the multiple for revenue quality, and put the cleanup in their own 100-day plan. The sponsor paid twice: once in lost realization, once in the multiple.
The corrected approach. A named criterion, a written expiry, and a trade for every grandfathered account. Exception authority in a matrix, not in a rep's judgment. And a list price that is the price: if half the base does not pay it, it is not the list.
4. The good notice on an unbriefed team
The approach. Pellman Scheduling, 160 people, $28M ARR, announced 12% with six weeks' notice and a well-written CEO email: specific product improvements, a clear timeline, the four paragraphs from Step 4 in order.
Where it broke. In week two customers called their CSMs, who had not been briefed. Answers ranged from “let me find out” to “yes, prices went up, not sure why.” Three of the top ten accounts by ARR requested formal business reviews.
Consequences. Two of the three reviews ended in downgrades worth $340K combined. The email was fine. It landed on infrastructure that could not carry it.
The corrected approach. The readiness gate. A 60-minute CS workshop four to six weeks out on why the price is fair, the outcome data by account type, what is and is not on the table, and the escalation path, then each CSM tested individually before the first notice.
5. The increase that hit its churn target and lost money
The approach. Kestrel People Systems, $32M ARR, sponsor-backed, ran a 10% increase by the book and reported 5.2% churn against an 8% target. The board was satisfied.
Where it broke. Eighteen months later NRR had fallen from 112% to 96%. The accounts that stayed were less active in the product. Four of the ten largest cut license counts at renewal; three declined modules they had been evaluating when the notice arrived. Nobody was measuring expansion, so nobody saw it stop.
Consequences. Roughly $1.8M of expansion ARR that should have been captured was not. The 18-month ROI of a “successful” increase was negative.
The corrected approach. The four-component model from Step 6, built before the percentage was set, and a 90-day, six-month, and 18-month review. Accounts that cut usage or opened a vendor evaluation in the 60 days after the notice are the leading indicator of delayed churn; risk-weight them into the model instead of waiting for the renewal.
The Notice Outline and the 30/60/90 Checklist
The price increase notice, paragraph by paragraph
Put the change and the date in the subject line. “Your [Product] pricing from [date]” beats “Important account update.” Nobody opens the second one calmly.
Value delivered. Two or three things the customer's team can do now that they could not at the last price, in their language and their numbers.
What is changing. The new rate or percentage, the effective date, and how it maps to their renewal. Stated as fact.
What stays the same. Contract terms, support, the integrations they depend on. Name the worries before they have to ask.
What happens next. Who will call them, when, and how to reach that person. Signed by someone the customer knows.
The 30/60/90 checklist
Days 1 to 30 decide, segment, and pass the readiness gate; nothing reaches a customer. Days 31 to 60 prepare: value reviews with at-risk accounts, which are not pre-announcements, and the enablement in Step 5. Days 61 to 90 announce and hold, in waves by cohort rather than by renewal date, embedded accounts first, so their renewals at the new rate are the reference when the moderate cohort pushes back.
- 1.Confirm at least two of the four signals and write the value narrative by cohort
- 2.Score every account on the six cohort signals
- 3.Set the increase by cohort; choose one step or a glidepath tied to releases
- 4.Write the exception policy, the grandfathering rules with expiry, and the discount authority matrix
- 5.Run the pocket price waterfall on the last 50 to 100 renewals as the baseline
- 6.Build the four-component ROI model and set the net target before the percentage is final
- 7.Build value summaries for the top 20% of ARR; start the intervention on the low-adoption cohort
- 8.Train reps and CSMs on the script, the objections, and the escalation path, then rehearse
- 9.Tie a component of variable comp to realized price for the window
- 10.Draft the notice by tier; have someone outside sales read it as a customer
- 11.Executive calls to the top 20% of ARR, then the written notice within days; personal emails to the middle, the template to the long tail
- 12.Weekly exception log review with commercial leadership present
- 13.Track the five numbers at 30, 60, and 90 days, rerun the waterfall, and decide: hold, adjust, or pause
Company names and figures in worked examples are illustrative.
Raising Prices Without Losing Customers: Common Questions
How much notice should you give B2B customers before a price increase?
What has to be ready internally before you announce a price increase?
Should you raise prices for existing customers or only new ones?
How do you raise prices on existing customers without churn?
What percentage price increase is reasonable?
Should a price increase be announced by email or by phone?
How do you handle a customer who threatens to leave over a price increase?
How do you measure whether a price increase worked?
Where Each Layer of the Playbook Goes Deeper
The blanket notice tax →
Five signals already in your CRM that predict whether an account accepts, pushes back, or opens a vendor review
8% Approved, 2% Realized →
The communication layer in depth: where an approved increase goes between the board deck and the invoice
The 100-day pricing playbook →
Where the increase sits in a post-close plan, and what to fix before it
The pocket price waterfall →
Build the instrument that shows which category the missing points went into
Discount governance for B2B SaaS →
Bands, lanes, approvers, and the exception log that protects the increase from your own reps
Sales compensation alignment →
Why a rep paid on renewals gives the increase back, and what to pay on instead
Price waterfall →
The concept page: list to invoice to pocket, and the leaks between them
Pricing diagnostic →
How commercial maturity is scored, and what a price increase reveals about yours
Your number is in the plan. Bring the whole sequence.
On the call, you bring your pricing page and your last 20 deals. In 15 minutes you leave with the one fix that matters most to your increase plan. If you want to see the gaps first, start with the readiness score.