AI has sped up work, but few companies can point to organization-wide return on investment (ROI). Everyone is calling this a paradox. This three-part series names the three things buying the tools never fixes on its own, the people, the organization, and the foundation, and what to do about each. Read all three to find where your own gap is hiding.
Part 1: The People | Part 2: The Organization | Part 3: The Foundation
Count the AI tools running in your company right now. The ones actually in use. The Copilot licenses, Enterprise Claude accounts, Salesforce Agentforce. The pilot the finance team built with a contractor. The thing the marketing group pays for on a corporate card. The internal assistant somebody in operations put together over a long weekend.
If you got past ten, you’re typical. If you can name who owns each one, what it costs, and whether it’s working, you’re rare. Atlassian’s 2026 research found that only 6% of executives can point to organization-wide AI ROI, and the reason isn’t that the tools don’t work. It’s that there is nothing to measure them with. Twelve tools, twelve logins, twelve vendors, no shared memory. Every pilot starts from zero. The company gets faster at individual tasks and no smarter as an organization.
Why this matters more than it did a year ago
Something shifted in the middle of 2026 that most executive teams haven’t fully absorbed: the frontier models became close to interchangeable. The gap between the leading providers narrowed to the point where, for most business tasks, which model you use matters far less than what you’ve built around it. The models are becoming commoditized. Prices fell. Switching got easier. The model has become something you rent.
That changes what the durable asset is. When the model is a commodity, the thing you wrap around it, your business context, the guardrails, your way of knowing whether it’s working, is the only part that appreciates.
The question for executive teams isn’t “which AI should we buy?” It’s “what should we own, regardless of what we buy?” Engineers call this the harness. We’ll call it the foundation. You rent the model. You own the foundation.
What the foundation is, in plain terms
Strip the architecture diagrams away and the foundation is five things. None of them is exotic. Most companies have a version of each for their financial systems and none for their AI.
A shared definition of your business. What “a customer” means in your company. What “an order” is, what “a batch” is, what “on time” means, and the history of each, because most systems of record overwrite yesterday and remember nothing. Written down once, in a form every tool can use, so the finance team’s assistant and the operations team’s forecast are talking about the same thing. Without this, every AI tool learns your business from scratch, and each one learns it differently.
One door. Every AI request in the company goes through a single point, so cost, usage and risk show up in one place. Without this, you cannot answer the CFO’s question about what AI is costing you, and you cannot swap vendors without rewriting everything that touches them.
A register. A list of every AI tool running in your company, bought or built, each with a named owner. Without this, you don’t know what you’re governing. Most companies discover the size of their AI footprint the first time something goes wrong.
A way to know if it’s working. Before anything goes live, and every week after. Not a vendor’s demo; your own test, on your own data, against what happens. Without this, “the pilot worked” is an opinion, and six months later nobody can say whether the thing in production still does. This is your evaluation framework.
Approval in proportion to risk. Who signs off on what, at what level of consequence, with the same rules for the tools you bought as for the tools you built. Without this, governance either doesn’t exist or exists as a committee everything waits behind.
That’s it. Five things. If you have them, you can add the eleventh tool in a week and know what it costs and whether it works by the second week. If you don’t, the eleventh tool is another island.
A nervous system, not a headquarters
Here is where executives get worried, and rightly. “Own the foundation” sounds like “centralize AI,” and centralizing AI is one of the fastest ways to fail. We wrote about that in the second article in this series: the AI Center of Excellence that becomes the place where the business goes to wait.
The foundation is not that. Think of it as a nervous system, not a headquarters; it’s the core of what makes your business, yours. A nervous system doesn’t decide where the hand goes. It makes sure the hand can feel, that the signal gets back to the brain, and that the whole body knows what the hand just learned. The center owns the foundation, the shared definitions, the one door, the register, the tests, the rules. The business units own the decisions: what to build, what to buy, whether it goes live in their operation. Standards are shared. Decisions are local.
Get this distinction wrong in either direction, and your AI initiatives won’t scale. Centralize all decision making and you have a bottleneck. Decentralize your foundation and you have twelve islands with twelve definitions of a customer. The companies getting results have done the unglamorous thing: they’ve been disciplined about what’s shared and explicit about what’s not.
The tools you already bought count
Most organizations are not in the business of building an agent-building program. You’ve bought licenses. That doesn’t exempt you from defining the foundation; it’s the strongest argument for it.
Governance that only covers what you build misses most of what you run. The Copilot seats, the vendor’s embedded AI, the SaaS tool that quietly added a model last quarter: all of it consumes your data, produces outputs your people act on, and costs your organization money, and almost none of it shows up on the same budget line item as the internal pilot.
The register is how it gets there. The one door is how you see what it costs, the tokenomics. The test is your evaluation framework to find out whether the expensive bundle you renewed in January is moving you closer to your north star.
This is the accountability answer for a company that has bought AI and can’t see the return. You don’t need to have built anything to need a foundation. You need one because you bought things.
What it looks like when it’s done right
One company we worked with, a manufacturer with operations across several regions, had systems of record that kept no history. Each month overwrote the last. That’s common, and it’s fatal for AI, because a model that can’t see yesterday can’t learn anything about tomorrow.
The first thing the foundation did was remember. Before any forecast, before any agent, the team built a place where the business’s own history accumulated: what was ordered, what shipped, what the plan said versus what happened. Alongside that history came a connector into the main system of record, a way to test outputs against reality, a handful of reusable patterns for how AI intakes data and asks a human for approval, and a written record of every architectural decision and why it was made.
None of those was the deliverable. The deliverable was a way for their users to interact with the data that was locked behind unavailable systems to the business unit. When the second use case came along, completely unrelated to this specific function, it needed almost none of that built again. When the business wanted to expand into another region, the only thing that changed was the connector. Each use case shipped faster than the last. That compounding of information is what the foundation is for, and it’s the same story we told in the second article about pilots that leave something behind. This is what “behind” looks like.
Governance that doesn’t mean slow
One more thing the foundation does, and it’s the one that makes the rest survivable: it lets you put the controls where the consequences are, instead of everywhere.
Not every AI decision needs a human gate. An assistant that drafts an internal summary needs a basic check and nothing more. A model that changes a price, approves a stage in your workflow or touches a customer, needs an independent second opinion, ideally from a different system than the one that produced the answer, and a named person who signs off. The gates go at the high-consequence moments, not spread evenly across every step so that everything moves at the speed of the slowest approval.
That’s what most AI governance gets wrong. It treats every use the same, which means either everything is slow or nothing is checked. Matching oversight to risk is the only approach that is sustainable, and you can only pull it off if the foundation exists. You need the register to know what’s running, the one door to see it and manage the costs, and the evaluation framework to judge its performance.
The muscle to build
If you intend to run many AI systems, whether you build them or buy them, the capability your organization needs to develop isn’t building more agents. Agents are getting easier to build. The capability you must develop to scale AI usage is the foundation: knowing what you’re running, knowing what it costs, knowing whether it works, and knowing who decides. Evaluation, governance, and the foundation they run on.
That’s the muscle we’ve learned to prioritize before anything scales — it’s the difference between compounding every new AI effort and starting from zero each time.
Questions to take back
- Who owns your business context and where does it live? If the answer is “in the systems” but the systems keep no history, or “in the data team” but every tool defines a customer differently, you don’t own it yet.
- If you swapped AI partners tomorrow, what would break? If the answer is “everything,” you’ve been building on rented land.
- Which of your AI tools could we measure this quarter? Cost, usage and whether it’s working? If the answer is “the one we built,” you’re governing a fraction of what you run.
Request an AI Briefing
AI has already changed how your people work. Request an AI Briefing with Robots & Pencils to see exactly where your organization sits on the productivity paradox, and what to fix first, across the people, the organization, and the foundation.
About the Author
Brendan Flynn is SVP, Strategist at Robots & Pencils where he heads industry strategy within the Generative & Agentic AI Studio.
Key Takeaways
- Most companies cannot say what AI tools are running, who owns them, or whether they work. Atlassian’s 2026 research found only 6% of executives can point to organization-wide AI ROI, largely because there is nothing in place to measure it with.
- Frontier AI models are becoming commodities. The gap between leading providers has narrowed enough that the model matters less than what a company builds around it.
- The foundation is five things: a shared definition of the business, one door every AI request goes through, a register of every AI tool with a named owner, a way to test whether each tool is working, and approval sized to the risk of what it touches.
- The foundation works like a nervous system, not a headquarters. Standards, shared definitions, the one door, the register, and the tests stay centralized. Decisions about what to build or buy stay with the business units.
- A company does not need to build its own AI to need a foundation. Buying tools is reason enough, since governance that only covers what a company builds misses most of what it actually runs.
- Companies with a foundation in place can add a new AI tool in about a week and know its cost and performance within two. Companies without one start every new tool from zero.
FAQs
What does it mean to own the foundation instead of the model?
AI models are becoming commodities as leading providers converge in capability, so switching between them is getting easier. What a company builds around the model, its business definitions, its governance, its way of testing outcomes, is the part that keeps its value no matter which model runs underneath it.
What are the five parts of an AI foundation?
A shared definition of core business terms, a single point every AI request goes through, a register of every AI tool with a named owner, a repeatable way to test whether a tool is working, and an approval process sized to the risk of what the tool touches.
Does a company need a foundation if it only buys AI tools and does not build any?
Yes. Governance that only covers tools a company builds misses most of what it actually runs, since most AI tools in a typical company are bought, not built. A foundation gives a company a way to see cost, usage, and performance across every tool, regardless of where it came from.
Does owning the foundation mean centralizing every AI decision?
No. The foundation centralizes standards, shared definitions, and the way tools are tested and tracked. Decisions about what to build, what to buy, and when it goes live in a specific business unit stay local to that unit.
What is the payoff of having a foundation in place?
A company with a foundation can add a new AI tool and know what it costs and whether it works within about two weeks. Without one, every new tool starts from zero and stays an island, disconnected from everything the company has already built.
