Enterprise Agent Decision Framework

The production agent stack is the decision.

Every enterprise agent needs 22 production capabilities across five layers. The platform you choose determines how many of those you get — and how many your team has to build and operate.

See the full stack

01 / Production stack requirements

A production agent is not just a model call.

Every agent that operates at enterprise scale needs five layers working together. The model is the intelligence layer — context, runtime, trust, and operations are the rest of the stack.

LAYER 1

Intelligence

Models

Provides the reasoning, language, vision, and generation capabilities behind each agent.

Example: A service agent understands a customer request and drafts an accurate response.

Why it matters here

Every agent requires model access.

Routing

Balances quality, speed, availability, and cost for every request.

Example: A routine order lookup uses a fast model while a complex dispute is sent to a frontier model.

Why it matters here

Estate scale or activity makes routing a material reliability and cost control.

Orchestration

Turns a request into a dependable sequence of steps, decisions, and actions.

Example: A claims agent gathers documents, validates coverage, calculates a recommendation, and requests approval.

Why it matters here

Act and Orchestrate agents execute multi-step workflows.

Agent-to-agent

Lets specialist agents collaborate on work that spans teams or systems.

Example: A sales agent asks pricing, inventory, and legal agents to assemble a compliant proposal.

Why it matters here

No orchestrated agent workflow is selected.

LAYER 2

Context & action

Connectors

Gives agents governed access to the systems where customer and business data lives.

Example: An account agent reads Salesforce history and checks an SAP order without manual re-entry.

Why it matters here

Enterprise agents must reach governed systems and data.

Grounding

Keeps answers anchored in current, approved enterprise information.

Example: A policy assistant cites the latest internal policy instead of relying on model memory.

Why it matters here

Useful agents need current, customer-specific context.

Tools & APIs

Allows agents to complete work, not just recommend what a person should do next.

Example: A support agent issues a refund through an approved commerce API after validating eligibility.

Why it matters here

Act and Orchestrate agents call tools or write to systems.

Sessions

Preserves the state of an interaction across multiple steps and channels.

Example: A customer begins a return in chat and completes it later by phone without starting over.

Why it matters here

Agent interactions require durable session state.

Memory

Enables useful continuity while retaining control over what an agent remembers.

Example: A relationship agent remembers communication preferences and approved portfolio objectives.

Why it matters here

The selected estate needs continuity across users, tasks, or long-running work.

LAYER 3

Runtime

Runtime

Runs multi-step agent work reliably beyond a single model response.

Example: A procurement workflow continues processing while waiting for an approval or supplier response.

Why it matters here

Production workflows require managed execution beyond a single model call.

Scale & isolation

Maintains performance during demand spikes while separating users and workloads.

Example: A retail assistant handles holiday traffic without one tenant affecting another.

Why it matters here

External demand or high activity requires scaling and workload isolation.

Sandbox

Lets agents run code or process files without exposing production environments.

Example: A finance agent analyzes an uploaded spreadsheet inside an isolated execution environment.

Why it matters here

Action-taking agents benefit from isolated execution.

Release controls

Enables controlled launches, versioning, testing, and rollback of agent changes.

Example: A new prompt is released to 10% of users and rolled back automatically if quality drops.

Why it matters here

Enterprise agents need controlled deployment, rollback, and versioning.

LAYER 4

Trust

Identity

Establishes who is asking, which agent is acting, and who owns each action.

Example: An employee agent signs in through corporate SSO and every action is attributed to that identity.

Why it matters here

Every agent action must be attributable to a user or workload identity.

Authorization

Restricts agent access to the permissions granted to the user and the task.

Example: A manager can approve an expense while the agent cannot access unrelated payroll records.

Why it matters here

Enterprise or action-taking agents need scoped delegated permissions.

Policy & safety

Enforces business, safety, privacy, and regulatory rules during execution.

Example: A healthcare agent blocks unsupported clinical advice and routes the case to a clinician.

Why it matters here

Audience, data sensitivity, or action-taking requires enforceable policy.

Human escalation

Keeps people in control of high-impact, uncertain, or exceptional decisions.

Example: A payment above a threshold pauses until an authorized employee approves it.

Why it matters here

Material actions or customer interactions need approval and escalation paths.

Audit

Creates evidence of what the agent knew, decided, and did.

Example: An auditor can reconstruct the data, policy, model version, and approval behind a decision.

Why it matters here

Regulation, external exposure, or system writes require auditable actions.

LAYER 5

Operations

Evals

Measures whether agent quality and safety remain acceptable as the system changes.

Example: A release is blocked when its refund-policy accuracy falls below the approved threshold.

Why it matters here

Production quality must be measured before and after releases.

Observability

Shows where an agent is slow, expensive, inaccurate, or failing.

Example: Operations traces a delayed answer to a slow CRM connector rather than the model.

Why it matters here

Production scale needs traces, metrics, and failure diagnosis.

Incident response

Limits customer impact and restores a safe service when something goes wrong.

Example: A faulty action tool is disabled globally and affected transactions are identified for review.

Why it matters here

Action-taking or external agents need rollback and incident ownership.

Registry

Makes every agent discoverable with clear ownership, purpose, status, and dependencies.

Example: Security can identify all agents using customer data and contact the accountable owner.

Why it matters here

A larger or orchestrated estate needs discovery and lifecycle ownership.

Cost controls

Keeps agent spending predictable and attributable to teams, customers, or use cases.

Example: A business unit receives a budget alert before an unexpected traffic spike exceeds its quota.

Why it matters here

Usage scale requires quotas, budgets, and cost attribution.

02 / Platform comparison

Build → Operate → Scale → Optimize

Select a platform and your cloud to see exactly what each capability requires — which services to wire, and what your team needs to build.

Runs on
Google Cloud (fixed)
Included First-party Wire up You build
01BuildCreate your agents
5 included
Capability

Google

Gemini Enterprise Agent Platform

Anthropic

Claude Enterprise

OpenAI

ChatGPT Enterprise

Foundation models

Included
Included
Included

Agent orchestration

Included
1P / SDK
1P / SDK

Tools & function calling

Included
1P / SDK
1P / SDK

Enterprise connectors

Included
Wire up
Wire up

Session & state

Included
Wire up
1P / SDK
02OperateRun safely
6 included
Capability

Google

Gemini Enterprise Agent Platform

Anthropic

Claude Enterprise

OpenAI

ChatGPT Enterprise

Managed runtime

Included
Wire up
Wire up

Identity / SSO / IAM

Included
Included
Included

Delegated authorization

Included
Wire up
Wire up

Policy & safety rails

Included
Included
Included

Human escalation

Included
You build
You build

Audit & compliance logs

Included
Included
Included
03ScaleHandle growth
5 included
Capability

Google

Gemini Enterprise Agent Platform

Anthropic

Claude Enterprise

OpenAI

ChatGPT Enterprise

Autoscale & workload isolation

Included
Wire up
Wire up

Agent-to-agent (A2A)

Included
1P / SDK
1P / SDK

Release & rollback controls

Included
You build
You build

Observability & tracing

Included
Wire up
Wire up

Incident response

Included
You build
You build
04OptimizeImprove continuously
6 included
Capability

Google

Gemini Enterprise Agent Platform

Anthropic

Claude Enterprise

OpenAI

ChatGPT Enterprise

Grounding & RAG

Included
Wire up
1P / SDK

Long-term memory

Included
Wire up
1P / SDK

Model routing

Included
1P / SDK
1P / SDK

Evals & regression

Included
1P / SDK
1P / SDK

Agent registry & catalog

Included
You build
You build

Cost & quota controls

Included
Wire up
Included

Coverage score ≠ best choice

Platform coverage shows what ships versus what your team builds. It is one dimension, not the whole decision. Assembly burden is real, but so are platform concentration and switching cost. These platform-specific strengths often matter more than the coverage gap.

Gemini Enterprise Agent Platform

Strongest when the estate is broad, regulated, or customer-facing and the team wants one vendor to own runtime, governance, and audit — at the cost of platform concentration.

Claude Enterprise

Strongest for reasoning-heavy or sensitive workloads — complex document analysis, legal review, nuanced judgment calls. No training on your data. Assembly burden is manageable at lower scale or with existing-tool coverage.

ChatGPT Enterprise

Strongest when the organisation already has ChatGPT seats and adoption is the bottleneck. User familiarity reduces training cost. Ecosystem breadth (plugins, integrations) reduces custom build for common use cases.

Wire up = a managed service exists; shown services are what you connect, configure, and maintain. You build = no off-the-shelf option; shown services are what you build on top of. First-party / SDK = the provider ships it but your team owns deploying and operating the runtime.

03 / Customer transformation journeys

Five companies, one repeatable path to agentic transformation.

These illustrative future retrospectives show what success could look like after customers move beyond isolated pilots and standardize on Gemini Enterprise Agent Platform: a comprehensive, secure, open, and governed platform across the agent lifecycle.

The shared transformation playbook

01

Choose the right use cases

Start with journeys where better decisions, faster action, and reusable capabilities create measurable value. Avoid isolated chatbots with no path to execution.

02

Make data agent-ready

Connect trusted enterprise data, define ownership and permissions, and improve the quality of the context agents use before scaling autonomous actions.

03

Standardize on a platform

Adopt Gemini Enterprise Agent Platform as the shared foundation for models, grounding, orchestration, runtime, security, evaluation, and lifecycle operations.

04

Transform and compound

Redesign work across functions, reuse governed components, measure outcomes, and expand from individual agents into a managed enterprise agent estate.

Illustrative future story

September 2028 · Wealth management

Northstar stopped funding assistants and started rebuilding the advice journey.

Three years after standardizing on Gemini Enterprise Agent Platform, Northstar's advantage was not a single wealth agent. It was a governed system for turning research, client context, policy, and advisor judgment into better decisions.

Where the journey began

More than 30 disconnected AI pilots competed for the same data, security reviews, and advisor attention. Most summarized documents; few changed client outcomes.

Explore the underlying economics scenario

Customer 01

Northstar Private Bank

1

Use cases

Northstar prioritized advisor preparation, research synthesis, and suitability review because they shared data and improved one end-to-end client journey.

2

Data

The bank created a governed client-context layer spanning portfolios, CRM history, approved research, product policy, and entitlements.

3

Platform

Gemini Enterprise Agent Platform supplied common grounding, identity, orchestration, evaluation, audit, and release controls across every agent.

4

Transformation

Advisors moved from assembling information to reviewing recommendations, handling exceptions, and spending more time with clients.

What went well

  • One suitability policy was enforced across all advisor agents
  • Research and client context became reusable platform services
  • New advisor journeys launched without repeating security architecture

Illustrative outcomes

Faster advisor preparationMore consistent suitability reviewHigher-value client conversations
Illustrative future story

October 2028 · Retail commerce

Kanso made every customer interaction part of one intelligent commerce journey.

Kanso's breakthrough came when it stopped treating search, service, merchandising, and fulfillment as separate AI projects. The company standardized the shared context and actions behind all four.

Where the journey began

Customer-facing pilots produced impressive demos but inconsistent answers because product, inventory, loyalty, and order data were fragmented across regions and channels.

Explore the underlying economics scenario

Customer 02

Kanso Retail Group

1

Use cases

Kanso selected product discovery, order resolution, and inventory action as a connected journey with clear conversion, service, and working-capital measures.

2

Data

A governed commerce graph unified catalog, inventory, customer consent, promotions, and order state with real-time access controls.

3

Platform

Gemini Enterprise Agent Platform provided multimodal models, managed connectors, session state, model routing, autoscaling, and common policy controls.

4

Transformation

Store, service, and merchandising teams began sharing agent capabilities instead of buying separate copilots for each function.

What went well

  • One commerce context layer served customer and employee agents
  • Model routing protected experience quality while controlling unit cost
  • Reusable tools connected recommendations directly to fulfillment actions

Illustrative outcomes

More relevant discoveryFaster issue resolutionLower cost to launch new journeys
Illustrative future story

November 2028 · Healthcare

Aster scaled agentic healthcare by making trust part of the platform, not the prompt.

Aster's agent strategy accelerated only after clinical safety, human escalation, provenance, and patient consent became reusable platform capabilities available to every care journey.

Where the journey began

Clinical documentation, prior authorization, and patient navigation pilots each built their own access patterns and review processes, slowing validation and increasing risk.

Explore the underlying economics scenario

Customer 03

Aster Health Network

1

Use cases

Aster began with administrative and clinician-reviewed workflows, then expanded autonomy only where evaluation evidence and escalation paths supported it.

2

Data

The network governed access to longitudinal records, benefits, pathways, and medical knowledge through purpose-specific identity and consent policies.

3

Platform

Gemini Enterprise Agent Platform standardized grounding, safety policies, human approval, audit evidence, evaluation, and incident response.

4

Transformation

Clinical teams redesigned handoffs around exceptions and judgment while agents prepared context, coordinated tasks, and completed bounded administrative work.

What went well

  • Clinical governance was encoded once and reused
  • Every answer and action retained provenance and audit evidence
  • Autonomy increased gradually through measured safety gates

Illustrative outcomes

Less administrative burdenFaster care coordinationSafer expansion of agent autonomy
Illustrative future story

December 2028 · Government services

Aurora replaced a maze of portals with journeys organized around citizen intent.

The transformation did not begin with a universal government chatbot. It began by selecting life events where agencies could safely coordinate data, decisions, and next actions around the citizen.

Where the journey began

Residents navigated separate systems for benefits, permits, tax, and case status. Each agency had different identity, content, and automation standards.

Explore the underlying economics scenario

Customer 04

Aurora Public Services

1

Use cases

Aurora prioritized veteran benefits, small-business launch, and case-status journeys where cross-agency coordination removed repeated citizen effort.

2

Data

The program introduced a consent-aware data layer, shared service taxonomy, authoritative content sources, and agency-specific authorization.

3

Platform

Gemini Enterprise Agent Platform delivered shared identity, connectors, orchestration, policy, audit, evaluation, and release management across agencies.

4

Transformation

Agencies retained policy ownership while reusing common agent services, enabling citizen journeys to cross organizational boundaries without erasing accountability.

What went well

  • Citizen intent replaced agency structure as the journey design principle
  • Shared controls shortened review for each new service
  • Auditability and human appeal paths remained visible by design

Illustrative outcomes

Fewer repeated submissionsFaster service completionConsistent cross-agency governance
Illustrative future story

January 2029 · Manufacturing

ForgeWorks turned plant knowledge into a governed operating system for frontline decisions.

ForgeWorks created value when maintenance, quality, planning, and safety agents began sharing the same operational context and controls across plants rather than remaining local experiments.

Where the journey began

Individual plants built promising copilots, but equipment taxonomies, maintenance histories, safety policies, and integration patterns differed by site.

Explore the underlying economics scenario

Customer 05

ForgeWorks Industries

1

Use cases

The company chose quality disposition, maintenance triage, and production recovery because they shared machine context and had measurable downtime and yield outcomes.

2

Data

ForgeWorks standardized asset identity, telemetry meaning, work-order history, operating procedures, and data-quality ownership across plants.

3

Platform

Gemini Enterprise Agent Platform provided multimodal grounding, agent coordination, managed runtime, safety controls, observability, and deterministic rollback.

4

Transformation

Frontline teams received contextual recommendations while engineers governed reusable skills that could be certified once and deployed across facilities.

What went well

  • Plant-specific data mapped to a common operational model
  • Safety boundaries remained consistent as agents scaled
  • Reusable agent skills spread improvements between facilities

Illustrative outcomes

Faster fault resolutionMore consistent quality decisionsQuicker replication across plants

04 / Delivery stacks

One platform. Three advantages.

An integrated stack isn't just cheaper to run — it ships faster, gives you tighter control, and scales securely without wiring together multiple vendors.

Quicker delivery

Skip the integration sprint. Models, runtime, context, and ops ship together — go from build to production in weeks, not quarters.

Tighter control

Policy, audit, identity, and approval live in one control plane. No drift between systems, no gaps at integration seams.

Scale & security

Unified autoscaling, sandboxing, and compliance across every agent — not bolted on per-service after the fact.

Integrated platform

Gemini Enterprise Agent Platform

Models + routing
Context + tools
Runtime + scale
Trust + policy
Evals + ops

One vendor. One control plane. Unified governance from day one.

Assembled stack

e.g. Claude Enterprise, OpenAI APIs

Model API
wire + test integration
Cloud runtime
wire + test integration
Context / RAG
wire + test integration
Trust tooling
wire + test integration
Ops / FinOps

Multiple vendors. Multiple seams. Each integration gap is yours to own, test, and operate.

05 / Decision guide

What are the platform components that matter most in your decision?

Platform fit comes down to which production capabilities your team is willing to own versus which need to ship out of the box.

Decision brief

Gemini Enterprise Agent Platform is the strongest fit for this estate

This estate's exposure and autonomy profile rewards a managed production stack. Gemini Enterprise Agent Platform ships the controls your team would otherwise build — runtime, governance, audit, and escalation all covered before the first agent goes live.

Economic driver

Integration and operating labor dominate total cost at enterprise scale — a managed stack reduces both.

Architecture driver

Customer-facing agents require consistent isolation, audit trails, and escalation paths — shared controls are structurally simpler than assembling equivalent guarantees per-agent.

Tradeoff

Lower assembly effort, with platform concentration, metered services, and switching cost.

Runner-up

Assembled stackwhen assumptions move

What could flip the answer

  1. 1High existing-tool coverage significantly reduces the assembly burden of an alternative approach.
  2. 2A meaningfully lower engineering cost base changes the build-vs-buy calculus on integration work.
  3. 3A very contained estate with simple, bounded agents may not need the full managed stack.