Who Pays for Agentic AI?

The enterprise budget problem no vendor will address — where vendor architecture visions clash with organizational reality.

By Derek du Preez · diginomica · January 16, 2026

Enterprise IT investment budget concept
Enterprise IT investment — Song_about_summer / Shutterstock

The Central Problem

Vendors pitch beautiful three-tier agentic AI architectures, but no organizational structure maps to funding them. Three stakeholder groups are stuck:

Data Teams

CDO / CIO

Funded from analytics budgets. Measured on data quality and cost efficiency. Don't own user-facing experiences. Can't justify cross-system spend.

App Owners

Departmental Buyers

Control budgets for Salesforce, Workday, SAP. Measured on domain-specific efficiency. Won't fund cross-system infrastructure for other departments.

Enterprise IT

Company-Wide Remit

Can mandate standards but isn't the budget holder for departmental apps. Told to enable agility, not control it.

The Three-Tier Architecture

The emerging enterprise AI stack everyone is selling — but few have deployed in production.

AI Agent Layer

Natural language understanding, orchestration, workflow execution

Context Layer

Semantically Harmonized Information

Systems of Record

Authoritative Operational Data

The Core Debate

Jon Reeddiginomica

Transactional Systems Retain Value

They own the system of record, workflow execution, integration infrastructure, and user relationships. The future is omni-engagement with transactional systems across multiple interfaces including AI. Verification always links back to authoritative systems.

Filip MisovskiSemos Cloud CEO

Reality Is Messier

Enterprises are deploying Snowflake/Databricks as central hubs with specialized AI agents on top. Sales people interact with agents that pull data from the platform and update Salesforce via API — reducing systems of record to data endpoints.

Orchestration Layer Competition

Multiple vendors competing to own the agent orchestration space — each with different organizational advantages.

Microsoft

Copilot Strategy

Horizontal layer spanning all systems via M365 ubiquity. Challenge: building something that works well enough across vastly different systems.

Salesforce

Agentforce Strategy

Enterprise agent platform leveraging customer-facing workflow ownership. Challenge: convincing enterprises a CRM vendor should own company-wide agent strategy.

ServiceNow

Cross-Functional Strategy

Strong cross-functional workflows and integration infrastructure. Challenge: expanding beyond IT and operations into broader enterprise work.

Vertical Platforms

Domain Expertise

SAP, Oracle, Workday building own agent capabilities with deep ecosystem integration. Challenge: credibly orchestrating beyond their domains.

The Decisive Factor: Governance

Why Governance Wins

In regulated industries — financial services, healthcare, pharma — agents must work through governed systems, not around them. Transactional systems already have battle-tested audit trails, role-based access control, data residency, and compliance certifications. When the CISO gets involved, they trust vendors who've passed security reviews — not startups with clever agents.

Value Capture Dynamics

Risk

Data Platforms → Cost Center

Essential infrastructure facing pricing pressure. Try explaining to the CFO why the data warehouse bill went up 40% to 'enable other teams' AI strategies.' AWS built an empire as infrastructure — can Snowflake and Databricks do the same?

Advantage

Application Layers → Value Capture

Direct user relationships, measurable productivity gains, clear business outcomes. Salesforce can charge for Einstein features that improve sales productivity. ServiceNow can justify agents based on reduced ticket resolution time.

Frequently Asked Questions

No single group clearly owns the budget. Data teams lack operational transformation budgets, departmental application owners won't fund cross-system infrastructure, and enterprise IT is told to enable agility rather than control it.
Transactional systems at the bottom hold authoritative data. Data platforms in the middle unify data and provide AI context. AI agents at the top understand natural language, pull context, and execute workflows through transactional systems.
Data platforms report to CDO/CIO with analytics budgets. Transactional apps are owned by departmental buyers with separate budgets. Enterprise IT has company-wide remit but isn't the budget holder. No structure maps to cross-system funding.
They own the system of record, workflow execution, integration infrastructure, and user relationships. Verification always links back to authoritative systems. The future is omni-engagement across multiple interfaces including AI.
Platforms like Coupa, SAP Ariba, and Blue Yonder are complete systems with own data layers, analytics, workflow engines, and AI. They're not lightweight apps reducible to API endpoints for horizontal agent layers.
Data platforms risk becoming essential but commoditized cost-center infrastructure. Application layers capture value through direct user relationships, measurable productivity gains, and clear business outcomes.
Regulated industries need audit trails, access controls, data residency, and explainability. Transactional systems have these battle-tested and auditor-approved. Agents must work through governed systems. CISOs trust vendors who've passed security reviews.
Most enterprises still use the same applications. New data platforms support uncoordinated departmental AI initiatives. The architectural vision is aspirational. Vendors are garden-walling their AI deployments.

Glossary

TermDefinition
Agentic AIAI systems capable of autonomous decision-making and workflow execution across enterprise systems
System of RecordAuthoritative transactional systems where workflows execute, audit trails live, and compliance happens
Three-Tier ArchitectureThe emerging AI stack: transactional systems, data platforms, and AI agents
Orchestration LayerMiddleware where AI agents coordinate actions across multiple enterprise systems
UnbundlingDecomposition of monolithic systems of record into specialized layers
Data PlatformUnified data infrastructure aggregating data from transactional systems for AI context
Vertical PlatformDomain-specific integrated platforms combining data, analytics, workflows, and AI
Omni-EngagementUsers interact with transactional systems through multiple interfaces while the system of record remains central
Cost Center ThinkingRisk that data platforms are viewed as essential but commoditized infrastructure
Garden WallingVendor strategy of closing AI deployments within their ecosystem for maximum lock-in

Guidance: 7-Step Evaluation Framework

A structured approach for CIOs and technology decision makers to navigate the organizational and commercial complexities of agentic AI deployment.

  1. 1

    Map your current architectural landscape

    Inventory all transactional systems, data platforms, and AI tools. Identify authoritative data sources and actual user interfaces.

  2. 2

    Identify budget ownership for each layer

    Map who controls data platform, application, and IT budgets. Document the gap between cross-system vision and siloed authority.

  3. 3

    Assess governance and compliance requirements

    Determine audit trail, access control, and data residency needs. Engage CISO and compliance officers early.

  4. 4

    Evaluate vendor claims against production reality

    Ask for cross-system demos with error handling, audit trails, and approval chains. Most can't deliver yet.

  5. 5

    Determine where value should accrue

    Assess whether data platforms will be strategic or cost-center in your context. Evaluate application-layer ROI.

  6. 6

    Plan for multiple coexisting orchestration layers

    Accept that Copilot, Salesforce, ServiceNow, and vertical platforms will coexist. Design integration points.

  7. 7

    Avoid architectural lock-in without alignment

    Start with departmental wins, build cross-functional governance, evolve toward enterprise-wide coordination incrementally.

Explore with SPARQL

Query the knowledge graph directly. Each query is scoped to this document's named graph.

1 Entity type counts
PREFIX schema: <http://schema.org/>
SELECT (COUNT(*) AS ?count) (?o AS ?EntityTypeID)
FROM <https://linkeddata.uriburner.com/dav/home/demo/docs/diginomica-agentic-ai-enterprise-budget-qwen37-max-1.ttl>
WHERE { ?s a ?o . }
GROUP BY ?o
ORDER BY DESC(?count)
Run query
2 FAQ questions and answers
PREFIX schema: <http://schema.org/>
SELECT ?q ?question ?answer
FROM <https://linkeddata.uriburner.com/dav/home/demo/docs/diginomica-agentic-ai-enterprise-budget-qwen37-max-1.ttl>
WHERE {
  ?q a schema:Question ;
     schema:name ?question ;
     schema:acceptedAnswer ?a .
  ?a schema:text ?answer .
}
ORDER BY ?question
Run query
3 Organizations and strategic positions
PREFIX schema: <http://schema.org/>
SELECT ?org ?name ?position
FROM <https://linkeddata.uriburner.com/dav/home/demo/docs/diginomica-agentic-ai-enterprise-budget-qwen37-max-1.ttl>
WHERE {
  ?org a schema:Organization ;
       schema:name ?name .
  OPTIONAL {
    ?org <https://diginomica.com/who-pays-agentic-ai-enterprise-budget-problem-no-vendor-will-address#hasStrategicPosition> ?position .
  }
}
ORDER BY ?name
Run query
4 HowTo guidance steps
PREFIX schema: <http://schema.org/>
SELECT ?step ?name ?pos
FROM <https://linkeddata.uriburner.com/dav/home/demo/docs/diginomica-agentic-ai-enterprise-budget-qwen37-max-1.ttl>
WHERE {
  ?step a schema:HowToStep ;
        schema:name ?name ;
        schema:position ?pos .
}
ORDER BY ?pos
Run query
5 All triples (sample 100)
SELECT DISTINCT ?s ?p ?o
FROM <https://linkeddata.uriburner.com/dav/home/demo/docs/diginomica-agentic-ai-enterprise-budget-qwen37-max-1.ttl>
WHERE { ?s ?p ?o . }
LIMIT 100
Run query

Knowledge Graph Explorer

Interactive force-directed graph. Click nodes to open entity descriptions. Drag to reposition. Scroll to zoom. Double-click to pin.

Settings

Physics Simulation

-300
100

Predicate Display

Labels
Icons

Edge Filtering

Node Filtering

Literal Text Filter

Resolver Preference

Arrow Style

Dual Arrows
Single Arrow

Legend

Class
Property
Instance