Revenue Operations in practice: marketing, sales and CS

Revenue Operations, or RevOps, is a way of running the company in which marketing, sales and post-sale answer for a shared revenue target, agree in writing on how the customer moves from one team to the next and read the same numbers in the same CRM. In practice, RevOps is a management capability that leadership builds in the team, with process, metrics and rituals, and the tool comes later. The companies I see hitting their targets with consistency share a sync between strategy, processes and the people who execute, more than team size or media budget. When those pieces drift apart, the team spends its energy figuring out the internal structure instead of selling, and hitting the target turns into luck.

This article accompanies the video above, the first webinar we recorded on the methodology, and the video is in Portuguese. Across the more than 200 companies I have worked with, the scene I see most often is a company that already pays for a CRM and still has each team measuring its own success in its own spreadsheet. I wrote the method below for the people who lead those teams and have to decide what changes.

What is Revenue Operations and why does it exist?

Revenue Operations is a management methodology that uses the CRM as infrastructure, in the sense I explain in what a CRM is and what it is for. The term reached the market attached to a job title, and I have seen companies hire a RevOps analyst expecting that one person to settle a dispute between three departments. The methodology works for startups, manufacturers, traditional businesses and multichannel retail, because the pain it addresses shows up in all of those models.

The pain comes from how the company holds each team accountable. Marketing answers for leads and MQLs, sales for proposals and closed deals, and post-sale for NPS, upsell and cross-sell. With their own metrics and processes, each team starts delivering results independently of the previous one, and the salesperson carries the target alone, with the individual quota speaking louder than the collective goal. Then come the silos, with sales complaining about lead quality and marketing complaining about the follow-up that never happened, in a dispute that burns more energy than the funnel. In a 2021 press release, Gartner predicted that 75% of the highest growth companies in the world would deploy a RevOps model by 2025, and its analyst named as a barrier to revenue growth the silos that hand the client from one function to the next, each with its own technology, people and processes.

RevOps answers this with process, so everyone speaks the same language at the handoff, and with people prepared to sustain it, because a well-designed methodology does not survive someone who acts as the hero of their own story. The CRM records the journey and gives the data governance. I reached this view after years of designing go-to-market plans that stalled in execution, because the team was not ready or the process did not match what was on paper. Since then I have argued that a conservative go-to-market plan the operation executes at eighty or ninety percent beats a perfect plan executed at ten.

Where does revenue leak between marketing, sales and CS?

The first leak happens at the handoff between marketing and sales, and almost nobody records it. Marketing generates the lead in the automation tool and celebrates, with good reason. Sales works in another system, gets no notification and waits for a message that never arrives, until someone calls three or four days later. In that gap a competitor may have replied the same day, and the monthly report will blame lead quality for a loss that came from missing integration and missing agreements between teams.

The second leak happens at the handoff from sales to post-sale. The reason the customer bought needs to travel with them to onboarding, or churn shows up six months later with no explanation. In our own funnel, someone who converts while reading a CRM comparison arrives with the pain of choosing a tool, and the onboarding team needs to know that on day one. Without that trail, post-sale starts from scratch and treats every customer the same way, as I explain in B2B post-sale.

The journey also runs through teams outside the revenue org chart. In a project with an importer of fitness equipment that supplies the largest gym chains in Brazil, the journey map included logistics, from payment confirmation to product assembly. Anyone who has bought something large online knows the anxiety of waiting for delivery, and if it is part of the commercial experience, someone has to own it in the process and in the CRM.

What changes for each leader with RevOps?

Sales leadership

For sales leadership, the most visible change is owning response time and the return of leads. A lead that does not fit goes back to marketing with the reason recorded, and that reason feeds the review of the ideal customer profile. The manager starts reading the pipeline by opportunity source and finds out which channels bring deals that close.

Marketing leadership

Marketing leadership trades a volume target for one tied to revenue, such as opportunities created, new revenue by source and the rate at which sales accepts leads. The switch can push MQL numbers down in the first quarter, and the executive team needs to know that before seeing the dashboard. Marketing gains access to loss and churn reasons, which show which message attracted the wrong customer.

Post-sale and Customer Success leadership

For post-sale and Customer Success, RevOps brings renewal and expansion into the shared target. CS receives the customer with the original pain, the success criteria and what the salesperson promised, and sends expansion signals and cancellation reasons back to sales and marketing. I ask CS leadership to help define the required sales fields, because they are the ones who feel their absence at kickoff.

C-level

For the C-level, the central decision is the target. As long as each department has a target it can hit at the expense of another, no process will hold the alignment together. The CEO or chief revenue officer sets the shared target, names an owner for each stage of the journey and runs the monthly committee where the three teams look at the same funnel. It also falls to them to hand the technical CRM work to someone who does not carry a closing quota.

How to implement RevOps: the four-phase method

The design puts the CRM at the center and, around it, the teams that use it. Marketing runs content, landing pages, ads and UTM tagging. Sales and pre-sales run calls, cadences, WhatsApp and the pipeline, and the service area brings together support and, in many operations, logistics, finance and legal.

Phase 1: diagnosis, and why it involves no technology

Diagnosis starts with conversations with everyone, from the CEO to the SDR. Then comes the data analysis: if someone says prospecting is hard, ask to see it, sit next to them and follow the process on a shared screen. Individual perception tends to differ from practice, and that difference is the diagnosis. Last comes the tool analysis, to check whether the reports match what you saw.

The first phase leaves technology out because the tool reproduces the process the company already has, flaws included. If the diagnosis starts with choosing a CRM, the discussion turns into a feature comparison, and nobody asks why the lead waits four days. In our own early consulting days, we brought technology in as if it were salvation, and our clients’ operations did not move. Today, in a good share of projects, the company already has the tool and lacks an agreement between teams.

Phase 2: process design and the SLA between teams

This is the rule I will not bend: the CRM only receives a structured process. The tool asks you to configure your process inside it, and without a defined process the company pays a subscription while inventing the process, which is how CRM projects blow their deadlines. In this phase leadership maps the journey from first contact to renewal, names an owner for each stage and writes the handoff rules into the SLA between marketing, sales and CS. This is the structure I use as a starting point.

Handoff	What needs to arrive	Commitment of the receiving team	Where it lives in the CRM
Marketing to sales	Lead within the MQL criteria, with source and stated pain	First contact within the agreed time and acceptance or rejection with a reason	Creation date, first activity and rejection reason
Sales back to marketing	Rejected lead or lost deal, with the reason	Nurturing and review of the MQL criteria	Rejection reason and loss reason
Sales to post-sale	Original pain, success criteria, buying committee and what was promised	Handoff meeting before kickoff and success plan	Required fields at the closed-won stage
Post-sale to sales and marketing	Expansion signal, churn risk and testimonial	Expansion opportunity opened by the right owner	Expansion pipeline and churn reason

Deadlines depend on each operation. I recommend starting with numbers the team can meet from the first week and tightening them later, with history in hand. I explain how to write, sign off and enforce this agreement in SLA between marketing, sales and post-sale.

Phase 3: enablement

Investing in process and tools without preparing people gives you blank fields. The team needs to understand why each field exists and who uses that information later. Training starts with leadership, who will enforce the SLA in the following weeks, and then reaches the people who run the operation. The reasons teams leave the CRM aside are in CRM adoption.

Phase 4: acceleration and management

The fourth phase is sustainment, carried by the management rituals and by a process owner. By the time implementation ends, the process has already evolved, because execution teaches and the company changes prices, services and strategy over the year. Leadership reviews the SLA and the metrics matrix every quarter. I discuss the difference between sustainable revenue and an operation that lives on spikes in RevOps and CRM in B2B funnel management.

Which RevOps metrics connect marketing, sales and CS?

The metrics matrix defines what each team measures, who answers for the number, where it lives in the CRM and how often leadership looks at it. The metrics cross team lines on purpose: time to first contact belongs to sales and depends on marketing delivering the lead with complete data, and churn belongs to CS and depends on what the salesperson promised. Start with a few rows and add more as the team fills in the fields.

Metric	Owner	Where to measure in the CRM	Frequency
Time from lead creation to first contact	Sales or pre-sales	Contact creation date and first activity date	Weekly
MQL acceptance rate by sales	Marketing	Lead status and rejection reason	Weekly
Stage-to-stage pipeline conversion	Sales	Funnel report by stage	Weekly
New revenue by source	Marketing	Contact source on the closed-won deal	Monthly
Forecast accuracy	Sales leadership	Forecast at the start of the period against closed-won at the end	Monthly
Loss reason	Sales, read by marketing	Required field on the lost deal	Monthly
Revenue churn and reason	Customer Success	Account status, cancellation date and reason	Monthly
Expansion revenue	Customer Success, with sales	Expansion pipeline on active customers	Monthly
SLA field completeness	RevOps process owner	Report of empty properties by stage	Biweekly

The last row holds up the others. If the loss reason is blank on half the deals, the monthly loss review turns into opinion. Leadership tends to find this out when it tries to use the number in a budget decision.

Which joint management rituals sustain RevOps?

The matrix gets used when each metric has a meeting where someone asks about it. The first ritual is a weekly half-hour handoff meeting between marketing and sales to review leads that went past the deadline without contact and the ones sales rejected. When the same rejection reason shows up week after week, both leaders adjust the MQL criteria right there.

The second is a biweekly meeting between sales and CS, where the salesperson presents closed deals to the onboarding owner and CS flags at-risk accounts and expansion opportunities. The third is the monthly revenue committee, run by the C-level with the three leaders, which looks at the whole funnel, compares forecast with actuals and leaves with decisions that have an owner and a date. Every quarter, the same committee reviews the SLA and the matrix.

How big does a company need to be for RevOps?

One person in marketing and one in sales are enough, because two different heads already create a need for alignment. Tools are not what holds you back: HubSpot, the platform I work with most, has a free plan and entry-level plans that serve a small operation. To make the case internally, count how much of the day the team spends on manual work: half a day of operational tasks with little return shows that RevOps has room to help, and finance understands that argument.

Revenue Operations training: what HR and L&D need to assess

How to recognize the need

The signs show up in the results meeting before they show up in the engagement survey. Marketing and sales present different numbers for the same period, lead quality comes back as a topic at every month-end close and the forecast misses quarter after quarter. In post-sale, the sign is an onboarding that starts with the customer explaining again what they bought.

Who takes part

The core group is leadership: marketing, sales and post-sale directors and managers in the same cohort, along with the coordinators who will enforce the process day to day. The C-level joins the opening and closing sessions, when the group validates the shared target and the SLA, and whoever administers the CRM joins to turn each agreement into fields and reports. A sales-only cohort leaves with a process that marketing and CS never signed.

How to measure

The satisfaction score measures the experience in the room and says little about the operation. Before the training, HR and leadership pull a baseline from the CRM with time to first contact, MQL acceptance rate, SLA field completeness and forecast accuracy. In the first weeks, measure adoption, with the rituals happening and the fields filled in. After one average sales cycle, compare conversion, forecast and churn with the baseline in the revenue committee.

If your leadership wants to replace the dispute between teams with revenue that all three answer for together, that is the work of the in-company Revenue Operations training. I run the training with marketing, sales and post-sale leaders in the same room, built on the company’s real funnel. The group leaves with the SLA between marketing, sales and CS and the RevOps metrics matrix written for your operation, ready for the first revenue committee.

Frequently asked questions

What is RevOps?

RevOps, or Revenue Operations, is the management methodology that aligns marketing, sales and post-sale around a shared revenue target. It combines handoff rules between teams, shared metrics and joint management rituals, with the CRM recording the customer journey.

Is RevOps a job title or a department?

RevOps is a management capability that leadership builds in the team. Larger companies appoint someone responsible for revenue operations to look after the process and the CRM, and that person depends on the three leaders keeping the SLA.

How do you implement RevOps in practice?

I work in four phases: diagnosis, process design, enablement, and acceleration with management. The diagnosis compares what people say with what the data shows, process design produces the journey and the SLA, and only then does the company configure the CRM and train the team.

Do I need to switch CRMs to implement RevOps?

In most of the cases I work on, the company already has the tool and lacks an agreed process between teams. Switching makes sense when the diagnosis shows the current CRM cannot support the process you designed, a conclusion that comes after the second phase.

Which RevOps metrics should I track first?

Start with the handoff metrics: time to first contact, MQL acceptance rate and completeness of the fields sales hands to post-sale. They show where revenue leaks and use data the CRM already records. Stage conversion, forecast and churn come next.