The Founder's Guide to Your First Head of Ops Hire
By Adriana Roche
You've hit that inflection point. Your startup is growing, and you're drowning in operational complexity. Time to hire your first head of ops. But what does that actually mean? Let's break it down.
The Wake-Up Call
Most founders realize they need an ops hire when:
• You're spending more time managing internal processes than talking to customers or helping build product
• Your team is growing, but your systems aren't scaling
• You've had a few "oh 💩” moments where things fell through the cracks
• Your calendar looks like a game of Tetris gone wrong
The instinct is to hire someone to "handle operations." Stop right there. That's like saying you want to hire someone to "handle code." We need to get specific.
First, Get Clear on Your Pain
Before you write that job description, answer these questions:
What's actually broken? Not "operations" - get specific. Is it:
Your sales process is a mess, and deals are getting stuck
You're drowning in administrative tasks
Your team communication is chaos
Your hiring process is bottlenecked
What level of autonomy do you need? Are you looking for:
Someone to execute on processes you design
A partner who can design and implement systems
A future leader who can run the company
This clarity will determine whether you need an Operations Manager, Head of Ops, or even a future COO.
The Three Flavors of Ops Hires
1. The Process Builder (Operations Manager)
Perfect for: Early-stage startups needing someone to create order from chaos
They love: Building systems, documenting processes, making things repeatable
Warning sign: If they talk more about tools than outcomes
Key interview question: "Tell me about a process you built that scaled with the company". How did you make sure it was adopted?
2. The Revenue Driver (Head of RevOps)
Perfect for: Companies with growing sales teams and pipeline complexity
They love: Sales efficiency, pipeline analytics, removing friction from deals
Warning sign: If they can't explain how ops drives revenue
Key interview question: "How would you measure the impact of operational improvements on revenue?"
3. The Mini-CEO (Head of Ops/Future COO)
Perfect for: Founders who need a true second-in-command
They love: Cross-functional leadership, strategic thinking, building teams
Warning sign: If they can't point to examples of leading through influence
Key interview question: "Tell me about a time you drove a major change without formal authority"
The Interview Process That Actually Works
The Pain Point Probe
The Real-World Test
The Scale Test
Setting Them Up For Success
The first 90 days are critical. Here's your playbook:
Week 1-2:
Deep dive into current processes
Meet key stakeholders
Identify quick wins
Week 3-4:
Start implementing quick wins
Draft 90-day plan
Begin documenting tribal knowledge
Month 2-3:
Execute on major initiatives
Build relationships across teams
Establish metrics for success
Red Flags to Watch For
They talk about best practices without context
They're more interested in their title than the problems
They can't explain how they'd measure success
They haven't asked about your growth plans
The Ultimate Test
After three months, ask yourself:
Are you spending more time on high-leverage activities?
Are fewer things falling through the cracks?
Does the team know how to get things done?
Are you sleeping better at night?
If yes, congratulations - you've found your ops leader. If no, revisit this guide and figure out where things went wrong.
Remember: A great ops hire doesn't just maintain order - they create leverage. They should make everyone else better at their jobs, including you.
Good luck, and may your systems scale.
