Pipeline type 05
Sometimes the problem is not the leads. It is that nothing happens to them.
This is the routing, qualification and measurement layer sold on its own, with no advertising attached. It is for practices that already have enquiries arriving — portals, referrals, boards, a website, a previous agency — and no system that decides what happens next.
One enquiry, instrumented end to end
- Source
- Portal enquiry, arrived as forwarded email
- Normalised
- Area, focus, timeline, consent extracted
- Validated
- Duplicate check, malformed number, spam signals
- Assigned
- Rule: area + focus + on duty
- Delivered
- WhatsApp + CRM + sheet, simultaneously
- Acknowledged
- Timestamped by the responder's action
- Closed
- Outcome required from a fixed list
Definition
What this layer actually is
Everything between an enquiry existing and a human acting on it, built as a system with records rather than as a habit that depends on who is in the office.
Most property practices do not have one lead pipeline. They have five or six unconnected ones: a portal that emails a shared inbox, a website form that goes somewhere nobody has checked in months, referrals that live in one person's WhatsApp, boards that generate calls with no record at all, and a CRM into which some of this is occasionally retyped. Nobody in the practice can answer how many enquiries arrived last month, or how long they waited.
This engagement builds the layer that makes those questions answerable: intake normalisation so every source produces the same record shape, deduplication so one owner arriving twice is one owner, a qualification field set applied consistently, assignment rules so no enquiry is unowned, redundant delivery, acknowledgement timestamps written by the responder's own action, and outcome capture from a closed list rather than free text.
We sell it without media on purpose. Putting advertising spend on top of a broken layer is the most reliable way to produce a practice that believes leads do not work — see where pipelines break. It is also worth having whether or not you ever advertise, which is why it is a separate line rather than a component of the other four.
Right for
Practices with volume and no visibility.
- Enquiries already arrive from several sources and nobody can say how many, from where, or how quickly they were answered.
- You have more than one person who could respond, which means you have an assignment problem whether or not you call it one.
- Something has gone wrong recently that nobody can reconstruct, because there is no record of who received what.
- You are about to increase advertising spend and want the layer working before the volume arrives.
- Someone senior is willing to own a response-time standard and enforce it by name.
Wrong for
Five practices we will turn away.
- You have almost no enquiry flow. There is nothing to route. Run a campaign first and instrument it once there is something to instrument.
- Nobody owns the outcome. Measurement without a decision owner produces a report that is opened twice and then never again, and we will have taken your money to build it.
- You want the system but not the behaviour change. This layer makes response latency visible by name. If that is politically impossible in the practice, it will be quietly disabled by month two and we would rather say so now.
- You already run a well-configured CRM with working routing and response reporting. We will audit it, tell you it works, and decline the build. Rebuilding something functional is not a service.
- You are a single agent with low volume and a good memory. The overhead is not justified and the honest recommendation is to spend the money on a campaign.
Signals captured
What the enquiry has to carry, and why each field is there.
This is the one pipeline that captures nothing from the market. The signals it produces are about your practice, and they are frequently uncomfortable.
- Time to first contact
- Per enquiry, per source, per person, measured from arrival to a responder's acknowledged action rather than to a note typed later. It is the number most practices assume they know and most are wrong about.
- Source attribution that survives forwarding
- Portal enquiries arrive as forwarded email and lose their origin on the way. Normalisation preserves the source so that spend and referral effort can be assessed against outcome rather than against impression.
- Field completeness at intake
- What proportion of enquiries arrive without an area, without a focus, without a usable number. This is the measure that tells you whether the problem is upstream capture or downstream follow-up.
- Duplicate rate across sources
- The same owner arriving through two channels within a fortnight. Untracked, they get two different people from your practice calling with two different pitches, which is worse than one call late.
- Outcome disposition
- Why each enquiry closed, chosen from a fixed vocabulary. Free-text outcomes are pleasant to write and impossible to aggregate, which is why almost every CRM contains thousands of them and no usable answer.
- Queue depth and age
- How many enquiries are currently unactioned and how old the oldest one is. A single number that surfaces a problem before it becomes a quarter of lost opportunity.
- Consent state and provenance
- What each contact agreed to and where that agreement is recorded, so that follow-up remains lawful under POPIA and a stop request can be honoured immediately across every channel.
Mechanics
How a campaign of this type is built differently.
The differences here are categorical. This is not a campaign built differently — it is a different kind of engagement with a different deliverable.
-
01
No media, no creative, no audience
Nothing is advertised. There is no ad account, no spend and no cost per enquiry, because no enquiries are being purchased.
The engagement can precede advertising, follow it, or exist entirely without it.
-
02
We work with what you already run
The layer is built around your existing CRM, inboxes and channels. We do not require a platform migration as a condition of the work.
A migration recommendation, if there is one, comes after the audit and is a separate decision.
-
03
Delivery is deliberately redundant
WhatsApp, email and CRM in the same moment. The failure being engineered out is an enquiry arriving somewhere nobody was looking.
Redundancy costs nothing and eliminates the most common silent loss.
-
04
Acknowledgement is an action, not a note
The timestamp is written when the responder acts, not when someone later records that they did. A self-reported response time is not a measurement.
This distinction is the difference between a report and a story.
-
05
Outcomes use a closed vocabulary
A fixed list, chosen at close, mandatory. Short enough to be used honestly, specific enough to be counted.
Every unused field in a CRM was once someone's good idea for free text.
-
06
The report is built to be argued with
Every aggregate resolves to the records behind it. If a person disputes their latency figure, they can open the enquiries and check.
A number that cannot be inspected will be dismissed the first time it is inconvenient.
Failure mode
The way this pipeline goes wrong.
Each of the five fails in a way the other four do not. Naming the failure in advance is how it gets designed out rather than discovered in month three.
Primary failure mode
The layer is installed, the report is produced, and nobody changes what they do.
Why it happens
Measurement is not an intervention. Once latency and disposition are visible, someone has to be willing to act on them — reassign an area, change a duty roster, retrain, or pause spend. Where no one holds that authority, the system documents the same failure every week with increasing precision and no effect.
How it shows up
The report is opened for the first month and then stops being opened. Outcome fields drift towards a single default value because nobody is checking. Response times are discussed as a general concern rather than as a named person's Tuesday.
What prevents it
A named owner with the authority to act, agreed before installation. One metric adopted as the operating standard, chosen by the practice rather than by us. A standing review with a decision attached — including the decision to pause spend or reassign an area. And an explicit agreement, in advance, about what happens when the report says something uncomfortable about a senior person.
Dependencies
What GatorScale needs from you for this to work.
This engagement needs less from you operationally than the campaign pipelines and considerably more from you politically.
- Access to the existing sources
- Inboxes, forms, portal forwarding, CRM, and whatever the referrals currently live in. Including the ones nobody has checked in a while — those are usually the most informative.
- One agreed operating standard
- A single response-time commitment the practice will hold itself to, set by you. We will tell you whether the current data makes it realistic before it is adopted.
- A named owner with authority
- Someone who can reassign an area or change a roster, not only someone who can circulate a report. Without the authority, the role is decorative.
- Honesty about the current state
- Who actually responds, when, and what happens at weekends and during show days. The audit will surface it regardless; starting from an accurate account saves a fortnight.
- A decision on uncomfortable findings
- Agreed in advance. The most common finding is that one person's latency is materially worse than everyone else's. Deciding then how that will be handled is the difference between a system that survives and one that gets switched off.
- A closed outcome vocabulary you will use
- Drafted with you, short enough that people use it honestly. A twenty-item list produces the same default value on every record.
Delivery
The first 90 days.
The structure is a three-month system rather than a set of one-off tasks: setup, then management and optimisation, then growth, reporting and refinement. What sits inside each window is specific to this pipeline type.
| Window | What GatorScale delivers | What you should be able to inspect | The decision at the end |
|---|---|---|---|
| Days 1–30 | Audit of every existing source, intake normalisation into one record shape, deduplication, qualification field set, assignment rules, and redundant delivery live across WhatsApp, email and CRM. | Every source arriving as the same record shape, assignment rules written down, and nothing sitting unowned. | Whether the current operating standard is realistic given what the audit found. Usually it is revised at this point. |
| Days 31–60 | Acknowledgement timestamps and closed-vocabulary outcome capture in production, queue-depth monitoring, and the first baseline covering latency, completeness, duplicates and disposition. | Your real response times by source and by person, and the size of the unactioned queue. | What the operating standard becomes, adopted by the named owner, and what changes in the roster or assignment to make it achievable. |
| Days 61–90 | The full baseline report, a standing review with decisions attached, refinement of routing against what the first two months exposed, and a recommendation on whether media should now go on top. | A quarter of inspectable records, aggregates that resolve to those records, and a measured trend rather than an impression. | Whether the layer holds without us, and whether the practice is now in a position to buy enquiries rather than lose them. |
Ad spend remains controlled by the practitioner and is separate from setup and management. GatorScale does not guarantee listings or mandates.
Baseline response latency across South African property practices. Not published, and we are sceptical of anyone who does publish it. The figure that matters is your own, produced from your own records in the first 60 days, with the records available for inspection behind it.
Questions
Asked before starting this pipeline.
Do we need to change CRM?
No. The layer is built around what you already run. If the audit finds the CRM genuinely cannot support routing or acknowledgement, we will say so and treat migration as a separate decision you make, not a condition of the work.
Can this run without any advertising?
Yes, and for many practices it should. If enquiries already arrive from portals, referrals and boards, the layer improves what happens to them without adding spend. Advertising on top of a broken layer is how a practice comes to believe leads do not work.
What if the report shows one of our agents is the problem?
That is a common finding and it should be anticipated rather than discovered. Before installation we agree who owns the response standard and what happens when a person is materially outside it. Practices that will not have that conversation should not buy this.
Next step
Find out whether this is the right pipeline for your area.
The assessment asks six questions about your area, your follow-up capacity and what you are actually short of. It returns a readiness result and a recommended first pipeline type — which may not be this one.