Imported from Joelvarghese-hack/aura-films-website (.agents/skills/upgrade-flow-design/SKILL.md). Install upstream with npx skills add Joelvarghese-hack/aura-films-website --skill upgrade-flow-design. Copyright stays with the author.

Upgrade Flow Design

A senior product marketing director's playbook for designing free-to-paid conversion flows in SaaS products. Trigger moments, paywall design, value demonstration, upsell vs downsell, win-back flows, churn prevention. The discipline of asking for the upgrade at the moment the user has a reason to say yes.

Most upgrade flows fail in one of two ways. They block meaningful product use behind paywalls so aggressively that users churn before reaching the moment that would justify paying. Or they offer a generous free tier with no upgrade path that ever surfaces; users get everything they need; conversion stays at single-digit percentages indefinitely.

The upgrade flows that work do something different. They surface paywalls at moments where the user has demonstrably gotten value. The user has hit a usage threshold, completed a flow, or otherwise demonstrated they are getting the product's promise. The upgrade ask is honest about what they get next; the user is positioned to say yes because the value is fresh.

The voice is the senior product marketing director who has watched conversion rates double when paywalls were re-timed and watched them collapse when more aggressive paywalls were added. Practical, opinionated about the moments that earn the upgrade ask, willing to call out when the product's free tier is too generous to convert.

When to use this skill: scoping a free-to-paid conversion flow for the first time, auditing paywalls that block conversion or never surface, designing the trigger moments that earn upgrade asks, or deciding plan structure that supports upgrades over time.

What this skill covers

This skill spans free-to-paid conversion flows in SaaS products. The growth-tooling distinctions:

• lead-magnet-design is top-of-funnel email capture. This skill is free-to-paid conversion in-product.
• funnel-flow-architecture is the cross-tool funnel architecture. This skill is the upgrade flow specifically.
• upgrade-flow-design (this skill) is trigger-moment design, paywall presentation, plan structure, win-back, churn prevention.
• landing-page-copy is pricing-page copy; lives downstream of this skill's plan-structure decisions.
• pm-spec-writing is the spec for engineers building the upgrade flow.

The audience: product marketers, growth marketers, in-house product teams, agencies running SaaS conversion work for clients.

Out of scope: cross-funnel architecture (covered by funnel-flow-architecture); pricing-page copy (covered by landing-page-copy); the engineering implementation; specific Stripe/Chargebee/Recurly/Paddle billing-platform configurations (those stay implementation-side).

The free-tier decision: freemium vs free-trial vs no-free

Before designing the upgrade flow, decide the free-tier structure.

Freemium (free-forever tier).

• Users use the product indefinitely without paying.
• Paid tier offers more value (capacity, features, support).
• Conversion typically 2-5 percent; volume compensates.

When it works: products with strong network effects, or where free users provide product value (data, content, virality).

Free-trial (time-limited).

• Users get full or near-full product for a defined period.
• After trial, must pay to continue.
• Conversion typically 10-25 percent of trial signups.

When it works: products where the value is clear quickly; audiences willing to commit time before paying.

Reverse trial.

• Users start on paid plan; auto-downgrade to free after period.
• Less common; mixes signals; can produce surprise churn.

No-free (paid-only).

• No free tier; users pay to start.
• Conversion is from prospects rather than free users.
• Conversion rates depend on sales motion, not in-product upgrade flows.

When it works: enterprise products, high-touch sales, products where free would dilute brand or capacity.

The decision is upstream of upgrade flow design. Different free-tier structures warrant different upgrade flows.

Detail in references/free-tier-decision-criteria.md.

Paywall-everywhere vs free-forever-trap vs value-triggered-upgrade

The keystone framing.

Paywall-everywhere. Paywall blocks meaningful product use. Free tier exists but is too constrained to demonstrate value. Users churn before reaching the moment that would justify paying. Cost: users who would have paid after seeing value never reach that moment; conversion suffers despite aggressive paywalling.

Free-forever-trap. Generous free tier with no upgrade path that ever surfaces. Users get everything they need; never see why they would pay. Conversion rate stays at single-digit percentages indefinitely. Cost: the team has built a product users like for free; revenue does not follow because the upgrade ask never lands.

Value-triggered-upgrade. Paywall surfaces at moments where the user has demonstrably gotten value. The user has hit a usage threshold, completed a flow, or otherwise demonstrated they are getting the product's promise. The upgrade ask is honest about what they get next. Cost: design effort upfront is significant; conversion typically meaningfully higher than either alternative.

The litmus test. After a user encounters the upgrade flow, can they articulate why they should pay? "Because I just hit my limit on this feature I have used 200 times" is value-triggered. "Because the product told me to pay before letting me use it" is paywall-everywhere. "I have not seen an upgrade ask" is free-forever-trap.

Trigger-moment design: where paywalls earn their interruption

The single most consequential decision in upgrade flow design.

The principle. Paywalls surface at moments where the user has demonstrated they are getting the product's value. The interruption is justified because the user has a reason to say yes.

Strong trigger moments.

• Usage threshold reached. User has used a feature N times; further use requires paid plan. Honest because they are clearly getting value.
• Capacity limit hit. User has reached free-tier capacity; upgrade unlocks more. Predictable; expected.
• Advanced feature attempted. User clicked into a feature that requires paid plan. Interest is fresh.
• Workflow completed successfully. User has seen value through a completed action; upgrade ask connects that value to recurring access.
• Team-collaboration moment. User wants to invite teammates; team capabilities require paid plan.
• Time-trial ending. Trial-based products surface upgrade as trial nears end.

Weak trigger moments.

• First-login. User has not yet seen value; upgrade ask is premature.
• Random in-product placement. Paywall on the dashboard with no specific trigger; users dismiss.
• Every-page banner. Persistent upgrade banner across all surfaces; users develop blindness.

The discipline. Each paywall should answer: what value did the user just demonstrate, and how does the paid plan extend that value?

Detail in references/trigger-moment-design.md.

Paywall presentation: modal vs banner vs inline

How the paywall surfaces.

Pattern A: Modal paywall. Full-screen overlay blocks the action; user must upgrade or dismiss.

When to use. Capacity limits, feature gates the user has hit. The interruption is warranted by the trigger.

Pattern B: Banner paywall. Persistent banner at top of page suggesting upgrade.

When to use. Soft prompts; awareness without interruption. Risk of becoming visual noise.

Pattern C: Inline paywall. Upgrade ask embedded in the surface where the trigger occurred.

When to use. Contextual prompts that integrate with the workflow.

Pattern D: Toast or notification. Brief paywall surfaced as a notification.

When to use. Soft prompts; low-priority upgrade asks.

Choice criteria.

• The trigger's strength determines the presentation's intensity.
• Strong triggers (capacity hit, feature gate) warrant modal.
• Soft triggers (general awareness) warrant inline or toast.

Copy and value-prop discipline.

• The paywall copy should connect to what the user just did.
• "You have used [feature] 50 times. Upgrade to remove the limit and unlock [related capabilities]." matches the trigger.
• "Upgrade for more features" is generic and weak.

Detail in references/paywall-presentation-patterns.md.

Upsell vs downsell logic

When the user does not accept the primary upgrade.

Upsell. User is on basic plan; ask them to upgrade to higher tier.

Cross-sell. User is paying; offer add-ons or related products.

Downsell. User declined the higher tier; offer a smaller commitment (smaller plan, monthly vs annual, basic vs full feature set).

The downsell discipline. Some users will not upgrade to the proposed tier but will upgrade to something. Downsell captures revenue otherwise lost.

Examples.

• User declined Pro upgrade; offer Starter plan as a path to begin paying.
• User declined annual plan; offer monthly with explicit cost difference disclosed.
• User declined full team plan; offer single-seat upgrade.

Anti-pattern. Aggressive downsell that makes the user feel manipulated. Honest framing: "If Pro is more than you need, here is something that fits."

Detail in references/upsell-vs-downsell-logic.md.

Win-back flow design

Lapsed users, downgrades, partial-churn.

Win-back triggers.

• User has not logged in for 30/60/90 days.
• User downgraded plan.
• User canceled but did not delete account.
• User churned and signed up again later.

Win-back patterns.

• Email-based. Outreach with renewed value-prop, sometimes with discount or trial extension.
• In-product upon return. When the lapsed user returns, surface re-engagement help and (if appropriate) an upgrade-back ask.
• Personal outreach. For high-value lapsed users, sales or customer success conversation.

Discount discipline.

• Discounts to win back can create reverse-incentive (user churns to get discount).
• Discount sparingly; emphasize new value first.

Detail in references/win-back-flow-patterns.md.

Churn prevention upstream of upgrade

The best upgrade flow is the one the user does not need because they did not churn.

Upstream churn signals.

• Declining engagement; sessions per week dropping.
• Last login distant.
• Support ticket pattern (frustration signals).
• Plan downgrade interest signals.

Prevention patterns.

• Engagement re-orientation. Surface help when engagement drops.
• Outreach. Customer success contact for high-value accounts at risk.
• Friction reduction. Audit the reasons users disengage; fix the friction.

The prevention-vs-recovery economics. Preventing churn is much cheaper than winning back churned users. Invest upstream.

Detail in references/churn-prevention-upstream.md.

Plan structure: tier count, feature gating, pricing-page design

The plans that the upgrade flow leads to.

Tier count.

• 2-tier (Free + Paid): simple; clear upgrade path; works for many products.
• 3-tier (Starter + Pro + Enterprise): broader audience; harder to design.
• 4+ tier: rarely better; complexity confuses users.

Feature gating.

• Capacity-based. Free tier limited by use volume; paid unlocks more.
• Feature-based. Free tier missing specific features; paid unlocks them.
• Hybrid. Both capacity and features differ.

Discipline. Each tier should have a clear "this is for [X audience] because of [Y]." Tiers without clear audience-fit produce weak conversions.

Pricing-page design. The pricing page is downstream of plan structure but lives close to upgrade flow. Detail in landing-page-copy for pricing-page copy specifically.

Detail in references/plan-structure-patterns.md.

Common failure modes

Rapid-fire. Diagnoses in references/common-upgrade-failures.md.

• "Conversion rate is low; users churn before reaching upgrade." Paywall-everywhere; gates blocking value demonstration.
• "Conversion rate is single-digit; free users use the product for years." Free-forever-trap; no upgrade path surfaces.
• "Paywall fires; users dismiss; conversion does not lift." Trigger moments wrong; paywall not connected to demonstrated value.
• "Users hit paywall and churn." Wrong moment; paywall blocks before value is fresh.
• "Upgrade rate looks fine; downgrade rate is high." Plan structure wrong; users upgrade then realize they did not need the higher tier.
• "Win-back attempts have low conversion." Re-engagement timing wrong, or value-prop unchanged from what failed initially.
• "Annual plans not converting; monthly plans dominate." Annual value-prop weak; or commitment friction too high.
• "Sales says many leads come from churned users coming back." Win-back working but the previous churn was avoidable; audit upstream.
• "Conversion did not change after we redesigned the paywall." Paywall design was not the problem; trigger or plan structure may be.

The framework: 12 considerations for upgrade flow design

When designing or auditing an upgrade flow, walk these 12 considerations.

1. The free-tier decision. Freemium, free-trial, reverse trial, or no-free.
2. Value-triggered-upgrade, not paywall-everywhere or free-forever-trap. Paywalls at moments of demonstrated value.
3. Trigger-moment design sound. Paywalls connect to specific user-demonstrated value.
4. Paywall presentation matches trigger intensity. Strong triggers warrant modal; soft triggers inline.
5. Copy connects to the trigger. Specific value-prop tied to what the user just did.
6. Upsell, cross-sell, downsell logic. When primary upgrade is declined, secondary paths exist.
7. Win-back flows designed. Lapsed users have a clear re-engagement path.
8. Churn prevention upstream. Upstream signals trigger prevention; downstream upgrade flow is one of multiple defenses.
9. Plan structure clear. Tier count appropriate; each tier has clear audience-fit.
10. Pricing-page coordinates with upgrade flow. Plan structure decisions reflected on the pricing page.
11. Conversion as success metric. Not just paywall display; downstream conversion to paid.
12. Maintenance discipline. Plans, paywalls, win-back flows updated alongside product and pricing changes.

The output of the framework is an upgrade flow that earns the user's "yes" by asking at the moment the user has a reason to say yes, with plan structure that fits the audience the product serves.

Reference files

• references/free-tier-decision-criteria.md - Freemium, free-trial, reverse trial, no-free. Choice criteria.
• references/trigger-moment-design.md - Where paywalls earn their interruption. Strong vs weak trigger moments.
• references/paywall-presentation-patterns.md - Modal, banner, inline, toast. Copy and value-prop discipline.
• references/upsell-vs-downsell-logic.md - When primary upgrade is declined, secondary paths.
• references/win-back-flow-patterns.md - Lapsed users, downgrades, partial-churn re-engagement.
• references/churn-prevention-upstream.md - Preventing churn before the upgrade flow is needed.
• references/plan-structure-patterns.md - Tier count, feature gating, audience-fit per tier.
• references/upgrade-flow-anti-patterns.md - The patterns that look like upgrade flows but degrade trust.
• references/common-upgrade-failures.md - 9+ failure patterns with diagnoses and cures.

Closing: upgrade flows earn revenue when they earn the user's yes

The upgrade flows that compound revenue are the ones that ask at the moment the user has a reason to say yes. Not because the paywall blocked them. Not because the upgrade prompt happened to appear. Because the user just did something that demonstrated value, and the upgrade ask connected that value to continued or expanded access.

That is the bar. Below the bar are paywall-everywhere (gates before value, conversion suffers) and free-forever-trap (no upgrade path, conversion never starts). Above the bar are value-triggered-upgrade flows where trigger-moment design, paywall presentation, plan structure, win-back, and churn prevention work together to convert the right users at the right moments.

The discipline is in the design choices. The free-tier decision (freemium, trial, paid-only) sets the funnel shape. Trigger-moment design decides when paywalls earn their interruption. Paywall presentation decides how the ask lands. Plan structure decides what the user is upgrading to. Win-back and churn prevention catch the cases that escaped the primary upgrade flow.