Ask an owner how an order moves through the company and you will get the org chart. Ask the person who has run dispatch for eleven years and you will get the truth.
The truth has exceptions in it. Which customers get called back the same day. Which estimate needs a second set of eyes before it goes out. What “done” means on a job that came in through a referral versus one that came in cold. None of it is written down. All of it is how the company actually works.
We call that the operating story. Every business has one. It is the part of the company that is not in the software and not in the handbook, and it is the part that makes the place run.
Why the machine never gets it
Most companies your size have already bought the licenses. Somebody has a prompt they show people. And the honest result, a year in, is a few faster emails and a lot of tools nobody opens twice.
That is not a failure of the technology. It is a failure of what the technology was given. The machine was handed the org chart and the handbook, which is to say the version of the company that exists on paper. It was never handed the story. So it does exactly what a new hire does on day two when nobody has explained anything: it produces confident, generic work that has to be redone.
A new hire fixes this by asking questions for six months. The machine cannot. Somebody has to get the story out of people’s heads and into a form it can use.
What extracting it looks like
It is less glamorous than it sounds. We sit with the people who actually do the work. We watch a week of it. We write down the decisions they make without noticing they are making them, and we write them the way they would say them, not the way a vendor would.
Three things come out the other side:
- The picture. How the work really moves, on one page, in your language. Most owners have never seen this. It is worth having even if you stop here.
- The decision rules. The exceptions and judgment calls, written down as rules the machine can follow and your people can correct.
- The wiring. Which piece of the work goes to the machine first, how your own knowledge gets to it, and how the workflow holds when someone is out sick.
The first piece is small. One workflow, one team, provable inside a quarter. Big rollouts are how this fails, and we would rather show you a small thing that works than sell you a large thing that might.
The part nobody tells you
Once the story is written down, it keeps paying whether or not you use AI at all. Training gets shorter. The person who has run dispatch for eleven years can take a vacation. When a good employee leaves, the way they did the job stays.
That is why we think of it as the product. The machine is a way to put the story to work. The story is the thing you own.