Ascension Offer

Promote an existing customer to the next tier at the exact moment their own usage proves they have outgrown the current one.

Pro moderate Funnel-Stage Offers

What it adds

The builder reads your tier definitions and usage signals from the source files and builds a triggered upgrade path that appears when a customer hits a documented ceiling, with prorated credit for what they already paid. It converts on evidence rather than persuasion: the customer sees their own behavior reflected back as the reason to move up, and the price gap is framed as the difference between tiers, not a new purchase. The conversion event is a completed tier change with billing adjusted.

What your builder is told to do

The actual instructions, in order.

1
Inspect the source files and enumerate each tier's limits and the observable signal that indicates a customer has reached one — usage volume, feature attempts, seat count, or completed milestones.
2
Bind the offer to that signal so it surfaces contextually where the ceiling is felt, not as a broadcast campaign; ascension shown at the wrong moment reads as an upsell and is ignored.
3
Write the opening as an observation of the customer's own activity, drawn only from data the source files expose, followed by what the next tier removes as a constraint.
4
Present the upgrade as a delta: what changes, what stays, and the price difference after prorated credit for the current term.
5
Make the upgrade action immediate and reversible within a stated window, with the new entitlements active before the next billing cycle rather than after it.
6
Define layout: mobile shows the triggering fact, the single unlocked capability, and the upgrade control in one screen; tablet adds a compact tier comparison beneath; desktop places the comparison table beside the contextual trigger message with current tier clearly marked.
7
Route non-upgraders to a documented alternative — a usage-management path or a scheduled reminder — instead of repeating the same prompt on every visit.
8
Track trigger fired, offer viewed, upgraded, and dismissed as separate events, and suppress the prompt for a defined cooldown after dismissal.

Edge cases it handles

The things an agent skips when you only say "build a ascension offer".

The customer hits the ceiling once due to an anomaly: require a sustained signal before triggering, not a single spike.
Mid-term upgrade: calculate and display proration explicitly rather than charging a full new term.
The customer is on a legacy plan not in the current tier list: define mapping before showing any comparison.
Downgrade after upgrade: define what happens to data or entitlements that exceed the lower tier.
Annual billing customers: express the delta in the same billing period they are on.

Definition of done

Your builder is required to check every one of these before reporting the work finished.

The offer triggers on a defined usage or milestone signal documented in the source files.
Copy references the customer's own activity using real data, never invented figures.
Price is shown as a prorated delta with the calculation visible.
Mobile, tablet, and desktop each render the trigger context and upgrade control appropriately.
New entitlements activate immediately on upgrade, with a stated reversal window.
Dismissal starts a cooldown and routes to an alternative path instead of repeating.
The builder lists source files defining tiers and signals, and flags unresolved entitlement assumptions.

Related offer files

Funnel-Stage Offers

Lead Magnet

Turn anonymous cold traffic into named subscribers by trading one narrowly useful asset for an email address in seconds.

Funnel-Stage Offers

Affiliate Launch Kit

Equip partners with dated assets, tracked links, and a run-of-show so they can promote a launch window without improvising.

Funnel-Stage Offers

Cart Recovery Offer

Close an abandoned checkout by returning the shopper to their exact cart and resolving the friction that stopped them.

How it works

1

Copy the link

Grab the Markdown blueprint URL for this offer type.
2

Give it to your builder

Paste it into Claude Code, Cursor, Codex, or whatever AI builder is already working in your app.
3

It maps, then builds

Your agent reads the blueprint first, then builds the offer into your app around the product, audience, and stack.

Works with your stack

These blueprints are written to adapt. They tell the agent to detect your framework, match your existing design system, and use your source files instead of guessing the offer.

Need it tighter than that? Customize the offer file and tell it exactly which source docs and stack to use.