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/win-back-flow-patterns.md
View on GitHub# Win-back flow patterns
Lapsed users, downgrades, partial-churn re-engagement.
When users disengage, downgrade, or churn, win-back flows attempt to bring them back. Done well, win-back captures revenue from users who left due to specific (often fixable) reasons; done poorly, win-back becomes spam that confirms the user's decision to leave.
---
## The respect-the-decline principle
Users who left often left for reasons. Win-back should be honest about the reasons and offer something genuinely changed, not just a discount.
**The win.** A user lapsed 60 days ago. Win-back email surfaces with: "Since you last logged in, we shipped [specific feature you mentioned wanting]. Want to try it?" The user returns; the value-prop is fresh.
**The fail.** Same user. Win-back email surfaces with: "We miss you! Come back for 20 percent off." The user dismisses; the discount feels like manipulation; the previous problems remain.
The discipline. Win-back is most effective when something has changed (new feature, fixed problem) the user would value.
---
## Win-back triggers
When to fire.
**User has not logged in for 30 days.** Soft trigger; light re-engagement.
**User has not logged in for 60-90 days.** Moderate trigger; more substantive re-engagement.
**User has not logged in for 6+ months.** Aggressive trigger; usually the last attempt before treating as fully churned.
**User downgraded plan.** Trigger surfaces post-downgrade; win-back attempts to retain the higher tier.
**User canceled but did not delete account.** Soft trigger; re-engage before full churn.
**User churned and signed up again.** Different trigger; usually treat as new signup with prior context.
The triggers vary by product and audience.
---
## Pattern A: Email-based win-back
Outreach with renewed value-prop.
**How it works.**
- Email sent to lapsed user.
- Content focuses on what has changed since they left.
- May include discount or trial extension.
**Email design discipline.**
- Subject line concrete; not generic "we miss you."
- Body specific to what has changed.
- One clear CTA back to product.
- Easy unsubscribe; respect users who do not want re-engagement.
**Strengths.**
- Cheap; can scale.
- Reaches users outside the product.
**Weaknesses.**
- Easy to feel like spam.
- Email deliverability for lapsed users is harder.
**When to use.** Default for lapsed-user re-engagement.
---
## Pattern B: In-product upon return
When a lapsed user returns, surface re-engagement help.
**How it works.**
- User logs in after long absence.
- In-product surfaces re-orientation and (if appropriate) upgrade-back ask.
**Design.**
- Welcome-back banner with what has changed.
- Brief tour of new features added during absence.
- Soft upgrade-back if user downgraded.
**Strengths.**
- The user has already returned; engagement is fresh.
- Can be specific to the user's prior usage.
**Weaknesses.**
- Misses users who do not return on their own.
**When to use.** When email or other re-engagement has produced a return.
---
## Pattern C: Personal outreach
For high-value lapsed users, sales or customer success conversation.
**How it works.**
- Customer success or sales reach out directly.
- Often via email or call.
- Conversation about what changed for the user; what would bring them back.
**Strengths.**
- Highest engagement potential.
- Surfaces real reasons; can address them.
**Weaknesses.**
- Expensive; only viable for high-value accounts.
- Risk of harassment if not done well.
**When to use.** Enterprise lapsed accounts, high-revenue lapsed customers, accounts with strategic value.
---
## Pattern D: Offer-based win-back
Discount or trial extension as primary motivator.
**How it works.**
- Offer (e.g., 30 percent off, 3 months free, extended trial) presented to lapsed user.
- Limited time; explicit terms.
**Strengths.**
- Can move users who left for cost reasons.
- Easy to implement.
**Weaknesses.**
- Can train users to lapse intentionally to get discounts.
- Discount alone does not address why they left.
**When to use.** Sparingly. Combine with value-prop changes; do not lead with discount alone.
The discount-as-only-strategy failure. Discounts to win back can create reverse incentives. If users learn that lapsing gets them discounts, lapse rate climbs strategically.
---
## Win-back sequence design
A multi-touch win-back rather than single email.
**Typical sequence.**
- Day 30: light re-engagement (what's new).
- Day 60: more substantive (specific feature; case study).
- Day 90: explicit win-back offer (if appropriate).
- Day 120: final outreach; respect non-response.
- Beyond Day 120: treat as fully churned.
The sequence respects the user's silence; multiple touches at different intensities.
---
## When to abandon win-back
Some users genuinely do not want to come back. Respect that.
**Signals to stop.**
- User unsubscribed from emails.
- User explicitly stated they do not want contact.
- Multiple win-back attempts produced no response.
- User left for reasons unfixable by the product (changed jobs, changed needs).
**The respect-the-no principle.** Continuing win-back after clear no signals is harassment.
---
## Discount discipline in win-back
When discounts make sense.
**Use discount when:**
- The user explicitly stated cost was a factor.
- The product's price has not changed but the user's situation has.
- A time-limited promotion is genuinely available.
**Avoid discount when:**
- The user left for non-cost reasons (poor experience, missing features).
- The discount would train lapse-for-discount behavior.
- The discount cannibalizes existing customer revenue.
---
## Win-back analytics
Track effectiveness.
**Metrics.**
- Re-engagement rate (lapsed users who returned after win-back outreach).
- Conversion rate (returned users who paid or upgraded back).
- Retention of returned users (do they stay or lapse again?).
**Diagnostic uses.**
- Low re-engagement: outreach not relevant or not delivered.
- High re-engagement, low conversion: returns happen but value-prop weak.
- Returns lapse again quickly: underlying issue not fixed.
---
## Common win-back failures
**Generic outreach.** "We miss you" with no specifics; user dismisses.
**Discount-only strategy.** Discount without value-prop change; trains lapse-for-discount.
**Frequency overload.** Too many win-back attempts; harassment.
**No segmentation.** Same outreach to all lapsed users regardless of why they left.
**Ignoring unsubscribes.** Outreach continues despite explicit no.
**No measurement.** Cannot tell if win-back works.
**Returns-lapse-again.** Win-back succeeds short-term; underlying issue persists; user lapses again.
---
## Methodology-level choices that stay in the public skill
The respect-the-decline principle. Win-back triggers. Patterns A through D (email, in-product, personal, offer-based). Win-back sequence design. When to abandon. Discount discipline. Win-back analytics. Common failures.
## Implementation choices that stay internal
Specific win-back sequences for specific products. Specific outreach copy in brand voice. Specific discount levels. The team's segment-specific approaches. 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 |