At some point every founder hits the wall. Operations eat 40% of your week. You are either going to hire somebody to take it over or you are going to build systems that run without a dedicated person.
Which one is right?
Most founders default to hiring. Hiring feels like progress. "I now have an operations manager" sounds better than "I now have a Supabase database and six workflows." It is not always the right call.
The Honest Framework
Three questions.
1. Is the work repeatable or judgment-intensive?
Repeatable work (reporting, reminders, data entry, lead routing, invoice generation, onboarding sequences) does not need a person. It needs a system. Hiring a person to do repeatable work is the most common mistake we see.
Judgment work (escalations, strategic decisions, client conversations, edge cases, quality review) needs a person. Systems cannot handle judgment reliably.
Most operations work is 70% repeatable, 30% judgment. The system handles the 70%. A person handles the 30%. If you hire first, the person ends up doing 100% manually and you have just bought yourself a very expensive assistant.
2. What is the volume?
Below a certain volume threshold, a person can handle it without a system. Above that threshold, no person can keep up.
Rough heuristic: if you handle fewer than 20 of any specific thing per week (leads, clients, invoices, tickets), a person can do it. Above 50, you need a system. Between 20 and 50, you need both.
3. What is the cost comparison?
An operations manager in Europe is €50K to €90K per year all-in, plus onboarding time, plus management overhead. A decent operations system is a one-time build plus a small monthly tool stack.
If the work is repeatable, the system wins on cost by 5 to 10 times.
The Right Order (Most of the Time)
Systems first, then a person.
Here is why. If you hire first, the person builds their own processes in their head. They become the process. When they leave (and they will), the knowledge walks out the door.
If you build systems first, the process is documented and automated. The person you eventually hire inherits a working system. They manage it, they don't reinvent it.
Ops managers running on top of good systems do judgment work. Ops managers without systems do manual work that should have been automated and they burn out.
When Hiring First Is Right
Three scenarios.
Scenario 1: You don't know what the process should be yet. If the work is new and undefined, a smart ops person can figure it out faster than you can. Once they've run it for 6 months, automate what they built.
Scenario 2: High-touch, relationship-driven work. If the "operations" is really account management or customer success, you need a person. Systems support them; they don't replace them.
Scenario 3: Compliance or regulated environments. Sometimes regulation requires a human in the loop. Healthcare, legal, financial. Systems augment, but a person owns.
When Building Systems First Is Right
The most common scenario. Repeatable work at volume with clear rules. Lead routing. Reporting. Onboarding. Reminders. Billing. Most of what founders call "operations."
Build the system. Then, if you still need a person, you will need a much smaller one.
The Hybrid
What usually happens in practice. Build a system for the 70% that is repeatable. Hire a part-time ops person (10 to 20 hours per week, contractor or fractional) to handle the 30% that is judgment. Much cheaper than a full-time hire.