TL;DR: Most founders bring in operational help too late, after the problems have already compounded. The right signal isn’t a headcount number or a revenue milestone. It’s a set of specific patterns: repeated interruptions you can’t stop, decisions only you can make, and processes that break every time you step away. This post covers what those signals look like, when bringing someone in won’t help, and what the right kind of help actually is.
There’s a version of “the business is going well” that looks a lot like a problem. Revenue is coming in. The team is busy. Clients are mostly happy. And you are answering the same questions you answered last week, making approvals that shouldn’t require you, and staying on top of things that have no business being on your plate.
A Harvard Business Review study found that founders spend close to 68% of their time on operational work rather than strategic activity. That ratio makes sense at the start, when there’s no one else. It stops making sense once the business has grown past you.
The question most founders ask is: do I need to hire someone? The better question is: what are my operations actually costing me right now? Because the answer to the first question depends entirely on the answer to the second.
What Does an Ops Person Actually Do?
An ops person takes the repeating, non-revenue work off your plate and owns it. Not strategically. Operationally. They answer the questions your team asks twice a week. They make sure the process runs when you’re not watching. They catch the thing before it becomes a fire.
PostHog described it plainly after building their first ops function: “Ops is a 100% defensive position in the early stages. Up to around 50 people, you’re putting out fires and making sure no one gets arrested.” That’s blunt, but accurate. The early ops role is not about building scalable systems for the next funding round. It’s about making the current week run without you touching everything.
When a good ops person is working well, they’re nearly invisible. The right things happen. Problems get caught early. Your team stops asking you questions that aren’t yours to answer. That’s the result. It’s quiet by design.
What Are the Signs You Need One?
The clearest signal that you need operational support is when your presence has become a structural dependency, not a choice.
A few patterns that indicate you’ve crossed that line: your team can’t move forward without your approval, and this happens more than a few times a day. You find yourself answering the same question for the third time this month. Your processes break down the moment you’re unavailable for more than a day. You’ve been aware of a recurring problem for three or more months and haven’t fixed it because you haven’t had time. You’re spending more time inside the work than on it, and that ratio has been worsening.
Research compiled from service business founders puts the figure at 30 to 40 hours per week spent on operational work that a properly structured business wouldn’t route through the owner at all. If you’re in that range, the cost isn’t just time. It’s the decisions you’re not making, the relationships you’re not building, and the problems you’re not catching because you’re too close to the day-to-day to see them.
The bottleneck isn’t always obvious from the inside. It often shows up as other things: slow delivery, team friction, projects that stall mid-execution. Most of the time the root is the same: too many things running through one person.
When Bringing Someone In Won’t Help
Here’s the part that doesn’t get said enough: if your processes aren’t documented, an ops hire won’t fix them. They’ll absorb your chaos instead.
A person stepping into an undocumented operation has to reverse-engineer how everything works, guess at the standards you haven’t written down, and make judgment calls in the absence of information. Some of that is unavoidable. But if the whole job is archaeology, they’ll spend six months figuring out what’s supposed to happen before they can do anything about it.
The mistake happens when founders treat a new hire as the system. The person becomes the process rather than the person who runs the process. That’s how the same problems persist under a new name.
The prerequisite for a good ops handoff is that the work is documented before you pass it on. Not perfectly (messy documentation beats none), but enough that someone can follow it and catch errors. The Self-Managing Business covers this directly: automation without foundation is just chaos at a faster speed. The same applies to delegation.
Working on the business means mapping the workflow, writing down what you do, and tracking what breaks. That’s the work you need to do before anyone else can take it over. If you haven’t done it yet, that’s the starting point, not the hire.
What Kind of Help Do You Actually Need?
Once you’ve established that you need outside operational support, the next decision is what shape that support should take.
The options are not just “hire someone or don’t.” There’s a spectrum, and matching the problem to the right model matters.
A project-based ops engagement is the right fit when you have a specific structural problem: a broken process, a system that needs building, a workflow that needs documenting and handing off. The engagement has a defined scope, a clear output, and an end date. You get the thing built and the work doesn’t continue indefinitely. Focused engagements typically run $10,000 to $25,000 for diagnosis and implementation support, compared to a fractional COO that runs $5,000 to $26,000 per month.
An ops coordinator or VA is the right fit when the problem is volume: too much recurring work, not enough hands. This is an executor, not a strategist. The first ops hire for most service businesses shouldn’t be a manager. It should be someone who does the operational work: answers the calls, runs the follow-up, manages the schedule, and removes it from your plate by doing it, not by directing others.
A fractional COO is the right fit when the problem is structural and strategic: the business needs new operating infrastructure, cross-functional decisions that sit above any one process, or leadership-level ops that can hold accountability across the team. Fractional COOs operate at a different altitude than ops managers. The cost reflects that. Most early-stage small teams don’t need one yet.
Choosing wrong costs time and money either way. Hiring an executor when you needed a strategist means someone doing manager-level work at executor rates while the structural problems persist. Hiring a strategist when you needed an executor means paying senior rates for work that didn’t require that seniority.
How The Admin Workshop Works
TAW sits in the project-based model. The work is always the same: find the structure problems, fix them, document everything so it holds, then step back. No retainer. No ongoing dependency. The goal is a business that runs on the system, not on whoever built it.
That’s the right fit when you know something is broken and you want it fixed properly, documented clearly, and handed off so you don’t have to touch it again. If that’s where you are, the Work With Me page has the details.
If you’re not there yet and the work is still at the foundation layer, start there. Build the systems that run without motivation, map the workflows, track what breaks. That work is yours to do first, and it’s worth doing before you bring anyone in.
The Right Question to Ask
The goal isn’t to hire an ops person. The goal is to stop being the single point of failure in your own business. Sometimes that requires a person. Sometimes it requires a better system. Usually it requires both, in that order.
The signal that tells you it’s time isn’t a revenue number or a headcount threshold. It’s what’s happening right now. If your business slows down when you’re unavailable, if problems route through you by default, if you’ve been aware of a fixable issue for months and haven’t had time to fix it, that’s the signal. The question then is just what to do about it.
Frequently Asked Questions
Ask yourself what would happen if you were unavailable for a week. If the answer is “things would break and no one would know what to do,” that’s a systems problem. If the answer is “things would run but I’d come back to a backlog of decisions only I can make,” that’s a capacity problem that a person can help with. Most founders need to address the systems problem first, document the process, make it hand-off-ready, before bringing someone in to run it.
A fractional COO is an embedded executive who owns operational outcomes across the business, sits in leadership meetings, and has authority over strategic decisions. An ops consultant typically comes in for a defined project: a broken process, a system that needs building, a workflow that needs documenting. The right choice depends on whether your problem is strategic or structural. Most small teams have structural problems that a project-based engagement can fix without the ongoing cost of a fractional executive.
There’s no universal threshold. The signals that matter are behavioral: you’re answering the same questions repeatedly, your team can’t move without your approval, your processes break when you step away. Some solo operators hit that point earlier than five-person teams. Some ten-person businesses still haven’t reached it. Team size and revenue are lagging indicators. The patterns in your day are the leading ones.
The work starts with identifying which structural problem is costing you the most right now. That leads into mapping the process as it actually happens (not as it should), fixing the specific break, documenting the fix so it’s maintainable, and handing it back. The engagement has a defined scope and a clear end. There’s no retainer, no ongoing dependency. You can find the details on the Work With Me page.
Yes. Solo operators are often the most affected by the single-point-of-failure problem, when everything runs through you, there’s no margin for unavailability. A project-based engagement can build the documentation, templates, and workflows that let you step away without everything pausing. That infrastructure also makes future delegation significantly easier, whether to a contractor, a part-time hire, or an automation.