Most CRM implementations start from the tool. Stages, properties and workflows are configured from a template before anyone asks how commercial work actually moves through this organisation — from first signal to closed deal to aftercare. The result is a system that looks structured and still feels foreign: the team bends its process to fit the software, and the data becomes an account of the form rather than of the business.
The system inherits the process; it cannot invent one.
Every stage, property and workflow in a CRM encodes an assumption about how commercial work moves. Configure them from a template and you inherit someone else's assumptions: a lifecycle that splits at the wrong moment, ownership that changes where no one actually hands over, reporting that counts activity the team does not recognise as work.
The alternative is unglamorous but decisive: map how a deal actually travels through the organisation — who touches it, what changes hands, where momentum is lost — and only then decide which of those moments the system should represent. Configuration becomes a translation of the process, not a replacement for it.
If the pipeline does not match how the team actually works, the data will describe the form, not the business.
Every stage needs an obvious next owner.
A stage is only useful when it is clear who acts on a record once it enters it. The most common failure in commercial systems is not bad configuration but ambiguous ownership: leads that sit in a shared queue, opportunities that change owner without a real handover, customers whose history lives with whoever happened to speak to them last.
When the process defines ownership explicitly — which role picks up, what that role is expected to do and when the record moves on — the system enforces continuity instead of depending on individual memory. Handovers become a designed moment in the process rather than a conversation that may or may not happen.
Reporting is only as honest as the stages it measures.
Dashboards inherit the quality of the stages beneath them. When lifecycle stages do not correspond to real moments in the process, conversion rates measure the gap between the form and reality — and management ends up discussing numbers no one on the floor recognises.
Stages should mark moments where genuinely something changes: a problem is confirmed, a buying group is identified, a proposal is committed. Those are the moments worth measuring, because they are the moments where the organisation can act. Anything in between is admin, and admin belongs in workflows, not in the pipeline.
“Report on the moments where something changes, and the numbers start telling the truth.”De Grijff · Commercial operating principle
Walk one deal through the system, end to end.
Take a recent deal and walk it through the CRM as it actually moved: every stage change, every owner, every handover. Note where the record lagged behind reality, where the next owner had to ask for context and where the reporting would have misled a manager.
That single exercise usually surfaces more than a full configuration review — the stages that exist only on paper, the handovers nobody designed and the properties that collect answers nobody uses. Fix those, and the system starts to reflect the way work moves instead of fighting it. If you want an outside eye on that mapping, that is exactly where a CRM & Commercial Intelligence engagement starts.
References & further reading
- Who owns each part of the commercial journey? — De Grijff
- Does CRM function as commercial memory? — De Grijff
- CRM & Commercial Intelligence — De Grijff
