The First 90 Days of RevOps Have Changed

There are roughly a hundred blog posts telling new RevOps leaders what to do in their first 90 days. Audit the stack. Meet the team. Build a dashboard by week two. Most of them were written for a job that stopped existing a while ago.

Five years back, doing well in RevOps meant keeping Salesforce upright, fixing broken workflows, and turning requests into reports. That was the job. Today the title comes with a different mandate: improve revenue predictability, guide strategic decisions, and connect every GTM function that used to run on its own island. If your 90-day plan still looks like a CRM cleanup checklist, you're solving last decade's problem.

The RevOps Role Isn't What It Used to Be

RevOps started as operational support

The original job was narrow, and honestly, fairly mechanical. CRM administration. Sales operations. Workflow automation. Reporting on whatever leadership asked for last. Useful work, but reactive by design: someone else decided what needed fixing, and RevOps fixed it.

Modern companies created a new problem

Then every department went out and bought its own tools. The result, a few years in:

• Marketing had one stack, sales ran another, customer success ran something else entirely
• Each team quietly built its own processes on top of its own tool
• Customer data fragmented across systems that didn't talk to each other
• Revenue visibility, the thing leadership actually needed, disappeared somewhere in between

RevOps didn't evolve because companies wanted better Salesforce hygiene. It evolved because somebody had to connect the systems, the teams, and the customer journey that was now scattered across a dozen disconnected tools.

But the tool sprawl is only half of it. The bigger push came from the market itself:

• Growth without headcount. Boards started asking companies to grow without simply adding headcount, which means more revenue has to come from the same number of reps working smarter, not a bigger team working harder.
• Tighter budget scrutiny. Finance started scrutinising every tool line item, so the "we'll just buy another platform" instinct doesn't fly the way it used to.
• AI raising the stakes on data quality. AI is getting layered onto the GTM stack, and it's only as good as the data underneath it. Feed a model a fragmented, half-updated CRM and it'll make confident, wrong decisions faster than a human ever could.

Someone has to own that. Increasingly, it's RevOps.

Today's RevOps leaders are expected to influence strategy

The questions changed too. It used to be "can you build this report?" Now it's "why did pipeline slow down," "can we trust this forecast," "where should we invest next," and "what's actually preventing growth?" Those aren't operational questions. They're the kind a company asks its strategic leaders, not its systems administrator, and that's precisely the shift most 90-day templates never caught up to.

Before You Plan Your First 90 Days, Ask One Question

What did the company actually hire you to do?

Here's the thing nobody tells you: "Head of RevOps" means something completely different depending on where you land. At Company A, it's CRM ownership, Salesforce admin, and process optimisation, full stop. At Company B, it's an executive leadership seat with forecasting, territory planning, and revenue strategy attached to it.

Same title. Different job entirely.

So don't walk in asking "what should I fix first?" That question assumes you already know what success looks like, and you don't yet. Ask instead: "what outcomes am I accountable for?" It's a smaller question with a much bigger payoff, because it tells you whether you were hired to run the machine or redesign it.

Your Goal Isn't Completing Tasks, It's Delivering Clarity

Skip the long checklist. Frame the entire 90 days around four deliverables instead. By day 90, leadership should have:

1. A clear understanding of how revenue is generated. Not a slide with logos on it. An actual map of how a lead becomes a customer and where the friction lives.

2. Visibility into what's breaking. Where deals stall, where handoffs fail, where the forecast quietly diverges from reality.

3. Confidence in which metrics can actually be trusted. Half the numbers in most CRMs are decorative. Leadership needs to know which half.

4. A prioritised roadmap of the 2-3 highest-impact improvements. Not fifteen. Three, maybe two if you're being honest with yourself.

Success here isn't measured by how many projects got shipped. It's measured by how much clarity exists in the building that wasn't there on day one.

Days 1-30: Understand the Revenue System

Don't change anything yet. Resist the urge, even when the fix looks obvious on day four. Your only job this month is understanding how revenue actually moves through the business: the customer journey, the handoffs between teams, the expansion paths, the bottlenecks, and how decisions really get made (as opposed to how the org chart says they're made).

Better stakeholder interviews

Most new RevOps leaders open every conversation with "what do you want from RevOps?" It's a fine question and it gets you nowhere useful. Try these instead:

• Which decisions take too long?
• Why do forecasts miss?
• Which metrics don't you trust?
• Where does revenue leak?

Every department is going to hand you its own version of reality, and they'll all be true from where that team is sitting. Reconciling those versions is the actual job.

Days 31-60: Understand the Systems Behind Revenue

Evaluate your tech stack

Skip the software inventory spreadsheet. Instead, for every tool, ask why it exists, whether anyone's actually using it, what breaks if you remove it, and whether it improves decision-making or just generates activity. A tool nobody trusts is worse than no tool at all; at least the absence is honest.

Evaluate CRM health through a business lens

Duplicates are easy. The harder one is connecting CRM quality to forecasting accuracy, rep productivity, reporting integrity, and increasingly, whatever AI tools your company is bolting onto the stack. Garbage in, garbage forecast.

CRM health stopped being a quarterly cleanup project a while ago. It's infrastructure now, and everything else, including that AI initiative someone on the leadership team is excited about, depends on it holding up.

This is the kind of check Findymail CRM Datacare runs for free before you commit to anything: a straight read on completeness, decay, and duplicates, so the case for fixing it writes itself instead of you having to sell it.

Days 61-90: Prioritise What Actually Moves Revenue

By now you understand the revenue system and the infrastructure underneath it. The temptation is to fix everything you found. Don't. Evaluate every opportunity against business impact, how often it actually occurs, effort required, how many teams it touches, and the commercial outcome if it's solved.

Strong RevOps leaders leave their first 90 days with a focused roadmap, not a backlog of forty disconnected improvements nobody has bandwidth for.

What Success Looks Like After 90 Days

Forget the completed-tasks scoreboard. A successful RevOps leader should be able to answer four questions without hesitating: How does revenue actually flow through our business? Which metrics should leadership trust? Where are we losing efficiency? And which 2–3 initiatives will create the biggest commercial impact next?

If you can answer those with confidence, the first 90 days worked. If you can't yet, you're not behind, you just found the real starting line.

Final Thoughts

The first 90 days were never about proving you know Salesforce or racking up as many fixes as possible. They're about showing leadership you understand how the business actually generates revenue, where it breaks down, and what should happen next.

Modern RevOps leaders create clarity before they create change. By day 90, leadership shouldn't be looking at a long list of tactical fixes. They should have confidence in the data, real visibility into the revenue engine, and a focused plan for the one or two initiatives that will actually move the number.

James Carter

James is a senior SaaS commercial leader specialising in enterprise sales, GTM strategy and revenue growth, with deep CRM platform expertise. He writes on CRM strategy to help revenue teams scale.