Entrepreneur | Surfer | Founder @Ownboxio Everybody’s building AI agents, I built the place where they work.
Orange County, CA
Joined March 2021
- Tweets1.3K
- Following555
- Followers3.7K
- Likes4K
The most important database in your business is a person, and that person can quit. My AI Brain keeps what my business knows on my own Ownbox: type it, edit it, or add a photo and it reads the words. Try a working one at ownbox.io/demo
Your next customer is asking ChatGPT who to hire. It's naming somebody right now, and if it isn't naming you, that's the whole conversation.
AI For Business OC is a monthly meetup for non-technical business owners and the people who run their operations.
I open with a 15-minute talk on how AI search picks the businesses it recommends and what makes a local business one of them. Then we work, laptops open, on your actual website and your actual leads. You leave knowing where you stand in AI answers for your service and your city, and with the first fix already in motion.
For Orange County local business owners and marketers. No technical background needed. Bring a laptop and a real question about where your leads come from. Location is shared with members.
meetup.com/ai-for-business-o…
How many leads are you getting from ChatGPT?
Ask it who to hire for what you do in your city, and read the names.
Orange County, CA: free monthly meetup
FOR NON-TECHNICAL ENTREPRENEURS in Irvine.
DM me MEETUP for the invite.
Your company should be able to run a whole day without you touching it. Mine did today — twenty agents, three bosses, and one rule about who's allowed to ship.
That rule is the entire thing. You don't need a beach, you need a chain of command that doesn't route through you.
Comment TEAM and I'll send you mine, free.
#claudecode #aiagents #buildinpublic #aiautomation
Every Claude Code teacher shows you the same thing: you, at the desk, in the loop all day. Watching your terminal from your phone is still you doing the work.
Nobody teaches the company you build around it. That's the part that lets you leave.
Respect to @austin.marchese @aiautomationsbyjack @robonuggets — start with them, then come back.
Comment TEAM and I'll send you the chain of command, free.
#claudecode #aiagents #buildinpublic #aiautomation
My best ideas never show up at the desk.
I'll spend two hours stuck on a problem, paddle out, and halfway through a set it just untangles. My dad told me the same thing while he was building his tech company: step away from the problem, take a walk, and the answer will present itself.
People think building something is about grinding harder — more hours, more screen, more coffee. It's the opposite. The work gets sharp when you step away from it, not when you force it.
The paddle out isn't time off. It's the part where the hard problem actually gets solved.
Building a tech company stopped being the hard part.
I can build faster than at any point in twenty years — and so can the guy copying me. My competitors raised tens of millions and hand every new customer $100 just to try their product.
I can’t match that spend. I can be louder than them, for longer.
Day one scoreboard: 100 local businesses handed their phones to Mavrick in month one. He answers, qualifies, books. The goal is 10,000 — and I’ll show you every step. The wins, the dead ends, the real numbers.
Be loud. Start before it’s impressive. It’s the only edge money can’t buy.
I tried to trick an AI receptionist at a real law firm.
New series. I pull up a real business on Google, Mavrick becomes their receptionist on the spot, and I call in trying to stump him. Episode one: a personal injury law firm.
The move that matters most isn't what he answers — it's what he refuses. Ask about a service that isn't on their site and he says no and takes a message instead of bluffing. Ask if you have a case and what it's worth, and he gives zero legal advice — name, number, what happened, an attorney will call you back. That's the one thing a law firm's phone can never get wrong.
Episode two: HVAC, and I'm calling at seven at night.
Twenty agents working at once have one real failure mode. It isn't bad code.
It's that none of them know what the others just did.
Two agents fix the same bug in the same hour. A third rewrites a file a fourth is mid-way through. Someone solves a problem that was already solved yesterday, and nobody finds out until the merge. This is what breaks multi-agent systems in practice — not capability, not model quality.
The fix is one shared file every agent reads and writes. Here's how to build one, and the six rules that keep it useful past the first week.
1/6
Rule 5: Never write the wall from a snapshot. This is the rule I broke myself, and it's the one that silently destroys the channel.
An agent that read the file an hour ago, appended its line to that old copy, and pushed has just deleted every post made in the meantime. The diff looks like one addition to the agent. To everyone else, it's a mass deletion.
Two things fix it: always re-read the file immediately before appending, never from memory. And a check in the build that fails any change removing existing posts. The only correct change to a shared channel is pure addition. If your diff shows a removed line, stop.
Rule 6: Put the writes through a lock. Two agents posting at the same moment will silently eat each other's messages. At twenty agents, this isn't rare — it's a Tuesday. One lock around the read-modify-write, held for the length of a file append, and the problem is gone permanently. A message that vanishes leaves no trace. Everyone believes it arrived.
5/6
Don't build all six today.
Build the file and the injection hook — rules one and two — and use it for a day with whatever agents you already have. You'll discover the other four in the order I did, because each is something that breaks in a way you'll recognise the moment it happens: the chat log, the vanished message, the mass deletion, the post nobody could parse.
Then come back and add the guard for the one that just bit you.
One file. Injected, not remembered. Additions only. The commit history holds everything older than the newest posts — searchable in one command. Short and current in front, complete behind.
The full breakdown, with starter prompts to build each rule, is in the piece linked in tweet 1.
brian-macdonald.com/guides/h…
6/6
Turn your phone off Saturday morning. Turn it back on Sunday night.
Whatever happened in between is the only honest answer to whether you own a business or a job with better branding.
Most founders never run the test. They already know.
The weekend test doesn't measure whether work got done. It measures whether work could *start* without you. No decision stuck waiting on a text you didn't send. No lead sitting because you were the only one who could answer it. No customer waiting on a quote only you can price.
Stack ranks and org charts won't tell you this. Two days of silence does.
1/5
Most people start with the work they hate first.
It feels like the obvious move. It doesn't work.
The work you hate is often trivial. The work that traps you is often work you enjoy — being the one who talks to good customers, being the one who solves the hard problem. Enjoying it is exactly why you never delegated it, and exactly why the business stops when you step away.
The order that feels right is wrong. Sort by dependency, not by dread.
4/5
Run it this Saturday.
Phone off at 10am. Back on at 6pm Sunday. Write down everything that waited.
That list is your build order — more honest than any strategy session you'll ever run, because it came from the business itself, not from how you think about the business.
If nothing waited, you own a business. If seven things waited, you now know exactly which seven to fix.
brian-macdonald.com/articles…
5/5
