This is the definitive playbook for spinning up an agency site on our network — the master teaching, the way the Vertical Spotlight Playbook is the master for spotlight sites. An agency is one component of what we do in a vertical. This page defines the anatomy, the build process, and the rules that keep every agency in the network coherent. Reference implementation: ensitefulmarketing.com, built end to end by an agent in one session.

front doors per vertical — spotlight, agency, personal brand, client proof

components every agency site carries, each mapped to its master

~$11 + 1 session

domain cost plus one agent session — the entire spin-up budget

See Where the Agency Sits in a Vertical

Our network already runs one proven pattern: the Spotlight Network — one mothership, a shared component library, and many industry-skinned vertical sites. The agency layer follows the same anatomy. Each vertical we operate has up to four front doors, and they do different jobs: the vertical spotlight site creates demand and ranks the industry, the agency site is where fulfillment and client relationships live, the founder’s personal brand site is the entity people actually trust, and the client sites and Business Profiles are the compounding proof. The spotlight ranks, the agency serves, the person is trusted, the clients prove.

The anatomy: masters above, four front doors per vertical, roots below. The agency is one component — this playbook is its master.

The propagation rule is identical to the spotlight fleet: the master version of every component lives upstream — on BlitzMetrics for methods, on Local Service Spotlight for tools and intake, on BlitzAdmin for infrastructure. When an agency build improves something, the improvement travels up to the master first, then out to every vertical. Never sideways. This article is itself that rule in action: the first agency build taught us the process, and this page is where the process now lives.

Build the Anatomy: Nine Components of an Agency Site

Every agency site in the network carries these, in the founder’s voice, with real photos and zero stock imagery:

#	Component	What it does	Master
1	Figurehead hero	The founder’s face, the phone number top-right, and one promise in plain English. People hire people.	personal brand website
2	Founder story About page	The operator credentials that earn trust, with Person schema and the mentorship lineage.	this playbook
3	Services mapped to methods	Every service links its definitive article — nothing proprietary, the edge is execution discipline.	Dollar-a-Day, Content Factory
4	Industries grid with carve-outs	Exactly which trades this agency owns — and which it deliberately leaves out. One agency per lane.	this playbook
5	Client wall from the live tracker	Real clients from the operational tracker — churned accounts never ship. Agents read ops state, not marketing copy.	ClientTracker
6	Results + weekly-report anatomy	Show the actual reporting format: bottom line, what worked, what needs a decision, what we did.	this playbook
7	Free-audit funnel	Routes to the shared LSS intake — one set of plumbing for the whole network, never rebuilt per site.	get-my-audit
8	Entity roots	Organization + Person schema, GTM plumbing, Keap contact, social links — wired before a dollar is spent.	digital plumbing
9	Launch articles	Three posts in the founder’s voice — origin story, reporting philosophy, methodology — cross-linked to the masters.	posting guidelines

Run the Six-Step Spin-Up

1. Buy the domain with discipline. Verify the exact spelling against the system of record — the Basecamp thread and tracker, not a voice memo — before money moves. One year, every upsell declined, protection off. Registrar carts default to multi-year terms; force it back. Target all-in cost: ten dollars and change.

2. Provision on the fleet. BlitzAdmin → WordPress → New Site: Local Service Spotlight dashboard, vanilla theme, standard Keap contact, operations email. The confirmation modal returns four AWS nameservers — capture them.

3. Point the four nameservers. At the registrar, switch to custom nameservers and paste the four from the modal (GoDaddy walkthrough). Propagation typically lands in minutes; the fleet flips the site active and SSL mints on first request.

4. Build from research, not templates. Ingest the client tracker, the founder’s existing sites and story, and the vertical’s prior coverage before writing a word. The About page is mainly about the founder. The client wall comes from the live tracker. Media is real photos and the founder’s actual podcast or video appearances.

5. QA like an auditor. Crawl every URL with cache-busters against the website QA checklist: zero broken links, valid schema, proper 404s, payload under 5 MB, phone top-right, video on the homepage, socials in the footer. Then run a forbidden-string sweep for every brand and name that must not appear — carve-outs are enforced with grep, not memory.

6. Document the run. Ship the meta article with receipts, post the summary to the client’s Basecamp thread, and fold anything new back into this playbook. The system improves itself or it doesn’t improve.

Respect the Gotchas (Learned the Hard Way)

Symptom	Cause	Fix
Every pretty URL serves the homepage (identical byte counts)	REST permalink update saves the option but never flushes rewrite rules	POST the options-permalink admin form with its nonce — that flushes properly
Design renders in a squeezed 600px column	Block theme’s is-layout-constrained caps content children	Override the constrained child selector with max-width:none in the page CSS
Connection refused mid-build	Repeated wp-login POSTs trip the fleet’s temporary IP ban	Log in once per session and persist the cookie jar to disk
Cart total 5× the expected price	Registrar defaults new domains to five-year terms	Force the term to one year before checkout; decline every add-on
Checkout stalls at payment	Card security codes are a human-only step — agents never type or store them	Stage the entire cart, hand the human exactly one action, verify the receipt

Keep the Network Coherent

Four rules, non-negotiable. The founder is the brand. An agency site carries its figurehead’s face and voice — clients hire their operator, and our network stays the engine room. One agency per lane. Each agency owns a defined trade set, declared on its Industries page; adjacent trades get their own agency with their own figurehead, and carve-outs are stated on the site and enforced in QA. One set of plumbing. Every agency’s audit funnel routes to the shared LSS intake; we never rebuild forms per site. Every build ships receipts. A meta article per run, a Basecamp update per client, and improvements folded back here — master first, then out.

Proof ledger: Verified — the reference build is live with all nine components, QA’d to zero broken links and a clean forbidden-string sweep; the diagram above reflects the same anatomy the Spotlight Network registry documents. Standing process — a weekly agent scan keeps the network registries true, and this playbook updates whenever a build teaches us something new.

THE DELIVERABLE

See the playbook running in the wild

The reference implementation is live — nine components, one figurehead, one session. The worked example with full receipts is the meta article.

Reference Build →The Worked Example →

The Agency-Site Playbook: Spin Up an Agency in Any Vertical