The scoring model
Revenue Maturity
Five levels, five layers.
The Diagnostic scores each of the five Revops OS layers on a five-level scale.
The score is not a ranking and it is not a badge. It is a way of deciding what to fix first, because a layer sitting two levels behind the others is the one to look at first.
The matrix
Five levels across five layers
A genuine matrix, so it stays a table. Read a row to see how one layer evolves. Read a column to see what a given maturity level looks like across the engine.
| Layer | 1. Ad hoc | 2. Defined | 3. Governed | 4. Instrumented | 5. Self-correcting |
|---|---|---|---|---|---|
| Data | Records are created inconsistently. Duplicates are normal. | A model exists on paper. Compliance is partial. | Fields have owners. Required data is enforced. | Quality is monitored and alerts on breach. | The model evolves from measured use, on a cadence. |
| Context | Fit and priority are judged case by case. | Scoring criteria are written down. | Scoring is applied uniformly and reviewed. | Scoring is calibrated against actual outcomes. | Scoring re-weights itself from closed-won and closed-lost data. |
| Workflows | Handoffs depend on people remembering. | Rules exist but run manually. | Rules are automated, owned and documented. | Failures alert. Exceptions are routed. | Rules are changed on evidence, with a tested protocol. |
| Action | Execution quality varies by person and by day. | Playbooks exist. Adoption is uneven. | One standard, applied and coached. | Activity produces structured data automatically. | Field learning changes the playbook every cycle. |
| Control | Reporting is retrospective and contested. | Definitions agreed. Dashboards exist. | One governed set. Forecast has rules. | Forecast accuracy is tracked. Gaps surface early. | Reviews produce owned decisions that are verified. |
How it is used
Reading the score
What matters is not the average. It is the gap between layers, and which layer is behind.
All five layers at 1 or 2
No shared operating logic exists yet. Configuring anything at this point would only harden the confusion, so the logic gets written first.
Design ahead of Systems
The thinking is done and the system does not carry it. The gap is implementation, not design.
Systems ahead of Action
Good infrastructure, inconsistent execution. Nothing structural needs rebuilding. The constraint is how the motion is run day to day.
Control two levels behind everything else
You are flying on lagging indicators. Very little else is worth touching until you can see what is actually happening.
Everything at 4 or 5
You do not need us, and we say so at the end of the Diagnostic.
Questions