Reference card — paid community retention
Paid community win-back email sequence
Decision tables for paid community operators building a three-email win-back sequence after member cancellation: email timing windows with open rate, response rate, and reactivation acceptance rate by email; format benchmarks (plain-text vs. HTML vs. automated); subject line performance benchmarks by email type; exit interview response categories with observable language signals and reactivation rates; and full response benchmarks by community size and price tier.
TL;DR
A three-email win-back sequence sent over 60 days recovers 15–20% of departed paid community members who would otherwise be permanent cancellations. The sequence has three distinct emails with non-overlapping purposes: an exit interview at 24–48 hours (diagnostic: collect the departure reason while the member can still articulate it), a community update at 14–21 days sent to respondents only (relationship: report back on what changed from their feedback), and a reactivation invitation at 60 days sent to all departures (recovery: reference a specific community change that addresses their stated departure reason). The most consequential formatting decision in the sequence is sending the exit interview as plain-text personal email: plain-text format achieves 22–36% response rates vs. 3–8% for identical questions in designed HTML email. The most consequential targeting decision is sending the reactivation invitation only to the sub-segments where it is likely to be accepted, not to all cancellations with a generic “we miss you” message (which achieves 3–6% acceptance regardless of timing or personalisation). The discount decision follows a single rule: offer only to members whose exit interview confirms pricing misalignment as the primary departure reason, which is 15–20% of departures.
Why win-back email benchmarks vary by sequence position and exit interview data
A win-back email sequence is not a repeated attempt at the same message. Each of the three emails in the sequence addresses a different psychological state of the departed member, pursues a different goal, and is judged by a different success metric. The exit interview (Email 1) is measured by response rate, not by reactivation rate — its success is generating data, not recovering revenue. The community update (Email 2) is measured by open rate and reply sentiment — its success is re-establishing the relationship and priming the 60-day invitation. The reactivation invitation (Email 3) is measured by acceptance rate — its success is converting a former member back into a paying member.
Operators who treat all three emails as variations of the same retention message — each one arguing for the community’s value and implicitly asking the member to return — see significantly lower outcomes across the full sequence. The exit interview reads as a retention pitch, response rate drops to 4–8%, and the operator has no departure reason to reference at day 60. The community update arrives with no prior relationship established, response rate drops below 5%, and the 60-day invitation lands cold. The reactivation invitation at 60 days with no personalisation achieves 3–6% acceptance regardless of community quality or price tier.
The benchmark tables in this reference card are structured to reflect the sequential dependency of the three emails. Each table is relevant to one or more specific positions in the sequence, and the notes in each row identify which email the data applies to. The critical upstream factor in all three tables is exit interview response rate: the diagnostic data from a 22–36% response rate exit interview transforms the reactivation invitation from a generic “we miss you” message (3–6% acceptance) into a specific “the thing you told me about is now different” message (12–18% acceptance for personalised invitations, 18–28% for the pricing-misalignment segment where a targeted discount is included).
The email-DM comparison: This reference card covers email win-back sequences specifically. For communities where the operator still has Slack access to departed members — or where the member remains in the workspace on a free basis after cancelling — Slack DM sequences achieve higher response rates at the exit interview stage (35–55% personal DM vs. 22–36% personal email) and comparable reactivation rates at the 60-day stage. The email sequence in this card applies when Slack access has been removed at cancellation, when the operator prefers to use email as the primary post-cancellation communication channel, or when the community is large enough that Slack DM outreach is not scalable. See the Slack DM win-back sequence post and the member win-back reference card for the DM-channel benchmarks.
Table 1 — Win-back email timing decision table
Each of the three emails in a win-back sequence operates in a specific timing window. The windows are not arbitrary: they map to the three psychological phases a departed member moves through after cancellation. Email 1 (exit interview) targets the active decision phase at 24–48 hours, when the departure reason is most salient and the member is most able to articulate it. Email 2 (community update) targets the settling-in phase at 14–21 days, when the departure decision has been made but the community relationship has not yet faded. Email 3 (reactivation invitation) targets the stable-but-familiar window at 55–65 days, when the initial departure inertia has diminished and the community remains salient enough for a specific development to be compelling. Sending any of the three emails outside its window degrades performance significantly: an exit interview at day 7 achieves 8–14% response (vs. 22–36% at 24–48h); a reactivation invitation at day 30 achieves 8–14% acceptance (vs. 12–18% at day 60); a reactivation invitation at day 90 achieves 6–12% acceptance (vs. 12–18%).
| Send timing | Audience | Purpose | Format | Open rate | Response / acceptance rate | Success metric | Common mistake | |
|---|---|---|---|---|---|---|---|---|
| Email 1 Exit interview |
24–48 hours after cancellation confirms | All cancellations | Diagnostic: collect the departure reason while the member can still articulate the primary cause | Plain-text personal email from the operator. No logo, no footer, no unsubscribe link in the visible body. | 55–68% (question-format subject line) |
22–36% (plain-text personal) 3–8% (HTML or automated) |
Response rate and response specificity (did the member identify a primary cause or list grievances?) | Sending the exit interview as a designed HTML email with the community logo and an “unsubscribe” link in the footer. HTML format signals “automated campaign,” response rates drop to 3–8%, and replies are shorter and less diagnostic. The second most common mistake is asking for the departure reason in a multi-question survey link rather than an open-ended reply to a personal email. |
| Email 2 Community update |
14–21 days after cancellation confirms (for respondents to Email 1 only) | Email 1 respondents only (do not send to non-respondents) |
Relationship: report back on what changed from their feedback; prime the 60-day invitation | Plain-text or lightly formatted personal email. Allowed: one bolded sentence, one hyperlink. No HTML email template. | 38–52% (specific-outcome subject line) 18–28% (generic update subject) |
8–14% (reply rate; replies are soft reactivation signals) |
Open rate (validates subject line specificity) and reply rate (replies from Email 2 respondents convert at 28–42% at the 60-day reactivation invitation stage, vs. 12–18% for non-respondents) | Sending Email 2 to all cancellations rather than to Exit interview respondents only. Non-respondents have not established a dialogue; a community update lands as an unsolicited marketing email from a brand they cancelled, suppressing open rates to 8–14% and producing no reactivation signal. The second mistake is making Email 2 a retention pitch rather than a genuine report-back — this collapses the trust established by the plain-text exit interview. |
| Email 3 Reactivation invitation |
55–65 days after cancellation confirms (60 days is the optimal target) |
All cancellations from the departure cohort (include non-respondents to Emails 1–2; personalise where data exists) |
Recovery: convert a former member back into a paying member based on a specific community change that addresses their departure reason | Plain-text personal email with one clear call to action. For pricing-misalignment segment: include one-click rejoin link. For all other segments: include a “here’s what changed” paragraph before the CTA. | 38–52% (outcome-specific subject for personalised) 18–28% (generic “we miss you” framing) |
12–18% (personalised, outcome-specific) 18–28% (pricing misalignment segment with discount) 3–6% (generic, no personalisation) |
Reactivation acceptance rate (rejoins within 14 days of Email 3 send). Split by segment: personalised-with-data vs. generic (non-respondents) | Sending a generic “we miss you — here’s 20% off” email to all cancellations. Generic invitations achieve 3–6% acceptance regardless of discount level, and the discount offer reduces LTV for the members who do accept (they rejoin expecting a lower rate). The reactivation invitation is only effective when it references a specific change that addresses the member’s stated departure reason — which requires exit interview response data from Email 1. |
The sequential dependency in the table above is the key structural insight of the three-email win-back sequence: Email 3’s performance is substantially determined by Email 1’s performance. A community with a 22–36% exit interview response rate has personalised data on 22–36% of its departed members and can send targeted reactivation invitations to that segment (achieving 12–18% acceptance) while sending a generic invitation to the remainder (achieving 3–6% acceptance). A community with a 3–8% exit interview response rate — typically because they sent a designed HTML email rather than a plain-text personal one — sends generic invitations to nearly all departures and recovers 3–6% of them. The formatting decision at Email 1 is the most consequential single variable in the entire sequence.
The non-respondent floor: The 3–6% reactivation rate for generic non-personalised invitations at day 60 represents the natural floor of the departure cohort that would have rejoined regardless of the operator’s actions. These are members whose departure reason resolved on its own (budget unfreezes, busy season ends, job situation changes) and who would have come back at some point. Operators who measure their “win-back rate” using only generic campaigns are measuring this natural-return floor, not the incremental impact of their outreach. The true incremental win-back rate is the difference between the 12–18% personalised acceptance rate and the 3–6% generic floor — approximately 9–12 percentage points per departure cohort. See the win-back email sequence blog post for the worked revenue arithmetic on a 200-member community.
Table 2 — Email format decision table
Email format is the most underappreciated variable in a win-back sequence. Most operators default to the format they use for their standard member communications — branded HTML newsletters with logos, headers, footers, and unsubscribe links. This format is appropriate for active member newsletters and community announcements. It is counterproductive for win-back emails, because it signals “marketing communication” at the moment when the departed member most needs to feel they are receiving personal outreach from the operator as a human being, not as a brand.
The format effect is largest at the exit interview stage (Email 1) because exit interview response rate is maximised by personal authenticity signals. A designed HTML email with a community logo activates the “mass email” mental model: the recipient does not feel they are being personally asked for their opinion; they feel they are receiving a retention campaign. The “plain-text personal” format — sent from the operator’s personal email address (or a personal-appearing address like “sam@communityname.com”), with no visible HTML formatting, no unsubscribe link in the body, and no marketing footer — activates the “the founder is emailing me specifically” mental model, which nearly eliminates the defensive response to a retention-adjacent email and produces the 22–36% response rates in Table 1.
| Format | Open rate | Response rate (exit interview) |
Response quality | Trust signal | Best suited to | Drawback |
|---|---|---|---|---|---|---|
| Plain-text personal (no HTML, no logo, no footer, sent from operator address) |
55–68% (question-format subject) |
22–36% | High — specific primary cause identified in 65–78% of responses | Strongest. Activates “personal outreach from a human” mental model. | Email 1 (exit interview). Strongly recommended. Email 3 (reactivation) for personalised segments where the operator has exit interview data. | Cannot include formatted tables, images, or multi-CTA layouts. Not appropriate for community updates that need to reference specific programming changes with links. |
| Hybrid (personal opening paragraph + minimal HTML body with one link) |
42–58% | 12–22% | Medium — specific cause identified in 42–62% of responses | Moderate. Personal opener signals intent; HTML body partially activates the “marketing email” model. | Email 2 (community update) when the operator wants to include a formatted link to a specific community announcement or event. Email 3 (reactivation) when the CTA requires a formatted rejoin button. | The HTML formatting in the body partially offsets the personal signal of the opening paragraph. Response rates are meaningfully lower than plain-text personal, though meaningfully higher than full HTML. Best used only when the content genuinely requires a formatted element. |
| Designed HTML (community logo, header, footer, unsubscribe link, standard newsletter template) |
28–42% (branded subject line) |
3–8% | Low — specific cause identified in 18–32% of responses; most responses are short and non-diagnostic | Weak for win-back. Activates “mass email campaign” model; triggers the defensive “this is a retention email” response in 60–75% of recipients. | Not recommended for any win-back email. Acceptable for community announcements sent to active members. Produces the same response rate as automated sequences despite higher operator effort. | Opens do not indicate genuine engagement — image-pixel open tracking inflates HTML email open rates by 15–25% vs. plain-text. The 28–42% open rate in this row reflects image-pixel tracking; text-confirmed open rates for HTML exit interview emails are closer to 18–28%. |
| Automated HTML (triggered from billing platform — Stripe, Memberstack, Chargebee — at cancellation event) |
22–35% (billing platform sender) |
3–5% | Very low — specific cause identified in 8–16% of the few responses received; typically one-word or one-sentence replies | None. Members correctly identify this as a system-generated cancellation acknowledgement, not a personal outreach. | The cancellation confirmation email. This email should not include a win-back attempt — its purpose is administrative confirmation of the cancellation, and mixing a retention pitch into an administrative confirmation produces the lowest response rates in the sequence. | The most common error is treating the automated cancellation confirmation as the exit interview by appending a “Why did you cancel?” question to the automated confirmation email. This produces 3–5% response rates and is read as a retention attempt disguised as an administrative message, which is the worst possible first impression of the win-back sequence. |
The practical implication of the format decision table is that a win-back email sequence can be structured with no dedicated email marketing platform. Email 1 can be sent from the operator’s personal email client (Gmail, Outlook) directly to the cancelling member’s email address. Email 2 can be sent from the same client, with a single Markdown-style link pasted as plain text or hyperlinked text. Email 3 can be sent from the same client with a one-click URL. The only tooling required is a way to know which members cancelled and when — available as a Stripe webhook, a Memberstack export, or a manual daily review of the billing dashboard. The format benefit of plain-text personal email is fully realised in a manual workflow at communities below 25–30 monthly cancellations.
The unsubscribe link and CAN-SPAM: Plain-text personal emails to individual members are not bulk commercial messages under CAN-SPAM / GDPR interpretation, and do not legally require an unsubscribe link when they are sent individually by the operator as genuine personal outreach. An exit interview email sent from sam@communityname.com to a specific former member is treated the same as a personal email from any other service provider, not as a marketing campaign. If you send the sequence via an email marketing platform (Klaviyo, ConvertKit, ActiveCampaign), the platform’s bulk sending classification will add an unsubscribe footer automatically, partially offsetting the plain-text personal signal. The highest-response exit interview sequences are sent from a personal email client directly, not via a bulk sending platform.
Table 3 — Subject line benchmarks by email type and framing
The subject line is the primary determinant of open rate in all three emails of the win-back sequence. Unlike active-member email where sender reputation and content quality are dominant signals, win-back emails from a sender the recipient no longer has an active relationship with rely almost entirely on the subject line to earn the open. The data in this table reflects the performance difference between the highest-performing and lowest-performing subject line categories for each email type. The performance gap is substantial: the best-performing exit interview subject lines achieve 55–68% open rates; the worst-performing achieve 15–22%.
| Subject line framing | Example | Open rate | Notes | |
|---|---|---|---|---|
| Email 1 Exit interview |
Single personal question — best performing | “One question, [First Name]” or: “One thing I’d like to know, [First Name]” |
55–68% | The question framing generates intrigue without revealing the retention-adjacent nature of the email. “One question” is short enough to render fully on mobile. First name personalisation adds 4–8 pp to open rate for personal-framing subject lines. Works best when sent from the operator’s personal name rather than the community name. |
| Email 1 Exit interview |
Curiosity / forward reference — good performing | “Something I’m trying to understand, [First Name]” or: “Before you go — one question” |
42–55% | Slightly lower than the pure question format because “before you go” signals the retention-adjacent intent, activating mild defensive response in some recipients. Still outperforms all non-question framings. |
| Email 1 Exit interview |
Retention framing — avoid | “We’re sorry to see you go” or: “Your [Community Name] membership has ended” or: “Come back — here’s a special offer” |
15–32% | “We’re sorry to see you go” is the most common exit interview subject line and achieves the lowest response rate because it reads as a mass-send marketing email. “Here’s a special offer” achieves the worst open rate in the sequence (often below 15%) because it primes the discount-hunting rather than the diagnostic intent, and activates spam filters in Gmail and Outlook. |
| Email 2 Community update |
Specific outcome reference — best performing | “What I learned from your feedback, [First Name]” or: “Something changed in [Community Name] this week” or: “That thing you mentioned — here’s what happened” |
38–52% | Performs best when the subject line is specific enough that the member recognises it refers directly to their exit interview response. The specificity requirement means this subject line category cannot be used unless the operator has a genuine specific community development to reference. |
| Email 2 Community update |
Generic update framing — avoid | “What’s new in [Community Name]” or: “An update from [Community Name]” |
18–28% | Generic community update framing produces newsletter-level open rates from a non-member, because the recipient reads it as an unsolicited community newsletter from a brand they cancelled. The Email 2 open rate advantage comes entirely from the personalisation of the subject line to the member’s specific exit interview response. |
| Email 3 Reactivation invitation |
Outcome-specific reference — best performing | “That [specific concern] you mentioned — we fixed it” or: “Something you said [X] weeks ago is now live in [Community Name]” or: “[First Name], [specific community development that addresses their stated reason]” |
38–52% | Requires exit interview data to use. The subject line references a specific departure reason the member stated 55–65 days earlier. Most effective when the community development referenced in the subject line is real and verifiable — the member will open the email expecting to see evidence of the change, and a vague or absent reference damages trust for any future communication. |
| Email 3 Reactivation invitation |
Pricing / discount framing — pricing-misalignment segment only | “One month back at [discounted rate] — no strings” or: “[First Name], I want you to see what changed first” |
32–44% | Appropriate only for the pricing-misalignment segment (15–20% of departures). The discount reference in the subject line slightly lowers open rate vs. the outcome-specific framing above but raises acceptance rate for this specific segment because the subject line pre-qualifies intent. Sending this subject line to non-pricing-misalignment segments damages brand perception and reduces acceptance rate below 3%. |
| Email 3 Reactivation invitation |
Generic “we miss you” — avoid | “We miss you, [First Name]” or: “Come back to [Community Name]” or: “It’s been 60 days since you left [Community Name]” |
18–28% | Generic reactivation subject lines are indistinguishable from SaaS “winback” campaigns, which most recipients have been trained to ignore or delete. Even when opened, the generic framing produces 3–6% acceptance rates regardless of the email body content, because the member opened expecting a generic retention pitch and reads the body through that filter. |
The subject line pattern across all three emails in the sequence is consistent: specificity and personal framing outperform generic framing by 10–30 percentage points, and question framing outperforms statement framing for the exit interview by 15–25 percentage points. The implication is that generic subject lines are not a neutral choice — they actively suppress open rates below what a non-personalised email to a non-member would achieve if it were framed as personal outreach.
Subject line testing at small community scale: Most paid communities below 500 members cancel fewer than 10–20 members per month, which means subject line A/B tests require multiple months to accumulate statistical significance. For operators at this scale, the benchmarks in Table 3 are more reliable guides than community-specific testing. The exception is operators who have sent multiple rounds of the sequence over 6+ months: at that point, comparing Email 1 response rates between periods with different subject lines can reveal community-specific patterns. See the paid community churn reference card for monthly cancellation benchmarks by community size and price tier.
Table 4 — Exit interview response categories
The value of exit interview data is in categorisation: individual departure reasons are most useful when they are aggregated across a departure cohort and mapped to the systemic cause they reveal. The table below maps four exit interview response categories to observable language signals in the responses (what the member actually writes), the estimated share of departures in each category (highly variable by community type and price tier), and the reactivation rate at 60 days for each segment with and without a targeted offer.
The exit interview response categories are the same root causes documented in the paid community cancellation rate reference card and the paid community offboarding reference card. The critical difference in this context is that the response category determines the reactivation invitation strategy at 60 days: the email body, the CTA, and whether a discount is appropriate are all determined by which category the member falls into. Members who left because of onboarding failure need to see evidence of improved onboarding, not a discount. Members who left because of engagement deficit need to see evidence of increased programming activity or peer engagement opportunities. Members who left because of pricing misalignment are the only segment for whom a discount is the correct offer.
| Response category | Observable language signals | Estimated share of departures |
Exit interview response rate |
60-day reactivation acceptance (personalised) |
60-day reactivation acceptance (with discount) |
Reactivation invitation strategy |
|---|---|---|---|---|---|---|
| Onboarding failure | “I never really figured out where to start” / “I didn’t know which channels to follow” / “I felt overwhelmed by the community structure” / “I joined but never got into the rhythm of it” / “I didn’t make any connections in the first few weeks” | 28–42% (highest share in communities under 6 months old or with no onboarding sequence) |
26–38% (members who left due to onboarding failure have the strongest diagnostic motivation to respond because they didn’t get what they came for) |
8–14% | 8–12% (discount does not address the departure reason; offer a free month for a second onboarding attempt instead) |
Reference the specific aspect of onboarding the member mentioned. Name a structural change: a new welcome sequence, a shorter channel sidebar, a designated onboarding buddy. Offer a 14-day reactivation period with a guided first-week experience as the CTA, not just a rejoin link. Do not offer a discount: the member left because they didn’t get the product, not because the product was overpriced. A discount signals the operator didn’t understand what the member was communicating. |
| Engagement deficit | “The conversations weren’t relevant to what I work on” / “The community felt quiet when I was active” / “I wasn’t connecting with people at my level” / “I got more out of the content than the community itself” / “The active members seemed much more senior / junior than me” | 22–35% | 18–28% | 14–22% | 10–16% (discount does not address the departure reason; offering it signals the operator prioritised price over solving the peer-connection problem) |
Reference the specific engagement gap the member mentioned (relevance of discussions, activity level, peer seniority). Name a concrete programming development: a new peer-matching format, a new AMA series, a new async discussion thread on their stated interest area. Offer access to one specific upcoming event or discussion as the reactivation CTA — lower friction than a full rejoin. Do not offer a discount. |
| Programming void | “I joined for [specific event type] but there haven’t been many recently” / “The content cadence slowed down while I was a member” / “I was hoping for more [specific format: workshops / AMAs / peer reviews / etc.]” / “The programming felt less consistent than when I joined” | 15–25% | 16–24% | 10–16% (requires a genuine programming development to reference — a promise of future programming produces 4–8% acceptance) |
6–12% (discount not appropriate; programming void is a product gap, not a price objection) |
Reference the specific programming format the member mentioned. Name a concrete scheduled programming item that addresses it: a specific upcoming event, a new recurring format, a renewed cadence. Only send the reactivation invitation when you have something real to reference — a vague “we’ve improved our programming” produces 4–8% acceptance (not meaningfully better than generic). The subject line for this segment should name the specific programming: “The [specific format] you mentioned — we have one scheduled for [date].” |
| Pricing misalignment | “I couldn’t justify the monthly cost right now” / “My budget changed and it was the first thing I cut” / “It’s not the right time financially” / “I got more from it when I was at [previous job/stage], but things have changed” / “I’m going to rejoin when the ROI is clearer” | 15–20% | 14–22% (lower than onboarding failure because pricing misalignment is often the stated reason rather than the true reason; members may have left for engagement deficit but cited cost as the politer exit) |
18–28% (highest reactivation rate when a discount or pause option is offered — this is the only segment where a discount is the primary lever) |
18–28% (the discount is the offer; framing matters: “one month to see what changed at [discounted rate]” outperforms “X% off your next month” by 5–9 pp) |
Offer a 30-day reactivation at a discounted rate (20–25% off one month, or one month free) with a clear path back to the standard rate after the trial. Frame the offer as access (“I want you to see what changed before you decide”) rather than as a price reduction (“here’s a discount”). Include one sentence naming a specific community development from the past 60 days to signal that the offer is not just a generic retention discount. Cap the discount at one billing cycle; permanent discounts produce the lowest LTV-per-reactivated-member outcome. |
The category distribution in Table 4 is highly variable across community types and price tiers. Communities under 6 months old or with no automated onboarding sequence see onboarding failure at 35–50% of departures (higher than the 28–42% range in the table above). Communities with strong onboarding but a recent programming slowdown see programming void at 30–45% of departures for the affected cohort. The category distribution from quarterly exit interview aggregation is the most actionable single input for community product decisions: if 38% of a quarter’s exit interviews cite onboarding failure, the highest-ROI investment is a structured onboarding improvement, not a pricing change or content calendar expansion.
The true vs. stated departure reason: Exit interview responses are the stated departure reason, which is not always identical to the true departure reason. Pricing misalignment is frequently cited as the polite exit by members who actually left because of engagement deficit — it is easier to say “I can’t justify the cost” than “I didn’t connect with people here.” The diagnostic signal of pricing misalignment responses is therefore mixed: roughly 60–70% of members who cite price as the primary departure reason have a genuine pricing misalignment; 30–40% have an unstated engagement or onboarding problem. This is one reason the discount-only strategy for the pricing misalignment segment produces 18–28% acceptance (not 35%+): a significant minority of that segment is citing price as a proxy for a different problem that a discount does not address. See the paid community offboarding blog post for the diagnostic framing of the exit interview question that reduces this proxy-reason rate.
Table 5 — Win-back email response benchmarks by community size and price tier
The absolute numbers produced by a three-email win-back sequence are a function of two inputs: the response rates in Tables 1–4, and the monthly cancellation volume, which is determined by community size and churn rate. A community with 500 members at 3%/month churn has 15 cancellations per month and can expect 3–5 reactivations per month from a personalised win-back sequence. A community with 100 members at 5%/month churn has 5 cancellations per month and can expect 0–1 reactivations per month from the same sequence. The table below provides full response benchmarks across four community size and price tier combinations, assuming a well-executed plain-text personal sequence as described in Tables 1–3.
| Community size & price tier | Monthly cancellations (at 3%/mo churn) |
Exit interview response rate | Responses with actionable data | 60-day reactivation (personalised segment) |
60-day reactivation (generic, no data) |
Expected monthly reactivations (blended) |
Monthly revenue recovered (blended, at tier price) |
|---|---|---|---|---|---|---|---|
| Under 100 members $29–$49/mo |
2–3 per month | 22–36% (0–1 responses/month) |
0–1 per month | 10–16% (applied to 0–1 member) |
3–5% (applied to 1–3 members) |
0–1 per month | $0–$49/mo (recovery ROI is low at this scale; sequence value is primarily diagnostic, not revenue) |
| 100–300 members $49–$99/mo |
3–9 per month | 22–36% (1–3 responses/month) |
1–3 per month | 12–18% (applied to 1–3 members) |
3–5% (applied to 2–6 members) |
0–1 per month | $0–$99/mo (recovery arithmetic: at 6 monthly cancellations, 2 responses, 1 personalised invite → 0.2 avg reactivations/mo → $10–$19/mo blended; at 9 cancellations, ~3 responses, 1–2 personalised → 0.2–0.3 avg reactivations/mo → $10–$30/mo blended) |
| 300–1,000 members $99–$199/mo |
9–30 per month | 22–36% (2–11 responses/month) |
2–8 per month | 12–18% (applied to 2–8 members) |
3–5% (applied to 7–22 members) |
1–2 per month | $99–$398/mo (at 20 cancellations, 6 responses, 4 personalised invites → 0.5–0.7 avg reactivations/mo personalised + 0.5–0.7 generic floor → ~1–1.5 reactivations/mo blended → $99–$298/mo at $99/mo; $199–$398/mo at $199/mo) |
| 1,000+ members $149–$299/mo |
30+ per month | 22–36% (7–11+ responses/month) |
7–11 per month | 12–18% (applied to 7–11 members) |
3–5% (applied to 19–23 members) |
2–4 per month | $298–$1,196/mo (at 30 cancellations, 9 responses, 7 personalised invites → 0.8–1.3 reactivations/mo personalised + 0.7–1.2 generic floor → 1.5–2.5 reactivations/mo blended → $225–$748/mo at $149/mo avg; $298–$748/mo at $199/mo avg; $448–$1,196/mo at $299/mo) |
The absolute revenue numbers in Table 5 are modest at smaller community scales, which is why the primary value of the three-email win-back sequence at communities below 200–300 members is diagnostic, not revenue recovery. At 4–6 cancellations per month, a plain-text personal exit interview generating 2–3 responses per month accumulates 24–36 qualitative departure reasons over a year — a statistically meaningful sample for identifying the systemic causes driving cancellations from the active member base. The reactivation revenue at this scale ($0–$99/mo blended) does not justify the sequence on revenue grounds alone; the diagnostic value from using the exit interview data to improve onboarding and engagement for the current member base is the primary return.
At 300+ members, the revenue arithmetic shifts. A community with 1,000 members at 3% monthly churn cancels 30 members per month; at a blended 1.5–2.5 reactivations per month, the three-email sequence recovers $2,700–$9,000/year in revenue that would otherwise be permanently lost, at approximately 10–15 minutes of operator time per month (one batch exit interview review, one batch reactivation send). This is the arithmetic behind the recommendation to automate the sequence at scale: the value of automation is not in improving the reactivation rate (a well-executed manual sequence achieves the same rates), but in removing the operator time cost that otherwise limits the sequence to communities with a dedicated community manager or operations team.
The automation crossover point: The three-email win-back sequence can be run manually at communities below 25–30 monthly cancellations (roughly 800–1,000 members at 3% monthly churn). Above that threshold, the 10–15 minutes per cancellation of manual outreach compounds to 250–375+ minutes per month (4–6 hours), which exceeds most operator budgets for retention operations. At this scale, the Foothold onboarding sequence (Day 0, Day 3, Day 7) reduces monthly cancellation volume by 0.8–2.0 percentage points through improved first-week activation — which reduces the departure cohort that requires win-back outreach by 27–67% at 1,000 members. See the Foothold onboarding health check to measure your current first-week activation rate and estimate the monthly cancellation volume reduction from a structured onboarding sequence. See the member win-back reference card for the full win-back protocol including Slack DM sequences and multi-channel recovery flows.