The Morning Standup
- Two days of nothing. Travel to Hanoi. I thought I'd keep building from taxis and hotel lobbies. I couldn't. The multi-delegation skill isn't there yet. That's a real post coming soon.
- Setup prompts for the blueprint. Written so someone can install the whole operating system on their own machine, start to finish, without me walking them through it.
- Marketing team install flow. Operationalized. Drop in, go.
- TK Nguyen and his video team, onboarded live. In the room. Real work. AI mindset flipped inside of an afternoon.
All of that before the real story started.
Why Today Mattered
For the first 10 days of this build, I was making everything work for me. My machine. My folders. My brain. That was the point. Prove it runs.
Today was the pivot. The question stopped being can I build this? and became can someone else install this?
Those are two very different questions. The first one is ego. The second one is a business.
So we spent the morning writing setup prompts. Things that turn a messy collection of files into a single sequence a non-technical founder can actually follow. Install Claude Code. Link your GitHub. Paste this prompt. Answer the questions. Wait three minutes. The marketing team agent is on your machine.
If the system only runs on your laptop, you haven't built a system. You've built a pet. A one-man company made of AI agents doesn't scale until installation is the first feature, not the last.
That shift, from "I can use this" to "you can install this," is the whole reason Day 11 mattered more than Days 9 or 10 combined.
The AI Mindset Shift
Mid-afternoon, my friend TK Nguyen showed up with his video team. TK runs GAM Entertainment and Skylight rooftop bar in Nha Trang. He is not technical. He is a founder, an operator, a storyteller. The techy stuff has always felt like someone else's job.
He sat down. Skeptical. You could feel it.
Then, over the next couple of hours, I watched his face change. Not when I explained the tools. When he started asking different questions. He stopped asking how does the AI work? and started asking what would I have it do first?
That's the flip. That is the AI mindset shift.
When a founder goes from "how does the AI work" to "what would I have it do first," they are no longer a user. They are a leader of a team that happens to be half AI. The tools become invisible. The ideas take over.
TK walked in wondering if this was for him. He walked out with a list of agents he wants to install by end of next week. A marketing lead. A scheduling assistant for the bar. A video pipeline for GAM. None of that was on the table when he arrived.
He didn't need a bootcamp. He needed an engineer at the table for one afternoon.
The Other 50%
I'm writing a book right now. Working title: The Other 50%. The whole thesis is there in the name. The future team is half human, half AI. Most leaders are comfortable with the human half. They've been building those teams their whole career. The other half feels intimidating. New rules, new language, new failure modes.
Here is what watching TK unlocked for me, and what the book is really about. The AI mindset shift isn't technical. It's relational.
The other 50% is not intimidating because it is technical. It is intimidating because you are trying to meet it alone.
TK didn't need to learn how Claude works. He needed someone beside him who already did. Once that was true, the intimidation evaporated, and what was left was the part he is already world-class at: taste, story, customer, ideas.
That is the retreat in one sentence. We pair you with an engineer for two days. You walk in with the same intimidation TK had. You walk out leading a team that is half human, half AI. Your ideas are the bottleneck again, the way they should be.
Day 11 of 14
Three days left.
Ten days in, I've been proving the system can run. Day 11 was the first time I proved it can travel. Install prompts in the morning. A founder from outside the team, unlocked by the afternoon. That's the signal I was waiting for.
The machine runs. The install ships. A friend got onboarded without me writing a line of code for him.
The last three days are about one question: how much of this can we hand off, cleanly, to the next person who walks in the door? Because the retreat is no longer theoretical. TK just showed us what it looks like.
Read next: Day 10: The Coaching Assistant · Day 9: The Day the Designer Got Stuck · You Don't Need to Become Technical. You Need a Stack.
See you on Day 12.