Grandfathered Pricing: What Exactly Should Early Customers Keep?
Define what old customers keep, inspect dated Parseur and Buildern evidence, and calculate a legacy cohort's contribution without inventing revenue.
Grandfathered pricing means an existing customer cohort keeps specified older commercial terms after new terms are introduced. The difficult word is specified. Keeping a price does not automatically explain which usage limits, features, seats, support obligations, or upgrade rules remain attached to it.
For a small software business, the policy is an operating commitment. Write what survives, who qualifies, and what happens when an account changes. Then check whether you can deliver that promise at the old rate. Loyalty is a reason to preserve terms; it is not a substitute for knowing what they cost.
Contents
What does grandfathered pricing preserve?
It preserves the terms you explicitly identify for an eligible cohort. Separate the amount charged from the product entitlement and the conditions under which either changes.
Chargebee's glossary describes retaining older pricing for existing subscribers when prices change. To make that idea usable, record four things: the cohort cutoff, the billing amount and interval, the included entitlement, and the events that end or alter eligibility.
For example, “existing accounts keep their monthly price” leaves several unanswered questions. Does adding a teammate preserve the old seat rate? Does switching to annual billing count as a migration? Can someone cancel and return? Are new, expensive capabilities included?
These are policy design questions, not a universal contractual interpretation. Check the actual terms you already offered before changing them. The point is to prevent a friendly announcement from becoming several incompatible promises across billing, support, and the product.
An old plan identifier is useful only if its behavior still matches what the customer was told.
What do real legacy plans look like?
Published examples show that legacy cohorts can remain much cheaper than newly sold plans, while reported average contract values mix several generations of customers. Read each figure with its date and its definition.
In its official policy article, checked October 18, 2026, Parseur says some customers still pay US$9 per month for a discontinued 1,000-credit plan; the article describes the nearest present equivalent as US$129 per month. That is Parseur's own disclosure, not our independent billing audit. Its pricing page separately advertises a free tier of 20 pages per month, with one page equaling one credit and applicable VAT/GST excluded. The retrieved page displayed the free price as €0; do not mix currencies when comparing paid quotes.
In the Buildern founder interview, the founder says early customers retain lower prices. The conversation discusses approximately $2 million ARR and 300 customers while explaining movement toward higher annual contract values. It does not provide a current price list or prove legacy pricing caused retention.
Read the Buildern record for the original context before copying the policy.
How much does the old cohort contribute?
Calculate the cash contribution of the cohort before comparing it with a hypothetical new-price cohort. The gap to list price is not automatically money you could collect.
Here is an illustrative monthly scenario, not a report about Parseur or Buildern:
| Item | Assumption | Result |
|---|---|---|
| Legacy customers | 60 accounts at $20 | $1,200 billed |
| Direct servicing cost | $6 per account | $360 |
| Contribution before shared costs | $1,200 minus $360 | $840 |
| New-price comparison | Same 60 accounts at $30 | $1,800 billed |
| Nominal billing gap | $1,800 minus $1,200 | $600 |
The $600 assumes all sixty customers would accept the higher price. It excludes cancellations, failed payments, migration work, and changes in usage. The $840 still needs to support shared engineering, administration, and founder time.
Parseur's policy discussion explicitly separates the list-price gap from churn avoided. Keep that distinction in your worksheet. A cohort can be profitable at its old rate, unattractive after support costs, or strategically useful; those are different findings and need different evidence.
Which policy can you actually administer?
Choose the narrowest policy that matches your commitment and that your billing and access systems can consistently deliver. More exceptions mean more states to maintain.
You might preserve a rate indefinitely for a defined plan, preserve it until an explicitly stated transition date, or leave an old plan available while offering an optional new package. These are design choices, not interchangeable promises. Calling a policy permanent while quietly requiring migration later creates a problem an FAQ cannot repair.
Ahrefs' official plan-identification guide, dated September 3, 2026, illustrates why entitlement matters: its example contrasts a US$199 Standard subscription with a US$249 current Standard plan, while explaining differences between credit-based and newer plans. Equal plan names do not establish equal products. Treat that as a documentation example, not a recommendation to change vendors.
Test renewal, added usage, upgrades, cancellation, and reactivation against the promise. Verify invoice and product access together. If the old price renews correctly but the promised feature disappears, the policy has still failed.
What belongs in the customer explanation?
Tell the customer what stays, what changes, when it applies, and what choices require an explicit action. Use the terms that actually appear in the account and invoice.
A complete explanation should identify the affected plan, billing interval, preserved limits, eligibility rule, and contact route for discrepancies. If a new optional capability has a separate charge, explain that before the user enables it. If nothing changes for the existing account, say exactly which terms remain the same.
Do not copy another company's promise without its economics. The difference between Parseur's disclosed $9 legacy plan and its stated $129 nearest equivalent is striking, but the public article does not expose the service cost or usage distribution of that cohort. Its published statement establishes what it says it preserves, not what your business can afford.
Keep policy versions dated. Support should be able to locate the version a particular cohort received rather than reconstructing it from old marketing emails. This is ordinary product maintenance, closely related to the technical debt created by duplicated rules.
What should you inspect before borrowing this model?
Inspect service cost, customer expectations, and the actual upgrade path alongside revenue. A low legacy price is neither proof of generosity you should imitate nor proof of money being wasted.
In the Buildern interview, old customer pricing helps explain why a blended contract-value calculation differs from the direction of newer accounts. The source interview supports that distinction; it does not disclose a controlled price experiment. Ask for cohort-level evidence instead of assuming every customer pays the reported average.
For your own model, list the expensive actions a retained customer can trigger: compute, message delivery, storage, support, or manual implementation. Track these by plan where possible. If you cannot distinguish old and new accounts in your data, that uncertainty belongs in the decision.
Then connect the policy to real delivery. Use time to value to check whether customers receive the promised outcome and founder coverage to see what remains after operating costs. A recurring price is only one part of a sustainable recurring business.
Frequently asked questions
Is grandfathered pricing the same as a lifetime deal?
No. A legacy subscription can continue charging every month or year at an older rate. A lifetime deal usually concerns a one-time payment and a much longer access promise; its obligations need separate analysis.
Must old customers receive every new feature?
That depends on the terms promised to them. Define entitlements explicitly and check existing commitments. Do not assume either universal inclusion or automatic exclusion from the phrase “old price.”
Is the difference from current list price a loss?
Not necessarily. It is a comparison with a hypothetical alternative. Collectability, cancellations, service costs, and transition work determine whether a different policy would actually improve the outcome.
Can I use these published prices as today's quote?
Use the dated official links to check your own eligibility and billing interval. Legacy examples are not offers available to a new account, and dynamic pricing or taxes may change a payable quote.