Review grandfathered prices by customer cohort

A grandfathered price can mean a fixed rate for a contract term, a legacy package kept available indefinitely or a discount that renews under specified conditions. Those arrangements have different economics and different options for change. Begin with the actual customer terms and the communications that created the expectation.

Group customers by the promise they received, the package they use and the date their terms can be reviewed. Do not assume every old account belongs in one cohort. Some may have renewed at a higher price, expanded into a new tier or received a personal exception that was never recorded in the main pricing table.

Have the appropriate commercial or legal reviewer establish what changes are permitted and what notice is required. Finance can calculate alternatives, but a profitable model does not establish a right to change a customer's agreement. Keep proposed actions separate from approved customer communications.

For each cohort, collect recurring fees, usage charges, credits and discounts over a consistent period. Reconcile those amounts to the billing records before calculating average revenue. A list price field can overstate collections when longstanding credits or waived overages remain active.

Estimate the delivery resources that vary with the cohort: hosting, transactions, fulfillment, support time or account-specific work. Use the company's documented contribution definition and state what remains outside it. Shared product development and general overhead may still matter to company profitability even when the short-term cohort calculation excludes them.

The IRS's business-record guidance describes invoices, receipts and other supporting documents used to substantiate transactions. Preserve comparable support for this analysis, including the source period and treatment of refunds. A renewal decision based on untraceable averages is difficult to explain when a customer challenges the proposed change.

Suppose an illustrative legacy cohort has 100 customers paying $100 per month, for $10,000 of monthly revenue. Sixty customers cost $20 each to serve, thirty cost $60 each and ten cost $300 each under the selected direct-cost definition. Total direct cost is $6,000, leaving $4,000 of contribution.

The average looks acceptable, but the ten highest-cost customers generate $1,000 of revenue and consume $3,000 of direct cost. Raising every customer by the same amount would address that imbalance differently from changing usage allowances or charging for expensive optional work. The calculation suggests where to investigate; it does not prove that those customers should be removed.

Examine whether high cost is persistent, temporary or caused by a product defect. Charging more for avoidable support problems may damage a relationship without fixing the underlying cost. Likewise, a customer with unusual implementation needs this month may become inexpensive to serve after onboarding finishes.

Compare specific alternatives: maintain the price, increase it at a permitted renewal, offer a different package or introduce a charge for additional usage where the agreement allows. Show the expected customer count, revenue and delivery cost under each option. A higher nominal price can reduce total contribution if enough customers leave or if migration requires substantial support.

Use retention scenarios rather than a single confident forecast. In the hypothetical cohort, moving the monthly fee from $100 to $120 would produce $12,000 if all 100 customers stayed. If ten departed, revenue would be $10,800. Contribution depends on which customers leave and which costs disappear, so applying the same average cost to every departure can mislead.

Keep migration spending separate: billing changes, customer assistance, contract review and refunds can affect the first period. If the new package requires product work, confirm its readiness before including savings from features or controls that do not yet exist.

Management may choose to keep a price for a strategic customer, an early supporter or an account with an active service issue. Record the reason, financial effect, approving person and review date. A documented exception is easier to manage than an invisible discount that survives every later renewal.

Give customer-facing teams clear choices they can offer. If support can waive any charge indefinitely while finance models a universal price increase, the forecast will not match delivery. Define the duration and limit of any transition discount, and make sure the billing system can express it accurately.

Avoid measuring the project only by the number of customers moved. A rushed migration can create disputes, duplicate subscriptions or incorrect renewal dates. Use a controlled customer list and reconcile the new invoices against approved terms. The commercial goal should include correct billing and retained contribution after the change.

Compare actual retention, collected revenue, credits and service demand with the modeled scenarios. Identify customers who accepted new terms but have not yet been billed, and customers whose cancellation takes effect later. An early announcement response is incomplete evidence of the financial result.

Investigate departures by cohort and reason without claiming that every cancellation came from price. Some accounts would have left under the old terms. Retain a comparison period and note other changes, such as a product launch or an outage, that could affect the result. Where the evidence is weak, report the observed change and the limitation directly.

Finish by updating the authoritative pricing records and removing expired exceptions. Leave each remaining legacy account with an understood promise, a supported cost picture and a next review condition. That record gives future teams a usable basis for renewal without reopening the entire history of the pricing decision.