Top-of-Funnel as a Service: One Operator, Every Rep's Pipeline
There are two ways to run cold email on a sales team. The familiar one gives every rep a sequencer seat and tells them to prospect. The model this guide covers is different: cold prospecting gets pulled out of the reps' hands entirely and run as a centralized service — one RevOps person (or a small ops pod) operates all cold campaigns in Smartlead, and the output is booked meetings dropped onto reps' calendars. Reps never touch a cold sequence; they sell.
This split puts a clean seam through the stack. Everything cold — domains, mailboxes, campaigns, replies — lives on Smartlead and ColdRelay, owned by ops. Everything warm — opportunities, threads with real prospects, forecast — lives in the CRM, owned by reps. This guide covers how to build that centralized motion: provisioning the infrastructure, structuring Smartlead as a meeting factory, wiring webhook attribution into Salesforce, and sizing capacity against each rep's quota.
Why the Centralized Model Runs on Smartlead + ColdRelay
Smartlead was built for operators who run campaigns on behalf of others — its client sub-accounts, campaign-level mailbox rotation, master inbox, and API were designed for agencies, and a centralized RevOps function is structurally the same job with internal clients. One ops person can stand up a sub-account per rep (or per territory), rotate a large mailbox pool across campaigns, and work every reply from a single master inbox without logging into anything twice.
What Smartlead deliberately doesn't do is supply the sending infrastructure. The mailboxes you rotate are mailboxes you bring — and in a centralized model the operator owns that layer too. ColdRelay provides it as a service: mailboxes on isolated Azure tenants with dedicated IPs, DNS (SPF, DKIM, DMARC) pre-configured, the whole pool ready in about an hour. There's no warmup waiting period — warmup runs continuously inside each mailbox's standard budget of 4 emails/day total, 2 outbound + 2 warmup — so the operator provisions in the morning and launches the same day.
The two are complementary layers, not alternatives: ColdRelay is the infrastructure underneath — domains, mailboxes, dedicated IPs — and Smartlead is the sending and sequencing layer the operator drives on top of it. The reps' corporate domain and CRM sit on the far side of the seam, untouched by any of it.
Visit Smartlead →Building the Centralized Stack: ColdRelay into Smartlead
Provision the operator-owned pool on ColdRelay
The ops owner — not individual reps — provisions the entire sending pool on secondary domains adjacent to the brand. ColdRelay supports 100-150 mailboxes per domain, so a pool serving a 6-10 rep team typically spans 2-3 domains. Everything lands on isolated Azure tenants with dedicated IPs, SPF, DKIM, and DMARC pre-configured, ready in about an hour. One person owns every credential; reps never see a mailbox login.
Bulk-import the pool under Email Accounts in Smartlead
Export credentials from the ColdRelay dashboard and load them through Smartlead's Email Accounts → bulk CSV import. Set each account's daily campaign limit to 2 outbound emails, mirroring ColdRelay's per-mailbox budget of 4 sends/day total — 2 outbound + 2 warmup, with warmup handled continuously on ColdRelay's side. The operator does this once for the whole pool; there is no per-rep connection step.
Structure sub-accounts per rep or territory
Use Smartlead's client sub-accounts — built for agencies, perfect for internal service delivery — to give each rep or territory its own workspace. Campaigns, lead lists, and stats stay segregated per rep while the operator administers everything from the parent account. When a sales manager asks how prospecting for their pod is performing, the sub-account is the report.
Build campaigns with mailbox rotation and spintax
Create one campaign per rep-ICP pairing, attach a slice of the shared pool, and let Smartlead's campaign-level mailbox rotation spread sends across it. Because one operator's copy goes out at team-wide volume, use spintax to vary openers and phrasings across sends — a single-author motion needs engineered variation that ten reps writing their own emails would produce naturally.
Wire webhooks into Salesforce and route meetings to rep calendars
Use Smartlead's API and webhooks — the same machinery agencies use for white-label reporting — to push reply and meeting-booked events into Salesforce. Each event writes a lead with campaign source and rep assignment, so attribution survives the handoff. Interested replies get booked through the assigned rep's scheduling link; the rep's first touch with the prospect is the meeting itself, already on their calendar and already in the CRM.
The Centralized Prospecting Playbook
Run an internal SLA, not a tool rollout
The centralized model succeeds when it's framed as a service with a contract: ops commits each rep a meeting number per month, and reps commit to working what's booked. Publish the SLA, report against it from Smartlead's sub-account stats, and treat a missed month the way an agency would — with a campaign post-mortem, not a shrug. Without the SLA, centralization reads as taking prospecting away from reps; with it, it reads as giving them a pipeline vendor.
Plan capacity backwards from quota coverage
Each rep's mailbox allocation is a quota calculation, not a guess. A rep carrying quota that needs 8 sourced meetings/month, at a 0.5% send-to-meeting rate, needs roughly 1,600 sends/month — about 80 per working day, which at 2 outbound/day per mailbox is a 40-mailbox slice (each sending 4/day total: 2 outbound + 2 warmup). Multiply across the team, add 15-20% headroom for ramping reps, and that's the pool the operator provisions on ColdRelay.
Hold the master inbox until the meeting is booked
The operator works every reply in Smartlead's master inbox — qualifying, handling objections, proposing times — and only hands off once a meeting is on a rep's calendar. Forwarding raw replies to reps recreates the distributed model with extra steps and stalls threads in five different inboxes. The seam is the calendar invite: before it, ops owns the conversation; after it, the rep owns the relationship in the CRM.
Treat campaign learnings as a shared asset
Centralization's quiet payoff is that every test compounds. When one operator runs all campaigns, a subject line that wins in one rep's territory rolls out to every sub-account the same week — distributed teams rediscover the same lessons ten times. Keep a living doc of winning angles per ICP, fed by Smartlead's campaign analytics, and review it with sales leadership monthly so message strategy stays a team asset rather than tribal knowledge.
Typical Centralized Prospecting Benchmarks (Smartlead + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Isolated Azure tenants with dedicated IPs, managed by one operator instead of per-rep account sprawl |
| Sourced meetings per rep per month | 6-12 | The SLA metric of the centralized model; varies with ICP seniority and list quality |
| Send-to-meeting conversion | 0.4-0.8% | The planning ratio for capacity math — a 40-mailbox slice per rep at 2 outbound/day each (4 sends/day total: 2 outbound + 2 warmup) supports roughly 8 meetings/month at the midpoint |
| Reply-to-handoff time | Under 4 hours | One operator in Smartlead's master inbox during business hours beats replies scattered across rep inboxes |
| Operator-to-rep ratio | 1:6-10 | One RevOps owner can run prospecting for a 6-10 rep team with sub-accounts, rotation, and webhook automation doing the leverage work |
What It Costs: Smartlead + ColdRelay
Infrastructure is billed per mailbox per month, with volume tiers that drop as you scale (see the table below) — relevant here because the centralized model provisions the whole team's pool in one order. Dedicated IPs, isolated Azure tenants, and pre-configured DNS are included.
Smartlead is billed separately on its own subscription, covering campaigns, mailbox rotation, sub-accounts, the master inbox, and API/webhook access.
The centralized model concentrates spend the way it concentrates work: one Smartlead subscription for the operator, one per-mailbox infrastructure bill sized to team quota. Adding a rep doesn't add a software seat — it adds a mailbox slice on ColdRelay, and the cost of a rep's pipeline becomes a line item you can actually compute.
| 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
Is ColdRelay a competitor to Smartlead?
No — they're complementary layers run together. Smartlead is the sending and sequencing layer: campaigns, mailbox rotation, sub-accounts, the master inbox, and webhooks. ColdRelay is the infrastructure layer underneath: the secondary domains, mailboxes, and dedicated IPs that Smartlead's campaigns actually send from. In the centralized model, one operator owns both layers.
Why centralize cold email under one operator instead of letting reps prospect?
Specialization and control. One operator running Smartlead full-time gets better at copy, lists, and deliverability than ten reps doing it as a side task — and every test they run benefits the whole team at once. Reps get their selling hours back, and because all cold volume runs on operator-owned ColdRelay domains, no rep can damage shared infrastructure with an off-script campaign.
How do reps get credit for meetings they didn't source themselves?
Through the webhook pipeline. Smartlead's API and webhooks push reply and meeting-booked events into Salesforce with the campaign source and rep assignment attached, so every sourced meeting lands on the right rep's record before they ever join the call. Attribution is cleaner than in rep-run prospecting, because one system of record writes it instead of ten people logging activity by hand.
Do the mailboxes need a warmup period before the operator can launch?
No. 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 to schedule around. The operator can provision the pool in about an hour, bulk-import it into Smartlead, and have campaigns sending the same day.