An operations manager owns how the work gets done — scheduling, process, vendor coordination, quality, and the daily decisions that keep production or delivery moving. In most small businesses, the owner does this job by default, usually alongside sales and finance.
The hire is expensive and hard to reverse, and the timing question is genuinely difficult because the most common signal people use to answer it is the wrong one.
The signal most people use, and why it's misleading
"I'm working too many hours."
Real, but not diagnostic. Owners work long hours at every stage, and the hours are frequently going into things an operations manager wouldn't take. If you're at sixty hours because you're doing quoting, collections, and customer relationships, hiring ops won't touch it. You'll have a new salary and roughly the same week.
The useful version of the question is not how many hours you're working. It's which hours, and what they'd be worth spent elsewhere.
The signals that actually indicate readiness
You're the bottleneck on decisions that don't need you. Work stops because someone is waiting on you to approve something routine, and you can't remember the last time you disagreed with what they'd have decided anyway. This is the clearest signal there is — it means the decisions are systematizable and you're the constraint.
Quality or delivery problems are recurring rather than isolated. One late shipment is an incident. The same category of failure three times in a quarter means nobody owns the process, and process ownership is exactly the job.
Growth is constrained by coordination, not demand. You could take more work but you're not confident you could deliver it. If you turned down or slow-walked business in the last six months because you weren't sure about capacity, that's a quantifiable cost of not hiring.
You've stopped doing the work only you can do. Nobody else can set your strategy, own your key customer relationships, or make pricing decisions. If those are being squeezed out by scheduling and vendor calls, the arithmetic has already turned.
The processes exist, even informally. An ops manager inherits and improves systems. Where there are none at all, they spend their first year inventing them from scratch — which some can do, but it's a much harder hire requiring a much more experienced person.
The signals that say wait
- Revenue is volatile. If your trailing twelve months swing wide, a fixed salary against variable revenue is a real risk. Look at your worst quarter, not your average.
- You can't articulate the role. If you can't write out what decisions this person owns and what they don't, you'll hire someone competent, fail to hand anything over, and conclude the hire didn't work.
- The problem is one person. Sometimes what looks like an operations gap is a specific individual underperforming. A new manager doesn't fix that, it adds a layer over it — handling it directly is the faster fix if that's actually your situation.
- You want someone to fix a problem you haven't diagnosed. Hiring in response to general stress produces vague roles and short tenures.
The affordability math
Fully loaded cost is not the salary. Add payroll taxes, benefits, and equipment — commonly 25–40% on top depending on what you offer. A $75,000 salary is realistically $95,000–$105,000 against your P&L.
Then run three numbers:
Months of runway at current cash. If the hire doesn't work out, how long do you have? Under six months and the risk is high enough to wait or hire more cheaply.
Break-even in revenue. At your gross margin, how much additional revenue covers the fully loaded cost? At 35% gross margin, a $100,000 cost needs roughly $285,000 in additional revenue. Ask honestly whether that's plausible in year one.
Cost of the constraint. What did you turn down, deliver late, or lose in the last twelve months because coordination was the limit? This is the number most owners skip, and it's often larger than the salary. It's also the only one that makes the case affirmatively rather than defensively.
Structuring the hire so it works
Write the decision list before you post the job. Ten to fifteen specific decisions this person will own without asking you. If the list is short, the role isn't real yet.
Hire for your actual constraint. Scheduling and throughput problems need a different person than quality and compliance problems. "Operations manager" covers both and they're rarely the same candidate.
Plan the handoff explicitly. The most common failure isn't a bad hire — it's a good hire who never gets given anything, because handing over work is uncomfortable and slower than doing it yourself for the first two months. Decide in advance what transfers in week two, week six, and week twelve.
Consider the interim version. A part-time ops consultant or a promoted internal candidate with support can test the thesis at lower cost — the same fractional-versus-full-time trade-off we've written about for the CFO role applies here too. Promotion from within also solves the process-knowledge problem, which is often the hardest part.
The short version
Hire when specific decisions are stacking up behind you, when the processes exist well enough to hand over, and when you've done the math on what the constraint has already cost you. Wait when the role is a feeling rather than a list.
When you want a second opinion on the math
Helm's HR Director advisor can help you draft the actual decision list before you post the role, and the COO advisor can pressure-test whether your processes are mature enough to hand over. Ask either one to check the affordability math against your real QuickBooks numbers — break-even revenue, current margin, months of runway — before you commit to a number you're guessing at.