saas-subscription-mastery
SaaS Subscription Mastery
Use When
- Use when building, launching, or scaling a subscription business — model design, 29 steps to subscription mastery, retention-point strategy, onboarding/activation, engagement loops, churn prevention, expansion, and billing-strategy decisions. Complements subscription-billing (billing mechanics), saas-business-metrics (measurement), and software-pricing-strategy (pricing).
- The task needs reusable judgment, domain constraints, or a proven workflow rather than ad hoc advice.
Do Not Use When
- The task is unrelated to
saas-subscription-masteryor would be better handled by a more specific companion skill. - The request only needs a trivial answer and none of this skill's constraints or references materially help.
Required Inputs
- Gather relevant project context, constraints, and the concrete problem to solve; load
referencesonly as needed. - Confirm the desired deliverable: design, code, review, migration plan, audit, or documentation.
Workflow
- Read this
SKILL.mdfirst, then load only the referenced deep-dive files that are necessary for the task. - Apply the ordered guidance, checklists, and decision rules in this skill instead of cherry-picking isolated snippets.
- Produce the deliverable with assumptions, risks, and follow-up work made explicit when they matter.
Quality Standards
- Keep outputs execution-oriented, concise, and aligned with the repository's baseline engineering standards.
- Preserve compatibility with existing project conventions unless the skill explicitly requires a stronger standard.
- Prefer deterministic, reviewable steps over vague advice or tool-specific magic.
Anti-Patterns
- Treating examples as copy-paste truth without checking fit, constraints, or failure modes.
- Loading every reference file by default instead of using progressive disclosure.
Outputs
- A concrete result that fits the task: implementation guidance, review findings, architecture decisions, templates, or generated artifacts.
- Clear assumptions, tradeoffs, or unresolved gaps when the task cannot be completed from available context alone.
- References used, companion skills, or follow-up actions when they materially improve execution.
Evidence Produced
| Category | Artifact | Format | Example |
|---|---|---|---|
| Release evidence | Subscription business assessment | Markdown doc covering the 29 steps to subscription mastery applied to the current state, retention plan, and growth plan | docs/business/subscription-assessment-2026-04-16.md |
References
- Use the
references/directory for deep detail after reading the core workflow below.
The business-side playbook for subscription businesses — how to design the model, hit the "retention point," build engagement loops, and prevent churn. Covers strategy; leaves billing mechanics to subscription-billing and pricing to software-pricing-strategy.
Sources: How to Build a Subscription Business — 29 Steps to Subscription Mastery (Hansen), Retention Point (Warrillow / Robbie Kellman Baxter / Rob Bell), The Instant 2020–2021 Guide on Subscription Billing for SaaS (John).
When this skill applies
- Designing a new subscription business or transitioning a one-off product to subscription.
- Churn is higher than you want and you're not sure where to intervene.
- Planning activation / onboarding to drive first-month retention.
- Designing engagement loops, member value, and stickiness.
- Deciding between freemium, free trial, and paid onboarding.
- Planning expansion (upsell, cross-sell, price increase).
- Reviewing a subscription billing provider decision.
The subscription mindset
One-off sales optimise for the transaction. Subscriptions optimise for the relationship:
- Revenue is recognised over time, not at sale.
- Customer value is LTV, not deal size.
- Acquisition is necessary but insufficient — retention is the product.
- Every feature, every email, every support interaction is a retention act.
See references/subscription-mindset.md.
The Retention Point
Customers have a moment where they cross from "trying this" to "committed to this." That's the retention point. Before it, churn is high; after, it's low. Your onboarding job is to get users there fast.
Tactics for finding your retention point:
- Identify the first 3–5 actions that correlate with long-term retention (cohort analysis).
- Track each user's progress through those actions.
- Instrument and intervene when stalls happen.
- Shorten the path (in time and steps).
- Make the retention point observable to the user.
Examples of retention points in the wild:
- Slack: team sends 2,000 messages.
- Dropbox: user uploads 1 file on 1 device.
- Netflix: watched a complete show.
- A B2B SaaS: imported one dataset, built one dashboard, shared one link.
See references/retention-point.md.
The 29-step framework (condensed for SaaS)
Hansen's book breaks subscription mastery into 29 steps across four phases:
Phase A — Foundation (steps 1–7)
- Subscription fit — is this product a subscription or a purchase?
- Value promise — what value you deliver per cycle.
- Ideal customer — narrow to 1–3 personas.
- Pricing model — subscription tier shape (free/trial/paid, unit vs flat).
- Positioning — category and differentiator.
- Brand promise — what you commit to deliver.
- Channels — how customers find you.
Phase B — Launch (steps 8–14)
- Landing page + offer — what converts.
- Onboarding — time-to-value.
- Activation metric — the action that predicts retention.
- Payment capture — frictionless at sign-up.
- Early-life communication — week 1, week 2 emails.
- Community — peers who reinforce value.
- Customer support — response time SLA early.
Phase C — Growth (steps 15–21)
- Habit loops — trigger → action → reward → investment.
- Referrals — customers invite customers.
- Partnerships — distribution deals.
- Content marketing — teach, then sell.
- Expansion offers — upsell, cross-sell.
- Price increases — compounding revenue without churn spike.
- Win-back — reactivating churned customers.
Phase D — Retain and scale (steps 22–29)
- Segmentation — cohorts by behaviour.
- Proactive churn prevention — intervene before cancel.
- Cancel flow — offer alternatives, collect reasons.
- Customer advisory board — loudest voices reshape the product.
- Financial discipline — unit economics that scale.
- Operational reviews — weekly + monthly + quarterly rhythm.
- Team structure — who owns acquisition, retention, expansion.
- Long-term roadmap — evolving value to keep paying.
See references/29-steps.md.
Freemium vs free trial vs paid
Freemium -> value compounds with usage, low marginal cost, free tier is genuinely useful
Free trial -> value is obvious within N days, time pressure drives decision
Paid -> purchased on promise + reputation; most mature or enterprise motion
Reverse trial -> starts on paid tier, downgrades to free at N days if no conversion
Rule: pick one. Don't mix unless you have clear segments.
See references/freemium-vs-trial.md.
Activation and onboarding
The first 7 days matter more than the next 90 days. Goals:
- User completes a personally meaningful action (aha moment).
- User invites at least one colleague or team member (when product is collaborative).
- User sees value from the product in their workflow.
Tools:
- Product tour (Intercom, Userflow, in-app).
- Empty-state design — never show a blank screen to a new user.
- Checklist of onboarding steps.
- In-app triggers for key actions.
- Week-1 email sequence that reinforces each step.
Measure: time-to-first-value, day-1 / day-7 retention, percent hitting activation.
See references/activation-onboarding.md.
Engagement and habit loops
Habit = trigger → action → reward → investment.
Apply to your product:
- Trigger — email, push, calendar, or internal (user opens app at 9 am).
- Action — the smallest useful thing to do.
- Reward — social, tribal, self-achievement, or informational.
- Investment — user adds data, preferences, connections — makes leaving costly.
Measure: daily active users / weekly active users (DAU/WAU), session frequency, feature-depth.
See references/engagement-loops.md.
Churn prevention
Voluntary churn — user cancels.
Involuntary churn — payment fails. (See subscription-billing skill for dunning.)
Early signals of voluntary churn:
- Login frequency drop.
- Seat usage drop.
- Support tickets about core features or cancellation.
- Integration disconnected.
- NPS / CSAT drop.
Intervention playbook:
- Automated reactivation email after 7-day silence.
- CSM reach-out after signal fires.
- In-app banner offering help or guide.
- Executive sponsor call for enterprise accounts.
- Pause-not-cancel option in cancel flow.
- Exit interview — why you're leaving (qualitative + category).
See references/churn-prevention.md.
Expansion — the second revenue lever
Expansion revenue (upsell + cross-sell) is cheaper than acquisition and compounds. Net Revenue Retention > 110% means expansion > churn; NRR > 120% is world-class.
Expansion mechanisms:
- Usage-based overage — they use more, they pay more.
- Seats — team grows, seats grow.
- Tiering — features unlock on upgrade.
- Add-ons — complementary products.
- Price increases — grandfather existing customers or migrate them carefully.
See references/expansion-revenue.md.
Pricing model decisions
- Flat — simplest, easiest to communicate. Works for simple products.
- Per seat — aligns with customer team size. Works for collaboration.
- Usage-based — aligns with value delivered. Works when value varies widely.
- Tiered — feature packaging. Combine with any of the above.
- Hybrid — platform fee + usage. Most common in B2B infra.
Avoid: too-many-dimensions pricing (seats × features × usage × region × volume discount). Customers can't do the maths.
See references/pricing-model-decisions.md and cross-reference software-pricing-strategy.
Billing provider selection
Decision drivers (most important first):
- Tax compliance — is the provider a Merchant of Record (Paddle, Lemon Squeezy) or do you manage tax yourself (Stripe, Chargebee)?
- Geographies — does it support your customer regions, currencies, local payment methods?
- Subscription lifecycle complexity — prorations, mid-cycle upgrades, trials, pause, coupons.
- Metered billing — can it handle usage-based precisely?
- Revenue recognition — does it export RevRec-ready data?
- Integrations — accounting, tax, CRM.
- Fees — flat vs percentage vs hybrid.
Common picks: Stripe Billing (flexible, you handle tax), Paddle/Lemon Squeezy (MOR, handles tax), Chargebee (enterprise, mature), Orb (usage-based focus).
See references/billing-provider-selection.md and cross-reference subscription-billing.
Financial metrics every subscription business tracks
- MRR / ARR — monthly / annual recurring revenue.
- NRR / GRR — net and gross revenue retention.
- ARPU / ACV — average per user / contract value.
- CAC — customer acquisition cost.
- LTV — lifetime value.
- LTV : CAC — target > 3; world-class > 5.
- CAC payback — months to recover CAC; target < 12.
- Logo churn vs revenue churn — revenue can be stable while logos leak.
- Quick Ratio — (new + expansion) / (churn + contraction); target > 4.
See saas-business-metrics for full framework; this skill focuses on what to do about them.
See references/metrics-quick-reference.md.
Anti-patterns
- Treating sign-ups as success — churn at week 1 undoes everything.
- No activation metric — you don't know if onboarding works.
- "We'll retain users by shipping features" — usually wrong; the first feature they need is to find value in what you already have.
- Ignoring involuntary churn (payment failures) — can be 20–40% of total churn; see
subscription-billingdunning. - Pricing page that lists features without matching them to customer problems.
- No cancel flow — loses signal, loses save opportunity.
- No customer advisory board at scale — you're guessing.
- Price-increase without preparation — spike in churn.
- Cohort analysis ignored — you can't improve what you don't segment.
Read next
subscription-billing— billing lifecycle, dunning, tax, refunds.saas-business-metrics— full metrics framework.software-pricing-strategy— pricing principles.habit-forming-products— Nir Eyal's Hook model applied.saas-sales-organization— how sales fits alongside subscription growth.lean-ux-validation— validating retention hypotheses before building.
References
references/subscription-mindset.mdreferences/retention-point.mdreferences/29-steps.mdreferences/freemium-vs-trial.mdreferences/activation-onboarding.mdreferences/engagement-loops.mdreferences/churn-prevention.mdreferences/expansion-revenue.mdreferences/pricing-model-decisions.mdreferences/billing-provider-selection.mdreferences/metrics-quick-reference.md
More from peterbamuhigire/skills-web-dev
google-play-store-review
Google Play Store compliance and review readiness for Android apps. Use
76gis-mapping
Use for web apps that need Leaflet-first GIS mapping, location selection,
48saas-accounting-system
Implement a complete double-entry accounting system inside any SaaS app.
47manual-guide
Generate end-user manuals and reference guides for ERP modules. Use when
38healthcare-ui-design
Design world-class clinical and patient-facing healthcare UIs for web,
38api-error-handling
Comprehensive, standardized error response system for PHP REST APIs with
31