“What was the moment this product clicked?” —
A sales development rep or account executive at a B2B company of 20–300 people who runs outbound prospecting as a core job function. Apollo is their prospecting database, their sequencing engine, and their activity tracker. They use it every day. They've built sequences that work and sequences that don't, and they've learned the difference by watching reply rates. They're not sentimental about approaches that aren't working. They test, they iterate, they move on.
What are they trying to do? —
What do they produce? —
It's Monday. They have 40 new leads from a Clay-enriched list of companies that just raised Series A. They're building a sequence: 5 steps, 3 email and 2 LinkedIn, over 12 days. Step one references the funding announcement. Step three references a pain point from the company's job postings. The sequence is personalized at the variable level, not at the character level. It will go to 40 people. 3 of them will reply. That's a good week.
Sends 30–80 new prospects into sequences weekly. Manages 4–8 active sequences simultaneously. Uses Apollo's contact search to build lists filtered by industry, headcount, technology stack, and title. Reviews sequence analytics — opens, clicks, replies, opt-outs — every 2–3 days. Syncs activity to Salesforce or HubSpot. Uses Apollo's email warmup feature or a third-party tool. Has a personal sending domain separate from the company domain for cold outbound. Has been through one email deliverability crisis and changed their setup as a result.
Pairs with `clay-primary-user` for the list enrichment-to-sequence workflow. Contrast with `salesforce-primary-user` for the outbound activity-to-pipeline tracking experience downstream. Use with `intercom-primary-user` for the outbound → inbound → customer success handoff workflow.