Pipeline type 04
Area farming is a frequency problem wearing a marketing budget.
Presence is not a number of impressions. It is the point at which an owner recognises your name before you introduce yourself. That point is reached by frequency inside a small boundary, and it is destroyed by spreading the same money across a large one.
Area enquiry — Durbanville estate
- Boundary
- One estate, single named boundary
- Recognition
- Third time seeing the same name
- Tenure
- In the property nine years
- Trigger
- Neighbour's house went on show
- Question
- What are units in here going for now?
- Intent
- No intention to sell yet
- Routed to
- Valuation pipeline, quarterly interval
Definition
What this pipeline actually is
A sustained presence programme inside a bounded area. The product is being the default name. Enquiries are the by-product and the measurement, not the goal.
Every other pipeline here buys a moment of intent. This one buys the position an owner is in when the intent arrives. When a household in a farmed boundary decides to sell, the question they ask themselves is not which agency to research; it is whether to call the name they already know. Farming is the work of becoming that name.
The mechanism is unglamorous. A boundary small enough that the same households see the same person repeatedly. Content that is mostly about the area rather than about you — what sold, what came on, what changed at the entrance, what the levy increase means. Consistency measured in quarters, so that the eleventh month benefits from the first.
It is also a feeder rather than a terminal. An enquiry from a farmed boundary is routed by what the person actually asked: a value question goes to valuation, a let question to rental owners, a stated intention to sell to the seller pipeline. Judging area farming on mandates alone misreads what it is for.
Right for
Practitioners committing to a place, not testing a channel.
- You intend to work the same area in three years' time and want the compounding.
- You can name the boundary in streets, complexes or estates, not in suburbs.
- You will publish something local every month — sold prices where publishable, movement, a plain note about what changed.
- You can tolerate a month with no enquiries without concluding the programme has failed.
- The name on the campaign is a person who is staying, not a brand that rotates staff through the area.
Wrong for
Five reasons we will decline to start this.
- You want a one-month or two-month test. Below a commitment measured in quarters the money buys reach that never becomes recall, and the test answers nothing.
- Your boundary is a metro or a large suburb. Frequency collapses, familiarity never forms, and you have paid to be forgettable across a wider area.
- The practice has high agent turnover. Recognition attaches to a person. If that person leaves, the asset leaves with them and the practice keeps the cost.
- Transaction frequency in the boundary is very low relative to the spend. Presence in an area that turns over rarely is a correct strategy with an expensive waiting period, and you should know that before starting rather than in month five.
- You will not publish anything. Ads alone are not presence. If there is no local material, there is nothing for the recognition to attach to.
Precondition
What counts as a boundary
Most failed farming programmes fail here, before a single ad runs. A boundary is not a suburb name in the copy — it is a specific, defensible geography with four properties.
- It can be drawn
- Named streets, a complex, an estate, a precinct with edges. If it can only be described as a suburb, it is almost certainly too large for the budget.
- It can be serviced
- You can physically get to a valuation appointment inside it without rearranging a day. Presence you cannot service is advertising, not farming.
- It can be reached at frequency
- The budget can put the same message in front of the same households repeatedly within a month. We size the boundary to the frequency target rather than the other way round.
- You know something about it
- What sold, what is on show, which block has the levy dispute, why the units on one side price differently. Farming without local knowledge produces content indistinguishable from a portal.
Being known in one street is worth more than being seen once in forty.
The sizing principle behind every farming boundary we set
Signals captured
What the enquiry has to carry, and why each field is there.
The field set is short and it is missing the one field every other pipeline treats as essential. That absence is deliberate.
- Recognition state
- Whether the name was already familiar, and roughly how often it had been seen. Asked plainly at the enquiry. It is the only direct read on whether the frequency model is working, and it arrives long before any mandate does.
- Tenure in the property
- How long the household has been there. Tenure is the most reliable available proxy for eventual transaction likelihood in an area where nothing else is known about the owner.
- Trigger event
- What prompted the enquiry now: a neighbour's sale, a renovation next door, a levy or rates change, a board going up. Triggers are local and they repeat, which means the content calendar can be built around them.
- Question type
- Value, rentals, local demand, or timing. This is the routing field. Area farming does not resolve enquiries itself; it classifies them and hands them to the pipeline that does.
- Boundary precision
- Which street, complex or estate — not which suburb. Recorded on every enquiry so that coverage can be checked against the boundary rather than assumed.
- No timeline field
- Deliberately absent. Asking a farming contact for a selling date suppresses response and returns a guess. The timeline question belongs to the pipeline this enquiry gets routed into, asked later, when it means something.
Mechanics
How a campaign of this type is built differently.
Six mechanics that are the reverse of how the other four pipelines are built. Optimising this one for cost per enquiry actively damages it.
-
01
The unit of work is a boundary
Not an audience, not an interest set. A named, mappable geography the practitioner can service, recorded and reported against.
Everything else in the campaign is derived from the boundary.
-
02
Frequency is set first, boundary second
We fix the frequency target, then cut the boundary until the budget sustains it. This inverts how most area campaigns are planned.
Planning the other way round is the origin of the failure mode below.
-
03
Most of the creative is not about you
The rotation is local movement, sold prices where publishable, and plain commentary. Self-promotion is the minority of the calendar.
Content about the area is what makes repetition tolerable rather than irritating.
-
04
Low, lumpy enquiry volume is expected
A month with no enquiries is not a failure signal on its own. The programme is assessed on coverage and recognition well before it is assessed on volume.
Reacting to a quiet month by widening the boundary is the classic error.
-
05
Enquiries are routed onward, not worked here
Question type determines the destination pipeline. Area farming is a feeder, and its conversion is measured in the pipeline it feeds.
Attributing the eventual mandate correctly requires the routing to be recorded at enquiry.
-
06
Reporting leads with coverage, not cost
Share of the boundary reached at the frequency target, plus recognition captured at enquiry. Cost per enquiry appears, but it is the least informative number on the page.
A farming programme optimised on cost per lead becomes a bad valuation campaign.
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 boundary is too big for the budget, so the money buys reach instead of familiarity.
Why it happens
Practitioners specify the area they want to own rather than the area the budget can cover at frequency. The spend then spreads across too many households, each one sees the name once or twice, and recognition never forms. Every individual metric looks acceptable; the mechanism the programme depends on simply never engages.
How it shows up
Impressions and reach look healthy, enquiry volume is thin, and the recognition field shows almost every enquirer encountering the name for the first time. The programme is usually stopped around month three, at which point the practitioner concludes that farming does not work.
What prevents it
Size the boundary to the frequency target before launch and be willing to cut it hard. Report reach-at-frequency from the first month, so a boundary that is too wide is corrected in week three rather than discovered in quarter two. Capture recognition on every enquiry as a leading indicator. And set the review point in quarters, agreed with whoever controls the budget. Metro differences matter here — see Cape Town versus Pretoria.
Dependencies
What GatorScale needs from you for this to work.
Farming is the pipeline most dependent on the practitioner and least rescuable by the campaign. Five things have to come from you.
- The boundary, drawn and named
- Streets, complexes or estates. If you cannot name it at that resolution, the first piece of work is defining it, and we will do that before we spend anything.
- A commitment horizon in quarters
- Stated up front by whoever controls the budget. A farming programme cancelled in month three has bought the cost of the asset and none of the asset.
- Local material only you have
- What sold and for roughly what, what is on show, what changed. This is the content that makes the programme work and it cannot be produced from outside the area.
- Consistency of the person
- The same name and face throughout. Rotating the person resets the recognition to zero while the invoice continues.
- Tolerance for quiet months
- Agreed in advance, so that a month without enquiries triggers a coverage check rather than a cancellation.
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 | Boundary definition and sizing against a frequency target, content calendar for the quarter, recognition and routing fields built into capture, and launch at whatever boundary size the budget genuinely sustains. | The boundary written down, the frequency model behind its size, and the first coverage report. | Whether the boundary needs cutting further. Almost always it does, and cutting it in month one is far cheaper than in month five. |
| Days 31–60 | Creative rotation through the calendar, recognition captured on every enquiry, onward routing into the seller, rental and valuation pipelines, and the first read on which triggers actually produce contact. | Reach at frequency across the boundary, the recognition distribution, and where each routed enquiry ended up. | Whether recognition is moving. If it is flat while reach is high, the boundary is still too wide — the budget is not the problem. |
| Days 61–90 | Quarterly coverage and recognition review, boundary adjustment, calendar rebuilt from the triggers that worked, and a recommendation covering the next two quarters rather than the next month. | A quarter of coverage data, recognition trend, and the routed-enquiry ledger showing what the feeder actually fed. | Whether to hold the boundary, contract it further, or extend it — the last of these only when the frequency target is being met comfortably. |
Ad spend remains controlled by the practitioner and is separate from setup and management. GatorScale does not guarantee listings or mandates.
Exposures required before name recognition forms in a South African suburb. Not published. We have not measured it and the imported figures circulated in marketing material are not from this market. We report your own recognition distribution instead, from the recognition field, month by month.
Questions
Asked before starting this pipeline.
How large should a farming boundary be?
Large enough to contain a realistic number of future transactions, small enough that the budget reaches every household repeatedly each month. The frequency target is fixed first and the boundary is cut to fit it. There is no universal size, because the answer depends entirely on the budget and the density of the area.
How long before area farming produces enquiries?
Enquiries can arrive in the first month and mean very little, or arrive in the fourth and mean a great deal. The programme is assessed on coverage and recognition first, because those move before enquiries do and they tell you whether the mechanism is engaging.
Can area farming replace a seller campaign?
No, and it should not be asked to. Farming changes your position when intent appears; a seller campaign buys intent that already exists. Practices needing mandates this quarter should run the seller pipeline and treat farming as the longer investment running alongside it.
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.