Obsidian for Consultants: Organizing Your Brain Without Losing Your Mind

By James Aspinwall

You have forty clients, six active projects, three proposals in flight, and a head full of ideas that connect to each other in ways no folder structure can capture. Sticky notes don’t scale. Notion is slow. Evernote forgot what it was for. Google Docs is where documents go to get lost.

Obsidian is different. It’s a note-taking app that works the way your brain already does — through connections, not hierarchies.

What Obsidian Actually Is

Obsidian is a markdown editor that runs on your local machine. Your notes are plain .md files in a folder on your computer. No cloud dependency, no proprietary format, no subscription required for personal use.

Open a folder, start writing. That folder is your “vault.” Everything lives there — notes, images, attachments. You can sync it with iCloud, Dropbox, Git, or Obsidian’s own Sync service. If Obsidian disappears tomorrow, your notes are still markdown files you can open in any text editor.

The two features that set it apart: links and graph view.

Links

In any note, type [[ and start typing. Obsidian autocompletes to any other note in your vault. Click the link, you’re there. This creates a bidirectional connection — the linked note knows who’s linking to it.

Met with Sarah at Acme Corp today. She mentioned they're expanding
into the EU market — see [[Acme Corp]] for full client profile.

Discussed the same compliance framework from [[GDPR Readiness Checklist]].
Might be relevant for [[Bright Industries]] too.

Three links, three connections. Now when you open the Acme Corp note, you see every note that references it. When you open the GDPR checklist, you see every client it applies to. The knowledge network builds itself as you write.

Graph View

Hit Ctrl+G and Obsidian shows you a visual map of your entire vault — notes as dots, links as lines. Clusters form naturally around topics. Orphan notes (unlinked) float at the edges, reminding you to connect them or delete them.

For a consultant, this is your second brain made visible. You can see which clients share problems, which frameworks apply to multiple engagements, and which ideas are isolated vs well-connected.

The Consultant’s Vault Structure

Obsidian doesn’t force a structure. That’s its strength and its danger. Here’s what works after years of refinement.

Top-Level Folders

vault/
  Clients/          — one note per client, one subfolder per engagement
  Projects/         — active project briefs and status
  Meetings/         — chronological meeting notes
  Frameworks/       — reusable methodologies, checklists, templates
  Ideas/            — raw captures, half-formed thoughts
  Daily/            — daily journal (one note per day)
  Templates/        — note templates for consistency

Six folders. Not twelve. Not twenty. The structure should take five seconds to navigate. If you need a subfolder, create it. If you’re creating more than two levels deep, you’re overcomplicating it.

Client Notes

Each client gets a single root note at Clients/{CompanyName}.md. This is the source of truth for the relationship.

# Acme Corp

**Industry:** Manufacturing
**Main Contact:** Sarah Chen (CTO)
**Status:** Active client since 2024

## Context
Mid-size manufacturer moving to cloud infrastructure. Conservative
culture, slow decision-making, but once committed they execute well.

## Engagements
- [[Acme Corp — Cloud Migration]] (2024 Q3, completed)
- [[Acme Corp — EU Compliance]] (2025 Q1, active)

## Key Decisions
- Chose AWS over Azure due to existing team experience
- Board requires quarterly security audits

## Notes
- Sarah prefers email over Slack
- Budget approval requires VP sign-off above $50K
- Their fiscal year ends in March

This note is a living document. You update it after every interaction. When a new consultant joins the account, they read this note and have full context in three minutes.

Meeting Notes

One note per meeting. Always. The filename pattern: YYYY-MM-DD - {Client or Topic}.md.

# 2026-02-14 — Acme Corp Weekly

**Attendees:** Sarah Chen, James, Mike (DevOps)
**Location:** Zoom

## Discussion
- Migration Phase 2 is 70% complete
- Mike raised concern about database latency in EU region
- Sarah wants a cost projection for multi-region deployment

## Action Items
- [ ] Send multi-region cost estimate by Friday → James
- [ ] Test EU latency with production-like data → Mike
- [ ] Schedule board presentation for March → Sarah

## Links
- Related: [[Acme Corp — EU Compliance]], [[AWS Multi-Region Patterns]]

The links at the bottom are the magic. This meeting note is now connected to the project, the client, and a reusable framework note. Six months later, when you search for “multi-region,” this meeting surfaces alongside every other time the topic came up.

Daily Notes

Obsidian has a built-in Daily Notes plugin. One note per day, auto-created with today’s date. Use it as a running log — not polished prose, just captures.

# 2026-02-17

- Morning call with [[Bright Industries]] — they want to accelerate timeline
- Idea: [[Compliance Automation Framework]] could be productized
- Read article on EU AI Act — relevant for [[Acme Corp — EU Compliance]]
- TODO: review [[Proposal — DataFlow Inc]] before sending tomorrow

At the end of the week, scan your daily notes. Anything important gets linked to the right client or project note. The daily note is the inbox; client and project notes are the organized archive.

Grouping by Interest with Tags and MOCs

Folders group notes physically. Links group them conceptually. But sometimes you need a third axis: interest areas that cut across clients and projects.

Maps of Content (MOCs)

A MOC is a note that links to all other notes about a topic. It’s a manually curated table of contents for an interest area.

# Cloud Migration — Map of Content

Everything I know about cloud migrations, organized by phase.

## Assessment
- [[Cloud Readiness Assessment Template]]
- [[TCO Calculator Approach]]
- [[Common Migration Blockers]]

## Planning
- [[Migration Wave Strategy]]
- [[AWS Multi-Region Patterns]]
- [[Database Migration Playbook]]

## Client Engagements
- [[Acme Corp — Cloud Migration]] — completed, AWS, 6 months
- [[Bright Industries — Infrastructure]] — in progress, hybrid approach
- [[DataFlow Inc — Proposal]] — proposed, data-heavy workload

## Lessons Learned
- [[2025-06-15 — Acme Retro]] — underestimated data transfer time
- [[2025-11-20 — Bright Standup]] — hybrid approach saved 40% cost

This note is a living index. Every time you learn something new about cloud migrations — from a client engagement, an article, a conference talk — you add a link here. Over time, it becomes your personal reference guide for the topic.

MOCs are how consultants turn experience into reusable intellectual capital. The knowledge doesn’t stay locked in one client’s folder — it’s connected across your entire practice.

Practical Habits That Make It Work

The tool doesn’t matter if the habits aren’t there. Three habits that separate a useful vault from a graveyard of abandoned notes.

1. Capture First, Organize Later

During a meeting or conversation, write in your daily note or the meeting note. Don’t stop to figure out where it belongs. Don’t create folders. Don’t add tags. Just write.

After the meeting, spend two minutes adding links ([[Client Name]], [[Project]]) and a few tags. That’s enough. The search and graph will do the rest.

2. Weekly Review (15 minutes)

Every Friday, scan the week’s daily notes and meeting notes. Ask:

Any unlinked notes that should be connected?
Any action items that need to move to a project or task tracker?
Any ideas worth expanding into a framework note?
Any client notes that need updating?

This is the habit that turns a pile of notes into a knowledge base.

3. Refine, Don’t Reorganize

Resist the urge to restructure your vault every month. Instead, refine individual notes. Add a sentence of context. Add a link you missed. Update a status. Small, continuous improvement beats periodic overhauls.

If a note is getting long, split it. If two notes overlap, merge them. If a tag is never searched, drop it. The vault evolves; it doesn’t get redesigned.

Plugins Worth Installing

Obsidian’s community plugin ecosystem is large. Most plugins are unnecessary. These are the ones that earn their place.

Plugin	What It Does	Why It Matters
Templater	Auto-fill templates with dates, titles, prompts	Consistent meeting notes and client notes every time
Dataview	Query your notes like a database	“Show me all notes tagged #proposal created this month”
Calendar	Visual calendar linked to daily notes	Click a date, see that day’s note
Local REST API	Expose your vault as an API	Integrate with other tools and automation

Templater is the highest-value plugin. Create a meeting template, a client template, and a project template. When you create a new note, pick the template and the structure is already there. You just fill in the blanks.

Why This Works for Consultants Specifically

Consultants deal with a unique problem: wide but shallow context across many clients, with deep expertise in specific domains. You need to remember that Acme Corp’s CTO prefers email, that Bright Industries has a March deadline, and that the compliance framework you built for one client might solve another client’s problem.

No single folder structure handles this. Folders force a primary axis — by client, by topic, by date — and everything else becomes hard to find.

Obsidian’s linking model gives you every axis at once. A meeting note lives in the Meetings folder, links to a client, references a framework, and carries tags for the domain. Search by any dimension and you find it.

The graph view makes cross-client patterns visible. When you see three client notes all linking to the same framework note, that’s a signal — maybe it’s time to productize that framework. When you see a cluster of meeting notes around a topic, that’s where your expertise is deepest.

The vault becomes an asset. Not just a record of what happened, but a map of what you know and who you know it about. That’s the difference between a consultant who starts from scratch every engagement and one who compounds knowledge across their entire career.

Start with a folder, a daily note, and two links. The rest will grow from there.