Revenue Operations

Nobody carries a customer from first click to renewal alone. One group draws attention with ads and content, another converts that attention into signed contracts, and a third makes sure the customer actually uses the product and stays for a second year. Those groups usually sit in separate teams, and each team picks the tools it likes. Marketing collects names in an email platform, sales records deals in a customer relationship management (CRM) system, and customer success logs conversations in a support desk. A CRM is the system that keeps every call, email and meeting with a customer in one place.

The trouble is that one company ends up stored three times under three different names — once as a company, once as a contact's personal email, once as the team that paid. That makes an ordinary question unanswerable. Of the 450 inquiries that came in from ads last quarter, how many did sales actually contact, and how many of those signed? Linking those three numbers requires all three systems to recognize the same customer as the same customer, and nobody owns that link. Each team can still report its own stretch — marketing knows what it produced, sales knows what it closed — and each report is accurate on its own terms. What disappears is the path between them, which is exactly the part a budget decision depends on.

Pagedeck hit exactly that wall. In a quarterly review Ravi reported 450 inquiries generated, and Sofia said almost none of them were worth working, so sales had touched only 60. When Grace asked what happened to the other 390, the room went quiet. The marketing tool still held all 450, but no rule moved that list into the CRM, so sales had been copying over whatever names looked promising by hand. The rest had not been rejected; they had simply never arrived. With no idea where the drop happened, the company could not decide whether to spend more or less on ads the following quarter.

Revenue operations exists to own that seam. It defines what travels with a customer when they pass from one stage to the next, forces the three teams to use the same definition for the same number, and puts the tools and rules that carry the flow under one owner. The name says revenue rather than sales for a reason. Revenue is built as a customer moves through three teams in sequence, and the leaks are usually between them, not inside them. Sales operations, which looks after tools and data inside the sales team, came first, but whoever sat in that chair had no reach into what marketing handed over or what customer success received.

The work splits into four branches: what the teams work with (tools), the sequence and boundaries they follow (systems), what gets paid for the outcome (compensation), and how anyone knows the whole thing is moving (metrics). The first three build the flow and the last one makes the flow report back.

Tools are the floor everything else runs on. The sales stack is the combination of tools a team sells with. Pagedeck keeps a CRM at the center and attaches an outbound email sequencer, a tool that records and transcribes calls, and an e-signature service. The word combination matters more than the list. Each tool looks good on its own, but if the same account piles up separately in four places, adding tools adds manual retyping. So the first question is not what else to buy but which tools exchange information with which. A rep who has to paste a phone number from the dialer into the CRM after every call will stop doing it by the third week, and the gap shows up months later as a pipeline report nobody trusts.

Systems are the sequence and the boundaries people follow. There are three — one for how a single deal progresses, one for who owns what, one for what happens after the signature.

1. Sales playbook — a written guide covering what to do at each stage and what has to be true before a deal advances. It holds the five questions to ask on a first call, the conditions required to move a deal to the proposal stage, and answers to the objections that keep coming back. Writing down how the strongest rep works shortens the stretch where a new hire is guessing.
2. Territory — the region or set of accounts assigned to a rep. Some teams split by geography, some by company size, some by industry. The point of splitting is less about fairness than about removing overlap: when two reps contact the same company separately, the prospect reads that as a vendor that cannot keep its own house in order. Clear lines also make the pipeline readable, because a thin quarter can be traced to a specific territory rather than to the team in general.
3. Sales handoff — the procedure for passing a closed customer to customer success. What was promised during the sale, what problem the buyer is really trying to solve, who approved the spend and who will actually use the product all travel together. Without it, a customer who just signed can sit for weeks with nobody reaching out.

Compensation is what puts the system in motion. Commission is the variable pay a rep earns on results, usually a percentage of contract value. Revenue operations owns it because pay rules change behavior immediately. Pay only on new logos and nobody renews existing accounts; pay purely on contract value and reps discount heavily to land big deals. Redraw territories without touching commission rules at the same time and the first argument will be about who gets paid for deals that changed hands mid-cycle.

Metrics are where the other three branches report in. Sales velocity compresses how fast revenue is being built into one number: multiply the number of open deals by average deal size by win rate, then divide by the average days to close. Forty deals, an average of 20 million won, a 25 percent win rate and a 60-day cycle works out to roughly 3.3 million won generated per day. The value of bundling those four inputs is that choosing which one to attack is the same as choosing which branch to fix. A weak win rate points at the playbook, too few deals points at what marketing is passing over, and a long cycle points at the paperwork in the contracting stage. Watching only the headline figure hides which of the four moved, and two of them can cancel each other out: a quarter where deal size doubles while win rate halves reads as no change at all.

The four branches run in one direction. Tools record, systems carry the record to the next person, compensation pushes people toward the system, and metrics send back the location of the blockage. That returned answer becomes the input that reshapes the systems and the tools, which is one full turn of the work.

"Can RevOps pull how many of last month's 450 inquiries sales actually touched?"

Marketing's number and sales' number disagree, so the question goes to whoever holds both records joined together.

"We need to settle commission rules before we redraw territories."

Changing account ownership alone leaves open deals with no rule for who gets paid, so both policies have to move together.

"There's no handoff procedure, so a customer who signed three weeks ago still hasn't met anyone."

A customer was dropped between two teams, and the point is that a procedure is missing rather than that someone was careless.

After the meeting where nobody could account for 390 inquiries, Pagedeck put one person on revenue operations. Their first move was not buying software but agreeing on words. They settled whether what marketing called an inquiry and what sales called a lead were the same thing, then wrote down which records qualify to move into the CRM. Companies under 20 employees get a self-serve onboarding email; companies of 20 or more go to sales, and return to marketing automatically if no rep makes contact within three days.

Three months later the review looked different. Ravi's 450 inquiries appeared on the same screen as how many qualified, how many were contacted within three days, and how many closed. Instead of saying the leads were weak, Sofia proposed raising the threshold from 20 employees to 30, backing it with a win rate for the 20-to-29 band that ran at half the rate of every other segment. Grace could decide in the room because the two of them were no longer bringing different numbers — they were reading the same one differently.

The most common misreading treats revenue operations as support work: keeping tools tidy and producing reports. The day-to-day does look like configuring systems and building dashboards, which makes the assumption easy. But what the role sets is rules, not settings. Which records get passed to sales, how many days of silence sends them back, how commission splits between new business and renewals — each of those changes what people do. Leave the decisions with individual team leads and each one picks the threshold that flatters their own scoreboard. Marketing loosens the bar to raise volume, sales raises its bar to protect win rate, both scorecards improve, and company revenue does not move.

The second misreading is that this is something to set up once the organization is large. The reasoning is that there is nothing to connect until all three teams exist. But the cost of connecting rises the longer it waits. After a year, each team's records hold the same account under three different names, and merging them takes several times longer than agreeing on rules would have. At a 45-person company, starting this work does not require a dedicated department; it requires three things: deciding what identifies a customer, writing down the conditions for passing them between teams, and reviewing the same screen together every week. Skip it, and doubling headcount next year comes with no basis for deciding where the new people should go.