What an ops manager actually does
An operations manager's job is to create order out of chaos. But "chaos" comes in two forms, and they require different solutions.
The first is operational chaos: workflows that don't exist, tasks that fall through the cracks, inconsistent execution of repeatable processes. This is largely a systems problem. The second is human and judgment chaos: team coordination, vendor disputes, client escalations, strategic decisions under uncertainty. This requires a person.
Most founders who hire an ops manager are trying to solve type 1 chaos with a type 2 solution. The ops manager then spends 60-70% of their time on work that should be automated: chasing invoices, sending follow-ups, compiling reports, updating CRMs. They are capable of much more, but they're buried in work a system should be doing.
What an ops manager actually costs
The salary number is only the starting point. For a US-based operations manager at a small or mid-size business, here is what the first year actually looks like:
On ramp time: The average SMB operations manager is fully productive after 3-6 months. During that ramp period, you are paying full salary for partial output while also spending your own time training and managing them.
What automation actually solves
For a business at $1M-$3M revenue, automation typically handles the operational layer that ops managers get stuck doing. The six most common flows:
- Flow 1 Lead in from any source, instant response sent, CRM record created, owner notified, follow-up sequence triggered
- Flow 2 Quote sent, follow-up at 3 days if no response, second follow-up at 7 days, escalation alert to owner at 14 days
- Flow 3 Job complete, invoice sent automatically, follow-up at day 3, firmer message at day 7, escalation at day 14
- Flow 4 Job complete, 24hr delay, review request text, thank-you if clicked, second request if not
- Flow 5 New client books, onboarding sequence starts, intro email day 1, check-in at day 7, satisfaction survey at day 30
- Flow 6 Weekly report auto-compiled from Jobber, QuickBooks, Google Sheets, sent to owner every Monday 8am
These six flows represent the operational layer that takes a capable ops manager 15-25 hours per week to do manually. Built once: $4,000-$12,000. Ongoing: $100-$300/month in tools.
Where each one actually wins
This is not an either/or argument. Automation and an ops manager solve different problems. The question is which problem you have right now.
- Invoice follow-up sequences
- Lead follow-up and nurture
- Appointment reminders
- Review request campaigns
- CRM data sync across tools
- Recurring report generation
- New client onboarding sequences
- Job dispatch and scheduling notifications
- Team hiring, onboarding, and performance management
- Client escalations and conflict resolution
- Vendor negotiations
- Strategic process redesign
- Managing subcontractors
- Complex scheduling requiring judgment
- Culture and accountability building
- Anything that changes week to week
The pattern is consistent: automation handles tasks that are rule-based, triggered by an event, and produce the same output every time. An ops manager handles the work that requires reading context, making a judgment call, or managing a human being.
The order matters
"Hire an ops manager to run your system, not to build it. If you hire before building, they spend half their time doing work automation should do."
Most founders who have done this once will tell you: build the automation layer first. When your ops manager starts, give them a business where the admin runs itself. They can then focus on what only a person can do: team development, client relationships, strategic execution.
The founders who hire ops managers first often find:
- The ops manager gets buried in repetitive admin within 60 days
- The chaos continues because the underlying processes were never systematized
- The ops manager eventually leaves because the role was not clearly defined
- They hire again, same outcome
The automation does not replace the ops manager. It clears the path so the ops manager can do the actual job you hired them for.
Decision framework: automate first, hire second
Case study: landscaping company, $2.1M revenue
The owner was on the verge of posting the job listing for an operations manager at $70,000/year base. Before doing that, he ran a workflow audit with Aplos AI.
Finding: 22 hours per week of the intended ops manager role were automatable. Lead follow-up, job completion sequences, invoice chasing, crew dispatch notifications, and weekly revenue reporting were all rule-based, repeatable, and had no reason to involve a person.
Built: Custom automation stack on Make, n8n, Jobber, and QuickBooks. $8,400 one-time. $180/month in tools.
Result: The owner decided to hold on the ops manager hire. Eight months later, with the business growing and the admin running itself, he hired an ops manager with a much cleaner brief: crew management, client relationships, and growth planning. The automation handled the entire admin layer, and the ops manager could actually do the job from day one.
When to hire the ops manager anyway
At a certain scale, you need an ops manager. The question is when. Here are the clear signals that the hire is right:
- You have 15+ employees and team coordination load is beyond what systems can handle
- Client relationships require a dedicated person, not just automated sequences
- You are ready to step out of day-to-day operations and need someone accountable for operational performance
- Your growth rate means new process problems emerge faster than you can systematize them
At that point, hire the ops manager. But hire them to run a system, not to build one from scratch. The businesses that do this in the right order get more out of the hire because the role is actually defined.
Not sure whether you need automation or an ops hire first? That is exactly what our free audit covers. We will look at your operation, identify what should be automated, and tell you what would remain for a future ops manager.
Book a Free Audit →