I put off hiring a RevOps person for almost a year longer than I should have, because I was waiting for a number. Some founder had told me "wait until $3M ARR" and I held onto that like it was gospel. Meanwhile our VP of Sales was building his forecast calls off a gut feeling, our lead routing was three Slack messages and a prayer, and nobody on the leadership team actually trusted the pipeline numbers in our reviews.
The ARR number was never the signal. The signal was sitting in every one of those forecast calls, and I ignored it for months because I was looking at the wrong metric.
The signal that actually matters
Revenue operations doesn't become necessary at a revenue milestone. It becomes necessary when the cost of your operational chaos starts exceeding the cost of fixing it. For most B2B SaaS companies that shows up somewhere around 10-15 reps and $5M+ ARR, but the number is a lagging indicator, not a trigger. Before that point, a fractional RevOps consultant a few hours a week usually covers it. After that point, the chaos compounds faster than a part-time person can clean it up.
Here's the test I use now instead of an ARR threshold: if your VP of Sales is building a forecast from a gut feeling instead of pipeline data your leadership team actually trusts, you don't have a sales problem, you have a data problem. And a data problem doesn't get better because your ARR crossed some line on a spreadsheet.
Why hiring junior is the expensive mistake
The most common mistake I see other founders make once they finally decide to hire is bringing in someone too junior and expecting them to build the function from scratch. A RevOps analyst two years out of a sales development role can execute a playbook. They cannot design one. Your first RevOps hire needs to be at Manager or Senior Manager level, with 3-5 years minimum of having actually built systems before, ideally at a company one stage ahead of yours. You are not hiring someone to run reports. You are hiring someone to decide what the reports should measure in the first place.
This is the same mistake founders make with an early marketing hire: bringing in a generalist to do a job that actually requires someone who has done it before, at your exact stage, and knows which fires to ignore.
The 90-day mandate to set before you hire, not after
Write the first 90 days down before you post the job. It should cover exactly three things: CRM hygiene and data quality, lead routing and assignment automation, and pipeline reporting that leadership actually trusts enough to make decisions from. Nothing else. Scoring models, territory design, tech stack consolidation — all of that comes after the foundation holds. A candidate who wants to jump straight to the interesting strategic work before your data is clean is telling you they'll build on sand.
Four questions that predict whether this hire works out
I now run every RevOps candidate through the same four questions, in this order, and the order matters because each one is harder to fake than the last.
First: "Tell me about your biggest RevOps failure and what you learned from it." I'm not looking for a rehearsed lesson. I'm looking for ownership of a specific, real mistake, and a change in behavior that followed it. Anyone who claims every project they've touched went smoothly has either not done enough of them or is not going to be honest with you when yours goes sideways.
Second, I hand them a reporting problem — something like "our win rate looks different in three different dashboards and nobody agrees which one is right." A strong candidate asks who uses each dashboard and what decision it drives before they touch the data. A weak candidate starts talking about which tool they'd use to fix it. The tool is never the interesting part.
Third: "Walk me through a time your forecast was wrong, and how you found out before your CEO did." This tells you whether they build monitoring into their own work or wait to get caught.
Fourth, after I've walked them through our actual lead-to-close process for ten minutes, I ask them to sketch it back to me from memory, including where they'd expect it to break at twice our current volume. This is the question that separates people who were listening from people who were waiting for their turn to talk, and it's the one candidates can't prepare for in advance.
The red flag that matters more than any resume gap
Certifications are not a red flag by themselves, but a resume that leads with certifications and has no scar tissue underneath it usually is. The same goes for defensiveness — if you push gently on a decision they made and they get prickly instead of curious, that's how they'll respond the first time your VP of Sales pushes back on their reporting six months into the job. You want someone who treats a hard question as data, not as an attack.
If you're at 10-15 reps, north of $5M ARR, and your last three forecast calls have been built on vibes instead of numbers your team actually trusts, stop debating the ARR threshold. Write the 90-day mandate, run these four questions on your next three candidates, and hire the one with the scars, not the one with the cleanest resume.