Sep 2, 2026 · 43m · saastr
Shipping Enterprise AI Agents with the CPOs of Rubrik, Glean, and Harvey
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
In this SaaStr panel hosted by Jason Lemkin, Chief Product Officers from Rubrik, Glean, and Harvey share practical strategies for building, governing, and monetizing enterprise AI agents. They demonstrate how deterministic guardrails, human-in-the-loop workflows, and domain-expert implementations are driving agentic adoption across cybersecurity, enterprise knowledge, and legal sectors.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Jason holds 29.8% of the talking time here. How this is scored →
speaking balance: gold is Jason, purple is the guest (3 minute bins)
When Lemkin claims corporate founders easily sign off on software whereas law partners guard their personal draws, Drumright immediately interrupts to challenge his corporate spending premise and reframes adoption around non-negotiable client expectations.
Hardest push from Jason ▶ 25:49 Lemkin pushes hard on autonomous agent liability and vendor blameLemkin refuses to gloss over governance, directly confronting Rubrik's CPO on who takes the blame when automated agents execute faulty recovery workflows in production.
Biggest teaching moment ▶ 10:50 Glean CPO explains offline organizational intelligence versus runtime MCP toolsGlean's CPO systematically educates Lemkin on why runtime protocol calls like MCP fall short of deep organizational context, which requires offline knowledge graph computation across historical company data.
Jason holds their own ▶ 18:15 Lemkin details the financial mechanics of selling software to equity partnershipsLemkin demonstrates deep insider domain knowledge of law firm economics, showing why selling seven-figure legal tech deals differs fundamentally from standard enterprise SaaS due to direct deductions from partner profit distributions.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Jason as informed peer | Guest teaching | Guest disagreement | Jason pushing back | Why |
|---|---|---|---|---|---|---|
| Rubrik: Engineering Autonomous Agents for Cyber Recovery | 6 | 5 | 1 | 2 | Lemkin shows solid familiarity with emerging AI infrastructure, specifically contrasting prompt-based search with MCP integrations and LLM memory. Glean's CPO educates the host on the architectural distinction between runtime API fetching via MCP and high-compute offline graph processing of company context. | |
| Harvey: Driving Agentic Adoption Across Elite Law Firms | 4 | 5 | 3 | 5 | Lemkin repeatedly expresses skepticism that conservative senior partners using ThinkPads are drafting and reviewing agentic prompts. Drumright pushes back politely against his characterization, explaining how top law firms use structured workflows and verification loops. | |
| The Economics of Legal Tech: Selling AI to Partnerships | 7 | 3 | 3 | 4 | Lemkin delivers an expert breakdown of law firm partnership economics, explaining how tech purchases come directly out of partner equity distributions rather than standard corporate budgets. Drumright pushes back playfully on his characterization of corporate buyers and argues that end-client pressure drives adoption. | |
| Demo: Rubrik's Ruby Agent and Deterministic Execution | 2 | 4 | 0 | 0 | Rubrik's CPO presents a detailed product demo of Ruby, explaining the shift from simple RAG to deterministic execution for cyber incident recovery. Lemkin steps back into a passive host role and allows the guest to demonstrate the technical architecture uninterrupted. | |
| Platform Governance: Accountability, Guardrails, and Systems Integrators | 6 | 4 | 2 | 6 | Lemkin presses hard on vendor accountability and enterprise liability when autonomous agents make catastrophic operational errors. Rubrik's CPO firmly defends their stance, arguing that vendors must take full responsibility and that well-guarded agents reduce human configuration errors. | |
| Demo: Glean's Revenue Operations Agent Builder | 6 | 5 | 1 | 5 | Lemkin challenges Glean on why an agent is needed when Gong natively syncs CRM fields to Salesforce, citing his own portfolio board experience with real-time win-loss agents. Glean's CPO clarifies that the agent applies nuanced executive context and sales frameworks rather than basic field dumping. | |
| Harvey: System-Wide Agent Architecture and Legal Customization | 5 | 5 | 1 | 3 | Lemkin interrogates Harvey's deployment model, probing how legal knowledge is systematized firm-wide. Drumright explains that Harvey employs dedicated pods including former practicing lawyers as legal engineers to craft bespoke firm-level playbooks. |