DevRev
Enterprise Context Layer · Warner Bros. Discovery

Building an enterprise context layer on your data lake

How DevRev connects Snowflake, SAP, ServiceNow, and Oracle into one intelligence surface for instant insight.

Computer × WBD
June 2026
What's inside

Overview of this document

Following our conversation, here's a comprehensive view of the platform, architecture, and a production case study for your team's review.

01

Platform architecture

How Computer connects to enterprise systems, builds context, and reasons across data — without importing it.

02

Production case study

India's largest airline — a 38-skill agent orchestrating payments, rebooking, and operations across 4 enterprise systems in real-time.

03

Your use cases

How the same pattern applies to WBD — content analytics, vendor intelligence, and finance self-serve via Snowflake, SAP, and ServiceNow.

04

Proposed next steps

A concrete 4-week POC path — from scope alignment to live validation.

For your team

This deck is designed to be self-contained — share internally with stakeholders who need the technical context.

The challenge today

Data is everywhere — insight is nowhere

Your data team navigates 10+ systems to answer one business question. That shouldn't take days.

Pain point

Fragmented data

Business intelligence spread across Snowflake, SAP, ServiceNow, Oracle ERP, and documents — no unified view.

Pain point

Manual insight generation

CFO needs content ROI numbers? That means navigating 4 dashboards, 3 applications, and a week of analyst time.

Pain point

Trapped knowledge

Vendor MSAs, SOWs, contracts, and RFPs hold critical intelligence but aren't searchable or analyzable at scale.

What if one intelligent layer could sit above all your data and answer any question in seconds?

The platform

Data in. Intelligence out. Decisions accelerated.

Computer unifies your systems into one permission-aware memory, then reasons and acts across all of it — governed, observable, auditable.

YOUR DATA, FLOWING IN Snowflake data lake & analytics SAP + Oracle ERP financials & procurement ServiceNow IT ops & workflows Docs & contracts MSAs, SOWs, RFPs + 50 connectors · AirSync (2-way) COMPUTER · THE CORE AirSync · Memory · NL-to-SQL Permission-aware context, assembled before the AI thinks Governed · Observable · Auditable WHAT YOUR TEAMS GET Natural-language answers ask in English, get cited multi-source results Cross-system analytics content ROI, vendor spend, franchise perf. Automated reports & actions scheduled or on-demand, multi-source
Ready to connect Planned
Same model · same question Memory does the work, so the LLM doesn't
Other AI · fetches all 3.2M
Computer · sends only signal 157K
Memory filters & joins in SQL before the LLM sees the data — 95% fewer tokens, 5.5× faster, and the gap widens as your data scales.
Your use cases

Three problems, one context layer

Each maps directly to DevRev Computer's capabilities — no custom development required.

01 Invoice automation

Email → invoice generation

Email arrives with vendor request → agent looks up opportunity in Salesforce, pulls contract terms from SAP/Ariba, generates invoice — no manual data gathering.

Example: "Process invoice request from vendor email — pull PO from Ariba, match to SAP contract, generate and route for approval."
Email-triggered workflow
02 Cross-system context

Opportunity enrichment across 5 ERPs

Query a Salesforce opportunity and get meeting transcripts, OneDrive attachments, Ariba procurement history, and Workday team data — unified context without ETL.

Example: "For this deal, show me all related contracts in SAP, recent meetings, and the approval chain from Workday."
Metadata orchestration
03 Vertical agents

Shared context layer for all agents

Multiple vertical agents (SAP-native, Salesforce-native, Ariba) can query one gold-standard context layer — no duplicated integrations, shared knowledge across teams.

Example: "Finance agent asks: 'What's the total vendor spend with Deloitte?' — pulls from SAP, Ariba, and contract store in one call."
Universal context API
Case study · Live in production

India's largest airline — Customer Payment Desk Agent

A fully agentic system orchestrating across 4 enterprise systems via API calls — no data imported into a knowledge graph. Pure context engineering.

38

Skills orchestrated by a single agent

5-10m

Avg handle time (down from 30-45 min manual)

4

Enterprise systems connected via real-time APIs

<5%

Error rate (down from 15-20% manual process)

Key insight

The agent uses ticket fields as session state, skills make real-time API calls, and the LLM orchestrates the flow — no ETL, no data lake sync needed.

Architecture · Context engineering

Orchestrate without importing data

TRIGGER Ticket Created payment issue arrives COMPUTER AGENT State machine · 16+ states Case Lookup Flight Search Sell + Save Ancillary Services Fare Override Commit + Pay Hold Release Refund Verify Session: API Token · PNR · OrderID · flags SKILLS → LIVE API CALLS Booking Engine search, book, modify, commit, ancillaries Payment Gateway links, polling, refunds, verification Booking Session History PNR / transaction details Ticketing Tool ticket lifecycle, status updates, close
Context engineering

Ticket fields store API Tokens, PNRs, order IDs — the agent never asks the human to repeat context.

No data import

Zero ETL. Every skill calls the source system's API in real-time with live credentials.

Deterministic + AI

Skills handle deterministic logic (fare math, ancillary codes); the LLM handles flow orchestration and UX.

What was built · 8 weeks

Full payment desk automation — 38 skills

Rebooking & flight search

Search, sell itinerary, save passengers, replicate ancillary services and seats — all automated across booking engine APIs.

Payment orchestration

Generate payment links, poll status, handle refund verification, fare overrides with tax calculation.

Case lifecycle

Ticket intake, status updates, email notifications, and auto-close — full loop from open to resolved.

Hold release, date mod & refund verify

Release held PNRs, modify travel dates, verify refund status by PNR or transaction, manifest lookup for lost PNRs.

How it's different
Agent reads case, decides flow, calls APIs in real-time
Ticket fields persist state — no memory loss between turns
On close, session fields flushed — zero data retention
Skills do the math — LLM orchestrates the flow
Human-in-the-loop for every critical action
No training data — works day one with APIs
How it works

Ask a question. Get a cited answer.

Computer reasons across your entire data estate — not just one database at a time.

VP, Data Platform What was the total production cost vs. revenue for the Harry Potter franchise across all channels?
Computer Based on Snowflake (content_analytics) + SAP (project_financials):
Production cost: $1.2B across 8 titles · Revenue: $7.7B theatrical + $2.1B streaming
Blended ROI: 7.2× — sourced from 2 systems
VP, Data Platform How does that compare to Spider-Man?
Computer Spider-Man (Sony co-prod): ROI 5.8× — lower due to rev-sharing, but streaming engagement 34% higher per title. Want the full comparison report?
See case study slides for a production example
Integration

Connects to your existing stack

No rip-and-replace. Computer layers on top with secure, read-only connectors.

Snowflake

Snowflake

Data lake queries, content analytics, engagement metrics

Native connector
SAP

SAP

Financials, procurement, project costs, vendor master

Native connector
ServiceNow

ServiceNow

IT operations, workflow data, request management

Native connector
Oracle ERP

Oracle ERP

Financial planning, budgets, actuals, GL data

Native connector
Also supported

SharePoint, Google Drive, Confluence (for documents) · Custom APIs via universal connector · SSO & RBAC inherited from your IdP

Proposed next steps

From here to live POC in 4 weeks

A lightweight pilot scoped to one high-value use case — proving value before broader rollout.

1

This week — align on scope

Pick 1 use case (e.g., content franchise analytics). Define 5-10 representative queries. Identify the data sources needed.

2

Week 2-3 — connect & configure

DevRev SE team connects Snowflake + one ERP source. Build the knowledge graph. Configure permissions and test queries end-to-end.

3

Week 4 — validate & expand

Your data team tests real queries. Measure time-to-insight vs. current process. Decision point: expand to additional use cases or full rollout plan.

DevRev

Let's build together.

One context layer. Every data source. Instant enterprise insight.

DevRev Team Solutions Engineering
Computer
devrev.ai
01 / 10