Article

For Restaurant Operators

AI Strategy for Restaurant CFOs: The Missing Half

A restaurant CFO's read on why most AI strategy advice stops halfway — what the missing half is, why it's the CFO's call, and what changes when you treat AI agents like new employees.

Quick Answer: Every AI strategy pitch you've heard stops at the same place — connect your POS, connect your labor, layer an AI tool on top, get faster answers. That's half the job. The other half is the unstructured stuff your operators actually run on: the playbooks, the weekly emails, the daily manager logs, the GM notes, the institutional knowledge nobody has ever written down. Feed an AI agent only the structured data and you get a faster analyst. Feed it both halves and you get something that does the work humans do today.

What every advisor sells you

Walk into any restaurant industry conference this year and you'll hear the same playbook five times before lunch:

1. Audit your data. POS, labor, inventory, guest feedback, delivery.
2. Get it into one place — warehouse, platform, dashboard, whatever.
3. Layer AI on top so non-technical folks can ask questions.
4. Watch analyst workload drop and insight velocity climb.
5. Report savings to the board.

True, true, true, true, true. And every operator in your category is hearing the same five steps right now. So when you implement it, you've matched the field. You haven't changed the game.

Think of agents as employees

You keep hearing the word "agents." Every vendor deck. Every AI strategy webinar. Sooo abstract. Sooo hand-wavy. Half the time you nod along, half the time you wonder if anyone in the room actually knows what they're talking about.

Here's the frame that makes it real. Stop thinking of an agent as a piece of software. Start thinking of it as an employee. One that doesn't sleep, doesn't take vacation, and never asks for a raise. But still — an employee.

The moment you do that, AI stops being abstract.

Because you know how to onboard an employee. You've done it a thousand times.

Think about Day 1 with a new hire. You don't sit them down and say "build me a spreadsheet for this huge project, due Friday." That'd be insane. You'd never do it. Day 1 you onboard them.

You have them read your core values. You introduce them to the department leaders. You walk them around, show them where the files live, who to ask about what. You explain the company vision. The quarterly objectives. The KPIs your team is on the hook for. The history. The wins, the losses, the things that worked and the things that didn't.

Two weeks in, they start doing actual work. Three months in, if they're good, they're fully productive.

Three months. That's how long it takes a smart human to absorb the culture, the vision, the SOPs, the playbooks, the unwritten rules — enough of it to operate without supervision.

Now contrast that with an AI agent.

Feed an agent every culture doc. Every onboarding SOP. Every playbook. Every quarterly objective. Every KPI dashboard. Give it access to the same shared drive, the same daily manager logs, the same training portal you'd give a new GM. Give it the same context a human would need three months to absorb.

It can start doing meaningful work today. Not three months from now. Today.

And here's the part your board hasn't done the math on yet: a human takes a month to onboard. An agent takes a morning. You can onboard three agents a day. Three agents a day, instead of one human a month.

That's not a faster analyst. That's a different cost structure.

What the un-onboarded agent does vs. the onboarded one

Picture two agents at your company. Same model under the hood — Claude, GPT, doesn't matter. The only difference is what they've been onboarded with.

Agent #1, hired on Friday, started Monday, given a POS login and nothing else. Looks at the numbers. Sees Store 14's lunch sales dropped 12% last week. Tells you Store 14 had a bad week. You knew that. Your area manager knew that. The store knew that. You've paid a vendor for a faster way to learn what everyone already learned by Tuesday morning.

Agent #2, hired the same day, but actually onboarded. Read your DM's last six weekly emails. Read the playbook you wrote two years ago for diagnosing a sales dip. Read the daily manager logs from Store 14 — including the one where the GM noted she was about to go on PTO and her second was covering. Read the post-mortem from the last time this happened in 2024.

Same Store 14 dip. Different answer. Agent #2 tells you Store 14's second-string GM is covering, she always struggles with the lunch transition without her usual team, last time this happened recovery took eight days but only after a specific shift change at 11am. It drafts the email to the area manager. It schedules the staffing change in your system. It flags two other stores running the same pattern and likely to dip next week.

Agent #1 told you a number. Agent #2 ran the play.

Why this is a CFO question, not an IT question

Your CEO is going to ask you the question every CEO is asking their CFO this year: how does AI change our cost structure?

Half-version answer: we were able to reduce analyst headcount and save our managers 40 hours per month. P&L cost improvements of 50-100 basis points. Real. Big. But not transformative.

Full-version answer: we run this company with materially fewer people doing today's work, and we reinvest the headcount into growth. HQ shrinks by half. District managers oversee twice the stores without breaking. GMs stop doing admin and get their hours back for guest experience and waste reduction — the two things only a human in a restaurant can actually do. And we plug all those savings back into growing stores instead of paying it out as the cost of staying flat.

That's a different operating model.

If your AI strategy doesn't have a plan for the unstructured half, your AI strategy is half a plan.

The honest part

Two things I want to be straight with you about, because this is where vendor content gets dishonest.

It isn't easy. Getting your playbooks, your emails, your manager logs, your tribal knowledge into a form an AI can actually use is real work. Most operators in your size band don't have anyone whose job it is to do this. It's not a six-week project you delegate to IT. It's an operating capability you have to build, and then keep building.

You don't have to do it all at once. Companies that get this right start small. One playbook. One weekly email. One area where the gap between great and average operators lives in someone's head and nowhere else. Get that one thing into a form an agent can use. See what happens. Add the next one.