A 30-60-90 Day Playbook for First-Time RevOps Leaders

A 30-60-90 Day Playbook for First-Time RevOps Leaders

A conversation with Hassan Irshad, Director of RevOps at FEVTutor.

Revenue Operations (RevOps) isn’t just a support function anymore. It’s the strategic engine that powers alignment, productivity, and visibility across the go-to-market (GTM) teams. And for first-time RevOps leaders stepping into the role, the first 90 days are absolutely critical. Your success depends on how well you can listen, diagnose, align, and act.

In this deep-dive, Hassan Irshad—former Director of RevOps at FEVTutor and a veteran in building RevOps functions from the ground up across multiple B2B SaaS organizations—shares a tactical, proven playbook for the first 90 days in the job. Structured into three phases, this playbook helps new leaders set up a high-impact, scalable RevOps engine.

Phase 1: The First 30 Days — Discovery and Trust-Building

Hassan calls this the “Discovery Phase,” and it’s arguably the most important segment of your 90-day plan. Here, the goal isn’t to solve every problem. It’s to understand the lay of the land, build stakeholder trust, and uncover real pain points.

“Think of yourself as a doctor. If you don’t listen well enough, you’ll misdiagnose the pain.”

Start by meeting with stakeholders across departments: Sales, Marketing, Customer Success, Finance, Product, and HR. Identify their KPIs, their blockers, and their goals. Create a document that captures all your findings—Hassan refers to this as the “Lay of the Land” doc.

At the same time, shadow end users. Sit with BDRs, AEs, and CSMs. Watch how they use tools. How do they enter data? Where do they get stuck? Walk through your CRM. Is reporting intuitive or a tangled mess?

Don’t stop there. Run a detailed tech stack audit. Map every tool in the ecosystem. What integrates with CRM? What’s shelfware? What’s overused or underused? Hassan emphasizes talking to users, not just system owners.

You should also:

  • Immerse yourself in the product: attend demos, listen to sales calls.

  • Map existing processes: selling, onboarding, renewals.

  • Identify low-hanging fruit for early wins: improve field logic, add help text, or train users on hidden CRM features.

Key Objectives:

  • Establish trust

  • Conduct a stakeholder audit

  • Perform a tech and process audit

  • Map current workflows

  • Identify quick wins

💡 Action Items:

TaskDescription
Stakeholder InterviewsMeet leaders from Sales, Marketing, CX, Finance, HR, and Product. Understand their KPIs, pain points, and top priorities.
Create a “Lay of the Land” DocumentA central repository of org structure, current GTM processes, key workflows, and metrics.
Shadow GTM TeamsSit with BDRs, AEs, and CSMs to understand how data is entered, how tools are used, and where bottlenecks occur.
Tech Stack AuditList every tool in use, usage rates, integrations, costs, redundancies, and gaps.
Process MappingMap the end-to-end selling, marketing, and renewal processes. Identify handoffs, duplication, and inefficiencies.
Product ImmersionAttend a demo, listen to sales calls, and understand the sales pitch and product-market fit.

✅ Quick Wins Template:

Win TypeExample
Usability FixClarify error messages in CRM workflows
Dashboard BuildBuild a simple commissions dashboard for reps
TrainingConduct a quick session on a misunderstood feature

Phase 2: Days 31-60 — Alignment and Control

This is the phase where you start “flexing your RevOps muscles,” as Hassan puts it. While discovery continues in some areas, you now begin putting controls and alignment mechanisms in place. Hassan calls this phase “Alignment and Control.”

“You need to be the catalyst for cross-functional collaboration. Nobody else is connecting the dots across sales, marketing, and CX.”

Start with KPI alignment. You’ll have already collected the individual KPIs in Phase 1. Now, assess whether those KPIs roll up into the broader company strategy. If they don’t, that’s a red flag—and your opportunity to bring the teams together.

Hold cross-functional syncs to align Sales, Marketing, and CS around shared quarterly goals. Create dashboards and reporting frameworks that reflect this shared accountability.

Also, start implementing operational controls:

  • Are close dates in CRM accurate?

  • Is forecasting behavior consistent?

  • Are stage definitions clear?

Don’t impose controls abruptly. Hassan suggests using logic and transparency. Example: If a rep uses spreadsheets to track deals, propose a CRM-based inline-editable report that feels like a spreadsheet but ensures visibility.

And begin vetting your tools:

  • Is a forecasting tool duplicating features available in Salesforce?

  • Are reps logging into a tool?

  • Can licenses be consolidated?

Key Objectives:

  • Improve GTM team collaboration

  • Put control mechanisms in place

  • Begin strategic alignment

  • Validate process improvements

💡 Action Items:

TaskDescription
Cross-Functional AlignmentFacilitate regular syncs between Sales, Marketing, and CX to align on quarterly goals.
KPI RationalizationAlign individual department KPIs with the company’s strategic objectives. Identify siloed or conflicting goals.
Governance SetupDefine request intake processes, project documentation standards, and response SLAs.
Control ImplementationUse logic and data to drive compliance (e.g., inline editable reports to update close dates instead of spreadsheets).
Change Management PrepIdentify stakeholders who will sponsor or resist change. Begin conversations to create buy-in.

Phase 3: Days 61-90 — Vision and Execution

By now, you’ve earned trust, understood the landscape, and started building momentum. Phase three is about turning that momentum into long-term strategy and execution. Hassan calls this the “Vision and Execution” phase.

“You’re now setting the foundation for your long-term roadmap. Think beyond tickets—think strategy.”

At this point, you should be ready to publish a two-quarter RevOps roadmap. This roadmap includes:

  • Strategic initiatives tied to revenue goals

  • Operational improvements already underway

  • Planned enhancements to the tech stack

This is also the time to start tracking and showcasing impact. Go back to the baselines you gathered in Phase 1. Show how time-to-insight improved, or how a forecast accuracy initiative reduced missed commits. Make your work visible.

Remember, this is also where change management becomes critical. Stakeholders may resist new processes. Hassan advises using your discovery-phase insights to preempt resistance. Understand their motivations and frame changes as value drivers.

Key Objectives:

  • Publish a roadmap

  • Begin implementation

  • Showcase wins

  • Plan for continuous improvement

💡 Action Items:

TaskDescription
Publish a RevOps RoadmapA two-quarter plan with milestones, tools, owners, and projected outcomes.
Implement High-Impact ProjectsFocus on fixes that will yield meaningful business value—clean data, accurate forecasting, unified dashboards.
Vendor ManagementEngage vendors for roadmap-aligned support, optimize licenses, or deprecate tools.
Executive ReportingBuild baseline-to-impact comparisons for metrics improved via RevOps.
Change Management ExecutionDrive adoption by revisiting discovery insights, socializing impact, and enabling champions.

📈 Roadmap Template:

QuarterInitiativeOwnerImpact GoalMetrics
Q1Unified Commissions DashboardRevOpsImprove AE payout visibilityRep NPS, Payout Accuracy
Q1Improve Forecasting AccuracyRevOps + Sales OpsAccurate pipeline projectionsForecast Accuracy YoY
Q2Renewal Process AutomationRevOps + CXReduce churn by 10%Retention Rate, Renewal TAT

After 90 Days: Iterate and Scale

The journey doesn’t end at Day 90. In fact, it just begins.

  • Version everything: Hassan’s advice is to treat every process like a product. Launch version 1.0, then iterate.

  • Prioritize ruthlessly: Not every idea makes the roadmap. Rank by impact, effort, and strategic alignment.

  • Celebrate your wins: Share improvements, metrics, and testimonials widely. This builds advocacy and credibility.

Final Thoughts

For first-time RevOps leaders, your first 90 days aren’t just about learning the ropes. They’re about defining your leadership style, establishing strategic value, and building a platform for scale.

Follow this 30-60-90 playbook, and you’ll go from being the new hire to the strategic architect of a high-performance revenue engine.

“If you can’t measure your impact, it didn’t happen. Treat your wins like closed deals—celebrate them.”

Want to hear more stories from revenue leaders? Subscribe to The Revenue Lounge podcast to never miss an episode!

More Resources

5 Steps to Navigate Buying Groups in 2025: A RevOps Guide

5 Steps to Navigate Buying Groups in 2025: A RevOps Guide RevOps 10 min In today’s business environment, B2B buying is never just one person. According to Forrester Research, more than half of global business buyers purchase in complex buying scenarios that include more people, more departments, and generally higher price points. And this buying group can be made up of 7 to 20 people! Unlocking the power of buying groups is a crucial aspect of the B2B landscape. This blog is a synopsis of our conversation with revenue operations leader, Nandini Karkare. She is currently the SVP of RevOps at Zywave. Nandini suggests strategic steps to navigate through the realms of Revenue Operations and helps uncover the strategies, insights, and best practices that constitute a comprehensive guide to mastering the dynamics of buying groups. Read on to get actionable tips on how you can navigate buying groups in 2025 (and beyond). And implement the learnings to create a winning GTM motion. Here are the 5 steps Nandini recommends: 1. Decode Your Buying Groups The buying groups typically consist of members from departments and they all contribute different aspects. It is critical to understand the scope of decision-making including the people who play the most significant roles in making the call. Gartner’s report on B2B Buying highlights that 77% of B2B purchases involve a buying group of four or more people. PS: The key stakeholder can turn out someone altogether different from who you had building a relationship with all along. a. Capturing Buying Group Members   Effective buying group management means considering not just decision-makers but influential stakeholders across departments. Misidentifying key players or focusing solely on the main contact risks derailing the sale. (i) How can you map the entire buying group efficiently? Leverage internal and external data to identify the key players Segment the Group by Role and Influence (ii) Not everyone in the buying group holds equal power or influence. Segment them into categories: Decision-makers (who give the final heads-up) Influencers (who sway the decision) Users (who use the product and provide feedback) Budget owners b. The Role Transition Within a Buying Group   Moving the focus from a buying group to a renewal or expansion committee includes knowing precisely who remains in the relationship, as well as who becomes more active as an account grows. (i) New roles may emerge in a Buying Group Technical or operational leaders may become more influential post sale, since they are now using the product. (ii) The focus shifts from buying to renewal The interaction should be more about the return on investment (ROI) of the product placed on the market, ongoing value delivery, and ongoing needs. (iii) Alignment between the buying groups and renewal committee Leveraging the same enthusiasm and relationships generated at the first-buying stage helps in anchoring the transitions and preventing any drop-offs in engagement. Related Resource: Navigate Enterprise Buying Committees: Strategies for Driving Alignment c. Understand the Personal and Collective Priorities of a Buying Group As per McKinsey & Company, B2B buying decisions increasingly require engagement across departments, with 60% of purchasing committees including members from outside traditional procurement, like IT and HR. (i)Alignment Between C-Suite and Technical Teams Decisions aren’t Made in a Vacuum Collaboration between C-suite and technical teams ensures a holistic approach to solving customer problems, creating stronger, more sustainable relationships Their cross departmental collaboration can help with: (ii) Alignment on Strategic Goals C suite executives need technical assistance to translate their strategic vision to reality that also aligns with company-wide objectives. (iii) Technical Validation These insights guide the C-suite in making informed decisions that fit technical infrastructure and future-proofing. (iv) Cross-functional Communication Bridging the gap between these two groups involves continuous, open communication, ensuring that technical evaluations don’t delay business goals but instead support them cohesively.   iii. Understand the Product Take product demos, listen to sales calls, and use tools that show how the product is sold. This helps in understanding the customer needs better. iv. Dive into Your CRM Understand your CRM (whether Salesforce or HubSpot) to assess how the data is organized. This is to check whether it’s easy to use, and identify immediate improvements. The CRM should be the central source of truth, with other tools supporting it. The data should be unified with easier adoption for the teams. v. Build Trust Internally Establish trust within your teams by listening carefully, asking questions about how RevOps can help, and addressing quick fixes to show you’re there to help. Having this trust shows them that you’re here to support their success. Quick wins, such as small fixes that make people’s jobs easier, helps in establishing credibility early. 2. Establish Clear KPIs   i. Understanding Team KPIs It is important to ask you stakeholders about the KPIs that matter to understand their goals and what their expectations are. ii. Aligning KPIs Across Teams Different departments oftentimes work in silos. RevOps should strive to align these departments and check if these KPIs match the overall business objectives. Gaps must be closed if their KPIs don’t align. iii. Setting RevOps KPIs As you approach the end of the first 30 days, start establishing RevOps-specific KPIs that match company goals, which may involve metrics like revenue increase, conversion rates, or improvements in overall efficiency. 3. Tech Stack Audit Deep dive into the existing tools that your company is using. Identify all redundancies, and find opportunities to streamline the entire tech stack. i. Map Out Tools Compile a list of all tools used by teams, noting their purpose and how they work with the CRM. ii. Evaluate Use and Cost Determine if tools are actively used or if there are duplicates. Look for cost-saving opportunities by consolidating tools when possible. https://www.youtube.com/watch?v=sVDJ9KI1tGw&t=869s Next 30 days – Alignment and Control The next 30 days marks a shift from discovery to alignment. The goals should be to create cohesion between departments (e.g., Sales, Marketing) and laying down effective controls. The improvements need to be implemented without overwhelming the teams. This phase combines

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top

Just one more step