I'm at a 45,000-Person Conference and My AI Second Brain Is Running My Company Back Home

I’m at HIMSS this week. 45,000 people. Three days of back-to-back sessions, hallway conversations, and vendor meetings in Las Vegas.

My company is running without me.

Not because I have a huge team covering for me. Because I built a system that does it.

The 5 AM Operating System

Every morning at 5 AM ET, before I wake up in my hotel room, a 17-step operating system kicks off automatically.

It pulls my call recordings from yesterday. Scans my calendar. Runs a company pulse check across Slack, email, and CRM. Enriches any new contacts in our CRM. Triages both my inboxes. Preps me for today’s calls. Summarizes everything that happened overnight across every channel. Reviews the sales pipeline. Scans industry news. Generates content ideas. Processes my task backlog. Pulls business metrics. Flags relationships I haven’t touched in a while. Audits whether I followed up on last week’s meetings. Plans my day.

Then it compiles all of it into a single daily brief that’s waiting for me when I open my phone.

By 6 AM, before I’ve had coffee, I know exactly what happened, what matters, and what to do first.

What Happened While I Was on the Conference Floor

That’s the morning. Here’s what happened while I was walking the HIMSS floor on Monday.

My system iterated a sales deck from v6 to v9. Four versions in one day. Fixed margins, updated slide content, improved centering. Uploaded each version to Google Drive and posted it to our internal channel for review.

It rewrote 12 marketing documents to match our new positioning. Pricing pages, FAQ, competitive analysis, proposal templates, ICP profiles, messaging frameworks. All consistent. All updated in parallel.

It ran a full LinkedIn content analysis across 62 published posts and a year of analytics data. Identified that customer case studies with specific numbers outperform everything else by 3x. Documented 14 improvement ideas for our content system.

It processed 292 emails across two inboxes. Classified every message. Archived what didn’t matter. Created task files for things that needed action. Both inboxes hit zero.

I didn’t touch any of it. I was in a session about AI agents in clinical workflows.

The Conference Anxiety Problem

Here’s the thing nobody talks about at conferences. The CEOs walking around aren’t fully present because half their brain is worrying about what’s piling up back at the office. The inbox growing. The Slack messages stacking. The decisions waiting.

I stopped worrying about that months ago.

How It Works

The system isn’t magic. It’s an Obsidian vault, Claude Code, a handful of API integrations, and a lot of carefully written skill files that tell the AI exactly how to do each job.

The reason that works is the same reason a coding agent is not just a coding tool: it becomes infrastructure around the way you operate.

It took months to build. It breaks sometimes. I fix it and it gets better.

But the compounding effect is real. Every skill I add makes the next one easier. Every morning pulse run catches things I would have missed. Every triage cycle keeps the noise from turning into chaos.

Tool vs. Infrastructure

I’m not saying every CEO needs to build this. I’m saying the gap between “CEO who uses AI tools” and “CEO whose company runs on AI infrastructure” is getting wider every month.

At HIMSS, I watched vendors pitch AI copilots that help with one task at a time. Summarize this note. Draft this email. Answer this question.

That’s helpful. But it’s not the same as a system that wakes up before you do, runs your entire operating rhythm, and hands you a brief that says “here’s what happened, here’s what matters, here’s your plan.”

One is a tool. The other is infrastructure.

I know which one I’d bet on.