Building Your First Operations Team From Scratch
The first operations hire is the most important hire a founder makes and the most commonly made wrong. Most founders hire for the task they can see rather than the system they need to build. Here is what the first operations team should actually look like.
Prince Kumar
Author
A founder running a D2C brand at ₹80 lakh monthly revenue hired an operations manager whose primary qualification was having managed a warehouse at a larger brand. The hire was sensible on paper. In practice, the operations manager was excellent at executing within a defined system and poor at building one. The brand's operations problem was not execution quality it was the absence of systems that could be executed at all. Hiring an executor into a system-building role is the most common operations hiring mistake in early-stage businesses.
The First Hire Should Be a Builder
The first operations hire needs to be someone who has built operational systems from near-zero before, not someone who has operated within a mature system. These are different skills. A builder will identify the processes that need to exist, document them, test them, and iterate. An operator will follow the processes that exist and escalate when they break. In a business that does not yet have mature processes, the operator has nothing to operate and the escalation queue is permanent.Builders are harder to identify in interviews because their output is less visible than operators. The right interview question is not 'tell me about a time you managed a high-volume operation' but 'tell me about a time you created an operational system from scratch what did it look like before, what did you build, and what did it look like six months later.'
What the First Operations Team Actually Needs to Own
The first operations team owns three things: order fulfilment integrity, inventory accuracy, and vendor reliability. Everything else process documentation, system implementation, team training is in service of these three outcomes. If orders ship correctly and on time, inventory is accurate, and vendors deliver reliably, the operations function is working. If any of the three is broken, nothing else matters.The mistake founders make is hiring for the visible tasks someone to manage the WhatsApp group with the logistics partner, someone to maintain the inventory spreadsheet rather than for these outcomes. Task-level hiring produces task-level accountability. You want outcome-level accountability from the first day.
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.