Keep every client's context separate
Hold a dozen clients' worth of context in one app without notes, pricing, or AI memory ever bleeding together across accounts.
For: consultants, agency leads, and advisors juggling multiple client relationships at once
If you’re a consultant, agency lead, or advisor managing multiple clients and terrified of mentioning Client A’s strategy during a call with Client B — this is for you.
When you use generic AI tools (ChatGPT, Claude web) for multiple clients, context bleeding is a constant risk. If you upload pitch decks, pricing models, and strategy notes for five different clients into the same chat window or account memory, the AI can accidentally reference Client A’s internal pricing while helping you draft a proposal for Client B. A slip like that takes a five-second copy-paste to cause and a lot more than five minutes to explain away.
How account isolation works
Dori deliberately doesn’t solve this with a hidden access-control layer that decides on your behalf what’s safe to surface. Every client gets a dedicated Account folder (accounts/{client_name}/) containing their specific notes, contacts, meeting summaries, and linked projects — a structure you can see and edit directly, not a black box. When you work inside an Account or ask Dori a question scoped to a client, Dori’s search and drafting prioritize that client’s folder over the rest of your vault.
That’s a deliberate tradeoff: a transparent, file-based boundary you can verify and fix yourself beats an opaque one you have to trust. If a note ever lands in the wrong client’s folder, you’ll see it sitting there and can move it — the same way you’d notice and fix a misfiled document today.
What’s actually driving this, and what it costs
Directory organization, account file scoping, and vault path filtering are handled by Dori’s local background engine at zero API cost — the scoping itself never touches your AI provider or its bill. Drafting deliverables or summarizing account histories is the part that does, using your connected AI provider against the account’s scoped files.
Scoped questions you can ask
Because Dori understands account boundaries, you can query client information scoped to one account:
- “Summarize all open action items for Meridian Corp only.”
- “What did we agree regarding Q4 pricing during my last call with Acme?”
- “Draft a monthly status update using notes from the Zenith account.”
- “List all key stakeholders linked to the Apex account.”
See Accounts for complete details.
Quick setup (one time, about two minutes)
Create an Account per Client
Go to Accounts → New Account and create an entry for each client (e.g., Meridian, Acme, Zenith).
Link Contacts & Projects
Assign client contacts to their respective Account under People, and assign client-specific work to their Project.
Work in Scoped Context
Whenever you take notes or run queries from an Account page, Dori scopes its search and drafting to that client’s folder.
A real-world scenario: Managing 12 client accounts simultaneously
- Client A Call: You finish a meeting with Meridian. The meeting recording, extracted tasks, and follow-ups are automatically saved under
accounts/meridian/. - Switching to Client B: Ten minutes later, you hop on a call with Zenith. Open Zenith’s Account page in Dori. Dori’s interface displays Zenith’s notes, history, and open tasks, drawn from Zenith’s own folder.
- Drafting a Client Deliverable: You ask Dori to draft a proposal for Zenith. Dori drafts from Zenith’s vault documents, scoped to that account — the same folder structure that lets you audit exactly what went into the draft.
Why this is critical for advisors and agencies
- Local, Not Pooled: Client data stays in its own Markdown directory on your Mac. Nothing is merged into a shared cloud AI memory pool the way it would be in a generic chat tool.
- Instant Client Context Switching: Walk into any client meeting with complete context ready in seconds, no matter how many accounts you manage.
- Clean Exportability: If a client engagement ends, their entire history lives in one dedicated folder (
accounts/{client_name}/) that you can easily archive or hand off.
Go further
- Want to track client pipeline stages? See Client relationships without a CRM.
- Need to review a client proposal before sending? Use Council to run your draft through a specialized critique pipeline.
- Need to send a client bundle to another tool? Create a scoped Handoff containing only that client’s files.
