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

Every client gets a dedicated Account folder (accounts/{client_name}/) containing their specific notes, contacts, meeting summaries, and linked projects. When you work inside an Account or ask Dori a question scoped to a client, Dori prioritizes files from that client’s folder. This is a vault-organization convention, not a hard database-level access boundary — everything is plain files you can see and re-file if something lands in the wrong place.

What’s actually driving this, and what it costs

Directory isolation, account file scoping, and vault path filtering are enforced by Dori’s local background engine at zero API cost — the isolation 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, operating strictly on the scoped files you selected.

Scoped questions you can ask

Because Dori understands account boundaries, you can query client information with total precision:

• “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)

A real-world scenario: Managing 12 client accounts simultaneously

1. Client A Call: You finish a meeting with Meridian. The meeting recording, extracted tasks, and follow-ups are automatically saved under accounts/meridian/.
2. 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 — completely isolated from Meridian’s files.
3. Drafting a Client Deliverable: You ask Dori to draft a proposal for Zenith. Dori reads only Zenith’s vault documents, ensuring no proprietary terms or figures from Meridian ever enter the response.

Why this is critical for advisors and agencies

• Data Privacy Compliance: Client data remains in isolated Markdown directories on your Mac. Nothing is merged into a shared cloud AI memory pool.
• 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.