Hey, it's Christian from the RevGrowth newsletter.
I’m emailing you a 3-minute insight that you can implement today to start generating more leads from your outbound campaigns.
Today I'm walking you through every essential tool we use, why we use it, and the n8n and Clay workflows that tie it all together.
THE STACK (AND WHY EACH PIECE EXISTS)
Most outbound stacks I see are either cobbled together with no real thought, or they're missing entire layers that silently kill performance.
There are five layers to a functioning outbound operation. If you're missing any of them, you're leaving serious pipeline on the table.
Here's how we build it:
1. Lead Sourcing — Apollo + Clay + Google Maps / Serper
Apollo is our starting point for most B2B campaigns. It's fast, covers a massive database, and lets you filter by industry, headcount, revenue, job title, etc. But Apollo data alone isn't enough.
We pipe every Apollo export into Clay to run two things before a lead ever enters a campaign:
Clay's AI company summary agent — pulls publicly available info on the company and writes a one-paragraph profile
ICP analysis agent — compares that profile against the client's ICP criteria and outputs a qualification score
This alone gets our lists from the industry-standard 50–60% qualified to 90%+ qualified. It's a big deal.
For local or niche TAMs where Apollo falls short, we use Google Maps and Serper scraping. Google-sourced leads consistently outperform Microsoft-sourced leads in our data — better domains, better contact data, better response rates.
One more thing we do in Clay: we pull personal (non-business) emails alongside business emails. This can unlock upwards of 125.7% more contact data and our personal email campaigns hit a ~2x better email-to-lead ratio. Separate campaigns, separate infrastructure — but worth it.
2. Deliverability Infrastructure — ScaledMail
This is non-negotiable. You can have the best scripts in the world and a perfectly qualified list and still land in spam if your infrastructure is weak.
We use ScaledMail for all client inboxes. They monitor 75,000+ inboxes and the deliverability data they surface is unlike anything else in the market. When an inbox starts trending toward spam placement, we catch it fast and rotate it out before it damages the sending domain.
The setup protocol we follow for every client:
2-weeks aged domains only — never brand-new domains for cold outreach
Proper DNS records across all sending domains (SPF, DKIM, DMARC)
Separate domains (and sometimes a separate EmailBison workspace) for personal email campaigns
Slow ramp on new inboxes — no hitting volume limits from day one
Most teams treat deliverability as a one-time setup task. It neeeeeeds to be treated as an ongoing monitoring process.
3. Sending & Sequencing — EmailBison
EmailBison is our sequencer. We've run 1,160+ campaigns in the last 12 months — it's built for volume and it handles spin syntax natively.
Every script we write uses {option1|option2|option3} spin syntax across key sections — subject lines, openers, CTAs. This keeps your sending fingerprint varied and helps avoid pattern detection across large sends.
Campaign structure we follow per client:
One inbox per campaign maximum (prevents shared reputation issues)
15–20 emails/inbox/day sending cap
3-step sequence max — initial email, follow-up 1, follow-up 2
All campaigns tagged by segment so we can isolate performance data fast
4. Automation Layer — n8n
This is where most teams have ZERO systems in place and it's where deals die.
When a prospect replies to a cold email, the average response time from most sales teams is hours — sometimes a day or more. By then, they've moved on. We've seen clients go from 60–80 positive replies per month with 0 closes to 8 deals closed per month just by fixing response lag.
Our n8n setup handles this automatically:
EmailBison fires a webhook to n8n the moment a reply comes in
n8n passes the reply text to an AI model that classifies sentiment — positive, negative, neutral, out of office
If positive: n8n pushes an instant Slack notification to the assigned rep with the lead's name, company, reply text, and a direct link to reply
If negative or OOO: routed to a separate Slack channel for review (we don't want reps wasting time on hard no's)
All reply data gets logged to a Google Sheet automatically for campaign reporting
The Slack notification is the most important piece. When a rep sees a ping in real-time and can reply within 5 minutes, close rates go through the roof compared to checking a shared inbox twice a day.
We also run a secondary n8n workflow that pulls weekly campaign stats from EmailBison's API and builds an automated performance report — reply rates, positive reply rates, sequence completion rates — all formatted and dropped into a client Slack channel every Monday morning.
5. Response Management
The last layer is the actual human side — how reps handle the replies once they come in.
We keep this simple:
Pre-written response templates for the 5–6 most common reply types (interested, "tell me more", "send me pricing", "not the right person", "not right now")
Templates live in a shared doc the rep can copy-paste and personalize in under 60 seconds
CTA is always a specific time slot first, Calendly link second — never lead with just a link
Once a meeting is booked, they go into the pre-call nurture sequence we've covered in a previous issue (confirmation email + reminder cadence = show rates up to 70–80%)
Put all five layers together and you have a system that sources qualified leads, lands in the inbox, reaches the right person at the right time, notifies your rep the second they reply, and gives them everything they need to close the conversation.
Most teams are running 2 or 3 of these layers. That's why most campaigns underperform.
Want to see every workflow, prompt, and system we use — including the full Clay ICP agent setup and n8n automations? It's all inside Outbound Secrets.
Use code REV20 for 20% off.
If you're a B2B company over $3M ARR and want us to build and run this for you, book a call at RevGrowth.ai and we'll see if you're a fit.
Hope you found this email valuable.
Have a blessed day,
Christian