Skip to main content
a16z Podcast

AI Agents and the Fight for Customer Data

50 min episode · 2 min read
·

Episode

50 min

Read time

2 min

Topics

Artificial Intelligence, Science & Discovery

AI-Generated Summary

Key Takeaways

  • Data foundation for AI agents: Companies do not need exotic new infrastructure to support AI agents. Existing modern data platforms — Snowflake, Databricks, or BigQuery — already serve as effective context layers for agents. Even Anthropic and OpenAI, both Fivetran customers, use standard centralized data lake architectures identical to traditional enterprises.
  • SaaS API lockdown response: When vendors like SAP restrict data access, CIOs should push back contractually. Fivetran publishes model MSA language at opendatainfrastructure.com that guarantees data portability rights. For contracts above $500k, explicitly negotiating data access clauses into MSAs yields results surprisingly often, even without legal escalation.
  • Data gravity is overstated: The belief that massive egress costs make data movement prohibitive is largely a myth created by poorly designed pipelines that copy entire datasets nightly. Change data capture replicates only incremental updates, making actual data transfer volumes across thousands of enterprise customers far smaller than conventional wisdom assumes.
  • AI agents as enterprise employees: Treating AI agents like human employees — giving them dedicated email addresses, phone numbers, Slack seats, and HR onboarding — proves more practical than building headless API-only systems. This approach slots agents into existing human-designed workflows without requiring companies to rebuild underlying systems from scratch.
  • SaaS-pocalypse is misdiagnosed: The real threat to incumbent SaaS companies is not AI replacing software categories wholesale. Software costs represent only 5–10% of enterprise headcount spend, making seat reduction an irrelevant optimization target. The actual risk is AI-native startups building equivalent products faster and potentially outcompeting incumbents on quality.

What It Covers

Fivetran CEO George Fraser and a16z's Martin Casado examine how AI agents are reshaping enterprise data infrastructure, why SaaS vendors like SAP are locking down API access, whether the "SaaS-pocalypse" is real, and how companies should structure data foundations to support agentic workflows.

Key Questions Answered

  • Data foundation for AI agents: Companies do not need exotic new infrastructure to support AI agents. Existing modern data platforms — Snowflake, Databricks, or BigQuery — already serve as effective context layers for agents. Even Anthropic and OpenAI, both Fivetran customers, use standard centralized data lake architectures identical to traditional enterprises.
  • SaaS API lockdown response: When vendors like SAP restrict data access, CIOs should push back contractually. Fivetran publishes model MSA language at opendatainfrastructure.com that guarantees data portability rights. For contracts above $500k, explicitly negotiating data access clauses into MSAs yields results surprisingly often, even without legal escalation.
  • Data gravity is overstated: The belief that massive egress costs make data movement prohibitive is largely a myth created by poorly designed pipelines that copy entire datasets nightly. Change data capture replicates only incremental updates, making actual data transfer volumes across thousands of enterprise customers far smaller than conventional wisdom assumes.
  • AI agents as enterprise employees: Treating AI agents like human employees — giving them dedicated email addresses, phone numbers, Slack seats, and HR onboarding — proves more practical than building headless API-only systems. This approach slots agents into existing human-designed workflows without requiring companies to rebuild underlying systems from scratch.
  • SaaS-pocalypse is misdiagnosed: The real threat to incumbent SaaS companies is not AI replacing software categories wholesale. Software costs represent only 5–10% of enterprise headcount spend, making seat reduction an irrelevant optimization target. The actual risk is AI-native startups building equivalent products faster and potentially outcompeting incumbents on quality.

Notable Moment

Fraser argues that Postgres, despite its widespread adoption, is fundamentally outdated technology burdened by decades of technical debt. He contends that database storage engines written by undergraduates in academic courses outperform Postgres architecturally — and that the industry needs an entirely new operational database built from scratch.

Know someone who'd find this useful?

You just read a 3-minute summary of a 47-minute episode.

Get a16z Podcast summarized like this every Monday — plus up to 2 more podcasts, free.

Pick Your Podcasts — Free

Keep Reading

More from a16z Podcast

We summarize every new episode. Want them in your inbox?

Similar Episodes

Related episodes from other podcasts

Explore Related Topics

This podcast is featured in Best Business Podcasts (2026) — ranked and reviewed with AI summaries.

Read this week's AI & Machine Learning Podcast Insights — cross-podcast analysis updated weekly.

You're clearly into a16z Podcast.

Every Monday, we deliver AI summaries of the latest episodes from a16z Podcast and 192+ other podcasts. Free for up to 3 shows.

Start My Monday Digest

No credit card · Unsubscribe anytime