Agency Infrastructure
Preamble
Infrastructure keeps the agency from mistaking a lead list for a market. It turns prospect research into artifact hypotheses, records what happened after contact, and stays useful only when it moves the work closer to buyer judgment.
Rows Are Only Clues
A lead database can make the market look obedient. Search a town, pull every plumber, sort by old site, thin proof, missing booking flow, or broken profile, and the screen fills with targets.
That list is a proxy. It shows possible opportunity before any owner has recognized value. Infrastructure has to keep that distinction visible before the agent starts treating rows as demand.
The How Is A Hypothesis Record
The first version can stay blunt:
business found -> signal captured -> artifact proposed -> owner contacted -> answer recordedA roofing company with strong reviews and a thin service page may become a Design hypothesis. A dentist with stale profile photos may become a GBP hypothesis. A mechanic with a buried phone number may become a Booking hypothesis. Each record needs the evidence, the artifact idea, the next action, and the owner’s answer.
The System Must Stay Smaller Than The Business
Infrastructure is internal. It can include sourcing, qualification, outreach support, light tracking, delivery checklists, telemetry, and reusable prompts.
The trap is building a CRM, scraper, and automation stack before the agency has earned the complexity. The system should ask fewer questions than a real sale answers: who might value a better public surface, what signal supports that belief, what was built, what the owner said, and what changed after contact.
When Infrastructure works, commercial learning compounds. When it fails, the agent gets excellent at managing prospects while avoiding the market.