Life memory for consultants: four clients, one day
Wednesday, 11:12am. You have eight minutes between a retail client's pricing workshop and a manufacturer's steering committee, and the second one is going to open with a question about the plant. You know the plant came up before. You think it was the operations lead, you think it was week three, and you are fairly sure it was mentioned in a way that made someone uncomfortable. What you have to work with is a folder with 340 files in it and a Slack search that returns nothing because the conversation happened on a call.
So you walk in and say "remind me where we landed on the site consolidation question," which is the consultant equivalent of asking someone to repeat their name. It works. It also costs you a small amount of the thing you are actually selling, which is that you have been paying closer attention to their business than they have.
Four clients means four contexts, and no tool holds any of them
Consulting is a context-switching job disguised as an analysis job. The engagement's real state lives in a hundred small facts distributed across calls, decks, email, dashboards, and the version of the model you sent finance on a Tuesday and then superseded. A notetaker records the calls. But the reason you cannot answer the plant question is not that a transcript was missing. It is that the answer requires connecting something said on a call in week three to something you read in a data room in week five, and nothing you use holds both.
LUCI holds both, because it is not a meeting tool. It is your computer's history. Your whole day on the computer: meetings, email, decks, everything in between. Both sides of the audio on a call with nothing joining it, what was on screen, the documents, the browsing. It is understood on-device and stored encrypted on your machine, with no cloud processing of your memory. Cards, keys, and passwords are blacked out before anything is saved, and private windows can be excluded.
Then your agent, in Claude, Cursor, or Codex, connects through the Agent Bridge. LUCI connects itself, nothing to set up. It queries your memory in natural language and reads only what a question needs. The practical effect is that the model you already use for drafting finally knows which client you are in.
Four workflows
The eight minutes before a client call. "When did anyone at this client first mention the plant closure, and what exactly was said." That covers calls and documents at once, which is why it works, and it takes the length of a lift ride rather than an afternoon.
Decision trails. Engagements do not go wrong because someone forgot a fact. They go wrong because a decision quietly changed owner. "Show me every time the scope of phase two came up, and who pushed back each time." You get the sequence, including the version where the CFO agreed on a call and the version where their chief of staff walked it back in email nine days later. That is the artefact you want on hand when the conversation about the change order happens.
Deliverable archaeology. "Which version of the cost model did I have open when I sent the finance summary." Consultants live with the fact that six near-identical files exist and only one of them was ever shown to the client. Your memory knows which one was actually on your screen at 4:15 on that Thursday, because it was there.
Weekly updates and engagement handover. Your agent distills each day and writes your Life: a folder of ordinary files on your disk. The status note stops being a memory exercise on Friday afternoon and becomes a matter of reading back your own week. When you roll off, there is a record to hand a colleague instead of a repository and a two hour brain dump.
The honest part
Your engagements run under confidentiality terms, so the tradeoffs need to be on the table. Because capture, understanding, and storage all happen on your machine, there is no vendor receiving client information, which is the thing standard NDA language is actually about, and there is no bot in the participant list for client IT to block or for a client to object to. Disclosure and consent are still yours to handle, and so is any engagement term that restricts recording outright. Some clients will say no. That is a legitimate answer and the tool does not overrule it.
The agent is a real seam and worth naming precisely. Your memory stays on your machine, but what an agent reads reaches that model's vendor. If you ask Claude about a client's cost structure, Claude's provider sees what Claude reads, and that is a disclosure your NDA may well cover. Check before you wire it up on a sensitive engagement, and remember that you can query your memory directly without an agent involved. The structural point is that you choose the agent and the memory outlives it, so no single vendor ends up holding your engagement history hostage. Two further caveats: LUCI is not open source, so the on-device architecture is a claim you weigh rather than inspect, and it only remembers time when the machine was on and capturing. The site visit where you took notes on paper is not in there.
Where to start
Pick the engagement with the most stakeholders and run it for two weeks. The test is simple: next time someone asks when a thing was first raised, see whether you answer in fifteen seconds or promise to come back to them.
Download LUCI for Mac or Windows, free, or read the NDA and bot-blocking detail on our page for consultants.
