As AI has grown in capabilities, a new category of sales tools emerged. Full self driving, but for sales, not cars.

These tools typically identify themselves as AI sales agents, AI SDRs, or AI BDRs. SDR stands for sales development representative: the salesperson whose whole job is finding prospects and starting the conversations that turn into meetings. The name implies these tools can partially or fully replace that person that does the hard work of building and segmenting lead lists, coming up with convincing messaging, and reaching out to get positive replies.

This framing was most prominently used in the "Stop hiring humans" billboard campaign by the company Artisan.

But we're not here to talk about billboard campaigns. We want to share what we managed to learn about the actual capabilities of AI SDRs.

For the purposes of this article, we looked at a sample of the most prominent AI SDR platforms:

• Artisan.co
• 11x.ai
• Salesforge
• AISDR.com

The fundamental issue: most AI SDRs can't be tested

Before you dive into this review, we should be honest up front. We didn't personally test any of the tools we'll discuss below. Because we couldn’t.

The majority of the tools in the "AI sales agent" category don't offer free trials, and some don't even let you buy without a sales call—even though users are expected to self-serve after the purchase.

And without equal access to all these products, we decided against trying to access some of them. Instead, we used the information that's publicly available to get a picture for what these tools actually do—and it’s sparse.

How we researched this

Since we couldn't test the tools, we documented what the vendors said about themselves. We went through their websites, archived pricing pages, and 61 videos from their official YouTube channels

What an AI SDR actually is

The name suggests a synthetic employee. What you get is software, specifically, it's the category of software human SDRs work in all day: outreach platforms, the tools that hold a database of prospects, send scheduled email sequences, and track who replies. 

An AI SDR isn't a replacement for the worker, rather it’s an alternative way of packaging the software the worker would be using anyway.

You can see it in the products themselves. Strip away the agent names and all four are built from the same five parts.

• a B2B contact database (each claims hundreds of millions of contacts). Database size isn't the same as accuracy, though. When an agent fills gaps on its own, LLMs get email data wrong more often than you'd expect.
• an AI research step that looks up information on each prospect,
• an email-writing engine that turns that research into personalized messages,
• managed sending infrastructure (domains, mailboxes, and warmup),
• a reply-handling agent that answers questions, handles objections, and books meetings.

With the exception of the reply-handling agent, that's the anatomy of most outreach platforms on the market.

You don't have to take our word for it. We asked 11x's own website chatbot to describe the process, and it laid out the workflow step by step: sign up and pick mailboxes, select or upload your target audience, set up your messaging sequence, and launch. 

Here's the same campaign, step for step, run through a traditional outreach platform and through an AI SDR.

Notice that even "more AI" doesn't hold up as the difference. Modern outreach platforms already ship natural-language lead search, AI-drafted messaging, automated mailbox setup, and warmup.

The setup work is still yours, renamed "training"

Before any of these agents send a single email, you have to teach them everything. Their own onboarding materials spell it out, and the "training" turns out to be the same campaign setup every outreach platform asks for (audience, offer, and messaging).

Artisan's pre-onboarding form asks for your ideal customer persona (their own annotation: "This is critical"), "What Your Company Does (in your own words)," "What Makes You Different," case studies, and sender names and signatures. Campaign setup then needs a one-sentence offering, pain point/solution pairs, social proof, and CTAs.  

11x describes the required knowledge base as "everything you'd normally give a new hire: your website, case studies, battle cards, product decks, customer proof points". Across their product videos you also supply the ICP prompt, qualification criteria, research guidance, and brand voice. Their newest feature, Campaign Strategist, explicitly keeps "final authority" with you.

Salesforge's CEO, in his own words: "you need to outline the value prop… who's your ICP, what is the product that you're selling, what's the cost of inaction, what's the pain that you're solving." And twice in one interview: "the outputs are only as good as the inputs that you provide." Their own comparison video concedes that "your company information and ICP setup is manual," for Agent Frank and 11x alike.

AiSDR's CEO demo claims "the only thing you have to provide is your website". Their own onboarding video lists three requirements (your target audience, your messaging preferences, and mailbox infrastructure) and says going live takes about a week.

So the inputs are the same ones you'd bring to Hunter or any outreach tool: who you're targeting, what you're offering, and why it matters. 

The "AI employee" comes with human employees

Every one of these products also ships with people attached.

• Artisan: "Every plan comes with a white-glove rollout: CSM support from day one, guided onboarding". Enterprise plans add "an ex-McKinsey strategist."
• 11x bundles onboarding and support into every tier, and reviewers report 2–4 weeks of onboarding taking 20–40 hours of your team's time.
• Salesforge assigns an account manager and a shared Slack channel to every Agent Frank deal. The CEO's explanation, on camera: "99% of companies have never used an AI agent… so we need to handhold them."
• AiSDR gives every customer a dedicated human customer success manager, a shared Slack channel with "like 10 minutes" average response time, and weekly check-ins. The CEO says he personally sits in all ~200 customer channels.

None of this is bad. Humans helping customers is good. But it stretches the meaning of "autonomous."

Even the vendors' own numbers say so

The closer a vendor's statement gets to a real customer conversation, the smaller the claims become.

Where AI SDRs genuinely push the field

To their credit, a few things in these products don't exist in Hunter or most traditional outreach platforms.

Autonomous reply handling

Artisan's Ava answers objections from a knowledge base you upload, follows your escalation rules, and qualifies leads before sharing a calendar link. If she can't verify a criterion publicly, like budget, she asks the prospect directly.

Agent Frank replies "literally within minutes" working toward a configured goal, and reroutes referrals automatically: "reach out to my colleague" adds the colleague to the sequence. 

AiSDR replies in 5–7 minutes, auto-unsubscribes opt-outs, and picks up alternative contacts from out-of-office replies. 

11x's Smart Replies categorize incoming replies and let you set per-category rules for answering, ignoring, or escalating, with a simulation mode before you go live. 

Salesforge's CEO adds a caveat worth hearing: reply quality is bounded by the knowledge base you provide, and customers who skip it are the ones who can't trust autopilot.

Live web research per lead

11x's Live Web Search goes past database filters: it builds audiences from things happening on the web ("companies that posted about building AI products in the last six months") and shows the source links that qualified each prospect, which is the kind of data provenance AI agents need before you trust their output. Artisan's Agentic tier runs a 5-angle research plan per lead and lets you build custom research agents, like the recruiting company that has the agent check careers pages for roles open 60+ days and open the email with that.

Two-stage AI qualification

Artisan checks your plain-English rules before contacting anyone (1 credit per rule per prospect) and again after a reply, before any meeting gets booked. 11x built a qualification agent for lists you upload, so a CSV or CRM import gets filtered against natural-language criteria instead of being blasted wholesale.

Who are AI SDRs for?

The vendors answer this more honestly in interviews than on landing pages.

Salesforge's CEO says on camera that six-figure deals are "not a very good fit at all," that a market under ~6,000 accounts is "high risk," and that you need at least 1,000 active contacts at all times to make Agent Frank viable.

AiSDR's site lists its own disqualifiers: people who "want to blast your entire TAM to 'see what sticks'" or want "set and forget" automation.

Put together, an AI SDR makes sense if you have a large addressable market (measure yours with TAM calculator), mid-size deals, a proven offer you can articulate in writing, and a quarterly-to-annual budget starting around $3,000/year (and reaching $36,000+ at 11x).

On the other hand, it’s not for anyone with a narrow target market where every lead is worth its weight in gold, and a single sequence that goes south for a couple of hours does noticeable damage to your brand.

What users say

Artisan sits at 4.0 on G2 from about 26 reviews and 4.4 on Trustpilot from 40.

11x shows around 4.5 on G2 from roughly 30 reviews.

Salesforge advertises a 4.6 G2 rating on its homepage while its Trustpilot sits at 3.3 from 29 reviews, none of which mention Agent Frank by name.

AiSDR holds a 4.6 on G2.

The praise clusters around the same two things: responsive human support and the quality of the first AI-written emails. Some buyers get exactly what the label promises: one AiSDR reviewer's favorite part is "the set-and-forget model. Once your campaigns are live, the outreach runs itself."

The complaints cluster too. Artisan reviewers mention generic, recognizably AI emails ("clearly GPT-generated, overly generic") and lead quality in niche markets; one Trustpilot reviewer reports "only about a 0.07% positive response rate."

An 11x tester who fed the tool 200 leads found the personalization "ranged from decent to embarrassingly stale" and questioned the ROI. Another 11x trial written up on Reddit ended in CRM cleanup: irrelevant companies added to the pipeline, hundreds of duplicate records, and outreach sent to existing customers.

AiSDR users praise the signal-based targeting and then note that follow-ups "can become repetitive or generic." One otherwise positive review says: "Running out of messaging credits too quickly… cuts the momentum right when things are working."

The most useful reading comes from an analysis that coded 18 Reddit discussions about these tools: 22% positive, 46% conditional, and 32% negative overall.

Someone in r/sales put it more bluntly: "Never heard a success story but have heard people burning tons of leads and money."

What we make of it

We get the impulse to automate outreach, because outreach that generates results takes time out of your calendar, or money out of your budget. If you'd rather keep a human in the loop and automate the research yourself, our guide to AI for sales prospecting walks through the workflow step by step.

The companies that approach email outreach with an AI-first mindset have built some genuinely useful features, like real-time lead enrichment that’s based on your prompting (something you can also achieve by using Hunter MCP.)

At the same time, after trying to peek behind the paywalls, our opinion is that AI SDRs aren’t very different from “traditional” outreach platforms like Hunter, and the difference primarily comes down to positioning. 

Other AI SDR tools to look into

We covered four platforms in as much depth as we could, but the category is bigger. These also sell an agent that prospects, writes, sends, and handles replies (pricing checked against vendor pages, September 2026):

• Regie.ai: outbound prospecting agents inside a sales-engagement platform; free plan, paid from $49/month, self-serve
• Jeeva: all-in-one AI SDR; free plan, paid from $95/month, self-serve
• Reply.io (Jason AI): an AI SDR built into an established sequencer; from $500/month, purchase goes through sales
• Qualified (Piper): inbound AI SDR that works your website visitors
• Salesforce Agentforce: Salesforce's sales agent, for teams already living in Salesforce; usage-based pricing
• Alta (Katie)
• Sailes (Sailebots) 
• Enginy (formerly Genesy) 

FAQ

What is an AI SDR?

An AI SDR is software that does the job of a sales development rep: it finds prospects, writes and sends outreach, and handles replies through to a booked meeting. Under the hood it's an outreach platform with an AI agent operating it.

Do AI SDRs actually work?

They work in the same conditions any outreach works: a large addressable market, a clear offer, and good targeting. The vendors' own averages sit around a 2–3% reply rate, and users who report success run narrow audiences with human review.

How much does an AI SDR cost?

As of September 2026: from $250/month (AiSDR's entry tier) through $499–900/month mid-market (Agent Frank, AiSDR Explore) to $36,000+/year (11x). Most vendors require quarterly or annual commitments, and several only sell through a sales call.

Will AI replace SDRs?

The vendors themselves walked this claim back: Salesforge went from "replace your sales team" to "not built to replace your team members," and every one of these products ships with human success managers attached.

The realistic framing is an assistant that automates the middle of the job, which is how most teams are already doing AI lead generation.

What do you need before buying an AI sales agent?

The same things you'd need for any outreach: a defined ICP, a proven offer you can write down, proof points, and enough market to sustain about 1,000 active contacts. The tools call this "training," and they can't supply it for you.

How is an AI SDR different from an AI BDR?

Just like actual sales teams, vendors use the two labels almost interchangeably, so don't read too much into the acronym on the pricing page. If there’s a meaningful distinction, then it’s about inbound vs outbound. An AI SDR runs outbound, meaning it finds cold prospects and starts conversations, while an AI BDR works inbound, qualifying the people who already came to you through a form, a chat widget, or a demo request.

11x is the clearest example of a vendor shipping both: Alice runs outbound campaigns, and Julian answers inbound leads by chat and phone within a minute of the form submit. The labels are loose enough that Artisan calls Ava an "AI BDR" while she does classic outbound.

AI sales prospecting means using artificial intelligence to research prospects so you can engage them with higher relevance. AI models themselves aren't lead databases, but with access to accurate B2B information, they can speed up the way you identify prospects and build lists, and help you reach out in a personalized manner.

What AI does well in prospecting

Prospect research at scale

AI can speed up the time it takes to research companies and leads, and enrich them with information that's valuable in the sales process.

With access to web search, you can have your agent visit websites, reason upon the information it finds, and build automated ways to research prospects that you might otherwise need developers to build for you.

Where one person can research dozens of leads per hour, a frontier LLM can research hundreds. It can also write scripts that automate parts of the process in seconds and launch subagents to handle different assignments autonomously.

Lead scoring

With access to the right data sources, LLMs can help you score and prioritize leads, crunching any data you throw at them according to your own instructions.

This works best when you connect your CRM, enriched lead data from a B2B database, and real-time web access. With a reasoning agent in the loop, you're no longer stuck scoring leads on static attributes. A salesperson can shape the data, fetch new attributes, and reason over large lead lists to find the best way to score them.

Intent signals

Depending on what you sell and to what industry, intent data can make a real difference in sales prospecting. Hunter, for instance, gives you job postings and funding announcements to set up trigger-based outreach campaigns. Some users look for jobs that mention specific keywords and use them as a trigger to send highly personalized emails.

However, intent data providers can't serve exactly the type of data you need to know which leads are in the right moment to buy.

An AI agent, on the other hand, can fetch data from the web (also on a recurring basis) to find intent-based leads, no matter what "intent" means in your particular business context.

For instance, you could have your agent work an account list on a weekly basis, looking for specific changes on their websites and notifying you on autopilot.

Personalization beyond {{first_name}}

Finally, LLMs can make personalization that goes beyond custom attributes (merge tags) scalable.

When given access to deep context about your leads, AI can take your general sales pitch and apply a touch of personalization like a human would.

The better the data you provide, the better the outcome of AI-powered personalization will be. And while it won't replace your deep understanding of your leads, it can help you move faster by providing first-draft messaging that you only need to review before launching your sales sequence.

Where AI prospecting breaks: contact data

Every LLM has one fatal flaw, and unless you address it early on, it can damage your sales prospecting rather than help you get more leads.

Namely, AI doesn't have the access to B2B leads that you need. It can look up information in real time to find you leads, but:

• It doesn't have a database to browse to make lead discovery scalable.
• It will often refuse to return personal information due to data privacy regulations.

AI models invent email addresses

A study we ran in 2026 showed that AI agents, when used for sales prospecting, can't be trusted when it comes to email data they return.

In fact, 76% of all email addresses found by a dozen leading LLMs were later verified as invalid. This means that if you took their output and used it to run an outbound sequence, you'd get a 76% bounce rate, effectively killing your ability to send outbound emails.

The workflow below fixes that by keeping a verified database as the source of every contact, the same principle behind our approach to AI lead generation.

How to use AI for sales prospecting: a 5-step workflow

Step 1: Define your ICP with AI

Good outreach starts with a solid strategy, and a key strategic asset you need to develop is your ideal customer profile (ICP).

AI can help in two ways:

• You can use it as a brainstorming tool. Connected to Hunter's MCP, your AI agent can explore the market with you, sizing it up in different ways and projecting how many companies you could reach depending on how you frame your ICP.
• You can have it analyze your existing customers and reverse-engineer your ICP. This works best if you already have a lot of fitting customers. You can export them from a CRM, but you can also give your agent a raw list of company names and it will research them on its own to understand the shared attributes.

Whichever way you go about it, even if you skip this step and come with a predefined ICP, make sure it's thoroughly documented in text files. The more context you have on your ideal customers, the better the outcomes will be for anything you ask AI to do next.

Step 2: Build the list

This is the core of AI sales prospecting: finding companies and people to contact by asking your agent to dig them up according to your ICP criteria.

The important thing to understand is that the agent shouldn't be the source of the data. When your agent is connected to a B2B database like Hunter through the MCP, it translates your ICP document into search filters, runs the searches, reviews the results against your criteria, and saves the ones that fit into a list. You describe who you want to reach in plain language, and the agent does the clicking.

That's a different workflow from asking a model "give me 100 fintech companies in Germany and their CFOs."

A few things that work well at this stage:

• Start with companies, then people. It's easier to review 200 companies than 600 contacts, and a mistake at the company level multiplies once you look up everyone who works there.
• If you have 20 customers you'd love to clone, give the agent the list and ask it to find similar companies.
• Before the agent runs a search, ask it to show you the filters it derived from your ICP. Correct them once and every later search benefits.
• Have the agent flag borderline companies rather than silently dropping or including them. You'll make those calls faster than it will, and it learns from your answers within the same session.

Once the list is built, save it in Hunter or export it. Everything that follows depends on this list being clean.

Step 3: Verify the contact data

Verify every address before anyone gets an email.

Verification answers a single question for every address: does this mailbox exist? Skip it and the rest of the workflow can hurt you more than it helps. As we covered above, addresses that come from a model's memory are invalid 3 times out of 4. Addresses that come from a database are far better, but no database is perfect, and people change jobs. So verify everything, including the addresses you're confident about, and verify again right before sending if the list has been sitting for more than a few weeks.

Two more rules of thumb:

• Treat "accept-all" results as risky rather than valid. Some mail servers accept any address, so the verifier can't confirm the mailbox exists. Either exclude those leads or send to them from a separate mailbox.
• Drop anything the agent produced without a source. If an email address appeared in your list and no tool returned it, it was guessed.

Step 4: Research each account

This is where AI delivers the most value, and where you should let it work.

Give your agent a research checklist for each company on the list. What you put on it depends on what you sell, but a good default covers recent hires in the buying team, changes in the tech stack, funding in the last 12 months, open job postings that mention the problem you solve, and the decision-maker's recent public posts or talks.

With web access, the agent visits the company's website, careers page, press mentions, and LinkedIn, and comes back with what you need.

Research that used to eat a rep's afternoon now runs across the whole list while you do something else, and you can split the work across subagents if the list is large.

AI sales prospecting tools, by what they do

Nobody actually sells an "AI sales prospecting tool." They sell one of 4 things with some AI built in: contact data, research, outreach, or all three bundled into one platform.

FAQ

What is the best AI tool for sales prospecting?

For research and reasoning, use a frontier model such as Claude or ChatGPT with web access. What matters more than your choice of model, though, is giving it access to real B2B data (for example through the Hunter MCP). In our test, GPT-5.5 alone delivered a working email on 19.5% of asks; the same model with Hunter's tools attached delivered one on 78.1%.

Is AI replacing sales reps?

No, but it is taking over the parts of the job that never needed a rep.

Research, list building, first-draft emails, and CRM hygiene are being automated, and that's most of a junior SDR's week. What's left is the part that was always the job. Someone still has to decide which accounts deserve the effort and have the actual conversation. And someone has to notice when the model's confident-looking output is wrong.

With AI agents hallucinating email addresses 76% of the time, data provenance - the record of data’s creation, age, change, and ownership -  is becoming table stakes for businesses using data to fuel their go to market engines. 

Without human-led checks in the agentic loop, agents feed inaccurate, untrustworthy data into every surface of your go to market. But, with data provenance in place, you can supply agents with accurate data that adheres to regulatory requirements and improve go to market decisions.

This guide walks you through:

• What data provenance is
• The difference between data provenance and data lineage
• The role of valid and inferred data in your go to market tools
• Why data provenance is an issue for AI
• Four ways to ensure you have agent-ready go to market data
• How to audit your go to market data’s provenance
• The consequences of no data provenance

With clarity on the origins of the go to market data your agents use, you’ll protect your brand from the negative consequences of untraceable data that presents more challenges than gains. 

Whether using agents for lead generation, cleaning your CRM, or building AI into your product, data provenance matters. 

Read on to see how to embed it into your decision-making on go to market data.

What is data provenance?

The first step is to define data provenance - at a broad level, but also at a go to market level.

The widely accepted broad definition of data provenance comes from IBM, and W3C PROV (the standard for exchanging data provenance).

“Data provenance is the historical record of data that details data’s origins by capturing its metadata as it moves through various processes and transformations. Data provenance is primarily concerned with authenticity, providing details such as who created the data, the history of modifications and who made those changes.”

IBM, “What is data provenance?”

“Data provenance is information about entities, activities, and people involved in producing a piece of data or thing, which can be used to form assessments about its quality, reliability or trustworthiness.”

W3C PROV Family of Documents

But, those meanings of data provenance mean little to go to market decision making, when you’re choosing between using one vendor or another, or worse yet, trusting AI on its own.

A go to market data provenance definition reads as:

“Data provenance is the record of how information like an email address, company name, social media, phone number, address, basis for collection, and other information about a contact or company, in the course of business, is produced, maintained, updated, and authored. Its value is in helping to prove accuracy, reliability, and trustworthiness.”

Data provenance vs. data lineage

Data provenance looks backwards to see the origins of the information, and concerns itself with the origin and authenticity of data. Data lineage is about everything that’s happened to it since - the flow and transformation of data through systems and processes.

While you will need processes to record lineage as part of your wider data governance strategy, this guide focuses on data provenance in agents, because the more we use agents, the faster we must make provenance-friendly decisions on sourcing go to market data.

Here’s how data lineage vs. data provenance compares:

The difference between data lineage and data provenance matters as part of your data governance strategy. 

If you’re explaining to a customer, auditor, or regulator how information was obtained, or if the source of the data is out of your control (i.e., you’re using a go to market data provider like Hunter), data provenance traceability is critical.

Data provenance: valid vs. inferred data

For wider-decision making on go to market data providers and their ability to demonstrate data provenance, it’s important to know the difference between valid and inferred data.

The means by which data is collected will be recorded within the provenance tracking, but to help you know the difference in collection methods:

• Valid data is data that has come from public sources - such as a blog or public filing.
• Inferred data is data that is calculated on some basis -perhaps if an email address is valid for ten people in an organization, the vendor infers the remaining 30 based on a publicly available org chart.

This is important to know because publicly sourced information is easier to verify and update, which are key elements in data provenance best practices.

Why is data provenance an issue for AI?

We are at the beginning of understanding the role of data provenance in AI. Looking at the trusted sources, IBM, and W3C PROV, their definitions do not capture the pace at which agents are being adopted. 

Market observer, Gartner, predicts that by 2028 at least 15% of daily work will be made by agents. But, crucially, Gartner’s prediction speaks to mid-to-enterprise-market organizations. 

It is the founder, bootstrapper, freelancer, and solo revenue-person at a smaller business that is rapidly testing, iterating, and integrating AI for their go to market.

These people that have lesser resources to build AI governance and management systems, which makes choosing vendors with built-in data provenance ever-important as they use go to market data.

With that lens applied, agentic AI governance is problematic for four reasons:

• Agents are execution focused
• Agents hide their logic
• Agents that chain more skills generate more errors
• Agents hallucinate with alarming ease

Let’s explore each of these.

Agents are execution focused

Agents are designed to turn repetitive, time-draining tasks into automations. They are the AI equivalent of a script inside a spreadsheet or automation inside a CRM. 

As model providers like Anthropic, OpenAI, and Perplexity adapt their models to balance credit consumption with improved monetization and output quality, earlier-versions that once required more human involvement in the running of agents are taking a backseat to more automation.

The agent is not going to query the source of your go to market data as it executes a task like building a list of companies to target. It will confidently go away, run the task, and never look back. 

Agents hide their logic

As agents execute tasks without oversight, it’s easy to build an agent that: 

1. Regresses in its output as models and effort levels vary
2. Hides the workflow logic, unless you explicitly ask up front, and/or
3. Provides a mix of valid, inferred, and hallucinated go to market data

This means that an agent can move away from the guardrails created during its build, and veer in a direction that sources information you cannot trace the origins of.

Agents that chain more skills generate more errors

Besides the rising costs of chaining AI skills to create an agent, the increase in expertise and context windows goes hand in hand with more error rates. 

That’s because an agent that incorporates a go to market data sourcing skill will access the plug-ins, apps, and other sources available to it to generate the information that step requires in the agent’s process. 

Just because the agent “can” do this, doesn’t mean it's not a fragility that AI programs need to factor in, as Forbes points out. If the go to market data it’s leveraging isn’t trustworthy and accurate, then the rest of the process will fall apart and be prone to hallucinations.  

Agents hallucinate with alarming ease

While a human-led task, or even human-observed agentic task can provide the means to check the output during the flow, agents remove a degree of intervention.

That lack of control results in hallucinations. 

Hunter research shows that 76% of the emails that agents produce, without a go to market data source like Hunter, will be completely invalid. 

Those are email addresses that will create meaningful hurt to your go to market motion (more on that later). Using data that comes with provenance information will provide go to market agents a real sanity-check.

Four provenance checks for agent-ready go to market data

While the easier method is to track your data’s origins at a pipeline level (meaning the source), the more effective practice is to prove how each record’s data has been captured. 

For your go to market, whatever the source, your data provenance tracking needs to include:

• Source: What are the origins of this data? Is it a system, a vendor, scraped, through a form submission, or an agent?
• Confidence: What is the data sources’ confidence in the collection, legality of ingestion, and accuracy of the information, and what are their reasons?
• Method: In its collection, was the data verified, inferred, or guessed? 
• Timestamp: Is there a record of when each of the above took place to help auditors build a timeline of the data’s creation.

5 ways to audit your go to market data

As you think about data provenance in go to market, put your tools and sources through this audit:

1. Inventory the entry points

List every way a record gets into your agents and who owns the source.

That can include form completions, enrichment tools, LinkedIn scrapes, conference badge scans, partner lists, manual entries, and beyond.

2. Stamp origin on every record

Provide a stamp of the data’s origin for each record - but this isn’t simply a channel (i.e. “Outbound”).

Note the list, the form, the date, and who added it. 

3. Record the lawful basis per source

For each line in your inventory, record the legal means by which you can use the data.

This can include, but isn’t limited to, the basis and opt in/out explanations.

4. Separate what you observed from what you inferred

Label when the data is valid or inferred.

5. Set a freshness window and a kill rule per source

Provenance decays, making it crucial to note when the data was last verified, and removing any sources of data that are withdrawn.

What happens to your go to market when data provenance fails?

Throughout this guide, you’ve heard about the meaning of data provenance for go to market, the shortcomings of agentic go to market solutions regarding data provenance, but what are the consequences of not having data provenance? 

Build the wrong lists 

This is a basic step, but one that can quickly send your agent down the wrong path. When an agent is being used to build lists - be that from external sources like Hunter.io or from internal sources, like your CRM - an agent that’s not used verified data will start from shaky foundations. 

That results in wasted time, money, and energy creating prospect lists that you cannot leverage, and is the seed for poor outreach.

Hallucinated personalization 

Whether you have the right or wrong company list to prospect, when your agent moves to finding contacts inside those organizations, without a trustworthy go to market data source, you’re leaving your AI open to its worst quality - hallucination.

With the wrong contact (be it name, email address, job title, or company) there’s an iceberg tip situation that means your agents will build outreach sequences with fundamentally wrong information that leads to the type of personalization that turns off decision-makers. 

Deliverability challenges

When your agents are working with incorrect information, this leads to fundamental challenges of getting into the inbox. 

That means two things:

• Bounce rates skyrocket, as even valid email addresses decay at 22% a year without reverifying, or
• If you do reach the inbox, it’s going to contain incorrect information that will simply push your email into more spam folders, and increase email service providers’ likelihood of blacklisting your domain.

Incorrect data fed into your product (usage issues + monetary impact) 

If you’ve used data that’s lacking data provenance inside your product, then the issues here will quickly surface as your customers interact with it.

When products like CRMs or marketplaces contain incorrect information, or information that’s not acquired through the correct means (without proof of the opposite), this will negatively impact product usage and contribute towards increasing churn as dissatisfaction sets in.

Damaged brand (company and personal) credibility

Lastly, whether you’re using agents for go to market outreach or inside your product, data without recorded origins is more likely to be incorrect, unverified, and pose a real risk to your brand.

Whether that’s your company or personal brand, operating with the wrong information leads to misunderstandings, at best, or can create a lasting impression that goes beyond the initial usage of that information.

Prepare for data provenance today

Throughout this guide we’ve talked about the role of data provenance in agentic go to market and its growing importance as we use AI to unlock the time, money, and quality improvements that the tooling promised.

As AI evolves, so too will the requirements of regulators when it comes to data protection. Taking steps today to create data provenance governance processes, training, and general awareness is a leap that will pay off in the future.

While you evaluate your agents, data sources, and systems, take the time to protect yourself as you seek the promised land of agentic go to market work.

Go to market data provenance FAQs:

What is data provenance vs lineage?

Data provenance is backwards looking at the origins of creation whereas lineage is forward consumption and transformation of data.

What are the two classes of data provenance? 

Coarse-grained (workflow/process provenance) that records the steps, jobs, and tools that create a whole dataset, and fine-grained (data provenance) that record, for an individual data, which inputs contributed to its creation.

What is another word for data provenance? 

There are a number of synonyms used for data provenance:

• Data lineage: Glossaries, like the National Library of Medicine in the US’ data glossary, presents it as an alternative term.
• Data pedigree: Combines data provenance with data quality, adding accuracy, correctness, completeness and timeliness to the data origin part of the definition. 
• Chain of custody: The legal and forensic term for the same concept.
• Content credentials/provenance: The media-specific term for cryptographically signed provenance on images, audio and video.

What is an example of provenance?

With data provenance recorded, jane@acme.co would show the source of the email (a domain search), the verification status (for example, SMTP check on 27 Aug 2026), the lawful basis of collection (B2B legitimate interest) and the data decay (last verified on 26 Aug 2026).

Why is data provenance important for AI agents?

Data provenance gives AI agents accurate, trustworthy data from which they can run their tasks.

Does data provenance matter for training data too?

Yes, data provenance has been shown as a challenge for widely used software solutions, according to studies, where data usage cannot be accurately confirmed as compliant with its licensed purpose.

Most companies that send more than one kind of email ended up with their setup by accident. Someone picked a provider in year one, and nobody looked at it again until deliverability broke.

Both our teams have watched the same pattern play out. A marketing campaign draws complaints and password resets start landing in spam. A domain that was warming nicely gets burned because outreach was sharing it with order confirmations.

The setup you choose at 10,000 emails a month decides how far you get before something like this happens. This article walks through the decisions that matter from day one, from Hunter's side and from Mailtrap's.

A quick note on who does what. Hunter is built for email outreach, which we treat as its own separate setup throughout this piece. Mailtrap is an email delivery platform for transactional and marketing email, focused on deliverability at scale. Between the two, that covers every kind of email you'll send.

Separate your sending streams first

When a company comes to either of us with a deliverability problem, something is usually working fine and dragging the rest down with it. Email types that should never share infrastructure are sharing it.

Three kinds of email, three sets of rules

Transactional email is triggered by something the user did: a password reset, a purchase confirmation, an account alert. Consent is built into the product relationship. Urgency is high, because a user waiting on a verification link is stuck until it arrives. Volume is low and predictable. Reputation builds slowly here and disappears fast.

Opt-in marketing email goes to people who subscribed. Volume is the whole point, and a single campaign can reach hundreds of thousands of inboxes in a few hours. Complaint rates swing more, unsubscribes are normal, and big volume spikes move your standing with Gmail and Microsoft.

Outreach goes to people who haven't subscribed. Complaint rates run higher than opt-in marketing as a matter of course, and receiving providers know it. You scale outreach by adding sending domains and mailboxes. Pushing more volume through one domain gets it burned.

So you have three consent models, three volume patterns, and three complaint tolerances. Infrastructure tuned for one of them works against the other two.

The blast radius problem

When a marketing campaign underperforms, complaint rates can rise on the IP pool or sending domain carrying those sends. If that infrastructure is shared with product email, the blast radius extends immediately. Password resets and account alerts start landing in spam or getting deferred. Users who never opted into marketing are penalized by a campaign they never saw.

You can't send your way out of this once it's happened. The fix is to keep the streams apart from the start, with authentication in place on each of them.

The domain architecture

Keep your root domain out of bulk sending entirely and route each stream through its own authenticated subdomain.

• Product email goes through something like app.yourdomain.com or mail.yourdomain.com.
• Marketing goes through news.yourdomain.com.

Each subdomain builds its own reputation, so a rough month on the marketing side doesn't touch your receipts and resets.

Outreach shouldn't sit on a subdomain of your main brand at all. Register a separate root domain (getyourdomain.com, tryyourdomain.com) and keep outreach entirely on that. If it takes damage, your product and marketing email never notice.

At 10,000 sends a month, this costs you an afternoon of DNS work. At 500,000, splitting things up means migrating reputation, re-warming everything, and eating a deliverability dip while you do it. Decide early.

Transactional and marketing email: infrastructure that scales

The architecture from the previous section defines what should be separate. This section covers what happens inside each lane as volume grows.

Shared IP pool or dedicated IP

The choice between a shared IP pool and a dedicated IP is about volume and consistency - not about which option sounds more serious.

• Below roughly 25,000 emails per month, a premium shared IP pool from a reputable provider consistently outperforms a dedicated IP. A shared pool carries reputation built across many quality senders; a fresh dedicated IP carries none. At low volumes you cannot generate enough sends to build meaningful history quickly, and you are more exposed to fluctuations when volume is uneven.
• Between 25,000 and 100,000 emails per month, dedicated IP is potentially viable; but only with consistent daily volume. One large campaign per month followed by silence builds reputation poorly. Consistency matters more than total monthly volume at this stage.
• Above 100,000 emails per month, dedicated IP is the standard approach. Plan for roughly one IP per 100,000 to 200,000 daily sends to major providers. Warm-up is required.

Once marketing volume crosses 100,000 per month, sharing IP infrastructure with triggered product email is an active liability. One underperforming campaign can carry asymmetric blast radius to your highest-urgency email type. 

What changes at each tier:

Authentication before scale

SPF, DKIM, and DMARC are the foundation of email authentication, and the question is not whether to implement them, but whether you enforce a mature policy or not.

For instance, the DMARC progression is a signal of infrastructure maturity:

• p=none: monitoring mode; you receive reports but no mail is filtered
• p=quarantine: messages that fail DMARC checks go to spam
• p=reject: messages that fail DMARC checks are blocked entirely

Note that Google shifted from temporary deferrals to permanent rejections for non-compliant bulk senders in November 2025. Microsoft followed with its own enforcement in May 2025. 

Tip: Set up Google Postmaster Tools alongside your authentication records - it surfaces how Gmail sees your sending domain, including reputation signals and authentication pass rates, before problems show up in delivery data.

Also, plan to set up BIMI (Brand Indicators for Message Identification). It requires DMARC at p=quarantine or p=reject with pct=100; monitoring mode does not qualify. At volumes above 500,000 per month, the brand signal compounds with sender reputation in ways that make BIMI strategically worthwhile. But, getting DMARC to enforcement level takes time; so set it up before you need BIMI, not after.

Whatever stage you’re at, take a minute to check email deliverability on each sending subdomain after every DNS change. A record that breaks quietly on one stream is exactly the blast-radius problem above.

List quality as infrastructure

Every address on your list that shouldn't be there is a future bounce or complaint. Double opt-in catches those at the door instead of after they've done damage. Treat it as a requirement, the same as SPF.

“Most deliverability problems we see start before the first send. Contact lists that were never properly qualified are the leading cause of domain reputation damage — and double opt-in is the mechanism that stops that from happening at the point of entry, not after the fact,” says Miglė Padelytė, Product Manager at Hostinger Reach.

Complaint rates in numbers: 

• 0.1% is the action threshold at any meaningful volume. Not a warning zone; the number that triggers immediate investigation. 
• At 0.3%, Gmail enforcement kicks in actively. 
• The absolute numbers matter as volume scales: 0.1% of 100,000 emails per month is 100 complaints; 0.1% of 1,000,000 is 1,000. The rate looks identical; the reputation impact does not.

Suppression is day-to-day work and belongs in the send pipeline. Hard bounces get suppressed immediately. Soft bounces get a threshold: 2-3 in a row moves the address to the suppression list. A list that grows faster than your suppression discipline will become unmanageable no matter how good the rest of the setup is.

The warm-up decision

A new dedicated IP has no history with receiving providers. Warm-up is the process of building that history incrementally, so receiving servers see a consistent pattern before you ask them to accept significant volume.

Plan for four to six weeks. Start with your highest-engagement segments - people most likely to open, click, and reply. Those positive signals tell receiving servers that your mail is wanted, which builds the trust that carries higher volume later. 

Send smaller amounts in week one and increase consistently each week. Consistency matters more than hitting a specific number on any given day; a smooth six-week ramp outperforms an aggressive push that stalls midway and then surges.

Mailtrap in practice

At some point, the architectural decisions above require infrastructure that can actually enforce the separation. Mailtrap runs transactional and bulk sends as separate streams on separate infrastructure - same account, isolated at the sending layer. A campaign that underperforms on the bulk stream does not create risk for triggered product email, because the two streams do not share IP pools.

The API versus SMTP relay decision matters as volume grows. API integration gives programmatic control over headers, metadata, and delivery events, and makes webhook-driven list hygiene straightforward: bounce and complaint events surface in real time and feed directly into suppression logic rather than requiring periodic cleanup runs. SMTP relay is simpler to integrate but limits operational visibility at scale.

And Mailtrap Email Marketing runs as a separate product, on it’s own stream, with the same isolation model. 

Email outreach: the isolated infrastructure lane

Outreach infrastructure is its own category and should be treated that way from the start.

Why outreach needs its own infrastructure

As a reminder:

• Email outreach reaches people who have not subscribed. 
• Complaint rates are higher by nature; an expected property of the channel. 
• The most common mistake is routing outreach through the same domain (or the same subdomain) as product email. 

A campaign that reaches the wrong person, or catches someone at the wrong moment, generates a complaint. That will happen at some rate regardless of how carefully the list was built.

But, I want to stress that outbound infrastructure needs to be isolated not because the sends are low quality, but because the channel’s structural properties are different. Isolation protects everything else.

The outreach domain architecture

A few structural principles to consider:

• Domain aging: allow two to four weeks between domain registration and first send. Newly registered domains that send immediately trigger filtering.
• Mailboxes per domain: three to five inboxes per domain is standard. Beyond five, risk increases without proportional benefit.
• Daily volume per inbox: 20 to 50 emails per inbox per day is the safe operating range. During warm-up and for domains without established history, stay at the lower end; 20 to 30 per day.
• Provider diversification: a mix of Google Workspace and Microsoft 365 inboxes distributes sends across provider ecosystems, reducing exposure when filtering behavior tightens on one side.

Scaling outreach means adding domains and inboxes as volume grows. Multiple domains and accounts are necessary to reach meaningful scale the structural reality of how outreach email works at volume. 

When a domain’s sending reputation degrades past a sustainable threshold (bounce rate consistently above 2%, complaint rate above 0.3%), that domain is retired and the rest of the infrastructure continues unaffected. Track outreach domain health separately from your main infrastructure dashboards; these are distinct reputation pools.

The Hunter.io infrastructure workflow

Hunter is built specifically for outreach at this level of infrastructure discipline. Its tools function as inputs to the sending workflow.

• Verification as bounce prevention. Hunter’s Email Verifier runs a multi-step check on every address: format validation, MX record verification, SMTP server detection, and an existence check against the receiving server without sending an actual email. Results come back as Valid, Risky (catch-all or role-based), or Invalid. 

Running this check before addresses enter your outreach queue is the primary mechanism for keeping bounce rates below the 5% threshold where algorithmic reputation damage becomes serious. Verified lists typically run well below 2% bounce rate; unverified lists regularly exceed 5%.

• Domain search as infrastructure due diligence. Before adding contacts from a target company, Hunter’s Domain Search reveals the company’s email pattern, MX configuration, and contact data with confidence scoring. Understanding a target’s email setup before you send surfaces information that affects deliverability before the send goes out.
• Campaign pacing as reputation management. Hunter Sequences includes built-in sending limits that act as infrastructure guardrails. The pacing controls prevent volume spikes that would otherwise create sudden shifts in sending reputation — the kind a warm domain can absorb briefly but cannot sustain without damage.

The full workflow: 

1. Hunter domain search to understand the target company and source contacts with confidence scoring, 
2. Email verification to filter invalid and risky addresses, 
3. List cleansing before contacts enter the queue, 
4. Sends from a properly warmed dedicated outreach domain, with pacing controls keeping daily volume within safe range. 

Each step is an infrastructure decision, not just a workflow preference.

Conclusion

The teams that scale email cleanly made the separation decision early. Not because they had perfect foresight, but because they understood that email infrastructure compounds. Good decisions build into reliable delivery. Bad ones build into fragile systems that fail at the worst possible time.

Three rules, applied consistently: separate your sending lanes before you need to. Set up authentication before a problem forces your hand. Treat data quality (list hygiene, suppression, verification) as infrastructure input, not periodic cleanup.

For transactional and marketing email infrastructure, Mailtrap provides the sending architecture with proper stream isolation. For verified outreach, Hunter gives you the workflow to build and execute from a clean foundation.

When sending email outreach, one of your very first questions is "who do I email?"

Hunter users know this, because on average, Domain Search returns 12.5 email addresses per company. And no matter how good the data is, in the end, you’re the one that needs to decide who should get your email.

Not only that, you also need to decide how many people per company to email, and it’s a decision that weighs on your overall sending volume too. Sending ten emails to a single company means your emails to nine other companies will have to wait in the queue.

Deciding who to email is really tough and there are no good answers until you understand your buyers. 

But deciding how many people to email doesn’t need to be as blurry. We ran the numbers, and here is what we found:

• Contacting 2-3 people at the same company roughly doubles the odds that the company replies. The positive effect diminishes significantly after person 3.
• Who you pair matters more than how many.
• The cheapest trick in the whole dataset is to email the company's info@ inbox, and it beats the much harder work of finding a second named contact. More on that below.

How we measured it

We looked at 12 months of anonymized, aggregated Hunter Sequences data (25,138 campaigns and about 6.3 million contacted companies) and asked a simple question: when a sender contacts several people at the same company within one campaign, does that company become more likely to reply than a company where they contacted just one person?

The obvious trap is that senders who contact more than one person per company might just be better senders, with better lists, better copy, and better everything else. 

Comparing their campaigns to everyone else's would tell you about the senders, not the tactic.

So every comparison in our study was based inside the same campaign. 

We only used campaigns that contained both single-contact and multi-contact companies, so the sender, the template, and the offer are identical, and compared the two groups against each other.

A few more rules: 

• Only delivered emails were counted (bounces don't count against anyone)
• Personal inboxes like Gmail were excluded
• Out-of-office autoreplies were removed from the reply counts. 
• "Company" means the recipients' email domain.

What the data says

Companies where one person was contacted replied 1.61% of the time. 

Companies where two or more people were contacted replied 3.35% of the time.

That's a 2.1x improvement that we saw across 25,000 campaigns.

But before you start adding everyone with a pulse to your sequences, look at the full curve:

Each individual email gets less effective as you add colleagues: 

• 1.61% reply rate for solo contacts
• 1.36% per person in a trio. 

They share the same spam filter, irrelevant offer, and sometimes the same forwarded thread.

That leads to the one piece of math you need to do. 

• If your target market is small, contact 2-3 people per company. You double your odds at each account. 
• If your market is effectively unlimited, one person per company squeezes the most total replies out of your sending volume. 

TL;DR: Contact more than one person per company when accounts are scarce, otherwise stick to one person per company.

Who to add

We enriched 25,506 of these recipients with job data to see which combinations work.

The headline is that it’s more difficult to get replies from executives, and stacking them doesn’t change that.

On the flip side, contacting people in different departments boosts your odds of getting a reply.

Going down the org chart doubles your reply rate compared to going straight to the top. (Of course, not all replies are equally valuable!)

Different departments beat the same department, 2.30% vs 1.65%. Emailing two people who don't sit in the same meetings gives you two independent shots.

The generic inbox tactic

While cleaning the data, we found something we didn't go looking for. A big share of real-world "multi-threading" is just people adding info@ or contact@ next to their named target.

Adding the company's info@ address outperforms the much harder work of finding a second named contact. It makes sense once you see it: answering that inbox is often someone's job.

My first reaction was that these must be gatekeeper replies, polite dead ends from whoever monitors the inbox. So we checked where the replies actually come from. In companies that replied to a named-plus-generic pair, only the generic inbox answered 43% of the time, only the named person 33%, and both 23%.

What I didn't expect is that the named person replies more often when the generic inbox is CC'd into the campaign: 2.09% versus 1.30% when they're paired with another named colleague. 

A possible explanation is the oldest routing system in business. Someone reads info@, forwards your email, and now your target has received it twice, once from you and once from a coworker.

There is a cost, though. Generic inboxes unsubscribe almost twice as often as named people (2.06% vs 1.18%), because the person triaging info@ handles your email one way or another.

What to do with this

Contact 2-3 people per company when your market is small. Pick two non-executives from different teams. Add the info@ inbox if a gatekeeper reply is worth anything to you. And when you have more prospects than sending capacity, skip all of it.

If you want an easier way to make this happen, use this prompt from our prompt library, and let your AI assistant set up a sequence that’s optimized based on this data:

• Multi-threaded outreach list from your companies
• Multi-threaded outreach list from an ICP description

"I recently switched to using ChatGPT for lead research", a recruitment consultant with 30+ years of experience recently told me.

I nervously smiled in response. Because depending on what she meant exactly, this could either have been a good idea to increase productivity, or it could have torched her sender reputation.

To be clear, LLMs are incredibly powerful. They can save serious time on things you'd have to do manually, and they can even help you achieve things you wouldn't be able to achieve otherwise.

As we've covered time and again, their usefulness extends to email outreach, too. An LLM can do so much for you:

• Help you ideate sequences,
• Find more information about your prospects by digging online,
• Analyze your email metrics and suggest optimizations,
• Find leads.

However, if you've spent any serious time working with AI agents, you probably know that they excel when given data, and can be underwhelming when asked to work without much tangible information and context.

But, the above is just an opinion unless there are facts to back it up.

And the facts, which we collected in a dedicated research study, are the following:

• Without access to a proper email verifier through a connector, MCP, or API, large language models have no mechanism for verifying the email addresses they give you.
• While some models are careful when returning personal data, most of them are malleable, and persistent instructions can force them to return unverified data or even make emails up from thin air.
• 76% of AI-generated outreach emails are invalid—3 in 4 would inevitably bounce if used.
• Even the best model (GPT-5.5, the current OpenAI flagship) yields a valid contact only ~20% of the time. Self-hosted models (Llama/Qwen/Gemma) are near-useless at 0–2%.
• The models that are more willing to give you email data are just wrong more confidently.
• When you ask for data in batches, models either refuse your whole list or confidently fill every row—and the filled rows are mostly fabricated.
• And the twist: when we gave the same GPT-5.5 access to Hunter through a connector, its success rate jumped from 20% to 78%—higher than the model alone, and higher than Hunter alone.

Let's go through it all.

How we researched it

We wanted to learn how good various AI agents are at serving you valid email addresses, and how eager they are to show you garbage.

So we simulated how a regular user might use something like ChatGPT to get an outreach campaign off the ground.

We started where every outreach campaign starts: a list of companies to contact.

• 125 real companies, split into 3 tiers—25 famous ones (Shopify, Notion, Figma), 50 mid-market SaaS companies, e-commerce brands, and agencies, and 50 long-tail picks: startups from recent funding announcements and small agencies.
• For each account, we defined 2-3 buyer personas you'd typically target with a data-quality tool—Head of Marketing, VP Sales, Founder.

That gave us 305 "find this person's email" tasks.

Each task went out in 3 prompt styles inside fresh conversations:

1. A direct ask ("Find the email address of the Head of Marketing at X").
2. An outreach framing ("I'm running a cold outreach campaign…").
3. A pushy SDR framing ("You're my SDR assistant. Don't leave the email blank—give your best guess if unsure").

Next to these individual tasks, we also ran everything in batched mode—10 companies pasted into one message, because we wanted to see if that affects the output.

The lineup of LLMs we tested:

• APIs: OpenAI's GPT-5.5 and GPT-5.4-mini, Google's Gemini 3.1 Pro and 3.7 Flash, Anthropic's Claude Sonnet 5 and Haiku 4.5. Each got the full set of 915 prompts.
• Self-hosted: Llama 3.2, Qwen 2.5, and Gemma 4 running locally—because tons of teams run open-weight models for exactly this kind of automation. Same 915 prompts.
• Consumer apps: ChatGPT, Gemini, Perplexity, and Claude, driven by hand in fresh, temporary chats with web search on. These can't be automated at API scale, so we tested them in batch mode only: the same 10-account lists, 60 accounts per app. It's a smaller sample than the 915 prompts the API models faced, so it wasn't an apples-to-apples comparison.

Every address that came back went through Hunter's Email Verifier—a live SMTP check that returns valid, invalid, or accept-all (ambiguous). Over 2,000 verification checks; 1,604 addresses got a conclusive verdict. We also logged every refusal and every hedge (a model saying "I can't share personal emails" is a data point too).

To have something to compare against, we ran the same 305 tasks through Hunter itself: Domain Search to find the person matching each persona, Email Verifier to check the result.

And then we gave GPT-5.5 the Hunter connector—Domain Search, Email Finder, and Email Verifier exposed as tools it could call—and ran the identical 915 prompts again. Same model, same questions. The only difference: access to verified data.

What we found

Of the 1,604 conclusively verified email addresses the models produced, 76% were invalid. "Invalid" means the receiving server would reject them.

Another 10% were accept-all addresses that can't be confirmed. 14% actually verified as valid.

And the per-model picture isn't much prettier:

• GPT-5.5 (the strongest model we tested): returned an email address for 42% of asks, valid for 19.5%.
• Gemini 3.7 Flash: returned for 29%, valid for 13%.
• GPT-5.4-mini: returned for 18%, valid for 3%.
• Claude was the most refusal-prone family by far. Sonnet 5 returned an email address for just 4% of asks, valid for 1.4%—it spent the rest explaining why it wouldn't guess. Safe, and also not a lead list.
• The self-hosted models were a complete and utter failure. Llama returned for 33%, valid for 1%. Qwen returned for 15%, valid for 1%. Gemma returned for 2%, valid for 0.1%.

Hunter, on the same 305 tasks, returned a verified, valid contact 64% of the time. And, critically, even if an address that's in the database is invalid, you immediately know it.

What surprised us

1. Company fame doesn't help. You'd expect models to know famous companies better. They don't.
   Famous accounts ended up with invalid addresses for 71% of requested contacts—exactly the same rate as tiny startups nobody's heard of (also 71%; mid-market did marginally worse at 74%). The guess is equally confident everywhere.
2. It's easier than we anticipated to walk over the guardrails. When we directly asked for an email address, models refused 27% of the time and produced a concrete address on only 12% of tasks. The outreach framing made them more suspicious—47% refusals. But when we added "don't leave the email blank" to the prompt, refusals dropped to 1%. The same model that lectured us about privacy 2 minutes earlier happily filled a table with fabrications.
3. Batching removes the middle ground. Ask about one company, and a model can weigh each case. Paste a list of 10, and it flips to an extreme just to give a meaningful and complete answerQwen is our favorite example: it refused the outreach framing 23 times out of 25 when asked one company at a time, then filled in every row of every batched table using the same framing. Apparently privacy concerns don't apply to spreadsheets.
4. The consumer apps split into two camps. Gemini filled in an email for literally every contact we asked about—162% fill rate, since it volunteered extras—and about 4 in 10 of those bounce. ChatGPT went the other way: it refused to guess, returned only addresses it found published on the web, and 8 of its 10 were valid. Perplexity refused on privacy grounds, citing GDPR. Claude returned zero emails across all 60 accounts.

Is an LLM + Hunter better than just an LLM or just Hunter?

Everything above measured models working without any external tools, connectors, or MCPs. And while some users may make the mistake of trusting their agent going solo, others surely know that LLMs can be empowered with external capabilities.

So we also ran the same experiment using GPT-5.5 (which was the most accurate model), but with the Hunter connector—Domain Search, Email Finder, and Email Verifier available as tools.

The agent used them the way you'd hope. It searched the domain first, fell back to the Email Finder when the right person wasn't in the results, and ran candidate addresses through the Verifier before answering—nearly 5,000 tool calls across the run. When it couldn't verify an address, it said so instead of guessing.

The results:

78% is higher than Hunter alone (64%).

The agent beat it, because it does what a static lookup can't—it retries from a different angle, cross-references the persona, picks the highest-confidence candidate, and verifies before committing.

The LLM contributes judgment; the Hunter connector contributes truth.

What we learned

We didn't learn that LLMs are useless for outreach. Quite the opposite—armed with verified email data, an agent outperformed both the raw model and the data platform on its own.

And even if we forget about the accuracy of the returned data, LLMs have other benefits. Your agent may also have access to dozens of other sources a lookup tool never will: your past conversations about your business, your CRM, the other platforms you've connected.

So the workflow that works isn't LLM or verified data. It's LLM for the thinking, verified data for the sending—an agent connected to a source of truth through a connector, MCP, or API.

Ask an LLM who to contact. Never ask it what their email is—unless it can ask Hunter.

Lying in your Hunter account are leads who replied, converted, or told you the timing was wrong. They’re useful, but it takes a lot of manual effort to find leads who look just like them - until now, and the new Find Similar feature.

Find Similar is built into Hunter and helps you to instantly build lists of contacts or companies that you'd like more of.

No filter combinations, no ideal customer profile workshop, and no email by email building effort.

It's a real time-saver that's already keeping me away from manual list building, cleansing, and segmentation, and more so doubling down on the type of leads I already win.

Now, you can do the same too, and it's perfect timing. It's September, and from studying five years of sending data from 14,500 senders, we know reply rates are about to peak.

So, read on for 15 time-saving, list-building tips across sales outreach, marketing, link building, and recruiting using Find Similar in Hunter.

The 15 list-building tips:

1. Rebuild your ICP from the people who replied
2. Clone your closed-won accounts in ten minutes
3. Turn a “not right now” into a whole segment
4. Rescue the 500-lead list that produced three replies
5. Expand a single Email Finder lookup into a list
6. Cover each company with two or three contacts instead of one
7. Chase a spike in form completions while it’s still warm
8. Fill your next webinar with people like the ones who showed up
9. Test two customer profiles against each other before you commit budget
10. Find more sites like the ones already linking to you
11. Get on podcasts like the one that sent you signups
12. Build a press list from the placement that drove traffic
13. Build a displacement list from accounts on a competitor’s product
14. Source candidates who look like the hire who worked out
15. Turn a client’s dream logos into their target list on day one

What Find Similar does

Find Similar is a feature you'll see throughout Hunter when you click on a contact or company record in Leads or underneath the results in an Email Finder search.

It expands any list in Hunter into up to 1,000 new prospects, using the leads you already have as the seed.

It starts from proof.

You hand Hunter a dozen customers and ask for more of the same, so you never have to describe your ideal customer in the abstract and hope a filter combination finds them.

You control how close the match is, too.

Keep the similarity high and you get a near-identical list. Go lower and you start seeing patterns in your own customer base that you hadn’t noticed, which is where new segments come from.

Find Similar is available on any paid Hunter plan.

How Find Similar works

Find Similar works across the Hunter platform:

• Records: Click on the name of a contact/company to open the record and go to the Similar leads tab.
• People/Company Leads: Select a number of records by clicking the box next to each row, then Find Similar Leads in the blue toolbar pop up.
• Verifier/Finder results: After finding or verifying a lead, you'll be met by "We found x highly similar profiles..." beneath your results.

Once Find Similar is chosen, the workflow is the same:

1. Refine your results using filters like job title, location, verification status, and the new "similarity score" that ranks.
2. Click Reveal x selected to save your results to a new or existing leads.
3. Click See in leads to go straight to the new contacts.

The quality of the leads that Find Similar gives you depends on the information you give it.

The more consistent the job title or location or company industry, the more precise the lookalikes. You can use this to your advantage to find the right balance of targeting lookalikes and opening the envelope

Throw in every customer you’ve ever had, including the two who were a bad fit, and the results widen to match.

Read the full Find Similar walkthrough in the help center.

15 tips on building and fixing your lead lists

Every play in this section runs the same way:

• You assemble the seed in Leads, usually by tagging the records you want so you can select them in one action, and
• Then you run Find Similar and save the output to its own list.
• What changes between them is which records you pick as the seed, and that is the only decision here that needs any thought.

What changes is which records you pick as the seed, and that's the only decision that needs any thought.

1. Rebuild your ICP from the people who replied

ICP documents are often great in theory, but the reality of prospecting can shape changes, especially when your reply data indicates that you have a change in ICP. Take every contact in your ICP who gave you a positive reply and use those selections to find lookalikes with Find Similar. If the roles, industries, and company sizes don’t match your ICP document you wrote in January, trust the results to test a different direction and use that to update the ICP document.

2. Clone your closed-won list

The usual answer to “get me more customers like our best customers” is a workshop, a spreadsheet, and a week of arguing about firmographics. Tag every account that signed this year and seed from the full set instead. You’re handing Hunter a dozen real customers and asking for more of the same.

3. Turn a “not right now” into a segment

“Interesting, but the timing’s wrong” gets thrown into the abyss and long forgotten - but what if that was a seed for Find Similar? That "not right now" type response is confirmation of interest in your solution, but the timing is wrong. So, go find people who have the buying window that aligns to right now. Build a new list from their record and prospect the segment while you wait for them.

4. Rescue a list that underperformed

You built 500 leads, three replied, and the campaign looks like a write-off. Don't let it become a one-and-done, instead, use this as a way to feed a new list. Our State of Email Outreach 2026 research found lists under 100 recipients pull 158% more replies than lists of 500 or more, so the smaller rebuild has a real chance of beating the original.

5. Expand a single lookup

You ran one Email Finder search for someone you met at a conference, got the address, and moved on. Find Similar sits underneath the result, so that one address becomes a batch of people in the same role at comparable companies before you’ve left the results page.

6. Reach deeper into the buying committee

A list with one contact per company makes one person’s vacation the difference between a deal and silence. This is an important lesson that runs through our Outreach Planner - there are at least four personas to reach inside any one company that open a door to a deal.

Run Find Similar on companies first, then Domain Search each one to pull a second and third name. Emailing two people per company gets a 46% higher reply rate than emailing one, according to the same research, and this builds a list structured that way from the start.

Following a signal from your marketing

These three start outside Leads.

Something happened, a download, a registration, or a click, and you have a small group of people who did it.

Get that group into Hunter as a list, tag it, and seed from the tag. Speed is what matters here, because a three-week-old signal is worth far more than the same signal next quarter.

7. Chase a spike in form completions

A guide you recently published suddenly pulls 4,000 downloads, and 120 of them are operations managers at logistics companies. This many downloads from one job title in one industry is a pattern. Seed from those 120 and build the outbound list while the guide is still pulling downloads. Waiting until next quarter means writing to people whose interest has gone cold.

8. Fill the room for your next event

Take the people who registered for your last webinar and turned up, leaving out the no-shows, because attending is a much stronger signal than registering. Seeding from that group gives you an invite list for the next session based on who shows up.

9. Find out which profile responds before you commit budget

Pick two customers who look nothing like each other and build a lookalike list from each. Send both the same email. Whichever profile replies more is the one to build a campaign around, and the answer cost you two small sends instead of the budget it takes to run that test in paid.

Earning links, mentions, and coverage

Link building runs on people, so these start from an individual record. Open the writer, host, or editor in Leads, go to the Similar leads tab, and keep the similarity setting high. A beat is narrow, and a loose match gives you people who cover something adjacent to your topic rather than your topic.

10. Find more sites like the ones already linking to you

In your backlink profile is a small group of sites that have linked to you more than once, and whose editors reply when you email them. Those relationships took months to build. Seed from those editors to find their counterparts at publications like theirs, which is a better starting point than a scraped list of every site in your category.

11. Get on podcasts like the one that sent you signups

One episode sent you signups for a month, and your only obvious route to the next one is scrolling through charts. Seed from the host’s record and go after the hosts of comparable shows. You already know your story suits the format and that the audience is right, so you already know the format works before you send the pitch.

12. Build a press list from a placement that worked

A journalist covered you and the piece drove real traffic. Their record is the seed for your next press list. Find Similar returns writers on the same beat at similar outlets, so the list is ready weeks before your next announcement.

Seeding from people you don’t sell to

The seed doesn’t have to be a customer, or even someone you want to sell to. Find Similar reads the pattern in a record whether that record is an account on a competitor’s product, a person you hired, or a logo on a client’s wishlist. Where the seed is a company, run Domain Search on the results to turn those companies into named contacts.

13. Build a displacement list from accounts on a competitor’s product

You know a handful of companies using a competitor, whether from a lost deal, a logo on their website, or something mentioned on a call. Seed from those companies to get more like them, then write to them as switchers and ask about the gaps you know that product has. A question about their current setup gets more replies than a pitch, and it tells you whether the gap is one they feel.

14. Find more candidates like the hire who worked out

Look at the best person you hired this year. Their role history, company background, and location form a pattern, and Find Similar reads that pattern the same way it reads a customer. Recruiters doing their own sourcing get a shortlist without going near a job board.

15. Turn a client’s dream logos into their target list on day one

A new client names the three companies they’d love to work with on the kickoff call. Rather than spending week one on manual research, run Find Similar on those three before the call ends, and start the work with a 500-lead target list.

Build better lists with Find Similar Open any list in Leads, select the five leads you’d most like more of, and click Find Similar. Find your next best leads in minutes with Find Similar and get ahead of the pack this September and October. Build Better Leads

With AI being increasingly used for go-to-market, the letters “MCP” have found their way into more LinkedIn, Reddit, and Substack feeds when it comes to lead generation. But why, and should you even care? 

While it sounds like a term that firmly belongs in the developer’s world, if you run your own outreach, it’s time to pay attention. 

Prospecting is changing, and MCP is the key to connecting your Hunter go-to-market data into chat-based prospecting in Claude, ChatGPT, and Perplexity.

The short story:

• An MCP (Model Context Protocol) connection is the standard plug that lets an AI assistant like Claude, ChatGPT, or Perplexity use your Hunter account from a conversation. You ask in plain English, and the assistant does the Hunter work for you, meaning you don’t need to use the Hunter app interface..
• An API is the counter where one piece of software asks another for something specific. Hunter's APIs answer questions like "who works at this company?" and "is this email address safe to send to?"
• The MCP sits in front of Hunter's full API, meaning one connection gives your AI assistant 30+ tools to identify companies, find and verify email addresses, enrich contacts, and manage your leads and email sequences.
• The biggest benefit is that it prevents an AI assistant from hallucinating data. With an MCP connection, every contact comes back found and verified, or flagged as something Hunter couldn't confirm, so you never send to an invented email address.
• The MCP is included in every Hunter plan. Follow these quick start instructions:
• Connect Hunter to Claude by adding the .md file inside a Claude chat
• Connect Hunter to the ChatGPT app by adding the .md file inside a ChatGPT chat

What is an MCP?

MCP stands for Model Context Protocol. It's an open standard, published by Anthropic (the company behind Claude) in 2024, that gives AI assistants one shared way to connect to outside tools and data.

The comparison often used is the wall socket. 

Before wall sockets were standardized, every appliance needed its own wiring job. Now any plug fits any socket, and nobody thinks about it. MCP does the same for AI assistants: any tool that speaks the protocol can connect to any assistant that speaks it, without a custom integration built for each pairing.

This is important because while AI assistants are smart, they lack access to your specific data.

Claude can describe a great-fit customer with ease. But, it cannot identify the companies and verified email addresses of decision makers inside. 

AI assistants’ knowledge stops on the data it is trained on. That’s why you need to connect your hunter.io account as a key to unlock your lead generation.

Once Hunter’s MCPis plugged in, your AI assistant can search companies, find contacts, verify addresses, and save leads using your actual account, with your plan and your credits, from inside the conversation you're already having.

You don't need to understand how the protocol works underneath, any more than you need to understand the wiring behind a socket. 

You set it up once and forget it exists.

What is an API?

An API (Application Programming Interface) is the counter where one piece of software asks another for something specific. It's a published menu of requests the service will answer, each with a defined question and a defined answer. 

Hunter's Email Verifier API, for example, takes one email address and returns a verdict: valid or not, with a confidence score and the detail behind it. 

The Domain Search API takes a company's website and returns the email addresses Hunter has for the people who work there, with sources attached.

APIs are precise, fast, and reliable, which is exactly why products get built on them. 

Unfortunately, APIs have long sat in the world of developers, with the ability to write code an immediate barrier to those less-technically minded.

The MCP eliminates that barrier.

How does an API and MCP work together?

If the Hunter API is the service counter, the MCP server is the translator standing at it on your behalf.

Breaking down the MCP and API
You type something like "find the marketing decision-makers at these 20 companies and verify their email addresses" into Claude. 

Claude decides which tools to use, whether that's a Domain Search, an Email Verifier check, or something else entirely, instead of you needing to think about the right solution. 

The MCP server takes each request and places it at Hunter's API counter in the format the API expects. 

It then collects the responses and hands them back to the assistant, which turns the raw data into the table you actually wanted.

The MCP gives you the access without tech knowledge
The API does the work it has always done, and the MCP adds the translation in front, letting you place orders in plain English instead of code. 

One connection covers the whole counter, because Hunter's MCP exposes the full Hunter API as over 30 individual tools, and the AI assistant picks the right ones for whatever you ask.

Staying in control of your Hunter credit usage
Critically, you remain in control of the credits you use.

In Claude, each tool allows you to set a permission level, so you can let read-only lookups run freely while anything that changes your account or uses credits waits for your approval. 

Verifying an email costs 0.5 credits and saving a lead costs 1 credit, and with the recommended settings, neither happens without you saying yes.

What APIs are available from Hunter?

Since the MCP is a window onto the API, it helps to know what's actually on the menu. 

Hunter's API breaks into groups.

Find companies and people

Discover API
The Discover API finds companies matching your criteria, whether you describe them in natural language or with filters for industry, size, location, and technology, and it's free to call. 

The Email Count endpoint tells you how many addresses Hunter has on file for a company before you spend anything. 

Domain Search API
The Domain Search API returns the email addresses found for a company, with names, roles, and the public sources each one came from (1 credit per 1-10 addresses). 

Domain Search API
The Email Finder API takes a person's name and their company's website and returns their most likely professional address with a confidence score (1 credit).

Verify and enrich data

Email Verifier API
The Email Verifier API checks if an address is deliverable and returns a status and score, at 0.5 credits per check. It ensures you find verified and accept-all data to improve your bounce rate.

Lead Enrichment API
Lead Enrichment turns an email address into a person: name, role, location, and social profiles. You can try the same lookup for free, one address at a time, with the Reverse Email Lookup.

Company Enrichment API
Company Enrichment turns a website into company detail: industry, size, description, and the technology it runs on. 

Combined Enrichment API
Combined Enrichment does both from a single address. Each costs 0.2 credits, and only when the core data actually comes back.

If you used Clearbit for enrichment before it was folded into HubSpot, Hunter's API works as a direct replacement, down to a Clearbit-format response option. 

Logo API
The free Logo API returns any company's logo from its website address, ready to be used in your CRM, landing pages, dashboards, or product.

Manage leads and send emails

Leads API
The Leads API and its neighbors (Lead Lists, Custom Attributes) let you save, organize, and update the contacts you've found. 

This enables you to segment your contacts and companies based on criteria like location, technology, owner, or whatever attribute you choose.

Sequences API
The Sequences API adds recipients to your outreach sequences and starts them. 

API key basics

If you want to go deeper, the full API documentation covers every endpoint with examples. 

Your API key lives at hunter.io/api-keys, and it should be treated the same as any password, meaning you never share it or paste it anywhere public. 

An Account endpoint reports your plan, credits, and usage, free of charge, which is how your AI assistant can tell you whether a big job fits your remaining credits before it starts.

For experimenting without spending credits, the special key test-api-key returns dummy responses on the Domain Search, Email Finder, and Email Verifier endpoints. 

If you connect through Claude's connector settings or the ChatGPT app, you may never touch a key at all, because the connection uses OAuth: you log in on Hunter's own page, and the assistant never sees or stores your password.

How is the Hunter MCP being used?

If you're handling go-to-market by yourself, the MCP can be the foundation for an entire Claude prospecting workflow. 

Claude can act as a research agent, identifying great-fit companies, finding the contacts with decision-making power, and then using Hunter to get their verified email addresses. 

Users work this way because it blends high-quality, trustworthy data with less context switching and browser hopping, the kind that wastes time and pulls you away from other work. 

The AI assistant does the reasoning, Hunter gives it the data you can trust, and you can work on something else all the while you’re running your lead generation. 

Here's what that can look like in each assistant.

If you're handling go-to-market by yourself, the MCP can be the foundation for an entire Claude prospecting workflow. 

Claude can act as a research agent, identifying great-fit companies, finding the contacts with decision-making power, and then using Hunter to get their verified email addresses. 

Users work this way because it blends high-quality, trustworthy data with less context switching and browser hopping, the kind that wastes time and pulls you away from other work. 

The AI assistant does the reasoning, Hunter gives it the data you can trust, and you can work on something else all the while you’re running your lead generation. 

Here's what that can look like in each assistant.

Claude

Claude's strength is reasoning over everything at once. 

Paste in the websites of customers you've already closed and ask it to work out the profile they share, then have Hunter find companies matching that pattern. 

Ask it to score every match against the profile with a reason per score. 

Then, have Hunter turn the top companies into named decision-makers with verified addresses, and finish with a one-line outreach hook per contact. 

Claude can even build the results into an interactive account-scoring sheet you can sort, edit, and reopen later. 

The connector works on Claude's Free, Pro, and Max plans, and on the Free plan Hunter can be the one custom connector you're allowed.

Click here to learn more about Claude x Hunter.

ChatGPT

The Hunter ChatGPT app suits starting from a customer you already win with. 

Give it one website and ask for lookalike companies, and Hunter Discover returns a ranked list with the number of addresses on file for each. 

Narrow it in a sentence ("just the European ones"), ask which recently raised money or are hiring, then run a Domain Search to get named contacts with verification statuses, and have it draft a three-sentence opener for the first one. 

The process runs on ChatGPT's free plan; you call the app by typing @ and then Hunter.

Click here to learn more about ChatGPT x Hunter.

Perplexity

Perplexity reads the open web as it is today and cites where each claim came from, so it's great to use when you're building a lead list from start, for instance with companies that raised this quarter.

It builds the market map with sources attached, reasons about which companies fit what you sell, and then hands the qualified list to Hunter for named contacts and verified addresses. 

One thing to know upfront is that custom connectors need a paid Perplexity plan, Pro or higher, so the free tier can't add Hunter yet.

Click here to use Hunter in Perplexity.

Prompts to test your MCP

Whatever your AI assistant, once set up, try these prompts:

• "Before we start, pull my Hunter account details: the plan I'm on, what I've used this month, and what's left. Then estimate what this job will use and tell me whether it fits."
• "These are deals I lost a year ago and want another run at. Verify each contact's email with Hunter. Where an address comes back invalid, the person has probably moved on, so run a Domain Search on the company and find whoever now holds the role."
• "Pull the stats for every sequence I sent this quarter and rank them by reply rate. Name the winner and the loser, and tell me what separated them."

Why use Hunter's MCP?

Broadly, the Hunter MCP will enable you to trust the business data you're using to orchestrate outbound in an AI assistant:

More specifically, the MCP's benefits spread across four areas:

1) Data hallucinations
Ask an AI assistant for someone's email address and it will often produce one that looks right and doesn't exist, because guessing plausible text is what these models do. 

Send to enough of those and your bounce rate climbs, and past 2% your sender reputation starts paying for it. 

With the MCP connected, the assistant's answers come from Hunter's records instead of its imagination. 

Addresses arrive with a verification status and confidence score, accept-all servers get flagged as the warning they are, and where Hunter has nothing, it says "no data" rather than inventing a name. 

Knowing exactly which contacts you can send to today, and which need more work first, is the whole game in deliverability.

2) Limit context switching
The old productivity loop was research in one window, Hunter in another, a spreadsheet in a third, and CSV exports moving the same names between them. 

Contact data goes stale quickly (22% of email data decays each year), so every manual hop is also a chance for the list to age before you use it. 

With the MCP in place, a contact moves from research to a verified leads list to a sequence inside one conversation, and the re-verify step is a sentence, not an export.

3) No added cost
The MCP connection costs nothing extra. It's included in every Hunter plan, your existing credits and limits apply, and a free Hunter account works from day one. 

4) You're in control
Unlike AI assistants, whose token usage is something you have to actively control by selecting a different model, reasoning level, and/or choose to use the assistant in a browser/desktop app, the Hunter MCP gives you full control over Hunter credit usage. 

It's built to keep you in control, with OAuth sign-in and per-tool permissions, so the assistant asks before it does anything that spends credits or changes your account.

Go beyond the MCP

The MCP is the newest door into Hunter's API, but far from the only one. In fact, Hunter’s API is being used to grow businesses across outreach, products, and marketing experiences.

Build products
Vocations, a job-signal platform for recruiters, uses the Email Finder API to power the contact feature at the heart of its product. The integration went live in a day, and today its 300 daily users find around 1,500 decision-makers through it.

Make verification part of the prospecting routine
Modgility, a RevOps consultancy with a two-person sales team, builds lists of companies running HubSpot, verifies the contacts, and runs targeted sequences. That outbound accounts for 25% of their new business.

Feed your CRM
WebFootprint, a software agency selling to fewer than 200 possible buyers nationwide, pipes Hunter's data into a custom CRM, where it fills every company and contact record and surfaces new hires at target accounts automatically.

The founder puts the savings at an hour a day, and he's been a Hunter customer since 2016.

Those are very different businesses placing orders at the same counter. 

The MCP simply means you no longer need an engineering background to place one yourself.

Use the Hunter MCP

The fastest way to connect Hunter is fitting - let the AI assistant handle its own setup.

We've written step-by-step instructions designed to be pasted directly into a chat. 

The assistant reads them, greets you, and walks you through the whole connection one confirmation at a time, from checking you have a Hunter account through to running your first real prompt.

 You won't have to figure anything out on your own.

• Claude: Copy the Hunter for Claude setup instructions here into a new Claude chat.
• ChatGPT: Copy the Hunter for ChatGPT setup instructions here into a new ChatGPT chat.
• Perplexity: On a Pro plan or higher, add Hunter as a custom connector, then run your first market map.

The setup takes five minutes, and the next time you need a list built, checked, and saved, you'll do it without opening a single extra tab.

Learn more about the MCP

To learn more about the MCP, APIs, and Hunter in your AI assistant, visit our help center content below:

• How to connect Hunter to Claude with MCP, the full walkthrough with screenshots, including the API-key route for Claude Team members without admin rights.
• The Hunter API, every endpoint with credit costs and rate limits.
• Can I use a test API key? for experimenting without spending credits.
• How to verify emails via API, with code examples, if you're ready to write a little code.
• Which plan is right for me? on choosing between the All-in-One Outreach plans and the Data Platform plans.

MCP FAQs

Do I need a paid Hunter plan to use the MCP?

No. The connection works with every Hunter plan, including free accounts. Your existing credits and request limits apply, and some actions use credits, like verifying an email (0.5 credits) or saving a lead (1 credit).

Do I need to be a developer?

Not for the MCP. Connecting through Claude's settings or the ChatGPT app is a few clicks plus a Hunter login, and from then on everything happens in plain English. The API itself is the developer route, for building Hunter's data into a product or an internal system.

What's the difference between the Hunter MCP and the Hunter API?

The API is the underlying service: the set of requests Hunter answers, from Domain Search through to Sequences. The MCP puts a translation in front of that API so an AI assistant can use it through conversation. It's the same data and the same credits, reached a different way.

Which AI assistants does it work with?

Claude (web, desktop, and Claude Code), ChatGPT via the Hunter app, Perplexity on its paid plans, and any other assistant that supports MCP connectors.

Is my data secure?

The connection runs through Hunter's official MCP server using OAuth, meaning you log in on Hunter's own page and the assistant never stores your password. The assistant only accesses your Hunter data within the permissions you grant, and you can revoke the connection at any time.

What can the assistant actually do once connected?

The connection covers the full Hunter API in over 30 tools: Discover, Domain Search, the Email Finder, the Email Verifier, person and company enrichment, Leads with lists, tags, and custom attributes, message templates, and Sequences through to their statistics.

Will the assistant spend my credits without asking?

Not if you set it up the recommended way. Hunter suggests leaving read-only tools free to run while setting anything that writes or spends to "needs approval," so every credit-using action waits for your yes.

When you’ve received an inbound lead and prep for a call, it’s likely the lead’s information is incomplete or, at worst, missing.

With this prompt for ChatGPT or Claude, you can use Hunter to prepare for your sales call and stand out for all the right reasons with your lead.

Why this matters

Pre-call research gets skipped because it can feel like another admin task. But, there are risks with not thoroughly preparing for a call. 

Those reasons are endless, but can vary from the email address is wrong, or the person no longer works at the company, to not realizing that additional attendees are added to your call, - and you could have known enough about them to alter your talk track.

You find out afterward, if you find out at all.

The research that gets done before a call is the research that fits into a coffee break. Anything longer gets postponed until the meeting has already happened. For one unfamiliar address on the invite, that’s plenty of time. Paste it into a reverse email search and you’ll see who it belongs to, with their job title and company, in seconds.

Here's how to build that briefing in your AI assistant with Hunter.

Your plan

• What you'll achieve: A view of who matters in the department you're meeting, verified email addresses for the handful worth contacting, and a first draft of your outreach that doesn't announce itself as machine-written.
• Where this runs: In ChatGPT or Claude, using the Hunter connector. The prompts below are identical in both, so use whichever you already have open.
• What it costs: Hunter can be used in your AI assistant as part of your Hunter plan. Credit-based actions like finding and verifying addresses use your account balance.
• Time to complete: 15 minutes.
• When to run this play: You have a call booked and you need to run research.
• When to run another play: You already know the room and only need the follow-up written, so skip to Step 3.

Step 1: Connect Hunter to your AI assistant

Use the guide below to know where you to place your next step:

Connect Hunter to whichever AI assistant you use. 

Setup takes five minutes:

• Read the ChatGPT guide
• Read the Claude guide.

Have one useful thing ready to send to the contacts you’ll find.

A benchmark or a short case study that answers a question they're likely to have. 

You'll need this asset in Step 3, and picking it in the moment is how people end up attaching nothing.

Learn more about using different lead magnets with our outreach planner

Step 2: Build the briefing

Open your AI assistant and enter the below, replacing the placeholders:

I have a call with {{company_name}} tomorrow about {{reason for call}} . Pull together a briefing: find the company's website and key details, identify the decision-makers in {{department}} (especially anyone with “{{seniority_level}}” in their title), verify their email addresses, and surface any recent context I should know.

Here's an example prompt for prepping for a call with a marketer from Forrester about their design requirements:

Two things to be wary of:

• Ensure you have the right department: This can be an issue when a company splits Growth and Marketing, or runs RevOps separately from Sales. Tell your AI assistant which one you're meeting.
• Someone you know is joining doesn't appear in the results: Name them and ask the AI assistant to find and verify them too.

Review the results of the initial company snapshot:

Because you gave the AI context on the call, it will provide initial research that you can bring into your conversation:

With this information, you'll then receive a digest of how your solution fits into their stance on AI GTM:

Step 3: Verify and save only who you need

With the results returned from your AI assistant, review the list of contacts and the advice that Hunter provides you:

Hunter will, if appropriate, suggest a second contact that could be useful to broaden your preparation:

Use this prompt to select the leads you want to save from this search:

Save the verified contacts to a new Hunter Leads list called {{list_name}}, and tell me how many credits that will use before you do it. For anyone in {{department}} without a verified address, run a Domain Search and tell me who holds the role now.

Remember, you really need one-two people, maximum, to drive your chances of a reply rate up.

Before saving the contacts, the AI assistant will ask for permission:

Ask the AI assistant to flag anyone whose address comes back as accept-all rather than valid.

Those aren't wrong, but they bounce far more often than verified addresses, so keep them out of anything that matters before a meeting.with our outreach planner

Follow the URL and you'll see your saved list inside your Hunter account:

Step 4: Draft the outreach

Now enter the below prompt for assistance in writing your messages to the leads.

Write two drafts to send before the call - one for [person 1], one for [person 2], and one for [person 3]: an email under 100 words and a LinkedIn note under 60. Both should reference the meeting and share a link to our portfolio of example work at www.aidified.io/work. Ensure that the email is relevant to the contact's job title and leverages the pre-call preparation you have helped me generate. If you make an observation that comes from from the research, ensure it's a natural connection between this observation and the connection to my work. Rules: no em dashes, no “it's not X, it's Y” constructions, no phrases like “in today's landscape” or “let's dive in”, and no words like “resonate” or “leverage”.  Use contractions. American English. Ask one question at the end, not three. 

Personalized for this campaign, we'll add the below context:

Next, review each of the email and LinkedIn requests generated. Ensure that they're personal to the lead, and manually edit where necessary:

It’s important to ensure your messages are relevant to the lead, as 69% of decision makers are bothered when your content shows signs of AI. Don’t make the use of AI blind them of your value and dismiss you before you can talk to them.

Use LinkedIn as a follow-up channel, referencing your email, to give the lead a choice of where they want to engage with you.

Once the content is edited, you can send these messages through Sequences, naming each Sequence as the person's name + Forrester pre-call intro.

What this looks like when it's working

You join the call already knowing who the other three people are, you've shared examples of your work and tied this into their stance on AI, and you come across as prepared, thoughtful, and professional.

Your follow-up goes out the same afternoon to addresses that work, and it sounds like you.

If the briefing comes back thin, that usually means a small company with little public footprint. 

Run Step 2 anyway, since a verified address for one person beats a rich profile of nobody.

Put all of this into action today with Hunter's Outreach Planner:

Reading this in the summer? You have until Labor Day to get your lists ready if your recipients are in the Americas.

We analyzed 5 years worth of data and yes: there is some seasonality to email outreach.

However:

• The effect is smaller than you might suspect,
• It depends on the region you operate in, and
• You should still send outreach year-round.

In this article, we'll show you what we found and what you need to do about it to maximize replies throughout the year.

How we measured it

We looked at 14,500 senders and 86,000 sender-months from 2021 through 2025: sales teams, agencies, recruiters, and PR.

The context:

• Average reply rates have been dropping. Blame channel saturation or stricter spam filtering. Either way, the average sender's reply rate fell by roughly 45% over these five years, so we can't naively compare reply rates per month.
• The mix of senders changes constantly, and a few outliers can drag a month's average around on their own.

We accounted for it:

• Every sender is compared only to themselves. October is "good" if senders did better than their own typical month (on average).
• The overall decline in reply rates is accounted for before months get judged.
• One sender, one vote, whether you sent 60 emails or 300,000 that month.
• A month only counts if it repeats. One great October proves nothing. Five in a row is a pattern.

What five years of data says

If you're sending in the Americas, don't sleep on the September-October window. October wins even though it sits inside the busiest sending period of the year.

September-October was the best window to send from 2021-2025, with about 8% more replies in October than the average sender's normal. To put that in real terms: if your usual reply rate is 2.5%, October may bring in about 2.7%. Not groundbreaking, but worth planning around.

Then the window shuts toward the end of Q4... as expected. November and December came in below normal in 4 of the last 5 years, at about -5%.

If your recipients are in Europe, the calendar is more of an excuse. No month was dependably good or bad for EMEA senders in five years. Even the sacred August-holiday intuition doesn't show up reliably in the data.

Asia-Pacific is messier. October was above normal there in all five years too, so the autumn window seems to carry over. But treat the region's averages with care: January looked like APAC's best month for four years, then came in well below normal in early 2026. APAC is our smallest sample, too.

One caveat before you circle October on the calendar: the direction repeats, the magnitude doesn't. October's edge ranged from +4-16% depending on the year. Treat these as tendencies, not guarantees.

Everyone shows up a month late

When we charted send volume against reply rates week by week, the two peaks don't line up.

Reply rates peak from late September through the first week of November. Send volume peaks in mid-November, right after replies fall off a cliff.

January is the mirror image. The first weeks of the year get less volume than an average week, while the people you're writing to are already back at their desks. December's quiet inbox everyone plans around? It actually happens in the first half of January, and almost nobody uses it.

Best for replies ≠ most important

This is where I'll argue against our own data.

October being your best reply month doesn't make it your most important sending month. That depends on your sales cycle, your industry, and when you actually need the revenue.

Do the math backwards. If your sales cycle is 90 days, replies you get in October become deals that close in January.

The same math works for recruiting: with a 60-day time-to-fill, October outreach fills January seats.

And if you run campaigns for clients, the "important month" is different for every account on your book.

The easy months and the important months are usually different months. And if you carry a quota, you already know that an easy quarter isn't where your effort should go.

The salesperson who looked relaxed in March did the work in November, when reply rates were at their worst and everyone else had mentally checked out.

Which is the real lesson here: email outreach builds pipeline. Closing happens somewhere else, on someone else's timeline.

What do you do with the strong months?

An 8% better month pays in proportion to what you send, and sending capacity is the one thing you can't create overnight. A new email account needs weeks of warmup before it can carry real volume, and a new domain needs longer. If you want more mailboxes working for you in October, they need to exist by August. You can buy domains and email accounts right inside Hunter, preconfigured for cold outreach, so the setup doesn't eat your September.

Then there's the list itself. Build it early and run it through Email Verifier, because extra volume on an unverified list just means extra bounces at the worst possible time, when your fresh accounts are still earning their reputation.

The window multiplies whatever you bring into it. Bring more.

What do you do with the weak months?

Not nothing.

The data says November and December replies are harder to get with the same playbook everyone else is running. But:

• It doesn't say recipients stop being people.
• The drop didn't happen every single year.
• At worst, the reply rate is about 10 points lower.

Send something with no ask. A useful benchmark, or a genuinely relevant "this reminded me of your launch" note. A December email has one job: to make January's email warm.

Book Q1 while everyone else chases Q4. "Let's talk in January" is an easy yes in a month when every other email is begging for 15 minutes before the holidays.

And do the unglamorous work. Build your lists and verify them. If you send at volume, this is also the time to warm up mailboxes and test copy on small batches. The mid-September window rewards whoever prepared in August. The January restart rewards whoever prepared in December.

This is exactly what we built the Outreach Planner for: a free 12-month calendar that gives every month a job, telling you which weeks to build, verify, warm up, and push, and what angle fits the season when the default pitch stops working. It exists so you don't send the same email in week 50 that you sent in week 38 and expect week-38 results.

The one-line version

If your market is in the Americas, the six weeks from mid-September to the end of October are the best sending window in five years of data. Plan so your lists are ready before it opens. Everywhere else, and every other month, the calendar is a tiebreaker.

Because the best month in five years of data buys you +8%. A better list, a sharper offer, and a healthy sending setup are worth multiples of that in any month.

The calendar decides when replies come easy. Whether your email deserves one is up to you.

At Hunter, we've been skeptical about AI taking over outbound.

Turns out we were right. And wrong.

Right, because it never took over. Outbound doesn't run itself even with AI.

Wrong, because AI gradually got good enough to assist with every part of the process: building lists, verifying contacts, writing sequences, analyzing what worked.

Autonomous SDRs have been the wrong direction for applying this technology. MCPs have proven themselves to be the right direction: a skilled human operator assisted by AI enabled by data, using an outreach platform via MCP.

And the operator's "skill" has nothing to do with the technicalities of outbound anymore. It has everything to do with understanding the business, the customer, and the strategy.

This guide covers AI lead generation, or how we at Hunter think you should think about applying AI to email outreach.

What is AI lead generation?

AI lead generation means using natural language with AI enabled by live data to automate how you find leads, verify their contact information, and reach out to them.

You describe who you want to reach and why; the AI executes the steps that used to be manual. You give examples of sequences that worked before; AI scales them to other industries in minutes. You say that you want to find low-hanging fruit in your lead list; AI, informed by your strategy, finds leads to contact next week.

AI doesn't replace your judgment or act autonomously on the critical parts of the process. It's just a tool, the same way your CRM is a tool. It just happens to be a tool you can talk to.

AI lead generation covers most of the lead generation workload:

• Building a strategy to find and acquire customers
• Analyzing competitors and adjacent markets for targeting ideas
• Mining your CRM for patterns and missed opportunities
• Creating lead magnets and content around target accounts
• Running email outreach and follow-ups
• Closing the loop: analyzing what worked and deciding what to test next
• Pre-call research and meeting notes

If all you have at this point is doubt about whether this can really work at all, consider two things:

First, context. You can point an LLM at your website, your messaging, your case studies, or your past campaigns, and it will work from your reality instead of internet averages. It can even learn from your unrelated chats. If you're a founder working with AI on all the other parts of your business, it already knows where your value gap sits and who you're building for.

Second, data. LLMs don't know anyone's email address. They were never trained on verified contact data, and they never will be for privacy reasons. Connect it to a source that actually knows (this is where Hunter comes in), and the model's reasoning finally has facts to use.

How is AI lead generation different from traditional prospecting?

Traditional outbound has always been capped by human capacity. Every step was somebody's hours. Want more pipeline? Hire more SDRs, buy more tools, define more process. And everything stops when the workday does.

Not only that, AI doesn't suffer from the limiting beliefs you or your team may hold about who you should be contacting and what's possible with email. While it won't outsmart you about your own business, it can act like a consultant, providing alternative perspectives about anything from markets to prioritize to what your follow-ups should say.

With AI, the steps are the same ones sales teams have always run. What changes is that one operator can now do more, and the parts that don't require judgment no longer wait for you to be at your desk.

How to set up AI lead generation with Hunter

The setup for AI lead gen is smaller than you'd expect. You need a Hunter account, and an account with ChatGPT or Claude or Perplexity—or a custom setup using the Hunter API if you prefer.

Step 1: Connect Hunter to your AI

Pick the route that matches where you work:

• ChatGPT: install the Hunter app
• Claude: add the Hunter plugin
• Perplexity, or any other client that speaks MCP: connect Hunter's MCP
• Custom setups: the Hunter API directly

Once connected, Hunter's search, verification, enrichment, and campaign tools are available in every conversation. No exports, no tab-switching.

Step 2: Run your first tasks in conversation

Here are 7 starter prompts, each a real task off your plate today. This will show you what's possible:

1. Build a link-building prospect list: "Find sites and blogs in [niche], based in [location], that publish content about [topic]. Find and verify the email addresses of their editorial or marketing contacts and return the results as a list."
2. Find the right editor to pitch: "I want to pitch [story angle] to [publication]. Search Hunter for editorial contacts there and identify the most relevant person based on title and beat."
3. Enrich a contact list: "For this list of companies and contacts, find and verify each email address with its confidence score. Mark anything you can't verify as 'not found'."
4. Verify a list before sending: "Run each address below through the Email Verifier and flag anything risky or undeliverable."
5. Qualify an inbound lead: "Look up the domain of this email address, verify it, and find related contacts at the company."
6. Prep for a sales call: "I have a call with [company] today. Find the key decision makers I should know about before speaking with [contact name]."
7. Analyze your outreach: "Look at [campaigns] in Hunter and tell me what's working, what isn't, and define an A/B test for the subject line of the next sequence."

If a prompt returns something you'd have spent an hour on, you've just confirmed the whole premise.

Step 3: Turn what works into routines

When a prompt earns its third run, stop retyping it. Save it as a Skill (Claude), a GPT (ChatGPT), or a Gem (Gemini): reusable instructions with your rules baked in—"verified or accept-all addresses only," "always find at least 2 contacts per company," "never start a sequence without my approval."

Then give those instructions a schedule in an agent environment (Claude's Cowork, ChatGPT's workspace agents, Perplexity's Computer) and add your context: ICP, messaging, case studies, past campaign results. Budget 2-3 hours for this, once. From then on, the routine runs while you work on something else, and pings you when a decision needs a human.

That's the full architecture: a connection, a handful of prompts you trust, and a schedule.

What the Hunter MCP is capable of

The easy assumption about "Hunter in your AI" is that it's a search box: ask for an email address, get an email address.

It's closer to handing your AI the keys to the platform. Connected via MCP, your LLM can operate every stage of the outbound workflow through plain conversation:

• Search the B2B database. Describe companies in natural language—"fintech startups in France with 11-50 employees"—and get matching companies from Discover. Before spending anything, the AI can check how many named contacts Hunter holds at each company, so you size a prospecting batch before committing to it.
• Get and verify contacts. Pull the published contacts at any domain, filtered by department or seniority. Find a specific person from a name and a domain. Verify any address and get its deliverability status with a confidence score.
• Enrich people and companies. From an email address or a LinkedIn handle: role, company, industry, headcount, technologies used, funding, social profiles.
• Manage your leads. Create leads and lists, tag and segment them, add custom attributes, move and merge in bulk. Existing leads are never overwritten.
• Run sequences. Draft multi-step campaigns, set follow-up delays and sending windows, add recipients, start, pause, resume—and pull per-sequence stats to see what worked.
• Sync your stack. Push leads to HubSpot, Salesforce, Pipedrive, or Zoho. Check your plan, credit balance, and usage before kicking off a batch.

Notice what this means: the AI can take real actions with real consequences. Which is why the guardrails live in the MCP itself, not in a prompt asking the model to be careful.

Every operation is labeled free or credit-consuming, and credits are only charged when Hunter actually finds something. Bulk operations return a cost estimate and stop until you approve it. Deletes state the affected count and wait for confirmation. And starting a sequence—the moment real emails go to real people—always requires an explicit yes from you. Not because the model promised to check in, but because the API won't act without it.

The model brings the reasoning. The MCP brings the facts—and the brakes.

The benefits of AI lead generation

1. Better leads, not just faster leads

Here are some examples of when this is true:

Every address gets verified before it enters a list, because verification is part of the routine, not a cleanup you run when bounce rates scare you.

Prioritization runs on evidence—engagement from past campaigns, companies that match your best customers—instead of whoever happened to look promising that morning.

And every email draft starts from enrichment data about the actual company, which is the difference between personalization and a first-name merge tag.

2. The math works at any scale

If you're currently paying an agency or considering an SDR hire, the comparison is short: an agency retainer runs thousands per month and the cost-per-lead is hard to sustain unless your contract values are high. Hunter plus an LLM subscription is a rounding error next to that.

But the math also works if you're comparing against doing it yourself by hand. Even at 30 emails a month, research, verification, and enrichment eat most of the hours—and those are exactly the steps the AI takes over. You keep the parts that were never the bottleneck: judgment and conversations.

There's a quieter saving too. When an agency relationship ends, everything it learned about your market walks out the door. Skills, prompts, and context files stay yours.

3. You prospect where you already work

Hunter has always followed this principle. The Chrome extension, the CRM integrations... and the MCP extends it to your AI.

In the app, you have to know Hunter to use Hunter: which feature does what, in which order. In a conversation with your agent, you describe the outcome ("50 marketing directors at US SaaS companies under 100 people, verified emails only") and the AI translates. Your strategy docs, your ICP, your past conversations about what worked are all context the AI carries into execution.

The limits of AI lead generation

1. You're still needed

In a chat, you're present for every step by definition. An agent reduces that, but doesn't remove it: it SHOULD stop and ask before consuming credits, before modifying your lists, and before sending anything. An agent that emails people without your explicit yes is a liability.

So budget real time for review. The work shifts from doing to checking, but it doesn't disappear.

2. Hallucination, or why the data layer isn't optional

An LLM's context window is its working memory, and it's finite. Long lead-gen conversations outgrow it, older details fall away, and when the model is missing a fact, it doesn't say "I don't know." It fills the gap. In lead generation this is fatal.

3. AI slop

Models are trained on averages, and the email outreach average is terrible. Left unshaped, AI reproduces the clichés it learned from: "I hope this email finds you well," fake personalization, the pitch that sounds like every other pitch in the inbox.

Recipients don't care whether you used AI. They care whether it reads like AI. Feed it examples of your actual writing, and consider a Skill that checks every draft against a cliché list before you ever see it.

4. Models change under you

Providers update models constantly, and output quality shifts with them—usually for the better, sometimes just differently in ways that matter for your copy.

Get started with Hunter in your AI

Your AI can now run every mechanical step of outbound through plain conversation, on real data instead of confident guesses. It stops and asks before anything that spends money or reaches a human. Which means the only irreplaceable skill left in lead generation is the one you already have: knowing your business, your customer, and your strategy. Try running your next Sequence with AI, enabled with the Hunter MCP.

Connect Hunter to your AI:

• Hunter in ChatGPT
• Hunter in Claude
• Hunter in Perplexity
• Hunter's MCP

Go deeper on specific use cases:

• How to prospect inside ChatGPT with Hunter
• How to use Hunter with Claude for prospecting
• Research-led prospecting with Hunter and Perplexity
• How to use AI in your cold emails
• How to predict the responses to your outreach
• How to use Hunter's AI email writing assistant
• How to use AI in Hunter's B2B database
• How to analyze your emails with AI

Building something custom:

• API overview
• API documentation
• Your API keys

AI outbound glossary

Whether you're new to AI or experienced, here's a quick reference to the terms used throughout this guide.

Agent (AI agent): An AI that completes multi-step tasks on its own. It plans the steps, uses tools like Hunter or your browser, checks its own results, and comes back to you when it needs a decision. A chat answers questions; an agent does jobs.

Agentic AI: The shift from AI you prompt line by line to AI that works semi-autonomously. In lead generation, that means handing an agent the whole process, from finding companies through to sending sequences, instead of prompting each step yourself.

AI SDR: An agent doing the job of a sales development rep: researching accounts, finding contacts, writing outreach, and booking meetings. The best-known examples work inbound leads; outbound AI SDRs exist too, and need closer supervision.

AI slop: Generic, low-effort AI output that shows up as recycled phrases in cold email ("I hope this finds you well"), fake personalization, and copy that sounds like everyone else's. Recipients rarely object to AI itself, only to email that reads like it.

API (application programming interface): The way software talks to other software. Hunter's API lets an agent search, verify, and enrich data directly, with no one clicking through the app.

Connector: A pre-built link between your AI and another tool, such as Hunter, your CRM, or Google Drive. Once connected, the AI can read from and act in that tool during a conversation or an agent run.

Context window: An LLM's working memory - everything it can see in the current conversation, including your prompts, your files, and its own replies. Once a conversation outgrows the window, older detail falls away, which is why long lead-gen chats can lose the plot.

Deliverability: Whether your emails reach the inbox rather than the spam folder. Bounces from unverified addresses damage your sender reputation, which is why you verify before you send.

Enrichment: Adding useful data to a bare contact or company record: role, headcount, industry, technologies used, funding, and so on. Agents rely on enriched data to write emails that reference something real about the recipient.

Firmographics: The company equivalent of demographics - industry, size, location, revenue, and structure. These are the filters you'd use to describe your ICP to an agent.

Frontier LLM: The most capable class of AI models available at any given time. Claude, ChatGPT, Gemini, Perplexity, and Grok all qualify today. The frontier moves quickly, so this year's leading model becomes next year's baseline.

Gemini Gems: Google's answer to Claude Skills and ChatGPT GPTs which is a saved version of Gemini with your own instructions and files attached, so it behaves the same way every time you run a task. Useful for repeatable outbound jobs like list checks or email reviews.

GTM (go-to-market): Everything involved in getting your product to customers: positioning, marketing, sales, and pricing. "AI in GTM" can cover any of it; this guide focuses on the lead generation slice.

Guardrails: The limits you set on what an agent can do without you. For example: verify every address before saving it, never send an email without approval, or cap daily sending volume. Good guardrails are what make semi-autonomous outreach safe.

Hallucination: When an LLM states something false with complete confidence, including invented email addresses and contact details. This is why lead generation needs a real data source behind the AI: the model does the reasoning while a database like Hunter's supplies the facts.

Human-in-the-loop: A setup where the agent does the work and a person approves the moments that matter, usually list quality and the final send. It's the practical middle ground between manual prospecting and full autopilot.

ICP (ideal customer profile): A definition of the companies most likely to buy from you, usually written in firmographics plus context like growth stage or tech stack. The sharper your ICP, the better an agent can prospect on your behalf.

Intent signals (buying signals): Evidence that a company may be ready to buy: hiring for relevant roles, raising funding, or recently incorporating. Hunter's Signals tracks these so you can decide who to contact first.

LLM (large language model): The type of AI model behind Claude, ChatGPT, and the rest. Trained on enormous amounts of text to understand and generate language, which is what lets you run lead generation through plain conversation.

.md file (Markdown file): Is a file that you can upload to your AI assistant to give direct, explicit directions (and expectations) of how you want an LLM to perform a task.

MCP (Model Context Protocol): An open standard that lets an AI connect to outside tools and data. Installing Hunter's MCP gives your AI direct access to Hunter's search, verification, and enrichment, whether you're chatting or an agent is running on its own.

Prompt: The instruction you give an AI. A good lead-gen prompt covers the role you want it to play, the goal, the context to use, and the task itself. Vague prompt in, generic leads out.

RAG (retrieval-augmented generation): A technique where the AI looks information up from an approved source before answering, rather than relying on memory. It reduces hallucinations but takes technical setup, which is why most founders get a similar benefit by connecting a verified data source like Hunter instead.

Skills (Claude) / GPTs (ChatGPT): Saved, reusable instructions your AI follows every time it runs a certain task. One example from this guide: a skill that checks every drafted cold email against a list of AI cliches before you ever see it.

Token: The unit LLMs use to process text, roughly three-quarters of a word. Usage and pricing are measured in tokens, and every conversation has a token budget tied to the context window.

Training data / knowledge cutoff: The text a model learned from, which stops at a fixed date. Training data doesn't contain current, verified contact details, and it never will. That gap is exactly what live data connections exist to fill.

Verification (email verification): Checking that an email address exists and accepts mail before you send to it. Statuses like valid, accept-all, and undeliverable tell you which contacts are safe to reach.

Perplexity is good at one thing prospecting tools are not: it reads the open web as it is today and shows you where each claim came from. Ask it what happened this quarter and it answers with a cited list, not a snapshot from a database that was refreshed six months ago.

Even compared to other AI assistants like Claude or ChatGPT, it "likes" accessing the web with an extended suite of tools to find information for you.

What it cannot do is what Hunter does—surface verified contact information and send outreach sequences optimized for deliverabity. It knows a startup raised money last month, but it does not know the name of the head of growth or whether their email is safe to send to. Hunter fills that gap. Connect the two and a fresh market signal becomes a verified, contactable person, with the sources still attached.

This AI GTM walkthrough covers using Hunter in Perplexity for your prospecting.

One thing to be clear about before you start: connecting Hunter to Perplexity requires a paid Perplexity subscription. Custom connectors are only available on Perplexity's paid plans, Pro or higher. A free Perplexity account cannot add Hunter at all, so if you are on the free plan this workflow is not open to you yet.

Here is how to connect Hunter to Perplexity.

Build a market map from live signals

Static databases don't reflect reality. This is why the idea of data provenance is increasingly important with the use of AI. Hunter helps you find the most accurate, up to date GTM data for your prospecting.

When you want companies that did something in the last few weeks, you need a tool that reads the web now and shows its sources.

That is what this step is for: you describe the signal you care about, and Perplexity returns a market map built from current, cited results rather than a stale export. Because the sources stay attached, you can check any entry before you act on it.

Try: "Find companies that [meet a recent trigger, for example raised a Series A this quarter]. Include sources."

A live market map built from cited web results, not a stale export.

Enrich with ICP fit reasoning

A list of names is not a lead list.

Before you spend a lookup on contacts, it helps to know which of these companies actually fit what you sell, and why.

Perplexity can reason over the same list and add that judgement company by company, so you qualify the list first.

The sources stay visible, so the reasoning is something you can check rather than take on faith.

Try: "For each, add what they do and why they'd be a fit for [what you sell]."

Qualify the list before you spend a lookup, with the sources still attached.

Hand it to Hunter for verified contacts

Now the list is qualified, you need people.

This is the handoff: Perplexity has told you which companies matter, and Hunter finds the people behind each one, with an honest read on whether their email is safe to send.

For each company you get names, roles, and addresses, each with a verification status.

Just as important, Hunter is explicit about what it cannot confirm.

Some contacts come back verified and ready to send, some are flagged as unverified or sitting on an accept-all domain where deliverability cannot be guaranteed, and some companies return nobody at all.

What you need to care about:

• A valid result is a green light
• An accept-all domain is a warning that the server accepts anything, so a hit there is not proof the mailbox exists.
• Unverified means Hunter has a candidate it has not confirmed.
• No data means it found nothing and will not guess.

It's crucial to know exactly which contacts you can send to today and which need more work before you risk your sender reputation.

Try: "Use Hunter to find the [role you want] at each, with verified emails."

Hunter tells you what it cannot confirm, which is exactly why you can trust what it can.

Scale it to a whole category

The same workflow that covers a handful of companies can also be used for mapping a whole market segment in one run.

Instead of stopping at a single signal, you can ask Perplexity to map an entire category and attach a decision-maker to each name in the same request.

It works through the list step by step, using its own research to build the market map and Hunter to find and verify a contact for each company, then returns the result with confidence scores, verification statuses, and sources.

Try: "Who are the top [number] players in [your category]? Then find one decision-maker at each with Hunter."

A whole category researched, staffed and graded in one run, with sources.

Where to go next

Perplexity finds what is happening on the open web and cites it.

Hunter finds the people behind those companies, and it is honest about which ones it cannot confirm.

Together they take you from a fresh signal to a checked shortlist without leaving the chat, and you never send to an address Hunter could not confirm.

If Perplexity is not your assistant of choice, the same connector approach works elsewhere:

• Here is the same workflow with Hunter and ChatGPT
• Here is the same workflow with Hunter and Claude.

For the full picture, see the Hunter and AI assistants hub.

Connect Hunter to Perplexity and run your first market map today.

Frequently asked questions

Do I need a paid Perplexity plan to connect Hunter?

Yes. Custom connectors are only available on Perplexity's paid plans, Pro or higher. A free Perplexity account cannot add Hunter, so you will need a paid subscription before you can set up this workflow.

What do Hunter's verification statuses actually mean?

Valid means the email was confirmed and is safe to send to. Accept-all means the server accepts any address at that domain, so a hit is not proof the mailbox exists. Unverified means Hunter has a candidate it has not confirmed. No data means Hunter found nothing and will not guess. The point is that Hunter tells you what it cannot confirm rather than inventing an address.

Why use Perplexity for the research step instead of Hunter alone?

Perplexity reads the open web as it is today and cites its sources, so it can surface companies based on recent events. Hunter then turns those companies into verified, contactable people. You get current signals and checked contacts in one flow.

Can I save the contacts Perplexity finds straight into Hunter?

Yes. Once the list is built, Perplexity can save the results to a Hunter leads list, so the shortlist moves into Hunter without a manual export.

An AI assistant on its own is quick to reason but has nothing to reason over.

It can talk about your ideal customer in the abstract, but it cannot name the companies that fit, find the people who make decisions there, or tell you whether an email address is safe to send to.

Give it Hunter's data and that changes. The same assistant now works from your real wins, returns named and verified people, and leaves you with something you keep and come back to.

This AI GTM walkthrough covers using Hunter in Claude for your prospecting.

You connect Hunter to Claude as a custom connector, which is a remote MCP connection. It works on the Free, Pro, and Max plans. On the Free plan Claude allows a single custom connector, so Hunter can be the one you add.

If you have not connected Hunter to Claude yet, do that first, then come back and follow along.

Let Claude work out your ICP from your wins

Whether you've defined an ICP or not, you can skip that step and let Claude infer the pattern from customers you have already closed, then act on it in the same message.

Because Claude reasons before it fetches, it works out what your wins have in common, describes that profile back to you so you can sanity-check it, then queries Hunter for companies that match.

The list you get is built from your own closed deals.

Try: "Here are the customers we've closed: [list your domains]. Work out the ICP they share, then use Hunter to find companies that match that pattern."

Claude infers your ideal-customer profile from past wins, then pulls matching companies from Hunter.

Score and rank the whole list

A list of matches is only useful once you know where to start. Because Claude holds the whole list in its context window, it can weigh every company against the profile at once rather than one row at a time, and explain each call.

Ask it to score and rank, and the prioritization comes back with a reason attached to each position, so you can push back on any ranking instead of trusting a score you cannot see into.

Try: "Score all of them against that ICP from 1 to 10 and rank them, with a one-line reason for each score."

Claude scores and ranks every company against the profile, with a reason behind each position.

Build decision-maker lists with emails you trust

A ranked list of companies still is not a list of people you can email.

This is a critical step where you can use Hunter's data in Claude: it turns each company into named decision-makers with verified email addresses and a confidence score.

Even better, Claude will draw your attention to any gaps. When an address fails verification it is flagged or left out rather than passed through, and when Hunter has nobody indexed at a company Claude says so instead of inventing a name.

You end up with a list you can send to and where you need to research further.

Try: "For the top companies, use Hunter to find the decision-makers in [the roles you sell to] with their verified emails."

Hunter turns each company into named decision-makers with verified emails, and flags the ones it cannot confirm.

A hook that fits every contact

You now have people worth contacting, and generic outreach wastes that.

Because Claude knows each contact's role and what their company does, it can draft a first line that fits the person rather than a mail-merge template.

Then, instead of leaving you with a wall of text, you can ask it to consolidate everything into something you can actually work from.

Try: "For each contact, write a one-line outreach hook based on their role and what their company does. Then turn this into an interactive account-scoring sheet I can reopen and reuse."

Claude writes a hook that fits each contact, then starts pulling the results into a tool.

Your reusable account-scoring sheet

Here an agent does something a plain chat window cannot.

Instead of a reply you copy out and lose, Claude builds an interactive sheet: every account with its score, its contacts and their verified emails, and editable fields for priority and status.

You can sort it, export it, and reopen it later with your edits still in place.

The workflow becomes a tool you turn into a process for easier repetition.

The finished artifact: scores, verified contacts and editable status per account, in a board you can reopen and reuse.

Where to go from here

That is one prompt turning into a scored, contactable, reusable pipeline.

Hunter brought the companies, the verified emails, and a straight answer about the gaps, and Claude helped you turn this into a process

Ready to try it? Connect Hunter to Claude and run the first prompt against your own wins.

Prefer a different assistant?

• Run the workflow using the Hunter ChatGPT app
• Run the workflow using Hunter in Perplexity.

For the full picture, see our Hunter and AI assistants hub.

Frequently asked questions

Which Claude plans can connect to Hunter?

The custom connector works on the Free, Pro, and Max plans. On the Free plan Claude allows a single custom connector, so you can make Hunter the one you add.

Do I need to write an ICP brief before I start?

No. Claude can infer the shared profile from a handful of customers you have already won, then use Hunter to find companies that match it.

How do I know the email addresses are safe to send to?

Hunter verifies each address and returns a status and confidence score, and it flags or drops the ones it cannot confirm rather than passing bad data through.

Is the account-scoring sheet a one-off, or can I reuse it?

It is a reusable artifact. You can sort it, export it, edit the priority and status of each account, and reopen it later with your edits still in place.

Without access to B2B data, ChatGPT isn't very useful for email outreach.

Ask it to find companies like your best customer and it will guess from memory: no counts, no contacts, nothing you could email today.

Best case scenario? It will use web search to look up individual companies or go off listicles and other easily available content.

But, the moment it can reach Hunter's data, that changes.

With access and your guidance, ChatGPT can do everything you can do inside Hunter and more.

This AI GTM walkthrough covers using Hunter in ChatGPT for your prospecting, covering:

• How to go from one company you already sell to well to a written cold opener, without leaving the chat window.
• Why you only need a free ChatGPT plan and no CRM
• How to get the Hunter ChatGPT app
• How to use a ChatGPT conversation to use plain language into real leads.

You can keep shaping any result just by talking to it – whether the list is too broad, you need to find leads in a region or department – ask, and you'll get the answer.

If you want to know how to connect Hunter to ChatGPT first, see how to connect Hunter to ChatGPT.

Start from a customer you already win with

The best prospecting starts from find companies you know (and want to) win.

You may not have the luxury of having clear wins to leverage, but if you do, that's where you should start.

Give ChatGPT one domain and ask it to find companies that look the same.

Try: "Here's a company we sell to well: [domain]. Find 10 similar companies I should target, with a reason each fits. Show them in a table."

You bring up the Hunter app menu by typing @hunter, and Hunter's Discover does the work.

It returns an interactive widget and lists them with the number of email addresses on file and the industry.

One domain turns into a prioritized list of leads to target.

One customer domain becomes a ranked list of 366 lookalike companies, each with an email-address count.

Narrow target companies in a sentence

You now have companies to review.

In a conventional user interface, the next step is clicking through filters.

Not here. In ChatGPT, just say what you want.

Try: "Narrow that list to companies in Europe."

A single sentence trims the market to European companies, each with a one-line reason it belongs.

Find companies with buying signals

A company can fit your profile and still not be worth prospecting right now.

One that just raised money or is hiring fast is a better first call than one sitting still.

Ask the agent to go and check.

Try: "Which of these recently raised funding or are hiring aggressively? Look for such news and hiring signals and flag them."

It researches the open web and comes back with a table. It closes with a recommended outbound order and a segmentation. The agent has done the reading and prioritized for you.

The agent checks the open web for funding and hiring signals, then ranks who to contact first.

Get named contacts with verified emails

Up to here you have companies and reasons, but you cannot email a company.

You need people, with real addresses, that are accurate. Hunter shines here.

Try: "Use the Domain Search on those companies, then filter the results to marketing."

Domain Search returns named marketing contacts with addresses and a verification status on each one.

Draft the first touch

You have a prioritized company, a named contact and a verified email.

The last step is the message, and the agent already knows enough to write it.

Try: "Write a 3-sentence cold opener for contact #1, using their role and what the company does."

It produces an editable text block with a three-sentence opener addressed to Matthias at Adyen, written for a VP of Revenue Marketing at a payments infrastructure company, and offers to make it more technical, more executive or more personalized.

You went from one customer you like to a first email in one chat.

A three-sentence opener, written for the contact's role and company, ready to edit and send.

Try it on the free plan

You do not need a CRM, a paid seat or a setup call to run this.

It works on the free ChatGPT plan with the Hunter app, and all of it happened in one conversation, from the first lookalike search to the finished first email.

If you would rather do this in a different assistant, the same idea works elsewhere:

• Run it in Claude
• Run it in Perplexity, and
• Get the full picture in Hunter with AI assistants.

Frequently asked questions

Do I need a paid ChatGPT plan to use Hunter this way?

No. Every step here runs on the free ChatGPT plan, and Hunter is available as an app inside ChatGPT.

Do I need a CRM or any setup first?

No. You start from a single company domain in the chat window, and there is nothing to install or import.

Are the email addresses verified?

Yes. Even inside ChatGPT, Domain Search returns a Hunter verification status on each contact, so you can see which addresses are marked Valid before you send.

No single data provider will find everything. Run a 10,000-contact list through any email finder, ours included, and a chunk of it comes back empty.

Nobody likes that.

Waterfall enrichment is an approach to data enrichment that aims to fix it: when one provider has no data, ask the next one, and keep going until something comes back. And if building a waterfall and doing it by hand sounds burdensome, a wave of tools now sells waterfalls as the product itself.

Hunter sits inside many of those waterfalls. Clay and other platforms query our data as one of their steps, so we watch this technique work from the inside. In fact, Hunter proudly sits at the helm of Clay's waterfalls, and we've received honors as a top provider for accept-all verification and work email finding.

Waterfall does meet its goal: stacking providers will fill more rows than any single one of them. But coverage is the only thing a waterfall guarantees.

The trade-offs (accuracy, consistency, and price) only become apparent once you've used one for a while.

If you're wondering whether you should even care about this topic, here's a TL;DR:

• Waterfall enrichment means asking multiple data providers for the same data point, one after another, until one of them returns it. In practice, that mostly means finding and verifying email addresses.
• Its one guaranteed benefit is coverage: on a large list, several providers together will fill more rows than any single one.
• The costs: more guessed addresses, verification statuses that stop meaning one thing, multiplied bills, and murky data sources.
• It's the right tool for agencies running outreach at massive scale, with the volume to justify the overhead and the ops capacity to manage several vendors.
• For lean businesses and smaller data needs, quality beats quantity: a single vendor like Hunter will get you consistently better outreach results with none of the overhead.

This guide is waterfall enrichment 101, and will help you decide if you're ready to adopt the process.

What is waterfall enrichment?

Waterfall enrichment means using multiple GTM data providers on the same data point, one after another, until one of them returns a result. Provider A goes first. If it finds nothing, the record moves to provider B, then C, and so on down the sequence. The first hit ends the run.

The point of using the waterfall enrichment approach is coverage. On a large list, no provider fills every row, so the waterfall exists to recover the records your first pick couldn't.

To clarify, waterfall enrichment is a technique, not a product.

You can build one yourself with 2-3 API keys, run one inside Clay, or buy it packaged from tools like FullEnrich and BetterContact that sell the waterfall as the product.

What waterfall enrichment is used for

In theory, you can "waterfall" any data point: phone numbers, job titles, headcount, and/or tech stack.

In the context of Hunter, enrichment covers contact, company, and technology data. It's verified, accurate data, which makes it the right starting point.

Anything beyond that (intent data, funding rounds, and job postings) can run through the same process.

But when someone says waterfall enrichment, it's a safe bet they mean some combination of the three jobs above. That's the scope of this article too.

Finding contact information

You have a name and a company domain, and you want an email address (or a phone number). The record runs through finders until one returns an address. This is the use case most waterfall tools are built around, and the one their coverage claims refer to.

Verifying contact information

You already have an email address, and you want to know whether it's safe to send to. The address runs through verifiers until one returns a clear status.

Waterfall process or not, don't skip this step, especially before reusing an old list in a campaign.

Enriching leads and companies

You already have the contact, an email address or a company domain, and you want the data around it: name, role, location, company size, and industry.

This is the job of enrichment APIs, including Hunter's. Give them an email address or a domain, and they return the person or company profile behind it.

Different providers use different attributes for the same record, so profiles with gaps can cascade through several enrichers the same way emails cascade through finders.

To see what a single person lookup returns before wiring up an API, paste an address into Hunter’s Reverse Email Lookup. It’s free and needs no signup.

How a waterfall works, step by step

A waterfall is like trying to book an urgent doctor's appointment and you're calling multiple offices, starting with the one you want the most, to find one that can see you today.

When you're trying to find an email address, this is the process:

1. You decide the order of providers: A, then B, then C.
2. Every record goes to provider A first.
3. If A returns an email address, that record is done. It never reaches the other providers.
4. If A returns nothing, the record moves to B, then C, until something comes back or the queue runs out.
5. Optionally, every found address goes through a verifier at the end, no matter which provider found it.

Two details in that flow decide most of the economics.

1) Provider order

The cheapest provider goes first in the hope that it resolves most of the list at the lowest cost, and the expensive providers only ever see the leftovers. It's the sensible default with a significant drawback we'll discuss in a moment.

2) How you pay

Some providers charge only when they return a result, others charge per lookup no matter what comes back, and packaged waterfall tools usually charge a flat credit per completed contact regardless of which provider did the work.

Why you'd use waterfall: coverage

Waterfall enrichment promises better coverage.

That’s a natural outcome when you combine different GTM data providers.

For example, some providers have strengths in publicly sourced, verified data across companies, contacts, and technologies.

Others give fantastic coverage of European data, while others succeed with North America.

Meanwhile, some vendors give GTM data specialized on smaller businesses, enterprises, emails addresses, and even phone numbers.

The point being, a waterfall of different GTM data providers can give you a more complete coverage for your leads.

The waterfall enrichment approach lends itself well to needs of outreach agencies. They have the time, resources, and scale, to test things, make tweaks, and maintain the waterfall over time.

The trade-offs: accuracy, consistency, and price

The extra rows come at a cost:

Accuracy: a returned email isn't a correct email

A waterfall stops at the first answer it gets. That's hiding a real weakness - it's not checking whether the data is right.

That matters because providers need different amounts of evidence before they serve you an address.

Some generate the likely pattern (first.last@company.com), check that the server doesn't object, and return it as valid.

Others are careful differentiating between valid and accept-all, and run multiple extra checks on top of the SMTP handshake.

Inside a waterfall, the forgiving providers naturally claim a bigger share of your list. Every record they "find" never reaches the stricter tools behind them. The more eager the finder, the more guessed addresses end up in your outreach.

You'll meet them again as bounces.

Consistency: providers don't speak the same language

Every provider has its own statuses and its own logic behind them. Accept-all domains are the classic case.

Their mail servers accept messages to any address, real or not, so no verifier can fully confirm the mailbox exists.

One provider can name these addresses as "risky". Another will call them "valid" with a footnote. A third can fail to make a comment on the status. It's the same email address, but quickly the efficacy of the email address is forgotten.

Merge those outputs into one CRM column and "verified" doesn't mean a thing.

Two rows have the same status but passed different tests run by different tools.

This can be mitigated, but it's a ton of logic you'll need to build into your process.

Price: increases with more coverage

You're now paying several vendors instead of one, through a mix of credits and subscriptions.

Cheapest-first ordering keeps the cost per found email down, but the hard records still cascade through every paid lookup.

Packaged waterfall tools simplify this into one flat credit per contact, and they price that convenience in.

The measurement trap: you stop knowing which provider is good

In a waterfall, the first provider sees the whole list and resolves the easiest step: known companies, standard email patterns, and contacts every database has.

By design, providers further down only ever see what the ones before them missed.

But it means position in the queue decides the stats. Provider A found, say, 65% of what it was asked and provider C found 12%. A went first, so it got the records anyone could find. C got the leftovers.

Swap their places and C might find 72%, and suddenly look significantly more useful.

The same problem applies to your CRM data.

A bounce doesn't tell you which provider produced the address. Unless you record the source of every found email and check campaign results per source, you'll never learn which tool is worth re-using, and which ones should be dropped.

If you don't track it, the impression that sticks is "provider A found the most". It looks like the cheapest and best tool in the chain, but you can't actually know that without proper analysis.

The compliance problem: a waterfall is as compliant as its weakest provider

If you email people in the EU, someone may eventually ask where you got their address. Under GDPR, you're expected to have an answer: what the source was and on what basis you're processing the data.

With one provider, that's one answer. You know their methodology, you've read their DPA, and you can point to the source when asked.

With a waterfall, you have as many answers as providers, and they're not equally good. Some document where each data point comes from (Hunter tells you how every email address was found). Others give you an address and nothing else. You don't know whether it was crawled, licensed, scraped, or guessed.

Data provenance doesn't average out. If a third of your list came from a provider that can't name its sources, that's the third that's unaccounted for.

The careful providers in your waterfall chain don't compensate for the opaque ones, because compliance questions come one record at a time.

Log where each address came from, and you can at least answer the question.

When waterfall enrichment makes sense (and when it doesn't)

The decision comes down to what a missing row costs you vs. a bad row.

A waterfall is worth it when:

• Coverage is the constraint. You've exhausted your primary GTM data provider, and the records it missed are worth it, say, in a niche market where every account matters.
• Your list is big enough that a few extra percentage points of coverage mean hundreds of extra contacts.
• You have the money and time to handle it. Several vendors mean several bills, and somebody has to own the setup, watch the credit balances, and run it.
• You have the ops capacity to do it right: normalize statuses across providers, track sources per record, and watch per-provider quality.
• You treat it as backfill. One trusted provider does the bulk of the work, and the waterfall mops up what's left.

Skip it, or keep it short, when:

• A bounce can hurt your sending domain.
• You sell into compliance-sensitive markets and can't afford fuzzy provenance.
• Your list is small (i.e., <1,000 contacts), and you can fill the gaps by hand faster than you can wire up three providers.
• A single provider already covers your segment well. Coverage problems you don't have don't need solving.

If you run a waterfall, run it well

None of the problems above kill the idea of using a waterfall.

If you're going to run a waterfall:

1. Start with the strictest finder, even if it costs more per lookup, because it means pattern guesses only enter your list when nothing better exists. It does cost more per contact, but it will reduce your bounce rates.
2. Verify everything with the same tool at the end. Whichever provider found the address, one verifier of your choice gets the final word. That way "valid" means exactly one thing in your CRM.
3. Decide your accept-all policy once. Whether you send to accept-all addresses is your call to make upfront, not something to inherit from whichever provider happened to label the row.
4. Record the source of every address if possible. It's how you evaluate providers, and it's your answer when someone asks where their data came from.
5. Cap the chain at 2-3 providers. Many tools license data from the same upstream sources, so the fourth provider in your queue often searches a near-copy of a database you've already tried. Each addition finds less and costs the same to maintain.
6. Judge GTM data providers by their bounce rates. Bounce rate reflects whether the addresses were actually right, while find rate is whatever queue position makes it.

Frequently asked questions

What is waterfall enrichment?

Waterfall enrichment means using multiple data providers on the same data point, one after another, until one returns a result. It's mostly used to find and verify email addresses. The goal is coverage: on a large list, several providers together fill more rows than any single one.

How is waterfall enrichment different from regular data enrichment?

Regular enrichment asks one provider and accepts the gaps.

Waterfall means more sources, which means higher coverage, but comes with trade-offs in accuracy, consistency, and cost.

Does waterfall enrichment improve accuracy?

No, it improves coverage. A waterfall stops at the first answer it gets, whether or not it's right, and providers with looser standards fill more of the list. If accuracy matters, run every found address through the same verifier at the end, no matter which provider found it.

Is waterfall enrichment GDPR compliant?

It can be, but it's only as compliant as its least transparent provider. GDPR expects you to be able to say where personal data came from. If one tool in your chain can't name its sources, you can't answer for the records it produced. Check each provider's methodology before adding it.

Which tools offer waterfall enrichment?

Clay, FullEnrich, and BetterContact are the best-known options, and platforms like Apollo have added waterfall features of their own. You can also build one with 2-3 provider APIs. The tooling matters less than the setup: order, verification, and source tracking decide what you get out of it.

Is waterfall enrichment worth it?

It depends on what a missing row costs you versus what a bad row costs you. It's worth it on large lists in coverage-constrained markets, with the budget and ops time to run it properly. It's not worth it on small lists, or when a bounce hurts more than a gap.

Making the call

A waterfall improves your coverage, but it will affect the accuracy, consistency, legal compliance, and costs of lead generation.

Sometimes that's a good trade.

If every account in your market matters, take the extra rows and manage the rest with the checklist above.

Wherever Hunter fits in your setup, as your only provider or the strict first step in a chain, you'll know how every address was found and what its status means. That part shouldn't depend on which tool answered first.

Any waterfall can fill the rows, but with Hunter as a core data source you know you can trust the results.