Automation vs. hiring: when to build instead of recruit
Not every capacity problem needs a new head. Sometimes the answer is a pipeline, not a person.
The default response
Business grows. Work increases. Hire someone to handle it.
This works — until it doesn't. Some work scales linearly with headcount. Some work shouldn't exist at all.
When to automate instead
The work is repetitive and rule-based. If a task follows the same pattern every time, a machine should do it. Humans are expensive pattern-matchers.
The work is time-sensitive but low-judgment. Data entry, reconciliation, status updates, notification routing — these need speed, not creativity.
The work creates bottlenecks at handoffs. If person A finishes something and person B doesn't know about it until they check a spreadsheet, that's a pipeline problem, not a capacity problem.
When to hire instead
The work requires judgment and relationship. Client management, strategy, creative direction — these need humans.
The work is genuinely novel each time. If no two instances look the same, automation can't capture the pattern.
You need someone accountable. Machines don't own outcomes. Sometimes you need a person who wakes up thinking about this problem.
The decision framework
Ask: "If I hired someone for this, what would they spend 80% of their time doing?"
If the answer is repetitive, rule-based, or handoff-dependent — build first, hire later. Use the saved salary budget to fund the build.