Scaling
When to Hire Your First Ops Person
The signals that tell you it’s time, the profile that actually works at your stage, and the mistakes that cost companies a year of progress.
The signals that tell you it’s time, the profile that actually works at your stage, and the mistakes that cost companies a year of progress.
Every founder I work with waits too long to make this hire. Not because they don’t feel the pain—they feel it every day. They wait because they can’t articulate what the role actually is. “Operations” is vague. The job descriptions they find online are written for enterprise companies with 500 employees. And the last thing a founder at $7M wants is to spend three months hiring someone who doesn’t fit.
So they keep doing it themselves. They stay up until midnight cleaning CRM data. They spend Tuesday mornings chasing down why a lead from last week never got a follow-up. They onboard new hires by sitting next to them for a week because nothing is documented. This is a part of the broader challenge of scaling operations without breaking what works—and the first ops hire is usually where that journey starts.
Here’s how to know when it’s time, what to actually look for, and how to avoid the mistakes that cost companies a full year of progress.
There’s no single trigger. It’s a pattern. When three or more of these are true at the same time, you’re past the threshold:
If you recognize three or more of these, you don’t need a “digital transformation.” You need a person who can build and run systems.
At $5M–$15M, you need a systems thinker, not a specialist. You need someone who can build process and use tools. Not a VP—an operator.
The ideal profile at this stage is someone who has built ops at a similar-stage company. They can admin a CRM, write an SOP that doesn’t rot, set up an automation in Zapier or Make, and manage a vendor—all in the same week. They’re T-shaped: broad capability across operations disciplines, with depth in systems thinking.
Your first ops hire should be able to do 80% of everything at a B-minus level and 20% of things at an A level. That 20% should be systems design — the ability to look at a broken process, figure out why it breaks, and build something that doesn’t. The other 80% is execution: CRM configuration, report building, vendor calls, documentation.
This person does not need to be a data scientist. They do not need to write SQL. They need to be able to set up a dashboard in your CRM, build a report that answers a business question, and know when the data looks wrong. They need judgment more than technical depth.
At the mid-market stage, your first ops hire needs to be a generalist operator who can build systems and run them solo. Hire for judgment and range, not for depth in a single domain.
I’ve seen the same four mistakes cost companies six to nine months each. Every one of them comes from pattern-matching to the wrong reference point.
Mistake 1: Hiring too senior. You post for a VP of Operations. You get someone who built a 12-person ops team at a Series C company. They arrive and expect an existing infrastructure—a data warehouse, a BI tool, a RevOps team to delegate to. They can’t execute solo. They spend their first quarter writing strategy decks instead of fixing the CRM. By month four, both sides know it’s not working. These are the same stage-specific walls that trip up the rest of your org chart.
Mistake 2: Hiring too junior. You hire an operations coordinator fresh out of college. They’re eager, they work hard, and they do exactly what you tell them. But they can’t prioritize. They can’t design systems. They execute tasks but don’t solve problems. You end up managing them so closely that you’re spending more time directing their work than you saved by hiring them.
Mistake 3: Hiring a specialist when you need a generalist. You hire an analytics person who builds beautiful dashboards but can’t touch the CRM. Or a CRM admin who can configure fields all day but can’t think strategically about pipeline stages. At this stage you need one person who can do both, not two people who each do half.
Mistake 4: Copying enterprise org charts. You read a blog post about RevOps and decide you need a Revenue Operations Manager, a Marketing Operations Specialist, and a Business Operations Analyst. You are an $8M company. You need one person, not three titles.
Describe a week in your company where three things break at once — a CRM automation stops working, a new rep needs onboarding, and a board report is due Friday. If your candidate can’t handle all three in the same week, they’re the wrong profile for this stage.
Forget the generic templates. At $5M–$15M, the title should be Operations Manager—not VP, not Director, not “Head of.” Those titles attract the wrong candidates and set the wrong expectations.
The responsibilities section should span five areas: CRM administration (owning the system, not just using it), reporting and analytics (building dashboards, answering data questions), process design (documenting and improving workflows), automation (setting up and maintaining tools like Zapier, Make, or native CRM automations), and vendor management (owning relationships with the 5–15 tools in your stack).
Must-haves: 3–5 years of operations experience at a company under 100 employees. Hands-on CRM administration experience (HubSpot, Salesforce, or equivalent). Demonstrated ability to build a process from scratch, not just optimize an existing one. Comfort working independently without a team to delegate to.
Nice-to-haves: Experience with your specific CRM platform. Background in your industry. Familiarity with automation tools. Basic data analysis skills (pivot tables, dashboards, data hygiene). Experience managing external vendors or contractors.
Notice what’s not on the must-have list: an MBA, enterprise experience, people management experience, or deep technical skills. Those are liabilities at this stage, not assets.
This isn’t an either-or decision. It’s a sequencing decision.
Fractional makes more sense when:
Full-time makes more sense when:
The highest-leverage move is the hybrid: a fractional operator builds the systems and playbooks, then a full-time hire runs them. Fractional builds, full-time runs. This way you get senior thinking during the design phase and cost-efficient execution during the run phase.
The hybrid model works because building and running are different skills at different price points. The person who can audit your entire stack, design a new lead routing system, and document it all into repeatable SOPs is a different cost profile than the person who runs that system day to day. Paying the build rate for the run phase wastes money. Paying the run rate for the build phase wastes time.
Most ops hires fail not because they’re the wrong person, but because they start wrong. They walk in on day one and start “fixing” things. They reconfigure the CRM before they understand why it was set up that way. They change a process that looks broken but actually has a reason behind it. By week three, they’ve created new problems without solving the old ones.
The first 90 days should follow a strict sequence:
Days 1–30: Audit. Map every tool in the stack. Document every process—even the informal ones. Identify every gap and every workaround. Talk to every person who touches operations. Don’t change anything. Just learn.
Days 31–60: Build. Pick the three highest-impact problems from the audit. Not the easiest—the highest-impact. Design solutions. Implement them. This is where you fix the lead routing, set up the missing automations, or build the dashboard that answers the question everyone keeps asking.
Days 61–90: Run. Operate the new systems. Measure whether they’re working. Iterate on what isn’t. Start building the documentation that will make these systems survivable without you. This phase proves the systems work in production, not just in theory.
Founders will push their new ops hire to “just fix the CRM” in week one. Don’t. Every premature fix creates a downstream problem. The 30-day audit isn’t slow — it’s the fastest path to changes that actually stick.
The 90-day structure also gives you a built-in evaluation framework. If by day 30 the new hire can’t articulate your top five operational problems clearly, that’s a signal. If by day 60 they haven’t shipped a single improvement, that’s a signal. If by day 90 the improvements they shipped aren’t measurably working, that’s a signal. You don’t need to wait six months to know if the hire is working.
Your first ops hire isn’t a luxury. It’s the difference between a founder who scales and a founder who burns out running the same broken systems forever. Get the profile right, get the first 90 days right, and you buy back the 15+ hours a week that should be going to the work only you can do.
30-minute discovery call. We’ll map your stack and show you where the margin is hiding.
Schedule Call