Fintech Outbound, Scaled into SDR Pods
This page is for the fintech team whose outbound already works. You've found the persona, the message converts, and now the board wants the motion to carry a real pipeline number — which means hiring SDRs and multiplying send volume without breaking the thing that got you here. Smartlead is built for exactly this stage: campaign-level mailbox rotation spreads volume across a pool instead of concentrating it, sub-accounts give each SDR pod its own clean workspace, the master inbox keeps reply handling centralized, and the API and webhooks push every reply into your CRM so pipeline attribution survives the headcount growth.
What Smartlead doesn't provide is the mailbox capacity itself — and scaling is where infrastructure decisions get expensive to unwind. That's ColdRelay's job: the secondary domains, mailboxes, and dedicated IPs that Smartlead rotates across. This guide covers how fintech teams structure pods, do the capacity math against a pipeline target, and keep deliverability flat while volume 5x's.
Why Run Smartlead on ColdRelay Infrastructure
Smartlead is a sending and sequencing platform — its rotation engine distributes campaign sends across however many mailboxes you connect under Email Accounts. But rotation only protects you if every mailbox in the pool is healthy; one weak sender in a rotation drags the campaign's aggregate placement down, and at fintech scale you're rotating across hundreds of mailboxes, not dozens. Provisioning that pool is the infrastructure layer's job.
ColdRelay solves the infrastructure half in a way that's built for scaling events. Mailboxes provision on isolated Azure tenants with dedicated IPs, fully DNS-configured (SPF, DKIM, DMARC), in about an hour — so growing a pod's pool from 50 to 250 mailboxes is a same-day order, not a multi-week project. There's no warmup waiting period gating the new capacity either: warmup runs continuously as part of each mailbox's 4 sends/day budget (2 outbound + 2 warmup), so new mailboxes join the rotation immediately and build reputation while they work.
The pairing is additive, not competitive: ColdRelay is the infrastructure, Smartlead is the sending and sequencing layer on top. You keep Smartlead's rotation, sub-accounts, master inbox, and webhooks — you just feed them a mailbox pool uniform enough that 5x volume doesn't mean 5x deliverability variance.
Visit Smartlead →Connecting ColdRelay Mailboxes to Smartlead for Pod-Scale Sending
Do the capacity math, then provision on ColdRelay
Work backwards from the pipeline target. If each SDR pod needs to put 100 prospects/day into sequence and each ColdRelay mailbox contributes 2 outbound sends/day (4 sends/day total, split 2 outbound + 2 warmup), a two-SDR pod sharing a pool needs roughly 100 mailboxes. ColdRelay supports 100-150 mailboxes per domain, so each pod's pool fits on one secondary domain — provisioned on isolated Azure tenants with dedicated IPs in about an hour, SPF, DKIM, and DMARC pre-configured.
Create a Smartlead sub-account per pod
Use Smartlead's client sub-accounts to give each SDR pod its own workspace — campaigns, mailboxes, and reporting stay scoped to the pod. This is the structure that keeps a four-pod org legible: when pod B's reply rate dips, you can see it without untangling it from pod A's numbers.
Bulk-import each pod's mailbox pool
Export each pool's SMTP/IMAP credentials from the ColdRelay dashboard and use Smartlead's bulk CSV import under Email Accounts to connect the whole pod pool in one upload. Set every mailbox's daily limit to 2 outbound emails per day to mirror ColdRelay's budget — 4 sends/day total per mailbox, 2 outbound + 2 warmup, with warmup left to ColdRelay's network.
Attach the shared pool to pod campaigns and enable rotation
Inside each sub-account, attach the full pod pool to the pod's campaigns and let Smartlead's campaign-level mailbox rotation distribute sends across all of it. Both SDRs in a pod draw from the same shared pool rather than splitting it — rotation across 100 mailboxes is what keeps per-mailbox volume flat as the pod's total output grows. Use spintax in the templates so the rotated sends don't read as identical copies to receiving filters.
Wire webhooks into the CRM for attribution
Use Smartlead's API and webhooks to push reply events into your CRM in real time, tagged with campaign and sub-account so every opportunity traces back to a pod and a sequence. SDRs work replies from the master inbox; revops reads pipeline-per-pod from the CRM. When leadership asks which pod's motion is producing the Q3 number, the answer is a report, not an archaeology project.
The Fintech Smartlead Playbook
Scale the pool before the volume
The instinct when an SDR pod gets a bigger quota is to raise per-mailbox limits. Don't — receiving filters at financial institutions read sudden per-sender volume jumps as a compromise signal. Hold every mailbox at 2 outbound sends/day and scale by adding ColdRelay mailboxes to the rotation instead. Going from 100 to 500 daily sends should mean a pool growing from 50 to 250 mailboxes, with each individual sender's behavior unchanged.
Give each pod its own domain blast radius
Put each pod's mailbox pool on its own ColdRelay secondary domain (one domain carries 100-150 mailboxes, so the math works). If one pod's list quality slips and reputation takes a hit, the damage is contained to that pod's domain — the other pods keep sending, and your primary fintech domain was never in the picture at all.
Make the webhook the system of record
At one-founder scale, 'check the sending tool for replies' works. At four-pod scale it's how attribution dies. Treat Smartlead's webhooks as the source of truth: every reply lands in the CRM with pod, campaign, and sequence-step metadata the moment it arrives. Comp SDRs on CRM-recorded meetings, not screenshots — it keeps the data honest and the pipeline reviews short.
Staff the master inbox like a rotation, not a free-for-all
A shared pool means replies to either SDR's prospects land in the same master inbox. Assign ownership by reply, not by mailbox — Smartlead's master inbox shows which campaign generated each reply, so route it to the SDR who owns that campaign. Set a same-business-day SLA: fintech buyers who reply are rare enough that a 48-hour response time is the most expensive mistake a scaled pod can make.
Typical Fintech Outbound Benchmarks (Smartlead + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Holds flat through scaling because volume grows by adding mailboxes to rotation, not by pushing senders harder |
| Mailbox pool per two-SDR pod | 75-125 | Sized for 150-250 outbound sends/day at 2 outbound per mailbox (4/day total with 2 warmup); fits on one ColdRelay domain |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup, unchanged at any pool size |
| Meetings booked per pod per month | 10-20 | At fintech reply rates of 1-3% with same-day reply handling from the master inbox; varies with list quality |
| Time to stand up a new pod | 1-2 days | ~60 minutes to provision the pool on ColdRelay; the rest is the sub-account, CSV import, campaign cloning, and webhook routing |
What It Costs: Smartlead + ColdRelay
You pay per mailbox per month for the infrastructure, with volume tiers that drop as you scale (see the table below) — which matters at pod scale, since a four-pod org runs hundreds of mailboxes and the per-mailbox rate falls as the pool grows. DNS, dedicated IPs, and isolated Azure tenants are included.
Smartlead is billed separately on its own subscription for the campaign builder, rotation, sub-accounts, master inbox, and API access — priced per its current plans.
Infrastructure cost scales with mailbox count, which scales with your pipeline target — so the cost of capacity is a line you can forecast directly from quota math. Smartlead's cost scales with plan tier. One bill for sending capacity, one for the sending software, and a cost-per-meeting you can actually compute per pod.
| 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; Smartlead handles the sending, sequencing, and inbox rotation on top.
Frequently Asked Questions
Does ColdRelay replace Smartlead?
No — they're complementary layers. Smartlead handles sequencing, campaign-level mailbox rotation, sub-accounts, the master inbox, and the webhooks feeding your CRM; ColdRelay provides the domains, mailboxes, and dedicated IPs that Smartlead rotates across. Fintech teams scaling into SDR pods use both together: Smartlead runs the motion, ColdRelay supplies the capacity underneath it.
How do we 5x send volume without hurting deliverability?
By scaling horizontally, not vertically. Every ColdRelay mailbox stays at the same 4 sends/day budget (2 outbound + 2 warmup) no matter how big the operation gets — you add mailboxes to Smartlead's rotation rather than raising per-mailbox limits. Receiving filters at banks and finance teams see hundreds of individually conservative senders instead of a few loud ones, which is why placement holds at 95%+ through the scale-up. Provisioning the additional mailboxes takes about an hour on ColdRelay.
Should each SDR get their own mailboxes, or should a pod share a pool?
Share the pool within a pod. Two SDRs drawing from one 100-mailbox pool via Smartlead's rotation get smoother per-mailbox pacing than two separate 50-mailbox pools — when one SDR is at a conference, their half of the capacity doesn't sit idle. Separate at the pod level instead: each pod gets its own Smartlead sub-account and its own ColdRelay domain (one domain carries 100-150 mailboxes), so reporting stays clean and a reputation problem in one pod can't spread to another.
Can we get reply data out of Smartlead and into our CRM?
Yes — that's what Smartlead's API and webhooks are for, and at pod scale it's not optional. Configure webhooks to push reply events into your CRM tagged with sub-account and campaign, so every meeting and opportunity attributes back to a specific pod and sequence. ColdRelay sits below this entirely: it keeps the mailboxes landing at 95%+ placement, and the reply data flows from Smartlead to your CRM untouched.