Most "best notes app" advice assumes your notes are only your problem. Consulting breaks that assumption immediately, and the constraints that follow decide the tool more than any feature comparison does.
Three things make consulting different:
- Client separation is not optional. Client A's material must not be discoverable from client B's context, and search that spans everything is a liability rather than a feature.
- Confidentiality is often contractual. NDAs, data-handling clauses, and sometimes a requirement that material stays in a client-controlled system.
- Your notes may be discoverable. In a dispute, what you wrote can be read by people you did not write it for.
That last point is the one people underweight, and it should change how you write, not just where.
At a glance
| Your situation | Reasonable pick | Why |
|---|---|---|
| Client mandates their tooling | Whatever they mandate | Not your call; keep your own layer separate |
| Independent, several clients | Obsidian, one vault per client | Hard separation, files you own, works offline |
| Small firm, shared delivery | Notion or the client's M365 | Collaboration, structure, permissions |
| Heavy meeting load | An AI notetaker plus your own three lines | Record and judgement are different jobs |
| Your own IP and frameworks | A separate personal vault | This is the asset; keep it out of client space |
The separation problem
The cleanest structural answer is one vault or workspace per client, plus one for yourself.
Obsidian handles this particularly well because a vault is just a folder: separate folders, separately syncable, separately encryptable, and trivially deletable at the end of an engagement — which is often a contractual requirement people forget until it is awkward. Nothing leaks between vaults because there is no shared index.
A single workspace with client tags is easier and worse. One mis-scoped search in a screen share, one exported PDF containing the wrong section, and you have a real problem. The convenience is not worth it.
Keep a fourth space for your own intellectual property: frameworks, patterns, what worked, reusable analysis. This is the thing that compounds across engagements and the thing most consultants never build deliberately. It should contain no client-identifying detail — the lesson, generalised, not the case. See evergreen notes.
Write as if it will be read
A practical discipline that costs nothing and prevents a great deal:
- Record observations and decisions, not characterisations. "Finance reported the migration slipped to Q3" is a note. "Finance is a mess" is a liability with no analytical value.
- Separate what you were told from what you concluded. Six months later the line is invisible unless you drew it. See literature notes for the same discipline in research.
- Date everything. Sequence is usually what a dispute turns on.
- Never put credentials, personal data or client secrets in your notes. Reference where they live instead.
None of this makes your notes less useful. It mostly makes them more precise.
The tools, briefly
Obsidian is the strongest default for independents: local files, no vendor holding client material, works on a plane, and per-vault separation is native. Costs you setup time and sync is your problem or a paid add-on — and if you use Sync, confirm the end-to-end encryption story satisfies your client agreements. See encrypted notes.
Notion wins for small firms doing collaborative delivery: shared pages, databases for workstreams, decent permissions. The trade is that client material sits on Notion's servers, which some engagements prohibit outright. Check before, not after.
OneNote is often the pragmatic answer when the client is an M365 shop, because it lives inside their tenant and their compliance perimeter. Weak at scale and weak at linking, but it satisfies the constraint that actually binds.
AI notetakers are increasingly standard for client calls and carry a specific risk here: a bot joining a client meeting is a recording, and recording a client without clear consent can breach both law and contract. See AI meeting notetakers.
What the notes are actually for
Three outputs matter, and they are worth building the system around:
- Commitments. Who agreed to what, by when. The most valuable and most-forgotten artefact from any client meeting.
- The evidence trail. What you were told, when, by whom — the basis for your recommendation.
- Your own pattern library. The generalised lesson, filed in your personal vault, that makes the next engagement faster.
The third is the one that makes a career compound rather than repeat. Most consultants deliver, archive, and start the next one from scratch. Ten minutes at the end of an engagement writing what you actually learned is the highest-return note-taking any consultant does. See how to keep a work journal and the weekly review.
Where ClairMind fits
ClairMind is a fast, private, phone-first notes app. In a consulting kit its role is capture between meetings — the observation on the way out of the building, the hypothesis that forms on the train, the follow-up you owe someone. Those are lost by default and they are frequently the most valuable thing you noticed all day.
It is a personal layer, not a client system of record. Keep client deliverables and controlled material where the engagement requires; use a capture tool for your own thinking, and observe the same discipline about what you write down.
More in best notes app for meetings, best notes app for freelancers, and best notes apps.