The Five Follow-Ups Founders Never Send
Ask a founder how their outbound is going and you'll usually hear about the first email — the one they agonized over, personalized, and sent to 80 prospects. Ask how many of those prospects got a fourth touch and the answer is almost always zero. Then a term sheet negotiation eats a week, a production incident eats another, and the follow-ups that were 'definitely happening Thursday' never happen at all. The brutal part: most cold email replies don't come from the first touch — they come from touches three, four, and five, exactly the ones manual discipline never reaches.
Woodpecker is built around fixing precisely this. Its core primitive isn't the blast — it's the follow-up path: condition-based branches, human-like sending intervals, and timezone-aware delivery that keep a five-touch sequence moving without anyone remembering to push it. What Woodpecker doesn't supply is the infrastructure those touches send from — the secondary domains, mailboxes, and dedicated IPs underneath. That's ColdRelay's half, and this guide covers wiring the two together so persistence becomes a property of the system instead of a property of the founder's calendar.
Why Run Woodpecker on ColdRelay Infrastructure
Woodpecker is a sending and sequencing platform — follow-up paths, if-opened and if-clicked branching, A/B testing, and per-campaign deliverability monitoring. It sends from whatever mailboxes you connect to it; it doesn't provision domains, assign IPs, or control whether those mailboxes land. And for a persistence-driven motion, the infrastructure matters more than usual: a five-touch sequence gives a shaky mailbox five chances to hit a spam trap, and reputation damage on touch two silently kills the touches three through five where your replies live.
ColdRelay closes that gap. You provision mailboxes on secondary domains, hosted on isolated Azure tenants with dedicated IPs, with SPF, DKIM, and DMARC pre-configured — live in about an hour. There's no warmup waiting period before your first sequence starts, because warmup runs continuously inside each mailbox's daily budget of 4 sends — 2 outbound + 2 warmup. With 95%+ inbox placement holding across every step, the fifth touch arrives with the same reliability as the first.
The pairing is additive, not competitive: ColdRelay is the infrastructure layer, Woodpecker is the sending and sequencing layer on top. Woodpecker guarantees the follow-ups go out; ColdRelay guarantees they land.
Visit Woodpecker →Connecting ColdRelay Mailboxes to Woodpecker
Size the pool for sequence depth, not just prospect count
A five-touch sequence consumes roughly five sends per prospect over its lifetime, so depth multiplies your capacity math. At 2 outbound sends/day per mailbox (4 sends/day total — 2 outbound + 2 warmup), a 25-mailbox pool moves 50 sends a day, which sustains about 10 new prospects entering the sequence daily once follow-ups are flowing. Most founders start at 20-40 mailboxes on one secondary domain — ColdRelay supports 100-150 mailboxes per domain, so the same domain absorbs the scale-up. Provisioning on isolated Azure tenants with dedicated IPs takes about an hour, DNS already configured.
Connect the mailboxes in Woodpecker and cap daily sends at 2
Export your mailbox credentials from the ColdRelay dashboard, then add each one in Woodpecker under email accounts via SMTP/IMAP. Set every account's daily sending limit to 2 outbound emails to mirror ColdRelay's per-mailbox budget — 4 sends/day total, split 2 outbound + 2 warmup. Skip any additional warmup layer on these accounts; ColdRelay's continuous warmup already occupies the other half of the budget.
Build the five-touch sequence with founder-authentic intervals
In the Woodpecker campaign editor, write all five touches upfront — the discipline happens now, while you have the time, not in week three when you won't. Use Woodpecker's human-like sending intervals and irregular day gaps (try 3, 5, 8, 12 days between touches) so the cadence reads like a busy founder circling back, not a cron job firing. Each follow-up should add something new — a customer result, a relevant launch, a sharper question — never 'just bumping this.'
Add condition-based follow-up paths so touches adapt
Use Woodpecker's if-opened and if-clicked conditions to branch the path: a prospect who opened twice but never replied gets a direct 'wrong time or wrong person?' nudge, while a prospect who never opened gets a fresh subject line on a different day of the week. This is what manual follow-up can't do at any volume — remember per-prospect behavior across five touches and adjust. Replies stop the sequence automatically, so persistence never tips into pestering.
Turn on timezone delivery and deliverability monitoring, then launch
Enable Woodpecker's timezone-aware delivery so touch four lands in each prospect's morning rather than your own, and keep its per-campaign deliverability monitoring open alongside ColdRelay's infrastructure view — Woodpecker watches the campaign, ColdRelay watches the mailboxes and IPs. Then launch and leave it alone. The whole point is that the sequence runs through your fundraise week, your incident week, and your conference week without you touching it.
The Founder-Persistence Woodpecker Playbook
Front-load your best material into touches three through five
Most founders spend all their ammunition on email one and leave the follow-ups as afterthoughts — exactly backwards, since the later touches are where replies concentrate. Put your strongest proof point in touch three and your most disarming, honest ask in touch five. Write them all before launch in Woodpecker's editor, while you still have the energy of a fresh campaign, because future-you in a fundraise week will not.
Let the branches do the remembering
The reason founders abandon follow-ups isn't laziness — it's that tracking who opened what across 200 prospects and five touches is a full-time job nobody hired for. Woodpecker's condition-based paths carry that memory: opened-but-silent prospects get the direct ask, never-opened prospects get a new subject line, clickers get the meeting link. You make the branching decisions once, at design time, and the system applies them per prospect forever.
Schedule around their Tuesday morning, not your 11pm
Manual founder follow-ups go out whenever the founder finally gets to them — which is usually late at night, the worst hour for a B2B reply. Woodpecker's timezone-aware delivery sends each touch in the prospect's local business morning regardless of when you built the sequence or what continent you're fundraising on. Touch four arriving at their 9:15am Tuesday looks deliberate; the same email at your 11:40pm looks like what it is.
A/B test the follow-up, not the opener
Everyone tests subject lines on email one; almost nobody tests touch four, even though that's where a sequence lives or dies. Use Woodpecker's A/B testing on the later touches — a breakup-style touch five against a value-add touch five, a question close against a calendar link — and let the variant data decide. Because the sends run automatically on ColdRelay infrastructure at a steady 2 outbound per mailbox per day, the test accumulates clean data whether or not you looked at the dashboard that week.
Typical Founder-Led Persistence Benchmarks (Woodpecker + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants hold placement steady across all five touches, not just the first |
| Share of replies arriving on touches 3-5 | 40-60% | The follow-ups manual discipline never reaches are where the pipeline actually is |
| Follow-up completion rate | 100% vs ~20% manual | Automated sequences finish every path; founder-managed follow-ups collapse the first busy week |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup |
| Full-sequence reply rate | 4-8% | A completed five-touch sequence typically doubles the reply rate of a first-touch-only campaign |
What It Costs: Woodpecker + ColdRelay
You pay per mailbox per month for the infrastructure, with volume tiers that drop as you scale (see the table below). DNS, dedicated IPs, and isolated Azure tenants are included — and a 20-40 mailbox pool sized for a five-touch sequence stays comfortably inside an early-stage budget.
Woodpecker is billed separately on its own subscription, covering the campaign editor, condition-based follow-up paths, timezone-aware delivery, A/B testing, and per-campaign deliverability monitoring.
One infrastructure bill that scales with mailbox count, one software bill that stays founder-sized. The combination is cheapest where it counts: the marginal cost of touches three through five is zero, and those are the sends doing most of the converting.
| 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 one stack. Woodpecker handles sequencing: follow-up paths, if-opened and if-clicked branching, timezone-aware delivery, A/B testing, and campaign-level deliverability monitoring. ColdRelay provides the secondary domains, mailboxes, and dedicated IPs those sequences send from. You use both together: ColdRelay as the infrastructure layer underneath, Woodpecker as the sending and sequencing layer on top.
Won't a five-touch sequence eat my 2-a-day send budget?
It changes the math, but predictably. Each mailbox sends 4 emails/day total — 2 outbound + 2 warmup — and follow-ups draw from the same 2 outbound sends as first touches. A five-touch sequence means each prospect consumes about five sends over its lifetime, so a 25-mailbox pool at 50 outbound sends/day sustains roughly 10 new prospects entering daily at steady state. If you want more throughput, add mailboxes on ColdRelay — about an hour to provision, 100-150 per domain — rather than cutting sequence depth, because depth is where the replies are.
Should I pause my Woodpecker campaigns during a fundraise or crunch week?
No — that week is exactly what this setup exists for. The sequence was fully written at design time, Woodpecker's conditions handle per-prospect branching, replies stop a prospect's path automatically, and ColdRelay's continuous warmup keeps the mailboxes healthy with zero attention from you. The only thing that should compete for your time during a crunch is answering the replies — and those can usually wait a day without dying, unlike a follow-up cadence that breaks permanently once abandoned.
Will sending five follow-ups get us flagged as spam?
Not when the persistence is built properly. Woodpecker's human-like sending intervals and irregular day gaps keep the cadence looking like a person circling back, condition-based paths stop the sequence the moment someone replies, and each follow-up carrying new substance reads as diligence rather than nagging. Underneath, ColdRelay's isolated Azure tenants with dedicated IPs and pre-configured SPF, DKIM, and DMARC keep placement at 95%+ across every touch — and Woodpecker's per-campaign deliverability monitoring gives you an early warning if any single campaign starts drifting.