RevOps: how to connect marketing, sales and CRM in complex enterprise operations
RevOps (revenue operations) unites marketing and sales process, data, tools and metrics in a single funnel in the CRM. See how to structure the operation.

RevOps, or revenue operations, is the function that organizes marketing, sales and post-sale process, data, tools and metrics around a single definition of revenue. Instead of each department keeping its own funnel, its own spreadsheet and its own version of the result, revenue operations sets common rules and a shared system of record, almost always the CRM. The goal is for the company to answer, with the same number in every meeting, where revenue comes from, where it stalls and how much it costs to produce.
In large companies, buying is rarely simple. A B2B sale can involve procurement, legal, technology, finance and the user department, with months between the first contact and the contract. In B2B2C operations, the company sells to distributors, retailers or brokers who serve the end consumer, and revenue depends on both links. In these contexts, counting completed forms says little. The discussion between marketing and sales tends to get stuck on lead quality, when the underlying problem is that the departments do not use the same definitions, do not record the same events and do not look at the same periods.
What RevOps is and how it differs from marketing ops and sales ops
Marketing operations takes care of marketing tools, data and processes: automation, campaign setup, contact scoring rules. Sales operations does the same for sales: territories, quotas, forecasting and CRM hygiene. RevOps does not eliminate these functions. It places them under a single revenue architecture, with one funnel that runs across marketing, sales and customer success, and with one owner for the rules that apply to everyone.
In practice, RevOps can be a department of its own, a committee with leaders from each function or a responsibility of commercial operations. The format matters less than the mandate. Someone needs the authority to define stages, approve changes to the CRM and arbitrate data conflicts between departments.
What revenue operations takes on
- Process: the funnel design, the criteria for moving between stages, the agreements between departments and the rules for distributing accounts and contacts.
- Data: the CRM data model, deduplication rules, integration with marketing automation, ERP and billing, and the quality of the fields that feed the reports.
- Tools: selecting, configuring and administering the CRM and connected systems, with change control.
- Metrics: the official definitions of pipeline, conversion, cycle, forecast and acquisition cost, and the dashboard where they appear for the executive team.
- Enablement: training, playbooks and materials that allow salespeople, analysts and partners to use the process as it was designed.
A single funnel, with verifiable criteria at each stage
The first product of RevOps is a funnel definition that every department accepts. Each stage needs an observable entry criterion, an owner and a recorded, dated event. A stage defined by the perception of whoever fills it in changes meaning from team to team.
The best known model separates MQL (marketing qualified lead, a contact that has met an interest criterion defined by marketing) from SQL (sales qualified lead, a contact that sales has agreed to work after confirming commercial conditions). It works when contact volume is high and the purchase is driven by a few people. In complex sales, many operations replace the contact with the account as the unit of qualification: they assess fit with the ideal customer profile, interest signals from several people in the same organization and the existence of an identified need. This is the logic of account-based marketing, or ABM.
Whatever the model, the questions to answer are the same.
- Entry: what evidence allows an opportunity to be opened, and which account does it belong to?
- Qualification: which commercial conditions need to be confirmed, such as need, timing, budget and who decides?
- Progress: what event demonstrates progress beyond the salesperson's perception, such as a proposal sent or a meeting with the buying committee?
- Close: how do you record wins, losses and postponements, with the reason for each?
- Revenue: how do you reconcile contract, billing and recognized revenue, in line with the view the executive team expects?
Record the date of each transition, not just the current stage. Without that history, it is not possible to measure the time spent in each stage or to tell a healthy flow apart from stalled opportunities.
The SLA between marketing and sales
The service level agreement, or SLA, turns the handoff between departments into a measurable commitment. Marketing commits to a qualification criterion and a volume forecast. Sales commits to a time to first contact, a number of attempts and recording the outcome. The two departments agree on what happens to contacts and accounts that are not accepted: a return to nurturing with a recorded reason, not silent disposal.
The SLA works when it is measured in the CRM and reviewed regularly. A report of accepted accounts not contacted within the deadline, or rejected without a reason, solves more than the generic debate about lead quality.
CRM integration: the data model for complex sales
CRM integration starts with the data model, not the tool. In enterprise operations, four entities need to exist separately and relate to each other explicitly.
- Accounts: the buying company, with a hierarchy across the business group, business units and branches with purchasing autonomy. The consolidated group view must not erase regional differences.
- Contacts: the people, linked to one or more accounts, with job title, department and interaction history. A person can take part in more than one negotiation and change companies.
- Opportunities: each negotiation, linked to an account, with value, product, stage, transition dates and owner.
- Buying committee: the relationship between contacts and the opportunity, with each person's role in the decision, such as who uses the solution, who approves the budget, who assesses the technical risk and who signs.
Define stable identifiers, deduplication rules and owners for resolving conflicts, and preserve the change history. Automated integrations amplify both a good design and existing inconsistencies.
When digital behavior data come from several sources, a CDP (customer data platform) can unify profiles before sending them to the CRM. The quality of the signals coming from the website depends on data collection, and choices about server-side tracking and consent mode determine which events arrive and with what consent. Because the CRM stores personal data, each use needs a defined purpose and legal basis, under the LGPD (Law 13,709/2018, Brazil's General Data Protection Law). The law provides for the data subject's right to have incomplete, inaccurate or outdated data corrected and requires a record of processing operations, especially when they are based on legitimate interest.
RevOps metrics the executive team should track
- Pipeline: value and number of open opportunities by stage, segment and source, with the creation date of each one.
- Stage conversion: the share of accounts or opportunities that moves from one stage to the next, measured by entry cohort.
- Cycle time: days between the creation of the opportunity and its close, and the average time in each stage.
- Win rate: opportunities won over opportunities closed, separating losses from postponements.
- Forecast accuracy: the difference between the revenue forecast at the start of the period and the revenue realized.
- CAC payback: how many months of a new customer's gross margin it takes to recover the cost of acquiring that customer.
CAC payback calls for care. Customer acquisition cost (CAC) should add up marketing and sales in the same period, including people and tools, and not just media. Revenue should be converted into gross margin. The result depends on assumptions, such as the reference period and the way shared costs are allocated, which need to be written down. There is no universally good payback: the benchmark is the company's cost of capital, customer retention and growth strategy.
In long cycles, compare cohorts, not months. Comparing the revenue closed this month with the accounts generated in the same month distorts the reading, because part of what came in is still maturing. State the observation horizon and which groups remain open. Remember also that revenue associated with a campaign in the CRM shows recorded influence, not incremental revenue: that is what media incrementality tests are for.
Hypothetical example: a quarter read by cohort
The following numbers are illustrative. They do not represent market or client data.
A hypothetical industrial company records 400 marketing qualified accounts in a quarter. Sales accepts 120 of them (30%). Of those, 60 become opportunities with a proposal (50%), and 15 are won over the following nine months (25% of the opportunities). End-to-end conversion is 15 out of 400, or 3.75%.
In the same quarter, the company spends R$ 1.8 million on marketing and sales attributable to acquiring new customers. The cohort's CAC is R$ 120,000 per customer. If each new customer generates, on average, R$ 10,000 in gross margin per month, the payback is 12 months. If the analysis had considered the 5 accounts closed within the quarter itself, CAC would appear to be R$ 360,000, and the program would be judged by a number that measures the calendar, not the operation.
How to implement RevOps in a large company
- Map each department's current funnel, with the definitions each one uses and the reports the executive team receives.
- Name the owner of the revenue rules and the forum that approves changes.
- Write the single funnel, with an entry criterion, an owner and a recorded event for each stage.
- Review the CRM data model: accounts, hierarchy, contacts, opportunities and buying committee.
- Agree on the SLA between marketing and sales and create the report that tracks it.
- Connect marketing automation, CRM and billing with common identifiers and deduplication rules.
- Publish the official metric definitions and a single dashboard for the executive team.
- Train the teams and audit the quality of the records periodically.
Order matters. Integrating systems before agreeing on definitions automates the divergence. This work depends on marketing data governance: a field dictionary, owners for each source and change control.
Common RevOps mistakes
- Treating RevOps as a tool swap. A new CRM with the same divergent definitions reproduces the same conflicts.
- Measuring marketing by contact volume when the purchase is decided by a committee.
- Calculating CAC with media and leaving out people, tools and sales costs.
- Ignoring the indirect channel in B2B2C operations, when part of the revenue flows through distributors or retailers that do not appear in the CRM.
Frequently asked questions about RevOps
What is RevOps?
RevOps, or revenue operations, is the function that unifies marketing, sales and post-sale process, data, tools and metrics around a single definition of revenue. In practice, it means a single funnel, a common data model in the CRM and one owner for the rules that every department follows.
What is the difference between RevOps and a CRM?
The CRM is the system where accounts, contacts and opportunities are recorded. RevOps is the operation that defines how that system should be used: which stages exist, which criteria apply, who is responsible for each piece of data and which metrics the executive team tracks. A CRM without these rules piles up records that do not talk to each other.
Do MQL and SQL still make sense in complex sales?
They do when contact volume is high and the decision is concentrated in a few people. When the purchase involves a committee and long cycles, many companies qualify accounts instead of isolated contacts, combining fit with the ideal customer profile and signals from several people in the same organization. The key point is that each stage has a verifiable criterion.
Should marketing be evaluated on closed revenue?
Revenue is the central benchmark, but in long cycles it needs to be read by cohort and combined with progression signals, such as stage conversion and cycle time. It is also necessary to separate influence recorded in the CRM from incremental effect demonstrated by testing.
What is the first step to implement RevOps?
Agree on entities, stages and criteria before integrating tools. With the single funnel written down and an owner named, the CRM data model and the integrations gain a stable reference.
To bring this operation into planning, explore our Data area and the discussion on CDP (customer data platform).