Expansion
Run it yourself
Gates upgrade prompts by lifecycle stage and behavior, because 41 percent of upgrades happen in month zero and the timing rules invert outside that window.
41 percent of upgrades happen in month 0
upgrade-timing analysis across a 110M+-subscription dataset
Validated against propensity-matched comparison groups.
How we grade evidence →Threshold trigger · Edition 1 · June 2026
Upgrades are not spread evenly across a subscription’s life: 41 percent of them happen in month zero, while the subscriber is still sizing the product against their problem. The behaviors that predict an upgrade in that first month read differently afterward. Outside the window, the timing rules invert, and a prompt that converts a week-two subscriber gets ignored at month six.
This tactic gates every upgrade prompt by lifecycle stage and behavior together. Rather than one upgrade playbook for everyone, it applies the month-zero rules inside the month-zero window and the post-window rules everywhere else, so the prompt appears only when the rules say this subscriber, at this stage, is in an upgrade posture.
Inside month zero, the tactic watches for early expansion behavior (plan-limit exploration, billing-page visits, advanced feature usage) and shows the prompt in-app while the subscriber’s plan decision is still live. The first month is the dense part of the distribution, and the tactic treats it as prime upgrade territory rather than a no-pitch grace period.
Outside the window, the bar rises. The tactic requires the post-window behavioral signals before any prompt fires, because the same surface-level activity no longer carries the same meaning. The result is fewer prompts later in life, each with a much better claim to the subscriber’s attention.
The 41 percent month-zero concentration comes from upgrade-timing analysis across 110M+-subscriptions, a structural feature of how subscribers buy rather than one product’s quirk. The window where plans are still being decided is where a plurality of upgrade decisions land.
The case for precision is what the rest of the data shows: among subscribers who change plans at all, downgrades outnumber upgrades nearly two to one. Plan changes are not a one-way escalator, which is why prompts blasted on a calendar are wasteful. The tactic exists to put the upgrade question in front of the subscribers and moments where the answer is plausibly yes.
In production, the tactic tracks each subscriber’s lifecycle stage, applies the matching rule set, and resolves prompt timing per subscriber. Acceptance applies the plan change in the billing provider. A dismissal feeds back into the rules as evidence the gate fired early.
Guardrails keep the prompt scarce: hard frequency caps, automatic suppression around any save or recovery activity, and a standing preference for missing a marginal upgrade over training subscribers to ignore upgrade prompts.
Want to run Upgrade Prompt Timing for your business? Connect the Churnkey MCP to your favorite AI agent. It reads your own usage and billing data and recommends the growth and retention plays most likely to move your LTV—starting with whether this one fits.
npm install -g @churnkey/mcpChurnkey's retention products run on the same dataset behind this tactic.
Schedule a demoRelated tools
Moves subscribers up the commitment ladder with staged offers, an annual term paired with a forever-percent discount, at the month-3 and month-12 milestones.
View tactic
Offers advanced features to subscribers riding a two-month upward usage trend, in the engagement pattern where these nudges land best.
View tactic
Maintains a continuous expansion-intent score for every subscriber, feeding downstream growth tactics and a watchlist of who to pitch, who to talk to, and who to leave alone.
View tactic
The same dataset behind these tactics powers Churnkey's retention products. See what it finds in your subscription data.