Two months ago, this wouldn’t have been possible.
Website audits. Implementation roadmaps. Site restructuring plans. Developer task lists with exact fixes. The kind of work that used to take days of grinding through tedious, boring, exhausting details.
Now? Brain to execution. Voice or text, doesn’t matter. Hours instead of days.
That’s the unlock.
But here’s what nobody’s talking about: just because you CAN go 10x faster doesn’t mean you SHOULD run at rocket speed all day long.
The Crew
The Content Capo is active now. The Bing crew handles strategy and planning. This weekend I’m exploring a secondary dev team, a separate crew focused strictly on technical work. Code reviews, pipelines, all the heavy development stuff that needs deep focus.
Multiple crews. Multiple machines. Distributed team experiments that honestly blow my mind every time I think about them.
Here’s what it actually looks like in practice: I have a Chief of Staff who orchestrates everything. An Architect who handles research and system design. A Content lead who writes copy and documentation. Each one has a defined role, a workspace, communication patterns. They talk to each other. They hand off work. They report back.
It’s not theoretical. I gave the Content lead a client site audit last week. Research came back in 35 minutes. The write-up was done 14 minutes after that. Work that would’ve taken me half a day of context switching and note-taking, done in under an hour while I was doing something else entirely.
I’m in the driver’s seat now. High agency architect and engineer who’s no longer stuck waiting for blockers outside my control. With agents helping, there’s literally nothing stopping me from executing.
Technically I’m still doing all the work. But I’m not getting blocked by roadblocks I can’t do anything about. That’s always been my biggest frustration. Now I find workarounds. Move forward. Ship.
The Cost
No pause in weeks. It feels like being in a tornado.
You can exhaust yourself with AI just like anything else. Maybe more so, because the speed makes you think you should keep going. The rocket ship energy is real. You finish something and immediately think “what’s next?” because the friction is gone. There’s no natural stopping point anymore.
With traditional work, there were built-in pauses. Waiting for a deploy. Waiting for a client to respond. Waiting for a designer to hand off assets. Those pauses were annoying, but they were also rest. Now there’s no waiting. Every bottleneck dissolves and you just keep going.
But I’m not a rocket ship. I’m a cool Cadillac Escalade powered by rockets, hot pink and black, very on brand. And even rocket-powered Escalades need to slow down sometimes.
The Lovable Gazelle redesign keeps dragging on even with all these tools because I’m obsessed with getting it right. It’s being built behind the scenes. I love the hero messaging. Refining the stories. But “shipped” doesn’t mean published yet. It means it exists somewhere, in an environment, getting better.
That’s something I’ve had to accept. Speed doesn’t mean everything goes live immediately. Speed means you iterate faster. You test more. You refine more. The output quality goes up, but only if you don’t skip the thinking part.
Can’t keep up with the pace in day-by-day format anymore. So I’m dropping the day numbers. This is just where we’re at now.
The Part Nobody’s Saying
If your employees can get what’s in their brain into high-value action plans and produce at 10x speed, they should be compensated accordingly.
10x output at the same pay is insane.
I’ve seen the conversation happening online and it’s almost always framed from the employer’s perspective. “AI makes workers more productive.” Great. But productive for whom? If someone is now delivering in one day what used to take a week, and their paycheck stays the same, that’s not innovation. That’s exploitation with better tooling.
Companies need to:
- Pay for the tools
- Teach people how to level up
- Charge clients appropriately
- Compensate employees for the actual value they’re creating
Just because things are easier doesn’t mean the value decreased. It increased. The person using AI effectively isn’t doing less work. They’re doing higher-leverage work. The thinking, the strategy, the decision-making, all of that still requires a human brain. AI handles the execution grunt work. The human handles the judgment.
That’s what makes this whole thing weird. The work that used to be too tedious to even consider? Now it gets done same-day. But running at this speed all day will burn you out if you’re not careful.
What’s Next
This weekend: exploring Miles.AI and building that secondary technical team. Figuring out what works when you’re running crews on different machines with different specializations.
The distributed team coordination experiments continue. I’m learning that managing AI agents is eerily similar to managing human engineers. They need clear roles. They need good handoffs. They need accountability structures. Skip any of that and things fall apart fast, just like with people.
The difference is the speed of iteration. With a human team, it takes months to figure out the right dynamics. With agents, you can restructure, test, and adapt in days. The feedback loops are compressed. The learning is faster. But the fundamentals are identical.
And honestly? With agents in the mix now, there’s literally nothing stopping me. Except maybe myself. Knowing when to slow the Escalade down before I hit a wall at rocket speed.
That’s the real unlock. Not just speed, but knowing when to use it and when to coast.
Still figuring that part out.
