Revenue operations

A journey for applying RevOps, one decision at a time.

Seven briefings for a leadership team that has never named the function. Read the argument. Download the page you sign. Come back to the step you left.

  1. 01

    People

    Who referees

  2. 02

    Process

    One written seam

  3. 03

    Data

    One meaning

  4. 04

    Tools

    Last, and frozen

Begin at the first seam
  1. 00

    Overview

    You do not have a revenue system. You have three departments.

    Shared language. One diagnosis. A one-page charter — not a software tour.

  2. 01

    People

    RevOps fails first on reporting lines, not on CRM.

    Who referees the seams — and who that person reports to.

  3. 02

    Process

    A sales methodology is not a revenue process.

    One seam, written, owned, and timed — before anyone automates it.

  4. 03

    Data

    You do not have a data problem. You have three meanings of the same word.

    Freeze the dictionary before you clean the CRM. Finance co-signs. Dashboards come last.

  5. 04

    Technology

    Most failed RevOps programs start with a platform.

    Tools enforce a model. They do not create one. Architecture and a kill list — not a bake-off.

  6. 05

    Standing it up

    If it is not on the charter, it is not in the quarter.

    Ninety days. Three workstreams. A stop-doing list. Not a transformation program.

  7. 06

    After it exists

    If RevOps is working, one meeting should die.

    Few metrics. One owner. One definition. Then stop briefing and run the quarter.