The two kinds of knowledge

Before you feed Claude any context at all, it helps to know this: not all of your knowledge is the same. There are two kinds, and treating them the same is exactly where teams come unstuck.

Static and dynamic

Static knowledge is the stuff that changes rarely: your standards, how you actually operate, your strategy, your pricing. It is small enough to hold in your head, which is exactly why it is worth writing down properly, once, and keeping it right.

Dynamic knowledge is the opposite: it changes constantly. Emails, calls, meeting transcripts, whatever is sitting in your CRM right now. It is huge, it is messy, and by the time you have copied any of it into a document, that copy is already out of date.

Mix the two up and it breaks. A stale pricing sheet is treated with the same confidence as this morning's call notes. Handle each one right, on the other hand, and the two start to compound together.

Keeping static knowledge trusted

Static knowledge only stays useful if it stays small and stays correct. That comes down to three habits.

1. 01
   One guarded place, kept deliberately small

   Do not let it sprawl. The moment it becomes a dumping ground, nobody trusts it, and nobody wants to be the one who has to read the whole thing.
2. 02
   A human approves every change before it counts

   Someone blesses each addition before it becomes part of the core. That single gate is what keeps the whole thing trustworthy.
3. 03
   Date every fact

   A confident answer built on a stale fact is the worst kind of wrong, because nothing about it looks wrong. A date lets anyone spot it in a second.

It's a team sport

Building and maintaining that core knowledge is not a solo project you hand to one person and forget about. It works best as a loop the whole team runs together.

1. 01
   Allow play, then share the wins

   Let people experiment with Claude in their own corner of the business, and make it normal to show off what worked.
2. 02
   Codify the best into the core

   When something proves itself, harden it and fold it into the guarded core knowledge, so everyone benefits from it, not just whoever found it.
3. 03
   Embed everywhere, then measure the value

   Push it out to the places people actually work, and keep an eye on whether it is genuinely saving time, not just whether it exists.

Find a champion to own this as a real, ongoing function, not a side project someone picks up between other things. Knowledge that nobody owns quietly rots.

Dynamic knowledge: connect, don't copy

Dynamic knowledge is too big and moves too fast to store. The right move is to leave it exactly where it already lives, in your inbox, your call recordings, your CRM, and connect Claude to read it live, at the moment you actually need it.

How you build it: loop one

You do not need a finished knowledge base to start. You need a first one, and a way for it to grow. That is loop one, the loop you run to get set up.

Get your knowledge in, build the Project on top of it, and every output improves from there. Once it is running, a second loop takes over: the one that keeps it alive.

How you keep it alive: loop two

New context arrives automatically as you deliver work: calls, emails, tickets, decisions. Capturing it is the easy half. Deciding what counts as trustworthy is the real work.

Next up