Pipeline research
Where Property Pipelines Break: A Lead Audit Framework
A repeatable audit any practitioner can run on their own pipeline to find the stage that is actually failing.
What this says
- Pipelines rarely fail everywhere at once. They fail at one or two specific stages, and the failing stage is findable with a paper audit that takes an afternoon.
- The audit computes one ratio per stage boundary and asks one diagnostic question at each.
- The most common finding is not a campaign problem. It is a gap between captured and contacted, or between contacted and recorded.
- A pipeline that does not record outcomes cannot be audited — which is itself the first finding.
When a pipeline disappoints, the argument that follows is usually conducted entirely in adjectives: the leads were bad, the market is slow, the campaign was wrong. This framework replaces the adjectives with a one-afternoon audit. It finds the stage where your pipeline actually leaks, using only information you already have — or reveals that you do not have it, which is the more important finding.
Why pipelines break at one stage, not everywhere
A property pipeline is a chain of dependent stages: an enquiry must be captured before it can be qualified, qualified before it can be routed, routed before it can be contacted, contacted before an outcome exists. Chains fail at their weakest link. In practice the weak link is remarkably consistent within a given practice — the same boundary leaks month after month, because the leak is structural: a form that captures nothing, an inbox nobody owns, a response window nobody defined, or an outcome nobody records.
This is good news. A pipeline that failed everywhere would need rebuilding. A pipeline that fails at one boundary needs one fix.
The audit
Assemble your last 60 to 90 days of enquiries from every source into one list. For each, establish which stages it reached. Then compute one ratio per boundary and ask one question at each.
| Boundary | Ratio to compute | Diagnostic question |
|---|---|---|
| Campaign → Captured | Enquiries with full context ÷ total enquiries | Does an enquiry arrive knowing area, type, timeline and intent — or just a name and number? |
| Captured → Qualified | Enquiries classified within a day ÷ captured | Does anyone decide what each enquiry actually is, or does classification happen implicitly on the first call? |
| Qualified → Routed | Enquiries with a named owner ÷ qualified | Can you say, for each enquiry, which one person was responsible for calling it? |
| Routed → Contacted | First contact attempts inside your window ÷ routed | Do you have a defined response window at all — and was it met? |
| Contacted → Recorded | Attempts with a written outcome ÷ attempts | Could you reconstruct, today, what happened on each call last month? |
| Recorded → Opportunity | Appointments or mandate conversations ÷ recorded contacts | Of the conversations that happened and were recorded, how many produced a next step? |
Reading the failure patterns
Pattern one: the context gap
The first ratio is low — enquiries arrive as names and numbers. Everything downstream inherits the damage: qualification becomes guesswork, prioritisation becomes arrival order, and the first call becomes a discovery interview. The fix sits at the form and the campaign, not the follow-up. This is the pattern the anatomy piece exists for.
Pattern two: the ownership gap
Enquiries are captured and even classified, but the routed ratio is low — no named person was responsible for any given enquiry. The signature symptom is that enquiries are seen by several people and called by none, because a shared inbox diffuses responsibility perfectly. The fix is structural and cheap: every enquiry gets one owner and one window, in writing — the routing rule the team operating model is built around.
Pattern three: the window gap
Routing works, but first contact happens whenever the day allows. In property this is expensive in a specific way — owners contact multiple practitioners, and valuation intent is a scheduled decision that gets scheduled with whoever responds inside the decision window. The response-time piece covers the mechanism. The audit finding here is usually not that people are slow; it is that no window was ever defined, so nothing was ever technically late.
Pattern four: the recording gap
Calls happen, but the recorded ratio approaches zero. This is the most consequential pattern because it makes the pipeline unfalsifiable: without outcome records, “the leads were bad” and “the follow-up was thin” are permanently indistinguishable, and every future campaign argument is conducted in adjectives again. The fix costs a sentence per call, and it is the measurement half of lead infrastructure. It is also the fix practices resist most, because its absence protects everyone's preferred explanation.
What the audit cannot tell you
The audit locates the leaking boundary. It does not, by itself, explain the leak — pattern two has at least three distinct causes (unclear ownership, overload, and routing to the wrong channel) that the ratio cannot distinguish. The diagnostic questions in the worksheet are the follow-up instrument: they turn a located leak into a named cause.
It also cannot compare you to the market. We deliberately publish no benchmark ratios here: GatorScale publishes a benchmark only from a measured dataset, and will not invent one.
Audited stage-ratio distribution across GatorScale-operated pipelines. GatorScale publishes where South African property pipelines break only from audited pipelines under consistent definitions, anonymised and with the method stated. No figures are claimed here.
Running it as a habit
The audit's value compounds when it stops being an event. Run quarterly, the same one-afternoon exercise becomes a control chart: the fixed boundary should improve, and any new leak announces itself while it is still one month old. Practices that run it quarterly also accumulate — as a side effect — exactly the outcome records that make every future campaign decision arguable from evidence.
That is the quiet point of the whole framework. The audit is not really a measurement exercise. It is the cheapest possible way to force a pipeline to start remembering what happens inside it.
Definitions used in this piece
- Stage boundary
- The transition between two pipeline stages — for example captured → contacted. Leakage is measured at boundaries, not inside stages.
- Leakage
- The share of enquiries that entered a stage and never left it. Every pipeline has leakage; the audit finds where it concentrates.
- Outcome record
- A written note of what happened after a contact attempt: reached, no answer, not ready, appointment set, disqualified. Without outcome records the later boundaries cannot be computed.
- Unfalsifiable pipeline
- A pipeline with no recorded outcomes, in which every explanation for poor results — bad leads, bad market, bad luck — is equally unprovable.
Method & limits
- What was observed
- The audit sequence GatorScale uses when assessing a practitioner's existing pipeline before recommending any campaign work.
- How
- Codified from operating practice into a framework a practitioner can run unassisted with their last 60–90 days of enquiries.
- When
- Documented August 2026.
What this cannot tell you
- The framework identifies where leakage concentrates; it does not by itself establish why, which requires the stage-specific follow-up questions given in the text.
- No benchmark ratios are published here: the audit compares your stages against each other, which requires no external benchmark.
- Small samples mislead. Below roughly 30 enquiries the ratios are noise; run the audit over a longer window instead.