by /
Dennis pointed at one Google Sheet — our internal Client Tracker — and said: make this public. Not the private numbers. The system. Here’s how an afternoon turned an ops spreadsheet into the definitive article on how we run many agencies on one set of rails.
We tell every client and every AI Builder that we teach openly. This is us doing it with the one document that runs the whole network.
1 sheet
decoded into a public playbook — 9 tabs, revenue + labor + tools
42 → 6
outbound links from the new article, plus 6 articles now linking back
0
private client names or dollar figures published — the system, not the ledger
Start with the real thing, not a topic
We didn’t write “an article about client tracking.” We opened the actual Client Tracker and read it: the revenue tab grouped by agency, the labor-costs tab, the tools tab, the naming in the Basecamp column. Real ingredients first. That’s the Content Factory rule — you produce from something that actually exists, then let AI process it. You never generate the substance out of thin air.
Publish the system, never the private ledger
The tracker holds real client names tied to real revenue, plus what every team member is paid. None of that belongs on a public page. So we drew a hard line: publish the structure, withhold the figures.
The article teaches the columns, the naming convention, the tiers, the package-to-SOP mapping, and the rev-share math — using the already-public agency names and a made-up example client (Acme Plumbing). Anyone can learn exactly how the machine works without seeing a single client’s numbers. Transparency about the method, privacy on the data.
The reusable rule
When you turn an internal ops artifact into public content, separate the pattern from the payload. The pattern (how we name, tier, own, and settle up) is the teachable asset. The payload (who pays what) stays behind the login. Ship the pattern.
Decode the naming convention into a picture
The hardest thing to explain in words is the project-name code, so we drew it. One line — Roof Launch Marketing's Clients 4 – Quickstart: Acme Plumbing — broken into four labeled parts: agency owner, tier, package, client. Plus the XXX prefix that means “not active.” A reader gets in one glance what a paragraph fumbles. It ties straight back to our existing Basecamp naming guide.
Every package points at an SOP
The tracker’s Type column isn’t decoration — each value is a real package with a written process. We linked them so the article isn’t theory: Maps Visibility System ($1,500/mo), the Conversion Engine ($3,500/mo), and Claude setup. Same discipline as the 239-task skill library: nothing gets sold that isn’t documented.
Cross-link both directions
A definitive article that only points outward is half-built. We wired six of the most related articles to point back at it, so a reader lands on the Client Tracker from wherever they start:
| Now links back to the Client Tracker | Site |
|---|---|
| Basecamp Basics | Local Service Spotlight |
| The Success Tracker | Local Service Spotlight |
| How AI Builders Do MAA | Local Service Spotlight |
| Free Basecamp Access for AI Builders | Local Service Spotlight |
| Naming Projects & Threads in Basecamp | BlitzMetrics |
| Why We’re Building a Two-Sided Network | BlitzMetrics |
What it took
| Step | Result |
|---|---|
| Read the source | 1 Google Sheet, 9 tabs (revenue / labor / tools / access), pulled via the gviz CSV export |
| Map the cluster | ~20 related articles found across both sites via WP REST search |
| Write + publish | ~2,400-word definitive article, custom SVG diagram, 5 branded tables, live in one session |
| Verify | All 15 unique internal links returned HTTP 200; styling, SVG, and categories confirmed on the live page |
| Cross-link | 6 backlinks appended and each re-checked for the live link |
Why this matters
The Client Tracker is the seam where our shared infrastructure meets each individual agency’s book. Documenting it publicly means a new AI Builder can see the whole operating system before they join — and an AI agent can read the same article to understand how to route a report. Teaching openly isn’t a marketing tactic here; it’s the operating manual.
The Deliverable
The Client Tracker: One Source of Truth Behind Every Agency We Run
The full definitive article — naming conventions, tiers, rev-share, package SOPs, and how agents run it.
Read the definitive article →Related: The Client Tracker · Naming Projects & Threads in Basecamp · Two-Sided Network · How we write meta articles
Dennis Yu
Dennis Yu is the CEO of Local Service Spotlight, a platform that amplifies the reputations of contractors and local service businesses using the Content Factory process. He is a former search engine engineer who has spent a billion dollars on Google and Facebook ads for Nike, Quiznos, Ashley Furniture, Red Bull, State Farm, and other brands.
Dennis has achieved 25% of his goal of creating a million digital marketing jobs by partnering with universities, professional organizations, and agencies. Through Local Service Spotlight, he teaches the Dollar a Day strategy and Content Factory training to help local service businesses enhance their existing local reputation and make the phone ring.
Dennis coaches young adult agency owners serving plumbers, AC technicians, landscapers, roofers, electricians, and believes there should be a standard in measuring local marketing efforts, much like doctors and plumbers must be certified.