Keep every client subaccount documented as your agency grows
At three clients, documentation is a nice-to-have. At fifteen, it's the difference between an agency and a pile of accounts each held together by whichever team member built it. When that person is on vacation, the client's system might as well be encrypted — and every question about it costs somebody a meeting.
The walkthrough
The steps
- 1
Connect the accounts you've already built — one click each with the Chrome app. Patchy writes the docs, so every existing client starts with real documentation instead of a blank page.
Every client account, documented to the same standard. - 2
Your team logs what they changed as they work — while they still remember why they changed it.
- 3
"How does this client's booking flow work?" is already answered. Nobody has to ask whoever built it, and nobody schedules a meeting to get unblocked.
Every client account becomes the same kind of readable map. - 4
Anyone can cover any client — what was built, how it connects, and what's changed since, without a handover call.
- 5
New hires read instead of shadow. Orientation is a link, not a week of meetings.
- 6
When a client's account changes, refresh it. Ship, refresh, move on.
Why this changes how you scale
Your team learns to read one kind of document, and that skill transfers to every client. When someone new rotates onto an account, orientation is "open the docs" instead of "book an hour with whoever built it." Any team member can pick up any client with a fraction of the ramp time, coverage gaps stop being emergencies, and "only Sarah knows that account" stops being a sentence anyone says.
The log-as-you-go habit adds the accountability half. Work on every account leaves a trail — who changed what, on which exact piece, and when — so "what's been happening in this client" is something you look up, not something you reconstruct from old Slack threads. It's also insurance: when a builder leaves, neither the docs nor the change history leaves with them.
The takeaway
Fifteen clients, one standard. Nobody books a meeting to find out how an account works — they open the docs.
FAQ
Does everyone on my team see every client?
Only if you invite them everywhere. Access is granted per client. Typical setup: account teams see their own clients, leads see all of them.
We have clients built by people who've already left. Does this still work?
Yes — that's the strongest case for it. Connect the account and the map shows what's actually there, connections included, with no dependence on the builder's memory.
What's the per-client overhead to keep this current?
A refresh when the account changes. The practical overhead is remembering to do it, so tie it to your delivery process rather than goodwill.