Apollo.io List Building: 9 Filters That Actually Find Decision-Makers (Not Just Job Titles)

The fastest way to waste Apollo.io credits is to search a job title, hit export, and start sending. Most people do exactly that, then wonder why reply rates are low. The issue is not the tool. It is the list logic.

Here are nine filters that separate a list of real buyers from a list of names with the right job title.

1. Seniority plus management level (not just title)

Job titles in Apollo are inconsistently formatted. A “Director of Sales” at a 20-person startup runs a one-person team. A “Director of Sales” at a 5,000-person enterprise owns six managers and a nine-figure number. They are not the same buyer.

Set Seniority to Director, VP, C-Suite, and Owner. Then add the Management Levels filter to require that the contact actually manages people. This removes individual contributors who carry inflated titles and surfaces the people with budget authority.

2. Headcount range to define the segment

A 200-contact list with tight filters beats a 10,000-row export every time.

Headcount is a proxy for budget cycle, buying committee size, and whether your product or service fits at all. A cold email that works for 50-person companies will not land the same way at 500-person companies, because the pain is different.

Pick a tight range before you build anything else. Two common starting points: 25 to 150 employees (where a single director often owns the whole decision) or 200 to 1,000 employees (where you need to map multiple stakeholders). Never let a single list span both.

3. Funding stage as a buying-signal filter

A company that raised a Series A six months ago has new budget, a mandate to grow, and a founder who is now under pressure to scale the team and the pipeline. That is a very different conversation than a bootstrapped company protecting margin.

Apollo lets you filter by last funding round and funding date. For outbound, Series A and Series B companies in the last 12 to 18 months are a reliable segment because they have money and urgency. Combine this with headcount to avoid the outliers (a Series A at 800 employees is unusual and usually means a different story).

4. Technology filter to confirm the stack

If your offer sits on top of HubSpot, Salesforce, or a specific platform, filter to companies using that technology. Apollo surfaces tech stack data under the Technologies filter. This is not perfect, but it removes the deals where you would spend the first three emails explaining a prerequisite.

For Clay enrichment, you can go further: use Apollo to pull the initial list, then run each domain through Clay’s Clearbit or BuiltWith integrations to confirm the stack with a second data source before the email goes out.

5. Department headcount to find teams with real buying power

Total company headcount tells you one thing. Department headcount tells you whether the function you are targeting actually exists at scale.

If you sell to sales teams, filter for companies where the Sales department has at least 10 people. If you sell to HR, look for companies with 5 or more in People. A 200-person company with two salespeople has a very different sales-tool buying process than a 200-person company with 30 salespeople.

6. Job change signal (recent hires and promotions)

New decision-makers buy. This is one of the most reliable intent signals in outbound. Someone who just became VP of Revenue has a 90-day window where they are evaluating vendors, building their stack, and open to conversations that a tenured executive would filter out.

Apollo has a “Changed Jobs” filter. Set it to the last 90 days for the seniority levels you are targeting. Pair this with your headcount and funding filters, and you get a list of newly empowered buyers in your segment. For deeper job-change signals and LinkedIn activity confirmation, Clay and similar enrichment layers are worth adding before you send.

7. Keyword exclusions to cut the noise

Apollo search returns everyone who matches your positive filters, including roles you do not want. Common junk that slips through: interns with “Director” in a program title, consultants billing through a company, advisors listed as employees, and contractors.

Use the Exclude Keywords field in the People filters. Common exclusions: “intern,” “advisor,” “consultant,” “freelance,” “contractor,” “part-time.” Run your list through this before export and the quality improves immediately.

8. Geography with local market logic

Pulling “Europe” as a single geography is almost always wrong. Buying behavior, GDPR obligations, language, and LinkedIn behavior differ significantly between Germany, the Netherlands, the UK, and France. If you are running outbound for European markets, build one list per country and write copy for that specific market.

Apollo lets you filter by country, state, and metro area. Use it. A 300-person list of German decision-makers with German-language copy will outperform a 3,000-person pan-European list in English every time.

9. Email status filter before export

Apollo assigns an email confidence score to each contact. Before you export, filter to show only contacts with verified or high-confidence emails. Contacts marked “guessed” or “unverified” will inflate your bounce rate and degrade your sending domain, which hurts every future campaign.

Even after this filter, run a verification pass through a dedicated tool (LeadMagic, ZeroBounce, or similar) before the list enters your sequencer. Apollo verification is a first pass, not a guarantee.

What to do after the list is built

A clean list is the input, not the output. Once you have 200 to 500 contacts who meet all nine criteria, the next step is writing copy that speaks to the specific pain of that segment. A filtered list of newly promoted VPs of Revenue at Series B fintech companies is only valuable if the email opens with their actual problem, not a generic pitch.

If you want this built and running without doing it yourself, we build the list, write the copy, and run the outbound for you. If you want to own the machine and learn the process, we can build it inside your stack. Either way, the nine filters above are where every good list starts.

For a side-by-side look at what Apollo does well versus where it falls short, see Clay vs Apollo before you decide how much of your list-building workflow to run natively versus through enrichment layers.