How I AI

Build your own company brain: the enterprise AI playbook from Stripe’s engineering team | Sharadh Krishnamurthy

· Summarized

Share this episode
Anyone with this link can open it.
Share Link
Start at 0:00

Key takeaways

  • Stripe built Kai from scratch to meet their specific enterprise needs, focusing on governance, security, and contextual awareness.
  • A layered, systemic approach to infrastructure, including resilient data warehouses and tiered data access, is critical for enabling scalable, safe AI queries.
  • Using 'projects' as a governance mechanism allows for controlled, purpose-specific AI workflows, with tool policies and human-in-the-loop safeguards.
  • The platform democratizes data and automation for non-technical users, enabling collaborative data visualization and workflow packaging.
  • Successful deployment relies on leveraging existing data platforms, cultural buy-in, and continuous iteration.
  • Enterprise AI systems should include telemetry, quality assessments, and maintenance policies to ensure relevance and safety over time.

Summary

Introduction to Stripe's Internal AI Initiative: Kai

The episode begins with Sharadh Krishnamurthy introducing himself and explaining Stripe's motivation behind building Kai, their internal AI agent. Stripe aimed to create an AI system that would serve over 10,000 employees weekly, built from scratch rather than bought off-the-shelf, to tailor governance, context-awareness, and security to enterprise needs. The discussion highlights the importance of infrastructure, governance, and embedding AI deeply into organizational workflows, emphasizing that their approach leverages their existing investments in developer experience and data infrastructure.

Design Principles and Infrastructure of Kai

The conversation delves into the technical architecture of Kai, including its context-awareness—knowing who the user is and their organizational role—and its integration with Stripe’s core systems to ensure safe, scalable queries. Key investments in resilience at the data layer, comprehensive data cataloging, and tiered access are emphasized. These foundational elements allow Kai to perform high-volume queries safely while enabling flexible, user-controlled access and privacy management. The importance of infrastructure hardware, such as load shedding and failure mode mitigation, is also discussed, illustrating the depth of engineering effort behind Kai.

Governance, Projects, and Tool Policies in Kai

A major focus is on how Stripe uses 'projects' as a governance layer—defining boundaries, permissions, and safety controls—rather than simply organizing workflows. Projects allow specific tool policies, such as restricting access to sensitive data or requiring human approval for certain actions. This setup ensures safe automation, especially when dealing with confidential information. Sharadh emphasizes how this layered, purpose-built management keeps AI safe and aligned with enterprise policies, enabling more bespoke, scalable usage of AI across varied business units.

Practical Demonstrations and Capabilities of Kai

The episode features live demos showing how Kai is used for creating dashboards, iterating on data visualizations, and packaging workflows into reusable skills. These examples illustrate how non-technical users can collaborate with Kai through multi-turn conversations, turning simple prompts into complex data artifacts like dashboards and insights. The platform's UI and management layers support editing, sharing, and evaluating skills, making it accessible to teams beyond technical experts. This demonstrates Stripe’s goal of democratizing AI-powered productivity tools.

Deployment, Adoption, and Scalability of Kai

Stripe’s lean team managed to deploy Kai rapidly—within a few weeks with less than 10 people—initially through internal enthusiasm and gradual expansion. The episode discusses strategies for encouraging organic adoption across teams, the importance of infrastructure investments in enterprise AI, and how to manage a large library of skills with telemetry, quality assessments, and deprecation policies to keep the system current and efficient. Sharadh notes that the success of Kai is rooted in their pre-existing data and developer platforms, which provide the leverage for AI integration.

Reflections and Future Outlook

Closing remarks touch on lessons learned from building Kai, including the need for continuous iteration and improvement. Sharadh acknowledges that they are still in early days of enterprise AI development, with many challenges ahead. The episode ends with personal insights from Sharadh about his own AI use, including using Kai as a personal assistant and for entertaining his children’s questions about the universe and dinosaurs. He advocates for gentle prompting and respectful human-AI interaction, emphasizing that the enterprise tools require ongoing evolution.

Sponsors

  • DX · Engineering intelligence for the AI era
  • Hyperagent · Deploy fleets of agents that handle real work

Show notes

Sharadh Krishnamurthy is an engineering manager at Stripe, where he helped build Kai, the company’s internal AI agent used by more than 10,000 employees every week. He’s worked across several of Stripe’s core infrastructure teams, including data and developer experience, which gives him a grounded, systems-level perspective on what it actually takes to make AI work at enterprise scale. He’s currently focused on the governance, skills, and infrastructure layers that let every Stripe employee use AI safely and effectively, regardless of their technical background.


What you’ll learn:

  1. Why Stripe built Kai from scratch instead of buying, and what tipped the decision
  2. What Kai knows about you by default and what you actually control
  3. Why “projects” at Stripe are a governance mechanism, not just a folder
  4. How Stripe structured its data layer so agents can query safely at scale
  5. Why the infrastructure Stripe built for human developers turned out to be exactly what agents needed
  6. How Kai’s skills platform lets any employee package a workflow, and what happens when you have 2,000 of them
  7. What Sharadh learned the hard way when agents nearly took down production systems

—

Brought to you by:

DX—Engineering intelligence for the AI era

Hyperagent—Deploy fleets of agents that handle real work

—

In this episode, we cover:

(00:00) Introducing Sharadh

(02:46) Why Stripe built an AI agent (Kai) instead of buying tools

(05:18) What Kai knows about you (and what you can turn off)

(06:51) Projects as a governance layer

(10:04) Live demo: Kai builds a dashboard

(12:18) Tools, skills, and the secure sandbox

(17:22) Why Stripe has benefited so much from AI

(19:20) Agentic identity, load shedding, and rogue agents

(20:41) Iterating on the dashboard

(25:01) How they rolled out Kai across the team

(29:07) How projects work

(34:18) Bespoke agents for bespoke use cases

(35:58) The skill builder workflow

(40:40) Skill quality, evals, and telemetry

(43:01) Recap

(45:13) Lightning round

—

Tools referenced:

• Trino: https://trino.io/

• Anthropic: https://www.anthropic.com/

• Gemini: https://gemini.google.com/

• Cursor: https://www.cursor.com/

—

Where to find Sharadh Krishnamurthy:

LinkedIn: https://www.linkedin.com/in/sharadhk

—

Where to find Claire Vo:

ChatPRD: https://www.chatprd.ai/

Website: https://clairevo.com/

LinkedIn: https://www.linkedin.com/in/clairevo/

X: https://x.com/clairevo

—

Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email [email protected].

Follow this show on AudioBrevity and new episodes get summarized for you. Create a free account

Couldn't load the audio. A blocker may be stopping the show's tracking links. Open the file