How do you manage LinkedIn outreach for multiple clients?
One seat per client, caps enforced per seat rather than per agency, and one shared suppression layer so two clients never work the same company in the same week. The failure mode is not tooling. It is planning capacity at the agency level and discovering the ceiling is per account.
The unit of capacity is the seat, not the agency
Every limit that matters is scoped to one LinkedIn account. LinkedIn publishes no numeric invitation limit, but whatever thresholds it enforces apply to each person you are sending as. Ten clients does not give you ten times one person's capacity in any form you can pool, because there is nothing to pool. Each seat spends its own allowance or it spends nothing, and an idle seat's allowance cannot be lent to a busy one.
Our enforcement sits deliberately below the platform's line. A new seat is capped at 20 invitations a day and 80 a week, server-side, and the warm-up ramp multiplies that by 0.5x in week zero, 0.75x in week one and 1.0x from week two. A client you signed on Monday is running at 10 invitations a day, not 20, and there is no settings field where an impatient operator can type a larger number.
Do that arithmetic before you sell the retainer, because it is the arithmetic that decides whether the retainer is deliverable. A fully ramped roster of ten seats has a ceiling of 800 invitations a week. A roster you onboarded all at once spends its first fortnight well below that, and a proposal that promised a monthly contact volume assuming full speed from day one is short by most of a week's capacity per client before anyone writes a message.
Onboarding a seat is a two-week event, not a day
Three things have to happen before a client seat produces anything: the LinkedIn account is connected, that client's contacted history is imported so suppression is live, and the first sequence is built. Only the first is technical. The second is the one clients delay, because it means someone digging an export out of a CRM or a spreadsheet, and it is the one that prevents the worst first-month mistake.
Then the ramp runs its course. Week zero at half speed, week one at three quarters, full speed from week two. Selling a 30-day pilot that begins on connection day means the client evaluates you on a period where the product is deliberately holding you back, so either the pilot runs long enough to clear the ramp or the expectation is set at signature.
After that, connection state becomes a standing operational item. Sessions drop, people change passwords, and a disconnected seat sends nothing while looking fine from a distance. Checking account status across the roster is a weekly routine, not an incident response, and reconnecting is a tool call rather than a support ticket.
The mistake: one plan, ten identities
The agency failure mode is writing one campaign plan and running it from ten different people's accounts. It is efficient right up to the point where the same message, the same trigger and the same call to action are landing in one market from ten senders, and recipients start reporting invitations they did not ask for.
The account that pays for that is the client's, not yours. An invitation restriction lands on a real person's profile, and the conversation you then have with that client is about their professional identity rather than about your service. There is no version of that conversation where the agency comes out ahead, which is why the discipline has to be upstream of the send.
What prevents it is per-client copy that names the sender's actual reason to be in the conversation, and per-client targeting that does not overlap. Both are judgment tasks, neither is batchable, and between them they are most of what an agency is genuinely selling. If the plan is one template with the company name swapped, you have built a single campaign with ten return addresses.
Shared memory is what makes multi-seat safe
The second collision is quieter. Two of your clients sell to the same buyer, and both seats work the same account list in the same month. Nobody at your agency notices, because the two campaigns live in different plans and different documents. The recipient notices, because they see both.
The fix is one workspace with one suppression layer rather than ten disconnected tools. Before a lead group is enrolled, company interaction history and a search of active sequences tell you whether that company already has an open thread on another seat. A hit means wait, or route the target to the seat that already holds the relationship, which is usually the better outcome anyway.
Importing each client's contacted history on day one is the other half of it. A CSV import turns past outreach into suppression from the moment of import, which matters most in month one, when you know the least about who that client has already approached and have the least standing to ask them to check.
Approval queues do not scale for free
Every send passes a human approval gate. Creating a sequence sends nothing. Enrolling a lead group queues drafts, and a reply stops the remaining follow-ups for that person immediately, so the queue shrinks as conversations start rather than piling up behind them.
At one client that is a pleasant safety property. At ten it is a job, and it is the line item agency pricing most often forgets. Either an operator reviews queued drafts daily, or the queue becomes the bottleneck and the retainer quietly stops delivering while the invoice does not, which is the version clients find out about at the quarterly review.
It is a real cost and we would rather you price it than discover it. It is also why ten seats are not ten times the work of one: draft review batches well across clients, and targeting judgment does not batch at all. Staff against the second number, not the first.
What this build does not do for agencies
There is no white-label reporting, no client-facing portal and no branded export. What exists is per-seat observability inside the workspace: account status, outreach volume over a window, an agent activity log, and an outreach analysis you can ask for at any time. You write the client update. The product does not brand one for you, and we are not going to call a chat summary white label.
There is also no CRM, Zapier, HubSpot, Salesforce or webhook integration in this build, and no bundled contact database. Sourcing is each client's own LinkedIn seat plus the CSVs you import. If your service promises a CRM-synced pipeline, that join is a person today.
The tier ceiling is real too: Agency covers up to 10 accounts at $119 a month and there is no unlimited plan. Write proposals against these limits rather than around them. An agency that promises a synced, branded, uncapped programme on this stack is writing a proposal it cannot deliver, and the client finds out in month two.
Per-seat invitation ceiling by ramp week, under our enforced caps
| Ramp week | Multiplier | Invitations per day | Invitations per week |
|---|---|---|---|
| Week 0 | 0.5x | 10 | 40 |
| Week 1 | 0.75x | 15 | 60 |
| Week 2 onward | 1.0x | 20 | 80 |
| Ten ramped seats | 1.0x | 200 | 800 |
Questions people ask next
How many LinkedIn accounts can one workspace manage?
Up to 10 on the Agency tier at $119 a month. Operator covers up to 3 at $59 and Solo covers 1 at $29. There is no unlimited-seat tier.
Can I run all my clients from one LinkedIn account?
No, and you should not want to. Invitations arrive from a named person, so one profile would absorb every complaint, and the weekly limit would be spent long before the roster is served.
How do you stop two clients contacting the same company?
One company, one seat, one week. It is enforced by checking company interaction history and active sequences before enrolment, plus suppression from the history you imported. It is a practice the agent runs, not a toggle.
Do you have white-label reporting for clients?
No. Per-seat observability and an activity log exist inside the workspace. There is no branded dashboard, client login or scheduled report, and no date we will promise.
Why this page exists: r/AgencyAutomation: "Managing LinkedIn outreach for multiple clients - the one mistake that kills agencies"
LinkedBoost is the LinkedIn MCP server: your agent sources, drafts, sends and works the inbox, inside caps the server enforces rather than suggests.
Related answers
One company, one seat, one week. It is a practice rather than a setting: before enrolment the agent checks company interaction history and searches active sequences for that company, and every CSV you import turns past outreach into suppression. Nothing in the product silently blocks a second seat for you.
The software is the cheapest line. Agency is $119 a month for up to 10 accounts, which is $11.90 per client seat at a full roster, $59 covers 3 and $29 covers 1. What costs real money is operator time on the approval queue, and capacity that is fixed per seat.