Why does AI in a small business have to start with the owner?

Owners want to hand AI to their integrator. Gus Waite and I explain why it has to start with the founder, and what a Source Code captures first.

Because a business is built around the way its owner thinks, and AI can only work from what it's told. If the founder hands the whole thing to an integrator before using it personally, the agents end up running on someone else's guess about what the owner wants. The owner has to go first, get clear on what they believe and how they talk, and then give it to the team.

Gus Waite and I got into this on the first episode of Season 2. It's the mistake I see most, and I've made plenty like it over a career of coaching owners.

Why not just give AI to the integrator?

Because the reason you want to hand it off is that you're too busy, and that's the same reason it fails. The usual model is that the founder has an idea, passes it to the integrator or the key person, and moves on. With AI that's failure number one. It isn't something you give away until you have it working for yourself.

It doesn't take much time. We block it out and wall it off. If it's two hours a week, that's enough to start interrupting the old thinking, because you begin to look at your own business through a different set of eyes.

What does the owner have to get clear on first?

Who they are, written down. Gus said it in a way that stuck with me:

Every business is a reflection of the owner's operating system.

Gus Waite

We capture that operating system in what we call a Source Code. It comes out of a long interview, and it covers three things: the owner's personal beliefs, where they want the business to go, and how they communicate. In practice that means questions like these:

• What are your vision, values and beliefs?
• Who is your ideal client, and who do you love working with?
• What do you love to do?
• How much money do you actually need to live the life you want?
• How many hours do you actually want to work?
• What words do you hate?

That last one matters more than it looks. Gus hates consultant speak and legalese. He says it makes him feel stupid and it doesn't sound like him. Once the Source Code is loaded into a Claude project, every outgoing email, blog post and LinkedIn post runs through it, so nothing goes out in a voice the owner would never use.

Gus made another point about the interview itself. Most owners have never had ninety minutes with another person focused only on them: their business, what they love, how they got into it, whether they want to hand it to their kids or sell it, where they want to be in two years. They can't have that conversation with their employees, and often not at home either. The interview is sometimes the first time they've said any of it out loud.

What happened when I did it myself?

Gus and I trade. I coach him on building his business and he coaches me on AI. When he walked me through my Source Code, I talked about things I had never talked about. I found blind spots I'd been too busy being busy to see. I got clear on what I loved, what I didn't, what I'd do next and what the future looked like. Some questions I couldn't answer, and that was fine. It had me thinking. That session alone changed my future, before we implemented a single agent.

Then came trust. I didn't believe a machine could understand me, so I pressure tested it. It had every one of my webinars and books, everything I'd shared, and it answered questions about my own methods better than I could, because it could recall what I'd forget in the moment. It described how I talk. It said I'm a drill-down straight talker who starts in the middle of things. My wife Judith had a field day. She said it described me to a T. When my wife says something is right about me, I know I can trust it. That was the moment I started trusting the tool.

What does owning the outcome have to do with AI?

Everything, and Gus told a story on himself to show it. He had someone helping with his inbound marketing. Something broke in the cold email outreach, the helper couldn't find the fault, and Gus was distracted. Gus got frustrated that it wasn't working. The helper went away for a week and got frustrated that Gus wasn't communicating clearly. In Gus's words, his internal operating system made it the other man's problem.

I told him what I tell every owner: you are responsible for the outcome, not the person you hired. So he started over. He brought on a new VA with a clear container around her: the results, the deliverables, no mission creep. He met her every morning at 6:00 for the first two weeks. She wasn't there to save him or to listen to his ideas, and he wasn't there to save her.

I own the outcome.

Gus Waite

Here's where the AI came in, and why it only worked because he'd done the owner work first. He got 85 resumes from the Philippines. He set up a Claude project and told it exactly what the deliverables were. It helped him write the ad and vet the candidates, set up the interviews and suggest what to ask. After each interview he fed the transcript back into the project and asked whether he should hire that person. He told me it would have taken weeks the old way, and he did it in two days. The tool was only as good as the clarity he gave it.

What does the owner get back?

Gus uses his Source Code as a daily check. He loads in his thirty-day action plan and the outcome he wants, and each morning he asks it for the three most important actions to take right now. It coaches him through them.

He also uses it as a safety valve. We've all fired off an email when we were tired and irritated and then had to send an apology. His agents draft his emails at the end of the day from the Source Code, and when he reads them he says they sound like him when he's really on his game. He asked us to imagine a whole company where every person's work goes out as their best self.

Then there's the harder part, the owner's ego. Gus asked whether an owner can hold the possibility of doubling or tripling their income while working two or three hours a day and doing only what they love. A lot of owners' sense of their own worth is tied to working eighty hours a week. He was clear this isn't magic and it isn't set it and forget it. The inside has to line up with a new possibility, and then someone has to lead them down the path.

So if you're about to hand AI to your integrator, stop for two hours this week first. Write down what you believe, who you love working with, what you need to earn, how many hours you want to work and which words make you cringe. Then use one AI project on your own work until it sounds like you. After that, you'll have something worth handing over.

Cut from How to Build a Business That Stops Costing You Your Life.