When the required events were not recorded
Customer, sales, delivery and finance records show different parts of the activity. Reconstruct the sequence of events and agree the definitions before interpreting the result.
Examine the reporting problemThe customer base is bigger and the pipeline is fuller, yet the revenue forecast is less reliable. The issue may be changing order values, uncertain buying dates or work that is contracted but not yet ready to deliver. Find out which uncertainty the records actually show.
A business can grow at a steady rate because its market is growing, a large customer keeps buying, or a favourable channel keeps producing demand. The result can look predictable even when the business cannot explain what will create the next period.
The test is what remains when that tailwind changes: can management explain which parts of demand, customer behaviour, conversion or fulfilment are shaping the next number?
If market demand, a large account or a productive channel has been carrying growth, the limitation may only become visible when that condition changes. The question is whether management can identify which revenue inputs moved before the headline number did.
Start with observable changes. Do not assume that a sales problem is caused by Sales, or that a revenue problem is caused by demand.
If revenue has already declined rather than simply become harder to predict, see why revenue is falling and work from the observed reduction backwards.
Fewer genuine commercial opportunities are entering the business, or the opportunities are becoming less valuable.
Similar-looking opportunities no longer reach a decision at the same rate, value or speed.
Renewal, repeat work, expansion, contraction or buying frequency is changing inside relationships that still look “active”.
Work is sold, but capacity, dependencies, exceptions or customer-specific commitments change when it can be delivered and economically realised.
Headline revenue may look similar while the mix shifts towards lower-value, higher-effort or less repeatable work.
Discounts, special terms, additional promises or other exceptions can gradually become normal without appearing as one obvious change.
Many service businesses can grow for years without a formal mechanism for producing future demand. Repeat work, referrals and relationships keep enough work coming in, so the next job often arrives without anybody having to model where it came from.
The weakness becomes visible when the business grows faster than that informal demand system. Headcount, management and delivery capacity become fixed commitments, while the next period still depends on work arriving through relationships that are only partly visible. Revenue has not necessarily become more volatile. It has become harder to explain before it arrives.
See what changes when the old way of generating work stops scaling →
Revenue can jump sharply and still be understandable if the business can explain what changed in demand, customers, conversion or delivery. Revenue can also look stable while nobody can explain where next quarter's number will come from.
Look at what tends to happen before the number moves: a change in demand, slower decisions, fewer repeat orders or delayed work.
Any of those actions might be sensible. It is worth establishing which part of the business changed before committing to one.
You do not need a perfect forecast. You need enough visibility to know what would have to change for the number to be wrong.
Where is the next period's revenue expected to come from?
What could materially change that expectation?
When revenue misses expectation, which part tends to move first?
Can management see that movement before it reaches the P&L?
A CRM may contain accounts, deals and activity history while commercially important changes remain implicit in conversations, delivery systems or individual memory. An active customer can become a renewal risk. A relationship can become a real opportunity. Won work can become constrained in delivery. If those changes are not visible, the system records history more reliably than it represents what may happen next.
If the problem looks like unreliable CRM data, reporting, forecasting or work happening outside the system, use the CRM problem map instead.
See common CRM problems and their causes →Customer, sales, delivery and finance records show different parts of the activity. Reconstruct the sequence of events and agree the definitions before interpreting the result.
Examine the reporting problemA clear history does not establish why the result changed. Compare the timing, customer mix, sales stages and operational conditions that could account for the difference.
Compare the revenue mechanismsYou cannot remove every uncertainty from a forecast. You can improve which assumptions are visible, who checks them and when they need to be revised.
Once that is visible, forecasting, CRM design, commercial process or operational changes can be made against an observed mechanism rather than a generic target such as “more sales”.
How to connect the management evidence →This changes whether the next action belongs in planning, reporting or operations.
A stable number of new enquiries can conceal a shift from referred buyers to colder, less qualified prospects. The aggregate conversion rate may move without a change in the team's handling of comparable opportunities. The choice of cohort and the definitions of funnel stages matter.