I built "Me Inc" as a personal operating system that runs like a firm. The idea: instead of Claude doing everything in one big conversation, I have a full org chart. CEO routes the brief. COO dispatches it. Departments execute. Specialists deliver. Here's the structure: Ariel (Principal) → CEO (classifies input, catches escalations, routes work) → COO (dispatches to the right department) → Delivery (client work, competitions, product builds) → Marketing (brand, content, copy, distribution) → Finance (cash, capital allocation, deal screening, pricing) → Knowledge (research, competitive intelligence, intake routing) → Partnerships (B2B relationships, outreach, deal conversion) → 20+ Specialists across all departments Coming soon: Studio, Career Each layer has CLAUDE.md files with routing rules, escalation gates, handoff formats, and model assignments. Took weeks to build. What Me Inc. Is and Why It's Built This Way I'm a solo operator — operations consultant, builder, running a portfolio of projects. When I first started using Claude Code in October last year, I built "Me Inc." as a way of keeping all of that organized, a way of running my life as a company would — and I hit the wall: Claude is powerful, but a single conversation doesn't scale. Every session started from scratch. Context would bleed between project types. I'd ask for a LinkedIn post and Claude would drag in client project context. I'd ask for a financial decision and get generic advice with no awareness of my actual sovereignty stage or capital position. I'd brief a competition build and the whole history of unrelated work would contaminate the output. More fundamentally: different work requires different thinking. A pricing decision and a cold outreach draft and a domain research sprint are not the same cognitive task. Routing all three to the same model at the same tier in the same context is like asking your accountant to also write your copy and also do your competitive research — in the same meeting.

At a going away party this weekend, I was talking to some government workers who mentioned they're mandated to use Copilot at work every day. Naturally curious I asked, "Oh what do you use it for?" They both sheepishly admitted that they don't. "We just don't see how it's useful for what we do." Later that night: birthday dinner at a German restaurant I'd been trying to get to for years. Some old theater colleagues: a props artisan, a lighting designer, they spend their days with hands-on physical work. AI didn't come up once. Meanwhile I was sitting at the table quietly asking Claude to translate the menu. It didn't just give me definitions — it told me the story behind one of the dishes. Monks during Lent, hiding meat inside pasta to get around fasting restrictions. Made for a very fun conversation topic but nobody noticed I had found out from Claude. It's very interesting being inside this bubble of thinking about how to make the most of AI all the time and finding that everybody else seems to just not care. A small win though, my brother got a Claude subscription this weekend. I've been sharing with him what I've been able to do with what I've learned here and it took him a bit to get over the hurdle of paying for a subscription (he's very frugal), but after a day auto-transcribing a jazz improvisation recording straight to sheet music, he's already organizing his context with folders and texting me about projects he wants to build. How is everyone else finding how people outside the community talk about AI?