TL;DR. AI is not a wave, a transformation, or an industry-disrupting force. It’s a small set of products, sold by a handful of serious vendors, on pricing terms that change every quarter, deployed to specific roles. Five decisions. You already know how to make all of them. The frame is the whole game.
You are getting AI handed to you in the wrong shape. A vendor wants forty-five minutes. A consultant wants a six-month engagement. A direct report forwarded a podcast. The board wants a strategy. Your CFO wants a number. None of these conversations get easier if you read another industry briefing. They get easier when you stop accepting the frame the briefing arrives in.
This guide is the frame. It’s what every other guide on this site assumes. It is short on purpose. If your mental model for AI is right, the rest of the work is just doing it.
How most executives misread this market
The picture you’re getting comes from three places: vendor sales motions, McKinsey-style strategy decks, and the tech-press coverage that lands in your LinkedIn feed. All three describe AI the same way. A wave. A transformation. A roadmap. Something happening to your industry that you must respond to.
This framing is not neutral. It is the framing that justifies a six-figure consulting engagement, a thirty-slide deck, and a quarterly steering committee. It makes you a passenger and the deck author the pilot. It is also wrong in a specific, costly way: it doesn’t help you decide whether to buy ChatGPT Business or Claude Team for your operations group on Monday.
The useful frame is operational. AI, as it touches your company, is a small set of software products. Made by a small number of serious vendors. Sold under pricing terms that changed last quarter and will change again next. Deployed to specific roles that get specific leverage. The interesting questions are: which product, which vendor, which tier, which roles, what to measure, what to restrict.
“What does AI mean for our industry” is not on that list. It is the wrong altitude. You don’t ask what email means for your industry. You ask who needs Outlook and who needs Gmail and how much you’re paying per seat.
The five decisions you own
Strip the deck off and there are five decisions that sit on your desk. Every other AI question your org will ask this year is downstream of one of them.
Vendor. Which of the four serious vendors — OpenAI, Anthropic, Google, Microsoft — does your org pay. Probably one or two. Not five. The decision is not “which model is best on benchmark X.” It is which vendor’s commercial terms, security posture, and integration story fit your stack. Vendors have business models. Read those, not the model release notes.
Tier. Which plan, at which price, with which data terms. The Team plan and the Enterprise plan from the same vendor are different products with different capabilities, different admin controls, and very different pricing per seat. The default for a mid-market org is almost always one tier cheaper than the vendor wants to sell you. Ignoring this is how budgets bloat.
Roles. Which jobs, on which teams, get a seat. Not everyone. Not “the whole company.” A correct deployment looks lopsided: heavy in roles where the leverage is real, absent in roles where it isn’t yet. The leverage is uneven. Your seat distribution should be too.
Measure. What you watch to know it’s working. Not seat activation. Not training hours. Not vendor-supplied “productivity uplift” charts. Observable changes in what your org ships, who ships it, and how fast. If your dashboard would look the same whether AI was working or not, you don’t have a dashboard.
Restrict. What you don’t allow. Customer PII into the consumer tier. Proprietary code into a free account. Auto-generated communications going out without a human name on them. The list is short and concrete. It fits on one page. The forty-page governance document is a defense mechanism, not a policy.
That’s it. Vendor, tier, roles, measure, restrict. Every guide on this site goes deep on one of these. If you can’t currently defend each of these five with a specific answer and a specific number, you don’t have an AI program. You have an AI line item.
What the frame gives you
A defensible budget. When the CFO asks why AI spend went up forty percent year over year, you don’t answer with “transformation.” You answer with “we moved twelve roles from the Team tier to the Enterprise tier because the data residency terms required it, and added eighteen seats in the operations group where the per-seat ROI is observable.” That sentence ends the conversation. The other one starts a steering committee.
A filter for vendor pitches. Every vendor meeting becomes a thirty-second exercise. Which of the five decisions is this pitch trying to change? Usually it’s tier — they want you on the more expensive plan. Sometimes it’s vendor — they want to displace your incumbent. Occasionally it’s roles — they want to expand the deployment. Once you know which decision is on the table, you know what to ask and what to ignore.
A way to evaluate any new model release in under a minute. The new model from Vendor X either changes one of your five decisions or it doesn’t. Most don’t. The ones that do are obvious: a price drop that changes your tier math, a capability that opens a new role, a data term that resolves a restriction. The rest is content for the engineering team to read on their own time.
A reason to stop saying “our AI strategy.” You will start saying “our Claude Team contract” and “our policy on customer data in third-party tools” and “the eight roles where we’ve seen real leverage.” This sounds smaller. It is. That’s the point.
What it costs you
You give up the comfort of the deck. There is no longer a forty-slide narrative about your AI journey. There is a contract, a policy page, a seat list, and a quarterly review of whether the seat list still makes sense.
You give up the consulting engagement. Or at least the strategic one. Implementation help on a specific decision — which tier, which roles — can be useful and cheap. The strategic engagement that produces the deck is a tax on not having a frame.
You give up the org chart with an AI Center of Excellence on it. Centers of Excellence are what organizations build when they’re trying to look like they have a strategy without committing to one. The five decisions live with the people who already make those kinds of decisions: procurement owns vendor and tier, line managers own roles, the CFO owns measure, legal and security own restrict. AI doesn’t need a new department. It needs the existing ones to do their jobs with one more product in the catalog.
The decision map
| Decision | Default for a mid-market org | Where to go deeper |
|---|---|---|
| Vendor | One primary (Anthropic or OpenAI), one secondary for redundancy | Choosing Tools |
| Tier | One step below what the vendor recommends | Choosing Tools, Evaluating Spend |
| Roles | Concentrated in operations, engineering, marketing, finance — not everywhere | Recognizing Leverage, Driving Adoption |
| Measure | Observable shipping changes by role; not seat activation | Measuring Returns |
| Restrict | One-page policy: customer data, proprietary IP, external comms | Building an AI Policy, Managing Risk |
Print that table. It is the entire executive view of AI on a single screen. Every meeting, every pitch, every budget question lands somewhere on it.
Monday morning
Pick the one decision on that table you can’t currently defend with a specific answer and a specific number. Read the guide it points to. Make the decision. The sequence the rest of your org runs on starts with you having a frame, not a strategy.
When the next vendor email arrives — and it will arrive this week — the first question is which of the five it’s trying to change. The second question is whether the change is justified. The third question is no longer “what is our AI strategy.” There isn’t one. There’s a contract, a policy, a seat list, and a measurement. That is the strategy. Stop apologizing for it being legible.