Every post-funding founder reaches the same moment. The round is closed, the hiring plan is approved, and somewhere on it sits a line that says "operations hire".
What happens next usually goes one of two ways. The hire becomes a force multiplier who frees the founder to do founder work. Or the hire becomes an expensive coordinator who schedules meetings, chases updates, and quietly leaves within a year.
The difference is rarely the person. It is the scoping, the timing, and the first 90 days. All three are decided by the founder before the hire walks in.
Why This Hire Is Different From Every Other Hire
Your first sales hire has a quota. Your first engineer has a backlog. The work defines itself.
Your first operational hire inherits a job that does not exist yet. Operations at a 15-person startup is whatever the founder has been absorbing: tooling, onboarding, reporting, vendor management, process gaps, and a hundred small decisions. None of it is written down. Most of it lives in the founder's head.
That means the hire's success depends almost entirely on how well the founder can hand over a function they have never defined. Which is why the preparation matters more than the interview process.
First Decision: Do You Actually Need a Hire Yet?
The honest checklist. You need an operational hire when:
You are spending ten or more hours a week on coordination work that does not need a founder. Internal questions all route to you by default. Processes break when you are not watching them. Reporting to investors takes days because data lives everywhere.
You do not need an operational hire when the real problem is undocumented processes, a broken tool stack, or unclear ownership. A hire inherits that chaos. They do not fix it, because they lack the context and authority to fix it. Foundation first, hire second. We laid out that sequence in Building Operational Foundation After Fundraising: The First 90 Days.
If you cannot write one page describing what this person owns, you are not ready to hire them.
Which Role to Hire First
Three realistic options, in order of how often they are the right answer:
Operations manager. Owns the running of the business day to day: tooling, onboarding, process execution, reporting. Right when the work is operational volume. This is the correct first hire for most startups between 10 and 30 people.
Chief of staff. Extends the founder: special projects, cross-functional coordination, investor materials. Right when the founder's bottleneck is leverage rather than process volume. Often wrong as a first hire because the role inherits ambiguity and adds none of the structure the business is missing.
Head of operations / COO. Owns operational strategy and builds the function. Almost always premature as a first hire. A head of operations with nobody to manage and no foundation to run becomes a very expensive operations manager. Hire this person second, or bring in fractional leadership until the function justifies a full-time executive.
The pattern to avoid: hiring senior because the title attracts better candidates. Scope the role to the actual work, then hire the level the work demands.
Scoping the Role: The One-Page Mandate
Before the job description, write the mandate. One page, four sections:
Own: the five to seven things this person is accountable for. Not "help with". Own.
Decide: what they can decide without you. Spending up to a threshold. Tool selection within a budget. Process changes within their areas.
Escalate: what still comes to you, and for how long.
Success at 12 months: three measurable statements. "Founder spends under two hours a week on internal coordination." "New hires productive in two weeks." "Monthly investor update produced without founder involvement."
This page does three jobs: it forces clarity before the search, it becomes the job description, and it becomes the onboarding plan.
The First 90 Days: Diagnose, Document, Then Own
The biggest onboarding mistake is handing the new hire a backlog of tasks on day one. Tasks make them a coordinator. The sequence that makes them an owner:
Days 1 to 30: diagnose. They shadow every function, sit in every recurring meeting, and map how work actually flows. Output: a written diagnosis of what works, what breaks, and what is missing. Founders consistently learn things from this document.
Days 31 to 60: document and fix. They write the SOPs for the five most critical processes and fix the three worst points of friction from the diagnosis. Quick wins build the authority they will need.
Days 61 to 90: own. Functions transfer formally, one at a time, against the mandate page. Each transfer includes the decision rights that go with it.
By day 90 the role either has clear ownership or it has drifted into assistance. There is rarely a middle state.
The Handover Discipline Founders Get Wrong
Transferring a function is not telling someone "you own onboarding now". It is three steps:
Do it together once. Watch them do it once. Then stop attending entirely.
The third step is where founders fail. Staying in the loop "just in case" signals to the whole team that the founder is still the real owner, and every question keeps routing around the new hire. If you have struggled with this pattern before, the dynamics are the same ones we covered in Why Founders Become the Bottleneck.
Where to Find This Person (And Who Not to Hire)
The best first operational hires come from three backgrounds, in rough order of fit:
Operations roles at slightly larger startups. Someone who has run operations at a 50-person company has seen what your 15-person company is about to become. They bring pattern recognition you cannot interview for. The risk is that they expect infrastructure that does not exist yet, so probe for comfort with building from zero.
High-performing generalists inside scaling companies. Chiefs of staff, programme managers, and founders' right hands who want ownership rather than proximity. They are used to ambiguity and usually hungry for a mandate of their own.
Ex-founders of small businesses. They have done every job, understand cash, and need no explanation of why processes matter. The risk is autonomy: some struggle to operate inside someone else's company. Reference-check for it directly.
Who not to hire: a big-company operations specialist whose experience is running one slice of a mature machine. The skills look right on paper, but the job at your stage is building machines, not operating them. Equally risky is the brilliant junior who "can grow into it". The role needs someone who has seen functioning operations somewhere, otherwise they are inventing best practice from first principles on your payroll.
In the interview, weight evidence over vision. Ask what they built, what broke, and what they would do in their first 30 days. Strong candidates describe a diagnosis. Weak candidates describe a toolkit.
What This Hire Should Cost (And What It Returns)
An operations manager for a 15 to 30 person startup typically lands between the cost of a mid-level engineer and a senior one, depending on market. The return calculation that matters is founder hours: if the hire recovers ten founder hours a week, the question is what those hours are worth deployed against product, customers, and the next round.
The hires that fail this calculation are the ones scoped as helpers. Coordination work does not compound. Ownership does.
Signals the Hire Is Working
At six months, three things should be observably true. Internal questions route to them, not you, by default. Processes run and improve without your attention. And the operational diagnosis they wrote in month one has become a roadmap they are visibly executing.
If instead they are scheduling your meetings and chasing status updates, the role has collapsed into assistance. That is a scoping failure, and it is recoverable, but only by rewriting the mandate and re-transferring ownership properly.
The Mistakes That Sink This Hire
Hiring before the foundation exists, so they inherit chaos without authority. Hiring a COO title for operations manager work. Skipping the mandate page and "seeing how it evolves". Keeping decision rights while transferring tasks. And treating the first operational mistake they make as a reason to take the function back.
Every one of these is a founder behaviour, not a candidate flaw. The hire succeeds when the founder does the preparation work this post describes, most of which echoes the wider lessons in Operational Mistakes Startups Make in Year One.
One final note on timing. The best moment to make this hire is roughly one quarter after the round closes, once the post-funding operating foundation is in place and before the headcount wave lands. Hire too early and they have nothing structured to own. Hire too late and they spend their first six months excavating chaos that twenty new employees are actively adding to. The quarter of preparation is not a delay. It is what makes the hire work.
Related Reading
- ·Building Operational Foundation After Fundraising: The First 90 Days - the foundation to build before this hire starts
- ·Operational Mistakes Startups Make in Year One - the patterns this hire should help you avoid
- ·Startup Operations Consulting - how we help post-funding founders build the operations function