“We have loads of data but no clear picture.” That is not always a reporting problem. Often the CRM has been designed to record activity, satisfy administration or mirror departmental tasks rather than show customer and commercial progress.
Stages do not represent real progress
A stage called “contacted” may include a useful conversation, a voicemail and an automated email. Those events have very different meaning.
Define stages using observable progress: meaningful response sent, customer contacted, need confirmed, next step agreed, appointment completed, proposal issued, decision made.
The next action is optional
A pipeline can look healthy while records sit untouched. Every active opportunity should have an owner, a next action and a date. Without those fields and behaviours, the CRM becomes a historical archive.
Managers need exception views: no next action, overdue action, no owner, stalled beyond the expected period and reopened repeatedly.
Lost reasons are too broad
“Not interested”, “bad lead” and “no response” describe little. Better reasons distinguish unsuitable fit, invalid details, timing changed, chose competitor, price, no contact after agreed sequence and unknown.
Unknown is legitimate. It is better than invented certainty.
Activity is mistaken for performance
CRM systems are good at counting calls, emails and tasks. They need process design to show whether the customer moved forward.
Salesforce describes sales tracking as capturing and analysing activity and performance across the process. The important word is process: the tool only reflects the definitions and behaviours built around it.
Fix the operating model before rebuilding the dashboard
Clarify stages, ownership, required next actions, hand-off rules, closure criteria and weekly review. Then configure the CRM to make those behaviours easier and the exceptions visible.
Break.Beat treats technology as support for the commercial system, not a substitute for it. The Platform should reinforce the Process. A new dashboard cannot compensate for ambiguous stages and inconsistent use.
A practical checklist
- Stages describe customer or commercial progress.
- Every active record has an owner.
- Every active record has a dated next action.
- Lost reasons are specific and usable.
- Unknown outcomes remain visible.
- Managers can see overdue, stalled and unowned records.
- Reports compare cohorts consistently.
What to do next
Start with a small evidence review rather than a large change programme. Choose a recent sample, follow the complete enquiry history and agree the first change that will improve response, follow-up, ownership or visibility. The Lead Leakage Scorecard is the proportionate next step when the problem is visible but the main leakage point is not yet clear.
Sources and further reading
• Break.Beat: Your CRM is not a graveyard. It is a timing system.
• McKinsey: From touchpoints to journeys
Evidence note: External findings support specific points and should not be treated as universal performance standards. The business’s own enquiry data should determine priorities.
FAQs
Do we need a new CRM?
Not necessarily. First test whether the existing system is being asked to support a clear process.
Why are reports inconsistent?
Definitions, required fields, duplicate records, stage behaviour and user adoption may vary.
Should every activity be logged?
Log information that supports continuity, decisions, compliance and management visibility. Avoid admin that adds no useful value.
Who owns CRM data quality?
Users create the data, but leadership owns the standards, process and review rhythm.
What is the first report to build?
An exception view of active opportunities with no owner, no next action, overdue action or excessive time in stage.