Bring in help when a piece of the work has become repeatable enough that handing it over costs less than doing it. Stay solo while the answer is no. The question is which specific tasks leave, and never whether you should have a team, because a team is a consequence of that decision rather than a goal.
Pick the one repeatable task that eats the most hours, and hand over that task instead of hiring a person.
A defined task can be handed over this month. A role has to be designed, filled and managed first.
Track two weeks of your hours and mark every one that didn't need your judgment.
Add when it gets easy.
Leah Neaderthal, Smart Gets Paid
You're ready when a specific task is repeatable, documented in your head, and eating hours that don't need your expertise. Readiness is a property of the work rather than a revenue milestone, which is why the usual "hire at X dollars" advice tends to miss.
Three tests worth running:
The principle I'd apply is the one I use for adding anything: add when it gets easy. Take something on once it has been systematized, or once you've offloaded a piece of it, and not while it's still chaotic. Handing over chaos creates a second job, which is managing the person doing the chaos.
What should never leave your desk is the judgment and the client relationship, because those are the things a client is buying. Everything else is negotiable, and consultants tend to have this exactly backwards, holding on to the admin and worrying about handing over the parts they alone can do.
| Hand over readily | Keep, at this size |
|---|---|
| Scheduling, formatting, invoicing, expense admin | The sales conversation and the relationship |
| Research pulls and first-pass data gathering | The diagnosis and the recommendation |
| Recurring document setup from a template | What goes in the document |
| Posting, repurposing, list maintenance | Your point of view and your voice |
| Meeting notes and follow-up drafts | Deciding what happens next in a live opportunity |
The right-hand column is the reason a client pays you rather than someone cheaper, and it's also the work that a long B2B sale turns on. Your voice belongs in the left column's outputs too: somebody can draft and schedule, and what's said still has to sound like you.
Contractors are the normal shape for a consulting business at this size, and most never move past that. My own business is supported by a distributed team of contractors, and the consultants I work with are typically solo or working with up to five people on the same basis.
The trade-offs, plainly:
The revenue swing is the thing to weigh hardest, because a fixed monthly cost against a variable income changes how every quiet month feels. If your income still moves a lot, steadying that first makes this decision much less risky than it is today.
Staying solo is a legitimate destination and not a stage you failed to leave. The assumption that a good business grows into a team comes from a different kind of business, and it gets applied to consulting where it often doesn't fit.
What solo can't do is exceed your own hours, and that's the real constraint. Which is exactly why pricing on the value of the outcome and the engagement levers come first: growing without adding hours raises the ceiling on a solo business without adding a single person, and a lot of consultants discover that the ceiling they were trying to hire past was a pricing structure instead.
I'd push back gently on the framing of the question, because "hire help or stay solo" sounds like a fork in the road and it usually isn't one.
What I see is women asking it when they're tired. And when you're tired, "I need help" feels like the answer, because help is a thing you can go and get. But hiring while you're at capacity means finding someone, onboarding them and managing them, all of which comes out of the hours you didn't have. That's why the first hire so often makes the next two months worse before it makes anything better.
So the order matters. If your price is tied to your time, help is a cost that comes straight out of a capped number. Change the structure first and the same help becomes an investment against a number that can grow.
The other thing I'd say is that a lot of what looks like a capacity problem is a saying-yes problem, and it's cheaper to fix. Before you add a person, look hard at what's on the calendar that shouldn't be. Then hire, if you still need to, into a business you'd want somebody to join.
Handing over costs time up front and the cost is bounded if you pick the right task. Choose something you do repeatedly, write the steps once while you're doing it, and let that document be the training. The repetition is what makes the investment pay back. A one-off task will always cost more to explain than to do, which is why the steady ones go first.
Some quality drop is normal at first and the question is whether the task tolerates it. Scheduling and formatting tolerate a learning period. Anything a client sees with your name on it needs a review step until the person's judgment is proven. Building that review in from the start is what keeps a handover from becoming a crisis in month two.
Outreach that trades on your relationships and your voice doesn't transfer well, so the parts of business development that can be handed over are usually mechanical: list building, scheduling, repurposing, follow-up drafting. The conversation itself is the product. A consulting sale runs on whether a client trusts the person who will do the work, and that person is you.
Employment status is a legal test rather than a judgment call, and it turns on control, exclusivity and how the working relationship operates, not on what the contract is titled. The rules vary by state and country and they change. Anyone whose contractor arrangement has started to look like a permanent role should get advice from an employment attorney or an accountant in their jurisdiction.