rampstackco/claude-skills / skills/upgrade-flow-design
upgrade-flow-design
VerifiedDesigning free-to-paid conversion flows for SaaS products. Trigger moments, paywall design, value demonstration, upsell vs downsell, win-back flows, churn prevention. Honest about paywall-everywhere (gates everything aggressively), free-forever-trap (no upgrade path surfaces), and value-triggered-upgrade (paywall surfaces at moments of demonstrated value) patterns. Triggers on upgrade flow, paywall, free-to-paid, freemium conversion, trial conversion, plan upgrade, subscription upgrade, win-back flow, churn prevention. Also triggers when free-to-paid conversion is low, when paywalls are blocking the wrong moments, or when upgrade flows are being scoped for the first time.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 360 B |
| SKILL.md | skill md | 17.9 KB |
| references/churn-prevention-upstream.md | markdown | 7.0 KB |
| references/common-upgrade-failures.md | markdown | 6.1 KB |
| references/free-tier-decision-criteria.md | markdown | 7.6 KB |
| references/paywall-presentation-patterns.md | markdown | 7.8 KB |
| references/plan-structure-patterns.md | markdown | 7.6 KB |
| references/trigger-moment-design.md | markdown | 7.2 KB |
| references/upgrade-flow-anti-patterns.md | markdown | 6.2 KB |
| references/upsell-vs-downsell-logic.md | markdown | 6.4 KB |
| references/win-back-flow-patterns.md | markdown | 7.1 KB |
references/paywall-presentation-patterns.md
View on GitHub# Paywall presentation patterns
Modal, banner, inline, toast. Copy and value-prop discipline.
How the paywall surfaces. Done well, the presentation matches the trigger's intensity; done poorly, presentation fights the trigger and conversion suffers.
---
## The presentation-matches-trigger principle
Strong triggers warrant prominent presentation; soft triggers warrant subtle presentation.
**The win.** A user hits a capacity limit; a modal surfaces explaining the limit and offering upgrade. The modal is justified because the trigger is hard (the user cannot continue without resolving). The user accepts the interruption.
**The fail.** Same user, soft trigger (general awareness moment). A modal surfaces the same way. The interruption is not justified by the trigger; user resents.
The discipline. Match presentation intensity to trigger strength.
---
## Pattern A: Modal paywall
Full-screen overlay blocks the action.
**How it works.**
- Modal overlay appears.
- User must engage (upgrade) or dismiss to continue.
- Often blocks the action that triggered it.
**Strengths.**
- Highest visibility.
- Clear demand for attention.
- Works for hard triggers (capacity hit, feature gate).
**Weaknesses.**
- Most disruptive.
- Easily abused; produces annoyance.
**When to use.** Hard triggers where the user cannot proceed without resolution.
---
## Pattern B: Banner paywall
Persistent banner at top of page.
**How it works.**
- Banner remains visible across pages.
- Often dismissable for the session.
- Soft prompt; does not block action.
**Strengths.**
- Persistent awareness without blocking.
- Reaches users who have not hit hard triggers.
**Weaknesses.**
- Visual noise; users develop blindness.
- Cumulative exposure can feel like spam.
**When to use.** Awareness campaigns. Use sparingly; persistent banners abused become noise.
---
## Pattern C: Inline paywall
Upgrade ask embedded in the surface where the trigger occurred.
**How it works.**
- Paywall content appears within the workflow.
- User reads in context; can act or scroll past.
- No overlay; no modal.
**Strengths.**
- Contextual; integrated with the workflow.
- Non-disruptive.
- Respectful of user momentum.
**Weaknesses.**
- Easier to miss.
- May not produce conversion if too easy to ignore.
**When to use.** Soft triggers; awareness without interruption.
---
## Pattern D: Toast or notification
Brief paywall surfaced as a notification.
**How it works.**
- Small notification appears (often corner of screen).
- Auto-dismisses after time or on click.
- Brief content.
**Strengths.**
- Lightest weight.
- Easy to dismiss.
**Weaknesses.**
- Easy to miss entirely.
- Limited content.
**When to use.** Soft prompts; low-priority awareness.
---
## Pattern E: Hybrid
Combining patterns.
**Common combinations.**
- Modal for hard triggers + inline for soft triggers.
- Banner for awareness + modal at hard trigger moments.
- Inline for in-feature prompts + modal at capacity limits.
**The hybrid discipline.** Each presentation has a clear role; users do not see overlapping or competing paywalls.
---
## Choice criteria
Which presentation fits which trigger.
**Use modal when:**
- Trigger is hard (cannot proceed without resolution).
- Capacity limit reached.
- Feature gate hit.
**Use inline when:**
- Trigger is contextual but soft.
- User can continue without resolving.
- Workflow integration is the priority.
**Use banner when:**
- Awareness campaign across pages.
- Soft prompt for users who have not hit hard triggers.
**Use toast when:**
- Low-priority awareness.
- Brief acknowledgment.
The simplest pattern that matches the trigger is usually right. Most upgrade flows benefit from inline + occasional modal.
---
## Copy and value-prop discipline
What the paywall says.
**The principle.** Paywall copy should connect to what the user just did and what they get next.
**Strong copy patterns.**
- "You have used [feature] 50 times this month. Upgrade to remove the limit and unlock [advanced capabilities]."
- "You have hit your free tier's [capacity]. Upgrade to expand to [paid capacity]."
- "Inviting teammates requires our [team plan]. Upgrade to invite up to [number] teammates."
What works: specific connection to user action; specific value of upgrade.
**Weak copy patterns.**
- "Upgrade for more features." (Generic; no connection.)
- "Get the full experience." (Vague; no specifics.)
- "Don't miss out." (FOMO without value.)
What fails: no connection to user behavior; no specific value-prop.
---
## Plan presentation in paywalls
Showing the upgrade options.
**Single-plan paywall.** One upgrade option presented. Simple; clear.
When to use. When the upgrade is unambiguous (capacity hit; one obvious path).
**Multi-plan paywall.** Two or three upgrade options presented (e.g., Pro vs Enterprise).
When to use. When multiple plans could fit; let the user choose.
**Presentation discipline.**
- Highlight the recommended plan.
- Make pricing clear.
- Make value differences clear.
**Anti-pattern.** Showing 5 plans in a paywall. Decision paralysis; user does not choose.
---
## Pricing presentation
How prices appear.
**Per-month vs per-year.** Default to the user's likely commitment level; offer the alternative.
**Price anchoring.** Show what the upgrade saves vs equivalent value (use carefully; can feel manipulative).
**Currency and locale.** Match the user's locale.
**Discounts.** Surface honest discounts (annual discount, promotion). Avoid fake urgency.
---
## Action design
The buttons and CTAs.
**Primary CTA.** "Upgrade to Pro" with specific plan name. Bold; visible.
**Secondary CTA.** "Maybe later" or "See plans." Allows decline without forcing.
**No third option.** Two paths (upgrade or decline) preferred. Three or more paths confuse.
**The decline-respect principle.** "Maybe later" should respect the decline. The same paywall should not re-fire immediately.
---
## Paywall as opportunity to communicate value
Even when the user declines, the paywall is a touchpoint.
**The principle.** Paywall copy explains what paid offers in concrete terms. Even users who decline understand more about the paid plan than they did before.
**Why this matters.** Future trigger moments find users with more context. The decline today may convert next month because the value is now understood.
---
## Paywall analytics
Track the paywall's performance.
**Metrics.**
- Display rate (how often does it surface?).
- Click rate (how many engage with upgrade button?).
- Conversion rate (of clicks, how many complete upgrade?).
- Decline rate (how many dismiss?).
- Re-show rate per declined paywall.
**Diagnostic uses.**
- High display, low click: copy or value-prop weak.
- High click, low conversion: friction in upgrade flow downstream.
- High decline rate: trigger may be wrong, or copy unclear.
---
## Common presentation failures
**Wrong presentation for trigger.** Modal on soft trigger; inline on hard trigger.
**Generic copy.** Paywall does not connect to user behavior.
**Plan paralysis.** Too many options in the paywall.
**Hidden price.** User has to dig to find the cost.
**Decline ignored.** Same paywall re-fires immediately after dismiss.
**Cumulative exposure.** User sees too many paywalls per session.
**Mobile-broken paywall.** Modal on mobile blocks all interaction.
**Loading delay.** Paywall takes time to appear; user has moved on.
---
## Methodology-level choices that stay in the public skill
The presentation-matches-trigger principle. Patterns A through E. Choice criteria. Copy and value-prop discipline. Plan presentation. Pricing presentation. Action design. Paywall as value communication. Paywall analytics. Common failures.
## Implementation choices that stay internal
Specific paywall designs for specific products. Specific copy in brand voice. Specific tooling. The team's analytics dashboards. These vary by team and product.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |