“The head of sales wants a list of 500 Series B SaaS companies that have posted a VP of Sales job in . Something that used to take 30 minutes took 30 seconds. They looked at the old way and couldn't believe they'd tolerated it. That was the aha.”
When I'm the head of sales wants a list of 500 series b saas companies that have posted a, I want to build targeted outbound lists enriched with signals that justify a personalized reach-out, so I can automate the research and enrichment that previously required manual SDR work.
A growth lead, revenue ops manager, or technical sales operator who found Clay and spent two weeks rebuilding their entire outbound motion around it. They were already combining data from LinkedIn, Apollo, Clearbit, and spreadsheets manually — a process that was slow, inconsistent, and unscalable. Clay collapsed that into one workflow. They now build outbound lists in hours that previously took weeks. They are evangelical about it. They're also aware that most people at their company don't understand what they've built.
To reach the point where build targeted outbound lists enriched with signals that justify a personalized reach-out happens through clay as a matter of routine — not heroic effort. Their deeper aim: automate the research and enrichment that previously required manual SDR work.
clay becomes invisible infrastructure. Build targeted outbound lists enriched with signals that justify a personalized reach-out works without intervention. The old problem — aPI credits that disappear faster than expected on large enrichment runs — is a memory, not a daily fight. Credit usage transparency that shows expected spend before a run starts prevents.
The head of sales wants a list of 500 Series B SaaS companies that have posted a VP of Sales job in the last 30 days, have more than 20 engineers on LinkedIn, and are using Salesforce. They want it by tomorrow with the founder's LinkedIn URL and a one-line company description. The growth operator is opening Clay now. They're going to use three enrichment providers and an AI column for the descriptions. It will take 90 minutes to build. It would have taken 40 hours manually.
Uses Clay daily for outbound list building and enrichment. Has built 15–40 Clay tables for different ICP segments, trigger-based outreach, and data cleanup. Uses Clay connected to Apollo, LinkedIn, Clearbit, Hunter, and OpenAI. Pushes output to HubSpot or Salesforce via Clay's native integrations. Has hit the credit limit mid-run. Has rebuilt a table from scratch when it got too complex to debug. Knows the difference between a waterfall enrichment and a single-source enrichment and when to use each.
The proof is behavioral: build targeted outbound lists enriched with signals that justify a personalized reach-out happens without reminders. They've customized clay beyond the defaults — templates, views, integrations — and their usage is deepening, not plateauing. When new team members join, they hand them their setup as the starting point.
It's not one thing — it's the accumulation. API credits that disappear faster than expected on large enrichment runs that they've reported, worked around, and accepted. Then a competitor demo shows the same workflow without the friction, and the sunk cost argument collapses. Their worldview — outbound at volume without personalization is spam; personalization at volume without — makes them unwilling to compromise once a better option is visible.
Pairs with `apollo-primary-user` for the list-building-to-sequencing outbound workflow end-to-end. Contrast with `salesforce-primary-user` for the downstream CRM experience after Clay-built lists enter the pipeline. Use with `hubspot-primary-user` for the marketing enrichment and lead scoring use case.