Price increases need notice and a response window

What it is

Raising the next-period price of a live subscription requires notice before the new price hits: old price, new price, effective date, and a window to cancel, downgrade, or lock the old rate. It is not trial-to-paid (zero to list). It is not a routine renewal reminder (same price, another capture). The contract term being changed is price.

Why it happens

People budget from the signup price. A raise that appears only on the next statement feels like a unilateral rewrite. Law often requires advance notice, but notice without the new price or a completable cancel is a fake window. Raises also hide as “plan renamed + new SKU,” which does not look like a raise until recon. The window must outlast reading mail and deciding, and it must live in-product, not depend on that one message still sitting in the inbox. If price-lock or grandfathering exists, it should appear as a choice, not a support oral.

Studying it

Change next-period price on an active sub. Compare: change on bill day, mail without new price, mail + in-app with old/new/date + cancel. Watch cancel, downgrade, dispute.

Independent variables: lead, old and new side by side, cancel or downgrade completable in the window, disguised as a new plan. Dependent variables: management before effective date, chargeback after, restating new price and date.

Do not treat “revenue up after the raise” as notice success. Measure informed choice, not short-run ARPU.

Where it stops holding

Tax or rail-fee pass-throughs that local law allows immediately should still be told as soon as possible; the window may be shorter than a commercial raise. Enterprise contracts follow addenda, not consumer mail. Price drops usually need no equal window, but a prepaid period should not be clawed back. Per-seat pricing must say whether unit or total rose.

Applying it

• Before effective date, send and pin on the subscription page: old price, new price, date, cancel and optional downgrade.
• Do not silent-migrate a raise as a new SKU; migration equals a raise notice.
• Cancel in the window keeps current-period benefits; do not shut off service the moment the notice goes out.
• Verify by raising next-period price on a test sub: from the notice alone, people state from which day, how much, how to cancel. No new price, or cancel only after the date, fails the window.

Related

• Within the group: H7.14.1 Warn before trial converts to paid · H7.14.3 Cancelled subscriptions keep remaining period benefits · H7.14.4 Multiple subscriptions need one view of dates and amounts
• Adjacent: H7.08 Subscriptions and cancellation · H7.03 Price transparency · O4.03 Dark patterns in subscribe and cancel
• Search terms: price increase notice · grandfathering · subscription repricing