How do product managers and engineers need to work differently in the AI era compared to traditional SaaS product development?
Answered at 9:58 in Everyone Is Still Undersizing the AI Market | Eric Vishria · Invest Like The Best
How do product managers and engineers need to work differently in the AI era compared to traditional SaaS product development?
In traditional product management, product managers understood customer problems but didn't specify implementation—that was the engineer's job. In the AI era, you must understand the jagged edge of model capabilities (what they're great at and where they fail), understand the customer problem, and bridge those gaps to build valuable solutions. You cannot do traditional product management anymore; you actually need to understand the nuances of model capabilities and put them together with customer problems. This mirrors how Cursor evolved from IDE to Tab Autocomplete to Agentic work, constantly iterating as the edge of capabilities changed.
Full answer and detailsRead the whole answer, key facts and every other question from this episode
In short
In traditional product management, product managers understood customer problems but didn't specify implementation—that was the engineer's job.
Eric Vishria, Venture Partner at Sequoia Capital · Everyone Is Still Undersizing the AI Market | Eric Vishria · Invest Like The Best · answer at 9:58
Key takeaways
- In traditional product management, product managers understood customer problems but didn't specify implementation—that was the engineer's job.
Quote to remember
“Every single day that you are hitting your plan, you are destroying equity value. Every day you hit that plan, you're fucking up. You're destroying value.”
— Eric Vishria
The full answer · about 3 min
In traditional product management, product managers understood customer problems but didn't specify implementation—that was the engineer's job. In the AI era, you must understand the jagged edge of model capabilities (what they're great at and where they fail), understand the customer problem, and bridge those gaps to build valuable solutions. You cannot do traditional product management anymore; you actually need to understand the nuances of model capabilities and put them together with customer problems. This mirrors how Cursor evolved from IDE to Tab Autocomplete to Agentic work, constantly iterating as the edge of capabilities changed.
Key facts
- Fireworks achieves 5x performance difference versus cloud providers on same models and hardware
- AWS S3 and EC2 launched in 2006
- Bezos discussed AWS importance in 2007 annual letter; investor reaction was poor
- In 2014, smart investors would have gone 0 for 30 correctly predicting AWS long-term margins
- Cloud computing roughly 40-30-20 split between AWS, Azure/GCP by 2026
People, companies and topics mentioned
More answers from this episode
- 1:19Why does Fireworks achieve 5x performance difference compared to cloud providers running the same open source models on identical NVIDIA hardware?
- 3:37What did AWS investor sentiment reveal about predicting long-term margin sustainability in infrastructure businesses in 2007?
- 4:47How did the market size for cloud infrastructure prove wrong the 2014 narrative that AWS would consume all enterprise software opportunities?
- 7:10What does the comparison between cloud adoption timelines and current AI adoption reveal about enterprise readiness in 2025?