A Five-Stage Maturity Model for Revenue Operations: Dimensions and Evidence-Based Assessment

Most maturity models fail in the same way: they are scored by the people being assessed, against descriptions vague enough to accommodate optimism. The result reliably overstates maturity by about one stage and produces a roadmap toward a position the organisation believes it already occupies.

This model is designed to resist that. Every stage is defined by evidence that can be produced on request, and the assessment protocol requires the evidence rather than the opinion.

1. The five stages

1. Ad hoc — process exists in people's heads. Outcomes depend on individuals. Nothing is documented and nothing is repeatable.

2. Defined — process is written down and broadly followed. Definitions exist but are not enforced by systems.

3. Measured — process is instrumented. The organisation can state what happened and, mostly, why.

4. Governed — changes to definitions and systems go through review. Drift is detected rather than discovered.

5. Optimised — the organisation runs controlled experiments on its own process and acts on the results.

2. The six dimensions

Maturity is not uniform. Assess each dimension separately; most organisations are two stages apart across them, and the lowest is usually the binding constraint.

• Definitions — are the terms that cross functions defined, and is there a single owner for each?

• Data architecture — is there a declared writer for each field that reporting depends on?

• Process documentation — does documented process match observed process, and are the gaps recorded?

• Ownership — does every process step have exactly one accountable owner, with a failure path?

• Measurement — can the organisation answer why last quarter landed where it did, from data, without argument?

• Change control — are changes to definitions reviewed, and recorded with a reason?

3. The assessment protocol

For each dimension, the assessor asks for evidence rather than a rating. The stage is the highest one for which evidence exists.

1. Definitions: ask two people from different functions to define the same term independently. Matching definitions is stage 2; a written definition with a named owner is stage 3; enforcement in the system is stage 4.

2. Data architecture: ask which system writes a specific field. An immediate, confident and correct answer is stage 3. A documented field-level map is stage 4.

3. Process: compare the documented process for one flow against what three practitioners describe. Divergence recorded as findings is stage 3; no divergence is stage 4.

4. Ownership: take a responsibility map and test nominal owners — how would you know this step was late, and what would you do? Both answered is genuine ownership.

5. Measurement: ask why last quarter landed where it did. An answer supported by data that survives challenge is stage 3.

6. Change control: ask for the last three changes to a lifecycle definition and the reason recorded for each. Produced on request is stage 4.

4. What moves an organisation up a stage

Each transition has a characteristic bottleneck, and recognising it saves considerable wasted effort.

• Ad hoc to defined: writing things down is not the hard part. Agreeing what the definition is, between functions with different incentives, is.

• Defined to measured: the constraint is almost always data architecture — undeclared field ownership makes measurement unreliable regardless of dashboard quality.

• Measured to governed: this requires giving up speed, and it fails when leadership wants both unreviewed changes and reliable history.

• Governed to optimised: requires enough volume to run controlled comparisons. Below a certain scale, stage 4 is the correct destination.

5. Using this without turning it into theatre

A maturity score is not a target. The useful output is the lowest-scoring dimension and the specific evidence that was missing when you assessed it — that gap is the next piece of work, and it is concrete.

Re-assess annually with the same questions and the same evidence standard. A model re-scored with a looser standard will show improvement that did not occur, which is the failure mode this design exists to prevent.