How to Build a RevOps Function from Scratch

Most companies build RevOps backwards. They hire the team, buy the tools, and then try to figure out what the function is actually supposed to do. That order of operations creates expensive chaos – and it’s more common than anyone in GTM leadership wants to admit.

Revenue Operations (RevOps) is the discipline of aligning your sales, marketing, and customer success teams under one operational umbrella. The goal is a single source of truth for pipeline data, consistent processes across the customer journey, and measurable accountability for revenue outcomes. Done well, it’s one of the highest-leverage structural decisions a growing company can make. Done poorly, it’s just another silo with a fancier name.

This guide is for operators building from zero – whether you’re a VP of Sales inheriting a mess, a first RevOps hire at a Series A company, or a founder who’s tired of their CRM being a graveyard of stale opportunities.

Step 1: Start With the Data, Not the Org Chart

Before you hire anyone or touch a tool, audit what you actually know. Pull your sales pipeline data and ask three honest questions: Where do deals get stuck? What’s the average sales cycle length by segment? And where is data being entered inconsistently or not at all?

That audit tells you where the operational gaps live. It’s not glamorous work, but skipping it means you’ll spend your first six months in RevOps solving the wrong problems with the wrong tools. Most early RevOps hires underestimate how broken the underlying data is – and overestimate how quickly automation can fix it.

From the audit, define your Ideal Customer Profile (ICP) operationally – not just as a marketing exercise. That means tagging every account in your CRM with ICP fit criteria and using that to segment your pipeline reporting. If you can’t tell the difference between an ICP deal and an off-profile deal in your data, your forecasting will always be unreliable.

Step 2: Build the Foundation Before You Build the Team

The foundation is three things: a defined revenue framework, a configured CRM, and a set of agreed stage definitions across go-to-market teams.

On the revenue framework – pick your core metrics and stick to them. For most B2B SaaS companies, that means tracking Annual Recurring Revenue (ARR), win rate by segment, Customer Acquisition Cost (CAC), and Net Revenue Retention (NRR). Those four metrics, reported consistently, tell you more about GTM health than a dashboard with forty widgets. Resist the temptation to add complexity before you have accuracy.

Stage definitions matter more than most people think. “Discovery” means something different to every AE if you don’t write it down. Define what has to be true – in terms of buyer actions, not seller feelings – for a deal to move from one stage to the next. Qualification frameworks like MEDDIC are useful scaffolding here, especially if you’re running enterprise sales motions. Enforce the definitions in your CRM. No exceptions.

Then configure your CRM to match the process you’ve defined – not the other way around. This is where most teams go wrong: they let the default CRM fields and stages dictate their process. Your CRM should reflect how your business actually sells, not how Salesforce or HubSpot assumes everyone sells. Check out our CRM Tools Directory if you’re still evaluating which platform fits your motion.

Step 3: Hire for the Right Skills in the Right Order

Your first RevOps hire shouldn’t be a strategist. It should be an operator – someone genuinely comfortable in a CRM’s back end, who can write a basic SQL query and has built a sales forecast model before. Strategic thinking matters, but not if the pipes are leaking.

Here’s a hiring sequence that actually works for companies between $2M and $15M ARR:

• Hire 1 – RevOps Manager or Senior Analyst: Owns CRM hygiene, pipeline reporting, and process documentation. This person is the foundation everything else sits on.
• Hire 2 – Marketing Ops specialist: Brings in attribution data and connects campaign spend to pipeline. Without this hire, marketing and sales will always argue about lead quality with no resolution.
• Hire 3 – Systems or Automation role: Handles tool integrations, workflow automation, and the technical debt that accumulates fast when you’re scaling.

Don’t hire a Head of RevOps before you have at least one of those foundational roles in place. A VP with no operator underneath them will spend all their time doing IC work and none of it on strategy – a waste of a senior salary and a fast path to burnout.

Common Mistakes That Set RevOps Back by Months

The biggest one: treating RevOps as a reporting function rather than a decision-support function. Reports are an output. The actual job is making sure the right people have the right information to make faster, better decisions about pipeline, headcount, and spend.

Closely related is building dashboards nobody uses. Every RevOps team has a graveyard of Salesforce reports that took two weeks to build and got looked at once. Before you build any report, identify who will use it, how often, and what decision it supports. If you can’t answer those questions, don’t build it.

Another common mistake is ignoring churn rate and expansion data in the RevOps remit. RevOps that only covers new business acquisition is half a function. Customer success data – especially around Customer Lifetime Value (LTV) and expansion revenue – belongs in the same operational model as your new logo pipeline.

Finally, don’t underestimate change management. You can design a perfect process and still watch it fail because AEs won’t update their CRM fields. Adoption is an operational problem, not just a training problem. Build compliance checks into your pipeline review cadence, and tie stage accuracy to forecast participation. People update their CRM when there’s a consequence for not doing it.

For more frameworks and step-by-step walkthroughs on building GTM infrastructure, browse our CRM Guides library. And if you want this kind of analysis in your inbox weekly, the CRM Daily Newsletter is worth subscribing to.

Start this week by pulling your stage-by-stage conversion data and finding the one drop-off point that’s costing you the most pipeline. Fix that first. Everything else can wait.