Building a CEO OS with Grok Bot
Five months since my last post. I've gone from a Slack hub that routed my messages to Grok Bot on the desktop, and what I'm building now is a CEO OS that shows me the next work and hides the rest.
My last post was March 15. I ended it saying I’d write the next day about workspace structure and heartbeat monitoring. I didn’t. Five months went by, and the work kept going without the writing.
Then
Back in March I was updating CouplePay and the whole operation ran through Slack. Diger was my Chief of Staff on GPT-5.4, sitting at the hub, with content, dev, growth, research, and ops out on the spokes.
I’d message Diger and Diger took it from there, pulling in whichever specialist the work needed, leaving a paper trail in their channel, coming back to me with an answer. I liked it. For one product, with one thing on my mind, it did what I wanted.
What it couldn’t do was tell me what to work on. Every loop started with me writing the message. Fine for one product. Bad fit for three lives.
Now
I’m running three things at once these days: my personal life, Switchboard Live, and Diger Studios. For a while a travel day, a company call, and a product decision all landed on the same pile, and I’d just pick up whatever felt loudest.
So I split them apart. I talk to Grok Bot on the desktop now, with separate assistants for each of the three so they stop sharing a pile, and Cursor cloud agents doing the work in the repos.
Personal. Calendar, travel, the rest of my life. The first thing I starve when work gets loud.
Switchboard Live. The company I already run. It has its own pace and I don’t get to change it.
Diger Studios. Consumer and SMB products. CouplePay lives here. This is where I ship.
I’m not trying to route my own Slack messages anymore. I’m building a CEO OS, so the three of these stay out of each other’s way.
Show me the next work
I don’t need another inbox.
What I want is the next piece of work sitting in front of me when I sit down. Most days the expensive part isn’t doing the thing. It’s working out what the thing is. Calendar, messages, company threads, product threads. I can burn an hour sorting all that before I’ve decided anything at all.
I’d rather Grok Bot hand me the queue and let me pick. I decide, it prepares.
If I still have to assemble the day myself, I don’t have an OS. I have more chat windows.
Hide the rest
The flip side is that I want everything outside that queue kept away from me.
Almost all of it can wait (status, small questions, things that feel urgent only because they just showed up). If I can see all of it, I’ll treat all of it like work.
Interrupt me for a founder call or a real blocker. A decision that’s actually mine to make. Something that stays stuck until I touch it.
Everything else sits in its lane until I come asking. I want fewer things reaching me.
Until the next post
That’s where I am right now. I’ll let it run for a while and pay attention to what actually reaches me.
Still building in public. Let’s see how this goes.
This is part of a series on how I’m using agents to run the work. Follow along on Twitter.