Obsidian

Here’s a pattern I see constantly — in my own work, with our clients, across every team I’ve worked with. You have a conversation. An important decision gets made. A technical detail comes up that matters. And then it vanishes. Into a Slack thread nobody will find again. Into a meeting that wasn’t recorded. Into a Google Doc nested three folders deep that you’ll never open again.

Six months later, someone asks “why did we decide to use Redis instead of Memcached?” and nobody can remember. The reasoning existed. Nobody captured it in a place they’d find it again.

Obsidian solves this. Not with another cloud service that owns your data, not with another SaaS that charges per seat. Obsidian stores everything as plain text Markdown files on your own machine. If Obsidian disappears tomorrow, your notes are still there: readable, searchable, portable, yours.

What Obsidian is

Three principles set it apart:

Local-first. Your notes live on your device as plain .md files in a regular folder. No cloud required. No internet required. No account required. Open the folder in any text editor and your notes are right there.

Linked thinking. Every note can link to every other note using double brackets. These links create a web of connected ideas — a knowledge graph that surfaces relationships you wouldn’t spot in a flat folder structure. Check the backlinks panel and you see every other note that links to the one you’re reading.

Extensible. 2,700+ community plugins add everything from Kanban boards to AI-powered semantic search. The core app is deliberately minimal. You build exactly the system you need.

Why not Notion?

I get this question a lot. Use Notion if you need real-time collaboration with your team, shared databases, and an all-in-one workspace. Notion is excellent at structured team workflows. Use Obsidian if you want privacy, offline access, data ownership, blazing speed, and maximum flexibility for individual knowledge work.

For me, the choice was clear: my notes contain client details, strategic decisions, contract analysis, salary information, hiring notes, and raw unfiltered observations I wouldn’t want on anyone else’s servers. I learned this the hard way when a team member accidentally shared a Notion page containing our internal pricing model with an external collaborator. Nothing catastrophic happened, but the fifteen minutes of panic were educational. Local-first means that particular category of mistake can’t happen.

Many people use both. Notion for shared workspace, Obsidian for personal knowledge management. Perfectly reasonable.

Getting started

Download the app (macOS, Windows, Linux, iOS, Android). It’s free — no account needed, no trial period. A vault is just a folder on your computer where your notes live. Create one and you’re in.

When you want to link to another note, type double brackets and start typing the name. Obsidian autocompletes. If the note doesn’t exist yet, the link creates it when you click it. This is the core mechanic: create notes freely, link them generously, and the structure emerges from the connections.

Core features

Backlinks are the magic. Open any note, check the right sidebar, and you see every other note that links to it. Without manual filing, tagging, or organizing, you’ve created a web of connections that surfaces relationships automatically. Over time, a note about a client links to notes about their project, their contract, their team, and decisions you’ve made. Click through any node and you can trace the reasoning chain.

Graph view visualizes your entire vault as a network of connected nodes. Honest take: it looks impressive but it’s more useful for orientation than daily work. In a small vault, too sparse to be interesting. In a large vault, too dense to be readable. I show it to people when I want to look smart. I use search when I want to find something.

Daily notes are your inbox. One keyboard shortcut creates a note titled with today’s date. Everything that happens during the day goes in: client calls, ideas, decisions, tasks. At the end of the day, move anything important into permanent notes with proper links. Low-friction, time-stamped, a place to put anything without thinking about where it “should” go.

Canvas is an infinite 2D whiteboard for arranging notes visually — project planning, architecture mapping, brainstorming.

Bases adds database-like views to your notes. Notion’s databases but built on local markdown files.

How to structure your vault

The most common mistake: over-organizing from the start. I did exactly this. My first vault had twelve top-level folders, sub-folders three levels deep, and a color-coded tagging taxonomy I designed in a spreadsheet. Beautiful. Used it for about two weeks before the overhead of deciding where to file each note became so annoying that I stopped taking notes altogether.

Start flat. Five folders: Inbox, Projects, Archive, Templates, Daily Notes. When you create a note, put it in Inbox or Projects. Link it to relevant notes. Don’t agonize. Over time, patterns emerge. You notice 15 notes about a specific topic — create a folder. You notice a recurring note type — make a template. Structure grows organically from actual usage, not from imagined future needs.

Three types of notes develop naturally. Fleeting notes — quick captures in the daily note, most get discarded. Project notes — working documents tied to specific work. Permanent notes — distilled knowledge that stays useful over time. Not every note needs polish. Most are captures. Some become documents. A few become permanent knowledge.

Essential plugins

Templater replaces the basic Templates plugin with dynamic templates that support dates, cursor positioning, and logic. One keyboard shortcut and you have a formatted meeting note in a second.

Dataview turns your vault into a queryable database. Write a simple query and it dynamically pulls notes based on tags, folders, or properties. Incredibly powerful for dashboards and project tracking.

Calendar adds a visual calendar to the sidebar that integrates with Daily Notes. Click any date to open that day’s note.

QuickAdd lets you capture notes with a single keyboard shortcut — presents a menu, prompts for a title, applies a template, files the note. Capture velocity matters.

Kanban turns markdown lists into visual boards. Drag cards between columns. Simple project management without leaving Obsidian.

Obsidian Git auto-commits and pushes your vault to a GitHub repository. Version control and backup for free. This is my primary sync mechanism.

AI integration

This is where Obsidian becomes a different tool in 2026. Your vault is a collection of plain Markdown files on your machine. AI tools can read, search, and write to them.

Smart Connections (800,000+ downloads) builds local embeddings of your notes and surfaces semantically related content. Open a note about a client problem and it shows conceptually related notes — even without shared tags or links. The chat feature lets you ask questions about your vault using RAG. It works with local models (completely private) or cloud APIs.

Claude Code + Obsidian via MCP is the power combination. Connect Claude Code to your vault through MCP, and Claude can read, search, create, and modify notes directly. Last month I was planning a database migration for a real estate platform client. I had notes from six months of conversations: architecture decisions, performance benchmarks, schema problems, client pain points across three calls. I pointed Claude Code at my vault and asked it to read my notes and draft a migration plan addressing everything the client had raised.

Claude read nine notes, cross-referenced complaints with our technical observations, and produced a plan starting with the two tables the client complained about most. Without the vault connection, I’d have spent thirty minutes re-reading my own notes before even starting. The vault becomes the memory that Claude doesn’t have natively.

Prompt library is a practical pattern I use constantly. A folder of your best prompts stored as individual notes, tagged and categorized. Client communication, code review, analysis, content. Over time you build a personal library that compounds in value.

Syncing and pricing

The core app is free. Forever. No limits, no feature restrictions. Every plugin and feature in this chapter works on the free plan. As of February 2026, Obsidian is also free for commercial use.

For syncing across devices, free options include iCloud Drive, Google Drive, or the Obsidian Git plugin (what I use — backup and version history as a bonus). Obsidian Sync ($4-5/month) is the zero-friction paid option with end-to-end encryption.

Obsidian Publish ($8-10/month) turns your vault into a website if you want that. For this book’s purposes, we use other deployment tools.

The pitfall: customization addiction

I need to say this directly because it’s the most common failure mode. You will be tempted to spend more time configuring your system than actually using it. The plugin catalog is vast. The YouTube rabbit hole of “ultimate Obsidian workflow” videos is bottomless.

Resist this. Start with the core app and Daily Notes. Write for a week before installing any plugins. Add plugins one at a time, only when you feel a specific friction.

The best Obsidian system is the one you use every day. A messy vault with 500 real notes beats a beautiful vault with 10 demo notes and 47 plugins. I know this because I’ve been the person with the beautiful vault and the 47 plugins. The notes I took during that phase? I can count them on one hand.

The bottom line

Obsidian is not just a note-taking app. It’s the foundation of a personal knowledge system that compounds over time. The local-first approach means your data is yours forever. The Markdown format means it’s readable by every AI tool in existence. The plugin ecosystem means you shape it to match exactly how you think.

Start simple. Create a vault. Enable Daily Notes. Write something every day. Within a month, you’ll have a knowledge base no cloud service can take away. Within a year, you’ll wonder how you worked without it.

---

This is the free web edition of Chapter 3. The full text — with vault setup walkthroughs, Markdown formatting guides, plugin configuration details, template examples, and Claude Code integration scripts — is available in 42: The AI Builder’s Stack, coming Q3 2026 on Amazon in hardcover, paperback, and digital.