RevOps in practice: how to stop losing revenue between marketing, sales and customer service

Marketing reports a record number of MQLs. Sales says the leads are weak and there’s nothing to close. Customer service reports that some new customers don’t really understand what they bought. Every department hits its KPIs, yet revenue stays flat. This is a typical symptom of a situation where sales and marketing management runs in three separate silos, with no shared owner of the funnel.

RevOps (Revenue Operations) brings order to this area. It combines the processes, data and tools of marketing, sales and customer service into one system accountable for revenue. Below you’ll find where revenue most often leaks between departments, how to set up sales and marketing management so it stops being a fight over attribution, and why implementing RevOps requires the discipline that project management provides.

Marketing and sales management: where revenue really gets lost in the pipeline

B2B companies lose the most revenue at handoff points. A lead moves from marketing to an SDR, then to an AE, and after the contract is signed, to customer service. At each of these stages the owner changes, and often so does the definition of what a good lead actually is.

A model example: marketing treats anyone who downloaded an e-book and has the word “manager” in their job title as an MQL. The SDR qualifies based on BANT, the AE based on whether the client has a real problem and budget this quarter. A sales specialist sees fifty new leads in the CRM, calls all of them and books six meetings, two of which make sense. Marketing reports success, sales reports wasted time, and the pipeline swells with opportunities that should never have been there. The problem only surfaces at forecasting.

In this setup, sales process management comes down to firefighting. Sales reps waste time on leads with no potential, while marketing management optimizes campaigns for a metric unrelated to revenue. If sales management also evaluates reps solely on the number of calls, nobody has an incentive to reject weak leads. RevOps addresses this directly: one definition of funnel stages, one set of sales and marketing KPIs calculated from the same data source, and one person responsible for the flow of leads between departments.

The second element is sales data analysis across the entire funnel, not just its final stage. A company that measures only AE win rates won’t see that the problem sits two stages earlier, in scoring. Lead quality management starts when someone looks at conversion between every stage and has the mandate to change qualification rules. Without that, every change becomes a negotiation between department heads. That’s why a RevOps implementation should be run from day one the way project management works: with a goal, a scope, an owner and a deadline. Companies that skip project management at this stage usually end up with a new dashboard and the old process.

Marketing management when digital marketing delivers traffic, not sales opportunities

B2B marketing teams have access to huge amounts of data: CTR, CPL, sessions, form conversions. Most of it, however, ends at the form. Digital marketing management optimizes what it sees in its own tools, and what it usually sees is the cost of acquiring a contact, not the cost of acquiring a customer.

The mechanics are simple (illustrative numbers). Campaign A generates 300 leads at a low CPL, campaign B generates 40 leads at a high CPL. On the marketing dashboard, A wins. But if campaign A produced no sales opportunities and B produced eight, then A drives up CAC, eats SDR time and clutters the CRM. Without connecting campaign data to funnel outcomes, digital marketing management will consistently shift budget in the wrong direction.

In a RevOps model, digital marketing is accountable for its contribution to pipeline and revenue. That changes how planning works: e-marketing management starts by asking which segments and channels bring opportunities that close within a reasonable cycle, and only then calculates cost per lead. Managing digital marketing without this information is guesswork with nice graphics.

Companies that sell part of their offer online face a similar problem. Online sales management and e-marketing management often sit with one team, while sales to larger clients is handled by a separate department. The e-commerce specialist sees the cart and store conversion, the sales rep sees a large client who made a trial purchase online three months earlier. If this data doesn’t come together in one system, nobody knows which channel actually opened the relationship. Digital marketing management should therefore track the whole account, not a single form. Connecting this data is a separate task that requires the same discipline as IT project management: a map of sources, an integration owner and testing.

Building a marketing strategy for pipeline, not reach

In many B2B companies, building a marketing strategy starts with channels: more LinkedIn this year, webinars, maybe a podcast. In a RevOps model, the order is reversed. The starting point is the deals won and lost over recent quarters: who bought, how long the cycle took, which source brought the first contact, and at which stage those who didn’t buy dropped out.

Only on that basis do market analysis and marketing research make sense. A Marketing Researcher can then check whether the segments that convert best in the funnel are large enough to grow on, and where there are similar companies that sales hasn’t reached yet. Building a marketing strategy without this analysis ends with a plan that looks good in a presentation but doesn’t give sales a concrete list of accounts.

The brand still matters. Brand management and corporate image management affect whether a cold call turns into a conversation or a hang-up, and whether the company makes it onto the client’s shortlist at all. The same goes for corporate social responsibility: with large corporate clients it can be a real criterion in the purchasing process, not just a section in the annual report.

Building a marketing strategy should run in parallel with sales strategy planning. If sales plans to enter a new segment next year while marketing budgets for existing customers, the misalignment will show up in the first quarter. The minimum is a shared planning calendar and shared ICP assumptions, and lead quality management must rely on the same criteria on both sides. The plan itself is best prepared the way project management works, with a timeline and checkpoints. Good marketing strategy work ends with a list of accounts and segments that marketing and sales work on together.

Customer service as the third leg of RevOps that revenue teams forget about

In many companies, RevOps ends when the contract is signed. Marketing and sales jointly track the pipeline, while whatever happens to the customer afterwards goes to another department, with a different system and different goals. Meanwhile, in a subscription model or with repeat orders, a large share of customer revenue comes after the first transaction.

Customer service holds data the other departments lack: why customers churn, which features are confusing, which sales promises don’t match reality. A customer service specialist is often the first to notice that a given segment regularly leaves after six months. If that information doesn’t make its way back to marketing, the company keeps acquiring exactly the customers it can’t retain, and pays for it with rising CAC.

This is where customer relationship management comes in, in a broader sense than just the tool. The customer’s history, from the first campaign touchpoint to service tickets, should live in one place and be available to anyone who talks to them. Relationship marketing in B2B works only when communication to existing customers is based on what is actually happening on the account.

An example: a client reports three implementation issues within a month, and in the same week receives a license expansion proposal from their sales rep. Marketing and sales management that can’t see customer service data regularly produces situations like this. Relationship marketing built on a full view of the account turns them into signals: an implementation issue triggers support, and the expansion proposal appears only after it’s resolved. In companies where online sales management also covers repeat orders, data on complaints and returns should influence who marketing targets with the next campaigns. Customer relationship management then becomes a shared process across three departments.

Bringing customer service into RevOps is usually the hardest stage, because it changes the processes of a team that has so far been measured mainly on ticket response time. Here project management has a very practical dimension: you need to decide which customer service data goes into the CRM, who enters it and how quality management of those records will be monitored. Well-run project management also means customer service gets real influence over the ideal customer definition, not just extra fields to fill in.

Implementing RevOps as a project: who owns the process, the data and lead quality

A failed implementation usually looks similar. The board decides the company is “moving to RevOps”, someone gets a new title, an additional tool is purchased, and six months later the processes look exactly the same as before. Three things are missing: a mandate to change cross-departmental processes, an implementation plan and measurable success criteria.

That’s why RevOps requires the approach that project management provides. The implementation touches marketing, sales, customer service, finance and IT, and each of these teams has its own priorities. Project management organizes the dependencies: you can’t change scoring until marketing and sales agree on a lead definition, and you can’t agree on a definition without data on conversion between stages. If a company is simultaneously changing its digital marketing management and connecting new lead sources, without a plan these two changes will block each other. Project management serves here as a risk control tool. The second pillar is quality management: of data, of leads and of the process of handing opportunities between teams.

Project management in RevOps: owners, dependencies and timeline

Project management in RevOps starts with scope. The first version should rarely cover everything at once. It’s more sensible to pick one handoff point, most often MQL to SQL, and build shared definitions, SLAs and reporting around it. Only then can the project be extended to the post-sale stage.

A practical breakdown of the implementation into stages usually looks like this:

1. Audit of the current funnel: stage definitions, data sources, conversion between stages, places where leads get lost.
2. Agreement on shared definitions and SLAs between marketing, sales and customer service.
3. Data cleanup and CRM configuration for the new definitions.
4. A shared dashboard and review cadence: weekly for operations, monthly for the board.
5. Extension to customer service, retention and upsell.

Each of these stages needs a single owner. In practice, project management in RevOps most often fails because a stage is owned by “the team”, which means nobody. The second trap is technical dependencies. A change to a website form requires a developer, CRM integration requires an administrator, and digital marketing management has to adapt campaigns to the new fields. If the timeline doesn’t account for this, the project will get stuck on a stage that took a week on paper.

Distributed teams are a separate challenge. If sales operates in several countries and marketing is centralized, communication in a multicultural team becomes part of the project. The same notion of a “qualified lead” means confirmed budget in one country and readiness to talk in another. Project management in this setup requires written definitions with examples, not general agreements from a meeting.

Short iterations work well for the timeline. Project management based on cycles of a few weeks lets you check whether the new definitions actually improve conversion before the company rebuilds the entire funnel. This kind of project management also gives sales and marketing quickly visible results, which directly affects the engagement of both teams.

Quality management of data in CRM systems

CRM systems show exactly what the team puts into them. If sales reps update opportunity stages once a month, before meeting their manager, the forecast in the first weeks of the month is fiction. If half the leads have no assigned source, marketing attribution is guesswork. If the database has three records of the same company, each assigned to a different rep, outbound sequences reach the same person three times.

Data quality management in RevOps is continuous work, not a one-off database cleanup. What works best is a combination of three elements: mandatory fields at key stages, automated rules (deduplication, source assignment, domain validation) and regular data reviews by a person responsible for its quality. Quality management without an owner quickly turns into a list of demands that nobody acts on.

Only on clean data do sales data analysis and meaningful sales KPIs make sense. Cycle length, stage-to-stage conversion or average opportunity value look credible in a report, but on polluted data they lead to wrong decisions. The company increases budget for a channel that only seemingly generates opportunities, or hires more sales reps because the pipeline appears overflowing. In the implementation plan, data cleanup should be a separate stage, and project management must allocate realistic time for it, not the weekend before a new dashboard goes live.

Roles in the revenue team: from the CMO to the sales and marketing analyst

In a RevOps model, roles don’t disappear, but what each of them is accountable for changes. The Chief Marketing Officer (CMO) stops being responsible for the number of leads and becomes responsible for marketing’s contribution to pipeline and revenue. That requires shared goals with the head of sales. If the CMO is bonused on MQLs and the Head of Sales on closed revenue, the conflict is built into the compensation system and no implementation will fix it.

The sales and marketing analyst, sometimes simply called a RevOps analyst, becomes a central role. They are responsible for metric definitions, data consistency and the reports the board relies on. In smaller companies this function is combined with CRM administration, in larger ones it’s a separate team.

The Brand Manager and people responsible for brand management fit into this setup indirectly. Their work affects how quickly a sales rep builds trust in the first conversation and how easily the company gets through a large client’s purchasing process. In RevOps, this impact is better measured by conversion in segments where the brand is recognized than by reach metrics alone.

On the sales side, sales team management changes. The manager stops looking only at activity: the number of calls, emails and meetings. They start looking at conversation quality, stage-to-stage conversion and loss reasons. This brings back skills that in many teams took a back seat after automation was introduced: sales and negotiation techniques and sales psychology. Automation can deliver a conversation to a sales rep, but it won’t have that conversation for them. If CRM data shows that deals regularly fall through at the negotiation stage, the team needs to work on how it applies sales and negotiation techniques. Another email sequence won’t fix it.

Each of these roles has its place in the implementation project. Project management in RevOps requires the CMO, the head of sales and the head of customer service to act as sponsors of the implementation, with the analyst as its operational owner. Without that division, project management comes down to coordinating meetings.

Sales and marketing management in a RevOps model: where to start

1. The first step is cheap and often the most revealing: mapping the current funnel from first contact to contract renewal, with a definition of each stage and an owner of each transition. Very often this alone reveals that marketing, sales and customer service use different names for the same things, or the same names for different things.
2. The second step is choosing one problem to solve in the first quarter. Usually this is the lead handoff from marketing to sales, because that’s where the effect is easiest to measure. Sales process management at this point covers a shared SQL definition, an SLA for contacting the lead and a regular review of leads rejected by sales, with feedback for marketing.
3. The third step is the owner. This can be a dedicated RevOps person, an analyst or, in a smaller company, one of the managers with a clearly defined mandate. They must have the authority to change processes on both sides, because sales and marketing management run by committee only works on paper.
4. The fourth step is cadence. RevOps works when the joint funnel review happens regularly and its decisions go into the plan. The approach that project management provides is useful here: a task list, owners, deadlines, progress reviews. Data and lead quality management should have a permanent slot in every such review.
5. The fifth step concerns the sales team. Even a well-organized funnel won’t close deals if sales reps can’t handle conversations with a client who arrives better qualified and with higher expectations. Investment in sales and negotiation techniques should go hand in hand with process improvement.

If after the first quarter the number of leads rejected by sales drops and SQL-to-opportunity conversion rises, the implementation is heading in the right direction and can be extended to customer service and retention. If nothing has changed, the problem usually lies in the mandate or in the data. Instead of buying more software, go back to the plan and check whether project management actually assigned each stage an owner who can make decisions.