
Every growing company hits the same inflection point: a workflow is bottlenecked, and someone proposes hiring. More volume needs more people, and people need to be hired now. The automation alternative takes longer, costs more upfront, and requires skills the team might not have.
So they hire. And the next quarter, they hire again. And again. Until the operations team is the largest department and the company's margins are permanently compressed by headcount that scales linearly with revenue.
There's a better framework for this decision. It starts with one question: does this workflow require judgment that can't be specified?
The Judgment Test
If you can write rules for every decision in a workflow, it should be automated. Not "could be automated someday" - should be automated now. Rules-based work done by humans is waste.
The test is specific: can you describe, in precise terms, how an expert handles every scenario? If yes, that's a system specification, not a job description. If the expert says "I just know" or "it depends on the vibe" - that's genuine judgment, and it might need a human.
But be rigorous. Most "judgment" calls are actually pattern matching on well-defined variables. "I look at the customer's history, the order size, and whether they've complained before" - that's an algorithm, not intuition. Push past the first answer. Most workflows that feel like they need judgment actually need better data and clearer rules.
The Volume Question
Low-volume, high-complexity work favors humans. A company that handles 10 custom enterprise contracts per month probably doesn't need an automated contract system - the volume doesn't justify the investment, and each contract genuinely requires negotiation.
High-volume, any-complexity work favors systems. Once you're processing hundreds or thousands of items per day, even moderately complex decision logic should be codified. The error reduction alone pays for the system.
The dangerous middle ground is medium-volume, medium-complexity. It feels manageable with people. It is manageable with people. But it doesn't scale, and the hidden taxes of manual operations compound as volume grows.
Low-volume, high-complexity work favors humans.
The Scaling Math
Here's the math most companies skip: if your revenue grows 50% next year, how does this workflow scale?
With people, costs grow linearly (or worse - hiring gets harder and slower as you scale). With a system, marginal cost approaches zero. The first transaction costs the entire system build. The millionth transaction costs infrastructure.
Plot both curves. The crossover point - where cumulative automation cost drops below cumulative hiring cost - is usually 12-18 months. After that, the gap widens every quarter. Companies that hire past the crossover point are choosing permanently higher operating costs.
The Real Framework
Hire when the work requires genuine creative judgment, relationship building, or novel problem-solving that changes shape constantly. Hire for the work that gets more interesting as it gets harder.
Automate everything else. Every workflow that is repeatable, rule-based, or data-driven. Every workflow where consistency matters more than creativity. Every workflow where speed matters and humans are the bottleneck.
The honest version: about 70% of operations work in most companies should be automated. Not augmented, not assisted - automated. The remaining 30% is where humans create actual value. Let them focus there.
Next time someone requests headcount, ask for the workflow specification instead. If they can write it down clearly enough to train a new hire, they've written clearly enough to build a system.
Related

Why Copilots Miss the Point
Copilots keep humans doing the wrong work. The goal isn't better tools for manual tasks - it's eliminating the manual tasks entirely.

Anatomy of an Autonomous Operation
What it actually means for a system to operate autonomously. Decision loops, exception handling, state management, self-correction.
Building something that should run itself?
Start Building