Sales & Revenue Operations

§1 What Revenue Operations Actually Is Foundational

Revenue operations (RevOps) is the unified operations layer that aligns sales, marketing, and customer success around shared revenue goals, systems, and data. That definition sounds like org-design jargon until you've lived through the alternative: separate ops functions for each go-to-market team, each optimizing their own metrics, each owning their own piece of the CRM, each building dashboards that don't talk to each other. The siloed model isn't just inefficient — it actively produces the wrong behaviors.

The evolution from separate ops functions to RevOps follows a predictable path. Early companies have a single ops person who does everything — this is actually RevOps by default, and it tends to work well until the company grows past ~30 people in GTM. Then teams specialize: Sales Ops handles CRM, quota, and comp; Marketing Ops handles MAP, campaign attribution, and lead routing; CS Ops handles renewals, health scores, and QBR processes. Each team gets good at its domain. The problem is that the handoffs between them — MQL to SQL, closed-won to onboarding, onboarding to renewal — are where deals die and data breaks. No one owns the seams.

RevOps owns the seams. Specifically, it owns four things across all three functions: CRM hygiene (the canonical data layer), pipeline reporting (the shared view of revenue across the funnel), process design (how deals move through stages, how leads get routed, what triggers a renewal), and GTM tooling (the stack that connects all of it). Compensation administration is often owned here too, because comp plans are the most direct lever on GTM behavior and they interact with every other system. The authority structure varies — some RevOps functions own reporting only; others own process design, systems, and comp. But the mandate is always the same: end-to-end revenue visibility, not silo-by-silo metric optimization.

The test of whether a RevOps function is working: can you trace a dollar from a marketing impression to a closed deal to a renewal to an expansion — with data — in under an hour? If that trace requires pulling reports from four separate tools and reconciling them in a spreadsheet, RevOps has not yet been built. If it's a single dashboard query, RevOps is working.

Related glossary: revenue operations, CRM, go-to-market, marketing automation platform

§2 The Sales Process — Stages, Criteria, and Why They Matter Building

A sales process is a defined sequence of stages with explicit exit criteria — the conditions that must be true for a deal to advance. This sounds like process for its own sake until you realize that without shared, objective stage definitions, your pipeline is fiction. Every rep has a different mental model of what "in negotiation" means. Your forecast is the average of those mental models. That's not a forecast; it's a collection of impressions.

The standard B2B sales process runs: Prospecting → Discovery → Qualification → Demo/Proof → Proposal → Negotiation → Close → Onboard. The sequence is roughly right, but the thing that makes a process actually work is the difference between activity-based and outcome-based stage gates. Activity-based: "rep has sent an email." Outcome-based: "prospect has articulated the business impact of not solving this problem." Activity-based gates are easy to advance, tell you nothing, and produce bloated pipelines full of deals that will never close. Outcome-based gates are harder to advance, require the rep to do real work, and produce pipelines that actually predict revenue.

Discovery is the most underinvested stage in most B2B sales processes. It's the stage where reps identify the business problem, understand the decision-making process, and find the economic buyer. Done well, discovery defines whether the rest of the cycle is a formality or a struggle. Done poorly, you build a proposal for the wrong problem, present it to someone without budget authority, and lose to "no decision" — the most common form of deal loss that gets misattributed to competitive loss.

MEDDICC (Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion, Competition) is the qualification framework that most enterprise B2B teams use explicitly or implicitly. Each element represents a piece of information that, if missing, makes the deal unpredictable. The rep who can't name the Economic Buyer is selling to someone who can't say yes. The rep who doesn't understand the Decision Process can't predict when a deal will close. MEDDICC fields in the CRM are both a coaching tool (what does the rep know?) and a forecast input (how complete is this opportunity?).

Related glossary: sales process, MEDDICC, exit criteria, discovery call, economic buyer

§3 CRM Hygiene and Pipeline Management Building

The CRM is not an administrative tool. It's the foundation of your forecast, your rep coaching, your territory planning, and your investor reporting. Every downstream decision about where to invest sales resources depends on the accuracy of what's in it. CRM hygiene — the practice of keeping opportunity data complete, current, and consistent — is therefore a revenue-critical function, not a compliance exercise.

The anatomy of a healthy opportunity has roughly six mandatory data fields: close date (within the current or next quarter, not parked 18 months out), amount (set at the realistic ACV, not best-case), stage (matched to actual deal status, not optimistic), contact roles (economic buyer, champion, and at minimum one technical evaluator identified), next step (specific action with a date — not "follow up"), and last activity (no opportunities without any recorded activity in the past 14 days). Completeness across these fields is the single best proxy for whether a rep actually knows their deal.

Data quality rules need to be codified and enforced through CRM automation, not manual audits. Close dates in the past signal deals that have been allowed to drift rather than disqualified. Stale open opportunities (no activity in 30+ days) are phantom pipeline inflating coverage ratios. MEDDICC fields empty past Stage 3 signal deals that are moving forward on hope rather than qualification. The weekly pipeline review is the enforcement mechanism — but it only works if the RevOps function has configured the CRM to flag violations and managers are trained to inspect them.

Pipeline coverage ratio — total open pipeline value divided by remaining quota — is the headline pipeline management metric. A 3× coverage ratio is the conventional target: if you need to close $1M to hit quota, you want $3M in pipeline. But coverage is only useful if the pipeline is clean. A 3× coverage ratio with 40% of deals stale or missing close dates is not actually 3× coverage — it's 1.5× good coverage and noise. The real metric is weighted coverage: pipeline weighted by stage probability, with stale and incomplete deals discounted.

Related glossary: CRM hygiene, pipeline coverage ratio, MEDDICC, stale opportunity

§4 Forecasting — From Pipeline to Number Building

A sales forecast is a prediction of how much revenue will close in a defined period. Its accuracy is a function of two things: the quality of the underlying pipeline data and the judgment of the people interpreting it. Most forecast problems are pipeline data problems wearing the costume of judgment problems.

Forecast categories are the structured vocabulary reps and managers use to express their conviction about a deal. The standard set: Closed (won or lost — revenue is determined), Commit (rep is highly confident it closes; willing to be held to this), Best Case (likely to close but not certain; includes Commit), Pipeline (possible but uncertain — not included in any near-term forecast). The commit/best-case distinction is the most important: a commit is a rep putting their credibility on the line; a best case is an informed guess. Managers who allow reps to treat these as the same category are flying without instruments.

The bottoms-up forecast aggregates individual deal-level calls into a team number: sum of committed deals + a haircut on best-case deals (typically 40–60% of the best case value) + assumed close from early-stage pipeline. The manager call adds a layer of judgment: the manager knows their rep's patterns (consistently sandbagging vs. consistently optimistic) and adjusts the mathematical roll-up accordingly. The most sophisticated organizations layer ML-assisted forecasting on top — using historical close rates by stage, rep, deal size, and time-of-quarter to generate an objective probability for each deal independent of rep conviction.

Forecast accuracy is a lagging indicator of CRM discipline. Teams with clean CRM data, consistent stage definitions, and enforced exit criteria produce accurate forecasts. Teams that let deals drift, allow subjective stage advancement, and skip MEDDICC qualification produce forecasts that are either systematically optimistic (happy-path reps) or systematically conservative (sandbagging reps). The root fix is always upstream, in the pipeline review process and stage gate rigor.

§5 Quota Design and Sales Compensation Building

Quota is the revenue target assigned to a rep, a team, or a territory for a defined period. It's the most direct behavioral lever in sales — reps optimize for whatever they're measured on, and quota defines what that is. Getting quota design wrong creates misalignment between rep behavior and company goals, which then shows up in the forecast, the pipeline, and eventually the P&L.

The three approaches to quota-setting each have different properties. Top-down: take the company revenue target, divide by sales capacity, assign territories. Simple, but treats all reps and territories as equivalent, which they aren't. Bottoms-up: each rep forecasts their territory based on their pipeline and historical close rates; quota rolls up from there. More accurate, but reps have an incentive to sandbag their estimates. Territory-based: quota scales with territory size (addressable market, account count, historical spend) — most defensible for enterprise where territory value varies dramatically. The right answer for most companies is a blend: top-down for the overall envelope, territory-adjusted for distribution.

Quota attainment distribution reveals the health of the comp plan. The classic bell curve — most reps clustering around 90–110% attainment with a tail in each direction — suggests quotas are calibrated correctly and the comp plan is motivating. A hockey-stick distribution — few reps near target, many at 0–50% and a handful above 150% — suggests quotas are too high for most reps (destroying motivation) or territory distribution is badly uneven. If more than 60% of your reps miss quota in a given quarter, the problem is not the reps.

OTE (on-target earnings) is the total expected compensation — base plus variable — when a rep hits exactly 100% of quota. OTE defines the value proposition for the rep role. Accelerators are the commission rate increases that kick in above quota — a 1.5× or 2× multiplier on deals closed above quota is standard. The comp plan design tradeoffs are real: simple plans are easier to explain and game; complex plans can capture more nuance but create confusion, which destroys motivation. The guiding principle is that a rep should be able to calculate their own commission in their head on any deal, in any scenario, without asking RevOps.

Related glossary: quota, OTE, accelerator, attainment distribution, comp plan

§6 RevOps Tooling and the GTM Stack Strategic

The GTM stack is the collection of software tools that powers the go-to-market motion: attracting prospects, managing sales cycles, capturing revenue, and retaining customers. The average B2B company runs 10–20 GTM tools. The question RevOps must answer continuously is not "what's the best tool?" but "what does the stack as a whole produce?" — which is a question about data flow, integration quality, and whether the people using the tools actually use them.

The core stack has three tiers. The data and record layer at the bottom holds the canonical truth: the CRM as the system of record for customer and deal data, a data warehouse for analytics, and enrichment tools that add firmographic and intent data to existing records. The engagement layer in the middle is where the actual GTM work happens: sales engagement platforms (outreach sequences, call logging), marketing automation (campaign execution, lead nurture), customer success platforms (health scores, renewal triggers). The insights and reporting layer at the top converts data from the other tiers into decisions: BI tools, revenue intelligence platforms, and the forecasting tools that aggregate rep-level data into a company view.

The integration problem is where most stacks break down. Each tool generates data. Without deliberate integration design, that data sits in isolated databases — your sales engagement tool knows how a prospect responded to outreach, but that data never makes it to the CRM, so it's invisible in the forecast. The CRM is the forcing function: if a GTM event isn't recorded in the CRM, it doesn't exist for the purposes of forecasting, coaching, or territory planning. Every tool in the stack should be evaluated not just on its standalone capability but on how well it writes to and reads from the CRM.

Build vs. buy vs. integrate decisions in RevOps are almost always "integrate a market-standard tool" — the cost of building CRM functionality, marketing automation, or revenue intelligence from scratch is prohibitive for all but the largest organizations. The decision is usually between tools within a category and between integrated suites (Salesforce + Pardot + Marketing Cloud) and best-of-breed point solutions (Salesforce + HubSpot + Outreach + Gong). Suites win on integration quality; point solutions win on feature depth. The total cost of ownership calculation has to include integration maintenance, not just licensing.

§7 Revenue Forecasting at the Company Level Strategic

Company-level revenue forecasting is the process of aggregating individual deal and cohort predictions into the number leadership, the board, and investors will hold you to. It's different from the sales forecast in two important ways: it includes expansion, contraction, and churn from the existing base (not just new business), and it has a longer time horizon — typically quarters ahead, sometimes full fiscal year.

The ARR waterfall (or bridge) is the canonical tool for SaaS revenue modeling: Beginning ARR + New Business + Expansion − Contraction − Churn = Ending ARR. Each component has its own driver model. New business is driven by the sales forecast. Expansion (upsells and cross-sells from existing customers) is driven by customer health scores and CS pipeline. Contraction and churn are driven by retention models — typically cohort-based, because churn rates vary by acquisition vintage, segment, and product usage patterns. The accuracy of the ending ARR forecast is the product of all five component models' accuracy.

The difference between internal operating forecasts and investor-facing forecasts is primarily about conservatism and scenario structure. Internal forecasts are working documents — updated weekly, scenario-rich, used to drive resource allocation decisions. Investor-facing forecasts are commitments — the range within which the company is promising to operate. The convention for board-level forecasting is to present three scenarios (upside, base, downside) with explicit assumptions for each, so the board can understand what would have to be true to land in each range. A company that presents only a base case is obscuring its own uncertainty.

Scenario planning is the practice of making the assumption dependencies explicit: what does new business close rate have to be for the base case to hold? What is the revenue impact of a 1-point increase in monthly churn? This sensitivity analysis is where the forecasting model earns its keep — not in the point estimate, but in the understanding of which variables are load-bearing and how much movement in each drives how much deviation in the outcome. The CRO and CFO need to agree on these sensitivities; when they don't, the forecast presentation to the board masks a real disagreement about business mechanics.

Open this guide in BizTech Primer →