AI for CEOs: What to Do Yourself, What to Delegate, and What to Refuse (2026)

TL;DR: The CEO's Job With AI Is Not to Become the Best Prompter in the Building

A CEO should use AI on the six jobs only the CEO does, delegate the three that scale, refuse the three that don't reverse, and publish a one-page policy so everyone else can move. That's it. Not a transformation program. Not a Chief AI Officer search. Not a tool budget with a Slack channel. I've sat in enough leadership meetings in 2026 to know the pattern: the company has licenses, the all-hands had a demo, and the CEO has never personally used the thing on a real decision. The routine below is what I run for myself and install for the founders I work with. It takes about three hours a week and it is the highest-return three hours on your calendar.

The six things a CEO should personally do with AI every week

Open Claude or ChatGPT, in a project or workspace with your company context loaded — strategy doc, org chart, last quarter's numbers, your current priorities. Then, weekly:

1. Pre-read everything before the meeting. Board decks, investor updates, the exec team's status docs. Paste it in and ask: what's missing, what's inconsistent with last month, and what question would a skeptical board member ask first. You walk in having already had the argument.
2. Draft and stress-test strategy memos. Write the memo yourself, then ask the model to argue against it as your sharpest competitor, your CFO, and a customer who just churned. The memo that survives three attacks is the one you send.
3. Prepare for hard conversations. A performance issue, a co-founder disagreement, a customer escalation. Role-play it. Ask for the three ways the other person might hear what you're planning to say. This is the single use that CEOs tell me changed their week the most.
4. Read what the company is telling you. Support tickets, sales call notes, exit interviews, NPS comments. Dump a month of it in and ask for the five themes and the one thing nobody has escalated. Your team filters bad news on the way up; the model doesn't.
5. Write the first draft of anything with your name on it. The all-hands, the investor letter, the LinkedIn post, the customer apology. First draft only. The voice is yours to fix; the blank page is no longer your problem.
6. Interrogate your own numbers. Paste the dashboard export and ask what changed, what's correlated, and what you'd want to know before you'd bet on the trend. It's not a replacement for your finance lead. It's the question list you bring them.

Notice what's not on the list: coding, marketing automation, customer service bots. Those are real, and they're someone else's job. The CEO's AI use is judgment amplification, not throughput.

The three things to delegate

• Repeatable knowledge work with a clear template. Proposals, job descriptions, SOPs, meeting summaries, first-pass research. Give a function owner a budget and a target, not a mandate to "explore AI."
• Customer-facing automation. Intake, triage, FAQ handling, follow-up sequences. Owned by whoever owns the customer, with a human review gate until the error rate is measured, not assumed.
• Tool selection and integration. Which assistant, which connectors, which data it can see. That's a fractional CTO or an AI consultant job, and the CEO's only role is to approve the one-page policy it has to fit inside. If you're a smaller company, the Claude for small business setup guide is the version of this you can do in an afternoon.

The three things to refuse

• Irreversible decisions. Hiring, firing, pricing, fundraising terms, the big contract. AI produces the options and the arguments. It never chooses. The day you let a model pick the candidate is the day you can't explain the decision to anyone, including yourself.
• Speaking for you when the stakes are personal. The termination conversation, the board answer under pressure, the public statement in a crisis. Draft with it, sure. Deliver it yourself, in your words, or the room will know.
• The strategy itself. Models are extraordinary at synthesizing what everyone already believes. Strategy is the bet on what they don't. Use AI to find the consensus so you know exactly what you're deviating from.

Write the one-page AI policy this week

Every company I've walked into without a policy has one of two cultures: reckless use (customer data pasted into personal accounts) or no use (everyone assumes it's banned). Both are your fault, and the fix is one page with five sections:

1. Approved tools and accounts. Which assistants, on company accounts, with which data controls on.
2. Never-paste list. Customer PII, credentials, unreleased financials, anything under NDA, anything legal would wince at.
3. Human-review gates. What must be read by a person before it reaches a customer, a regulator, or the public.
4. Owners by function. One name per department who decides what AI does there. Not a committee.
5. How to ask for an exception. A form, a Slack message, a 24-hour answer. Permission, not restriction.

Sign it. Put your name at the top. The policy is the thing that turns "the CEO said AI is a priority" into something a mid-level manager can actually act on. AI for managers is the companion piece for the people who have to run it day to day.

Adoption vs. adoption theater: how to tell

Theater looks like this: a tool budget, a #ai-tips channel, a vendor demo at the all-hands, an "AI champion" in each department, and no metric that moved. Real adoption looks like shorter cycle times on named workflows, the same throughput with fewer hours, and people who can tell you, specifically, the three tasks they now do differently.

The fastest test I know takes ten minutes. Ask five people, individually, what they did with AI yesterday. If you get five specific answers, you have adoption. If you get "we're exploring it," you have licenses. As of 2026 most companies I meet are in the second group and reporting themselves as the first.

AI for founders: the 5-to-50-person version

If you're a founder-CEO of a company with five to fifty people, everything above applies and one thing changes: you don't have the functions to delegate to yet. You are the head of sales, the head of product, the head of people, and the finance department, in whatever order the week demands. That's exactly why AI matters more to a founder than to any Fortune 500 CEO. The jobs you do alone before you can afford to hire for them are the jobs a frontier model is best at drafting.

Here's what my founders' daily AI use actually looks like, as of 2026:

• Customer research: transcripts in, patterns out, before you write a line of product spec.
• Sales: call notes to follow-up email in two minutes, proposal from your last three winning ones.
• Product: the spec's first draft, the edge cases you didn't think of, the test plan.
• People: the job description, the scorecard, the interview questions that actually test for the thing.
• Finance: the model you'd otherwise build in a spreadsheet at midnight, with the assumptions listed so you can argue with them.
• Marketing: the first draft of everything, in your voice once you've loaded twenty of your own posts as examples.

The founder-specific rule is the inverse of the big-company one. A large-company CEO's risk is never touching the tool. A founder's risk is letting it touch everything. Keep your hands on two things personally: the customer conversations and the numbers. Let AI draft around them. The day you stop reading the support inbox because the model summarizes it, you've traded your best signal for a convenience. If you want the wider view of who owns what at this size, I wrote it up for AI for executives and, for the people-leadership side, AI for leaders.

What changes above 50 people

Past fifty, the CEO's personal AI use shifts from doing the work to modeling it. Your team copies what you visibly do. If they see you paste the board deck into Claude before the meeting and walk in with better questions, they will do it with their own decks. If they hear you talk about AI and never see you use it, they'll correctly conclude it's a talking point. At this size, the policy matters more, the function owners matter more, and the theater test matters most — because you're now far enough from the work that you'll be the last to know it isn't happening.

The micro-action for today

Take whatever's on your calendar tomorrow that you're least prepared for. Paste the relevant material into Claude or ChatGPT and ask for the three questions you'll wish you'd asked. That's the entire onboarding. If you want to know whether your company is ready for more than that, the AI readiness checklist takes ten minutes and tells you which of the five policy sections you're missing. And if you'd rather talk it through, the 30-minute strategy call is free and has no pitch in it — most CEOs use it to figure out whether the problem is the tools or the org.