Every client promise, on the record.
Scoping calls, workshops, weekly check-ins. Knack. keeps one memory per client: what was scoped, what was promised, what changed, with the audio to settle any debate, and your notes filed where you keep them.
Per client, not per meeting
Ask what Meridian said about budget in March. Get the answer with the recording to prove it.
Both directions, tracked
What you owe them and what they owe you, pulled from the conversation, not from memory.
Notes land where you work
Markdown to your Drive, recaps to the client, deadlines to your list. No copy-paste tax.
The problem is not the meeting, it is month four
Consulting work is a long argument with a client's memory. You scoped something in January, the scope drifted in February, someone promised something in a corridor in March, and in April there is a polite disagreement about what was included.
Notes do not solve this, because notes are a summary written by one party. When two people remember a conversation differently, a summary is just a third opinion. What settles it is the recording, and specifically being able to jump to the moment rather than scrub through ninety minutes.
This is why the verify chip matters more in client work than almost anywhere else. Every line in a Knack recap links back to the second it was said, so "we agreed the migration was out of scope" stops being an assertion and becomes something you can play.
One memory per client, not one document per meeting
Most tools file a meeting and move on, which leaves you with forty documents and a search box. That is fine for finding a meeting and useless for answering a question.
The unit that matters in client work is the relationship. What did this client say about budget, ever? What have we committed to that is still open? When did the scope actually change, and who said so? Those questions cross meetings, so the memory has to as well.
In practice that means you can ask across every conversation with a client and get an answer with the receipts attached, rather than remembering which meeting it was in and opening that file.
Commitments run in both directions
The obvious half is what you owe the client, and most people track that reasonably well because it turns into work.
The half that leaks is what the client owes you: the data set they were going to send, the stakeholder they were going to introduce, the decision they were going to make by Friday. Those slip quietly, and then the delay becomes your problem in the retrospective.
Because both sides are extracted from the conversation rather than typed by whoever remembered, the record of who owed what is symmetrical. That is a much easier conversation to have in week six than a reconstruction from memory.
Your notes stay where you keep them
Independent consultants and small firms already have a system, usually some combination of a drive, an editor and something with a database in it. A tool that demands you move into its interface is a tool you will stop opening.
So recaps and transcripts sync out as Markdown to your own Google Drive, organised per client. They are readable, greppable, portable, and they feed whatever you have built on top, including your own AI tooling.
You also choose what leaves the room. A client-facing recap of scope and decisions can go to the client while your private read on the meeting stays yours.
Can clients get the recap too?
Yes. You choose what leaves the room: a client-facing recap of scope and decisions, while your private notes stay yours.
Where do my notes end up?
Markdown files synced to your Google Drive, organised per client, plus one searchable memory inside Knack. They stay readable and portable, so they feed whatever else you have built.
Does this work for video calls as well as in-person client meetings?
Knack's home turf is the in-person conversation, captured on your phone. If your week is mostly video calls at a desk, a call-native tool will fit that half better, and plenty of consultants run both: one for calls, Knack for client sites and workshops.
How do I settle a disagreement about what was agreed?
Play it. Every line in a recap links to the second it was said, so a scope dispute is resolved by the recording rather than by two summaries written from two memories.
Can I ask questions across every meeting with one client?
Yes, that is the point of keeping one memory per client rather than one document per meeting. Ask what they said about budget in March and you get the answer plus the moment it was said.
Is it awkward to record a client meeting?
Less than most people expect, and considerably less than a bot appearing in a call. One sentence in the greeting, framed as note-taking so you can be present, and the promise of an accurate written summary reads as professionalism.
What happens to recordings of confidential client work?
They are encrypted in transit and at rest, processed on infrastructure in Frankfurt, and never used to train foundation models. You can export everything and delete anything.