How We Run the Entire Outbound Motion From Slack

If you run outbound today, you know the real work is not writing the email. It is the assembly. You pull a list in one tool, enrich it in another, check it against your definition of a good account in a doc somewhere, write the copy in a fourth place, then load it into a sender. Every campaign rebuilds that pipeline from scratch. We moved the whole thing into Slack, and the difference is not speed alone. It is that the motion finally runs against our actual definition of a good account instead of a guess.

The problem: outbound is four tools in a trench coat

Outbound looks like one job and runs like four. Here is the version most teams live:

Someone opens a prospecting tool and builds a search. They export the list. They push it through an enrichment tool to fill in the emails and titles the first tool missed. They open the doc that describes the ideal customer and hand-check the list against it, or more honestly, they skip that step because it is tedious. They write the copy in a separate editor, trying to remember which case study lands with this segment. Then they load everything into a sending tool, set up the sequence, and hit go.

Each handoff is a place to lose fidelity. The list drifts from the ICP because checking it by hand is slow. The copy drifts into generic because pulling the right proof point takes effort. And none of it is reusable: the next campaign starts the same pipeline over again. The marketer is not doing marketing. They are doing data entry between five browser tabs.

What a better outbound loop needs

Before naming any tool, here is what the motion actually requires to be good:

• Grounded targeting. The list should be built against a written, current definition of a good account, not a rep's gut. If your ICP is a real artifact, the targeting can be checked against it every time.
• Real enrichment. Names are not enough. You need titles, verified emails, and company signals, pulled from more than one source so coverage holds up.
• Personalization from your own material. Good outbound sounds like your company had a specific reason to reach out. That means the copy has to draw on your real stories, positioning, and wording, not a template with a variable in it.
• One place to send. One-to-one notes and broadcast campaigns should run from the same motion, so you are not rebuilding the pipeline depending on volume.
• A workflow you keep. The whole thing should be teachable once and repeatable, so campaign number ten is not as manual as campaign number one.

The tools to do each piece already exist. The friction is that they do not talk to each other, and a person is the integration layer.

How we run it in Slack

We made the integration layer an AI coworker. Mio lives in Slack, connects to the tools our GTM team already uses, and runs the motion end to end. You describe the campaign in a channel and Mio assembles it.

Find and enrich the targets

Mio sources prospects and enriches them through Apollo and RocketReach, so the list arrives with verified titles and emails instead of half-filled rows.

@Mio find heads of RevOps and GTM leaders at Series A-B B2B SaaS companies in North America, enrich them through Apollo and RocketReach, and post the count and a sample of 10 in #outbound

Build the list against our real ICP

Our ideal customer profile is not folklore. It lives in Git and Notion, and Mio builds the list against that definition. The targeting is grounded in what we have actually written down as a good account.

@Mio filter that list against our ICP in Notion, drop anyone outside it, and tell me why each excluded account didn't fit

Draft messages in our own voice

Mio drafts the personalized outreach by pulling from our own stories and positioning, not a generic template. Personalization means a specific reason to reach out, written the way we actually write.

@Mio draft a first-touch email for each account using our positioning and the customer story that fits their segment. Show me the drafts before anything sends.

Send through Resend, one-to-one or broadcast

Mio sends through Resend. The same motion handles a handful of one-to-one notes and a full broadcast campaign, so volume does not change the workflow.

@Mio send the approved drafts through Resend as a broadcast to this segment, and hold the enterprise accounts for one-to-one sends I'll review individually

Read the results and adapt the next campaign

Sending is not the end of the motion. Mio reads the campaign results back, opens, replies, and conversions, and interprets them to propose who and how we should target next: which segment replied, which message landed, which accounts to drop or double down on. The proposals are suggestions we approve, not silent changes to the next send.

@Mio look at the reply and conversion rates from that Resend campaign by segment, tell me which ICP slice is responding, and propose the next list and message angle. Wait for my sign-off before building it.

The whole thing happens in one channel. Nobody exports a CSV. Nobody tabs between five tools. You describe the campaign and watch it get built.

What changes when the motion is one conversation

Two things get better, and one of them matters more than speed.

The obvious win is time. The four-tool relay collapses into a thread, so a campaign that took a morning of assembly takes minutes of describing and reviewing.

The bigger win is fidelity. Because the list is built against the ICP we keep in Git and Notion, the targeting reflects our actual definition of a good account instead of drifting toward whoever was easy to find. Because the copy pulls from our own stories, the personalization is specific instead of a first-name variable. The parts of outbound that usually erode under time pressure hold, because the coworker doing the assembly does not get bored of checking the ICP or finding the right proof point.

The real shift: you teach the workflow once

Here is what makes this more than a faster tool. You teach Mio the outbound workflow one time, and after that it runs almost on autopilot. It is a coworker you hand a campaign to, working in the background, not a machine you drive click by click.

That is the part worth sitting with. A 24/7 agent that sources, enriches, writes, and sends used to be something only a well-resourced team in San Francisco could stand up, with engineers wiring the tools together. Teaching a workflow once in Slack and having it run puts that same capability in the hands of a two-person GTM team. The advantage stops being who can afford to build the pipeline and starts being who has the sharpest ICP and the best stories to tell.

If you already run outbound, you have all the raw material. The change is moving the assembly into the place your team already talks, and teaching it once.

For more on running go-to-market work this way, see the best Slack AI agents and the AI RevOps Manager.

Try Mio free at app.mio.xyz.

FAQ