The 1:1 Founder Outreach Cadence
At small scale, personal DMs are your highest-leverage retention tool — but only if systematized so you don't play favorites or forget.
☐ Trigger A: member hits activation event → DM a genuine thanks within 48h
☐ Trigger B: member goes quiet 14 days → one personal check-in
☐ Trigger C: member shares a big win → DM to amplify + ask to spotlight
☐ Cap: no more than 2 founder DMs per member per month
☐ Log every DM: member, trigger, date, response
The SOP ties each DM to a countable trigger, so outreach scales by rule instead of mood. The log prevents double-messaging and shows you who's slipping. Past ~500 members, hand Trigger A and B to ambassadors using the same script.
Review the log weekly for unanswered check-ins.
Save this for your next launch.
At small scale, personal DMs are your highest-leverage retention tool — but only if systematized so you don't play favorites or forget.
☐ Trigger A: member hits activation event → DM a genuine thanks within 48h
☐ Trigger B: member goes quiet 14 days → one personal check-in
☐ Trigger C: member shares a big win → DM to amplify + ask to spotlight
☐ Cap: no more than 2 founder DMs per member per month
☐ Log every DM: member, trigger, date, response
The SOP ties each DM to a countable trigger, so outreach scales by rule instead of mood. The log prevents double-messaging and shows you who's slipping. Past ~500 members, hand Trigger A and B to ambassadors using the same script.
Review the log weekly for unanswered check-ins.
Save this for your next launch.
The Event Attendance Loop
Low live turnout is almost always a reminder-system failure, not an interest failure. Build a fixed pre-event cadence.
☐ T-minus 7 days: announce with date, time in two timezones, one-line value
☐ T-minus 1 day: "tomorrow" reminder + add a calendar link
☐ T-minus 1 hour: "starting soon" ping in the main channel
☐ T-minus 5 min: drop the join link as a fresh message
☐ T-plus 1 hour: post the recap + replay for the 80% who missed it
The SOP treats the recap as part of the event, not an afterthought — most of your community consumes events asynchronously. The fresh link at T-minus 5 beats a link buried in a 7-day-old post. Run the same cadence every time so members learn the rhythm.
Track live ÷ registered and recap views separately.
Save this for your next launch.
Low live turnout is almost always a reminder-system failure, not an interest failure. Build a fixed pre-event cadence.
☐ T-minus 7 days: announce with date, time in two timezones, one-line value
☐ T-minus 1 day: "tomorrow" reminder + add a calendar link
☐ T-minus 1 hour: "starting soon" ping in the main channel
☐ T-minus 5 min: drop the join link as a fresh message
☐ T-plus 1 hour: post the recap + replay for the 80% who missed it
The SOP treats the recap as part of the event, not an afterthought — most of your community consumes events asynchronously. The fresh link at T-minus 5 beats a link buried in a 7-day-old post. Run the same cadence every time so members learn the rhythm.
Track live ÷ registered and recap views separately.
Save this for your next launch.
The Evergreen Content Recycling Loop
Your best threads die in the scroll within 48 hours. Build a loop that re-surfaces proven content on a schedule.
☐ Tag every thread that beats 2x your average reply depth as "evergreen"
☐ Store the link + one-line hook in a recycling doc
☐ Cadence: one evergreen re-share per week, reframed as "worth revisiting"
☐ Rotate so no piece repeats inside 90 days
☐ Update the resource before re-sharing if facts changed
The SOP rule: re-share by performance data, not by what you personally liked. New members never saw your old hits, and the algorithm forgot them — recycling serves both. A documented evergreen library means your worst content week still ships proven material.
Audit the doc quarterly; retire pieces that underperform on re-share.
Save this for your next launch.
Your best threads die in the scroll within 48 hours. Build a loop that re-surfaces proven content on a schedule.
☐ Tag every thread that beats 2x your average reply depth as "evergreen"
☐ Store the link + one-line hook in a recycling doc
☐ Cadence: one evergreen re-share per week, reframed as "worth revisiting"
☐ Rotate so no piece repeats inside 90 days
☐ Update the resource before re-sharing if facts changed
The SOP rule: re-share by performance data, not by what you personally liked. New members never saw your old hits, and the algorithm forgot them — recycling serves both. A documented evergreen library means your worst content week still ships proven material.
Audit the doc quarterly; retire pieces that underperform on re-share.
Save this for your next launch.
Automated welcome DM vs manual greeting: the 200-member line
The instinct is to automate welcomes early. That kills the one signal new members read for: is a human here?
The line is roughly 200 weekly joins.
Below 200/week:
☐ Manual greeting, tagged by a named human, within 4 hours.
☐ One specific question per new member, not a template.
☐ Reply rate to your greeting is your activation metric.
Above 200/week:
☐ Automated welcome that does ONE job: route to the next step.
☐ Keep a human follow-up only for members who reply.
☐ Never let the bot ask a question it can't answer.
The tradeoff: manual scales your warmth but caps your volume. Automation scales volume but flattens warmth to zero if it pretends to be human.
The hybrid wins: bot routes, human catches the repliers. Set the trigger at reply, not at join.
Save this for your next launch.
—
Ещё больше linkedin algorithm в @B2BLabReport
The instinct is to automate welcomes early. That kills the one signal new members read for: is a human here?
The line is roughly 200 weekly joins.
Below 200/week:
☐ Manual greeting, tagged by a named human, within 4 hours.
☐ One specific question per new member, not a template.
☐ Reply rate to your greeting is your activation metric.
Above 200/week:
☐ Automated welcome that does ONE job: route to the next step.
☐ Keep a human follow-up only for members who reply.
☐ Never let the bot ask a question it can't answer.
The tradeoff: manual scales your warmth but caps your volume. Automation scales volume but flattens warmth to zero if it pretends to be human.
The hybrid wins: bot routes, human catches the repliers. Set the trigger at reply, not at join.
Save this for your next launch.
—
Ещё больше linkedin algorithm в @B2BLabReport
The First-72-Hours Onboarding Loop
Most members who go silent do it in the first 3 days, not month 3. Build a fixed SOP (standard operating procedure) tied to join time, not vibes.
☐ Hour 0: auto-DM with one question they must answer to unlock posting
☐ Hour 2: a human (named, with photo) reacts to their intro
☐ Hour 24: tag them into one live thread matched to their intro answer
☐ Hour 48: send the single best evergreen resource, no pitch
☐ Hour 72: ask for one tiny contribution (a reply, a vote, a link)
The trigger is always elapsed time since join, fired by a scheduled job, never by a moderator remembering. Track the percent who complete step 5. That number is your real onboarding rate.
Save this for your next launch.
Most members who go silent do it in the first 3 days, not month 3. Build a fixed SOP (standard operating procedure) tied to join time, not vibes.
☐ Hour 0: auto-DM with one question they must answer to unlock posting
☐ Hour 2: a human (named, with photo) reacts to their intro
☐ Hour 24: tag them into one live thread matched to their intro answer
☐ Hour 48: send the single best evergreen resource, no pitch
☐ Hour 72: ask for one tiny contribution (a reply, a vote, a link)
The trigger is always elapsed time since join, fired by a scheduled job, never by a moderator remembering. Track the percent who complete step 5. That number is your real onboarding rate.
Save this for your next launch.
The Lurker-to-Poster Activation Ladder
90% of a healthy community never posts, and that is fine — until you can't convert the 10% who would. Give them a rung-by-rung path with rising effort.
☐ Rung 1: react with an emoji (zero-typing ask)
☐ Rung 2: vote in a poll (one tap, opinion captured)
☐ Rung 3: answer a fill-in-the-blank prompt
☐ Rung 4: reply to someone else's post
☐ Rung 5: start their own thread
The SOP rule: never ask a lurker to jump two rungs at once. Your weekly content cadence should always contain at least one Rung 1 and one Rung 2 entry point, so a silent member can act in under five seconds.
Measure how many members climb one rung per month.
Save this for your next launch.
90% of a healthy community never posts, and that is fine — until you can't convert the 10% who would. Give them a rung-by-rung path with rising effort.
☐ Rung 1: react with an emoji (zero-typing ask)
☐ Rung 2: vote in a poll (one tap, opinion captured)
☐ Rung 3: answer a fill-in-the-blank prompt
☐ Rung 4: reply to someone else's post
☐ Rung 5: start their own thread
The SOP rule: never ask a lurker to jump two rungs at once. Your weekly content cadence should always contain at least one Rung 1 and one Rung 2 entry point, so a silent member can act in under five seconds.
Measure how many members climb one rung per month.
Save this for your next launch.
The Ambassador Program in 4 Defined Tiers
Ambassador programs fail when "helping out" has no structure. Define tiers with explicit entry triggers and concrete perks, written down before you recruit anyone.
☐ Tier 0 Helper: answered 5 questions this month — gets a role badge
☐ Tier 1 Guide: ran 1 onboarding welcome batch — gets early-access to drops
☐ Tier 2 Host: ran 1 live event or AMA — gets co-branding on the recap
☐ Tier 3 Partner: sustained 3 months at Tier 2 — gets revenue share or comp
Each promotion fires on a countable action, reviewed monthly, not on favoritism. Each tier has exactly one expected duty and one perk. Publish the ladder so every member sees the path.
Keep a roster doc: name, tier, entry date, last activity.
Save this for your next launch.
Ambassador programs fail when "helping out" has no structure. Define tiers with explicit entry triggers and concrete perks, written down before you recruit anyone.
☐ Tier 0 Helper: answered 5 questions this month — gets a role badge
☐ Tier 1 Guide: ran 1 onboarding welcome batch — gets early-access to drops
☐ Tier 2 Host: ran 1 live event or AMA — gets co-branding on the recap
☐ Tier 3 Partner: sustained 3 months at Tier 2 — gets revenue share or comp
Each promotion fires on a countable action, reviewed monthly, not on favoritism. Each tier has exactly one expected duty and one perk. Publish the ladder so every member sees the path.
Keep a roster doc: name, tier, entry date, last activity.
Save this for your next launch.
Pairs well with this channel
@ServerSignal — Deep research into what makes Discord and Telegram communities thrive — long… Quietly one of the better feeds in the space.
@ServerSignal — Deep research into what makes Discord and Telegram communities thrive — long… Quietly one of the better feeds in the space.
The 3-Strike Moderation Decision Tree
Mods burn out when every incident needs a judgment call. Replace judgment with a decision tree so any mod responds identically.
☐ Is it spam or a scam link? → Remove + ban, no warning, log it
☐ Is it rule-breaking but human? → Strike 1: remove + DM the rule
☐ Repeat within 30 days? → Strike 2: 24-hour mute + DM
☐ Third within 30 days? → Strike 3: remove from community
☐ Is it a gray-area conflict? → Escalate to lead, do not improvise
Write the SOP so the answer is never "it depends on the mod." Strikes reset after 30 clean days. Keep a shared incident log with member, date, and action — that log protects you when someone appeals.
Review the log monthly for repeat patterns.
Save this for your next launch.
Mods burn out when every incident needs a judgment call. Replace judgment with a decision tree so any mod responds identically.
☐ Is it spam or a scam link? → Remove + ban, no warning, log it
☐ Is it rule-breaking but human? → Strike 1: remove + DM the rule
☐ Repeat within 30 days? → Strike 2: 24-hour mute + DM
☐ Third within 30 days? → Strike 3: remove from community
☐ Is it a gray-area conflict? → Escalate to lead, do not improvise
Write the SOP so the answer is never "it depends on the mod." Strikes reset after 30 clean days. Keep a shared incident log with member, date, and action — that log protects you when someone appeals.
Review the log monthly for repeat patterns.
Save this for your next launch.
The Activation Metric Worksheet
You can't improve "engagement" because it isn't one number. Define your single activation event — the action that predicts a member stays.
☐ List actions new members take in week 1
☐ For each, check 30-day retention of members who did vs didn't
☐ Pick the action with the biggest retention gap — that's your activation event
☐ Write it as one sentence: "Activated = posted once in first 7 days"
☐ Build every onboarding step to drive that one action
The rule: one activation event, defined numerically, reviewed quarterly. For most communities it's a first post or a first reply received, not a join or a profile fill. Once defined, your whole onboarding loop has a target instead of a vibe.
Post your activation rate where the team sees it weekly.
Save this for your next launch.
You can't improve "engagement" because it isn't one number. Define your single activation event — the action that predicts a member stays.
☐ List actions new members take in week 1
☐ For each, check 30-day retention of members who did vs didn't
☐ Pick the action with the biggest retention gap — that's your activation event
☐ Write it as one sentence: "Activated = posted once in first 7 days"
☐ Build every onboarding step to drive that one action
The rule: one activation event, defined numerically, reviewed quarterly. For most communities it's a first post or a first reply received, not a join or a profile fill. Once defined, your whole onboarding loop has a target instead of a vibe.
Post your activation rate where the team sees it weekly.
Save this for your next launch.
The Dormant-Member Win-Back Sequence
Lapsed members are cheaper to wake than strangers are to recruit. Build a fixed reactivation cadence triggered by inactivity, not by guilt.
☐ Trigger: 21 days no activity — fires the sequence automatically
☐ Touch 1: "here's what you missed" — 3 best threads, no ask
☐ Touch 2 (day 3): one open question on their original topic interest
☐ Touch 3 (day 7): direct invite to the next ritual with a time
☐ Touch 4 (day 14): one last value drop, then mark them cold
The SOP stops after 4 touches — pestering churns them harder than silence. Personalize Touch 2 using their join-time interest tag. Anyone who replies re-enters the active loop and exits the sequence.
Measure win-back rate: replied ÷ sequence started.
Save this for your next launch.
Lapsed members are cheaper to wake than strangers are to recruit. Build a fixed reactivation cadence triggered by inactivity, not by guilt.
☐ Trigger: 21 days no activity — fires the sequence automatically
☐ Touch 1: "here's what you missed" — 3 best threads, no ask
☐ Touch 2 (day 3): one open question on their original topic interest
☐ Touch 3 (day 7): direct invite to the next ritual with a time
☐ Touch 4 (day 14): one last value drop, then mark them cold
The SOP stops after 4 touches — pestering churns them harder than silence. Personalize Touch 2 using their join-time interest tag. Anyone who replies re-enters the active loop and exits the sequence.
Measure win-back rate: replied ÷ sequence started.
Save this for your next launch.
The High-Conversion Intro Thread Template
A blank "introduce yourself" prompt gets blank results. Structure the intro so it doubles as a matchmaking and segmentation tool.
☐ Field 1: one line on what you do (for tagging)
☐ Field 2: what you're trying to solve right now (for matching)
☐ Field 3: what you can help others with (for ambassador spotting)
☐ Field 4: one non-work fact (for human connection)
☐ Close with: "reply to one person below" (forces a second action)
The last line is the trick — it converts a one-off intro into the member's first real interaction. Store Field 1 answers as interest tags that feed your onboarding and reactivation loops. Pin the template so it's copy-paste for newcomers.
Audit monthly: what percent complete all four fields.
Save this for your next launch.
A blank "introduce yourself" prompt gets blank results. Structure the intro so it doubles as a matchmaking and segmentation tool.
☐ Field 1: one line on what you do (for tagging)
☐ Field 2: what you're trying to solve right now (for matching)
☐ Field 3: what you can help others with (for ambassador spotting)
☐ Field 4: one non-work fact (for human connection)
☐ Close with: "reply to one person below" (forces a second action)
The last line is the trick — it converts a one-off intro into the member's first real interaction. Store Field 1 answers as interest tags that feed your onboarding and reactivation loops. Pin the template so it's copy-paste for newcomers.
Audit monthly: what percent complete all four fields.
Save this for your next launch.
The 5-Type Prompt Bank
Running out of things to post is an inventory problem, not a creativity problem. Build a prompt bank sorted by type so you never face a blank channel.
☐ Low-effort: one-tap polls and this-or-that (drives lurker Rung 2)
☐ Status: "what are you shipping this week?" (recurring identity)
☐ Help-request: "stuck on X, who's solved it?" (drives expertise)
☐ Spotlight: surface a member's win (drives belonging)
☐ Spicy: a defensible hot take in your niche (drives debate)
The SOP: keep 10 ready prompts per type in a doc, rotate so no type repeats two days running. Build the bank once, draw from it daily. A scheduler posting from the bank beats a human improvising at midnight.
Refill the bank when any type drops below 5.
Save this for your next launch.
Running out of things to post is an inventory problem, not a creativity problem. Build a prompt bank sorted by type so you never face a blank channel.
☐ Low-effort: one-tap polls and this-or-that (drives lurker Rung 2)
☐ Status: "what are you shipping this week?" (recurring identity)
☐ Help-request: "stuck on X, who's solved it?" (drives expertise)
☐ Spotlight: surface a member's win (drives belonging)
☐ Spicy: a defensible hot take in your niche (drives debate)
The SOP: keep 10 ready prompts per type in a doc, rotate so no type repeats two days running. Build the bank once, draw from it daily. A scheduler posting from the bank beats a human improvising at midnight.
Refill the bank when any type drops below 5.
Save this for your next launch.
The Community Launch-Day Runbook
Launch day chaos comes from undefined roles, not low effort. Assign every job before doors open.
☐ T-minus 1 day: seed 5 starter threads so day one isn't empty
☐ Hour 0: "greeter" reacts to every intro within 10 minutes
☐ Hour 0: "firefighter" watches for spam and broken links only
☐ Hour 2: pin the rules + the first ritual date
☐ Hour 6: "recap host" posts "who joined today" highlight
☐ Day 1 close: log join count and activation rate as baseline
The rule: one named human per role, no overlap, no "we'll figure it out." An empty community on day one signals dead; the seeded threads and fast greeting prevent that first-impression death. Capture day-one numbers as the baseline you'll measure every loop against.
Save this for your next launch.
Launch day chaos comes from undefined roles, not low effort. Assign every job before doors open.
☐ T-minus 1 day: seed 5 starter threads so day one isn't empty
☐ Hour 0: "greeter" reacts to every intro within 10 minutes
☐ Hour 0: "firefighter" watches for spam and broken links only
☐ Hour 2: pin the rules + the first ritual date
☐ Hour 6: "recap host" posts "who joined today" highlight
☐ Day 1 close: log join count and activation rate as baseline
The rule: one named human per role, no overlap, no "we'll figure it out." An empty community on day one signals dead; the seeded threads and fast greeting prevent that first-impression death. Capture day-one numbers as the baseline you'll measure every loop against.
Save this for your next launch.