The Chief AI Officer Show

Christian Napier On Government AI Deployment: Why Productivity Tools Worked But Chatbots Didn't

The Chief AI Officer Show

Show Notes

Utah's tax chatbot pilot exposed the non-deterministic problem every enterprise faces: initial LLM accuracy hit 65-70% when judged by expert panels, with another 20-25% partially correct. After months of iteration, three of four vendors delivered strong enough results for Utah to make a vendor selection and begin production deployment. Christian Napier, Director of AI for Utah's Division of Technology Services, explains why the gap between proof of concept and production is where AI budgets and timelines collapse. His team deployed Gemini across state agencies with over 9,000 active users collectively saving nearly 12,000 hours per week. Meanwhile, agency-specific knowledge chatbots struggle with optional adoption, competing against decades of human expertise. The bigger constraint isn't technical. Vendor quotes for the same citizen-facing solution dropped from eight figures to five during negotiations as pricing models shifted. When procurement cycles run 18 months and foundation models deprecate quarterly, traditional budgeting breaks. Topics discussed: Expert panel evaluation methodology for testing LLM accuracy in regulated tax advice scenarios

Low-code AI platforms reaching capability limits on complex use cases requiring pro-code solutions

Avoiding $5 million in potential annual licensing costs through Google Workspace AI integration timing

Tracking self-reported productivity gains of 12,000 hours weekly across 9,000 active users

AI Factory process requiring privacy impact assessments and security reviews before any pilots

Vendor pricing dropping from eight-figure to five-figure quotes as commercial models evolved

Forcing adoption through infrastructure replacement when legacy HR platform went read-only

Separating automation opportunities from optional tools competing with existing workflows

Digital identity requirements for future agent-to-government transactions and authorization

Regulatory relief exploration for AI applications in licensed professions like mental health

More from The Chief AI Officer Show

Aug 20, 2026

98% of IT leaders say they're using AI, yet 43% aren't measuring ROI and 80% admit they're not using it to its potential. Olga Lagunova, Chief Innovation and Technology Officer at GoTo, says the industry won the adoption battle but hasn't reached the outcomes it needs. Olga breaks down GoTo's federated AI steward model, where functional leaders own roadmaps and a central enablement team provides infrastructure. She explains why SMB pragmatism shaped their practical AI principles and how 39% of employees already report AI is eroding their skills.

May 28, 2026

Eric Ries built the Lean Startup methodology, helped advise on Anthropic's long-term benefit trust structure, and is now making an argument most enterprise leaders aren't ready to hear: deploying AI agents inside a company with bad governance isn't just a compliance risk, it's an existential one. His new book, Incorruptible, makes the case that the same slow-moving forces that corrupt companies over decades will be dramatically accelerated by AI, and that the standard governance playbook most executives have been handed is the actual source of the problem. In this conversation, Eric and Ben cover the legal and structural traps that silently strip companies of mission control long before anyone notices, why Anthropic walking away from a $200M Pentagon contract turned into an unexpected competitive advantage, and what AI leaders specifically need to do before they deploy agents at scale. Eric is direct about what he thinks leaders are getting dangerously wrong right now, and he pulls no punches. Topics Discussed: Why standard "best practice" corporate documents are structurally designed to separate mission from control

May 12, 2026

Intercom launched outcome-based pricing before the market had a framework for it, before inference costs made it profitable, and before customers knew how to budget for it. Fergal Reid, Chief AI Officer, was inside that decision and he shares exactly how they modeled their way through it, what two bets he personally owned, and why they went to $1 per resolution knowing it was a loss. That pricing story is inseparable from their model strategy. Fergal walks through the production data that led them to conclude that Opus 4.5 didn't outperform Sonnet 4.0 on their RAG customer service task, what that told them about the limits of general intelligence at the application layer, and why it pushed them to build Apex, their own model trained via reinforcement learning on an open-weight base specifically for customer service. With 85% of Intercom's own support volume now fully automated, the bets held. Topics discussed: Outcome-based pricing mechanics: the $2 beta, the loss-leader move to $1, and the two assumptions Fergal had to own

Apr 9, 2026

What happens when a journalist turned Amazon product manager becomes the Chief AI Officer of one of the world's largest international broadcasters? You get someone who sees the AI threat to media not just as a distribution problem, but as a full production chain crisis that requires a fundamentally different organizational architecture. Marie Kilg, Chief AI Officer at Deutsche Welle, makes the case that legacy media's survival depends on something most AI transformation conversations ignore: data interoperability across systems that were never designed to talk to each other. With 32 languages, siloed editorial teams, and decades of layered organizational structure, Deutsche Welle's path to an AI-powered content flywheel starts at the infrastructure layer, not the model layer. Topics Discussed: Why AI threatens the full media production chain, not just distribution

Mar 26, 2026

Most security leaders treat AI as a new threat category requiring new defenses. Rohit Parchuri, SVP and Chief Information Security Officer at Yext, pushes back hard on that. His argument: if your foundational controls are solid, AI does not require you to rebuild anything. What it does is amplify whatever you already have, gaps included, which makes the real question not "what new controls do we need?" but "how well are we actually executing on what we already built?" Rohit walks host Ben Gibert through how Yext is operationalizing this at scale: threat-modeling AI as just another system with inputs, processing, and outputs; building AI security testing directly into the existing CI/CD pipeline rather than standing it up as a separate track; investing heavily in data classification and taxonomy to solve DLP before deploying any AI tool internally; and establishing an AI Excellence Committee with cross-functional representation to run a single governance funnel across every AI request in the company. He also makes the case that the CISO who earns a seat at the AI strategy table is the one who deeply understands the business value chain, not just the threat landscape. Topics discussed: Threat-modeling AI as a system instead of a threat category

See all episodes →