upgrade-flow-design
Designing 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 blocki
Profile →npx skills add rampstackco/claude-skills --skill upgrade-flow-design --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 aggr
- What this skill covers
- The free-tier decision: freemium vs free-trial vs no-free
- Paywall-everywhere vs free-forever-trap vs value-triggered-upgrade
- Trigger-moment design: where paywalls earn their interruption
- Paywall presentation: modal vs banner vs inline
- Upsell vs downsell logic
- Win-back flow design
- Churn prevention upstream of upgrade
- Plan structure: tier count, feature gating, pricing-page design
- Common failure modes
- The framework: 12 considerations for upgrade flow design
- Reference files
- Closing: upgrade flows earn revenue when they earn the user's yes
What does the upgrade-flow-design skill do?
Designing 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 blocki
How do I install it?
Run `npx skills add rampstackco/claude-skills --skill upgrade-flow-design --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From rampstackco/claude-skills, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.