I’ve been building websites since I was 13 years old. It started out as something I taught myself for fun, then it turned into something businesses were paying me to do properly, and I’ve had my hands in the code of every site I’ve owned since. So handing my own website over to a team of AI agents wasn’t a decision I took lightly.
But that’s exactly what I did. This website you’re reading right now, I didn’t build it. My AI agents did. And they’re the ones running it now, too.
One of them writes the articles. One watches how the pages are performing in search and tells the others what’s missing. One owns the code and pushes the changes live. I set the direction and I say yes or no, and that’s genuinely about it. The hands on the keyboard aren’t mine anymore, and I’ll be honest, it took me a while to get comfortable with that.
The other thing worth mentioning is that the whole team runs on a piece of software that isn’t even finished yet.
Where My Team Actually Lives
The platform is called Buzz. It’s built by Block, the company behind Square and Cash App, and it’s essentially a messaging platform where humans and AI agents work together in the same space, sharing ideas, knowledge, context and understanding between each other. I post a task into a channel, one of my agents picks it up, goes off and does the work, then posts the result back where the rest of the team can see it. Nothing is tucked away in a private chat window that only I can open.
It’s also in developer preview, which is a polite way of saying it breaks.
The Things That Broke
I started keeping a list, mostly because I got tired of rediscovering the same problems on a Sunday afternoon. Here’s some of what I’ve run into so far.
Mentions sent from my second device that quietly never arrive.
Delete commands that tell you they worked and then delete nothing.
Access settings that never reach the agent until you rebuild it from scratch.
Member lists that disagree with the change you made ten seconds ago.
Every one of those cost me time, but the delete one is the worst and it’s worth explaining why. Something that fails loudly in front of you is easy. You see it, you swear at it, you fix it. Something that tells you it worked and quietly did nothing at all will sit there for days before you notice, and by then you’ve built three other things on top of it. That’s a lesson I’ve since applied to a lot more than Buzz.
So Why Am I Still Using Buzz?
Because right now it’s small enough that I can understand the whole thing. I can hold it in my head. When something breaks I can usually work out why, and most days I can find a way around it before the day is out. Try doing that with an enterprise platform that’s had ten years of features bolted onto the side of it.
That window doesn’t stay open for long though. In two years Buzz will be polished and crowded, and there will be consultants charging good money to explain it back to you. The things I’m learning by hand this year, mostly around how agents actually behave once you give them a job and walk away, all of that gets buried under a friendly interface by then.
So the mess is sort of the point. Anyone wrestling with this stuff now is getting a two year head start on everyone who waits for the manual to come out.
What an Agentic Workforce Actually Looks Like
That phrase gets thrown around a lot at the moment, usually by someone selling something, so here’s the plain version. An agentic workforce is a group of AI agents with actual defined jobs, working in the same space as the humans, picking work up on their own instead of sitting there waiting for you to prompt them.
That last bit is the whole difference and it’s the part most people miss. Using ChatGPT well is still a conversation you have to drive. You open it, you ask, you read the answer, you copy it somewhere useful, then you do the same thing again tomorrow. Every single step needs you sitting there.
My team doesn’t work like that. The SEO agent finds a gap in what the site covers and writes up a brief. The writer picks up that brief, drafts the article, checks it against my language rules (which are strict, ask anyone who has tried to write in my voice) and gets it ready to publish. The developer agent handles anything that touches the structure of the site. I read the thread and I say yes or no.
The work moves sideways between them without coming back through me every time, and that’s the bit that genuinely gave me my week back. I’m still the one in charge. I’m just no longer the bottleneck standing between one task and the next.
Rebuilding the Site Was the Easy Part
Agents are good at a job with a clear brief and a clear finish line. Rebuilding a website is exactly that. You can see when it’s done.
Running it afterwards is the hard part, and that’s where I’ve learned the most. The site still needs watching. The copy still has to sound like me rather than a machine doing an impression of me. Someone has to notice on a random Tuesday that a page has slipped in search or a form has stopped delivering, without me asking them to go and look.
Working in shared channels is what made that possible. Because the work lives in a thread, I can scroll back and see exactly how a decision got made. I’ve sat there and watched one agent push back on another agent’s plan and argue the case for a different approach. When something does go wrong, the trail is sitting right there in front of me instead of being locked inside a private session I can’t get into.
What This Means for Your Business
You don’t need Buzz, and I want to be really clear about that. Most people reading this should be nowhere near a developer preview, and I wouldn’t put a client’s live operations on one either.
The tool matters far less than the timing. Every technology that ends up running businesses goes through a window where it’s rough and cheap and small enough to understand, and then the window closes and the price goes up. The people who spent that window with their hands dirty come out the other side knowing things you can’t read anywhere, because nobody has bothered to write them down yet.
Agents are in that window right now. And I mean agents that hold down a job and keep working after you’ve closed the laptop for the night. That’s a very different thing to the chat assistant you already have open in a tab.
If you want to be ready for it, go and run one. One agent, one job you’d otherwise hand to a junior, and enough patience to sit with it while it gets things wrong for the first few weeks. You’ll learn more in a fortnight of that than in a year of reading about it.
Jack Dorsey’s teams have built things that changed how people talk to each other before, so I’d back this one to land. But even if Buzz doesn’t go the distance, that fortnight still isn’t wasted, because whatever comes along and replaces it is going to look a lot like this.
So start now, while it’s still messy and nobody has written the manual. That’s when it’s cheapest to learn.
And if you’d rather not work all of that out on your own, I’m building a program around exactly this, for a small first group. It isn’t open yet, but tell me what you’d want an agent to take off your hands and you’ll hear about it before it goes wider.