Metrics & economics

I built a business case for hiring a community manager. The LTV calculation I ran revealed I was solving the wrong problem.

By Foothold · October 2026 · See the LTV formula and four-scenario table →

Priya Chakraborty ran The RevOps Collective — a paid Slack community for revenue operations managers, sales ops analysts, and GTM systems engineers at Series-A to Series-C SaaS companies, $129 per month, launched August 2025 — for six months before she calculated what a single member was worth. She was not calculating LTV to understand the economics of her community. She was building a business case for a hire.

She wanted to bring on a part-time community manager at $2,000 per month. The role would produce better weekly programming: a structured Q&A series featuring RevOps leaders from her network, a biweekly curated resources digest, and an “ask the operator” format where members could submit questions publicly. She had been running all of this alone for six months and it was consuming more of her consulting hours than she had planned. The case for hiring was simple: the programming would reduce churn, the additional retained MRR would cover the hire, and she would get her consulting hours back. She just needed to model what “reduce churn” was actually worth.

She opened a spreadsheet. Six months in, the numbers were: 220 members, $28,380 MRR, 10% monthly churn rate, 61% month-two renewal rate. The simple LTV formula gave her $129 ÷ 0.10 = $1,290 per member. Retaining 1.55 extra members per month would cover the $2,000 community manager cost. She had been losing 22 members per month, so retaining 2 of those 22 through better programming — less than 10% of her monthly cancellations — would break even. The math felt achievable.

But before she posted the job listing she made a decision that changed the entire analysis. She decided to check where the churn was concentrated. She had been attributing cancellations to a generic “the community did not meet expectations” cause. She wanted to know whether the programming she planned would actually reach the members who were leaving. So she opened her Slack workspace admin dashboard, exported the member list, and sorted by total messages sent.

What the Slack admin sort revealed

Of her 220 members, 134 had never sent a message in the workspace. Zero messages, ever, despite being paying members for an average of 3.4 months each. Another 24 members had sent one or two messages — an introduction post or a single reply — and had gone silent since. That was 158 members, 72% of her paying base, with essentially no participation record.

The remaining 62 members — 28% of the base — had sent 10 or more messages. These were the members who appeared in threads, replied to each other, asked questions in #gtm-systems and #revenue-reporting, showed up for the live Q&A sessions. They were the community she experienced when she opened Slack every day.

She then cross-referenced the Slack admin export against her Stripe data, matching each member’s Slack account to their payment record by join date and email. This took about two and a half hours. When she finished, she ran the cancellation data against activation status for the prior two months: of 44 cancellations, 41 were from the 134 never-activated members. Two of the remaining three were from the “posted once or twice” group. One was an activated member who had cited a career change in their cancellation note.

Ninety-three percent of her churn was concentrated in members who had never posted in the workspace.

The LTV calculation by segment

She recalculated LTV with the segments separated.

Activated members (62 members, 28% of base): Of the 62 activated members, 3 had cancelled in the prior two months. Monthly churn rate for this segment: 3 ÷ 62 ÷ 2 months = 2.4% per month. She adjusted upward to 5.5% to account for a smaller sample size and natural variance. LTV at 5.5% monthly churn: $129 ÷ 0.055 = $2,345.

Never-activated members (134 members, 61% of base): Of 134 never-activated members, 41 had cancelled in two months. Effective monthly exit rate: 41 ÷ 134 ÷ 2 months = 15.3% per month, though this understated the cliff-one concentration — most of those cancellations had happened in the member’s first billing month. Cross-checking her cohort data, she found that never-activated members who reached their second billing date (those who had joined more than 45 days ago) cancelled at roughly 8% per month — still much higher than activated members. But the majority of never-activated members did not reach their second billing date. For the cohort as a whole, average tenure for a never-activated member was 1.4 months. LTV: $129 × 1.4 = $181.

The ratio: activated LTV ($2,345) vs. never-activated LTV ($181) = 13x.

The blended $1,290 LTV — the number she had used to build the business case for the community manager — was an average of $2,345 × 28% and $181 × 72% (with the activated-but-quiet middle segment blending in). It looked like a reasonable number for a community in her price range. It pointed to a modest programming investment to retain a modest number of marginal members. It contained no signal that 61% of her paying members were on a less-than-two-month trajectory.

Why the blended number hid the real problem

The blended LTV formula — ARPU ÷ monthly_churn_rate — is built for steady-state analysis. It assumes that churn is distributed roughly evenly across the member lifecycle: a member who joined last month has approximately the same probability of cancelling this month as a member who joined three months ago. For SaaS products, this assumption is roughly true after the first 30 days. For paid Slack communities, it is not true at any lifecycle stage.

Community churn is front-loaded at two specific points: month one (the activation cliff, where never-activated members cancel at 40–50%) and months two–three (the relevance cliff, where activated-but-quiet members who found value in week one but stopped engaging cancel as the habit of participation erodes). The simple blended formula smooths across both cliffs and produces a number that looks like a stable, manageable churn rate. It is not managing a stable situation. It is averaging a 45% monthly exit rate for the non-activated majority with a 5% monthly exit rate for the activated minority into a number that reads as “moderate.”

Priya had been running a community with two distinct populations inside it for six months. The metrics she tracked — MRR, total member count, monthly churn rate, month-two renewal rate — had never separated those two populations. The 61% who had never posted were invisible in the aggregate numbers, showing up only as a steady outflow of cancellations that she was attributing to insufficient programming. The 28% who were active were setting the tone of the community experience she was building programming for. The community manager she planned to hire would have been writing Q&A series, curated digests, and “ask the operator” threads for that 28%. The 72% were not opening Slack to see any of it.

The investment comparison

She put the two investment options in the same spreadsheet.

Option A: Hire a part-time community manager ($2,000/month). The programming they would produce — Q&A series, resources digest, operator-led threads — would reach members who were already opening Slack. The target population for this investment was the 28% who were already engaged. These members were cancelling at roughly 5.5% per month. A 20% improvement in their retention rate would reduce monthly churn for this segment by about 0.7 members per month. The programming might also improve recruitment through word-of-mouth from satisfied members, adding 2–3 new members per month in referrals. Maximum realistic impact: retaining 2–3 additional members per month. Revenue impact at $2,345 LTV per activated member: $4,690–$7,035 in additional cohort LTV per month. Net of the $2,000 cost: $2,690–$5,035 per month.

Option B: Build a Day-0/3/7 onboarding sequence (one-time setup, near-zero ongoing cost). The sequence — a personalised day-0 DM with a goal-specific first-action ask, a conditional day-3 nudge for non-activated members, a day-7 operator escalation for members still silent after the nudge — would target the 72% who had never activated. Based on case studies she had read from other operators, improving activation from 28% to 65% was achievable with a properly structured sequence. Her intake would involve a four-question checkout form to personalise the day-0 DM by RevOps role and stated challenge. Setup estimate: 6–8 hours over two sessions. Ongoing time: 15–20 minutes per week to review the day-7 escalation list. Ongoing cost: $0.

The LTV math for Option B, at her current new-member rate of 30–35 per month:

• Before (28% activation): 9 activated, 25 never-activated per month → 9 × $2,345 + 25 × $181 = $21,105 + $4,525 = $25,630 in monthly cohort LTV.
• After (65% activation): 21 activated, 13 never-activated per month → 21 × $2,345 + 13 × $181 = $49,245 + $2,353 = $51,598 in monthly cohort LTV.
• Difference: $25,968 in additional monthly cohort LTV. Generated by 6–8 hours of setup. Ongoing cost: zero.

She was not choosing between two good investments. She was choosing between an investment that reached the 28% and one that reached the 72%. The scale of the difference — $2,000 monthly cost for Option A vs. $0 monthly cost for Option B, with Option B generating roughly 5× the LTV impact — was not a close call.

She shelved the community manager hire and started building the onboarding sequence.

Building the intake form and Day-0/3/7 sequence

The first step was adding a four-question intake form to her checkout flow. She was using Memberstack for billing and Slack invite management; the form sat on the checkout confirmation page and its answers were emailed to her automatically. The questions:

1. What’s your primary RevOps focus area? (GTM systems and tooling / Revenue reporting and analytics / Sales-marketing alignment / RevOps team building and hiring)
2. What stage is your company? (Pre-Series A / Series A / Series B or later / Post-IPO or PE-backed)
3. What’s your biggest RevOps challenge right now? (Open text, 1–2 sentences)
4. What do you most want from this community? (Peer connections with other RevOps leaders / Frameworks and tactical resources / A space to think through a specific problem / All three)

She mapped each focus-area answer to a channel route: #gtm-systems for tooling and systems answers, #revenue-reporting for analytics answers, #sales-and-marketing-alignment for alignment answers, #revops-hiring for team building answers. A member who answered “GTM systems and tooling” and described their challenge as “consolidating three CRM instances after an acquisition” would get a day-0 DM that cited the live thread in #gtm-systems closest to their stated problem and asked one specific question: There’s a thread in #gtm-systems right now about post-M&A CRM consolidation that I think you’d find directly useful — what’s the migration approach you’re evaluating?

She wrote four base templates, one per channel route, with merge fields for the member’s stated challenge and a live thread reference. The day-0 DM went out within one hour of the member being added to the Slack workspace. The day-3 nudge was suppressed for any member who had posted in the prior 72 hours; it went only to members who were still silent. The day-7 escalation gave her a list of three members: their name, their stated challenge, their last-login date from Slack admin, and a suggested personal DM she could send. She spent 10–15 minutes on this list each Friday morning.

Before fully automating, she ran a manual test with 30 existing members who had never posted: she sent personalised DMs by hand, using the checkout form data she had collected from members who had filled it in and LinkedIn research for the few who had not. Eighteen of the 30 replied within 48 hours. Seventeen posted in the workspace within 72 hours. A 57% activation rate, compared to the 28% baseline.

What changed in five months

She tracked three numbers weekly: week-one activation rate (calculated each Monday by reviewing new members from the prior seven days), month-two renewal rate (the percentage of members who renewed at their second billing date), and weekly active poster rate (the number of unique members who sent at least one message that week).

By month five:

• Week-one activation rate: 28% → 64%
• Month-two renewal rate: 61% → 82%
• Never-activated cancellations: 41 of 44 total cancellations (93%) → 8 of 22 (36%) — total cancellations also fell as the community retained more members
• Weekly active poster rate: 12% of total membership → 46%
• Median days to first peer reply: 27 days → 5 days
• Monthly MRR: $28,380 → $36,200

The MRR growth came from two sources: improved retention (fewer members leaving) and improved referrals (activated members recommending the community to peers, citing specific conversations they had participated in). Activated members who could point to a thread where they had worked through a specific GTM systems problem with three other people were giving referrals that converted at a different rate than members who said “I think it’s a good community” without a specific memory to anchor the recommendation.

The nature of the Slack workspace itself changed. The 46% active poster rate meant that Priya was no longer the primary source of content in most channels. Members were opening threads, asking questions, tagging each other. She spent less time producing reactive content to fill the silence and more time facilitating the conversations that were already happening. The programming she had wanted to hire for was partly happening on its own, because the community now had enough activated members to sustain it.

The community manager hire, revisited

In month six of the onboarding sequence — eleven months after she had first planned the hire — Priya hired a part-time community manager. The same role, the same $2,000/month budget, the same programming plan: Q&A series, curated digest, “ask the operator” threads.

The difference was that she now had a 46% active poster rate and a community manager hiring into a base of 140+ engaged members who knew each other. The Q&A series launched to 60 attendees. The curated digest was shared in channels by members who found it relevant. The “ask the operator” threads got replies before she had typed her response.

The $7,820 in additional monthly MRR generated by the onboarding improvement covered the community manager’s cost 3.9 times over. She was not justifying a $2,000 hire by hoping to retain 2 extra members. She was funding it from a concrete revenue improvement that was visible in the cohort data.

The original business case — $1,290 blended LTV, retain 1.55 members per month, break even on the hire — was not wrong as arithmetic. It was wrong as a diagnosis. The blended number had answered the question “what is the average value of a member?” It had not answered the question “where is the LTV problem, and what is it worth to fix?” Those are different questions, and the second one required segmenting the average before it could be answered.

The LTV segmentation test

The practice Priya used — running the LTV formula separately for activated and never-activated members rather than as a blended total — is a diagnostic worth naming. Call it the LTV segmentation test.

The test has four steps:

1. Pull the Slack admin export and sort by total messages sent. Identify three segments: never-posted, posted 1–2 times (activated-but-quiet), posted 3+ times (engaged). Note the percentage of your current membership in each segment.
2. Cross-reference with your payment processor. For each segment, calculate the monthly churn rate separately over the past 60–90 days (cancellations in that segment ÷ segment size ÷ months). For small communities, use the empirical benchmarks: never-activated cancel at roughly 40–50% in month one, activated cancel at 5–8% per month in steady state.
3. Calculate LTV per segment using ARPU ÷ segment monthly churn rate. Note the ratio between your highest-LTV segment and your lowest-LTV segment. A 10–13× ratio is typical. A 5–8× ratio means your onboarding is already working to some degree. A 15×+ ratio means the activation problem is acute.
4. Calculate the dollar value of moving members between segments. Each member you move from the never-activated track to the activated track gains (activated LTV − never-activated LTV) in lifetime value. At your current new-member rate, multiply by the number of members you could move with a properly structured Day-0/3/7 sequence (typically the difference between 30% and 65% activation, per 100-member cohort). That total is the value of your activation opportunity.

The result of this calculation typically outweighs every other investment an operator is considering for their community: hiring, content production, event programming, platform changes, premium integrations. Not because those investments have no value, but because they are downstream of activation. A member who has not activated will not benefit from better programming. A member who has activated will benefit from programming, and will be retained by content, and will refer peers, and will upgrade to inner-ring tiers, and will stay for the long-arc LTV that the 12–18× number represents. The content and programming investments compound on top of a healthy activated base. They produce very little return on a non-activated base, because the non-activated members are not there to see them.

This is not an argument for not investing in content. Priya hired the community manager. Her investment in programming was real and the returns were real. It is an argument for sequencing: know where your LTV problem is before investing to solve it. The LTV segmentation test tells you where the problem is. The Day-0/3/7 sequence solves it. The content calendar and programming investment then operate on a base where they can compound.

Related: Paid Slack community member LTV — the formula, the two cliffs, and the four-scenario table · Paid community revenue models — the five economics patterns and activation stakes for each · 18 months without measuring activation — and what Hiroshi found when he finally did · How to reduce Slack community churn — three segments and interventions.