The Renewal-Window Long Game for IT Services, Run Through Woodpecker
Almost every business an MSP wants is already someone else's client — locked into a managed services agreement that renews once a year. Cold email can't break that contract, and it doesn't need to. The deal goes to whoever is present and familiar in the narrow window when the contract comes up and the incumbent has just fumbled a ticket. The problem is that you can't know which week that window opens for any given prospect — so the winning motion isn't a three-week blast, it's a patient, always-on drip that keeps your firm quietly in view for months and then accelerates the moment a prospect shows interest.
Woodpecker is unusually well built for that shape of campaign: condition-based follow-up paths that branch on whether a prospect opened or clicked, timezone-aware delivery per prospect, and per-campaign deliverability monitoring that keeps a sequence healthy over a lifespan measured in quarters. ColdRelay is the layer underneath — the secondary domains, dedicated mailboxes, and dedicated IPs those long-running sequences send from. This guide covers wiring the two together and running outbound as a waiting game you're set up to win.
Why Run Woodpecker on ColdRelay Infrastructure
Woodpecker handles the patience: campaigns with follow-up delays as long as you like, if-opened and if-clicked conditions that change a prospect's path based on behavior, human-like sending intervals that keep the cadence natural, and a Deliverability Monitor that flags when a campaign's placement starts to slip. What it doesn't handle is the infrastructure those campaigns send from — Woodpecker connects to whatever mailboxes you give it, and it doesn't provision domains or guarantee they deliver.
That's where ColdRelay fits. Instead of buying workspace seats and configuring DNS by hand, you order dedicated mailboxes on isolated Azure tenants with dedicated IPs, fully DNS-configured (SPF, DKIM, DMARC) and ready in about an hour. Connect them to Woodpecker and every touch in the long drip sends from infrastructure built to land.
The pairing matters more for this motion than for any burst campaign, because an always-on sequence ages. A campaign that runs for nine months gives mailbox reputation nine months to drift — and a quarterly touch that quietly slides into spam in month five defeats the entire strategy, since presence in the inbox is the product. ColdRelay's continuous warmup and 95%+ inbox placement keep the sending side healthy for the campaign's whole life, while Woodpecker's per-campaign monitoring gives you the gauge to verify it. ColdRelay is the infrastructure, Woodpecker is the sequencing layer on top — additive, not competitive.
Visit Woodpecker →Connecting ColdRelay Mailboxes to Woodpecker
Provision a small, durable mailbox pool on ColdRelay
Pick secondary domains related to but separate from your primary firm domain — clients open tickets on the main one, so it never touches outbound. The long-interval motion is volume-light by design: with weeks between touches, 10-25 mailboxes keeps several hundred prospects in active rotation, well under the 100-150 mailboxes per domain ColdRelay supports. Everything provisions on isolated Azure tenants with dedicated IPs in about an hour, with SPF, DKIM, and DMARC already configured.
Connect the mailboxes in Woodpecker and cap sends to the ColdRelay budget
In Woodpecker, go to Settings → Email accounts and connect each ColdRelay mailbox via SMTP/IMAP using the credentials exported from the ColdRelay dashboard. Set each account's daily sending limit to 2 outbound emails per day, mirroring ColdRelay's per-mailbox budget — 4 sends/day total per mailbox, split 2 outbound + 2 warmup. Leave Woodpecker's human-like sending intervals on so the low daily volume also paces naturally within the day.
Build the long-interval drip with condition-based follow-up paths
Create the campaign in Woodpecker's editor as a drip designed to run for quarters, not weeks: a useful opener, then follow-ups spaced 4-6 weeks apart, each one a small piece of standalone value — an outage post-mortem lesson, a renewal-checklist tip, a note on a vendor price change. After each touch, insert a Woodpecker condition step (if-opened / if-clicked) so behavior, not the calendar alone, decides each prospect's next path. Enable timezone-aware delivery so every touch lands in the prospect's business morning regardless of where in your service area they sit.
Add the if-clicked escalation branch
Give the quiet drip exactly one link per touch — your services or pricing page. Then build the escalation path: on Woodpecker's if-clicked condition, the prospect leaves the slow lane and enters a short, direct three-email pursuit over two weeks, ending in a concrete ask for a 20-minute contract-comparison call. A click on a services page months into a quiet drip is a prospect telling you their evaluation window just opened — the branch makes sure your follow-up speed matches their timing, automatically.
Turn on the Deliverability Monitor, A/B test the touch, and launch
Enable Woodpecker's per-campaign deliverability monitoring before launch — for a campaign meant to run most of a year, it's the smoke detector, not a nice-to-have. Use Woodpecker's A/B testing on the recurring touch itself (a tip-led variant against a proof-led variant) so the message improves across cycles instead of fossilizing. Then launch and let it run; this campaign's job is to still be working in month eight.
The Renewal-Window Woodpecker Playbook for IT Services
Design the sequence in quarters, because that's how MSP contracts move
A standard five-email, three-week sequence asks a question most of your market can't say yes to: they're under contract, and no amount of copy fixes that. Build the Woodpecker campaign for the actual buying cycle instead — touches spaced 4-6 weeks apart, each useful enough to be welcome on its own, running until the prospect replies, clicks, or churns off the list. The per-touch reply rate looks modest; the compounding doesn't. By the time a renewal approaches, the prospect has heard from you five or six times without ever feeling chased — and familiarity is what gets the second quote requested.
Treat a click as the renewal window opening, and let the branch do the sprinting
Nobody idly browses an MSP's pricing page. When a prospect who's ignored four quarterly touches suddenly clicks the services link, something changed — a renewal notice arrived, an outage went unresolved, the incumbent's account manager quit. Woodpecker's if-clicked condition turns that moment into an automatic gear change: the prospect exits the slow drip and enters a two-week active pursuit while the frustration is still warm. The asymmetry is the point — you run hundreds of prospects at near-zero effort, and the sequence itself concentrates your energy on the handful whose window just opened.
Mine "we're under contract until March" replies — they're the best outcome a touch can produce
The most common reply to MSP cold email reads like a rejection and is actually a gift: a named renewal date from the prospect's own keyboard. Build the operational habit around it — log the date in your CRM the day the reply lands, pause the prospect in Woodpecker, and re-enroll them in a short pre-renewal sequence timed to start about 90 days before the contract turns, when procurement rules and notice periods still allow a switch. A list of fifty prospects with known renewal dates is worth more than five thousand cold contacts, and the drip's only job for those fifty is to make sure you're the firm they already know when the date arrives.
Audit campaign health monthly — an always-on campaign fails silently if you let it
A three-week blast either works or it doesn't, and you find out fast. A nine-month drip can decay invisibly: placement slips in month five, opens fade, and you keep paying for touches that land in spam. Put a monthly health check on the calendar — Woodpecker's Deliverability Monitor per campaign for placement trend and open-rate drift, the ColdRelay dashboard for mailbox-level reputation underneath. If a mailbox degrades, rotate it out of the campaign and let a fresh one take its slots; because ColdRelay warmup runs continuously as part of each mailbox's 4/day budget (2 outbound + 2 warmup), replacements are ready without a ramp-up gap. Presence is the entire strategy — verify it like you verify backups.
Typical Renewal-Window Benchmarks (Woodpecker + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants outperform shared Google/Microsoft pools — and hold up over month-long campaign lifespans |
| Reply rate per quarterly touch | 1-3% | Low per touch by design; compounds across five or six touches a year per prospect |
| Reply rate on the if-clicked escalation branch | 10-20% | Prospects enter the branch by signaling intent — clicked prospects behave like warm leads, not cold ones |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup |
| First touch to signed agreement | 6-12 months | Bounded by the incumbent's contract calendar, not your copy — which is why the campaign must outlast it |
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 because long-interval drips are volume-light, a 10-25 mailbox footprint covers most of this motion, making it one of the cheapest infrastructure profiles in cold email.
Woodpecker is billed separately on its own subscription for campaigns, condition-based follow-up paths, timezone-aware delivery, A/B testing, and the Deliverability Monitor — priced per its current plans, typically per connected mailbox or seat.
Infrastructure cost scales with mailbox count; Woodpecker's cost scales with its plan tier. Both stay small here, and that's the strategic point — the always-on motion is cheap enough to run indefinitely, which is exactly what a strategy built on outlasting contract cycles requires.
| 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
Does ColdRelay replace Woodpecker?
No — they're complementary layers of one stack. Woodpecker is the sequencing software: condition-based campaigns with if-opened and if-clicked paths, timezone-aware delivery, A/B testing, and per-campaign deliverability monitoring. ColdRelay is the infrastructure underneath: the secondary domains, dedicated mailboxes, and dedicated IPs those campaigns actually send from. You connect ColdRelay mailboxes in Woodpecker's email account settings and run both together.
Won't emailing the same prospect for nine months annoy them?
Not at this cadence and quality. A touch every 4-6 weeks is five or six emails a year — less than most vendors' newsletters — and each one carries something genuinely useful rather than a repeated pitch. The structure protects you too: Woodpecker's condition paths move anyone who engages into a faster lane, replies pull prospects out for human handling, and unsubscribes are honored immediately. What actually annoys prospects is five emails in ten days asking for a meeting they can't take because they're under contract.
How many mailboxes does the long-interval motion need?
Fewer than any other MSP outbound play. With touches spaced 4-6 weeks apart, each prospect consumes roughly one send a month — so at 2 outbound sends/day per mailbox (half of the 4/day total budget, the rest being continuous warmup), a 15-mailbox pool comfortably keeps 600-800 prospects in active rotation. Most firms start with 10-25 mailboxes on one or two ColdRelay domains and only scale up if they expand the prospect universe; ColdRelay supports 100-150 mailboxes per domain when they do.
Do I need a warmup period before launching, and what keeps deliverability healthy months in?
No separate warmup period — ColdRelay mailboxes warm continuously, 2 warmup sends/day per mailbox as part of the 4/day total alongside 2 outbound, so you can provision in the morning and launch the drip the same day. For the long run, the two layers split the job: ColdRelay's continuous warmup and dedicated IPs maintain mailbox reputation underneath, while Woodpecker's Deliverability Monitor watches each campaign's placement on top. Check both monthly; if a mailbox drifts, swap a fresh one into the campaign with no ramp-up gap.