When to Hire vs Automate: The Founder's Decision Framework
Every operational bottleneck presents the same decision: hire someone to handle it, or automate it. The wrong choice is costly in both directions. A framework for making this decision consistently and correctly.
Aditya Sharma
Author
A logistics-dependent D2C brand was spending 3 hours daily reconciling courier NDR reports across four different platforms. The founder hired a coordinator to handle it. Twelve months later, the coordinator was spending 4 hours daily on the same task because volumes had grown, and the founder was considering a second hire. The task was automatable from day one. The hire was a decision made out of urgency rather than analysis. The automation cost ₹8,000 per month in tooling. The coordinator cost ₹35,000 per month and was still underutilised on the non-automatable portions of their role.
The Automation Test
A task is a candidate for automation if it meets three criteria: it is rules-based (the logic for completing it can be written down explicitly), it is repetitive (it occurs on a defined schedule or in response to a defined trigger), and it is high-volume (it occurs frequently enough that the labour cost of human execution is significant at scale). Tasks that meet all three criteria should be automated before being staffed, except in two cases: when the task requires relationship judgment that cannot be encoded, or when the regulatory or reputational risk of an automated error exceeds the cost of human oversight.Tasks that fail any of the three criteria that require discretion, occur rarely, or occur at low volume are hiring candidates rather than automation candidates. The error is applying automation to low-volume, judgment-intensive tasks (where the implementation cost exceeds the labour saving) or applying human labour to high-volume, rules-based tasks (where the labour cost grows linearly with volume instead of being fixed).
The Hybrid Approach
Most operational tasks are not purely automatable or purely human. They have a rules-based component that can be automated and a judgment component that requires human review. The right architecture for these tasks is automated execution with human exception handling: the automation handles the 80% of instances that follow the rule, and a human handles the 20% of exceptions that require judgment.This hybrid architecture is more efficient than full human handling (80% cost reduction on the rules-based volume) and more reliable than full automation (the judgment component has human oversight). It also scales better than either alternative volume growth increases automation throughput without increasing cost, while the human exception handling load grows more slowly than total volume because only exceptions route to the human.
Related articles
View all →
Seasonal InventoryInventory Planning for Seasonal Demand
Seasonal demand is predictable. Seasonal inventory problems are not inevitable they are the result of predictable demand being met with reactive planning. The brand that plans its Diwali inventory in October is already too late. The brand that planned it in August has the right stock, in the right channels, at the right cost.
Systems DesignBuilding Systems That Scale With You
Most founders build systems for the current problem. The right systems are built for three problems ahead designed to handle 5x the current volume with configuration changes rather than architectural rebuilds. The difference between a system that scales and one that requires replacement is in the design decisions made when the current volume is modest.
Real-Time DataWhy Real-Time Data Changes Everything
The difference between data that is 3 days old and data that is 3 hours old is not precision. It is the ability to act in the decision window. Most operational decisions have a window a period during which action changes the outcome. Real-time data keeps decisions inside the window. Daily or weekly data arrives after it has closed.