Every CIO and CTO I talk to is living the same paradox. The board wants an AI strategy. Vendors promise transformation in a slide deck. And somewhere in the building, a dozen disconnected pilots are quietly dying — not from bad models, but from bad approach.
Here’s the uncomfortable truth: most enterprises don’t have an AI problem. They have an approach problem. The technology works. What’s missing is executive discipline — the same discipline you’d apply to any major capital bet.
This is a field guide for that discipline.
1. Start with the P&L, not the model
No AI initiative should exist without a named business outcome and a rough ROI thesis written in plain language. Not “leverage LLMs for synergy” — but “cut claims processing time by 40%” or “resolve tier-1 support tickets without human touch.”
If you can’t write the outcome on a whiteboard, you don’t have a strategy. You have a science project. Fund accordingly — which is to say, barely.
The question to ask of every proposal: where does AI earn its keep here? If nobody can answer with a number, the answer is “nowhere yet.”
2. Your data estate is the real project
Here’s what the demos never show: the AI was the easy part. The hard part was the twenty years of data underneath it — fragmented across systems, inconsistently defined, with lineage nobody can trace.
Most AI failures are data failures wearing an AI costume. Before you approve a single model evaluation, demand a data readiness verdict: is our data fit for machine consumption — quality, completeness, freshness, access, lineage? If the answer is no, your AI budget is actually a data modernization budget. Say so out loud. Boards respect honesty more than hype.
3. Escape pilot purgatory
The enterprise AI graveyard is full of pilots that proved the technology and changed nothing. The pattern is always the same: too many pilots, too thin, no path to production, no owner with P&L responsibility.
The fix is concentration, not experimentation:
- Pick two or three workflows where AI moves a real number. Not ten. Two or three.
- Fund them like products, not experiments. A product has an owner, a roadmap, and a production date. An experiment has a demo day.
- Define the production gate up front. What eval score, what cost per transaction, what error rate earns the right to scale? Write it down before the pilot starts, when everyone’s still honest.
One workflow in production beats ten pilots in a slide deck. Every time.
4. Demand governance that accelerates
Many executives treat governance as the thing that happens after the engineers finish — a review board, a checklist, a six-week delay. Then they’re surprised when teams route around it.
Flip it. The governance that works in the AI era ships with the system: eval harnesses that catch regressions automatically, guardrails as code, human-in-the-loop checkpoints placed where the cost of error is highest. Frameworks like the NIST AI Risk Management Framework give you the structure — Govern, Map, Measure, Manage — but the principle is simpler: if your governance slows shipping without reducing risk, it’s theater.
Ask your teams one question: “Show me the guardrail.” If it’s a document, you have a problem. If it’s running in the pipeline, you have governance.
5. Know your unit economics
AI has a cost structure executives aren’t used to: it scales with usage, not with seats. A support agent that costs pennies per ticket at pilot scale can cost a fortune at enterprise volume — token spend compounds silently in multi-step workflows.
Before scaling anything, demand the unit cost: what does one transaction cost us, fully loaded? Cost per resolved ticket. Cost per processed document. Cost per generated report. Then ask what happens to that number at 10x volume.
If nobody knows the unit economics, you’re not running an AI strategy. You’re running an experiment with the company’s money.
6. Run hub-and-spoke, not chaos or centralization
Two operating models fail predictably. Pure centralization creates a bottleneck — one AI team, a hundred requests, everything waits. Pure decentralization creates chaos — fifteen teams buying fifteen tools, no shared learning, no leverage.
What works is hub-and-spoke: a central platform team owns the foundations (data pipelines, eval harnesses, model access, guardrails, cost monitoring), and embedded teams in the business units own the use cases. The hub provides leverage. The spokes provide proximity to the actual problem.
Your job as the executive: protect the hub’s mandate and hold the spokes accountable for outcomes, not activity.
7. Hire for the bottleneck, not the hype
You don’t need an army of prompt engineers. The roles that actually unblock enterprise AI are far less glamorous:
- Data engineers who can make the estate AI-ready — because that’s the real project (see #2).
- Evaluators who can tell you whether the system is getting better or worse — because without evals, you’re flying blind.
- Product-minded engineers who think in workflows and outcomes, not demos.
If your hiring plan says “AI experts” without naming these three, rewrite it.
8. Measure like an executive, not a researcher
Benchmark scores don’t pay bills. Hold your AI portfolio to decision-grade metrics:
- Outcome metrics: the business number it was supposed to move. Did it move?
- Quality metrics: eval scores, error rates, escalation rates — trending which direction?
- Economic metrics: unit cost per transaction, and its trajectory at scale.
- Risk metrics: incidents, bias findings, data exposure events. Zero surprises is the target.
Review these the way you’d review any business unit. AI doesn’t get a grace period from accountability — that’s exactly how pilot purgatory starts.
9. Interrogate your vendors
Every vendor will tell you their AI is enterprise-ready. Few can prove it. Before you sign, demand answers:
- Show me your eval methodology — not your benchmark scores, your methodology.
- Where does our data go? Who can see it? How do we get it back?
- What happens to our unit cost at 10x volume?
- What’s our exit strategy if this doesn’t work?
The vendors worth partnering with answer these crisply. The rest are selling slides.
The one question
Strip away the frameworks and the org charts, and the executive’s job on AI comes down to a single discipline: keep asking where does AI earn its keep here — and fund only the answers backed by evidence.
Start with the P&L. Fix the data. Concentrate your bets. Govern at the speed of shipping. Know your unit costs. Measure like it matters — because it does.
The enterprises that win the AI era won’t be the ones that experimented the most. They’ll be the ones that approached it with the most discipline.
For the practitioner’s companion to this guide — the full method with principles, delivery phases, and reference architectures — see The Agentic Architecture Framework. Jugal Shah writes about production AI, agentic systems, and enterprise data architecture at aideeva.com, where he publishes The Agentic Enterprise newsletter.
