How a Fortune 200 outbound team turned cold lead lists into $500K of pipeline in 15 days

The math nobody wanted to run

A Fortune 200 client had a large book of historical leads sitting cold. Calling them with humans never penciled out. Loaded rep cost at roughly $20/hour against 36,000 dials meant about $60,000 in payroll and the better part of two years tying up a team. Even a fantasy "superhuman" rep working non-stop couldn't close the timeline gap.

They didn't need a deck explaining why voice AI mattered. They needed someone who'd shipped this before to design the cadence, the agent, and the infrastructure that wouldn't melt under load.

How we built it

The stack was a voice AI provider running on a low-latency outbound-tuned telephony partner, orchestrated by a workflow engine handling cadence, retries, callback scheduling, and CRM writeback.

The constraints set the design space:

• Compliance with do-not-call lists and outbound disclosure requirements
• CRM sync without doubling records
• Cadence rules that didn't burn leads with too many attempts but converted the curve
• A human escalation path for any call flagging distress or confusion

Then the work itself:

1. Mapped the historical list and segmented by recency, prior touch, and likely value tier.
2. Wrote the agent prompt and tool calls. The agent could check live CRM data mid-call and speak to the lead's actual record, not a generic script.
3. Built a callback-on-request loop. If a lead said "call me tomorrow at 2", the agent scheduled it programmatically and the system delivered on it. That one mechanic moved completion materially. It stopped the conversation from feeling like a robocall.
4. Shipped the call cadence. Average 1.8 calls per lead, tuned for contact rate, not vanity dial count.
5. Stood up the analytics layer. Every call tagged, every outcome recorded, every drop-off mapped. The data is the asset, and we treated it that way from day one.
6. Ran the dial. 20,000 unique leads. 36,000 total calls. 15 days from cold launch to dial complete.

Fifteen days later

• 27.5% completion rate on contacted leads, closer to 31-32% once secondary touches got counted
• 5,500 booked calls out of the campaign
• ≈ $3,000 in pure AI calling infrastructure across 36,000 calls; even fully loaded for orchestration, storage, and platform fees, the number stayed well under any human equivalent
• $500K+ in additional revenue, conservative. At the client's $12-15K product price, a 1% conversion on those 5,500 booked calls clears half a million. The actual figure ran higher. We report the conservative cut.
• 15 days end to end. A human team at the same dial volume would have needed 500 days, or 350 if you fantasized about a non-stop superhuman.

What we'd ship differently next time

Push the callback feature on day one. It moved completion more than any prompt change we tried, and we didn't ship it until late in the campaign.

Tag emotional cues by default. The next generation of voice models will detect them natively. We should have been logging proxies for that from the start so we'd have ground truth when the models got good enough.

Run the data layer harder. The campaign generated thousands of structured outcome rows. There were second-order signals about which lead segments deserved human escalation that we caught late. They're now standard playbook.

Why this story matters

This is an instrumented production deployment with documented numbers from a Fortune 200 buyer. Not a demo. Not a screenshot. The gap between "we built a voice agent" and "we shipped one that moves real revenue at scale" is the gap between a few weekends of tinkering and the kind of work we do every week.

Got a list, a use case, or a deployment that isn't converting? The Voice AI Roadmap gives you the same level of clarity in 14 days.

Talk to us.