GTM Index
Submit a playbook

Outbound

Blocklist before you enrich

Past clients and competitors go in first. Then Ocean, Apollo, Sales Nav, and the scraper. Waterfall the emails. Export only after dedupe and seniority.

Deepak Amirtha RajGTM Engineer · ClayGTM Index

The loop

  1. 01Open a Clay tableThis is non-negotiable. The list lives here, not in a CSV you enrich later.
  2. 02Put the blocklist in firstPast clients, competitors, companies you do not want. Clean the data before you spend a credit.
  3. 03Pull from four sourcesOcean.io for domains. Apollo via webhook for contacts. Sales Nav for decision-makers. Instant Data Scraper for the rest.
  4. 04Waterfall, then verify they still work thereEmails: Prospeo → LeadMagic → FullEnrich. Phones: FullEnrich. LinkedIn check: they still work there.
  5. 05Filter, then export lastRevenue, location, tech, title. Instantly / Smartlead / Lemlist only after duplicates are gone and the list is sorted by seniority.
linkedin.com ↗Enrichment is layer 3, not layer 1.Use a Clay table. Layer 1 blocklist (past clients, competitors). Layer 2 Ocean.io domains, Apollo webhook contacts, Sales Nav DMs, Instant Data Scraper. Layer 3 email waterfall Prospeo → LeadMagic → FullEnrich; phones FullEnrich; verify they still work there. Layer 4 filter revenue/location/tech/title. Layer 5 export Instantly/Smartlead/Lemlist ONLY after removing duplicates and sorting by seniority. He says this is the difference between 2% and 15% replies.

Most lists enrich first and filter later. Deepak’s version is the opposite. The blocklist is layer 1. Credits only run after the junk is out.

The interesting constraint is the export gate. The sequencer is last. Dedupe and seniority sort happen in Clay, not in the inbox tool. He says this is the difference between 2% and 15% replies.

More playbooks

All playbooks →