Outreach
LinkedIn Outreach Email Outreach WhatsApp Automation Dialer Unified Inbox CRM / Pipeline
Data
Signals Lead Finder Email Finder Phone Finder Company Follower
Deliverability
Deliverability Center Mailboundry Email Infrastructure (Google, Microsoft & Azure) Email Warmup Inbox Placement Test
AI & Automation
AI Personalization AI Reply Agent ICP Score
Built For
Founders Agencies Sales Teams B2B SaaS
Use Cases
LinkedIn Outreach Cold Email Outreach Multichannel Outreach Signal-Based Outreach Outbound Sales Lead Generation Account-Based Outreach Appointment Setting Recruiting Outreach Link Building & PR Outreach
Resources
Free Tools Help Center Mobile App API & Webhooks Roadmap Blog Cold Email Guides Deliverability Guides LinkedIn Guides Lead Generation Guides Affiliate Pricing Log in Book a demo Start free trial
BlogSalesConvert · Sales

Outbound for Agencies: Running 20 Clients Without Chaos

Running outbound for one client is a skill. Running it for twenty is a different business, and the thing that breaks is never the campaigns.

RAUpdated
← All articles

Agencies that run outbound well at five clients frequently fall apart at fifteen, and it is almost never the campaigns that break.

What breaks is the operating model. Shared infrastructure that was fine with four clients becomes a liability with eighteen. A reporting process that took an hour a week takes a day. Onboarding that lived in someone’s head stops being repeatable the moment that person is on holiday.

This is the operational side of agency outbound, the part that decides whether twenty clients is a business or a crisis.

The one rule everything follows from

One workspace per client, no shared infrastructure.

Not folders, not tags, not naming conventions inside a shared account. Separate workspaces with separate domains, separate IPs, separate suppression lists and separate billing.

The reason is blast radius. One client’s aggressive list damages the sending reputation of everyone sharing that infrastructure, and you cannot explain the cause to the affected client without disclosing another client’s behaviour. That conversation ends relationships and there is no good version of it.

It also makes offboarding a transfer rather than an extraction, which matters more than it sounds. Agency workspace structure covers the layout in detail.

Pricing your service

Three models, and the one you pick shapes which clients you attract.

Retainer. $3,000–$8,000 a month typically. You are selling capacity. Predictable for both sides, and the failure mode is comfort, once a client is broadly satisfied, the pressure to improve drops.

Per meeting. $150–$600 per held meeting. Aligns incentives, and the failure mode is targeting drift: to produce more meetings you widen the list, and the meetings get worse. Only works with written qualification criteria.

Hybrid. A base covering your costs plus a per-outcome fee. The most common structure at the professional end, and the one I would default to.

Whatever you choose, settle booked versus held before you discuss price. At a 20–40% no-show rate, paying on booked meetings costs a client roughly 40% more per meeting that actually happens, and that gap is where most agency disputes start. Covered fully in agency pricing models.

The margin question

Most agencies mark up tooling invisibly and wonder why margins are thin. The honest arithmetic:

For a 50-mailbox client, infrastructure costs you roughly $60–$85 a month. Clients pay $200–$400 for equivalent managed infrastructure elsewhere. Even bundled into a retainer, that is real margin you are either capturing or giving away.

Whitelabel turns software cost into software revenue at 60–75% gross. Across twenty clients that is meaningful recurring income on work you already do. The cost is support: once your name is on the login, every deliverability question is yours. Budget the hours. White-labelling the stack has the full model.

Onboarding, standardised

The difference between an agency that scales and one that does not is whether onboarding is a checklist or a conversation.

  1. Create the workspace, named to convention
  2. Register domains in the client’s name, with delegated access to you
  3. Configure DNS, verify records, start warmup
  4. Three mailboxes per domain
  5. Load the client’s suppression list and their current customer list
  6. Apply your global do-not-contact list
  7. Assign the client manager, restrict everyone else
  8. Set daily limits and sending windows
  9. Run an inbox placement test before the first campaign
  10. Document who owns what, in writing, where the client can see it

That last step prevents most of the arguments that happen eighteen months later.

Point two is the one agencies skip for convenience and regret at offboarding. Registering domains in your own account takes ten minutes less and costs you a reference.

What you are actually selling

Worth being clear about internally, because it changes how you price and how you defend the retainer.

You are not selling software. A working stack is $400–$800 a month and the client could buy it. You are selling:

  • Experience. You have run 200 campaigns; they have run none. Your first six weeks produce what their first five months would.
  • Capacity. Somebody does the work who is not them.
  • Judgement. Which segments to try, when to stop, what the reply rate is telling you.

Agencies that forget this compete on tooling and lose to the client discovering they can buy it themselves. Agencies that remember it survive the client asking exactly that question, because the answer is “yes, and it will take you five months to get where we are.”

Reporting that clients actually read

Most agency reporting is activity theatre: sends, opens, clicks. Clients do not care and eventually notice they do not care.

Report four things:

Meetings held, not booked. The number they are buying. Pipeline value, if they will share it. Cost per meeting, which makes your value legible against an SDR salary. What you changed and why, which is the evidence of judgement.

Monthly, one page. A weekly activity dump trains clients to ignore you.

The fourth item is the one that renews contracts. A client who can see you making decisions is buying expertise; a client who sees only numbers is buying a service they could shop around.

The two failure modes

Shared infrastructure. Covered above. It is the one that ends agencies, because the damage is cross-client and inexplicable.

Key person dependency. Everything about client setup, campaign logic and deliverability lives in one person’s head. They leave, go on holiday, or get sick, and nothing is repeatable. The fix is boring: write the checklists down, including the deliverability diagnostic order.

A third, quieter one: the client who asks for volume. Every agency has one client pushing for more sends against your advice. Giving in damages their domains, then their results, then the relationship. The answer is to show them the bounce and complaint thresholds and let the numbers do the refusing.

When to turn a client down

Three cases where the engagement will fail and take a reference with it.

Unrealistic ACV. A client with $2,000 annual contracts cannot support a $5,000 retainer at any conversion rate you can deliver.

No ICP. If they cannot tell you who buys, you will build a list from guesses and both of you will blame the other.

They want their domains on your account. Occasionally a client prefers this. Decline, you do not want to own the asset, and the exit conversation will be worse than the onboarding one.

A workspace per client, whitelabel included

Agency at $399 includes 20 LinkedIn seats, whitelabel, workspaces and 500 deliverability tests, with separate domains, IPs, suppression and billing per client, and per-workspace usage for rebilling.

See Outboundry for agencies

Managing many LinkedIn accounts safely

Engage · LinkedIn Outreach

Turn this into booked meetings

Reach the right buyers on LinkedIn and email in one sequence, with every reply landing in one inbox, ready to become a meeting.

See how it works

Safety is the thing that can sink an agency fastest: a flagged client account is a flagged client relationship. Each account needs human-like sending limits, proper warm-up (especially for newer accounts), and activity spread across the day. Doing this manually across many clients is impractical; you need a system that enforces safe limits per account automatically.

The short version

What breaks at fifteen clients is operations, not campaigns. One workspace per client with genuinely separate infrastructure is the rule everything else depends on.

Standardise onboarding and offboarding as checklists. Register domains in the client’s name. Report meetings held and decisions made rather than sends and opens.

Price on experience and judgement rather than tooling, because the tooling is cheap and the client will eventually price it themselves.

And turn down the clients whose deal size, ICP clarity or asset demands mean the engagement cannot work. A failed client costs more than an empty slot.

Next: structuring workspaces for a multi-client agency, or white-labelling your stack.

Frequently asked questions

How do agencies manage outbound for multiple clients?

One workspace per client with separate domains, IPs, suppression lists and billing. Shared infrastructure means one client’s list quality affects everyone else’s placement, and the cause cannot be explained without breaching confidentiality.

What should a lead gen agency charge?

Retainers typically run $3,000–$8,000 a month, per-meeting pricing $150–$600 per held meeting. A hybrid base-plus-outcome structure is the most common at the professional end.

What should agency reporting include?

Meetings held rather than booked, pipeline value, cost per meeting, and what you changed and why. Activity metrics like sends and opens train clients to ignore the report.

When should an agency decline a client?

When deal size cannot support the retainer at any realistic conversion rate, when they cannot define who buys from them, or when they want sending domains registered to the agency’s account.

Is it safe to run LinkedIn outreach across many accounts?

Yes, if each account stays within human-like limits and is warmed up properly. Tools that enforce per-account safety automatically make this manageable at scale.

Ready to run outbound on autopilot?

Start free trial