
Operations
Part of Reviewing membership site marketing: strengths, gaps and a verdict
Reading membership site marketing case studies: what to verify before copying a tactic
A method for checking membership site marketing case studies: the record each case must contain, how to check the evidence, and how to test one mechanism locally before copying a result.
What to take away
- Document the platform mechanism before claiming an outcome.
- A tier change can affect access and refunds.
- Replicate the member-value mechanism locally.
- Name the site, its audience, and its price before repeating its result.
Case 1: Stratechery, Dropout, and Defector on tier promises
Membership site marketing case studies often show a revenue screenshot and skip the member job, cohort, and refunds. Fees, labor, and cancellations go missing too.
A decision-grade record covers the audience, offer, price, billing period, and platform. It states the baseline, the intervention, and the dates, plus the acquisition source and the first-value behavior. Then come retention, support, and moderation. Net revenue, mature cost, and confounders close the record.
YouTube's help pages describe how membership levels are set up and reviewed on the platform. A creator who changes or removes a level should check those pages for what happens to existing members, rather than assuming the change is immediate.
A useful case records existing member distribution, promised perks, and communication. It records workload, refunds, cancellations, and later participation before calling a simpler structure successful.
Stratechery is Ben Thompson's tech newsletter, launched in 2013 with paid subscriptions added the following year. Its prices are listed on its own site, and they change, so check them there before using any figure. The model rests on one writer, plus an interview and podcast feed.
Dropout grew out of CollegeHumor and sells a subscription. Check its current price page before comparing any figure.
Defector was launched in 2020 by former Deadspin staff and is owned by its employees. This article gives no Defector price, because none could be checked against a current source.
A hypothetical creator with four overlapping tiers consolidates future enrollment into two clearer levels while honoring current obligations. Tests compare offer comprehension, net starts, perk fulfillment, support contacts and refunds.
Existing members get direct notice and a clear choice. The team reports platform constraints and does not attribute every change to tier count. A membership site marketing checklist keeps those tests in one place, from audience proof through measurement, including 90-day retention.
Case field / Required record
- Context
- Audience, offer, price, billing period, and platform
- Baseline
- Member count, starts, and results before the change
- Intervention
- Exact change, dates, and which members received it
- Outcome
- Net starts, retention, and support contacts after the change
- Cost
- Fees, labor, refunds, and cancellations
- Limit
- Confounders, missing data, and what the record cannot show
Case record fields
- Contextaudience, job, plan, tenure
- Baselineenrollment, value, retention, cost
- Changeexact page and service difference
- Exposurewho encountered the change
- Outcomemember value and net economics
- Limitseasonality, selection, other promotion
Case 2: Patreon, GitHub, and Nebula on sponsor routes
GitHub lets a repository display a sponsor button through a funding file at .github/FUNDING.yml. That confirms the routing mechanism, not sponsorship incrementality, donor intent, or retained value. A case must still document the audience, exposure, completed support, and operating context.
Patreon showed how fast a routing rule becomes a refund problem. In early December 2017 the company announced that patrons would pay processing fees of 2.9% plus 35 cents per pledge. Creators with small pledges objected, and Patreon withdrew the change on December 13, 2017, within about a week. For how cancellations follow a pricing change, see membership site marketing mistakes.
Nebula is a streaming service owned by the creators it features. This article gives no Nebula price, because none was checked against a current source.
Routing vs incrementality
What the button proves
- Mechanism
- Funding links display
- Sponsorship lift
- Not established
- Donor intent
- Not captured
- Retained value
- Not measured
- Operating context
- Not included
What it does not prove
- Mechanism
- Not tested
- Sponsorship lift
- Requires comparison
- Donor intent
- Needs interviews
- Retained value
- Needs renewal window
- Operating context
- Must be documented
A hypothetical maintainer adds a clearly labeled sponsor route to active repositories while keeping the project and issue process public. The team compares completed sponsorships, retained support, and sponsor interviews before and after the change. It reports other announcements, unassigned journeys, and differences among repositories rather than crediting every payment to the button.
Illustrative check: reading one claim
Suppose a case says a tier change "doubled revenue in one month." An illustrative check asks four things. What was the member count before, and did it change? Were existing members moved, or only new buyers? What did refunds and cancellations do in the same month? Was there a price change or a launch at the same time?
If the answers are missing, the claim goes into the record as a lead to test, not as a result. In this illustration, a doubling of net revenue that came mostly from one-time launch sales is a different finding from a lasting rise in renewals.
Build a local replication
- Choose one member job and one uncertain mechanism
- Preserve the current offer, cohort, and operating baseline
- Define member-value, trust, and business measures
- Change the smallest complete experience
- Observe through the relevant renewal window
- Publish the net result, cost, limits, and next decision
- Start from a named case, such as Dropout or Patreon, and copy its mechanism
Audit the published evidence
The FTC advertising substantiation policy requires a reasonable basis before objective advertising claims are disseminated. Apply that U.S. rule to any performance statement in a membership site marketing questions case study, and take advice on the actual facts.
The FTC's consumer reviews and testimonials rule (16 CFR Part 465, effective October 2024) bans fake reviews, sentiment-conditioned incentives and review suppression. Apply those checks when a case study names providers.
Separate provider claims, customer statements, measured records, and independent findings. Record selection criteria, commercial relationships, product version, and study population. Note the method and any missing evidence.
Reproduce one material claim with local data before recommending a provider or copying a case. If the method is unavailable, describe the item as a lead for testing rather than a verified result.
For membership site marketing case studies, keep the evidence record beside the decision. A reviewer can then reproduce the reasoning without memory. Set the next review date for each case and name the change that would trigger an earlier check.
Record rejected options and the chosen path; the original constraint may later change. Use the same definitions in the interface, export, meeting note, and correction log.
Common questions
Is a testimonial a case study?
No. It is one person's reported experience unless supported by transparent context and operational evidence.
Can a platform screenshot prove attribution?
No. Preserve source definitions and explain identity, cross-device, and selection gaps.
How many cases are enough?
Enough comparable replications to support the decision without exposing the entire membership to an uncertain change.
Which named cases transfer best?
Copy the mechanism, not the figure. Stratechery's plan structure and Patreon's fee reversal answer different questions, and neither is a benchmark for another site.







