Identify which clients are affected
Separate new sales from existing subscriptions. A changed price on a landing page does not by itself describe what happens to an existing client’s arrangement. Record the current plan version, proposed version, affected group and intended date. Consult the applicable agreement and qualified advice when necessary; this operational checklist does not establish a legal right to change a price.
Explain the reason in concrete terms
A useful explanation identifies the changed scope or cost basis and the client’s available choices. Avoid disguising a price increase as a harmless settings update. In a fictional example, adding a separately supported feature might justify a new package for future clients while existing clients retain their earlier scope. That decision should be explicit rather than inferred from a product-plan label.
Rehearse the transition
Check the billing object, access configuration and communication record for one authorized test case before making a wider change. Determine whether an old price remains active and how a scheduled transition is represented. Stripe subscription documentation illustrates why billing states and lifecycle events matter; it does not guarantee identical behavior in every connected HighLevel configuration. Verify your actual arrangement.
Keep a recoverable history
Preserve the prior plan description and the evidence of any accepted change. Record the effective date and a way to investigate an unexpected invoice. Do not delete an old price or relationship merely to tidy the interface while clients still depend on it. If the required behavior is uncertain, hold the transition and continue servicing the existing arrangement until the specific question is resolved. Prepare a transition table separating existing clients, new clients and exceptions. Review each group against its actual arrangement before assuming a single global price update is appropriate for the entire book of business.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Stripe subscription lifecycle — Merchant documentation · docs.stripe.com · Merchant-controlled · checked 2026-09-27
- HighLevel pricing — Merchant documentation · gohighlevel.com · Merchant-controlled · checked 2026-09-27