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.

· Co-founder, GatorScale Media

Editorial cover art for Where Property Pipelines Break: A Lead Audit Framework
Aerial view of Sea Point, Cape Town
A pipeline is easiest to see from above. Sea Point, Cape Town.Photo: CC BY-SA 3.0, via Wikimedia Commons

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.

The audit worksheet. Compute each ratio across your own enquiry set; the comparison is between your own stages, so no external benchmark is required.
BoundaryRatio to computeDiagnostic question
Campaign → CapturedEnquiries with full context ÷ total enquiriesDoes an enquiry arrive knowing area, type, timeline and intent — or just a name and number?
Captured → QualifiedEnquiries classified within a day ÷ capturedDoes anyone decide what each enquiry actually is, or does classification happen implicitly on the first call?
Qualified → RoutedEnquiries with a named owner ÷ qualifiedCan you say, for each enquiry, which one person was responsible for calling it?
Routed → ContactedFirst contact attempts inside your window ÷ routedDo you have a defined response window at all — and was it met?
Contacted → RecordedAttempts with a written outcome ÷ attemptsCould you reconstruct, today, what happened on each call last month?
Recorded → OpportunityAppointments or mandate conversations ÷ recorded contactsOf the conversations that happened and were recorded, how many produced a next step?
Six pipeline stages drawn as a chain, with leakage concentrating at one boundary rather than spread evenly. Campaign Captured Qualified Routed Contacted Recorded leakage concentrates here
The characteristic audit finding: stage occupancy holds, then drops at one boundary. Illustrative shape — where the drop sits varies by practice, which is what the audit determines.

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.

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. 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 have deliberately published no benchmark ratios here, because we have not yet published a measured dataset and will not invent one.

Measured claims only

Audited stage-ratio distribution across GatorScale-operated pipelines. As GatorScale accumulates audited pipelines under consistent definitions, the anonymised distribution of where South African property pipelines actually break will be published here. No figures are claimed until then.

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.

Next step

Apply this to your own pipeline.

The assessment asks six questions about your area and follow-up capacity, and returns a readiness result with a recommended first test — before anyone contacts you.

Assess my area
Prefer to talk first? WhatsApp SMS Contact