Operating model · Agency
Agencies
Multiple areas, multiple practitioners, and pipeline structure that must hold across all of them.
Fit
Who this model is for.
- Agencies operating across multiple suburbs or branches, with principals accountable for aggregate results.
- Organisations where campaign spend is centralised but follow-up is distributed — the structural gap the model exists to close.
- Principals who want area-level evidence for where to invest next, not office-level anecdotes.
Structure
How the pipeline is built for this model.
The unit of structure is the area-pipeline pair, not the office. Each area runs as its own pipeline with its own capture, routing and ratios, because areas fail independently — a working office can contain a broken suburb and vice versa. Definitions are standardised across all of them: what counts as qualified, what the response window is, what an outcome record contains. Consistency is what makes areas comparable, and comparability is what makes the aggregate reporting mean anything.
Operations
Ownership, routing and reporting.
- Who owns follow-up
- Distributed to the practitioner owning each area, with branch-level escalation. The agency case adds one structural safeguard the smaller models do not need: enquiry ownership survives practitioner departure. When someone leaves, their pipeline's enquiries re-route by rule, not by memory.
- What reporting looks like
- Three layers: practitioner, area, and portfolio. The portfolio view is deliberately unflattering — it ranks areas by their weakest boundary ratio, because the principal's real decision is where structure needs attention, and an average across areas hides exactly that. Campaign spend recommendations follow the evidence: areas earn budget by their measured downstream behaviour, not their seniority.
The failure mode
What this model has to defend against.
Definition drift. Branch A's 'qualified' quietly stops meaning Branch B's, the cross-area comparison silently becomes fiction, and decisions get made on numbers that no longer measure the same thing. The countermeasure is unglamorous: shared definitions, written down, audited quarterly.
Requirements
What GatorScale needs from you.
The system is a collaboration. These are the non-negotiables for this model — stated up front because discovering them mid-campaign helps nobody.
-
01
Required
A principal-level mandate for consistent definitions across branches.
-
02
Required
One accountable owner per area-pipeline, named in writing.
-
03
Required
Quarterly definition audits alongside the ratio review.
Next step
Start with an assessment, not a sales call.
Answer six questions about your area and follow-up capacity. You get a readiness result, a recommended first test and the risk most likely to cost you mandates — before anyone contacts you.