Blog · · 4 min read
Managing multiple freelancers without becoming a PM
Three freelancers can cost you a day a week of coordination. How to run five or more on one rhythm, one shared view, and deliberate routing.
The trap with multiple freelancers isn't any one of them — it's the coordination between them landing entirely on you. Three freelancers on three ad-hoc arrangements quietly costs a day a week of message-chasing and mental bookkeeping; five makes you a part-time project manager for your own vendors. The way out is not working harder at coordination but deleting most of it: one update rhythm, one place work lands, and routing decisions made once instead of hourly.
TL;DR
Coordination cost grows with every pairwise arrangement, not headcount — so standardize: one weekly update format for everyone (stated at kickoff), one shared view where all tasks and updates land, async status by default with calls reserved for decisions. Route work deliberately instead of to whoever's responsive. Done right, freelancer #6 costs you minutes a week, not hours.
Why does the third freelancer break the system?
Because each ad-hoc engagement carries its own overhead: its own channel (email, Slack, WhatsApp), its own update style (or none), its own version of "how's it going?" One freelancer like this is fine. Three means you're the sole human integration layer across three unstandardized pipes — every status question, every priority conflict, every "who's blocked on whom" resolves through your attention.
The failure is invisible on any given day and obvious in aggregate: you hired freelancers to reduce your workload and somehow acquired a management job. Founders usually respond by adding meetings, which scales even worse.
What should you standardize first?
The update rhythm. One format, one day, everyone — freelancers and internal folks alike. What got done, what's next, what's blocked; outcomes, not activity logs. Introduce it at kickoff as house process ("we do a short Friday update — everyone here does") and it reads as professionalism; introduce it mid-drift and it reads as suspicion. The contractor kickoff checklist covers setting this expectation on day one.
Standardization is what makes reading scale: five updates in the same shape take ten minutes and comparisons come free — you notice that two people are blocked on the same dependency, or that the same integration keeps slipping, because the reports line up.
Where should all of it land?
One shared view — emphatically not your inbox. The test: can you answer "what is everyone working on right now?" in thirty seconds without asking anyone? If the answer lives across five chat threads, the system is your memory, and your memory is why you're tired.
The mechanics matter less than the properties: every freelancer's tasks and updates in one place, visible at a glance, with each freelancer seeing only their own work (they don't need — and shouldn't have — visibility into each other's engagements or rates). This is exactly the shape WorkedOn's business side is built around: each person gets their own scoped workspace, their activity and updates flow into your single dashboard, and Monday delivers one digest covering everyone.
How do you route work without becoming the bottleneck?
The default routing algorithm — "whoever answers fastest gets the task" — over-assigns your most responsive freelancer and under-uses the rest, and it runs through you every single time. Two upgrades:
- Route on skills and load, not responsiveness. Keep a lightweight picture of who does what and who has capacity. (WorkedOn's AI suggests the best match with a reason when you create a task — you still click, nothing auto-assigns.)
- Make blockers visible, not conversational. A freelancer blocked on your API keys should surface it in a structured update you see today — not in a DM that competes with forty others. Blocked freelancers on the clock are the most expensive silence there is.
Contract structure changes what you need to watch, too — hourly work needs progress visibility, fixed-price needs milestone visibility. Fixed-price vs hourly unpacks how each shifts your attention.
What does good look like at five-plus freelancers?
A Monday morning where you read one digest in five minutes: each person's done / in-progress / blocked, side by side. Two blockers surfaced before they cost the week. Zero "quick status calls" scheduled. Task routing that took four clicks total. Your actual job — deciding what matters — intact.
That's the honest pitch: not managing freelancers better, but deleting the management layer between you and their work.
FAQ
How many freelancers can one person manage without help?
With ad-hoc communication, about three before coordination eats a day a week. With standardized updates landing in one place, five to ten is comfortable — the limit is your system, not your calendar.
Should I make all my freelancers use the same update format?
Yes — one rhythm, one shape, stated at kickoff as how you work with everyone. Reading five identical-format updates takes ten minutes; reading five bespoke ones across five channels is a research project.
How do I keep track of which freelancer is doing what?
One shared view where each person's tasks and updates live — not your memory, not five chat threads. If "what's Maria working on?" requires scrolling Slack, the system is your inbox, and inboxes don't scale.
Do check-in calls scale across multiple freelancers?
No — five weekly 30-minute calls is 2.5 hours to learn what written updates deliver in ten minutes. Save synchronous time for decisions and direction; let status travel asynchronously.