RevOps Tooling As A Venture Category

Revenue operations tooling is one of the venture categories I spend the most time on, both as an operator who has run RevOps functions inside large companies and as an investor evaluating the next generation of products. The category is underserved relative to the size of the operating function it supports, and the founders building into it tend to be operators who lived the pain firsthand.

Why RevOps tooling matters now

The RevOps function has become a real C-suite-adjacent role inside most B2B SaaS companies. Five years ago it was a sales operations job. Today it is a strategic function that touches forecasting, pricing, deal desk, compensation, renewals, and operating cadence design. The tooling that supports the function has not kept pace.

Most RevOps teams stitch together a CRM, a forecasting tool, a deal desk approval platform, a comp management system, a customer success tool, and a handful of homegrown spreadsheets. Each component is decent. The integration between them is brittle, and the operator spends meaningful time keeping the system working instead of doing the strategic work the role demands.

What makes the category interesting

Three structural features make RevOps tooling an attractive venture category.

First, the buyer is sophisticated. RevOps leaders and their executive sponsors (CROs, CFOs) understand operating tools well enough to evaluate them on substance. The marketing-driven sales motion that dominates other SaaS categories matters less here. Product depth matters more.

Second, the contract economics are good. RevOps tools are sticky once integrated, multi-year contracts are common, and expansion within existing accounts is structurally available because the function keeps growing.

Third, the moat is built from workflow integration and data accumulation. Tools that sit at the center of how a RevOps team operates, with proprietary data about that team's pipeline, comp, forecast, or renewal patterns, become hard to displace.

What I look for in deals

The founders who win in this category share three traits.

Operating depth in the specific RevOps sub-function the tool serves. Founders who have run the function understand the workflow nuance that determines whether a tool is genuinely useful or marginally helpful.

Workflow integration as the moat strategy, not feature breadth. The best RevOps tools become the system of record for a specific operating process and resist horizontal expansion until the depth is genuinely earned.

Customer base composed of sophisticated RevOps buyers, not generalist operations teams. Selling to a real RevOps function is different from selling to a generic operations role, and tools optimized for the latter often struggle when they try to move upmarket.

What I avoid

Tools that claim to "automate RevOps" without addressing a specific workflow. RevOps is too broad to automate as a category. Tools that succeed pick a specific operating process and own it.

Tools whose differentiator is "AI-powered" without operating depth. AI is going to be embedded in every RevOps tool over the next three years. The question is whether the AI is doing meaningful work in the workflow or is a marketing layer on top of a more traditional product.

Why I keep coming back to this category

I have lived the operating pain RevOps tooling solves. I have seen the workflows up close, in companies of every size. The market is real, the problem is unsolved, and the founders building into it tend to be the kind of operators I want to back.

The category is not glamorous, but the businesses that win it will be among the most durable B2B SaaS companies of the next decade.