Lenny's Podcast: Product | Career | Growth - Thinking beyond frameworks | Casey Winters (Pinterest, Eventbrite, Airbnb, Tinder, Canva, Reddit, Grubhub)
Episode Date: March 30, 2023Brought to you by Amplitude—Build better products | Eppo—Run reliable, impactful experiments | Ahrefs—Improve your website's SEO for free—Casey Winters is a longtime and legendary advisor and ...operator. He’s worked with companies like Airbnb, Faire, Canva, Whatnot, Thumbtack, Tinder, and Reddit and until recently was the Chief Product Officer at Eventbrite, where he managed the PM, design, research, and growth marketing teams. Before Eventbrite, he led growth and product teams at Pinterest and Grubhub. In today’s episode, we discuss what Casey calls the “zero interest rate phenomenon” product manager and how to avoid becoming one. He provides valuable insights on thinking outside popular frameworks, shipping products efficiently, and avoiding overreliance on user research. We explore the three types of network effects, how to leverage them, and how to break someone else’s network effect. Finally, Casey shares his contrarian approach to interviewing product managers and his thoughts on the future of PM roles with AI.—Find the full transcript at: Zhttps://www.lennysnewsletter.com/p/thinking-beyond-frameworks-casey—Where to find Casey Winters:• Twitter: https://twitter.com/onecaseman• LinkedIn: https://www.linkedin.com/in/caseywinters/• Blog: https://caseyaccidental.com/—Where to find Lenny:• Newsletter: https://www.lennysnewsletter.com• Twitter: https://twitter.com/lennysan• LinkedIn: https://www.linkedin.com/in/lennyrachitsky/—In this episode, we cover:(00:00) Casey’s background(03:36) What Casey is up to(05:24) Why the CPO position is frequently short-lived(07:26) What Casey learned in his role as CPO of Eventbrite(10:15) The “zero interest rate phenomenon” product manager(12:17) Advice for thinking outside common frameworks(18:35) When to bring in research(21:16) What Whatnot does(21:59) Casey’s approach to interviewing PMs (23:29) Red flags in interview responses(24:27) The future of product management with AI(27:47) Founder intuition vs. team expertise(33:33) How to influence founders(37:17) Adding the delivery driver app at Grubhub(40:00) Network effects(43:10) Why Zillow is a sticky product(44:05) How Grubhub’s network effect got taken over by DoorDash and Uber Eats(51:47) Don’t underestimate the competition(54:43) SaaS adding marketplace and vice versa(01:02:30) Defining marketplaces(1:03:34) What Substack is nailing(1:05:43) Tips for B2C subscription startups(1:13:15) Lightning round—Referenced:• Casey Winters on Lenny’s Podcast previously: https://www.lennyspodcast.com/how-to-sell-your-ideas-and-rise-within-your-company-casey-winters-eventbrite/• Whatnot: https://www.whatnot.com/• The 700-calorie breakfast you should eat if you want to live forever, according to futurist Ray Kurzweil: https://www.businessinsider.com/what-ray-kurzweil-eats-to-live-forever-2016-4• The Way of the Gun on Hulu: https://www.hulu.com/movie/the-way-of-the-gun-0fc9590c-3f85-48ab-96e9-1da1b9695065• Notion AI: https://www.notion.so/product/ai• Zapier: https://zapier.com/• Founder intuition vs. team expertise vs. customer expertise: https://caseyaccidental.com/founder-intuition-team-expertise/• Erika Warren on LinkedIn: https://www.linkedin.com/in/erika-warren/• Alyssa Ravasio (Hipcamp) on LinkedIn: https://www.linkedin.com/in/alyssa-ravasio-23114717/• Marketplace supply strategy: comprehensive, exclusive, or curated: https://a16z.com/2021/03/31/marketplace-supply-strategy/• Nassim Taleb on Twitter: https://twitter.com/nntaleb• The Innovator’s Dilemma: The Revolutionary Book That Will Change the Way You Do Business: https://www.amazon.com/Innovators-Dilemma-Revolutionary-Change-Business/dp/0062060244• OpenTable: https://www.opentable.com/• Booking.com: https://www.booking.com/• Faire: https://www.faire.com/• How to increase your retention: https://www.lennysnewsletter.com/p/how-to-increase-your-retention-issue• The Goal: A Process of Ongoing Improvement: https://www.amazon.com/Goal-Process-Ongoing-Improvement/dp/0884271951• Thinking, Fast and Slow: https://www.amazon.com/Thinking-Fast-Slow-Daniel-Kahneman/dp/0374533555/r• Profit from the Core: A Return to Growth in Turbulent Times: https://www.amazon.com/Profit-Core-Return-Growth-Turbulent/dp/1422131114/• Party Down on Starz: https://www.starz.com/us/en/series/party-down/2011• The Last of Us on HBO: https://www.hbo.com/the-last-of-us• Station Eleven on HBO Max: https://www.hbomax.com/series/urn:hbo:series:GYZWoOQ6F9cLDCAEAAABP• Kicking and Screaming on Netflix: https://www.netflix.com/title/70052286• Raven by Kelela on Spotify: https://open.spotify.com/album/06uhdSmIYrWRkdnAPjcRcT• Optical Delusion by Orbital on Spotify: https://open.spotify.com/album/2jQbFspnSh7erex6RDKQGJ• Stakes Is High by De La Soul on Spotify: https://open.spotify.com/album/3jlC2uhYNrhikZXLviEnpu—Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email podcast@lennyrachitsky.com. This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit www.lennysnewsletter.com/subscribe
Transcript
Discussion (0)
Every new person in the product team is acting like they work at Google and have these infinite resources and infinite time to make sure everything is perfect.
And there became such this focus on the right way of doing product management that no one's taken any risk.
And I felt like, oh, am I responsible for this?
Like I've created a bunch of, you know, frameworks on Reforge.
You know, I'm onboarding these UPS.
It's like, is this my fault?
But, you know, in Reforge, we're building frameworks that are tools.
in a toolkit. You pull them out when relevant. They're not a coloring book to stay, you know,
inside the lines of. Welcome to Lenny's podcast where I interview world class product leaders
and growth experts to learn from their hard-won experiences building and growing today's most
successful products. Today, my guest is Casey Winners. Casey was one of the first ever guests
on the podcast and the first to make a return appearance. He's a legend in the growth and product
community having worked with or advised companies like Pinterest, Reddit, Canva, Airbnb, Tinder,
Thumbtack, Grubhub, and many more. He recently led product at Eventbrite for just about three years
and recently returned to full-time advising and he's exploring new opportunities. In our chat,
we cover something he calls the zero interest rate phenomenon product manager and how to avoid
that. What he's found works best when interviewing product managers, what impact he expects from
GPT4 on the role of product management.
When to trust your instincts versus your team's insights and instincts?
What are all the different kinds of network effects and how do you effectively leverage
them?
Plus a great story about what Grubhub missed that led DoorDash and Uber Ether Lunch.
I always learned so much from chatting with Casey and I am 100% sure you will learn a lot
from this episode.
With that, I bring you Casey Winters after a short word from our sponsors.
This episode is brought to you by Amble.
If you're setting up your analytics stack but not using Amplitude, what are you doing?
Anyone can sell you analytics while Amplitude unlocks the power of your product and guides you
every step of the way.
Get the right data, ask the right questions, get the right answers, and make growth happen.
To get started with Amplitude for free, visit Amplitude.com.
Amplitude, power to your products.
This episode is brought to you by Epo.
Epo is a next generation
AB testing platform
built by Airbnb
alumni for modern growth teams
companies like Netlify,
Contentful, and Cameo
rely on Epo to power their experiments.
Wherever you work,
running experiments is increasingly essential
but there are no commercial tools
that integrate with a modern growth team stack.
This leads to wasted time building internal tools
or trying to run your experiments
through a clunky marketing tool.
When I was at Airbnb,
one of the things that I loved
about our experimentation platform,
was being able to easily slice results by device, by country, and by user stage.
Epo does all that and more, delivering results quickly, avoiding annoying prolonged analytics cycles,
and helping you easily get to the root cause of any issue you discover.
Epo lets you go beyond basic click-through metrics, and instead use your North Star metrics,
like activation, retention, subscriptions, and payments.
And Epo supports tests on the front end, the back end, email marketing, and even machine learning clients.
Check at Epo at getepo.com, get EPPO.com, and 10X your experiment velocity.
Casey, welcome back to the podcast.
Thanks, Lenin. Great to be here.
You're the first ever returned guest to my podcast. How does that feel?
I feel honored, perhaps a bit unworthy, but, you know, I'll go with it.
Well, you're both worthy and I'm honored as well.
So thanks for joining me again.
I have a lot of stuff that I want to chat about.
But first of all, I'm just curious, what are you up to these days?
I know you left Eventbrite as CPO.
I know you're doing a few advisorships with startups,
but how are you spending your days?
And what do you think is next for Casey Winners?
So I'm still spending some time with whatnot and Eventprite as advisors.
You know, I step back from the CPU of Eventbrite in October,
but still working on some long-term marketplace strategy stuff,
some gross strategy stuff.
I'm on the board of a company called Beak,
which is like Netflix for audio in Latin America.
And I'm doing some angel investing in marketplaces and what I call tech debt as a service,
which is, you know,
what are startups that are building out things that were hard for my teams in the past
to, like, build or maintain inside previous companies.
The other thing I'm working on is revamping the product strategy program for Reforge.
So I got some things keeping me busy, but definitely not as busy as I was last year.
This is like a rare free agent Casey Winner's time.
Should people reach out if they're interested and maybe working with you?
What's your advice for people listening?
Yeah, look, I always love seeing how I can help companies, right?
So everyone should err on the side, reaching out and seeing if I have time to help
if there's something they think I can help with.
I just, you know, I love talking to startups.
So, yeah, absolutely.
Like, can't promise anything.
But, yeah, I just love talking to people about this stuff.
Awesome.
And we'll point people to how to get in touch with you at the end of the episode and I'll be
in the show notes too.
But talking about the CPU role, so you're at Venbrate, your CPU.
It reminded me of a post you wrote about how hard the CPO role is.
And there's some quotes that I recall in your post about how, one, if you ever ask a CPO,
chief product officer, how they're doing, no one's ever going to say, I'm crushing it right now.
Yeah.
And then there's this other quote about how you basically, as a CPO, just try to put some points on the board before you inevitably get fired.
Why is that?
Why do you find that?
And do you still believe that to be true after, you know, leaving that role?
Yeah, I would say I still believe those things I said.
It was funny.
A product leader who will remain nameless emailed me when I hit year three at Eventbrite.
And they said, congrats.
You didn't get fired after two years.
What's your secrets?
You know,
I think it's very hard to keep product market fit as a CPU within a company for a long time.
You know, the needs to business shift over time.
And of course, we all have different strengths and weaknesses in our game.
Like, no one's perfect at everything.
And in general, you know, as an executive, it's just impossible to do everything.
perfectly. And any little misstep mistake or something you just missed can blow up in a major way.
You know, frequently CEOs have visions that can change and get misaligned with the product
leader. And also, you know, with leadership roles, you don't get put on a pip, right? Like,
if a CEO loses confidence, it's over immediately. So nothing like that happened at Eventbray. I
started to see that the areas of leverage for a product leader were just less in my wheelhouse over time.
And I just talked to my boss about it and you worked out something where I continue to advise on the things that I'm uniquely good at and find other people who are better at some of these other things that were maybe more important at the time.
But yeah, it's a really hard role or a really challenging role.
You know, it can be a lot of fun.
And I, you know, I learned a lot from doing it.
But yeah, I still believe and I think I've still yet to hear someone say they've really crushed it.
Is there anything that you learn from that experience to survive in that role for three years?
I imagine you have a lot of skills and you're very valuable to the company.
But I don't know.
For someone that's in that role, maybe right now, just like here's something that I did that maybe you should do.
The first one I can think of is a big change from being a product leader to a CPU or something equivalent.
is you're actually a company exec first and a product exec second.
So I think some mistakes I made, you know, early that I corrected successfully is you want to show
that you are caring and paying attention to the overall business first before just taking
care of your own, you know, product designers, product managers, researchers, whoever.
So that's, that's advice I found myself doling out to other product leaders a lot more now that
have, you know, gone through it.
You have to not only truly care, but create the perception that you care about sales, about marketing, about, you know, legal, et cetera.
Because first and foremost, you're expected to leave the business, you know, at that level.
So I think that's something that I think is really important.
And I think something else is really trying to diagnose without as much bias as possible.
Where are the strengths and weaknesses of your team, where the strengths and weaknesses of your product.
lay that out with your peers and say, here's where we are, here's where I think we need to go,
here's the timeline on which I'm going to work to get us there.
Because I think products such a confusing discipline for people who aren't in it,
like a sales leader, many CEOs, you know, marketing leader, that they don't necessarily
know what great looks like.
And the things they know about great leadership, they don't know if you know those
things. So you have to make it really clear. Yeah, I know our OKRs are not as quantitative as they
should be yet. That's because this team isn't ready for X, Y, and Z. This is where we're going to get
them to, but it's going to take some time. So one of the things we did at Eventbrite that I thought
was really helpful is, you know, when you go public, you tend to rotate over your executive team
and get public company execs versus startup execs. So a few of us were new. And it's just like,
hey, let's do a deep dive on product. Let's do a deep dive on customer support. Where is it at right?
now. What do you feel like your job is? What do you feel like are the issues you're facing?
Where do you want to take it over the next three to five years? And then let's talk about it.
And just forcing you to like write it all down is is really helpful. But then it forces you to
explain it. And it helps the rest of the executive team get better company execs because,
you know, now they really understand product a lot more deeply or understand finance a lot more
deeply, whatever the function is. Speaking of gaps and opportunities for
people in the company to level up.
You've kind of been highlighting this trend that I thought was really interesting,
something you call the zero interest rate phenomenon product manager.
Can you talk about what that is and what you've been noticing?
Yeah, sure thing.
So this is something I started noticing while managing PMs and product designers at Eventbrite,
and it's now coming up with whatnot as I hire, help them hire new PMs,
is the environment in which a lot of product managers have come up
is very distorted from when you and I started doing this kind of work.
I think we used to always describe PMs as, you know,
this gang of misfits.
We all started in different functions.
We all had different strengths and weaknesses.
And the PM team, you know, gained as a whole
from that diversity of skills and previous experiences.
So what I noticed is when we started doing product reviews of Embryde.
if there was any sort of like uncertainty in a problem or a solution,
the product manager instead of like shipping to learn would talk about all this research they have to do,
to really learn the problems, really learn a solution.
You know, and my feedback would be like, no, like we, you know, user research is a scarce resource.
We have to reserve it for the areas that have extreme uncertainty and high leverage for getting to certain.
So if you're redesigning the login page for events,
right, you don't need to use that resource to learn what to do.
Just go see what Fang and the top unicorns did.
They probably did a good job.
And even if they didn't, all of our customers also use those products.
So they're going to be familiar with us copying any approach that they've taken.
So I think we sort of forgot in the industry that many times the fastest way to learn is to ship.
So then, if you actually get them to skip research,
and just go look at competitors.
Another thing I was noticing is I'd get like a list of options
other companies have done.
But there would be no analysis of why those companies chose different options
and what's, you know, most applicable, you know, for us.
So it got me thinking like, okay, every new person in the product team
is acting like they work at Google and have these infinite resources
and infinite time to make sure everything is perfect.
and there became such this focus on the right way of doing product management that no one's taken any risk.
And I felt like, oh, am I responsible for this?
Like I've created a bunch of, you know, frameworks on Reforge.
You know, I'm onboarding these UPS.
It's like, is this my fault?
But, you know, in Reforge, we're building frameworks that are tools in a toolkit.
You pull them out when relevant.
They're not a coloring book, you know, to stay, you know, inside the lines of.
So at one point, I got so fed up, I wrote like an internal blog post and I called it on best practices and breakfast rituals.
And I talked about how there were these articles about the morning habits of the most successful people.
And if you try to do all those things, it'd take you like six hours every morning.
And there was this article, I think it was on Business Insider or something about this futurist at Google.
And he talked about all the pills and food heats for breakfast every morning to try to live longer.
and the reporter estimated that it cost him $1 million a year to have these habits.
So I was like, hey, I want to make it clear at Event Bright, we don't have that much money,
we don't have that much time.
There's no framework that allows you to not use your brain at this company and just follow
some sort of process for success in this profession.
So I adopted this thing into like a public blog post that's on my blog now.
But now that I've had some time outside of Eventbrite, I feel like I at least partially
missed the mark and what's really going on.
You know, I see this with like whatnot because one of the things I'm helping them with is
interviewing ICPMs again, which I haven't, you know, done in a while.
And it's fascinating interviewing a PM or managers early in their career because whatnot
it's a startup.
And, you know, you know, better than most of us as a former founder of one, startups typically
require us to wear lots of hats.
You have to write SQL.
You have to talk directly to customers.
You have to prep marketing in sales.
And most importantly, you have to make a lot of decisions under uncertainty,
which you wouldn't necessarily expect a PM to do, say, a Google.
But it all boils down to using your brain in different ways.
You know, Lisa, who's on our legal team, she called Eventbride a public startup
because the pandemic basically erased her business and we had to build it back from scratch.
So now that I'm doing these interviews and whether they come from a small startup,
a unicorn or a public company,
they all sort of look the same
because there's been so much funding
to all these companies.
Every company's been acting
like their Google with Google margins,
meaning a lot of engineering support,
a lot of design support,
a lot of research support,
lots of analysts around them.
And they actually seem pretty ill-prepared
for a real startup
or even a public company
with some uncertainty around it,
like Eventbrite.
So you start getting these weird responses
in the interview process.
You ask them to solve a problem
and they'd say things like,
I can't even begin to come up with solutions
until I see all the data and talk to customers.
And I'm like, yeah, I get that that's something you would normally do if you took the job.
But like, you don't have the data.
You can't talk to customers.
Make a decision now.
What would you do?
I want to see how creative you are.
I want to see how much you're intuiting about the real problem and the solution.
And they can't really answer.
And then, you know, my follow up, which I don't ask, but what I really want to ask is like,
so when's the last time you used your brain versus follow to process someone else designed at your company?
Because, like, I want the former, not the latter.
Wow. Amazing. There's a lot of things I want to dig into here. And I was going to ask why you call it zero interest rate phenomenon. But I think what I'm hearing is it's when interest rates are zero, everyone's got a lot of money. Things are going great. Everyone looks like they're killing it, successful. Everyone thinks they've got it all figured out. And then when that goes away, it's like, oh, shit, maybe not so.
And also I think zero interest rates allowed every startup to operate like it was a public company with billions of dollars.
And that's going to go away over the next five years.
And it sort of takes us back to what product management used to be like, which was, you know, you didn't have all these resources around.
You didn't have all this time to figure it out because if you don't figure it out now and make it work, you may run out of, you know, funding, right?
Yeah, like a very concrete thing that's changes.
A lot of research teams have been laid off because they grew really large in the company.
companies kind of found maybe we don't need the like if all the things we can cut it's probably
an area we can cut yep for sure there's probably pms listening to this wondering shoot am i one of
these just like following a bunch of frameworks what's your advice for someone that may fear that
oh shoot this is maybe who i am and i don't want to necessarily be this and what could they maybe do i always
advise going to companies where you can you know learn quickly and and try things right and i think
you know, it's certainly okay to like learn a bunch of frameworks.
There's a reason I've invested a ton of time in reforge
because I think it actually really does help people
to see how other people have built things in a way
that they can, you know, scale to their other companies.
But you have to understand that the job is not to follow the process.
The job is not to learn every framework possible.
The job is to figure out how to add value to customers
that translates into value to the business.
And, you know, just reorient your North Star
if you've gotten away from that.
when I joined Eventbrate, you know, there was this team that didn't ship anything in a quarter.
And, you know, I went to the designer who I knew and, you know, I know that he, you know, likes to get stuff out there and likes to get feedback.
And I was like, dude, you didn't ship anything.
Like, how could you have gone the entire quarter, not shipped any of your designs and felt that that was okay?
And if you didn't feel it was okay, why just censor yourself?
Come to me.
telling me why this team is not letting you ship.
There's just no way you can get better as a designer.
There's no way you can have the impact on the company.
There's no way you can have the impact on our users.
So, you know, those are some things that come to mind to that question.
So if you're a PM on a team that maybe isn't shipping, maybe he's overusing research,
do you have any advice of just like when it makes sense to invest in research?
Say you have the resources.
Like, is there kind of a rule of thumb you have of like, okay, let's actually spend the time on this for some?
I think about it a little bit, depending on the type of job you have and the types of customers you have.
So, you know, the more scale you have tends to be you have less sophisticated customers
because you're generally like, you know, a consumer thing where the customers are rational,
they're not experts.
And that's generally where you just try things, you measure the impact they have,
and you only really bring in research research when the impact seems confusing.
right, but you can run experiments, like you can get data really easily.
So biased towards, you know, getting stuff out there and seeing what users respond to.
In consumer, in consumer products.
Right.
If you're super enterprise, it's kind of the opposite, right?
Each customer, first off, is sophisticated and tend to be rational.
They're paying you like six figures or more.
And you could talk to the customers and sales.
Who knows the customers really well directly?
And they tell you what they want.
They tell you what they're willing to pay for.
You build it.
They pay you, bang, boom, right?
It's not obviously a super.
as that, but you're basically doing the research directly with the customer and with the sales team
and translating that the things that are strategic to the business.
And I would say those are the two extremes probably most people are familiar with.
But we now have a lot of companies in the middle where they have more customers.
Those customers are more sophisticated.
They're consumers.
There may be employees at companies or their small businesses.
And that's where you have to be more nuanced.
And this is, of course, where Eventbrite was.
on, hey, when do I really lean in on research?
When do I lean in on data?
When do I pay attention to internal feedback?
So, you know, for Eventbrite, we really tried to focus research on the B2B side of Eventbrite
where the problems seem big but not well defined enough.
Or that problem's well defined, but we just really don't feel like we have the right solution.
And, you know, if research is going to be a scarce resource inside the company, which I think
it will in most places, you have to figure out where it's a high leverage area, which means
either really big problem, we don't understand it well enough, or we know the problem's big,
we understand it well, but we're just not sure if our solution is going to, at any way,
like, you know, hit the mark.
Makes me think about some of the best researchers I've worked with, and they often tell me,
like, we don't need to do research on this.
We have enough information.
Like, we have other things we should be doing.
I love it when they say that, yes.
Yeah.
This would have been a really good segue to another topic I want to talk about, which is around
gut instincts.
versus team expertise, which we're going to get to.
But I have a couple more questions along these lines.
Sure.
You talked about interviewing PMs at WhatNot.
Can you usually describe What Not just because you mentioned a couple of times just so people
know we're talking about it.
Oh, sure.
So What Not's a live streaming marketplace.
Mostly focus on the collectibles market.
So, you know, sellers, whether it's like, you know, baseball cards or women's handbags
or sneakers, you know, they'll go live on video and show you the products they have that
they're selling and people who are watching the stream can engage with the sellers and bid on, you
know, different items. So kind of like Twitch meets eBay.
Awesome.
Awesome. And I'll just mention I'm a tiny angel investor in that company.
Oh, that's why you brought it up. Okay, I get it.
I just wanted to make sure people understood what this word was because it's like a fun word,
whatnot. But what I wanted to actually get to is you said you were interviewing a lot of product
managers for them. Yeah. What is your approach to interviewing PMs? What do you find is a really
good signal for someone that's going to be successful? I feel like the whole thing's gotten so
performative. It's like interviewing is handing out Oscars based on who's prepared the best
tell me about a time response versus actually assessing like who can do the job we're hiring for.
So it's like most PMs are better PM interviewers than PMs now. There's this quote
from a movie called The Way of the Gun. I don't know if you've ever seen it. But Benicio del Toro
says in it, it's like these days they want to be criminals more than they want to commit crime.
And I think about that quote a lot when it comes to interviewing. So,
So I would say I'm a big cotrarian here in my approach.
I don't ask about your work history.
I don't care about your perfectly practiced answers.
I'm going to give you real scenarios that I expect from the role.
I want to hear how you'd approach them.
And if you can't come up with a few reasonable ideas,
figure out how to test them quickly without analysts support or research,
I'm just not interested.
And I'm not saying this is a perfect approach.
Interviewing is a very lossy format.
But the more I can see them do the job we're hiring for with questions, whether it's a presentation, a prompt, that gets me the most comfortable that they know the job they're signing up for, that they've shown in a practice scenario they can do it. And they actually enjoyed it in some way.
Are there like red flags you look for in these interviews? Like one is maybe said over like, I can't even begin to answer this with that research and data. Is there anything else?
Some things I pay attention to is if they're talking about solutions that are going to take a long time to get signal from.
whether it's months and months of engineering time before you actually, you know, see the impact on users or the business.
I think that's, you know, always great.
If they're not factoring in the amount of time, it will take, in general is not, you know, a good sign and not thinking a bit more holistically about the types of metrics they expect to improve versus track to make sure, like, they haven't gone down.
Those are some things that I pay a lot of attention to you.
How much do you think they're intimidated by being interviewed by Casey Winters?
How much do you think that factors in?
I think you overestimate my importance or awareness in the community.
I think most people have no idea who I am when they start talking to me.
Well, I don't know.
Another thought is there's this meme that GPT4 is going to, or five or six or ten,
is going to replace product managers.
And anytime some new feature comes out, people will put out these videos of,
oh, look, they're doing all the PM's jobs.
What's your take on the future of PM and AI?
I think if you thought the PM job was just filling in the latest, you know, Reforge or Shreyaas framework and then getting, you know, that automatic Fang promotion every year and a half, then yeah, you're going to get replaced by AI. But I think the real PM job is the least likely to get replaced over time because you need, you know, real subject matter expertise. You need to, you know, be trading off a lot of different types of things and in making good decisions for the company and for your customers. So in terms of using, you know,
AI now as a PM, I'd actually be cautious in like the current iteration of the cycle for PMs.
Yeah, it's a tool that's trained on sounding smart rather than always necessarily being smart.
I was at Eventbrite the other day and someone was telling me how they were loving the new Notion AI integration.
And she asked me if I used it. I said, no. She's like, oh, you totally need to. Hey, go ask you your bio. It's really cool. And I said, all right, let's just do it on your screen.
So she did, and like my bio said I started my career at Google and worked on Google Trends and a bunch of other products, none of which happens.
Like it's just complete nonsense.
It did have some stuff that did happen.
It knew I worked at Eventbrite and it knew I worked at Pinterest and stuff.
But like half of it was just completely made up.
It sounded plausible, but it wasn't actually, you know, true.
I think where I'm more inclined for PMs to try to get leverage out of something like,
gpt four is a lot of the tedious work that's maybe not their specialty to begin with.
So, you know, if you're not great at like Excel or Google Sheets and you need to model something,
you can ask it out of format something. That'll probably be perfect. Or like how to get some
Zapier integration to work. Like it probably knows how to do that really well. So I think at
this point, it's a pretty good no code, low code tool. And it's obviously going to become a lot more
than that. But for a lot of these other use cases that people are touting, there's a decent chance
confidently tells you the wrong thing.
And that would scare me as a PM.
I've had the exact same experience.
I had it described what I've done
and it was like 70% mistaken.
Yep.
Is there anything you've found valuing yet
with GPT of any kind of in your work?
Or is it still kind of just poking around
in novelty for you?
Yeah, I've had a couple of those things
where it's like, hey, how do I actually get
this weird thing done?
And it's been like, you know,
clear a bullet point.
take these steps, and I'm like, oh, great.
Like, this was actually really hard to find on Google.
So things like that, I actually quite like it for.
So that's where my head goes to, like, more confidently use it.
Because, of course, I'll try it.
And if it's wrong, I'll learn where it's wrong.
So it's low risk.
But it's been right on some of those things.
And it's like, oh, cool, I couldn't figure out how to do that.
There's something on Google Docs that I need to figure out how to do that was kind of fancy.
I asked ChatGPT.
It told me how to do it.
And I was like, oh, great.
I had a similar experience where I just needed a formula in Google Sheets,
and I just told it like I need this thing and just gives me the actual formula.
Yeah, that's so magical when it happens.
Yeah, I don't know.
I'm not that good with Sheets formulas.
Shifting course a little bit,
you also wrote this really interesting post on founder intuition versus team expertise,
and there's a lot to it.
And I think it's a really interesting topic because it's this classic discussion that startups have.
How much should a founder trust their gut and how much should it be top of?
down, here's what we should be doing, versus the team kind of bottom up, figure out what to build.
And so I'd love to spend a little time here. So maybe just to start broadly, what is this?
You kind of came up with a framework of how to think about when founder intuition should overrule,
say, team expertise and how that changes over time. So maybe just talk about that.
If founders are lucky slash good enough to find product market fit, they've usually built up
all this intuition about their customers, about their product and their business that are
really hard to explain to others and may even be like subconscious.
So when they start to hire people, you know, these people will come in with a lot of, you know, excitement, ideas,
maybe even really relevant experience, especially, you know, senior leaders.
And I've seen some founders are like, cool, I need to let these experts start to own these areas and get out of the details.
And I think that's actually the opposite of what you want.
Because none of these people know the business as well as you get.
you actually need to direct them until they show you they've really got it and are making better decisions than you would.
So this is not a founder example, but I remember when I hired Erica Warren to build out our loyalty program at Grubup.
She now leads growth at Change.org.
And after a month or so, she was like, dude, you're in all my meetings.
I got this.
And that let me know.
She was in a different part of the situational leadership framework than I had put her in.
So I backed away and, you know, she crushed it from there.
Founders will put a lot of new leaders in that delegate bucket too quickly.
It's like, ah, it's theirs, they got it.
They know more than me when founders actually know the right answer and she just tell them.
And this can, of course, change like in the case of Erica, you know, if you hire the right people, they do get smart than you.
You can and should start delegating.
And many founders don't notice the signals where their founder intuition has been usurped by team expertise.
or maybe it's just ebbed in effectiveness over time.
And that, of course, makes sense, right?
Founders have all these different things they're dealing with,
and your employees can really dive deep in certain areas.
So I encourage employees to proactively signal both directions,
like, hey, I need direction from you, or, hey, I got it from here.
Trust me on this one.
Interesting.
So you're saying as a founder, the heuristic should be,
if you feel confident about a decision,
generally you should be clear like hey I think I know what we need to be doing here and don't just like make people feel better necessarily by just saying okay you tell us what you want to do and then on the flip side as a as an employee at the company if you feel really confident about something make it clear to the founder like I really think this is the right move is there anything more you want to add there yeah well I mean there's obviously the feedback group of that of like you know what happens when you do either of those things um so you know depending on the
the founder's response to that or the employee's response to that, there's kind of different
approaches, you know, you can take.
And part of this, yeah, this cool chart of just like over time, the founder expertise
becomes less and less relevant.
And I guess is that because they just don't spend as much time with the customers because
they have other stuff going on or they hire people that are smarter.
And then over time, team expertise goes up.
If you're lucky enough to scale a company, there's just more and more things going on
that all will reach the founder in some way.
but it means more breadth and less depth on any particular issue.
And the reverse is true for, you know, people you hire, right?
They're able to get really deep into things that maybe you were really deep into two years ago.
But, you know, you just can't, you can't stay deep in anymore.
So I built this, you know, chart on or I guess I should say table on the different phases of, you know, a startup, right?
And when you're finding product market fit, like everything goes through the founders.
You cannot outsource that.
And then, you know, when you start scaling the company, because you found product market fit,
it's the first time that founders run into this like classic problem of what got you here,
won't get you there.
What got you to product market fit was iterating on product and doing things that don't scale.
Guess what?
You found a product that works.
Don't do that anymore.
Make it scale.
Don't come up with new products.
You found the one that works.
The reason I came up with this, you know, framework originally is when I was at,
at Grubhub, you know, we were scaling pretty nicely and fairly organically. I think Mike and Matt,
the founders, had intuitive these phases of, like, building a company, like, pretty well. But we acquired
a competitor, and, you know, I saw how that company we acquired operated. And even though they were
largely in the same phase as us, they still operated like they were founding the company. Like,
everything was going through the founder. And, you know, intuitively, I was like, oh, this is why we're
requiring you and not the other way around. So I think it's really hard for founders to get those
signals organically. And I think it's up to us as employees to help. And, you know, the founders
can listen to the signals or not listen to those signals. But that's part of why we're here.
But we should also give those signals when we're confident we really get it. Not like come in day one
being I know what your sales strategy should be. You're doing it all wrong. Chances are the founders
weren't doing it all wrong. They knew something you don't know about yet.
what is it that you think made it such that you won and they didn't is it because they didn't invest they didn't shift to scaling and delegating to their employees as much as the founder just telling everyone correct right like the um everything was like not moving as quickly because everything had to go through the same person to get done so it just allowed them to not launch as many markets to not sign up as many restaurants to not figure out as many you know growth channels uh yeah as we had done got it so they just bottleneck themselves and they weren't able to move as fast because they
the founder thought they needed to make these decisions and they were still the ones that knew
everything.
Yep.
That makes me think about most companies, maybe not most, but many founders just like believe
they have the answers.
Like they are confident they know what to do.
Right.
And it's rare they get to a place of like, no, I actually don't.
Well, I would say no one gets to it super intuitively.
Mm-hmm.
Any advice for either as an employee at a company with a founder like that or leader of just
how to push back and help the founder understand.
Maybe you should let go and trust people to make decisions.
I think the first thing is you have to understand that it's their company, not yours,
and that founders have impossible jobs.
They're not going to scale perfectly with the needs of the company.
Like, it's just something's going to be off.
And it may be because there's a whole lot of hubris by being the one of a thousand
startups that made it, or, you know, they just have personal styles,
but they can run the company any way they want.
And I think it's sometimes surprising when founders actually want to run things suboptimally.
Like, I think we've seen examples where founders just want to build cool shit
versus focusing on what customers want.
Or they're too obsessed with the design.
They're always rebranding, redesigning things in ways that confuse customers.
And, you know, of course, that's going to happen.
And those are some of the worst cases.
But I think, you know, if you do state your point, you've actually built up the expertise, you're confident, and you are refuted for whatever reasons.
You have to find ways to be contrarian and prove you're right. And different founders have different forms of feedback they listen to.
It might be talking to other CEOs or other operators or trusted advisors, certain customers. Some might be very data oriented.
So you just run the experiment and ask for, you know, forgiveness after you prove it works, whatever.
Like, everyone's got like a different thing they respond to.
So you try to figure out what actually influences, you know, the CEO and build that case,
whether it's through an experiment, the right customer intro, the right external advisor.
And if they rebuke that as well, then you got to disagree and commit or find a new company to join or start your own.
Like I said, it's their company.
They can make the call.
I remember when I joined Pinterest, I was just coming off, you know, 100x increase in user growth from GrubHub.
And I was ready to drive the same sort of impact at Pinterest.
But no one knew who I was.
I didn't come from Facebook or Google like most of the other people are Pinterest.
No one gave a shit about Chicago startups at the time.
So, you know, when they didn't trust my proposals, I just went and talked to the heads of growth at all the startups they did respect.
I talked to Dropbox.
I talked to Facebook.
And when they said all the same things I was saying,
but I said that they said it, not me,
that was sadly more convincing.
But I didn't care because I still got what I wanted out of it,
which is to do the right thing to grow the company.
And now you're one of those people that people go to.
If Casey says it, it's probably the right way to do it.
Whether I'm correct or not,
it is a role I sometimes play in the ecosystem, I will admit.
There's an example where you were convinced something
was the right way to go on the founder
at one of the companies you worked at had a different
opinion and they were they ended up being right. When I was at Grubhub, one of the ideas, one of the founders came up with was to build an app for delivery drivers. So at the time, you know, restaurants had their own delivery drivers. They did not work for us. And we wanted to build an app for the delivery drivers so you could see where the food was along the way. So you can know if there's a five minutes way, whatever, right? Domino's was the first to have done this at the time. And we thought that would that would make a bunch of sense. And I was just like, how am I supposed to convince the delivery driver who doesn't have a relationship with. And
with us to download this app from Grubhubhub to actually turn it on to create, you know,
anxiety for the consumer of like they maybe didn't take the right turn or whatever.
I was like, I don't think this makes sense.
No one's going to use it.
And, you know, Mike and Matt like overruled me and pushed us to do it.
And in the long run, it ended up being quite necessary because of the innovations around
DoorDash and Postmates and later Uber Eats into having their own delivery network and
us needing to counter that.
That's, of course, a key piece of technology that needs to learn.
have parity with those new services.
So that was an area where perhaps they were thinking a little bit more longer term than I was.
And, you know, I was not able to kind of get where they were going on the longer term time horizon
of how this would be actually ultimately adopted in use school.
This is an awesome segue to the next area.
But real quick, how did they get drivers to start using this app?
Is there anything really clever they did?
I think it was fairly low adoption for a while and leveraging basically restaurant
authority. So if we're able to push on our restaurant customers effectively to say like, hey,
if you use this, it'll get you more orders, we'll get you prominence in the UI, things like that,
to them push down, you know, to their direct relationships with the drivers to get them to adopt.
Awesome. This episode is brought to you by Ahrefs. You probably know Ahrefs as one of the leading
all-in-one SEO tools used by companies like Facebook, Uber, Shopify, LinkedIn, Pinterest, and thousands more.
But HREFs is not just for big companies.
With their new H.RFs webmaster tools,
you can optimize your personal website, like a professional, for free.
You can scan your website for over 100 common SEO issues
that might be hurting your performance and search engines,
plus get advice on how to fix those errors.
You can have it automatically browse your website's internal and external links
and get actionable insights from your backlink profiles,
and you can learn what keywords your website ranks for
and see how you stack up against your competitors.
Visit H.RFs.com slash A.
and start improving your website's visibility.
That's hrfs.com slash a wt.
Okay, so shifting to our last topic that I was excited to chat about
is around network effects and marketplaces and SaaS
and kind of how those things connect.
I feel like you have the clearest way of thinking about
and explaining network effects.
So maybe just to start, can you just like simply explain
what is a network effect and then the different types of network effects that exist?
Yeah, no pressure after you say that, right?
Yeah, so at its core, a network effect is when a product or a business gets better with more users or customers using it.
And there's three types that I tend to focus on.
So the first and probably the most well known is it called direct network effects.
And that's when every additional user makes the product better for all the existing users.
So when someone joins WhatsApp, other people can talk to them that wouldn't be able to talk to them before.
and that makes what's at valuable, more valuable for everyone.
And then there are cross-side network effects
where there's two distinct types of users
and adding an additional user on one side of the network
makes it more valuable for all the types of users
on the other side of the network and vice versa.
So when a restaurant joins Grubhub,
it creates more selection for users to order food.
And when more users start ordering more food,
Grubhub becomes more attractive for restaurants to join
so they can make more money from delivery orders.
The last network effect I focus on is data network effects.
And that's when the quality or cost of something improves as more data is collected through the product.
So when you save content to Pinterest to a board, it gives Pinterest signal on the quality of that content,
it's relevance to other pieces of content since they're shared to the same board,
and more signal on your preferences.
And this allows Pinterest to better recommend more content to use.
as well as to other people who look like you and share similar interests.
So one thing that's tricky about these network effects is most people talk about network effects
in the context of social network, not marketplaces or SaaS like my background.
And the thing that's really tricky in understanding social networks is they're traditionally
described as these direct network effect businesses.
But all of them have to become either cross-side and or data network effect business.
over time. The only companies that stay direct network effect businesses are these pure communication
tools like messenger, I message, WhatsApp. And there isn't a clear path to make money with those.
But you want to sell ads, you're becoming a cross-site network effect business. And also
creators versus consumers creates a cross-side network effect business. If you want to get better
at personalization, guess what? You're recommending content by leveraging, you know, data network effects.
I love that. You nailed it. I imagine marketplace founders listening to this may be wondering,
hey, how do I, can I add on these additional network effects? Can I evolve towards one of these?
And what you're saying is not only can you, you need to eventually.
I agree, right? I think, you know, they're a great form of defensibility first off. So do they make
sense for every business? No, but in a lot of cases, in order for you to evolve properly and
continue to grow, they can become a necessity. Are there any other examples of marketplace
companies that come to mind that did a great job evolving or adding one of these network effects
or just like interesting.
So let's take some inventory, right?
So I think Zillow is really interesting
in that a real estate listing site
is not particularly an interesting product,
but the ability of saying very rarely do,
you know, both sides of this network,
people who are buying homes and selling homes need to connect.
But I can find a way for the brand
to connect with both of them
by giving real-time pricing information
on the value of homes.
and that creates a much stickier product for both sides.
I think that was a pretty genuine innovation, you know,
that other people have tried and rarely been as successful with.
So that's one that definitely sticks with me, you know, off the top of my head.
Great.
We've been talking about Grubhub at some pretty strong network effects
and large part things of the work you did.
And one of the benefits of network effects is it creates a barrier to entry.
it's hard to replicate and compete with a company where they already have all this network effect.
But famously, Grubh got disrupted by DoorDash and New Breeds.
And I need to talk about how that happened and why that happened.
And it'd be cool to hear just like, what do you think they could have done differently
in what happened where their network effect got eaten for lunch, pun intended?
Sure.
It's a great question.
And I think people do mistake any form of network effect as this perfect form of defensibility.
they're the best form of defenseability,
but that doesn't mean they're immune to disruption.
And I think the main way this happens
with cross-side network effects
that we typically talk about for marketplaces
is when a disruptor dramatically expands selection.
So I want to be clear.
I left Grubhub at the end of 2013
before said lunch was eaten.
So what I'm communicating is more like public knowledge
of watching these amazing companies compete
rather than like being inside the fire at the time.
But one important thing to remember is Grubhub was an asset light marketplace model.
Restaurants did their own delivery through their own delivery drivers that they hired.
And I wrote this post for Andrewson Horowitz a few years ago about supply strategies and marketplaces.
So in that, like, you really need to be comprehensive or have exclusive inventory.
And Grubhub strive to be comprehensive.
We'd show every restaurant that delivered to you, even if we didn't work with them directly for online
ordering. So what happened about a year before I left Grubhub was that these competitors started
to raise their seed rounds or series A's to build delivery networks. Postmates and Dordash were the
first two that rose to prominence. Whober eats would come later, but they actually started with
a pretty different business model. And this is an extremely different business. You're hiring drivers.
You're managing logistics. So we call this a heavily managed marketplace model.
as you are now facilitating the transaction
versus just connecting buyers and sellers
and taking payments like Grubhub did.
So on the one hand, you have Grubhub,
this extremely high margin business,
and these businesses coming up
are actually negative margin businesses.
At least they were for a long time.
So in 2013, Grubhub
acquired Seamless, its closest competitor at the time.
And Seamless still had a lead
on Grubhub in New York,
partially because it had this corporate program.
where law firms and banks and consultants got lunch stipends,
you had to redeem by ordering the food through seamless.
So Grubhub operated in these dense cities and suburbs like a New York,
because those were the only places that had restaurants that had delivery.
DoorDash, when it started operated in less dense suburbs
and worked with restaurants that had never done delivery before,
and they would provide the delivery drivers themselves.
So this allowed DoorDash to grow.
without much competition in the early days.
And these companies also took some real gambols.
One of the things they did is they delivered from restaurants
they didn't have an agreement with.
And that caused controversy and lawsuits.
But what it meant is when these companies did launch in the cities
to go after Grubhub,
it felt like DoorDash and Postmates and Uber
had dramatically larger selection of restaurants to choose from.
And Grubhub was definitely no longer near comprehensive.
And back when we talked about cross-side network effects, the more selection of restaurants,
the more attractive it is to users and vice versa.
So at that point, you know, Grubhub's put in a very peculiar position.
It had gone public after raising $80 million in venture capital and raising $100 million in an IPO,
telling investors it's an extremely profitable, high growth, asset light marketplace.
But now it's got disruption pressure from operationally intensive, negative margin,
delivery services that were raising $100 million every six months from the private markets.
So what Grup Hub assumed is that these businesses were just structurally unprofitable
and that VCs would stop subsidizing them eventually.
Of course, that didn't happen.
They kept raising more money.
DoorDash eventually raised, you know, multiple billions of dollars in this market.
And part of what they used that money for was to lock up agreements with national chains,
which Grubhubbh never worked with.
It was always like the local mom and pops
and promotions and discounts on the demand side.
So all of this is happening,
and then the pandemic hits.
And all of those negative margins
turned positive for DoorDash for the first time,
if I understand things correctly.
And on top of that,
all this corporate ordering that we got from Seamless
no longer mattered because no one goes to the office anymore.
So this gambit really paid off,
and Doordash just took the market.
Grubhub then tried to copy the approaches
of DoorDash and Pradesh.
Postmates, and they wrote kind of this famous letter saying that they still thought the approaches
were stupid, but their hand was forced, which is kind of funny to read in retrospect.
So, you know, a lot of armchair thinkers are like, how could Grubhub have been so stupid to let
Dordash take the market that they built? And look, I'll admit, Grubhub made some mistakes.
But I think it would have been extremely hard for Grubhub to come out on top here.
So let's say in 2014, after you IPO, you do actually think what DoorDash Postmates and Uber are doing are smart.
What do you do?
Go to investors that you promised high growth and high profits and say you need to raise more money and debt to compete with negative margin upstarts in a way that will destroy all that potential profit, you mentioned.
The stock would drop 90%.
A lot of your employees would be because their stock is now worthless.
And on top of that, building a deluxe.
the delivery network is a heavy operations play
that much is none of your core competencies.
So to me, that feels like a death sentence.
So I think the only play here
was to buy DoorDash as early as possible
and let DoorDash and their operationally heavy culture
eat Grubhub from the inside out.
I think Grubb probably could have acquired them multiple times
for whatever reason it ever happened.
It would have seemed pretty risky had Grubhubb done that.
Investors probably would have hated it.
it, but it would have been their Netflix moment where, you know, Netflix bet it all on streaming and they bet right.
And this is all incredibly easy to say in hindsight.
But I think what I've learned, you know, now that I'm more senior in my career, is during existential threats, you know, it's like when Nassim Talib says the only rational reaction is overreaction.
Unless you have a real viable reason to assume otherwise, you've got to assume the disruptor is right.
and base your strategy on them playing an optimal game.
Whereas I think, you know, Grubb assumed the disruptor was wrong
and that it would all play out eventually in their favor.
And it clearly did.
Wow. I have never heard that full story.
That was amazing.
Thank you for getting in so much detail there.
I don't know how much of it is right.
It seems right from the outside.
And it's interesting that it's like a version of Innovator's dilemma.
Usually Innovators dilemma is people come and do something cheaper
at the low end of the market.
And in this case, it was more they were doing something that they didn't believe with scale.
It was like just much more inefficient even though it was a better experience.
And is that innovator's dilemma or is that some other version of innovator's dilemma?
Because to your point, they couldn't almost go after it.
I think it is in spirit for sure.
The takeaway there that you've learned is don't underestimate someone that's trying to do something that's going to eat your lunch eventually,
even though it feels like a terrible business model.
right like if the market's rewarding it the market will probably find a way to make it profitable and uh you know it's
essentially when everyone's find like a more efficient network effect for demand on the on the on the marketplace side
you probably need to copy that like as soon as possible and if you can't copy it own it right like buy it
and i think we've seen this a few times like rover and wag was another interesting example of this
um where they found a more frequent use case that fit the same supply and demand
them and, you know, Rover just copy it as soon as possible.
And that ended up, you know, working out for them in a way that, you know, it didn't
as much for growth up.
I just did a talk recently on Marketplace growth strategy.
And someone asking me a really interesting question.
If you were trying to go up up against the DoorDash or an Uber today, what would you do?
And my answer is just like money was so freely available at that point that they were able to
like a lot of this was spend that so much money raised.
You said they're raising $100 million every six months.
like, is it even possible in today's climate where you can't actually raise that much money to have any sort of chance to eat at DoorDash or Nuber?
Yeah, I mean, clearly they took advantage of the zero interest rate environments that we talked about earlier.
That is not a replicable strategy in 2023.
So any approach to compete with them has to be competing on a very different angle because, yeah, they can spend you into the dust.
So, you know, we'll see if anyone's able to build a way that creates a new.
supply and market. I think you and I've seen a couple of earlier stage examples of that. We'll see if any of them scale or something that feels cheaper or more fun on the demand side. That would be like another way to potentially disrupt things. I think another thing that was working pretty well before the pandemic in building disruptors was focusing on the pickup use case, which you know, DoorDash cannot do as easily. They've tried, right? But like their whole value prop is the delivery network, which you don't need for pickup. But of course, the pandemic put a lot of those startups.
grinding to a halt as well.
So, you know, there's always angles,
but you're going to need to be incredibly clever
because just attacking with a war chest
is not really going to work.
Yeah. I've noticed a lot of startups launching
that are trying to do white-label delivery for restaurants
so they don't have to really rely on DoorDash.
But maybe that's a wedge to get in
and eventually they do DoorDash sort of thing.
And I would say I'm pretty skeptical of those
because they're just not really building
the network effects on the demand side.
They're just more like SaaS businesses.
and I think they'll struggle to be, you know,
multi-hundred million dollar in revenue businesses.
Because the take rate is typically like, you know,
a third or a fourth of what, you know,
a DoorDash can charge.
Perfect segue to my next question.
I only have a couple more.
There's this concept and I think pull from marketplace founders
to add a SaaS tool eventually and have both business models.
And then there's often the reverse where a SaaS company wants to add a marketplace.
And I know this question is something you get a lot.
And so just a question for you, does this work?
Are there examples where they've added this additional way of making money and which
direction do you find is most often successful and not successful?
You know, the canonical example that a lot of these founders use is open table.
And that always felt really unfulfilling to me because it's very old at this point.
Probably the younger people listening to the podcast are like, what's open table?
And I think, you know, that business has incredibly underperformed the market it operated in.
So it had a good exit.
It sold for $2.6 billion, I think, to booking.com.
But booking subsequently wrote that value down like below a billion.
So, you know, that's not really the outcome I think we're looking for traditionally in marketplaces.
And maybe explain, like, what it was initially the SaaS tool versus.
Oh, sure.
So Open Table promised both a SaaS tool that would help you understand like what tables are open and where to seat people.
so for like the host in the front of the house in a restaurant,
but also bring in additional reservations to fill up your restaurant, right?
Because I think what people misunderstand about restaurants,
they're like, oh, these restaurants are these incredibly low-margined businesses.
And it's like, yeah, they are because they're paying the rent no matter what happens.
So once you're already paying the rent no matter what happens,
you're incentivized to pump as much food out the kitchen
and to get as many people seated in-house as possible.
So people would say like, oh, Grubhub and DoorDash, you're charging too much.
And it's like, no, like delivery orders and catering orders are basically pure margin to restaurants.
The chefs are already there.
The rent is already being paid.
The more things we pump out of the kitchen, the more money we make.
Which is why restaurants are willing to pay higher fees.
These restaurants are not stupid.
They're not being misinformed, right?
So OpenTable, well before there were any delivery startups, was like,
we're going to fill up your tables.
And we're going to give you the software that helps you manage your tables most effectively to make the most profit.
Got it.
Okay. Great. So keep going.
So that's open table.
So look, this is definitely the strategy we're working on with Eventbray, where we started with something that was more SaaS-like, you know, enabling easy payments and, you know, certain tools to make Event Creator's business more efficient.
And we're layering and more the traditional marketplace value prop of demand, you know, driving more to sales for these.
event creators. And, you know, I would say it's got a ways to go to be working really well. And
what is working really well look like? It's when the marketplace model unlocks those cross-side
network effects that make it easier to grow. So, you know, event creators, when Event Bright started,
they would just go do their own marketing to bring people to Event Bright to transact on their
events that they had listed there. And now Event Bright drives, you know, 25% of the ticket sales
itself. And, you know, that percentage is growing faster. That's amazing. Yeah, it's growing faster.
than the rest of the business, which is great.
But it probably needs to be closer to like 50%,
to unlock those real cross-side network effects.
And that would mean that creators start selecting Eventbrite
because of all the demand Eventbrite has
versus the quality of the SaaS tools.
So that's obviously something we're working on.
Thayer is a company I advise more recently
that I think has unlocked this model in like the reverse
where Fair is a wholesale marketplace
between independent retailers and brands,
so that you could sell products at these retailers,
like a boutique in your local neighborhood.
So Faire built the marketplace first,
and then it later built a SaaS tool
that allowed the brands to onboard their current retailers
into the platform and get better terms on payments
and free returns.
And it didn't charge anything to use the SaaS tool
for any rebookings that happened through that platform.
But what that did is it onboarded more independent retailers
that they could cross-sell to other brands without, you know, needing to use a sales team.
And when they cross-sold, of course, Farr did, you know, take their percentage on those transactions.
So I think that models worked out really well, and Faire has grown quite quickly.
And so the examples you gave, Ben Bright was a SaaS tool trying to add a marketplace.
Yep.
Fair is an example of a marketplace adding a SaaS tool.
And is the takeaway there that it's, in your experience, it's generally more,
you're going to have a better time if you're a marketplace adding a SaaS.
tool versus the other way around. Yeah, I think that's right. So I think, you know, I don't know when
it was. It was maybe like 2015 or whatever, a bunch of investors started writing about SAS to
marketplace transitions. And like, that's the transition of MEPRites going through. It's going to
work, but it's hard. And it's not replicable for a lot of other SaaS businesses. You need to
have a direct relationship with your customers, customers, first off. Those customers need to have
needs beyond that single supplier.
Usually it's like a discovery value prop, you know, for other suppliers.
And you need to build like this totally new skill set to build tools for your customer's
customer who is very different from your current customer.
Whereas, you know, marketplaces that add a SaaS component, you know, as a customer acquisition
tool like there or a workflow or attention tool to, you know, increase retention or
reduce disintermediation, I think you'll see that be a lot more common approach and much more replicable.
Is this just rooted in the fact that marketplaces are incredibly hard, no matter whether you start with them or whether you add them?
Like, is that the root of the issue here?
I think that's a good way to frame it.
So if you're building a startup in 2023 and you're like, oh, I'm going to build the SaaS business.
And then five years later, I'm going to build this marketplace business on top of that.
It's kind of like, it's going to take a long time for you to de-risk the hardest part of that strategy.
Whereas if you get the hard part done up front, it opens up a lot of amazing, you know, adjacencies, different ways to grow.
So I think there's definitely truth in that statement.
So kind of the takeaway here is if you're trying to add a marketplace, it's going to be very hard.
You shared a couple things of a couple attributes that kind of tell you that maybe it might work.
Maybe just share those again real quick.
So take Square or Substack or Patreon or like Eventbrite, right, right?
All of these are examples of SaaS businesses.
that in providing the SaaS service deal with the customer and the customer's customer,
right?
That makes it a lot easier because you already have a relationship.
They already know your brand.
Whereas like Stripe, when we buy things, we don't know if we're buying it through Stripe,
right?
Like it's just a SaaS tool that's white labeled in the back end.
We have no idea.
So I think that's the first element, right?
There's a lot of businesses that look like that,
but it is a subset of SaaS businesses that look like that.
And then secondly, those customers that you're building a relationship with,
They need to have a reason to transact with more than one of your current customers on the supply side, right?
So if you're always going to use that same supplier, there's no need for me to show you the rest of the inventory.
And basically all marketplaces win on like we mentioned selection and you needing selection.
And then there's, of course, the marketplaces that win with like standardization of like, I can get it at any time.
It might be from different people, but I know the Uber car is going to be there in five minutes or whatever.
I don't care as much who the driver is.
So one of those has to be there.
And you just find in a lot of these examples,
like, there isn't really that much of a discovery need
for, for, you know, who the demand side would be
in this theoretical marketplace when you dig into it.
It might be helpful just to define, like,
what makes it a marketplace in my eyes?
It's your driving demand to supply.
That's like the nuance, right?
Because otherwise you're just a tool that they're using to do something.
Yeah, exactly, right?
It's like the primary value prop of why supply signs up is that you're going to bring them extra business.
And if you have, you know, customers, buyers and sellers, but the primary reason supply signs up is for tooling or payments, like how Eventbrite started, that's not really a marketplace.
You know, I call it a SaaS like network.
Some people might just call it a SaaS business, a payments business, whatever the case may be.
But it doesn't really have those cross-side network effects that we associate with marketplaces.
What this makes me think about is Patreon and Substack.
And interestingly, when I was looking at early Patreon days, what I understand is they wanted to be a marketplace.
They wanted to be a place where artists come.
They collect payment and then people can discover artists to patronize.
And what they found is nobody needed.
That wasn't a problem anyone had.
I'm not looking for other people to donate money to.
Same with GoFund me, right?
And so with that story in mind when I was chatting with the substack people early on, I was like,
this is exactly what you're going to run into.
No one's sitting around looking for more newsletters to subscribe to.
But shockingly, they've actually pulled it off.
Yeah.
They have a really wild network effect going now.
I've been very impressed with what they've built.
I don't know if I'd call it, you know, a marketplace yet.
Yeah.
But I think they were able to abstract away the version of what you just said to something
that was actually useful, which is, yes, I don't want more emails to subscribe to you.
But I do, I am fundamentally interested in more.
articles relevant to my interest.
And no one has really solved that super well.
Twitter was a very hacky form of that, you know, where I follow you and then I see when
you post a new blog, because you tell everyone on Twitter you post a new blog.
But it isn't built for that.
Whereas, you know, the substack reader will now allow me to be like, oh, yeah, sure, I'll
subscribe.
So I really like what they've done.
It'll be interested to see, you know, how big a business that is and how it all plays out.
But I think their execution has been really solid.
awesome. I feel the same way. And it is, I also wasn't sure whether it makes, like, it's worth, like, it's worth, 80% of my new signups are coming from Subststacks Network. The recommendations feature and they're onboarding things like that. Do you think that's unique to you because you are already a top one percenter substacker? Or is that a meaningful number for newish players? Like, if I finally switch my email list to Substack, which has been on my list for a long time, you know,
that probably will be the same percentage for me, right?
Absolutely not.
Yeah.
Now, I think there's definitely, if you're there first,
and people know of you,
more people will recommend you.
But I think over time,
more and more people start to recommend you.
I think they released a stat that something like 40%
of their new users are coming from a recommendation
or new science or something like that.
So it's pretty widely happening.
But I don't know how much of that is just the top 10.
So it's pretty incredible.
It was a really innovative future and good jobs up.
And we had,
they're had a product on this podcast talking about that exact feature for a whole hour if you're
interested.
Awesome.
Okay.
Final question.
And then we have a very exciting lightning round.
And this is around consumer companies and consumer subscription companies.
I know you work with a lot of founders that are building consumer subscription companies and just consumer startups in general.
Yeah.
You often tell me how they're incredibly hard to build into thriving businesses.
You just talk about why consumer subscription startups are so hard and private.
I feel like you're making this quite a downer podcast, Lenny.
This is people need to hear the truth.
You know, there's a lot of happy talk out there, a lot of posts.
Here's how you do this.
Sure.
And sometimes you can't.
I think in order to understand these businesses, you have to start with,
why do investors like B to B SaaS?
Why do they like B2B subscription?
And I think the way most respond to that question is they're like, oh,
predictable revenue, right?
And it's like, ah, sure.
I mean, that's cool and all.
But I think that's actually not the most important.
So I'd argue there's two great attributes of B2B SaaS.
One is that businesses are more predictable in how well they're routine.
They're rational.
You can understand who are good versus bad businesses for your product,
as well as which ones are going to grow versus go out of business.
And more importantly, the second thing that's great about B2B SaaS is net dollar retention.
So what is net dollar retention if you don't work at SaaS?
Well, as a SaaS company, some of your customers are going to churn.
some of your customers are going to stay.
And normally, outside of potentially current macroeconomic conditions with all the layoffs,
when customers do stick around, they tend to spend more.
Either they buy more seats if you're a seat-based model or they use the product more,
if you're a usage model.
So the SaaS company just makes more money in year two, year three, et cetera.
So consumer subscription just doesn't have any of these benefits.
Consumers are way less predictable.
They tend to retain worse than businesses.
and they also don't have net dollar retention characteristics.
So if the user retains paying you in year two,
you probably make it the same amount that you made from them in year one,
not more.
What that means is you need higher user-based retention
than a B2B SaaS businesses with more unpredictable users,
and it's a lot higher than I think founders tend to think.
We're talking indoor retention that needs to be north of 60,
perhaps even 70%.
So you look at who's actually been able to do that at scale.
And it's a really small list.
Netflix in the U.S., Amazon Prime, Spotify, Duolingo, I think is emerging as one of these players that's making it work.
And when you look at how they do it, they're either doing it with massive OPEX and economies of scale or through a network effect or some other bespoke growth loop that's not that easy to replicate.
So Duolingo has a strong data network effect.
The lessons get better the more people use it.
Beak, the company I'm on the board up,
has a cross-sad network effect between creators
who create the content and the listeners,
and the creators bring a lot of distribution
from their existing social networks
to bring new people in the app to listen.
Netflix and Amazon, they spend billions of dollars on content.
So I think the default path of like,
I'm going to spend money on paid acquisition,
I'm going to retain half of my audience year over year.
That's just a path to going eventually.
And I think what's interesting about these businesses is you can model it.
So you can learn when it's going to happen.
You can learn like, you know, when the retention dips
and when you can no longer let you are profit-prolily acquire users.
And if you want to look at like a model in real time,
just look at Blue Apron.
The company raised $300 million in an IPO that valued it at $2 billion.
It's worth $50 million today on the New York Stock Exchange.
And I think people understand now if they didn't before that paid acquisition tends to get
worse as you scale.
You know, you target the best customers first.
They have great conversion, great retention.
And then as you expand, your targeting of new customers, every one of those metrics
gets worse until it's no longer profitable.
Maybe two years from now, it may be five years from now.
But eventually it'll be no longer profitable.
and what network effects allow you to do if they allow your product to get better, faster than the customers you target get worse.
Normally through increased selection, like some of the examples we gave with Dward Ash and others.
Such a cool topic.
I actually have a post about this that I recall now as you're talking about it.
And just to kind of double click on the retention point and it's like freaks you out when you really get into it.
That say your retention is like 70% like cohort retention for a year.
I forget the math, but like every three or four years,
you basically have to rebuild your entire user base
because it just keeps trickling out.
So your growth just has to continue being.
It's mind-boggling.
You run out of humans.
Like, yeah, it's really hard.
So like, if you can retain people incredibly well,
meaning those people just never churn,
yeah, you've got a great business.
But look at the effort,
the companies that have done that are doing to do that.
Spotify does make profit.
Netflix, Amazon,
to spend so much money to try to try to,
do that and how replicable is that for a startup. I'd rather say like, let's try and get some
network effects involved here. Let's get our customer acquisition cost to zero. You know,
let's think about other ways to monetize because this alone feels like hard. And this is also why
a lot of these companies pivot to B2B. They realize they're not going to get anywhere with B2C.
The other lesson I took away because I interviewed a lot of these early B2C subscription app founders
employees. And I think about companies like Grammarly, Duolingo, Noom, forget there a few more.
One of the other trends across the mall is they're all very efficient and very small for a long time because they needed time to figure out how to make anything work and then just continue to stay small and super scrappy.
I think that's a great point. It was an interesting case study between Calm and Headspace because Calm remained like 10 people forever.
Wow.
And Headspace had gone into like, you know, hundreds of people. And Calm like basically never lost money. And that allowed them to be, you know, allowed them.
them to pivoties you're during, you know, massive changes, like, you know, app tracking transparency,
like through a wrench into all paid acquisition. So if you're not losing money, like, cool,
you have time to figure out how to, like, grow again. But if that increases your burn by like
$100 million, you have a lot more of a panic on your hands. So maybe just to tie the loop,
tie the knot, close the thread on this topic. If you're a B to C subscription founder,
what would be some takeaways that you would want to put in their head to,
think about how to maybe survive.
Yeah.
So if what your plan is is to use paid acquisition on top of a freemium model to get a
percentage of people to convert and hopefully stick around forever, I'd pivot right now.
Like, I just can't see it working.
So how do you pivot?
Well, how do you make it social so that people are bringing in other people?
How do you get a supply side to the, you know, content or education or whatever you're
building and make it in the supply side's interest to refer people?
You have to do something that's either, you know, building some more organic growth loops into the business or building network effects into the business or else, like, we could go spend two hours and model out exactly when you're going to run out of money.
Like, it's just that predictable.
And, you know, a lot of founders don't like to hear it when I tell them that, but I'd rather them hear it now than learn it three years from now.
Well, we've reached our very exciting lighting round.
I'm just going to dive right in.
What are two or three books that you've most recommended to other people?
Definitely the goal by Elihu Gold Rat, which explains how my brain works pretty well.
Thinking Fast and Slow by Danny Conman.
I took a lot of the behavioral economics classes in my MBA program,
and then his book came out like the year after.
So I just like absorbed it as quick as possible.
Wait, was you a professor or that was just the topic?
Some of his like pupils were professors of mine.
Amazing.
Very cool.
And then the third is a book called Profit from the Core by Chris Zook.
Amazing.
That's a new one.
I love when there's new books being added to the collection.
There we go.
Okay.
Next question.
Favorite recent movie or TV show?
Well, Party Down just came back.
And that's like, I've been watching.
That's one of my favorite.
I've never heard of it.
It's one of my favorite comedies of all time.
Yeah, go back.
Cool.
I watch the first couple seasons.
That's what I've been doing.
That's what I've been doing.
Other things like The Last of Us is great.
I really enjoyed the video games.
Severance is great.
Station 11 is great.
I loved the book too,
but I thought that was really good.
Movies,
there haven't really been a lot of great movies lately,
but I did rewatch kicking and screaming from the 90s.
And it really holds up well.
I don't know how many you have heard of it,
but it's about a group of college kids
to graduate, but they just decide not to lead campus and start their lives, and they just
stick around campus. So I really enjoyed that one.
Amazing. We have a drinking game anytime someone mentions Last of Us. So if you're driving
bit to work, listening to your podcast on your commute, take some coffee, whatever you got.
Two more questions. What's something relatively minor you've changed in your product
development process, or maybe that you've recommended people change, that has had a tremendous
impact on people's ability to execute.
You know, I preach like cross-functional teams and alignment pretty aggressively.
So how to get people from all the different functions allied on the same OKRs and working together.
And I used to say like, look, if someone in that cross-functional team is pulling rank, it means, you know, something's fucked up on a team.
But something we started doing more recently at both Eventbrite and whatnot is just designating the person on the cross-functional team who drives the project.
At an event probably we call it the driver or whatnot,
we call it the DRI directly responsible individual.
But once that person makes the call,
it's disagree and commit time.
There's no escalation path.
Like, if you're not the DRI and you're on the team
and they made the call, all right.
It's time to sign up and go forward on that decision.
And if they made the wrong decision later,
okay, we'll learn, you know, once we ship.
Final question.
Something I left that you do in your own newsletter and blog
as you share what you're listening to.
What are you listening to these days?
Sure.
Colola recently came out with her second album, Raven, which is really great.
I've been listening to that.
Orbital came out with a new album called Optimal Delusion.
That's been pretty good.
And then an oldie but goody is De La Sol's music finally came out on Spotify.
And the stakes is high is one of my favorite hip-hop albums ever.
So I've been jammed to that.
Amazing.
Where can folks find you all?
online if they want to reach out, learn more. And how can listeners be useful to you? I blog not near as
frequently as you at kCaccidental.com. You can find me, you know, on Twitter at one case man.
And yeah, just pay it forward. Help help your companies build better products and better businesses.
That's all I care about. Casey, thank you so much for being here. I feel like we're building
some kind of network effect, you and I doing these podcasts. Hopefully you'll be back for a third time
someday. Thank you again. Really appreciate it. Yeah, thanks for having me. Hopefully they don't
could save me by then.
Bye, everyone.
Thank you so much for listening.
If you found this valuable, you can subscribe to the show on Apple Podcasts, Spotify,
or your favorite podcast app.
Also, please consider giving us a rating or leaving a review,
as that really helps other listeners find the podcast.
You can find all past episodes or learn more about the show at lenniespodcast.com.
See you in the next episode.
