Your First 90 Days as a New RevOps Leader

Landing a RevOps leadership role is exciting - and disorienting. You're expected to understand a complex tech stack, earn trust across sales, marketing, and customer success, and start delivering results, all at the same time. The first 90 days set the tone for everything that follows. Move too fast and you break things. Move too slow and stakeholders lose faith.

This guide gives you a structured, realistic playbook to navigate that window without burning out or burning bridges.

Days 1-30: Listen Before You Build

Your first month is not about fixing things. It's about understanding what's actually there - and why it was built that way. Most RevOps leaders underestimate how much institutional context lives in the heads of individual contributors. Before you redesign anything, you need to extract it.

Run a Stakeholder Interview Sprint

Book 30-minute 1:1s with every key stakeholder in your first two weeks: sales managers, marketing leads, CS ops, finance, and the CEO or CRO if you have access. Ask the same five questions to everyone:

• What does a good quarter look like from your perspective?
• Where do you lose the most time to manual work or bad data?
• What reports do you trust, and which ones do you ignore?
• What did the last RevOps person get wrong?
• If you could change one thing in the CRM tomorrow, what would it be?

The patterns that emerge across these conversations are your real brief. Write them up and share back a summary - this alone builds credibility fast.

Audit the Tech Stack and Data Layer

Get read access to every system in the stack as quickly as possible. Don't wait for formal onboarding. You need to see the CRM, the MAP, the data warehouse if there is one, the BI tools, and any point solutions the team is using.

Start by mapping what's connected to what. In CRM-heavy environments, your automation layer is often where years of accumulated logic live - sometimes contradictory logic. A visual dependency map can shortcut this discovery work dramatically, helping you see which workflows share properties, which are redundant, and where there are likely conflicts before you touch anything.

Days 31-60: Diagnose and Prioritize

Once you've listened and mapped the landscape, you move into structured diagnosis. This phase is about translating observations into a prioritized list of problems - not solutions yet.

Score Your Data Quality

Data quality is the foundation of everything in RevOps. Bad data makes your pipeline forecasts unreliable, your lead routing broken, and your reports misleading. In your second month, run a systematic data quality assessment:

• Measure field completion rates on your critical objects (contacts, companies, deals, tickets)
• Identify properties that are defined inconsistently or duplicated across the schema
• Check for lifecycle stage logic gaps - leads stuck in stages, contacts with no owner, deals with missing close dates
• Review which properties are actually used in automation vs. which are orphaned

Property sprawl is almost universal in organizations that have had multiple RevOps owners. A property impact analysis can show you which properties are actively driving automation logic and which are safe to clean up - so you don't accidentally break something by deprecating a field that looked unused.

Build Your Quick Win List

Every new RevOps leader needs at least two or three visible wins in the first 60 days. These don't have to be strategic - they just have to be felt by the people who matter. Look for:

• A broken report that a sales manager checks every morning
• A manual process someone on the team hates (a spreadsheet used as a workaround, a data entry step that could be automated)
• A data quality issue that's causing visible pain (wrong owner assignments, leads not being routed, duplicate records hitting reps)

Fix one of these per week in month two. Ship it, announce it, get the credit. This buys you time and goodwill to do the harder structural work in month three.

Days 61-90: Build the Operating System

The third month is where you shift from reactive to proactive. You now have enough context to start building the systems and rhythms that will define how RevOps operates at this company.

Establish Your Reporting Cadence

RevOps is most valuable when it's the connective tissue between revenue functions - and that means owning the data narrative. Define and own the reports that matter:

• Pipeline health and velocity by stage
• Lead source attribution and conversion rates by channel
• Forecast accuracy vs. actuals (rolling 90 days)
• SLA performance between marketing and sales (lead response time, handoff quality)

Present a version of this in your first leadership team meeting. It doesn't have to be perfect - it has to be honest and discussed. The goal is to make RevOps the place everyone comes to when they have a data question.

Document What You've Found - and What You're Changing

One of the most durable things you can do in your first 90 days is leave a clear record of the state you found the system in. This protects you when something breaks six months later, and it creates a baseline you can point to when demonstrating your impact.

Document your findings from the audit, the decisions you made, and the rationale behind them. Structured documentation isn't just for your successor - it's how you scale your own memory and bring new team members up to speed faster. The RevOps documentation canvas approach works well here: keep your system maps, workflow logic, and property decisions in one place that anyone can navigate.

Set Your 90-Day Review Meeting

At the end of day 90, schedule a formal review with your CRO or CEO. Present three things: what you found, what you fixed, and what you're building next. Frame it as a state of the union, not a self-promotion exercise. Include the problems you haven't solved yet - this signals maturity and sets honest expectations.

The Mindset That Makes It Work

The biggest mistake new RevOps leaders make is trying to prove their value through changes. In reality, your value in the first 90 days comes from your judgment - knowing what to change, what to leave alone, and in what order.

RevOps is a trust-dependent role. You touch the systems that everyone relies on. Every decision you make either builds or erodes the confidence that other revenue leaders have in you. Move with curiosity in month one, rigor in month two, and conviction in month three.

The leaders who succeed in RevOps long-term are the ones who become the most reliable interpreter of what's happening in the revenue engine - and that reputation is built in the first 90 days.