Sales / deal desk

The Operating Partner's Pressure-Test for Price Increase Communications

Emily Ellis · 2025-10-06

A price increase is the fastest lever your portfolio company has to expand earnings before interest, taxes, depreciation and amortization (EBITDA) without adding headcount or acquiring new customers. But most operating teams approach it wrong. They set a number, send a form email, and hope for the best. Then they're surprised when customers escalate, churn spikes, and the VP of Sales starts offering exemptions to close deals.

The number is rarely the problem. The communication is almost always the problem.

The Revenue at Stake

A price increase of 8% across a $50M annual recurring revenue (ARR) base generates $4M in incremental annual revenue. At a 10x multiple, that's $40M in enterprise value, with near-zero incremental cost. The margin improvement flows almost entirely to EBITDA.

But a badly executed price increase that triggers 6% churn on the affected base costs you $3M in ARR before the increase revenue is even realized. The net EBITDA impact flips negative in year one, and you've damaged customer relationships that will take two years to rebuild.

The risk isn't the price increase itself. The risk is the communication cadence, the value narrative, and the exemption policy. Get all three right and you can increase prices annually with minimal disruption. Get them wrong once and your customer success (CS) team will spend two quarters doing relationship management instead of expansion.

The Working Model

Three steps your operating team should build into the price increase playbook before a single customer email goes out.

Step 1: Segment customers by churn risk before communication. Not all customers have the same price sensitivity or the same relationship depth. Before you communicate the increase, score every account on two dimensions: product dependency (how embedded is the product in their workflow?) and relationship strength (how often does your CS team have meaningful contact?). High dependency, strong relationship customers are your safest increases. Low dependency, weak relationship customers need a different treatment: either a smaller increase or a concurrent value conversation.

Step 2: Build the value narrative from the customer's perspective. Your customers don't care that your costs have gone up. They care about the return they're getting from your product. Your communication should lead with what's improved since their last renewal: new features shipped, support response time improvements, platform reliability gains, compliance certifications added. The price increase is the last sentence of the email, not the subject line.

Step 3: Set a clear exemption policy before communication begins. The moment your price increase communication goes out, your sales and CS teams will receive escalation calls. If you haven't set a clear policy for what exemptions are and aren't available, your reps will negotiate individually. Some customers will get exemptions others didn't. Your price increase will be inconsistently applied, which creates pricing precedent problems that follow you into the next cycle. Define the exemption criteria in advance: which segments, which contract sizes, and which situations qualify for a one-cycle hold.

Where the Plan Breaks

A project management software company at $28M ARR decided to execute its first price increase three years after acquisition. The operating team set a 12% increase across the board and tasked the CS team with communicating it via an automated email sequence two months before renewal.

The CS team wasn't prepared for the escalations. Forty percent of enterprise accounts called within a week. Reps made individual deals to avoid churn: some customers got the 12% increase, some got 6%, some got zero and a contract extension at the old price. By the time renewals cycled through, the realized average increase was 3.8%, not 12%.

Before: $28M ARR, plan for 12% price increase, no segmentation, no exemption policy, automated email communication.

After (restructured): Re-run of the same increase the following year with segmentation, a customer-specific value narrative, and a defined 6% cap on exemptions produced an average realized increase of 9.4% with 1.8% churn on the affected base. Incremental EBITDA of $2.5M against a plan of $2.6M.

Steps for This Quarter

Review your portfolio company's last renewal cycle and identify how many renewal conversations included a price increase discussion. If the answer is fewer than 20% of renewals, your CS team isn't treating renewals as a pricing event. Change that before the next cycle.

Assess Your Commercial Health to build your price increase communication framework.

Frequently Asked Questions

How much churn should a PE-backed software company expect from a price increase?

A well-structured price increase of 8-12% in a product with strong retention and clear value delivery typically produces churn rates of 2-4% among affected customers. The churn risk is significantly higher when the communication is poorly timed, lacks a clear value narrative, or arrives without advance notice. Companies that manage this well often find that the churn from a price increase is lower than their baseline annual churn rate.

When is the right time in a hold period to execute a price increase?

The best time is 12-18 months after acquisition, once your operating team has stabilized the business and can point to concrete product or service improvements delivered since close. Price increases executed in the first six months of a hold carry higher churn risk because the customer relationship hasn't been reset. Price increases attempted in the last six months before exit carry credibility risk in due diligence.

Find out where your commercial gaps are.

Take the Free Assessment →