By Inkrush · Reviewed 6 November 2026. The examples are made-up planning arithmetic, not industry benchmarks.
There is no dependable universal client number. A manager can handle only the client work that fits inside their available monthly delivery time, after internal meetings, administration, leave and unexpected work are allowed for.
Work out the real hours each client needs across strategy, production, approvals, publishing, community management, reporting and communication. Then compare the total with protected delivery capacity, not the person’s theoretical working hours. This applies to freelancers as much as to agency teams.
Why client count alone is misleading
Two clients can each be one line on a roster and still create very different workloads. One may supply approved photography, need two posts a week and have one decisive reviewer. Another may expect original video, daily publishing across several platforms, community replies, weekly reporting and several rounds of approval.
Count the promised work, coordination and risk rather than assuming every client weighs the same.
Step 1: calculate monthly working hours
Use the person’s contracted hours rather than assuming a standard full-time week:
Monthly working hours = weekly contracted hours × 52 ÷ 12
This is a planning average. Real months include public holidays, leave, training and uneven workloads.
Step 2: remove non-delivery time
Subtract recurring time you cannot promise to clients:
- internal meetings and management;
- administration and timesheets;
- sales and proposal support;
- training and process improvement;
- expected leave and public holidays;
- your own marketing; and
- other time the role needs.
What remains is usable delivery time before contingency.
Step 3: protect a contingency buffer
Do not sell every remaining hour. Social work is exposed to late approvals, urgent changes, platform issues, staff absence and campaigns that land on the same day.
Choose and document a planning factor that suits how you deliver. There is no single correct percentage.
Protected delivery capacity = usable delivery hours × chosen planning factor
Step 4: calculate each client’s true monthly workload
For each client, estimate or measure:
- strategy and research;
- copywriting;
- design, photography and video;
- internal quality checks;
- client approval and revisions;
- scheduling and publishing;
- community management and escalation;
- reporting and analysis;
- meetings and routine communication;
- connection problems and failed posts; and
- onboarding, offboarding or campaign work.
Keep recurring work separate from variable work. A retainer may cover predictable posts while launches, events and urgent responses add extra demand.
Step 5: calculate a theoretical maximum, then round down
Theoretical client capacity = protected delivery capacity ÷ average client monthly workload
Always round down. Then test the roster against real deadlines and dependencies. A remainder does not mean another whole client will fit.
Worked example: a lighter, standard package
A manager has 150 average monthly working hours. After internal commitments, 105 hours remain. The team protects extra contingency, leaving 84 planned delivery hours. A standard client package is measured at 12 hours a month.
84 ÷ 12 = 7 theoretical clients
Before accepting seven, check whether approval deadlines, reporting days and specialist production overlap. If several clients launch together, the safe number may be lower.
Worked example: high-touch client work
The same manager still has 84 protected hours. A high-touch client needing original production, several platforms, community management and weekly reporting is measured at 28 hours a month.
84 ÷ 28 = 3 theoretical clients
Three clients fill the same capacity that supported seven lighter packages. Neither answer proves a universal limit.
Check deadline concentration
Monthly totals can hide a weekly problem. Five clients may each fit on paper while all needing approval, video editing and reporting in the last three days of the month. Map recurring deadlines and find work that depends on one person, such as a video editor or final approver.
Watch approval and communication load
Slow or unclear approvals force work to be paused, reopened and rechecked. Record the named approver, review window, expected revision rounds and late-approval rule in the scope. Frequent calls and urgent messages are also part of delivery, even when they do not produce a post.
Warning signs the roster is too large
- work routinely finishes in overtime;
- scheduled content waits on missing checks;
- client messages often miss the agreed response time;
- reporting is late or reduced to activity lists;
- chasing approvals replaces planned production time;
- failed posts have no one following them up;
- quality checks are skipped to keep up with volume; or
- ordinary leave disrupts service.
One busy week is not a capacity failure. Repeated overtime or skipped checks is.
Questions people ask
How many clients can one social media manager handle?
As many as fit within measured, protected delivery capacity while the agreed service standard stays achievable. That may be a few high-touch clients or more lighter, standard ones.
How much capacity should I keep free?
Enough to absorb the normal ups and downs of your service without relying on overtime. Review the buffer against actual overruns rather than copying a generic figure.
When should I hire or change scope?
When the forecast roster exceeds protected capacity and a specific process change cannot close the gap. Identify which role is the constraint, such as production, account management, community management, approvals or reporting, rather than hiring from client count alone.
What software can and cannot change
Separate client workspaces, approvals and scheduling can cut duplicated admin and make problems easier to spot. Software cannot guarantee a number of clients, remove production effort, make clients approve on time or override platform rules.
See how Inkrush keeps each client in its own workspace, or compare plans. To plan the work itself, read the multi-client content calendar guide.