Skip to content

The discipline, mapped.

Four domains, twenty-one capabilities, five layers.

This section is reference material. It describes what revenue operations actually covers, where one capability ends and the next begins, and which layer of the operating architecture each one belongs to. Nothing here is sold on its own. There is no price on these pages and no form. When you have located your problem, the entry point is the Diagnostic.

Start with the Diagnostic

Two pages before the map.

If revenue operations is new to you, read the definition first. If you already know the discipline and want to know what it looks like on your own platform, read the second.

What is Revenue Operations?

Definition, origins, adjacent disciplines, the five layers and how to tell whether your company needs the discipline at all.

Read the definition

The RevOps glossary

Forty concepts specific to the discipline, each with a working definition and the common error that goes with it.

Explore the glossary

RevOps on your existing CRM

HubSpot, Salesforce, Zoho, Odoo and Pipedrive: what each platform provides, and the design question each one leaves to you.

Compare platforms

Designs the commercial logic

Revenue Design

Build the operating logic that turns demand into revenue.

Revenue growth is not one function. It is a chain of decisions: how demand enters the business, how leads are handled, when sales should act, how opportunities progress, how customers retain and expand, and how management knows what to do next. Revenue Design defines that chain before anything is built.

  1. 01

    Acquisition & Demand

    Design the acquisition model and the entry points into the revenue journey.

    Owned at Context layer
    Owned at Context layer
  2. 02

    Lead Management

    Define lifecycle, ownership, prioritization, nurture and recycling rules.

    Owned at Context layer
    Owned at Context layer
  3. 03

    Sales Pipeline

    Design stages, evidence, progression rules and management cadence.

    Owned at Workflows layer
    Owned at Workflows layer
  4. 04

    Customer Revenue

    Structure onboarding, retention, renewal, expansion and reactivation.

    Owned at Workflows layer
    Owned at Workflows layer
  5. 05

    Revenue Intelligence

    Turn commercial signals into diagnostic and management decisions.

    Owned at Control layer
    Owned at Control layer

Makes the logic executable

Revenue Systems

Make your revenue infrastructure operate as one system.

A CRM, a dashboard or an automation tool is only useful when it supports the way the business actually creates revenue. Revenue Systems structures the data, workflows, controls and integrations behind the revenue model so teams work from the same reality and routine work moves without manual friction.

  1. 01

    CRM & Revenue Data

    Lifecycle, objects, fields, ownership and data governance.

    Owned at Data layer
    Owned at Data layer
  2. 02

    Workflow Automation

    Triggers, rules, actions, exceptions and escalation.

    Owned at Workflows layer
    Owned at Workflows layer
  3. 03

    Lead Routing

    Assignment logic based on fit, intent, territory, language, offer or capacity.

    Owned at Workflows layer
    Owned at Workflows layer
  4. 04

    Opportunity Management

    System controls that operationalize the sales pipeline.

    Owned at Workflows layer
    Owned at Workflows layer
  5. 05

    Reporting & Forecasting

    Governed definitions, dashboards and forecast logic.

    Owned at Control layer
    Owned at Control layer
  6. 06

    Integrations & Architecture

    Connect the required stack without creating technical debt.

    Owned at Data layer
    Owned at Data layer

Operates the motions

Revenue Execution

Add execution capacity without losing control of the revenue process.

A good system still needs disciplined execution. Revops can operate selected revenue motions directly, inside the same CRM, definitions, workflows and controls designed for the client. The objective is not permanent outsourcing. It is reliable execution that strengthens the operating model and produces usable market intelligence.

  1. 01

    SDR & Prospecting

    Structured outbound targeting, calling and follow-up.

    Owned at Action layer
    Owned at Action layer
  2. 02

    Qualification

    Consistent decisions on fit, intent, need, timing and next action.

    Owned at Action layer
    Owned at Action layer
  3. 03

    Reactivation

    Recover value from dormant leads, lost opportunities and inactive customers.

    Owned at Action layer
    Owned at Action layer
  4. 04

    Customer Engagement

    Operate customer conversations while preserving context and ownership.

    Owned at Action layer
    Owned at Action layer
  5. 05

    Revenue Campaigns

    Coordinate growth, systems and sales follow-up as one motion.

    Owned at Action layer
    Owned at Action layer

Creates the signals

Growth & Content

Create attention that the revenue system can recognize and act on.

Growth and content are treated here as signal production, not as brand work. Every program, asset and campaign is designed to produce a signal the engine can capture, qualify and act on. If an asset cannot be connected to a commercial action, it is not produced.

  1. 01

    Demand Generation

    Campaign programs that create and capture buying signals.

    Owned at Action layer
    Owned at Action layer
  2. 02

    Performance Marketing

    Paid acquisition optimized beyond platform-level metrics.

    Owned at Action layer
    Owned at Action layer
  3. 03

    Content & Creative

    Messaging and assets with a defined commercial role.

    Owned at Action layer
    Owned at Action layer
  4. 04

    Social Media

    Structured narratives, publishing and conversion paths.

    Owned at Action layer
    Owned at Action layer
  5. 05

    Video & Media

    Reusable video assets designed for attention, proof and response.

    Owned at Action layer
    Owned at Action layer

How they work together

Signals in, revenue out.

Growth creates the signals, Design decides how they are treated, Systems makes that executable, and Execution operates it. What execution learns flows back into the design. The order is not a hierarchy, it is a dependency.

  1. 01

    Growth & Content

    Creates the signals

  2. 02

    Revenue Design

    Designs the commercial logic

  3. 03

    Revenue Systems

    Makes the logic executable

  4. 04

    Revenue Execution

    Operates the motions

Clear boundaries

Where one capability ends and the next begins.

Some capabilities sit close together and are easy to confuse. Each one owns a different part of the problem, which is what lets you start with the one that matches yours.

  1. 01

    Acquisition & DemandDemand Generation

    Acquisition & Demand designs the acquisition architecture: ICP, channel roles, conversion model, economics, lifecycle entry points and handoffs. Demand Generation operates the market programs that create buying signals.

  2. 02

    Sales PipelineOpportunity Management

    Sales Pipeline designs the business process: stages, gates, exit criteria, buying progress and governance. Opportunity Management implements that logic in the system: fields, tasks, approvals, alerts and hygiene.

  3. 03

    Reporting & ForecastingRevenue Intelligence

    Reporting & Forecasting establishes operational truth: definitions, dashboards, actuals and forecasts. Revenue Intelligence turns that truth into decisions, owners and deadlines.

  4. 04

    Lead ManagementLead RoutingQualification

    Lead Management owns the lifecycle and the rules. Lead Routing implements assignment. Qualification is the execution of the decision.

  5. 05

    Demand GenerationRevenue Campaigns

    Demand Generation creates and distributes demand programs. Revenue Campaigns orchestrates the whole motion, from audience and creative through CRM, routing, sales follow-up and revenue measurement.

  6. 06

    Content & CreativeVideo & Media

    Content & Creative owns the message architecture and written assets. Video & Media owns production and the reusable media library.

Explore by problem

Or start from the symptom you can already see.

A symptom shows up in one layer and is owned in another. Both are named below, because confusing the two is how companies spend a year fixing the wrong thing.

  1. 01

    Unprocessed leads

    Workflows

    Signals arrive and nothing happens to them.

    Lead Management
  2. 02

    Leads that do not convert

    Context

    Volume is fine. The standard applied to it is not.

    Qualification
  3. 03

    Poorly used CRM

    Data

    The system of record records almost nothing.

    CRM & Revenue Data
  4. 04

    Sales and marketing silos

    Workflows

    Two teams, two definitions, one lost handover.

    Acquisition & Demand
  5. 05

    Limited pipeline visibility

    Control

    You find out the quarter is missed inside the quarter.

    Reporting & Forecasting
  6. 06

    Lost opportunities

    Action

    Deals stall quietly and nobody is alerted.

    Opportunity Management
  7. 07

    Scattered data

    Data

    Six tools, six truths, no shared model.

    Integrations & Architecture
  8. 08

    Manual tasks

    Workflows

    People are the integration layer.

    Workflow Automation

Questions

Frequently asked

Are these capabilities sold separately?

No. They are the map of the discipline, used to locate a problem. The work itself is scoped inside an engagement, which usually touches several capabilities at once.

Why twenty-one capabilities?

Because that is how many distinct problems the discipline separates. Each one owns a different failure and states where it stops, which is what allows a repair to be scoped precisely.

Where should we start reading?

Start from the symptom rather than the structure. The symptom list on this page maps what you can already see to the capability that owns the fix.

Locate the problem, then read the engine.

The Diagnostic tells you which of these capabilities is actually costing you revenue, and in what order to repair them.

Book the DiagnosticTalk to us