Adding more is harder than the first time they bought.

Connected

Account, plan, the add-on they started, billing already on file.

Example eligibility rule

Use the shortened expansion flow when an authorized billing user starts a specific add-on, the account has a valid payment method and accepted terms, and the change is available through self-service. Route price exceptions, contract changes, missing authority, and regulated purchases to the appropriate approval flow.

Invite a seat, add a line, attach a warranty, lift a cap. Default is a full billing flow, a new cart, or a sales form. They are mid-job. The stall is the work to say yes, not the offer.

Avoid this assumption

A bigger "Upgrade" button is not less effort. Finishing from the screen they are on is.

Effort at expansion is shortening a path they already want. Prefill, in-flow add, skip the second account. Test against the long checkout they already survived once.

Reach

How many eligible people can you reach in the chosen channel and time period?

Cost

What will content, delivery, QA and ongoing maintenance cost?

Return

What incremental outcome would cover that cost, and what is it worth?

Planning inputs, not measured results. Estimate reach × incremental outcome rate × value per outcome, then subtract cost. Use a range and a consistent time period.

Example format: Experience

Add from the current screen. Confirm, no second cart.

Compare lighter and deeper responses

Choose the lightest response that solves the need.

Assist: Offer useful help

Keep the flow. Prefill who they are and what they already have.

Adapt: Change a meaningful part

Add from the current screen. Confirm, no second cart.

Transform: Tailor the journey

One-tap add for the thing they just hit, receipt in-product, undo for a day.

What to watch out for

• One-click charges with no undo.
• Sending them to a generic pricing page mid-job.
• A sales-assisted flow for a $10 add-on.

Control

Default add-seat, add-on, or second-checkout flow.

Treatment

Short in-flow add, with a holdout.

Success measure

Completed expansion of the started add.

Guardrail

Accidental adds and refunds. One-tap must be reversible.

Win or lose, record what worked, for whom and why. What you learn becomes the next signal.

• Pendo in-app guides Product experience platform combining usage analytics with in-app guides targeted by user or account segments.
• Appcues In-product engagement platform for building targeted flows, tooltips, checklists, and announcements without engineering.
• Userpilot In-app flows, checklists, and multi-channel workflows targeted by behavior and segment, built without code.
• Iterable Cross-channel journeys (email, SMS, push, in-app) built from a single visual studio, triggered by real-time customer behavior.

They hit the limit of the plan they're on. Tell them they hit a wall, and how to keep going. Don't throw up a paywall.

They keep doing it the hard way. Show the easier way while they're still doing it by hand.