💡

InsightHunt

Hunt the Insights

B

Bret Taylor

Episode #42

Co-founder & CEO, Sierra

Sierra

🎯Product Strategy🚀Career & Leadership⚡Execution📈Growth & Metrics

📝Full Transcript

16,530 words
Lenny Rachitsky (00:00:00): You're CTO of Meta. You are a co-CEO of Salesforce, you're chairman of the board at OpenAI. How do you think the AI market is going to play out? Bret Taylor (00:00:07): The whole market is going to go towards agents. I think the whole market is going to go towards outcomes-based pricing. It's just so obviously the correct way to build and sell software. Lenny Rachitsky (00:00:16): This makes me think about, I had Marc Benioff on the podcast. You guys were co-CEOs. He was extremely agent-pilled. Bret Taylor (00:00:21): It's so hard to sell productivity software, which I learned the hard way. Lenny Rachitsky (00:00:24): What's a story that comes to mind when you think about your biggest mistake? Bret Taylor (00:00:27): I was the product manager for, it was called Google Local had a pretty tough product review with Marissa and Larry, and to not do that well with a link from the Google homepage is embarrassing. Lenny Rachitsky (00:00:37): I think it's really empowering for people to hear it's possible to succeed in spite of a massive failure like this. Bret Taylor (00:00:41): They gave me another shot to do the V2 of it that resulted in Google Maps. We got about 10 million people using it on the first day. Lenny Rachitsky (00:00:48): What mindset contributed to you being successful in such a variety of roles? Bret Taylor (00:00:52): Waking up every morning, what is the most impactful thing I could do today? Lenny Rachitsky (00:00:56): Today, my guest is Bret Taylor. Bret is an absolute legendary builder and founder. He co-created Google Maps at Google. He co-founded the social network, FriendFeed invented the like button and the real-time newsfeed, which he sold to Facebook. He then became CTO at Facebook. He then started a productivity company called Quip, which he sold to Salesforce for $750 million. He then became co-CEO of Salesforce. He's also currently chairman of the board at OpenAI. At one point he was chairman of the board ...

💡 Key Takeaways

  • 1Stop digitizing analog behaviors; instead, deconstruct the components and reassemble them into a digitally native experience (e.g., Google Maps vs. Yellow Pages).
  • 2Adopt 'Outcomes-Based Pricing' for AI products: Move away from seat-based or token-based models toward charging for successful resolutions or business outcomes.
  • 3Practice 'Identity-Agnostic Leadership': Don't let your background (e.g., engineering) dictate how you solve business problems; focus solely on the most impactful action of the day.
  • 4The 'Agentic Era' requires a shift in go-to-market strategy: Direct sales is returning because AI agents often have a disconnect between the end-user (employee) and the buyer (procurement/finance).
  • 5For AI development, shift from 'fixing code' to 'Root Cause Context Engineering': If an AI makes a mistake, don't just fix the output; fix the context (MCP) so the error becomes impossible.
  • 6When seeking advice, ask 'Why?' repeatedly to understand the advisor's underlying framework rather than just accepting their rule of thumb.
  • 7The future of coding is 'Systems Thinking': As AI writes syntax, the human role shifts to verifying system integrity, security, and architecture.

📚Methodologies (4)

🎯 Product Strategy

Instead of porting an existing solution to the web/mobile (digitizing the Yellow Pages), break the problem down into its component parts (the 'Legos') and reassemble them into a hierarchy that is only possible through technology.

Core Principles

  • 1.Identify the incumbent solution (e.g., The Yellow Pages or MapQuest paper-style maps).
  • 2.Deconstruct the solution into component capabilities (Local search, driving directions, satellite imagery, business listings).
  • 3.Invert the hierarchy: Make the secondary feature the primary canvas (e.g., making the Map the canvas rather than a sidebar image).
  • +1 more...

"Disassembling the Lego set and reassembling into something new rather than just digitizing what was there before."

#deconstruction#strategy#product
View Deep Dive →
🚀 Career & Leadership

A daily ritual to detach your professional identity from your actions, ensuring you are working on what the company needs rather than what you find comfortable.

Core Principles

  • 1.Wake up and ask: 'What is the most impactful thing I could do today?' irrespective of job title.
  • 2.Identify your 'Single Issue Voter' bias: Recognize if you are defaulting to engineering, design, or sales solutions because of your background.
  • 3.Reframe the job: If you are an Engineering Manager but the biggest fire is recruiting, your job is now Chief Recruiter.
  • +1 more...

"I realized this subconscious limiter... I was trying to conform the job to the things I thought I liked to do."

#identity-agnostic#impact#audit
View Deep Dive →
⚡ Execution

A framework for selecting between Developer-Led, Product-Led Growth (PLG), or Direct Sales based on who holds the credit card and who touches the keyboard.

Core Principles

  • 1.Developer-Led (e.g., Stripe): Use when the product is a platform/API and the individual engineer has the latitude to choose the solution.
  • 2.Product-Led Growth (e.g., Shopify): Use when the User and the Buyer are the same person (e.g., small business owner) and self-service is possible.
  • 3.Direct Sales (e.g., Salesforce/Sierra): Use when the User (e.g., customer support agent) is different from the Buyer (e.g., VP of Finance). PLG fails here because the user cannot authorize the spend.
  • +1 more...

"If PLG means that you aren't actually engaging with the buyer of your software, you're not going to grow."

#gtm-buyer#matrix#execution
View Deep Dive →
📈 Growth & Metrics

A pricing strategy for autonomous agents where customers are charged per successful resolution or defined outcome, rather than per seat or per token.

Core Principles

  • 1.Autonomy: The software must be able to complete a job independently (e.g., resolve a customer support ticket).
  • 2.Measurability: The outcome must be binary and verifiable (Ticket Closed vs. Ticket Escalated).
  • 3.Alignment: Ensure the pricing model aligns the vendor's incentives with the customer's success (getting paid only when the problem is solved).
  • +1 more...

"I think the whole market is going to go towards outcomes-based pricing. It's just so obviously the correct way to build and sell software."

#outcomes-based#pricing#growth
View Deep Dive →
← Browse All Episodes