The short answer
RevOps, short for revenue operations, is the function that runs marketing operations, sales operations and customer success operations as one system: one funnel from first touch to renewal, one data model in one CRM, and one set of metrics that every team reports against. A RevOps team owns the CRM and its configuration, data quality, lead and account routing, reporting, the sales and marketing tool stack, and the forecast. It does not sell or run campaigns; it makes sure the people who do work from the same records and the same definitions. In a B2B company of 20 to 200 people, the need usually shows up as arguments about whose numbers are right. The first 90 days go to an audit, shared definitions, a clean company key and one dashboard, in that order.
The definition follows common usage in B2B sales and marketing teams, and this page cites no market statistics. Details of the Bizzy integrations come from bizzy.ai/integrations, read on 1 October 2026.
What revenue operations brings together
Most companies grow three operations roles without planning it. Marketing operations runs the automation platform, the forms and campaign attribution. Sales operations runs the CRM, territories, quotas and the pipeline report. Customer success operations, where it exists, runs onboarding, renewals and the health score. Each is right inside its own tool.
RevOps puts those three under one owner and one set of agreements.
Area | Separate ops teams | With RevOps |
|---|---|---|
Funnel | Marketing counts leads, sales counts deals, success counts renewals, with gaps at every handover | One funnel from first touch to renewal, with an agreed definition and owner for every stage |
Data model | Marketing automation, CRM and support tool each hold their own copy of the company | One company record in the CRM, with the other tools syncing to it |
Metrics | Each team reports its own conversion rate on its own definition | One scorecard, with every metric defined once |
Tools | Bought by whichever team needed them | One stack with a named owner and a check before anything is added |
The point is that a lead, an opportunity and a customer mean the same thing in every report. Which metrics to track and how to define them is covered in the sales KPIs that matter.
What a RevOps team owns
CRM. The object structure, fields, pipeline stages, permissions and the rules on who may change them. Choosing the system comes first; the CRM comparison for Belgian SMEs sets price and fit side by side.
Data quality. Which field is the company key, how duplicates are merged, which external sources may write to which fields and how often records are refreshed.
Routing. Who gets an inbound lead, a new account or a renewal, by territory, size or language, and how fast.
Reporting. The weekly dashboards, with one version of each number.
Tooling. The stack around the CRM, from marketing automation and sequencing to enrichment, and the integrations between them.
Forecasting. The method, the cadence and the stage probabilities, checked against what actually closed.
Targets, strategy and the choice of market stay with leadership; RevOps turns them into systems. See how to build a go-to-market strategy.
When a company of 20 to 200 people needs it
Below about 20 people, one founder or sales lead usually holds the whole funnel in their head, and a few hours a week of CRM administration is enough. Between 20 and 200, three things change: marketing, sales and customer success become separate teams with separate managers, a second or third tool starts holding customer data, and leadership asks for a forecast it can budget on.
The signs that someone needs to own this:
Marketing and sales report different numbers for the same month, and the meeting is spent on whose figure is right.
Reps keep their own spreadsheets because they do not trust the CRM.
Inbound leads wait a day or more because nobody is sure whose they are.
The same company sits in the CRM three times: under its trading name, its legal name and a typo.
The forecast is a number the sales lead adjusts by feel.
The first step is rarely a team. For example, a Ghent software company with 60 staff might give one person from sales or marketing operations the RevOps remit and the authority to change the CRM, with a monthly meeting of the three team leads. A second person follows when the requests outgrow the first.
The first 90 days
Rebuilding the CRM in week two does more harm than good. The order below settles definitions before systems, and data before dashboards.
Weeks | Focus | What to do | Done when |
|---|---|---|---|
1 to 2 | Audit | Interview the three leads, list every tool holding customer data, count duplicates and empty key fields | A one-page problem list, ranked by revenue impact |
3 to 4 | Definitions | Agree in writing what a lead, an opportunity, each stage and a customer are, and who owns each stage | The funnel definitions are signed off by all three leads |
5 to 6 | Company key and deduplication | Make the company identifier a required field, fill it in and merge duplicates on it | Every active account has the key and no key appears twice |
7 to 8 | Routing and handovers | Write who gets which lead and account, and what each handover must contain | Inbound leads reach an owner automatically |
9 to 10 | Enrichment and refresh | Decide which fields come from external sources and how often they are refreshed | A written field policy and a first refresh run |
11 to 12 | One dashboard | Build the weekly scorecard on the agreed definitions and retire the old spreadsheets | Leadership reviews one dashboard, not three |
13 | Review | Compare the plan with what changed and set the backlog for the next quarter | A prioritised backlog for the next 90 days |
Data foundations: get the company key right first
Everything in that table rests on one decision: what identifies a company. The name does not; trading names, legal names and abbreviations all point to the same business.
In Belgium the answer is the enterprise number, the ten-digit identifier the KBO gives every registered company. It is unique, it survives a change of name or address, and for companies subject to VAT the VAT number carries the same digits with BE in front. Store it as ten-digit text so the leading zero survives, and accept numbers that start with 1, which the KBO has issued since September 2023. In the Netherlands the KVK number plays the same role. The format, the modulo 97 check and where to find the number are in the Belgian enterprise number explained.
Three decisions follow from the key, and RevOps owns all three:
Deduplication. Merge on the key, not the name, and decide which record wins when two disagree. The day-to-day routine of standards and validation is in data hygiene best practices for sales teams.
Enrichment. Decide which fields external data may fill, which it may overwrite and which it must never touch, such as notes and the contacts a rep added after a conversation. What B2B data enrichment can and cannot give you covers the match problem and the field rules.
Decay. Company records go stale as companies stop, move, change directors or change activity codes, and contacts go stale faster. Set a refresh cycle per type of field. How fast Belgian B2B data decays puts figures on it.
Weeks 9 and 10 are where a new RevOps owner often gets stuck, with hundreds of accounts whose company fields nobody wants to update by hand. Bizzy shows every Belgian company with its enterprise number, register data from the KBO, filed accounts from the National Bank of Belgium and publications from the Belgian Official Gazette. Its integrations with HubSpot, Salesforce, Pipedrive, Microsoft Dynamics 365, Teamleader Focus and Odoo push new companies and contacts or complete the records you already have, and for every mapped field you choose whether Bizzy overwrites the existing value or only fills what is empty. In HubSpot, Teamleader Focus and Odoo, existing records are matched on the enterprise number rather than the name, and new companies arrive with their number already on them. Companies in the Netherlands and other countries are covered through Creditsafe data.
Frequently asked questions
What does RevOps stand for? Revenue operations: the function that runs marketing, sales and customer success operations as one system, with one funnel, one data model and one set of metrics.
What is the difference between RevOps and sales ops? Sales operations supports the sales team only. RevOps covers marketing and customer success too, so definitions and data hold from first touch to renewal.
Does a small B2B company need a RevOps team? Not a team. From about 20 people, one person with the authority to change the CRM is usually enough.
What should RevOps do first? Audit the current state, agree the funnel definitions in writing, then fix the company key and the duplicates before building any dashboard.
Photo: the Minnewater in Bruges, Marc Ryckaert (MJJR), CC BY 3.0, via Wikimedia Commons