The Meetings Are in the Follow-Ups Nobody Sends
Pull the activity log on almost any sales team and you'll find the same shape: a strong first email, a dutiful bump two days later, and then silence. Reps move on to fresher names because a new prospect feels more promising than a fourth attempt at an old one — even though the data says otherwise. The majority of cold email replies arrive on touches three through seven, the exact sends that human discipline reliably fails to make.
Teams pick Woodpecker because it turns that persistence into machinery. Condition-based follow-up paths fire the third, fourth, and fifth touches automatically — branching on whether the prospect opened or clicked — so the follow-through happens whether or not the rep remembered. What Woodpecker doesn't supply is the sending infrastructure those touches go out on. A seven-touch sequence multiplies your exposure to deliverability: one burned mailbox doesn't cost you an email, it costs you an entire relationship arc. This guide covers the pairing — ColdRelay provides the domains, mailboxes, and dedicated IPs underneath; Woodpecker runs the follow-up engine on top.
Why Automated Persistence Needs Infrastructure That Holds for Seven Touches
A two-touch motion can limp along on mediocre infrastructure — if the opener lands, you got your shot. A seven-touch motion can't. Every prospect in a Woodpecker condition tree represents five or six future sends that all depend on the same mailbox still reaching the inbox weeks after the sequence started. When reputation degrades mid-sequence, the touches that were statistically most likely to convert — three through six — are exactly the ones that land in spam. The follow-up engine keeps firing; the prospect just stops seeing it.
ColdRelay is built for that sustained reliability. Mailboxes provision on isolated Azure tenants with dedicated IPs, DNS (SPF, DKIM, DMARC) pre-configured, ready in about an hour — and there's no warmup waiting period, because warmup runs continuously as part of each mailbox's standard budget of 4 emails/day total, split 2 outbound + 2 warmup. That always-on warmup matters more in a follow-up-heavy motion than anywhere else: it keeps reputation steady across the weeks a sequence spans, so the sixth touch lands as reliably as the first. With 100-150 mailboxes supported per domain, most teams run their whole pool on one or two secondary domains.
The two products are complementary layers, not rivals: ColdRelay is the infrastructure underneath — domains, mailboxes, dedicated IPs — and Woodpecker is the sending and sequencing layer on top, deciding which prospect gets which touch on which day.
Visit Woodpecker →Connecting ColdRelay Mailboxes to Woodpecker
Provision the pool on ColdRelay — sized for sequences, not sends
Pick a secondary domain or two adjacent to your brand and provision the pool on isolated Azure tenants with dedicated IPs, SPF, DKIM, and DMARC pre-configured, ready in about an hour. Size it with follow-up math, not opener math: a prospect in a 7-touch sequence consumes seven sends over its lifetime, so a 50-mailbox pool (100 outbound sends/day at 2 per mailbox, each mailbox sending 4/day total — 2 outbound + 2 warmup) sustains roughly 14 new prospects entering sequences per day, not 100.
Add the mailboxes in Woodpecker and cap daily sends at 2
Connect each ColdRelay mailbox under Woodpecker's email account settings via SMTP/IMAP, then set every account's daily sending limit to 2 outbound emails — mirroring ColdRelay's per-mailbox budget of 4 sends/day total, 2 outbound + 2 warmup. Warmup runs continuously on ColdRelay's side, so there's no warmup add-on to enable and no waiting period before the first campaign.
Build the full condition tree before the first send
In Woodpecker's campaign editor, build all seven touches as condition-based follow-up paths before launch — if-opened and if-clicked branches included. A prospect who opened twice but never replied gets a different touch 3 (new angle, same thread) than one who never opened (rewritten subject line, fresh thread). The rule that makes this model work: a campaign doesn't go live until the entire tree exists, because follow-ups added 'later' are follow-ups that never get added.
Turn on timezone-aware delivery and human-like sending intervals
Enable Woodpecker's timezone detection so each prospect's touches arrive in their local morning regardless of where your pool sends from, and leave the human-like sending intervals on so the 2 daily sends per mailbox space out naturally instead of firing on a robotic schedule. Both settings compound over a long sequence — seven well-timed, naturally spaced touches read like a diligent rep; seven 3:00 AM sends read like a machine.
A/B test the follow-ups, watch per-campaign deliverability, launch
Use Woodpecker's A/B testing on the mid-sequence touches — the third and fourth emails are where copy changes move the most replies, and where almost nobody tests. Then launch, and check Woodpecker's per-campaign deliverability monitoring weekly alongside your ColdRelay dashboard: campaign-level stats catch a list or copy problem early, while the infrastructure layer keeps the mailboxes themselves at 95%+ inbox placement.
The Follow-Up Discipline Playbook
Make persistence a build-time decision, not a willpower one
The reason sequences die at touch two isn't strategy — it's that each next touch was a decision someone had to make on a busy Tuesday. Remove the decision: standardize a 7-touch condition tree as the team's default campaign template in Woodpecker, and treat a campaign with fewer touches as the exception that needs a reason. Once the fifth follow-up is something the system sends rather than something a rep remembers, your team's effective persistence stops depending on who had a good week.
Branch on behavior, because touch 4 to an opener isn't touch 4 to a ghost
A flat drip sends everyone the same bump; a condition tree reads the signal first. Use Woodpecker's if-opened path to send engaged-but-silent prospects a different objection or proof point in the same thread — they've seen the pitch, they need a new reason. Send never-openers a rewritten subject on a fresh thread — the pitch was fine, the envelope failed. Same touch number, opposite diagnosis, and the branching is exactly the judgment a good rep would apply if they had time to check who opened what.
Count capacity in completed sequences, not daily sends
With each mailbox at 2 outbound/day (4/day total including the 2 warmup sends), the honest unit of capacity is prospects fully worked, not emails fired. Every prospect entering a 7-touch tree books seven sends against the pool over the following weeks — so divide daily outbound capacity by seven before promising pipeline numbers. Teams that skip this math quietly cannibalize their own follow-ups: new prospects crowd out touches 4-6 for old ones, and the motion degrades back into the two-touch pattern they bought Woodpecker to escape.
Read deliverability per campaign, fix at the right layer
Woodpecker's per-campaign deliverability monitoring and ColdRelay's infrastructure view answer different questions — use both. If one campaign's open rate sags while the rest of the pool holds, the problem is that campaign's list quality or copy: pause it in Woodpecker, fix it, relaunch. If placement dips across every campaign on a mailbox set, that's an infrastructure signal for the ColdRelay side. Diagnosing at the wrong layer is how teams burn a healthy mailbox pool fixing a bad list — or keep blasting a tired list through innocent mailboxes.
Typical Follow-Up-Driven Benchmarks (Woodpecker + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Isolated Azure tenants with dedicated IPs — the floor that keeps touch 6 landing as reliably as touch 1 |
| Share of total replies arriving on touches 3-7 | 50-60% | The statistical case for the whole motion — the majority of meetings come from sends most teams never make |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup, with warmup running continuously on ColdRelay |
| New prospects entering sequences per 50 mailboxes | ~14/day | 100 outbound sends/day divided by a 7-touch tree per prospect — the sequence-complete math that protects follow-ups from being crowded out |
| Reply rate, full 7-touch tree vs. 2-touch motion | 1.5-2x | Same list, same opener — the lift comes from condition-branched touches 3-6 that flat or abandoned sequences never send |
What It Costs: Woodpecker + ColdRelay
Infrastructure is billed per mailbox per month, with volume tiers that drop as you scale (see the table below). Dedicated IPs, isolated Azure tenants, and pre-configured DNS are included — and because a follow-up-heavy motion works each prospect harder, the pool a team needs tends to be sized to sequence math rather than raw send ambition.
Woodpecker is billed separately on its own plans, covering condition-based follow-up paths, timezone-aware delivery, A/B testing, per-campaign deliverability monitoring, and the agency panel for teams running client campaigns.
The two bills track different commitments: Woodpecker scales with the campaigns and seats running the follow-up engine, ColdRelay scales with the sending capacity behind it. Deepening sequences — more touches per prospect — costs nothing extra on either bill; it just changes how the same daily capacity is spent.
| Mailboxes | ColdRelay price / mailbox / month |
|---|---|
| 1–199 | $1.00 |
| 200–999 | $0.85 |
| 1,000–4,999 | $0.70 |
| 5,000+ | $0.55 |
Each mailbox sends 4 emails per day — 2 outbound to prospects + 2 warmup. ColdRelay provisions mailboxes on isolated Azure tenants with dedicated IPs; Woodpecker handles the sending, sequencing, and inbox rotation on top.
Frequently Asked Questions
Is ColdRelay an alternative to Woodpecker?
No — they're complementary layers of the same stack and teams run both together. Woodpecker is the sending and sequencing layer: condition-based follow-up paths, timezone-aware delivery, A/B testing, and per-campaign deliverability monitoring. ColdRelay is the infrastructure layer underneath: the secondary domains, mailboxes, and dedicated IPs that Woodpecker's sequences actually send from.
Do ColdRelay mailboxes need a warmup period before Woodpecker campaigns launch?
No. ColdRelay mailboxes warm continuously as part of their standard budget — each mailbox sends 4 emails/day total, 2 outbound + 2 warmup — so there's no waiting period and no warmup add-on to enable in Woodpecker. Connect the mailboxes, cap each account at 2 outbound sends/day, and the first campaign can launch the same day the pool is provisioned in about an hour.
At 2 outbound sends per mailbox per day, doesn't a 7-touch sequence take forever?
The cadence per prospect is unaffected — touches are spaced days apart by design, and Woodpecker schedules each prospect's next touch on its own timeline. What the budget actually constrains is how many prospects can be in flight at once: at 2 outbound/day per mailbox (4/day total with warmup), a 50-mailbox pool sends 100 emails/day, which sustains roughly 14 new prospects entering 7-touch sequences daily with every follow-up fully funded. If you need more prospects in flight, add mailboxes — don't shorten the tree, because touches 3-6 are where the replies are.
Won't sending seven touches to every prospect hurt our deliverability?
Persistence isn't the risk — sloppy persistence is. Woodpecker's condition trees space touches days apart, branch on engagement instead of blind-bumping, and stop the moment a prospect replies, while human-like sending intervals keep the pattern natural. Underneath, each ColdRelay mailbox stays inside its 4/day budget (2 outbound + 2 warmup) on isolated Azure tenants with dedicated IPs, so volume per identity never spikes. Watch Woodpecker's per-campaign deliverability monitoring weekly: a well-built 7-touch tree on this infrastructure holds 95%+ placement across the full arc.