In today’s economy, many companies find their growth stalls because of operational friction, misaligned teams, and a lack of data-driven strategy. Efficient growth is a necessity, and the solution lies in building a strategic Revenue Operations function.
To explain this process, we sat down with Navin Persaud, VP of Revenue Operations at 1Password. Drawing from his journey from frontline sales to leading RevOps at a 1500-person company, Navin provides a clear blueprint for what an effective RevOps function looks like and how to build one. He emphasizes that a robust RevOps team does not just manage tools; it acts as the “truth-teller” that aligns the entire organization around a single, data-backed reality.
This article breaks down Navin’s expert framework for defining the scope, structure, and strategic priorities of a RevOps function, creating an operational hub for your go-to-market engine that drives predictable, scalable revenue.
Navin Persaud shared these insights on an episode of The Go-to-Market Podcast. Listen to the full conversation with host Amy Cook to dive deeper.
Defining The Scope Of A Modern Revenue Operations Function
A common mistake is to view RevOps as just an extension of sales support. According to Navin, a strategic Revenue Operations function has a much broader remit. He breaks it down into two core areas: the “front of house” analytics that serve the GTM team and the “back of house” systems that power it.
“Front of house is everything, forecast analysis, where the entire go-to-market org is our customers,” Navin explains. “Back of house is like, here are all the systems, here are all the data, all the integrations.” This dual focus ensures that RevOps serves both the immediate needs of revenue teams and the long-term systems required for sustainable growth.
What RevOps Should Own From Day One
When asked about the scope of his function, Navin provided a comprehensive list: “My remit includes the go-to-market analytics, territory management, sales incentive plans, the entire go-to-market tech stack, our partner operations function, and our deal desk function.”
This holistic ownership prevents the silos that plague many organizations. When territory management lives in one department, incentive plans in another, and analytics in a third, you create competing priorities and conflicting data. By consolidating these functions under a single RevOps umbrella, companies establish a single, reliable source for performance metrics and strategic decision-making.
Pay close attention to the deal desk function. Navin emphasizes that having a dedicated team ensures “everything’s clean as we go through it.” This operational rigor at the point of transaction prevents downstream problems in forecasting, commission calculations, and revenue recognition.
The ‘Truth-Teller’s’ Role In Go-To-Market Strategy
One of Navin’s most powerful insights concerns the relationship between RevOps and executive leadership. While the CRO and CMO set the GTM strategy, RevOps serves a different but equally critical function.
“I generally love working on providing like input to strategy, but at the end of the day, CMO, CRO feeds that strategy down so I can go execute it,” Navin explains. “I need clarity of vision and we’ll go make it happen.”
This positioning is deliberate. RevOps removes emotion from strategic discussions by grounding conversations in data. When sales leaders argue for more territory or marketing claims higher attribution, RevOps provides the neutral, numbers-driven perspective that keeps strategy anchored in reality rather than assumptions.
Why Sales And Marketing Alignment Starts With Unified Ops
The benefits of unified operations extend beyond efficiency. Navin points out that bringing sales and marketing ops under a single RevOps umbrella forces teams to align on a single set of metrics and a shared narrative.
“When it comes to the narrative, the performance of the business, you’ve interjected or inserted a truth there,” Navin notes. Instead of sales and marketing pulling in different directions, “they’re doing more of like this,” he says, bringing his hands together to illustrate alignment.
This structural change transforms how teams collaborate. When everyone operates from the same data and definitions, debates shift from “whose numbers are right” to “what should we do about it.”
A Practical Guide To Building Your RevOps Team
Understanding the need for RevOps is the first step; the next is building the team correctly. Navin offers clear, actionable benchmarks for companies ready to scale.
When To Make Your First RevOps Hire
The timing question comes up frequently, and Navin has a clear answer: invest in RevOps once you have product-market fit. “If you plan is, ‘you know what, my sales leader will sort of own that,’ or ‘my tech team will sort of own that,’ those are both flawed strategies,” he warns.
The reasons differ but are equally problematic. Sales leaders lack the neutrality required to make objective decisions about territories, compensation, and performance metrics. Tech teams, meanwhile, “will build something that’s perfect and no sales teams will want to use it.”
Waiting too long creates a different problem. RevOps becomes a “limiter on future growth” rather than an enabler. The operational debt accumulated during rapid scaling becomes increasingly expensive to address.
A Simple Ratio For Sizing Your RevOps Investment
Navin’s most actionable insight is his rule of thumb for team sizing.
“The ratio we operate under right now is around 10%. So 10% of the entire go-to-market org sits in rev ops.”
At 1Password, with a go-to-market organization approaching 500 people, this means a RevOps function of around 40 to 50 people. This ratio provides a tangible benchmark for leaders at any stage. A company with a 50-person GTM team should plan for approximately 5 RevOps professionals.
The Essential Traits Of A RevOps Professional
Beyond technical skills, Navin emphasizes the soft skills that make RevOps professionals effective. “You have to be humble and you have to be curious,” he says. “Ironically, those are traits I look for when I hire for people on the rev ops team.”
He specifically seeks candidates with “a servant leadership mentality, want to do good or want to do right.” This orientation matters because RevOps professionals must collaborate across departments, uncover hidden problems without creating defensiveness, and build trust with frontline teams who may initially view them with skepticism.
The RevOps Leader’s Playbook For Driving Predictable Growth
Once the team is in place, the RevOps leader must set the right priorities. Navin’s playbook focuses on agility, ownership, and transforming data into clear actions that guide the business.
Why Your GTM Tech Stack Must Live Within The Revenue Operations Function
Navin takes a strong stance on tech stack ownership: “Until you really have to, leave your go-to-market tech stack with your rev ops teams.” He acknowledges that “eventually companies reach the maturity or public nature where a separation of duty becomes necessary,” but during growth phases, this ownership is essential.
The reason is agility. When RevOps owns the systems, the team can configure tools for pace and usability rather than abstract perfection. They can respond to changing business needs without navigating bureaucratic approval processes.
Embrace ‘Pace, Not Perfection’ To Avoid Analysis Paralysis
Speed matters more than perfection in a growing company. Navin frames this through a vivid analogy: “I think of pivoting as like an oil tanker in the ocean. It takes a while to turn that thing around.”
The cost of slow pivots is concrete. “You might have to change incentive plans, you might have to change territories, org structure. You only have 12 months in a year to get your number. And if you’re gonna lose two and three of those months in terms of a pivot, that’s a difficult loss to absorb.”
A RevOps function that moves quickly allows the business to test, learn, and adapt without losing months to a single change. This is where tools that accelerate planning become critical. Companies like Udemy have reduced planning time from months to weeks by prioritizing pace over perfection.
From Data Manager To Strategic Partner: Becoming The Source Of Truth
Navin’s origin story of analyzing baseball card stats as a child points to the ultimate goal of RevOps: becoming the source of truth that powers everything from weekly pipeline calls to annual strategic planning.
“They’re gonna tell you where all the hidden problems are,” Navin says of effective RevOps leaders. “They’re going to ensure the systems provide the data by which you can then generate the strategy.”
This transformation from a reactive data manager to a proactive strategic advisor requires clean systems, clear KPIs, and the ability to surface insights that leaders can act on. It demands moving beyond reactive reporting to proactive analysis that anticipates problems before they derail performance.
Final Thoughts
Building a high-impact Revenue Operations function is not about hiring another admin; it is about investing in the operational backbone of your go-to-market team. As Navin Persaud outlines, this means defining a broad scope of ownership, using the 10% rule to scale the team appropriately, and prioritizing pace over perfection.
By establishing RevOps as the data-driven “truth-teller,” leaders ensure their GTM engine runs efficiently and is built to accelerate toward future goals. The real question leaders should ask is not whether they can afford this function, but how long they can afford to operate without one. The companies that build this operational discipline will gain a sustainable, competitive advantage.
Ready to align your GTM plan with execution? See how Fullcast’s approach to Territory Management helps RevOps leaders design, manage, and automate their plans directly in Salesforce.
