Most people A/B test one variable at a time. Change the subject line, measure open rates, wait two weeks, repeat. I got impatient with that.
Instead, I built a system that runs four completely different outreach campaigns in parallel — same target market, different angles — all managed by an AI agent that finds prospects, validates them, and queues them for contact automatically.
Here is how it works and what I have learned after a week of running it.
The Four Campaigns
Each campaign tests a fundamentally different value proposition against the same audience: dental offices, medical practices, law firms, and CPAs in South Florida.
Receptionist Campaign — "What happens when someone calls your office after hours?" This hooks into the pain of missed calls. Every missed call is a missed patient or client.
Reviews Campaign — "How are you handling negative Google reviews?" Reputation management is a universal anxiety for local businesses. Nobody likes that one-star review sitting at the top.
AI Campaign — "Which tasks eat most of your admin time?" This is the broad automation pitch. Less specific, but it opens a wider conversation.
Boring Campaign — "What is the most repetitive thing you do every day?" The anti-pitch. No buzzwords, no AI hype. Just asking about tedious work.
The Automation Stack
The whole pipeline is orchestrated by a cron-scheduled AI agent running on my server. Every few hours, it:
- Scrapes Google Maps for businesses matching specific categories and locations
- Validates each prospect — checks for a working phone number, website, and physical address
- Deduplicates against the existing queue in Redis
- Assigns a campaign based on the scheduled rotation
- Pushes to the call queue for automated outreach
The agent added 153 validated prospects in just the last five days. That is 30+ prospects per day, zero manual research.
What Makes This Different from Typical Lead Gen
The key insight is not the automation — it is the parallel testing structure.
Most outreach tools let you send emails at scale. But they assume you already know your angle. You write one pitch, blast it out, and hope for the best.
Running four campaigns simultaneously means I am not guessing which message resonates. I am measuring it. Same geography, same business types, different hooks. After a few hundred contacts, the data will tell me which pain point actually gets people to pick up the phone.
Technical Details That Matter
A few things I learned building this:
Redis as a queue is underrated. I store the entire prospect queue as a JSON array in a single Redis key. Simple, fast, and I can inspect or modify it with one command. No need for a dedicated queue service when your volume is hundreds, not millions.
Deduplication is harder than it sounds. The same dentist shows up in multiple Google Maps queries. Phone number matching catches most duplicates, but some businesses list different numbers on different listings. I ended up matching on a combination of name similarity and geographic proximity.
Campaign rotation prevents bias. If I ran all four campaigns from the same time slots, the receptionist campaign would always hit businesses at 10 AM and the boring campaign at 8 PM. Rotating the schedule means each angle gets tested across different times of day.
Results So Far
It has been one week. The queue grew from zero to over 150 prospects across dental offices, law firms, medical practices, and CPAs in Miami, Fort Lauderdale, Boca Raton, and Palm Beach Gardens.
The system runs five times per day, adding 3-8 prospects per run. It has not needed manual intervention once — no crashes, no bad data, no duplicate storms.
Conversion data is still early. But the infrastructure is solid, and the test is running. That is the part most people never get to because they spend weeks picking the perfect pitch instead of testing four at once.
The Takeaway
If you are doing cold outreach, stop optimizing one message. Run multiple angles in parallel. Let the data pick the winner.
And if you are building automation, do not overthink the stack. A cron job, a Redis queue, and an AI agent that can search Google Maps is enough to build a pipeline that most sales teams would need three people to run.
The boring answer is usually the right one: simple tools, clear structure, let it run.
Top comments (0)