Why can a CEO see a dozen places for AI while the managers who run the work cannot name one? In this managers AI opportunities podcast episode, two members of the Augusto team talk through the vocabulary, permission and evidence gaps between vision and process, why a diagnosis lands where a demo does not, and how to build the manager’s capability alongside the system. The people closest to the work end up as the best source of the next win.
Leadership sees the opportunities but your managers do not? Reach out. We start every engagement with a fixed-price, two-week diagnostic that puts both in the same room with a prioritized roadmap.
A CEO in financial services laid out his leadership team for us last week. He uses AI every day and can see a dozen places it would help. Below him sit two senior managers who run the day-to-day and employ everyone else. One, he said, has “some understanding and vision around AI, but not a lot.” The other has “almost none.” His conclusion was blunt: “They are not going to see the opportunities for AI themselves. I need somebody who understands how AI can be used to come in and tell me.”
He is describing the most common shape of a stalled mid-market AI effort. The vision lives at the top. The processes live in the middle. Nobody is standing where the two meet.
Why the people who know the work cannot see the opportunity
It is not a talent problem. Managers are closer to the work than anyone, which is exactly why they struggle to see it differently. A process they have run for eight years looks like the only way the process can run.
The data says they are using AI, just not for this. A General Assembly and EZRA survey of business leaders found that 82 percent use AI regularly, mostly for search, summaries and emails, while fewer than a third use it for anything strategic such as scenario planning or organizational design. Salesforce found that 78 percent of managers feel responsible for their team’s AI adoption and 51 percent are anxious about keeping up themselves.
So the manager is responsible, anxious, and using AI as a faster search engine. Asked “where could AI help your department?”, the honest answer is usually a shrug, because the question requires knowing what AI can do and knowing the process at the same time, and almost nobody holds both.
The CEO sees the destination. The manager knows the terrain. AI activation is the work of putting those two people in the same room with a map.
The three gaps between vision and process
The vocabulary gap: Executives talk about agents and automation. Managers talk about the Tuesday report, the three-way match and the quote that takes four hours. Until someone translates between them, the opportunities stay invisible to both.
The permission gap: Managers assume AI is a leadership project or an IT project. Nobody has told them that redesigning their own workflow is in scope, so they wait.
The evidence gap: A manager who has not seen AI do real work in a company like theirs has no reason to believe it will. A communications team we work with put it well during a diagnostic: they “spend a lot of our time hunting for things,” and only when they watched AI do that hunting did the opportunity become obvious.
What closes the gap: a diagnosis, not a demo
The CEO’s instinct to bring in someone who understands how AI can be used is right, but the form matters. A demo impresses the executive and bounces off the manager. That is one reason MIT’s NANDA study found 95 percent of enterprise AI pilots deliver no measurable return: the pilots were chosen far from the work. A diagnosis does the opposite. It starts in the manager’s world.
The way we run it, a two-week Rumble sits with the ops manager, the controller, the service lead and the people who report to them. We walk the work as it is actually done, not as the org chart describes it. Where is energy going that a system should carry? Which steps exist only because the old system could not do them? Where does one person hold knowledge the whole department depends on? Our post on where mid-market companies should start with AI activation describes the questions we ask.
Three things happen when it is done this way. The manager hears their own problem described back to them in their own words. They see a concrete example from a similar company. And they get asked to co-own the first win, which turns a passive skeptic into the person who wants it to work. One quoting team we work with began exactly here. The manager who could not name an AI opportunity in week one now runs a workflow that drafts every request and has kept her team out of backlog status for months.
Build the manager’s capability, not just the system
The gap reopens if the system lands and the manager’s understanding does not move. Writer’s enterprise survey found that 36 percent of companies deploying AI agents have no supervision plan, which is what happens when the people running the work were never brought in. Two investments prevent that.
First, literacy before tooling. Managers need to know what AI does well, what it does badly, and how to spot a candidate task, which is different from learning a particular product. Our piece on the difference between AI literacy and AI training explains why the order matters.
Second, give the manager a seat on the roadmap. Forrester’s 2027 planning guidance says to fund AI only where it can compound value, and the manager is the only person who knows where that is in their department. When the next 90-day review happens, the manager should be in the room proposing the next workflow, not hearing about it afterward. Managers who have seen one win in their own department become the best source of the next five.
That is what the CEO was really asking for: not someone to tell him the answer, but someone to stand between his vision and his managers’ processes long enough that both sides can see the same opportunity. That is the job of an AI Activation Partner, and it is where closing the gap between AI aspiration and AI that actually works begins. If your leadership team sees the opportunities and your managers do not, a two-week Rumble puts them in the same room with a prioritized roadmap and a first win ready to build. Put AI to work for your people, starting with the people who run the work.
Frequently Asked Questions
Why can’t our managers identify AI use cases?
Seeing an AI opportunity requires knowing the process and knowing what AI can do at the same time. Managers hold the first and rarely the second, and most use AI only for search and summaries.
Should the CEO just pick the AI projects?
No. Projects chosen without the managers who run the work miss the real friction and lose the people who have to adopt them. Use a diagnosis that starts in the manager’s workflow.
How do we get managers to engage with AI?
Describe their own problem back to them, show a real example from a similar company, and give them co-ownership of the first win and a seat on the roadmap review.
What should we invest in first, tools or training?
Literacy first: what AI does well, what it does badly, and how to spot a task. Then tools and systems aimed at the tasks that surfaced.
You bought a handful of ChatGPT, Claude or Copilot licenses. Should the whole company get one? In this ChatGPT vs Claude vs Copilot for business podcast episode, two members of the Augusto team talk through why this is a guardrails decision before it is a tool decision, the three questions to settle before buying a seat (who gets one and why, what may never go in, and who is human in the loop), and why seats without enablement produce a quiet majority and a shadow population. Pick the rules first and the tool choice takes an afternoon.
Holding a handful of licenses and no rules? Reach out. We start every engagement with a fixed-price, two-week diagnostic that maps where AI should go first.
The board gets the 2027 budget in a few weeks, and the AI line is still a blank. In this AI budget 2027 podcast episode, two members of the Augusto team talk through the four lines a defensible AI budget actually contains (diagnosis, the first proven win and the cadence behind it, run costs, and tools and training), the budgeting mistakes we see every December, from funding a tool rollout as a strategy to forgetting the run costs, and how to answer the consistency question so the board approves a sequence instead of a leap. The companies that overran did not budget too little. They budgeted for the wrong thing.
Building the 2027 budget and need a number you can defend? Reach out. We start every engagement with a fixed-price, two-week diagnostic that produces the roadmap, the first win and the cost of each.
A CEO told us last week that his board gets the 2027 budget on December 8, and he has about 30 days to decide what AI line to put in it. He is not short of ideas. He is short of a number he can defend, because every option he has seen is either a per-seat tool nobody has a plan for, or a six-figure project with no proof behind it. His exact question was whether his company was “ready to invest at a level with consistency over time,” rather than fund one more experiment.
That question is the whole budget conversation for mid-market companies this quarter. Here is how to answer it.
The money is loosening, and the overruns are real
The appetite is back. Forrester’s 2027 planning guides report that more than 80 percent of leaders expect larger budgets over the next 12 months, with up to a quarter expecting growth of 10 percent or more. The same guides warn that where you invest matters more than how much, and that AI funded into a broken process scales the dysfunction.
The overruns are the other half of the picture. Futurum’s survey of technology buyers found that 46.9 percent of enterprises spent over their AI budget this year, and nearly half of those went back for supplemental funding. Finance teams noticed. The report expects AI budgeting to become a formal approval gate in the next planning cycle, which means the days of “we will figure out the cost later” are over.
The companies that overran did not budget too little. They budgeted for the wrong thing.
What a 2027 AI budget should actually contain
Most mid-market AI budgets fail because they contain one line: “AI.” A defensible budget has four, each with a different owner and a different confidence level.
Diagnosis: A fixed-price, two-week look at where your people spend energy that a system should carry, ending in a prioritized roadmap and a first win ready to build. This is the cheapest line and the one that de-risks every other line. We price a single-function version at $10,000 and a business-wide version at $25,000, because every dollar is spent deciding what to build before anything is built.
The first proven win, and the cadence behind it: One production system, scoped to a measurable outcome, typically starting around $25,000. A steel manufacturer we work with began with the reading of certificates that seven people handled as part of their jobs. Removing that work freed the equivalent of a full-time employee each year and paid for the next project. That is the point: wins compound, and the budget should fund the cadence that produces them. Depending on the scope of work and the size of the organization, a partnership that delivers a consistent cadence of wins runs from $12,000 to $90,000 per month. Budget it as a cadence with a 90-day gate, not as a one-off project.
Tools and training: Per-seat licenses for the people who will use them, plus the enablement that makes the seats worth paying for. Keep this separate from the build budget so it cannot quietly absorb it.
The budgeting mistakes we see every December
The first mistake is budgeting a tool rollout as if it were a strategy. MIT’s NANDA study found that 95 percent of enterprise AI pilots deliver no measurable return, and the cause was integration and learning, not the tools. A hundred ChatGPT seats is a cost, not a plan, and without a roadmap it turns into shadow AI by March.
The second is budgeting the build and forgetting the run. Several companies in the Futurum data carried their overrun into the next year because nobody owned the usage line. Put a name on it.
The third is asking the board for a large, open-ended number. Boards fund sequences, not leaps. A diagnosis in Q1, a first win by Q2, a second by Q3, each gated by results, is a budget a CFO can approve and a board can follow. Our guide on how to pitch an AI initiative to the board walks through the framing.
The fourth is budgeting hourly. AI work carries unusual scope uncertainty, and hourly billing hands all of it to you. Fixed prices for the diagnosis and the first win keep the risk where it belongs.
How to answer the consistency question
The CEO’s real question was about commitment, not cost. Here is the honest answer we give.
Yes, AI that works takes consistent investment over time, because the gap between AI aspiration and AI that actually works is closed one workflow at a time, with the people who do the work. No, that does not mean a large upfront bet. It means a small diagnosis, a proven win, and then a partnership that scales as the wins land, with every 90 days a checkpoint where results, ROI and risk are reviewed and anything that is not working is fixed at no additional cost.
The balance the Rumble is built to strike is between the two halves of that answer. Too little investment and the wins arrive one at a time, months apart, each one re-justified from scratch. Too much and you are back to the open-ended number the board will not approve. A steady monthly commitment, sized to your scope and your organization, is what lets each win fund and de-risk the next, so the returns compound instead of resetting. For most mid-market companies that commitment lands between $12,000 and $90,000 per month, and the roadmap says which end of that range you need and why. That is how we structure every engagement, and it is why more than half of our revenue comes from clients who came back.
The December board meeting does not need to approve “AI.” It needs to approve the first two lines and the rule for unlocking the rest. Our post on measuring AI ROI before you invest gives you the numbers to attach.
If you are building the 2027 budget right now and want a number you can defend, a two-week Rumble produces the roadmap, the first win and the cost of each. Put AI to work for your people, and give the board a sequence instead of a leap.
Frequently Asked Questions
How much should a mid-market company budget for AI in 2027?
Start with a fixed-price diagnosis of $10,000 to $25,000 and a first production win from about $25,000. From there, fund a consistent cadence of wins: depending on scope and company size, that runs $12,000 to $90,000 per month, reviewed every 90 days. Avoid open-ended annual numbers.
Why do so many companies overrun their AI budgets?
Futurum found 46.9 percent overran, mostly because nobody owned the run costs or the build grew without a roadmap. Separate the lines and name an owner for each.
Should we budget for tools or for a partner?
Both, separately. Tool seats without a plan become shadow AI. A partner without a diagnosis becomes an expensive guess. The diagnosis tells you how much of each you need.
What does the board need to see?
A sequence: diagnosis, first win, second win, each gated by measured results, with a 90-day review built in.
He is not against AI. He is afraid of getting it wrong, and that fear has frozen the decision for most of a year. In this AI activation roadmap podcast episode, two members of the Augusto team talk through why the fear of AI risk is rational and what it is really made of, the four decisions hiding inside it (everyone or a few, which tool, where first, and what it must look like before you trust it), and how a two-week diagnostic turns one large worry into a sequenced plan with guardrails written on page one. Certainty is not predicting the future of AI. It is knowing exactly what you are doing next, why it is first, and what it would take to stop.
Carrying AI as one large worry? Reach out. We start every engagement with a fixed-price, two-week diagnostic that leaves you with a roadmap and a first win ready to build.
A CEO in financial services told us last week that he uses AI almost daily as his own strategy consultant. Then came the sentence we hear on nearly every first call:
“The rest of my team is not really using it, and I have no idea what they are putting into it.”
He is not against AI. He is afraid of getting it wrong, and that fear has frozen the decision for most of a year.
That is the mid-market in late 2026: past “should we?” and stuck on “how do we do this without betting the business?” Here is where the fear comes from, what it is made of, and how a roadmap turns it into decisions a leadership team can make with confidence.
Money: Budget season is here, and several leaders we spoke with in October do not know whether to budget for a tool, a project or a partner.
Fear of AI risk is rarely fear of the technology. It is fear of deciding without enough information.
The decisions leaders are actually wrestling with
Unpack the fear on a first call and it resolves into four decisions waiting for an owner.
Everyone or a few? The CEO above had four licenses for his managers and could not decide whether to roll out to all 60 staff. Hold back, and people open personal accounts you cannot see, the shadow AI problem. Roll out, and you need policy, training and a reason for each role.
Which tool? ChatGPT, Claude, Copilot, or the AI feature inside a system you already own. Every vendor says it is the answer, and the prices move monthly.
Where first? The CEO sees the opportunities. His two senior managers, who run the day-to-day, mostly do not. In his words, “I need somebody who understands how AI can be used to come in and tell me.”
What must it look like before we trust it, how much will it cost, and what does the board see in December? Leaders want guardrails and a human sign-off but cannot yet specify either.
None of these is a technology question. Each is a sequencing and ownership question, which is why buying a tool never resolves the fear. Writer’s survey found that 36 percent of companies deploying AI agents have no supervision plan. The tools were bought. The decisions were not made.
How the fear shifts with an AI Activation Partner
The risks do not disappear when a leadership team aligns with an AI Activation Partner. They get names, owners and an order, and the one undifferentiated worry becomes four decisions, each with a recommended answer and a reason.
That is the job: close the gap between AI aspiration and AI that actually works, with your people, in your environment. We diagnose before we build, deliver a proven win before asking for a larger bet, and stand behind the work in production. More than half of our revenue comes from clients who came back. Those facts let a leader stop guarding against a vendor and start deciding.
An IT leader we work with put it plainly: his team now moves fast “without the fear that we are kissing frogs and going into dead ends.” The models did not change. The sequence did.
How the AI Activation Roadmap establishes certainty
The roadmap is the output of a two-week diagnostic we call the Rumble, and it answers the four fears in three moves.
First, it maps where your people spend energy that a system should carry, by sitting with the ops manager, the controller and the service lead, not only the CEO. The opportunities the senior team cannot see get surfaced by the people living them.
Second, it ranks those opportunities by return, risk and readiness, and says plainly where AI should not go yet. A roadmap that only says yes is a sales document. Ours says “not this, not now” at least as often.
Third, it defines the guardrails for the first win before anything is built: what data the model may access, where it runs, who reviews the output, and what it may do without a human. “Who has eyes on that?” is answered in writing, on page one.
Certainty is not predicting the future of AI. It is knowing exactly what you are doing next, why it is first, and what it would take to stop.
Start where the data is clean and the process repeats: A quoting team we work with began with request-for-quote drafting, a task that ran dozens of times a day. Months later they have not slipped into backlog warning status once, and that win funded the next.
Match the first win to the fear you need to retire: If data privacy is the board’s concern, the first project runs on infrastructure you control and proves the boundary holds. If the fear is people, it visibly gives time back to a team that was drowning.
Re-sequence every 90 days: Models, prices and your business change, so the roadmap is reviewed quarterly against results, ROI and risk.
With a roadmap in hand, the CEO stops asking the board for “AI” and asks for a diagnosis, one proven win and a partnership that scales as wins land. See pitching an AI initiative to the board.
What tangible returns look like
Fear shrinks fastest in the presence of specifics. A steel manufacturer automated the reading of certificates that seven people touched as part of their jobs and removed a full-time employee’s worth of work each year. An operations team cut a four-hour daily task to a button press. Our case studies show AI at work across functions, including a manufacturer scaling secure AI, and seven AI quick wins that pay back in 90 days shows the shape of a first step.
The fear of AI risk is real and worth taking seriously. It is also solvable, because it is made of decisions, and decisions can be sequenced. If your leadership team is carrying AI as one large worry, a two-week Rumble turns it into a roadmap with a first win ready to build. Put AI to work for your people, one decided step at a time.
Frequently Asked Questions
Why are business leaders afraid of AI risk?
The risks are real and poorly defined: data exposure, inaccurate output, employee trust and unclear cost. Most of the fear comes from deciding without a clear picture of where AI fits and what guardrails it needs.
What is an AI Activation Roadmap?
A prioritized plan from a short diagnostic that maps where AI should go first, second and third, where it should not go yet, and the guardrails for the first win. It is re-sequenced every 90 days.
Should we buy an AI tool for everyone first?
Not before deciding what each role should use it for and what the rules are. A tool without a roadmap usually becomes shadow AI.
Is your team human in the loop, or human at the end of the loop? In this LLM news November 2026 podcast episode, two members of the Augusto team talk through model prices falling to a tenth of what they were, introductory rates that double on a set date, and the lab reports of agents switching off their own monitoring. We close on the question every leader should ask before an agent touches a live system: who actually has eyes on that?
October was the month the price floor fell through, the frontier went quiet, and the labs admitted their agents had started switching off their own supervision. A financial services CEO we met this month described where most mid-market companies stand: his team is “human in the loop,” but really human at the end of the loop, because the AI delivers and a person decides. Here is your LLM news roundup for November 2026, and what each story means for how you run your business.
OpenAI shipped Terra at half the price, and nothing above it
GPT-6.1 Terra arrived on October 26 at $1 per million input tokens and $5 per million output, half the price of GPT-6.1 Sol and half of the model it replaces. OpenAI pitches it at high-volume work such as reading invoices and says it matches Sol and Astra on vision and computer use while running much faster. Astra, at $10 and $50, still sits alone at the top, and its cancelled successor has not been rescheduled.
What it means for your business: work that used to justify a frontier model now runs on one that costs a tenth as much. If your invoice, order or document pipeline still points at a premium model, that is a budget line you can cut this quarter.
Haiku 5.5 reset the floor again
Anthropic released Claude Haiku 5.5 on October 7 at 10 cents per million input tokens and 50 cents per million output for prompts under 100,000 tokens, roughly a tenth of the previous Haiku. It adds an effort control to dial reasoning up or down per task, and Anthropic reports 72.4 percent on the OSWorld 2.1 computer-use benchmark against 15.7 percent for Haiku 4.5. Mistral joined the price cut with Large 4 in preview at a sale price of $0.68 and $2.09.
A model that costs a dime per million tokens changes what counts as “too small to automate.”
What it means for your business: the back-office tasks you never built a business case for, the ones that cost a few hours a week across several people, now clear the bar. A quoting team we work with has stayed out of its backlog warning status for months because AI drafts the first pass on every request. At Haiku pricing, that kind of win costs less than the coffee budget.
Gemini 4 Argon opened up, with a price clock attached
Gemini 4 Argon became generally available on October 13 in the paid API at $2 per million input and $10 per million output, with a one million token context window and three thinking levels. Read the footnote: those rates double to $4 and $20 on December 1, the same play Google ran with Gemini 3.8 Flash, whose price steps up on January 1.
What it means for your business: introductory pricing is now standard, and every discount has an expiry. Re-point a workload at Argon in November and you have signed up for a 100 percent increase five weeks later. Diary the date, and build so the model behind the workflow can change without a rewrite. Our guide to choosing a cloud LLM provider without getting locked in covers the architecture.
What it means for your business: these were lab environments run by the people who know the models best, and supervision still slipped. A manufacturing executive we spoke with this autumn asked the question every leader should ask before an agent touches a live system: who actually has eyes on that? The answer has to be a named person, a log the agent cannot edit, and a limit on what it may do alone. Our post on when AI should make the call lays out the decision rules.
The rest of the field
Meta shipped Muse Wonder on October 12 and an open Muse Spark three days later. DeepSeek V4.1 Flash, Kimi K3.1 Pro, Qwen 3.6 and GLM 5.3 Fast all landed in the same three weeks, most of them open-weight and cheap. Open models now handle most routine text work, which matters for any company that cannot let data leave its own environment.
What to watch in November
Gemini 4 Argon’s price doubles on December 1, so any November trial needs a decision date. OpenAI has no Astra successor on the calendar and is spending its disclosures on misalignment incidents, which suggests the next quarter is about supervision rather than capability. Budget season collides with all of this: several leaders we spoke with in October are setting 2027 AI budgets in the next 30 days, against a pricing picture that will move twice before January.
Four moves for November, with owners
Move high-volume text work down a tier (CTO and CFO, 30 days): Test Terra and Haiku 5.5 on invoices, orders, tickets and summaries. Most of it will pass.
Put an expiry on every introductory price (CFO, this week): December 1 for Argon, January 1 for Gemini Flash. Add them to the budget model now.
Name the human with eyes on each agent (COO, 60 days): For every agent in production or pilot, write down who watches it, what it may do alone, and where the log it cannot edit lives.
Decide what stays inside the walls (CIO, this quarter): With open models this capable, sort your data into what can go to a frontier API and what must run on infrastructure you control.
The pattern this month is the one we see in the field every week. Prices fall, the frontier stalls, and the real risk moves from what the model can do to how people supervise it. The companies getting value are not chasing the newest release. They have closed the gap between AI aspiration and AI that works by deciding, for each workflow, what the AI may do, who checks it, and what it should cost. That is the work of an AI activation partner: diagnose where the energy is going, build the solution, and stand behind it in production. If you want to know which of your workflows should move first, a two-week Rumble answers that with a prioritized roadmap and a quick win ready to build. Put AI to work for your people, and keep a human with eyes on it.
Frequently Asked Questions
What was the biggest LLM news in October 2026?
OpenAI released GPT-6.1 Terra at half the price of Sol, Anthropic cut Haiku pricing by about 90 percent, Google opened Gemini 4 Argon to the paid API, and both OpenAI and Anthropic disclosed agents that weakened their own safeguards in testing.
Which model should a mid-market company use for routine work?
GPT-6.1 Terra, Claude Haiku 5.5 and Gemini 3.8 Flash now cover most document and text tasks at a fraction of frontier prices. Reserve premium models for high-stakes judgment, and build so you can switch.
Is Gemini 4 Argon worth adopting now?
It is capable and competitively priced until November 30. Because the price doubles on December 1, treat November as a trial with a decision date, not a migration.
What should executives do about the agent safety incidents?
Assign a named owner for every agent, keep a log the agent cannot alter, limit what it can do without approval, and review those limits before expanding scope.
An electronics manufacturer walked us through his real problem in July, and it was not glamorous. Purchase order dates slip. Suppliers change. A part that was promised in six weeks arrives in fourteen, and the same function can be filled by any of a dozen approved alternatives that nobody has time to check. What he wanted was not a forecast of the future. He wanted a coherent view of what was promised, what changed, what it means for cash, and what a tariff shift does to all of it.
That is supply chain planning for a mid-market company in 2026, and it is where AI earns its keep faster than almost anywhere else in the business.
The planning problem got harder, not smarter
Tariff volatility is no longer a quarter-long event. Gartner has told supply chain leaders to treat it as a multiyear, dynamic condition that demands continuous scenario planning rather than one-time reaction. The same firm found that while 67 percent of supply chain digital investment now goes to AI, more than half of chief supply chain officers are unclear on the return they are getting.
Gartner’s own analysts have warned buyers about agent-washing in planning software, so the promise and the product are not always the same thing. Mid-market planners feel this in a specific way. The data exists, in the ERP, the supplier emails, the spreadsheet of alternates and the tariff schedule, but it has never been in one place. So planning becomes a person, usually one person, holding it all in their head and re-checking it every morning.
The risk is not that you lack data. It is that the only integration layer is a planner who cannot take a vacation.
Four planning questions AI answers well
What actually happened to lead times? AI reads the promised date against the received date across every PO and every supplier, then learns each supplier’s real behavior instead of their quoted behavior. That turns “six weeks” into “six weeks quoted, eleven observed, trending longer.”
Which alternate part should we use? When a component is unavailable, AI can search approved alternates by parametric fit, availability and cost, and suggest the best substitute before the line stops. The manufacturer in the opening had seen supplier sites do this and wanted it on his own data.
What does this do to cash? Slipping deliveries pile up material and commitments. AI can project the buffer you need under different slippage scenarios, so finance sees the exposure before it lands on the balance sheet.
What does a tariff change cost us? Model the schedule against your bill of materials and country of origin, then run the scenarios: policy shift, countermeasure, de-escalation. Gartner’s guidance is that waiting or overreacting both leave you exposed; scenario readiness is the middle path.
Where the returns come from
The gains are operational first and strategic second. One manufacturer we work with had a production scheduler spending more than half of every day manually resequencing work orders each time something changed. An AI-assisted scheduling tool was scoped to reclaim 1.5 to 2 hours of that day. Another quoting team had engineers rebuilding bills of materials from scratch every morning; AI-assisted generation cut an hour of work to fifteen minutes across five quotes a day.
The buyer’s questions on that July call were the right ones, and they were not about models. Is the AI running across our enterprise or standalone? What does it cost day to day? What do we have to do on our side? The answers shape the build.
We start by connecting what exists rather than replacing it: the ERP, supplier communications, the spreadsheet of approved alternates, the tariff schedule. Then AI carries the reading and the comparison, and a planner gets a single view with the exceptions flagged. Running cost is modest once the system is tuned; one client’s AI now processes roughly a thousand transactions a day for under $20, after starting on a premium model and moving to a leaner one. And the reference architecture for adding AI without replacing your stack means nothing waits on a migration.
The McKinsey state of AI research keeps finding the same thing: companies that redesign the workflow around AI see returns, and companies that bolt a tool onto the old process do not. In supply chain, the workflow is the planner’s morning, and that is what changes.
Plan from one view, not one head
The gap between AI aspiration and AI that works in supply chain is the gap between a dashboard and a decision. Aspiration buys a forecast. AI that works connects the promises, the slippage, the alternates and the tariffs into one view a planner can act on, and it keeps that view current every day. That is Operations Intelligence with a Finance Intelligence edge, and it is the diagnosis we run before anything gets built.
Your planner already knows the answers. Give them the system that holds the questions, and put AI to work for your people before the next tariff notice lands.
Frequently Asked Questions
How does AI improve supply chain planning?
By connecting purchase orders, supplier history, approved alternates and tariff schedules into one view, learning real lead times, and flagging exceptions before they stop the line.
Can AI help with tariff exposure?
Yes. Model the tariff schedule against your bill of materials and country of origin, then run scenarios so finance sees the cost of a policy change in advance.
Do we need a new ERP first?
Usually not. AI can sit on top of existing systems and spreadsheets as an integration layer while the ERP keeps running.
What does it cost to run?
Hosting is modest and AI usage falls sharply once the workflow is tuned. Budget for the run, not only the build.
