“An enquiry is not a viewing. Treat the journey as an observable service system: instrument each hand-off, inspect the buyer experience, and repair the smallest broken promise first.
Diagnose the failure
Lead volume hides the hand-offs that lose intent: a form may submit, a call may go unanswered, or a salesperson may lack a suitable slot. Name stages—received, contacted, qualified, appointment proposed, confirmed, attended—and record a timestamp and owner at each boundary. A missing boundary is itself a measurement defect.
Use a decision framework
Use stage-to-stage conversion and median time, not only cost per enquiry. A sharp fall after first contact suggests response capacity; a fall after qualification suggests promise or fit. Google Analytics can mark business-critical actions as key events, but the event definition must match the operational stage and be reconciled with the CRM.
A hypothetical real estate example
Implement and measure
Create one shared pipeline and require a reason code for every stalled lead. Audit a small sample of call notes weekly. Measure stage rates, response time, no-contact rate, and attended-viewing rate by source. Treat the dashboard as a diagnosis tool; it can locate a leak, but cannot by itself prove why the leak exists. The useful unit is the journey, not the record count: every transition needs a clear owner, an observable timestamp, and a reason when it stops.
Put it to work
- Define the six stages and owner in one page.
- Add timestamps and stall reasons to the CRM.
- Review ten lost journeys with sales each week.