# How to Build a Verified Decision-Maker List for Cold Outreach

*How-to — 2026-01-20 — by Mahmoud Zalt*

A practical playbook for building a verified decision-maker list for cold outreach: sources, filters, email verification, and where AI Employees take over.

**Short answer.** Build a verified decision-maker list in four steps: define the buyer (title, company size, region), pull a raw list from Apollo or LinkedIn Sales Navigator, verify emails with a tool like NeverBounce or MillionVerifier, then enrich with a triggering signal (funding, hire, tech stack). If you do not want to wire this yourself, a Sistava AI Sales Employee runs the whole loop (source, verify, enrich, send, follow up) inside one workspace.

## What does verified actually mean in a decision-maker list?

Verified is a word every list vendor abuses, so it pays to define it before you buy anything. A genuinely verified decision-maker record has three layers checked, not one. First, the person exists in the role today: title scraped within the last 30 days, ideally cross-checked against LinkedIn and the company website. Second, the email actually delivers: an SMTP check confirms the mailbox accepts mail, the domain has valid MX records, and the address is not catch-all, role-based, or on a known disposable list. Third, the company matches your ICP at this moment: headcount band, country, industry code, and at least one freshness signal like a funding round, a new hire announcement, or a website change. A list that nails one layer and skips the other two will quietly burn your sender reputation inside a week. The bounce numbers you see quoted on Twitter (under 2 percent on a clean list, over 8 percent on a scraped one) come from this gap, not from any clever subject line.

## At a Glance

- **<2%** Bounce rate on a properly verified list
- **>8%** Bounce rate on a raw scraped list
- **30 days** Max staleness before re-verification
- **3 layers** Person, email, company match

## Where do you actually find decision-maker contacts?

Almost every credible list starts in one of five places, and each has an honest tradeoff. Apollo and Clay are the workhorses for B2B titles at small to mid companies: deep filters, large database, fair monthly pricing, but freshness varies by industry. LinkedIn Sales Navigator is the gold standard for senior titles and recent role changes, but exports require care because LinkedIn does not give you the email directly. ZoomInfo and Cognism cover enterprise contacts more reliably and surface direct dials, at enterprise pricing. Specialized scrapers (PhantomBuster, Captain Data, Clay enrichment chains) help when your ICP sits in a niche source like Crunchbase, Product Hunt, or a specific job board. Manual research still wins on the top 50 accounts where one wrong name kills the deal. The right move is rarely picking one. You build the raw list in two sources, dedupe across them, and only then run the verification step.

## Benefits

### Apollo or Clay

Best for SMB and mid-market B2B titles. Big database, deep filters, fair monthly cost.

### LinkedIn Sales Navigator

Best signal for senior titles and recent role changes. Pair with an enrichment tool for emails.

### ZoomInfo or Cognism

Strongest for enterprise contacts and direct dials. Pricing only justifies for enterprise ACVs.

### Niche scrapers

PhantomBuster, Captain Data, Clay chains for sources like Crunchbase, Product Hunt, job boards.

### Manual research

Reserved for your top 50 accounts where one wrong name kills the conversation.

## What are the exact steps to build the list?

The shortest path that still hits a 2 percent bounce target has five steps, and skipping any of them costs deliverability later. Most teams I work with try to compress steps two and four (filter and verify) and pay for it inside a week with replies dropping and Google moving them to Promotions. The order below is the one I use on my own outbound and the one the Sistava AI Sales Employee follows internally before it sends a single message. Treat it as a checklist, not a suggestion. If your CRM is messy, do the first pass on a clean spreadsheet so you can see every step. The goal is not the longest list you can buy, it is the shortest list you can trust enough to email this week without warming up a new domain in panic.

### Five steps from blank sheet to send-ready list

1. **1. Lock the ICP** — Write down the title, seniority, company size band, country, industry, and one disqualifier. A sloppy ICP makes every later step waste money.
2. **2. Pull from two sources** — Export a raw list from Apollo or Clay plus LinkedIn Sales Navigator. Dedupe on email then on company domain. Expect 20 to 40 percent overlap.
3. **3. Verify emails** — Run the deduped list through NeverBounce, MillionVerifier, or ZeroBounce. Drop catch-all, role-based, and unknown results. Keep only valid.
4. **4. Enrich with one signal** — Add one freshness signal per record: funding, hire, tech stack, traffic change. This is what makes a cold message land as relevant, not random.
5. **5. Tier and load into the sender** — Split into Tier A (top 50, manual personalization) and Tier B (volume, templated). Load each into the right sending tool with different daily caps.

Step three is where most founders quietly cheat themselves. Verification tools cost money per check, the rates feel painful in bulk, and there is always a temptation to skip the catch-all bucket because it looks like leaving leads on the table. Resist. A catch-all domain accepts every address you throw at it without telling you the mailbox is real, which means your bounce metric stays clean while your reply rate silently dies. Treat catch-all as unknown and either drop it or send a manual one-to-one message from a personal mailbox where the cost of a soft bounce is zero. That single discipline separates a list that ships replies from a list that ships unsubscribes.

Most solo founders read that five-step process and realize they will not actually do it weekly. The math is honest: a clean list takes four to six hours per 500 records, every two weeks, every campaign. That is half a working day on the lowest-leverage piece of outbound, before a single message is written. The next question is whether you wire the steps yourself, or hand them to something that runs the loop while you sleep. Both work. They cost differently.

## How do AI Employees change the list-building loop?

An AI Sales Employee is the cleanest way to compress the five-step loop into a recurring job that does not need your time once configured. The Sistava AI Sales Employee, for example, pulls from an Apollo or Clay key, runs deduplication and verification inside the workspace, enriches with a chosen signal source (funding from Crunchbase, hires from LinkedIn, traffic from SimilarWeb), then hands the verified list straight to the same employee for sending and follow-up. Lindy and CrewAI can be wired to do similar work if you are comfortable with builder time, and n8n with a verification node is the bootstrapper path. The difference with an AI Employee approach is that one role owns the whole loop, so the list, the message, and the follow-up share memory. You do not get a clean handoff bug between tools because there is no handoff. The honest tradeoff is configurability: you trade some control for not having to maintain the pipeline yourself.

## Benefits

### Source and dedupe

Pulls from Apollo, Clay, or LinkedIn via API key, deduplicates against your CRM and previous campaigns.

### Verify emails

Runs every address through a verification provider before any send touches the list.

### Enrich with signal

Adds funding, hire, traffic, or tech stack signals so personalization has something honest to anchor on.

### Send and follow up

Same employee owns the sequence, so verification state, sending state, and reply state share one memory.

## What kills deliverability even on a verified list?

A verified list is necessary but not sufficient. The four things that still kill deliverability after the list is clean are sender warmup, domain reputation, daily volume, and copy that pattern-matches as spam. A brand-new domain sending 200 messages on day one will land in spam regardless of how clean the addresses are. A reputable old domain sending the same volume with a copy that mentions guarantee or risk-free will land in Promotions. SPF, DKIM, and DMARC need to be set up before the first send, not after the first complaint. Daily caps matter more than total volume: 30 to 50 per mailbox per day on a warmed domain is the conservative band most senders settle into. And the copy needs to feel like a one-to-one note from a human, which is exactly where most AI-generated sequences quietly fail because they all converge on the same three opening templates. The list got you to the door. The four items above decide whether it opens.

## Frequently asked questions

## FAQ

### How much does it cost to build a verified decision-maker list?

For 500 verified records, expect roughly $50 to $80 per month on data subscriptions (Apollo or Clay starter) plus $5 to $15 for verification credits on a tool like NeverBounce. Niche enrichment adds $20 to $50 depending on source. Doing it weekly with manual labor costs more in time than the tools cost in cash.

### Is Apollo enough on its own, or do I need a second source?

Apollo is enough for SMB and mid-market B2B targets if you accept some freshness drift. For senior titles, recent role changes, or any niche outside the core ICP, pair Apollo with LinkedIn Sales Navigator and dedupe. The overlap will surprise you and the gaps reveal where your real prospects live.

### Can I skip the email verification step if the source claims it is verified?

No. Apollo, Clay, and ZoomInfo all surface verified emails, but verified there means the address parsed cleanly at some point in the past. Run a fresh verification on the day you send. The cost is a few cents per record and the saved bounce rate alone justifies it on the first campaign.

### How do I avoid scraping LinkedIn against terms of service?

Use Sales Navigator with an enrichment tool that resolves emails through legitimate sources (Apollo, Clay, Cognism) rather than scraping LinkedIn directly. The lookup happens against company domains and public databases, not the LinkedIn API. PhantomBuster and similar scrapers operate in a gray zone that is fine for small volume but risky at scale.

### What does an AI Sales Employee do that I cannot do with Apollo plus a sender like Lemlist?

Nothing magical. The difference is one role owns source, verification, enrichment, sending, and follow-up with shared memory, so you do not lose context between tools. If you have the time to maintain the pipeline yourself, Apollo plus Lemlist is a fine combination. If you do not, an AI Employee removes the weekly maintenance cost.

Once the list is verified and loaded, the work shifts to running the actual sequence: copy variants, follow-up cadence, reply handling, calendar booking. That is its own discipline and a different article. The piece I would read next walks through the end-to-end cold outreach loop assuming the list step is done, so you can see how the verified records you just built feed the rest of the machine without you babysitting every step.

The honest frame for list building is that the work is unglamorous but cheap to get right and expensive to get wrong. Five steps, two data sources, one verification pass, one enrichment signal, then tier and load. Doing this once teaches you more about your ICP than any positioning workshop, because every wrong record forces a real definition of who you are not selling to. Whether you wire the pipeline yourself with Apollo plus a verification tool plus a sender, or hand the whole loop to a Sistava AI Sales Employee that owns it inside one workspace, the underlying discipline is the same: never send to a list you have not verified this week, never trust a single source, and never let a tool tell you a catch-all is a real mailbox. Hold those three lines and your reply rate stops being a mystery.

**Tags:** cold-outreach, decision-maker-list, lead-list-building, email-verification, ai-sales-employee, apollo-alternative, b2b-prospecting