What does a great RevOps 30-60-90 day plan look like for a new VP or Director?

Direct Answer

A great RevOps 30-60-90 for a new VP or Director is built around restraint, not ambition. Days 1-30 are Listen and Audit: 1:1s with every GTM leader plus 12-20 individual contributors, plus a written audit of forecast accuracy, CRM hygiene, pipeline coverage, comp plans, and the tech stack.

Days 31-60 are Pilot: run 1-2 quick-win pilots on the three highest-leverage initiatives, usually CRM cleanup, forecast cadence, and the MQL-to-SQL handoff. Days 61-90 are Commit: present a 12-month roadmap with tooling, hiring, OKRs, and budget to the CRO and CFO, then execute.

TL;DR

• Days 1-30 are listening, not deciding. You produce a written audit, not opinions.
• Days 31-60 pick three highest-leverage initiatives and run 1-2 small pilots that the org can feel.
• Days 61-90 deliver a 12-month roadmap with tooling, hiring, OKRs, and a locked budget.
• The five common mistakes are doing too much, picking the wrong first project, skipping IC 1:1s, over-promising in week 2, and buying tooling before fixing process.
• The three reliable quick wins are forecast cadence redesign, MQL-to-SQL SLA, and a pipeline coverage dashboard.

Days 1-30: Listen + Audit

The first thirty days are for evidence, not action. The most common failure mode for a new RevOps leader is walking in with a playbook from the last company and trying to install it before learning where this company actually is. In month one your only deliverable is a written audit, and your only currency is questions.

What to do. Book 1:1s with every GTM leader in the first two weeks: CRO, VP Sales, VP Marketing, VP Customer Success, VP Finance, the head of enablement, and your peer in product if PLG matters. Then go a layer deeper than most new leaders do: 12-20 individual contributor 1:1s with frontline AEs, SDRs, CSMs, and any existing RevOps analysts.

ICs will tell you the truth about the CRM, the forecast call, the comp plan, and which dashboards everyone secretly ignores. In parallel run a five-pillar audit: forecast accuracy versus actuals for the last four quarters, CRM data hygiene (field fill rate, stage definitions, ownership), pipeline coverage trends, comp plan integrity, and the GTM tech stack with line-item spend and utilization.

What NOT to do. Do not promise an overhaul to the CRO in week two; the moment you commit, you are anchored to a wrong plan. Do not change a Salesforce field, dashboard, or stage definition. Do not fire anyone. Do not buy anything. The end-of-month-one artifact is one document: a 10-15 page written audit covering findings only, ranked by impact.

Days 31-60: Pilot the 3 Highest-Leverage Initiatives

Month two is where you move from witness to operator, but carefully. You are allowed to act, but only on 1-2 small pilots, never an org-wide change. The job is to put visible wins on the board so that when you come back in month three asking for budget and headcount, the org already trusts you.

What to do. From your audit findings, pick the three highest-leverage initiatives. Nine times out of ten they are the same three: clean up the most-broken CRM data (opportunity stage and close-date hygiene), redesign the forecast cadence, and document the MQL-to-SQL handoff with an SLA and disposition tracking.

These are universal quick wins because they cost almost nothing, produce measurable lift in a single quarter, and earn the trust capital you will spend in month three. Forecast cadence redesign typically lifts call accuracy by 5-10 percentage points in one quarter. An MQL-to-SQL SLA with disposition tracking rebuilds marketing-to-sales trust, often for the first time in years.

A pipeline coverage dashboard that executives actually trust changes how the QBR runs. Pick two of those three and pilot them on one segment or region, not the whole org.

What NOT to do. Do not start a Salesforce overhaul; that is a four-to-six month project disguised as a quick win and it will swallow your entire 90 days. Do not buy tooling yet.

Process and data come first; fix those, and the tooling decision almost makes itself. Do not roll a pilot org-wide before it has produced a measurable result. A pilot has to be able to fail privately.

Days 61-90: 12-Month Roadmap + Commit

Month three is the commitment moment. You have evidence, you have one or two quick wins in flight, and you have the org's attention. Now you deliver the plan you were hired to deliver.

What to do. Present a 12-month roadmap to the CRO and CFO together. It should include the audit's biggest findings translated into three to five process changes you will lead, a tooling decision (consolidate, replace, or expand, with line-item ROI math), a hiring plan with seat-by-seat justification, the OKRs you will personally own for the next four quarters, and a locked budget ask.

The 90-day report becomes the appendix. By end of day 90 you want explicit written buy-in from CRO and CFO, a locked budget in next quarter's plan, and the first hire posted or already in pipeline.

A real example. A new VP RevOps at a $40M ARR Series C followed this exact arc. By day 30 they had a written audit with 17 findings.

By day 60 they had run a forecast cadence pilot in one region that improved accuracy from plus-or-minus 18 percent to plus-or-minus 9 percent. By day 90 they had CRO and CFO buy-in for a $400K tech stack consolidation plus three hires (a senior analyst, a Salesforce admin, and a deal desk lead).

The CRO described the 90-day report as the clearest GTM document she had seen in three years.

Frequently Asked Questions

Should I bring my old vendors with me? Almost never in the first 60 days. Even if the new vendor is genuinely better, swapping tooling before you understand the workflows is how new RevOps leaders burn political capital. Re-evaluate in month three with the rest of the tooling decisions, and let the ROI math decide, not loyalty.

When is it okay to fire someone? Not in the first 90 days unless there is a clear ethics or performance issue already documented by the prior leader. People you inherit deserve a fair look in your audit. Most "wrong-seat" calls become obvious by day 120 anyway, and waiting buys you credibility on the calls you do make.

What if I disagree with the CRO on direction? Put the disagreement on paper, with data, by day 90. The 12-month roadmap is the right forum. CROs respect a RevOps leader who shows up with evidence and a recommendation; they lose patience with one who litigates in hallway conversations.

Sources

1. Pavilion. 2024 RevOps Leader Benchmarks. Https://www.joinpavilion.com/research
2. Lane, Sean. The Revenue Operations Podcast, "First 90 Days as a RevOps Leader" episodes. Https://www.driftcast.com/revops
3. Liu, Hugh. RevOps Co-op community playbooks, "First 90 Days" template. Https://www.revopscoop.com/playbooks
4. McKinsey & Company. The First 90 Days Research Series. Https://www.mckinsey.com/capabilities/people-and-organizational-performance
5. Force Management. Command of the Message and RevOps Onboarding. Https://www.forcemanagement.com/resources
6. OpenView Partners. SaaS Benchmarks Report 2024, RevOps Leadership Section. Https://openviewpartners.com/benchmarks
7. Watkins, Michael. The First 90 Days, updated edition. Harvard Business Review Press.
8. Gartner. CSO Update 2024, Revenue Operations Maturity Model. Https://www.gartner.com/en/sales