Business · Artificial intelligence
How to Know If Your Business Is Ready for AI
· 4 min read ·
"Are we ready to use artificial intelligence?" usually gets answered with a list of systems and a budget calculation. Those are the wrong answers, because the question isn't about technology.
Artificial intelligence does one thing: it finds patterns in what's already happened and uses them to suggest what to do next. If your operation has no patterns — because every case is handled its own way and the information changes depending on who writes it down — there's nothing to find.
Finding out whether you have patterns doesn't take an audit. It takes watching an ordinary week and noticing four things.
Notice what happens before Monday's meeting
Someone prepares the numbers. The question is how long it takes, and what they're doing during that time.
If they open a report and print it, that's a good sign: the information is ready to use. If they export three files, paste them into a fourth, correct two lines they know are wrong, and only then print it, what they have in front of them isn't a report — it's a weekly hand-built reconstruction that exists because no single system knows the answer.
An AI connected to those systems would pull the same wrong data, without the correction that person makes from memory.
Notice who people ask
During the week, when someone needs to know the state of a process, what do they do? Check the system, or get up and ask a colleague?
Asking a colleague is faster, and there's nothing wrong with it now and then. When it's the habit, it's saying one of two things: that the system doesn't have the answer, or that it does but nobody trusts it. Either way, the real knowledge about the operation lives in people, not in the records — and it's the records AI will search.
Notice what counts as an exception
Pick a process and track ten cases. How many followed the normal path from start to finish?
If eight or nine did, you have a process. If it was three, you don't: you have ten ways of doing the same thing, and the "normal path" is a fiction that only exists in the manual.
This matters because a system trained on those ten cases will learn the inconsistency. It will suggest, with total confidence, what to do next — and the suggestion will be right some of the time and wrong the rest, with no way of telling why. It's the fastest way to get teams to stop using the tool.
Notice what never gets written down
There are decisions made every day that nobody has ever written down: which customers get extended deadlines, which orders jump the queue, when the deposit gets waived.
Whoever's been there ten years knows it by heart. Whoever joined three months ago asks. AI can do neither: it only knows what's on record.
Writing those rules down is usually the most tedious and most useful part of getting ready. And it has a pleasant side effect: half of them, seen in the light of day, no longer make any sense at all.
What to do with what you've noticed
If all four observations came back badly, the conclusion isn't "don't proceed". It's to proceed differently: pick a small area where the foundations are already reasonable and start there, instead of trying to straighten out the whole company.
If they came back well, you're probably more ready than you thought, and all that's left is choosing the first case and measuring it.
Either way, the work ahead is the same as ever: tidying up where the data comes from, connecting systems that don't talk to each other, and writing down what only exists in someone's head. It's what we do in advice and delivery and in CRM and integrations.
Want an outside view?
Tell us what an ordinary week looks like in your business and what systems support it. We'll tell you where the foundations are solid and where they aren't.