How AI Helped Me Ship 9 Months of Product in 5 Days | Sriram Iyer, SVP of Product (ex-Salesforce)
SVP of Product Sriram Iyer explains how he compressed a nine-month roadmap into five days — and why the only thing standing between most teams and that kind of speed isn't technology, it's trust.
A program manager told Sriram Iyer it would take 6 to 9 months to ship the first slice of their new product. Sriram challenged the team to do it in just five days.
At first, they laughed. Then he rolled his sleeves up, dug in with the team, and they did it. 5 days, from Monday to Friday.
Sriram has spent his career walking into companies like Salesforce, Adobe, and Freshworks, and pulling timelines apart. He calls himself the Simplifier-in-Chief, and the secret isn't the AI tooling. It's everything underneath the AI tooling that most leaders won't actually do.
In this episode, we talk about:
Why most slow organizations aren’t suffering from a tech problem — they have a trust deficit
How Sriram shipped a new vertical in just five days that a program manager had scoped for nine months
Why the real constraint on AI adoption isn’t tools or budget — it’s mindset
1. Shipping in 5 days instead of 9 months
Sriram walked into a leadership meeting where 20 senior leaders were staring at a program plan with a first deliverable set to launch six to nine months out. He asked why not six weeks — then raised the stakes.
“I said, ‘I want this shipped in six days.’ And that’s when the pin dropped.”
First, three days before the sprint even started, the team identified the thinnest viable slice: not a prototype, not a POC, but “live production code” that was still “consumable” — like a slice of pizza that “still has all the toppings.”
Then came a key insight most teams skip: they didn’t need to find external customers to validate it.
“We have people in this company who are employees, but who are also potential customers, so why don’t we go ahead and talk to them?”
Those internal customer-zeros became part of the tiger team itself.
The sprint ran Monday 8 AM to Friday 5 PM — a co-located team, unlimited food, and a $1,000 bonus on the line. And woven throughout, implicitly, was the AI layer:
“The designer had Figma Make. The engineers had Cursor, and we came up with our own tool to write PRDs using Claude Code.”
By Friday, something real was shipped. It was hidden behind a flag, but in production, testable, and generating valid feedback.
2. The real AI constraint isn't tools — it's mindset
By 2026, the procurement debate is over. Most companies have already approved AI tools and written the costs into their budgets. The question being asked now isn’t which tool — it’s how we can prove the AI is working.
But Sriram’s observation is sharper than that. The bottleneck was never the tools.
“The real constraint is mindset. Imagine five hundred engineers, all of them with this tool to their disposal. Is every engineer using it the same way? The answer is clearly no.”
Some engineers are leaning in hard. Others aren’t. So the move isn’t a company-wide mandate or a training program — it’s finding the five who are already aggressive, already breaking barriers, and building the experiment around them.
“You have to find those five engineers... who have the mindset to say, ‘Yeah, let’s go ahead and break barriers, and let’s make this thing happen.’”
Then, let the results do the talking. Once the rest of the org sees what five people shipped in a week, something will shift.
“That energy, that enthusiasm is infectious. And once you show that this is doable in five days, others say, ‘Hey, I wanna be a part of that magic.’”
3. Why product managers still matter (and always will)
A lot of PMs right now are quietly asking whether their role is shrinking. If AI can write PRDs, generate specs, and prototype in minutes, what’s left?
Sriram’s answer is direct: you’re asking the wrong question.
“In the world of AI, someone’s got to answer the question, ‘Why are we doing this? What is the business rationale behind this? What is the thesis?’”
AI is exceptional at execution. It can’t tell you what’s worth executing on. And that distinction — between doing and deciding what to do — is exactly where product managers thrive.
The deeper point is about uncertainty. Every real business decision exists in a gray zone where the data doesn’t give you a clean answer. Someone has to read that room, synthesize the competing signals, and stake a position.
“There’s always gonna be a zone of gray in real life, in real business. So the product manager who can bring clarity to that room, define the why, define the thesis, and show direction is still worth amazing. No AI is going to be able to do that for you.”
The skills that made great PMs twenty years ago: clarity of thinking, customer empathy, the ability to define a thesis and defend it, aren’t becoming less valuable. They’re becoming the last defensible moat.
Chapters
00:00 Introduction
02:40 How growing up in a small business shaped Sriram's leadership style
05:14 Sriram's first principles thinking
07:11 The "thinnest slice of pizza" framework that kills scope creep
12:01 How AI tools like Cursor and Figma Make made the sprint possible
13:45 Why mindset (not tooling) is the real constraint in any org
16:32 Applying the same audacity to revenue: why not 100% growth?
20:25 Building a repeatable framework, not just a one-time stunt
22:59 Why trust and personal accountability are what make teams follow you
27:18 The product manager's role in a world where AI can do everything else
28:42 Conclusion
What does LogRocket do?
LogRocket’s Galileo AI watches user sessions for you and surfaces the technical and usability issues holding back your web and mobile apps. Understand where your users are struggling by trying it for free at LogRocket.com.