Agencies and consultancies sell what their people know about each client. That knowledge sits in briefs, meeting notes, brand folders and a few people’s memories, and it leaks at every handover. This page is about where it leaks and what stops it.
Service firms are unusually exposed to this. Every client is a separate body of facts, every meeting produces promises, and every departure takes context with it. The tools most firms already use (a task board, a chat tool, a shared drive, a CRM) each hold part of the picture. None of them holds the part in between: which fact is current, what was promised in which meeting, which of forty logo files is the right one.
The agency workflow, and where it breaks
The work runs in a loop. A brief comes in and becomes a plan. The plan becomes deliverables built from brand assets. Client meetings review the work and produce commitments. Reports go back with numbers the client will quote to their own boss. Each step depends on the one before, and each step is usually owned by a different person.
The evidence below comes from two agency engagements that used this method: Suncoast Interactive, a marketing agency of roughly eight people in Florida, and Inside Studio, a creative and social-media agency in Colombia serving about 20 client brands. Both approved the numbers for publication.
Swipe to compare
| Where | What we saw | What changed |
|---|---|---|
| Meeting commitments | After one client review at a Florida agency, 13 actions were agreed across six owners and 3 reached the task board. The client ended up chasing the agency for its own promises. | A meeting-to-task flow drafts every commitment, checks it against open tasks and waits for a person to approve. Its first live run captured 8 of 8 action items (a different meeting, so not a controlled comparison). |
| Client facts | A client’s active store count was assumed at 37 in working documents. The verified number was 33. | One canonical facts file per client. The correction was written once, with its source, and the wrong number stopped resurfacing. |
| Brand assets | A creative agency held 6,213 files for one client group, with one brand name spelled two ways, a 36-page brand manual made entirely of images and the same logo duplicated dozens of times. | An asset registry filled in a fixed order: brand books, manuals, logos, fonts, latest report, last two grids, approved pieces. One day’s sweep produced 46 candidate brand values for the client to confirm. |
| Briefs and knowledge in people’s heads | One traffic lead ran 20 brands from memory, an iPad and a spreadsheet. When the person who reconciled hours went on leave, the account team lost its numbers. | Process maps for traffic, creative and management, written from the team’s own sessions, so the next person starts from a page instead of a handover call. |
Why another tool usually does not fix it
Inside Studio had been through Excel, then Jira, then Slack, then a ClickUp trial, and was drifting back toward Excel. Each tool promised order and each needed someone to keep it fed. A partner set the rule for the next attempt: one chance. The production lead put the fear precisely: stepping out of the operation for a month to feed an AI was acceptable for one person, but asking every lead to do it would repeat what happened with Slack.
The lesson is not that tools are bad. It is that the missing piece is structure beside the tools, maintained as part of work people already do, rather than a new place everyone has to remember to visit. At Suncoast the task board, chat, drive and outbound tool all stayed. The brain sat next to them and held what they did not.
What a structured brain changes
In practice it is a small set of agreements, written down so people and AI agents can follow them the same way.
- One file per client with the baseline, canonical facts, channel strategy and house rules. House rules come from real failures, such as a lead definition that excludes raw click and view events after a previous vendor double-reported conversions.
- One process map per recurring workflow, so a new account manager can run a monthly report without a week of shadowing.
- A task ledger with receipts, recording where each commitment came from and what counts as done, next to the task board rather than instead of it.
- An asset registry with one canonical version of each file and a rule for discarding duplicates.
- Human approval before anything an agent drafts reaches a client or the task board. When one of Inside Studio’s clients said the agency was abusing AI and wanted more human touch, this is what made the human judgment visible.
Once that exists, AI workflows become testable. At Inside Studio the committee rejected the first AI-assisted content plan in the room because it did not mention a single product. Five days later the same pipeline, now reading the brand files and the committee’s quality bar, produced a plan for one brand that was approved to move to design.
What we have not measured
Neither engagement has measured hours saved, margin per account or client retention yet. Inside Studio’s work is in its first month, and its 46 brand values are candidates the client was asked to confirm, not a finished brand system. Suncoast’s 3 of 13 and 8 of 8 come from different meetings. We publish those caveats with the numbers because a firm deciding whether to do this deserves them.
For consultancies the shape is the same with different nouns: engagements instead of campaigns, findings instead of brand assets, steering committees instead of client reviews. If you want to do the groundwork yourself, our Google Drive knowledge base guide walks through it.
When you do not need this
If you are under about three people, serve one main client, or already keep everything in one tool that everyone actually uses, you do not need a structured brain. The leaks described here come from handovers between people and tools, and with few handovers there is little to leak. A tidy shared folder and a habit of writing decisions down will serve you well until the team or the client list grows.