16:42Eric Michaud · Demo
Grok Just Got a Phone (Voice Agent Builder)
An AI agency owner live-builds two Grok voice agents from scratch and puts real appointment bookings through them, no script, no edits.
July 7thThe argument in one line.
Obsidian becomes a productive operating system only when you collapse capture, execution, and intelligence into one unified workspace, eliminating the context-switching friction that turns most note-taking apps into information graveyards.
Read if. Skip if.
READ IF YOU ARE…
- A knowledge worker or solopreneur running 2-3 active projects who currently switches between 5+ tools daily and loses context in the gaps.
- Someone with ADHD or attention management challenges who needs single-location task execution, not just note capture, to maintain focus.
- A creator or analyst who already uses Obsidian for notes but hasn't connected it to your actual workflows and wants to collapse tool sprawl into one vault.
SKIP IF…
- You're new to Obsidian or note-taking apps — this assumes comfort with vault setup and focuses on systems design, not onboarding basics.
- Your work heavily involves collaboration or requires tools your team already standardizes on — this is built for solo operating systems, not team infrastructure.
- You're looking for a Second Brain philosophy or deep dive into capture methodology — this explicitly argues against that model and doesn't explore note architecture itself.
The full version, fast.
Obsidian works best when treated as a unified operating system rather than a passive note repository, because capture without execution produces a graveyard of unused information. The method is to collapse capture, dashboards, agents, browser, terminal, and communication tools into a single workspace, then run two anchoring commands each day, a morning agent that pulls calendar, inbox, and carryovers into three priorities, and an evening close-day routine that logs metrics through voice dictation. The payoff comes from eliminating context-switching friction and pairing AI agents with persistent memory, so daily activity feeds an intelligence layer that surfaces trends. Stop assembling isolated workflows and instead build one system where inputs, reporting, and execution compound in the same place.
Free for members
Chat with this breakdown — free.
Sign in and you get 23 free chat messages on us — ask for the hook, quote a framework, find the exact transcript moment, generate a markdown action plan. Bring your own key when you want unlimited.
Create a free account →Where the time goes.
00:00 – 00:43
01 · The Vault as a Workspace
Opens directly on the custom Operations Dashboard. Hook: capture is useless without execution. Promise: reporting, intelligence, execution.
00:43 – 01:48
02 · Daily Focus Dashboard
Shows Today's Focus widget, one-at-a-time task queue, ADHD-friendly single-priority design, shortcuts, quick capture inbox, activity log, calendar.
01:48 – 02:26
03 · Metrics and Insights
Audience + Content Performance view: heat maps, subscriber growth chart, overlapping graphs correlating revenue to daily actions.
02:26 – 03:42
04 · Daily Agent Commands
Daily Template with metric properties, /today py agent (pulls calendar + inbox + carryovers), close day voice dictation. Two slash commands run the entire tracking loop.
03:42 – 04:51
05 · Systems vs. Workflows
Core argument: workflows = individual actions on a shelf; systems = everything working together. Counters the Claude Code + folder structure objection directly.
04:51 – 05:46
06 · Eliminating Friction
Context-switching erodes momentum invisibly. Shows Telegram, Slack, email, YouTube Studio, terminal, localhost all inside Obsidian. Toolbox analogy.
05:46 – 06:56
07 · The Intelligence Layer
Agents input to Obsidian structure; Obsidian fills agent memory gaps. Custom plugin turns daily notes into a mini intelligence app. The compound effect.
06:56 – 07:20
08 · Vault Access / CTA
Free starter vault in description. Full dashboard + intelligence plugin via School community. Subscribe ask.
Lines worth screenshotting.
- Capturing notes you never act on isn't a productivity system — it's a graveyard with good metadata.
- Every context switch — alt-tabbing between a browser, an agent, a dashboard, and a terminal — loses momentum you don't notice you're losing.
- A folder structure an AI agent can read is not an operating system; an operating system is where you actually do the work.
- Correlating which daily actions caused a revenue spike — then doing more of them — is the analytical advantage a unified vault enables.
- Most Obsidian tutorials teach individual workflows; the actual leverage comes from building a system where all those workflows reinforce each other.
- Running two commands — one at the start of the day and one at the end — is the minimum viable routine for a self-improving daily tracking system.
- When your toolbox is disorganized across five apps, you spend cognitive energy navigating your tools instead of using them.
- Obsidian and agents are complementary: agents write structured data into Obsidian, and Obsidian fills the memory gaps agents can't hold.
- The second brain trap is optimizing for input — the only thing that matters is whether what you captured changes what you do.
- A Python agent that pulls calendar events, inbox items, and carryover tasks into a daily note at startup removes the need for a morning planning ritual.
Steal the OS frame.
Joe's playbook
The Second Brain angle is exhausted — the sharper hook is the operating system angle: one environment where you capture, execute, and learn from everything.
- Lead with the anti-workflow argument: 'I don't build workflows, I build systems' is a cleaner differentiator than any feature list.
- The two-command day (/today + close day) is a format you could ship as a JoeFlow morning template — launch, dictate close, everything logged.
- Context-switching as productivity poison is underused as a content hook — measurable, relatable, makes the single-tool pitch feel obvious.
- Show your actual vault live. Real data (heat maps, revenue trends) beats polished slides for trust and shareability.
- The intelligence layer argument (agents fill Obsidian, Obsidian fills agents) is the strongest moat claim — worth its own dedicated video.
- His CTA structure (free vault first, then paid community) is a clean entry-level funnel worth modeling for MCN+.
Terms worth knowing.
- Obsidian
- A local-first note-taking app that stores notes as plain Markdown files and supports heavy customization through plugins, dashboards, and linked references.
- Vault
- The folder of Markdown files and settings that makes up a single Obsidian workspace, holding all notes, templates, and plugin configurations in one place.
- Second Brain
- A popular productivity concept of capturing every idea, link, and reference into a personal knowledge system so it can be retrieved and reused later.
- PKM
- Personal Knowledge Management — the practice and category of tools used to capture, organize, and retrieve personal notes and reference material.
- Daily note
- A dated Markdown file created each day as a single landing page for that day's tasks, logs, metrics, and reflections, typically generated from a template.
- Properties
- Structured metadata fields attached to a Markdown note in Obsidian, used to store values like dates, numbers, or tags that other views and queries can read.
- Heat map
- A grid visualization that colors each cell by intensity, commonly used to show activity or metric values across days of the week or weeks of the year.
- Canvas
- An Obsidian feature that provides an infinite whiteboard where notes, images, and embeds can be arranged spatially and connected with lines.
- AI agent
- A program that uses a language model to take multi-step actions on the user's behalf, such as reading files, calling tools, and writing structured output.
- Python agent
- An AI agent implemented as a Python script that can be triggered from inside the vault to read notes, call external services, and write results back as Markdown.
- Memory layer
- Persistent storage that an AI agent reads from and writes to between runs, giving it long-term context that survives beyond a single conversation.
- Intelligence layer
- A layer on top of stored notes that synthesizes, summarizes, or surfaces insights from the underlying data instead of just displaying the raw information.
- Localhost
- An address that points back to the user's own machine, used to run and preview web apps or dashboards locally without deploying them to the internet.
- Context switching
- The mental cost of moving attention between different apps or tasks, which fragments focus and slows down overall productivity even when each switch feels small.
- Claude Code
- Anthropic's command-line coding agent that can read and edit files inside a folder structure, often discussed as an alternative interface for AI-assisted work.
- Voice dictation
- Speech-to-text input that converts spoken words into written text, used here to talk through end-of-day reflections instead of typing them.
- School community
- A paid membership site hosted on Skool.com where a creator distributes courses, templates, and community discussion to subscribers.
Things they pointed at.
04:06toolClaude Code
04:55toolTelegram
04:55toolSlack
Lines you could clip.
00:27
“Data collection is only as good as what you do with that information.”
04:10
“It's not enough that your agent can just read and navigate a folder structure. That's not an operating system.”
05:20
“Every time you change context or have to switch views or whatever, you're losing momentum. You might not notice, but you absolutely are.”
06:45
“Stop thinking about things as individual workflows and start building out systems where all these different things start working together for you.”
Word for word.
Read-along
Don't just watch it. Burn it in.
See every word as it's spoken — crank it to 2× and still catch all of it. The same dual-channel trick behind Amazon's Kindle + Audible.
metaphoranalogy
This is my Obsidian vault. This is where I keep all of my context, whether it's my daily notes, the metrics I wanna keep track of, content research. It's also where I keep my AI agents and custom workflows, pretty much the whole thing.
But this doesn't just capture notes. This also is where I do all of my work. And that's the part I think a lot of people are missing.
Right? Because capture is one thing, but it's totally useless if you can't do anything with it. And that's exactly what we're gonna talk about in this video.
Data collection is only as good as what you do with that information. Okay? So it's not just about inputs.
We're also gonna talk about reporting, intelligence, and execution. So let's dig into it. So first things first, I don't wanna turn this into a vault tour.
I just wanna show you what you're missing out on. If you're thinking more about the workflow and not systems, how things work together. What I really wanna do is get you focused on how you can customize this platform to work for you.
Right? Like, this is a custom view I built out so I could get a real feel for exactly what I need to see right now. Not just metrics and stuff, which is, you know, awesome, but really what my focus is for the day.
Part of my daily routine is kind of the to do list, right? Making sure that I knock off the most important thing one at a time.
So for me, that's really important. I've got ADHD. Don't know if you can tell.
But knowing exactly what I'm doing, one, two, three, is pivotally important. Right? This is the current focus, front and center.
This is what you're doing right now end to end. Right? I can log the time.
I can knock it off. If I need a little more information, I click context, and I can pull up some stuff from my notes that match this search criteria. Also, shortcuts in terms of tracking.
Right? So I've got a few things that if I do every single day, things tend to fall into place for me. Right?
So I can knock those off by clicking these things on or off, you know, through the day. I can also quick capture some ideas and log it to an inbox, which is fantastic. It makes things really, really easy, and it's just directly in front of me.
Right? If I wanna drill down on any of these bits of information, I've also got the full on metrics view for it. Right?
I can go over here. Check this out. I'm looking negative today because it's still in progress, but, you know, you can see the heat map here for what we've got going on through the week.
Overall, the summary, see what's going on, look at trends. You you get the thing. Right?
Just optics. But, I mean, I can also look at overlapping graphs, and I get real insights as to if my revenue goes up one week, for example, I can really drill down and see what actions I was taking during that time and then just do more of that. I'm not obviously not gonna show you the business views because, know, there's some, uh, private information there, but you get the idea how things all work together.
I'm gonna get more into the mindset stuff in a second, but I'm just gonna finish up how this all comes together. And it's pretty straightforward, actually. I run everything off of two commands that I start my day with and end my day with, and that's how we track different things.
But not only that, every activity I do inside the vault is also logged as well. And that's gonna come in later. Okay?
But what we do, we got this daily template with all of the metrics I wanna track as properties. That's important. Then we've got the three main priorities that are populated based on my daily notes.
Some are carried over from the day before. Got the tasks, my activity log, which is running throughout the day, calendar, my schedules, right, and all the different things I wanna talk about. It's really not hard to wrap your head around how we are tracking this thing.
It's just setting it up and getting into the routine of actually using it. Every day, I run my py agent. I just go slash today.
I'm hoping my face isn't covering this. Then it pulls in my calendar, my inbox, any carryovers from the day before, and we figure out what it is that I need to focus on that day. Same thing at the end of the day, I write close day, and I just use my voice dictation to talk about the day.
I'll go in and I'll fill in the other half of the metrics. For example, you know, time with my family or effort put in, like, of ten, you know, the different things that are important to me. And it'll go and log those, and we can see the the different trends.
Right? If you like this video so far, please consider leaving a like and subscribe to the channel. YouTube tells me only 8% of you are actually subscribed, which is kinda wild.
So if you wouldn't mind making sure that you are, that would really help me out. And it also tells YouTube that you wanna see more content just like this. Let's get back to it.
Okay. So here's where things are changing a little bit and why I wanted to do this video like this and not a big flashy tutorial. Okay?
Because there's a lot of that and people don't seem to connect the dots ever. Everybody is interested in putting one and one and one and one, but not two and two. They're thinking about workflows and not systems, I think that is a a fundamental misstep.
I still, to this day, get the question, why use Obsidian and not just Cloud Code with some fun folder structures? And you're missing the point entirely. It's not enough that your agent can just read and navigate a folder structure.
That's not an operating system. I wanna keep everything in one place. I want it to be the one place where I can do everything, right, and not have to alt tab all the time or go in and separately make notes of my activity for the day.
If I keep it all in the one spot, I am infinitely more focused. There's a lot of folks out there putting out like operating systems and using Obsidian as a memory layer for it. And then they'll build out another interface for metrics and monitoring and all that other stuff.
And it doesn't make sense to me to have to go from one app to another app to another app to do all these different things. I can go to Obsidian and keep my eyes on everything, but not only that, I can work in it as well. It's the entire system.
It's not just the one workflow after another. It it's all working together. Like, I can check out Telegram.
I can check out Slack. Check my email. Bounce over to my school community.
See what's going on on YouTube. If people are, like, you know, responding to comments and that kind of thing. Right?
I've got my terminal right here, and then I can spin up the local host and just run this wherever. Can I move any of these windows wherever I want? It's really customizable, and the system is all in the one spot.
That is so important, and I'm gonna tie it back into the dashboard here in just a sec. Okay? But like a browser here, uh, the agent here, a different folder there, your dashboard somewhere else, all of that causes friction, and friction isn't harmless.
Every time you change context or have to, like, switch views or whatever, you're losing momentum. You might not notice, but you absolutely are. It might sound dramatic, but it's just good system design.
If you keep everything tight, so you don't have to go, like, searching or reaching for anything, and it's all in the same place, you're gonna be more productive. It's a lot easier to work with your toolbox nicely organized than it is to, like, go looking for a different toolbox is maybe the best analogy I can come up with off the top of head.
Anyway, back to the conversation at hand. Agents and Obsidian are great friends because they complement each other's strengths. Agents help you input to the Obsidian structure.
Obsidian fills in the memory gaps in your AI agent. It works great, except it still leaves the problem a lot of people have with note taking and personal knowledge based apps where they just, like, collect information and it . Where Obsidian is uniquely powerful over other PKMs is you don't just have to sit on all that information.
You can turn it into an intelligence layer either through a custom plug in like this, which is great. You just build out a mini app essentially to pull from your daily notes. You can do it with your canvas, right, with different charts views and things like that.
There's a lot of ways you could get there, and Obsidian offers that. That is useful and beneficial on its own, but when you factor in that you can actually go in and do the work in this platform as well, that's where things start to really compound. It doesn't make sense to think of these as like individual workflows anymore, and that seems to be what is most popular on YouTube tutorials is like, oh, I can do this, and then you put it back on the shelf, then you go to another app for something else.
No, man. Keep it all in the same place, and you'll be exponentially more productive. And that's really what I'm trying to say here, is stop thinking about things as like individual workflows and start building out systems where all these different things start working together for you.
So while I said the point isn't to, you know, worry about this particular dashboard, I do have a free starter vault that I'll leave a link in the description to some of my free stuff. But I also have this exact layout with the dashboard and intelligence plugin available through my school community. I'm updating that very shortly.
It'll be in the tools and agents section right here. The link to that will also be in the description. Make sure to subscribe if you wanna see how this continues to grow out as I build it out in the future.
Thanks for hanging out with me. I'll see you.
The Hook
The bait, then the rug-pull.
Eric Michaud opens his vault live — no intro, no B-roll — and within the first twenty seconds names the thing almost every productivity video leaves out: capture without execution is just a graveyard with a pretty interface. This is not a Second Brain tour. It's an operating system demo.
Named ideas worth stealing.
03:42concept
Workflows vs Systems
Workflows = individual automations strung together, put on a shelf after use. Systems = all components (capture, reporting, intelligence, execution) working together in one unified environment.
Steal forAny video or post arguing against SaaS sprawl or tool-hopping — maps directly onto Joe's stop-renting positioning
02:46model
Two-Command Day
- /today (open day — pulls calendar, inbox, carryovers)
- close day (end day — voice dictation + metric fill-in)
Entire daily tracking loop runs on two slash commands issued to a py agent. Everything else is logged automatically from activity inside the vault.
Steal forMorning routine / JoeFlow dictation integration — one command starts the day, one closes it
04:30concept
Obsidian as AI OS
Obsidian as unified operating system: notes + agents + browser + terminal + metrics all in one window. Contrasted against Claude Code + folder structure which lacks unified intelligence and reporting.
Steal forContent angle for MCN or JoeFlow — your tools should be one thing, not ten tabs
How they asked for the click.
VERBAL ASK
06:56product
“I do have a free starter vault that I'll leave a link in the description. I also have this exact layout with the dashboard and intelligence plugin available through my school community.”
Soft sell — mentions free resource first, then paid community. No urgency, no scarcity. Naturally embedded at end without a hard break.
MENTIONED ON CAMERA
FROM THE DESCRIPTION
PRIMARY CTAWhere the creator wants you to go next.
Visual structure at a glance.
