Over the past month, I have been in a running conversation with enterprise leaders about the same two questions: where do AI agents actually create value, and where inside their organization does the momentum live?
Most of the answers on the table are about technology. Which model, which vendor, which platform. But after two decades driving transformation across investment banking, asset management, media, and regulatory compliance, one lesson has repeated itself in every engagement: transformation rarely fails because of technology. It fails because the organization does not understand how its own people, knowledge, workflows, and decisions connect.
AI agents raise the stakes on that old problem. If you want AI to transform an enterprise, you first have to teach AI how the enterprise actually works. Most companies are skipping that step. They are buying intelligence and pointing it at an organization the intelligence cannot see.
Everyone is focused on making AI smarter. The enterprise challenge is making the organization understandable to AI.
The Pattern Behind Twenty Years of Transformation
Every stop in my career taught the same lesson from a different angle.
In investment banking, the systems were never the hard part. The hard part was the workflows underneath them: how a trade actually moved through the firm, who touched it, where the exceptions lived. In asset management, the entire culture was built on making decision-making criteria explicit, because a decision you cannot articulate is a decision you cannot systematize. In media, the challenge was fragmentation: content and data ecosystems that had grown up separately and had no shared model of what anything meant. In regulatory compliance, every workflow step had an owner, an approval, and a consequence, whether anyone had written that down or not.
Different industries. Different technology eras. Same failure mode. The organizations that struggled were not short on tools. They were short on a shared understanding of how the business actually operated. The knowledge existed, but it lived in people's heads, in unofficial processes, in the judgment of whoever had been there longest.
My career has never really been about deploying technology. It has been about understanding complex systems, aligning people around outcomes, and using platforms to change how organizations operate. AI does not change that work. It makes the cost of skipping it impossible to hide.
What an Ontology Actually Is
The word sounds academic. The concept is not.
A simple way to hold it:
- A database tells you what happened.
- A knowledge base tells you what people wrote down.
- An ontology tells you how the business works.
For enterprise AI, the ontology becomes the digital twin of the organization: the operating model translated into a structure a machine can reason over. It teaches AI what your business means, not just what your documents say.
An ontology has four parts, and each one solves a specific failure of AI systems today.
Objects are the nouns. Customers, contracts, employees, invoices, support tickets, sales opportunities. Without objects, AI sees "row 12478 in Salesforce." With them, it sees Acme Corp, a Fortune 500 customer, renewal coming in 45 days, owned by Sarah, with three open support issues. Objects give AI a business vocabulary.
Properties are the facts. Industry, contract value, renewal date, risk score, role, permissions. Ask an AI without properties to "show me risky accounts" and it guesses. With properties, risky account has a definition: renewal inside 60 days, usage down 30 percent, an unresolved P1, negative sentiment on the last three calls. The answer stops being a vibe and starts being a query.
Links are the relationships. Customer owns contract. Contract includes products. Support ticket affects renewal risk. Sales rep manages account. This is where intelligence emerges, because the AI stops retrieving isolated facts and starts understanding a graph of the company.
Actions are the verbs. Create the renewal plan. Escalate the ticket. Update the CRM. Trigger the workflow. This is what separates a chatbot from an agent. The ontology tells the agent what exists, how things relate, and what it is allowed to change.
What exists, how it connects, what can be done about it. That is the operating system AI needs, and no vendor can ship it to you. Which raises the real question: where does it come from?
People Define the Ontology
The people closest to the work hold the context that no system of record captures. How decisions actually get made. Which exceptions matter. Which processes are unofficial but load-bearing. Where knowledge actually lives. Who really owns a call, regardless of what the RACI chart says.
The org chart does not describe how a company operates. The ontology does.
This is why I keep coming back to the foundation layer of the Apex Pyramid: People + Outcomes = Transformation. I wrote there that AI amplifies whatever already exists, and that structure has to precede systems. Ontology is what that foundation layer produces when you take it seriously. Clear ownership of outcomes, explicit decision rights, alignment on what good looks like: those are not soft cultural exercises. They are the raw material of a machine-readable operating model. An organization that has done the people work can write its ontology down. An organization that has not will discover it cannot, and that discovery is worth more than any pilot.
Outcomes Give the Ontology Direction
Here is the mistake I watch companies make in the first meeting: "We need AI."
The better question is: what business outcome are we transforming? Cut customer resolution time by 40 percent. Shorten onboarding from months to weeks. Raise compliance accuracy. Compress the sales cycle.
The outcome determines which objects matter, which properties need to be precise, which links carry the intelligence, and which actions the agent needs permission to take. An ontology built around outcomes stays lean and useful. An ontology built for completeness becomes a data governance project that ships nothing.
The agents are downstream of all of it. The architecture that is emerging looks like this: people define the knowledge, knowledge structures the ontology, the ontology grounds the agents, and the agents drive business outcomes. The model sits in the middle of that chain as the reasoning engine.
The model is not the transformation. The model is the engine you rent.
The Moat Moved
The first wave of enterprise AI was a straight line: user, prompt, model, answer. It produced demos and disappointment in roughly equal measure.
The enterprise future runs through structure: user, agent, ontology, business systems, action. And that reordering changes where advantage lives. Every company gets the same models. GPT, Claude, Gemini, open source: the reasoning engines are converging into commodities, and they are improving on someone else's schedule, for everyone at once.
Your ontology improves on your schedule, for you alone. It encodes how your company thinks, decides, and changes, and no competitor can copy it because no competitor operates the way you do. The models are rented. The understanding is owned.
That is the moat. If a company asks whether AI can automate their entire enterprise, the honest answer is: not without first mapping how decisions happen. You cannot automate what you don't understand.
The Same Problem, One Level Down
I see this pattern from both sides now. Advising enterprises, the ontology is the operating model of a company. Building Revolv, it is the operating model of something smaller and more personal: a professional network. The objects are people, companies, meetings, and commitments. The properties are trust, recency, and context. The links are who knows whom, and how well, and why. The actions are the intro, the follow-up, the meeting brief.
The scale is different. The principle is identical. Intelligence without a model of the underlying system produces answers that sound right and change nothing. Intelligence grounded in how the system actually works is what produces transformation, whether the system is a Fortune 500 operating model or one person's network of relationships.
Two decades of transformation work taught me that the technology was never the constraint. Understanding was. AI has not changed that.
It has just made understanding the product.
