The question comes up in a board meeting, usually somewhere between the growth update and the CFO report. "What's our AI strategy?"
Every executive team in the mid-market is fielding some version of this right now. And the honest first reaction, for a lot of leaders, is a pause. Not because they don't know what AI is, but because the question sounds like it's about technology when it's actually about something harder to answer.
A board asking about AI readiness is not asking for a tool list. They're asking whether the company can adopt AI without breaking something, wasting money, or embarrassing itself.
That's a fair question. It's also one that most technology assessments never really address, because most assessments are run by someone who's already decided what the answer should be.
Readiness is not a feeling. It's a set of things that either exist or don't.
Four elements determine whether a company is ready to adopt AI in a way the board will be able to defend six months later. None of them are AI.
Data you'd put in front of an auditor. AI is only as useful as the data it draws on. If sales, finance, and operations each define "pipeline" differently, an AI model won't reconcile the disagreement. It will institutionalize it. Reports will look precise and won't hold up. Before any AI investment, one question matters: do we have one version of the numbers, or do we have three?
Processes worth automating. A broken process with AI applied to it is a faster broken process. If invoice approval takes fourteen days because it routes through five people who don't need to see it, automating that workflow just moves theproblem downstream at speed. Readiness work is often process work, done beforeany tool is selected.
Clear ownership. Someone has to own AI-touched output. Who approves it, who monitors it, who answers for it when the number turns out to be wrong. In most mid-market companies, that responsibility is undefined by default. That's fine until something goes wrong. Auditors are beginning to ask whether AI touched the numbers in a financial report. There should be a real answer.
Systems thatcan support it. Some current platforms are a foundation. Others are anobstacle. A general ledger with clean master data and consistent coding willsupport AI-driven analysis. A patchwork of aging systems held together withmanual reconciliation won't, and no amount of AI will paper over that. Knowingthe difference matters.
A real readiness assessment answers four questions with evidence, not with a feeling.
Where is the data actually clean, and where is it not. Which processes are stable enough to automate, and which need to be fixed first. Who currently owns AI-related decisions, and who should. Which existing systems will support the intended use cases, and which will need to change.
The output is adefensible recommendation and a sequence, not a shopping list. Sometimes therecommendation is to invest in a specific AI use case immediately. Sometimesit's to fix a data foundation first and revisit in six months. Both arelegitimate answers.
Every software company that sells an AI product will offer to assess your readiness for it. This is not dishonest. It's structural. The people whose compensation depends on you buying something are not the right people to tell you whether you need it.
The value of an independent assessment is that "you're not ready yet" is an available answer. So is "the tools you already have would work if configured correctly." Neither outcome generates a software commission, which is exactly why they should be on the table.
The right first move is not a pilot. It's an assessment: a structured evaluation of data, processes, ownership, and systems against what the company is actually trying to accomplish.
If the board isasking the question, the answer they want is not enthusiasm. It's discipline.Discipline is what turns AI from a line item into an advantage.