Your pipeline report says $2.4M. Your finance team says $1.1M. Your VP of Sales is "confident" about next quarter, but marketing is blaming sales for not following up on MQLs, and customer success is wondering why nobody told them about the upsell conversation that apparently happened three weeks ago.
If this sounds familiar, congratulations. You are running a normal B2B company with siloed operations. And you are probably about six months away from either a painful miss or an expensive replatforming project.
I have seen this exact scenario play out at more than 50 companies over the past decade. The fix is not another dashboard or another weekly alignment meeting. The fix is revenue operations.
But most of what you will read about RevOps online is recycled consulting jargon. This guide is different. I am going to explain what revenue operations actually is, what it looks like inside a real company, and when it makes sense to invest in it, based on what I have seen work (and fail) across B2B companies from 20 to 2,000 employees.
What is revenue operations, really?
Revenue operations is the practice of unifying your sales, marketing, and customer success teams under a single operational function. That is the textbook answer. Here is what it actually means.
Right now, your company probably has three separate operational worlds:
- Marketing ops manages your email platform, runs campaigns, and tracks MQLs. They own HubSpot Marketing Hub (or Marketo, or whatever you are using).
- Sales ops manages your CRM pipeline, builds reports for the VP of Sales, and fights with Salesforce configuration.
- Customer success ops (if you even have this) manages renewal tracking, health scores, and onboarding workflows. They own Gainsight or a spreadsheet.
Each team has its own tools, data definitions, and reporting. Marketing counts a "qualified lead" differently than sales does. Sales marks a deal as "committed" while finance calls it "best case." Customer success tracks churn in a spreadsheet that has not been updated since last quarter.
Revenue operations removes these silos. Instead of three ops functions reporting to three VPs, you create one ops team that reports to a single revenue leader (usually a CRO, COO, or CEO). This team owns the entire customer journey from first website visit to renewal.
The result? One definition of "qualified lead." One pipeline methodology. One source of truth for revenue data. One team responsible for making the handoffs between marketing, sales, and customer success actually work.
Sounds obvious when you read it. The execution is where 90% of companies get stuck.
Revenue operations vs sales operations: what is actually different?
This is the question I hear most often from founders, so let me be direct about it.
Sales operations is a subset of revenue operations. Sales ops focuses on making the sales team more effective: CRM configuration, territory planning, quota setting, compensation models, deal desk, and sales reporting.
Revenue operations does all of that, but also covers marketing operations and customer success operations. More importantly, RevOps owns the connective tissue between these functions.
Here is a concrete example. At a company I worked with last year (Series B, 120 employees, selling to mid-market), the sales team was using HubSpot, marketing had set up their own instance of HubSpot Marketing Hub, and customer success was tracking everything in Notion. Three systems. Three sources of truth. Three different answers to the question "how many customers do we have?"
Sales ops would have fixed the CRM configuration. RevOps fixed the entire data architecture, connected all three systems through HubSpot Operations Hub, built a unified customer lifecycle model, and created a single reporting layer that everyone trusted. Sales ops is plumbing for the sales team. RevOps is plumbing for the entire revenue engine.
Another way to think about it: sales ops asks "how do we close more deals?" RevOps asks "how do we generate, close, and retain more revenue?" The scope is different. The mandate is different. The organizational placement is different.
If you are running a company under 30 people, sales ops is probably enough. Once you pass 50 employees and start feeling the friction between marketing and sales (and especially once customer success becomes a real function), that is when the shift to RevOps pays off.
The revenue operations framework: what it looks like inside a company
A lot of people talk about RevOps frameworks in the abstract. Let me show you what one actually looks like. This is based on the framework we use at Ziel Lab when we build RevOps functions for clients.
Process layer
This is where you define how revenue is generated. You document every stage of the customer journey, from anonymous website visitor to closed-won customer to renewal.
In practice, this means:
- Lead scoring criteria that marketing and sales agree on (not marketing's version of lead scoring that sales ignores)
- A pipeline methodology with clear stage definitions and exit criteria
- Handoff protocols between marketing and sales (when exactly does an MQL become an SQL?)
- Customer onboarding workflows that pull data from the sales process
- Renewal and expansion playbooks that customer success actually follows
I worked with a Series A startup last year that had five different definitions of "pipeline" depending on who you asked. The CEO saw one number in the board deck. The VP of Sales saw another in HubSpot. The SDR manager had a completely different number in a spreadsheet. That is not a reporting problem. That is a process problem.
Data layer
The data layer is where most RevOps implementations fail or succeed. This is your single source of truth: one CRM, one data model, one set of definitions.
For most B2B companies in the 50-200 employee range, this means:
- HubSpot as your core CRM (or Salesforce, depending on your situation)
- Segment or a similar CDP for collecting product usage and website data
- Clay for data enrichment and prospecting intelligence
- A clean data model with standardized properties, lifecycle stages, and attribution
The biggest mistake I see? Companies that try to solve data problems with dashboards. If your underlying data is dirty, no amount of Looker wizardry will save you. RevOps starts with cleaning the data, standardizing the definitions, and building integrations that keep everything in sync.
At Ziel Lab, this is where we spend the majority of our time during a CRM implementation. Getting the data model right is 70% of the work. Everything else builds on top of it.
Technology layer
Here is where it gets fun for the nerds (myself included). The RevOps tech stack for a modern B2B company typically looks like this:
Core CRM: HubSpot is our default recommendation for companies in the 50-500 employee range. It handles marketing, sales, and service in one platform, which eliminates a huge category of integration headaches. We have written extensively about why HubSpot works for growth-stage companies.
Data enrichment: Clay is the best tool I have used for enriching and maintaining CRM data. It pulls from 100+ data providers, handles waterfall enrichment logic, and integrates directly with HubSpot. We use Clay to keep CRM data fresh, score accounts, and power outbound prospecting workflows.
Automation: n8n handles the workflow automation that sits between your tools. Things like "when a deal closes in HubSpot, trigger an onboarding sequence in customer success, update the billing system, and notify the account team." You can self-host n8n or use their cloud version. Either way, it replaces the duct tape of Zapier with something you can actually maintain. We build these automation workflows for clients regularly.
Analytics: HubSpot's native reporting covers 80% of what you need. For the remaining 20%, a BI tool like Looker or Metabase connected to your data warehouse gives you the custom analysis.
Product data: Segment collects product usage events and routes them to your CRM, analytics tools, and data warehouse. If you are running a product-led growth motion alongside sales, this is non-negotiable.
The mistake most companies make is buying too many tools too early. Start with HubSpot and Clay. Add n8n when you have workflows that need automating. Add Segment when you need product data in your CRM. You do not need 15 tools on day one.
People layer
RevOps needs at least one dedicated person. At the 50-100 employee stage, that is usually a RevOps manager who reports to the COO or CRO. At 100-200 employees, you probably need 2-3 people covering CRM administration, data analysis, and process design.
The first RevOps hire should be someone who understands both data and process. Technical enough to configure HubSpot workflows and write SQL. Strategic enough to sit in a revenue meeting and ask the right questions about pipeline conversion rates. This person is rare, which is why many companies outsource RevOps to a specialist firm while they build the internal muscle.
Before and after: what RevOps actually changes
Let me give you two real examples from companies I have worked with. Names and some details changed, but the situations are real.
Example 1: Series A SaaS, 65 employees
Before RevOps:
- Marketing generated 800 MQLs per month but sales only accepted 200 of them. The other 600 sat in a queue nobody looked at.
- Average lead response time was 47 hours. By the time an SDR called, the prospect had already talked to a competitor.
- Sales forecast accuracy was around 40%. The CEO had stopped trusting the pipeline report and was making decisions based on gut feel.
- Customer churn was 18% annually, but nobody could explain why because the data was spread across four different tools.
After RevOps (6 months in):
- Lead scoring was rebuilt with input from both marketing and sales. MQL volume dropped to 350 per month but sales accepted 310 of them.
- Lead routing was automated through HubSpot workflows. Average response time dropped to 4 hours.
- Pipeline stages were redefined with specific criteria. Forecast accuracy improved to 72%.
- Churn analysis became possible because all customer data lived in one place. They identified that 60% of churned customers had never completed onboarding, which led to a completely redesigned onboarding process.
The revenue impact: pipeline-to-close rate went from 12% to 23%. Annual churn dropped from 18% to 11%. The CFO started trusting the board deck again.
Example 2: Series B marketplace, 140 employees
Before RevOps:
- Three separate CRM instances (yes, really). Sales used Salesforce, marketing used HubSpot, partnerships used Pipedrive.
- Nobody could answer "what is our customer acquisition cost?" because attribution data did not connect across systems.
- Sales spent 8 hours per week on manual data entry and reporting.
- Customer expansion revenue was invisible. CS tracked upsells in a Google Sheet shared with nobody.
After RevOps (9 months in):
- Consolidated into HubSpot with custom objects for their marketplace model. Took three months to migrate and clean the data.
- Built a unified attribution model using Segment data flowing into HubSpot. First time the company could see true CAC by channel.
- Automated CRM data entry using Clay for enrichment and n8n workflows for syncing. Sales admin time dropped from 8 hours to 2 hours per week.
- Expansion revenue was tracked alongside new business. Turns out, expansion was 40% of total revenue, and nobody had been optimizing for it.
When to hire vs outsource RevOps
This is where I am going to be self-serving but also honest.
Hire internally when:
- You have a clear RevOps strategy and just need someone to execute it
- You are past 150 employees and need full-time, embedded ops support
- Your tech stack is stable and you mainly need optimization
- You have the budget for a $120K-180K hire (the going rate for a good RevOps manager in 2026)
Outsource when:
- You need to stand up RevOps from scratch and lack internal expertise
- You are going through a CRM migration or major tech stack change
- You need specialized skills (HubSpot architecture, Clay implementation, automation engineering) for a defined project
- You want to move fast. An experienced consultancy can do in 8 weeks what takes most internal hires 6 months.
At Ziel Lab, most of our engagements fall into the second category. A company comes to us with a mess of tools and data, we build the RevOps foundation (CRM architecture, data model, integrations, automation), and then hand it off to an internal hire who maintains it.
The worst approach? Hiring a junior ops person and asking them to "figure out RevOps." I have seen this fail a dozen times. Architecture decisions made in the first 90 days shape everything after. Getting those decisions wrong means rebuilding in 18 months.
The honest case against RevOps
I should be transparent about when RevOps is not the right move.
If you are under 30 employees, you probably do not need a formal RevOps function. Your CEO or COO can own the ops work, and a well-configured HubSpot instance is enough infrastructure.
If your product-market fit is not established, investing in RevOps is premature. Fix the product first. Operations optimization on top of a broken product just helps you measure failure more precisely.
If your teams are not experiencing friction between marketing, sales, and customer success, do not create a problem to solve. Some companies run fine with separate ops functions until they hit 300+ employees.
RevOps is an investment. It requires budget (either for a hire or an external partner), executive sponsorship, and organizational willingness to change. If you do not have all three, wait until you do.
How to get started with RevOps: the first 30 days
If you are convinced RevOps is the right move, here is what the first month looks like:
Week 1: Audit your current state. Map every tool your revenue teams use. Document how data flows between them. Interview your sales, marketing, and CS leaders about their biggest operational pain points.
Week 2: Define your data model. What is an MQL? What are your pipeline stages? How do you define churn? Get marketing, sales, and CS in a room and do not leave until you have written definitions everyone signs off on. This is harder than it sounds.
Week 3: Pick your core tools. If you do not have a CRM, start with HubSpot. If you have one but it is a mess, plan the cleanup. Identify the 2-3 critical integrations you need.
Week 4: Build the first workflow. Pick one painful handoff (usually the MQL-to-SQL handoff) and fix it end to end. Define the criteria, build the automation, create the reporting. Show the company a quick win.
If that sounds like a lot, it is. That is why many companies bring in a RevOps partner like Ziel Lab to accelerate the process.
FAQ
What does a revenue operations team actually do day to day?
A RevOps team manages CRM configuration, builds reports and dashboards, designs workflow automations, manages data quality, and runs cross-functional process improvements. A typical week might include fixing a broken lead routing rule, building a board-level pipeline report, and working with marketing to improve lead scoring. It is part analyst, part systems administrator, part process consultant.
How is RevOps different from just having a good sales ops person?
Sales ops focuses on the sales team. RevOps covers the full revenue cycle from marketing through customer success. The big difference is ownership of the handoff points. Sales ops optimizes within sales. RevOps optimizes across all revenue functions. The practical impact is that a RevOps person can fix the problem of "marketing sends leads that sales ignores" because they own both sides of that handoff.
What is the right time for a B2B startup to invest in RevOps?
Most companies feel the pain between 50 and 100 employees, or around Series A to Series B. The trigger is usually when you have distinct marketing, sales, and customer success teams that are starting to step on each other. If your board is asking questions about pipeline accuracy, if your CRO cannot get a straight answer on conversion rates, or if your teams are spending more time arguing about data than acting on it, you are ready.
Can you do RevOps without expensive tools?
Yes. You can start with HubSpot's free CRM, Google Sheets for reporting, and manual processes for handoffs. It is not about the tools. It is about the alignment, the data model, and the processes. That said, once you pass 50 employees, the manual approach breaks down fast. The cost of a proper tech stack (HubSpot, Clay, n8n) is usually less than the cost of the revenue you are losing to bad data and slow processes.
Should RevOps report to the CRO, COO, or CEO?
At companies under 100 employees, RevOps usually reports to the CEO or COO. This gives them authority to make changes across all revenue functions without getting stuck in political battles. At 100+ employees, a CRO is typically the right home, but only if the CRO genuinely owns marketing, sales, and customer success. If your CRO only owns sales, COO is the better reporting line. The principle: RevOps needs to report to someone with authority across all revenue teams, not just one.
Revenue operations is not a magic fix. It will not solve bad product-market fit, weak sales hiring, or a market that is not buying. What it will do is remove the friction between your revenue teams, give you data you can trust, and make it possible to execute the strategies you are building.
If you are running separate ops silos and feeling the pain of misaligned data and unreliable forecasts, let's talk about how to fix it. We have built RevOps functions for companies from seed stage to Series C, and we can help you figure out whether you need a full overhaul or just a few targeted fixes.