Repeatable by Ryan Lee: Seven Recurring Revenue Models Dissected Like System Architectures
Every engineer who has debugged a retention problem in a SaaS product knows the pattern: users churn, the product team ships more features, users keep churning, the team ships more features. Nobody runs the root cause analysis until the damage is structural.
Ryan Lee's Repeatable is a 7-lesson, $299 course that applies the same diagnostic thinking to subscription businesses outside of software. The course teaches seven distinct recurring revenue models, each with different production requirements, retention dynamics, and audience fit profiles. Ryan Lee built a PDF continuity program to $230,000 per month on two to three hours of weekly production. The course reverse-engineers that model and six others into a repeatable system.
Before investing $299 in a single course, consider that Course To Action carries the full Repeatable breakdown alongside 110+ other premium course summaries for $49 per 30 days or $399 per year. No auto-renewal. Every summary includes audio. The free tier gives you 10 summaries and AI credits to apply frameworks to your own business — no credit card required.
Here is why this course matters to anyone thinking about subscription revenue as a system design problem.
Step 1: The Diagnosis — Overwhelm Is a System Failure, Not a Content Problem
In observability engineering, there is a critical distinction between symptoms and root causes. CPU spikes are a symptom. The unbounded loop generating them is the cause. Treating symptoms without tracing causes produces dashboards that look healthy while the system degrades underneath.
Ryan Lee's diagnosis of membership site churn follows identical logic. Low retention numbers are the symptom. The cause, in most cases, is not poor content quality, incorrect pricing, or weak marketing. It is overwhelm: the state where a subscriber's backlog of unfinished content makes renewal feel irrational. The member is not dissatisfied. They are behind. And being behind produces guilt, which produces cancellation.
The data supporting this diagnosis is not theoretical:
- Beyond Diet (Jeff Siegel): 26,000 members at $14.95/month, 10-month average stick rate
- MS Gym (Ken Allen): 2,400 members at $79/month
- Ryan Lee's PDF continuity: $230,000/month on 2-3 hours of weekly production
None of these programs are content-heavy by industry standards. All three are deliberately constrained. The constraint is not a limitation. It is the architecture.
Step 2: The Core Architecture — Seven Recurring Revenue Models
This is the structural heart of Repeatable, and it reads like a pattern library for subscription businesses. Each model is a different architecture for recurring income, with different production requirements, different retention mechanisms, and different failure modes.
Model 1 — Secret One. An invitation-only, exclusivity-gated tier. Value derives from access restriction, not content volume. The production overhead is minimal. Think of it as a private API: the scarcity of the endpoint is the value proposition. This works when your audience values association with a restricted group more than any specific deliverable.
Model 2 — PDF Newsletter. Ryan Lee's flagship architecture. Subscribers receive a regularly published PDF — typically 4 to 12 pages — on a defined topic. No video pipeline. No course platform. No community moderation stack. The operational simplicity is the point. Lee's $230K/month program ran this architecture. When people hear that revenue number, they expect a complex system. The actual infrastructure is closer to a well-maintained static site than a full SaaS product.
Model 3 — Give Away / Charge for Depth. Free surface content, paid access to extended analysis. Structurally similar to how most developer tools monetize: the open-source version handles 80% of use cases, the paid tier handles the 20% requiring depth. Substack's paid model operates here. So does most financial research publishing.
Model 4 — Give Away / Charge for Access. Free content as the acquisition layer, paid access to the creator or community as the product. This maps to the open-core model: you give away the code, you charge for the support contract and proximity to the maintainers. The content is marketing. The relationship is revenue.
Model 5 — Gated Real-Time Intelligence. Time-sensitive information delivered before it becomes public. The value driver is timing, not volume. Sports handicapping, trading signals, regulatory intelligence, competitive analysis — any domain where being first to information has measurable value. Think of this as the premium API tier: same data, earlier access window, higher price.
Model 6 — Supporter/Patron. Value-aligned subscribers who pay to sustain the creator's work rather than for a specific deliverable. This is the open-source sponsorship model applied to content. GitHub Sponsors and Patreon run this architecture.
Model 7 — Curation/Summary. Subscribers pay for research and synthesis done on their behalf. The product is time saved, not exclusive information. Developer newsletters that surface relevant releases, security disclosures, and tooling updates from across the ecosystem run this model. TLDR Newsletter, Morning Brew, and most technical digests operate here.
Step 3: The Diagnostic — Architecture Mismatch as the Root Cause of Churn
Here is where the taxonomy becomes operationally powerful.
Many subscription businesses fail not because the model is wrong but because they are running the wrong architecture for their actual production capacity. A founder who has PDF Newsletter production capacity — can write 8 pages per month, does not want to produce video, cannot staff community management — but who is trying to build a Give Away/Charge for Depth program with 30 modules and weekly live sessions is running a mismatch.
The operator is overwhelmed producing content they cannot sustain. The subscriber is overwhelmed consuming content they cannot finish. Churn is the deterministic output of the mismatch.
This is the same mistake engineering teams make when they choose microservices for a two-person team because Netflix uses microservices. The pattern is valid. The fit is wrong. The architecture does not match the team's capacity, and the resulting operational overhead creates failures that have nothing to do with the quality of the code.
Ryan Lee forces you to identify which of the seven models you are actually running and whether it matches your production constraints. That diagnostic exercise alone has more value than most $2,000 business coaching programs in this space.
Step 4: The Constraint System — Why Less Output Produces Better Retention
The Repeatable Flywheel is the foundational loop that runs the entire business: Traffic leads to Opt-in, Opt-in leads to Email, Email leads to Continuity, Continuity funds more Traffic. One loop. Not a branching pipeline of funnels, upsells, downsells, and webinar replays. One loop.
The most counterintuitive element is that the entire business runs on this single cycle. Every successful program Ryan profiles operates on the same flywheel. The operators who struggle are the ones who over-engineer one stage, adding friction to a loop that works best when it is frictionless.
Where most operators break the loop: the transition from email to continuity. The offer demands a commitment level that exceeds the trust the email sequence has built. The flywheel stalls not because traffic dried up but because the final conversion point asks for more than the relationship supports.
Supporting this architecture, the Light as a Feather Principle formalizes what the highest-retention programs share: they deliver content members actually finish. A 4-hour video module creates anxiety for anyone who cannot allocate four hours this week. A 6-page PDF creates zero anxiety. The member reads it during lunch. The psychological contract is fulfilled every delivery cycle.
When the deliverable is not completable, that contract deteriorates into guilt. Guilt is the precursor to cancellation. The member is not leaving because your content is bad. They are leaving because your content made them feel like they failed.
Step 5: The Content Strategy — Fresh vs. Evergreen as a Design Decision
The Fresh vs Evergreen Content Framework separates content into two categories with different operational profiles.
Fresh content has a short TTL. Current events, real-time intelligence, trend commentary. Miss an issue and you have missed something that will not be reprinted. This creates urgency and drives renewal in time-sensitive domains.
Evergreen content has an effectively infinite TTL. Methodologies, frameworks, foundational case studies. New subscribers can start at any point in the archive. The value compounds rather than expires.
Most membership programs blend both without defining the ratio or making deliberate trade-off decisions. The framework forces a strategic choice: are you using freshness as your retention mechanism, or are you building a deep archive that compounds value over time? Both are valid architectures. The failure mode is trying to run both at full production capacity simultaneously.
The Evergreen Numbered Volume Model applies specifically to high-evergreen programs. Publishing by volume number instead of calendar date removes implied urgency, allows new members to enter at any point, and eliminates the anxiety of a missed publication. It is a small interface decision with measurable retention impact.
Step 6: The Validation System — Ship to Learn, Not to Launch
The Beta Launch Framework is the closest thing to a proper MVP process that exists in the membership site space.
The standard membership build: spend six months producing a full content library, design the member portal, record onboarding sequences, launch. By the time you have invested that much, the sunk cost pressure makes objective assessment impossible. You optimize copy, emails, and webinars. You never consider that the model itself might be wrong.
Ryan Lee's version: define the model, write the founding member pitch, collect payments before content exists, use the first cohort's real behavior to validate the architecture before the full production investment is sunk. The founding member cohort is your staging environment. You find the bugs before you push to production.
The Six-Stage Product Launch Framework provides the structured sequence for moving from validation to scale. Guest expert David Schloss, who has managed over $200 million in ad spend, contributes the paid acquisition economics — real CPAs, real AOVs, real stick rates by audience and price point. The section does not teach platform mechanics. It provides a practitioner's framework for determining whether paid acquisition makes economic sense for your specific program before you spend a dollar.
Step 7: The Trade-Off Assessment — What This Course Is and Is Not
What Repeatable covers well:
Real numbers from real programs. Actual churn rates, CPAs, stick rates, and monthly revenue figures — not percentages and hypotheticals. The seven-model taxonomy as a diagnostic and prescriptive tool. A validation framework that de-risks the build. Guest expert case studies with enough operational detail to use as reference architectures.
What Repeatable does not cover:
Platform and technology setup. Entirely out of scope. Which membership platform to use, how to configure billing, how to handle failed payments, how to wire delivery infrastructure — none of this is addressed. If your primary constraint is implementation, you need a different course.
Advertising beyond Facebook/Meta. Schloss brings real expertise but it is concentrated in one channel. YouTube, Google, TikTok, and native advertising are not covered.
No downloadable tools. No worksheets, financial modeling templates, or launch checklists. The frameworks are taught verbally. Implementation tooling is your responsibility.
No unit economics modeling framework. Lee gives you the inputs — real CPAs, real stick rates, real revenue — but building the projection model for your specific program is your work.
Who Should Study This Course
The ideal buyer has some experience with subscription revenue — running a membership, building a newsletter, managing client subscriptions — and is either experiencing unexplained churn or planning a new program and wants to choose the right architecture before committing to a build.
Skip it if you are starting from zero with no audience, need platform setup tutorials as your primary deliverable, or operate in a niche where information changes fast enough that the evergreen production model does not fit.
The Build vs. Buy Calculation
At $299, Repeatable delivers a strategic framework from an operator who has built recurring revenue programs since 2001 with production numbers to back every claim. The implementation layer is yours to build. The strategic clarity is worth the investment for anyone serious about subscription income.
For the cost-conscious: Course To Action carries the full Repeatable summary with audio for $49 per 30 days, alongside 110+ other premium courses. Their AI-powered "Apply to My Business" feature lets you take Ryan Lee's seven models and stress-test them against your specific situation — your audience, your niche, your production capacity. Three AI credits come free on the free tier, along with 10 summaries, no credit card required. That is $299 for one course versus $49 for the complete library with AI-powered analysis.
The subscription model Ryan Lee teaches in Repeatable is the same model that makes Course To Action's pricing work: scoped, completable, high-value deliverables at a price that makes renewal feel obvious. The irony is instructive.
Whether you access the frameworks at full price or through a summary, the core diagnostic — that overwhelm, not dissatisfaction, is the primary driver of subscription churn — deserves serious consideration from anyone building recurring revenue. The fix is not shipping more features. It is choosing the right architecture and constraining output to what your subscribers can actually consume.
That constraint is not a compromise. It is the system.
Top comments (0)