RevOps Manager: The Forecast Is Yours Now

The RevOps Manager is the person whose number the CFO writes in the board deck. Not the rep's commit, not the CRO's "feels good," not the Clari AI summary. The Manager's reconciled call, after they've spent Sunday night arguing with their own spreadsheet.

The job sits between three rooms that don't naturally talk: the data, the CRO, and the first-line sales managers actually inspecting deals. The Manager's value is being the only person fluent in all three. Enough Salesforce admin to trust the report. Enough business judgment to know which line on it matters this quarter. Enough range to deliver an inconvenient number to a CRO without turning into the office Cassandra.

The title became the standard mid-level RevOps label around 2019–2021, as the discipline grew out of its "Salesforce Admin who also runs the deck" origins. Sales Operations still exists as a parallel title, and at most companies a Sales Ops Manager and a RevOps Manager are doing the same work with different reporting lines. The honest difference: a Sales Ops Lead reports into the CRO and stays in Sales's lane. A RevOps Manager nominally owns marketing handoff and customer expansion too. Whether the org actually lets them is the interview question that tells you what the job will be.

A day in the life

After a few months in the role you stop tracking days and start tracking cadences. Mondays are forecast. Wednesdays are pipeline. Thursdays are the CRO. Fridays are the only block long enough to think.

Monday: the forecast call. This is the meeting that defines the Manager's reputation, and it's running by 9am whether or not you slept. Sunday night you cross-check the Clari AI commit against your bottom-up read from Salesforce, find the three deals where the rep call and the data disagree, and decide which version you're going to defend. The forecast call itself is part deal-level inspection, part translation: taking what the reps said about Q3 and turning it into a number a CFO can commit to. The good Mondays are the boring ones. The number holds, the meeting ends in 25 minutes, and nobody emails the CRO afterward.

Wednesday: pipeline review. The forecast is about this quarter. Pipeline review is about the next one. You're looking at quarter-out coverage against target, by segment and by region, and asking where the gaps are going to bite. This is where the RevOps Manager earns cross-functional credibility. You're pulling marketing-sourced versus outbound-sourced pipe, asking CS for the expansion view, and giving sales leadership a picture they can't build without you. The Wednesday conversation usually shapes what shows up in Monday's forecast a week later.

Thursday: the CRO 1:1. Treat this as a status update and you stay a Manager for five years. Treat it as the strategic seat it actually is and you're a Director in three. The CRO has one recurring question, sometimes spoken: what should I be worried about that I'm not worried about yet? The RevOps Manager who has an answer two to four weeks ahead of the headline number — early-stage velocity slowing in mid-market, ramp time creeping on the Q1 hires, stage-2-to-3 conversion dropping in EMEA — gets scope. The Manager who shows up with last week's metrics gets the same scope they had last quarter.

Friday: the only thinking block. This is the time more senior Managers guard hardest. It's where the territory model gets reviewed before sales planning, where forecast methodology gets audited for the bias that crept in after a pricing change, where the process documentation that lives in someone's head finally gets written down. Friday is also when the Manager and the RevOps Engineer (if there is one) sit down to translate business problems into something the platform team can build.

Required skills

Salesforce admin fluency, enough SQL to investigate your own variance, and working knowledge of Clari, BoostUp/Terret, or whatever the forecasting layer is. That's table stakes. Job postings at Stripe, HubSpot, and Gong ask for all three by name. None of it is what gets a Manager promoted.

What separates the strong from the adequate is the ability to deliver a bad number with enough context that the CRO understands the why before they react to the what. And the ability to recognize when a metric is reflecting a data quality issue, a process change, or a field-definition drift rather than a real shift in the business. Most reporting fights inside a revenue org are actually definition fights nobody wrote down. The Manager who notices that first is the one running the meeting six months later.

Typical KPIs

The Manager's KPIs are explicitly different from the Engineer's. The Engineer is on the hook for system reliability: data accuracy, automation coverage, integration uptime. The Manager is on the hook for the outputs those systems produce.

Forecast accuracy at ±5% variance against the called number, measured month-over-month on a rolling 90-day window, is the canonical Manager KPI. Pipeline coverage at 3–4× target, measured at the start of the quarter, is the second. The third is rarely written into the JD but often determines whether the Manager keeps the job: quota attainment distribution. If 80% of reps are clearing quota, the comp plan and the territory model are doing their job. If 50% are clearing, the company doesn't have a RevOps problem; it has a sales-model problem that RevOps is being asked to absorb. Knowing the difference, and saying so out loud to the CRO, is the work.

What it pays

The chart shows core-revops with the Manager-titled subset overlaid in dark. Manager-titled postings sit highest in Mid and Senior; that's the title's actual range. The Lead overlay narrows because most Lead-band postings carry Director or VP titles, and the Manager who wants those numbers takes the title that comes with them.

Reading the offer

Spread within a Manager band is driven almost entirely by stage and ARR. A RevOps Manager at a $10M-ARR series-B in Austin earns materially less than one at a $200M-ARR series-D in New York with the same title and similar scope. Equity is uneven for the role: common at sub-100-person companies, rare at public ones, and the offer letter rarely advertises the size. Ask directly, get the strike price and the 4-year value at the current 409A in writing, and assume the recruiter's verbal "competitive grant" means somewhere between $20k and $200k a year until proven otherwise.

Tools they use

Salesforce is the floor. Every RevOps Manager job posting from Atlassian to Zendesk lists it, and the rare HubSpot-only role pays meaningfully less because the talent pool is smaller and the ceiling is lower.

The forecasting layer above Salesforce is where vendor choice tells you something about the company. Clari is the default at series-B and above and is what most CROs reach for when they've been burned by a missed quarter. Gong has expanded from conversation intelligence into forecasting, and roughly 40% of Gong's mid-market customers run Clari on top anyway. BoostUp rebranded to Terret in late 2025 and is the budget-conscious enterprise alternative. Salesforce's native forecasting still ships at earlier-stage and more conservative orgs, and there's nothing wrong with it; the BI layer (Looker, Tableau, occasionally Hex) does the heavy lifting where Salesforce reports stop. What sinks Managers is treating the dashboard as the deliverable. The deliverable is the Wednesday meeting that uses it, and a Looker chart nobody opens between meetings is just shelfware with a query plan.

The Manager-titled overlay tracks closely with the broader category. Managers operate the same tools as the teams they run. HubSpot and Gong over-index slightly in the Manager overlay because Manager-titled postings cluster at companies where the role does forecast inspection on top of CRM admin.

Career trajectory

Most RevOps careers either accelerate or plateau at this level, and the difference is whether the Manager develops executive presence or stays in reporting mode. The Analyst builds the report. The Manager presents it. The Director decides what's worth measuring at all. Moving from one to the next means spending fewer hours in Salesforce and more hours in rooms where the strategy is being argued.

The jump from Manager to Senior Manager or Director typically takes three to five years. The lever is scope: first managing one or two reports, then owning a full operational function (all of Sales Ops, or a regional pod), then shaping the operating model itself. The VP track requires muscles the Manager role only partially builds: comfort with ambiguity, hiring and developing a team, board-level credibility. That's why most VPs of RevOps had a Director run in between. The Managers who skip the Director stage usually get hired into VP titles at series-A companies where they end up doing the Director work anyway, just with a worse safety net.