Before You Hire the AI Team, Run the Readiness Test

An AI readiness test checks whether a process can run without you before you hand it to AI. An AI employee follows what’s written and fills in the rest with confident guesses, so a process that lives only in your head produces gaps nobody sees until a client does. Run the test first. Hire second.

What does an AI employee inherit from you?

Only what’s written. It takes the process exactly as it exists on the page. The exceptions you handle by instinct and the judgment call you make in a blink stay behind, because you have never once explained them to anyone.

I found that out when I opened my inbox and saw two emails sitting side by side. The first was from a client telling me her deadline had moved and we needed to push the project back. The second was from my AI employee, sent an hour later, telling her to prepare for the next phase. Of course it did. I had taught it the process. The part where I know when to stop following the process lived in my head, and I call that kind of knowledge a Hostage File.

Why does the AI readiness test come before the hire?

AI is an amplifier. I treat it like any new team member, which means it gets a trained process, a clear standard, and feedback. A job title delivers none of those.

Give an amplifier a clean signal and it makes the signal louder. Give it noise and it does the same, at speed, around the clock. Hand it a process with gaps and you get the gaps, delivered promptly and beautifully formatted. Finding the gap on paper costs you an afternoon. Letting a client find it costs you a conversation you’d rather not have.

Org charts full of AI employees are everywhere right now, a named role for every function, each with a tidy little icon. They photograph well. Nobody photographs the process underneath, which is where the team either holds or quietly doesn’t. A team is only as ready as the processes it’s handed.

How do you run an AI readiness test on your own business?

Pick one task you want AI to take. Start with one where a mistake stays inside your walls, like internal notes, before you try one that reaches a client. Then ask three questions.

1. Could someone follow it without asking you anything? Write the steps for a stranger. Every place you’d say “it depends” is a place the process still lives in your head. “It depends” sounds like flexibility. It is a Hostage File in a good outfit.
2. Can you describe what a correct result looks like? If you can’t say what done well means, the AI employee will guess, and so will everyone who reviews its work.
3. What happens when it goes wrong, and who finds out? A process ready for AI has a trigger that signals trouble, a threshold for how much is too much, and a fallback for when it fails.

Three yeses mean the process is ready to leave your head. Anything less means not yet, and not yet is a perfectly workable answer. AI can draft while you review every output, until the process is written down.

What if your AI readiness test says not yet?

Then the test is doing its job. A business built on the founder’s expertise, which is the kind I work with, carries a great deal of knowledge that was never written down. Every not yet is a Hostage File with an address. Each one also marks where the Touch Tax gets collected: the time and attention your business charges every time work has to pass through you to move.

Read the results that way and they become a starting order. You know where to begin, and each hiring decision after that gets easier.

AI will carry whatever you hand it. Hand it something ready.

Where do you start?

The Profit Leak Scorecard is free, and it works in the same spirit as the AI readiness test. It shows where your business still runs on you instead of through you, where the Touch Tax is bleeding your time, which workflows are one departure away from collapse, and whether you’re facing an architecture problem or a gap problem.

---

It’s Handled™ | Operational architecture for founders who built the business, and are ready to stop being the infrastructure.