How I AI

Kath Korevec is a member of the Product staff at OpenAI working on Codex, and she spent over a year building and using ChatGPT Sites internally before its public launch. She’s been on the front lines of shipping Plugin Insights, MCP plugin hosting, and the connector ecosystem, which now includes around 60 integrations.

What you’ll learn:

1. What Plugin Insights actually does, and why it changes who can use a site
2. The incident command site Kath built for her OpenAI team, and how it uses live Slack and Notion connectors
3. The one phrase that tells Codex to wire up connectors for you
4. The infrastructure layer inside Sites that most people haven’t touched yet
5. How Kath fixed her Spotify after her kids wrecked it, using Reddit and computer use
6. The skill distribution model behind her community dungeon crawler, and why it’s a new way to think about collaboration
7. Why model speed is what actually determines how creative you get
8. Where Kath draws a hard line on AI acting in her name

—

Brought to you by:

Merge—Connective infrastructure for production AI

Vanta—Automate compliance and simplify security

—

In this episode, we cover:

(00:00) Welcome and intro

(01:00) Sites: internal testing and use cases

(05:53) Sites infrastructure

(09:00) Kath’s favorite connectors

(11:10) Unique ways to use Sites

(12:28) Curating a custom Spotify playlist

(15:50) Game design and development

(25:42) Bringing inference into Sites: the widget experiment

(30:00) Awesome Sites gallery

(31:57) Kath’s prompting strategy

(34:20) Wrap-up and how to find Kath

—

Tools referenced:

• ChatGPT Sites: https://chatgpt.com/sites

• OpenAI Codex: https://openai.com/codex

—

Other references:

• OpenAI DevDay: https://openai.com/devday

• Awesome Sites: https://awesomesites.ai

—

Where to find Kath Korevec:

LinkedIn: https://www.linkedin.com/in/kathleensimpson/?isSelfProfile=false

X: https://x.com/simpsoka

—

Where to find Claire Vo:

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

Website: https://clairevo.com/

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

X: https://x.com/clairevo

—

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

John Lindquist created egghead.io, a developer education platform used by hundreds of thousands of working engineers. These days he’s building mega.dev, a hands-on program specifically for developers who want to do real work with AI agents, not just prototype them.

What you’ll learn:

1. Why Jev is a decision engine, not a chatbot, and what that distinction actually changes about how you build
2. How John built a real-time voice to-do app that classifies and executes commands with no visible pause
3. The data deduplication pattern that merges messy records in milliseconds using confidence scores
4. Why Jev works best as a router, and how a single text input can navigate users deep into an app
5. What a chess match between Jev and a low-reasoning LLM reveals about speed, cost, and when to use which
6. The multi-step classification pattern John reaches for when one Jev pass isn’t enough
7. Where Jev falls short, and when you should still reach for a full generative model

—

Brought to you by:

Vanta—Automate compliance and simplify security

—

In this episode, we cover:

(00:00) John Lindquist returns for Jev week

(04:32) What Jev actually outputs

(06:15) Demo: real-time voice to-do app

(08:17) How sequential Jev calls chain together

(10:38) Demo: plain English to function name (grocery cart)

(11:50) Demo: data deduplication and record merging

(13:45) Confidence scores and multi-model validation

(15:06) Demo: Jev as a multi-level app router

(18:23) Architecting around Jev

(19:35) Demo: Jev vs. traditional LLM at chess (speed and cost benchmarks)

(24:29) DOM interactions as a decision set, not an infinite canvas

(28:21) Demo: Wikipedia “path to philosophy” route mapper

(30:28) Demo: multi-agent coordination and collision avoidance

(33:36) Demo: real-time presentation coach

(36:56) Quick recap

(39:54) Lightning round and final thoughts

—

Tools referenced:

• Jev (TypeSafe AI decision model): https://typesafe.ai/blog/introducing-system-one-models-and-jev

• Vercel AI Gateway: https://vercel.com/docs/ai-gateway

• OpenRouter: https://openrouter.ai

• Opus 5.5 (mentioned in context of iterative demo building): https://www.anthropic.com/claude-opus-5-5

—

Where to find John Lindquist:

LinkedIn: linkedin.com/in/john-lindquist-84230766

X: https://x.com/johnlindquist

Mega.dev: https://mega.dev/

Egghead.io: https://egghead.io/

—

Where to find Claire Vo:

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

Website: https://clairevo.com/

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

X: https://x.com/clairevo

—

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

I spent the day at OpenAI’s DevDay in San Francisco, and I have good news and bad news: OpenAI released a lot of stuff.

In this episode, I break down the announcements worth paying attention to - and show you what happened when I tested some of them early. We’ll meet my Dot, explore why Spaces and Sites could matter for how teams work, and get into the model and API updates I’m most excited about as a developer.

I use the Decisions API to find podcast thumbnails where nobody looks awkward, build a collaborative sketchpad with Astra ultrafast, and let my kids redesign a 3D world in real time. That last experiment cost about $97. My wallet has thoughts.

These are my early impressions: what’s promising, what still feels rough, and what I think you should try first.

What you’ll learn:

1. What OpenAI’s Dots can do, how I’ve been using mine, and why I’m waiting to give a full verdict
2. Why Spaces might be one of the most underhyped announcements for collaboration between humans and agents
3. How Sites with connectors and plugins could help teams share internal tools with the right data permissions
4. Where GPT-6.1 Sol fits in my model stack—and why speed and cost matter
5. What vision adds to the Decisions API, including my thumbnail-selection and hot dog demos
6. What Astra ultrafast makes possible for interactive AI apps, from collaborative drawing to a changing 3D game
7. Where the speed feels magical, where the experience still needs work, and what it costs

—

In this episode, we cover:

(00:00) OpenAI DevDay recap—and pressing the Codex reset button

(00:58) Dots: early impressions and rough edges

(06:57) Spaces: working with humans and agents

(10:37) Sites, connectors, and sharing internal tools

(13:06) Models and platform: GPT-6.1 Sol

(14:36) Decisions API: fast decisions with vision

(15:27) Finding better podcast thumbnails with AI

(16:29) Hot dog or not hot dog?

(17:17) Astra ultrafast: speed, pricing, and possibilities

(18:50) The Other Pencil: drawing alongside AI

(19:45) Little Starship: a 3D world you can change with a prompt

(21:24) The $97 AI game—and what it makes possible

(22:25) Agents API, computer use, plugins, and plan updates

(23:03) What I’d try first

—

Tools referenced:

• ChatGPT: Dots, Spaces, and Sites: https://chatgpt.com/

• Codex: https://openai.com/codex/

• OpenAI API — GPT-6.1 Sol, Decisions API, and Astra ultrafast: https://platform.openai.com/

• Jev: https://typesafe.ai/

—

Other references:

• OpenAI DevDay 2026: https://devday.openai.com/

—

Where to find Claire Vo:

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

Website: https://clairevo.com/

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

X: https://x.com/clairevo

—

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

Jev is TypeSafe AI’s new decision model. It returns type-safe structured values (a choice, a score, a probability) instead of generated text, at 4 cents per million input tokens with no output charge. This week I ran it on five real projects: PR categorization, a meta-analysis of my own Claude and Codex sessions, Gmail triage, the ChatPRD product insights graph, and a live audience dashboard built from 4,500 YouTube comments.

What you’ll learn:

1. What makes Jev fundamentally different from every other model I’ve used
2. How I analyzed 1,700 PRs for 9 cents and what I found out about where my engineering effort actually went
3. The personal meta-analysis you can run on your own Claude and Codex sessions right now
4. Why I stopped using Jev alone, and what I pair it with now
5. How I turned 4,500 YouTube comments into a searchable audience dashboard for almost nothing
6. The real-time app I built in an afternoon that shows something surprising about Jev’s speed
7. Why Jev’s pricing model is different from any LLM I’ve used, and what it makes practical to build
8. The ChatPRD product insights project: 1,100 signals, 200,000 classifications, and what it cost me

—

Brought to you by:

OpenArt—An all-in-one AI creation platform for images, videos, music, audio, and more

—

In this episode, we cover:

(00:00) Jev launch and what makes it different from every other model

(02:49) Type-safe values explained

(05:28) Understanding Jev outputs

(07:39) Use case 1: PR categorization and pairwise clustering

(11:12) Use case 2: analyzing your own local Claude Code and Codex sessions

(13:00) Use case 3: Gmail triage with Jev scoring and LLM follow-up

(14:30) Use case 4: ChatPRD’s product insights graph

(18:17) Demo: How I AI audience signal dashboard

(22:14) Demo: voice-to-color emotion-mapping app

(25:16) Jev week recap and what’s coming in episode 2

—

Tools referenced:

• Jev (TypeSafe AI): https://typesafe.ai

• Vercel: https://vercel.com/ai

• GitHub API: https://docs.github.com/en/rest

• YouTube Data API v3: https://developers.google.com/youtube/v3

• OpenAI Realtime Voice API: https://platform.openai.com/docs/guides/realtime

• Gemini 3.5 Flash-Lite: https://ai.google.dev/gemini-api/docs/models/gemini-3.5-flash-lite

• API Ninjas Quotes API: https://api-ninjas.com/api/quotes

—

Where to find Claire Vo:

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

Website: https://clairevo.com/

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

X: https://x.com/clairevo

—

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

I got up early to record an Opus 5.5 review. Then Anthropic and OpenAI dropped new models on the same morning, and I decided to do something I’d never done before: take the How I AI bench live. I put GPT-6 Astra, GPT-6 Sol, Claude Opus 5.5, and more through the work I actually care about: emails, PRDs, frontend prototypes, backend work, long-running agents, SVGs, and video editing. I scored the outputs without knowing which model made them, so you get to watch me make predictions, change my mind, and reveal my own very inconsistent taste. Astra won my heart. Opus 5.5 won my week. Sol still has me split. There’s a creative result I got completely wrong, an LLM judge that disagreed with me, and a return to Barbie Bench: the 3D fashion game that keeps reminding me how far we have to go. The hands are tragic. AGI has not arrived.

What you’ll learn:

1. How I run the How I AI bench blind, and what gets an output a bad score before I even know which model made it
2. Why Astra won my heart while Opus 5.5 might be overall strongest, especially for long-running agents and B2B frontend
3. Where Sol still wins me over on clear writing, readable PRDs, and price
4. The character SVG results that completely overturned my prediction about Anthropic
5. What happened when I asked these models to edit video, and why I think skills explain part of the disappointment
6. Why an LLM judge disagreed with my rankings, and what it was rewarding that I wasn’t

—

In this episode, we cover:

(00:00) LIVE setup and new model launches

(01:30) What’s new in Opus 5.5, Sol, and Luna

(04:11) Guardrails, personality, and speed

(09:00) The How I AI bench and blind evaluation process

(11:31) Email and personal-productivity results

(13:50) Frontend prototype vibe checks

(24:10) Backend, agent personality, and long-running tasks

(28:25) SVG illustration test

(29:48) AI video-editing results

(30:43) Predictions before the reveal

(31:20) Barbie Bench: the 3D fashion-game test

(34:17) Results: Astra, Sol, and Opus 5.5

(35:04) Writing clarity and creative surprises

(36:51) Why the LLM judge disagreed with me

(37:24) What each model is actually best for

—

Tools referenced:

• Claude Opus 5.5: https://www.anthropic.com/claude-opus-5-5

• GPT-6 Sol and Luna: https://openai.com/index/introducing-gpt-6-sol-and-luna/

• Codex (OpenAI): https://openai.com/codex

—

Where to find Claire Vo:

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

Website: https://clairevo.com/

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

X: https://x.com/clairevo

—

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

I’ve been off Claude for months. Not because it got dumb, but because it got annoying. The rambling, the hedging, the preachy little disclaimers on tasks that didn’t need them. I moved most of my daily work to Codex and I didn’t miss it. Then Anthropic shipped Opus 5.5: 40% cheaper than Opus 5, faster, and with what they’re calling a fundamentally different alignment approach. I ran it for a week across real work, including four long-running agentic tasks, a full ChatPRD homepage redesign, an SVG benchmark, and one very firm refusal, and I’m ready to give you the honest verdict. There’s a lot to like. There are still two things that drive me a little crazy. And there’s one capability I genuinely wasn’t expecting.

What you’ll learn:

1. Why I walked away from Claude entirely, and what it took for me to come back
2. The real cost math on Opus 5.5 and why pricing matters more for agentic work than single prompts
3. What happened when I ran four long-running agentic tasks, including one that tried to manipulate Claude mid-run
4. Why Opus 5.5 is now my go-to for frontend prototyping, and where it still lets me down
5. The one capability I genuinely didn’t see coming, and no other model in my stack can match it
6. The moment Opus 5.5 told me flat-out no, and what that says about where Anthropic’s safety posture actually lands in practice
7. Where Codex still wins, and how I’m splitting my model stack after a full week of testing

—

In this episode:

(00:00) Why I stopped using Claude

(01:02) What Anthropic says Opus 5.5 is

(01:54) Cost, speed, and benchmark overview

(03:20) Safety, alignment, and the cybersecurity limits

(05:02) How I AI bench

(05:39) Voice test: is it actually not annoying?

(07:54) Long-running agentic task results

(10:50) Frontend prototyping

(17:23) Writing voice and email

(19:41) SVG illustrations

(20:46) Video editing

(21:42) My verdict: what it’s good at, what it still isn’t

—

Tools referenced:

• Claude Opus 5.5: https://www.anthropic.com/claude-opus-5-5

• ElevenLabs MCP connector: https://elevenlabs.io/mcp

• Codex (OpenAI): https://openai.com/codex

—

Where to find Claire Vo:

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

Website: https://clairevo.com/

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

X: https://x.com/clairevo

—

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

Zach Lloyd is the co-founder and CEO of Warp, an AI-powered terminal and software factory platform used by tens of thousands of engineers. Before Warp, he spent nearly a decade at Google, including time as a principal engineer on Google Sheets. He built Warp from the ground up as a modern, AI-native alternative to legacy terminals, and the team has since expanded into software factories: a full cloud-based system that takes an idea in Slack all the way through to a merged PR.

In this episode:

1. Why a software factory is more than a coding agent
2. The public Slack → Linear → GitHub → QA workflow
3. Human interactions per PR as a signal of automation and throughput
4. Why human review is still the bottleneck
5. Scoring agent runs, finding failure modes, and self-improving agent workflows
6. Replaying real tasks to choose model cost and quality tradeoffs
7. CEO workflows with Figma MCP, Granola, and research agents

—

Brought to you by:

DX—Engineering intelligence for the AI era

OpenArt—An all-in-one AI creation platform for images, videos, music, audio, and more

—

In this episode, we cover:

(00:00) Intro

(02:35) Warp’s AI software factory, Wilson

(09:23) Automatic factory triggers

(11:12) The engineering leader dashboard Zach wishes he’d had

(15:18) How code review is changing in an AI factory

(17:08) Tracking cost per PR across model configs

(18:47) Using LLM-as-a-judge to score every agent run

(20:02) Catching redundant tests

(22:19) How the factory self-improves from failed runs

(26:03) Quick recap

(28:33) Building a cost-quality Pareto chart for model selection

(31:35) How Zach uses AI for non-technical CEO work

(32:10) Figma MCP demo

(35:43) Granola MCP demo

(36:41) GOG CLI demo

(38:20) Thinking in parallel tasks instead of sequential ones

(40:42) Zach’s prompting strategy for factory tasks

(44:48) Where to find Zach

—

Tools referenced:

• Warp (AI terminal and software factories): https://warp.dev

• Warp Factories: https://warp.dev/factories

• Linear (project and issue tracking): https://linear.app

• GitHub (version control and PR management): https://github.com

• Slack (team communication and factory input layer): https://slack.com

• Sentry (crash reporting and automated issue triggers): https://sentry.io

• Figma (design, used via Figma MCP): https://figma.com

• Granola (AI meeting notes and MCP integration): https://granola.so

• Grok Bot (fast inference, cost/quality trade-off): https://x.ai/bot/guides/grok-bot-101

—

Where to find Zach:

X: https://x.com/ZachLloydTweets

—

Where to find Claire:

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

Website: https://clairevo.com/

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

X: https://x.com/clairevo

—

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

I spent a few hours putting Meta’s Muse, its new personal AI agent, through a real first-pass test: onboarding, calendar management, goal setting, a one-shot family morning newsletter, browser-based shopping, and the animated avatar that honestly surprised me.

What you’ll learn:

1. Why Muse is the best-designed personal agent I’ve tested, and what specifically made it feel that way
2. The one-shot family PDF Muse produced that Claude and Codex never quite nailed
3. How Muse’s permission model works, and why it’s different from every other agent I’ve used
4. Why I set up a sleep training goal in Muse, and what it revealed about agent tone
5. The activity feed feature I immediately wished Codex and Claude Code had
6. Where Muse failed, and what it says about the limits of this category right now
7. The animated avatar decision that showed me what top-of-craft AI product design actually looks like

—

Brought to you by:

Optimizely—Your AI agent orchestration platform for marketing and digital teams

OpenArt—An all-in-one AI creation platform for images, videos, music, audio, and more

—

In this episode, we cover:

(00:00) What Muse is and who it’s actually built for

(04:41) Signing in and the onboarding flow

(07:16) The activity feed and its task lineage

(08:24) First real task: managing the family calendar and deleting soccer practice

(09:48) Requesting a morning newsletter PDF

(14:29) The personalized news feed and how I set it up

(16:05) The “Ideas” feature as an out-of-the-box prompt library

(17:10) Setting up personal goals (water, shoes, and sleep training)

(21:40) Library: documents, websites, images, videos, and podcasts

(23:11) Quick recap and what I love

(23:56) Activity feed design deep dive: tool calls and step-by-step lineage

(25:18) How Muse handles permissions

(26:12) The animated avatar: Polly becomes Slime, the teal dragon

(29:34) Browser use test: shopping for New Balance 9060s (not great)

(31:15) Browser use test 2: buying IMAX tickets for The Odyssey (much better)

(33:34) TL;DR and what I’ll actually use Muse for going forward

—

Tools referenced:

• Muse: https://muse.ai/

• Stripe Link (payment method featured in Muse): https://link.com

• 1Password (future Muse integration mentioned): https://1password.com

• OpenClaw (Claire’s previous personal agent setup): https://openclaw.ai/

• Grok Bot (Grok-based agent from prior stack): https://x.ai/news/introducing-grok-bot

• Codex (OpenAI coding agent, comparison point): https://openai.com/codex

• NotebookLM (Google, comparison to Muse’s podcast generation): https://notebooklm.google.com

—

Where to find Claire Vo:

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

Website: https://clairevo.com/

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

X: https://x.com/clairevo

—

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

John Bai and Peng Zheng are designers on the Grok Bot team at SpaceXAI, where they’re building one of the most talked-about AI products right now. John writes publicly about his design process (his piece “Designing Grok Bot with Grok Bot” has already made the rounds) and shares bot templates with the design community. Peng brings a product-design sensibility to personal tools, and his website doubles as a live demo of what he builds.

What you’ll learn:

1. How Peng built a self-updating personal website using Grok Bot as the entire backend pipeline, with no CMS and no Figma file
2. The exact check-in bot setup that lets Peng send a photo or a place name and have his portfolio update itself automatically
3. How John’s Figma Bro bot handles production design tasks while he’s at the gym
4. How John uses voice memos to direct Figma work through an MCP connection without opening his laptop
5. The “shower thought to prototype” workflow John uses with DevBot to test interaction ideas without first going through a product manager or engineer
6. The “trash can method” of software development
7. How both designers organize their personal bot ecosystems
8. What John and Peng actually think AI means for the future of design as a craft

—

Brought to you by:

WorkOS—Make your app enterprise-ready, with SSO, SCIM, RBAC, and more

Vanta—Automate compliance and simplify security

—

In this episode, we cover:

(00:00) Introducing John and Peng

(02:53) The Grok Bot hype train

(04:35) Peng’s self-updating personal website built with Grok Bot

(15:12) How AI makes design more accessible

(19:35) Website update result

(20:13) John’s Figma Bro bot

(23:35) Creating marketing materials for the bot marketplace

(26:00) DevBot: from shower thoughts to working prototypes

(28:48) The trash can method of software development

(31:19) Other bots John and Peng are using

(39:05) Practical tips for when bots don’t do what you want

—

Tools referenced:

• Grok Bot (xAI): https://x.ai/bot

• Figma: https://www.figma.com

• Figma MCP server: https://www.figma.com/mcp-catalog/

• Google Places API: https://developers.google.com/maps/documentation/places/web-service

• Notion: https://www.notion.so

• Swarm (Foursquare): https://www.swarmapp.com

—

Other references:

• Designing Grok Bot with Grok Bot: https://x.ai/bot/guides/designing-grok-bot-with-grok-bot

• Figma Bro bot template (shared by John Bai): https://x.ai/bot/marketplace/bots/figma-bro

• From zero coding background to hardware hacker: How Cursor + a Raspberry Pi makes AI fun: https://www.lennysnewsletter.com/p/from-zero-coding-background-to-hardware?utm_source=publication-search

—

Where to find John and Peng:

John Bai on X: https://x.com/johnbai

Peng Zheng on X: https://x.com/pengzheng_

—

Where to find Claire Vo:

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

Website: https://clairevo.com/

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

X: https://x.com/clairevo

—

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

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

What you’ll learn:

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

—

Brought to you by:

DX—Engineering intelligence for the AI era

Hyperagent—Deploy fleets of agents that handle real work

—

In this episode, we cover:

(00:00) Introducing Sharadh

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

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

(06:51) Projects as a governance layer

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

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

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

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

(20:41) Iterating on the dashboard

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

(29:07) How projects work

(34:18) Bespoke agents for bespoke use cases

(35:58) The skill builder workflow

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

(43:01) Recap

(45:13) Lightning round

—

Tools referenced:

• Trino: https://trino.io/

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

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

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

—

Where to find Sharadh Krishnamurthy:

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

—

Where to find Claire Vo:

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

Website: https://clairevo.com/

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

X: https://x.com/clairevo

—

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