## Background
Published on YouTube by Ai4 on August 22, 2026, this panel session explores how AI-powered copilots and generative agents are redefining modern contact center operations. The discussion focuses on how organizations deploy automated tools for real-time recommendations, instant knowledge retrieval, and voice workflows while balancing agent productivity and customer experience.
## TL;DR
Moderated by Andy Tang, the panel contrasts the perspectives of AI founders (Bland, Maven AGI) with enterprise CX buyers (The Cigna Group, FCP Euro) on the real-world economics and architecture of contact center automation. The speakers examine why thin AI wrappers face unsustainable unit economics, arguing that true enterprise value lies in automating mission-critical, high-stakes conversations rather than building rigid deflection trees. Enterprise leaders reveal that messy legacy infrastructure and missing metadata remain the primary bottlenecks to scale, concluding that success requires disciplined, outcome-focused partnerships over software-for-software's-sake.
## Atmosphere & style
The discussion is candid, grounded, and brisk, characterized by an intentional 'providers versus buyers' seating dynamic that produces lively, unvarnished debates on enterprise AI adoption. Moving away from standard tech optimism, the conversation balances sharp skepticism about VC-subsidized AI wrappers with practical insights into the messy realities of healthcare IT and automotive parts fitment. It feels like an authentic, operator-level strategy session full of executive war stories, tactical pushback, and energetic banter that culminates in a playful rapid-fire round.
## Key takeaways
- [04:39](https://www.youtube.com/watch?v=tcijaaGmmBQ&t=279s) Enterprise AI wrappers reliant on third-party frontier LLM APIs face severe unit economic risks once venture subsidies expire, favoring providers with in-house proprietary models.
- [04:39](https://www.youtube.com/watch?v=tcijaaGmmBQ&t=279s) Customer experience (CX) and developer coding copilots represent the two primary sectors currently delivering immediate, measurable productivity ROI for enterprises.
- [08:54](https://www.youtube.com/watch?v=tcijaaGmmBQ&t=534s) True business transformation requires aligning AI with overarching enterprise architecture and fixing broken underlying processes rather than pursuing isolated 'AI for AI's sake' initiatives.
- [08:54](https://www.youtube.com/watch?v=tcijaaGmmBQ&t=534s) Enterprises should enforce cost discipline by auditing repetitive tasks first and rejecting exorbitant vendor pricing when scrappy internal builds or human reviews provide better ROI.
- [16:16](https://www.youtube.com/watch?v=tcijaaGmmBQ&t=976s) Universal consumer demand for faster, empathetic service and severe operational bottlenecks are accelerating CX AI adoption across all verticals, outpacing traditional tech adoption curves.
- [18:52](https://www.youtube.com/watch?v=tcijaaGmmBQ&t=1132s) The greatest enterprise value in voice AI lies in automating high-stakes, regulated, and complex interactions rather than settling for low-risk call deflections.
- [23:35](https://www.youtube.com/watch?v=tcijaaGmmBQ&t=1415s) Rigid interactive voice response (IVR) phone trees are being replaced by adaptive conversational AI personas, lowering phone anxiety for younger demographics like Gen Z.
- [26:07](https://www.youtube.com/watch?v=tcijaaGmmBQ&t=1567s) Slow AI adoption in complex sectors like healthcare stems primarily from deeply fragmented legacy data infrastructure and non-standardized EMRs rather than regulatory barriers.
- [30:00](https://www.youtube.com/watch?v=tcijaaGmmBQ&t=1800s) Building bespoke internal AI bots often fails due to complex multi-system actions, necessitating dynamic graph-of-record architectures to personalize interactions without tedious ETL pipelines.
- [36:09](https://www.youtube.com/watch?v=tcijaaGmmBQ&t=2169s) Resolving missing enterprise metadata requires a combination of AI-driven synthetic generation and rigorous human-in-the-loop validation before models ingest data.
- [37:51](https://www.youtube.com/watch?v=tcijaaGmmBQ&t=2271s) Enterprises buy outcomes rather than software, shifting AI vendors toward a high-touch Palantir-style consultative model where providers co-build missing data architecture.
- [39:34](https://www.youtube.com/watch?v=tcijaaGmmBQ&t=2374s) Combating executive 'AI psychosis' and scope creep demands strict discipline to master one core domain, such as the contact center, before expanding to secondary digital touchpoints.
- [41:01](https://www.youtube.com/watch?v=tcijaaGmmBQ&t=2461s) Enterprise CX leaders and AI founders unanimously favor open-source model architectures over closed proprietary systems for long-term enterprise sustainability.
## Detailed walkthrough
### [00:04](https://www.youtube.com/watch?v=tcijaaGmmBQ&t=4s) Seating Arrangements, Customer Service Roots, and Panel Introductions
Moderator Andy Tang kicks off the panel by drawing attention to the deliberate seating arrangement: two enterprise customers sitting opposite two AI founders. The dynamic is immediately clear to everyone in the room—"We're all pitching to these guys. That's where the money, the demands are." Tang shares a personal story about why he chose to moderate this specific panel despite normally focusing on other venture sectors. When his summer analyst class of six interns asked for career guidance, he advised every single one of them to get a job in customer service or restaurant waitstaff, emphasizing that front-line service is an essential life and business skill rather than just a way to pay for college.
```mermaid
flowchart LR
accTitle: Panel Composition and Roles
subgraph AI_Founders["AI Technology Providers"]
direction TB
B["Isaiah Granet<br/>CEO, Bland"]
M["Jonathan Corbin<br/>CEO, Maven AGI"]
end
subgraph Enterprise_Buyers["Enterprise CX Leaders"]
direction TB
C["Kirby Forlin<br/>SVP Digital & Analytics, Cigna"]
F["Alejandro Villacis<br/>VP CX, FCP Euro"]
end
AI_Founders <-->|"Pitching & Automating vs. Buying & Evaluating"| Enterprise_Buyers
```
The panelists introduce themselves and outline their respective footprints in the contact center and CX landscape:
- **Isaiah Granet** (Co-founder & CEO, Bland): Bland automates high-stakes, highly complex phone calls end-to-end—focusing on mission-critical conversations where "if we get it wrong, someone's going to sue or die." Bland builds all its models in-house, recently launched an industry-leading text-to-speech model, has raised over $100 million, and supports 250 enterprise clients alongside 350,000 self-serve users.
- **Jonathan Corbin** (Co-founder & CEO, Maven AGI): Maven AGI builds generative AI agents for enterprise customer experience. The company employs roughly 100 people, has raised around $78 million, and serves about 100 enterprise customers, including Dell, Hinge, and Hard Rock.
- **Kirby Forlin** (SVP of Digital, Data, and Analytics, The Cigna Group): Approaching the panel from a digital healthcare perspective, Forlin focuses on unifying customer context across digital applications and call centers so human agents and digital touchpoints share identical, real-time information.
- **Alejandro Villacis** (VP of Customer Experience, FCP Euro): Representing a 40-year-old family-owned European automotive parts business (online for 25 years), Villacis upholds the brand ethos: "if we wouldn't put the part on our cars, we wouldn't sell it to our customers." Over the past year, FCP Euro has integrated AI into its contact center to eliminate rote work and redirect agent time toward revenue generation and retention.
---
[04:39](https://www.youtube.com/watch?v=tcijaaGmmBQ&t=279s) The AI Bubble, Unit Economics, and Macro Reality
Andy Tang reflects on his 20 years in early-stage venture capital, recalling how Isaiah was turned down by 198 investors after Y Combinator in 2023 because VCs claimed audio was dead and "nobody will be doing phone calls a year from now." Tang also jokes about seeding Otter.ai in a Palo Alto cafe back in 2015 despite initially thinking recording all global audio was both "creepy" and unrealistic. When Tang asks whether the current AI economic cycle is fundamentally different from past tech bubbles, Granet answers bluntly: "No."
Granet warns that companies sporting higher valuations than Walmart while operating on fragile unit economics signal an unsustainable market. He points out that Bland made the deliberate, difficult decision to build in-house models rather than rely on frontier LLM APIs, anticipating that AI will follow the path of Uber: once venture-funded subsidy periods end, companies lacking sound gross margins and true architectural fundamentals will face severe trouble.
Jonathan Corbin offers a complementary view, acknowledging that while private market valuations may be inflated, the macro productivity impact is real. While previous technological shifts took 5 to 10 years to reach full enterprise maturity, generative AI adoption in customer experience and software engineering is moving faster than any prior technology cycle.
- **198 VC rejections**: The number of investor rejections Bland received post-YC due to prevailing skepticism around voice-based AI.
- **The subsidy trap**: The risk that enterprise AI wrappers reliant on third-party frontier models will collapse once introductory API pricing subsidies expire.
- **Micro traction hubs**: Customer experience (CX) and developer coding assistants remain the two primary arenas delivering immediate, measurable ROI.
---
[08:54](https://www.youtube.com/watch?v=tcijaaGmmBQ&t=534s) Strategic Transformation vs. "AI for AI's Sake"
Kirby Forlin diagnoses a major pitfall across legacy, non-digitally native enterprises: treating AI as an isolated initiative rather than aligning it with overall business strategy. Many organizations purchase duplicative tools and automate existing workflows without fixing fundamentally broken underlying processes. While individual productivity tools like Claude Opus allow executives to draft slide presentations in seconds and free up strategic thinking time, Forlin emphasizes that slide generation is not fundamental business reinvention. True transformation requires enterprise architecture discipline and strategic alignment between business leaders and technologists.
```mermaid
flowchart TD
accTitle: FCP Euro Pragmatic AI Adoption Framework
A["Identify CX Bottlenecks"] --> B{"Evaluate Internal Tools First"}
B -->|"Leverage Existing Tech"| C["Internal Data & Tool Utilization"]
B -->|"Assess External Vendors"| D["Vendor Cost-Benefit Analysis"]
D --> E{"Exorbitant TCO?<br/>(e.g., $100k base fees)"}
E -->|"Yes"| F["Reject Flashy Vendor / Build Scrappy"]
E -->|"No"| G["Controlled Deployment for High-Value ROI"]
```
Alejandro Villacis details how FCP Euro approaches AI adoption with extreme cost discipline. After their software engineering team successfully adopted coding copilots, customer experience followed three to six months later with a deliberate roadmap:
1. **Repetitive Task Elimination**: Auditing and prioritizing routine support tasks to automate or streamline agent workflows.
2. **Conversation Analysis**: Extracting intelligence from customer interactions after transcribing all voice calls over the preceding 18 months.
3. **Vendor Pricing Reality Checks**: Rejecting vendors offering unproven call-analysis tools with $100,000 baseline fees plus per-interaction charges. Villacis notes that paying more for experimental call analysis than for their entire warehouse management system (WMS) or web hosting infrastructure on AWS makes zero financial sense when human review remains cheaper.
---
[16:16](https://www.youtube.com/watch?v=tcijaaGmmBQ&t=976s) Regulatory Friction and the Universal Demand for Better CX
Tang poses a question regarding industry adoption curves, observing that past waves like the internet spread first through communication, retail, and enterprise software before reaching heavily regulated sectors like financial services, healthcare, and government. He asks whether AI is adhering to the same regulatory friction patterns, specifically referencing healthcare compliance and HIPAA.
Corbin challenges the historical premise with a laugh, noting that the government originally funded the internet. Turning to enterprise reality, Corbin argues that customer experience adoption is outpacing traditional adoption curves across every vertical because poor service is an urgent, universal pain point. Whether a customer is experiencing a frustrating hotel check-in or waiting a year for an appointment to evaluate a basketball knee injury, consumers and enterprises alike are demanding lower-cost, responsive, and reliable communication channels.
[18:52](https://www.youtube.com/watch?v=tcijaaGmmBQ&t=1132s) Consumer Pressure, Operational Scale, and High-Stakes Phone Calls
Jonathan Corbin explains that the push for enterprise AI adoption comes from both sides: intense consumer demand for better interactions and severe operational bottlenecks inside scaling organizations. Drawing on his background at customer experience market leaders like Adobe, Marketo, and HubSpot, Corbin notes that HubSpot dealt with 220,000 companies and hundreds of millions of people attempting to contact support—a volume impossible to staff with human agents alone. Achieving fewer people while handling dramatically more interactions creates a compelling business case even across heavily regulated spaces, especially as platforms systematically complete compliance playbooks like HIPAA certification and FedRAMP authorization.
```mermaid
flowchart LR
accTitle: High-Stakes Voice AI Routing
A["Caller in Crisis / Patient"] --> B["Bland Voice AI Engine"]
B --> C["Detect Vital Reading / Emergency"]
B --> D["Identify High-Risk Foreign Survey Data"]
C --> E["Dispatch to Hospital / First Responders"]
D --> F["Secure Data / Protect Citizens"]
```
Isaiah Granet responds to the discussion around high-risk, regulated calls by sharing real-world examples from Bland. Their AI handles 45-minute remote patient monitoring sessions with individuals over 90 years old, guiding them through finding and placing blood pressure cuffs, checking readings, and diagnosing whether an anomaly is an actual medical emergency or just a loose strap—all while casually chatting about their grandchildren to keep them engaged. Bland also conducts polling and surveys in volatile foreign countries where data falling into authoritarian government hands could result in door-to-door arrests. Granet argues that the inverse of conventional wisdom is true: the deepest enterprise value is not low-risk deflections, but automating difficult, regulated, and critical calls that contact centers have spent thirty years failing to eliminate via clunky IVRs and call-deflection tactics.
- At HubSpot, over 220,000 customer businesses generated hundreds of millions of attempted interactions, demonstrating the necessity of automated scale.
- Maven AGI and Bland have pursued formal certifications (HIPAA compliance, FedRAMP marketplace approval) to prove viability in regulated sectors.
- Granet envisions Bland eventually powering 911 dispatch calls with zero human fallback, requiring an ultra-reliable proprietary telephony stack and in-house models rather than brittle third-party wrappers.
- Granet cites a Y Combinator partner's framing: "There are companies before December 2025 and there are companies after." Post-2025 enterprises will not use AI merely to assist human workflows (like generating slides or invoices), but to execute complete end-to-end workflows autonomously.
---
[23:35](https://www.youtube.com/watch?v=tcijaaGmmBQ&t=1415s) Eliminating Phone Trees and Navigating Generational Social Anxiety
Granet addresses the universal frustration with interactive voice response (IVR) systems, admitting that Bland has a zero-tolerance policy for them: if a customer attempts to build a rigid phone tree using Bland's platform, "we will fire you as a customer." Bland instead deploys adaptive personas like "Bland Tone"—often styled as a friendly, reassuring late-50s Midwestern voice designed to de-escalate callers. Granet reveals that over 70% of callers on their platform either do not know or do not care that they are conversing with an AI.
Bland objectively measures user sentiment using caller utterance length:
| Metric Type | Caller Behavior / Utterance | Underlying Sentiment & Engagement |
|:--- |:--- |:--- |
| **High Engagement** | Long replies (> 2–3 words), conversational banter | Positive experience; caller accepts and collaborates with AI |
| **Frustration / Disengagement** | Clipped words ("operator", "yes", "help", "transfer") | Negative experience; caller is attempting to break the system |
Andy Tang and Granet discuss whether comfort with voice AI varies across generations. Granet points out that Gen Z notoriously avoids going to the doctor largely due to crippling social anxiety surrounding telephone calls. If healthcare networks like UC Health allowed patients to interact seamlessly with an AI contact over text or call without human friction, young people would schedule appointments far more consistently rather than opting out of medical care entirely.
---
[26:07](https://www.youtube.com/watch?v=tcijaaGmmBQ&t=1567s) The Messy Reality of Healthcare Data Infrastructure
Kirby Forlin offers a grounded perspective from inside the healthcare system. Coming from a data science background in consumer packaged goods (CPG) with initial ambitions to "solve the world's problems" and help cure cancer, Forlin discovered that healthcare's slow AI adoption is not primarily caused by regulation, but by deeply fragmented, legacy data infrastructure across non-digitally native entities.
```mermaid
flowchart TD
accTitle: Complex Healthcare Context Graph
A["Patient Digital Request"] --> B["Data Integration Layer"]
B --> C["Insurance & Coverage Terms"]
B --> D["Electronic Medical Records (Epic & Others)"]
B --> E["In-Network Provider Directories"]
B --> F["Out-of-Pocket Cost Calculators"]
C & D & E & F --> G["30-Second Digital Resolution or Agent Context"]
```
Forlin argues that any interaction capable of being resolved in 30 seconds or less (such as booking an MRI) ought to occur digitally without picking up a phone. However, executing even basic transactions requires orchestrating massive, disjointed datasets: reconciling insurance plan coverage, navigating diverse non-standardized electronic medical record (EMR) systems like Epic, determining in-network status, and calculating real-time out-of-pocket costs.
- Forlin stresses that while regulation mandates the use of EMRs, it never enforced a single universal EMR standard, leaving the industry with fractured interoperability.
- Tang recalls investing in an early YC AI doctor startup a decade prior, noting they severely underestimated the complexity of getting healthcare payers to reimburse unproven business models.
- Both Forlin and Tang note that Gen Z digital natives reject phone-first approaches, preferring online self-service that only escalates to a voice call when complex issues arise.
---
[30:00](https://www.youtube.com/watch?v=tcijaaGmmBQ&t=1800s) E-Commerce Fitment Gaps and the Build vs. Buy Dilemma
Alejandro Villacis connects the conversation to e-commerce at FCP Euro, echoing that contact centers exist to bridge the gap between ideal customer self-service and current system limitations. In European automotive replacement parts, selecting the wrong component leaves a customer’s primary vehicle broken down for days. Because vehicle configurations are intricate, human agents must manually cross-reference vehicle identification numbers (VINs) across external catalogs and disconnected databases. While Villacis aims to productize this logic into complete web self-service within the next five years, the constant influx of new automotive makes, models, and parts creates a continuously expanding data problem akin to healthcare.
```mermaid
flowchart TD
accTitle: Traditional ETL Pipeline vs Maven Graph of Record
subgraph Traditional["Traditional AI Approach"]
T1["Siloed Enterprise Data"] --> T2["Heavy ETL Batch Jobs"]
T2 --> T3["Static Knowledge Base"]
T3 --> T4["Shallow QA Chatbot"]
end
subgraph Maven["Maven AGI Approach"]
M1["Disparate Data Sources"] --> M2["Direct Connectors (No ETL/Duplication)"]
M2 --> M3["Graph of Record + Instant Search"]
M3 --> M4["Personalized, Autonomous Action Execution"]
end
```
Tang shifts the panel to the debate between building internal AI agents versus buying specialized enterprise solutions. When product managers attempt to build DIY bots on top of standard knowledge bases, they quickly hit walls when trying to execute personalized, multi-system actions. Corbin explains that Maven bypasses tedious manual ETL pipelines by utilizing a live "graph of record" that maps enterprise relationships in real time. Combining search indexing with LLMs allows the platform to instantly evaluate user licenses, past tickets, and account statuses on active calls without duplicating enterprise data.
[36:09](https://www.youtube.com/watch?v=tcijaaGmmBQ&t=2169s) Solving the Metadata Bottleneck: AI and Human-in-the-Loop Solutions
The panel dives into one of the most critical hurdles facing enterprise AI adoption: missing or unstructured metadata. Kirby Forlin highlights her core struggle with deploying AI agents at scale in large organizations, pointing out that "without metadata, there's no information about the data itself." Before buying or deploying complex agentic systems, companies must first lay the foundational legwork of structuring their data assets.
In response, Jonathan Corbin notes that Maven AGI addresses missing metadata by evaluating raw data structures and generating synthetic options to fill in the gaps. Kirby Forlin shares how her team at Cigna worked around this exact issue by deploying AI internally to automate data mapping and documentation across their data warehouse. However, she emphasizes that AI alone isn't sufficient; human oversight remains essential to validate data structures across disparate enterprise systems before feeding clean inputs into downstream models.
```mermaid
flowchart LR
accTitle: Metadata Processing and Validation Pipeline
A["Raw Data Warehouse"] --> B["AI Automated Mapping & Documentation"]
B --> C["Synthetic Metadata Generation"]
C --> D["Human-in-the-Loop Validation"]
D --> E["Clean Input Models"]
```
- **Enterprise Data Architecture:** Clean data pipelines exist within data warehouses, but legacy systems often lack proper documentation and cross-system data mapping.
- **Human-in-the-Loop (HITL) Validation:** Subject-matter experts and data leads step in to review AI-generated metadata and verify system contexts before models consume the data.
---
[37:51](https://www.youtube.com/watch?v=tcijaaGmmBQ&t=2271s) "Buying Outcomes, Not Software": The Palantir Model for Enterprise AI
Isaiah Granet pivots the discussion toward the underlying philosophy of enterprise software delivery, arguing that large corporations like Cigna are "buying an outcome, not a software." When scaling to enterprise levels, traditional SaaS delivery begins to resemble high-touch consulting because vendors must actively assist clients in solving foundational data problems. Drawing a direct parallel to Palantir's model—where engineers worked directly alongside government agencies—Isaiah explains that if a client lacks metadata, vendor teams must step in directly to build it out alongside them.
The primary obstacle to this approach is organizational discipline. Isaiah points out that enterprise clients frequently suffer from internal political shifts, rotating leadership, and a tendency to prematurely discard software investments. He recalls clients who abandoned vendor partnerships two years prior to build in-house solutions following OpenAI updates, only to spend far more money in the long run without reaching their target outcomes.
- **Enterprise Buying Behavior:** Large corporations often flip vendor choices annually or attempt costly, inefficient internal builds when leadership changes occur.
- **Consultative AI Delivery:** Vendors must be willing to act as outside partners who do hands-on work—such as constructing missing metadata—to guarantee measurable business value and maintain delivery pace.
---
[39:34](https://www.youtube.com/watch?v=tcijaaGmmBQ&t=2374s) Focus vs. Scope Creep and "AI Psychosis"
As Kirby Forlin asks how vendors manage broad cross-departmental integration across web and mobile apps while focusing on contact center outcomes, Isaiah Granet describes the widespread phenomenon of "AI psychosis" among enterprise CTOs. Driven by rapid AI advancements, leaders frequently jump between disparate initiatives without establishing a solid foundation in any single domain.
Isaiah explains that vendors must act as an anchor of discipline, giving enterprises "permission" and an "excuse to say we're throwing out the playbook" to focus exclusively on transforming one functional area at a time. While turning down immediate requests to expand into web chat or mobile channels can occasionally cost short-term expansion opportunities, maintaining strict focus on the contact center first is vital for long-term project viability.
- **Scope Management Strategy:** Vendors must enforce rigorous piece-by-piece discipline, refusing to tackle secondary touchpoints (e.g., website or app integrations) until contact center metrics and outcomes are fully locked in.
---
[41:01](https://www.youtube.com/watch?v=tcijaaGmmBQ&t=2461s) Rapid-Fire Round and Closing Remarks
Moderator Andy Tang closes the panel with a fast-paced, rapid-fire question round, pushing the panelists to take quick positions on key industry debates:
- **Work Week Structure (5-Hour vs. 35-Hour):** The panelists overwhelmingly prefer a 5-hour work week, with Alejandro Villacis citing more time with family. (When asked about "996"—the intense Chinese tech work schedule of 9 AM to 9 PM, 6 days a week—the panel reiterates their preference for 5 hours).
- **Education vs. Trade (BS in Electrical Engineering vs. Master Electrician):** Isaiah Granet and Jonathan Corbin lean toward a Bachelor of Science in Electrical Engineering, while Alejandro Villacis and Andy Tang express support for the practical value of a Master Electrician certification.
- **Model Architecture (Open Source vs. Proprietary):** The entire panel unanimously votes in favor of **Open Source** models.
- **AI Regulation (Regulate Now vs. 3 Years from Now):** Opinions split down the middle—Alejandro Villacis and Isaiah Granet advocate for immediate regulation ("Now"), while Jonathan Corbin and Kirby Forlin prefer delaying heavy regulation ("Three years from now").
- **Nvidia Export Controls (Export Controls vs. Free Market):** Alejandro Villacis, Isaiah Granet, and Jonathan Corbin vote in favor of export controls, while Kirby Forlin jokingly opts to side with the consensus due to unfamiliarity with the specific geopolitical nuance, ending the session on a lighthearted note.
## Notable quotes
> [00:04](https://www.youtube.com/watch?v=tcijaaGmmBQ&t=4s) We're all pitching to these guys. That's where the money, the demands are. — Andy Tang
> [00:04](https://www.youtube.com/watch?v=tcijaaGmmBQ&t=4s) if we wouldn't put the part on our cars, we wouldn't sell it to our customers. — Alejandro Villacis
> [00:04](https://www.youtube.com/watch?v=tcijaaGmmBQ&t=4s) if we get it wrong, someone's going to sue or die. — Isaiah Granet
> [04:39](https://www.youtube.com/watch?v=tcijaaGmmBQ&t=279s) nobody will be doing phone calls a year from now. — Andy Tang
> [18:52](https://www.youtube.com/watch?v=tcijaaGmmBQ&t=1132s) There are companies before December 2025 and there are companies after. — Isaiah Granet
> [23:35](https://www.youtube.com/watch?v=tcijaaGmmBQ&t=1415s) we will fire you as a customer. — Isaiah Granet
> [36:09](https://www.youtube.com/watch?v=tcijaaGmmBQ&t=2169s) without metadata, there's no information about the data itself. — Kirby Forlin
> [37:51](https://www.youtube.com/watch?v=tcijaaGmmBQ&t=2271s) buying an outcome, not a software. — Isaiah Granet
> [39:34](https://www.youtube.com/watch?v=tcijaaGmmBQ&t=2374s) we're throwing out the playbook — Isaiah Granet
## Mentioned
Ai4, Andy Tang, Draper Associates, Isaiah Granet, Bland, Jonathan Corbin, Maven AGI, Kirby Forlin, The Cigna Group, Alejandro Villacis, FCP Euro, Dell, Hinge, Hard Rock, Y Combinator, Otter.ai, Walmart, Uber, Claude Opus, AWS, Adobe, Marketo, HubSpot, HIPAA, FedRAMP, Bland Tone, UC Health, Epic, Palantir, OpenAI, Nvidia
## Video description
Jonathan Corbin - CEO/Co-Founder, Maven AGI
Alejandro Villacis - Vice President Customer Experience, FCP Euro
Isaiah Granet - Co-Founder, CEO, Bland
Andy Tang - Partner, Draper Associates
Kirby Forlin - VP Digital & Analytics Performance, The Cigna Group
AI isn’t just transforming customer-facing chatbots—it’s also empowering human agents behind the scenes. This panel will explore how AI-powered copilots are providing real-time recommendations, automatic call summarization, sentiment analysis, and instant knowledge retrieval to boost agent productivity. Panelists will discuss how companies are deploying these tools in contact centers, measuring improvements in resolution time and customer satisfaction, and balancing automation with the human touch. Expect insights into the platforms and strategies that are redefining the modern contact center and helping organizations deliver faster, more consistent, and more empathetic support at scale.
Enterprise customer experience adoption is moving faster than prior technology cycles, but industry leaders argue that long-term viability requires moving beyond venture-subsidized wrappers and superficial deflection toward sound unit economics, unified data infrastructure, and autonomous execution of high-stakes workflows.
Unit Economics and the Vendor Subsidy Trap (4:39)
Bland CEO Isaiah Granet cautions that the current generative AI cycle exhibits the hallmarks of past tech bubbles, warning that startups commanding valuations larger than Walmart while operating on fragile margins face eventual collapse. Granet compares third-party frontier API wrappers to early venture-funded ride-sharing subsidies: once introductory API pricing ends, companies lacking proprietary models and disciplined unit economics will fail. Bland opted to build its models in-house to protect gross margins, despite early skepticism from 198 venture capital investors who initially rejected the company.
Maven AGI CEO Jonathan Corbin presents a complementary outlook, conceding that while private tech valuations may be inflated, enterprise productivity gains in customer experience and software engineering are already delivering immediate, measurable return on investment. Corbin notes that generative AI adoption is maturing significantly faster than previous five-to-ten-year enterprise technology transitions.
Enterprise Restraint Against AI for AI's Sake (8:54)
Enterprise CX executives emphasize that deploying software tools without addressing fundamentally flawed operational processes creates zero strategic advantage. Kirby Forlin of The Cigna Group points out that while individual productivity tools like Claude Opus can draft slide decks in seconds, slide generation does not constitute fundamental enterprise transformation. Real business impact requires strict enterprise architectural discipline and strategic alignment between business leaders and engineering teams.
Demonstrating this cost discipline, Alejandro Villacis of FCP Euro outlines a pragmatic adoption framework that audits routine support tasks and assesses internal data before looking at external software. Villacis notes that FCP Euro rejected vendor call-analysis platforms with $100,000 baseline fees because paying more for experimental call analysis than for their entire AWS web hosting infrastructure or warehouse management system made no financial sense when human review remained cheaper.
Automating High-Stakes Interactions Over Basic Deflection (18:52)
Rather than relying on legacy interactive voice response (IVR) phone trees—which Granet actively bans on Bland's platform—the primary enterprise opportunity lies in executing complex, mission-critical calls end-to-end. Granet reports that over 70% of Bland's callers do not know or care that they are interacting with AI, as the platform guides 90-year-olds through 45-minute remote medical checkups and conducts volatile overseas polling. Granet envisions voice AI eventually powering 911 dispatch calls, arguing that the deepest business value comes from resolving regulated, high-risk conversations where failures risk lawsuits or death.
Corbin reinforces that consumer demand for immediate, frictionless service pairs with severe internal enterprise bottlenecks. Citing his experience at HubSpot—which handled hundreds of millions of interactions across 220,000 organizations—Corbin argues that scaling support through human labor alone is impossible. As platforms secure HIPAA compliance and FedRAMP authorizations, automated execution becomes essential across both consumer touchpoints and heavily regulated sectors.
Resolving Data Bottlenecks and Vendor Scope Creep (36:09)
Deploying agentic systems remains severely constrained by fragmented data architecture and missing metadata. Forlin explains that healthcare's slower adoption is primarily caused by non-standardized electronic medical record systems and fragmented insurance databases rather than regulation. While Maven AGI applies direct connectors and synthetic metadata via a live 'graph of record,' and Cigna uses AI to map data warehouses, Forlin stresses that human-in-the-loop validation remains mandatory to verify data context before models can consume clean inputs.
Because enterprise clients frequently grapple with data deficits, Granet contends that vendors must emulate Palantir by delivering consultative outcomes rather than hands-off software licenses. He cautions that vendors must actively combat enterprise 'AI psychosis,' a tendency where corporate leaders prematurely expand into mobile and web channels before proving stability. Vendors must enforce operational focus, refusing secondary expansions until core contact center workflows achieve validated outcomes.
While the panel demonstrates that contact centers offer immediate, measurable ROI for generative AI, long-term industry success remains contingent on unresolved structural issues: bridging broken legacy metadata architectures, surviving the expiration of subsidized compute pricing, and maintaining strict execution discipline rather than chasing disjointed multi-channel experiments.
[0:04] Andy Tang: We're all pitching to these guys. That's where the money, the demands are.
[0:04] Alejandro Villacis: if we wouldn't put the part on our cars, we wouldn't sell it to our customers.
[0:04] Isaiah Granet: if we get it wrong, someone's going to sue or die.
[4:39] Andy Tang: nobody will be doing phone calls a year from now.
[18:52] Isaiah Granet: There are companies before December 2025 and there are companies after.
[23:35] Isaiah Granet: we will fire you as a customer.
[36:09] Kirby Forlin: without metadata, there's no information about the data itself.
[37:51] Isaiah Granet: buying an outcome, not a software.
[39:34] Isaiah Granet: we're throwing out the playbook
Original transcript
[0:04] All right, great. Welcome. Um, I'm excited. This
is going to be great. Uh, you know, this, uh,
[0:10] I took a lot of care in the seating arrangement.
I hope you appreciate that. Two customers and two
[0:16] AI experts. So, it's going to be fun when we,
you know, ask these guys questions. We can see
[0:21] your list of priorities. Yes. [laughter] Yeah.
Exactly. Yeah. Yeah. Exactly. We're all We're
[0:25] all pitching to these guys. That's where the money
the mans are. Um yeah, so but before before this
[0:32] I want to tell you when they asked me they gave
me a list of panels to moderate um I picked this
[0:39] one and I think it surprised a lot of people um
because it's not very often I get to talk about
[0:46] customer related things and it occurred to me um
it is an area of my passion because our latest
[0:58] uh analyst class from the summer. There were
six of them. They asked me what they should
[1:03] do. I told every single one of them to go get
a job in customer service or um restaurant way
[1:10] staff. And in fact, I'm curious how many of you
have worked, you know, when you were younger
[1:16] worked in some sort of customer service related
industry or way staff, right? Yeah. Great. So,
[1:22] I think passed on that message to the our Gen
Alpha friends. um it is an important skill set.
[1:29] It's not just a way to pay for, you know, college
and whatnot, right? So, I thought it's kind of
[1:34] interesting. Uh, yet now we're combining that
with this um, you know, flavor of the day AI. So,
[1:41] it's a it's a great topic that I want us to to
think about. Uh, but without further ado, I would
[1:47] like all of us to introduce ourselves. Why don't
we start from Isaiah? Perfect. Uh, hi everyone.
[1:53] I'm Isaiah. I'm the co-founder and CEO at Bland.
Um what we do is we automate the really difficult,
[1:59] really ugly phone calls. So the way I like to say
it is we want to be doing the phone calls where
[2:04] um if we get it wrong, someone's going to sue
or die. So we're doing the really hard stuff,
[2:08] fully automating end to end. Um we build all
of our models inhouse. So some of you might
[2:12] have seen actually we just released our new
texttospech model yesterday, which is now um
[2:17] EVEL does the most realistic in the world. We've
raised a little bit over a 100 million to date.
[2:22] We work with 250 enterprises and 350,000 self-s
served users today. Hey everyone, I'm Jonathan
[2:28] Corbin, CEO and co-founder of Maven AGI. Uh we
create AI agents for customer experience working
[2:35] with about a 100 customers including some that
you've probably heard of, folks like Dell, Hinge,
[2:40] Hard Rock, uh and many others. Um and we've have
about 100 employees. Um raised about $78 million.
[2:50] um and excited to share more about our journey. Hi
all, I'm Kirby Forland. I um in the SVP of digital
[3:00] data and analytics. I'm going to have a little bit
of a different perspective here because I'm really
[3:04] come at this from a digital perspective. But the
thing that we've been working on this year is how
[3:08] do we make sure all the context about customers
is connected. So within all the applications
[3:14] that they might be going to and data might be
going over there and they might then eventually
[3:19] call. How do we make sure that everybody's on the
same page and has the same information from which
[3:23] that we can give a better customer experience? Hi
everyone, I'm Alejandro Vijas. I am with FCP Euro
[3:31] family-owned company 40 years old online for
about 25 years. Um, we sell automotive parts
[3:38] for European vehicles and our brand promise is
that if we wouldn't put the part on our cars,
[3:43] we wouldn't sell it to our customers. So, we
stand behind every product we sell and and we
[3:49] try to sell only highquality products that that
we can stand behind. Um, I've been in e-commerce
[3:55] for about 15 years. um have been at FCP Euro
for about two two and a half years and have
[4:02] really spent the last year implementing AI in the
contact center to try to augment the capabilities
[4:08] of our agents and focus more on the value added
um types of conversations that they can have where
[4:14] we're generating revenue and where we're driving
retention. So our focus for the next year at least
[4:23] is continuing to find what are those opportunities
where we can save time from agents doing road
[4:29] activities so that we can dedicate them to more
sales and retention activities. Great. Um so you
[4:39] know I'm an early stage venture capitalist
been doing this for 20 years. Uh I've seen
[4:43] multiple cycles. So, one of the things I want to
ask you guys, especially the two of you, Isaiah is
[4:48] smiling because you know this guy is an incredible
entrepreneur. Uh, I'm glad I wasn't one of the 198
[4:57] pitches you made coming out of IC. I think he got
turned down by 198 investors. I'm glad I wasn't
[5:02] one of them. They were complaining to him about
not wanting to back audiobased um companies. Phone
[5:09] calls will be dead. The exact quote was, "Nobody
will be doing phone calls a year from now." And
[5:15] that was in 2023. [laughter] Wow. It was uh Yeah.
Yeah. By the way, uh fun fact, I backed a company
[5:21] called uh seeded a company called Otter AI out
of a um a cafe in downtown Powto in 2015. They
[5:30] wanted to record all the audio conversations in
the world. I thought they were both creepy and
[5:37] uh and what else I say? uh uh unrealistic, but
I'm glad both you guys proved me wrong. Um but
[5:45] I'm very disappointed I didn't I wasn't the 199th
investor you talked to. But um uh that aside,
[5:54] what do the two of you think about the um
AI economic cycle? You guys are founders,
[6:00] you are CEOs. Um you have you're you're looking
at the big picture. You're guiding your company.
[6:08] So tell tell us what you think. Is this is this
time different? No. Um I [snorts] mean I think
[6:16] ultimately when you have companies that are valued
at more than Walmart with unit economics that look
[6:21] about the same you start to ask questions and say
hey is this fundamentally sound? And then when
[6:27] you start looking at down market and see all the
companies that are built on top of them. I think
[6:31] what's particularly dangerous and part of why we
built bland without frontier models. This was a
[6:36] really difficult decision was that we looked at
historically what happens with Uber with other
[6:40] companies. The subsidy period eventually expires
and at that point if your business doesn't have
[6:46] real lags and real fundamentals it gets really
ugly. I think that there's a probably a very
[6:50] high chance that we're in a big bubble right
now. Um and I think that uh it doesn't mean AI
[6:55] isn't valuable just like the internet wasn't
valuable in the early 2000s. Uh but it does
[7:00] mean that companies need to be really careful and
mindful and that the people that are spending like
[7:04] there's no tomorrow and are not paying attention
to the fundamentals, gross margin um are going to
[7:09] be in hot water and the companies that are buying
these software from that companies um they need to
[7:14] be concerned about the long-term health of those
businesses because otherwise it could be a really
[7:19] ugly situation. Yeah. Yeah, I agree with you.
I think this time you know if I compare this to
[7:23] internet or um you know um share economy and you
know a few other cycles after uh sort of before
[7:32] this people actually paying now right it's not
just the eyeballs the question is are they paying
[7:37] enough to keep you guys afloat but I'm pleased to
hear you guys all have a lot of customers Jonathan
[7:43] your your view on this I think it depends on
what you're looking at right if you look at
[7:46] it from a macro perspective I think that AI is
going to fundamentally change the way that we do
[7:51] everything. If you look at it from like what is
the impact of AI from a micro perspective, where
[7:58] are we seeing the most results of it? There's like
two areas. One of them is the reason why we're all
[8:04] here today, which is customer experience. The
other is coding. Now, will we see that trickle
[8:09] over into other areas of the economy and other
places within like white collar and blue collar
[8:15] jobs? I think so. Like how long does that take?
If we look at other cycles, we'll usually start
[8:21] off with like you know the people who are early
innovators kicking the tires, people who want to
[8:26] like test out new technology and you see a trickle
down effect. Typically see it takes about 5 to 10
[8:31] years for to reach full maturity. Yeah. Now we're
seeing the evolution of this moving much faster
[8:37] than anything we've ever seen before. Like where
it's actually impacting what customers are doing,
[8:43] companies are doing, and how they're thinking
about the future. So are companies overvalued?
[8:48] probably like but is there a massive macro impact
for sure. Yeah. Yeah. Yeah. Now from the customer
[8:54] side what do you what are you guys seeing from
just from a corporate perspective? You are you
[8:59] know buyers of AI products right? Um you guys
have very healthy balance sheet. Um are you guys
[9:09] making investments in the AI areas? Do you want
to start? I mean definitely making investments
[9:17] in the AI in the AI areas. Um I mean I think
it's an interesting time in business because I
[9:22] think especially in a non-digitally native company
like Sigma is I think um they're they're trying to
[9:29] figure out right now um let's do AI and I think it
needs at some point to flip in that AI isn't like
[9:37] you have to change your business strategy that
it that AI helps you with a different business
[9:41] strategy. I think the problem right now is it's
sort of AI for AI sake instead of like the whole
[9:47] business reimagined about what it could be. So I
think that's probably the thing I'm seeing most in
[9:52] business. A lot of investment, a lot of things
happening but sort of a disconnected ecosystem
[9:58] and I think that stems from not reimagining how
it could be in the in the world where you know
[10:04] Gen AI and of course all the other aspects of
AI exist. What I' what I've seen from a lot of
[10:10] companies is they're like we're going to transform
our business with AI and they're like let's give
[10:15] some AI to everyone and it has absolutely no
impact. What are you guys doing like how are
[10:20] you thinking about implementing that? I'm really
curious to get it from your perspective. I mean
[10:23] I think it's similar right like and I I mean I
think there's things that are doing impact. So
[10:27] we have like I mean even just having you know
uh co-pilot or something that's helping people
[10:32] become more efficient and you know in corporate
America you spend so much time writing PowerPoint
[10:37] decks. I'm sure everybody here can appreciate how
much time you have spent like one of the greatest
[10:42] efficiencies for me is the opus model and being
able to quickly generate slides which seems like
[10:48] uh like seems kind of crazy but like it does
allow me to do a lot more strategic thinking
[10:52] because I'm not spending so much time generating
slides but that isn't business reinvention. I
[10:56] think the other thing I see is that there's a lot
of process automation trying to be able to use AI
[11:01] but we're not re like we're just automating the
process that already exists that was probably
[11:05] kind of broken. So I think there's like something
to be there. So I I and I I see a lot of tools
[11:10] and duplicative tools being bought um instead
of you know I think this is where enterprise u
[11:16] architecture comes in and we need a much more
thoughtful view on how we're going to actually
[11:20] go forward on this. But again I think it goes back
to a lot of times it's like landing in the digital
[11:26] world the tech world and what I keep saying is
like hey guys like we actually need the strategy
[11:31] and then we can tell you what AI we need. And
I think it's ver I think it's upside down a
[11:36] lot of the times right now. And I think we need
to get like tech and the business needs to come
[11:40] together from a strategic viewpoint of what's
possible. And I think it's very hard because
[11:46] if you're not familiar with it, it's very hard to
envision what's possible. So I think there's a I
[11:50] I think the idea that there's a big macro change
happening is true. I think it's going to take a
[11:56] little while longer and I do think companies
will overinvest invest in the wrong things.
[12:01] we're going to make a lot of missteps. And I think
the non-digitally native companies that will win
[12:05] are the people that bring in the talent that can
really think about reinvisioning a business and
[12:10] and how it might be totally different. And and
I don't want to um go into a tangent too much.
[12:15] Maybe you should go next and then I'll follow up.
Yeah. Yeah. So I'll say at FCP Euro, we're we're
[12:20] very cautious about what investments we're making.
So we're being very thoughtful with AI investments
[12:25] and I think we started in the technology teams or
software engineering particularly to look at how
[12:33] can we leverage some of these models for coding
to make ourselves more efficient to be able to
[12:37] deliver more more um updates and and and stuff.
We've seen some success there. The technology
[12:46] team and the data team they've taken their
own approach to this is these are the things
[12:50] that we're going to invest in. These are the
things that we want to um eliminate repetitive
[12:55] work and we want to be able to deliver faster.
Other teams such as my own customer experience,
[13:03] we started probably with a 3 to six month lag
from the technology teams thinking about okay
[13:09] to your point what is our strategy for how we're
going to implement this. We don't want to go out
[13:15] there and just start talking to every vendor that
is showing us tools that seem very similar and
[13:24] to to be honest in some cases wasting our time on
conversations that all sound the same where it is
[13:30] difficult to differentiate between what different
vendors might be able to provide. And so we focus
[13:36] on the strategy like what do we want to try to
do if we implement AI? There were a couple things
[13:43] that were clear to us. We spent a lot of time on
things that are repetitive that we can save time
[13:49] on. Okay, great. Let's identify what all of those
are. Let's prioritize them. Let's figure out what
[13:55] AI solutions we can use or buy or what do we
already have access to so that we're not buying
[14:01] duplicative software and start to leverage that.
And then we said, okay, well, what is another pain
[14:07] point? We don't have enough resources to devote to
gathering insights and analyzing transcripts and
[14:14] conversations. We started recording transcripts
about 18 months ago and we hadn't implemented
[14:21] any tools to try to analyze them or extract
value from them until about 6 months ago. And
[14:27] so first we focused I hope you were using Otter
AI. [laughter] Just kidding. We're not. But but
[14:37] um we we um we started transcribing all
our calls and we started thinking about
[14:42] okay there's a lot of value that we can derive
here. What tools do we already have in place
[14:47] that we can use? What are the new tools and
and models that we might be able to use? And
[14:53] then we started little by little thinking about
okay like what is the investment that we have to
[14:57] make and let's make sure that it aligns with
the strategy and that the costs make sense.
[15:04] I've had some vendors come to me and say, "Hey,
like we can analyze all of your phone calls for,
[15:09] I don't know, a base fee of $100,000 a year
plus however many transactions we're going to
[15:16] evaluate." And and I'm like, when I start thinking
about how many conversations we have and I start
[15:22] building out a total cost of ownership on this,
you're asking me to pay more for a new solution
[15:26] that is unvetted, unproved than we pay for our
WMS software that we're that we're adding to the
[15:34] to to the to cheaper to do it by human. Yeah. and
and it's like where what what is the differential
[15:39] value that you're going to to bring to the table
when you're asking me to pay almost as much as
[15:45] we pay for AWS to host our entire like website
infrastructure for call analysis like that doesn't
[15:52] make sense right so coming back to the strategy
it's like okay what did we prioritize what do
[15:58] we want to focus on and what are the tools that we
can use and can we start small and scrappy yes use
[16:04] new technology and new tools but don't go to the
to the flashy Yeah. vendor that is trying to sell
[16:10] you the dream. Yeah. Well, let me ask you this.
So, we we have um Kirby coming from, you know,
[16:16] healthcare, Alejandro coming from e-commerce.
Um I'm I'm sort of looking and I'm going to say
[16:23] something. I have a feeling you guys are going
to disagree. So, this is a this is a a green
[16:28] light for disagreement. If I look at internet, the
adoption of internet started in communication. Um
[16:36] and then and then in retail and in uh enterprise
and then in um let's see maybe industrial and then
[16:46] financial services uh you know education they
probably would never adopt and then government
[16:53] um right so if you kind of look at the order
of adoption this is essentially the level
[17:00] of regulation they have essentially the more
regulated industry is it took them a little bit
[17:05] longer [snorts] Right. Are you guys seeing that um
in AI adoption? Uh let's start from um um Jonathan
[17:15] and Isaiah and I'm also so curious to see what the
healthcare expert has to say specifically about
[17:20] this because you're very famous for HIPPA, right?
So is AI following sort of the same footsteps?
[17:29] I think it's interesting and I'll disagree with
the first part of it because depending on who you
[17:33] talk to some people say the internet was invented
by the government so [laughter] at the beginning
[17:38] but no I think like seriously I think that um what
we're seeing is like the business cases are there
[17:44] for broadscale adoption like if so if we think
about customer experience most of us here have
[17:50] had a terrible customer experience like I had one
today checking in my hotel I'm sure you all did as
[17:58] Like everyone has has that bad terrible
customer experience. So companies hear
[18:03] from their customers, hey improve, I'm taking my
money elsewhere. Like do something different or
[18:09] like face the consequences. And so you have
people who have like broadscale consumer
[18:14] interactions saying I need to do something
different and if I can save money doing it,
[18:18] amazing. They're investing hundreds of millions
of dollars for large companies and customer
[18:23] experience and not getting much further value. The
other thing is is like when you start to look at
[18:28] like like healthare like not to pick on healthare
like [laughter] we were talking about it earlier
[18:34] like I tweaked my knee playing basketball the
other day and I'm like trying to get a hold
[18:38] of my insurance company and my doctor's like come
see me in a year and you're like okay this doesn't
[18:42] feel like it's working really well. And I think
that everyone has these things where it's like,
[18:48] wow, like if we just had a cheaper way to
be able to communicate with each other,
[18:52] a better way to interact, like this would actually
make life a lot better for all of us. Yeah. And so
[18:57] there's a lot of consumer pressure for people
to improve. The other is like how do I improve
[19:02] my operational efficiency? So prior to starting
Maven, I worked at a bunch of companies that were
[19:07] market leaders in the customer experience space.
Companies like Adobe and Marquetto and HubSpot.
[19:13] And the challenges that we had is like we had
so many customers and we wanted to talk to all
[19:17] of them but we couldn't afford to. Like we had at
HubSpot we had 220,000 companies we were working
[19:23] with hundreds of millions of people who wanted to
interact and talk to our customer support team. We
[19:27] just didn't have enough people. And so we said,
how do we like change this and how do we improve
[19:31] this at scale? And so like the efficiencies
that you realize of actually less people,
[19:37] more customer interactions makes the business
case really meaningful for broadspread adoption
[19:42] even in heavily regulated industries because
now we know what the playbook is in terms of
[19:47] adoption. Like like we went out when we started
the company a few years ago, we started doing
[19:52] getting certifications. We're HIPPA certified.
We're in the process of getting Fed RAM. So you
[19:56] can move much faster if you have a clear path to
adoption. So this time could be different. Isaiah,
[20:02] what I'm I'm dying to find out what these um
phone calls you've been fielding that that avoid
[20:09] lawsuits and what is that su or dies. Death,
man. This is sounds like healthcare industry,
[20:14] but go ahead. Well, [laughter] maybe a couple of
examples, right? One is um we do remote patient
[20:19] monitoring calls where we're doing 45 minute long
calls with patients that are sometimes over 90
[20:24] years old, helping them find their blood pressure
device, helping them put it on, take the reading,
[20:29] and understand if they're having a medical
emergency or if they just didn't tighten it
[20:32] enough. Um and and the entire time talking
about their grandkids, keeping them engaged,
[20:37] making sure that all those things are happening.
And there are medical emergencies on those calls.
[20:41] We do realize that people need to go to the
hospital. We also have um worked with companies
[20:45] to do surveys and polls of countries that we've
all been hearing about in the news recently
[20:50] um and collecting data that if that was to be in
the hands of the governments that could see that
[20:55] they might actually go doortodoor and find those
people. We deal with really serious calls. And the
[21:00] interesting thing is that is the exact inverse of
what you were saying in my mind which is the real
[21:08] value we drive is the regulated industries. It
is the difficult calls because it turns out that
[21:14] um people in the business have been trying for
the last three decades to do everything they can
[21:19] to shrink the contact center or get rid of it
in every way. They put IVRs, they try and get
[21:24] you off, they call deflection time, they send
you the website, they give you the runaround,
[21:27] they transfer you a thousand places. Um the humans
that are there today exist because the business
[21:33] has a gap between what the business wants to do
what the business can do today and that gap can
[21:38] only be filled by human judgment right now. And
so our AI um where you know also now Fed ramp
[21:45] uh in the marketplace we're working with these
really complex customers the value that we see
[21:50] is actually when we're doing those hard calls. Um
and what I always talk about is one day we want
[21:55] to be doing 911 calls. And so for everyone in the
audience, just to imagine if you called 911 and an
[22:01] AI picked up, but there is no human. There is no
you can't say human 50 times and get one. There
[22:07] is no there's nobody in that call center. That
AI has to be really damn good. Right. Right. But
[22:14] there's not a whole lot of value in between that
AI actually being able to handle you, you know,
[22:19] screaming on the phone in an emergency and and
like routing you to the right fire department or
[22:25] police department. And so what we think about is
our job is to handle those most complex difficult
[22:30] calls. That's part of why we don't use external
models um and even are building things like the
[22:35] telefan stack in house because we have to be able
to deliver that level of reliability. And what we
[22:40] see from a lot of enterprises right now is um I
was at a dinner with uh YC partner recently. He
[22:47] said something interesting. There are companies
before December 2025 and there are companies
[22:51] after. The companies after December 2025 look
really different. because they're not trying to
[22:56] use AI to assist human workflows. They're just
using AI to do the workflow. And it started me
[23:02] thinking like a lot of us think that we're using
AI, but we're not actually. Like using it for
[23:06] your slides is awesome, but what if you weren't in
the loop to even have to do the slides? Uh or for
[23:13] finance, AI assisted invoicing, but if you were
starting a company today, would you even have a
[23:18] finance department? How would that work? And most
people can't actually fathom what that looks like.
[23:23] And our job is help deliver that reality and
deliver it for the ugliest, most difficult, scary
[23:28] phone calls where uh you really have to trust
what's happening on the other end. Um I can't help
[23:35] but jump in and say that I am that guy who gets on
the phone and my immediate reaction is operator. I
[23:42] would say 15 times. Um it has to be that it's the
quality you're talking about, right? Um because I
[23:50] think we all had some bad experience because
it's that runound is is there quality there
[23:56] already and yes so bland we there's probably some
blandigans in the audience and they know that I
[24:02] uh hate phone trees with a passion and it is like
the one thing that you can do that we will fire
[24:07] you as a customer if you try to build a phone tree
with our product because the experience has to be
[24:12] superior and it has to be safe and so we have this
thing called bland tone which is like how does our
[24:17] AI talk to you and usually it turns out. It's like
some Midwestern sort of late50s like very sweet
[24:24] like engagement tone and how does it redirect
you? And with our new voices, what we're seeing is
[24:29] um for a lot of our customers over 70% of the
calls are doing people either don't know or
[24:34] don't care it's AI. The way we measure that is
by utterances. So what we track is how many words
[24:40] are you saying in reply to when our AI talks. If
it's more than two or three words, you're actually
[24:45] probably engaging with it really positively
and it's highly linked. If it's two words of
[24:50] no operator, yes operator, help, transfer, like
those small utterances, then you probably are
[24:56] not having a great experience. And so what we're
seeing is starting to cross that threshold. Um,
[25:02] but it takes time and it takes earning trust. Is
is this a a kind of a generational experience?
[25:08] Like my kids are 12 and 15. Do you think they have
they're more comfortable with that? My favorite
[25:14] example is that Gen Z doesn't go to the doctor.
And the reason that Jenz does not go to the doctor
[25:19] is because they have social anxiety about picking
up the phone. This is like pretty well documented.
[25:25] Yeah. Um [laughter] and I say this as uh for
Gen Z, right? Potentially. Why don't we pick on
[25:33] why don't we pick on Gen Alphas? There aren't any
in the Those kids don't get it. Uh but uh Gen Z,
[25:39] right? Like they have social anxiety because
there's this pressure about picking up the phone.
[25:43] And I guarantee you if your doctor was an AI
contact in your phone that you could text or call
[25:48] with the UC health system um right I think about
California people would make way more appointments
[25:52] and they'd be way more likely to engage and if
we don't make that the future then people just
[25:58] aren't going to go to the doctor um they will
opt out and we've seen this it happens uh and
[26:02] so I think it is better yeah right you guys are
sitting here too complacent so what do you guys
[26:07] think especially Kirby on the healthcare regulated
industry you AI adoption would you be do you see
[26:16] this as a potential leading other industries or
more kind of follower? Um I I think the thing
[26:24] that's been interesting because before I was in
healthcare which I've been in healthcare for about
[26:27] the last five years I was in the consumer package
goods industry. Yeah. And so I actually and I'm
[26:32] a data science by background. And so what I was
interested in was like coming in and like taking
[26:38] all their data and solving the world's problems um
with you know with curing cancer. I had these like
[26:43] you know lofty ideas. The reality of why I think
healthcare is slow to adopt is because their data
[26:50] is in such bad shape. And so you could say all day
long you know it's that they're regulated or it's
[26:56] this or it's that. It's a very very complicated
ecosystem that um is is difficult and they are
[27:03] non-digitally native and so they haven't spent
a lot of time getting what you actually need to
[27:08] have together to be actually able to do the things
that AI is going to enable. I love the idea of and
[27:15] I believe human in the loop or a really great a
you know AI agent that can actually handle those
[27:20] calls. That's the right thing that I believe our
agents should be handling. And I honestly think
[27:25] like you need an MRI, you should be able to do
that online and you should be able to book that.
[27:29] And our goal is like and the friction we're trying
to take out of the consumer experience is anything
[27:34] that you that you should be able to handle in 30
seconds or less digitally, you should. And the
[27:39] only things that should go to the call center are
the things that cannot be handled digitally. The
[27:43] problem that we run into is to do all of that.
There's a massive data lift that needs to get
[27:48] invested in so that we can in fact do this so that
I we have all the context so we know your plan,
[27:54] your insurance, your EMR is connected, we
understand who your provider is, we understand
[27:58] what's in your provider network so we can we can
we can route you there that we understand your
[28:03] plan and how much that's going to cost. It's a
really super complicated uh data problem that is
[28:10] what's holding I think the healthcare industry
back and I think they're doing a lot of good
[28:13] work to do it. But I think it's a much more messy
problem than I understood. Um and I I didn't have
[28:19] a lot of empathy for this um industry. Um before I
came in and was like, "Woo, this is messy." Um you
[28:26] know, and there's no regulation right now, right?
That like there's regulation that you need to have
[28:30] an EMR, but they didn't regulate that everybody
had to have the same EMR. So sorry electronic
[28:36] medical records like so that we can understand
what's happening everybody like there's tons of
[28:40] them like yes epic is the biggest one but there's
so many more so how do you get interoperability
[28:44] with that if we need to understand that to have
a really good you know conversation to understand
[28:49] when it should escalate so I think that is the
thing that holds it's less it's less it's less
[28:56] regulation maybe more regulation could help us get
there but uh maybe not I don't know but there's um
[29:00] is a data problem yeah yeah I I I you're good
companies 10 years ago I invested in also YC
[29:07] company it's a AI doctor AI companies were more
primitive back then but it's the same idea right
[29:14] if you have this AI it was probably founded by
a Gen Z person uh because you don't have to go
[29:21] to a doctor you can just call to your AI doctor
right no phone calls required of course it was
[29:26] very difficult to get the payers to pay it's we
didn't I think we all underestimated the business
[29:31] model well and like talk about Gen Z I think the
thing that they'd want is to actually be able to
[29:35] book online, right? Like they don't even there's
like I have two Gen Z kids. So like they're like,
[29:40] "Oh my gosh." Like I when I suggest they call
their friends, we're like what? Like that is
[29:44] not You should text them first. Yeah. You you
don't call people. But um you know like the part
[29:49] of the problem is like why aren't people like we
should be able they should be able to go online.
[29:53] We should be able to find their doctor. We should
be able to book like that should be something
[29:55] that's digital and you know and escalate to call
if there's something more important. Let's talk
[30:00] about e-commerce. I I think something Isaiah said
earlier really resonated with me where he said the
[30:06] contact center like only exists because there's a
difference between what you can deliver today and
[30:11] what you would ideally want to be able to deliver
to these customers, right? And we see that all the
[30:16] time. Um in our business, uh the fitment of a part
for a vehicle has to be right for the vehicle that
[30:25] you own. You're spending hundreds of dollars on
fixing your vehicle because you need to use it to
[30:30] get to work typically, right? Or you need to use
it to transport your family. So you we we have to
[30:36] get you the right part. If we don't, your vehicle
stays broken down for a couple more days. our the
[30:44] way that our website works today, we we try to
drive a lot of self-service and selecting the
[30:49] right vehicle part, but because of the complexity
of the European vehicles and like what parts are
[30:56] compatible with different models, sometimes
you need VIN verification. We haven't built
[31:01] that out like that's not built out on our website.
There are tools that we use to connect different
[31:07] data sets so that we can answer those questions
and that's where our um experts on the team add
[31:14] value. Um but it exists because we haven't built
out the technology for self-service. Would we
[31:20] like our our our customers to self-s serve more
often? Absolutely. They can't right now. And so
[31:27] we're providing a value added service for now. Can
we structure the data in such a way that we could
[31:35] to your example about healthcare like be able to
create productize it on the website and and get to
[31:41] a self-service? I'd like to think yes in the next
5 years that should be possible. Um but there are
[31:48] constantly new vehicle makes and models coming
out every single year. There's a proliferation
[31:54] of parts with different qualities and different
fitments assigned to them. And so it's a it's like
[32:00] an everexpanding data problem which I'm sure you
face a lot in the healthcare space as well. Um and
[32:07] it just becomes challenging. Yeah. Yeah. Um along
those lines of um sort of building versus buying.
[32:15] Uh I'm curious what you guys have seen both from
the customer side as well as a solution side. How
[32:21] do people maybe start with the two of you? um
as you talk to customers is there's this idea
[32:28] of we might be able to build this ourselves. In
fact, I actually have a startup. Um I'm convinced
[32:34] it's because they're in that space where the agent
space is not quite mature yet. So they're forced
[32:42] to build their own agents and then they realize if
I build a few agents and I have to maintain these
[32:47] agents, right? this idea of coding you either have
that um um the um AI code it for you completely
[32:56] this idea of human machine collaboration makes
maintenance very difficult so they have to build
[33:01] their agent factory just for their own use
I'm very curious what you guys are seeing
[33:07] um what customers are telling you build versus
buy I think I think one of the things that's
[33:12] interesting is like what you just described for
healthcare and for your company in particular of
[33:17] you have fragmented data that lives across the
entire enterprise. And in order for you to be
[33:23] able to deploy and use AI within your business,
you need to bring together all of that data set,
[33:28] run it through this like ETL process, and now
you're ready to like feed it into AI. And that is
[33:34] the scenario that every major company is in. And
so it's really easy for you to set up an AI agent
[33:40] that can sit on a knowledge base and can like like
repeat like pieces of information back to people.
[33:46] Yeah. Yeah, it becomes much harder when you
actually say what is the problem that we want to
[33:50] solve? Well, we want to solve like better customer
experience. How do we do that? Well, part of it
[33:57] is giving people the information they need. But if
you think about what's the full service experience
[34:02] that's required to do that, you need to be able
to bring context into the interactions. You need
[34:07] to understand who is this person? What are the
historic interactions they had? Like what is the
[34:12] subscription level that they have to my service?
How many licenses do they have? What is the
[34:17] account balance within the accounts they have with
us? And then you have to be able to take actions
[34:21] on their behalf. And what that requires is going
out mapping all the enterprise data, understanding
[34:27] which piece of information I'm pulling into
each turn of the conversation. It's incredibly
[34:32] complex. And that's why it's really hard for you
to go and build this. Even though it's tempting,
[34:36] right? Because these are all your data. These are
every every like new product manager that joins
[34:41] the company is like, I am going to go build this.
[laughter] But how do you and [snorts] that's when
[34:46] they'll call you. But if if we're how how are you
coming in as a you know somebody who's already had
[34:52] it built and then implementing it on the data
that actually needs to feed into your system,
[34:57] I feel like the problem still exists. Yeah. Kind
of. So I I think when we went out there and we
[35:02] started having conversations with people on how do
we change the customer experience and the journey
[35:07] that you've constructed for companies today, it's
not built for customers. It is built for companies
[35:13] using their existing ecosystem and the limitations
that they have. If we were to reimagine that,
[35:17] what would it look like? It would be this like
biodal interaction. It's proactive and reactive.
[35:23] And in order to be able to enable that, you
need to go out and connect and map out all the
[35:28] different data that exist across the ecosystem.
And for us, we built, we call it a graph of record
[35:33] where it connects to all the different pieces
of information across the ecosystem. We create
[35:39] instant graphs that understand the relationship
between like me as a consumer all the pieces of
[35:45] information across the enterprise that relate to
me and you can create this personalized experience
[35:50] for each individual user and so we connect to
the data we don't copy it over we don't have to
[35:55] run it through an ETL process and because like we
use a combination of search technology along with
[35:59] large language models it allows us to be able
to have this like instant understanding of like
[36:05] here's the information here's how it pertains to
this customer and you can do it on a phone call,
[36:09] you can do it in chat, you can do it in generative
search, whatever modality you want to use. I can't
[36:15] help myself. But what if the metadata like doesn't
exist, right? So there's no context to the data
[36:20] which in these big companies I've been in and
someone who's pretty involved in data that would
[36:25] be like the thing that I'm struggling with is like
on agents in general is I'm like you got to build
[36:30] your metadata and then then you can buy but like
without metadata there's no information about the
[36:34] data itself and I'm not sure how and I'd love to
hear but like so I'm curious like because that's
[36:38] like a big problem. Yeah, I think it it definitely
is. And so there's there's actually like ways that
[36:43] we've created for us to be able to evaluate data
and create synthetic options that replace that.
[36:51] Yeah. So so I'll I'll jump in here. Actually,
one of my data colleagues is in the audience and
[36:55] he's partnered with me a lot on this. To your
point about building out the meta metadata,
[37:01] we've started to use AI to be able to do that.
Um because we had to build out a lot of data
[37:07] connections and data mapping. to Jonathan's
point um that didn't exist previously. We had
[37:13] to document all the data that we had. We had good
pipelines like everything sitting in our in our
[37:19] data warehouse. We were just not leveraging a lot
of the the data and connecting it appropriately.
[37:24] But AI tools can help us document can help us
add the metadata. Um and and we've actually
[37:30] done that like our data team has taken the lead
on a lot of that. And then we do bring humans in
[37:34] the loop who have more context about the data
structures and all the different systems that
[37:39] they're coming from and people like myself can
help validate okay what what is here and is this
[37:46] accurate and if it is accurate then we can start
feeding it into other models. Part of all of this
[37:51] I think ultimately comes down to a company
the size of Sigma. you are buying an outcome,
[37:57] not a software. And we talk to our deployed team
about this, but your job is to deliver outcomes.
[38:03] And at some scale, software just starts to look
like consulting because that's kind of what it is
[38:08] a little bit. And so if you said to us today, the
metadata isn't there. We'd say, okay, we're going
[38:13] to go build that with you to get the metadata in
there. And we've done that with customers. Um,
[38:18] and the biggest thing that we see is that does
Sigma have the political time, appetite, and
[38:23] will internally to not go try and flip over and
buy something every year. And one of the biggest
[38:30] struggles that we have is that enterprises are not
investing in a software and a tool right now and
[38:35] everything around it. And every time someone gets
fired, they flip around and they try something
[38:40] new. And we have people that we started working
with, you know, two years ago and they said, "Oh,
[38:44] we're going to build this ourselves now that,
you know, OpenAI real timeout is whatever. Two
[38:49] years later, they spent a lot more money than
they would have spent on us." Um, because a
[38:53] lot of it is bringing in this outside party whose
job is to deliver outcomes. And our job is to use
[38:58] that software to leverage and and deliver that
at a much higher pace and route. Um, and then
[39:04] ultimately like make sure that we're driving
business value for you. And if that means going
[39:09] and filling in the metadata, then that's what we
will actually go do to get it done. I mean, that's
[39:15] actually the Palanteer model, right? Imagine going
to the government and build out software for them
[39:20] and catch Osama bin Laden. [laughter] That's what
it took. Yeah. I I think that's I mean I think
[39:26] that's actually a really interesting point in like
making some bets and investments in the companies
[39:30] that you're going to stick with because I I agree
with that part. I think the other thing that like
[39:34] for me because I work across quite a few different
departments um is like so if we built that for the
[39:41] call center then I want to make sure that we're
thinking about how that then maps into like the
[39:46] broader data ecosystem. So I'd be curious how I
can I ask a question um I'm curious no please but
[39:53] u two-minute warning so make it fast and we are
going to wrap it up. Okay. Um how do you do that?
[39:57] how when you guys are talking to these customers
specifically about the outcomes and call centers,
[40:01] how do you have the broader conversation about
the web and app and you know everything else
[40:05] that's trying to use that same context? Man, it
there's a lot of CTOs out there with AI psychosis
[40:10] right now. Uh and they're basically jumping in
between different things very fast. And a big part
[40:15] of our job is that we are there because to give
permission to the enterprise to go do something to
[40:21] do it in a new way and to actually transform. um
we're giving them an excuse to say we're throwing
[40:26] out the playbook uh because Xpland is helping to
do this and this is the way they say to do it. Um,
[40:31] and what we have to do is drive focus. And so my
job is going to be to get the call center outcomes
[40:38] right. And if someone wants to talk to me about
the website and chat, then our answer is going
[40:42] to be not until we finish this call center piece
because it requires so much discipline and follow
[40:47] through. And it burns us sometimes to be honest
because then someone comes in and does the web and
[40:52] it trickles over. But those enterprises that don't
have the discipline to go piece by piece lose
[40:56] a lot of times is what we see. Catch these guys
outside after the panel. So, I got rapid fire for
[41:01] you guys. Okay. So, I'm going to start here. Five
hour work week versus 35 hours. Five hours. So,
[41:08] I could spend more time with my family. Perfect.
Five. What is 996? Five. All right. Next one. Um,
[41:16] Bachelor of Science, Electrical Engineering versus
Master Electrician. Isaiah. Bachelor of Science.
[41:23] Bachelor of Science. Electrician. I think I'd take
electrician, too. All right. You do great. Uh,
[41:30] open source versus proprietary models. Uh, open
source. Open source. Open source. Open source.
[41:37] Right. Very good. Regulating AI now versus
three years from now. From here. Now. Now.
[41:44] Three years from now. Three years from
now. All right. Um, last but not least,
[41:50] Nvidia export control versus free market. Export
control. Export control. Export control. I am not
[41:59] familiar with this one. So, I'll go with
the [laughter] Well, with that, thank you