Thousands of files. One searchable brain.
Build a Company Brain With Obsidian: A Setup Guide
Build a company brain with Obsidian and years of scattered files stop being storage and start being a coworker. This guide walks the whole path, and it ships with a free downloadable Claude skills pack: a two-layer set of instructions you deploy in a Claude Project so Claude walks you through the entire build, from installing Obsidian to serving the vault and querying it.
Free skills and prompts for Claude and strategy work
Templates for Claude, ChatGPT and Perplexity — from diagnostics to board-ready decks.
What a company brain actually is
A company brain is one Obsidian vault that holds your organization's notes, memos, research, and decisions as linked markdown files. Every idea becomes a single note, and the links between notes form a graph: a living map of how the company thinks. Build a company brain with Obsidian and the thousands of files sitting across drives, inboxes, and old decks collapse into a single place you can search, navigate, and hand to an AI.
Picture what happens when you point an AI at years of a company's files. It reads the whole vault, maps which notes connect, and starts predicting what a team needs before anyone searches. Last month it flags a link between a two-year-old client memo and a live proposal, a connection no single person still remembered. That is the shift. The vault stops being a filing cabinet and starts being a coworker that knows everything the company has ever written down.
Scattered files
Documents live in ten drives and a hundred inboxes. Nothing connects, knowledge leaves when people do, and every answer starts with does anyone remember where.
A company brain
Every idea is one linked note in a shared graph. Context compounds, memory survives departures, and one search answers what used to take a meeting.
The rest of this guide is the build. If you already run structured prompts and skills in Claude, the brain is the missing input layer underneath them. Pair it with our Claude workflows for strategy and the brain becomes the memory those workflows read from.
Download the company-brain skills pack
6 Claude skills in two layers. One zip, free, no signup. Deploy it in a Claude Project and Claude builds the brain with you.
The Claude skills pack: build it with Claude
You can build the brain by hand with the steps further down, or you can let Claude do it with you. The pack is 6 skills in two layers. You deploy them in a Claude Project, tell the orchestrator to set up your company brain, and it runs the five worker skills in order, pausing at each stage to confirm before it moves on.
Two layers
Layer 1 is the orchestrator, the only skill you normally talk to. Layer 2 is the five worker skills, each owning one stage of the build. Say "set up my company brain" and the orchestrator drives the rest.
Company Brain Orchestrator
OrchestratorUse when. You want Claude to set up your entire company brain end to end, not one piece at a time.
Output. A guided, staged build. Claude runs the five worker skills in order, confirming prerequisites and checking in with you at each stage.
Skill file: company-brain-orchestrator
Set Up Obsidian Vault
WorkerUse when. You are starting from nothing and need Obsidian installed and a company vault created.
Output. Obsidian installed, one shared company vault created, and the handful of settings and core plugins that matter switched on.
Skill file: set-up-obsidian-vault
Ingest Company Files
WorkerUse when. Your documents are scattered across drives and inboxes and need to live inside the vault.
Output. Existing material pulled into the vault as markdown notes, with a clean note-per-source intake pattern and a start-small plan.
Skill file: ingest-company-files
Structure and Company Taxonomy
WorkerUse when. Notes are piling up and you need a shared structure so the whole team files the same way.
Output. A shallow folder scheme that mirrors the company, a naming convention, note templates, and properties: the branding of the brain.
Skill file: structure-and-company-taxonomy
Link and Build the Graph
WorkerUse when. You have notes but they are not connected, so nothing compounds into knowledge.
Output. Wikilinks, tags, maps of content, and index notes that turn a folder of files into a navigable, searchable graph.
Skill file: link-and-build-the-graph
Serve, Sync and Query
WorkerUse when. The brain works on one machine and you need the whole team to reach it and query it.
Output. The vault synced to a server with access by role, and Claude pointed at the markdown to answer, summarize, and surface links.
Skill file: serve-sync-and-query
Deploy the pack in a Claude Project
The pack is designed to run inside a Claude Project. Upload the skills once, then every conversation in that project can call them. Four steps take you from the zip to Claude actively building your company brain.
Download the skills pack
The zip contains a README and 6 SKILL.md files: one orchestrator and five worker skills. Unzip it anywhere.
Create a Claude Project
Go to claude.ai, open the left sidebar, click Projects, then Create Project. Name it something like "Company Brain" so you can reuse it every time you work on the vault.
Add the skills as Project Knowledge
Inside your project, open Project Knowledge, click Add Content, and upload the six SKILL.md files (the README too, if you like). Claude now references them automatically in every conversation inside that project.
Tell Claude to run the orchestrator
Open a new conversation inside the project and name the orchestrator. Claude asks a few questions about your company, then runs the five worker skills in order, stopping after each stage so you can confirm before it continues.
Example prompts
- "Use the company-brain-orchestrator skill to set up my whole company brain, start to finish."
- "We are a 20-person operations team with no external clients. Build us a knowledge base and walk me through each step."
- "Resume building our company brain. We already installed Obsidian and made the folders."
Tip
Name the skill in your prompt instead of describing the task. "Use the company-brain-orchestrator skill" points Claude at the exact instruction set instead of leaving it to guess. Prefer Claude Code? Drop the skill folders into ~/.claude/skills/ instead of a project.
How a company brain works, in five stages
A company brain is not one feature you switch on. It is five stages, each building on the last. Collect the files, structure them, connect them into a graph, serve the graph to the whole team, then let an AI query it. Miss the connect stage and you have a shared drive. Get it right and you have a brain.
From scattered files to a working brain
Collect
Pull every scattered document, memo, and deck note into one local vault of plain markdown, so the whole company reads from a single source instead of ten drives.
Structure
Give the vault folders that mirror the company itself, its teams, clients, and functions, so the shape of the knowledge matches the shape of the business.
Connect
Link notes to each other with wiki links, tags, and maps of content. The links are what turn a folder of files into a graph, the actual brain.
Serve
Sync the vault to a server the whole team can reach, with access controlled by role, so it becomes a shared company asset rather than one person's laptop.
Query
Point an AI assistant at the vault. Now the brain answers questions, surfaces buried links, and drafts the memo, instead of just storing files.
Build the vault by hand, step by step
Prefer to build it yourself, or want to understand exactly what the skills pack does under the hood? These are the same eight steps, by hand. You do not need the command line or any developer tooling. If you can install an app and organize a folder, you can build this.
Download and install Obsidian
Go to obsidian.md and download the app for Windows, macOS, or Linux. Obsidian is free for personal use and offers a commercial license for company use. Install it like any other app and open it once to reach the welcome screen.
Tip
Obsidian is local-first: your notes are plain markdown files in a normal folder on disk, not locked inside a database. That is exactly what makes them safe to version, sync, and hand to an AI later.
Create the company vault
On the welcome screen choose Create new vault, name it something like Company Brain, and pick a folder to hold it. A vault is just a folder Obsidian watches. Everything you add to it, every note and sub-folder, becomes part of the brain. Start one vault for the whole company rather than one per person.
Pull in the company files
Copy your existing material into the vault folder: meeting notes, client memos, research, process docs, and the text of past decks. Markdown and plain text drop straight in. For Word, PDF, or spreadsheet files, keep the original and add a short markdown note beside it that summarizes what it is and why it matters, so the brain can reason over it.
Tip
You do not need to migrate everything on day one. Start with one team or one client, prove the value, then widen. A brain with a hundred well-linked notes beats one with ten thousand loose files.
Give it structure
Create a small set of top-level folders that mirror the business: Clients, Sectors, Functions, and Internal is a good starting frame. Resist deep nesting. In Obsidian the links between notes carry more weight than the folder tree, so a shallow structure plus good linking beats a deep hierarchy nobody maintains.
Unite the notes
This is the step that creates the brain. As you write, link related notes with wiki links, add tags for clients and topics, and build a few maps of content: hub notes that link out to everything on one theme. The four methods below are the connective tissue. Every link you add makes the next answer easier to find.
Turn on the graph and search
Open the graph view to see the vault as a living network of connected notes, the closest thing to looking at the company thinking. Use the built-in search and the quick switcher to jump anywhere in seconds. As the links multiply, clusters appear around your busiest clients and themes, and the gaps show you what the company has never written down.
Put it on a server and control access
To make the vault a shared company brain rather than one laptop, sync it. The simplest route is the official Obsidian Sync service. For full control, keep the vault in a private Git repository or on your own file server, and let teammates work against the shared copy. Because the notes are plain files, this is ordinary file hosting, no special database required.
Tip
Control access the way you already control any sensitive folder: by role. Put client-confidential folders behind their own permissions, keep an internal-only tier, and give read access far more widely than write access so the brain stays clean.
Point an AI at the brain
The final step is what makes it feel alive. Feed the markdown notes to an AI assistant as knowledge, so it can search the vault, answer in your company's own context, and draft from what you already know. Ask it to find the link between two projects, summarize a client history, or turn a cluster of notes into a first draft. The brain stops being storage and starts being a coworker.
Unite the files: the four ways notes connect
Collecting files gives you a folder. Connecting them gives you a brain. These are the four tools Obsidian gives you to unite thousands of notes into one graph. Use all four and the vault stops being a place you store things and becomes a place you think.
Wiki links
Type double brackets around any note title to link two ideas. Every link is bidirectional, so both notes now know about each other and the graph grows.
Tags
Add a hash tag like a client name or a topic to any note. Tags cut across folders, so one memo can belong to a client, a sector, and a workstream at once.
Maps of content
A hub note that links out to everything on one theme. A hub for a client or a market becomes the front door a new hire opens first.
Properties
Structured fields at the top of a note, such as owner, status, or date. They make the vault filterable and let an AI reason over the notes as data, not just text.
A rule of thumb: never save a note without linking it to at least one other. That single habit, kept across a team, is what compounds a pile of documents into a graph dense enough to be useful.
Put it on a server and control who gets in
A brain on one laptop is a personal notebook. A brain on a server is a company asset. Because Obsidian keeps everything as plain files, sharing the vault is ordinary file hosting, not a database migration. There are three common routes, from simplest to most controlled.
Obsidian Sync. The official paid service syncs the vault across every teammate's device with end-to-end encryption. It is the fastest way to make a vault shared, with no server of your own to run.
A private repository. Keep the vault in a private Git repository. Every change is versioned and reversible, and you get a full history of how the company's thinking evolved, which is valuable in its own right.
Your own file server. Host the vault folder on company infrastructure or a private cloud drive, and manage access with the permissions you already use for sensitive files.
Whichever route you pick, control access by role. Put client-confidential material behind its own permissions, keep an internal-only tier, and grant read access far more widely than write access. A brain the whole company can read but only trained hands can edit stays both useful and clean.
What company branding means for the brain
Company branding here is not a logo on a note. It is the shared structure that makes ten people's notes read as one company brain instead of a hundred private systems. Four conventions carry your firm's identity into the vault itself.
A shared taxonomy. Agree on the handful of top-level folders that name your business: clients, sectors, functions, and internal. When everyone files the same way, the vault reads as one brain, not a hundred private filing systems.
A naming convention. One rule for note titles, such as client, then topic, then date. Consistent titles make wiki links predictable, so people link as they write instead of hunting for the right file.
Templates. A standard note shape for meetings, client profiles, and decisions, with the same properties every time. Templates are how the company's way of thinking gets encoded into the brain itself.
A house ontology. A small, shared vocabulary of tags and hubs that reflect how your firm actually sees the world. This is the real company branding of the brain: its structure carries your identity.
Write these four into a short one-page vault guide and pin it as the first note new hires read. That page is the constitution of the brain, and it is what keeps a fast-growing vault coherent.
What a company brain unlocks
The build pays off the day the brain starts answering questions no filing system could. These are the use cases teams reach first once the vault is linked, served, and queryable.
Instant onboarding
A new hire opens the client hub and reads years of context in an afternoon, instead of scheduling ten catch-up calls.
Proposal reuse
The next proposal starts from the last five. The brain surfaces the passages, pricing logic, and case studies that already won.
Institutional memory
When someone leaves, their thinking stays. The reasoning behind a decision lives in linked notes, not in a departed inbox.
Cross-project links
The graph connects a lesson from one engagement to a live problem in another, a link no single person would have spotted.
Faster answers
One search across the whole company replaces the group chat that starts with does anyone remember where the numbers for.
Board-ready output
The connection the brain surfaces becomes a slide. Analysis moves to a decision instead of staying stuck in a folder.
From the brain to the boardroom with Oria
A company brain ends its job at the insight. It finds the connection, recalls the client history, assembles the analysis. Then the work has to leave the vault and land in a room, which almost always means a slide. That handoff is where most knowledge systems stall, and where Oria takes over.
The brain surfaces the substance. Ask the vault to pull the option comparison, the market read, or the two projects it just connected, and it hands you the raw thinking in your own words.
Oria makes it a slide. Paste that text into Oria inside PowerPoint and it becomes a fully editable, on-brand slide in two to three minutes, on your corporate template, ready for a partner or board review instead of a manual formatting pass.
It is the same division of labor consultants already use with Claude: the model does the thinking, Oria does the deck. For the full path from analysis to a board-ready file, see how to turn Claude output into editable PowerPoint, and for the wider operating system, the full strategy engagement pack that runs on top of a brain like this.
Frequently asked questions
What is a company brain in Obsidian?
A company brain is a single Obsidian vault that holds your organization's notes, memos, research, and decisions as linked markdown files. Instead of documents scattered across drives and inboxes, every idea is one note, and the links between notes form a graph you can search, navigate, and hand to an AI. The result is a shared, queryable memory of how the company thinks.
Why Obsidian instead of a wiki or a shared drive?
A shared drive stores files but never connects them, and a traditional wiki locks your content inside a database. Obsidian keeps every note as a plain markdown file on disk, so the knowledge is portable and future-proof, while its wiki links and graph view turn those files into a connected brain. Plain files are also the easiest possible input for an AI assistant, which matters the moment you want the brain to answer questions.
How do I put an Obsidian vault on a server for the whole team?
Obsidian is local-first, so a shared vault is just a shared folder. The simplest option is the official Obsidian Sync service. For more control, keep the vault in a private Git repository or on your own file server and have each teammate sync against the shared copy. Control access by role using ordinary folder permissions, with read access granted more widely than write access.
How many files can a company brain hold?
Obsidian handles vaults with tens of thousands of notes comfortably, because each note is a small text file. The practical limit is not the file count but the linking. A vault of a few hundred well-linked notes is a far better brain than a dump of ten thousand unconnected ones, so invest in the links, tags, and hub notes rather than sheer volume.
How does the company brain connect to Oria?
The brain does the thinking and Oria does the presentation. When the vault surfaces the connection, the client history, or the analysis you need, paste it into Oria inside PowerPoint and it becomes a fully editable, on-brand slide in two to three minutes. The brain turns scattered files into an insight, and Oria turns that insight into a board-ready deck.