Building & Scaling a High-Performing RevOps Team
A conversation with Roman Gruhn, VP of RevOps at Multiverse.
“You’re not hired to keep things the same. You’re hired to lead change—deliberate, strategic, and scalable change.”
— Roman Gruhn, VP of Revenue Operations, Multiverse
Revenue Operations (RevOps) has become more than a supporting function—it’s the strategic backbone of go-to-market (GTM) alignment. Yet, building and scaling a RevOps function at an enterprise level is a complex task, often underestimated. It requires more than just systems knowledge or analytical ability. It requires leadership, empathy, and adaptability.
In this episode of The Revenue Lounge, we spoke with Roman Gruhn, VP of RevOps at Multiverse. With a background that spans computer science, management consulting, and GTM strategy at high-growth companies like MongoDB and Remote, Roman brings a rare mix of technical depth and business acumen.
This blog distills his insights into a detailed, actionable guide for enterprise RevOps leaders navigating complexity, change management, cross-functional alignment, and AI integration.
Roman's Career Arc: From Code to CRO Support
Roman began his journey in computer science but quickly realized his interests were broader. His transition into management consulting helped him develop an eye for process design and organizational effectiveness—skills that proved invaluable when he entered the SaaS world at MongoDB.
“When I joined MongoDB, I didn’t know much about sales. But I brought a consultative mindset and a systems-thinking approach that helped me learn fast,” Roman recalls.
At MongoDB, he moved through roles in strategic sales support, Chief of Staff for the CRO, and eventually into leading sales operations and sales tech—building operational infrastructure for a company in hypergrowth mode. Later, at Remote, he was tasked with rebuilding and maturing the RevOps function to support rapid scale.
Now at Multiverse, Roman is applying those lessons in an exciting domain: upskilling the workforce for the AI age.
Step 1: Understand Before You Act
When stepping into a new RevOps leadership role, Roman’s first instinct is not to make immediate changes.
“You have to sit on your hands at first. Don’t assume. Just listen. Every meeting is a puzzle piece.”
He compares the early days to solving a 1,000-piece puzzle. You gather fragments through conversations, team meetings, and documentation, slowly forming a picture of how the GTM engine operates—and where it’s breaking down.
90-Day Discovery Framework
| Phase | Key Actions |
|---|---|
| Weeks 1–4 | 1:1s across GTM, product, finance, delivery. Map existing systems and flows. |
| Weeks 5–8 | Identify major friction points and redundancies. Use AI to theme-sort notes. |
| Weeks 9–12 | Validate hypotheses. Prioritize initiatives. Create early roadmap. |
This structured discovery approach is critical—especially in enterprise environments where systems are deeply entangled and historical decisions carry invisible context.
What an Enterprise-Ready RevOps Function Looks Like
Roman emphasizes that effective RevOps requires deliberate design—not just reactive firefighting. He breaks down the core pillars of a scalable RevOps framework into five focus areas:
5 Pillars of Scalable RevOps:
1. Strategy & Planning: Fiscal planning, territory modeling, quota grameworks.
2. Systems Architecture: CRM scalability, automation, permissioning, compliant.
3. Analytics & Insights: Forecasting, KPI dashboards, attribution modeling
4. Process Optimization: Deal desk operations, lead-to-revenue process, lifecycle automations
5. Project Delivery: Strategic rollouts, cross-functional projects, system launches
“You’re not just building for today. You’re building for repeatability and future scale,” Roman notes.
This framework helps RevOps leaders understand where to invest resources, hire talent, and measure impact.
One of the most debated questions in RevOps is whether to hire generalists or specialists. Roman’s take? It depends on scale.
“When you’ve got 20 sellers, you need utility players. When you’ve got 150+, you need dedicated owners across planning, systems, analytics, and more.”
📊 Org Design by Sales Team Size
| Sales Headcount | RevOps Team Structure |
|---|---|
| 10–30 | 1–2 Generalists handling all ops functions |
| 30–80 | Add dedicated owner for systems or analytics |
| 80–150+ | Specialists across strategy, data, systems, enablement |
| 150–300+ | Regional pods + Centers of Excellence (COEs) |
Roman also encourages internal mobility within the team. For example, someone in a systems role might rotate into analytics or planning—ensuring talent remains agile and engaged.
Hiring the Right People: It’s About Mindset
Roman is clear: technical skills matter, but soft skills are non-negotiable. RevOps professionals operate in a dynamic environment where agility is a must.
✅ Must-Have Soft Skills in RevOps
Curiosity: A hunger to explore new tools, processes, and possibilities.
Coachability: Willingness to learn—and unlearn.
Conviction with humility: Bring strong opinions, but adapt when data says otherwise.
Energy & Drive: RevOps is high-volume, high-context. Grit matters.
Pragmatism: Know when “good enough” is good enough.
“You want people who can think big—but also say, here’s a V1 that gets us moving,” Roman explains.
How Roman Measures RevOps Success
Aligning Metrics Across GTM
Unlike sales or marketing, RevOps doesn’t own a revenue number. But Roman has developed a layered KPI framework to track team performance and impact.
Roman also looks at qualitative indicators, such as whether GTM leaders see RevOps as a blocker or enabler. “You don’t want to be the function of ‘No.’ You want to be the function of ‘Here’s how.’”
One of the biggest pitfalls in enterprise GTM teams is siloed metrics. Marketing chases MQLs. Sales chases bookings. CS chases renewals. RevOps must drive shared understanding.
“Everyone says they’re aligned. But when you peel back the onion—they’re not. They’re just measuring their own kingdoms.”
Roman recommends creating a centralized “metric dictionary” that includes definitions, owners, and dependencies to reduce ambiguity and finger-pointing.
AI in RevOps: From Doers to Conductors
AI is no longer a nice-to-have. It’s central to the future of RevOps. Roman sees it transforming both how RevOps operates and how GTM teams execute.
“We’re shifting from playing every instrument to being the conductors—coordinating systems, signals, and actions.”
⚙️ Where AI Can Help in RevOps
| Function | AI Application Example |
|---|---|
| Data Analysis | Auto-detect patterns in territories, pipeline movement |
| Forecasting | Smart modeling using historical + third-party signals |
| Dashboards | AI-generated weekly insights: “These are the anomalies to review today” |
| GTM Enablement | AI assistants writing prospect research briefs or rep coaching summaries |
Roman encourages his team to build the “AI muscle”—experimenting with tools even if they aren’t perfect yet.
“You won’t get it all right. But sitting on your hands is worse. Experiment, adapt, and evolve.”
Should Marketing Ops Roll into RevOps?
It’s a hot topic. Roman believes the answer is: it depends.
“If most revenue is inbound, it may make sense. If it’s heavily outbound, they can stay separate—but need shared goals.”
Whether centralized or not, communication is non-negotiable.
“Structure doesn’t guarantee alignment. Communicate relentlessly—upstream, downstream, cross-stream.”
Final Words: Think Long-Term, Act Short-Term
Roman’s parting advice is simple but powerful:
“Don’t wait for perfect. Build for change. Stay curious. And always start with the why.”
As AI reshapes GTM strategies and orgs become more complex, the need for strategic, scalable, and human-centric RevOps leadership has never been higher. Leaders like Roman Gruhn are setting the benchmark—not just for how to build RevOps—but how to evolve it.
Want to hear more stories from revenue leaders? Subscribe to The Revenue Lounge podcast to never miss an episode!
More Resources

How to Strategically Engage and Conquer Buying committees
Delve into the complexities of engaging buying groups and unveiling strategic approaches to conquer the challenges that arise. In Sales, the key to accelerating deals lies in understanding the nuances of buying group dynamics.

Top 15 Guided Selling Tools for 2025
Top 15 Guided Selling Tools for 2025 RevOps 10 min Imagine that you are planning to build a new house but are unsure where to start. You have a basic idea of what you want but are not an expert in home construction or design. In such a situation, you would need a skilled architect who understands your needs, preferences, and budget and then guides you through designing your dream home. The architect would help you make informed decisions about your new home’s design, materials, and features. Similarly, a guided selling tool uses customer data and sales expertise to help customers navigate the purchasing process and make informed decisions. It can provide personalized recommendations based on the customer’s needs and preferences, answer questions, and offer advice to help them choose the right product or service. What is Guided Selling? Guided selling is a strategy involving a structured approach to lead potential customers through the sales process. It is the process of analyzing current sales, historical sales, and customer data to help sales reps provide tailored product recommendations to customers and increase the likelihood of conversion. Let’s say you are shopping for a new laptop. You visit a website that offers guided selling, and you’re prompted to answer a series of questions. The questions might include things like: What will you primarily use the laptop for? Do you need a large screen or a lightweight design? How important is battery life to you? What is your budget? Based on your responses, the website would then recommend a few different laptops that meet your needs. It might provide detailed information about each laptop, such as the processor, RAM, and storage capacity, as well as customer reviews and ratings. The website might offer additional guidance, such as recommending accessories or providing information on warranties and support. Throughout the process, the focus is on helping you make an informed decision based on your unique needs and preferences. Guided selling can be particularly effective for complex or high-value products or services where customers may require more personalized guidance and support to make informed purchasing decisions. By providing a more consultative sales approach, guided selling also helps to establish long-term customer relationships. How Does Guided Selling Work in B2B SaaS In B2B SaaS, guided selling typically involves a sales representative or a customer success manager who guides the customer. The process usually begins with the customer expressing their needs and goals and the guide using that information to suggest relevant products or services. The guide may use various tools, such as a software demo, to help the customer understand the features and benefits of each option. In addition, guided selling often involves providing educational resources to the customer to help them better understand the product or service and how it can help them achieve their goals. This may include case studies, white papers, or other content that provides valuable insights into the benefits and use cases of the product. Let’s have a look at the guided selling process in detail: The Process of Guided Selling Tools The guided selling process is a customer-centric approach to sales that involves guiding potential customers through the buying process by providing personalized recommendations, advice, and support. The following are the general steps involved in a typical guided selling process: 1. Gathering customer information The first step of the process involves collecting data on the customer’s needs, preferences, budget, and any other relevant information that can help the sales process. 2. Identifying customer pain points In this stage, the sales team uses the information gathered in the previous stage to identify the customer’s pain points or areas of concern.This is typically done through a series of questions or a needs assessment. 3. Providing product recommendations Based on the customer information and pain points identified, the sales team provides recommendations on the products or services that best meet the customer’s needs. 4. Presenting solutions At this stage, the sales team presents the recommended products or services to the customer and explains how they address the customer’s pain points. The sales representative provides information about the recommended products or services, including their features, benefits, and pricing. 5. Handling objections If the customer has any objections or concerns, the sales team addresses them and provides additional information or alternative solutions as needed. 6. Closing the sale Once the customer is satisfied with the recommended product or service, the sales team closes the sale by facilitating the purchase process. 7. Follow-up and customer support After the sale is complete, the sales team provides follow-up support to ensure the customer is satisfied with their purchase and offers any additional assistance or support as needed. Examples of Guided Selling Tools in Businesses Here are some examples of techniques of guided selling tools: 1. Automate sales playbook To ensure consistent performance, sales playbooks should be automated. Guided selling relies on a solid foundation of methodologies, blueprints, and plays that facilitate the sales process. It’s important to choose a solution that simplifies the playbook for sellers, allowing them to follow the plan and consistently advance deals easily. 2. Identify specific needs In some situations, customers may need a clearer idea of what they are looking for when they visit your website. In such cases, a brief questionnaire can be used to determine and guide their specific requirements. For instance, if you run an online clothing store, you could ask customers questions about their preferred fit and fabric to steer them toward products that best match their preferences. This approach can increase the likelihood of a purchase by helping customers make informed decisions based on their needs. 3. Real-time response For a guided selling software to be effective, it needs to be adaptable and flexible, able to react to changing circumstances in real time. At a fundamental level, ensuring that sales representatives remain attentive to communication and other sales activities can reduce the time it takes to close deals and result in higher revenue velocity. In other cases,
A 30-60-90 Day Guide for First-Time Directors of Revenue Operations
A 30-60-90 Day Guide for First-Time Directors of Revenue Operations RevOps 10 min Starting a new job as a Director of Revenue Operations is an exciting opportunity to make a significant impact on a company’s revenue growth. To ensure success in this role, it’s essential to have a strategic plan that guides your actions during the crucial first three months. Here’s a 30-60-90 day plan that will help you strategically manage revenue operations and drive sustainable growth. We recently spoke to Hassan Irshad, Director of RevOps at FEVTutor. He shared his approach to this powerful framework, demonstrating how each phase (30, 60, and 90 days) builds strategically upon the last to deliver alignment, trust, and sustained improvement. By breaking down complex goals into achievable milestones, the 30-60-90 day approach empowers RevOps leaders to initiate meaningful change without overwhelming teams. For all the RevOps leaders, it’s a way to approach change with purpose, driving measurable impact and laying the groundwork for long-term success. The 30-60–90 day framework must be an indispensable tool and here is how you can implement progressive, sustainable growth strategies from day one. First 30 days for a Director of Revenue Operations The purpose should be to gather insights and understand the organization, especially the needs and challenges of different teams. 1. Goals for first 30 days: i. Meet Key Stakeholders Meet with cross departmental teams like Finance, HR, and Sales to understand their goals, challenges, and priorities. ii. Document Everything Create a “lay of the land” document summarizing findings on different team goals, challenges, and processes. 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 further exploration with actionable improvements with the primary task being bringing the teams into sync. 1. Ways to bring your teams together i. Encouraging cross-team collaboration by addressing silos and ensuring all teams work toward shared quarterly or company-wide goals. ii. By creating alignment, you help teams see RevOps as a support system rather than an enforcer. This keeps communication channels open and creates buy-in. iii. Based on your findings, introduce controls wherever needed to improve workflow. Example: If close dates aren’t being recorded properly, this could skew reports. Meet with sales, identify the root cause (e.g., manual data entry that is taking too much of a reps’ time), and provide solutions or tools to make their tasks easier. Ensure that controls are practical and developed with the trust built in the first 30 days. Foster internal consensus within teams so that these improvements are adopted seamlessly. 2. Navigate Organizational Politics (i) Barrier Removal Larger organizations may have internal politics or ingrained processes that resist change. Find an internal “sponsor” who trusts and supports RevOps initiatives and can authorize actions to navigate any resistance. (ii) Trust and Consistency As you implement changes, make sure your efforts consistently demonstrate how RevOps can make work easier and more efficient for everyone. 3. Evolving the Tech Stack (i) Assessing Tech Needs If tools aren’t fully integrated (e.g., a tool not writing data back to the CRM), identify their gaps and consider evolving the tech stack. (ii) Holistic View Use insights from the discovery and alignment phases to start envisioning necessary tech improvements that align with company goals. Beginning of the 90-Day Phase: Vision and Execution This phase, described as “Vision and Execution,” involves shaping and executing a strategy based on insights gathered from the discovery and alignment phases. a. Roadmap Creation Create a roadmap covering the next two quarters, focusing on long-term, high-impact changes that align with business goals. Use learnings based on stakeholder needs, organizational goals, and the findings from the first 60 days i. Set Priorities Collaborate with end users (Sales, Marketing, Customer Success) to understand their pressing needs and align the roadmap with these needs. ii. Strategic Execution Prioritize initiatives that will have immediate revenue impact or