The Client Tracker: One Source of Truth Behind Every Agency We Run

One Google Sheet holds every client, every agency, and every dollar in our network. Open it and you know — in ten seconds — who the client is, which agency owns them, what they pay, what package they bought, and what we made. That sheet is the Client Tracker, and it is the spine of how we run many agencies on one set of rails.

Most agencies keep this in someone’s head. Or in a CRM nobody updates. Or spread across five tools where no two numbers agree.

We keep it in one place. A shared, always-current Google Sheet that every operator and every AI agent reads before they do anything. It is deliberately boring. Boring is the point — boring is what scales.

This is the definitive article on what the Client Tracker is, how it’s built, and why it’s organized the way it is. We publish it openly because the whole model only works if it’s transparent: if you want to grow your own agency on our infrastructure, you should be able to see exactly how we operate.

What the Client Tracker actually is

The Client Tracker is the master roster. One row per client. It answers the questions an owner, an operator, or an agent asks a hundred times a week: Who is this? Whose is it? What did they buy? Are they paid up? What did we earn?

It is not a CRM and it is not fancy software. It’s a spreadsheet on purpose, so anyone — a 19-year-old running their first agency, a new operator, or a Claude agent doing a weekly sweep — can read it without a login, a training course, or a license fee.

It’s easy to confuse three things we use every day, so let’s separate them cleanly:

The Client Tracker sits on top. Every relationship in it has a Success Tracker proving results and a Basecamp project doing the work. The tracker is the index that ties them all together.

The columns: what every row shows

Each client is one row. Here’s what the columns hold and why each one earns its place:

The naming convention is the whole trick

The most important column is Basecamp, because the project name isn’t just a label — it’s a code. Read the name and you instantly know the client’s tier, which agency owns them, and whether they’re active. This is the same strict system we teach in Naming Projects and Threads in Basecamp, extended with an agency owner in front.

Tiers tell you the size

Every client sits in a tier, and the tier is baked into the name. We used to run four; three matter now:

Yes, Quickstart is labeled Clients 4 even though it’s the third tier — “Silver” used to be tier 3 and we never renumbered. The full explanation lives in the Basecamp naming guide. One-offs get Special Project: and program participants get labels like AI Builder:.

The agency prefix tells you whose it is

Here’s the extension that makes the tracker work across a network instead of one shop. In front of the tier, we put the owning agency:

• Roof Launch Marketing’s Clients 4 – Quickstart: …
• HVAC Growth’s Clients 4 – Quickstart: …
• Ensiteful Marketing’s Clients 4 – Quickstart: …

No prefix means it’s a house account run directly by Local Service Spotlight. A prefix means one of the young-adult-run agencies in our network owns the relationship. That single word decides whose revenue it is, whose rev-share it feeds, and who gets coached on it.

Grouped by agency — the network made visible

The revenue tab isn’t one flat list. It’s grouped into sections with a header per agency and a Total row under each: the house clients under Local Service Spotlight, then a block for each agency — Roof Launch Marketing, HVAC Growth, Ensiteful Marketing, and the rest. At the bottom sits an UNPAID section so nothing gets quietly forgotten.

Scroll the tab and you’re literally looking at the two-sided network: local service businesses paying on one side, the agencies serving them on the other, all running on the same rails.

One account manager. Always exactly one.

Every project has a single owner — the person Accountable in the RACI model (Responsible, Accountable, Consulted, Informed). Not a committee. Not “the team.” One name.

That’s a rule, not a preference. When two people own something, nobody does. The Accountable person is the one who loads SMART tasks into Basecamp, runs the client calls, and files the weekly report. The tracker and the Basecamp project always make it obvious who that one person is — including when an account changes hands, so a client is never orphaned.

Revenue and rev-share: how we keep the split fair

The tracker isn’t just a client list — it’s a monthly P&L. Alongside each month’s Revenue tab are two more:

Revenue minus labor minus tools is the real margin on each agency’s book. That’s the number that makes rev-share fair instead of a guess. We have Claude do the arithmetic — read the tabs, attribute revenue and cost to the right agency and the right person, and tell us what each side actually earned. When the math is transparent and the same for everyone, nobody has to wonder if the split was fair. They can see it.

Every package ties to a defined SOP

The Type column is never vague. Every value maps to a real package with a real price and a written, agent-runnable SOP behind it. That’s what lets an operator — or an agent — deliver it the same way every time:

Sell any of these and the delivery isn’t improvised — it’s the same documented process every time, which is exactly what makes it safe to hand to a new operator or a Claude agent. This is the same discipline behind our 239-task skill library: every job has a definitive article, and every package points at one. See the full menu on the pricing page and the Skill Pack Library.

How agents actually use the tracker

This is where the boring spreadsheet earns its keep. Our agents read the Client Tracker on a schedule and act on it:

• Daily and weekly sweeps pull the active roster — every row without an XXX — and check each project’s analytics, so we catch a drop before the client does. See how we run weekly AI-agent audits across every client.
• The weekly Friday MAA (Metrics → Analysis → Action) rolls up from those sweeps. The tracker tells the agent who’s active, who owns them, and where the Basecamp project is; the agent files the MAA report in the right project.
• Ownership routing — because every row names the Accountable person and the owning agency, an agent always knows who to tag and where a report belongs.

The tracker is what makes the whole thing legible to an agent. Without it, an AI agent is guessing. With it, the agent knows exactly who the current account manager is, whose revenue a result affects, and which Basecamp project to update.

Why centralized infrastructure wins

Here’s the part most people miss. The agencies in our network don’t build their own systems. They plug into ours.

We give AI Builders free Basecamp projects inside our account — so they look professional from day one, don’t pay for their own software, and (this is the key part) their client projects show up in the same Client Tracker we all read. One tracker. One skill library. One knowledge base. One hosting fleet. One set of naming rules and one meetings checklist.

That means an agency owner doesn’t have to think about tools, servers, SOPs, reporting formats, or how to wire up an AI agent. It’s already built. They get to spend their time on the two things that actually matter: the relationship and the work.

Intrapreneurs, not lone entrepreneurs

The people running these agencies are mostly young adults building real books of business — but they’re not doing it alone in a garage. They’re intrapreneurs: building their own agency inside a system that already has the rails laid down.

That’s better than being a lone entrepreneur, and the tracker is why. An entrepreneur starting cold has to build the infrastructure and win the clients and figure out fair accounting. An intrapreneur on our network inherits the infrastructure, gets coached on the clients, and can see the fair accounting on a shared sheet. Same upside, a fraction of the risk. The AI Builder Program and our agencies run on exactly this.

Why we publish this openly

We could keep all of this behind a login. We don’t, on purpose. The model is a two-sided network — paying local service businesses on one side, agencies delivering the work on the other — and a network only earns trust when both sides can see how it runs.

So the rules are public. Basecamp Basics — because if it didn’t happen in Basecamp, it didn’t happen. The Meetings Checklist — because a meeting is a process with deliverables on both sides, not a calendar event. RACI, so the right people are in the right conversations. And this — the Client Tracker — so you can see how it all ties together.

Centralize the communication in Basecamp. Centralize the roster in the tracker. Tie every package to an SOP. Put one person in charge of every account. Do that, and you get a system that’s fair to the client, fair to the agency, and simple enough that both humans and agents can run it.

That’s the Client Tracker. Boring, transparent, and the reason we can run many agencies without the whole thing turning into chaos.

Related reading: Behind the scenes: how we published this · Basecamp Basics · Naming Projects & Threads in Basecamp · The Meetings Checklist · Practice RACI Always · The Success Tracker · How AI Builders Do MAA · Free Basecamp Access for AI Builders · The Skill Pack Library · Why We’re Building a Two-Sided Network · How It Works