Revenue operations is the function that owns the systems, data, and process behind marketing, sales, and customer success: the CRM, routing, reporting, forecasting, and the handoffs between teams. Its job is to make the revenue team faster and its numbers trustworthy.

When should a startup hire its first RevOps person?

Usually once there are three or more people selling, the CRM data is too unreliable to forecast from, and founders or sales leaders are spending meaningful time on reports and tool administration. For many companies that lands between a Series A and a Series B.

Should my first RevOps hire be a generalist or a specialist?

A generalist who can both build and analyse. The first person will administer the CRM, design the pipeline stages, build reports, and connect tools. Specialists in sales operations, marketing operations, or deal desk come later, once there is enough volume to split the work.

What is the difference between RevOps and a GTM engineer?

They overlap. RevOps traditionally owns process, reporting, and CRM hygiene. A GTM engineer builds data pipelines and automation that find and engage accounts, and is often more technical. At a small company one strong person can cover both, and the title matters less than which problem you need solved first.

When to Make Your First RevOps Hire (and What That Person Should Do First)

Make your first RevOps hire when three or more people are selling, CRM data is too unreliable to forecast from, and founders or sales leaders are losing real time to reporting and tool administration. Hire a builder-generalist who can own the CRM, pipeline definitions, and reporting, not a specialist, because the first job is creating one trusted version of the numbers.

Hired too early, a RevOps person optimises a process that does not exist yet. Hired too late, they spend a year cleaning up data while the board asks why the forecast keeps moving. The right moment is when the cost of bad data is visible every week.

Signals it is time

The forecast is a conversation, not a report. Every pipeline review starts with arguing about which deals are real.
Each rep runs the CRM differently. Stages mean different things to different people, so conversion rates are meaningless.
A leader is the tool administrator. Your head of sales or a founder spends hours a week on fields, integrations, and exports.
Marketing and sales disagree about where pipeline came from. Attribution is argued rather than measured.
You are about to hire several reps. Onboarding them into a messy system multiplies the mess.

One or two of these is normal at seed. Three or more at once, especially just before a hiring push, is the signal.

Signals it is too early

The founder still closes most deals personally.
There is no repeatable sales motion to systematise yet.
The CRM has fewer deals than one person can hold in their head.

At this stage, a founder spending a few hours setting clear pipeline stages, or a short contract with a CRM consultant, does the job.

What the first RevOps hire should own in the first 90 days

Window	Focus	Outcome
Days 1 to 30	Definitions and audit	Agreed pipeline stages and entry criteria, a list of what is broken in the data and tools
Days 31 to 60	Clean up and connect	Trusted CRM data, routing that works, marketing and sales systems talking to each other
Days 61 to 90	Reporting and forecast	One pipeline and forecast view that leadership and the board both use

If after 90 days leadership still exports to spreadsheets to answer basic questions, either the scope was wrong or the hire was.

RevOps, sales ops, or GTM engineer?

Role	Primary job	Hire first when
RevOps generalist	CRM, process, reporting, forecasting across the funnel	The numbers cannot be trusted and several teams touch revenue
Sales operations	Territories, quotas, compensation, sales tooling	A sales team large enough to need territory and quota design
GTM engineer	Data pipelines and automation that find and engage accounts	Pipeline generation, not pipeline management, is the constraint

Many seed to Series B companies need a little of all three and can afford one person. Decide which problem is costing you most this quarter and hire for that. A RevOps generalist with a build habit and a GTM engineer who likes reporting can look like the same candidate; test for the work you need done first.

What to test for in interviews

Diagnosis. Give them a sanitised export of your pipeline and ask what is wrong with it.
Systems thinking. Ask how they would define stages and entry criteria for your sales motion.
Hands-on skill. Have them build or fix something real in your CRM or a sandbox.
Influence. Ask how they got a sales team to follow a process they did not want to follow.

Common questions

What is RevOps?: Revenue operations is the function that owns the systems, data, and process behind marketing, sales, and customer success: the CRM, routing, reporting, forecasting, and the handoffs between teams. Its job is to make the revenue team faster and its numbers trustworthy.
When should a startup hire its first RevOps person?: Usually once there are three or more people selling, the CRM data is too unreliable to forecast from, and founders or sales leaders are spending meaningful time on reports and tool administration. For many companies that lands between a Series A and a Series B.
Should my first RevOps hire be a generalist or a specialist?: A generalist who can both build and analyse. The first person will administer the CRM, design the pipeline stages, build reports, and connect tools. Specialists in sales operations, marketing operations, or deal desk come later, once there is enough volume to split the work.
What is the difference between RevOps and a GTM engineer?: They overlap. RevOps traditionally owns process, reporting, and CRM hygiene. A GTM engineer builds data pipelines and automation that find and engage accounts, and is often more technical. At a small company one strong person can cover both, and the title matters less than which problem you need solved first.