A verified lead list is a set of prospects that fit your ideal client profile, where every email address has been checked for deliverability and carries a status before anything sends. Building one means filtering search results, checking contacts before pulling their details, refusing to guess unknown fields and verifying again right before the campaign starts. Done well, it is the cheapest deliverability protection an agency has.
Nerdy Joe is owned by Agency Growth Partners (AGP), so this is our own system and we are not neutral about it. This article covers the list stage inside Artemis, AGP's growth engineering system, as one step in the AGP growth machine, and gives you a checklist that works with any tool.
Where the list stage sits
The list stage sits between data and sending. Our guide to B2B contact data for agency outbound covers how an ideal client profile becomes a ranked, enriched search. This stage turns those search results into a list you can safely send to.
The difference matters. A search result is a set of people who might fit. A send-ready list is a set of people who fit, who can be reached at a verified address, and who are not on any list you should never email.
AGP's rule here is simple: contacts are enriched and verified before anything sends, and every address is verified before it is sent to.
What "verified" should mean
"Verified" gets used loosely. For an outbound list, it should mean five specific things.
| Requirement | What it means | Why it matters |
|---|---|---|
| Deliverability status on every email | Each address carries a status, for example verified | You can filter out risky addresses before sending |
| Checked before reveal | You can check a contact before revealing its details | You only pull the addresses you actually need |
| Nulls, not guesses | Unknown fields come back empty | No invented first.last@ patterns that bounce |
| Source per record | Each record names the dataset that supplied it | You can trace and fix bad data at the source |
| Verified before send | Status is checked close to the send date | A list verified months ago is not verified today |
Inside Artemis, each of these is built into how records are handled. Every email carries a deliverability status, contacts can be checked before contact details are revealed, unknown fields come back empty rather than guessed, and each record names the dataset that supplied it.
Why nulls beat guesses
This is the requirement most lists fail quietly. When a database does not know someone's email, there are two choices: leave the field empty, or fill it with a pattern guess like firstname.lastname@company.com.
A guessed address looks complete in a spreadsheet. It inflates the count of "contacts with email." It also bounces when the guess is wrong, and every bounce tells mailbox providers your list is not maintained.
An empty field is honest. It tells you to enrich that contact, find another person at the account, or skip them. That is why Artemis returns nulls for unknown fields rather than guesses.
Why check-before-reveal matters
Pulling every contact's details from a search wastes effort and creates a bigger list to maintain. Check-before-reveal flips the order: confirm a contact is worth reaching first, then pull only the details you need.
In practice that means a shortlist built from fit, intent and reachability, followed by reveals only for the people who will actually go into a campaign. The list stays smaller, tighter and easier to keep clean.
Step by step: from search results to a send-ready list
Here is a sequence that works the same way whether you use Artemis or build it yourself.
Step 1: Filter for reachability before you export
Use email status, email type and reachability filters at the search stage. There is no reason to export contacts you already know you will not send to.
Step 2: Shortlist by fit and intent
Sort by fit first, then intent. Cut anyone outside the ideal client profile for agency outbound, even if their score looks decent. A smaller list of the right people beats a big list padded with near misses.
Step 3: Check before you reveal
For each shortlisted contact, check the record before pulling the email. Skip anyone whose status suggests the address will not land.
Step 4: Apply exclusions
Remove current clients, open deals, partners, competitors, past clients who left on bad terms and anyone who has unsubscribed from earlier campaigns. Unsubscribes must stay unsubscribed. In Artemis, unsubscribes are honored automatically, but your exclusion list should still be maintained as its own file.
Step 5: Deduplicate
Remove duplicate people and, where it makes sense, limit contacts per company so one account does not get five cold emails on the same day.
Step 6: Verify right before sending
Run verification as close to the send date as practical. Keep addresses with a verified status. Move riskier statuses, such as catch-all or unknown, to a separate small batch or leave them out.
Step 7: Send a small first batch and watch
Start with a modest batch from warmed mailboxes. Watch bounces, replies and placement for the first few days before scaling the list. The mailbox side of this is covered in our guide to mailbox warmup and inbox placement.
Bounce risk: what actually causes it
Bounces come from a short list of causes. Knowing which one you are seeing tells you how to fix it.
| Cause | What happened | Fix |
|---|---|---|
| Person left the company | Address was valid when collected, not now | Re-verify close to send; enrich to find their replacement |
| Guessed address | Pattern was wrong from the start | Use sources that return nulls instead of guesses |
| Old export | List sat for months before sending | Re-verify everything before a new campaign |
| Domain changed | Company rebranded or merged | Re-enrich at the company level |
| Typo or formatting error | Bad manual entry or import | Validate format and deduplicate on import |
Bounces are not the only risk. Google's sender guidelines tell senders to keep their user-reported spam rate below 0.1% and to prevent it from ever reaching 0.3%. Google defines a bulk sender as one sending close to 5,000 or more messages to personal Gmail accounts in 24 hours, and recommends honoring unsubscribe requests within 48 hours to keep lists healthy. An accurate list sent to the wrong people still earns spam reports, which is why verification and ICP fit go together.
Artemis vs a DIY list stack
You can build a verified list with separate tools: a database for search, a spreadsheet for exclusions, a checker for verification and a sending tool for the first batch. Many teams do. The trade-off is how many handoffs a record goes through before it sends.
| List task | Artemis | Typical DIY stack |
|---|---|---|
| Search and filter | Inside the same system | Data tool |
| Deliverability status | Carried on every email | Added by a separate checker |
| Unknown fields | Returned empty | Depends on the data tool |
| Source per record | Named on each record | Often lost on export |
| Exclusions and unsubscribes | Unsubscribes honored automatically | Maintained by hand across tools |
| Verification before send | Every address verified before it is sent to | Depends on someone running the check |
Each handoff in a DIY stack is a place where a status, a source or an exclusion can get lost. That does not make DIY wrong. It means someone has to own every step.
List hygiene after launch
A verified list does not stay verified. Hygiene is ongoing work, not a one-time step.
- Remove hard bounces immediately. Never send to the same dead address twice.
- Honor unsubscribes right away. Add them to a permanent exclusion list that every future campaign checks.
- Retire old lists. If a list has not been used for weeks, re-verify before reuse.
- Track bounces by source. If one source keeps producing bad records, stop pulling from it. This is where a source name on every record pays off.
- Watch bounces by segment. A segment with unusually high bounces often means the targeting pulled in the wrong kind of company.
- Recycle "not now" replies carefully. They are not unsubscribes. In Artemis, "Not now" replies get a dated follow-up, which keeps them out of cold sends while preserving the conversation.
For how the overall system keeps mailboxes healthy once a list is live, see how AGP's growth machine handles deliverability.
The verified list checklist
Use this before any list goes into a campaign. If a line is unchecked, the list is not ready.
- [ ] Every contact matches the written ICP (industry, size, title, seniority, location)
- [ ] Every email carries a deliverability status
- [ ] Only verified addresses are in the main send
- [ ] Catch-all and unknown statuses are removed or isolated in a small separate batch
- [ ] No guessed addresses; unknown fields are empty
- [ ] Each record shows the source that supplied it
- [ ] Verification ran close to the send date
- [ ] Current clients, open deals, partners and competitors are excluded
- [ ] All past unsubscribes are excluded
- [ ] Duplicates are removed and contacts per company are capped
- [ ] Each contact has company and intent context for personalization
- [ ] The list is assigned to warmed mailboxes on dedicated sending domains, never the main domain
- [ ] A small first batch is planned before full volume
If you want to compare dedicated checkers for a DIY build, our roundup of the best email verification tools covers the options and what each status means.
Who this is not for
A strict verification process suits most outbound programs, but not every situation.
- Warm lists. If you are emailing existing clients or people who opted in, this is the wrong playbook. That is email marketing, not cold outbound.
- Tiny account-based lists. For 20 named accounts, hand research and direct confirmation may beat any automated flow.
- Teams that want maximum list size above all. This process deliberately makes lists smaller. If raw count is the goal, it will feel slow.
Whatever provider you use, ask to see the status field, the source field and the verification date on a sample of 20 records. If any of the three is missing, the list is not verified in a way that protects your domains.
What comes next
Once the list is clean, it needs somewhere safe to send from. The next stage, agency cold email sending infrastructure, covers dedicated sending domains, SPF, DKIM and DMARC, and how sends are spread across mailboxes. Our general guide to cold email infrastructure is also useful if you are setting up domains yourself.
To see how verified lists connect to every other stage, from strategy to signed contract, read the full walkthrough of the AGP growth machine.
Want this built for your agency?
If you want a second opinion on a list before it touches your domains, book a call with David. He will look at how your list is built and tell you plainly what would make it send-ready.
Sources
- Agency Growth Partners, Artemis (deliverability status, check-before-reveal, nulls, source per record, verification before send): https://agencygrowth.partners/artemis
- Agency Growth Partners, home: https://agencygrowth.partners/
- Agency Growth Partners, Services: https://agencygrowth.partners/services
- Google, Email sender guidelines FAQ (spam rate thresholds, bulk sender definition, unsubscribe timing): https://support.google.com/mail/answer/14229414?hl=en
- Booking page, David Tile: https://agency-growth-partners.cal.com/david/nerdy-joe
Frequently asked questions
What is a verified lead list?
A verified lead list is a set of prospects whose email addresses have been checked for deliverability before sending, with each record carrying a status such as verified. It should also match your ideal client profile and exclude clients, open deals and anyone who has opted out.
How do you verify a lead list before cold emailing?
Check every address with an email verification step, keep only addresses with a verified status, remove duplicates and role accounts you do not want to contact, apply your exclusion lists and re-check anything that has not been verified recently. Then send a small first batch and watch bounces before scaling.
What is a good bounce rate for cold email?
As low as you can get it. Mailbox providers do not publish one universal cold email bounce threshold, so treat any noticeable rise in bounces as a reason to pause sending from that list and re-verify it.
Should I send to catch-all or unknown email addresses?
Treat them as higher risk. Many teams leave them out of the first sends or move them to a separate, small, closely watched batch, because a catch-all domain accepts mail at the server level even when the person does not exist.
How often should a lead list be re-verified?
Re-verify any list that has sat unused for weeks and any record before a new campaign sends to it. People change jobs and companies change domains, so a list verified months ago is not a verified list today.
Are purchased lead lists verified?
Some vendors claim verification, but ask when each address was checked, by what method and what status it returned. Without a status and a date on every record, assume the list is unverified.