The Agency's Own Pipeline, Run Through Instantly
This page is about one motion only: the outbound an agency runs for itself. Not campaigns delivered for clients — the always-on machine that fills your own pipeline with retainer conversations, quarter after quarter. It's the motion agencies are famously bad at sustaining, because the moment client work gets busy, the agency's own outbound is the first thing that stops.
Instantly is a natural fit for this machine: a fast campaign builder, A/Z variant testing for trying positioning angles against each other, and the Unibox for working replies without living in twelve inboxes. ColdRelay is the layer underneath — the secondary domains, mailboxes, and dedicated IPs Instantly actually sends from. This guide covers wiring the two together and, more importantly, running the machine so it never goes dark.
Why Run Instantly on ColdRelay Infrastructure
Instantly's paid plans let you connect unlimited email accounts — but unlimited connections only matter if you have good mailboxes to connect. Instantly doesn't provision domains, configure DNS, or carry the sending reputation of the accounts you plug in. That's the infrastructure layer, and for an agency pitching its own services, it's the layer your first impression rides on.
ColdRelay fills it. You order mailboxes on isolated Azure tenants with dedicated IPs — SPF, DKIM, and DMARC pre-configured — and they're ready in about an hour. ColdRelay supports 100-150 mailboxes per domain, so an agency's own pipeline pool typically fits on one or two secondary domains, leaving the agency's primary domain — the one on your proposals and invoices — untouched by outbound.
The pairing is additive, not competitive: ColdRelay is the infrastructure, Instantly is the sending and sequencing layer on top. You keep Instantly's campaign builder, A/Z testing, and Unibox — you just feed it mailboxes built to land.
Visit Instantly →Connecting ColdRelay Mailboxes to Instantly
Provision the new-business pool on ColdRelay
Pick one or two secondary domains close to your agency brand and provision the pool there — ColdRelay supports 100-150 mailboxes per domain, and everything goes live on isolated Azure tenants with dedicated IPs in about an hour, DNS (SPF, DKIM, DMARC) pre-configured. This pool exists for one job: the agency's own pipeline.
Bulk-import via CSV in Instantly
Export your mailbox credentials from the ColdRelay dashboard and use Instantly's Email Accounts → Add New → Bulk Import via CSV to connect everything over SMTP/IMAP in one pass. Because Instantly's paid plans don't cap connected accounts, the whole pool comes in at once — no per-seat math.
Set sending limits and skip double-warmup
Set each account's daily campaign limit in Instantly to 2 outbound emails per day, matching ColdRelay's per-mailbox budget of 4 sends/day total — 2 outbound + 2 warmup. Warmup runs continuously on ColdRelay's network, so leave Instantly's own warmup off rather than burning your send budget warming twice.
Build one campaign per service line, with A/Z variants
In Instantly's campaign builder, create a separate campaign for each service line you sell — paid media, SEO, lifecycle, creative — and load A/Z variants that test different positioning angles for that line. Attach the shared ColdRelay pool to all of them; capacity is pooled, positioning data stays per-campaign.
Make Unibox the daily ritual
Route every reply into the Unibox and block fifteen minutes a day — calendar-protected, even in delivery crunch weeks — to triage it. Check Instantly's campaign analytics weekly to kill losing variants and promote winners. The machine only compounds if someone actually works the replies.
The Agency New-Business Instantly Playbook
Treat each service line as a positioning experiment
Most agencies pitch 'full-service' and convert nobody. Run each service line as its own Instantly campaign with A/Z variants testing a different sharp claim — 'we cut CAC on paid social' vs. 'we rebuild your funnel measurement' — and let reply data tell you which line and which framing actually opens doors. The losing variants are cheap; the winning one becomes your homepage.
Map proof points to verticals, not to campaigns
Keep a library of results organized by prospect vertical — e-commerce, B2B SaaS, healthcare, local services — and build Instantly campaigns that pull the matching proof into the first line. An e-commerce founder skims past your SaaS win; the same email with a same-vertical number gets a reply. One campaign per vertical, one proof point per campaign, rotated quarterly as new results land.
Write to the budget calendar
Agency retainers get signed when budgets move, so the copy should move with them. September–October sequences speak to next year's plan ('who's owning paid growth in your 2027 budget?'); January sequences speak to the reset ('new budget, same agency — worth a second opinion?'); end-of-quarter sequences catch unspent dollars. Same pool, same Instantly campaigns — only the angle and CTA rotate with the calendar.
Set a send floor, not a send goal
The classic agency failure is feast-or-famine: outbound sprints when the pipeline is dry, dead silence when delivery is busy — which guarantees the pipeline is dry again in ninety days. Set a minimum the machine never drops below — every mailbox sending its 2 outbound/day (of the 4/day total, with 2 warmup), Unibox triaged daily — and treat it like a client deliverable with your agency as the client. Pausing doesn't just cost sends; it costs the compounding reply data your A/Z tests are built on.
Typical Agency New-Business Benchmarks (Instantly + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants outperform shared Google/Microsoft pools |
| Reply rate (agency new-business) | 3-6% | Vertical-matched proof points; peaks in Sept-Oct planning and January budget resets |
| Strategy calls booked per 1,000 outbound sends | 8-15 | Assumes a conversation CTA, not a proposal ask; varies by service line |
| 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 on ColdRelay, plus campaign setup in Instantly |
What It Costs: Instantly + 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 the new-business pool is a fixed monthly line item, it budgets like the marketing spend it is.
Instantly is billed separately on its own subscription for the campaign builder, A/Z testing, Unibox, and analytics — and since paid plans don't charge per connected email account, its cost stays flat as your ColdRelay pool grows.
Infrastructure cost scales with mailbox count; Instantly's cost scales with plan tier, not accounts. For an agency, the whole machine is a predictable fixed cost against pipeline generated — the easiest ROI math in your P&L.
| 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; Instantly handles the sending, sequencing, and inbox rotation on top.
Frequently Asked Questions
Does ColdRelay replace Instantly?
No — they're complementary layers, not competitors. Instantly is the sending and sequencing layer: campaigns, A/Z variant testing, the Unibox, analytics. ColdRelay is the infrastructure layer underneath: the secondary domains, mailboxes, and dedicated IPs Instantly sends from. You use both together — one is the software, the other is what the software sends through.
Instantly offers unlimited email accounts — so why do I need ColdRelay?
Unlimited refers to how many accounts you can connect to Instantly, not where those accounts come from. Someone still has to provision the domains, create the mailboxes, configure SPF, DKIM, and DMARC, and carry the sending reputation. ColdRelay does that — mailboxes on isolated Azure tenants with dedicated IPs, ready in about an hour — and Instantly's unlimited connections mean the whole pool plugs in without raising your software bill.
Should we pause our own outbound when client work gets busy?
No — that's the cycle that creates agency feast-or-famine. The infrastructure side runs itself: warmup continues automatically as part of each mailbox's 4 sends/day budget (2 outbound + 2 warmup), and campaigns keep rotating without intervention. The only human commitment is a daily Unibox pass. Keep the send floor running through crunch periods and the pipeline is there when the retainer ends — instead of starting cold ninety days too late.
How many mailboxes does an agency need for its own pipeline?
Less than you'd think, if it runs consistently. At 2 outbound sends/day per mailbox, 25 mailboxes is 50 sends/day — roughly 1,000 prospects a month at steady state, enough to keep most agencies' calendars full of strategy calls. Scale the pool on ColdRelay ahead of budget season (September and December) when you want extra reach; with 100-150 mailboxes supported per domain, growth rarely needs new domains.