What to Tell Your CEO When They Ask About AI

At some point in the last year, someone above you said a version of: "We should be doing something with AI. Can you figure out what?"

It sounds like an opportunity, and it is — but it's also a trap. Come back with vague enthusiasm and you look unserious. Come back with a vendor's slide deck and you look like you outsourced your judgment. Come back with "here are the risks" and nothing else, and someone less careful ends up owning the initiative.

What actually earns credibility in that room is specificity. Here's a five-part structure for the answer — one you can build with information your company already has. The theme throughout: every claim is one of your own numbers. Numbers from your operation can't be argued with the way opinions and analyst quotes can.

1. Where we stand today

Start with the current footprint, honestly: which teams already use AI tools (officially or not), what's worked, what's stalled. Almost every company has quiet, unofficial AI use — surfacing it shows you did the diligence, and it usually contains a lead worth following: someone already found a use case worth formalizing.

One slide. You're establishing that this assessment starts from facts, not aspiration.

2. What our current workflows cost us

This is the section that separates your answer from every generic AI presentation your CEO has seen. Pick the three or four operational problems you already know about — quotes that take days, intake documents processed by hand, reporting assembled manually, follow-up that doesn't happen — and put an annual dollar figure on each, from your own operating data:

(hours per week × loaded cost × 52), or (opportunities delayed or lost × close rate × average value)

State your assumptions and round down. Conservative math survives the boardroom; optimistic math gets taken apart by whoever runs finance. A modest number nobody can argue with beats an impressive number someone dismantles in front of the CEO.

3. What I recommend we do first — and why this one

Present a ranked shortlist of two or three workflow fixes, drawn from the costs in section two. For each: the problem, the annual cost, the shape of the fix, and the metric that will prove it worked. Then commit to one.

Make the first one contained: a workflow where a rough first month is embarrassing at worst, not revenue-threatening — and say out loud that this is deliberate. "We start where the downside is small and the measurement is clean; the revenue-critical workflow is second, after we've proven the approach" is exactly the risk posture a board hopes someone in the room has.

4. How we'll know it worked

One slide, three numbers: the baseline today, the target, and the review date. That's the whole slide.

This is the part most AI initiatives skip, and it's why so many of them are still "being evaluated" two years later — nobody defined what success would look like, so nothing can fail or succeed. A stated baseline and a review date make your initiative falsifiable, which is precisely what makes it credible. You're not asking the board to believe in AI. You're asking for a small, measured test with a date on it.

5. The risks, stated plainly

Name the real ones and the mitigation for each: data leaving the building (which tools, under what terms, and what's off-limits), errors reaching customers (where humans stay in the loop, and that the first project deliberately isn't customer-critical), and compliance obligations specific to your industry. Skip the science-fiction risks; naming the mundane ones precisely is what signals you understand the operation.

Why this works

Notice what this structure never asks anyone to believe: no market statistics, no analyst projections, no claims about what AI will do to your industry. Five sections, and every load-bearing fact in them is internal — your footprint, your costs, your baseline, your risk posture. That's what "defensible" means in practice: the CEO can repeat any line of it to the board without you in the room, and it holds.

The work is in section two — the honest costing of your own workflows — because that's where the diligence lives and where most people have to guess. If you want that part done systematically rather than assembled by hand, that diagnostic is our product: the AI Readiness Audit walks through your operation in a guided 30-minute assessment and produces a written report — prioritized opportunities, each with a dollar figure built from your own baselines — that's designed to be presented upward. Several sections of the answer above come out of it ready to use.