How I structure my vaults for my Obsidian business second brain

First step is the thinking/building/product split I mentioned inside a single project here https://www.skool.com/ai-automation-society/how-i-structure-projects-so-my-obsidian-second-brain-works-efficiently?p=18e6d9d9

But once you're managing a business or multiple clients, you need three more layers on top of it:

1) Canonical vault — this is your business's protocols and SOPs. Not project-specific, this is the stuff that's true across every project: your frameworks, your qualification criteria, your playbooks. This is what compounds. Every project's thinking folder feeds into this when something is reusable, not just filed to Obsidian and forgotten.

2) Client vault — one vault, individual folders per client, each with its own knowledge base. Client history, decisions made, what's worked and what hasn't for them specifically. This is different from the canonical vault because it's not reusable across clients, it's specific context that needs to persist for that one relationship even as projects with them come and go. So the full picture is: project-level thinking/building/product folders feed into either the canonical vault (if it's a reusable pattern) or the client vault (if it's client-specific context) once a project checkpoints.

3)Your personal Obsidian second brain sits above both, for the stuff that's neither business protocol nor client-specific, just your own accumulated knowledge.

Curious to always learn, how are others here doing it?

3 comments

How I structure my vaults for my Obsidian business second brain