Repricing Legacy Accounts Without Blowing Up the Renewal

Legacy pricing usually isn't a mistake, it's the residue of decisions that made sense at the time: an early customer who took a risk on you before you had a track record, a discount given to close a logo you needed for credibility, or a price point set years before your product had the features it does now. None of that is a reason to apologize for raising it. It is a reason to be deliberate about how, since the account has had years to build an expectation around what they pay.

Before any renewal conversation, have someone actually reread the original agreement, not just the current invoice. Some legacy contracts include a price cap on renewal increases, often tied to a formula like inflation plus a fixed percentage, and violating that cap is a contract breach regardless of how reasonable the new price seems. Others require a minimum notice period before a price change takes effect, sometimes measured in weeks ahead of the renewal date.

Route the original document through your contract system, using something like Foxit eSign's stored records, to confirm you're actually reading the final signed version and not an earlier draft that got amended before signature.

Moving a legacy account straight to current list price in a single renewal is the single most common way this goes wrong. Even when the new number is fair relative to what new customers pay, the size of the jump, not the destination, is what triggers a churn conversation or an angry escalation to your own leadership. Phase it instead, over two or three renewal cycles, with each step communicated well ahead of the invoice. A customer who sees a clear glide path can plan for it. A customer who sees a shock increase starts shopping alternatives out of reflex, even if they'd have accepted the same destination gradually.

For example, a long-standing account pays far below what a new customer with the same footprint would pay today. Rather than moving it to list price at once, the CSM proposes a first step at this renewal, describes the next step a year ahead, and points to features the account has not adopted yet. The customer's budget owner can now plan for the change and explain it internally. If the customer pushes back on the first step, the team can hold the second until the first has settled, which keeps the relationship intact while the price still moves toward where it should be.

A price increase with no explanation reads as opportunistic, even when it's overdue. Tie the conversation to something concrete: features shipped since the account signed that they aren't using yet, usage growth that's moved them into a different pricing tier under your current model, or a direct comparison to what a new customer with the same footprint pays today. The goal isn't to justify every dollar. It's to give the customer's own internal budget approver a reason to say yes that isn't just that the vendor decided to charge more.

A legacy repricing should never arrive as a system-generated invoice change with no human context. Loop in the account's CSM or AM early, since they know whether this is a healthy, expanding relationship that can absorb an increase or a fragile one that needs a lighter touch and more time. Run the renewal packet through a standard checklist, something like Process Street, that confirms the contract's cap and notice terms were checked, the increase was phased if needed, and the relationship owner signed off before the customer sees a new number.

Finance and revenue operations should also see the plan before it goes out, since they're the ones who'll field the question later if the increase gets escalated or if a similar account asks why their own price hasn't moved. A repricing that only the CSM knew about tends to get renegotiated away the first time someone above them pushes back.

Before the customer sees a new number, confirm that:

• Someone has reread the final signed agreement for any renewal price cap and minimum notice period.
• The increase is phased over more than one renewal cycle if the jump would otherwise be large.
• The conversation ties to concrete value, such as shipped features, usage growth, or what a comparable new customer pays.
• The CSM or AM who owns the relationship has signed off and will deliver the news.
• Finance and revenue operations have seen the plan and can answer questions if it gets escalated.