Field Guide · Business Development · By Emre Ozgurler · July 2026

Run outbound from a conversation.

Apollo.io's native connector puts its 240M+ contact database, enrichment engine, and sequences directly inside Claude. This guide is the full loop — from ICP to enrolled sequence to weekly reporting — without leaving the chat.

Find Enrich Personalize Sequence Analyze
01 · Setup — ten minutes, once

Connect Apollo to Claude

Apollo ships an official connector in Claude's directory, built on its own MCP server. Every action you take in chat is recorded back in Apollo — searches, enrichments, sequence enrollments all sync to your account.

1

Add the connector

In Claude, open Settings → Connectors, search for Apollo.io, and click add. Authorize via OAuth with your Apollo login — no API key needed. Each teammate connects their own account; access mirrors their Apollo permissions.

2

Set per-action permissions

Click Configure next to Apollo.io and review each action. Recommended: leave searches and reads on auto-allow, but set sequence enrollment and bulk enrichment to ask first — enrichment consumes Apollo credits, and enrollment can start sending real emails.

3

Give Claude your ICP once

Create a Claude Project called Outbound and put your ideal customer profile, value props per vertical, sender mailboxes, and tone guidelines in the project instructions. Every prospecting chat inherits that context — no re-explaining who you sell to.

4

Power-user path (optional)

Apollo also publishes a plugin for Claude Code and Cowork that bundles its APIs into slash-command workflows — useful for heavy batch runs and analytics pulls. Start with the connector; graduate when volume demands it.

02 · The core loop

Five stops from ICP to inbox

This is a real working cadence for a B2B services team (examples use managed IT services — swap in your own vertical). Each stop is one prompt you can paste and adapt.

A

Find — build the list in plain language

Goal · 25–50 net-new accounts that actually match

Skip the filter UI. Describe the segment the way you'd describe it to a colleague — industry codes, headcount, geography, tech signals — and let Claude run the Apollo search.

Search Apollo for companies in the Portland metro area, 10–100 employees, in healthcare clinics, law firms, and RIAs (use NAICS where helpful). Exclude companies already in my saved accounts. Return the top 25 with domain, headcount, and why they matched.
B

Enrich — verified emails, right titles

Goal · decision-makers with deliverable contact data

Enrichment is where credits are spent, so batch deliberately — ten at a time keeps costs visible and lets you sanity-check quality before committing to the whole list.

From that list, find the owner, practice manager, or IT decision-maker at each company. Enrich the first batch of 10 with verified emails and LinkedIn URLs, show me the results, and wait for my go-ahead before enriching the rest.
C

Personalize — first lines that aren't templates

Goal · one specific, human sentence per prospect

This is where Claude out-earns any merge tag. Pair Apollo's firmographic data with web research for openers referencing something real — a hiring push, a compliance deadline, a new location.

For each enriched contact, check Apollo's data and search the web for one recent, specific fact about their company (new office, job postings, news). Draft a one-sentence personalized opener per contact tying that fact to a pain we solve. Flag any where you couldn't find anything specific.
D

Sequence — build the cadence, then enroll

Goal · a mixed-step sequence, contacts loaded, right sender

Claude can create the sequence itself — emails, call tasks, LinkedIn touches — and enroll contacts under a specific sender mailbox. Always review the full copy before anything goes live.

Create an Apollo sequence called "Clinics — Q3 Portland": Day 1 email (use the personalized openers), Day 3 call task, Day 6 follow-up email with a customer proof point, Day 10 LinkedIn touch, Day 14 breakup email. Show me every email draft for approval. Then enroll the approved contacts using [your sender mailbox].
E

Analyze — let the data pick next week's plays

Goal · know what's working before you scale it

Apollo's analytics are queryable in plain language: opens, replies, meetings by sequence, by step, by vertical. Ask for the comparison, then feed the winner back into stop A.

Pull performance for my active sequences over the last 30 days: delivery, open, reply, and meeting rates, broken down by sequence and by step. Which vertical and which email step are converting best? Give me three concrete changes for next week.
03 · Prompt library

Plays for the rest of the week

Signals

Job-posting triggers

Which companies on my target list have open job postings for IT, operations, or compliance roles right now? Those are my warm-signal accounts — prioritize them.
Hygiene

CRM cleanup

Find contacts in my Apollo account with missing titles or bounced emails. Re-enrich the fixable ones and list the rest for removal.
Tasks

Morning task triage

Show my Apollo tasks due today. For each call task, give me a 3-line brief: who they are, which sequence they're in, and what the last touch said.
Replies

Response drafting

A prospect replied "we already have an IT guy." Draft two responses: one warm and curious, one that offers a free second-opinion audit. Keep both under 80 words.
Lookalikes

Clone your best customers

Here are my five best customers: [domains]. Find 20 lookalike companies in Apollo — same size band, industry, and region — that aren't in my account yet.
Reporting

Friday pipeline note

Summarize this week's outbound: new contacts added, emails sent, replies, meetings booked. Write it as a 5-line update I can post to the team channel.
04 · Guardrails

Automate the work, not the judgment

SEND

Nothing goes out unreviewed. Sequence enrollment can trigger real emails immediately depending on your sequence settings. Make "show me every draft first" part of every enrollment prompt, and keep enrollment permissions on ask-first.

CREDITS

Enrichment spends credits from your Apollo plan — typically one per person. Batch in tens, check quality, then continue. Ask Claude for your credit usage stats monthly.

DELIVER

Protect your domains. Rotate sender mailboxes, keep per-mailbox daily volume conservative, and warm up new inboxes before loading them into a sequence. Great copy from a burned domain still lands in spam.

TIMING

The connector works only while you're chatting — there are no background triggers. It won't ping you when a prospect replies at 9pm. Build the check into your routine (see the weekly rhythm below) instead of assuming it's watching.

LAW

Stay compliant. CAN-SPAM, GDPR, and local rules still apply to AI-assisted outreach: real sender identity, working unsubscribe, and honor opt-outs everywhere. Automation scales your reach — and your liability.

05 · Operating rhythm

A week of outbound, one chat a day

Fifteen to thirty minutes each morning keeps the machine fed. Same Project, so context carries over.

Monday
Build. Run the Find prompt for one vertical. Enrich the first batch. Queue the rest for approval.
Tuesday
Personalize + launch. Generate openers, review drafts, enroll into the sequence.
Wednesday
Work the tasks. Morning task triage — call briefs for everything due, reply drafts for anyone who wrote back.
Thursday
Signals. Check job postings and news across the target list. Move warm-signal accounts to the front of next week's build.
Friday
Report + refine. Pull the 30-day analytics, write the team update, and pick one change to test next week.
EMRE OZGURLER · PORTLAND, OR · © 2026