When should I hire my first operations person?

When you have become the bottleneck: when growth is capped by your hours, the same fires keep starting because no one but you can put them out, and you are doing the work instead of building the business. The signal is not revenue at a magic number; it is that the operation cannot move faster than you personally can, and that ceiling is now the thing holding the brand back.

Should my first ops hire be a generalist or a specialist?

Usually a generalist operator who can own process, not a specialist who does one task well. Early on you need someone who takes whole problems off your plate, inventory, fulfillment, customer issues, and runs them end to end. A specialist solves one thing and hands the rest back to you. Hire the owner first; add specialists once there is enough volume in one area to justify one.

How do I set up an operations hire to succeed?

Document the work before they start, even roughly, so you are handing over a process, not just chaos. Delegate outcomes, the inventory never stocks out, not tasks, click these buttons. And start with a paid trial on real work, because operations is judgment under pressure, and you learn more from two weeks of real tasks than from any interview.

Why do first operations hires often fail?

Three reasons: hired too late, when the founder is too underwater to onboard anyone; hired as a specialist when the brand needed an owner; or handed undocumented chaos and blamed for not fixing it. The fix for all three is the same: hire before you are desperate, hire for ownership and judgment, and write down the work first so there is a system to step into.

Insight The operator's journey

Hiring your first operations person: when, who, and how

Hire an operations person too early and you spend your time managing them; too late and you are the ceiling your own business hits. Here is when to make the hire, who to look for, and how to set them up to actually take work off you.

April 12, 2026 7 min read

Every founder hits the same wall: the business cannot grow faster than you personally can work, because everything still runs through you. The answer is your first ecommerce ops hire, and it is one of the most mistimed, mis-specced decisions a brand makes. Hire too early and you spend your scarce hours managing someone with not enough to do. Hire too late and you are so underwater you cannot onboard them properly. Get the who wrong and you add a task-doer when you needed an owner. Here is how to think about when, who, and how.

When to make your first ecommerce ops hire: the day you became the ceiling

There is no revenue number that says hire now. When to hire operations is not a question of size; the real signal is that you have become the bottleneck. Growth is capped by your hours. The same fires keep starting because no one else can put them out. You are spending your days inside the operation instead of on the business, and you can feel that your own capacity is now the thing holding the brand back. That is the moment, and it almost always arrives before founders are willing to admit it, because hiring feels like a cost and they are used to doing everything themselves.

You do not hire your first operator when you can afford to. You hire when you have become the thing your business cannot grow past.

Who: an owner, not a task-doer

This is where hiring ecommerce operations most often goes wrong. Under pressure, founders hire a specialist, someone who runs ads, or edits listings, or answers tickets, because that is the task in front of them. But a specialist solves one thing and hands the rest back to you, so you are still the owner of everything else. What you actually need first is a generalist operator: someone who can take a whole problem, inventory, fulfillment, customer issues, and own it end to end without you in the loop.

Hire for judgment, not for a skill list. Operations is decisions under incomplete information and time pressure, and you cannot hand that to someone who needs the answer for every situation. The specialists come later, when one area has enough volume to justify a dedicated person. The first hire’s job is to take ownership off your plate, not tasks.

How: hand over a system, not a mess

The fastest way to fail an operations hire is to drop undocumented chaos on them and expect them to fix it. They cannot run a process that exists only in your head.

Set up a first operations hire to succeed

Document the core work first, even roughly, so they inherit a process
Delegate outcomes, the inventory never stocks out, not button-clicks
Start with a paid trial on real tasks, not just interviews
Give them whole problems to own, not fragments to execute
Hire for judgment and ownership over a long skill list

Writing the work down first is the unlock, and it is the same point as the guide to SOPs: a procedure is what turns your instinct into something another person can run. If you document the core routines before the hire starts, you are handing over a system to step into, not a fire to fight blind.

And start with real work. Operations is judgment under pressure, and you learn more from two weeks of someone handling actual tasks than from any number of interviews. A paid trial on live problems tells you, fast, whether they own outcomes or wait for instructions.

The deeper point

Your first operations hire is really the moment you decide to build a business instead of a job. It is the same shift behind scaling without operational chaos: the work stops living in your head and starts living in a system and a person who can run it. Most founders delay it because they are good at the work; the ones who break through are the ones who get good at handing it off.

This is the operator’s journey at its most practical: learning that the highest-leverage thing you can do is stop being the only one who can do everything. If you are the bottleneck and not sure what to document or delegate first, that mapping, what only you can do versus what a system and a hire can, is exactly where a Growth Audit starts.