Questions I get before the first conversation
The questions I get before the first conversation. If yours isn’t here, ask it in a note.
“We tried AI and it was useless.”
You tried a reader before giving it a readable business. A generic model knows how to read. It doesn’t know your company’s authority structure, so it guesses, and it guesses confidently. Make the business legible first and the same model stops guessing.
“Can’t I just do this myself with ChatGPT?”
You can, and your subscription won’t tell you which of three conflicting documents governs. Someone has to make the business legible first. Use ChatGPT, use Claude, use Copilot, use whatever ships next and I’ll work inside whichever one your team already runs. I’m not selling you the reader. I’m making sure your business is readable.
“Our files are too messy.”
That’s the problem I fix, and it’s why I start with the business, not the AI. I don’t expect clean files before we start. The mess is there for a reason.
“We can’t take on a transformation project right now.”
This isn’t one. Nothing stops, nothing migrates, and the audit asks a few hours of your people’s time in conversations, not a committee. You keep operating while it happens.
“I don’t trust it with our files.”
The system lives in your folders, on your machines, and a person can read every part of it with no AI in the room. You log into whatever AI you already pay for, and that’s the only login involved. No subscription of mine, no seat count, no account that stops working if I do.
“It’s expensive. I can’t see the ROI.”
You’re not comparing this to a chatbot subscription. You’re buying operational infrastructure that removes key-person dependency and gives you one governed source of truth. The number to weigh it against is what the data problem already costs you in wasted time, lost revenue, and answers nobody can trust, not the price of a model you already have.
“What do I actually walk away with?”
From the audit, an operating map: how the work runs today, how it would run rebuilt, which workflow is worth doing first, what a system should and shouldn’t do, and what it’s worth in hours and risk. The map comes as a PDF built from what we talk through in the audit and it opens with the quickest win before it gets into the detail. From the build, an Operational Knowledge System: your documents organized and marked for what governs, the unwritten knowledge captured while your experienced people are still in the building, rules for when AI answers and when a person decides, and answers that cite their sources.
“How long does it take?”
The audit takes one hour of your time, and the report is in your inbox within 48 hours. When your information flows, the first working system is live inside 30 days. When it’s hard to reach, it takes longer, and I tell you which in the audit rather than after.
“What happens after it’s built?”
There’s ongoing work if you want it, keeping the system tended as the business changes, because a structure nobody maintains grows back into a mess. But the test is that it shrinks.