Your First Operational Hires, and the Order to Make Them
The first few operational hires set the shape of the company for years. How to decide what to hire, and in what order.
Hire against the constraint that is actually binding, and hire the shape of person who can build the function rather than run it. The first three or four operational hires set how the company works for years, because each one brings their own assumptions about how things should be done and those assumptions become the default long before anyone writes them down.
Separate the constraint from the noise.
The instinct is to hire where the pain is loudest, which is usually wherever the founder spent their worst week. That is a poor signal, because the loudest pain is often a symptom of a constraint sitting somewhere else entirely.
The better question is what would still be true in six months if nothing changed. A support queue that is briefly overwhelmed after a launch is noise. A support queue that is overwhelmed because nobody owns onboarding is a constraint, and hiring another support person will not fix it.
This distinction is worth an hour of genuine thought before any brief is written. That hour is the difference between a hire that removes a problem and a hire that absorbs one.
Builders and runners are different people
Early operational hires are being asked to create a function that does not exist: decide how it should work, set it up, and then operate it. That is a different person from someone who is excellent at running an established function well.
Candidates from larger companies often have deeper functional expertise and far less experience deciding what the function should be. Some make the transition comfortably and some find the absence of structure genuinely disorienting.
The interview question that separates them is not about achievements. Ask what they did when the process they needed did not exist.
A rough sequence that usually holds
Every company is different, but the order below is a reasonable default for a B2B business, and the column that matters most is the last one.
| Hire | Owns | Overdue when |
|---|---|---|
| Customer onboarding and success | The path from signed to using it properly | Churn is happening in the first ninety days |
| Revenue or sales operations | Pipeline hygiene, forecasting, tooling | Nobody can answer what is actually in pipeline |
| Delivery or implementation | Getting the work done repeatably | Delivery quality depends on who happens to pick it up |
| Finance and administration | Cash, invoicing, reporting rhythm | The founder is still doing invoicing at month end |
| People and operations | Hiring, onboarding, internal process | New starters take more than a month to be useful |
| Senior operating leadership | How the whole thing runs together | The functions now collide rather than connect |
Write the brief from the outcome backwards
Most early job descriptions are a list of responsibilities, which attracts people who are comfortable with the responsibilities and tells you very little about whether they can produce the outcome.
Write down what should be true in six months that is not true now. Then describe the person who could make that true in a company with very little existing structure. The list of duties falls out of that, and the interview has something to test.
It also gives you an honest basis for the first review, rather than a conversation about whether someone seems to be working hard.
Do not hire around an unmade decision
A hire made to avoid a decision inherits the ambiguity. If nobody has decided whether the company sells to small businesses or to enterprises, a commercial hire will pick one, and the decision will have been made by default by whoever you happened to hire.
The same applies to operating structure. Hiring a senior operator into an undefined mandate usually produces six months of discovery the business could have done itself in six weeks.
Where the decision is genuinely hard, it is cheaper to get senior help making it than to hire a permanent person and hope the decision emerges.
Count the capacity the hire consumes
Every early hire costs existing capacity before it adds any. Someone has to write the brief, run the process, onboard them, answer questions for a month, and correct course when the first attempt at something is wrong.
In a small team that cost is significant and routinely ignored in planning. Two simultaneous hires into a ten-person company can consume most of a founder's quarter.
Sequencing hires rather than batching them is usually the right call, not because the roles are less urgent but because the business can only absorb so much onboarding at once.
Know when the answer is not a hire
Some of what looks like a capacity problem is a design problem, and some is work that should not exist. Before adding a person to absorb administrative load, it is worth asking how much of that load is repeatable enough to remove.
Contractors, fractional support, and automation all cover ground that does not yet justify a permanent seat, and all of them are easier to reverse than a hire.
The test is whether the work will still be there, at that volume, in twelve months. If the honest answer is unclear, a permanent hire is the most expensive way to find out.
What to check in your business
- The constraint has been separated from the loudest pain.
- The brief describes an outcome, not a list of duties.
- The role is a builder brief, not a runner brief, where the function does not exist yet.
- No hire is standing in for a decision nobody has made.
- The onboarding cost has been counted against existing capacity.
- Contract, fractional, or automation options were considered first.
The first few operational hires are not just capacity. They are the point at which the company acquires opinions about how it works, so it is worth choosing those opinions deliberately.
Frequently asked questions
What is the first operational hire a startup should make?
Most commonly customer onboarding and success, because it protects revenue that has already been won and it is usually the first place informal handling starts costing money. The real answer is whichever constraint would still be binding in six months if nothing changed.
Should I hire a senior operator or a junior one first?
Where the function does not exist yet, seniority in deciding how it should work matters more than functional depth. A capable junior hire into an undefined function usually ends up asking the founder how everything should be done, which does not relieve the constraint.
How do I know if I am hiring too early?
If you cannot describe what should be true in six months that is not true now, the brief is not ready. Work that would not still exist at that volume in twelve months is better tested with a contractor or a fractional arrangement.
Can I make two operational hires at once?
You can, but count the cost. Each hire consumes briefing, process, onboarding, and correction time before it adds capacity, and in a ten-person company two at once can absorb most of a founder's quarter.
Discuss your operating challenge.
I aim to respond within two business days.