Two people in the same meeting give you two different pipeline numbers. Both have a spreadsheet. Both are right, given how they count. Then somebody says what everyone is thinking: we need a RevOps person.
This is for founders and CROs at early stage to Series C companies who are about to open that role. You have probably read when to hire and how to interview. Most of that advice skips the part that decides whether the hire works. A first RevOps hire does not fix an undefined revenue system. They inherit it, and the definitions they need are decisions only you can make.
What the guides tell you, and what they skip
Landbase, a data vendor, published a first RevOps hire guide in April 2026. Its advice is typical of the genre. Look at 10 to 15 sales reps, or $5 million in ARR, or leadership spending more than ten hours a week on ops work, and suggests fractional help below those lines. Those thresholds are Landbase's advice, not research, and nothing in them is unreasonable. If you are burning ten hours a week reconciling reports, something is broken.
But a smoke alarm is not a plan. Thresholds tell you the pain is high enough. They say nothing about what the new person is handed on day one, and that is where first hires go wrong.
What the hire actually inherits
On day one they get admin access to the CRM and a request: make the numbers match. So they open the stage field and ask what "Proposal" means. Sales says a quote went out. Customer success says legal review has started. Nobody wrote it down. They ask what counts as a qualified lead, and marketing and the account executive answer differently. They ask which number goes to the board. You say the one in the deck, and the deck was assembled by hand.
None of that is a data problem. Each one is a business decision with money attached to it: comp, forecast, board commitments. The hire can build a report on any answer you give. They cannot pick the answer. If they try, they are doing it with less authority than you have, and they are the one who gets blamed when the numbers move.
The cost is already being paid before anyone is hired. Salesforce's State of Sales research, fifth edition, published in December 2022, surveyed 7,775 sales professionals in August and September 2022. It found that reps spend just 28% of their week selling, with most of the rest going to things like deal management and data entry. That is Salesforce's survey, of salespeople rather than founders, and it is four years old, so treat it as direction. Where definitions are missing, the admin load lands on sellers first. A new hire picks that load up at a different desk. It does not disappear.
Six definitions only you can write
Before you open the role, put these on one page. A sentence or two each.
- Qualified. What has to be true before a lead becomes a pipeline opportunity, and who makes that call.
- Stages. A name for every stage and an exit rule for each: what the buyer has said or done before the deal moves on. Evidence from the buyer, not a feeling from the rep.
- Handoffs. For each one (lead to rep, closed won to onboarding, onboarding to renewal): who owns it, what travels with the deal, and how long the receiving side has to act.
- Source. Where a deal's origin is recorded, once, and who is allowed to change it.
- Customer fit fields. The two or three fields that say whether this is the customer you want, required when an opportunity is created.
- The forecast. Which single number is the forecast, who calls it, and when it locks.
If you cannot agree a sentence for one of these, good. You have found a real disagreement in your business, and a dashboard was never going to resolve it. RivoAxis has written about cleaning ghost deals out of a pipeline and about why the loss reason in your CRM is only a hypothesis. Both problems start at this page.
"Isn't that what I'm hiring them for?"
Fair objection, and partly right. You are hiring for time you do not have, and a good operator will document, build and maintain all six. Pedowitz Group, a consultancy, says early stage companies need generalists in this seat, and we agree. This is cross functional work.
But there is a split. The hire writes the definitions down, builds them into the CRM, and polices them. You decide what they say. What counts as qualified changes how your reps get paid. What the forecast is changes what you promise your board. Those are commercial choices, and an operator with six weeks of tenure should not be making them on your behalf.
It does not take long. Write a rough version in one sitting, argue with your sales and customer success leads for an hour, and hand the result over. The hire then edits a real document instead of starting from a blank page and a rumor.
Hire, part time, or wait
Here is the recommendation.
If you can write the six in a sitting and the team mostly agrees, and you are in Landbase's pain zone, hire. The person has a mandate and something to build on.
If you can write them but nobody is keeping them honest, ten hours a week from an experienced fractional operator is probably enough for now. That is our view, not a benchmark. Reassess when the definitions start to change faster than one person can maintain them.
If you cannot agree on them, do not hire yet. A full time hire in that situation is likely to spend a quarter producing the argument you avoided, in the form of a document, and will be judged on numbers nobody signed off. Settle the disagreement first. That is a leadership meeting, not a recruiting process.
The forecast definition is easy to skip, and it is the one the board sees. If your forecast is a gut call with a spreadsheet around it, our piece on deal scoring for forecasting is a place to start.
Write the mandate from the definitions
Pedowitz Group warns that a vague mandate turns the role into a catch all that fails on expectations. That is what happens when the job post lists tools and tasks. Write it from the six instead.
The mandate has four lines:
- Own the six definitions as a living document, with one person who approves changes.
- Make the CRM enforce them, so a deal cannot move forward without meeting the exit rule.
- Produce one weekly number pack from one source.
- Raise disagreements to the founder or CRO rather than settling them quietly.
Add what they do not own: what counts as qualified, how comp works, and who gets hired. Writing the exclusions down protects them as much as you.
Then set the ninety day test. Any two people in the company, asked for pipeline, produce the same number and can say why. Nothing grander than that.
One more check before you post the role. Hand the draft to an account executive and ask them to explain what the person will do all day. If they cannot, neither can the candidates. RivoAxis has laid out how RevOps works as the operating layer of a go to market system, and it only works when the terms underneath it are agreed.
The order matters
The hire is the second step. The definitions come first, they can take a day, and they make the call to hire, or to wait, much easier.
If you want a second pair of eyes on the six, or you suspect your team will not agree on them, that is exactly what a Revenue Diagnosis conversation with RivoAxis is for.
Book a Revenue Diagnosis