Loading tutorials…
Loading tutorials…
Apollo has the cheapest entry into B2B sales intelligence, but the default account configuration will silently torch your domain reputation. This walks the exact setup order that keeps your inbox warm and your credits efficient.
Who this is forFounders, BDRs, and demand-gen leads spinning up Apollo for outbound. If you have already connected an inbox and started sequences without warming, this tutorial is corrective — you may need tutorials 4 and 5 first.
What you'll need
Step 1
Sign up at apollo.io with your business email → name the workspace by company (not your name) → choose the right plan tier for your volume.
Go to apollo.io → "Sign up free." Use a business email on your real company domain. Gmail/Outlook free addresses get throttled on data exports and have weaker enrichment.
On the workspace setup screen, name the workspace by company ("Acme — Outbound") not by your name. Apollo workspaces cannot be renamed without contacting support, and personal-name workspaces become awkward once you add teammates.
Pick a plan: Free (limited credits, no sequences), Basic ($59/seat/mo — has sequences but capped exports), Professional ($99/seat/mo — most outbound teams live here), Organization ($149+/seat/mo — adds Plays, dialer minutes, and advanced analytics).
Most B2B teams should start on Professional. Basic looks cheap until you hit the email credit ceiling in week 2.
Skip the "invite teammates" prompt for now. Add users after the workspace is configured — adding them before SPF/DKIM/users-roles are set means they walk into a misconfigured account.
Step 2
Never send Apollo sequences from your primary @company.com domain. Buy a lookalike (try-acme.com, getacme.com, acme-team.com) for outbound only.
Cold outbound at Apollo's volumes (50-500 sends/day per inbox) damages domain reputation. If you do it from your primary @company.com, your transactional and team email start landing in spam.
Buy 1-3 lookalike domains specifically for outbound: try-yourcompany.com, get-yourcompany.com, yourcompany-team.com. Cost: $10-15/domain/year. Total: $30-45 for the year — cheap insurance.
Point each lookalike's MX records to a separate mailbox provider (Google Workspace or Microsoft 365). $6-12/inbox/month. Each new inbox gives you ~50 safe sends/day after warm-up.
Forward inbound replies from the lookalike inbox to your primary inbox so you do not miss responses. Use the mailbox provider's native forwarding — not Apollo's reply sync.
Critical: NEVER point lookalike MX records to your primary domain. Cross-contamination of DKIM signatures will pull your primary into spam triggers.
Step 3
Apollo → Settings → Email Accounts → Connect Email. Always use OAuth (Google/Microsoft direct connection), never SMTP/IMAP, when available.
Open Apollo → top right gear icon → "Email Accounts" → "Connect Email."
Choose your provider: Google (Workspace or Gmail), Microsoft (365 or Outlook), or Custom (SMTP/IMAP). Always pick the OAuth option for Google or Microsoft — SMTP is the fallback for niche providers.
OAuth grants Apollo permission to read/send via the official API. Better deliverability, faster sync, no app password headaches.
Run through the OAuth consent screen and approve. Apollo will show "Connected" within 30 seconds.
In the email account row, set: Daily sending limit (start at 25-30/day per fresh inbox, never default to 200), Reply tracking ON, Out-of-office detection ON, Bounce-to-blocklist ON.
Repeat for every inbox you want to send from. Apollo treats each inbox as a separate sender — Professional plan allows 5 connected inboxes per seat.
Step 4
Add SPF (TXT), DKIM (CNAME or TXT, provided by your mailbox provider), and DMARC (TXT, start at p=none) to the SENDING DOMAIN, not the primary.
SPF: in your DNS provider, add a TXT record at the root: v=spf1 include:_spf.google.com ~all (for Google Workspace) or include:spf.protection.outlook.com (for Microsoft 365). If you already have SPF, ADD the include — do not stack multiple SPF records.
DKIM: Google Workspace → Admin → Apps → Google Workspace → Gmail → Authenticate email → Generate key → copy the CNAME or TXT record into your DNS. Microsoft 365: Defender → Email & collab → Policies → DKIM → Enable for domain → copy CNAMEs.
DMARC: add a TXT record at _dmarc.yourdomain.com → v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com. Start at p=none for the first 30 days to monitor without blocking. Move to p=quarantine after 30 days of clean reports.
Validate at mxtoolbox.com or dmarc.postmarkapp.com. All three (SPF, DKIM, DMARC) must show "Pass" before sending a single cold email.
Without these, modern Gmail and Outlook will reject 30-60% of your sends or land them in spam invisibly. Apollo will not warn you.
Step 5
Apollo → Settings → Users → Invite. Use Member role for BDRs; Admin only for ops. Custom roles available on Organization plan.
Open Apollo → Settings → "Users & Permissions" → "Invite User."
Apollo roles: Admin (full control + billing), Manager (manage users, sequences, sees all data), Member (manage own sequences and lists only).
For BDR teams: each rep is a Member, the SDR manager is Manager, ops/founder is Admin. Never give every rep Admin — they can change billing or delete sequences others depend on.
Set up team data sharing: Settings → "Data Settings" → "Sharing Permissions." Decide whether prospect lists are workspace-wide (recommended for SMB) or rep-private (recommended for enterprise to prevent prospecting collision).
For larger teams (10+ reps), enable Apollo's assignment rules: prevent two reps from sequencing the same contact within 60 days.
Step 6
Apollo → Settings → Plans & Billing. Apollo charges per email credit (export) and mobile credit (phone reveal). Set monthly caps before launching.
Open Apollo → top right gear icon → "Plans & Billing."
Understand credits: Email credits are consumed when you export a contact (1 credit per email reveal). Mobile credits are consumed when you reveal a phone number (typically 5-10x more expensive per credit).
Set monthly credit caps. Default is unlimited — at $0.50-1.00 per email credit at scale, this is how teams blow their Apollo budget by 5x in month one.
Apollo offers credit rollover on annual plans but not monthly. If you are unsure of volume, start month-to-month, measure 30-day usage, then switch to annual for the discount.
For invoicing (over $5K/year commitment): contact Apollo sales — invoicing is not self-service. Approval takes 5-10 business days.
Set a backup payment method. Apollo pauses all sequences if the primary card declines — losing 3-5 days of pipeline.
Step 7
Before launching real sequences: send a 5-contact test sequence to your own seed list (test inboxes you control across Gmail, Outlook, Yahoo). Verify primary inbox delivery.
Create a seed list of 5-10 test inboxes you control: 2-3 Gmail, 2-3 Outlook/Hotmail, 1-2 Yahoo, 1 corporate Gmail Workspace inbox.
In Apollo → Sequences → "New Sequence" → add a 1-step template with a real cold-style email.
Add your seed list as the audience. Launch.
Check each test inbox 5-10 minutes after delivery. Did the email land in Primary/Inbox, Promotions, or Spam? Where it lands at test time is roughly where it will land for real prospects.
If anything lands in Spam: stop. Do not launch real sequences. Common fixes: missing DKIM (check at mxtoolbox), aggressive subject line, sender display name mismatch, missing physical address in footer.
Run this test every time you add a new sending domain or inbox. Skipping the test is how teams discover deliverability problems 2 weeks and 5,000 wasted sends later.
Common mistakes
Sending from your primary @company.com domain
What goes wrong: Cold outbound at Apollo volumes burns domain reputation within 30 days. Transactional emails (receipts, password resets, team email) start landing in spam. Recovery takes 60-90 days and is not always successful. Lost revenue from missed transactional emails alone is typically $5K-50K depending on company size.
How to avoid: Buy a lookalike domain ($10-15/year) before the first send. Point it to a dedicated sending mailbox. Forward replies to your primary. NEVER mix.
Skipping SPF, DKIM, or DMARC setup
What goes wrong: Modern Gmail and Microsoft 365 require all three for cold sender domains as of 2024. Without them, 30-60% of your sends are rejected or land in spam silently — Apollo's dashboard still shows them as 'delivered.' You spend $500-2,000 in Apollo credits delivering to nowhere.
How to avoid: Configure SPF, DKIM, and DMARC on the sending domain before connecting to Apollo. Validate at mxtoolbox.com. All three must pass.
Default 200/day sending limit on a fresh inbox
What goes wrong: A brand new inbox sending 200 cold emails on day 1 triggers Gmail's spam-burst detection. The inbox is silently blacklisted within 48-72 hours. Recovery requires a 30-day cooldown and re-warming. The $300-500/mo inbox spend is wasted for the month.
How to avoid: Start at 25/day per fresh inbox. Ramp by 10/day per week. A fresh inbox reaches safe 50-100/day volume only after 6-8 weeks of warm-up (see tutorial 4).
Stacking multiple SPF records
What goes wrong: SPF spec allows ONE root TXT record. Adding a second (Google + your CRM + SendGrid as separate records) breaks all three. Email is rejected. Apollo shows delivered, recipients see nothing. Wasted spend $200-1,000/month until detected.
How to avoid: Combine all includes into ONE SPF record: v=spf1 include:_spf.google.com include:spf.salesforce.com include:sendgrid.net ~all
Personal-name workspace that can never be renamed
What goes wrong: Workspace named "John Smith — Sales" becomes a problem when John leaves or when teammates join. Apollo does not allow workspace renaming without a support ticket (which often gets denied). Re-creating the workspace means losing every sequence, list, and analytic.
How to avoid: Name the workspace by company at signup ("Acme — Outbound"). Verify before clicking continue.
No monthly credit cap
What goes wrong: A 5-rep team with no cap can burn $3K-8K in email credits in month 1 — typically 3-5x what they budgeted. The founder discovers it on the next credit card statement. Pricing pages do not surface this risk.
How to avoid: Set a monthly credit cap before launching real prospecting. Start conservatively (10K credits/month for a 3-rep team), measure actual usage, then adjust.
Recap
Done — what's next
How to set up Apollo filters and personas for high-precision prospecting
Read the next tutorial
Hand it off
Apollo setup looks straightforward in the UI, but the configuration traps (sending domain, daily limits, SPF stacking) compound silently. A vetted demand generation specialist will set up Apollo, configure deliverability, warm the inbox, and validate the first sequence in 4-6 hours. From $14-16/hr — most ongoing engagements land between $800-2,000/mo depending on volume.
See specialist rates
Practically no. Free tier is limited to 60 email credits/month and does not include sequences. It is useful only for one-off lookups. For real outbound you need Professional ($99/seat/mo) minimum.
It is not overkill — it is the single most common reason Apollo accounts succeed or fail. Cold outbound damages sender reputation. Doing it from your primary domain damages your business's ability to send transactional and team email. $30-45/year for lookalike domains is the cheapest insurance in your stack.
After warm-up: 5-10 inboxes at 50-100 safe sends/day each. With a 6-8 week warm-up window. Total cost: ~$30-100/month in mailbox provider fees plus the lookalike domain. Starting cold and trying to hit 500/day in week 1 is a domain-destruction event.
Apollo is the all-in-one cheaper option (data + sequences + dialer in one tool, $99/seat/mo). ZoomInfo is enterprise-grade data accuracy with no native sequences ($15K-50K/year minimum). Full breakdown in tutorial 9 of this series.
No. Email credits are consumed when you EXPORT a contact (reveal the email address), not when you send. Sending is unlimited — bounded only by your connected inbox limits. This is why daily sending limits and warm-up matter more than credit caps.
Apollo.io
Apollo's database is 275M+ contacts — meaningless without precision filters. This walks the persona builder, Boolean title logic, and the signal filters that separate qualified prospects from credit drain.
Apollo.io
Sequences are where Apollo earns its $99/seat. They are also where most operators destroy their sender reputation. This walks the right step structure, cadence, personalization layer, and reply handling that books meetings without burning inboxes.
Apollo.io
Warm-up is the boring 6-8 weeks that determines whether your Apollo investment pays back. Skip it and you torch the inbox in week 2. This walks the exact ramp schedule, the tools, and the signals that tell you the inbox is ready for real sends.
Apollo.io
Apollo's send infrastructure is fine. Your deliverability problems are 95% on your end — DNS, content, sending patterns, and reputation. This walks the full deliverability stack: authentication, monitoring, content rules, and recovery.
Apollo.io
DIY Apollo is a fine idea — until it isn't. This is the honest framework: when the cost of self-managing exceeds the cost of hiring, and how to tell which side you're on.