Community Structure Reference
Paid community cohort model — structural comparison, activation benchmarks, and operator decision reference card
This page is a structured reference card for paid Slack community operators deciding between cohort, always-open, and hybrid intake models. It covers a four-dimension structural comparison table (member start timing, programming structure, social graph formation, and renewal mechanics across all three models), month-one activation rate benchmarks by model, month-three retention benchmarks, a six-row operator archetype decision table, an eight-item cohort minimum viable checklist, and a six-step hybrid model implementation sequence — all in table and checklist form, not narrative. For the strategic reasoning behind these structural choices, including the isolation anxiety mechanism, the peer density threshold, and the cohort completion cliff, see the companion post: Paid community cohort model — when to run cohorts, when to stay always-open, and how to bridge both. This card is for the operator who already understands the “why” and needs the benchmarks and decision criteria in scannable reference form.
TL;DR
Cohort activation rate: 60–80% (vs. 40–60% always-open with onboarding; vs. 15–30% always-open without onboarding). Cohort month-3 retention: 55–75% (vs. 35–55% always-open). Minimum cohort size: 20 members/intake. Switch prerequisites: waitlist ≥100 qualified applicants + intake capacity ≥20/window + sequential curriculum. Hybrid model: rolling intake + quarterly 8–10 week programming windows; captures lockstep programming advantage without synchronized intake requirement.
Structural comparison: cohort vs. always-open vs. hybrid
The three paid community intake models differ on four structural dimensions that determine activation rate, retention, and operator workload. The table below covers member start timing, programming structure, social graph formation mechanics, and renewal mechanics for each model. “Operational implication” gives the downstream operator requirement that follows from each structural choice — the cell most operators skip when evaluating which model to run.
| Dimension | Cohort | Always-open | Hybrid |
|---|---|---|---|
| Member start timing | Synchronized. All members in a given cohort join within a defined intake window (typically 1–2 weeks). No rolling admission between intake windows. Waitlist holds applicants between windows. | Continuous. Members join at any point. No waitlist required. A new member joins into whatever state the community is currently in. | Continuous intake, synchronized programming. Members join at any point, but are invited to join the current quarterly programming window as their structured onboarding experience if they join within 3 weeks of a window start. |
| Programming structure | Sequential curriculum. Each week of the cohort period advances along a defined learning or outcome progression. Weeks 1–2: orientation and peer introductions. Weeks 3–6: core curriculum delivery. Weeks 7–8: application and peer accountability. Week 9–10: completion and renewal framing. | Evergreen + event cadence. Core value comes from accumulated content archive and community access, not sequential curriculum. Programming is a repeating calendar of events (live sessions, async challenges, spotlights) rather than a one-time progression. | Evergreen baseline + quarterly progression windows. Standard always-open programming runs continuously. Four times per year, an 8–10 week programming window runs a defined event and challenge sequence that all current members participate in together. |
| Social graph formation | Peer-dense and time-bounded. All members are at the same curriculum point at the same time. Social comparisons are immediate (visible peers with same starting conditions). Peer accountability relationships form within weeks 1–3. Social graph is cohort-internal and tight. | Distributed and asynchronous. A new member joins a community where members are at different points in their engagement arc. Social graph formation depends on the introductions channel and operator-facilitated peer introductions. Typically slower: meaningful peer relationships form in weeks 4–8 on average. | Distributed baseline + window-dense formation. Members outside a programming window follow the always-open social graph formation pattern. Members who join within 3 weeks of a window start experience cohort-style peer formation within the window period (8–10 weeks of synchronized participation). |
| Renewal mechanics | Milestone-based. Renewal is framed as enrollment in the next cohort (a step forward), not subscription continuation. The week-9 bridge conversation is the primary renewal intervention: completers who discuss their next-step goal during week 9 renew at 20–35pp higher rates than completers who receive a standard renewal email. | Subscription-based. Renewal is framed as continued access. No natural milestone creates a renewal conversation. The primary renewal intervention is a pre-renewal sequence starting 6–8 weeks before the annual date. Without a structured renewal sequence, renewal depends on habit and passive value perception. | Hybrid: subscription baseline + window completion renewal trigger. Standard subscription renewal framing applies. Members who complete a programming window receive a window-completion renewal conversation framing the next window as a specific reason to continue. Produces renewal rates between always-open and full cohort benchmarks. |
The most common structural error: running a cohort model without a sequential curriculum. Operators who synchronize intake timing but deliver the same evergreen content and event calendar an always-open community would use get cohort intake complexity without cohort activation benefits. The activation rate advantage of cohort structures (60–80% vs. 40–60%) comes from lockstep curriculum progression — the fact that all members are working through the same material at the same time and can compare notes, share blockers, and measure their progress against peers. Without a sequential curriculum, synchronized intake creates a cohort name but not a cohort dynamic.
Activation rate benchmarks by model
Month-one activation rate is defined as the percentage of new members who complete all three of the following behavioral events within their first 30 days: (1) post in an introductions or equivalent channel, (2) select a stated goal track or category, and (3) subscribe to or actively open at least two content channels. These three gates predict 90-day renewal better than any other behavioral indicator. The benchmarks below reflect communities with at least 50 paying members and at least three full cohort or monthly intake cycles of measurement.
| Model | Month-1 activation rate | Primary driver of rate | Primary driver of shortfall | Activation-to-3-month retention correlation |
|---|---|---|---|---|
| Cohort | 60–80% | Shared start eliminates isolation anxiety (no member is joining into a community of strangers who have been there longer). Lockstep curriculum creates peer accountability within the first 2 weeks. | Cohort size below 20 (peer density disappears). No sequential curriculum (cohort timing without curriculum progression does not produce the peer comparison mechanism). Day 0 DM adapted for always-open rather than cohort context. | High (0.82). Activated cohort members renew at month 3 at rates 18–25pp above activated always-open members, because the cohort completion milestone is a natural renewal trigger. Activation rate benchmarks reference card. |
| Always-open with structured onboarding | 40–60% | Day 0 DM + conditional Day 3 nudge + Day 7 operator scorecard. Structured three-touch sequence removes the friction of not knowing what to do first. | Isolation anxiety in weeks 1–2 (joining a community where all visible peers have been there longer). No peer comparison available until operator facilitates introductions. Month-2 programming void after three-touch onboarding ends. | High (0.79). Activated always-open members with a structured onboarding sequence reach month-3 retention benchmarks of 50–65%, which is 15–20pp above always-open communities without structured onboarding. Retention strategies guide. |
| Always-open without structured onboarding | 15–30% | Self-selection: highly motivated members who would have activated in any environment. | No Day 0 DM means no clear first action. No conditional Day 3 nudge means no recovery for week-1 non-posters. No Day 7 scorecard means operator has no visibility into stalled members until they cancel. Combined: 70–85% of new members experience week-one ambiguity with no intervention. | Moderate (0.71). Low base rate means even high activated-to-retained conversion produces community-level retention rates of 35–45% at month 3. Onboarding health check diagnostic. |
| Hybrid (rolling intake + quarterly programming windows) | 50–70% | Members who join within 3 weeks of a programming window start receive near-cohort activation experience. Members who join mid-window receive structured onboarding into an active programming period (higher baseline than standard always-open). | Members who join in the 4–6 weeks between programming windows receive always-open onboarding without cohort context, producing always-open activation rates (40–60%) for that intake subset. The community-level activation rate reflects the mix of within-window and between-window joiners. | High for within-window joiners (0.80). Moderate for between-window joiners (0.75). Community-level activation-to-retention correlation depends on the ratio of within-window joiners to total intake. |
The activation rate gap between always-open without onboarding (15–30%) and always-open with structured onboarding (40–60%) is larger than the gap between structured always-open and cohort (40–60% vs. 60–80%). For operators currently running always-open without a Day 0 DM + Day 3 nudge + Day 7 scorecard sequence, implementing structured onboarding produces a larger activation rate improvement than switching to a cohort model. Fix always-open onboarding before evaluating a model change.
Month-3 retention benchmarks by model
Month-three retention is defined as the percentage of new members who remain active and paying at day 90 from their join date. A member is “active” for retention purposes if they have opened the Slack workspace and taken at least one behavioral action (post, reaction, or DM) within the 30-day window ending on day 90. Month-three retention is the primary lagging indicator of community health because it captures whether members who passed the activation gate continued to find value through the onboarding-to-engagement transition — the most common point of churn outside week one.
| Model | Month-3 retention benchmark | Primary driver of retention | Primary driver of shortfall |
|---|---|---|---|
| Cohort | 55–75% | Peer relationships formed during cohort period persist into months 2–3. Cohort members have named peers they expect to see at week-6 and week-8 events. Completion milestone framing prevents the subscription-inertia fade that causes month-2–3 churn in always-open communities. | Completion cliff: cohort-1 completers who do not receive a week-9 bridge conversation default to treating completion as an exit point. Month-3 retention for completers without a bridge conversation falls 15–20pp below completers who had one. Alumni layer absence also reduces month-3 retention by removing the post-completion identity anchor. |
| Always-open with structured onboarding | 35–55% | Activated members who formed one or more named peer relationships during weeks 1–4 retain at the high end of the benchmark. Operator-facilitated peer introductions (direct “@A meet @B, you both work on X” messages) are the highest-impact mid-range retention lever. | Month-2 programming void: the three-touch onboarding sequence ends at day 7, and without a deliberate week-4 and week-8 re-engagement moment (async challenge, member spotlight, live event), members who did not form peer relationships in week 1 quietly disengage. The month-2 churn cliff accounts for 30–40% of total annual churn in communities without mid-range programming. |
| Always-open without structured onboarding | 20–40% | Self-selected motivated members who activated without onboarding and formed organic peer relationships. This segment is real but small: 15–30% of new members activate, and of those, a subset form durable relationships. The retained group at month 3 is primarily that subset. | Low month-1 activation (15–30%) means 70–85% of members never experience the value that produces month-3 retention. The month-3 retention rate for this model reflects the activation rate floor as much as the retention dynamics of activated members. |
| Hybrid | 45–65% | Within-window joiners retain at cohort benchmarks (55–75%) because the programming window creates the peer relationship density that drives month-3 retention. Between-window joiners retain at always-open benchmarks (35–55%). | Between-window joiner month-3 retention dominates community-level retention if the ratio of between-window joiners is high. Operators who admit large between-window cohorts without supplementary re-engagement programming see hybrid retention rates converge toward always-open benchmarks. |
Operator archetype decision table
The recommended model depends on three operator variables: the nature of the community outcome (skill-based with measurable progression vs. network access vs. mix), the operator’s intake capacity (ability to fill a minimum viable cohort of 20 members per intake window), and community size. The table below gives the recommended model for six operator archetype combinations. “Primary constraint” names the variable that is most likely to make the recommended model fail in practice if not addressed before switching.
| Operator archetype | Outcome type | Intake capacity | Recommended model | Primary constraint |
|---|---|---|---|---|
| Skill progression operator | Measurable skill acquisition with defined milestones (e.g., “close your first $10k month,” “ship a product MVP,” “write a newsletter with 500 subscribers”) | ≥20 paying members per intake window, sustainable across 3+ consecutive windows | Cohort | Sequential curriculum completeness. A cohort model requires 8–10 weeks of defined curriculum before the first intake. Operators who launch a cohort without a full curriculum tend to run improvised sessions that produce inconsistent peer experiences and high completion-cliff churn. |
| Accountability-dependent outcome operator | Outcomes that require sustained peer accountability to achieve (e.g., revenue goals, fitness targets, writing output, fundraising). The peer accountability mechanism is part of the value proposition, not incidental to it. | ≥20 per window | Cohort | Cohort size. Accountability pair formation requires enough peers for members to find an accountable match within their goal track. Below 20 members, goal-track diversity often produces cohorts where a given goal track has 2–3 members — not enough for pair formation if there are personality mismatches. |
| Network access operator | Primary value is access to a specific network of peers (e.g., founders at a specific stage, operators in a specific niche, buyers in a specific category). The value compounds with community size — more members make the network more valuable. | Any (no intake minimum required) | Always-open with structured onboarding | Month-2 programming void. Network access value compounds over time, but members who do not form named peer relationships in weeks 1–4 disengage before the network compounds for them. The operator must add week-4 and week-8 re-engagement programming to prevent the month-2 churn cliff that always-open network communities are most susceptible to. |
| Expertise access operator | Primary value is access to operator or curated expert time (e.g., weekly Q&A with a domain expert, curated research or deal flow, access to a specific practitioner’s knowledge). Network effects are secondary. | Any | Always-open with structured onboarding | Operator time. Expertise access communities scale by limiting direct operator exposure, not by adding cohort structure. Switching to cohort intake adds intake management complexity without improving the core value delivery mechanism (access to expert time or curated content). |
| Mixed outcome operator with high intake | Community value is a mix of network access, skill progression, and accountability, without a dominant single outcome type. Members join for different reasons. | ≥15 per month (total across all join dates; not synchronized) | Hybrid | Programming window design. The hybrid model’s retention advantage comes entirely from the quarterly programming window quality. A hybrid model with a low-effort programming window (3–4 events that any always-open community would run) produces always-open benchmarks, not hybrid benchmarks. The window must have enough structured progression to create the peer relationship formation that drives the benchmark gap. |
| Intake-constrained skill operator | Skill-based outcome (would benefit from cohort model) but operator cannot reliably fill 20 seats per synchronized intake window. | <20 per synchronized window; but ≥10–15 per month rolling | Hybrid | Sequential curriculum within windows. The hybrid model for this archetype works by concentrating curriculum delivery into quarterly 8–10 week windows while accepting intake continuously. The curriculum must be designed to work for members who join the window at different points in their overall community tenure, not just for a fully synchronized cohort of new joiners. |
The most common model mismatch: running always-open for a skill-progression outcome. Operators whose community value is a measurable skill acquisition outcome often start with always-open intake because it is simpler, then wonder why month-3 retention is below 45%. The structural mismatch is that skill progression requires lockstep peer accountability — the mechanism cohort structure produces automatically and always-open requires explicit operator intervention to replicate. If your outcome type is skill-progression and your month-3 retention is below 50%, evaluate cohort or hybrid model before adding more always-open programming.
Cohort minimum viable checklist
An operator should not switch from always-open to a full cohort model until all eight items below are in place. Missing any item before the first cohort intake produces predictable failure modes noted in the “failure mode if missing” column. The checklist is ordered from the most common missing item (waitlist size, item 1) to the least commonly checked but frequently missed item (Day 0 DM cohort adaptation, item 8).
- Waitlist of 100 or more qualified applicants. “Qualified” means applicants who match your ICP on job title, community goal, and willingness to pay at your stated price. A waitlist of 100 unqualified applicants (collected via a generic landing page without qualification questions) provides false confidence: the first cohort fills, the second does not, and the intake model collapses before the third. Run at least a two-question qualification screen (goal type and current situation) before counting a waitlist entry as qualified. Failure mode if missing: cohort 2 or 3 cannot fill to 20 members; underfilled cohorts produce below-always-open activation rates and peer accountability failures.
- Reliable intake capacity of 20 or more paying members per window. Test this before the first cohort by running two waitlist conversion sequences and measuring conversion rate from waitlisted qualified applicant to paying member. If conversion is below 30%, the waitlist is not converting at the rate needed to sustain 20-member cohorts without constant waitlist refilling. Fix conversion before the first cohort intake. Failure mode if missing: cohort sizes fluctuate below 20; peer accountability relationships do not form; activation rate converges to always-open baseline.
- Sequential curriculum for 8–10 weeks of cohort period. The curriculum must define week-by-week learning objectives, one primary deliverable per week (a post, a completed exercise, a peer review), and the peer accountability mechanism that operates across the weeks (accountability pairs, small groups, or public tracking). A curriculum that is mostly live Q&A sessions without a defined progression is a programming calendar, not a sequential curriculum. Failure mode if missing: cohort model name without cohort activation advantage; members experience always-open dynamics within a synchronized intake structure.
- Live event capacity for at least one synchronous event per week during the cohort period. Cohort communities require at least one live moment per week — a session, an AMA, a peer showcase — for the peer accountability relationships to form and maintain. Async-only cohort delivery produces 20–30pp lower activation rates than live-anchored cohort delivery, because the live event is the primary peer recognition moment that converts individual participation into social accountability. Failure mode if missing: peer accountability relationships remain shallow; completion cliff is 15–25pp worse than live-anchored cohort benchmarks.
- Renewal framing prepared before the first cohort starts. The week-9 bridge conversation (the renewal intervention that produces 20–35pp higher re-enrollment than a standard renewal email) must be scripted before the first cohort completes. The conversation has a specific structure: acknowledge what the member completed, name the specific gap between where they are and the next-level outcome, frame cohort 2 as the step toward that outcome — not as continued access. Operators who improvise the week-9 conversation in week 9 produce outcomes no better than subscription renewal emails. Failure mode if missing: completion cliff wipes 20–35pp of potential renewal rate on the first cohort; the pattern is hard to recover because cohort-1 completers who lapsed are the highest-LTV re-engagement target.
- Alumni layer designed before the first cohort completes. Cohort completers need a post-completion identity within the community — a channel, a role, or a programming responsibility that is different from their in-cohort identity. Without an alumni layer, completers have no reason to stay active after week 10 and often reduce their activity to passive subscription levels between cohorts. The alumni layer does not need to be elaborate: an #alumni channel with a monthly async discussion and access to cohort-2 live events is enough. Failure mode if missing: month-3 retention for completers drops to always-open levels (35–55%) because the post-completion community anchor disappears.
- Week-9 bridge conversation scripted and owner assigned before intake opens. Separate from the renewal framing (item 5), the week-9 bridge conversation must have a named owner (operator or a trained community manager) and a trigger condition (week-9 start = all completers receive a specific DM initiating the conversation). The script and owner should be in place before intake opens because the cohort period is high-operational-load and the bridge conversation is the highest-leverage renewal intervention: it is easy to deprioritize in week 9 and very hard to recover. Failure mode if missing: bridge conversation does not happen; completion cliff produces standard renewal email outcomes (15–25pp lower re-enrollment than bridge conversation).
- Day 0 DM adapted for cohort context. The standard always-open Day 0 DM (three-step checklist: introduce in #intros, pick your goals, subscribe to 2 channels) must be rewritten for cohort context. The cohort Day 0 DM should reference: the cohort start date, the first live event (with a direct calendar link or RSVP), the accountability pair formation process (how and when they will be matched with a peer accountability partner), and the week-by-week structure that begins this week. An always-open Day 0 DM sent to a cohort joiner produces the same isolation anxiety the cohort structure is supposed to eliminate — because the DM does not tell the member that there are 19 other people starting today. Failure mode if missing: cohort joiners who receive an always-open DM report feeling like they joined a generic community, not a cohort; peer accountability formation is delayed by 1–2 weeks.
Hybrid model implementation steps
The hybrid model is implemented in six steps that convert an always-open community into a community with quarterly programming windows without requiring synchronized intake, a waitlist, or a sequential curriculum from day one. Each step can be executed without the next; the steps are sequenced from lowest operational overhead to highest. Steps 1–3 provide most of the activation rate benefit; steps 4–6 provide most of the retention benefit.
Steps 1–3 — activation layer| Step | What to do | Operational requirement | Expected activation impact |
|---|---|---|---|
| 1. Group same-month joiners | Tag every new member with their join month in your member management tool. Create a private Slack channel for each monthly intake cohort (#jan-cohort, #feb-cohort) and invite all same-month joiners to their month channel. Post a brief cohort introduction message in the channel naming all members who joined this month and pointing to the first async challenge. | 5–10 minutes per new member. Requires Slack channel creation at the start of each month and member management tagging discipline. The monthly cohort channel is the peer comparison surface that reduces isolation anxiety: new members can see that others started at the same time. | +5–15pp month-one activation rate above baseline always-open. Primary mechanism: reduces isolation anxiety by making same-start peers visible. Most impactful for communities where the between-window joiner experience was previously indistinguishable from joining an established community as the only new member. |
| 2. Adapt Day 0 DM for monthly cohort context | Update the Day 0 DM to reference the new member’s monthly cohort channel (“You’ve joined with 8 other members this month — say hi in #jan-cohort”), the current month’s async challenge, and the next live event. The monthly cohort reference turns the always-open Day 0 DM into a cohort-aware onboarding message without requiring synchronized intake. | Monthly update to the Day 0 DM template to reference the current month and cohort channel. A mail-merge or template variable for the current cohort channel name automates this if the community uses a bot-based Day 0 DM. Manual update if the DM is sent by the operator directly. | +3–8pp month-one activation rate above Step 1 alone. Primary mechanism: the cohort channel reference creates an immediate social anchor (a channel the member is expected to post in) distinct from the main community channels, which reduces the “which channel do I post in first?” friction that delays first posts. |
| 3. Add week-3 async challenge | Run one async challenge per monthly cohort at the 3-week mark (day 18–22 from join date). The challenge should be a specific action tied to the community outcome (share a work-in-progress, post a 3-sentence update on your stated goal, introduce one peer you have DM’d this month). Send the challenge to the monthly cohort channel, not the main community. Challenge is cohort-visible, not community-wide. | One challenge post per month per active cohort channel. At steady state (if multiple monthly cohorts overlap), one challenge post per cohort channel per month — typically 2–3 channels running in parallel. Challenge design can be reused across months with minor customization for the current community context. | +8–15pp month-one activation rate above Step 2. The week-3 async challenge is the highest-impact single addition to an always-open onboarding sequence: it creates a second activation gate (beyond the Day 0 intro post) at the point where always-open members most commonly disengage (days 14–28). Communities running only a Day 0 DM without a week-3 challenge see most of their non-activator disengagement in this window. |
| Step | What to do | Operational requirement | Expected retention impact |
|---|---|---|---|
| 4. Add week-6 live event | Host one live event per quarter anchored at the 6-week mark of the quarterly programming window. The event should be structured around a topic at the application stage of the community outcome: not introductory content (week-1 material) and not advanced content (post-completion material), but specifically the challenge that members who have been in the community 4–8 weeks are most likely to face. Invite all active members, not just the monthly cohort. | One live event per quarter with a defined topic, a guest or operator host, and advance registration. The advance registration step is operationally significant: events with advance registration produce 25–35% attendance vs. 8–15% for open-join events. Requires a dedicated registration message sent 5–7 days before the event and a same-day DM to registrants the morning of the event. | +5–12pp month-3 retention above Steps 1–3. The week-6 live event is the primary peer relationship deepening moment in the hybrid model: members who formed weak peer relationships in weeks 1–4 use the live event to meet peers they recognize from the cohort channel but have not yet spoken with directly. Peer relationships formed at or after a live event have 2–3× the median duration of relationships formed only through async channel interactions. |
| 5. Add week-10 completion check-in | At the end of the quarterly programming window (week 10), send every member who participated in at least two window events a direct 1:1 DM. The message: “You made it through [window name]. What did you get done?” followed by a specific reference to something they posted or shared during the window. Do not send this to members who did not participate in the window events. The completion check-in is a low-friction renewal trigger: it frames the end of the window as a completion milestone, not a subscription continuation decision. | One DM per participating member at the end of each quarterly window. At 20–40 participating members per window, this is 20–40 DMs per quarter (5–10 per month averaged). The message should be personalized with a specific reference to each member’s contribution — a template with a one-sentence customization per member, not a broadcast. This is operationally similar to the member spotlight DM pitch and can be batched into 1–2 hours of operator time per window. | +4–10pp month-3 retention above Step 4 for the participating member subset. The completion check-in replicates the week-9 bridge conversation dynamic from the full cohort model in a lower-overhead format. Members who receive a personalized completion acknowledgment renew at higher rates than members who receive a standard subscription renewal reminder, because the DM reframes the end-of-window moment as a completion event rather than a billing-cycle event. |
| 6. Add alumni channel for programming window completers | Create a single #alumni channel (not one per window) for all members who have completed at least one quarterly programming window. Invite each window’s completers after the week-10 check-in. The alumni channel purpose: one async challenge per month (a brief expert-level prompt suited for members past their first window), advance access to sign-up for the next window before general community members, and visibility to each other across cohorts. The alumni channel is not a high-activity channel — two to three posts per month from the operator is the right baseline. | Channel creation (one time). Monthly async challenge post (12 per year). Advance window invitation message (4 per year). New member invitation DM at end of each window (1 per participating completer, 4 times per year). Total: approximately 20–30 minutes of operator time per month for the alumni channel at steady state. | +3–7pp month-3 retention for alumni members above Step 5. The alumni channel provides the post-completion identity anchor that prevents cohort completers from reverting to passive subscription behavior between windows. Members with a named alumni identity within the community have a specific social reason to open the workspace in months where no programming window is running. |
The hybrid model’s retention improvement is front-loaded in Steps 1–3, not Steps 4–6. The activation layer (same-month grouping, cohort-aware Day 0 DM, week-3 challenge) closes the most common retention failure mode: non-activation in weeks 1–4. A member who does not post in the first 30 days is unlikely to remain paying through month 3 regardless of what programming the community runs in months 2 and 3. Operators who skip Steps 1–3 and implement only Steps 4–6 (the programming layer) are optimizing for month-3 retention of an already-activated member base while leaving the primary retention leak (week-1–4 non-activation) untouched. Run Steps 1–3 first; add Steps 4–6 in the subsequent quarter once the activation rate baseline has improved. See the paid community programming calendar guide for the full quarterly programming window event sequencing.
FAQ
What activation rate should a cohort community expect?
A cohort-based paid community should expect 60–80% month-one activation, where activated means posting in an introductions channel, selecting a stated goal track, and subscribing to at least two content channels within 30 days. The cohort structure drives this benchmark through three mechanisms: shared start eliminates isolation anxiety; lockstep curriculum creates peer accountability; peer comparisons are immediately available because all members started together. Always-open communities with structured onboarding achieve 40–60%. The gap is structural — improving the welcome message within the always-open model cannot close it. The activation rate benchmark table on this page covers all four model variants with drivers and shortfall causes. See also: paid community member activation rate reference card.
What is the minimum cohort size for a paid community cohort?
The minimum viable cohort size is 20 members per intake. Below this threshold, peer density disappears: not enough peers for goal-track diversity, accountability pair formation, or the social comparison that drives week-1–2 activation. A 10-person cohort functions as a small group program, not a community, and produces below-always-open activation rates. The cohort minimum viable checklist on this page includes intake capacity as item 2 and covers the pre-launch conversion test that confirms whether your waitlist will convert at the rate needed to sustain 20-member cohorts across 3+ windows. See the companion blog post: Paid community cohort model — when to run cohorts, when to stay always-open, and how to bridge both.
When should a paid community switch from always-open to cohort?
Switch when three conditions are simultaneously true: waitlist ≥100 qualified applicants, reliable intake capacity ≥20 paying members per synchronized window, and a sequential curriculum covering 8–10 weeks of defined outcome progression exists. A waitlist of 100 provides the buffer required to maintain consistent cohort sizes across 4–5 windows without depleting qualified candidates. Communities whose value is primarily network access (not curriculum) are better served by the hybrid model (rolling intake + quarterly programming windows) than a full cohort structure — see the operator archetype decision table on this page. The cohort minimum viable checklist covers all eight prerequisites before the first cohort intake. See also: paid community retention strategies guide for how the model choice interacts with month-3 and year-one retention.
What is the hybrid cohort model for paid communities?
The hybrid cohort model combines rolling always-open intake with quarterly 8–10 week programming windows. Members join continuously; each quarter, a defined programming window runs a structured event and challenge sequence that all current members participate in together. Members who join within 3 weeks of a window start receive a near-cohort onboarding experience. Between-window joiners receive standard structured always-open onboarding. The hybrid model produces activation rates of 50–70% (between always-open with structured onboarding at 40–60% and full cohort at 60–80%) and month-3 retention of 45–65%. It is the recommended model for operators with mixed-outcome communities or intake capacity below 20 per synchronized window. The six implementation steps on this page sequence the hybrid build from lowest to highest operational overhead, with Steps 1–3 providing the activation improvement and Steps 4–6 providing the retention improvement. See paid community programming calendar for quarterly window event sequencing. Use the onboarding health check to diagnose current always-open activation before choosing a model.