AI Prospecting Workflow: Build a Prospect List With MCP
A full outbound prospecting push, from account list to a clean send-ready file, run start to finish in one AI conversation connected over MCP.
A prospecting push is a sequence with a start and an end, not a single lookup. Here's how the whole thing runs inside one AI conversation. We'll start from a raw account list until we get a file ready to import.
A list of accounts to reach doesn't turn into a send-ready file in one step. It goes through stages: figure out who you're actually trying to reach at each account, get their verified email, merge in whatever you already had, check nothing on the list has gone stale, then decide what to do with the accounts that came back empty. Skip a stage and the file you end up with either has gaps or has addresses that bounce.
An assistant connected to Anymail Finder over MCP can run that whole sequence inside one conversation, one stage after the other, instead of switching between a finder tool, a verifier, and a spreadsheet. What follows is that sequence end to end, using one example push to walk through it.
How to build a prospect list with an AI assistant, in six steps
- Start from the account list. Give the assistant your domains plus the role you're targeting, not names you already have.
- Ask for the whole batch in one pass. Get one table back with hits and misses both included.
- Merge in what you already have. Point the assistant only at the gaps, and leave existing verified rows untouched.
- Verify the carried-over addresses once, at the end. Run the deliverability check right before the send, on older and imported addresses; emails found during the conversation are already verified.
- Decide what happens to the misses. Broaden the title, flag for manual review, or drop and revisit next quarter.
- Move the finished file out once. Import into the CRM or sequencer only after the list is complete and checked.
Build your prospect list from accounts, not contacts
Most prospecting tools want a name first. That's backwards for an account-based push, where the list you actually have is companies, and the person you need at each one is defined by a role, not a name you already know.
MESSAGE TO THE ASSISTANT I'm running an outbound push to VP-level buyers at these forty accounts before the end of the quarter. For each one, find whoever runs revenue or sales and get me their verified email: [domain list]
The assistant treats each account as its own search rather than one combined query, so an account with no VP of Sales still gets checked against a Head of Revenue or a similar title before it's marked as a miss. Put the goal, the deadline and the seniority level in that first message, and it carries through to how edge cases get filled in later in the same conversation, without you having to repeat the context each time.
Ask for the whole batch in one pass (misses included)
Running one account per message multiplies the back and forth for no benefit, and it also means the misses don't show up until you've lost track of which accounts you already checked.
A single message covering the full list comes back as one table, hits and misses both included. An account with nobody found stays in the output as a blank row rather than disappearing, which matters later: that's the row someone still has to decide what to do with, and it needs to still be on the list to get decided on.
Bring in what you already have before asking again
Few pushes start from zero. There's usually a spreadsheet from a previous quarter, a partial export from a CRM, some rows already filled in and some not.
MESSAGE TO THE ASSISTANT Here's the same forty accounts, but eighteen already have a verified email next to them from last quarter. Only look for the twenty-two that don't, and keep the eighteen exactly as they are.
Ask about the gaps rather than the whole list again, and the credits spent on this stage stay proportional to what's actually missing, with last quarter's addresses left untouched instead of re-searched.
Verify the prospect list before it goes anywhere near a send
An address found six months ago and an address found ten minutes ago don't carry the same risk. Sometimes people change roles, or domains get retired, or mailboxes close. The stage right before a send exists to catch that, not to re-confirm what a search already confirmed on the spot.
MESSAGE TO THE ASSISTANT Before I load this into the sequencer, check the eighteen addresses we carried over from last quarter and flag anything that's not solidly deliverable right now.
This step belongs at the end of the process, not after each individual search earlier in the conversation. An address a search just returned has already been checked against the mailbox directly, so running it through the same check again at that point buys nothing, it's the addresses carried over from months back that actually need the pass.
Decide what happens to the accounts that came back empty
Every batch this size ends with some accounts unresolved: a company with no clear VP of Sales, a domain that returns nothing at all. This is the stage that's easiest to skip and the one that quietly shrinks a target list if it gets skipped.
Options at this point are usually one of three: try a broader title at that account, flag it for a manual look, or drop it from this push and revisit it next quarter. Once the rest of the list is settled, we can simply ask the assistant which of the three applies to each account, since it already has the full context.
Order of operations
The order matters more than any individual step. A few things worth keeping in mind when running this end to end:
- State the goal once at the start. The seniority level and the deadline belong in that first message, so later messages in the same conversation, filling gaps, re-checking a subset, don't need to repeat that context.
- Verify only what needs it. Emails Anymail Finder just found are already verified in real time, so there's no reason to check them again right after. Save the final verification pass for older or imported addresses before the list goes to a sequencer.
- Treat the misses as a deliverable. A finished push includes a decision for every account, not just the ones that resolved cleanly.
- Move the file out only once. The file should only reach a CRM or a sequencing tool once the list is complete and checked, or rows that still need fixing end up imported along with it.
The mechanics behind each of these stages, what an assistant can ask for and what each one costs, are laid out on the Anymail Finder MCP integration page. This piece is about the order to run them in for a push like the one above, not the reference for each action on its own.
Frequently Asked Questions
Give an AI assistant connected to Anymail Finder over MCP your account list plus the role you're targeting, and ask for the whole batch in one pass so hits and misses come back together. Merge in any addresses you already have, run a single deliverability check on the older and imported addresses before the send (emails found during the conversation are already verified), then decide what to do with the accounts that came back empty. Move the finished file to your CRM or sequencer only once, after the list is complete and verified.
There isn't a fixed batch size to stick to. For a longer list, splitting the work into smaller batches makes the output easier to review before moving to the next stage.
No. A column of domains pasted straight in works the same as one typed out. The assistant reads a list the same way either way, the only thing that changes is how you get the result back into a sheet afterward.
Yes. The stages don't change, only the role you're asking for. A recruiting list built by department or seniority runs through the same batch-then-verify sequence as a sales list built by buyer title.
After the list is clean, not before. Partial or unverified rows imported into a CRM tend to create duplicate work later, once bounces show up and someone has to go back and fix records. Run the full sequence first, then import the finished file, and that cleanup pass never has to happen.
Run the whole push in one conversation
Connect your assistant to Anymail Finder over MCP and every search comes back verified in real time.
Get 100 free credits