Revenue operations usually starts as nobody's job. A sales leader builds the first CRM pipeline, a marketer sets up the email tool, and the founder pulls the board numbers into a spreadsheet. That works for a while. Then the cracks show: reports disagree, the CRM fills with duplicates, lead routing breaks, and senior people spend hours each week on admin. At that point, the question is whether to hire a dedicated RevOps person, who, and when. This article covers the signs you need one, the profile to hire first, how hiring compares with a fractional consultant, what the first 90 days should deliver, and a job description you can adapt.
Signs you need RevOps
Look for these signals. Sales, marketing and finance report different numbers for the same metric. Reps or managers spend hours a week on CRM administration, data clean-up or building reports. Lead routing or follow-up fails often enough that leads are lost. Adding a tool or changing a process requires the founder or sales leader to do the configuration. Board reporting takes days of manual work each quarter. The CRM has grown messy enough that people work around it. You are planning to add reps, a new team such as customer success, or a new market, and the current setup will not scale. If three or more apply, a dedicated owner for systems, data and process is likely to pay for itself in recovered selling time and better decisions.
Generalist first, not strategist
The first RevOps hire should usually be a hands-on generalist who can administer the CRM, build reports and dashboards, manage integrations and automation, clean data and document processes. Strategy and process design matter, but in a small company they come from the leadership team, with RevOps translating them into working systems. A senior strategist without hands-on skills tends to produce plans that wait for someone else to build them. Look for someone who has administered your CRM or a similar one, has built reporting that leaders used, understands the sales and marketing funnel, and communicates clearly with non-technical colleagues.
Which profile fits your situation
Profiles vary by background. Match the first hire to your biggest gap.
| Profile | Strengths | Best when | Watch out for |
|---|---|---|---|
| CRM administrator generalist | Configuration, automation, data hygiene | CRM is messy and processes are manual | May need support on analysis |
| Sales operations background | Pipeline, forecasting, territories, compensation | Sales team growing, forecast unreliable | May underweight marketing data |
| Marketing operations background | Attribution, lead management, automation | Lead flow and attribution are the main pain | May underweight sales process |
| Analyst | Reporting, modelling, data tools | Data is clean but insight is lacking | May lack systems administration skills |
Hire or fractional?
A fractional RevOps consultant can be the right first step. It suits companies that need a senior design of the system, such as stage definitions, data model, routing and reporting, before they need daily administration; companies unsure what profile to hire; and those whose volume of work is not yet full-time. A full-time hire suits companies with enough ongoing administration, requests and reporting to fill the week, and where continuity matters. A common sequence is a fractional consultant to design and build the foundation, then a full-time generalist to run it, with the consultant helping to hire and hand over.
Where RevOps should report
RevOps works across sales, marketing and customer success, so reporting into one of them can bias priorities. In small companies, the first RevOps hire often reports to the CEO, the COO or the most senior revenue leader. Reporting to the head of sales is common and works if that leader takes marketing and customer success requests seriously. Whatever the line, set up a simple request process and a monthly prioritisation meeting with all revenue leaders, so the role is not consumed by whoever asks loudest.
What the first 90 days should deliver
In the first 30 days: an audit of the CRM, tools, data quality and reporting; interviews with sales, marketing, customer success and finance; and a prioritised backlog. By 60 days: core fixes in place, such as stage definitions with required fields, deduplication rules, lead routing and a single agreed dashboard for pipeline and conversion. By 90 days: documentation of the data model, processes and integrations; a request process; and a plan for the next quarter. Judge the hire on whether leaders now trust the numbers and spend less time on admin, not on the number of tickets closed.
Job description template
Title: Revenue Operations Manager (or Specialist). Purpose: own the systems, data and processes that support sales, marketing and customer success, so that the revenue team works efficiently and leadership can trust its numbers. Responsibilities: administer and configure the CRM and connected tools; maintain data quality, definitions and the data dictionary; build and maintain dashboards and reports for revenue leaders; manage lead routing, assignment and handoff automation; manage integrations between CRM, marketing automation, billing and support tools; document processes and train users; run the tool inventory and support renewal decisions; support forecasting and planning with data. Requirements: hands-on administration experience with your CRM or a comparable one; strong reporting skills; understanding of B2B funnels and sales processes; clear communication with non-technical teams; attention to detail. Useful extras: experience with your billing system, middleware or a BI tool, and with the markets you sell into.
Interview questions
Ask candidates to walk through a CRM they cleaned up: what was wrong, how they decided priorities and how they got users to adopt the changes. Ask how they would resolve a disagreement between sales and marketing over lead quality numbers. Give a short practical task, such as designing stage exit criteria for your pipeline or building a simple report from sample data. Ask how they document their work so others can maintain it. Good candidates focus on the business problem behind each request and talk about adoption as much as configuration.
Setting the new hire up to succeed
A first RevOps hire often struggles for reasons outside their control. Give them administrator access to the CRM and connected tools from the first day, and introduce them to every revenue leader as the owner of systems and data, so that requests come through them rather than around them. Agree in writing which decisions they can make alone, such as field changes, routing rules and report design, and which need sign-off, such as changes to stage definitions or compensation-related data. Protect time in their first month for the audit, rather than filling it with urgent requests. And make sure someone senior champions the changes they propose, because RevOps work often asks teams to change habits, and a new hire without visible backing will find adoption slow. A monthly prioritisation meeting with all revenue leaders gives them that backing and a fair way to say no.
Growing the function after the first hire
Once the first hire has stabilised the systems, the function grows with the business. Common next roles are a marketing operations specialist when lead management and attribution become complex, a sales operations analyst when forecasting, territories and compensation need dedicated attention, and a data or analytics role when reporting needs to combine many systems. Customer success operations often follows once there is a dedicated customer success team. At that point the first hire may become a RevOps lead with a small team, or the company may hire a more senior head of RevOps above them. Plan the sequence against the problems the business is facing, not a template org chart.
FAQ
When reps, managers or founders spend meaningful time on CRM admin, reporting disputes and tool fixes, typically once there are several reps and more than one go-to-market team.
Usually a hands-on generalist with real CRM administration and reporting experience. A strategist without hands-on skills tends to produce plans that wait for someone else to build them.
Often the CEO, COO or the most senior revenue leader. Use a shared request process and monthly prioritisation so all revenue teams are served fairly.
Yes, especially to design the foundation before the workload is full-time, or to help define and hire the first full-time role.
An audit and backlog, core fixes such as stage definitions, deduplication and routing, an agreed dashboard, and documentation of the data model and processes.
Revenue Operations Manager or Specialist is common. Choose the title that matches the seniority you are hiring, and avoid Head of RevOps unless the person will set strategy and build a team.