Operations & Measurement
How to run a paid community audit: a step-by-step process for operators who want real numbers
Most paid community operators know roughly when things are going wrong — cancellations feel heavier than usual, event attendance has drifted down, revenue growth has flattened — but they do not know which specific number is the binding constraint. A paid community audit replaces that feeling with a number. It is three layers of structured measurement — member health, programming effectiveness, and unit economics — that together tell you exactly which problem is the most expensive one, in a form specific enough to act on. This guide walks through each layer step by step, with the exact data pulls, the calculations, the benchmarks, and the sequencing rule for which finding to fix first.
Why a paid community audit has three layers, not one
Most operators who run any kind of community review focus on a single number — usually monthly cancellation rate, sometimes event attendance — and make decisions from it. The problem is that a single number has no diagnostic specificity. A 6% monthly cancellation rate tells you how many members are leaving; it does not tell you which tenure window they are concentrating in, which means it cannot tell you what intervention to run. A 40% event attendance rate tells you fewer members are coming to events; it does not tell you whether the problem is the topic, the time slot, the format, or the fact that the members attending events are not the members at churn risk.
Three layers are required because the three dimensions of a paid community — its member health, its programming, and its economics — each have separate root causes and separate interventions. A community can have healthy member activation rates and terrible unit economics because it is priced below its value. A community can have excellent economics and a deepening programming void that has not yet shown up in the cancellation numbers because it operates on annual subscriptions whose billing dates are 5 months away. A community can have strong programming attendance and a month-one cancellation concentration because new members are not finding the events in their first week. Each of these scenarios has a specific fix; all three scenarios look similar at the level of “things feel off.”
The audit is a mechanism for moving from the feeling to the number, and from the number to the specific intervention. It takes 90 minutes to two hours. The constraints are your billing data pull (which varies by tool) and your Slack workspace admin access. Everything else is arithmetic.
Layer 1: Member health — the three numbers that matter
Member health covers three measurements: 7-day activation rate, contribution rate, and tenure-segmented cancellation distribution. All three are calculated from the same two data sources: your billing export and your Slack workspace admin panel.
Step 1: Pull the data
From your billing system, download the full subscription export as a CSV. You need three fields per row: member email, original subscription start date, and cancellation date (leave blank for active members). In Stripe, this is the subscription export filtered by your community’s product. In Memberstack, it is the Member List export with plan and status filters. In Outseta, it is the Subscription report. In Memberful, it is the Member report with the “billing start” and “cancelled at” columns.
From your Slack workspace admin panel (accessible at your-workspace.slack.com/admin/stats for workspace owners and admins), you need three numbers: the total active member count, the weekly active member count (Slack defines this as members who posted, reacted, or replied in the past 7 days), and the member list export, which shows each member’s join date and last active date. The member list is available under the “Members” tab in workspace admin as a downloadable CSV.
If your billing system and Slack use different email addresses for the same member — which is common in communities that accept payment via one address and use a different address for the Slack invite — you will need to manually reconcile a subset. Focus on the most recent 30 days of joins, since that is the cohort where the activation calculation matters most. Reconciling the full member base is not necessary for the audit; you need the first 30 days of new members to calculate activation rate, and the full cancellation list to build the tenure table.
Step 2: Calculate the 7-day activation rate
Take all members who joined in the last 30 days. From the Slack member list, identify which of those members have a last-active date more than 7 days after their join date and show at least one posting activity in their Slack record. Members who have only read but never posted, replied, or reacted are “observers” — they are not activated. The 7-day activation rate is: (members who completed at least one contribution event within 7 days of joining) ÷ (total new members in the 30-day period) × 100.
Benchmarks: a healthy activation rate is 65–75% for communities with a structured onboarding sequence. Communities without a structured sequence typically see 35–50%. If your rate is below 50%, the member health problem is an onboarding gap. See the paid community member activation rate guide for the full definition of qualifying contribution events and the four interventions ranked by activation ROI.
Step 3: Calculate the contribution rate
The contribution rate is the share of all active members (not just new ones) who contributed in the last 30 days. Take the Slack weekly active member count from admin stats, multiply by 4 for a rough monthly estimate, divide by total members, and multiply by 100. A more precise version pulls the monthly active member count from admin stats directly if your Slack plan provides it.
A healthy contribution rate for a paid community with 200–500 members is 30–45%: roughly one in three members contributes in any given month. Below 20% signals a passive-observer accumulation problem where the community has a large body of members who are paying but not participating — members who are one billing renewal away from cancelling because a consumption product that requires $99/month is substitutable. Above 50% is uncommon and typically indicates a small, very engaged early-stage community; watch for it to normalise as membership scales.
Step 4: Build the tenure-segmented cancellation table
In your billing export, add a column for “tenure at cancellation”: the number of days between the subscription start date and the cancellation date. Filter to cancelled rows only. Create four buckets: 0–30 days (month-one cancellations), 31–90 days (months 2–3), 91–210 days (months 3–7), and 211–395 days (approaching annual renewal). Count the cancellations in each bucket over the last 6–12 months.
To calculate the per-window rate: divide month-one cancellations by total new members in the period. Divide months 2–3 cancellations by members who survived beyond day 30. Divide months 3–7 cancellations by members who survived beyond day 90. Divide the annual window cancellations by members who survived beyond day 210. Compare each window’s rate against the benchmarks: month-one healthy is under 4% (above 8% signals messaging misalignment); months 2–3 healthy is under 8% of surviving cohort (above 12% signals activation lag); months 3–7 healthy is under 6% per month of surviving cohort (above 9% signals programming void); annual non-renewal healthy is under 25% (above 35% signals relationship-thin failure). The window with the highest excess rate is Layer 1’s primary finding. For the full root-cause analysis of each tenure window, see the paid community cancellation rate guide.
Layer 2: Programming effectiveness
Programming effectiveness measures whether the community’s events, threads, and content are working — not just whether they are happening. There are three measurements: event attendance rate, repeat attendance rate, and content engagement concentration.
Step 5: Calculate event attendance rate
For each live event you ran in the last quarter (AMAs, office hours, cohort calls, workshops), pull the actual attendee count from your video call tool or Slack event log. Divide by total active members at the time of the event, not total members — using total members inflates the denominator with inactive members who were never realistic attendees. Multiply by 100 for the rate.
A healthy attendance rate for a paid community event with at least 7 days of promotion is 15–25% of active members per event. Below 10% signals either a topic-fit problem (the event topic is not matching the members’ current priority) or a format problem (the time slot, duration, or modality does not fit the member base’s working patterns). Above 30% per event is excellent and typically indicates either a highly engaged early-stage community or a particularly well-positioned guest or topic. When attendance is below 10%, run a poll in the community: “what one topic would make you clear your calendar this month?” The top answer usually identifies the gap between your programming calendar and your members’ current priority.
Step 6: Calculate repeat attendance rate
The repeat attendance rate is the share of event attendees who attended more than one event in the quarter. Pull the attendee list for each of your last three or four events, merge them, and count the members who appear in more than one list. Divide by the total unique attendees across all events, multiply by 100.
A healthy repeat attendance rate is 40–60%: roughly half of the members who attend one event come back for another. Below 30% signals that the community’s events are producing one-time engagement — members attend once, do not find a compelling reason to return to the next event, and the programming is not building a recurring attendance habit. Above 60% is strong but watch for concentration: if 60% repeat attendance means the same 20 members attend everything while the rest of the community never comes, that concentration problem will appear in the month 5–7 cancellation data as a programming void for the non-attending majority.
Step 7: Measure content engagement concentration
In Slack, check the last 30 days of your top channels for the number of unique members who posted or replied. Count the members who contributed in 3 or more different threads across the channel. Divide by total members who posted at all. A healthy community has 25–40% of its contributors engaged across multiple threads (broad engagement); a concerning community has 70–80% of its activity generated by fewer than 10 members (concentrated engagement). High concentration is a fragility signal — when those members reduce their participation, the community’s visible activity collapses faster than membership numbers would suggest.
Layer 3: Unit economics
Unit economics covers three numbers: average member LTV, member acquisition cost (MAC), and gross margin per seat. These are the numbers that determine whether the business is viable at scale, independent of how the community feels to operate.
Step 8: Calculate average member LTV
From your billing export, calculate the total revenue generated per cancelled member: multiply their subscription price by the number of months between join date and cancellation date. Average this across all cancelled members in the last 12 months. This is your realised LTV for the churned cohort. Separately, calculate the projected LTV for active members using their current tenure and the average LTV of the churned cohort as a ceiling.
A practical shortcut: if your community has been running for at least 18 months, take total revenue in the last 12 months and divide by the number of new members who joined in the first 6 months of that period. This rolling-average approach accounts for the full monetisation window without waiting for the entire cohort to conclude. Benchmarks: a $99/mo community with 6-month average tenure has a member LTV of approximately $594; with 18-month average tenure (well-run) the LTV is approximately $1,782. The tenure extension from 6 months to 18 months — achievable through structured programming and relationship facilitation — triples the LTV without changing the price.
Step 9: Calculate member acquisition cost
Member acquisition cost is total marketing and outreach spend in a period divided by new members acquired in that period. Include your time at an honest hourly rate for outreach activities (email, social, community appearances) that are not automated. Most early-stage paid community operators find their MAC is dominated by time cost rather than paid advertising: 10 hours of personalised outreach per month at $100/hr is $1,000 MAC on 10 new members. That is a viable MAC if your LTV is above $2,000 and unsustainable if your LTV is $400.
The LTV-to-MAC ratio is the most diagnostic single number from the economics layer. A healthy paid community has a ratio of at least 3:1. Below 2:1 the economics are fragile — any increase in CAC (which happens naturally as the community scales past the founder’s personal network) produces a business that loses money on each new member. The 3:1 threshold provides enough margin to absorb the platform costs, operator time, and content production without requiring volume to subsidise early losses.
Step 10: Calculate gross margin per seat
Gross margin per seat is monthly subscription price minus the direct cost of serving that member per month. Direct costs include: your video call platform (Zoom, etc.) prorated per member, any per-seat tools in your stack, the Slack tier cost prorated, and the operator time cost for community management prorated per member. Indirect costs (content production, newsletter, tooling) are typically not included in gross margin but should be tracked separately as overhead.
A typical paid Slack community at $99/mo per member has gross margins of 70–80% if the direct tooling costs are under $20/member/month and the operator is not fully allocating their time to community management. Communities that price at $49/mo and carry $25 in direct per-seat costs have gross margins of roughly 50%, which is viable but leaves little room for error on MAC or platform cost growth. This calculation is the basis for the pricing review — if gross margin is below 60%, the pricing is too low relative to the cost structure, not necessarily too high relative to the value delivered.
Synthesising the findings: the sequencing rule
After running all three layers, you have up to nine numbers (activation rate, contribution rate, four tenure-window rates, attendance rate, LTV-to-MAC ratio, gross margin). Most operators find two to four of these numbers outside their healthy range. The sequencing question is: which finding to act on first.
The sequencing rule is: fix the earliest failure first. Member health problems upstream of economics problems mean the economics will never reach their ceiling, regardless of how well the downstream interventions are designed. An activation rate below 50% (Layer 1) means a large share of every incoming cohort is not receiving the value the community claims to deliver — fixing that before optimising the programming calendar or the pricing is the highest-ROI intervention. A month-one cancellation concentration (Layer 1) means a significant fraction of acquired members are exiting before they can be retained by any programming intervention (Layer 2) — fixing month-one misalignment before redesigning the programming calendar is the correct sequence. A 2:1 LTV-to-MAC ratio (Layer 3) that is caused by a low LTV (because of a month 5–7 programming void producing early cancellations) is fixed by addressing the void — not by cutting outreach cost.
The rule has one exception: if gross margin is below 50%, fix the pricing before anything else. Retention improvements do not compound into economics improvements if the margin per retained seat is too thin to cover the cost of the retention programming. In practice, this exception applies to communities priced below $49/mo — and most operators who price that low already know the pricing is wrong but have not had a number to justify raising it. The gross margin calculation is that number.
Once the primary finding is identified and the intervention is chosen, run it for one full cohort cycle (6–8 weeks) before re-running the affected layer. The most common audit mistake is running all interventions simultaneously — the measurement becomes ambiguous and no individual intervention can be properly evaluated. For the full intervention playbook for each tenure window, see the paid community retention strategies guide. For a diagnostic starting point before running the full audit, the Onboarding Health Check identifies the most likely Layer 1 problem in five questions.
Frequently asked questions
How long does a paid community audit take?
A three-layer paid community audit — member health, programming effectiveness, and unit economics — takes approximately 90 minutes to two hours for a community with 12 months of billing history and a standard Slack workspace. The member health layer takes 30–45 minutes: export the billing subscription list, calculate tenure-at-cancellation for each cancelled row, and bucket into the four tenure windows. The programming layer takes 20–30 minutes: pull event attendance from your calendar or Slack event log and calculate the repeat-attendance rate. The economics layer takes 20–30 minutes: calculate average LTV from billing data, divide by member acquisition cost, and calculate gross margin per seat. The bottleneck is almost always the billing data pull, which varies by tool — Stripe and Memberstack exports are clean; older tools may require some reconciliation.
What data do I need to run a paid community audit?
You need two primary data sources: your billing system’s subscription export and your Slack workspace admin panel. From the billing export, you need three fields per member: original join date, cancellation date (if applicable), and monthly price. These are available in Stripe, Memberstack, Outseta, and Memberful as CSV downloads. From Slack workspace admin, you need total members, weekly active members, and the member list with join date and last active date. If your billing system and Slack use different email addresses for the same member, reconcile the most recent 30 days of joins — that is the cohort that matters most for the activation-rate calculation.
What is a healthy activation rate for a paid Slack community?
A healthy activation rate for a paid Slack community is 65–75% within 7 days of joining, measured as the share of new members who complete a qualifying contribution event (a substantive first post, a direct reply, or active channel reading defined as 10+ messages). Communities with a structured Day 0, Day 3, Day 7 onboarding sequence typically achieve 70–80% activation within 7 days. Communities without a structured sequence typically achieve 35–50%. Below 50% indicates a serious onboarding gap that is worth fixing before addressing any other community metric.
How do I calculate LTV for a paid community member?
Member LTV is: average monthly price × average tenure in months. Calculate average tenure from your billing export by averaging the number of months between join date and either cancellation date (churned) or today (active) across all members. A practical shortcut: total revenue in the last 12 months ÷ new members who joined in the first 6 months of that period. This rolling-average approach accounts for the full monetisation window. A healthy LTV-to-MAC ratio is at least 3:1; below 2:1 the economics are fragile even at scale.
How often should I run a paid community audit?
Run a full three-layer audit quarterly. Run the member health layer alone monthly. The monthly health check — just activation rate, contribution rate, and 30-day cancellation count — takes 20 minutes and catches early signals before they compound into a quarterly problem. Most operators who run both find the monthly check rarely produces a surprise that the quarterly audit would not have caught; its primary value is keeping the operator habituated to looking at the numbers regularly rather than only when something feels wrong.