Skip to content

The reasoning model

ROUTE

How a signal becomes revenue action.

ROUTE is a way of deciding, not a software module. It describes what has to happen to one commercial signal: a form, a call, a reply, a usage spike, a silence.

Every capability on this site applies it, and every Diagnostic uses it to find where signal is being lost between the moment it arrives and the moment revenue does or does not appear.

The five steps

  1. Recognize. Did we even see it?

    A form, a visit, a reply, a usage spike, a silence. If a signal is never captured, nothing downstream can recover it.

  2. Organize. Is it structured enough to act on?

    Normalised, deduplicated, attached to the right account and the right owner. Structure turns an event into a record.

  3. Understand. What does it actually mean?

    Scoring, intent, segment, history, stage. Data without context cannot be used, only stored.

  4. Trigger. What happens next, and who does it?

    Routing, prioritisation, ownership, SLA. Analysis with no action attached to it produces nothing.

  5. Execute. Did it produce revenue?

    The call, the campaign, the follow-up, then the loop back into the model. Action without measurement cannot improve.

The four laws

What follows from it

Four statements that come out of the model and govern most of our recommendations.

  • A signal that is not processed is a lost opportunity.
  • Data without context cannot be used.
  • Analysis without action produces nothing.
  • Action without measurement cannot be improved.

Where it is applied

ROUTE per domain

The five questions do not change. What each one asks depends on the domain.

  1. 1

    Revenue Design

    Name what counts as a commercial signal here, and where it is allowed to enter.

  2. 2

    Revenue Systems

    Build the capture surfaces so no signal depends on someone remembering.

  3. 3

    Revenue Execution

    Pick the signal up when it is assigned, not when someone gets round to it.

  4. 4

    Growth & Content

    Identify the buyer question, the proof gap or the attention problem.

ROUTE and Revops OS

The difference

The two are often confused. ROUTE is the reasoning applied to one signal. Revops OS is the architecture that applies it to every signal without anyone thinking about it.

ROUTE

Scope: one signal. Nature: a reasoning model. Used for deciding what should happen. Output: a decision path.

Revops OS

Scope: every signal, every day. Nature: an operating architecture. Used for making it happen repeatably. Output: data, context, workflows, action, control.

Questions

Frequently asked

Where does ROUTE come from?

It was written from diagnostic work, as a way of asking the same five questions about any commercial signal regardless of channel, sector or tooling.

Is it a maturity model?

No. ROUTE describes the treatment of one signal. Maturity is scored separately, layer by layer, in the Revenue Maturity model.

Can we use it ourselves?

Yes. Walk one real lead through the five questions and the step where you cannot answer is usually where the leak is.