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.