Draft status: Outlined and ready to expand. The provocative framing is set. Fill in with agency-specific stories and case scenarios before publishing.
The day your best person gives notice
It happens at every agency. Someone senior , your director of strategy, your top account lead, the person who’s been on that big client for four years , gives notice. Two weeks.
You’re congratulating them and calculating simultaneously: what exactly do we lose?
Not just their labor hours. Their knowledge. The relationship history with that client. The institutional understanding of why your positioning is what it is. The context behind 50 past decisions that shaped how your agency works today. The competitive intelligence they’ve accumulated across every category they’ve ever worked in.
That knowledge is leaving. And it’s probably not written down anywhere accessible to anyone else on your team.
[EXPAND: Make this visceral. Tell a story , real or composite , about what it actually felt like to lose a senior person and only then realize how much institutional knowledge they held. What went wrong in the months after?]
What “institutional knowledge” actually means
It’s a phrase people use abstractly. Let’s make it concrete:
Process knowledge , Why your workflow works the way it does. Not just what the steps are, but the context behind them. “We do the creative brief before client alignment because of what happened with Client X in 2021.” Nobody new knows that story.
Client relationship history , Not the CRM notes (those are always incomplete). The actual texture of the relationship. What the client responds to. What they don’t say in meetings but clearly mean. What the real decision-making hierarchy actually is, not what the org chart says.
Category expertise , The accumulated knowledge about a client’s industry that your senior person has built across 3+ years of working in it. The competitive landscape they’ve watched evolve. The trend they spotted 18 months ago that turned out to be right.
Tactical reasoning , Why you chose that messaging angle over the other one. Why you structured that proposal the way you did. Why that campaign worked and the similar-looking one from two years earlier didn’t.
None of this is in your Slack. None of it is in your project management tool. Some of it is in scattered Docs that nobody can find. Most of it is in one person’s head.
[EXPAND: Maybe a table here. “Where agency knowledge lives vs. where it should live.” Column 1: current state. Column 2: what a knowledge base changes.]
The junior-senior interruption tax
Here’s a less dramatic but more expensive version of the same problem:
Your junior account coordinator needs to know how to handle a specific client situation. So they Slack your senior strategist, who is in the middle of a deliverable. The senior strategist stops, answers, and then needs 10 minutes to get back into flow.
Multiply that by 8-10 interruptions a day. You’ve just consumed 1-2 hours of your highest-cost person’s day on interruptions that a good knowledge base could have answered.
[EXPAND: Quantify. If a senior strategist bills at $X/hour and loses Y hours/week to junior interruptions, what’s the annual cost? Then contrast with the cost of a knowledge base.]
What a team second brain changes
When your agency has an AI-maintained knowledge base:
- A junior AE preparing for a client call can query the vault: “What do we know about this client’s competitive position?” and get a sourced brief, not a Slack thread that nobody answers at 8:45pm.
- When someone new joins, they can query the knowledge base to understand how the agency thinks , methodology, standards, past decisions , before their first client call.
- When a senior person gives notice, you have 4-6 months of their knowledge already captured from their past work, not scrambling to extract it in 2 weeks.
- When you’re pitching in a new category, you can query the competitive intel vault and find research from 2 years ago that directly applies.
The knowledge base doesn’t replace your people. It makes their knowledge accessible to the whole team.
[EXPAND: A concrete scenario. A new account manager, 90 days in, queries the vault before a client call. What they find. How it changes the call. This is the payoff paragraph.]
The emergency extraction scenario
[NEW SECTION , high value]: When a senior person gives notice, we offer an emergency knowledge extraction: we work with them during their notice period to compile their key knowledge domains into the vault. Past project docs organized and summarized. Their competitive intelligence compiled. Their process knowledge documented and coded.
This isn’t a replacement for the ongoing system , it’s a triage option. Two weeks is not enough time to build a comprehensive knowledge base. But it’s enough time to get the highest-priority knowledge extracted before it walks out the door.
Building it before you need it
The agencies that call us in a panic are usually calling because someone just gave notice or because a major client relationship was rocky after a team change.
The agencies that call us when things are going well are building the knowledge infrastructure before they need it. They’re compiling their institutional knowledge while they have the people to contribute to it.
[EXPAND: Frame this as proactive vs. reactive. The cost of building a knowledge base now vs. the cost of scrambling to rebuild institutional knowledge after losing 3 senior people in a year.]
Interested in building your agency’s knowledge base? See how we build team second brains →