I have trained more than 90,000 people since 1998, and I still catch myself answering the same question three times in one week. Not because the answer is hard. Because the answer lives in my head and nowhere else.
That is the bottleneck nobody talks about. You write the SOP, you send the Loom, you get on the call, and three weeks later the contractor asks the exact same thing again, and you answer it again, because saying no to a person you hired feels terrible.
So you keep repeating yourself. And the business keeps depending on your calendar.
The Real Cost Is Not the Time, It Is the Interruption
When I count what a new contractor actually costs me, the hours are not the expensive part. The interruptions are.
I am deep in something, a proposal, a build, a conversation with a client, and a Slack message arrives. Where do we save the final versions. Do I invoice before or after the kickoff. What do I do when a client goes quiet for two weeks. Small questions. Each one takes me a minute. The problem is that it takes me a minute to get back into what I was doing, and that is the actual number that matters.
If you are the founder of a service business, you are not short on knowledge. You are short on distribution. Everything you know about how the work gets done sits in your head, in three old documents, and in a Slack channel nobody searches.
The fix is not another Google Doc. It is an onboarding buddy that never gets tired of the twentieth question, because the twentieth question costs it nothing.
You Already Have the Raw Material, You Just Have Not Structured It
Here is what I want you to do before you touch any AI tool. Go find the documents you already have. The client onboarding checklist. The proposal template with the notes in the margins. The Loom where you explain your process. The email you sent a contractor six months ago explaining how you handle revisions.
That is your source material. Most founders have 80 percent of an SOP system already written and just never collected it in one place.
Now structure it. I use three buckets, and they matter more than any tool choice:
How we do things. The process steps. How a project moves from signed to delivered. Where files live. What the checklists are.
What we believe. The judgment calls. Why we push back on scope creep. Why we do not chase every lead. Why the client call comes before the deliverable. This is the part founders skip, and it is the part that makes a contractor sound like they work for you instead of for a template.
What to do when you are stuck. Escalation. Who to ask. What is urgent enough to interrupt a client. What can wait until Thursday.
That third bucket is the one that saves your sanity. If a new contractor has a clear path for stuck moments, they stop inventing one, and the invented one is always a message to you at 9pm.
Turning Those Documents Into an AI Onboarding Buddy
You do not need to build software. I have set this up three different ways, and the simplest one works fine for a business your size.
Option one: a custom GPT or Claude project. I use Claude Projects for this. You create a project, drop in the structured documents, and paste in a system prompt that says who the agent is and how it should answer. Something like: you are the onboarding buddy for a five person design studio, answer only from the attached documents, if the answer is not there say so and tell them to ask the founder, keep answers under 120 words. That last line matters. Long answers do not get read.
Option two: Notion AI or a Notion page with an embedded assistant. If your SOPs already live in Notion, this is the lowest friction path because the documents and the answers are in the same place. The contractor works in Notion and asks questions in Notion.
Option three: a Slack bot connected to your docs. Tools like Chatbase or CustomGPT let you upload documents and get a shareable link or a Slack integration in an afternoon. I like this for teams that already live in Slack, because the question gets asked where the work happens.
Whichever you pick, the setup is the same three steps. Collect the documents. Write the system prompt with the personality and the limits. Test it by asking the twenty questions a new contractor actually asks, and fix the answers that are wrong or vague.
That test round is the whole job. It takes an afternoon. If you skip it, you get an agent that confidently says something untrue, the contractor stops trusting it, and you are back to being the help desk.
What the Agent Should Handle and What It Should Never Touch
I want to be direct about this, because I have watched people hand too much to an AI agent and then act surprised when it goes badly.
The agent should handle: how do I structure a proposal, where do final files go, what is our revision policy, how do I log hours, what does a good kickoff call look like, what is the difference between a change order and a new project, and any version of can you remind me how we do this.
That is 90 percent of what a new contractor asks in month one. If your agent answers those well, you have removed almost all of the repetition.
It should never handle: pricing decisions, firing a client, hiring, anything about a specific person's performance, or a judgment call with real money attached. And it should always end with a clear handoff line when it does not know. Mine says: I do not have that one. Message Joe and he will get back to you by end of day.
That line is not a failure of the system. It is the system working. You want the agent to be honest about the edges, because a contractor who learns to trust the agent's confidence is worse off than one who asks you directly.
The Founder Part Nobody Wants to Hear
An AI onboarding buddy does not remove the need for you to write things down. It makes writing things down worth it.
For years I treated SOPs as a chore I did for other people. Now I treat them as the thing that lets me leave. Every hour I spend structuring how we do things is an hour I get back later, multiplied by every contractor who never has to ask me.
Start with the twenty questions. Write the answers. Put them in a project. Test it. Then hire your next contractor and watch them get onboarded without you.
That is as close to cloning yourself as this gets. And it is a lot cheaper than the alternative.
If this resonates and you want to build this kind of infrastructure in your own business, the Mastermind is where we do the work live. You can learn more at mastermindshq.business.