Lean Sales Teams, Volume Without the Enterprise Stack
Not every sales team has a RevOps function, a Salesforce admin, or a cadence governance policy. A lot of B2B outbound is run by two to five people — a founder or sales lead plus a couple of SDRs — who picked Instantly precisely because it skips the enterprise overhead: a simple campaign builder, bulk account import, A/Z testing, and one Unibox for replies.
What Instantly doesn't supply is the sending infrastructure itself. The mailboxes, domains, and IPs your campaigns send from are yours to bring — and at the volumes a lean team needs to hit pipeline targets, that layer decides whether your emails land at all. This guide covers how small sales teams pair ColdRelay infrastructure with Instantly: provisioning a shared mailbox pool, structuring one campaign per ICP, and triaging the Unibox without a dedicated inbox manager.
Why Run Instantly on ColdRelay Infrastructure
Instantly's paid plans let you connect unlimited email accounts — which quietly moves the hard problem upstream. The bottleneck for a lean team isn't how many accounts the software accepts; it's sourcing mailboxes that actually reach the inbox, without someone on a three-person team spending their week buying domains, configuring DNS records, and babysitting reputation.
That sourcing job is what ColdRelay does. You order a pool of mailboxes on isolated Azure tenants with dedicated IPs, DNS (SPF, DKIM, DMARC) pre-configured, ready in about an hour. There's no warmup waiting period before you can send — warmup runs continuously as part of each mailbox's standard budget of 4 emails/day total, split 2 outbound + 2 warmup. ColdRelay supports 100-150 mailboxes per domain, so even an ambitious small team rarely needs more than a couple of secondary domains.
The two products are complementary layers, not rivals: ColdRelay is the infrastructure underneath — domains, mailboxes, dedicated IPs — and Instantly is the sending and sequencing layer on top, rotating campaigns across whatever pool you give it.
Visit Instantly →Connecting ColdRelay Mailboxes to Instantly
Provision a shared mailbox pool on ColdRelay
Pick one or two secondary domains adjacent to your brand and provision the pool — for a 2-5 person team, 30-100 mailboxes is a typical start. Everything lands on isolated Azure tenants with dedicated IPs, SPF, DKIM, and DMARC already configured, ready in about an hour. The pool belongs to the team, not to individual reps; lean teams share capacity instead of carving out per-rep allocations.
Bulk-import the accounts into Instantly via CSV
Export the mailbox credentials from the ColdRelay dashboard and use Instantly's Email Accounts → Add New → Bulk Import (SMTP/IMAP via CSV) flow. The whole pool connects in one upload — no clicking through OAuth screens thirty times — which is exactly the workflow Instantly's unlimited-accounts model is built around.
Cap each account at 2 outbound sends per day
In each account's sending settings, set the daily campaign limit to 2. That mirrors ColdRelay's per-mailbox budget — 4 emails/day total, 2 outbound + 2 warmup — with warmup handled on ColdRelay's side. Resist the temptation to raise the limit: with Instantly, scale comes from connecting more accounts, never from pushing individual mailboxes harder.
Build one campaign per ICP with A/Z variants
Create a separate Instantly campaign for each ICP you sell to, attach the full shared mailbox pool to every campaign, and load 2-3 subject/body variants into Instantly's A/Z testing from day one. Instantly rotates sends across all connected accounts automatically, and per-campaign analytics stay clean because each campaign maps to exactly one audience and one message.
Set up the Unibox and launch
All replies from every account and campaign flow into Instantly's Unibox — one inbox for the whole team. Agree on who owns triage before you launch (see the playbook below), turn the campaigns on, and you're sending the same day the infrastructure was provisioned.
The Lean Sales Team Instantly Playbook
Run a Unibox triage rotation, not an inbox owner
A five-person team can't dedicate a head to reply management, and replies left overnight go cold. Rotate Unibox duty daily: whoever owns the day labels every reply as interested, objection, or not-now within a couple of hours, books interested prospects straight to the closer's calendar, and clears the rest. One shared inbox plus one named owner per day beats five people half-watching it.
One campaign per ICP, and kill the losers monthly
Lean teams win on iteration speed, not coverage. Keep each Instantly campaign mapped to a single ICP so its analytics mean something, run A/Z variants continuously, and hold a monthly cut: any ICP campaign below your reply-rate floor gets archived and its share of the daily budget reallocated to what's working. Three sharp campaigns outperform eight neglected ones.
Size the pool to the meeting target, not to headcount
Work backwards from meetings, not reps. If you need 10 meetings a month, a 1% list-to-meeting rate means roughly 1,000 outbound emails — about 50 sends per working day, which at 2 outbound/day per mailbox is a 25-mailbox pool (each mailbox sending 4/day total: 2 outbound + 2 warmup). Because the pool is shared, adding a rep changes nothing until the meeting target does.
Graduate to enterprise tooling on process, not pain
The Instantly + ColdRelay stack is the right weight while you're still finding the message and the ICP. The signal to add a heavier engagement platform isn't frustration — it's stability: when the same two campaigns have held their reply rate for a quarter and the constraint is multi-channel orchestration or CRM governance, layer that tooling on. Your ColdRelay infrastructure moves with you; the mailbox pool doesn't care what sends through it.
Typical Lean Sales Team Benchmarks (Instantly + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Isolated Azure tenants with dedicated IPs, versus reputation-pooled shared infrastructure |
| Reply rate on cold campaigns | 3-6% | Small teams targeting tight SMB/mid-market ICPs with fast A/Z iteration trend above enterprise-motion averages |
| Team-wide cold capacity | 100/day | A shared pool of 50 mailboxes × 2 outbound/day each (4 sends/day total per mailbox — 2 outbound + 2 warmup) |
| Time to first campaign send | Same day | ~60 minutes to provision on ColdRelay, plus CSV import and campaign setup in Instantly |
| A/Z test cycle to a winning variant | 1-2 weeks | At 100 sends/day across 2-3 variants, lean teams get statistically useful reads fast enough to iterate weekly |
What It Costs: Instantly + 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 all included — there's nothing extra to buy or configure per domain.
Instantly is billed separately on its own subscription, covering the campaign builder, A/Z testing, account rotation, and the Unibox — with unlimited email account connections on paid plans.
For a lean team the math is refreshingly flat: one Instantly subscription regardless of pool size, plus a per-mailbox infrastructure bill that tracks exactly with your meeting target. Doubling capacity means adding mailboxes on ColdRelay — your software cost doesn't move.
| 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
Is ColdRelay an alternative to Instantly?
No — they're different layers of the same stack and you run them together. Instantly is the sending and sequencing layer: campaigns, A/Z testing, account rotation, and the Unibox. ColdRelay is the infrastructure layer underneath: the secondary domains, mailboxes, and dedicated IPs that Instantly's campaigns actually send from.
Instantly supports unlimited email accounts — why pay for mailboxes at all?
Unlimited connections means Instantly won't cap your pool; it doesn't make the pool exist. Someone still has to supply mailboxes that reach the inbox — domains, DNS, IPs, and reputation. ColdRelay provides that as a service: mailboxes on isolated Azure tenants with dedicated IPs and 95%+ inbox placement, instead of a teammate spending days assembling and maintaining accounts by hand.
Should we use Instantly's warmup on ColdRelay mailboxes?
No need. 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 nothing to enable in Instantly. Point Instantly at outbound sending only and keep each account's daily campaign limit at 2.
When should a small team move beyond Instantly to an enterprise sales platform?
When the process is stable, not when the team is busy. If your core campaigns have held a consistent reply rate for a quarter and the real constraint is CRM-governed cadences or multi-channel orchestration across a growing rep count, that's the time. Your ColdRelay mailbox pool carries over unchanged — the infrastructure layer is independent of whichever sending platform sits on top.