Outbound
Hiring filter first. Bounce under 3% before you scale
Don't start from a static Apollo dump. Clay queries domains that are hiring. Then Apollo → Lusha → Hunter. Clean the dials. Verify the emails. Only then does the queue open.
The loop
- 01Don't start from a static Apollo dumpA bought list is already stale. The TAM is companies that are hiring right now.
- 02Query domains on a hiring filterClay is the table. Active hiring is the filter. If they are not hiring, they are not this week's list.
- 03Waterfall Apollo → Lusha → HunterContacts come from the waterfall, not one provider. Each layer only runs on what the last one missed.
- 04Clean dials and verify work emailsDirect dials get cleaned. Work emails get verified. Nothing unverified goes to the sequencer.
- 05Hold the queue until bounce is under 3%Do not blast. Do not scale a campaign that is already bouncing. Under 3% is the gate.
Most outbound lists are an Apollo export with a waterfall taped on. Prem’s version flips the order. Hiring is the filter. The waterfall is just how you fill the row.
The interesting constraint is the bounce cap, not the providers. Under 3% before scale. Anything above that means the list was a dump.
