TL;DR: about 85% of what a RevOps hire spends their week on is reporting, CRM hygiene and process docs, all of which are automatable today for $4,000-8,000 and $150-400/month, against $110,000 in year one for the hire. The other 15% is the part you cannot automate, and if that 15% is your real bottleneck, hire. Most founders posting this job have not worked out which it is.
I am Ivan, I run 2pizza.team. Every week I see the same posting on LinkedIn: Sales Operations or RevOps, $65-85k, must have three years of CRM experience, at a company somewhere between twenty and eighty people.
I know what is happening inside that company, because it is always the same thing. The founder is drowning in manual reporting. The CRM is a mess. Leads fall through because follow-up is manual. Sales data lives in five spreadsheets, three of which disagree. Hiring someone to own it feels obviously correct.
What actually happens after the hire
The search takes two to three months. The person joins, spends the first month learning the business, and produces a set of dashboards and a process document. Both are good. Six months later the founder is still pulling numbers by hand for the board deck, because the dashboards do not quite answer the question that gets asked.
Nothing went wrong. The hire is competent, the dashboards are fine. The problem is structural: you added one person to a volume problem that keeps growing, and one person does not scale with volume. The bottleneck moves about six feet and stays the same size.
Where the week actually goes
I asked several founders who had made this hire to break down where the time went. The shape was consistent enough to be worth repeating.
Around 40%: building and maintaining reports and dashboards
Around 25%: CRM cleanup, deduplication, data entry
Around 20%: writing process documentation and training people on it
Around 15%: the actual strategic work, meaning pipeline analysis and decisions
The first three categories are 85% of the role, and they are automatable now, with tools that exist, at a fraction of what the person costs. Not eventually. Not in principle. The fourth category is not automatable at all, and it is the reason the job exists in the founder's head.
That is the whole decision in one line: you are considering paying a full salary to get 15% of a role, and absorbing the other 85% as overhead because it came in the same package.
What automating the 85% actually looks like
Concretely, because this is where most articles wave their hands.
Reporting
A pipeline summary generated on a schedule from CRM data and delivered to Slack or email. Nobody pulls it. It is accurate because it runs against the source rather than against a copy of a copy, and it is identical every week, which makes it comparable week to week - something hand-built reports almost never are.
CRM hygiene
New records enriched on arrival with company size, industry and contact data. Duplicate detection at import rather than at quarterly cleanup. Deal stages moved by observed activity rather than by someone remembering to update them. This is the category that quietly decides whether any of your reporting means anything.
Follow-up
A deal goes quiet for seven days and a task appears. A form gets submitted and a relevant reply goes out in minutes rather than at the end of the day, generated against criteria you set and reviewed by rules you wrote. The gain here is not the writing; it is that nothing is dropped when someone is on holiday.
Process documentation
The partially automatable one, and worth being honest about. A system can keep a record of how the process actually runs, which is more accurate than a document describing how it was supposed to. It cannot persuade a sales team to follow it. That part is human and it stays human.
The arithmetic, both sides
The general version of this trade, across any role rather than RevOps specifically, is in automation versus hiring. A $70,000 RevOps salary lands at roughly $90,000-95,000 all-in once taxes and benefits are counted. Add $15,000-20,000 in year one for recruitment and the ramp period you pay for and do not get output from. Call it $110,000 before the person is fully productive, recurring annually and rising.
Building the automations above runs $4,000-8,000 depending on your CRM and how clean the data is, with $150-400/month to operate. Payback under two months on the time saved alone. In year two the comparison is not close, because one line recurs in full and the other drops to the running cost.
The system also does not resign eighteen months in, taking the undocumented half of how everything works with it. That is not a joke about headcount; it is the single most expensive thing that happens to small-company operations, and it happens on a schedule.
When you should hire anyway
Four cases, and they are real. I have told people to hire in all four.
The bottleneck is stakeholder management. Getting sales, marketing and finance to agree on what a qualified lead is has never been a tooling problem.
Your process genuinely changes every quarter. Automation encodes a process; encoding one that is about to change is paying twice.
Nobody can state how the work is done today. Then the first job is extraction from someone's head, and a person does that better than a spec.
You need someone accountable in the room. A system has no opinion in a pipeline review and cannot be asked why the forecast slipped.
If one of those is your situation, hire, and hire well. Just do not also expect the hire to fix reporting, because they will spend 40% of their week on it forever.
The failure mode on my side of the argument
Automating instead of hiring goes wrong in one specific way, and I would rather you hear it from me. You automate the reporting and the CRM hygiene, the founder's Monday gets shorter, and nobody ever does the 15% strategic work, because it was never anyone's job and now the pain that would have forced the hire is gone.
Six months later the numbers arrive beautifully every Monday and nobody is analysing them. That is a worse outcome than the messy version, because it feels solved. If you go the automation route, put the pipeline analysis on someone's actual calendar, by name, or you have bought silence rather than insight.
The order I would do it in
Automate the 85% first, live with it for a quarter, then look at what is left. What remains is the real job description, and it is a much better one: someone who does pipeline analysis and cross-functional work on top of a system that already runs, rather than someone who spends their first year rebuilding reports by hand.
You will also hire better, because the role you are advertising is now interesting. The best operations people do not want to own a spreadsheet ritual, and the posting you were about to publish is, read plainly, a spreadsheet ritual with a salary attached.
Have a RevOps posting open right now? The audit at 2pizza.team/audit takes two minutes and no call, and it will tell you which side of the 85/15 split your actual bottleneck sits on. If it is the 15, it will say hire.
Originally published at 2pizza.team. We build AI and automation systems for small teams - fixed price, two to six weeks. See the work.
Top comments (0)