Marketing agencies: how to white-label Leafer for client outreach
Agencies running outbound for ten clients on ten Apollo seats are setting money on fire. A walkthrough of the multi-workspace, white-labelled, per-client suppression setup that lets one ops person source and draft for the entire roster — and where the boundary sits.
By Bora Esen
Most marketing agencies running outbound for ten clients are also running ten Apollo seats, ten Smartlead sub-accounts, and one shared Slack channel where the team copies and pastes templates between workspaces. That setup costs roughly $4,000 a month before the first hire and breaks the moment one client wants something the others do not. The white-label playbook below is how we see the best agencies set this up instead.
The agency-side problem
Outbound tooling is built for end-user companies, not for agencies. The default workspace model assumes one company owns one domain, one sending pool, one suppression list. An agency owns N clients, N domains, N sending pools, N suppression lists — and the work happens in parallel, not serially. The mismatch shows up in two places.
First, the seat math. Apollo charges per user per workspace. Ten clients means ten workspaces means at least ten seats. Multiply by the number of agency operators who touch each client and the seat count balloons.
Second, the brand math. Each client expects messages to come from their domain, signed by their team, with their brand voice. Centralising on one platform that has “Apollo” in the sender footer is a fast path to a client renewal conversation.
How the white-label setup actually works
The Leafer agency tier solves the seat and brand problems with three primitives: per-client workspaces, a shared operator pool, and per-client branding.
Per-client workspaces. Each client gets their own workspace with their own custom domain, ICP, suppression list, audit log, and DPA. Compliance is isolated; clients do not see each other’s prospects.
Shared operator pool. One agency-level pool of operators (account managers, SDRs, copywriters) can be assigned to any subset of the client workspaces. The seat cost stays flat at the agency level even as client count grows.
Per-client branding. Every dashboard, every export, every PDF report can carry the client’s logo, colour palette and custom domain. The agency is invisible in the client-facing surface; the client’s brand is the one on the screen.
Where the boundary sits
Be exact about what the shared workspace does and does not cover, because agencies price against it. Leafer covers the research half: signal mining and discovery per client ICP, website crawling and decision-maker extraction, email finding and verification, lead scoring, the evidence-grounded draft, the approval queue, and the compliance record. It does not dispatch. Whatever the agency sends with today — the client’s own mailboxes, a dedicated sending tool per client — it keeps, and that stays a separate line on the invoice.
That boundary is worth understanding before you model the savings. The work Leafer removes is the sourcing-and-drafting labour that scales linearly with client count. The work it does not remove is the per-client outbound plumbing, which scales the same way it always did.
The operational pattern
The way the best agencies use the setup looks roughly like this.
Monday: the AM reviews what came back from last week per client, identifies the campaigns that are underperforming, and queues an ICP or brand-voice tweak. Tuesday–Thursday: the SDR works one approval queue across every client workspace, reading drafts and pushing the approved ones out through each client’s own sending setup. Friday: the agency lead reviews the audit logs and prepares the weekly client report (PDF auto-generated from the workspace).
Everything client-facing — dashboards, exports, weekly reports — carries the client’s brand. Everything operator-facing — the queue, the ICP library, the suppression import — is shared at the agency level. The line between “client’s view” and “agency’s view” is the white-label boundary and it stays clean.
What this means for new clients
The honest part of this pitch: agencies that adopt the white-label workflow tend to bring on more clients per quarter than the ones still running on per-client Apollo. The constraint that used to slow new-client onboarding — “we need to spin up a new toolstack first” — disappears. New client lands on Tuesday, has a working outbound campaign by Friday.
The white-label tier is the way the next generation of outbound agencies is going to run. If you are still on the per-client spreadsheet pattern, the moment to switch is before the eleventh client lands.
