Claude Code for consultants

Every client gets its own thread, its own promises, its own half-remembered context from the last call. You are the IT department, the account manager and the delivery team. Here is what a system that files itself actually does about that.

Consulting is a memory problem wearing a delivery problem's clothes. You are not short on expertise. You are short on a reliable place to put what you learned on Tuesday's call so it is still true, and still findable, when the client emails on Thursday asking about the thing you already told them.

Most consultants solve this with a mix of a notes app, an inbox and a bad feeling that something from last month's engagement is about to surface at the worst possible time. The notes app remembers exactly what you typed. It does not remember what changed, what got decided, or what you owe whom. That gap is the entire job when you are running four clients at once with no one to hand the filing to, which is exactly the problem covered on the researchers page from a different angle, and the reason the book behind this site exists at all.

What it looks like after a call

You get off a client call. Instead of typing notes into a doc that will sit there until you need it, you hand the transcript or your rough notes to the system, and it does the filing: which client this was, what changed since the last touch, what you now owe them and by when. That is the shape of automatic AI meeting notes that file themselves, and it is the difference between "I have notes somewhere" and "the file is current."

The harder half is the follow-up, not the note. A consultant's real liability is the promise that quietly falls off the list: the deliverable you said would land Friday, the intro you said you'd make, the question you said you'd chase down. A system worth using tracks those the way a good account manager would, which is the whole subject of the follow-up tracking system, no CRM page.

The cost of getting this wrong is not abstract. A client who has to repeat themselves, or catches you not remembering a commitment you made two weeks ago, does not conclude you are busy, they conclude you are not paying attention to their account specifically. Trust in a consulting relationship is built almost entirely out of small moments like that, and it erodes faster than it builds. A system that remembers on your behalf protects the relationship even on the weeks when you genuinely are stretched too thin to hold everything in your head.

Where this differs from just taking better notes

The instinct is to reach for a better notes app. That fixes capture, not upkeep. Nothing about a nicer editor decides that the PDF a client sent belongs with the thread from March, or updates three other pages the moment one fact changes. That is the actual failure mode of every notes-first tool, and it is worth reading in full on the site's role guide, because it applies to nearly every client-facing role, not just consulting.

What changes the outcome is permission, not software: an assistant that is allowed to read the mail and the transcripts you were already generating, and to write back into a file the moment something changes, without you copying and pasting it there yourself.

Setting it up

None of this requires an IT department, because you are the IT department. It is plain files on your own machine, and a habit of talking to them the way you would brief a very literal associate. If you want the same approach built and run for you rather than set up yourself, that is worth a separate conversation, covered below.