No HR department. No finance team. No marketing hire. One owner holding every seat in the C-suite, and an AI operating layer doing the work the org chart used to. This is not a product I'm selling. It's a bet I'm running live, in a real business, with real money and real labor. Here's the bet, and here's exactly how far along it is. I'm sharing it in the open and would love to compare notes with anyone building something similar.
The exception rate falls faster than the business grows.
Delete the departments and the work doesn’t vanish. Every exception, every novel call, everything the agents can’t handle routes to one human. Me. So the wager isn’t “can AI do the work.” It’s whether the things that need me shrink faster than the portfolio expands. If that line goes down, that’s real leverage. If it doesn’t, I’ve built myself a worse job. That’s the part I’m actually testing, in the open.
I don’t need it to work today. Parts work now. Parts don’t. The intelligence is arriving on a curve I can see, and the honest alternative was never a well-run company. It was an owner drowning in fires, dropping balls, letting it drift. I’m not claiming perfect. I’m claiming better than that, which is most of us. I log every decision so that when the intelligence catches up, the context is already loaded and it just runs.
The traditional hotel company is an org chart of salaries. Each box is a person, a benefits line, a layer between the owner and the work. I replaced the boxes with agents and routed all of them through one orchestrator that answers to me.
Every box below is a real system I’ve built or am building — a dashboard, an agent, a data pipeline, an API connection — grouped by the seat it fills. This is the honest state of the bet: what runs today, what’s mid-build, what’s still on the bench. It updates as I ship.
Every layer between the owner and the work is delay and dilution. The org chart isn’t the company. It’s the tax the company pays to move information slowly.
The easy gains are spent. What’s left is application: wiring real intelligence into real operations and funneling it to one screen. That is the entire game now, and it’s the part I’m trying to crack.
The model is rented and everyone rents the same one. The standards, the history, the way this specific business decides: that’s the asset, and it compounds every week the knowledge base grows.
Most owners my size never hire the C-suite. They let it run reactive, stressed, dropping balls. I’m not measuring against a flawless company. I’m measuring against that, and against that the bar is low.
Activity logs are noise. What compounds is the judgment: the exception, the call I made, and why. Capture that and the future model loads judgment and takes off. Capture clicks and it loads sludge.
That’s the honest risk, stated plainly. If the exceptions shrink faster than the business grows, this is freedom. If they don’t, it’s a trap with better tooling. I’d rather find out in the open than pretend.
The edge isn’t a smarter model. It’s owned context.
Anyone can rent the same models and the same connectors. What compounds is the operational context underneath: the standards, the history, the way this specific company makes decisions. Own that context and rent the connective infrastructure around it. The agents get sharper every week because the knowledge base does, not because a model got retrained. That’s the part a competitor can’t copy by buying the same tools.
I'm always hunting for the next thing worth automating. If you have an idea, a problem you'd want solved, or feedback on any of this, send it my way. Leave your name and a way to reach you if you want a reply, or send it anonymously. Both are welcome.
I’m building this in the open because I learn faster that way, and I’m genuinely open to feedback and new ideas. If you’re working on something similar — or it just sparks something — I’d love to hear what you’re building, share what I’ve learned, and trade notes.