A RevOps lead gets asked for best practices and hands over a list that reads like a maturity model: align the teams, build a single source of truth, standardize the process, pick the right tools, measure everything. None of it is wrong. None of it helps on the Tuesday when the CRO asks whether to add a data vendor, the sales director wants territories redrawn, and a frontline manager says the reps have eight hundred accounts each and no idea which ones to call.
The gap has a cause. Most RevOps guidance is written about the system: data, process, tooling, reporting. The person the system exists to serve is a rep holding a list, and the question that rep answers dozens of times a day (why this account, why now) sits outside every one of those categories. A list tool answers who exists. A sequencer answers how many touches went out. The CRM records what happened after someone decided to act. None of them records the reason to act, so none of the dashboards can see when it is missing.
So instead of another maturity model, this article takes the five decisions a RevOps lead actually makes in a year and gives a position on each that you can defend in the room. They share one idea: your list is not the problem, the missing reason is. Every decision below gets easier once your system can say, for any account, what changed, where you saw it, and when.
What the standard advice leaves out
Read the top guides side by side and they agree. Salesforce's list of six RevOps best practices runs from assessing where you are today, through shared revenue goals, standardized processes, metrics and a single source of truth, to choosing the right technology. Cognism's version has eight, covering alignment, data quality, process, training, tracking, forecasting, customer success and customer focus. Forrester frames the function as unifying data, processes, technology and talent across the customer lifecycle in its history of revenue operations.
These are the right categories. What they skip is the unit of work. Territory planning appears in those lists as a benefit of good data, and the question of which account a rep should work this week is left to the rep. That is where the system leaks. The rep fills the gap with habit: the accounts they know, the list in alphabetical order, or whoever opened an email yesterday.
The data says the gap is expensive. Validity surveyed 602 CRM users and administrators for its State of CRM Data Management in 2025 report. 76% said less than half of their organization's CRM data is accurate and complete. Workers spent an average of 13 hours a week hunting for basic information in the CRM. And 37% said staff regularly fabricate data to tell leaders what they want to hear. A system that people have to hunt through and sometimes pad is a system that does not hold the reason to act, because nobody could find one to write down.
Timing makes it worse. 6sense surveyed 934 B2B buyers for its research on when buyers reach out to sales and found buyers initiated first contact 83% of the time, after completing about 70% of their buying journey. If the buyer usually moves first, the seller's only way to be early is to know something changed before the buyer calls. That is a research job, and in most revenue organizations nobody owns it.
Decision one: what the CRM must hold
Every year someone proposes a data cleanup. The standard advice says build a single source of truth. The defensible position is narrower: decide which fields a decision depends on, make those trustworthy, and stop there.
A CRM with two hundred fields at 40% completeness is worse than one with twenty fields at 95%, because nobody can tell which 40% to believe. Start from the decisions, not the schema. Forecasting needs stage, amount, close date and the evidence behind the stage. Routing needs segment, owner and territory. Prioritization needs something most CRMs have no field for at all: the most recent reason to contact the account, where it came from, and when it happened.
That last one is worth adding deliberately. Three fields on the account record:
- What changed. A new leader in the buying function, a funding round, a hiring spike in the team your product serves, an expansion into a new region, a stack change.
- Where you saw it. The link. A press release, a job post, a filing, a LinkedIn post. No link, no field.
- When it happened. The date of the event, not the date someone logged it. A reason from last quarter is a weak reason.
These three fields are the reason test in data form. A name is worth calling when a rep can answer all three. An account with the fields empty has not been researched yet, and your reports can now show that as a number instead of a feeling. If you are deciding what to buy to fill the rest of the record, CRM data enrichment covers which firmographic fields are worth paying for and which go stale.
Decision two: how pipeline stages are defined
Stage definitions get rewritten roughly once a year, usually after a forecast miss. The standard advice is to standardize the process. The defensible position: every stage exit criterion is a fact about the buyer that a second person could verify, not an activity the seller completed.
"Discovery call held" is an activity. "Buyer confirmed the problem, named who owns the budget, and gave a date the current contract ends" is a set of facts. The first moves deals forward on effort, which is how a pipeline ends up large and soft. The second moves them forward on evidence, which is what a forecast needs.
The same logic extends one step earlier than most stage models start. Before an opportunity exists, there is a stage most CRMs never name: the account has a reason to be contacted, or it does not. Treat that as stage zero. An account enters it when the three reason fields are filled with something checkable. It leaves when a rep acts on the reason or the reason goes stale. Now you can measure how much of the book is sitting at stage zero, which tells you whether the constraint is research or execution. Stages of the sales pipeline goes through exit criteria stage by stage if you are rebuilding the whole model.
Decision three: how many accounts each rep carries
Territory and coverage decisions usually start from the top down: total addressable accounts divided by headcount. That produces the eight-hundred-account book. The defensible position: cap the working set at the number of accounts a rep can research to the reason test in a month, and park the rest.
Work the arithmetic with your own numbers. If a good manual research pass takes fifteen minutes an account, and a rep can protect five hours a week for it, that is twenty accounts a week, around eighty a month. A book of eight hundred means each account gets a real look roughly once every ten months. Everything between those looks is worked on habit.
| Coverage model | What reps do with it | What it costs |
|---|---|---|
| Large book, no research budget | Work the familiar names, sequence the rest | Low reply rates attributed to messaging, not to targeting |
| Large book, research as a side task | Research the first few dozen, then stop | Accounts at the bottom of the list never get looked at |
| Working set sized to research capacity | Every active account has a reason on file | Parked accounts need a trigger to come back in |
The third row needs one more piece: a way for parked accounts to earn their way back. That is a watch list, re-checked for new reasons on a schedule, with an account promoted into the working set when something changes. Sales territory planning and sales capacity planning both cover the headcount side of this. The research side is the part those models rarely price in.
Decision four: how leads and accounts are scored
Scoring models get retuned every year, usually by adding signals. The defensible position: fit tells you who could buy, recency tells you who might buy now, and a score that blends them into one number hides which one is doing the work.
A typical model adds points for industry, headcount and title, then adds more for email opens and site visits. The result is a number that goes up when a well-fitting company exists and when someone at a poorly fitting one clicks a link. Reps learn quickly that the number does not mean much, and go back to habit.
Keep the two apart. Fit is slow-moving and belongs in the definition of the working set. Recency is fast-moving and belongs in the order within it. An account that fits and has a dated, sourced reason goes to the top. An account that fits and has no reason stays in the working set, below the line. An account with a reason and poor fit gets a look, not a sequence. Forrester's revenue operations history cites its Q1 2023 Global B2B Intent Data Survey: over 85% of companies using intent data achieved business benefits. Intent data is one source of recency, not the only one, and it tells you someone is reading about a topic without telling you what changed at the company. Lead scoring best practices goes deeper on weighting, and trigger events in sales lists the events that tend to make a reason worth acting on.
Decision five: what to add to the stack, and what to cut
The tooling decision arrives as a vendor pitch or a rep complaint. The standard advice is to use the right technology. The defensible position: every tool in the stack has to answer a question no other tool answers, and the question has to be one a rep asks every day.
Write the questions down and map the stack against them:
- Who exists? The list and contact data vendor.
- What happened with this account? The CRM.
- How many touches went out, and what came back? The sequencer.
- What did the call sound like? Conversation intelligence.
- Why this account, why now, and what should I say? Usually nothing. The rep, in a browser tab, when there is time.
Two tools that answer the same question are a candidate for a cut. A question with no tool is where the next budget line should go, whether that is headcount, a research process or software. For that last question, PitchSmart is one option: it researches every lead on your list against what you sell and returns a plan per lead, saying who to contact, what to pitch, why now and what to say, with a source attached to every claim. A plan can also say not yet, or skip, which is what separates it from a tool that only ever sends. Whatever fills the gap, hold it to the reason test: if the output does not tell you what changed, where it was seen and when, it has not answered the question.
How to run the reason test this week
None of these five positions needs a platform decision to start. Run this by hand on one rep's book before the next planning meeting:
- Pull twenty accounts at random from one rep's active list, not their top twenty.
- For each, try to answer the three questions from what is in the CRM today: what changed, where it was seen, when. Count how many pass.
- Research the ones that fail for fifteen minutes each: the company's news page, recent job posts in the function you sell to, the leadership team's recent posts. Count how many pass after research.
- Time it. Minutes per account, multiplied by the size of the book, is the research load your coverage model is ignoring.
The first count tells you how much of your CRM can support a prioritization decision today. The gap between the first and second counts tells you how many reasons are out there that nobody has written down. The time tells you what it would cost to close the gap by hand. Bring those three numbers to the next territory or tooling conversation and the five decisions above stop being opinions.
RevOps owns the system that decides where effort goes. The best practice that sits under the other five is making sure that system can see the reason behind each account, and can tell when it is missing. If you are still drawing the line between what RevOps owns and what enablement owns, sales enablement vs sales operations sorts out that charter.
