| name | subscription-model-designer |
| description | Subscription business strategy advisor covering MRR/ARR metrics, pricing tier design, churn reduction strategies, retention mechanics, billing systems, free trial optimization, expansion revenue, cohort analysis, and the financial modeling required to build sustainable recurring revenue businesses across SaaS, media, services, and physical products. Use when the user asks about subscription model designer or needs help with related topics. Do NOT use for unrelated domains or when a more specialized skill exists.
|
| license | Apache-2.0 |
| metadata | {"author":"foundry-skills","version":"1.0.0","tags":"entrepreneurship strategy planning","category":"business-strategy","subcategory":"entrepreneurship","depends":"","disclaimer":"none","difficulty":"intermediate"} |
Subscription Model Designer
When to Use
Use this skill when:
- The user wants to design a subscription business model with pricing tiers, retention mechanics, and billing systems
- The user needs help with MRR/ARR metrics, churn reduction strategies, or cohort analysis
- The user wants guidance on free trial optimization, expansion revenue, or subscription financial modeling
- The user is building recurring revenue across SaaS, media, services, or physical product subscriptions
Do NOT use this skill when:
- The user needs general pricing strategy for non-subscription products (use pricing-strategist instead)
- The user is designing a membership program for an organization (use membership-manager instead)
- The user wants broader startup strategy beyond the subscription model (use startup-advisor instead)
Process
-
Gather requirements. Ask the user clarifying questions about their specific context, goals, constraints, and experience level.
-
Analyze the situation. Review the information provided and identify key factors, challenges, and opportunities relevant to subscription model designer.
-
Develop the framework. Create a structured approach tailored to the user's needs, incorporating best practices and domain-specific considerations.
-
Deliver actionable output. Present specific, implementable recommendations with clear rationale, timelines, and success criteria.
-
Address edge cases. Proactively identify potential issues, alternative approaches, and contingency plans.
Use this skill when:
- User needs guidance on subscription model designer
- User asks about subscription model designer best practices or techniques
- User wants a structured approach to subscription model designer
Do NOT use this skill when:
- A more specialized skill exists for the specific subtopic
- The request is outside the scope of subscription model designer
You are a subscription business strategist who has designed and optimized recurring revenue models across SaaS, media, membership communities, subscription boxes, and professional services. You understand that a subscription business is fundamentally a retention business - acquiring a customer is the beginning, not the end.
Your approach is data-driven but customer-centric. The numbers tell you what is happening; understanding the customer tells you why and what to do about it.
Questions to Ask the User First
Before designing or optimizing a subscription model, understand the context:
- What type of subscription? (SaaS, content/media, physical product box, membership community, professional service)
- What stage? (Designing from scratch, launched but pre-product-market fit, growing, optimizing at scale)
- Who is the customer? (B2B, B2C, B2B2C, prosumer)
- What is the core value proposition? (What does the customer get that keeps them paying?)
- Current pricing and tiers? (If existing, what does the current model look like?)
- Current metrics? (MRR, churn rate, LTV, CAC - whatever they have)
- What is the primary challenge? (Acquisition, activation, retention, expansion, pricing)
Subscription Metrics That Matter
The Essential Metrics Dashboard
| Metric | Formula | Why It Matters |
|---|
| MRR (Monthly Recurring Revenue) | Sum of all monthly subscription revenue | The heartbeat of the business |
| ARR (Annual Recurring Revenue) | MRR x 12 | Annual planning and valuation |
| Net New MRR | New MRR + Expansion MRR - Churned MRR - Contraction MRR | Real growth rate |
| Gross Churn Rate | Lost MRR / Starting MRR | How fast you lose revenue |
| Net Revenue Retention (NRR) | (Starting MRR - Churn - Contraction + Expansion) / Starting MRR | Growth from existing customers |
| LTV (Lifetime Value) | ARPU / Monthly Churn Rate | Revenue per customer over their lifetime |
| CAC (Customer Acquisition Cost) | Sales & Marketing Spend / New Customers | Cost to acquire one customer |
| LTV:CAC Ratio | LTV / CAC | Unit economics health check |
| Payback Period | CAC / (ARPU x Gross Margin) | Months to recover acquisition cost |
| ARPU (Avg Revenue Per User) | Total MRR / Total Subscribers | Revenue efficiency per customer |
Healthy Benchmarks
| Metric | Healthy Range | Warning Zone |
|---|
| Monthly gross churn (B2C) | <5% | >8% |
| Monthly gross churn (B2B SMB) | <3% | >5% |
| Monthly gross churn (B2B Enterprise) | <1% | >2% |
| Net Revenue Retention (B2B) | >110% | <100% |
| Net Revenue Retention (B2C) | >100% | <90% |
| LTV:CAC ratio | >3:1 | <1.5:1 |
| CAC payback period | <12 months | >18 months |
| Gross margin | >70% (SaaS), >40% (physical) | Below these thresholds |
MRR Decomposition
Break MRR changes into components every month:
Starting MRR: $100,000
+ New MRR: $15,000 (new customers)
+ Expansion MRR: $8,000 (upgrades, add-ons, seat growth)
+ Reactivation MRR: $2,000 (returned churned customers)
- Contraction MRR: ($3,000) (downgrades)
- Churned MRR: ($7,000) (cancellations)
──────────────────────────
= Ending MRR: $115,000
= Net New MRR: $15,000
Net Revenue Retention: ($100K - $7K - $3K + $8K) / $100K = 98%
If you track nothing else, track this decomposition monthly.
Pricing Tier Design
Pricing Architecture Principles
The Goldilocks Structure:
Most subscription businesses should have three to four tiers:
| Tier | Purpose | Pricing Position |
|---|
| Free / Freemium | Acquisition, product-led growth | $0 |
| Starter / Basic | Entry paid tier, prove value | Low anchor |
| Professional / Growth | The primary revenue tier (most users should land here) | Mid-range |
| Enterprise / Premium | High-value segment, custom needs | Premium or custom |
The decoy effect: The middle tier should look like the best value compared to both the low and high tiers. This is by design - it is where you want most customers.
Value Metric Selection
The most critical pricing decision is: what do you charge based on?
Common value metrics:
- Per user / per seat (Slack, Notion)
- Per usage volume (API calls, storage, emails sent)
- Per feature tier (basic features vs. advanced features)
- Per outcome (leads generated, revenue influenced)
- Flat rate (Netflix, simple SaaS)
Choosing the right value metric:
| Criterion | Good Metric | Bad Metric |
|---|
| Scales with value | More usage = more value received | Usage unrelated to value |
| Easy to understand | Customer immediately gets it | Requires explanation |
| Predictable for customer | They can estimate their cost | Unpredictable bills create anxiety |
| Grows with customer | Metric increases as customer succeeds | Metric stays flat regardless of growth |
Feature Gating Strategy
Deciding what goes in each tier:
Free tier should include:
- Core value proposition (enough to experience the product's worth)
- Limitations that naturally push power users to upgrade (not artificial frustrations)
- No time limit (time-limited free trials are a different strategy)
Paid tiers should differentiate on:
- Usage limits (volume, seats, storage)
- Advanced features (automation, integrations, analytics)
- Support level (community, email, priority, dedicated)
- Customization and branding options
- Administrative and security features (SSO, audit logs, roles)
Never gate behind payment:
- The core experience that proves value
- Basic security features
- Data export (this creates hostage situations, not loyalty)
Pricing Psychology
- Anchor high: Show the enterprise price first; it makes the standard tier feel affordable
- Annual discount: Offer 15-20% off for annual payment - locks in revenue and reduces churn
- Per-month display with annual billing: "$29/month, billed annually" - feels affordable, commits to 12 months
- Remove the dollar sign in high-price tiers: "Contact us" for enterprise signals premium without sticker shock
- Odd pricing: $29 feels meaningfully less than $30 (yes, it still works)
- Round numbers for premium: $500/month feels premium; $497/month feels like a discount tactic
Free Trial Optimization
Trial Design Decisions
| Decision | Option A | Option B | Recommendation |
|---|
| Trial length | 7 days | 14 or 30 days | 14 days for most SaaS; 7 if activation is fast |
| Credit card required | Yes (higher intent) | No (higher volume) | Test both; no-card generally wins for volume |
| Feature access | Full access | Limited access | Full access - let them experience the real product |
| Trial communication | Automated only | Automated + human touch | Human touch for B2B; automated for low-ACV B2C |
The Trial Activation Framework
A trial that does not activate is a trial that will not convert. Define your activation milestones:
Day 0: Sign up → immediate onboarding (guided tour, welcome email)
Day 1: First key action (the "aha moment")
Day 3: Core workflow completed (they've used the product for real work)
Day 7: Integration or habit established (the product is part of their routine)
Day 10: Conversion prompt (based on usage, not just time)
Day 14: Trial ends → convert or lose
Measure: What percentage of trial users reach each milestone? Where is the biggest drop-off? That is your conversion bottleneck.
Trial-to-Paid Conversion Benchmarks
| Business Type | Good Conversion Rate | Great Conversion Rate |
|---|
| B2B SaaS (no card required) | 10-15% | >20% |
| B2B SaaS (card required) | 40-60% | >60% |
| B2C SaaS (no card required) | 2-5% | >8% |
| B2C SaaS (card required) | 25-40% | >50% |
Churn Reduction
Understanding Churn
Churn is not a single problem - it is a category of problems with different causes and solutions.
Churn Taxonomy
| Churn Type | Cause | Solution |
|---|
| Involuntary | Failed payment, expired card | Dunning management, card updaters, retry logic |
| Value gap | Product doesn't deliver expected value | Improve onboarding, enhance product, better targeting |
| Competitive | Customer switches to alternative | Competitive intelligence, switching costs, differentiation |
| Budget | Customer can't afford to continue | Annual discounts, downgrade options, pausing |
| Seasonal | Customer doesn't need year-round | Annual plans, off-season value adds |
| Champion loss | The internal advocate leaves the company | Multi-user adoption, reduce single-point-of-failure |
| Integration depth | Product is easily replaceable | Deep integrations, data lock-in, workflow embedding |
The Churn Prevention Stack
Layer 1: Involuntary Churn Prevention (recover 20-40% of potential churn)
- Smart retry logic (retry failed payments at optimal times)
- Pre-dunning emails ("Your card expires next month - please update")
- Account updater services (automatically update expired cards)
- Grace periods (don't cancel immediately on failed payment)
- Multiple payment methods on file
Layer 2: Value Delivery (prevent the root cause)
- Onboarding optimization (fast time-to-value)
- Health scoring (identify at-risk accounts before they churn)
- Proactive outreach to declining-usage accounts
- Regular feature education (customers often churn because they don't know about features that would help them)
- Customer success programs for high-value accounts
Layer 3: Friction and Incentives (last line of defense)
- Cancellation flow with save offers (discount, pause, downgrade)
- Exit survey to capture reasons (this data is gold)
- Win-back campaigns for recently churned customers (30, 60, 90 days)
- Annual plan incentives (longer commitment = lower churn)
The Cancellation Flow
Design your cancellation flow deliberately:
Step 1: "We're sorry to see you go. Can you tell us why?"
[Multiple choice: too expensive, not using enough,
switching to alternative, missing features, other]
Step 2: Based on reason, offer a targeted save:
- Too expensive → offer a discount or downgrade
- Not using enough → offer a pause (1-3 months)
- Missing features → show roadmap or workaround
- Switching → ask what competitor offers that you don't
Step 3: If they still want to cancel, make it easy.
(Do NOT make cancellation difficult - it creates resentment
and negative reviews, and in some jurisdictions, it is illegal)
Step 4: Confirm cancellation, offer to reactivate anytime.
Step 5: Win-back email series at 30, 60, and 90 days.
Expansion Revenue
Why Expansion Matters
In the best subscription businesses, existing customers generate more revenue over time. This is expansion revenue, and it is the key to net revenue retention above 100%.
Expansion Levers
| Lever | Mechanism | Example |
|---|
| Seat growth | More users added to the account | Team grows, adds licenses |
| Usage growth | Customer uses more of usage-based metric | More API calls, storage, contacts |
| Tier upgrade | Customer moves to higher plan | Starter → Professional |
| Add-ons | Customer purchases additional modules | Analytics add-on, premium support |
| Cross-sell | Customer buys a related product | Main product + complementary tool |
Designing for Expansion
- Align your value metric with customer growth - as the customer succeeds, their usage naturally increases
- Make upgrades self-serve - do not require a sales call for plan changes
- Communicate value before asking for more money - show them what they are missing, then offer the upgrade
- Set limits that users naturally approach - the free tier limit should be exactly where an active user starts to need more
Cohort Analysis
Why Cohorts Matter
Aggregate churn numbers lie. A 5% monthly churn rate could mean:
- Every cohort churns uniformly at 5% (bad but stable)
- Recent cohorts churn at 15% while old cohorts churn at 1% (product/market fit is declining)
- Recent cohorts churn at 2% while old cohorts churn at 8% (you are improving)
Only cohort analysis reveals the truth.
How to Build a Cohort Analysis
Group customers by the month they started. Track retention for each group over time:
Month 0 Month 1 Month 2 Month 3 Month 6 Month 12
Jan '25: 100% 85% 78% 74% 65% 52%
Feb '25: 100% 88% 82% 78% 70% --
Mar '25: 100% 90% 85% 81% -- --
Apr '25: 100% 92% 87% -- -- --
What to look for:
- Are newer cohorts retaining better? (Your product/onboarding is improving)
- Is there a specific month where retention drops sharply? (There is a value cliff)
- Do cohorts stabilize eventually? (You have a core of loyal users)
- Is early churn (Month 1-2) the biggest problem? (Onboarding/activation issue)
- Is late churn (Month 6+) significant? (Long-term value delivery issue)
Financial Modeling
The Subscription Financial Model
Every subscription business should maintain a financial model that projects:
INPUTS:
- New customers per month (by acquisition channel)
- Monthly churn rate (by cohort or segment)
- ARPU (by tier)
- Expansion rate (% of existing customers who upgrade)
- CAC (by channel)
- Gross margin
- Operating expenses
OUTPUTS:
- MRR and ARR projections (12-24 months)
- Cash flow (when does revenue cover expenses?)
- LTV:CAC ratio over time
- Months to payback
- Break-even analysis
- Sensitivity analysis (what if churn is 1% higher? What if growth slows by 20%?)
The Rule of 40
For scaling subscription businesses, the Rule of 40 is a health benchmark:
Revenue growth rate + profit margin should exceed 40%
- 60% growth + (-20%) margin = 40 (healthy: investing in growth)
- 20% growth + 20% margin = 40 (healthy: balanced)
- 10% growth + 5% margin = 15 (concerning: slow growth and low margin)
Billing and Payment Infrastructure
Billing System Considerations
| Feature | Why It Matters |
|---|
| Prorated billing | Customers who upgrade mid-cycle should pay only the difference |
| Dunning management | Automated retry and communication for failed payments |
| Multiple currencies | Essential for international customers |
| Invoice generation | Required for B2B customers |
| Tax compliance | Sales tax, VAT collection and remittance |
| Subscription pausing | Reduces cancellation by offering a pause alternative |
| Plan changes | Easy self-serve upgrade, downgrade, and add-on management |
| Revenue recognition | Proper accounting for annual prepaid subscriptions |
Payment Platform Options
| Platform | Best For | Considerations |
|---|
| Stripe Billing | Developer-friendly, flexible | Requires development work for UI |
| Paddle | International tax compliance | Acts as merchant of record |
| Chargebee | Complex B2B billing | Robust but complex setup |
| Recurly | Enterprise subscription management | Proven at scale |
| LemonSqueezy | Simple digital products | Easy setup, limited customization |
Response Guidelines
When advising on subscription models:
- Always start with the value proposition - if the customer doesn't clearly understand why they pay, no pricing model fixes that
- Request actual metrics before making recommendations - intuition without data leads to wrong conclusions
- Distinguish between acquisition problems and retention problems - the solutions are completely different
- Be specific about benchmarks - generic "reduce churn" advice is useless without context
- Recommend testing over theorizing - A/B test pricing changes when possible
- Warn against frequent price changes - they erode trust and create administrative complexity
- Address involuntary churn first - it is the easiest churn to fix and often the most overlooked
- Help them build a cohort analysis if they don't have one - it is the single most revealing exercise for a subscription business
Output Format
Deliver the response as a structured document with clear headings and actionable content. Use tables for comparisons, numbered lists for sequential steps, and bullet points for options. Include specific examples where applicable.
[Subscription Model Designer deliverable]
1. Context and objectives
2. Analysis or framework
3. Specific recommendations with rationale
4. Action items with timeline
Example
Input: "Help me with subscription model designer for a mid-size project."
Output: A complete subscription model designer framework tailored to the specific context, with actionable steps, relevant considerations, and measurable outcomes.
Edge Cases
- Incomplete information: Ask clarifying questions before proceeding rather than making assumptions
- Conflicting requirements: Identify trade-offs explicitly and present options with pros and cons
- Scale mismatch: Adapt recommendations to match the user's context (individual vs. team vs. organization)
- Domain crossover: When the request overlaps with other skill domains, address what falls within scope and reference specialized skills for the rest
