Outreach based on Slack membership

# Turn a community's member list into a campaign

You have access to web search and an email-enrichment tool, plus
browser access to the community itself (a Slack workspace, a forum, a
user group — anywhere members post in their own words). Run this
against **[the community you're a member of, and the segment it maps
to]**.


## 1. Collect the member list, and expect it to disappoint

Membership lists in chat tools are usually virtualized — only the
visible rows exist in the page at any moment, and the rest render in as
you scroll. **A script that sets scroll position programmatically often
scrolls a list that never actually redraws**, especially in a
browser-automated background tab, and silently re-reads the same
handful of rows forever. Clicks and screenshots keep working, which
makes the failure easy to miss. A real scroll event (a wheel event, not
a position jump) is what forces the list to repaint — loop: scroll,
read what's rendered, repeat.

Expect the raw roster to be thin: most member profiles carry a handle,
not a full name, and no company or title at all. That's expected — the
next step is where the real signal comes from.

## 2. Gather members' own introductions first

Most communities like this have an #introduction Slack channel, or a
thread serving the same purpose, where members state their own name, company, and what they do in plain prose.
That text is both the resolution key and the personalization source —
a bare handle is nearly unfindable, but "hi, I'm [name] from [company],
I do [role]" resolves in seconds and gives you a real detail to write
from.

Work the #introduction channel first, in full, before touching the rest of the
roster — it's a small fraction of the community but by far the highest
quality. Then work the rest of the roster as a second, higher-volume
pass with name-only search; it resolves far fewer people per hour, but
meaningfully grows the list beyond the #introduction channel alone.

## 3. Match each member to a profile — reward corroboration, not confirmation

Search each name (with their stated company, where you have one) for a
professional profile match. For roster-only people with no stated
company, the search result's own headline (name, role, employer) often
becomes the entire personalization source — capture it.

Accept a match only when something about it actually corroborates the
person — matching company, matching role, matching context — not just a
name that happens to match. Where two plausible profiles exist for the
same name and neither one corroborates, treat it as unresolved rather
than guessing. **Prefer no match to a weak one.**

## 4. Find emails, reject mismatches

Enrich the resolved profile for a work email. Ask for email only, not
phone, unless you specifically need it — phone lookups typically cost
far more credits per hit.

Enrichment tools return the person's **current** employer's domain,
which isn't always the company they introduced themselves as. Someone
who described a side project or a new venture in the community may
still get an email at their day job. **Reject any email whose domain
doesn't match what the person actually said about themselves** — a
meaningful share of matches fail this check, and sending to the wrong
address at the wrong company is worse than not sending at all.

## 5. Write openers for each role group's real problem

Group resolved people by role type — founders, in-house operators,
agencies/consultants, investors are common splits — since they don't
share a problem and a single angle won't land for all of them. Agencies
in particular are often a partnership opportunity rather than a direct
buyer; treat that as a different message, not a smaller version of the
same one.

Write two short sentences per opener, using the person's own words from
step 2 or 3 wherever you have them. Check each one with a simple test:
swap in a different person from the same segment — if the line still
reads true, it isn't personalization yet, it's a segment description.

**One hard constraint on the copy itself: never reference the community
the list came from, and never assert what tool the person uses based on
their membership in it.** A fact about your own product is fine to
state; an inference about their behavior, drawn only from where you
found them, isn't — there's no innocent way to know it, and naming the
source erodes trust in one line.

## 6. Stage the campaign for a person to launch

Before creating anything, check what's already sending — list live
campaigns and their enrolled people, and skip anyone already enrolled
elsewhere targeting a similar audience rather than adding them again.

Load each segment into its own track with its own copy. Verify the
personalization landed — spot-check a few loaded rows against what you
intended to send. Then stop: stage everything for review, and never
call a send or launch action. A person reviews drafts by segment and
launches from there.

## Output

Report: how many members extracted from the roster, how many resolved
through the #introduction channel vs. the wider roster, how many passed
identity resolution, how many emails were rejected for not corroborating
the person, the segment breakdown, and the campaign staged for review.