I hired a fractional RevOps consultant at ten hours a week because a full-time salary felt reckless at our stage. Four months later I'd paid for two rebuilt versions of the same lead-routing rule, a dashboard nobody trusted, and a forecast that was still wrong by 40% every month. The mistake wasn't the fractional model. The mistake was using it to solve a problem that needed someone in the building full-time.
The question I was asking wrong
Most founders frame this as a budget decision: can we afford $150K plus equity for a full-time RevOps hire, or should we start with a $4-6K/month fractional retainer instead. That framing gets the decision backwards. Budget tells you what you can afford, not what your systems actually need. The real question is whether your problem is a discovery problem or a maintenance problem, and those two need completely different kinds of attention.
The 3-question test
I now run this test before every RevOps hiring decision, and I wish someone had handed it to me before I burned four months on the wrong model.
First: is the work discovery or maintenance? Discovery means nobody on your team knows why the numbers don't reconcile, why win rate looks different across three dashboards, or what your actual lead-to-close funnel looks like. That's diagnostic work, and diagnosis needs full context held in one person's head over consecutive days, not four scattered hours a week. Maintenance means you already know the answer and just need someone keeping the system clean: routing rules enforced, fields populated, reports refreshed on schedule. Fractional handles maintenance well. It handles discovery badly, because a consultant who shows up Tuesday and Thursday loses the thread of what changed Wednesday.
Second: is it one broken system or three? A single clear problem, like your lead routing rule assigning deals to the wrong rep, is a contained fix a fractional person can scope, execute, and hand off. Three broken systems that touch each other, like routing, forecasting, and comp all breaking at once because none of them agree on what a "qualified deal" means, is not three separate part-time projects. It's one job, and it needs one person who owns the whole picture and is accountable when the pieces stop lining up again next month.
Third: could you write the full-time job description today, without a consultant's help, and have it be right? If yes, you already understand the role well enough that a fractional person can execute against your spec while you keep evaluating whether the volume justifies converting them. If no, that itself is the signal that you don't yet know what you need, and the fractional engagement's real job for the next 60-90 days is to answer that question, not to fix everything.
What fractional actually buys you
Fractional RevOps is not a cheaper version of a full-time hire. It's a different tool that buys you two specific things: a second opinion from someone who has seen the same failure pattern at ten other companies, and a low-commitment way to find out what a real RevOps job at your company should even contain. What it does not buy you is continuity. A part-time person context-switching across three or four clients will not sit in your Tuesday pipeline review, notice the anomaly nobody else caught, and chase it down before your Thursday board prep. That kind of catch only comes from someone whose full attention is on your numbers.
The cost math nobody shows you
A fractional retainer at 10 hours a week runs roughly $4,000-7,000/month depending on seniority, or $48,000-84,000/year. A full-time RevOps manager runs $110,000-140,000 base plus benefits and equity, call it $150,000-180,000 fully loaded. On paper, fractional looks like a 60-70% discount. It isn't, once you account for the ramp cost you pay twice: once when the fractional person builds context, and again when a full-time hire has to rebuild that same context from scratch six months later because nobody wrote it down. In my case, that rebuild cost more than just hiring full-time from month one would have, in both dollars and in three forecast cycles my board didn't trust.
The trigger that means it's time to convert
The signal to convert from fractional to full-time isn't a revenue milestone, it's a frequency signal: when the same fractional person is fielding urgent Slack messages between their scheduled hours more than once a week, you're already paying for full-time attention without getting full-time accountability. That's the moment to have the conversion conversation, not at some ARR number you picked out of a blog post.
Before you post a job or sign a retainer, run your situation through the three questions above. If you're staring at a diagnosis problem with three interlocking systems and you can't yet write the job description, start fractional but set a 90-day checkpoint to answer the question properly, not to keep the arrangement indefinitely because it's comfortable.