Start with three questions.
What did you change? What did you expect to improve? What actually happened? That is enough to start.
What changed → what should have improved → what actually happened.
The same disappointing result can come from very different things.
Define the change
What did management increase, introduce or redesign?
Define the expectation
What result was supposed to move, and why?
Follow what happened
What had to happen in the business for that result to follow?
Test reality
Which explanation is actually supported by evidence?
I separate what we know from what we think.
The aim is enough evidence to make the next decision - not a precise-looking answer built from guesses.
Direct evidence supports the finding.
Several independent traces point in the same direction.
The business does not currently capture what would be needed to establish the answer.
The smallest useful measurement or check that would reduce uncertainty.
Evidence that weakens the preferred explanation is kept visible rather than explained away.
A plausible explanation that the available evidence does not currently justify.
Do not ask a business for data it never captured.
A clean dataset is useful. It is not a prerequisite for thinking.
I can work from interviews, recent commercial situations, proposals, account history, operational traces, system records and existing reports.
If the remaining question genuinely depends on missing data, that gap becomes part of the finding rather than a number built from guesses.
Where evidence stops, the conclusion stops too.
Revenue Visibility Review
Can the business follow the customer story across systems and people?
£595 · written PDF →I do some homework first.
I look at the company, offer, customers, business model and the visible change before the first conversation.
You receive a written PDF.
Both main products end with a documented view of the evidence, findings, unknowns and recommended next step. The analysis does not disappear when the meeting ends.
I separate the business question from the software that records it.
The CRM may be part of the mechanism. Or it may simply be where an older commercial model becomes visible.
See why CRM problems keep coming back →The intervention comes last.
Process, Management View, reporting, CRM configuration, integration, automation and custom development are scoped only after the requirement is clear.
See services →