Email List Reference Card
Paid community email list — two-list decision matrix, digest format reference, list growth mechanisms, subject line formulas, and re-engagement email structure
This page is a structured reference card for paid community operators building or auditing their email list strategy. It covers: a two-list decision matrix (prospect list vs. member list — when to build each, what triggers to set up, primary conversion goal, and what failure looks like); a three-component digest format reference (session takeaway / member win / upcoming item — what each must include, what poor vs. good versions look like, and what each component is doing for each list type); a list growth mechanism selection table (in-article upgrade / bottom-of-post digest pitch / health check tool — when to use each, expected conversion rate range, required conditions, and what to avoid); a subject line formula table by re-engagement scenario (30-day silence / 60-day silence / post-event follow-up / prospect-to-member conversion moment); and a re-engagement email structure table (subject line pattern, opening sentence, single question, closing, what not to include and why). For the conceptual framework — why the announcement-list trap kills email leverage, how the two lists work causally, and why email re-engages lapsed members that Slack cannot reach — see the companion post: Paid community email list: the two lists that actually work. This card is for the operator who understands the reasoning and needs the templates, decision criteria, and reference tables in quick-reference form.
TL; DR
Most paid community operators build one email list that functions as a Slack announcement mirror — meeting reminders, new content links, billing notices. This list is redundant for active members and invisible to lapsed members who have muted Slack. The operators who retain at the highest rates build two separate lists: a prospect list (acquisition function, independent value delivery, converts readers to members) and a member list (retention function, community-specific value, re-engages lapsed members email can reach when Slack cannot). Use Table 1 to determine which list you need to build first. Use Table 2 to write the digest format for each list. Use Table 3 to select the list growth mechanism that matches your content asset. Use Table 4 to select the subject line formula for each re-engagement scenario. Use Table 5 to structure the re-engagement email body. If you can only do one thing: write a single email to your lapsed members (silent for 30+ days) with a personal-feeling subject line and one forward-oriented question — the reply rate will tell you who is recoverable before you have built any of the infrastructure in this card.
Table 1 — Two-list decision matrix
The two email lists a paid community operator needs, in the order they interact with a subscriber’s decision process. The prospect list addresses the acquisition question (“should I join?”); the member list addresses the retention question (“should I stay?”). These questions are structurally different and require structurally different email content to answer them. A single list that tries to answer both questions for both audiences simultaneously answers neither question adequately for either audience. The “primary conversion goal” column names the single action the list is optimized to produce; the “what failure looks like” column names the most common symptom when the list is built or operated incorrectly.
| List type | Who is on it | When to build it | What triggers sign-up | Primary conversion goal | Send cadence | What failure looks like |
|---|---|---|---|---|---|---|
| Prospect list | People who have consumed public content — organic search visitors, content upgrade subscribers, social followers who clicked through to a long-form post — but have not yet paid to join the community. The prospect list is your acquisition asset. Every organic content investment compounds here when the list is built correctly: a long-form post that attracts 500 readers this month adds subscribers who will convert to members over the next 6–18 months, not just the 48 hours after the post goes live. Without a prospect list, organic content produces a one-time traffic spike that does not compound. | Before you have a large community. The prospect list is the correct first list to build because it produces the acquisition function that fills the community, whereas the member list assumes a community that is already running. Operators who wait until they have 100+ members before building the prospect list have already lost the compounding benefit of 6–18 months of organic content investment. The trigger to start the prospect list is when you publish the first piece of content that targets your ICP — not when the community reaches a size threshold. | Three triggers, in order of conversion rate to paying member: (1) A content upgrade offered inside a specific long-form post at the point where the reader encounters the problem the upgrade resolves (2–5% of page visitors, highest intent because the sign-up is contextually motivated). (2) A bottom-of-post digest pitch with a specific honest description of what the digest contains (1–3% of readers who reach the end of a post). (3) A community health check tool or self-assessment that produces a specific output and offers the email digest as a follow-up resource (10–25% of completers, highest because the reader has already invested time and is primed for the output). Generic “subscribe to our newsletter” prompts placed on the homepage or sidebar produce under 1% conversion and attract low-intent subscribers who do not convert to members. | Single-action conversion to paying member. The prospect list has one job: turn a reader who knows the problem exists into a paying subscriber who has seen enough specific evidence of the community’s value to make the purchase decision. Every email in the prospect cadence should contain information that advances this goal directly — a session takeaway that demonstrates what happens inside the community, a member win that shows the specific result a reader at the prospect’s stage achieved, an upcoming event that is only accessible inside. The prospect list is not a relationship-building list in the general sense; it is a conversion list with a longer timeline than a sales page. | Weekly. The weekly cadence is the correct default for the prospect list because it is frequent enough to maintain top-of-mind awareness during the 4–12 week decision window most qualified prospects need, and infrequent enough that the content standard required for each issue (one specific session takeaway, one specific member win, one specific upcoming item) is achievable without manufacturing content. Biweekly cadences produce lower conversion because the decision window often closes between sends; monthly cadences produce lower open rates because the memory of the previous issue has faded. | High unsubscribe rate from prospects who joined with genuine interest but did not convert within 60 days. This typically indicates the digest content is not specific enough to be distinguished from generic community marketing (the “outcomes-without-proof” failure mode): the session takeaway is a category statement rather than a specific metric-and-mechanism observation, the member win is a testimonial quote rather than a named result with a stage descriptor. The symptom to watch: if the open rate is above 30% but the click-through rate to community content is below 5%, the content is being opened and recognized as relevant but not delivering specific enough evidence to advance the conversion decision. |
| Member list | Paying subscribers. The member list is your retention asset. Its primary audience segment is lapsed members — paying subscribers who have reduced their Slack check-in frequency, are muting Slack notifications, or are moving toward cancellation. These members cannot be reached effectively through Slack because the channel they have reduced engagement with is Slack. Email is the only channel that reaches them where they still have attention. Building the member list after members have already cancelled is too late; the correct trigger is when the first member joins the community. | On launch day, when the first member joins. Every new member should be added to the member list at the moment they are added to the Slack workspace. The onboarding sequence (Day 0 DM, Day 3 nudge, Day 7 scorecard) operates through Slack; the member list operates through email as a parallel retention channel that runs independently of Slack engagement. The two channels address different member behavioral states: Slack reaches active members, email reaches lapsed members and members in quiet periods. | Automatic add on successful payment. Members should not opt into the member list — they should be added automatically when they join and have an unsubscribe option in each email. The reason to make the member list an automatic add rather than an optional opt-in: the members who most need the re-engagement function of the member list are the members who are least likely to proactively opt into an additional email list. An opt-in member list is self-selecting toward active members who are already engaged and least at risk of cancelling — the opposite of the audience the list needs to reach. | Keep subscription active through low-engagement periods without requiring the member to return to Slack to receive value. The member list has a different primary conversion goal than the prospect list: it is not trying to convert the member to anything new, it is trying to prevent the cancellation decision from being triggered by silence. A lapsed member who receives weekly evidence that the community is producing specific value for members at their stage is more likely to re-engage when their workload permits than a lapsed member who has been out of contact with the community for 90 days and has mentally disengaged. The secondary goal is re-engagement: the upcoming item component of the digest should provide one specific reason to return to Slack this week. | Weekly. Same cadence as the prospect list for the same reason: the 30-day window before a lapsed member reaches the cancellation threshold is short enough that a biweekly cadence misses it for a meaningful percentage of members. The content of the member list digest is identical in format to the prospect list digest (three components: session takeaway, member win, upcoming item) but differs in the stage specificity of the member win and the framing of the upcoming item. For the member list, the upcoming item should have a specific re-entry call-to-action attached: “This Thursday’s async challenge is about [specific topic]. The thread will be live from Thursday morning — if you want to drop in a question before then, reply to this email and I’ll make sure it gets into the prompt.” | High cancellation rate among members who have been in the community for 45–90 days despite reasonable activation during week one. This indicates the member list is either not running (no email channel to reach lapsed members), not delivering content that is specific enough to distinguish from generic community updates, or sending content that mirrors the Slack announcement channel (which the lapsed member has already muted). The symptom to watch: if the Slack weekly active user rate drops between months two and three across multiple cohorts simultaneously — rather than gradually across individuals — the problem is programming rhythm and the member list is not compensating for it. |
The single most common email list mistake in paid communities is building a member list that functions as a Slack announcement mirror. Meeting reminders, content notifications, and billing notices are operationally necessary but they train the subscriber to open the email only for operational reasons — which means when a lapsed member who has stopped checking Slack receives an email from the community, they have been trained to expect operational information rather than value. An announcement-mirror member list actually accelerates cancellation among lapsed members who have moved to a low-Slack-engagement state because it reinforces the perception that the community’s email channel is for operational updates, not for the community-specific value they signed up for. The member list digest format in Table 2 is designed to deliver independent value on every send, not mirror what is happening in Slack.
Table 2 — Three-component digest format reference
The three-component digest format that applies to both the prospect list and the member list, with component-level guidance for what each must include, what the poor version looks like for each, and what each component is doing for each list type. The format is fixed and consistent across every issue — both because consistency trains subscribers to know what they will receive before they open the email (which reduces the cognitive cost of the open decision) and because the three components are designed to work together as a single conversion argument. Missing any one component degrades the argument; substituting a links roundup or a community news section for a component degrades it more severely because it replaces specific-value content with generic-utility content.
| Component | What it must include | Poor version (what it looks like) | Good version (what it looks like) | What it does for prospect list | What it does for member list |
|---|---|---|---|---|---|
| 1. Session takeaway | The single most transferable insight from the most recent AMA, office hours, or community discussion. Must include: the specific metric or mechanism that makes the insight actionable (not a category statement, but the precise operational detail that changes how a reader approaches the problem); the stage of the member or operator who generated the insight (so the reader can assess whether the insight applies to their situation); and the community context that produced it (what type of session, what the question was). Length: 3–5 sentences. The takeaway is not a summary of the session; it is the single transferable insight extracted from the session and stated in a way that is useful to someone who was not there. | “We had a great office hours session last week where members shared their experiences with improving member retention. Lots of good insights came out of the conversation about onboarding and engagement.” | “In last Thursday’s office hours, an operator who’d just crossed 200 paying members shared a specific fix for the month-two drop-off: she replaced her week-four ‘check-in’ email with a single question — ‘What’s the one thing you haven’t had time to do in the community yet?’ — and sent it only to members who hadn’t posted in 14+ days. Her 90-day cancellation rate dropped from 18% to 11% in the following cohort. The key mechanism: the question surfaces the specific barrier rather than asking the member to self-assess whether they’ve gotten value.” | Demonstrates that the community is producing specific, transferable, stage-relevant knowledge that the prospect cannot get from reading another blog post or community newsletter. The prospect’s decision to join is partly a prediction: “will the conversations inside be specific enough to be useful to me?” The session takeaway is the evidence that answers that question directly. A generic takeaway produces no evidence; a specific takeaway with a metric, a mechanism, and a stage descriptor is the strongest conversion evidence the digest can include. | Re-surfaces community value to a lapsed member who has stopped checking Slack and may have mentally disengaged from the community. A lapsed member who reads a session takeaway that is directly relevant to their current situation is more likely to think “I should check what else came out of that session” than to think “this community isn’t relevant to what I’m working on right now.” The session takeaway is the most important component for the member list because it is the component most likely to trigger a single specific re-engagement action. |
| 2. Member win | A single member’s recent result, written in a specific three-part structure: (1) stage descriptor of the member at the time they started working on the problem (not who they are now, but who they were when they joined or when they started the initiative); (2) the specific metric that changed, with the before and after values; (3) the specific mechanism or action inside the community that contributed to the result. The member win must be at a stage that the reader can identify with — not a success story from a member who is three stages ahead, but a win from a member who was recently in the reader’s situation. Length: 3–4 sentences. The member win is not a testimonial; testimonials are subjective assessments of value. A member win is an objective description of a specific result with a named mechanism. | “Community member Sarah shared that Foothold has been a game-changer for her community. She says she’s been able to focus on what matters most and her members are more engaged than ever before.” | “One of our members — a solo operator who was at 85 paying members and running a 22% 90-day cancellation rate when she joined — dropped that rate to 13% in two cohort cycles. The mechanism: she used the Day 3 conditional nudge template her small group refined in the activation workshop, which replaced her previous ‘hope you’re settling in’ message with a message that asked one goal-specific question and linked directly to the thread that matched the goal she’d stated in her intro post. Her week-one activation rate went from 31% to 54% across the two cohorts.” | Provides the specific social proof that converts a prospect who believes the community could work in theory into a prospect who is confident it will work for someone at their stage specifically. The stage descriptor is the critical element: a member win from someone at the same stage as the prospect (“85 paying members, 22% cancellation rate”) is 3–5 times more persuasive than a win from someone significantly more advanced or less advanced, because the prospect can directly assess whether the situation matches their own. | Provides evidence that the community is continuing to produce specific results for members at various stages, which addresses the lapsed member’s most common silent concern: “maybe the community was more useful when I was actively engaging with it, but I wonder if it’s still producing the kind of results that were relevant to me when I joined.” A stage-matched member win demonstrates that the community is still working for members at the lapsed member’s stage, not just for members who are more advanced. |
| 3. Upcoming item | A single specific event, thread, or resource that is only available inside the community and that the reader cannot access without joining or re-engaging. Must include: the specific format (office hours, async challenge, AMA with a named guest, live session), the specific topic or focus area (narrow enough to be stage-relevant, not “a great community session”), and the specific access mechanism (reply to join the thread, return to Slack to participate, DM the operator to get the recording if they miss it live). The upcoming item should be included in both list versions but with different framing: for the prospect list, the framing is what the subscriber is missing by not being inside; for the member list, the framing is a specific low-barrier re-entry invitation. | “We have lots of great events coming up in the community this month! Join us for our upcoming office hours, community challenges, and exclusive content. Sign up now to get access.” | Prospect version: “This Thursday we’re running a live session specifically for operators between 50 and 150 paying members who are hitting the month-two drop-off for the first time. The session is inside the community only — not recorded publicly. If you want access to the session notes and the follow-up async thread, the community page is here: [link to pricing page]. It’s a 30-day evaluation, so if you join before Thursday, you can attend live.” Member version: “This Thursday we’re running a live session on month-two drop-off for operators at 50–150 members. If you’re working on this right now, this one is worth dropping into. You can drop a question for the session in advance here: [specific thread link]. Or reply to this email and I’ll make sure your situation gets into the conversation.” | The upcoming item is the primary conversion trigger in each digest issue for the prospect list. It answers the question “what specific thing am I missing by not being inside?” with a time-bounded, stage-specific example. The prospect who has been reading the digest for 4–6 weeks and considering joining will often convert on an upcoming item that is directly relevant to their current situation — not because the event itself is what they are paying for, but because the event is the specific decision moment where deferred intent becomes immediate action. | The upcoming item is the primary re-engagement trigger in each digest issue for the member list. The low-barrier re-entry mechanism (drop a question in the thread, reply to this email) is designed to lower the activation energy required for a lapsed member to re-engage: rather than “come back to Slack and catch up on everything you’ve missed,” the invitation is “do one specific thing that takes two minutes and is directly relevant to what you’re working on right now.” Reducing the re-entry action to a single specific minimum-viable step is the most effective mechanism for re-engaging lapsed members without making them feel like they are behind. |
The three-component format works because each component answers a different question in the reader’s decision process. The session takeaway answers “is the conversation inside specific enough to be useful to me?” The member win answers “has this community worked for someone at my stage?” The upcoming item answers “is there a specific reason to act now?” A digest that adds a fourth component — links roundup, community news section, tool recommendations, team update — reduces the clarity of the conversion argument by adding content that answers a different (usually weaker) question. The three-component format is a minimum viable conversion argument, not a minimum viable newsletter. More content does not make it more useful; it makes it less focused and harder to scan.
Table 3 — List growth mechanism selection
Three list growth mechanisms that produce reliable results from organic content without paid acquisition. The mechanisms operate at different conversion rates because they intercept the reader at different points in their intent trajectory: the in-article upgrade intercepts at a high-intent moment (the reader is in the middle of a post and has just encountered the specific problem the upgrade addresses); the bottom-of-post pitch intercepts after the reader has consumed the full post (high familiarity, medium intent); the health check tool intercepts after the reader has invested time in a self-assessment (highest intent, because the tool completion signals that the reader is actively working on the problem). Selection criteria are the operator’s current content assets and the reader’s stage in their decision process, not which mechanism has the highest theoretical conversion rate.
| Mechanism | When to use it | Expected conversion rate | Required conditions | What to avoid |
|---|---|---|---|---|
| In-article upgrade | Use when a long-form article has a specific, discrete section that addresses a narrow problem the ICP reader is actively working on, and when a template, checklist, or reference table that extends the article’s argument can be produced as a standalone document. The upgrade must be genuinely specific to the article’s argument — not a generic resource that could be offered on any page, but a resource that is directly useful only to a reader who has just finished reading the specific section where the upgrade is offered. Best articles for in-article upgrades: step-by-step how-to posts where the reader needs a template to execute the steps, diagnostic posts where the reader needs a checklist to run the diagnosis, and reference posts where the reader needs a table to implement the framework. | 2–5% of organic page visitors. Higher than bottom-of-post because the sign-up is contextually motivated: the reader is at a moment of high intent (they have just encountered the specific problem the upgrade resolves) and the upgrade is the natural next step in executing what they just read. The 2–5% range varies by article specificity (more specific articles attract readers who are more actively working on the problem, producing higher conversion) and by upgrade quality (a template that can be used immediately produces higher conversion than a checklist that requires setup). | Two required conditions. First, the upgrade must be genuinely article-specific: a content upgrade placed inside an article about paid community activation rates that offers a “community newsletter template” is not article-specific — the reader is reading about activation rates, not about newsletters, and the upgrade does not extend the article’s argument. The conversion rate for a non-specific upgrade placed inside an article drops to under 1%, the same as a generic homepage subscribe prompt. Second, the upgrade form must be placed at the specific point in the article where the reader has just encountered the problem the upgrade resolves — not at the top of the article before the problem is established, and not at the bottom after the reader has finished. Placement at the moment of problem-encounter produces 3–4x higher conversion than placement at the article bottom. | Do not use a generic resource as the upgrade content (“download our free community growth guide”). Do not place the upgrade form before the reader has encountered the specific problem it addresses. Do not offer multiple upgrade options on the same article — offering a template and a checklist and a recording reduces conversion because it forces the reader to choose, which creates cognitive cost that reduces sign-up rate. One article, one upgrade, one form, placed at the specific section where it is most useful. |
| Bottom-of-post digest pitch | Use on every long-form post that attracts ICP readers, as the default list growth mechanism for the prospect list. The bottom-of-post pitch is the lowest-effort mechanism to implement (no additional content asset required, just a clear description of the digest) and the highest-coverage mechanism (it captures readers from any post, not just the posts where a specific upgrade has been created). Best articles for the bottom-of-post pitch: long-form how-to posts and reference posts where the reader is likely to want to stay informed about the topic area after finishing the article. | 1–3% of readers who reach the bottom of the post. Lower than the in-article upgrade because the sign-up moment is not contextualized by a specific problem the reader has just encountered — it is a general invitation to receive more content. The conversion rate is significantly higher than a generic “subscribe” prompt (which converts under 0.5%) because the pitch describes the specific content of the digest rather than making a general benefit claim. The 1–3% range varies by the specificity of the digest pitch copy: a generic pitch (“subscribe to our weekly newsletter for community growth tips”) converts at 0.3–0.8%; a specific pitch (see the example below) converts at 1.5–3%. | One required condition: the pitch copy must describe the specific content of the digest, not what the community is or what the newsletter is about in general terms. The pitch should answer the reader’s question “what will I actually receive if I subscribe?” before they ask it. Specific pitch components that must be present: the format (one AMA takeaway, one member win, one upcoming item); the specificity level (with the specific metric and mechanism, not a general observation); the send cadence (once per week); and a clear description of what the digest is not (“no links roundup, no community news, just the three things above”). Including what the digest is not is as important as describing what it is, because it distinguishes the digest from generic community newsletters that subscribers have already subscribed to and stopped reading. | Do not use vague benefit language in the pitch (“get insights on community growth delivered to your inbox” — this describes every newsletter in the community operator category and does not distinguish this digest from any of them). Do not place the pitch at the top of the post before the reader has read the content that establishes your credibility to deliver on the promise. Do not include multiple calls-to-action at the bottom of the post (subscribe + follow on social + download a resource) — each additional CTA reduces the conversion rate of each individual CTA. |
| Health check tool | Use when the operator has a short self-assessment or diagnostic tool that produces a specific output tailored to the user’s answers. The health check tool is the highest-converting list growth mechanism because it intercepts the reader after they have invested time in providing their own data, which primes them to receive the specific follow-up the tool output promises. Best deployment: a five-to-eight-question self-assessment covering the operator’s ICP problem (for Foothold: onboarding sequence completeness, activation rate, channel count, monthly retention rate, member re-engagement approach) that produces a specific diagnosis based on the answers and offers the email digest as the follow-up resource for the reader who wants to address the diagnosis. | 10–25% of tool completers. Significantly higher than the other two mechanisms because the conversion happens after an interaction that has already demonstrated the reader’s high intent: completing a self-assessment requires time, honest input, and the expectation of a specific output. A reader who completes a five-question health check and sees a diagnosis that identifies three specific things to fix is more likely to subscribe to a weekly resource that addresses those specific things than a reader who encountered a generic subscribe prompt at the bottom of a post. The 10–25% range varies by how closely the tool output aligns with the digest content (highest conversion when the output identifies the same problem the digest covers). | Two required conditions. First, the tool must produce a genuinely specific output based on the user’s answers. A health check tool that produces the same output regardless of the answers (“your community has room to improve in all three areas”) trains readers not to complete the tool because the output is predictable regardless of their input — and a reader who suspects the output is generic will not reach the email subscribe prompt. Second, the connection between the tool output and the digest must be explicit and specific: “Based on your answers, your week-one activation rate is below the 45% threshold. The digest covers a specific onboarding intervention each week from operators who have been working on exactly this — here’s how to get it.” A generic “subscribe to learn more” prompt following a specific diagnosis converts at 3–5%; a prompt that explicitly connects the tool output to the digest content converts at 10–25%. | Do not use a tool that produces the same output for different inputs. Do not require the reader to provide their email address before seeing the tool output — this significantly reduces tool completion rates (most readers will not provide an email address for an output they have not yet evaluated as worth having). Collect the email after the output is visible, with the offer of a follow-up resource that extends the diagnosis. Do not make the tool longer than eight questions: each additional question after eight reduces completion rate by approximately 8–12% in tools of this type. |
The three mechanisms are not mutually exclusive and they are not substitutes for each other. The correct implementation is all three, deployed in the sequence that matches your current content assets: start with the bottom-of-post digest pitch (no additional content asset required, deploys on every existing post immediately); add in-article upgrades to the three highest-traffic posts (requires one specific upgrade per post, but produces higher conversion from readers who are most actively working on the problem); build the health check tool as a longer-term asset (highest conversion rate, but requires the most effort to build and the most maintenance to keep the output accurate as the community’s knowledge base evolves). See paid community member acquisition for the channel comparison table that places email list growth in the context of the six acquisition channels available to paid community operators.
Table 4 — Subject line formula by re-engagement scenario
Four re-engagement scenarios with the subject line formula that produces the highest open rate for each. Subject line selection matters more for re-engagement emails than for any other email type because the open decision for a re-engagement email is made by a recipient who has been in a reduced-attention state toward the community for 30+ days — which means the subject line must earn the open without the benefit of a warm relationship or a recent high-engagement send history. The formula in each cell identifies the structural pattern, not a fixed template; fill in the brackets with the specific details of the member’s situation and the community’s current event or content.
| Scenario | Subject line formula | Example using the formula | Why it works | What to avoid and why |
|---|---|---|---|---|
| 30-day silence (member has not posted in Slack for 28–35 days; still within the recoverable window where re-engagement rate is 35–55%) | Forward-oriented question about the member’s current focus, with no mention of silence or absence. Formula: “[One question about what the member is working on right now, phrased as if the operator has been thinking about the member’s specific situation]” or “Quick question about [the specific problem area the member named in their intro post]” or “[Specific topic] — are you working on this right now?” | “Quick question about your month-two drop-off” / “What are you most focused on in your community right now?” / “Month-two retention — are you working on this?” | The 30-day silence window is early enough that the member has not formed a strong mental model of themselves as “lapsed.” They have been quiet, but they are likely still thinking about the problems the community addresses. A forward-oriented subject line meets them where their attention currently is (the problem they are working on) rather than where the operator has noticed they haven’t been (Slack). The question format produces higher open rates than a statement because it creates a natural response impulse — the reader wants to answer the question, which means they open the email to see what context it is being asked in. | Do not open with silence or absence (“Haven’t heard from you in a while”, “We miss you in the community”, “Checking in — everything okay?”). These subject lines make the member the subject of the email rather than their work, which produces defensive reading rather than curious reading. A member who has been quiet for 30 days knows they have been quiet; opening with that observation provides no new information and positions the email as a social obligation rather than a resource. |
| 60-day silence (member has not posted in 56–70 days; re-engagement rate drops to 15–30%; the primary goal shifts from re-engagement to identifying whether the member is pre-cancellation) | Specific community event or resource with a direct connection to the member’s known situation. Formula: “[Specific session or resource] + [the specific problem area it addresses] + one implied question” or “This [month/week’s] [session/thread/resource] — relevant to [the specific situation the member described when they joined]?” | “This month’s retention session — directly relevant to the month-two problem you mentioned?” / “Last week’s office hours: the exact activation question you asked in your intro” / “One thing from Thursday’s session that’s relevant to [their stated goal]” | At 60 days of silence, the member has formed a partial mental disengagement from the community. The subject line must re-connect the community to something they specifically said they cared about when they joined — which requires using the member’s own language from their intro post or their stated goal in the Day 0 DM. A subject line that references the member’s specific situation (“the month-two problem you mentioned”) feels personal rather than mass-email because it contains information that is only available to someone who was paying attention when the member joined. | Do not use urgency or scarcity framing at the 60-day mark (“Your membership is at risk”, “Last chance to re-engage before we remove your access”). A member who has been silent for 60 days and receives an urgency email will interpret it as a cancellation prompt rather than a re-engagement invitation — it accelerates the decision to cancel rather than deferring it. Do not use the member’s name in the subject line without a genuine personal reference: “Hi [Name], we miss you” is personalisation without substance and produces lower open rates than a non-personalised forward-oriented question. |
| Post-event follow-up (member attended a community event but has not posted in Slack in the 7 days following the event; re-engagement rate at this moment is 40–60% because the event has restored some community salience) | Specific reference to what the member got from the event, with one forward-oriented question. Formula: “[The specific thing from the event that is most likely to have been relevant to this member] — what did you think?” or “From [event name]: [specific takeaway] — are you trying this?” | “From Thursday’s session: the Day 3 nudge rewrite — are you testing this?” / “What you took from the activation workshop — quick check-in” / “The specific question you asked at office hours — here’s what two other members said after” | The post-event window is the highest-probability re-engagement moment outside the initial onboarding window because the member’s community salience is temporarily elevated. The subject line must capture that elevated salience immediately by referencing the specific event content before the salience fades. A subject line that references what the member specifically got from the event (“the Day 3 nudge rewrite”) is more effective than a general reference to the event (“from Thursday’s session”) because it connects to the member’s attention at the highest-salience moment — the specific thing they were focused on during the event. | Do not use a general session recap subject line (“Session recap: Thursday’s office hours”). A member who attended the event already has the session content in their memory; a recap subject line positions the email as a repeat of something they already have, which reduces open motivation. The post-event email is a forward-orientation email, not a recap: its job is to connect what the member took from the event to what they do next, not to summarise what happened. |
| Prospect-to-member conversion moment (prospect subscriber has been on the list for 6–10 weeks and a specific upcoming community event is directly relevant to their stated situation; conversion rate at a well-timed specific offer is 18–32%) | Specific upcoming community event with a time-bounded framing and a direct connection to the subscriber’s known situation. Formula: “[Specific event happening inside the community] — [direct relevance to the subscriber’s situation] — [time-bounded access note]” or “[The problem the subscriber is working on] — live session Thursday for members only” | “Month-two drop-off session Thursday — for community members only” / “Operators at 50–150 members: live session on the activation cliff, this Thursday inside the community” / “The specific question you asked in your intro survey — we’re covering it Thursday” | The prospect-to-member conversion moment requires three elements in the subject line: specificity of the event (not “a great session” but the exact problem being addressed), stage-matching (the event is only relevant if the prospect recognises their own situation in the stage description), and exclusivity framing (the event is only inside the community, not a public webinar). All three elements must be present for the subject line to produce the conversion impulse rather than a general-interest open. The time-bounded framing (“this Thursday”) converts deferred intent into an immediate decision without manufacturing urgency: the deadline is real (the session is on Thursday), not artificial. | Do not use pricing or discount language in the subject line at the conversion moment (“Join now at 20% off”, “Special offer for newsletter subscribers”). A prospect who has been reading the digest for 6–10 weeks has been building a value-based decision; a discount subject line reframes the decision as a price-based decision and activates comparison-shopping behaviour rather than the value-recognition behaviour the digest has been building. The conversion subject line should complete the value argument, not introduce a price argument. |
The subject line formulas in Table 4 share one structural property: they are about the recipient’s situation, not about the community’s news. The most common subject line failure in community re-engagement emails is centering the community rather than centering the member: “What’s new at [Community Name]”, “[Community Name] monthly update”, “We’ve been busy at [Community Name]”. These subject lines answer the question “what has the community been doing?” rather than “what is the recipient working on right now?” A recipient who has been in a reduced-attention state toward the community is making the open decision based on whether the email is about something they care about right now — and what they care about right now is their work, not the community’s news. The subject line formulas that consistently produce the highest open rates in re-engagement scenarios are the ones that meet the recipient where their attention is, not where the operator wishes it were.
Table 5 — Re-engagement email structure
The five-component structure for a re-engagement email to a silent paid community member. The structure applies to the 30-day and 60-day re-engagement scenarios from Table 4; the post-event follow-up and prospect conversion moment scenarios use a modified structure where component 2 (the bridge) precedes component 1 (the single question). Each component has a specific job in the email’s conversion argument; the “what not to include and why” column identifies the most common additions that degrade the component’s effectiveness.
| Component | What to include | Example | What not to include and why |
|---|---|---|---|
| 1. Opening sentence | One sentence that references the member by first name and states one specific thing that is happening in the community right now — not a general “there’s been a lot happening” opener, but a single named event, takeaway, or thread. The opening sentence is not an acknowledgement of the silence; it is a transition directly to the community’s current activity that is relevant to the member. The sentence should be short enough that the recipient can read it in the preview pane before opening: ideally under 15 words. | “Hey [Name] — we just wrapped a session on the month-two activation cliff that I think you’d find useful.” | Do not open with a greeting about the silence (“It’s been a while since I’ve heard from you”, “I noticed you haven’t been as active recently”). These openings make the recipient the subject of observation rather than the recipient of something useful, which produces a reading posture of self-consciousness rather than curiosity. Do not open with a general community update (“Things have been really exciting in the community lately”) because it provides no specific information and signals that the email is a mass newsletter rather than a personal message. |
| 2. Single question | One forward-oriented question that is directly relevant to the member’s likely current situation and that has a one-word or one-phrase answer. The question must be answerable by replying directly to the email — not by clicking a link, filling out a form, or returning to Slack. The single-question format produces substantially higher reply rates than multiple questions (each additional question reduces reply rate by approximately 30–40% because it forces the recipient to evaluate which question to answer first). The question should be one the operator genuinely wants to know the answer to: manufactured questions produce lower reply rates because they are harder to write authentically and recipients can often sense the difference. | “What are you most focused on in your community right now?” / “Where are you with the month-two problem you mentioned when you joined?” / “Is activation still the thing you’re working on, or has the focus shifted?” | Do not include multiple questions (“How are things going? What are you working on? Is there anything I can help with?”). Multiple questions require the recipient to decide which one to answer, which introduces cognitive overhead that reduces reply rate. Do not include a question that requires a long answer (“Tell me about your biggest community challenge right now”) — open-ended questions with no implied scope produce lower reply rates than focused questions with a clear one-phrase answer. Do not include a question about the silence (“Is there anything that’s been keeping you from being as active in the community?”) — this asks the member to produce a socially awkward answer about their own absence, which the member will avoid by not replying. |
| 3. Bridge sentence | One sentence that connects the question to a specific community event or resource, making the operator’s reason for asking explicit. The bridge sentence is the most important structural element for avoiding the “this feels like a template” reading: it shows that the operator is asking the question in the context of a specific community event or resource, not as a general check-in. The bridge must reference something real and specific: a named session, a specific thread, a named member who recently worked through the same problem. | “I ask because [Member name, with a stage descriptor] just worked through exactly this in last week’s session and I think you’d find the outcome relevant — but I want to make sure I send you the right part of the notes.” | Do not use a bridge that is generic or could apply to any member (“I ask because we’re always looking for ways to help our members”). Generic bridges reveal that the email is templated rather than personalized, which reduces the reply rate because the recipient concludes that the operator is not actually interested in their specific situation. Do not use a bridge that implies the recipient has been falling behind (“I want to make sure you don’t miss out on what’s been happening”) — this implies that absence is a problem the member needs to solve, which is a subtle version of the silence-acknowledgement problem from component 1. |
| 4. Closing (re-entry invitation) | One specific low-barrier re-entry point — not a general invitation to return to Slack, but a single named action that the member can take without catching up on everything they have missed. The re-entry point must be: specific (a named thread, a named session, a specific resource — not “come check out what’s been happening”); low-barrier (an action that takes two minutes or less and does not require the member to have read anything before they can participate); and optional (“if this is relevant to where you are right now” rather than “I’d love to see you back in the community”). | “If the month-two problem is still where your focus is, the thread from last week’s session is here: [specific thread link]. Or reply to this email and I can pull out the two or three points that are most relevant to your situation.” | Do not close with a general re-engagement invitation (“Hope to see you back in the community soon”, “We’d love to have you more active”). These closings make the member’s absence explicit again and frame the email as a request for the member to change their behavior rather than as a delivery of something useful. Do not include multiple re-entry options (a thread link, an event invitation, a resource, and a “come back to Slack” ask) — multiple options produce the same cognitive overhead problem as multiple questions. One specific re-entry point, with an alternative that requires even less effort (reply to this email instead of returning to Slack). |
| 5. Signature | The operator’s first name. No title, no team name, no unsubscribe-guilt language (“I hope you don’t unsubscribe”). The signature should match the sender name in the From field — the email should come from “[Operator first name] at Foothold” or equivalent, not from “The Foothold Team” or “[Community Name]”. The reason: a re-engagement email signed by a team name is implicitly a mass newsletter; a re-engagement email signed by the operator’s first name is implicitly a personal message. The distinction is visible in the signature even when everything else is identical, and it affects the reading posture the recipient brings to the email. | “[Operator first name]” or “[Operator first name] / Foothold” | Do not include a promotional postscript (“P.S. If you haven’t tried the community health check yet, here’s the link”). A postscript in a re-engagement email signals that the email has a secondary agenda beyond the question it asked, which reduces the authenticity of the primary question. Do not include social media links, company news, or resource lists below the signature — these belong in the digest format, not in a personal re-engagement email. The re-engagement email should end with the signature and nothing else: the email is a question and a bridge, not a newsletter with a re-engagement hook. |
The five-component re-engagement email structure is short by design: three to five sentences total, plus the signature. Length is the most common error in re-engagement emails — operators who have not been in contact with a member for 30–60 days often feel the need to justify the email by providing a lot of content. A longer email performs worse for re-engagement because: (1) it signals to the recipient that they need to invest time to process it, which raises the activation energy for reading; (2) it is harder to make a long email feel personal, so the template quality becomes more visible; and (3) a long email that requires the recipient to read several paragraphs before getting to the action point produces the same abandonment pattern as a long form on a conversion page. Three to five sentences, one question, one re-entry invitation, one signature. See paid community member win-back for the inactivity segment framework that determines which member profile each component of this structure is most effective for.
Frequently asked questions
What is the difference between a paid community prospect list and a member list?
A prospect list is for people who have consumed public content but not yet paid to join the community. Its primary conversion goal is a single action: convert a reader into a paying member by delivering enough specific evidence of the community’s value that the prospect can make the purchase decision. A member list is for paying subscribers. Its primary goal is retention and re-engagement, not acquisition — specifically, reaching lapsed members who have reduced their Slack check-in frequency and cannot be reached effectively through Slack. The two lists require separate sign-up forms, separate send cadences, and separate content approaches even though the digest format (three components: session takeaway, member win, upcoming item) is identical across both. The operational distinction: the prospect list is your acquisition channel; the member list is your retention channel. Building one when you need the other is the most common email list mistake in paid communities. See Table 1 for the full two-list decision matrix with when to build each, what triggers sign-up, the primary conversion goal, and what failure looks like for each list type. For the strategic reasoning behind the two-list approach, see the companion post: Paid community email list: the two lists that actually work.
What should a paid community email digest include?
A paid community email digest should include exactly three components in a fixed, consistent format: a session takeaway (the single most transferable insight from the most recent AMA or office hours, with the specific metric or mechanism that makes it actionable), a member win (one member’s recent result in a three-part structure: stage descriptor + specific metric that changed + the community mechanism that contributed to it), and one upcoming item (a specific event or resource only available inside the community, with different framing for prospect subscribers vs. member subscribers). The digest should not include links roundups, community news, promotional copy, or a fourth component of any kind. Each component answers a different question in the reader’s decision process: the session takeaway answers “is the conversation inside specific enough to be useful to me?” The member win answers “has this community worked for someone at my stage?” The upcoming item answers “is there a specific reason to act now?” Adding content beyond the three components reduces the clarity of the conversion argument, even when the additional content is genuinely useful. See Table 2 for the three-component format reference with what each component must include, what the poor version looks like, and what each component is doing for each list type.
How do you grow a paid community email list from content?
Three mechanisms produce reliable results from organic content without paid acquisition. The in-article upgrade offers a specific, article-related template or checklist at the moment in the article where the reader encounters the exact problem the upgrade resolves. Expected conversion: 2–5% of organic page visitors; requires the upgrade to be genuinely specific to the article’s argument and placed at the right section (not at the top or bottom). The bottom-of-post digest pitch describes the specific content of the digest at the end of every long-form post — not what the community is or a general benefit claim, but a clear honest description of what one issue looks like: format, specificity level, send cadence, and what the digest is not. Expected conversion: 1–3% of readers who reach the bottom of the post; the specificity of the pitch copy is the primary variable. The health check tool is a short self-assessment (five to eight questions) that produces a specific output and offers the email digest as the follow-up resource. Expected conversion: 10–25% of tool completers; requires the output to be genuinely specific to the user’s answers, not generic. Deploy all three in sequence: bottom-of-post pitch first (no additional content required), in-article upgrades on the highest-traffic posts, health check tool as a longer-term asset. See Table 3 for all three mechanisms with required conditions and what to avoid.
How do you write a re-engagement email for a silent paid community member?
A re-engagement email should follow a five-component structure: (1) opening sentence that references the member by first name and names one specific community event or resource — no mention of silence or absence; (2) single forward-oriented question that has a one-phrase answer and can be replied to directly (“What are you most focused on in your community right now?”); (3) bridge sentence that connects the question to a specific community event or resource so the operator’s reason for asking is explicit; (4) one specific low-barrier re-entry point (a named thread or event, plus an alternative that requires even less effort: “or reply to this email and I can pull out the relevant parts”); (5) the operator’s first name as the signature, not a team name. Total length: three to five sentences. The email should not include: multiple questions, a list of re-entry options, acknowledgement of the silence, urgency framing, promotional postscripts, or social media links. The subject line should be forward-oriented and personal-feeling: “What are you most focused on in your community right now?” or “Quick question about [the specific problem area they named when they joined]” — not backward-oriented (“Haven’t heard from you in a while”). See Table 4 for subject line formulas by re-engagement scenario and Table 5 for the full five-component structure with examples and what to avoid for each component.