Ten weeks ago I wrote up my first five patterns with Obsidian, mostly guessing at which habits would hold once the novelty wore off. I now open the vault before I open Slack most mornings, and the honest scorecard on that early guess is mixed: two of those patterns quietly died inside the first month, one turned out bigger than I expected, and a fourth I never even mentioned back then is now the actual backbone of my Obsidian daily workflow. This is the update where I say which parts of that first report were right, which were hopeful, and what a real daily habit with a client knowledge base looks like once the shine is gone.
In this article
- Why the habit that survived wasn’t the one I expected
- What my Obsidian daily workflow actually runs on now
- Where Smart Connections earned its keep, and where I stopped trusting it
- The client knowledge base routine that replaced search-and-scroll
- What the first field report got wrong about effort
- Where the Obsidian daily workflow still breaks down
- FAQ
Two Months In, the Habit That Survived Wasn’t the One I Expected
The habit that stuck wasn’t the AI plugin’s auto-suggestions — it was a two-minute end-of-day note I almost cut from the original piece as filler. Every evening, before I close the laptop, I add three lines to a running daily note: what a client asked for, what I promised back, and what surprised me. That note takes less time to write than it takes to describe, and it is the only thing from May that I have done every single working day since.
The pattern I flagged as already dropped after a week in that first piece never came back, and I’m not sorry. It was a tagging scheme built for a vault that didn’t have enough notes yet to justify the overhead. What replaced it wasn’t a smarter tagging scheme; it was fewer notes, checked more often. That is the part the early report undersold — an Obsidian daily workflow rewards frequency over structure, at least for one person managing a handful of active accounts.
My Obsidian Daily Workflow Now Runs on Three Notes, Not Fifty
An Obsidian daily workflow that works for one operator doesn’t need fifty open notes — it needs three that never close. After two months of trimming, the vault I actually touch every day has shrunk to:
- A running daily log, where the three end-of-day lines land in date order.
- One index note per active client, linking every call, brief, and decision back to a single page.
- A standing “owed answers” note, for client questions I couldn’t fully address in the moment.
The rest of the vault — old research dumps, half-finished frameworks, a branding agency director’s entire onboarding packet from March — still exists, and Smart Connections still surfaces pieces of it when I’m writing. But my actual Obsidian daily workflow lives in those three notes. Everything else is reference material I visit, not a habit I maintain.
Smart Connections Earned Its Keep Only After I Stopped Trusting It
Smart Connections is still installed two months later, but only because I learned to treat its first suggestion as a starting question, not an answer. The plugin’s core function hasn’t changed since May: it uses a local embedding model to surface related notes as I write, through a connections view, a lookup mode for when I start from a question instead of an open note, and a graph view that groups notes by meaning even when I never linked them myself. None of that requires an API key for the core feature set, which matters to me given how much client detail sits in that vault.
What changed is my trust in its first pick. Early on I copied whatever note it surfaced into a brief without rereading the source. Twice that meant repeating an outdated client preference that had already been overturned in a later call. Now I use it the way I’d use a colleague’s hunch — worth checking, not worth quoting directly. That shift in trust is most of what actually changed in my Obsidian daily workflow over the past two months.
The plugin never actually saved me research time; it just moved my doubt earlier in the process, which is the only reason I still open it every morning.
That’s the honest version of “AI plugin integration” two months in. It’s a nudge toward the right note, not a substitute for reading it.
The Client Knowledge Base Routine That Replaced Search-and-Scroll
The real change since May is that I stopped scrolling old Slack threads to answer a client’s own question back to them. Before the daily note habit, if a startup operator asked “didn’t we already decide on the launch date?”, I’d spend ten minutes hunting through three different apps. Now I check the client’s index note first, because the answer is usually a single click away from whatever I logged that same week.
The routine looks like this on a typical day:
- Open the client’s index note before any call, not after.
- Log the outcome in the daily note within the hour, not at end of day if the call was substantial.
- Let Smart Connections’ lookup mode catch anything related I might have forgotten to link manually.
None of that is exotic. It’s closer to filing than to anything AI-driven, and that’s exactly the point — the habit that held is boring, not clever. That’s also the clearest sign that an Obsidian daily workflow can survive a busy week instead of collapsing back into old habits.
What the First Field Report Got Wrong About Effort
The May piece undersold how much manual linking the early weeks demanded before Smart Connections had enough notes to work with well. A local embedding model needs a body of writing to compare against, and a two-week-old vault doesn’t have much of one. I remember treating that setup period as a footnote in the original report; in hindsight it deserved its own section, because it’s the reason the five patterns I wrote up when the vault was brand new read a little more optimistic than the first month actually felt.
It’s a similar gap to what I found running the same stuck-versus-dropped test on Notion AI after eight months — the habits that look most impressive in week one are rarely the ones still running two months out. What’s different this time is that the tool itself didn’t change; my Obsidian daily workflow around it did.
Where the Obsidian Daily Workflow Still Breaks Down
An Obsidian daily workflow still breaks down the moment a client wants something that isn’t plain text — a slide deck, a spreadsheet, anything visual belongs in a different tool entirely. I still draft those pieces elsewhere and only link back to them from the client index note, which means the vault stays a table of contents for that kind of work rather than the workspace itself.
The other open question is Obsidian Sync. The core app is free without limits, but multi-device sync runs $4 a month billed annually or $5 monthly on Obsidian’s own pricing page. I’m still working from one machine, so I haven’t paid for it, and until a client project forces me onto a second device I don’t have a real answer for whether it’s worth the subscription. That’s a smaller decision than the AI plugin question, but it’s the one still sitting unresolved after two months — not unlike how I still split retainer context differently across Claude Projects for the drafting side of the same client work.
For anyone building the same setup, the plugin’s official site and Obsidian’s own download page are the only two places I’d start from — not a roundup post promising a perfect stack on day one.
FAQ
Is Smart Connections still worth installing for a solo knowledge base?
Yes, for the connections and lookup views alone. The core feature set runs on a local embedding model with no API key required, which fits a client vault where I’d rather not route sensitive notes through an external service just to find related pages.
Did switching to a daily habit replace Notion entirely?
No, and I never expected it to. Notion AI still handles meeting-note triage and action items for me; my Obsidian daily workflow covers the slower, cumulative side — the running record a client conversation builds over months, not the same-day summary.
Is Obsidian Sync worth paying for at this stage?
Not yet, at least not for a one-machine setup. At $4 a month billed annually it isn’t expensive, but I can’t justify paying for cross-device sync I’m not using, and I’d rather wait until a second device actually forces the question.
Does an Obsidian daily workflow work without any AI plugins at all?
It depends on how much of the vault is old enough to search manually without help. In the first two or three weeks, before there’s enough written material for a local embedding model to compare against, a plain folder structure does almost the same job. The plugin earns its place later, once there’s a real body of notes worth connecting.
For me, the two-month mark is where an Obsidian daily workflow stopped being an experiment and started being closer to filing paperwork — unglamorous, occasionally annoying, and the reason I stopped losing client details between calls. The plugin gets credit for surfacing what I’d forgotten, but the three-note habit is doing the actual work. I’d rather report a routine that’s a little boring and still running in ten weeks than one that looked impressive in the first draft and quietly disappeared. That’s the trade I’d make again.
Sources
AI-assisted research and drafting. Reviewed and published by ToolMint.