What does a great RevOps 30-60-90 day plan look like for a new VP or Director?
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.
Related on PULSE
- [What is a RevOps Manager — and how is the role different from RevOps Analyst, Director, or VP?](/knowledge/q10806)
- [Should I Hire a Fractional CRO If I Need a 30-60-90 Plan Before a Board Meeting?](/knowledge/q16100)
- [What does a modern RevOps data warehouse and reverse-ETL stack look like in 2027?](/knowledge/q16184)
- [What does your RevOps first-hire profile look like in 2027?](/knowledge/q12369)
- [What does a RevOps job description look like — and what skills do you actually need?](/knowledge/q10805)
- [What does AI conversation coaching for AEs actually look like in 2027?](/knowledge/q12325)
Common Pitfalls That Derail New RevOps Leaders
Even the best 30-60-90 plan fails when leaders fall into predictable traps. The most common is over-promising in the first 30 days — committing to specific pipeline targets, tool implementations, or headcount before understanding the actual data quality and team capacity. A VP or Director who promises a 20% increase in lead conversion during week two will spend months defending that number rather than fixing root causes.
Another frequent mistake is auditing in a vacuum. If you conduct 1:1s only with executives and skip the SDRs, BDRs, and sales ops analysts who actually touch the systems daily, you’ll miss the operational reality. The CRM “works” according to the CRO — but the SDR team has 47 custom fields they ignore because they’re irrelevant. Similarly, trying to fix everything at once during days 31-60 dilutes impact. A new leader who launches CRM cleanup, forecast redesign, comp plan changes, and a new lead scoring model simultaneously will see none of them stick. The most effective pilots are limited to one or two initiatives with clear success metrics and a 4-week deadline.
A third trap is ignoring the political market. RevOps sits between Sales, Marketing, and Finance — each with competing priorities. A director who aligns solely with the CRO may find the CFO blocking budget requests, or marketing refusing to change lead definitions. Great plans include a stakeholder mapping exercise in the first 30 days, identifying who has veto power, who will resist change, and who will champion your initiatives. Without this, even a technically perfect 90-day plan will stall.
How to Measure Success in Each Phase Without Vanity Metrics
A common error in 30-60-90 plans is using activity-based metrics that look good on paper but reveal nothing about impact. For the first 30 days, success isn’t “completed 25 meetings” — it’s validated findings. A better measure: you’ve identified the top 3-5 systemic issues that, if fixed, would move the revenue engine by at least 10-15%. Document these in a one-page audit summary with specific examples (e.g., “43% of closed-won deals have no recorded discovery notes,” or “forecast accuracy is 62% against a target of 85%”).
During days 31-60, measure pilot completion and early signal validation, not revenue impact. A successful pilot might show that a new forecast cadence improved accuracy from 62% to 71% in a single month, or that cleaning CRM fields reduced time-to-close by 3 days for 10 reps. These aren’t boardroom numbers yet, but they prove the concept works. Avoid measuring “pipeline created” or “deals influenced” at this stage — those take 60-90 days to attribute correctly.
By days 61-90, the right metric is stakeholder buy-in and roadmap approval. A successful 90-day plan ends with the CRO and CFO signing off on a 12-month budget and headcount plan. Quantifiable wins like “forecast accuracy improved to 78%” are great, but the real success is that the organization now trusts your process and is willing to invest in your recommendations. Track the number of executives who actively reference your audit findings in their own planning — that’s the strongest signal of lasting impact.
Adapting the Plan for Different Company Stages and Team Sizes
A 30-60-90 plan for a Series A startup looks fundamentally different from one at a $500M enterprise. At a seed-stage or Series A company (typically 20-50 employees, 1-3 RevOps people), the first 30 days should focus on building the foundation — establishing basic CRM hygiene, creating a simple forecast process, and defining lead routing rules. There’s often no existing RevOps function, so you’re building from scratch. Days 31-60 might involve selecting and implementing a single critical tool (like a lightweight CRM or revenue intelligence platform), and days 61-90 are about hiring your first analyst or ops manager. The plan should be 50% execution, 30% hiring, and 20% strategy.
For a growth-stage company (100-500 employees, 5-15 RevOps team members), the focus shifts to scaling and optimization. Your audit in days 1-30 should uncover bottlenecks in the existing processes — like a lead-to-cash cycle that takes 45 days when it should take 20. Days 31-60 might involve running a pilot on automating manual data entry or redesigning the sales comp plan. Days 61-90 should produce a 12-month roadmap that includes tool consolidation (you likely have 8-12 tools that overlap) and a hiring plan for 2-3 more team members. The political market here is more complex, so stakeholder mapping is critical.
At an enterprise company (1,000+ employees, 20+ RevOps staff), your 30-60-90 plan must emphasize governance and alignment. You’re likely inheriting a mature but fragmented operation with multiple CRMs, conflicting data definitions, and entrenched processes. Days 1-30 should focus on understanding the existing governance structure — who owns data quality, how decisions are made, and where the friction points are. Days 31-60 might involve launching a cross-functional working group to standardize lead definitions across regions. Days 61-90 should produce a multi-quarter roadmap that addresses tool rationalization, data architecture, and organizational design. The success metric here isn’t speed — it’s getting 5-10 senior stakeholders to agree on a single version of the truth.
FAQ
How long should the listening phase really take? The first 30 days are non-negotiable for listening and auditing. Rushing past this to “show value” often backfires because you miss political landmines or data quality issues. Most successful VPs spend at least 20 hours in 1:1s before proposing any changes.
What if the CRO wants results in the first two weeks? Push back respectfully—explain that a wrong move in week two can cost months of rework. The best approach is to deliver a quick “state of the union” memo by day 14 (just observations, no recommendations) to demonstrate you’re working, then stick to the full 30-day audit plan.
How many pilots should I run in days 31-60? Exactly one or two, never more. Trying to fix CRM hygiene, forecast cadence, and the MQL-to-SQL handoff simultaneously dilutes focus. Pick the single highest-leverage initiative—usually forecast accuracy—and prove you can move the needle on that before expanding.
What if I inherit a toxic team culture? Your 30-60-90 plan must include intentional team-building, not just process fixes. Schedule weekly skip-levels and anonymous pulse checks. If you ignore culture for the first 60 days, you’ll lose your best people before you finish the roadmap.
Should I present the 12-month roadmap to the board or just the CRO? Present it to the CRO and CFO first in days 61-90. Only take it to the board after you’ve secured budget alignment and executive sponsorship. A premature board presentation can get your plan killed by stakeholders who weren’t prepped.
How do I handle a legacy tech stack that’s clearly broken? Don’t rip and replace in the first 90 days. Instead, document the pain points and cost of inaction in your roadmap, then propose a phased migration starting in month 4. Quick tech changes made without trust often get reversed within a quarter.
Sources
- Pavilion. 2024 RevOps Leader Benchmarks. https://www.joinpavilion.com/research
- Lane, Sean. The Revenue Operations Podcast, "First 90 Days as a RevOps Leader" episodes. https://www.driftcast.com/revops
- Liu, Hugh. RevOps Co-op community playbooks, "First 90 Days" template. https://www.revopscoop.com/playbooks
- McKinsey & Company. The First 90 Days Research Series. https://www.mckinsey.com/capabilities/people-and-organizational-performance
- Force Management. Command of the Message and RevOps Onboarding. https://www.forcemanagement.com/resources
- OpenView Partners. SaaS Benchmarks Report 2024, RevOps Leadership Section. https://openviewpartners.com/benchmarks
- Watkins, Michael. The First 90 Days, updated edition. Harvard Business Review Press.
- Gartner. CSO Update 2024, Revenue Operations Maturity Model. https://www.gartner.com/en/sales