Ian Titus
Notes

How do I get what’s in my head written down so my business stops running through me?

You get it out of your head by talking it through instead of writing it. Pick the job that would hurt most if you were gone a month, walk through it on a recorded call while someone asks why, let AI turn the transcript into a draft, and correct it. Then file it where your team and your AI look.

There’s more in there than it feels like. The Systems Effect reviewed 16 small businesses it worked with and found half of all role areas had nothing written down at all, and its interviews turned up a median of 159 questions per business that only someone’s memory could answer.

That’s a firm that sells documentation looking at its own clients, so read the numbers as a direction and not a census. Still, nobody gets 159 answers out of their head in a month, which is why this starts with one job.

I’m Ian Titus and this is the work I do for companies of 10 to 150 people in Franklin, Tennessee and around Nashville. If you’d rather start with your own situation, the free assessment takes about 15 minutes and I’ll reply in writing.

What it looks like when it works

It looks like a conversation you were going to have anyway turning into a file your team can use, and that file staying current without anyone sitting down to update it. I’ve built the first half for a coach’s client calls and shown the second half on a fictional property company’s drive.

The smallest version is the System Starter, built for a business coach who runs client calls. After each call he drops the transcript in a folder and says two words, and that client’s record updates itself. Before the next call he gets a one-page brief with where things were left.

He installed it from two files and runs it on his real roster, and I haven’t changed anything since. Nobody writes a summary after a call, because the transcript already holds what was said and the system files it.

The other half is what knowledge does once it’s in the files. On a property drive I built to show the method, the lease renewal dates lived in one person’s head, so a renewal option lapses the week that person takes vacation. It’s a fictional company and the case study says so.

Once the dates were in the files, the system surfaced three renewal notice deadlines inside ninety days without anyone asking. It also caught that the written renewal process was dead. The procedure called for notice at 120 days and a tracking log in a Renewals folder, and neither existed anywhere in the drive, so the real process lived in one person’s head.

How to get what’s in your head written down

Start with one job, talk it through on a recording while someone asks why, let AI draft it, correct the draft, and file it where people look. Then hand it to your newest person to find what’s missing. It’s six steps, and the part that needs you most is one conversation.

1. Pick the job that would hurt most if you were gone a month

For a week, keep a tally of the questions that come to you, the way the first note in this series lays out. Then pick the one job behind them where a wrong answer costs money. In most companies that’s pricing, scheduling or anything with a deadline attached.

One job is the right size. If the 159 figure is anywhere close for your business, trying to capture everything at once is how the binder ends up half-finished on a shelf.

2. Talk it through on a recording while someone asks why

Walk through the job out loud while someone asks why at each step. The guide at whatstheprocessfor puts a good interview at 30 to 45 minutes, done as if you’re explaining it to a new hire, and that’s about right for one job.

It doesn’t have to be a sit-down interview. When I’m talking with someone to understand a problem, I record that conversation and use the transcript as the starting point. Record the real work when you can, a quote you’re pricing or a screen you’re clicking through, because the written process and the real one drift apart.

Then record the person who does the job too. When I sit down with an owner, I get the owner’s version of how the work should be done and to what standard. Then I sit with the person doing the work, and there might be some conflict with what the owner said. I may miss it and the owner may miss it, but the AI captures all of it, so once both transcripts are drafted everyone can see the discrepancy laid out in front of them.

The person asking can be an AI. If someone who has done this kind of work writes the questions first, you can drop them into whatever AI you use and let it interview you with nobody else on the call. When I set something up, I’d rather have done the work first and have the questions loaded, and that’s been an effective way to get the same information out.

Talking is faster than typing for most people, and the ums don’t matter because the AI filters them out. Where you talk does matter. A crowded coffee shop or a cubicle with people working around you makes it harder, so find a door you can close.

3. Let AI draft it, and tell it to list what it couldn’t find

Hand the transcript to the AI you already pay for and ask for the steps, the rules, the exceptions and a separate list of questions the transcript doesn’t answer. That last list matters most. Left alone, a model fills the silence in a transcript with steps that sound right, and you won’t be able to tell its guesses from your words.

It’s the same rule I hold every system to, that if there’s no source you don’t get an answer, applied to a draft. Use a business account for this. A transcript of how you price is exactly the kind of thing you don’t want training anyone’s model.

4. Correct the draft

Read it and fix it, out loud on a second short recording if that’s easier. The corrections are the knowledge. A draft might say to quote the standard rate, and you’ll say unless it’s a repeat customer or the job is over an hour away, and that exception is the part your team could never have guessed.

Answer the open questions in the same pass, and settle every place where your version and your employee’s version disagree, because that’s usually where the exception is hiding. Anything you can’t answer with a rule is a judgment call, and those go on their own list (more on that below).

5. File it where your team and your AI look, and say which version governs

Put it in the folder where the job’s other files live, as plain text a person can read without any AI. If an older procedure covers the same job, mark it superseded and move it to a folder nothing cites. Don’t delete it, because deleting is how you lose the one copy that mattered.

Then add one line to the folder’s index saying this file governs. Otherwise your team and the AI find both versions and go with whichever turns up first.

6. Hand it to your newest person

Have the newest person do the job from the file without asking you anything. Every question they still have to ask is a gap, so fix the file and run it again. Cogent Analytics’ guide uses the same test, and it’s the right one, because the newest person is the one who can’t fill gaps from memory.

If you’d like someone to find which jobs to start with, that’s the audit. It’s about an hour of your time, in person in Franklin or by video, $1,250, and the operating map is in your inbox within 48 hours. The first step is the free assessment.

Why writing your own SOPs never gets finished

Writing them takes time an owner doesn’t have, and the usual advice assumes you’ll find it. Most guides ask the person who knows the job to sit down and write it, which puts the busiest person in the company on the slowest version of the work.

ScreenSteps’ guide from 2019 is a fair example of the standard advice. It asks the expert to spend a few hours a week listing task names, then build a habit of capturing screenshots while doing each task. That works for someone who has the hours, and the owner whose business runs through him is the one person who doesn’t.

The results show it. The Systems Effect rated only 22% of the role areas it reviewed as solid, meaning a new hire could follow what was written. Another 30% had something partial or out of date.

Talking it out changes who does the slow part. You spend one conversation, the AI does the first draft, and your time goes into correcting it, which is the part only you can do.

Can AI write SOPs from a recording or a transcript?

Yes, and it does a good first draft in minutes. What it won’t do on its own is tell you what the transcript left out, so you have to ask for that list and then answer it. The draft is where you start, and your corrections are what make it true.

Most owners already have the tool. Intuit’s own 2026 survey found 77% of the US small and midsize businesses it asked use AI regularly, up from 48% in July 2024. It’s a vendor’s own survey, so read it that way.

BlitzMetrics’ Brain to Bot guide is the fullest version of the record-and-transcribe approach I found. It gathers call recordings and transcripts into one folder, has AI write the procedures from them, then moves on to agents that run the work.

I’d stop sooner. An agent running on a draft nobody corrected does the wrong thing faster, so the draft gets corrected and tested on a person before anything acts on it.

Two habits keep it safe. Tell the people on the call you’re recording, and run the transcript through a business account, because on personal plans conversations can be used to train the model unless someone has turned that setting off.

What should stay in your head

Your judgment stays. Facts and lookups belong in files, like how you price, who you call and what happens when a job runs over. Whether to make an exception this time stays with you, and the system’s job is to send that question to you instead of guessing.

Most guides treat everything you know as something to document. The useful split is between answers that come out the same every time and decisions that depend on the day. On my own list of what I build, the first kind is how you price, who you call and what happens when X.

Judgment calls get written down too, as a line that says this one comes to you. That’s still a file, and it’s what lets your team tell a lookup from a decision without asking.

On the property drive, asked who pays for HVAC at one property, the system quoted both lease clauses, explained why neither clearly governs and named who has to decide. As the first note in this series puts it, the point is to take you out of lookups. The decisions can stay yours.

How do I capture what my experienced employees know before they leave?

The same way, with them doing the talking. At 10 to 150 people it’s rarely a whole department. It’s the office manager who knows which vendors to double-check or the estimator who knows what a job really costs, so record them doing the work, let AI draft it and have them correct it.

Start with the person whose week off causes the most trouble. That’s the Harpeth Bend problem, where the renewal dates lived with one person and a renewal option lapses the week that person takes vacation.

Be straight with them about why. You’re writing down what they know so the company runs when they’re out, and so they stop getting interrupted for things a file could answer.

Do it while they’re here. Once someone gives notice you get a two-week scramble, and once they’re gone you get nothing.

Writing it yourself, recording your screen, or talking it out

For most owners, talk it out and let AI draft it, because it costs the least of your time. Screen recordings are right for software steps, shadowing fits work that’s physical, and writing it yourself is right when you already have the hours.

Write it yourselfRecord your screenHave someone shadow youTalk it out and let AI draft
Your timeHours per job, spread over weeksDoing the task onceDoing the job, plus their questionsOne conversation, then correcting the draft
What it capturesWhat you remember to writeEvery clickWhat they see you doWhat you say, including the exceptions when someone asks why
What it missesSteps you do without thinkingThe reasons behind the clicksWhatever didn’t come up that dayWhatever the transcript leaves out, which the AI lists as questions
How it stays currentSomeone rewrites itRecord it againShadow againThe next recording corrects it
What an AI can do with itRead itRead the narration, if there is oneRead their notesRead it, and draft from the next recording

The methods come from the guides themselves. ScreenSteps and whatstheprocessfor cover writing it yourself and screen recordings, and Permanent Equity’s guide pairs experienced people with newer ones through shadowing and names Loom for video.

I’m biased toward the last column because it’s how I work. The honest tradeoff is that it depends on the correction step, because an uncorrected AI draft reads like the truth whether it is or not.

The columns mix fine. Record the screen for the software part, talk through the judgment part, and keep both in the same folder.

Can my business run without me?

Not while the answers live only in your head, and that matters long before you think about selling. A two-week vacation or a second location tests the same thing a buyer would, which is whether the business works when you’re not in the room.

Selling may be closer than you’re planning for. Chase surveyed about 1,000 small business owners in March 2026 and found 40% plan to retire within the next decade, 70% are in early-stage planning or have no formal succession plan, and 8% say they’re fully prepared to transition ownership.

Whoever takes over, a buyer or someone in your own family, inherits what’s written down. Everything else leaves with you.

Who this works for, and who doesn’t need it yet

This works for companies of 10 to 150 people where the knowledge sits with the owner and two or three experienced people. Owner-run trades and home services, professional services firms, and property and real estate companies are the usual fit.

If you’re a coach or a solo operator with a client roster, start with the free System Starter. It turns your call transcripts into client records that stay current, which is the same idea at the size of one person.

If you have about five people, you can run the six steps above yourself with the AI you already pay for. Pick one job this week.

If the knowledge is spread across several people and years of files, that’s what the audit maps. And if you’re well past 150 people with your own AI team, you probably want a firm with a bench, because I’m one person and there’s no bench behind me.

Questions owners ask

How long does it take to get one job out of my head?

One conversation and one sitting to correct the draft. The guide at whatstheprocessfor puts a good interview at 30 to 45 minutes, done as if you're explaining the job to a new hire, and that's about right for one job. Correcting the AI's draft and answering the questions it couldn't settle is a second, shorter pass.

The test takes longer. Your newest person does the job from the file, and every question they still have to ask you becomes a fix. How many rounds that takes depends on how many exceptions the job carries, so a job you do the same way every time comes out faster than one where you make a call on every customer.

Can AI interview me instead of a person?

Yes. It doesn't have to be a person on the call. If someone who has done this kind of work writes the questions first, you can drop them into whatever AI you use and it will walk you through them, ask for the why and keep your answers as the transcript, with nobody else needed.

The questions are what make it work. When I set something up, I'd rather have done the work first and have the questions loaded before anyone starts talking, and that's been an effective way to get the same information out without booking a call. Recording a real conversation about a real problem works too, and that's usually where I start when I'm trying to understand how someone's work runs.

What should I use to record and transcribe?

Use whatever your meetings already run on. If it can give you a transcript, that's all the AI needs, and a phone recording works for a walkthrough on a job site as long as you can get the text out of it. The System Starter on this site reads Fathom transcripts, but any transcript the AI can read will do.

Pick the room as carefully as the tool. Talking is faster than typing for most people, and the ums and false starts don't matter because the AI filters them out. A crowded coffee shop or a cubicle with people working around you makes it harder to talk freely, so find a door you can close.

Is it safe to give call recordings to AI?

It can be, with two habits. Tell the people on the call you're recording, and run the transcript through a business account whose published terms say your data isn't used to train the model. On personal plans, conversations can be used for training unless someone has turned that setting off.

A transcript of how you price a job is exactly the kind of thing to keep inside the company. The files it turns into stay in your own folders, and you choose which AI company reads them, so nothing about the method ties your knowledge to one vendor. Which accounts train on what, and how to switch it off, is in [Is it safe to put my business information into ChatGPT?](/notes/is-it-safe-to-put-business-information-into-chatgpt)

What if I'm not good at explaining things?

Then do the job and let someone ask why as you go. Record yourself pricing a real quote or clicking through a real order, and the steps come out in the order you actually do them, with the exceptions showing up when the work hits one.

You don't need to sound polished either. The AI drafts from whatever you say, false starts included, and the draft is something you correct, which is easier for most people than explaining from a blank page. Recording a real conversation about a real problem works for the same reason, because the problem asks the questions for you.

Do I have to document everything?

No, and trying to is how it stalls. The Systems Effect's interviews across 16 small businesses turned up a median of 159 questions per business that only someone's memory could answer. Nobody gets through that in a month, and you don't need to.

Start with the job that would hurt most if you were gone for a month, then the next one. Each job you capture is a set of questions that stops coming to you, and the order you go in should follow the interruptions, which a week of keeping a tally will show you.

What's the difference between an SOP and a knowledge base?

An SOP is the steps for one job. A knowledge base is the facts and rulings those steps depend on, like current prices, which vendor to call for what, and which version of a contract counts. You want both, and to an AI they're the same thing, files it can read.

What matters more than the label is that every topic has one file that governs and the older versions are marked instead of deleted. Otherwise your team and the AI find two answers and pick whichever turns up first, and neither of them can tell you why.

Will my team actually use it?

They will if it's where they already look and it's right the first time they check it. That's the reason the last step is handing it to your newest person. A file that's wrong when someone finally opens it sends them straight back to your desk.

You can help it along. When someone asks you a question the file answers, point them to the file, and when the file doesn't answer it, fix the file before you answer. Keep that up for a few weeks and the questions that reach you start to be the ones that should.

How do I keep it up to date?

Let the work update it. When a job changes, record the next conversation about it and correct the file from the transcript, so nobody ever has to run a documentation project. That's how the System Starter handles a coach's client records, where each call's transcript updates the record without anyone writing a summary.

Put dates in filenames and mark old versions stale instead of deleting them. A file called current that has been wrong for three months does more damage than a missing one, because nobody goes looking for a problem in a file whose name says it's fine.

What if what I say contradicts what's written down?

If you're the one who decides, what you say wins, and the old file gets marked superseded and moved where nothing cites it. Nothing gets deleted, because deleting is how you lose the one copy that turns out to matter.

Contradictions are common because the written process and the real one drift apart. On the property drive I built to show the method, the written renewal procedure called for notice at 120 days and a tracking log in a Renewals folder, and neither existed anywhere in the drive. The work had moved on and the document hadn't.

Sources

Start with the free assessment

The fastest way to find out whether any of this fits is the free assessment. It takes about 15 minutes, in writing or on a call, and I’ll tell you plainly if the audit isn’t worth it for you.

Next

Tell me what you’re dealing with.

You don’t have to take a meeting to find out if I can help. Send a note about where your company’s knowledge gets stuck, and I’ll tell you what I see and whether I think I’m the right fit. If you’re a one-person shop and all the knowledge is yours, you don’t need this yet, come back when you’re hiring.

Tell me what you’re dealing with Questions? Read the FAQ →

Tell me what you’re dealing with

This is the free assessment. A few quick questions so I understand your situation, then I reply in writing with what I see and whether the audit is worth it for you. No meeting required, and I read these myself.

Would you rather I reply in writing, or set up a short call?