Turn Artificial Intelligence into Proprietary Intelligence

How to Win with AI

Decision 4: Technology Architecture

Decision 4: Technology Architecture

Own enterprise orchestration.

By Sarah Elk, Chuck Whitten, Hernan Saenz, Gene Rapoport, Nicolas Bloch,
Pascal Gautheron, and Anne Hoecker

Own the key parts of the stack where your competitive advantage is encoded and your risks are controlled.
  • Own the part of the agentic layer where your company’s most important know-how gets encoded. This knowledge may include your operational skills—the steps your business follows and in what order—and the tools that carry out those actions.
  • Having agents operating is not enough. You must also own access and agent governance, because that is where you control risk. As agents act autonomously on live systems, the most recommended place to approve, deny, audit, or contain what they do is the boundary where they reach into your data and tools, not inside the agent’s reasoning, which is more brittle and bound to regular changes. Own that boundary, and you can answer your Chief Information Security Officer (CISO) and your board about who authorized an agent to touch what.
  • Adopt and enforce discipline about how agentic systems are built and managed. Agentic systems become sprawling and unmanageable faster than almost any software you have run before, and an estate you cannot inventory, audit, or reason about is one you cannot change or improve. Mandate standards from the top to keep it manageable (everything registered, versioned, and tested; business logic captured).
  • Agentic AI is probabilistic rather than deterministic, stateful, and continuous. So, its behavior drifts as models and data change, and it is prone to cascading failure in multi-agent chains, where a single error propagates through every downstream agent. Maintaining agent health means continually testing whether it continues to produce the right answers. Agents also must be continually tested for vulnerability to attack.
  • What you build today may be obsolete within months. Build it anyway. The code is disposable by design, and the assets the build produces (the semantic layer, the registries, the engineering muscle, the experience curve) survive every rewrite, making the next iteration faster. The tech is what you ship today; the proprietary intelligence is what you keep.
  • SaaS portfolios must be actively reassessed. AI is cannibalizing vendor value propositions faster than most contract cycles. As AI-assisted development accelerates agent proliferation across your organization, this reassessment cannot be a one-time exercise. It must become a continuous operational discipline.

Where your competitive advantage lives

The most important technology decision you will make in your AI transformation is not which model to use. Models are changing so rapidly that any specific choice will be obsolete within months. Most of the stack you can buy. But a few layers are where your competitive advantage is encoded and where your risks are controlled, and those risks you have to own yourself. We call this enterprise orchestration: The layers where your company manages its agents, tools, and skills as first-class enterprise assets, governs what those agents are allowed to do, and turns its proprietary data into reusable agent-ready assets, rather than ceding to a scattered collection of vendor-supplied tools you cannot change, connect, or hold accountable.

Owning your enterprise orchestration means you do two things extremely well:

  1. First-class asset management: codifying, registering, versioning, and testing your skills, tools, and agents so they can be inventoried and improved rather than buried in prompts no one can extract. This process makes the estate manageable as it scales, and it is where much of your encoded know-how physically lives.
  2. Behavior governance: controlling what skills, tools, data, and systems each agent is allowed to access. As agents act autonomously on live systems, this boundary is the recommended place to approve, deny, audit, or contain what they do, and owning it lets you answer your CISO and your board about who authorized an agent to touch what. Your proprietary data matters, but your encoded workflows are a genuine part of your AI estate that compounds into a durable moat.

If you cede that layer to a single vendor, you are handing them architectural control of your AI estate. Your agents will be limited to what that vendor’s platform allows. Your ability to switch models, add new capabilities, or integrate with new data sources will depend on their roadmap, not yours. Owning the enterprise orchestration layer is the technology equivalent of owning your supply chain; it is the strategic control point that determines how much flexibility and advantage you can extract from everything else.

Asset management, governance, and security aspects of good enterprise orchestration are ongoing throughout the software and agent life cycle process inside a company. It is not something that is built once and left; it is living and breathing as builds progress and capabilities improve.

Circular lifecycle diagram showing AI primitive management across five stages: Build, Register (agent primitive), Evaluation (including shadow evaluation), Deploy, Monitor, Discover Patterns, and Improve (optimize or redesign process). The cycle feeds into Institutional Learning at the bottom. Center text reads: 3x, 5x, 10x value unlock.

Ramp, the comprehensive financial operations platform for businesses, shows what proprietary intelligence looks like on the ground. After reaching 99% adoption of AI tools across the company, the team realized most employees had plateaued—not because the models were inadequate, but because there was no shared infrastructure to connect tools, propagate workflows, or carry context across sessions. The team built Glass, an internal AI productivity layer where one person’s breakthrough rapidly becomes the company’s baseline, and the system accumulates persistent memory across the organization. As the company’s leaders put it, internal productivity is a moat, and an organization does not hand its moat to a vendor.

At this point, a reasonable CEO will ask why anyone should build infrastructure that will be obsolete within months. The specific orchestration code, the agent designs, the integration patterns, and even today’s architectural conventions are all moving targets. The objection is fair—and it is the wrong reason to wait. The artifacts of an AI build are partly disposable by design, but the assets the build produces are not. Going through an actual orchestration effort is how a company builds out its semantic layer, hardens its registries and governed gateways, develops the engineering muscle to operate probabilistic software at scale, accumulates change-management capability, and earns the experience curve that no shortcut replaces. None of those efforts is the code itself. All survive every rewrite, and each one makes the next iteration faster. The companies that wait for the technology to stabilize before they invest are not protecting themselves from obsolescence; they are allowing the durable assets of an early build to accrue to their competitors.

What sets agentic AI apart

Agentic AI is a fundamentally different class of software, and the differences carry serious operational consequences. Traditional enterprise software is deterministic: same input, same output, every time. Agents are probabilistic, stateful, and continuous: Behavior can drift as data and underlying models evolve. The most critical distinction is that traditional software fails safely; agents don’t. In multi-agent systems, an orchestration-level error propagates through every downstream agent before anyone detects a problem. Cascade risk is among the most underappreciated challenges in enterprise AI.

Enterprises must also distinguish functional correctness from adversarial resilience. Golden test suites and shadow-mode testing confirm output quality on anticipated inputs. Still, they don’t reveal how an agent behaves under active manipulation by techniques such as injected prompts, tool abuse, data exfiltration, or privilege escalation across agent handoffs. Both assessments are required before any agent with meaningful system access reaches production, and threat model results should inform the trust policy that the runtime enforces.

Governance must operate at the boundary—every tool call, data source, external connection, and agent delegation—because the LLM’s internal reasoning is inaccessible.

Three mechanisms make this work:

  • A registry: Unregistered agents and tools don’t run
  • A governed gateway: Every tool call is policy-evaluated, fully logged, and fails closed.
  • Promotion gates: Agents don’t reach production without passing structured quality checks. No committee reviews every agent, but the gate passes or blocks automatically.

The economic argument for a shared platform is as important as the technical one. Without shared infrastructure, every agent team duplicates the same foundational work, data preparation, system integrations, governance mechanics, evaluation pipelines, and deployment automation. The third team spends the same months as the first team, solving problems the first team already solved, producing results that the fourth team cannot reuse. With a governed platform, data models built for one domain are reusable across adjacent domains. Tool integrations built for one use case are available to every subsequent use case in that domain. Skills are the encoded procedural expertise that tells an agent how your organization actually operates, and they improve with every calibration run and benefit every agent that uses them. The organization accumulates operational knowledge as a compounding asset rather than as a series of disposable projects.

What is required to do enterprise orchestration well?

Layered architecture diagram showing five planes of enterprise AI orchestration stacked vertically. At the top, the Control plane observes all activity, tracking fleet visibility, cost attribution, audit trails, and dashboards. Below it, Governance includes gateway, OPA policy engine, telemetry, registries, and promotion gates. Inside Governance sits the Execution plane — a framework-agnostic runtime with memory services supporting LangGraph, OpenAI SDK, Google ADK, CrewAI, and any future framework — alongside a Tool registry of governed versioned tools organized by domain, and a Skill registry with MCP-governed access. Below that, the Data plane makes enterprise data agent-ready and reusable across domains. The Infrastructure plane is cloud-agnostic across Azure and GCP. At the bottom, External connections include enterprise systems, LLM providers, MCP servers, data sources, and users.

  • AI TRANSFORMATION: ENTERPRISE GLOSSARY

Vous souhaitez continuer cette conversation ?

Nous aidons des dirigeants du monde entier à matérialiser des impacts et des résultats pérennes et créateurs de valeur dans leurs organisations.