The Operator's Guide to Price Increase Communications

Price increases fail on communication, not on math. The number itself is rarely the problem. A 7% increase is received differently when it arrives with a generic email citing market conditions than when it arrives anchored to three specific product releases shipping in the same quarter.

This guide covers the communications framework that makes the increase stick.

What's at stake

At a $40M ARR portco, a 7% price increase represents $2.8M of annualized recurring revenue, net of churn. At near-100% incremental margin, that's $2.8M to EBITDA. The same increase, poorly communicated, typically produces 3-5% of net realized lift because discounting absorbs the rest and a portion of customers churn.

The difference between a well-communicated and a poorly-communicated increase is rarely less than 4 points of realized margin. Across a portfolio of 8 SaaS portcos, that difference routinely exceeds $15M of annual EBITDA.

The mistake isn't the increase. The mistake is treating communications as the thing the comms team handles at the end, rather than as the lever that determines whether the increase lands.

The framework

1. Anchor the increase to product velocity

Why it matters. Customers accept price increases that correspond to product improvement. They reject price increases that feel like rent collection.

What to do. Time the price increase to coincide with or immediately follow a meaningful product release. Name specific shipped features in the customer letter. Reference release notes the customer can verify.

Common failure mode. Citing "continued investment in the platform" without specifics. Customers hear that as marketing copy and discount it.

2. Tier the outreach by account value

Why it matters. A single communication strategy across a $2M customer and a $5K customer wastes effort on the long tail and under-services the top accounts. The top 20 accounts carry the churn risk.

What to do. For top 20 accounts: phone call from the CRO or CEO, prepared business case, in-person or video. For mid-tier: account manager call, personalized email follow-up. For long tail: templated email, clearly written.

Common failure mode. Sending the same templated email to the entire base. The long tail responds to templates. The top 20 respond to calls.

3. Lead with the value the customer already receives

Why it matters. Customers calculate price increases in terms of the value they perceive. If the letter leads with the price, the reader anchors on the cost. If the letter leads with a summary of value delivered in the last 12 months, the reader anchors on the value.

What to do. Structure the letter as: value delivered, value shipping next, price change, effective date. In that order.

Common failure mode. Leading with "effective January 1, your pricing will change." That opening guarantees a defensive read.

4. Train the sales team before the letter goes out

Why it matters. The letter creates awareness. The sales conversation decides whether the increase sticks. Untrained reps apologize for the price, which signals that the price is wrong.

What to do. Run two training sessions on objection handling. Provide reps with three specific data points (product investment, feature releases, platform improvements) they can reference. Rehearse the top five customer objections.

Common failure mode. Sending the letter without training. Reps improvise. They discount.

5. Tighten deal desk during the rollout

Why it matters. Price increases trigger a reflex in the sales team to discount harder to protect quota. Without tighter governance, the increase gets absorbed by new discounting.

What to do. Lower the deal desk approval threshold during the 90-day rollout window. Require CRO sign-off on any discount above 8% during that period. Report pocket price realization weekly.

Common failure mode. Running deal desk on the normal threshold. The net realized increase drops from 7% to 3%, and the operating partner blames the market instead of the governance.

6. Give enterprise customers procurement time

Why it matters. Enterprise customers need budget cycles to approve pricing changes. A 30-day notice at an enterprise customer guarantees escalation and disputes.

What to do. Provide 90-day notice to every enterprise customer. For annual renewals in Q4, notify in Q2 of the prior year. For multi-year contracts, respect the existing contract term and communicate the change for the next term.

Common failure mode. Applying SMB timelines to enterprise customers. A $500K ARR customer served a 30-day notice files a dispute. That dispute costs more than the increase.

7. Measure realization, not list

Why it matters. The list price increase is the announcement. The realized increase is the result. Those numbers diverge by 3-5 points in most rollouts.

What to do. Report pocket price realization before and after the rollout. Compare to list. Hold the CRO accountable for realization, not list change.

Common failure mode. Declaring victory on the list increase and never measuring realization. Six months later, the margin didn't appear.

Diagnostic questions

• Does your price increase letter name specific shipped product improvements?
• How much notice are you giving enterprise customers before the effective date?
• Who leads the conversation with your top 20 accounts?
• What is your deal desk approval threshold during the rollout window?
• Have your sales reps rehearsed the top five customer objections?
• What is your realized increase versus list increase historically?
• Does your pocket price realization get reported weekly during the rollout?

Immediate next steps

• Draft the value-first version of your next price increase letter, anchored to specific product releases
• Tier your account base and define communication approach for each tier
• Lower deal desk approval thresholds for the 90-day rollout window
• Schedule two rep training sessions on objection handling before the letter ships

Common mistakes

• Generic emails citing macro conditions. A $25M ARR portco sent a price increase letter citing "inflationary pressures." Churn doubled and negotiated discounts consumed 60% of the list increase.
• Short notice to enterprise accounts. A $45M ARR portco gave 30 days' notice to a $600K ARR customer. The resulting procurement dispute delayed renewal by five months and cost 12% of the contract in concessions.
• Untrained reps on the front line. A $30M ARR portco let reps improvise responses. Realized lift was 2.8% against a list increase of 7%.
• Running the rollout without tighter deal desk. A $55M ARR portco kept its normal 12% discount threshold during a rollout. Sales discounted harder. Realized lift dropped below 4%.

---

Run the free assessment or book a consultation to apply this framework to your specific situation.