Most PKM setups fail the same way: tools overlap, filing decisions happen mid-thought, and maintenance debt compounds until the system collapses. The fix is boundaries, not cleverness.
- —Three tools, three distinct jobs: Wispr Flow (capture only), Obsidian (thinking and writing), Notion (anything that needs a status, date, or relation).
- —The filing rule that eliminates mid-thought decisions: does this need a status field? Yes goes to Notion. No goes to Obsidian.
- —Notion links out to Obsidian; Obsidian never links back to Notion. Directional data flow prevents the synchronisation overhead that collapses most PKM systems.
- —Wispr Flow’s single function is capture as an input method. It has no permanent home for content, only a path into Obsidian or Notion.
Test: does this need a status field? Yes → Notion. No → Obsidian.
Wispr is not a storage layer. It's a dictation engine — you speak, text appears wherever your cursor is. The setup is minimal and the benefits compound fast once you're in the habit.
- Hotkeyfn (desktop default) — keep it frictionless.
- Privacy ModeEnable before dictating anything client-confidential. Audio and active-window screenshots are transmitted to Wispr's servers by default.
- Custom dictionarySeed immediately with domain vocabulary: Marketo, BrightEdge, AEM, GA4, GSC, OKLCH, Saltiga, Innovation Atlas, fishtripper, Prado.
- Command Mode (Pro)Select text → "make this more formal" / "turn this into bullet points."
- NotetakerMac only, free plan, launched Aug 2026. System-audio meeting capture — no bot joins the call. Windows and mobile not yet available.
Primary use case: dictating long Claude prompts and dumping raw ideas directly into the Obsidian inbox note.
Obsidian is the thinking layer. Every note lives in a local markdown file — no proprietary format, no lock-in. The vault structure below is opinionated but simple: four numbered folders plus a templates directory. The inbox folder does the heaviest lifting.
00-inbox/ ← everything lands here first, unprocessed 10-projects/ ← one folder per active project 20-areas/ ← ongoing: career, properties, fishing 30-library/ ← research + RAG source docs 40-archive/ _templates/
Every note uses the same frontmatter structure — this makes the Bases views work and keeps retrieval consistent:
--- type: # idea | project | research | log project: # e.g. innovation-atlas, lambda, strata-tool status: # unprocessed | active | on-hold | done created: # YYYY-MM-DD tags: [] ---
Bases Views
Three views are all you need. Install Bases and configure these — they make the daily processing loop fast.
status == 'unprocessed'All notes where status = 'unprocessed', ordered by creation date. This is where you start every morning.
type == 'project' AND status == 'active'All project-type notes currently active. Your working dashboard.
status == 'unprocessed' AND created < today() - 30dUnprocessed notes older than 30 days. Review candidates — delete, file, or promote to Notion.
Templater, QuickAdd, Obsidian Git, Excalidraw. Resist adding more until these earn their keep. The marginal plugin is where vaults go to rot.
RAG note: keep one markdown file per topic in 30-library/, headings as retrieval anchors, no exotic formatting — this is already the ideal shape for feeding into Claude.
Notion handles everything with a status or a date. If a project exists as an Obsidian folder, it also exists as a row in the Projects database — but working content lives in Obsidian, never duplicated in Notion.
Database Schema
Projects
Tasks
Ideas
Content
The system only works if the loop runs. Three cadences, each with a distinct scope:
Wispr → Obsidian inbox or Notion Ideas. No filing decisions in the moment. Volume over curation.
Empty the Obsidian inbox — delete, file into a project folder, or promote to a Notion row. Nothing stays unprocessed overnight.
Notion Projects board — set next action per project. Obsidian Stale view — archive or act.
No two-way sync
Notion links out to Obsidian via URL. Never automate the reverse — keeping Notion as read-only of the vault avoids the infinite loop of conflicting updates.
No project duplication
The row lives in Notion. The folder lives in Obsidian. Working content is in one place only. The moment you copy content across both, you've created a maintenance burden that never resolves.
Build in order
Wispr + Obsidian inbox (week 1) → Notion spine (week 2) → Bases views (week 3) → agents last, once there's real data to run them against. Skipping ahead means building on air.
This stack isn't clever. It's boring in the right way — each tool does one thing, the boundaries are explicit, and the maintenance loop is short enough to actually run. The goal isn't a perfect system, it's one that doesn't require willpower to maintain.
Tiago Forte · Atria Books
The PARA method (Projects, Areas, Resources, Archive) for organising digital notes — the framework most compatible with Obsidian's folder and tag structure.
Sönke Ahrens · Independently Published
An explanation of Niklas Luhmann's Zettelkasten method — the practice behind Obsidian's linked-thinking design and the origin of the evergreen note concept.
David Allen · Penguin Books
The capture-clarify-organise-reflect-engage workflow that complements any PKM system — particularly relevant to the inbox and action-item layer of a multi-tool stack.