When you're driving expansion — upsell, cross-sell, additional seats, or deeper usage — follow a core principle: expansion experiences should be behaviorally triggered, opt-in by default, and anchored to what the user is already doing. No surprise upsells. No interruption Modals. This article walks through three plays and how to choose between them.

The Appcues App is in beta and rolling out gradually. If you don't see it yet at app.appcues.com, it hasn't been enabled for your account. See Introducing the Appcues App for more.

Three expansion plays

Play 1 — Behaviorally triggered Slideout

The pitch: "I see you're doing X — have you tried Y?"

When to use it: The user has demonstrated value with one feature and there's a logical next-step feature that adjacent power users typically adopt. The Slideout fires on the action that signals "ready for next."

Why it works: The user is already in flow and has earned credibility — they've shown they get value from the product.

Play 2 — Pin with opt-in CTA

The pitch: A persistent Pin on the relevant feature area with a CTA to schedule time or chat with an expert.

When to use it: The expansion conversation is sales-led, not self-serve. The user needs a human, not a product tour.

Why it works: Persistence respects the user's pace. They engage when they're ready, not when you push.

Play 3 — Empty-state paywall

The pitch: An Embed or contextual message in the empty state of a gated feature, surfacing the value and a clear path to unlock it.

When to use it: A user navigates to a feature they don't have access to. They've self-qualified intent by going looking for it.

Why it works: The user explicitly came looking for this — they're already interested.

Why Embeds default for expansion

Default to Embeds for expansion. They look native to the product, sit inline where the user is already working, and don't interrupt productive flow. Slideouts work for new-product expansion announcements; Tooltips and Pins work for gated-feature callouts. But Embeds should carry the most expansion content because they feel like part of the product rather than a sales pitch.

Two targeting strategies

Split expansion targeting into two cohorts and decide which to focus on first:

• Usage-based — target users with low engagement on a feature they have access to. Surface value before they conclude the feature isn't for them.
• Feature-based — target users who don't have access to a gated feature. Highlight what they're missing and how to unlock it.

The experience types differ between these cohorts. Usage-based expansion uses behavioral triggers and contextual nudges. Feature-based expansion uses empty-state Embeds and strategic Pins.

Sales-led vs. self-serve

Diagnose which motion your expansion requires:

• Sales-led — focus on handraise patterns: Pins with a "schedule a meeting" CTA, Slideouts with a "talk to an expert" action. The experience hands the user off to a human.
• Product-led (PLG) — map a journey funnel that auto-progresses users toward expansion without a human handoff. Behavioral triggers, contextual Embeds, and gated empty states do the work.

What to avoid for expansion

• Modal expansion CTAs. Interrupts a productive workflow with a sales pitch. Always use a less intrusive alternative.
• Mass-targeted upgrade messaging. Expansion only works when targeting is grounded in usage signals. Don't blast "upgrade now" to everyone.
• Expansion experiences to users who haven't activated. If someone hasn't gotten value from what they already have, selling them more is the wrong move. Check activation status before recommending expansion.
• Banner-style "upgrade now" persistence. Looks like an ad. Use an Embed or Pin instead.