Paid community retention

She had 2.9% monthly churn and 74% bilateral activation in month ten. By month twelve both numbers had collapsed. Nothing in her programming had changed. Named concept: the anchor member concentration risk.

Adunola Fashade’s paid Slack community looked healthy by every metric she tracked. 74% bilateral activation. 2.9% monthly churn. 230 members, $25,070 MRR, referrals coming in at 7 to 8 per month. In October 2025, two founding members left in the same month — both for reasons entirely outside her control. By November 2025, bilateral activation had dropped to 56% and monthly churn had risen to 5.3%. She ran NPS surveys, reviewed her programming, checked every change she had made. Nothing had changed. A peer at a December 2025 operators roundtable asked her one question: before those two members left, what share of new member intro posts had a reply from either of them? She went back and checked. 69% of intro posts from the first nine months had a reply from Taiwo or Emeka within 24 hours. Named concept: the anchor member concentration risk — the degree to which a paid community’s peer-value delivery is concentrated in a small enough subset of members that the departure of one or two of them constitutes a system-level risk to retention metrics, invisible in aggregate numbers until the concentration fails.

The community at month ten

Adunola launched The B2B SaaS Product Operations Network in December 2024 — a paid Slack community for Head of Product Operations, Product Program Managers, and Senior Product Operations Managers at B2B SaaS companies with $20M–$100M ARR. The community addressed the operational complexity of a maturing product function: roadmap governance when the organization has grown beyond a single PM team, cross-functional dependency tracking across engineering, design, and data teams, quarterly planning design and OKR program architecture, and the transition from ad hoc product coordination to a formal product operations function. $109 per month.

By September 2025 (month ten): 230 active members, $25,070 MRR. Bilateral activation — the share of all members who had ever joined and both posted and received a substantive reply from a peer they had not previously known, within their first seven days — was at 74%. Monthly churn was 2.9%.

Both numbers were strong relative to the informal benchmarks she tracked through the operators community she participated in. Bilateral activation at 74% was about 10 percentage points above the 65% informal benchmark she had been targeting since launch. Monthly churn at 2.9% was just below the 3% threshold she considered the boundary between “well-run community” and “exceptional community.” She had reached those numbers through eighteen months of deliberate onboarding work: a goal-track-keyed Day-0 DM, a conditional Day-3 nudge for stalled members, a weekly reply-gap audit of zero-reply intro posts, and a monthly cohort virtual coffee for members who had joined in the same calendar month. The activation and retention systems were mature.

Referrals had been coming in consistently: 6 to 8 new members per month were arriving through direct referrals from existing members, contributing roughly 40% of her monthly new member acquisition alongside waitlist conversions. She had not built a formal referral program — no incentive structure, no referral tracking mechanism. The referrals were organic, driven by members who found the community useful enough to recommend it to peers in their network who shared the same functional profile.

Two departures in October

On October 3, 2025, Adunola received a Slack DM from Taiwo Bankole, Head of Product Operations at a Series B SaaS company and one of her first thirty members. He wrote that he had been promoted to Chief Product Officer at his company, effective the following week. His new scope — leading the entire product organization, not just the operations function — meant his day-to-day challenges had moved above the community’s niche. He was cancelling the subscription, and he wanted to tell her directly because he had found the community genuinely valuable during his time in the product operations role. He said he hoped to refer colleagues who were still in product operations functions and expected to do so within the month.

On October 17, 2025, Emeka Osei, Senior Product Program Manager at a Series A SaaS company and one of her first twenty members, messaged to say his company had been acquired by a larger enterprise software firm. The acquiring company had implemented a freeze on discretionary SaaS subscriptions pending an integration-period budget review. He was cancelling not because the community had lost value but because the expense approval process at the new parent company was unclear and he was not willing to expense it personally. He also expected the freeze to lift in three to six months and said he would likely rejoin when it did.

Both departures were ordinary. Neither was caused by community quality, programming gaps, or pricing. Both members left positive comments. Neither departure was predictable from any community engagement signal — both Taiwo and Emeka had been posting actively in the week before they cancelled.

The collapse

October 2025 was the first month since launch that bilateral activation had declined. It dropped from 74% to 61%. Monthly churn rose from 2.9% to 4.1%. Adunola noticed both numbers but attributed them tentatively to the two departures: losing two tenured, paying members in one month had a direct effect on churn, and she assumed activation would recover in November as the new-member cohort cycled through.

November was worse. Bilateral activation: 56%. Monthly churn: 5.3%. Referrals: zero.

The referral number was the one that alarmed her most, because referrals had been structurally consistent for six months. She had received at least 6 referral-driven new members in every month from April through September 2025. In November, she received none. No DMs from existing members introducing a colleague. No new member sign-ups who named an existing member as the reason they joined. The referral pipeline, which had been generating approximately 40% of new member acquisition, had gone silent.

She began investigating. She sent an NPS survey to all 228 current members in mid-November. 71 responded (31%). Average NPS: 46 — down from 61 in her last survey six months prior, but still positive. The free-text responses were largely favorable: members mentioned specific threads and connections they found valuable. No respondent identified a problem.

She reviewed every change she had made to her programming in October and November. There were none. Same Day-0 DM. Same Day-3 nudge. Same reply-gap audit. Same monthly cohort coffee. Same channel structure. Same event cadence. She had not changed any element of the operational system she had spent eighteen months building.

She pulled Slack engagement metrics for October and November and compared them to the prior three months. Total messages sent per week: down from an average of 340 in July–September to 290 in October and 275 in November. The decline was real but not dramatic — 20% reduction in weekly message volume. The drop was concentrated in the first two weeks of October, following which volume had stabilized. She could not find anything in the engagement data that pointed to a cause.

She posted in the operators forum she participated in: “My bilateral activation dropped 18 points and my churn nearly doubled between September and November. I haven’t changed any programming. NPS is still positive. I can’t find the cause. Has anyone seen a sudden drop without an obvious trigger?”

Obinna Osei-Mensah replied within a day.

The peer

Obinna ran The B2B SaaS Product and Engineering Alignment Network — a paid Slack community for Engineering Directors, VPs of Engineering, and product leaders managing the cross-functional alignment challenges between product and engineering at B2B SaaS companies with $25M–$150M ARR: sprint capacity planning, roadmap visibility across engineering teams, incident and escalation protocol design, and the organizational mechanics of maintaining alignment through rapid headcount growth. $119 per month. By December 2025: 285 active members, $33,915 MRR, 71% bilateral activation, 2.3% monthly churn.

Obinna had seen the activation collapse pattern before — not from outside, but from his own data. In June 2025, at month eight of his community, he had run an analysis he called a “value delivery audit” after noticing that one founding member — Chukwuemeka Adeyemi, VP Engineering at a Series C SaaS company — was appearing in a disproportionate share of the engagement events he tracked as positive activation signals.

Chukwuemeka was not a formal moderator or community manager. He was simply a paying member who engaged heavily. He replied to new member intro posts with specific, substantive responses. He answered technical questions in goal-track channels with frameworks he had developed in his own work. He occasionally mentioned the community to VP Engineering peers in his network, several of whom had subsequently joined. His contributions were voluntary, valuable, and entirely informal.

Obinna had noticed his centrality and wanted to understand its magnitude. He pulled the past six months of #intros replies and goal-track channel activity. The finding was stark:

• 72% of first replies to new member #intros posts in the prior three months had come from Chukwuemeka or two other founding members (Adaeze Okafor and Femi Adeyemi)
• 65% of substantive expert responses in the #product-engineering-alignment and #roadmap-governance channels had come from those same three members
• 78% of referral-driven new members over the prior six months had been referred by those three members

The concentration was not a problem yet. Chukwuemeka was still active, still engaged, and there was no sign that he was about to leave. But Obinna could see clearly what would happen if he did: bilateral activation would drop significantly, because 40% of all first replies to new member intro posts were coming from one person. Referrals would likely collapse, because half of all referrals had originated with one person. Expert response density in the goal-track channels would thin, because one person was generating a third of all substantive replies.

Obinna ran what he now called the anchor member concentration diagnostic: a structured measurement of how concentrated the community’s peer-value delivery was in a small subset of members, designed to identify whether the departure of one or two people would constitute a system-level risk to retention metrics.

The anchor member concentration diagnostic

The diagnostic measures three types of peer-value delivery concentration:

1. Intro reply concentration

The share of new member #intros post first replies that came from the same five members in the prior 90 days. This is the most direct input to bilateral activation: a new member who posts in #intros and receives no reply within 24 hours activates at dramatically lower rates than one who receives a reply within that window. If the replies that drive activation are concentrated in a few members, the departure of those members collapses activation regardless of how mature the Day-0 and Day-3 programming is.

Flag threshold: greater than 50% of first replies from the same five members.

2. Expert response concentration

The share of substantive expert or diagnostic replies in goal-track channels — replies that contain a specific framework, a recommendation, or a named methodology — that came from the same three to five members in the prior 90 days. This type of value delivery drives renewal and referral: members who can cite specific expert insights they received from peers in the community renew at higher rates than members who cite general engagement, and referrals are more likely to include a specific “the community has people who can help with [problem]” endorsement when the expert responses are concrete and memorable.

Flag threshold: greater than 60% of substantive goal-track replies from the same five members.

3. Referral concentration

The share of new member referrals over the prior six months attributable to the same four to five members. Referral concentration risk has the longest lag of the three: a community can maintain healthy referral generation for two to three months after the high-referral anchor members become less engaged, because referral behavior tends to follow the member’s overall engagement level with a delay. When referral concentration is high and the high-referral members leave, the referral pipeline can go from 7 to 8 per month to zero in a single month, because the community had no distributed referral generation mechanism — the referrals were the personal networks of a few highly engaged individuals.

Flag threshold: greater than 70% of referrals over the prior six months from the same four members.

What Obinna found, and what he did about it

Obinna’s June 2025 diagnostic found all three concentration flags active. 72% intro reply concentration in three members. 65% expert response concentration in the same three members. 78% referral concentration, with 48% from one person (Chukwuemeka alone).

His response was not to ask Chukwuemeka to do less. The concentration was not a problem caused by the anchor members being too active — their contributions were the community’s most valuable outputs. The problem was that the contributions were not being replicated by other members who had the expertise to make them.

He ran a three-step distribution effort over July and August 2025.

Step 1: The curator role DM

Obinna identified 14 members (beyond the three concentrated anchor members) who had replied to at least two intro posts or goal-track questions organically in the prior three months — not members who had been asked to do so, but members who had done it voluntarily. These were the latent anchor members: people whose behavior already showed the pattern of substantive peer engagement, but whose engagement was incidental rather than named and consistent.

For each of the 14, he sent a personal DM. The structure was consistent: name the specific behavior he had observed (“I’ve noticed you’re often the person who replies to new members in #roadmap-governance when they post about [specific challenge area]”), name the value of that behavior (“the frameworks you share — specifically the prioritization model you described to [name] last month — are exactly the kind of thing that makes members feel the community is worth $119”), and offer a named role (“I think of you as the curator for that thread cluster”).

He was explicit about what the curator role was not: not moderation, not community management, not a volunteer position with ongoing obligations. The ask was specific: when you see a question in your area that you have useful context on, reply to it. If you occasionally spot a new intro post from someone working on what you work on, reply to that too. That’s it. I’ll occasionally route specific posts your way when they look like a match for your expertise, so you don’t need to monitor every channel — I’ll surface the ones that map to what you do.

Of the 14 members who received the curator DM, 11 responded positively. 9 explicitly accepted the named curator role. 2 said they would do what they were already doing but weren’t sure about the “curator” framing. 3 did not respond.

Step 2: The weekly routing brief

For the five members in the highest-concentration goal-track clusters — the clusters where Chukwuemeka and the other two concentrated anchor members had generated most of their replies — Obinna added a weekly routing brief: a brief personal Slack DM sent every Monday with one specific post or thread the recipient had not yet replied to. The DM named the new member or question-poster, described the specific topic, and explained why the routing recipient’s work mapped to that topic.

The routing brief was not a mass message. Each brief was sent individually to one member, referencing one specific post. The labor was approximately 20 minutes per week: reviewing the prior week’s unresponded intro posts and goal-track questions, matching each to a curator whose expertise applied, and writing a brief one-to-two-sentence routing DM.

The routing brief served two functions. First, it reduced the barrier for curators who had agreed to the named role but had not yet built the habit of proactively monitoring channels: the routing DM brought the relevant post to their attention rather than requiring them to find it. Second, it distributed introductions across the curator pool rather than allowing the highest-engagement member to reply first to everything visible.

Step 3: Goal-track matching expansion

Obinna had been making peer introductions as part of his Day-0 DM: when a new member named their goal-track in the Day-0 response, he would route them to the one or two most obviously relevant members in that goal-track cluster. In practice, those one or two most obviously relevant members were usually Chukwuemeka or one of the other anchor members, because they were the most visible and most reliably engaged.

He changed his routing practice to deliberately send new members to their second or third most relevant peer match — not the most active anchor member, but the curator who had relevant experience and who would benefit from the connection exposure. The most active anchor members continued to receive routing DMs; they were simply no longer the default first route for every new member.

The results of the distribution effort

By August 2025 (eight weeks after the curator DMs began):

• Intro reply concentration (top-5 share): from 72% (3 members) to 44% (10 members, more evenly distributed)
• #intros reply coverage within 24 hours: unchanged at 83% — the coverage rate held because the curator pool had grown, not because existing anchor members replied less
• Referral concentration: from 78% (3 members) to 51% (7 members) over the prior 60 days

In September 2025, Chukwuemeka transitioned to a new company as VP Product — moving out of the engineering-side leadership role that had made the community directly relevant to his current work. He cancelled the subscription with positive comments and a referral to a VP Engineering he had just met at a conference. His departure, which Obinna had identified as the community’s highest single-member concentration risk in June, produced no measurable impact on bilateral activation or churn. The distribution effort had transferred the value-delivery function from one person to ten.

What Adunola found when she ran the diagnostic

At the December 2025 operators roundtable, Obinna asked Adunola the question that reframed the problem: “Before Taiwo and Emeka left, what fraction of your month-one-through-nine intro posts had a reply from either of them?”

She went back and ran the count the following week. 227 intro posts from December 2024 through September 2025. 157 of those posts (69%) had at least one reply from Taiwo or Emeka within 24 hours. Of the remaining 70, 41 had received a reply from another member within 24 hours; 29 had received their first reply after 24 hours or not at all.

She also ran the referral attribution check. Of her 68 referral-driven new members from April through September 2025, 51 (75%) had been referred by either Taiwo, Emeka, or one other founding member (Oluwaseun Adeyemi, who had remained in the community). With Taiwo and Emeka gone, Oluwaseun was now the source of approximately 85% of whatever referral generation remained. He had made no referrals in November.

The concentration map made the November collapse legible. Adunola had not had a programming failure. She had had a concentration failure. The community’s activation mechanism had been working, but it had been working because two people were doing 69% of the work that made it work. When those two people left, the mechanism failed — not because the Day-0 DM or the Day-3 nudge or the reply-gap audit were wrong, but because the peer-side of the bilateral activation equation had been structurally dependent on two specific individuals rather than distributed across a broad enough base to absorb departures.

Reading the concentration in retrospect

Adunola ran the diagnostic backward through her Slack history to understand when the concentration had formed. The answer: it had been there since the beginning. In her first month, three of the first thirty members had accounted for 80% of replies to new intro posts. In months two and three, that share had dropped to 71% (Taiwo and Emeka had become the two dominant responders, with a third member contributing occasionally). By month six, the share had stabilized at around 65–70% from two people. The concentration had not developed over time; it had been the structure from the start.

This is the characteristic pattern of anchor member concentration formation in paid Slack communities. The founding members who join in the first three months tend to be the most engaged, because they had the most specific motivation to join (they were either referred directly by the operator or were actively seeking the community’s niche at the time it launched). Among those founding members, some subset will be more engaged than others — more willing to reply to new arrivals, more likely to share in goal-track channels, more naturally inclined to refer colleagues. Those members become the community’s de facto activation engine. If nothing is done to replicate their behavior across the broader membership, the concentration persists or increases as the community grows, because newer members join a community where certain people have already established the reply-and-respond pattern and the new members observe that pattern rather than replicating it.

The aggregate metrics — 74% bilateral activation, 2.9% monthly churn — reported the community’s output correctly. The community was producing bilateral activation at a 74% rate. It was just producing that activation by channeling 69% of it through two specific people rather than distributing it across a network. The aggregate numbers could not distinguish between those two structures, because they measured outcomes (did the new member get a reply?) without measuring the distribution of the mechanism (from how many different members did those replies come?).

Adunola’s distribution effort

Adunola began the distribution effort in January 2026. She ran a modified version of the approach Obinna had described.

First, she identified the latent anchor members in her current active membership: 228 members, filtered to those who had replied to at least two intro posts or goal-track questions in the prior 90 days without being prompted. She found 11 members who met this criterion — a smaller pool than Obinna’s, partly because her community was two months younger at the point of running the effort and had fewer tenured members who had accumulated organic reply behavior.

She sent the curator role DM to each of the 11. The language she used named the specific behavior she had observed and explained what the curator framing meant: “I’ve noticed you’re often the person who replies to new members in #quarterly-planning when they’re working on OKR program design. The specificity of what you share — the actual frameworks you’ve used, the mistakes you’ve made — is exactly what makes those replies worth reading. I’d like to give that behavior a name. I think of you as the curator for that thread cluster, which means I’ll occasionally route specific intro posts or questions your way when they look like a match for what you do. It doesn’t add time — it makes what you’re already doing visible to both of us and means you get some posts surfaced to you rather than having to find them.”

8 of the 11 responded positively. 7 explicitly accepted the curator framing. 1 said they would keep doing what they were doing but preferred not to have an official-sounding name attached. 3 did not respond.

She added the weekly routing brief for the five highest-concentration goal-track clusters in the community: #quarterly-planning, #cross-functional-alignment, #product-operations-tools, #org-design-for-product, and #dependency-management. Each Monday she reviewed the prior week’s unresponded or low-response intro posts and goal-track questions in those five clusters and sent individual routing DMs to the two or three curators whose expertise most directly matched each post.

She also changed her Day-0 DM peer-routing practice: rather than routing new members exclusively to the members she knew were the most responsive (which had been a proxy for Taiwo and Emeka by name when they were present), she rotated the routing across the full curator pool, matching by goal-track selection from the Day-0 DM and company stage rather than primarily by the curator’s likelihood to respond quickly.

Results

By April 2026 (four months after the distribution effort began):

The bilateral activation recovery took two months to become visible in the numbers: January 2026 saw a partial recovery to 63%, February to 68%, March to 71%, April to 72%. The lag reflected the time it takes for a new cohort of curators to build the reply habit into their weekly routine rather than relying on the routing brief as the primary trigger. By April, 7 of the 8 curators who had accepted the named role were replying to intro posts and goal-track questions without routing brief prompts for at least some of their replies.

The referral recovery followed a similar pattern: zero in November and December 2025, two in January 2026, four in February, six in March, seven in April, from nine different members. The distribution of the referral generation had changed structurally: referrals were no longer coming primarily from two or three people but from a pool of single-figure contributors each generating one to two referrals per month.

Adunola ran a second concentration audit in April 2026. Intro reply concentration (top-5 share): 38%. Expert response concentration (top-5 share): 47%. Referral concentration (top-4 share over prior 90 days): 54%. All three numbers were below their respective flag thresholds. The concentration risk had not been eliminated — some members would always be more engaged than others — but it had been distributed enough that the departure of any single member or pair of members would not collapse the activation mechanism.

The named concept: the anchor member concentration risk

The anchor member concentration risk is the degree to which a paid community’s peer-value delivery — the replies, responses, and referrals that drive activation, renewal, and acquisition — is concentrated in a small enough subset of members that the departure of one or two of them constitutes a system-level risk to retention metrics.

The risk is structurally invisible in aggregate metrics because the aggregate metric for bilateral activation reports whether new members are getting replies, not how many different members are generating those replies. A community with 74% bilateral activation driven by two people delivering 69% of replies is structurally fragile in a way that is indistinguishable from a community with 74% bilateral activation distributed across 20 curators — until the two people leave.

Concentration risk is a function of the community’s founding dynamics rather than its programming quality. The activation and onboarding systems Adunola had built — the goal-track Day-0 DM, the conditional Day-3 nudge, the reply-gap audit — were correctly designed and correctly executing. They had produced 74% bilateral activation. They had just produced it in a way that was structurally dependent on two specific people, because those two people had organically become the community’s reply infrastructure without any mechanism to distribute that function.

The distribution effort does not replace the existing activation programming. It runs alongside it, adding a peer-side layer that the standard onboarding systems do not address. The Day-0 DM and conditional Day-3 nudge address the new member’s behavior. The curator role DM and routing brief address the existing members’ behavior. Both sides of the bilateral exchange need to be intentionally maintained for the activation mechanism to be structurally resilient.

The diagnostic is worth running once per quarter for communities above 100 members, and immediately after any two founding members depart in a short window. The flag thresholds — 50% intro reply concentration, 60% expert response concentration, 70% referral concentration — are guidelines rather than precise cutoffs. The operative question is simpler: if two of your most active members left in the same month, would your bilateral activation rate and referral generation survive the departure? If the answer is no, the concentration risk is real regardless of where the percentage falls.

Foothold’s Day-7 scorecard tracks who replied to each new member’s intro post and when the reply arrived. At community sizes where the reply log is exportable, the concentration audit can be layered directly onto the scorecard data. If you want to see your community’s reply concentration alongside tenure decomposition and goal-track decay data, the waitlist is below. We’ll show you the structure in the first two cohorts.