Claude Code and Obsidian: Build a Business Knowledge Base So You Stop Re-Explaining Your Company
Every new AI chat starts from zero, so you retype who your clients are, how you price and what the team does. Here is how operators are putting the business into an Obsidian vault that Claude Code reads at the start of every session, what it costs and what it gets wrong.
Claude Code and Obsidian for a small business
You open a new AI chat to draft a client update and spend the first five minutes typing the same background you typed yesterday: who the client is, what you charge them, who on your team handles them, what went wrong last month. Then the draft comes back generic anyway, because a paragraph of context is never the whole picture. Multiply that by every task, every day, and the AI is costing you the time it was supposed to save.
The fix that keeps showing up among operators is boring on purpose: write the business down once, in plain text files, and have Claude read them before it does anything. Obsidian holds the files. Claude Code reads them. This guide covers how to set that up for a small company, what it really costs and the parts the enthusiastic posts leave out.
Two operators who built this
The clearest example on this site is How a 50 Property Real Estate Operation Gave Claude Full Context Before Typing a Word. Barrett Linburg runs three operating companies and more than 50 multifamily properties in Texas. He put the operation into an Obsidian vault as short notes, one topic per file, linked them together and wrote a single master instruction file that tells Claude how the company works and how to navigate the notes. His post reached 76.3K views, and he describes the next step as building specialist agents, a deal analyst and a legal devil's advocate, on top of the same vault. He does not report time saved in hours, so treat it as a pattern, not a measured result.
The second is David Johnson-Igra, a former executive ghostwriter profiled by Fortune in May 2026. He lost most of his clients to AI and rebuilt the business around context: an Obsidian knowledge graph of every interview, post and public statement an executive has made, plus Python analysis of about 4,000 rows of their LinkedIn history, which Claude draws on through MCP when drafting. He does not disclose revenue. The lesson from both is the same: the model was never the bottleneck. The missing context was.
How the setup works
Obsidian is a free note app that stores everything as ordinary Markdown files in a folder on your computer, called a vault. Notes link to each other with double square brackets, so a note about a property can link to its owner, its vendors and its open issues. There is no proprietary database. If Obsidian disappeared tomorrow, your notes would still be readable text files.
Claude Code is Anthropic's agent that works directly with files on your machine. When you start it inside a folder, it automatically loads a file called CLAUDE.md from that folder at the start of every session. That file is where you write who you are, what Claude's job is and where things live. Claude then opens the specific notes a task needs, reads the bracket links as plain text and can follow them to the linked file by name. You do not need an Obsidian plugin for any of this. Claude Code just reads the folder.
Anthropic's own guidance is to keep each CLAUDE.md under about 200 lines, because longer files take up context and Claude follows them less reliably. A CLAUDE.md can also pull in other files with an at-sign followed by the file path, such as @company/pricing.md, up to four levels deep, which is how you make a few always-relevant notes load automatically without bloating the main file.
A worked example: a five-person property management firm
Picture a property management company with five staff, about 180 units across 22 owners, and a steady stream of the same writing tasks: monthly owner updates, vendor scope requests, lease renewal letters, answers to "why was my distribution lower this month?" Today the office manager writes those from memory and old emails. The owner wants Claude to draft them, but every chat starts blank.
The vault has five folders. Company holds pricing, the management agreement summary, team roles and the house writing style. Owners has one note per owner with their properties, how they like to be updated and any history worth knowing. Properties has one note per building with unit count, open maintenance items and links to the owner and vendors. Vendors lists who does what, rates and response quality. Processes holds step-by-step notes for renewals, move-outs and month-end.
Now a monthly update takes one sentence: "Draft the November update for the Elm Street owner using the property note and the maintenance log I just pasted." Claude reads CLAUDE.md, opens the Elm Street note, follows the link to the owner note to see they prefer short updates with numbers first, and drafts. The office manager checks the numbers against the accounting system and sends. The firm in this example is illustrative. Building the first version of the vault is roughly a day of work spread over a week, and most of that is writing down things that were only in people's heads.
Step by step: build it this week
Step 1: Log what you re-explain for five working days
Keep a note open and every time you type background into an AI tool, or explain something to a new hire, write one line: "how we price cleanings," "which owners hate phone calls," "our refund rule." After a week you will have 20 to 40 lines. Each line becomes a note. This list matters more than any software choice, because it tells you what the vault needs on day one.
Step 2: Install Obsidian and create the folder structure
Download Obsidian from obsidian.md and create a new vault in a normal folder, for example Documents/company-brain. Create folders that match how you think about the business: company, clients or owners, properties or projects, vendors, processes, decisions. Keep it shallow. Two levels of folders is plenty for a small company.
Step 3: Write short notes, one topic each, and link them
Write each note in plain language, as if briefing a capable new hire. Put facts first: numbers, names, rules. Keep notes short; a page is plenty. Link related notes with double brackets, for example [[Elm Street]] inside the owner note and [[Jordan Smith]] inside the property note. Add a line at the top of each note saying when it was last checked, because stale notes are the main way this system goes wrong. Do not paste in bank details, passwords, tenant Social Security numbers or anything you would not send to an outside vendor.
Step 4: Write CLAUDE.md at the root of the vault
Create a file called CLAUDE.md in the top folder. Give it four short sections. Who we are: two or three sentences on what the business does and for whom. Your role: "You are the operations assistant. You draft; a human reviews and sends." Map: one line per folder saying what lives there. Rules: "Always name the note you used for any fact. If a number is not in a note, say it is missing; never estimate it. Write in the style described in company/style.md. Never edit notes in owners/ without asking." Add @company/style.md and @company/team.md so those two load every time. Keep the whole file under 200 lines.
Step 5: Install Claude Code and start it inside the vault
Claude Code comes with a paid Claude plan. Install it, open a terminal, move into the vault folder and start Claude Code there, so it picks up your CLAUDE.md. If you would rather avoid the terminal, Claude Cowork in the Claude desktop app can work on a local folder you choose, and it is available on paid plans. Before you load anything client-related, open Claude's privacy settings and decide whether to allow your chats to be used for model training. That choice applies to Claude Code on consumer plans too.
Step 6: Test it on five real tasks and fix the notes, not the prompt
Run five jobs you did last week: an update, a quote, a vendor request, an internal summary and one question about a past decision. For each, check every fact against the source. When Claude gets something wrong, the fix is usually a missing or vague note, not a cleverer prompt. Add the missing fact to the right note and run it again. Stop when it gets four out of five right with only light edits.
Step 7: Give the vault a weekly 15-minute update
Block 15 minutes every Friday. Ask Claude Code: "List notes in clients and properties whose last-checked date is older than 60 days," then update those. When a decision is made, ask Claude to add it to decisions with the date and reason, and review the change before accepting it. A vault that nobody updates will confidently give you last quarter's prices.
What this costs
Obsidian is free, including for work use, as of November 2026. A commercial license is optional at 50 dollars per user per year. Obsidian Sync, which keeps the vault in step across computers and phones, costs 4 dollars per user per month billed annually or 5 dollars monthly. You can skip Sync and use a folder you already back up.
Claude Pro costs 20 dollars a month, or 17 dollars a month billed annually, as of November 2026, and includes Claude Code and Cowork. Heavier daily use may push you to a Max plan, which costs more. Team and Enterprise plans cost more per seat but are not used for model training by default, which matters if staff will load client information.
The real cost is time: about a day to write the first set of notes, and 15 minutes a week to keep them true.
What it gets wrong, and when not to bother
The most repeated claim about this setup is that your data never leaves your machine. That is only half true. The vault files are stored on your computer, but Claude Code sends your prompts and whatever files it reads to Anthropic to generate a response. On consumer plans, Anthropic keeps that data for 30 days if you have turned off training and up to five years if you allow it. So the vault is local storage, not a private AI. Anything regulated, such as patient records or client tax files, belongs on a business plan with the right agreements or outside the vault entirely.
Second, a knowledge base is only as current as its last edit. If the facts that matter change daily, like balances, schedules or open tickets, they belong in your actual systems, and Claude should read them from there through a connector, not from a note someone forgot to update.
Third, sharing is harder than it looks. A vault on one person's laptop is one person's brain. If five people need it, you need Sync or a shared folder and a rule about who edits what.
And if you only use AI a few times a week for one-off writing, this is overkill. A single saved instruction or a Claude Project with three key files will get you most of the benefit in 20 minutes.
Frequently Asked Questions
Does Claude Code work with Obsidian?▾
Yes. An Obsidian vault is a folder of Markdown files, and Claude Code reads and edits files in whatever folder you start it in. No plugin is required. Put a CLAUDE.md file in the vault's top folder so Claude loads your instructions at the start of every session.
Do I need an Obsidian plugin or MCP server to connect Claude?▾
Not for basic use. Starting Claude Code inside the vault folder is enough for it to read and write notes. Plugins and MCP servers can add search or let other Claude apps reach the vault, but they are optional and add setup and maintenance.
Is my data private if I use Claude Code with an Obsidian vault?▾
The files stay stored on your computer, but anything Claude reads to answer you is sent to Anthropic for processing. On consumer plans you choose whether chats can be used for training, and retention is 30 days with training off. Team and Enterprise plans are not used for training by default.
What should go in CLAUDE.md for a business?▾
A short description of the business, Claude's role, a one-line map of each folder and a few hard rules, such as citing the source note and never estimating missing numbers. Anthropic recommends keeping it under about 200 lines and pulling in other files with at-sign imports instead of pasting everything in.
How much does a Claude Code and Obsidian setup cost?▾
Obsidian is free, with optional Sync at 4 to 5 dollars per user per month. Claude Pro is 20 dollars a month, or 17 dollars on annual billing, as of November 2026. Expect about a day of setup time and 15 minutes a week of upkeep.
Is this better than Claude Projects?▾
It suits operators with a lot of interlinked context who want plain files they own and can edit anywhere. Projects are faster to set up and fine for a handful of reference documents. If you are not sure, start with a Project and move to a vault when you outgrow it.