RevOps · Revenue Operations
Revenue Operations (RevOps)
What is RevOps?
- Aligning marketing, sales, and CS as one
- Run the entire revenue process as one
- Siloed departments cause revenue leakage
What RevOps actually changes is not the org chart but who owns the numbers. Once the question of who defines and who can fix lead, pipeline, and renewal data is settled in one place, you no longer have marketing reporting 412 inquiries and sales reporting 297 for the same month. Meetings change too. Instead of listening to three departmental reports in turn, you put up a single funnel stitched together from first touch to renewal and argue only about 'which stage is leaking.' Accountability shifts from teams to stages.
Don’t mistake it for a rebranded Sales Ops. Where Sales Ops handles productivity inside the sales organization, such as quotas, territories, and compensation, RevOps sits above it and pulls in marketing ops and CS ops to govern four axes: data, process, technology, and enablement. Org structures usually fall into three types: a distributed model with an ops owner in each team, a centralized model where one team holds company-wide operating authority, and a hybrid model where a central team owns data and systems while each team runs its own execution. In Korean B2B, the practical threshold for hiring a dedicated owner is usually when you pass 20 salespeople and 10 SaaS tools in use.
The most common misstep in practice is treating RevOps as a 'CRM integration project.' Even if you merge the systems into one, if the performance metrics stay the same, sales still watches new contracts, marketing watches MQL counts, and CS watches NPS, each pulling in a different direction. The unified dashboard gets flashier while lead leakage stays the same. The second misstep is seating people without giving them authority. If you don't give them an approval line to change lead routing rules or stage definitions, the role hardens into a reporting job that just churns out spreadsheets and dashboards. If you don't spell out in writing 'what they have the authority to change' in the first quarter, all that remains a year later is an expensive tool contract.
John KimAuthor of B2B Marketing Design and CEO of Nanum Consulting
Seungtae ParkAI transformation (AX) practitioner who teaches AI business development and marketing automation by building it hands-onAn extension of Sales Ops to the entire revenue process, it emerged in the late 2010s alongside the need for departmental alignment in B2B and SaaS.
Let's walk through a hypothetical case. Company A sells cloud attendance and payroll SaaS, with 140 employees and KRW 18 billion (≈ US$13,467,000) in ARR. About 600 MQLs came in each month, but sales actually contacted only around 40% of them. Every renewal season, CS called sales to say, 'We don't know what this customer was promised when they signed.' When NRR fell to 97%, the CRO led a six-month RevOps rollout.
- In the first meeting, the CRO put the pipeline reports from three team leads side by side. New opportunity counts for the same month came to 412, 368, and 297, so they spent 30 minutes just reconciling the numbers.
- Kim, who joined as head of RevOps, declared, 'We're rewriting the lead definition from scratch.' Over eight weeks, the team rewrote the MQL and SQL criteria and merged 4,200 duplicate accounts into a single CRM.
- Marketing and sales put the SLA in writing: any MQL not contacted within 2 business days of handoff is automatically returned. In the first month, 190 leads were returned, and for the first time it was clear who had not followed up.
- After CS was brought in and an at-risk customer alert 90 days before renewal was built into the CRM, the CSM in charge began scheduling proactive visits, saying 'I can now see on screen what sales promised at signing.'
- The turning point was explicitly handing Manager Kim the approval authority to change lead routing rules and stage definitions. In the two months before the authority document existed, all that grew was the number of dashboards.
- Six months later, the MQL-to-opportunity conversion rate rose from 11% to 19%, average lead response time dropped from 38 hours to 6 hours, and NRR climbed from 97% to 108%.