Stop Sending Follow-Up Three to Everyone
Most staffing BD sequences treat every prospect identically: the same follow-up three goes to the HR director who opened your last two emails and to the one who never saw the first. That's a wasted read on one side and a wasted send on the other. The prospect who keeps opening is telling you they're curious about your bench; the one who hasn't is telling you the angle is wrong, not necessarily the timing.
Woodpecker is built for exactly this fork in the road. Its condition-based follow-up paths split a campaign on behavior — if-opened, if-clicked, if-not-opened — so engaged prospects can graduate to concrete roles-available alerts while cold ones get a different, lighter angle entirely. ColdRelay is the layer underneath: the secondary domains, mailboxes, and dedicated IPs Woodpecker sends from. This guide covers building a behavior-branched client BD motion on that stack, including a third path for the moment a prospect's job postings show they're hiring right now.
Why Run Woodpecker on ColdRelay Infrastructure
Woodpecker's strength is adaptive sequencing: condition-based campaign paths that branch on opens and clicks, timezone-aware delivery so each prospect gets the email in their own working morning, human-like sending intervals that keep volume looking like a person, and per-campaign deliverability monitoring that tells you when a specific campaign is starting to slip. For a staffing firm, that toolkit means one campaign can quietly run three conversations at once — a bench-availability track, a market-content track, and an urgency track — without anyone manually re-sorting lists.
What Woodpecker doesn't provide is the sending infrastructure itself. It sends from whatever mailboxes you connect, and their reputation is yours to build. That's the ColdRelay layer: dedicated mailboxes on isolated Azure tenants with dedicated IPs, DNS (SPF, DKIM, DMARC) pre-configured, live in about an hour, with no warmup period before they can send — warmup runs continuously as part of each mailbox's 4 sends/day budget (2 outbound + 2 warmup). ColdRelay supports 100-150 mailboxes per domain, so a branched BD motion fits comfortably on one or two secondary domains.
The two are complementary layers, not competitors: Woodpecker decides which branch each prospect walks down; ColdRelay makes sure every branch actually reaches the inbox. A conditional path is only as smart as the deliverability of the emails it routes.
Visit Woodpecker →Building a Branched Client BD Campaign in Woodpecker on ColdRelay Mailboxes
Provision ColdRelay mailboxes on secondary domains
Order mailboxes on domains adjacent to your firm's brand — never the primary domain that carries contracts, submittals, and payroll. They provision on isolated Azure tenants with dedicated IPs in about an hour, with SPF, DKIM, and DMARC pre-configured and no warmup period before sending. ColdRelay supports 100-150 mailboxes per domain, and a behavior-branched BD motion is targeted rather than massive, so most firms start with a compact pool.
Connect the mailboxes in Woodpecker and skip its warm-up
Add each ColdRelay mailbox as a sending account in Woodpecker via SMTP/IMAP and cap it at 2 outbound emails per day. That mirrors ColdRelay's per-mailbox budget of 4 sends/day total — 2 outbound + 2 warmup — with warmup running continuously on ColdRelay's side, so leave Woodpecker's warm-up features off rather than warming the same mailbox twice.
Build the campaign with condition-based follow-up paths
Use Woodpecker's if-conditions to fork the sequence after the opener. The if-opened path graduates to a roles-available alert — named, vetted candidates for the role families the prospect hires: 'three credentialed surgical techs available for March starts.' The if-not-opened path switches angle instead of escalating: a short market-trend note with a new subject line, because a prospect who never saw email one needs a different hook, not a louder bench pitch. The if-clicked path skips straight to a booking ask.
Add the surge path for prospects who start hiring mid-sequence
Build a third, faster campaign for active hiring signals. When your weekly check of job boards or posting data shows a prospect just opened multiple reqs in your specialty, move them from the nurture campaign into the surge path — tighter intervals, a first line that names the open roles, and a this-week availability CTA. Woodpecker's human-like sending intervals keep even the faster cadence looking like a person typing, not a blast.
Turn on timezone delivery, A/B test per branch, and watch deliverability per campaign
Enable Woodpecker's timezone-aware delivery so a hiring manager in Phoenix and one in Boston each get the email mid-morning their time — staffing decisions get made before lunch, not at 6 p.m. A/B test openers separately inside each branch, since what wins for engaged prospects rarely wins for cold ones. Then keep Woodpecker's per-campaign deliverability monitoring open: if the not-opened branch starts slipping, it warns you there before it stains the rest of the pool.
The Behavior-Branched BD Playbook for Woodpecker
Let the open decide the next email
An open is a small but real vote of interest, and Woodpecker's if-conditions let you act on it automatically. Prospects who keep opening have earned specificity — actual candidate availability, credentials, start dates. Prospects who haven't opened anything haven't rejected your bench; they've rejected your subject line, so the not-opened branch should change the angle and the sender name pattern, not repeat the pitch with 'just bumping this.'
Save the bench alert for prospects who asked for it with their behavior
Leading every sequence with available candidates burns your scarcest asset — a real bench changes weekly, and an alert sent to someone who never opens is inventory wasted. Gate the roles-available email behind engagement: it lands only on the if-opened path, where it reads as a useful heads-up to someone already curious instead of a cold pitch. When that candidate is placed, the alert in flight gets updated, which only stays manageable because the branch keeps the audience small.
Promote prospects between paths when the hiring signal fires
A prospect sitting calmly in your nurture branch becomes a different prospect the week they post six reqs. Run a standing weekly review of posting signals against your active Woodpecker campaigns and manually promote matches into the surge path — the cold-path market note they were due for is the wrong email when they're staring at open seats. The reverse matters too: when a surge prospect's postings close, demote them back to nurture instead of pestering a solved problem.
Read per-campaign deliverability like a smoke detector
Branched campaigns create a diagnostic advantage: each path is its own deliverability sample. Woodpecker monitors deliverability per campaign, so when the not-opened branch — the one sending to your least-engaged audience — starts degrading first, that's your early warning to refresh copy or rest that segment before the damage spreads. Treat the engaged branch's numbers as your baseline and the cold branch's numbers as the canary.
Typical Behavior-Branched BD Benchmarks (Woodpecker + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants — branching logic is worthless on emails that land in spam |
| Reply rate on the engaged (if-opened) branch | 8-12% | Roles-available alerts to prospects who already opened twice outperform flat sequences |
| Reply rate on the surge-escalation path | 9-14% | Triggered when posting signals show active hiring; names the open roles in line one |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup |
| Time to first campaign | Same day | ~60 minutes to provision mailboxes, plus branch and condition setup in Woodpecker |
What It Costs: Woodpecker + ColdRelay
Billed per mailbox per month, with volume tiers that drop as you scale (see the table below). DNS, dedicated IPs, and isolated Azure tenants are included — and because a branched BD motion spends sends more efficiently than a flat blast, most firms run it on a smaller pool than volume outreach would need.
Woodpecker is a separate subscription covering condition-based campaigns, timezone delivery, A/B testing, deliverability monitoring, and its agency panel for firms running multiple divisions — priced per its current plans.
Woodpecker's cost buys the routing intelligence; ColdRelay's buys deliverable capacity. They scale independently — adding a new branch or division is a Woodpecker decision, adding send volume is a mailbox decision — so neither bill forces the other's hand.
| 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 is the sending and sequencing software: condition-based follow-up paths, timezone-aware delivery, A/B testing, and deliverability monitoring. ColdRelay is the infrastructure underneath: secondary domains, mailboxes, and dedicated IPs on isolated Azure tenants that Woodpecker sends from. Staffing firms run both together — Woodpecker routes each prospect down the right branch, ColdRelay gets every branch into the inbox.
Should we run Woodpecker's warm-up on ColdRelay mailboxes?
No. ColdRelay mailboxes are warmed continuously on ColdRelay's side as part of each mailbox's 4 sends/day budget — 2 outbound + 2 warmup — with no warmup period needed before sending. Stacking Woodpecker's warm-up on top double-warms the same mailbox, which spends budget without adding reputation. Connect the mailboxes for outbound only and cap each at 2 sends/day in Woodpecker.
How many mailboxes does a branched client BD motion need?
Usually fewer than a flat-volume campaign, because branching concentrates sends where they work. A desk nurturing 400-800 client prospects across three paths — engaged, cold, and surge — runs comfortably on 20-40 mailboxes at 2 outbound sends/day each (4/day total with 2 warmup), follow-ups included. That fits on a single secondary domain, since ColdRelay supports 100-150 mailboxes per domain, with headroom as new divisions get their own Woodpecker campaigns.
A prospect in our nurture sequence just posted a dozen open roles — can we escalate them immediately?
Yes. Move them out of the nurture campaign and into your surge path in Woodpecker the same day — the faster cadence and roles-naming opener are the right email for that week, and Woodpecker's human-like sending intervals keep the tighter rhythm looking natural. If the surge means you also need more capacity, new ColdRelay mailboxes provision in about an hour on isolated Azure tenants with dedicated IPs, DNS pre-configured, and need no warmup period before sending.