Most successful freelancers reach the same fork in the road. The practice is busy, the pipeline is full, and the obvious next step is to take on more work than one person can deliver. That means hiring: a contractor, then a producer, then a small team. The question is whether the result is a healthy small agency that pays the founder more, or a treadmill where the founder works longer hours for the same take-home because each hire ate the margin it was meant to add. This guide covers the first scale-up: when to hire, who to hire, contractor versus employee, the SOPs that make delegation possible, how project management changes, what to do when you're no longer the only client contact, how to price agency work, and which partnership structures hold up.
TL;DR
- Make the first hire when you have turned down three projects in a quarter you would have taken, six months of operating cash on hand, and SOPs written for the work you would delegate.
- The first hire is a project manager, not another maker. The bottleneck in a scaling freelance practice is coordination, not craft.
- Price agency work at a 2 to 3x multiplier on contractor cost. Underpricing here is the fastest way to break a scaling practice.
Signs you are ready to scale, and signs you are not
The urge to scale usually arrives before you're ready. The pipeline is full, the work is exciting, three good prospects are waiting for capacity, so surely it's time to hire? Freelancers who scale well treat that moment with suspicion. A full pipeline is necessary, but it isn't enough.
You're ready when all three of these are true:
- You've turned down at least three projects in the last quarter that you would have taken if you'd had capacity. Not "maybe" projects, but ones you regret losing.
- You have at least six months of operating cash on hand, enough to cover the new hire and your own draw through a slow quarter without panic.
- You've written down the SOPs (not just thought about them) for the work you'd hand off.
If any one is missing, the hire is premature and the practice will absorb the cost before the revenue catches up.
You're not ready, even if it feels like you should be, when you see these signs:
- Revenue is unpredictable. The pipeline is full but month-to-month revenue swings, and you can't forecast a steady baseline to pay the hire from.
- You're exhausted but profitable. Hiring out of exhaustion usually means hiring poorly and managing badly.
- Your tools are held together with browser tabs. Adding a second person to a system you can't describe in writing multiplies the chaos.
Look at real numbers before deciding. COLO's reports on payments, invoices, customers and projects export as CSV, Excel or PDF, so you can see a year of revenue by month and by client instead of going on gut feeling. If you're in between (busy enough to feel the pressure, not stable enough to commit to payroll), the better move is usually to raise rates, sharpen the offer and be more selective for two more quarters. A 15 percent rate rise on the same workload often brings in more take-home than a first hire does in year one. The freelance pricing guide covers how to raise rates.
Should your first hire be a contractor or an employee?
A first hire should almost always be a contractor. Contractors carry no payroll tax, statutory benefits, notice periods or redundancy liability, and they scale up and down with the workload. Convert to employment later, once revenue is stable and the hours make the classification a legal risk.
Your first hire should almost always be a contractor, not an employee. It takes many founders months to accept this. "Building a team" of employees is appealing; starting with contractors is what keeps the practice solvent.
Contractors carry far less employment risk for the founder: no payroll tax beyond paying the contractor's invoice, no statutory benefits, no notice periods, no redundancy liability and no employment tribunal exposure. The contractor invoices for hours or projects, you pay the invoice, and either side can end the arrangement. For a first hire, when you're learning to delegate and finding out whether the numbers work, that flexibility lets the experiment fail without sinking anyone.
Contractors also scale with the workload. A contractor working 20 hours a week this month, 40 next month and 10 the month after is normal. An employee on that variable load is a risk, because you pay the salary in the slow months. Until you're confident in the revenue baseline (typically 18 to 24 months of stable monthly recurring revenue), contractor flexibility is what carries the practice through seasonal dips.
Converting a contractor to an employee comes later, usually when they're working enough hours that their classification is at risk, or when retention and culture matter more than flexibility. The tests differ by country:
| Jurisdiction | Classification test |
|---|---|
| United States | IRS economic reality test; the ABC test in California and similar frameworks in other states |
| United Kingdom | IR35 and the off-payroll working rules |
| European Union | Country-specific tests for false self-employment |
The rule of thumb: if a contractor is full-time, exclusive and managed like an employee, they probably need to be an employee, for both legal and ethical reasons.
For marketing agencies, design studios and web designers, contractor-first is the industry norm. Almost every small agency founded in the last decade started with a network of contractors before its first salaried hire.
The first hire: a project manager, not another maker
When freelancers imagine scaling, most imagine cloning themselves: "another senior designer", "another senior developer", "another senior strategist". That's usually wrong. The bottleneck in a growing freelance practice is rarely the craft, since the founder can usually still do the work. It's coordination: client communication, scheduling and admin. Hiring another maker moves the bottleneck sideways without removing it.
The right first hire is a project manager or producer: someone who schedules calls, chases assets from the client, drafts the kickoff summary, updates the project tracker, sends the milestone invoice and follows up on late payments. That frees the founder for two things only the founder can do well: sales, and senior delivery where the founder's craft is the product. Adding a PM at the right moment can substantially grow revenue without adding any senior craft capacity.
The PM also makes the second hire possible. Once someone else runs the day-to-day operations, the practice can take on a junior or mid-level maker (contractor or employee) without the founder managing them directly. The PM manages the makers; the founder manages the PM. At that point you're a small team rather than a solo operator with helpers.
In COLO, projects and tasks give a PM what they need from day one: tasks with owners, statuses, priorities and comments, project members, files, and time tracking against each task. Roles and per-module permissions control what each team member can see and change. The client portal and project chat give the PM a direct line to the client, so the founder doesn't need to be copied on every email. If your projects currently live in Asana or ClickUp while proposals and invoices live elsewhere, putting them in one workspace means a new PM learns one tool instead of several.
SOPs: the documents that make delegation possible
Most first hires fail not because the person was wrong but because the founder couldn't describe the work clearly enough in writing for someone else to do it. SOPs (Standard Operating Procedures) are written, step-by-step documents for every recurring process in the practice. Without them, every new hire is trained from scratch, every deliverable depends on the founder remembering how it's done, and the founder stays the bottleneck even after hiring.
A minimum set covers six processes:
- Proposals: how a discovery call becomes a sent proposal.
- Onboarding: what happens between the deposit and the first deliverable.
- Project delivery: how a typical engagement runs from start to finish.
- Invoicing: what triggers an invoice, who sends it and when.
- Late payments: what happens when a client pays late.
- Client communication: channels, frequency and escalation.
Each SOP is one to three pages, written so a new hire can follow it on day one without asking the founder.
SOPs turn the founder's instincts into the way the practice runs. If you've written down how you run a kickoff call, you can hand it to the PM and it will run the same way (same agenda, same documents, same summary) without you there. If you haven't, you have to be in every kickoff call yourself, which is where most attempted scale-ups stall.
Keep SOPs wherever your team already works: a shared document folder, or files attached to an internal project in COLO so they sit next to the work they describe. The free client onboarding checklist template and freelance proposal template make good starting points. Adapt them to your practice and they become a new hire's training material. In COLO, saved proposal templates and contract templates also work as living SOPs: the PM starts from the approved version instead of the last thing the founder sent.
If you worry that SOPs will make the work feel mechanical, the opposite is usually true. SOPs handle the repetitive scaffolding so there's more room for the craft. The kickoff call still has your personality; the agenda just makes sure nothing is missed.
Project management at scale: when keeping it in your head stops working
A solo freelancer can keep three concurrent projects in their head: deadlines, who owes what, what's urgent today. By project six, that starts failing. By project nine with a team of three, it has failed completely, and the practice is missing deadlines and surprising clients.
Moving from your head to a tool is the change that separates a growing practice from a stuck one. The tool doesn't need to be elaborate. Tasks with owners, due dates and statuses, plus a clear view of who is working on what, is enough. In COLO, the founder sees every project and its tasks, the PM runs the day-to-day, and you control per project which tasks the client can see in the portal.
The key rule at this size is single ownership:
- Every project has one named owner, usually the PM.
- Every task has one named owner: the person who does it.
- Every deliverable has one named approver, usually the founder or a senior maker.
Shared ownership ("the team will handle it") is how things fall through the cracks. Named ownership is how they get done.
The other change is visibility of workload. A solo freelancer can sense their own load; a team needs to see it: who is overloaded this week, who has capacity, where the bottleneck is. COLO's timesheets and reports show hours logged by person, task and project, and each task shows its owner and status. That answers the question without calling a status meeting, and it prevents the "I thought you were handling that" failure.
If you run projects in Asana or ClickUp, consider whether a workspace that also holds contracts, invoices and the client portal would save your PM time on cross-tool updates. It also gives the client one place to log in for files, tasks, invoices and messages, which keeps the client experience together as the team grows.
Client communication when you are no longer the only contact
The hardest conversation in scaling is with the existing client who hired you specifically and now finds themselves talking to a PM they didn't choose. Handled well, the handover frees you for senior work. Handled badly, the client leaves within a quarter.
The handover has three rules.
1. Announce it clearly and in writing, before it happens. A short note from you: "I'm bringing X onto your project. They'll be your day-to-day contact from next week. I'm still on every senior decision and the strategy work, and you can always escalate to me." The client knows what's happening, why, and where you fit.
2. Stay involved at the senior level. The PM runs the day-to-day; you own the senior relationship: quarterly strategy reviews, major creative or technical decisions, the renewal conversation. Clients who hired you need to see you in the work, not in every status email.
3. Separate the clients who can move from those who can't. Some clients hired you for your judgment, your specific craft or your personal accountability, and won't accept a delegated relationship at any price. They need a different conversation: a premium retainer with explicit senior hours, a scope that keeps you in the work, or a respectful handover to another freelancer if the new pricing doesn't suit them. Pushing every client into the new agency setup is how you lose your founding clients.
For marketing agencies and design studios this transition is well understood. In COLO, adding the PM as a member of the client's project means they appear in the project chat alongside you, so the client sees the team supporting them instead of feeling handed off to "the assistant".
Pricing agency work: the multiplier that keeps you solvent
The most common reason growing freelance practices fail financially is pricing agency work like solo work. You used to charge £120 an hour solo; a contractor costs you £60 an hour; so the margin is the £60 difference? Not in practice. That £60 has to cover the PM's time on the project, the senior review, client communication, admin overhead and a real margin to fund growth.
The standard agency multiplier on contractor cost is 2 to 3x. A contractor costing £60 an hour bills to the client at £120 to £180 an hour. Below 2x, the agency loses money at any real volume: overhead eats the margin and the founder ends up funding the team from their own draw. Above 3x, the agency only wins when its senior craft is genuinely premium; at that level most clients compare prices and the win rate drops.
Treat agency work as a different product from solo work, not the same product with a different cost structure. An agency engagement includes the PM, the senior review, the client portal, documentation and a QA pass, and that bundle carries a different rate. In COLO you can save separate proposal templates for agency and solo offers, each with its own line items and rates, so each client sees the scope and price for what they're buying. The freelance proposal template is a free starting point.
The safest way to make the switch is to put new clients on agency pricing, keep existing clients on their current rates, and move them to agency pricing at their next renewal. Moving every existing client to the new rate at once is how the founding client list disappears in a quarter.
Partnership structures: what works and what breaks practices
The other route to scale is partnership: two or more freelancers forming a small agency together. It sometimes works very well and often fails badly. The pattern is consistent: partnerships that last wrote the agreement before billing their first project; partnerships that fail started on chemistry and trust and only wrote things down when the relationship was already breaking.
A clean partnership agreement covers six things:
| Clause | What it settles |
|---|---|
| Equity split | Who owns what percentage |
| Decision rights | Which decisions need consensus, which one partner can make alone, which need a vote |
| Profit distribution | How cash reaches the partners (for example a monthly draw plus an annual bonus) |
| Roles and responsibilities | Who runs sales, delivery and operations |
| Exit terms | What happens if a partner leaves: buyout formula, notice period, non-compete |
| Dispute resolution | How disagreements are settled, including mandatory mediation before any legal action |
These clauses force the conversations partners tend to avoid until it's too late. "What if you want to leave?" is awkward to ask a future partner, but not having the answer is what breaks the partnership years later when one of you does want to leave. The agreement isn't about romance; it records how the practice runs, so neither of you can rewrite it to suit the moment.
When partners have complementary skills (one runs sales and client relationships, the other runs delivery and the team), clear roles are what make the model work at scale. When two senior makers partner and hire a small team underneath, the equity usually starts equal and decision rights become the more important conversation. Both models work; both need the same upfront paperwork.
A service contract template can be a starting point for a very simple two-person arrangement, but for anything more complex a lawyer-drafted partnership agreement is essential. One rule worth keeping: don't put more than three months of unpaid effort into a partnership before the agreement is signed. A partnership is most vulnerable to disagreement before any money has come in.
How COLO helps with this
Going from solo to a small agency is the point where an operating system for the practice stops being optional. A solo freelancer can run on willpower; a three-person team can't. COLO keeps projects, tasks, clients, billing and communication in one workspace, so you don't bolt on a new tool with each hire.
- Projects and tasks with owners, statuses, priorities, comments and files give a PM what they need on day one, and you can copy a project to reuse a proven structure.
- Roles and per-module permissions control what each team member sees.
- The client portal, branded with your logo and colors, keeps the client experience consistent as the team grows, and project chat includes the client alongside your team.
- Time tracking with a per-task rate, project budgets and expenses linked to projects show what each engagement costs. Project, timesheet and expense reports export as CSV, Excel or PDF, so you can check whether the scale-up is paying for itself.
For marketing agencies, design studios and web designers making the same transition, the setup is the same; only the craft on top differs.
COLO has a free-forever Solo plan; see pricing for the plans that add team members. Whatever you use, the goal is the same: make the move from solo to agency a planned step rather than a gamble.
FAQ
Q: When am I ready to make the first hire?
When you have turned down three projects in a quarter you would have wanted to take, you have at least six months of operating cash on hand, and you have written SOPs for the work you would hand off. Hiring earlier puts you on the treadmill of selling to feed the team; waiting longer means losing momentum.
Q: Should my first hire be a contractor or an employee?
A contractor — almost always. The first hire is a test of whether you can delegate and whether the practice can sustain the cost. Contractors carry no employment risk, can scale up and down, and let you learn how to manage before you commit to fixed monthly payroll.
Q: What is the right first hire — another maker or a project manager?
A project manager or producer, not another senior maker. The bottleneck in a scaling freelance practice is rarely the craft — it is the coordination, the client communication, the scheduling. A PM frees the founder's time for sales and senior delivery; another maker just shifts the bottleneck sideways.
Q: What are SOPs and why do I need them?
Standard Operating Procedures — written, step-by-step documents for every recurring process in the practice (proposals, onboarding, invoicing, project handoff). Without SOPs, every new hire is trained from scratch and every deliverable depends on the founder remembering how it is done.
Q: How do I manage projects at agency scale versus solo?
Solo, you can keep everything in your head. At three or more people, you cannot. Move to a project management tool with task ownership, due dates and visible workload — the difference between a practice that scales and one that breaks at five concurrent clients.
Q: How do I keep clients happy when I am no longer the only point of contact?
Name the new contact early, in writing, with a personal handover note from you. Stay involved in the senior-level relationship; let the PM run the day-to-day. The clients who care about working with "you specifically" need a different conversation — usually a higher rate or a clear retainer with senior hours.
Q: How do I price for agency work versus solo work?
Agency rates carry overhead — the PM's time, the contractor margin, the senior review. Standard agency multiplier on contractor cost is 2 to 3x; the agency rate to the client is usually 30 to 60 percent higher than the equivalent solo rate. Underpricing here is the fastest way to break a scaling practice.
Q: Should I structure as a partnership with another freelancer?
Possible, but write the partnership agreement before any money moves — equity split, decision rights, exit terms, profit distribution, dispute resolution. Most freelance partnerships fail at the year-three mark because the founding conversation was about chemistry rather than structure.
Q: How do I hire without burning my margin?
First hires should be billable from week one — the cost is paid by the client work they handle, not your savings. Target a 30 to 40 percent gross margin on every billable hire; below that, the hire is loss-making and the math gets worse as you scale.
Q: What is the first sign my scaling is going wrong?
Cash flow tightens, the founder is working more hours than before the hire, and quality complaints start arriving from clients you have not personally touched. Any one of the three means the SOPs are weak, the hire was wrong, or the pricing did not carry the overhead. Stop hiring until it is fixed.
Related guides
Scaling is the last major transition in the freelance lifecycle; the full lifecycle is in the freelance business management guide. For pricing agency work versus solo work, see the freelance pricing guide. For contracts covering agency engagements and partnership agreements, see the freelance contracts guide. For invoicing at agency scale, see getting paid as a freelancer. For onboarding clients when you have a team, see the client onboarding guide. For the tax and finance side of running a small agency, see the freelance taxes and finance guide.