How Barrett Linburg Gave Claude Full Context on a 50-Property Real Estate Operation Before Typing a Word
Barrett Linburg built an Obsidian knowledge base connected to Claude Code so Claude knows his entire three-company, 50-plus-property operation at the start of every session — no re-explaining, no setup, straight to work.
The Strategy
Barrett Linburg, co-founder of Savoy Equity, runs three operating companies and manages 50-plus multifamily properties across Texas. Every time he opened Claude, he was doing the same thing: re-explaining the business. How it makes money. Who owns what. Key metrics. Pricing. Team structure. He was onboarding the same employee every morning and then wondering why AI felt slow. The fix was not a new AI tool. It was a filing system. Barrett built a structured knowledge base in Obsidian — free software that stores markdown files locally on your computer — and connected it directly to Claude Code. Now every session starts with the full operation already loaded. Claude knows the team, the numbers, the processes, and the relationships between them before Barrett types a single word. The architecture has three components. Obsidian holds the knowledge base as a collection of short, focused markdown files — one topic per file. Claude Code connects directly to the vault on his local hard drive, reading files without uploads, without cloud storage, and without file size limits. A single master instruction file tells Claude how the company works, what role it plays in the operation, and how to navigate the knowledge base. The result is a briefed-in chief of staff that never forgets. For real estate operators who handle sensitive client data, financial records, and deal structures, the local-only approach solves a problem that Claude Projects cannot. Projects put your files on Anthropic servers and cap how much context you can load. The Obsidian setup removes both constraints. Your data never leaves your machine and your context has no ceiling.
How It Works
Audit what you re-explain to AI most often. Walk through a typical week and note every time you find yourself giving Claude background it should already have. How the business makes money. Your org chart and who owns what. Pricing structures. Key metrics per team member. Your sales process. Brand voice and communication standards. Each of these becomes its own file.
Create one markdown file per topic. Keep each file short and tightly focused — one subject per file, no sprawling documents. Markdown is plain text with simple formatting that AI reads cleanly and consistently. Name files clearly so Claude can navigate them without ambiguity.
Install Obsidian (free). Move all your markdown files into a single Obsidian vault. Obsidian stores everything locally on your hard drive. Nothing goes to the cloud. For operators with sensitive financial data, client records, or proprietary deal structures, this is the critical differentiator from cloud-based tools.
Build your wikilink structure. Connect every related file using wikilinks — tagged internal links that Obsidian recognizes. When Claude looks up a specific property, the wikilinks pull every connected lease, contractor note, financial summary, and team assignment automatically. One question surfaces the full picture rather than a single isolated file.
Connect Claude Code to your Obsidian vault. Claude Code is the desktop version of Claude with direct file system access. Point it at your vault folder and it reads files directly off your computer — no uploading, no file size limits, no data leaving your machine. This is what makes the system work at scale: 50 properties worth of documentation loads instantly.
Write one master instruction file. This is the most important piece of the system. It tells Claude who you are, how your company operates, what role Claude plays, and how to navigate the knowledge base. Barrett frames it as the onboarding document you would hand a senior executive on their first day — except this executive never forgets it and never needs to be re-briefed. Include your decision-making framework, communication standards, and any standing context that applies to every session.
Open Claude Code. Every session now starts with full operational context already loaded. Skip the setup. Skip the re-explaining. Go straight to the work.
Results
Barrett runs three operating companies and 50-plus multifamily properties with full Claude context loaded at session start — no onboarding time, no repeated explanations. The post reached 76.3K views and generated significant discussion among real estate operators and agency owners building similar systems. Multiple replies reported immediately implementing the same Obsidian-Claude Code setup for their own operations. Barrett noted the next phase involves building specialized agents on top of the knowledge base — a Legal Devil's Advocate and a Deal Analyst — using the same local vault as their shared context layer.
Our Take
Most AI productivity advice misses the real bottleneck. It is not the quality of your prompts. It is the fact that you are re-explaining your business from scratch every single session. Barrett's system attacks that problem directly and the solution is almost embarrassingly simple: organized markdown files, a free local app, and a direct connection to Claude Code. The wikilink architecture is the detail that separates this from just dumping files into a folder. When every file connects to related files, Claude does not retrieve isolated documents — it navigates a knowledge graph. Ask about a specific property and you get the full context: team assignments, open issues, financial notes, contractor history. The quality of the answer scales with the quality of the connections you build into the system. The local-only approach is a genuine differentiator for real estate operators. Multifamily ownership involves sensitive financial data, client and investor relationships, and proprietary deal structures that many operators will not put on a third-party server. Claude Projects requires uploading files to Anthropic infrastructure and caps context at a fraction of what a real operation needs. The Obsidian setup removes both constraints entirely. The master instruction file framing — treat it as an executive onboarding doc — is the most transferable insight in the thread. Every business owner knows what they would put in that document. Most have never thought to build it as a persistent AI context layer. Best suited for operators running multiple entities or locations who want Claude to function as a briefed-in chief of staff rather than a blank-slate chatbot. Also highly relevant for agencies managing multiple clients who want to maintain separate but interconnected knowledge bases for each account.
Related Strategies
More AI agent strategies you might find useful
How Lauren Lucas Grew Her Real Estate Business to $400K GCI Using AI Automation
Lauren Lucas grew to $400K GCI by building AI systems that run her real estate b…
AI Voice Receptionist for Real Estate Agents: Full Build
Folu built a real estate AI voice receptionist using Vapi, OpenAI, Google Calend…
AI Voice Receptionist for Real Estate Agents: Lead Qualification Architecture
Jack Rossi built a real estate AI receptionist inside GoHighLevel with separate …
Want more strategies like this?
Get weekly AI agent case studies in your inbox.