How Srini Raghavan helped $3.4B SaaS Giant Freshworks Embrace the AI PDLC

Check out the conversation on Apple, Spotify and YouTube. Brought to you by* Customer.io - Send smarter messages using your product data* Ariso - The AI operating partner for every manager and team* Product Faculty - Get $150 off their #1 AI Builder Fellowship. Code AAKASH150* Land PM Job - Join me for Cohort 5 starting November 16th* Amplitude - Custom agents that monitor your funnel and file the ticket Today’s EpisodeFreshworks is a $3.4B giant of SaaS. They’ve been around since 2010. They have over 75,000 customers and 4,000 employees. Their 2026 revenue will be $960M.They’re a colossus.When Srini Raghavan joined them as Chief Product Officer, they had a 6 month release process. Under his tenure, they moved to a 2 week release cycle. They embraced a new way of working powered by AI.In today’s episode, he breaks down everything:* The AI PDLC they embraced* The AI Harness they created in Cursor, so it can run on any models* How the PM role shifted to Product BuilderIf you’re a product leader, this is a great example of how to become AI-native. If you’re a PM, it’s a great harness (using Grok models!) to learn from.I hope you enjoy it as much as I did:Apple | Spotify. | YouTubeI’ve written up the key takeaways for newsletter subscribers as well.1. The AI PDLC they EmbracedHow do you go from shipping every 6 months to every 2 weeks? It’s not about becoming AI first! Most teams try that: they open Cursor or Figma Make and start prompting. Srini made the point that it actually all begins with being Data First:When you’re data first, you create the right foundation to actually be AI first. At Freshworks scale, with 300 million end users, you can’t afford a hallucination. For Freshworks, that was three things:* A design system structured so agents can parse it* Coding standards written down explicitly* A single repo as the source of truthThey wrapped that all into a system they call Prism. It’s a knowledge hub that knows the product and its dependencies inside out, plus a context hub that passes feature context between phases, and a central library of what they call AI builder artifacts. These are the skills, rules, commands, and agents that describe how Freshworks specifically builds. The AI PDLC sits atop all of that. And it looks like this:It’s the same lifecycle every SaaS company runs from discovery through release, with two changes. First, there’s a governed AI agent working inside each. Second, there’s an evals phase at the end. And that’s how their release cycle went from 6 months to 2 weeks.But even in the episode, there were some cracks. Figma Make skipped a few design system components. Srini noted that those are the places where humans still have a role. 2. The AI Harness in Cursor they createdI began in engineering. After 14 years of not touching code, now I’m spending a lot of time in Cursor.Srini is now spending lots of time in Cursor, and he showed us. Everything starts with a slash command, <stro