Articles

Apollo Lead Generation: How We Build 200-Lead Lists in 15 Minutes

Ibby SyedIbby Syed, Founder, Cotera
9 min readMarch 6, 2026

Apollo Lead Generation: How We Build 200-Lead Lists in 15 Minutes

Apollo Lead Generation Guide

Marcus used to spend every Monday morning the same way. Open Apollo. Set filters. Scroll through results. Click profiles one by one. Copy to a spreadsheet. Clean the data. Remove duplicates against HubSpot. Two hours later he'd have maybe 80 contacts, half of which were stale.

He did this for nine months.

When we finally timed the whole process start to finish, the actual searching took about 20 minutes. Everything else was clicking, copying, cleaning, and cross-referencing. The kind of work that makes you wonder why you went to college.

Now an AI agent builds his Monday list in 15 minutes. 200 contacts, already deduplicated, already enriched, exported to Google Sheets and ready for outreach. Marcus reviews the list over coffee instead of building it.

Here's how we got there, and what we learned about Apollo's search that makes it work.

Apollo's Search Is Better Than You Think

Most people use Apollo's search the way they use LinkedIn search. Type in a job title, pick an industry, maybe set a company size. Get back 10,000 results and feel productive.

That's not searching. That's browsing.

Apollo has over 65 filterable fields. The good ones are buried. Revenue range is more useful than employee count for B2B targeting because a 50-person company doing $40M in revenue looks nothing like a 50-person company doing $3M. Technologies used lets you filter by tech stack, so if you sell a Salesforce integration, you can find companies actually running Salesforce. Funding date and amount lets you target companies within 6 months of raising a round, when budgets are loose and new tools get bought.

We tested a broad search versus a filtered search against the same ICP. Broad search: "VP Marketing" at "SaaS companies" with "51-200 employees." Got back 8,400 results. We contacted 200 of them. 11 replied. 3 booked meetings. That's a 1.5% meeting rate.

Filtered search: same title, but added revenue $5M-$50M, technologies include HubSpot or Marketo, funding raised in last 18 months, headquarters in US or Canada. Got back 1,200 results. We contacted 200. 34 replied. 14 booked meetings. A 7% meeting rate from the same number of contacts.

The filter didn't just narrow the list. It changed the quality of every name on it.

The Filters That Actually Matter

After building a few hundred lists, here's where we landed on which filters earn their keep.

Job title plus seniority level. Use both. "Director of Marketing" as a title combined with "Director" seniority level catches people whose actual titles are things like "Senior Director, Growth Marketing" or "Director & Head of Demand Gen." Apollo's seniority mapping isn't perfect but it catches variations that exact title match misses.

Revenue range over employee count. A 200-person company could be a bootstrapped services firm or a VC-backed rocket ship. Revenue tells you which one you're looking at. If your product costs $30K/year, companies under $5M in revenue probably can't buy it no matter how interested they are.

Technologies used is the single most underrated filter. If you're selling to marketing teams, knowing they run HubSpot versus Pardot versus nothing tells you completely different stories about their maturity, budget, and pain points. We've built entire outbound campaigns around "companies using Competitor X" and the reply rates are double our industry-generic campaigns.

Hiring signals, when a company has open roles on their careers page, tell you where they're investing. A company hiring three SDRs is actively scaling outbound. That's a good time to sell them sales tools. A company hiring a VP of Data is about to care about data quality. Time your outreach to what they're building toward, not where they are now.

Department headcount lets you estimate team size without guessing. A "Head of Marketing" at a company with 2 marketers has completely different problems than one with 30 marketers. Your pitch should be different too.

The Filters That Waste Your Time

Not everything in Apollo's search panel is worth touching.

Keywords in bio sounds useful. It isn't. People write wildly inconsistent bios. Some are detailed. Most are empty. You'll miss 80% of your audience because they never filled out a profile summary.

Industry tags are broad and often wrong. Apollo maps industries from multiple sources and the categorization is inconsistent. A company might show up as "Computer Software" or "Information Technology" or "SaaS" depending on which data source Apollo pulled from. Use revenue range and technologies instead, they tell you more.

Company name search is fine for account-based lists but terrible for discovery. If you already know the company you want to target, just look them up directly. Don't build a filter around it.

The search gets you names. But names without context are just a spreadsheet of strangers.

Apollo's enrichment adds verified emails (their accuracy hovers around 85-91% depending on the domain), phone numbers, company details, and social profiles. We run enrichment on every contact before export because sending an email to a bad address doesn't just waste your time, it damages your sender reputation.

Here's what the old workflow looked like for Marcus:

  1. Search Apollo. 20 minutes.
  2. Manually review profiles and remove obvious mismatches. 25 minutes.
  3. Export to CSV. 2 minutes.
  4. Upload to Google Sheets. 3 minutes.
  5. Deduplicate against existing HubSpot contacts. 30 minutes.
  6. Enrich missing fields. 15 minutes.
  7. Format for outreach tool import. 10 minutes.

Total: about 1 hour 45 minutes for a list of 80-100 contacts.

The new workflow with an Apollo Prospect List Builder agent:

  1. Define ICP parameters once.
  2. Agent runs search, enriches contacts, deduplicates against CRM, exports to Google Sheets.
  3. Marcus reviews the list. 15 minutes.

Total: 15 minutes of human time. 200 contacts. Already clean.

The quality is actually better because the agent doesn't get tired on contact #47 and start rubber-stamping profiles. It checks every contact against the same criteria the same way every time.

Building Lists That Convert

We learned something counterintuitive about list size. Bigger lists perform worse per contact but sometimes better in total. Smaller lists perform better per contact but you hit the ceiling faster.

Our sweet spot: 150-250 contacts per weekly list, with tight filters. We'd rather run a small list through a great sequence than blast a huge list with generic copy.

When Marcus runs his Monday build now, the agent creates three segments automatically. Tier 1 is contacts that match every filter perfectly. Usually about 40-60 people. These get personalized outreach. Tier 2 matches most filters. About 80-100 people. These get semi-personalized sequences. Tier 3 is looser matches. The rest. These go into nurture campaigns, not direct outreach.

The tiering alone changed our reply rates. Before tiering, we averaged 4.2% reply rate across all outbound. After tiering and matching message intensity to contact quality, Tier 1 hits 12.8%, Tier 2 hits 5.1%, and Tier 3 hits 2.3%. The blended rate went from 4.2% to 6.1%. Same total volume, 45% more replies.

Common Mistakes We Made

We burned through a lot of Apollo credits learning what not to do.

Don't build one massive list per month. Build weekly. People change jobs. Emails go stale. A contact who was perfect on March 1st might have left the company by March 20th. Weekly lists of 150-200 contacts stay fresh.

Don't skip the deduplication step. We once uploaded 200 contacts and 34 of them were already in our CRM with active deals. Those SDRs got some confused replies. Now the agent checks HubSpot automatically before anything gets exported.

Don't use Apollo's "net new" filter as your only dedup method. It only checks against contacts already in Apollo's system, not your CRM. You need both.

Don't export without enrichment. Raw Apollo search results have email accuracy around 70-75%. After enrichment that jumps to 85-91%. The enrichment step costs credits but saves you from bounce-rate damage that costs way more.

Apollo's API vs. The UI

Most people never leave Apollo's web interface. That's fine if you're building one list at a time. But the API unlocks things the UI can't do.

Saved search automation. Through the API, you can run the same search on a schedule and only return new contacts since the last run. In the UI, you'd have to re-run the search manually and figure out which contacts are new. The API handles incremental fetching natively.

Multi-search combination. Sometimes your ICP isn't one search. It's three overlapping searches with different filter combinations. VP Marketing at companies using HubSpot. Director Demand Gen at companies that recently raised Series B. Head of Growth at companies with 100-300 employees and $10M-$50M revenue. In the UI you'd build three separate lists. Through the API, an agent runs all three, merges and deduplicates them, and delivers one combined list ranked by match strength.

Real-time enrichment. The UI enriches contacts when you view them or export them. The API lets you enrich on demand, check email deliverability, and validate phone numbers before a contact ever enters your workflow. Garbage stays out instead of getting cleaned up later.

We resisted moving to the API for months because it felt like "developer stuff." It's not. The agents handle the API calls. You just tell them what you want.

The 15-Minute Monday

Here's what Marcus's Monday actually looks like now.

8:00 AM: Agent runs automatically. Pulls new contacts matching three saved ICP definitions. Enriches. Deduplicates against HubSpot. Tiers the list. Exports to a shared Google Sheet.

8:15 AM: Marcus gets a Slack notification that the list is ready. He opens the sheet, scans the Tier 1 contacts, flags any that look off. Maybe removes 5-10 that slipped through.

8:30 AM: Done. List goes to the outreach tool. He spends the rest of his morning on actual selling.

Two hours of tedious work replaced by 15 minutes of review. Multiply that across a five-person SDR team and you're saving 40+ hours per month. That's a full week of selling time that used to disappear into Apollo's search UI.

The tool is powerful. The UI is fine. But the workflow around it is where teams lose all their time. Automate the workflow and the tool becomes something else entirely.


Try These Agents

For people who think busywork is boring

Build your first agent in minutes with no complex engineering, just typing out instructions.