Revenue engine methodology

The five areas in detail

Each area exists because of a stage or a property of the engine. Most engagements cross two or three of them — because the problems do.

The four engagement steps in detail

Every engagement runs the same sequence, sized to the situation — from a two-week diagnostic to a twelve-month implementation.

1. Step 1

   Baseline the engine.

   A bounded diagnostic of two to six weeks on your own data — CRM, pricing, retention, planning and call records. It establishes the baseline, quantifies the opportunity and ends with an executive readout of prioritised recommendations. The diagnostic is fixed-fee, so its conclusion is not influenced by what might follow it. In time-sensitive situations this step compresses into a four-to-eight-week sprint to one decision; in transactions it runs inside the deal timetable.

2. Step 2

   Find the constraint.

   The stage or connection that caps performance is quantified before any solution is designed. A conversion problem is not solved with more demand, and a retention problem is not solved with more logos. Recommendations are sequenced by value and by the effort to capture it, so the plan starts where the return is fastest.

3. Step 3

   Fix the system, not the symptom.

   Design and implementation cover the choices, processes, roles, incentives and systems around the constraint, so a change in one place holds in the others. Improvements are built into the CRM and the operating rhythm — inspected by managers and reinforced through cadence and coaching — because methodology training alone rarely survives a quarter. Design is scoped and priced separately from implementation, so the design is not distorted by the economics of delivery.

4. Step 4

   Measure what moved.

   Measurement is agreed at kick-off: baseline, cohort, time window, owner, target and attribution method. One business result that matters to the sponsor — realised price, forecast error, gross retention, cost per qualified opportunity — is tracked alongside the process controls that explain why it moved. Pipeline created, time saved and revenue realised are reported separately, never added together, and pilots carry explicit scale, pivot or stop criteria.