Debug Information

Processing Details

• VTT File: 02982aafcb6e8aa6bce6c69c4119d4ca.vtt
• Model Used: models/gemini-2.5-flash-lite
• Processing Time: September 12, 2025 at 11:22 AM
• Total Chunks: 2
• Transcript Length: 118,717 characters
• Caption Count: 1,070 captions
• Temperature: 0.1
• Max Tokens: 1024
• Top-K: Not used
• Top-P: 0.95
• Candidate Count: 1
• Affiliate Tag: spokengoods-20

Prompts Used

Prompt 1: Context Setup

You are an expert data extractor tasked with analyzing a podcast transcript. 
I will provide you with part 1 of 2 from a podcast transcript. 
I will then ask you to extract different types of information from this content in subsequent messages. Please confirm you have received and understood the transcript content.

Transcript section:
[00:00:00.000 --> 00:00:01.760] Let's talk about product market fit.
[00:00:01.760 --> 00:00:08.080] You have to deliberately not act on the feedback of many of your early users.
[00:00:08.080 --> 00:00:13.760] And this is at the same time as listening to people intensely and building what people want.
[00:00:13.760 --> 00:00:16.720] That's what we're here to do is to make something that people want.
[00:00:16.720 --> 00:00:17.840] But it can't be all people.
[00:00:17.840 --> 00:00:20.320] And the question becomes: how do you listen to them?
[00:00:20.320 --> 00:00:24.960] And then, even of what they say, what do you pay attention to and what don't you?
[00:00:25.120 --> 00:00:26.080] The trick here is.
[00:00:26.320 --> 00:00:29.440] You're not doing what a lot of CEOs think they need to be doing with their time.
[00:00:29.440 --> 00:00:33.200] A lot of CEOs think they need to spend time on hiring or org building.
[00:00:33.200 --> 00:00:36.400] And you intentionally, I will spend time on product and marketing design.
[00:00:36.400 --> 00:00:39.840] So this is a technique that I call the switch log.
[00:00:39.840 --> 00:00:50.480] And it's born out of the observation that your calendar says what you thought you were going to do, but it's really only your trail of work that describes what you actually did.
[00:00:50.480 --> 00:00:51.600] How can we capture that?
[00:00:51.600 --> 00:00:53.200] So I came up with the following idea.
[00:00:53.200 --> 00:00:56.000] What if I just did whatever the heck I wanted?
[00:00:56.000 --> 00:00:58.800] What's the most pivotal moment in your career, in your life?
[00:00:58.800 --> 00:01:02.000] I learned the real secret behind virality.
[00:01:02.000 --> 00:01:06.160] There is no such thing as a truly viral product.
[00:01:06.160 --> 00:01:07.840] What then is the true secret?
[00:01:07.840 --> 00:01:09.280] It is.
[00:01:11.840 --> 00:01:14.080] Today, my guest is Rahul Vora.
[00:01:14.080 --> 00:01:22.240] Rahul is the founder and CEO of Superhuman and one of the most thoughtful and insightful and articulate founders that I've met.
[00:01:22.240 --> 00:01:32.240] As you'll see in our conversation, it's hard not to be captivated by Rahul's storytelling skills and also his really insightful takes on how to build great products and teams.
[00:01:32.240 --> 00:01:56.800] This episode is for anyone who's looking to build their product taste, help their teams move faster, learn how to think better from first principles, and also learn about Superhuman's very unique approach to building their company, including why they manually onboarded every single new user for years and why they've decided to stop, why they ignored most of their customer feedback on their way to finding product market fit, and also how you can use his approach to finding product market fit for your own company.
[00:01:56.800 --> 00:01:59.520] Also, the power of game design in building great products.
[00:01:59.520 --> 00:02:07.800] A very contrarian take on pricing strategy, what Rahul has learned about building scale products on top of AI and LLMs, and so much more.
[00:02:07.800 --> 00:02:15.160] A huge thank you to Ed Sims, Conrad Irwin, Bill Trenchard, and Gara Vora for suggesting questions and topics for this conversation.
[00:02:15.160 --> 00:02:19.560] If you enjoy this podcast, don't forget to subscribe and follow it in your favorite podcasting app or YouTube.
[00:02:19.560 --> 00:02:27.000] Also, if you become a yearly subscriber of my newsletter, you get a year free of Superhuman that you can start using immediately.
[00:02:27.000 --> 00:02:31.400] You also get a year free of Notion, Perplexity Pro, Granola, and Linear.
[00:02:31.400 --> 00:02:33.720] Check it out at lennysnewsletter.com.
[00:02:33.720 --> 00:02:37.640] With that, I bring you Rahul Vora.
[00:02:38.600 --> 00:02:41.240] This episode is brought to you by Eppo.
[00:02:41.240 --> 00:02:49.160] Eppo is a next-generation A-B testing and feature management platform built by alums of Airbnb and Snowflake for modern growth teams.
[00:02:49.160 --> 00:02:55.160] Companies like Twitch, Miro, ClickUp, and DraftKings rely on Eppo to power their experiments.
[00:02:55.160 --> 00:03:01.320] Experimentation is increasingly essential for driving growth and for understanding the performance of new features.
[00:03:01.320 --> 00:03:08.760] And Eppo helps you increase experimentation velocity while unlocking rigorous deep analysis in a way that no other commercial tool does.
[00:03:08.760 --> 00:03:18.200] When I was at Airbnb, one of the things that I loved most was our experimentation platform, where I could set up experiments easily, troubleshoot issues, and analyze performance all on my own.
[00:03:18.200 --> 00:03:31.880] Eppo does all that and more with advanced statistical methods that can help you shave weeks off experiment time, an accessible UI for diving deeper into performance, and out-of-the-box reporting that helps you avoid annoying, prolonged analytic cycles.
[00:03:31.880 --> 00:03:38.120] Eppo also makes it easy for you to share experiment insights with your team, sparking new ideas for the A-B testing flywheel.
[00:03:38.120 --> 00:03:46.240] Eppo powers experimentation across every use case, including product, growth, machine learning, monetization, and email marketing.
[00:03:44.600 --> 00:03:51.600] Check out Eppo at getepo.com/slash Lenny and 10x your experiment velocity.
[00:03:51.840 --> 00:03:55.840] That's getepo.com/slash Lenny.
[00:03:56.480 --> 00:03:59.920] This episode is brought to you by the Fundrise Flagship Fund.
[00:03:59.920 --> 00:04:03.680] Full disclosure, real estate investing is boring.
[00:04:03.680 --> 00:04:10.000] Prediction markets are exciting, meme coins are a thrill ride, even the stock market can swing wildly on a headline.
[00:04:10.000 --> 00:04:11.200] Hello, DeepZeek.
[00:04:11.200 --> 00:04:17.760] But with real estate investing, there's no drama or adrenaline or excuses to refresh your portfolio every few minutes.
[00:04:17.760 --> 00:04:22.400] Just bland and boring stuff like diversification and dividends.
[00:04:22.400 --> 00:04:27.840] So you won't be surprised to learn that the Fundrise Flagship Real Estate Fund is a complete snooze fest.
[00:04:27.840 --> 00:04:36.960] The fund holds $1.1 billion worth of institutional caliber real estate managed by a team of pros focused on steadily growing your net worth for decades to come.
[00:04:36.960 --> 00:04:37.600] See?
[00:04:37.600 --> 00:04:38.640] Boring.
[00:04:38.640 --> 00:04:39.840] That's the point.
[00:04:39.840 --> 00:04:46.880] You can start investing in minutes and with as little as $10 by visiting fundrise.com/slash Lenny.
[00:04:46.880 --> 00:04:53.040] Carefully consider the investment objectives, risks, charges, and expenses of the Fundrise Flagship Fund before investing.
[00:04:53.040 --> 00:04:59.120] Find this information and more in the fund's prospectus at fundrise.com/slash flagship.
[00:04:59.120 --> 00:05:00.960] This is a paid ad.
[00:05:03.920 --> 00:05:06.080] Rahul, thank you so much for being here.
[00:05:06.080 --> 00:05:07.680] Welcome to the podcast.
[00:05:07.680 --> 00:05:10.400] Hello, hello, and thank you for having me, Lenny.
[00:05:10.400 --> 00:05:12.320] I have so many questions for you.
[00:05:12.320 --> 00:05:14.640] We're going to have so much to talk about.
[00:05:14.640 --> 00:05:18.000] I actually want to start with your time before Superhuman.
[00:05:18.000 --> 00:05:23.680] When I was preparing for this chat, I actually asked you, What's the most pivotal moment in your career, in your life?
[00:05:23.680 --> 00:05:30.120] And you told me that other than starting Superhuman, it was selling your previous company, Reportive, to LinkedIn.
[00:05:29.440 --> 00:05:31.400] So, let me just start there.
[00:05:31.720 --> 00:05:32.920] What was that experience like?
[00:05:32.920 --> 00:05:37.640] What do people not know about this phase in your life, and just why was it so pivotal?
[00:05:37.640 --> 00:05:41.560] So, for folks that don't know, Reportive was my last company.
[00:05:41.560 --> 00:05:46.120] It was the first Gmail extension to scale to millions of users.
[00:05:46.120 --> 00:05:57.080] Basically, on the right-hand side of Gmail, we would show you what people look like, where they work, links to their recent tweets, their LinkedIn profile, and everything else that they were doing online.
[00:05:57.080 --> 00:06:03.480] So, if you were hiring, marketing, selling in BD, super useful.
[00:06:03.480 --> 00:06:14.760] It turns out we somehow attracted most of LinkedIn's daily active users onto this one free app, and I then ultimately ended up selling that to LinkedIn.
[00:06:14.760 --> 00:06:22.760] And that by far, as you said, was the most pivotal thing I'd done in my career prior to starting Superhuman.
[00:06:22.760 --> 00:06:29.000] Now, had I known that we'd amassed most of LinkedIn's active users onto one app, I would have sold it for far more.
[00:06:29.000 --> 00:06:45.800] But the actual pivotal moment was really who I got to work with, because I reported to LinkedIn's head of growth, Elliot Schmuckler, and he was responsible for scaling LinkedIn from 25 million members to, when I joined, north of 250 million members.
[00:06:45.800 --> 00:06:51.640] And during my first one-on-one, I learned the real secret behind virality.
[00:06:51.640 --> 00:06:55.080] And big hint, it's not about viral mechanics.
[00:06:55.080 --> 00:07:01.880] And overall, that acquisition experience gave me the time to figure out what was next and the resources to truly swing for the fences.
[00:07:02.440 --> 00:07:06.760] Okay, well, I have to follow this thread that you put out there of what the secret is to virality.
[00:07:07.080 --> 00:07:08.440] What did you learn there?
[00:07:08.440 --> 00:07:13.720] Well, in my first one-on-one, I sat down with Elliot and I said, Hey, I'm here to learn.
[00:07:13.720 --> 00:07:17.280] Please teach me everything that you know about virality.
[00:07:17.600 --> 00:07:27.120] And he said, Okay, well, hate to burst your bubble, but there is no such thing as a truly viral product.
[00:07:27.200 --> 00:07:28.400] I said, What do you mean?
[00:07:28.480 --> 00:07:29.760] How do you explain Facebook?
[00:07:29.760 --> 00:07:32.560] For that matter, how do you explain LinkedIn?
[00:07:32.560 --> 00:07:44.080] And he said, What I mean is no app has sustained a viral factor of greater than one for any real period of time.
[00:07:44.400 --> 00:07:49.680] Even Facebook in its heyday had a viral factor of about 0.7.
[00:07:49.680 --> 00:07:51.920] And he told me that lasted for perhaps a year.
[00:07:51.920 --> 00:07:56.720] So one person was creating about 0.7 new users.
[00:07:56.720 --> 00:08:01.200] And I double-clicked again and I said, Well, Elliot, what about the address book import?
[00:08:01.200 --> 00:08:04.560] This is one of the things that LinkedIn got famous or infamous for.
[00:08:04.560 --> 00:08:12.560] You could import your address book, and then it would spam/slash invite everyone who happens to be members of LinkedIn in your address book.
[00:08:12.560 --> 00:08:15.440] And then eventually it would just invite everyone to LinkedIn.
[00:08:15.440 --> 00:08:20.960] And he said, That's an amazing feature, but you have to remember not everyone is going to use it all the time.
[00:08:20.960 --> 00:08:27.840] So even that feature had a lifetime viral factor of about 0.4.
[00:08:27.840 --> 00:08:29.040] And that's considered good.
[00:08:29.040 --> 00:08:31.520] So 0.4 is good for a viral feature.
[00:08:31.520 --> 00:08:33.200] 0.6 is great.
[00:08:33.200 --> 00:08:36.720] Something like 0.7 is absolutely incredible.
[00:08:36.720 --> 00:08:40.800] You're in the stratosphere up with Facebook at that time.
[00:08:41.120 --> 00:08:44.960] So I said, well, okay, all of these things by definition are going to peter out.
[00:08:44.960 --> 00:08:46.480] There's going to be an asymptote.
[00:08:46.480 --> 00:08:51.440] None of these viral mechanics keep on compounding, which actually makes sense.
[00:08:51.440 --> 00:08:54.720] It would be a little absurd if things just kept on growing.
[00:08:54.720 --> 00:08:58.640] What then is the true secret behind virality?
[00:08:58.960 --> 00:09:02.280] And he said, it is word of mouth.
[00:08:59.520 --> 00:09:06.920] It is the virality you can't measure that isn't a mechanic, that isn't in a feature.
[00:09:06.920 --> 00:09:12.920] It is when one user spontaneously tells another user about your product.
[00:09:12.920 --> 00:09:17.000] And that really colored how I think about growth and virality.
[00:09:17.000 --> 00:09:23.240] Since then, it has shaped so much of what we do at Superhuman and so much of how I think about growing brands.
[00:09:23.240 --> 00:09:23.560] Wow.
[00:09:24.200 --> 00:09:25.320] You're such a great storyteller.
[00:09:25.320 --> 00:09:27.080] I'm just like listening here, captivated.
[00:09:27.240 --> 00:09:28.280] What is he going to say next?
[00:09:28.760 --> 00:09:29.640] That was fascinating.
[00:09:29.640 --> 00:09:37.960] I actually have a post that I'm going to that very much aligns with what you're talking about, which is titled Virality is a Myth, mostly.
[00:09:37.960 --> 00:09:43.080] And it's based, I forget, on this book where they do all this research on like actual viruses.
[00:09:43.080 --> 00:09:46.920] And it turns out they're not actually spreading in this like exponential way.
[00:09:46.920 --> 00:09:51.480] There's like one person that spreads it to a lot of people and it keeps happening.
[00:09:51.480 --> 00:09:54.520] And that's actually apparently what the data shows.
[00:09:54.520 --> 00:10:03.960] And I'm curious if you found this same thing, which is when people think of app as going viral, it's like one person with a massive platform sharing it and their audience adopts it.
[00:10:03.960 --> 00:10:06.200] And it's like, that's just one to many.
[00:10:06.200 --> 00:10:13.160] And then it just happens a couple of times and it looks like it's going viral, but it's like a person to many people, not many people to many people.
[00:10:13.160 --> 00:10:14.760] Thoughts on that?
[00:10:14.760 --> 00:10:26.040] Yeah, we've definitely found that there are whales, to use the gaming terminology, that one person is going to be responsible for inviting 25, 50, 100 people.
[00:10:26.040 --> 00:10:28.360] And they may have various motivations for doing that.
[00:10:28.360 --> 00:10:39.240] In Superhuman, as an individual subscriber, if you refer somebody else and they sign up, you both get a free month, which is a great incentive if you're paying out of pocket.
[00:10:39.240 --> 00:10:50.480] So we have people who send many, many hundreds of invites, and there are some people who essentially have free superhuman for life now due to how many people they've invited.
[00:10:50.800 --> 00:10:59.280] But of course, that incentive doesn't necessarily work inside of a company or inside of a team where ultimately it's the company paying for the product.
[00:10:59.280 --> 00:11:02.720] So you have to then come up with new motivations for those people.
[00:11:02.720 --> 00:11:10.160] And that's where there really isn't any substitute to having a genuinely multiplayer or a genuinely collaborative product.
[00:11:10.240 --> 00:11:15.040] That's one of the huge evolutions we've taken Superhuman through over the last probably about two years.
[00:11:15.040 --> 00:11:19.280] Early last year, we launched what we call Superhuman 2.0.
[00:11:19.280 --> 00:11:26.640] And the basic idea is we saw almost every single other app of Note become collaborative by default.
[00:11:26.640 --> 00:11:31.120] Figma, Notion, Loom, these are all multiplayer or collaborative by default.
[00:11:31.120 --> 00:11:42.720] Yet email, the one tool that we all use more than anything else, even more than things like Slack, was still firmly stuck in its single-player origins.
[00:11:43.040 --> 00:11:51.360] I want to come back to something that you mentioned that I kind of didn't come back to, and I think is really core to what you just shared, which is word of mouth being so important.
[00:11:51.680 --> 00:11:56.240] Like people talk about all these viral features and sharing contact books and all these things.
[00:11:56.240 --> 00:12:06.880] And your point is that takes you to a place, but really what helps a consumer-ish product spread is word of mouth people sharing with each other, which then the question is, how do you do that?
[00:12:06.880 --> 00:12:11.040] We're going to talk about a lot of things that you did to make Superhuman something people want to share.
[00:12:11.040 --> 00:12:13.840] But in the end, it's just like making something people want to share.
[00:12:13.840 --> 00:12:15.600] That's like the definition almost.
[00:12:15.600 --> 00:12:18.320] So then it's like, what makes people want to share stuff?
[00:12:18.320 --> 00:12:19.120] It's amazing.
[00:12:19.120 --> 00:12:20.280] It's helping them.
[00:12:20.280 --> 00:12:22.000] Something that is remarkable.
[00:12:22.000 --> 00:12:25.280] Well, it turns out, you mentioned remarkableness.
[00:12:25.280 --> 00:12:27.920] That is one of our core company values.
[00:12:27.920 --> 00:12:31.240] And if you think about what a company has to do, it has to grow.
[00:12:29.600 --> 00:12:32.280] How do things grow?
[00:12:29.680 --> 00:12:36.360] Well, let's take Elliot's advice at face value, and I believe it's true.
[00:12:36.360 --> 00:12:39.560] It's creating something that people share.
[00:12:40.200 --> 00:12:44.040] You mentioned one way of doing it, which is something that people want to share.
[00:12:44.040 --> 00:12:49.400] There's actually another way, which is simply creating something remarkable.
[00:12:49.400 --> 00:12:50.600] You use that word.
[00:12:50.600 --> 00:12:53.240] And that is one of the core values of Superhuman.
[00:12:53.240 --> 00:12:59.880] So we have create delight, create something that is so joyful that it really truly brings people delight.
[00:12:59.880 --> 00:13:09.320] We have deliver remarkable quality, something that is so striking, so compelling, and worthy of attention that people can't but help tell others about it.
[00:13:09.320 --> 00:13:16.120] And then we have build the extraordinary, which is a measure of the sort of efficacy or the innovativeness of what we want to build.
[00:13:16.120 --> 00:13:22.600] So that's another trick, which is literally baking these raw ingredients for growth into your company values.
[00:13:23.080 --> 00:13:24.680] I didn't know that was one of your values.
[00:13:24.680 --> 00:13:26.280] That makes so much sense.
[00:13:26.280 --> 00:13:34.360] Okay, we're going to come back to that because I think that is, there's so much to learn about how you think about product and how you think about building the company that builds the product.
[00:13:34.360 --> 00:13:39.160] But I want to actually start here with how this conversation came to be.
[00:13:39.480 --> 00:13:48.440] So the COVID hunt, Rajiv, tweeted months ago, he tweeted this, and we're going to show this if you're on YouTube.
[00:13:48.440 --> 00:13:52.680] Superhuman's product velocity feels like it's kicked into another gear as of late.
[00:13:52.680 --> 00:13:54.440] Does anyone else notice this?
[00:13:54.440 --> 00:13:56.920] And I saw that, I'm like, I completely have noticed this.
[00:13:56.920 --> 00:14:00.680] It feels like there's just feature shipping left and right, AI this, AI that.
[00:14:00.920 --> 00:14:02.840] It feels like you're just like a new company.
[00:14:02.840 --> 00:14:03.960] And I tagged you on the tweet.
[00:14:03.960 --> 00:14:04.840] I'm like, hey, we're cool.
[00:14:04.840 --> 00:14:05.800] What changed?
[00:14:05.800 --> 00:14:12.120] And you answered with a few things, and it just made it clear there's a lot to learn about what you did.
[00:14:12.120 --> 00:14:16.960] Because a lot of companies are in this phase, I think, of just like things aren't moving as fast as we want.
[00:14:16.960 --> 00:14:20.640] We used to be so much faster, we used to ship all these features, and now we don't.
[00:14:14.840 --> 00:14:26.640] And so I think this is a really cool, real case study, illustrative example that we can analyze.
[00:14:26.640 --> 00:14:31.520] So let me ask you this: what did you notice that told you something needed to change at Superhuman?
[00:14:31.520 --> 00:14:37.280] And then what did you change that actually had the most impact on your ability to ship and move faster?
[00:14:37.600 --> 00:14:51.120] I think what we noticed was this sentiment, and we felt it first ourselves, but we also started hearing it from the market, from our users, from our customers, that we've slowed down.
[00:14:51.120 --> 00:14:55.760] And as a founder, as a CEO, that's the absolute last thing you want to hear.
[00:14:55.760 --> 00:14:59.040] It's our job, after all, to speed things up.
[00:14:59.040 --> 00:15:09.920] And when I asked people what they mean by slowing down, they didn't mean the product, of course, the product wasn't working any slower, but that the pace of delivery seemed to have slowed down.
[00:15:10.240 --> 00:15:15.360] So I think to break this down, it's important to start by defining what we mean by a slowdown.
[00:15:15.360 --> 00:15:22.560] There's the kind of slowdown that is unavoidable in certain spaces, and then there is the kind of slowdown that is quite avoidable.
[00:15:22.560 --> 00:15:24.080] We actually had both.
[00:15:24.080 --> 00:15:34.640] So starting with unavoidable slowdown, you can classify anything that you build in a company into one of two categories: solution deepening and market widening.
[00:15:34.640 --> 00:15:42.880] Now, solution deepening means making your product better for its existing users, but not making it available to more users.
[00:15:42.880 --> 00:15:50.240] Whereas market widening means making your product available to more users, but not making the product itself any better.
[00:15:50.560 --> 00:16:04.920] And there are some spaces, there are some markets, there are some platforms where market widening is really fast and really easy, and there are some spaces, email is one of them, where market widening is really hard and really slow.
[00:15:59.600 --> 00:16:06.920] And when we started, we had a great deal of focus.
[00:16:07.160 --> 00:16:10.360] We only supported Gmail, we were only on the web.
[00:16:10.360 --> 00:16:19.560] And in those early years, we could pour every ounce of RD energy, every engineering dollar into solution deepening, making the product better for existing users.
[00:16:19.560 --> 00:16:20.760] And of course, users loved it.
[00:16:20.760 --> 00:16:22.600] It's how we got to product market fit.
[00:16:22.600 --> 00:16:24.280] It's how most startups do.
[00:16:24.280 --> 00:16:30.520] But at a certain point, almost every company then has to start investing in widening the market.
[00:16:30.520 --> 00:16:40.200] For example, the market of people who will use a new Gmail front end, but without a mobile app, does exist, but it is relatively small.
[00:16:40.200 --> 00:16:45.000] And this is something that every new email startup is going to learn sooner or later.
[00:16:45.000 --> 00:16:52.920] In order to keep on growing, you are going to have to need to add an iOS app, and then a Mac OS app, and then a Windows app, and then an Android app.
[00:16:52.920 --> 00:17:02.200] And then you'll soon want to support Office 365, but that's not one thing, that's actually three things, because you have to support Office 365 on desktop, and then on iOS, and then on Android.
[00:17:02.200 --> 00:17:04.920] And that's all much easier said than done.
[00:17:04.920 --> 00:17:13.800] I think we at Superhuman now know things about these APIs that literally no other company knows and I would not wish it upon my worst enemy.
[00:17:13.800 --> 00:17:21.320] So fast forward to today, and Superhuman now works wherever you do on every combination of Gmail, Outlook, Mac, Windows, Web, iOS, Android.
[00:17:21.320 --> 00:17:24.840] And this actually turns out to be a really great technology moat.
[00:17:24.840 --> 00:17:26.920] Almost no other email app can claim this.
[00:17:26.920 --> 00:17:29.480] It's taken many years of intense investment.
[00:17:29.480 --> 00:17:36.760] And I think we'll touch on this later, but it's one of the main reasons why we can sell into the enterprise because we now know everyone can use it.
[00:17:36.760 --> 00:17:37.960] But this is the hard part.
[00:17:38.520 --> 00:17:42.040] When you're doing that market widening, you're not solution deepening.
[00:17:42.040 --> 00:17:45.360] And so your perceived product velocity may decrease.
[00:17:44.680 --> 00:17:50.640] You can avoid some of these things with some smart technology decisions, but mostly you just have to grind through it.
[00:17:50.720 --> 00:17:53.360] And it is worth it to get to the other side.
[00:17:53.360 --> 00:17:57.840] Then there's the kind of slowdown that is avoidable.
[00:17:57.840 --> 00:18:02.960] And if I remember my answer to Rajiv's tweet, that was the kind I was talking about.
[00:18:02.960 --> 00:18:05.920] And in that case, it was our management structure.
[00:18:05.920 --> 00:18:07.360] Or who does what?
[00:18:07.440 --> 00:18:12.880] When we hired our initial executive teams, I followed very conventional wisdom.
[00:18:12.880 --> 00:18:18.560] I ended up with a set of VPs and eight, I think, direct reports, maybe even nine.
[00:18:18.560 --> 00:18:20.560] And I thought that's what you were meant to do.
[00:18:20.560 --> 00:18:23.360] That's how startups are meant to scale.
[00:18:23.360 --> 00:18:27.760] But as anyone who's been there knows, eight direct reports is a lot.
[00:18:27.760 --> 00:18:32.720] It's a lot of hiring, it's a lot of goal setting, it's a lot of OKRs, it's a lot of accountability conversations.
[00:18:32.720 --> 00:18:34.960] And fortunately, also, it's a lot of firing.
[00:18:34.960 --> 00:18:39.360] No CEO ever gets their executive team right on the first try.
[00:18:39.360 --> 00:18:50.320] So that time I had for the things that I think I can genuinely be world-class at, things like product and design and technology and marketing, that all began to rapidly disappear.
[00:18:50.320 --> 00:18:54.320] And as a result, the organization began to slow down.
[00:18:54.560 --> 00:18:58.400] Fortunately, I was also tracking my time very closely.
[00:18:58.400 --> 00:19:00.240] I had this crazy way of tracking it.
[00:19:00.240 --> 00:19:09.280] And at one point, I noticed I was spending six to seven percent of my week on these areas, these areas where I can truly be world class at.
[00:19:09.280 --> 00:19:10.720] So I had two realizations.
[00:19:10.720 --> 00:19:21.360] Number one, as CEO, once you get to a certain scale, and we were definitely at that scale, you can actually define what you want the role of a CEO to be at your company.
[00:19:21.360 --> 00:19:30.120] And number two, the superhuman opportunity deserves everyone who works at the company to spend as much time as possible in their zone of genius.
[00:19:30.120 --> 00:19:33.080] And so that includes me as well as everybody else.
[00:19:29.680 --> 00:19:35.640] So, what I did is I hired a really great president.
[00:19:35.880 --> 00:19:38.680] I went from eight direct reports to two.
[00:19:38.680 --> 00:19:49.560] And the amount of time that I spend on product design, technology, and marketing went up from six to seven percent to about sixty to seventy percent of my week.
[00:19:49.560 --> 00:20:02.040] Just to mirror back a few things: one is people may feel like you are not shipping as much as you used to because you're actually building things they don't care about, which is support for office and all these things that they don't need.
[00:20:02.040 --> 00:20:07.480] But the business needs to expand integrations with Microsoft and Android and all these things.
[00:20:07.480 --> 00:20:14.440] I think that's such a good point that it looks like nothing's happening when there's a lot of good stuff happening for other users that aren't you.
[00:20:14.760 --> 00:20:22.600] And then there's this point about people delegate and then they realize a leader who delegates hires all these execs and then like, this is not what I wanted.
[00:20:22.600 --> 00:20:23.800] Why have I done this?
[00:20:23.800 --> 00:20:27.080] And things, and you think it's going to speed up, but it slows down.
[00:20:27.400 --> 00:20:29.240] A couple threads here that are really interesting.
[00:20:29.240 --> 00:20:31.320] One is this time tracking thing.
[00:20:31.320 --> 00:20:33.480] I need to know what, how do you do this?
[00:20:33.480 --> 00:20:42.680] This is the fact that you knew like seven to eight percent or whatever the number you said, like to that granularity of your time you're spending on things you wanted was that low.
[00:20:42.680 --> 00:20:44.520] How do you do time tracking?
[00:20:44.520 --> 00:20:47.560] Let's not go super far, but just what's your approach?
[00:20:47.880 --> 00:20:51.800] So, this is a technique that I call the switch log.
[00:20:51.800 --> 00:21:04.440] And it's born out of the observation that your calendar says what you thought you were going to do, but it's really only your trail of work that describes what you actually did.
[00:21:04.440 --> 00:21:06.040] So, how can we capture that?
[00:21:06.040 --> 00:21:18.800] And actually, how can we create a system of work that isn't tethered to a calendar where you aren't at the behest of what some timetable says you do or you don't have to do?
[00:21:19.120 --> 00:21:21.680] So, I came up with the following idea.
[00:21:21.680 --> 00:21:25.760] What if I just did whatever the heck I wanted?
[00:21:25.760 --> 00:21:32.960] What if every single time I changed task, I just Slack DM'd my EA?
[00:21:32.960 --> 00:21:37.280] But this also works in Slackbot, like you can just, it just has to go somewhere.
[00:21:37.280 --> 00:21:45.280] I slack DM my EA and I said TS colon and then a few words for the task I was doing.
[00:21:45.600 --> 00:21:48.400] Well, that would create certain changes.
[00:21:48.400 --> 00:21:54.480] Instead of having to constantly look at the calendar and think, oh, should I stop this task, start that task?
[00:21:54.480 --> 00:21:55.680] I can just do what I want.
[00:21:55.680 --> 00:22:01.680] Like, if what I feel right now is, oh boy, I really need to prepare for Lenny's podcast, I'll go ahead and do that.
[00:22:01.680 --> 00:22:12.880] And if I get bored or distracted eight minutes in, which sometimes happens, because something else just bubbles up to the top of my mind, well, there's a reason that my body is bubbling it up to the top of my mind.
[00:22:12.880 --> 00:22:20.400] I also practice transcendental meditation, so I'm very keen on the idea of being aware and listening to what's bubbling up.
[00:22:20.400 --> 00:22:32.160] And so it's okay for me to then go and attend to that thought, as opposed to start to expend my focus points or my discipline or willpower on the thing that I thought I was meant to be doing.
[00:22:32.160 --> 00:22:37.760] All I'd have to do is I'd go back to Slack, TS, colon, dealing with this other thing.
[00:22:37.760 --> 00:22:40.400] And by the way, you should obviously turn up for your meetings.
[00:22:40.400 --> 00:22:44.320] I'm not saying just like blow through your meetings and not turn up for your one-on-ones.
[00:22:44.320 --> 00:22:45.680] Definitely do those things.
[00:22:45.680 --> 00:22:52.080] What I'm saying is, do what feels right for as long as it feels right to do.
[00:22:52.080 --> 00:22:55.200] Then at the end of the week, you can see where your time is going.
[00:22:55.200 --> 00:23:02.360] And I realized at one point that I was spending only, in those days, like 5% of my time on recruiting.
[00:22:59.680 --> 00:23:06.680] Whereas perhaps I should be spending 20 or 30% or more of my time on recruiting.
[00:23:07.000 --> 00:23:14.680] But the biggest thing was I saw I was only spending 6 to 7% of my time on product, on design, on technology, and marketing.
[00:23:14.680 --> 00:23:16.920] And these are things where I know I'm really good at them.
[00:23:16.920 --> 00:23:21.160] I should either be teaching people how to do them or doing them or some combination of both.
[00:23:21.160 --> 00:23:22.840] That's probably the best thing for me.
[00:23:22.840 --> 00:23:28.680] It keeps me really happy, very joyful, keeps me sharp, but it's also scaling the organization.
[00:23:28.680 --> 00:23:30.600] And so that's how we had that kind of an insight.
[00:23:30.600 --> 00:23:37.160] Once you have this Slack log, you can then graph it and chart it and see where your time is actually going.
[00:23:37.480 --> 00:23:38.600] How cool.
[00:23:38.600 --> 00:23:44.360] Clearly, this is an app opportunity or like an agent opportunity where you're just telling this thing every time.
[00:23:44.360 --> 00:23:48.120] It's essentially tracking context switches, which we're always hearing.
[00:23:48.120 --> 00:23:49.800] Try to not avoid context switches.
[00:23:50.120 --> 00:23:52.520] Yeah, I think context switches are fine.
[00:23:52.520 --> 00:24:04.760] I mean, there's definitely this idea that for every interruption you have, the brain does take roughly 21 minutes on average to recover, to get back to the efficacy before that you were disturbed.
[00:24:04.760 --> 00:24:06.040] And it's a big deal, of course.
[00:24:06.040 --> 00:24:07.400] I'm building productivity software.
[00:24:07.400 --> 00:24:13.160] We design superhuman to minimize the amount of distraction and disruption that's possible within the app.
[00:24:13.160 --> 00:24:20.920] But if you're working on something and at the back of your mind, something bubbles up, you have to attend to it in one way or the other.
[00:24:20.920 --> 00:24:26.440] Sometimes I just write it down and I have a actually, I don't have my notebook with me, but it's really big.
[00:24:26.440 --> 00:24:32.440] I have like a gigantic, whatever, twice the size of A4 is, I guess, A3 sketchbook.
[00:24:32.440 --> 00:24:34.680] And I always have a 4-H pencil.
[00:24:34.680 --> 00:24:38.440] So whenever one of those thoughts comes up, I just scribble it down.
[00:24:38.440 --> 00:24:41.960] Or I actually stop what I'm doing and I attend to that task.
[00:24:41.960 --> 00:24:44.200] Because there's a reason it's bubbling up right now.
[00:24:44.200 --> 00:24:49.920] And I'll let you know exactly the type of paper and pencil, 4-H pencil, A3 paper.
[00:24:44.920 --> 00:24:50.720] Very basic one.
[00:24:51.840 --> 00:24:53.360] Okay, this is going to be a theme.
[00:24:53.360 --> 00:24:54.400] You mentioned meditation.
[00:24:54.400 --> 00:24:55.360] You said you do TM.
[00:24:55.360 --> 00:24:57.600] So you do 20 minutes in the morning, 20 minutes.
[00:24:57.760 --> 00:25:00.880] Do you do it that style or you do a longer session?
[00:25:00.880 --> 00:25:03.920] I do about half an hour in the morning, including rest time.
[00:25:03.920 --> 00:25:06.240] The physical rest component of it is very important to me.
[00:25:06.240 --> 00:25:10.080] So it's 20 minutes of the actual meditation, then 10 minutes of rest.
[00:25:10.080 --> 00:25:12.960] And I do that in the morning as well as in the afternoon at around 3 p.m.
[00:25:13.200 --> 00:25:14.640] And you just carve that out on your calendar.
[00:25:14.640 --> 00:25:16.400] You know, everyone knows Rahul at 3 o'clock.
[00:25:16.400 --> 00:25:17.680] He's going to be out.
[00:25:17.680 --> 00:25:18.640] Absolutely.
[00:25:18.640 --> 00:25:24.640] And my EA knows, they are the one who's organizing the calendar and making sure things happen when they need to happen.
[00:25:24.640 --> 00:25:29.520] They also know that nothing can override this TM block.
[00:25:29.680 --> 00:25:32.480] Without it, I genuinely start to fall apart.
[00:25:32.480 --> 00:25:39.040] But with it, I'm able to access some very deep competencies that I didn't have before.
[00:25:39.040 --> 00:25:41.600] I've been doing this now for about four or five years.
[00:25:41.600 --> 00:25:49.840] And initially, I simply felt happier, occasionally even more euphoric, coming out of a really great meditation session.
[00:25:49.840 --> 00:25:54.960] But over time, I found that my ability to focus was increasing.
[00:25:54.960 --> 00:26:02.240] I could hold attention on something for much longer, but I also was able to become much more creative and much more expressive.
[00:26:02.560 --> 00:26:08.320] These are well-known side effects, as it were, or intended effects for some people of TM.
[00:26:08.640 --> 00:26:17.040] And interestingly about TM, if you compare it to other forms of meditation, they don't have quite the same impact across quite as many executive functions.
[00:26:17.040 --> 00:26:25.520] So there's something particularly interesting that's going on with transcendental meditation as opposed to other forms that folks are still trying to unravel and figure out.
[00:26:26.160 --> 00:26:32.200] Folks want to, if they're inspired and they want to check out this form of meditation, any advice on where they could go learn?
[00:26:32.520 --> 00:26:33.560] Absolutely.
[00:26:33.560 --> 00:26:34.120] A lot.
[00:26:34.120 --> 00:26:37.640] But in summary, have a coach teach you.
[00:26:37.640 --> 00:26:42.760] I had many false starts myself with meditation, trying the various apps, learning from books.
[00:26:42.760 --> 00:26:44.920] None of it really worked for me.
[00:26:44.920 --> 00:26:56.200] What worked was having one-on-one teaching from someone themselves who had been taught one-on-one, the yogic or the Raj tradition of teaching.
[00:26:56.200 --> 00:27:03.000] And this person in particular had also been a venture-backed founder multiple times over.
[00:27:03.000 --> 00:27:10.840] And so they're very well aware of the kinds of stresses that I tend to be under, and all of his clients are mostly in technology as well.
[00:27:10.840 --> 00:27:19.560] If you're in the Bay Area, this person's name is Laurent Valasek, and they run an institution called the Peak Leadership Institute.
[00:27:19.560 --> 00:27:30.920] And this is all about how we can live a more integrated and whole life, integrating wellness practices like meditation, but for the purpose of unlocking peak performance in life and in business.
[00:27:30.920 --> 00:27:31.800] Thank you for sharing that.
[00:27:31.800 --> 00:27:33.160] That is very actionable.
[00:27:33.160 --> 00:27:35.400] We're going to link to that in the show notes.
[00:27:35.400 --> 00:27:37.800] Okay, I'm going to try to bring us back on course.
[00:27:37.800 --> 00:27:41.720] The other thing you mentioned that I think is really interesting is hiring a president.
[00:27:41.720 --> 00:27:51.160] A lot of founders and leaders might be hearing this and be like, going from eight reports and doing all these things I don't want to spending most of my time on the product and design and marketing, amazing.
[00:27:51.160 --> 00:27:58.680] What did this president take off your plate and what is their responsibility that allowed you to do the stuff you wanted to do?
[00:27:58.680 --> 00:28:07.800] The biggest thing was taking off the operations and the management of the executive team and the rest of the company.
[00:28:07.800 --> 00:28:16.000] So think of the president role in Superhuman as an operationally, extremely challenging and very growthful role.
[00:28:16.000 --> 00:28:22.240] Like it is, it's perfect for someone who wants to go on to be a CEO in their next role.
[00:28:22.560 --> 00:28:35.040] And instead of hiring and firing that team, instead of managing and setting their goals, instead of the accountability conversations, someone else is now doing that.
[00:28:35.040 --> 00:28:50.240] In addition, because that's not the only job, in addition, they're also a very strong thought partner when it comes to corporate strategy, when it comes to where do we take Act One, our email product.
[00:28:50.240 --> 00:28:52.880] How far do we go down the multiplayer path?
[00:28:53.120 --> 00:28:56.080] How aggressively should we lean into AI?
[00:28:56.400 --> 00:29:00.080] What's a reasonable gross margin in a world with AI?
[00:29:00.080 --> 00:29:04.880] Are we, from a financial perspective, okay, dipping now and then coming back later?
[00:29:04.880 --> 00:29:07.440] When should we start building our second product?
[00:29:07.440 --> 00:29:10.000] How do we think about our RD strategy?
[00:29:10.000 --> 00:29:12.000] Should we keep on hiring in the Bay Area?
[00:29:12.000 --> 00:29:18.080] Or, as we've done for many of our recent hires, should we continue hiring in Latin America?
[00:29:18.080 --> 00:29:20.880] Should we consider other time zones as well?
[00:29:20.880 --> 00:29:22.320] And so on and so on and so on.
[00:29:22.320 --> 00:29:26.080] I mean, I'm just randomly coming up with questions, but the list is truly endless.
[00:29:26.080 --> 00:29:33.040] It is another way to think about it: it's like a grown-up co-founder.
[00:29:33.040 --> 00:29:38.640] The two people I co-founded the company with, Conrad and Vivek, they've long since gone from Superhuman.
[00:29:38.640 --> 00:29:45.680] We're now a 10-year-old organization, and I'm one of those rare founders that is persisting and thriving actually 10 years in.
[00:29:46.000 --> 00:29:54.880] That said, the journey never gets easier, it gets different, and you still need that co-founding energy around you.
[00:29:54.880 --> 00:30:03.960] And I have a handful of people in the organization who are in their roles providing that kind of energy, that kind of inputs, and who thrive off doing so.
[00:29:59.840 --> 00:30:05.720] And then the president role is definitely one of them.
[00:30:06.920 --> 00:30:08.680] Incredibly interesting.
[00:30:08.680 --> 00:30:10.440] There's so many, so much there.
[00:30:10.760 --> 00:30:14.840] One, just a couple of things I'll share, and then I want to move on to a different topic.
[00:30:14.840 --> 00:30:21.800] One is just, it's cool, the solution to helping you move faster and do the work you want to do is org design.
[00:30:21.800 --> 00:30:25.640] That feels like a really doable thing.
[00:30:25.640 --> 00:30:38.600] If you're finding you're not spending time on things you want to spend on time on and things aren't moving as fast as you want, it's essentially you can find people to take on things that you don't want and shift the way that the org is structured and that could solve a lot of problems.
[00:30:38.600 --> 00:30:39.880] That's what it did for you.
[00:30:39.880 --> 00:30:41.560] And then I think it's also really interesting.
[00:30:41.560 --> 00:30:50.760] There's this lesson here of as a founder, if you're just feeling like, I don't know, depleted or just like not, don't have the partner you want, you could bring someone on that could be that person.
[00:30:50.760 --> 00:30:51.800] Absolutely.
[00:30:51.800 --> 00:30:52.520] Yep.
[00:30:52.520 --> 00:30:52.920] Okay.
[00:30:52.920 --> 00:30:53.640] There's so much there.
[00:30:53.640 --> 00:30:57.000] That was much more of a rich area than I even expected.
[00:30:57.000 --> 00:30:58.680] I want to zoom out a little bit.
[00:30:58.680 --> 00:31:06.280] And there's a couple themes that came up again and again when I talked to folks that you've worked with, investors and superhuman.
[00:31:06.280 --> 00:31:13.800] And the two themes are contrarian thinking in terms of building the company and strong attention to detail.
[00:31:13.800 --> 00:31:16.360] Let's spend a little time on attention to detail.
[00:31:16.360 --> 00:31:21.000] And like I said, this is one of the things that came up again and again when I was asking people about you.
[00:31:21.000 --> 00:31:23.800] So I have this quote from Ed Sims.
[00:31:23.960 --> 00:31:25.240] Maybe your first investor?
[00:31:25.240 --> 00:31:26.840] Were they your first investor?
[00:31:26.840 --> 00:31:29.800] Yeah, there's a bunch of people on Twitter who are going to fight for that.
[00:31:29.800 --> 00:31:35.880] But to get the record straight, Ed Sim did actually write the first three checks into Superhuman.
[00:31:35.880 --> 00:31:38.600] First three checks, like subsequent rounds.
[00:31:38.600 --> 00:31:41.160] Well, yeah, I mean, quick sidebar on that.
[00:31:41.560 --> 00:31:46.320] He runs Boldstart Ventures alongside his partner, Elliot Durbin.
[00:31:46.960 --> 00:31:53.920] And they have a particular interest in backing second-time founders, but they'll also back first-time founders.
[00:31:53.920 --> 00:31:58.240] And they love application and infrastructure areas like Superhuman.
[00:31:58.240 --> 00:32:00.160] So we were like the perfect investment.
[00:32:00.160 --> 00:32:04.240] He also wrote a check from his previous fund into Reportive.
[00:32:04.240 --> 00:32:07.040] And I think I'd made him like 5x that money.
[00:32:07.280 --> 00:32:11.040] Nothing to write home about, but definitely I'm going to back this guy again, right?
[00:32:11.040 --> 00:32:15.360] And so I went to him and I said, Hey, listen, and this is going to sound crazy.
[00:32:15.360 --> 00:32:16.720] I want to take on Gmail.
[00:32:16.720 --> 00:32:17.680] He said, Do you have a deck?
[00:32:17.680 --> 00:32:18.640] I was like, Yeah, here it is.
[00:32:18.640 --> 00:32:19.760] One slide, here it is.
[00:32:19.760 --> 00:32:22.480] And it was a screenshot of Gmail with most of it scribbled out.
[00:32:22.640 --> 00:32:23.520] I want to build that.
[00:32:23.520 --> 00:32:25.520] It was going to be amazing.
[00:32:26.000 --> 00:32:28.240] So he said, Cool, we're in.
[00:32:28.560 --> 00:32:29.760] Can I wire you the money?
[00:32:29.760 --> 00:32:31.520] And I said, No, I don't even have a bank account yet.
[00:32:31.680 --> 00:32:34.400] I come back two days later with a bank account.
[00:32:34.400 --> 00:32:37.920] And he's like, Cool, I want to wire you 750K.
[00:32:37.920 --> 00:32:41.120] And I said, I don't even know what I'm going to do with that money.
[00:32:41.120 --> 00:32:42.240] I'm not paying myself.
[00:32:42.240 --> 00:32:43.520] I won't for a while.
[00:32:43.520 --> 00:32:45.680] We don't have any employees.
[00:32:46.000 --> 00:32:48.240] I can't think of anything I want to spend it on.
[00:32:48.240 --> 00:32:50.880] Tell you what, I'll just take 250K.
[00:32:50.880 --> 00:32:52.160] And he was like, What?
[00:32:52.240 --> 00:32:54.800] No, yeah, I'll just take 250K.
[00:32:55.120 --> 00:32:57.680] We start having the conversation around venture economics.
[00:32:57.680 --> 00:32:59.200] I'm like, yeah, you know, it's fine.
[00:32:59.200 --> 00:33:00.240] We'll figure it out.
[00:33:00.240 --> 00:33:02.480] And then a few months back, I took another 250K.
[00:33:02.480 --> 00:33:10.960] And a few months back, I took another 250K as I began inventing ways and finding channels to deploy capital properly.
[00:33:11.280 --> 00:33:12.240] I love this story.
[00:33:12.240 --> 00:33:13.440] I love all these stories you're sharing.
[00:33:13.440 --> 00:33:14.720] I've never heard before.
[00:33:14.720 --> 00:33:15.840] And by the way, Ed is awesome.
[00:33:15.840 --> 00:33:19.520] We're talking about him coming on the podcast, maybe breaking our VC rule.
[00:33:19.840 --> 00:33:29.120] So, specifically, the story he shared with me that is maybe an example of you and your attention to detail is he said that you created your own font because existing fonts weren't good enough.
[00:33:29.120 --> 00:33:30.000] Is that true?
[00:33:31.080 --> 00:33:32.040] Kinda.
[00:33:32.040 --> 00:33:32.440] Okay.
[00:33:32.760 --> 00:33:38.280] The font that we use today is a modified version of Adele Sans.
[00:33:38.280 --> 00:33:48.520] And the story there is: I looked at all of the major font families, and honestly, none of them was what I would call truly excellent.
[00:33:48.520 --> 00:33:50.680] And that may sound like an odd thing to say.
[00:33:50.680 --> 00:33:56.120] So, let's, if you will, permit me to talk about typography and email for a minute.
[00:33:56.440 --> 00:34:05.880] So, the first thing we did was we took our UI and we laid it out in about 15 different styles using examples of the major font families.
[00:34:05.880 --> 00:34:11.160] We actually printed these out and we left them on a desk in the middle of our office.
[00:34:11.480 --> 00:34:23.400] Sometimes with design, you want to tune in to your immediate, most visceral response, but sometimes you want to truly let a design marinate.
[00:34:23.400 --> 00:34:24.600] And this was the latter.
[00:34:24.600 --> 00:34:26.440] So, we let these designs marinate.
[00:34:26.440 --> 00:34:29.400] We let these font choices percolate.
[00:34:29.400 --> 00:34:31.640] And like I said, none of them was truly excellent.
[00:34:31.800 --> 00:34:36.040] Number one, I was looking for a font that was in and of itself gorgeous.
[00:34:36.040 --> 00:34:44.200] Number two, I was looking for a font that could also convey a message of any kind without overpowering the sentiment of that message.
[00:34:44.200 --> 00:34:49.480] For example, does the font work when this is inviting you to a party?
[00:34:49.480 --> 00:34:54.840] Many fonts, including almost all serif fonts, are actually too somber or too sober for that.
[00:34:54.840 --> 00:35:01.640] Or to pick another extreme, does the font work if it is informing you of somebody's passing?
[00:35:01.640 --> 00:35:03.800] Many fonts are just too jaunty for that.
[00:35:03.960 --> 00:35:07.720] You wouldn't want that kind of message in Comic Sans, for example.
[00:35:07.720 --> 00:35:14.280] And number three, I was optimizing for a font that made reading speed and comprehension really fast.
[00:35:14.280 --> 00:35:20.240] And number four, I was looking for fonts that made email addresses themselves look great.
[00:35:20.560 --> 00:35:23.360] So I discarded all the 15 because they weren't good enough.
[00:35:23.360 --> 00:35:31.120] And after searching high and low, I came across a font called Adele Sans, which is designed by a foundry called Type Together.
[00:35:31.120 --> 00:35:32.720] It's type-together.com.
[00:35:32.800 --> 00:35:34.320] They have a whole bunch of lovely fonts.
[00:35:34.320 --> 00:35:35.520] Go check them out.
[00:35:35.840 --> 00:35:39.360] And if you go through my list, number one, Adele Sans is gorgeous.
[00:35:39.360 --> 00:35:41.120] I think each character is a work of art.
[00:35:41.120 --> 00:35:42.400] It's beautifully formed.
[00:35:42.400 --> 00:35:50.080] Number two, Adele Sans is, I would say, upbeat, it's optimistic, yet it's serious enough to convey any kind of message.
[00:35:50.080 --> 00:35:54.880] It has just the right amount of personality, yet not too much personality.
[00:35:54.880 --> 00:36:02.240] Number three, Adele Sans is also unusually narrow, and that actually fits email particularly well.
[00:36:02.240 --> 00:36:09.600] One of my pet peeves with Gmail, which by default uses Arial, is that the lines are as wide as your window.
[00:36:09.600 --> 00:36:15.040] So if you're in a wide screen, then the lines get really arbitrarily long.
[00:36:15.040 --> 00:36:25.120] And the problem with really wide and really long lines is that they decrease reading speed, because by the time you've reached the end of one line, your eyes have lost track of the start of the next line.
[00:36:25.120 --> 00:36:29.920] And Arial itself has fairly wide characters, which further exacerbates that.
[00:36:29.920 --> 00:36:42.960] So at Superhuman, if you've used the product, you know this, we fix the line length or the typographical measure to the optimal length for reading speed, which depending on the font is around 90 to 120 characters.
[00:36:42.960 --> 00:36:51.360] And Adele Sans is quite narrow, so it actually lets us do this on quite small windows with a fairly dense line.
[00:36:51.360 --> 00:37:00.920] So, we get a lot of information on fairly small windows without getting a very long typographical measure, optimizing for reading speed and for comprehension.
[00:37:01.240 --> 00:37:07.640] And then, number four, finally, Adele Sans has a very unusual treatment of the at symbol in an email address.
[00:37:07.640 --> 00:37:15.160] It actually puts the base of the A in the at on the same baseline as the rest of the text.
[00:37:15.160 --> 00:37:25.800] So, for example, if your name has an A, my name does Rahul at Voras, three A's or two A's and an at, they're all actually on the same baseline.
[00:37:25.800 --> 00:37:31.000] It's a small thing, but it makes the email addresses look incredibly natural.
[00:37:31.000 --> 00:37:41.320] If you look at that and then you actually look at email addresses laid out in other fonts, those other fonts look really clunky and awkward because the A is kind of shifted around and it just looks a bit silly in my opinion.
[00:37:41.320 --> 00:37:42.840] Now, Adele Sams isn't perfect.
[00:37:42.840 --> 00:37:51.080] So, we then worked with a type designer on some of the specific details that there are some of the glyphs which get a little pincery, as it were.
[00:37:51.080 --> 00:37:54.840] And what we use today is very close to retail Adele Sams.
[00:37:55.160 --> 00:37:58.520] And this was pre-launch, or this was after you'd already launched?
[00:37:58.840 --> 00:38:03.320] We probably had about 10, 15 users' appetite.
[00:38:03.320 --> 00:38:11.160] So, I think that's pretty contrarian, unique to be this focused on the font and the typeface before you even launch.
[00:38:11.160 --> 00:38:13.160] This was like, is this even going to be a thing?
[00:38:13.160 --> 00:38:14.440] Will anyone even care?
[00:38:14.440 --> 00:38:17.480] And I think this says a lot about the way you think about product.
[00:38:17.800 --> 00:38:20.840] Oh, yeah, that I mean, that thought never crossed my mind.
[00:38:21.000 --> 00:38:29.960] I think we'll probably come to it later, but the idea that is this never going to be a thing, I think that's a dangerous thought.
[00:38:30.280 --> 00:38:35.240] We can't start thinking that way, because at what point do you stop second-guessing it yourself?
[00:38:35.560 --> 00:38:36.120] Interesting.
[00:38:36.120 --> 00:38:39.000] So, you're like, you were confident this was going to work.
[00:38:39.000 --> 00:38:43.320] So, because I am so confident it will work, I will make, I need to get this right.
[00:38:43.640 --> 00:38:50.000] There's also just, you know, this trap founders fall into of just spending too much time perfecting a thing that never works.
[00:38:50.000 --> 00:38:53.040] And there's always advice, launch early, launch often.
[00:38:53.520 --> 00:38:54.240] Thoughts there.
[00:38:54.240 --> 00:38:55.600] Just like, how do you find that balance?
[00:38:55.600 --> 00:38:57.120] What's your advice there?
[00:38:57.440 --> 00:39:06.480] How much to spend time ahead of launch really does depend on the markets and the structure, the nature of your business model.
[00:39:06.480 --> 00:39:12.800] For example, let's say you're building a marketplace in a greenfield opportunity.
[00:39:12.800 --> 00:39:16.880] So imagine Lyft or Uber in their heyday.
[00:39:17.200 --> 00:39:22.080] And there's a strong network effect because the more cars you have on your platform, the shorter waiting times are.
[00:39:22.080 --> 00:39:27.040] Therefore, people are going to preferentially use your app versus the other person's app.
[00:39:27.360 --> 00:39:29.760] That's when there's no time to spare.
[00:39:29.760 --> 00:39:33.200] That's when you probably shouldn't even be sleeping.
[00:39:33.200 --> 00:39:36.720] You're going to hire the most aggressive, maniacal people possible.
[00:39:36.720 --> 00:39:42.160] You're going to work 120-hour weeks because every marginal minute actually does matter.
[00:39:42.480 --> 00:39:50.640] Every marginal minute in the market, growing compounding is going to make your next year even better.
[00:39:50.960 --> 00:39:57.520] That's actually not true of all startups, and it certainly isn't true of something like Superhuman.
[00:39:57.520 --> 00:40:10.560] Yes, working harder is always better, and we work tremendously hard at Superhuman, but not to the point where it made sense to release something that didn't work.
[00:40:10.560 --> 00:40:20.560] I'm reminded of a story of a founder that was in White Combinator told me about their demo day experience.
[00:40:20.560 --> 00:40:25.760] And they used Mailbox, which some folks may remember, was also a startup.
[00:40:25.760 --> 00:40:29.440] And Dropbox famously acquired them for about $100 million.
[00:40:29.560 --> 00:40:42.120] And the reason that they were well known, apart from the acquisition, is they were the first to popularize swipe to archive or swipe to Markdown, which of course is now standard in Superhuman and every other app.
[00:40:43.080 --> 00:40:49.800] So this founder was using Mailbox and was having an amazing demo day.
[00:40:49.800 --> 00:40:55.800] They're working in the room, they're meeting investors, they're pitching their photography app in this case.
[00:40:55.800 --> 00:41:05.160] And he went home that night and went to his laptop, fired up Mailbox, and sent off a bunch of follow-up emails.
[00:41:05.160 --> 00:41:07.800] He waited a day, didn't hear back.
[00:41:07.800 --> 00:41:10.760] He waited two days, didn't hear back.
[00:41:10.760 --> 00:41:13.480] On the third morning, he figured something was up.
[00:41:13.480 --> 00:41:20.120] So he fired up Gmail, went to his sent mail, and you guessed it, there were no sent mails there.
[00:41:20.120 --> 00:41:23.880] So something had broken with Mailbox.
[00:41:23.880 --> 00:41:28.920] So he's cursing to himself, trying to remind himself everything's going to be okay.
[00:41:29.240 --> 00:41:33.720] Sent all the same emails from Gmail manually.
[00:41:33.720 --> 00:41:35.880] And they all came through.
[00:41:36.840 --> 00:41:44.680] But then one of the investors said, hey, by the way, you might want to check your email client because I've been getting some of your emails twice.
[00:41:44.680 --> 00:41:46.440] And now he goes back into Gmail.
[00:41:46.520 --> 00:41:52.200] He sees that, yes, actually, the original emails that were queued up in Mailbox have now indeed been sent.
[00:41:52.200 --> 00:41:56.440] And some of the investors, unfortunately, most of the investors, he actually pitched twice.
[00:41:56.440 --> 00:41:58.360] Now, is this the end of the world?
[00:41:58.360 --> 00:41:59.000] No.
[00:41:59.000 --> 00:42:00.440] An investor can overlook that.
[00:42:00.440 --> 00:42:02.920] Probably a good thing that you're trying new apps.
[00:42:02.920 --> 00:42:04.280] But was it horrifying?
[00:42:04.280 --> 00:42:05.760] And was it terrible?
[00:42:05.840 --> 00:42:07.240] Like, was it really scary?
[00:42:07.240 --> 00:42:08.440] Absolutely.
[00:42:08.440 --> 00:42:10.040] And imagine this wasn't investors.
[00:42:10.040 --> 00:42:21.200] Imagine this was a customer, someone who you were trying to convince to buy your thing and that you knew what you were doing and you had attention to detail and you had everything just buttoned up and under control.
[00:42:14.840 --> 00:42:22.320] Well, now you've lost face.
[00:42:22.400 --> 00:42:24.000] Now you look foolish.
[00:42:24.000 --> 00:42:34.560] And that's why when you have mission-critical products like email, where you are interfacing with customers, with candidates, with investors, it turns out to really matter.
[00:42:34.560 --> 00:42:36.240] Email is mission-critical.
[00:42:36.240 --> 00:42:40.560] So it's not something where you can simply launch with a half-bates product.
[00:42:40.560 --> 00:42:42.720] This is such an important nuanced take on.
[00:42:42.720 --> 00:42:50.400] There's always this debate: how much to focus on craft and user experience, how much to focus on time to launch and get it out and speed.
[00:42:50.400 --> 00:42:58.400] And what I'm hearing here, which I completely agree with, is it depends on the market you're in and the criticality essentially of how of your product.
[00:42:58.400 --> 00:42:59.840] So if it's email, it just needs to work.
[00:42:59.840 --> 00:43:00.640] You need to get that right.
[00:43:00.640 --> 00:43:01.600] You need to spend all the time.
[00:43:01.600 --> 00:43:03.120] You need to get that right.
[00:43:03.120 --> 00:43:08.800] This reminds me of something else that one of your early investors shared with me, Bill Trenchard from First Round Capital.
[00:43:08.800 --> 00:43:14.080] He talked about how speed was the thing that you just dialed up as a lever to like 11.
[00:43:14.080 --> 00:43:18.720] That's where you just, we will make this the focus, speed, speed, speed.
[00:43:19.040 --> 00:43:27.520] And I think maybe the lesson there is just you pick the thing that you think will most differentiate you, make you significantly better than what's out there.
[00:43:27.520 --> 00:43:37.360] So I guess just thoughts and just how to decide, how you decided speed was the thing you were going to obsess with, and just, I don't know, advice for folks that are trying to decide where to dial up things to 11.
[00:43:37.680 --> 00:43:39.280] Bill is right, and I agree with him.
[00:43:39.280 --> 00:43:41.280] You have to pick something.
[00:43:41.600 --> 00:43:44.320] Knowing what to pick is the trick.
[00:43:44.320 --> 00:43:50.240] And in the early days of Superhuman, I read a book on positioning that really influenced my thinking.
[00:43:50.240 --> 00:43:54.240] And it is, I believe, called Positioning the Battle for Your Mind.
[00:43:54.560 --> 00:44:01.960] And it struck me how the most well-known brands have stood for one clear thing, like they have a clear position.
[00:44:02.280 --> 00:44:13.240] And so in order for Superhuman to be memorable, I believed that we needed to occupy a clear position that was unique and which was available and which reinforced our product strategy.
[00:44:13.240 --> 00:44:20.920] In the first year of Superhuman, therefore, I interviewed hundreds of potential customers about their experience with Gmail and with Outlook.
[00:44:20.920 --> 00:44:26.280] And predictably, almost everybody said that email takes way too much time.
[00:44:26.280 --> 00:44:33.480] But interestingly, many people also said that Gmail and Outlook were way too slow.
[00:44:33.800 --> 00:44:39.000] And that was how I first thought that speed could be an interesting position for us.
[00:44:39.000 --> 00:44:44.040] I then asked myself, is the position of speed unique and is it available?
[00:44:44.040 --> 00:44:54.440] And the answer was overwhelmingly yes, because almost no software was being sold or has ever been sold on the value proposition of speed.
[00:44:54.440 --> 00:45:02.040] The last time I could remember anyone trying to do this was when Google launched Chrome, and obviously that went incredibly well for them.
[00:45:02.040 --> 00:45:13.800] And you may remember they had slow motion videos where they were comparing Chrome render web pages and showing that was faster than an actual strike of lightning.
[00:45:13.800 --> 00:45:15.800] And no one had done it since then.
[00:45:15.800 --> 00:45:20.280] And I then asked, well, does speed reinforce our product strategy?
[00:45:20.280 --> 00:45:22.680] And again, the answer was overwhelmingly yes.
[00:45:22.680 --> 00:45:25.480] I knew that our competition was not going to be startups.
[00:45:25.480 --> 00:45:27.000] It was incumbents.
[00:45:27.000 --> 00:45:37.000] And I also knew that incumbents generally struggle with speed, because by definition, they have massive scale and usually entrenched architecture.
[00:45:37.000 --> 00:45:47.680] And then finally, I did what I call the cocktail party test, which is to look at cocktail parties and to watch how people pitch your product to other people.
[00:45:47.680 --> 00:45:49.920] And in our case, the pitches were simple.
[00:45:49.920 --> 00:45:53.120] People would say, dude, you have to use it.
[00:45:53.120 --> 00:45:54.800] It's really fucking fast.
[00:45:54.800 --> 00:45:55.680] And that's it.
[00:45:55.680 --> 00:45:56.800] That was the pitch.
[00:45:56.800 --> 00:46:00.800] And that's how I knew that speed would be a really great position for us to start with.
[00:46:01.120 --> 00:46:07.120] I'm excited to chat with Christina Gilbert, the founder of One Schema, one of our longtime podcast sponsors.
[00:46:07.120 --> 00:46:08.320] Hi, Christina.
[00:46:08.320 --> 00:46:10.400] Yes, thank you for having me on, Lenny.
[00:46:10.400 --> 00:46:12.480] What is the latest with One Schema?
[00:46:12.480 --> 00:46:18.400] I know you now work with some of my favorite companies like Ramp, Vanta, Scale, and Watershed.
[00:46:18.400 --> 00:46:25.920] I heard that you just launched a new product to help product teams import CSVs from especially tricky systems like ERPs.
[00:46:25.920 --> 00:46:34.800] Yes, so we just launched OneSchema File Feeds, which allows you to build an integration with any system in 15 minutes as long as you can export a CSV to an SFTP builder.
[00:46:34.800 --> 00:46:43.360] We see our customers all the time getting stuck with hacks and workarounds, and the product teams that we work with don't have to turn down prospects because their systems are too hard to integrate with.
[00:46:43.360 --> 00:46:47.760] We allow our customers to offer thousands of integrations without involving their engineering team at all.
[00:46:47.760 --> 00:46:59.360] I can tell you that if my team had to build integrations like this, how nice would it be to be able to take this off my roadmap and instead use something like OneSchema and not just to build it, but also to maintain it forever?
[00:46:59.360 --> 00:47:00.400] Absolutely, Lenny.
[00:47:00.400 --> 00:47:05.120] We've heard so many horror stories of multi-day outages from even just a handful of bad records.
[00:47:05.120 --> 00:47:11.120] We are laser focused on integration reliability to help teams end all of those distractions that come up with integrations.
[00:47:11.120 --> 00:47:18.960] We have a built-in validation layer that stops any bad data from entering your system, and OneSchema will notify your team immediately of any data that looks incorrect.
[00:47:18.960 --> 00:47:24.720] I know that importing incorrect data can cause all kinds of pain for your customers and quickly lose their trust.
[00:47:24.720 --> 00:47:26.560] Christina, thank you for joining us.
[00:47:26.560 --> 00:47:30.440] And if you want to learn more, head on over to oneschema.co.
[00:47:29.920 --> 00:47:31.960] That's oneschema.co.
[00:47:33.240 --> 00:47:46.760] The next area I want to spend time on, and I imagine we'll have much insight, is some of the contrarian ways you approach building superhuman that a lot of companies never thought about doing that you did that worked out for you.
[00:47:46.760 --> 00:47:51.400] So the first is manually onboarding every single new user.
[00:47:51.720 --> 00:47:58.200] Sure, startups have done this, like, you know, founders bring on some folks and then like, cool, show it, show it to them, and then they stop doing that.
[00:47:58.200 --> 00:48:00.680] And then it's like self-service or sales teams.
[00:48:01.640 --> 00:48:08.120] How far did you scale this manual onboarding phase of your company?
[00:48:08.120 --> 00:48:09.640] Like, how many people did you have onboarding people?
[00:48:09.640 --> 00:48:11.720] How many people did you manually onboard?
[00:48:12.040 --> 00:48:20.520] Yeah, so for folks that don't know, in those early days, we insisted on one-to-one concierge onboarding, and it was absolutely the right thing to do.
[00:48:20.520 --> 00:48:24.440] You couldn't use superhuman unless you went through the onboarding experience.
[00:48:24.440 --> 00:48:26.120] And now it's almost the reverse.
[00:48:26.120 --> 00:48:29.560] Almost every new superhuman customer goes through self-service.
[00:48:29.560 --> 00:48:31.240] The onboarding experience is still there.
[00:48:31.240 --> 00:48:34.440] But again, it is absolutely the right thing to do.
[00:48:34.440 --> 00:48:40.440] To answer your question, at peak, we had about 20 people doing manual onboarding.
[00:48:40.440 --> 00:48:41.800] Okay, so it's not that many people.
[00:48:41.800 --> 00:48:43.080] That's really interesting.
[00:48:43.080 --> 00:48:49.480] Because I always imagined it was like a massive team, but 20 people can do, can handle a lot is the takeaway there.
[00:48:49.480 --> 00:48:55.480] What was the scale, I guess, where you stopped manual onboarding, just for folks that are like thinking about doing this and then went to stop?
[00:48:55.480 --> 00:49:03.720] So I think the reason to stop is that there will always be certain personality types who do not want to go through a one-on-one onboarding.
[00:49:03.720 --> 00:49:07.080] And at a certain point, those people will become very important.
[00:49:07.080 --> 00:49:11.720] And you will need to be ready with a world-class self-service option.
[00:49:11.720 --> 00:49:16.480] When we started building self-service, it seemed nearly impossible.
[00:49:16.640 --> 00:49:35.280] In fact, it was terrifying because it's difficult to overstate how much the entire DNA of the company was built around this idea that we would onboard users manually.
[00:49:35.280 --> 00:49:40.640] And after all, we did so much in our one-to-one onboardings, and there's only so much that software can do.
[00:49:40.640 --> 00:49:44.080] Now, we did, after a lot of grind and persistence, eventually figure it out.
[00:49:44.080 --> 00:49:49.440] And we have a world-class self-service experience today, but we did not at the time.
[00:49:49.760 --> 00:49:53.840] So the flip side is, why would you even do this to begin with?
[00:49:53.840 --> 00:49:55.280] Well, we found two things.
[00:49:55.280 --> 00:50:03.760] Number one, the user metrics are excellent for things like engagement, retention, product market fit score, NPS, virality, for all of those metrics.
[00:50:03.760 --> 00:50:12.320] I think you will significantly beat your industry benchmarks if you go to the effort of one-on-one onboarding your early customers.
[00:50:12.320 --> 00:50:20.240] And it becomes so powerful to have that early cohort of super fans when it comes to things like building a brand.
[00:50:20.240 --> 00:50:26.240] And if folks remember that conversation from way up at the top, what is it that creates true virality?
[00:50:26.240 --> 00:50:27.760] It's not viral mechanics.
[00:50:27.760 --> 00:50:28.960] It's word of mouth.
[00:50:28.960 --> 00:50:29.840] It is brand.
[00:50:30.000 --> 00:50:32.640] This is how you can kickstart a brand.
[00:50:32.640 --> 00:50:47.600] And number two, in a world where you can easily and quickly raise funding, like for example, the zero interest rate phenomenon era, you can actually use dollars to avoid building a first-time user experience and all of the normal growth loops that you would then have to build.
[00:50:47.600 --> 00:51:04.920] You would then instead focus all of your engineers on finding product market fit or in solution deepening or in market widening, but not, for example, on a first-time user experience, not, for example, on activation because you have humans doing activation for you.
[00:51:05.240 --> 00:51:17.080] And by contrast, I saw other companies often competing spend almost half their engineering dollars on those things, on self-service flows for products that ultimately did not find product market fit.
[00:51:17.080 --> 00:51:24.600] So makes sense to do if you really want to create that brand, which I think all consumerist companies need to do.
[00:51:24.600 --> 00:51:31.160] And if there is a, you know, there is money falling off trees for whatever reason, which we did have for a period of time.
[00:51:31.160 --> 00:51:33.960] Arguably, AI companies have that again today.
[00:51:33.960 --> 00:51:39.960] So if you can weave this into your strategy, I think you should, but you should also know when to stop.
[00:51:39.960 --> 00:51:41.000] Super interesting.
[00:51:41.000 --> 00:51:46.280] So I guess some factors to think about, because I wanted to ask you, when should people consider doing this?
[00:51:46.280 --> 00:51:47.960] If they're hearing this, they're like, this is awesome.
[00:51:48.120 --> 00:51:51.800] So many problems solved if I just have somebody onboarding every new user.
[00:51:51.880 --> 00:51:52.760] Everyone's activated.
[00:51:52.760 --> 00:51:53.560] Amazing.
[00:51:53.880 --> 00:52:03.080] So some of the variables you're sharing is: do you have like cheap cash to invest in, say, like it doesn't have to be 20 people, it could be a few people to start.
[00:52:03.080 --> 00:52:09.880] And then if there's like an LTV kind of ACV element of just like, are you going to make enough from a new customer?
[00:52:09.880 --> 00:52:11.240] I imagine that's a variable.
[00:52:11.480 --> 00:52:14.040] Is there anything else you think founders should think about?
[00:52:14.360 --> 00:52:15.000] Absolutely.
[00:52:15.000 --> 00:52:16.360] You don't want to lose money doing this.
[00:52:16.360 --> 00:52:19.960] And we always made money doing onboarding, to be clear.
[00:52:19.960 --> 00:52:31.240] It's just that at a certain point, that the mass market, whether it for us as enterprise or all of the prosumers in the world, you hit a top of funnel width.
[00:52:31.240 --> 00:52:37.160] It needs to be wide enough where manually onboarding no longer makes sense.
[00:52:37.160 --> 00:52:37.800] Awesome.
[00:52:37.800 --> 00:52:38.360] Okay.
[00:52:38.360 --> 00:52:40.040] Let's talk about product market fit.
[00:52:40.040 --> 00:52:43.720] I know that everyone, when they think of Rahul, they think product market fit.
[00:52:43.720 --> 00:52:48.720] You wrote this epic first round post that described the way you guys approach product market fit.
[00:52:48.720 --> 00:52:53.200] We're not going to spend a lot of time on describing it because people can look it up.
[00:52:53.200 --> 00:53:06.720] So let me just ask you this: just what are, I don't know, a couple things that you think people still don't understand about finding product market fit, getting to product market fit, considering it's the most important thing you got to figure out as a founder, right?
[00:53:06.720 --> 00:53:09.680] If you don't find something people want, nothing else matters.
[00:53:09.920 --> 00:53:11.600] Anything there you want to share?
[00:53:11.920 --> 00:53:20.160] The core ideas are still weird enough that I'll start there, which is number one, you can measure product market fit.
[00:53:20.160 --> 00:53:23.360] Number two, you can optimize products market fit.
[00:53:23.360 --> 00:53:29.920] Number three, you can systematically, even numerically increase product market fit.
[00:53:29.920 --> 00:53:36.560] And number four, you can even have an algorithm write your roadmap for you.
[00:53:36.560 --> 00:53:40.080] And that is a roadmap that is guaranteed to increase product market fit.
[00:53:40.080 --> 00:53:45.760] Now, if that sounds crazy, I would be the first to admit it doesn't seem like that should be true.
[00:53:45.760 --> 00:53:48.320] But go check out that post.
[00:53:48.320 --> 00:53:52.960] I think it is still the most widely shared post on first round review.
[00:53:52.960 --> 00:54:07.920] It's called I think How Superhuman Built an Engine to Find Products Market Fit, or just Google the Superhuman Products Market Fit Engine, and you'll see the algorithm laid out there, fully explained, and why it works.
[00:54:07.920 --> 00:54:19.600] And I'd say the second thing is to get to products market fit, you have to deliberately not act on the feedback of many of your early users.
[00:54:19.920 --> 00:54:27.280] And this is at the same time as listening to people intensely and building what people want, right?
[00:54:27.280 --> 00:54:30.360] That's what we're here to do: to make something that people want.
[00:54:30.680 --> 00:54:32.120] But it can't be all people.
[00:54:29.840 --> 00:54:33.160] It can't be everybody.
[00:54:33.320 --> 00:54:36.280] And the question becomes: how do you listen to them?
[00:54:36.280 --> 00:54:41.640] And then, even of what they say, what do you pay attention to and what don't you?
[00:54:42.280 --> 00:54:45.240] All of that's covered in the product market fit engine.
[00:54:45.560 --> 00:54:51.240] Okay, I gotta follow this thought on algorithmically building your roadmap to increase product markets.
[00:54:51.240 --> 00:54:55.080] They talk about just what that one would do that.
[00:54:55.080 --> 00:54:59.400] Well, I mean, that's really the meat of the engine.
[00:54:59.400 --> 00:55:04.040] So let's see if I can condense it here in a very easy to grok fashion.
[00:55:04.360 --> 00:55:10.360] So let's assume, for the sake of argument, that you can put a number on product market fit.
[00:55:10.360 --> 00:55:11.880] And it turns out you can.
[00:55:11.880 --> 00:55:16.280] Very simply, you're going to ask people, how would you feel if you could no longer use this product?
[00:55:16.280 --> 00:55:17.880] You give them three responses.
[00:55:17.880 --> 00:55:20.120] One of them is very disappointed.
[00:55:20.120 --> 00:55:21.960] The other is somewhat disappointed.
[00:55:21.960 --> 00:55:23.400] And the other is not disappointed.
[00:55:23.400 --> 00:55:26.600] Very disappointed means I would be like devastated.
[00:55:26.600 --> 00:55:29.400] I love this product or I need this product.
[00:55:29.720 --> 00:55:40.120] And what Sean Ellis found, Sean Ellis, if you don't know him, is the guy who coined the term growth hacker and he instrumented, benchmarked this initial question.
[00:55:40.120 --> 00:55:54.120] What he found is that the companies that struggled to grow almost always had less than 40% very disappointed, whereas the companies that grew the fastest almost always had more than 40% very disappointed.
[00:55:54.120 --> 00:56:03.480] And this question, this metric, is way more predictive of success than something, for example, like net promoter score.
[00:56:03.800 --> 00:56:06.680] Okay, so far, so easy.
[00:56:06.680 --> 00:56:09.800] How do we make this number go up?
[00:56:09.800 --> 00:56:14.760] Well, you want more people to be very disappointed without your product.
[00:56:15.440 --> 00:56:24.240] And the trick here is not to act too much on the feedback that the very disappointed people are giving you because they already love your product.
[00:56:24.240 --> 00:56:37.360] Also, not to act at all really on the feedback that the not disappointed people are giving you because they're so far from loving your product that they are essentially a lost cause, but to focus on the segment of the somewhat disappointed people.
[00:56:37.360 --> 00:56:42.800] They kind of love your product, but something, and I would wager something small, is holding them back.
[00:56:42.800 --> 00:56:50.000] So you then divide them into two camps: the camp for whom the main benefit of your product resonates, and the camp for whom it doesn't.
[00:56:50.000 --> 00:56:51.360] And what do I mean by that?
[00:56:51.360 --> 00:56:54.880] Well, you go back to the people who really love your product and you basically ask them why.
[00:56:54.880 --> 00:56:57.520] What is it about my products that you really love?
[00:56:57.520 --> 00:57:05.360] In the early days of Superhuman, it would have been speed and keyboard shortcuts and the overall design aesthetic, as well as the time that we were saving you.
[00:57:06.000 --> 00

Prompt 2: Key Takeaways

Now please extract the key takeaways from the transcript content I provided.

Extract the most important key takeaways from this part of the conversation. Use a single sentence statement (the key takeaway) rather than milquetoast descriptions like "the hosts discuss...". 

Limit the key takeaways to a maximum of 3. The key takeaways should be insightful and knowledge-additive. 

IMPORTANT: Return ONLY valid JSON, no explanations or markdown. Ensure:
- All strings are properly quoted and escaped
- No trailing commas
- All braces and brackets are balanced
Format: {"key_takeaways": ["takeaway 1", "takeaway 2"]}

Prompt 3: Segments

Now identify 2-4 distinct topical segments from this part of the conversation.

For each segment, identify:
- Descriptive title (3-6 words)  
- START timestamp when this topic begins (HH:MM:SS format)
- Double check that the timestamp is accurate - a timestamp will NEVER be greater than the total length of the audio
- Most important Key takeaway from that segment. Key takeaway must be specific and knowledge-additive.
- Brief summary of the discussion

IMPORTANT: The timestamp should mark when the topic/segment STARTS, not a range. Look for topic transitions and conversation shifts.

Return ONLY valid JSON. Ensure all strings are properly quoted, no trailing commas:
{
  "segments": [
    {
      "segment_title": "Topic Discussion", 
      "timestamp": "01:15:30",
      "key_takeaway": "main point from this segment",
      "segment_summary": "brief description of what was discussed"
    }
  ]
}

Timestamp format: HH:MM:SS (e.g., 00:05:30, 01:22:45) marking the START of each segment.

Prompt 4: Media Mentions

Now scan the transcript content I provided for ACTUAL mentions of specific media titles:

Find explicit mentions of:
- Books (with specific titles)
- Movies (with specific titles)  
- TV Shows (with specific titles)
- Music/Songs (with specific titles)

DO NOT include:
- Websites, URLs, or web services
- Other podcasts or podcast names

IMPORTANT: 
- Only include items explicitly mentioned by name. Do not invent titles.
- Valid categories are: "Book", "Movie", "TV Show", "Music"
- Include the exact phrase where each item was mentioned
- Find the nearest proximate timestamp where it appears in the conversation
- THE TIMESTAMP OF THE MEDIA MENTION IS IMPORTANT - DO NOT INVENT TIMESTAMPS AND DO NOT MISATTRIBUTE TIMESTAMPS
- Double check that the timestamp is accurate - a timestamp will NEVER be greater than the total length of the audio
- Timestamps are given as ranges, e.g. 01:13:42.520 --> 01:13:46.720. Use the EARLIER of the 2 timestamps in the range.

Return ONLY valid JSON. Ensure all strings are properly quoted and escaped, no trailing commas:
{
  "media_mentions": [
    {
      "title": "Exact Title as Mentioned",
      "category": "Book",
      "author_artist": "N/A",
      "context": "Brief context of why it was mentioned",
      "context_phrase": "The exact sentence or phrase where it was mentioned",
      "timestamp": "estimated time like 01:15:30"
    }
  ]
}

If no media is mentioned, return: {"media_mentions": []}

Prompt 5: Context Setup

You are an expert data extractor tasked with analyzing a podcast transcript. 
I will provide you with part 2 of 2 from a podcast transcript. 
I will then ask you to extract different types of information from this content in subsequent messages. Please confirm you have received and understood the transcript content.

Transcript section:
ound, Sean Ellis, if you don't know him, is the guy who coined the term growth hacker and he instrumented, benchmarked this initial question.
[00:55:40.120 --> 00:55:54.120] What he found is that the companies that struggled to grow almost always had less than 40% very disappointed, whereas the companies that grew the fastest almost always had more than 40% very disappointed.
[00:55:54.120 --> 00:56:03.480] And this question, this metric, is way more predictive of success than something, for example, like net promoter score.
[00:56:03.800 --> 00:56:06.680] Okay, so far, so easy.
[00:56:06.680 --> 00:56:09.800] How do we make this number go up?
[00:56:09.800 --> 00:56:14.760] Well, you want more people to be very disappointed without your product.
[00:56:15.440 --> 00:56:24.240] And the trick here is not to act too much on the feedback that the very disappointed people are giving you because they already love your product.
[00:56:24.240 --> 00:56:37.360] Also, not to act at all really on the feedback that the not disappointed people are giving you because they're so far from loving your product that they are essentially a lost cause, but to focus on the segment of the somewhat disappointed people.
[00:56:37.360 --> 00:56:42.800] They kind of love your product, but something, and I would wager something small, is holding them back.
[00:56:42.800 --> 00:56:50.000] So you then divide them into two camps: the camp for whom the main benefit of your product resonates, and the camp for whom it doesn't.
[00:56:50.000 --> 00:56:51.360] And what do I mean by that?
[00:56:51.360 --> 00:56:54.880] Well, you go back to the people who really love your product and you basically ask them why.
[00:56:54.880 --> 00:56:57.520] What is it about my products that you really love?
[00:56:57.520 --> 00:57:05.360] In the early days of Superhuman, it would have been speed and keyboard shortcuts and the overall design aesthetic, as well as the time that we were saving you.
[00:57:06.000 --> 00:57:15.360] You then go back to the somewhat disappointed users, and in the superhuman example, I would simply ask, wait, do you like superhuman because of its speed or for something else?
[00:57:15.360 --> 00:57:36.560] And if it's something else, well, and this is hard to do, but politely disregard those people and their feedback, because even if you built everything that they asked for, they're still pulling you in a different direction, and the thing that they like the most from your product isn't actually what the people who en masse love it the most for is.
[00:57:37.200 --> 00:57:48.720] So you have then articulated the sub-segment of the sub-segment that it makes sense to pay attention to, and there's another question in the engine to figure out what they don't like about the product.
[00:57:48.720 --> 00:57:58.480] Now you have a list of things people love, you have a list of things people don't love, and you can work down that list to make the product market fit score go up.
[00:57:58.480 --> 00:58:13.640] And basically, at the start of every planning cycle, I advise spending half your time doubling down on what people really love and half your time systematically overcoming the objections of the somewhat disappointed users, but specifically those for whom the main benefit resonates.
[00:58:13.960 --> 00:58:15.720] That was an excellent summary.
[00:58:15.720 --> 00:58:18.440] I know I said we wouldn't spend a ton of time here, but I'm really glad we did.
[00:58:18.440 --> 00:58:19.560] That was really helpful.
[00:58:19.560 --> 00:58:20.280] Let me ask you this.
[00:58:20.280 --> 00:58:21.880] I know you used this initially in the early days.
[00:58:21.880 --> 00:58:24.280] Are you still operating this way in some form?
[00:58:24.600 --> 00:58:31.000] We don't run the engine as is for superhuman as a whole.
[00:58:31.000 --> 00:58:35.320] There are enough subcomponents of superhuman now that are almost individual products.
[00:58:35.320 --> 00:58:43.160] For example, superhuman for sales, our multiplayer and collaboration features, how we think about the enterprise, AI is its whole thing.
[00:58:43.160 --> 00:58:46.600] But we do sometimes run it on those individual pieces.
[00:58:46.600 --> 00:58:53.720] For example, we'll ask a salesperson the product market fit engine as it relates to superhuman for sales.
[00:58:53.720 --> 00:58:59.320] And as we think about starting new products, we would absolutely deploy the product market fit engine.
[00:58:59.320 --> 00:58:59.880] Awesome.
[00:58:59.880 --> 00:59:04.360] And the way you ask this question is an in-product interstitial sort of survey pop-up thing?
[00:59:04.600 --> 00:59:06.200] You can do it however you want.
[00:59:06.200 --> 00:59:10.760] The way Sean initially benchmarked the number was via email surveys.
[00:59:10.760 --> 00:59:13.240] I think email surveys work just fine.
[00:59:13.240 --> 00:59:23.240] The key thing is, and this applies to any survey methodology, if you're going to change the method of surveying, all of your old numbers are invalidated.
[00:59:23.240 --> 00:59:25.320] So it's just a new baseline going forwards.
[00:59:25.320 --> 00:59:25.720] Got it.
[00:59:25.720 --> 00:59:28.680] And we had Sean on the podcast, and he describes this method in detail.
[00:59:28.680 --> 00:59:31.160] So folks want to explore this John Ellis test.
[00:59:31.480 --> 00:59:32.360] Listen to that podcast.
[00:59:32.440 --> 00:59:33.320] We'll link to it.
[00:59:33.320 --> 00:59:39.000] Okay, next topic that I'm excited to get your take on is game design versus gamification.
[00:59:39.000 --> 00:59:43.080] This is one of the more unique ways you think about designing product.
[00:59:43.080 --> 00:59:48.160] And when people hear you talk about this, they think it's like, oh, gamification, making things like games, oh, Zynga, Farmville.
[00:59:48.160 --> 00:59:49.120] I don't want to do that.
[00:59:44.840 --> 00:59:55.760] But you actually have a really different perspective on how to make, why you need to think about game design as you design products.
[00:59:55.760 --> 00:59:57.520] Talk about your insights there.
[00:59:57.840 --> 01:00:09.440] Yeah, well, I strongly believe that we should make business software like we make games because when we make products like we make games, people find them fun.
[01:00:09.440 --> 01:00:10.880] They tell their friends.
[01:00:10.880 --> 01:00:12.240] They fall in love with them.
[01:00:12.240 --> 01:00:18.320] It's another way actually of backing into where we opened this conversation, which is you're making a brand.
[01:00:18.320 --> 01:00:20.240] You're giving reason for word of mouth.
[01:00:20.240 --> 01:00:24.560] It's actually an altogether different kind of product development.
[01:00:24.560 --> 01:00:26.080] So how do we do this?
[01:00:26.080 --> 01:00:28.560] Well, as you've said, it's not gamification.
[01:00:28.640 --> 01:00:30.160] That doesn't work.
[01:00:30.160 --> 01:00:33.920] Game design works, but game design is not gamification.
[01:00:33.920 --> 01:00:40.400] It's not, for example, simply taking your product and adding points, levels, trophies, or badges.
[01:00:40.400 --> 01:00:46.640] And to understand why gamification does not work, we actually have to start with human motivation.
[01:00:46.640 --> 01:00:52.640] And there's a very interesting study from Stanford, I think, that demonstrates the difference perfectly.
[01:00:52.640 --> 01:00:58.880] In the 1970s, these Stanford researchers recruited children who were aged three to four years old.
[01:00:58.880 --> 01:01:02.640] And all of these kids were generally pre-interested in drawing.
[01:01:02.640 --> 01:01:07.600] Some kids were told they would get a reward, a certificate, with a gold seal and a ribbon.
[01:01:07.600 --> 01:01:12.640] And some kids were not told about any reward and they did not even expect one or didn't know of one.
[01:01:12.640 --> 01:01:18.160] Now, each child was then invited into a separate room to draw for six minutes.
[01:01:18.160 --> 01:01:21.280] And afterwards, they would either get the reward or not.
[01:01:21.600 --> 01:01:29.120] And over the next few days, the children were observed to see how much they would continue to draw by themselves.
[01:01:29.120 --> 01:01:35.400] So the children with no reward, they spent 17% of their time drawing.
[01:01:35.720 --> 01:01:42.760] But the children who expected a reward, sadly, they only spent 8% of their time drawing.
[01:01:42.760 --> 01:01:46.840] The very presence of a reward halved their motivation.
[01:01:46.840 --> 01:01:48.120] So what's happening?
[01:01:48.120 --> 01:01:54.040] What's happening here is researchers differentiate intrinsic motivation and extrinsic motivation.
[01:01:54.040 --> 01:01:59.160] With intrinsic motivation, we do things because they are inherently interesting and satisfying.
[01:01:59.160 --> 01:02:04.760] And with extrinsic motivation, we do things to earn rewards and to achieve external goals.
[01:02:04.760 --> 01:02:09.720] And that's the problem with rewards, is they just massively undermine intrinsic motivation.
[01:02:09.720 --> 01:02:11.880] And that's why gamification doesn't work.
[01:02:11.880 --> 01:02:18.920] And when gamification does work, it's because the underlying experience was already designed like a game.
[01:02:19.080 --> 01:02:21.880] What makes something, I guess, like a game?
[01:02:21.880 --> 01:02:26.360] I know Superhuman is really good at this, of just like your inbox zero quest that you're on.
[01:02:26.360 --> 01:02:29.080] I guess just to make that a little more real, what is game design?
[01:02:29.080 --> 01:02:29.880] What does that mean to you?
[01:02:29.880 --> 01:02:31.960] Like, what makes it feel like a game?
[01:02:31.960 --> 01:02:39.240] Well, many folks don't know this, but before I was a founder, you can probably tell, I was actually a professionally a game designer.
[01:02:39.240 --> 01:02:43.400] And as it turns out, there is no unifying theory of game design.
[01:02:43.400 --> 01:02:51.400] To create games, what we need to do is draw upon the arts and the science of psychology, mathematics, storytelling, interaction design.
[01:02:51.400 --> 01:02:57.320] And at Superhuman, we've identified five key areas that we really care about.
[01:02:57.320 --> 01:03:01.400] Goals, emotions, toys, controls, and flow.
[01:03:01.400 --> 01:03:05.240] And across these, we've identified many principles of game design.
[01:03:05.240 --> 01:03:12.360] And one example principle would be: make fun toys and then combine those into games.
[01:03:12.360 --> 01:03:16.960] So, a question I like to ask is, are toys the same as games?
[01:03:17.120 --> 01:03:18.640] They do seem different.
[01:03:14.520 --> 01:03:23.840] For example, we play with toys, but we play games.
[01:03:23.840 --> 01:03:27.120] A ball is a toy, but football is a game.
[01:03:27.120 --> 01:03:31.360] And as it turns out, the best games are constructed out of toys.
[01:03:31.360 --> 01:03:31.920] Why?
[01:03:31.920 --> 01:03:36.240] Because then they are fun on both levels: the toy and the game itself.
[01:03:36.240 --> 01:03:42.880] So, for example, in Superhuman, one of our favorite toys is the time autocompleter.
[01:03:42.880 --> 01:03:48.880] If you use Superhuman, this is the thing that appears when you hit H, when you snooze or set reminders on emails.
[01:03:48.880 --> 01:03:50.480] You can type whatever you want.
[01:03:50.480 --> 01:03:53.520] It can be gibberish, and it does its best to understand you.
[01:03:53.520 --> 01:03:59.760] For example, if you type in 2D, that becomes two days, 3H is three hours, 1MO is one month.
[01:03:59.760 --> 01:04:06.160] And the Time Autocompleter is fun because it indulges your playful exploration.
[01:04:06.160 --> 01:04:11.200] In onboardings, it wasn't long before I saw people asking, what can it do?
[01:04:11.200 --> 01:04:12.080] Where does it break?
[01:04:12.080 --> 01:04:13.280] How does it work?
[01:04:13.280 --> 01:04:16.480] What happens if I keep on typing in a series of tens?
[01:04:16.480 --> 01:04:19.120] Well, it turns out that's October the 10th at 10:10 p.m.
[01:04:19.440 --> 01:04:21.040] Or how about the series of twos?
[01:04:21.040 --> 01:04:24.640] Well, that's February the 2nd, 2022 at 2 p.m.
[01:04:24.960 --> 01:04:33.520] And then you start trying more complex inputs like in a fortnight and a day, and that works, which is a pleasant surprise.
[01:04:33.520 --> 01:04:38.400] And it's not long before you find more pleasant surprises, like time zone math happens without you thinking about it.
[01:04:38.400 --> 01:04:39.760] You can just type in 8 a.m.
[01:04:39.920 --> 01:04:42.080] in Tokyo, and it turns out that's 8 p.m.
[01:04:42.160 --> 01:04:45.280] Eastern time, and you no longer have to do the time zone math.
[01:04:45.280 --> 01:04:52.320] And then most people were really delighted to find out that if you really want, you can snooze emails until never.
[01:04:52.320 --> 01:04:55.040] I.e., you can literally type in never and the email will never come back.
[01:04:55.040 --> 01:04:59.080] And it had like a little shrug emoji at the same time.
[01:04:59.400 --> 01:05:02.520] So, you know, is this toy going to win awards?
[01:04:58.800 --> 01:05:02.920] Nope.
[01:05:03.240 --> 01:05:04.680] But is it fun?
[01:05:04.680 --> 01:05:06.680] Actually, surprisingly, yes.
[01:05:06.680 --> 01:05:11.720] So what I would encourage people to do is think about the features of their product.
[01:05:11.720 --> 01:05:15.080] Do those features indulge playful exploration?
[01:05:15.080 --> 01:05:17.640] Are they fun, even without a goal?
[01:05:17.640 --> 01:05:21.160] And do they elicit moments of pleasant surprise?
[01:05:21.160 --> 01:05:27.960] If so, you have a toy and you can combine that with other toys and actually start to build a game.
[01:05:28.280 --> 01:05:36.520] If people were to listen to this segment of the podcast, they would never guess we're talking about B2B software and email, which I love.
[01:05:36.840 --> 01:05:40.520] Let's talk about pricing strategy and your approach to pricing.
[01:05:40.520 --> 01:05:49.080] Another very contrarian approach that you guys took where you charge $30 a month for email that was free, that people don't need to pay for anywhere.
[01:05:49.080 --> 01:05:49.960] And it's worked.
[01:05:49.960 --> 01:05:51.880] And now a lot of companies are thinking of it this way.
[01:05:51.880 --> 01:05:54.520] You've even raised your prices recently.
[01:05:54.520 --> 01:05:57.960] What have you learned about pricing strategy that you think might be helpful to folks?
[01:05:58.280 --> 01:06:06.520] I always say the same thing when it comes to pricing, which is before you figure out pricing, you must first figure out positioning.
[01:06:06.520 --> 01:06:10.760] And Superhuman is the best email tool on the market.
[01:06:10.760 --> 01:06:13.400] We fortunately have the metrics to show this.
[01:06:13.400 --> 01:06:23.160] One of the cool things about selling an email tool is you can compare the 30 days prior to using Superhuman to the 30 days after, or the year before to the year after.
[01:06:23.480 --> 01:06:25.400] And we do that, obviously.
[01:06:25.400 --> 01:06:35.880] We're able to show that people get through their email twice as fast with Superhuman, that they respond one to two days faster, and that they save four hours or more every single week.
[01:06:35.880 --> 01:06:44.960] Because of that, we're very confident in saying that Superhuman is the best email tool on the market and that we're building it for high-performing teams and high-performing individuals.
[01:06:44.520 --> 01:06:47.840] In other words, we serve the high end of the market.
[01:06:48.320 --> 01:06:52.720] Once you understand your positioning, you can then move on to pricing.
[01:06:52.720 --> 01:06:59.600] And one of the best books on this is a book called Monetizing Innovation by Madhavan Ramanjam.
[01:06:59.600 --> 01:07:02.720] And Madhavan covers a lot of ways to develop pricing.
[01:07:02.720 --> 01:07:08.240] We used one of the easiest methods, which is the Van Westendorp price sensitivity research.
[01:07:08.240 --> 01:07:15.600] And in the early years, we asked, I think it was around 100 of our earliest users the following four questions.
[01:07:15.600 --> 01:07:21.440] Number one, at what price would you consider Superhuman to be so expensive that you would not consider buying it?
[01:07:21.440 --> 01:07:28.480] Number two, at what price would you consider superhuman to be priced so low that you'd be worried about its quality and you wouldn't buy it?
[01:07:28.480 --> 01:07:38.800] At number three, what price would you consider superhuman to be starting to get expensive so that it's not out of the question, but you'd have to give some thought to buying it?
[01:07:38.800 --> 01:07:44.960] And number four, at what price would you consider superhuman to be a bargain, a great buy for the money?
[01:07:44.960 --> 01:07:50.560] Now, most startups orient around price point number four.
[01:07:50.560 --> 01:07:55.600] This is especially true for greenfield opportunities, marketplaces.
[01:07:55.600 --> 01:08:05.760] You've got to set the transaction value around price point four, basically when you want as many people to sign up as is humanly possible at the top of the funnel.
[01:08:06.080 --> 01:08:12.960] But the price point that supports our best-in-class, best-in-cate position is actually the third one.
[01:08:12.960 --> 01:08:21.200] It starts to feel expensive, but then you sit down and you think about the time that you spend an email, the ROI, and you still buy it anyway.
[01:08:21.200 --> 01:08:27.520] And it turns out that the median answer for the third question was $30 per month, and that's how we picked our price.
[01:08:27.520 --> 01:08:32.280] And once we picked our price, we then do a quick gut check on market size.
[01:08:32.280 --> 01:08:40.520] You know, for example, we're a venture scale company, but at the time, the question that we had to ask is, could we grow into a billion-dollar valuation?
[01:08:40.520 --> 01:08:45.080] Well, let's assume that at that point, our valuation is 10 times our ARR.
[01:08:45.080 --> 01:08:47.480] So our ARR would have to be $100 million.
[01:08:47.480 --> 01:08:51.080] Well, that would be 300,000 subscribers at $30 per month.
[01:08:51.080 --> 01:08:55.880] And that is conservatively assuming no other ways to increase ARPU.
[01:08:56.040 --> 01:08:57.240] You mentioned price increase.
[01:08:57.240 --> 01:08:58.680] You can also go at market.
[01:08:58.680 --> 01:09:01.160] You can sell new products and so on.
[01:09:01.320 --> 01:09:09.240] We asked ourselves, without those tricks, do we think we can get to hundreds of thousands of subscribers?
[01:09:09.240 --> 01:09:11.240] And we answered emphatically yes.
[01:09:11.240 --> 01:09:13.560] And so we went ahead with that price.
[01:09:13.560 --> 01:09:14.040] Okay.
[01:09:14.040 --> 01:09:16.760] There's a couple more things I want to chat about in the time that we have.
[01:09:16.760 --> 01:09:18.280] And then I know you have to run.
[01:09:18.280 --> 01:09:20.520] One is around AI and the work you guys are doing there.
[01:09:20.520 --> 01:09:21.720] I know that's been a big unlock.
[01:09:21.720 --> 01:09:24.520] And then two, the stuff you're doing in enterprise.
[01:09:24.520 --> 01:09:29.080] And then if we have time, there's a question I want to ask that I think is a really interesting way you guys operate.
[01:09:29.080 --> 01:09:30.760] So let's talk about AI first.
[01:09:30.760 --> 01:09:35.560] It feels like there's this being in the right place at the right time.
[01:09:35.560 --> 01:09:43.000] It feels like you guys, like, we've been building this for a while, and then AI just unlocked another stage in what you're able to do with email.
[01:09:43.000 --> 01:09:52.200] I guess just talk about what you've done and how you think about AI integrating into what you're doing, how it's enabled you to kind of take off again.
[01:09:52.520 --> 01:09:59.240] It's true that sometimes startups boil down to being in the right place at the right time.
[01:09:59.240 --> 01:10:03.720] And we actually had a massive AI launch recently, about two weeks ago.
[01:10:03.720 --> 01:10:08.680] But even before then, we had multiple flagship AI features.
[01:10:08.680 --> 01:10:14.520] Our first AI feature was write with AI, jot down a few words, and we'll turn them into a fully written email.
[01:10:14.520 --> 01:10:17.440] We actually match the voice and tone in the emails you've already sent.
[01:10:17.440 --> 01:10:24.000] So unlike Copilot, unlike Gemini, unlike basically every other email app, the email sounds like you.
[01:10:24.320 --> 01:10:28.640] And this AI feature is way more popular than I expected it to be.
[01:10:28.640 --> 01:10:33.760] On average today, users are using it 37 times per week.
[01:10:33.760 --> 01:10:40.320] Number two, our next AI feature was auto-summarize, which shows a one-line summary above every conversation.
[01:10:40.320 --> 01:10:43.120] And as new emails arrive, it updates instantly.
[01:10:43.120 --> 01:10:46.160] Again, unlike Copilot and Gemini, it's pre-computed.
[01:10:46.160 --> 01:10:51.600] One of the things we do is we go above and beyond to make these features really premium and feel amazing.
[01:10:51.600 --> 01:10:56.080] The next AI feature after that was instant reply.
[01:10:56.400 --> 01:11:02.240] Imagine waking up to an inbox where every email already has a draft reply.
[01:11:02.240 --> 01:11:04.720] You would simply edit and then send.
[01:11:04.720 --> 01:11:08.000] And sometimes you wouldn't even need to edit.
[01:11:08.000 --> 01:11:19.680] And I can share, because we just finished this analysis, that over 2024, the percentage of emails that are AI written and sent with Superhuman has grown four times just in one year.
[01:11:20.480 --> 01:11:25.200] Then if I remember correctly, the feature after that was Ask AI.
[01:11:25.200 --> 01:11:34.960] Email, of course, is this treasure trove of critical information, things like project statuses, customer communication, meeting updates, deal execution, and so much more.
[01:11:34.960 --> 01:11:40.000] And for over 40 years, we've had to rely on what we hilariously call search.
[01:11:40.000 --> 01:11:47.120] You have to remember senders, guess keywords, scan subject lines, and now you can just ask, where is the Q1 off-site?
[01:11:47.120 --> 01:11:49.680] Or what are my flight details?
[01:11:49.680 --> 01:11:56.880] Or what is the top five most positive customer responses to the Ask AI launch?
[01:11:56.880 --> 01:12:08.920] A task, by the way, which previously used to take me 20 or 30 minutes to read through all the emails and then create that report, now happening in less than five seconds.
[01:12:08.920 --> 01:12:13.080] And recently, we, like I said, announced our biggest evolution yet.
[01:12:13.080 --> 01:12:15.800] And Superhuman AI is constantly helping you.
[01:12:15.800 --> 01:12:17.400] It's organizing your inbox.
[01:12:17.400 --> 01:12:19.960] It's also making sure you never drop the ball.
[01:12:19.960 --> 01:12:23.320] So we have things that we call auto labels.
[01:12:23.320 --> 01:12:29.240] You can now write a short prompt like job applications or requests to review work.
[01:12:29.560 --> 01:12:36.440] And you can then immediately see when emails match that prompt when people apply for a job or they ask you to review work.
[01:12:36.440 --> 01:12:42.760] With auto reminders, if your email needs a response, Superhuman will now automatically set a reminder.
[01:12:42.760 --> 01:12:44.520] You don't have to remember to do that.
[01:12:44.520 --> 01:12:46.360] Then you'll never drop the ball again.
[01:12:46.360 --> 01:12:49.160] All you need to do is hit send.
[01:12:49.160 --> 01:12:59.560] With auto drafts, Superhuman will now automatically draft your follow-up emails for you and will soon be drafting replies to basically every email that needs a response.
[01:12:59.560 --> 01:13:09.080] And finally, with what we call workflows, you can now turn email into repeatable, automated workflows.
[01:13:09.080 --> 01:13:19.320] For example, I often get emails from people who are interested in working at Superhuman, and I would normally reply to that candidate, and I would let them know that the team will take a look.
[01:13:19.320 --> 01:13:28.120] I'll then forward the original message, including any resume or any letter, to our head of people in operations and ask her to reach out if interested.
[01:13:28.120 --> 01:13:32.120] With workflows, I can now automate this entire process.
[01:13:32.120 --> 01:13:37.160] And you can imagine sort of creating a little flowchart of what has to happen.
[01:13:37.480 --> 01:13:45.280] Not only does that save a huge amount of time, with workflows, you don't even have to be in your inbox.
[01:13:44.760 --> 01:13:47.600] In fact, you don't even have to be working.
[01:13:47.920 --> 01:13:53.360] You could be on vacation while superhuman AI is working for you.
[01:13:53.680 --> 01:13:55.440] This sounds like product market fit to me.
[01:13:55.440 --> 01:13:56.800] This all sounds wonderful.
[01:13:56.800 --> 01:13:58.080] Like it just makes sense.
[01:13:58.080 --> 01:14:06.720] This is the stuff we've been promised: our underwater cities and flying cars and then just email that just works magically and replies for us and all these things.
[01:14:06.960 --> 01:14:08.720] So I love all these things you're doing.
[01:14:08.720 --> 01:14:25.120] For folks that are building with AI, I'm curious to just, what's maybe been the biggest surprise, either good or bad, building so deeply on top of AI models that you think might be helpful for folks to just like, watch out for this or, hey, check this out.
[01:14:25.440 --> 01:14:36.400] I think for me, the biggest surprise has been how unpredictable the user love has been in terms of what they love and what they don't love.
[01:14:36.400 --> 01:14:38.880] For example, Write with AI.
[01:14:40.480 --> 01:14:42.240] This sounds like a commodity feature.
[01:14:42.240 --> 01:14:43.840] And on surface level, it is.
[01:14:43.840 --> 01:14:47.920] Every email app, every writing surface has a Write with AI feature in.
[01:14:47.920 --> 01:14:50.240] I would wager ours is the best at emails.
[01:14:50.240 --> 01:14:52.480] And surprisingly, that's what we do.
[01:14:53.120 --> 01:15:00.320] But the surprising thing was just how much people love it and how often it gets used.
[01:15:00.320 --> 01:15:06.960] 37 times per user per week is still mind-blowing to me.
[01:15:07.600 --> 01:15:08.960] I had not expected that.
[01:15:08.960 --> 01:15:11.040] So that's the most surprising thing.
[01:15:11.040 --> 01:15:20.960] And on the flip side, there were certain AI features where I did expect a ton of usage, but we didn't quite get the usage that we were perhaps hoping for.
[01:15:20.960 --> 01:15:30.920] And hopefully, I'm not an AI Kramer, but basically, everything I thought would work out well, people use it less than I thought they did, and everything where I was like, I don't know, but let's build the thing.
[01:15:29.600 --> 01:15:32.120] People love that.
[01:15:32.360 --> 01:15:37.480] So maybe I should just create an anti-me to do AI roadmapping.
[01:15:37.800 --> 01:15:39.320] That's in a simple agent right there.
[01:15:39.320 --> 01:15:41.240] Whatever Rahul says, do the opposite.
[01:15:41.240 --> 01:15:41.720] Yeah.
[01:15:42.040 --> 01:15:44.360] Okay, another, maybe a last topic.
[01:15:44.360 --> 01:15:47.080] I know that you guys are starting to move into the enterprise.
[01:15:47.080 --> 01:15:52.040] When people think of superhuman, they think of just, you know, it's like consumer-y, it's like for people.
[01:15:52.040 --> 01:15:56.040] And you guys are doing a lot of work to make it a B2B enterprise product.
[01:15:56.040 --> 01:16:06.600] For founders, maybe that are starting to think about this, transitioning from PLG to sales-led and B2B enterprise-y, what have you learned about just what it takes to get to that point?
[01:16:06.600 --> 01:16:10.280] And just what does that sales motion look like for you guys?
[01:16:10.600 --> 01:16:18.920] In some ways, it's very like selling to prosumers, except these users are not coming from Gmail where prosumers would normally come from.
[01:16:18.920 --> 01:16:20.440] They're coming from Outlook.
[01:16:20.440 --> 01:16:24.760] And Outlook users have very different expectations to Gmail users.
[01:16:24.760 --> 01:16:36.920] For example, Outlook users expect their email app to also be a fully featured calendar app, whereas Gmail users are happy with those two things being entirely different.
[01:16:36.920 --> 01:16:44.200] So as a result, we've invested in calendar very heavily and we continue to do so.
[01:16:44.200 --> 01:16:47.800] And there's only so much I can say that, but it's pretty exciting.
[01:16:50.600 --> 01:17:03.960] Outlook users are also used to certain safeguards, like if you've used Outlook in an enterprise, warnings when a recipient is external to your domain or what Outlook users might know as sensitivity labels.
[01:17:03.960 --> 01:17:09.720] And as a result, we've built support for external recipient indicators and sensitivity labels.
[01:17:09.720 --> 01:17:15.000] But in some ways, it's very different to selling to prosumers because there are other stakeholders involved.
[01:17:15.040 --> 01:17:22.240] For example, we've built support for enterprise mobile management by implementing Microsoft InTune.
[01:17:22.240 --> 01:17:28.880] We recently sold one of the big three strategy consulting firms, which is super exciting.
[01:17:28.880 --> 01:17:36.320] I can't say which one, but they love Superhuman and they have thousands of people internally using Superhuman.
[01:17:36.320 --> 01:17:43.520] But we, and this is after a year, they've been piloting for a year and then accelerating over the last few months.
[01:17:43.520 --> 01:17:59.600] We only just got them the mobile app, believe it or not, because at an enterprise like that, there are significant controls on what a allowed, compliant mobile app can and cannot do.
[01:17:59.600 --> 01:18:10.160] For example, IT needs to be able to control which apps can save attachments or which apps you can copy and paste text into from email.
[01:18:10.160 --> 01:18:13.680] And for many enterprises, those controls are super important.
[01:18:14.000 --> 01:18:14.400] Wow.
[01:18:14.400 --> 01:18:14.720] Okay.
[01:18:14.720 --> 01:18:20.960] So it sounds like essentially just building all these features that large companies need is kind of the road you're on right now.
[01:18:21.280 --> 01:18:21.760] Exactly.
[01:18:21.760 --> 01:18:29.120] And there's two stakeholders: there's the users, which are actually quite different because they're Outlook users, and Calendar is one of the main ways that manifests.
[01:18:29.120 --> 01:18:30.800] And there's a whole bunch of other stakeholders.
[01:18:30.800 --> 01:18:33.920] IT is one of them, but there are others as well.
[01:18:33.920 --> 01:18:42.240] For example, companies this large have workplace management groups who want to see analytics of how people are working, how they can make their teams more efficient.
[01:18:42.240 --> 01:18:46.960] And so it truly is a multi-threaded sale with multiple stakeholders.
[01:18:47.440 --> 01:18:55.920] We had a linear on the podcast, the head of product from Linear on the podcast, Non, and he actually, I don't know if you heard that episode, but he talks about how they decide what to prioritize.
[01:18:55.920 --> 01:19:02.680] The thing they never build is middle managers needing to track how their reports are doing and things like that.
[01:19:02.680 --> 01:19:06.440] So that's an interesting opportunity for you guys, maybe, to cut stuff.
[01:18:59.680 --> 01:19:06.840] I don't know.
[01:19:07.080 --> 01:19:08.840] Anyway, I want to end on one more nugget.
[01:19:08.840 --> 01:19:10.440] Okay, I'm glad we have time for this.
[01:19:10.440 --> 01:19:15.560] So you shared that you have this system internally at Superhuman for making decisions.
[01:19:15.560 --> 01:19:19.080] You call it single decisive reason.
[01:19:19.800 --> 01:19:20.840] SDR.
[01:19:20.840 --> 01:19:21.960] What is that?
[01:19:22.600 --> 01:19:30.200] SDR is a thinking tool that I picked up from Reid Hoffman during my time at LinkedIn.
[01:19:30.200 --> 01:19:39.480] And the idea here is that for important decisions, you should be able to identify one, one reason that on its own supports the decision.
[01:19:39.480 --> 01:19:48.200] And it's based on the observation that all too often we rely on a collection of weak reasons to justify decisions.
[01:19:48.200 --> 01:19:50.120] And it's very, very easy to do this.
[01:19:50.120 --> 01:19:52.440] Imagine you're contemplating a decision.
[01:19:52.440 --> 01:19:55.080] You write a list of the pros and the cons.
[01:19:55.080 --> 01:19:58.840] There are three pros, but let's say there are 10 or 15 cons.
[01:19:59.160 --> 01:20:08.920] The sheer number of cons, the efforts of thinking them through, the time it took to write them down, is going to affect you, consciously or worse, subconsciously.
[01:20:08.920 --> 01:20:17.080] And this is especially true I've seen in group settings, which just in general are a little bit more risk-averse and a little bit more consensus-driven.
[01:20:17.080 --> 01:20:29.240] So whenever anyone is making a decision, and they bring that decision to me, and they say, well, we want to do this because of XYZ, and there are multiple reasons, I've asked them, what's the SDR?
[01:20:29.560 --> 01:20:32.440] What's the single decisive reason?
[01:20:32.440 --> 01:20:37.800] If they can't yet isolate it, that tells me they haven't yet figured out why they want to make the decision.
[01:20:37.800 --> 01:20:39.480] It doesn't mean the decision is wrong.
[01:20:39.480 --> 01:20:44.680] It just means that they haven't figured out the singular reason why we should do the thing.
[01:20:44.800 --> 01:20:50.800] They can then go through their list of reasons and ask, is this alone enough to support this decision?
[01:20:50.800 --> 01:20:54.080] Meaning, if this was true and all the other things were not true, would I still do it?
[01:20:54.080 --> 01:20:57.520] And sometimes we still do, but actually sometimes we don't.
[01:20:57.520 --> 01:21:11.040] And we realize that a collection of weak reasons alone means that, for example, the outcome is less likely than we thought it was, or it was hiding a really strong reason on the other side of the decision.
[01:21:11.360 --> 01:21:12.480] That is very cool.
[01:21:12.480 --> 01:21:20.320] So this is just when someone comes to you with a decision, the way you use this idea is you ask them, what's the single decisive reason?
[01:21:20.640 --> 01:21:21.840] Pretty much, yeah.
[01:21:21.840 --> 01:21:26.720] And what they can't do, I mean, obviously this happens, people are human and natural.
[01:21:26.720 --> 01:21:30.560] They'll usually start mentioning three or four things, and that's fine.
[01:21:30.560 --> 01:21:37.120] And then I will say, okay, but if only one of those was true and you're still advocating for this decision, what is it?
[01:21:37.440 --> 01:21:39.840] And I think that's just a bar for a good decision.
[01:21:40.320 --> 01:21:41.600] Why is that so important?
[01:21:41.600 --> 01:21:50.160] Because you found that just like a bunch of low-quality reasons just don't add up to a good reason to do something.
[01:21:50.480 --> 01:21:53.520] Multiple reasons, which is ironic.
[01:21:53.520 --> 01:21:57.040] But that's my SDR for why SDRs work, which is yes.
[01:21:57.360 --> 01:22:04.960] Multiple low-quality reasons rarely add up to a high-quality reason to do something.
[01:22:04.960 --> 01:22:09.760] But there are also other things as well, which is any decision you take has an opportunity cost.
[01:22:09.760 --> 01:22:12.960] Any feature you build is another feature that you didn't build.
[01:22:12.960 --> 01:22:20.240] And if we're going to build this for a collection of weak reasons, whereas we could build that for one strong reason, I'd much rather build that for one strong reason.
[01:22:20.240 --> 01:22:24.800] Now, this is all other things being equal, and these things often end up being quite complicated.
[01:22:24.800 --> 01:22:27.200] But you can apply SDR all the way down.
[01:22:27.200 --> 01:22:28.320] I mean, you just did that to me.
[01:22:28.320 --> 01:22:30.040] What's my SDR for SDR?
[01:22:31.000 --> 01:22:32.520] There we go.
[01:22:29.680 --> 01:22:36.840] Rahul, is there anything that we haven't covered that you wanted to cover?
[01:22:37.000 --> 01:22:43.160] Is there any last piece of wisdom you want to leave listeners with before we let you go?
[01:22:43.800 --> 01:22:45.320] I feel good.
[01:22:45.320 --> 01:22:47.720] So I think we covered a lot.
[01:22:47.720 --> 01:22:49.720] Thank you for asking amazing questions.
[01:22:49.720 --> 01:22:50.920] This is really fun.
[01:22:50.920 --> 01:22:51.800] This was incredible.
[01:22:51.800 --> 01:22:55.240] Okay, so let me just ask you this then: where can folks find you online?
[01:22:55.240 --> 01:22:57.000] Where can they check out Superhuman?
[01:22:57.000 --> 01:22:59.640] What should they know before they try it out?
[01:22:59.640 --> 01:23:01.880] And then just how can listeners be useful to you?
[01:23:02.200 --> 01:23:05.400] If you want to find me online, I'm generally on X.
[01:23:05.400 --> 01:23:10.600] That is X.com/slash Rahul Vora, R-A-H-U-L-V-O-H-R-A.
[01:23:10.600 --> 01:23:11.880] And my DMs are open.
[01:23:11.880 --> 01:23:13.480] So feel free to ping me.
[01:23:13.480 --> 01:23:16.200] If you're going to do that, I would suggest also emailing me.
[01:23:16.200 --> 01:23:20.120] That's rahul at superhuman.com.
[01:23:20.440 --> 01:23:22.920] And hopefully I'll see your message soon.
[01:23:22.920 --> 01:23:27.480] If you haven't tried Superhuman, then gosh, what are you doing?
[01:23:27.480 --> 01:23:33.880] This is my call to you to do so because your time is worth more than whatever you think it might be.
[01:23:33.880 --> 01:23:37.960] So go download Superhuman, give it a shot, invite your team.
[01:23:37.960 --> 01:23:39.240] The metrics are real.
[01:23:39.240 --> 01:23:50.440] I know they sound like the kind of metrics that startups make up, but getting through your email twice as fast, responding one to two days sooner, saving four hours or more every single week.
[01:23:50.440 --> 01:23:51.640] They're all real.
[01:23:51.640 --> 01:24:03.560] Actually, speaking of which, the consulting firm I mentioned earlier, because they're so into data and into analysis, they wanted to corroborate those numbers for themselves.
[01:24:03.560 --> 01:24:04.360] And so they did.
[01:24:04.360 --> 01:24:13.880] They ran their own internal case study on Superhuman and they were like, yeah, you're saving our partners 3.3 hours per person per week.
[01:24:13.880 --> 01:24:18.240] And there's only one other tool that we've bought that does that, which is ChatGPT.
[01:24:18.240 --> 01:24:18.960] So thank you.
[01:24:18.960 --> 01:24:19.760] We love Superhuman.
[01:24:19.760 --> 01:24:20.640] We're rolling it up.
[01:24:20.640 --> 01:24:25.200] If that sounds interesting to you or your company, please do give it a shot.
[01:24:25.200 --> 01:24:26.720] That is super cool.
[01:24:27.040 --> 01:24:35.440] Reflecting back on what I imagined this conversation would look like, a lot of contrarian thinking and attention to detail, I think that's exactly what it was.
[01:24:35.440 --> 01:24:36.640] Ruli, you're awesome.
[01:24:36.640 --> 01:24:38.720] Thank you so much for being here.
[01:24:38.720 --> 01:24:39.760] Bunny, thank you.
[01:24:39.760 --> 01:24:40.560] Bye, everyone.
[01:24:40.720 --> 01:24:42.000] Bye, everyone.
[01:24:43.280 --> 01:24:44.800] Thank you so much for listening.
[01:24:44.800 --> 01:24:51.200] If you found this valuable, you can subscribe to the show on Apple Podcasts, Spotify, or your favorite podcast app.
[01:24:51.200 --> 01:24:57.520] Also, please consider giving us a rating or leaving a review, as that really helps other listeners find the podcast.
[01:24:57.520 --> 01:25:02.880] You can find all past episodes or learn more about the show at lennyspodcast.com.
[01:25:02.880 --> 01:25:05.120] See you in the next episode.

Prompt 6: Key Takeaways

Now please extract the key takeaways from the transcript content I provided.

Extract the most important key takeaways from this part of the conversation. Use a single sentence statement (the key takeaway) rather than milquetoast descriptions like "the hosts discuss...". 

Limit the key takeaways to a maximum of 3. The key takeaways should be insightful and knowledge-additive. 

IMPORTANT: Return ONLY valid JSON, no explanations or markdown. Ensure:
- All strings are properly quoted and escaped
- No trailing commas
- All braces and brackets are balanced
Format: {"key_takeaways": ["takeaway 1", "takeaway 2"]}

Prompt 7: Segments

Now identify 2-4 distinct topical segments from this part of the conversation.

For each segment, identify:
- Descriptive title (3-6 words)  
- START timestamp when this topic begins (HH:MM:SS format)
- Double check that the timestamp is accurate - a timestamp will NEVER be greater than the total length of the audio
- Most important Key takeaway from that segment. Key takeaway must be specific and knowledge-additive.
- Brief summary of the discussion

IMPORTANT: The timestamp should mark when the topic/segment STARTS, not a range. Look for topic transitions and conversation shifts.

Return ONLY valid JSON. Ensure all strings are properly quoted, no trailing commas:
{
  "segments": [
    {
      "segment_title": "Topic Discussion", 
      "timestamp": "01:15:30",
      "key_takeaway": "main point from this segment",
      "segment_summary": "brief description of what was discussed"
    }
  ]
}

Timestamp format: HH:MM:SS (e.g., 00:05:30, 01:22:45) marking the START of each segment.

Prompt 8: Media Mentions

Now scan the transcript content I provided for ACTUAL mentions of specific media titles:

Find explicit mentions of:
- Books (with specific titles)
- Movies (with specific titles)  
- TV Shows (with specific titles)
- Music/Songs (with specific titles)

DO NOT include:
- Websites, URLs, or web services
- Other podcasts or podcast names

IMPORTANT: 
- Only include items explicitly mentioned by name. Do not invent titles.
- Valid categories are: "Book", "Movie", "TV Show", "Music"
- Include the exact phrase where each item was mentioned
- Find the nearest proximate timestamp where it appears in the conversation
- THE TIMESTAMP OF THE MEDIA MENTION IS IMPORTANT - DO NOT INVENT TIMESTAMPS AND DO NOT MISATTRIBUTE TIMESTAMPS
- Double check that the timestamp is accurate - a timestamp will NEVER be greater than the total length of the audio
- Timestamps are given as ranges, e.g. 01:13:42.520 --> 01:13:46.720. Use the EARLIER of the 2 timestamps in the range.

Return ONLY valid JSON. Ensure all strings are properly quoted and escaped, no trailing commas:
{
  "media_mentions": [
    {
      "title": "Exact Title as Mentioned",
      "category": "Book",
      "author_artist": "N/A",
      "context": "Brief context of why it was mentioned",
      "context_phrase": "The exact sentence or phrase where it was mentioned",
      "timestamp": "estimated time like 01:15:30"
    }
  ]
}

If no media is mentioned, return: {"media_mentions": []}

Full Transcript

[00:00:00.000 --> 00:00:01.760] Let's talk about product market fit.
[00:00:01.760 --> 00:00:08.080] You have to deliberately not act on the feedback of many of your early users.
[00:00:08.080 --> 00:00:13.760] And this is at the same time as listening to people intensely and building what people want.
[00:00:13.760 --> 00:00:16.720] That's what we're here to do is to make something that people want.
[00:00:16.720 --> 00:00:17.840] But it can't be all people.
[00:00:17.840 --> 00:00:20.320] And the question becomes: how do you listen to them?
[00:00:20.320 --> 00:00:24.960] And then, even of what they say, what do you pay attention to and what don't you?
[00:00:25.120 --> 00:00:26.080] The trick here is.
[00:00:26.320 --> 00:00:29.440] You're not doing what a lot of CEOs think they need to be doing with their time.
[00:00:29.440 --> 00:00:33.200] A lot of CEOs think they need to spend time on hiring or org building.
[00:00:33.200 --> 00:00:36.400] And you intentionally, I will spend time on product and marketing design.
[00:00:36.400 --> 00:00:39.840] So this is a technique that I call the switch log.
[00:00:39.840 --> 00:00:50.480] And it's born out of the observation that your calendar says what you thought you were going to do, but it's really only your trail of work that describes what you actually did.
[00:00:50.480 --> 00:00:51.600] How can we capture that?
[00:00:51.600 --> 00:00:53.200] So I came up with the following idea.
[00:00:53.200 --> 00:00:56.000] What if I just did whatever the heck I wanted?
[00:00:56.000 --> 00:00:58.800] What's the most pivotal moment in your career, in your life?
[00:00:58.800 --> 00:01:02.000] I learned the real secret behind virality.
[00:01:02.000 --> 00:01:06.160] There is no such thing as a truly viral product.
[00:01:06.160 --> 00:01:07.840] What then is the true secret?
[00:01:07.840 --> 00:01:09.280] It is.
[00:01:11.840 --> 00:01:14.080] Today, my guest is Rahul Vora.
[00:01:14.080 --> 00:01:22.240] Rahul is the founder and CEO of Superhuman and one of the most thoughtful and insightful and articulate founders that I've met.
[00:01:22.240 --> 00:01:32.240] As you'll see in our conversation, it's hard not to be captivated by Rahul's storytelling skills and also his really insightful takes on how to build great products and teams.
[00:01:32.240 --> 00:01:56.800] This episode is for anyone who's looking to build their product taste, help their teams move faster, learn how to think better from first principles, and also learn about Superhuman's very unique approach to building their company, including why they manually onboarded every single new user for years and why they've decided to stop, why they ignored most of their customer feedback on their way to finding product market fit, and also how you can use his approach to finding product market fit for your own company.
[00:01:56.800 --> 00:01:59.520] Also, the power of game design in building great products.
[00:01:59.520 --> 00:02:07.800] A very contrarian take on pricing strategy, what Rahul has learned about building scale products on top of AI and LLMs, and so much more.
[00:02:07.800 --> 00:02:15.160] A huge thank you to Ed Sims, Conrad Irwin, Bill Trenchard, and Gara Vora for suggesting questions and topics for this conversation.
[00:02:15.160 --> 00:02:19.560] If you enjoy this podcast, don't forget to subscribe and follow it in your favorite podcasting app or YouTube.
[00:02:19.560 --> 00:02:27.000] Also, if you become a yearly subscriber of my newsletter, you get a year free of Superhuman that you can start using immediately.
[00:02:27.000 --> 00:02:31.400] You also get a year free of Notion, Perplexity Pro, Granola, and Linear.
[00:02:31.400 --> 00:02:33.720] Check it out at lennysnewsletter.com.
[00:02:33.720 --> 00:02:37.640] With that, I bring you Rahul Vora.
[00:02:38.600 --> 00:02:41.240] This episode is brought to you by Eppo.
[00:02:41.240 --> 00:02:49.160] Eppo is a next-generation A-B testing and feature management platform built by alums of Airbnb and Snowflake for modern growth teams.
[00:02:49.160 --> 00:02:55.160] Companies like Twitch, Miro, ClickUp, and DraftKings rely on Eppo to power their experiments.
[00:02:55.160 --> 00:03:01.320] Experimentation is increasingly essential for driving growth and for understanding the performance of new features.
[00:03:01.320 --> 00:03:08.760] And Eppo helps you increase experimentation velocity while unlocking rigorous deep analysis in a way that no other commercial tool does.
[00:03:08.760 --> 00:03:18.200] When I was at Airbnb, one of the things that I loved most was our experimentation platform, where I could set up experiments easily, troubleshoot issues, and analyze performance all on my own.
[00:03:18.200 --> 00:03:31.880] Eppo does all that and more with advanced statistical methods that can help you shave weeks off experiment time, an accessible UI for diving deeper into performance, and out-of-the-box reporting that helps you avoid annoying, prolonged analytic cycles.
[00:03:31.880 --> 00:03:38.120] Eppo also makes it easy for you to share experiment insights with your team, sparking new ideas for the A-B testing flywheel.
[00:03:38.120 --> 00:03:46.240] Eppo powers experimentation across every use case, including product, growth, machine learning, monetization, and email marketing.
[00:03:44.600 --> 00:03:51.600] Check out Eppo at getepo.com/slash Lenny and 10x your experiment velocity.
[00:03:51.840 --> 00:03:55.840] That's getepo.com/slash Lenny.
[00:03:56.480 --> 00:03:59.920] This episode is brought to you by the Fundrise Flagship Fund.
[00:03:59.920 --> 00:04:03.680] Full disclosure, real estate investing is boring.
[00:04:03.680 --> 00:04:10.000] Prediction markets are exciting, meme coins are a thrill ride, even the stock market can swing wildly on a headline.
[00:04:10.000 --> 00:04:11.200] Hello, DeepZeek.
[00:04:11.200 --> 00:04:17.760] But with real estate investing, there's no drama or adrenaline or excuses to refresh your portfolio every few minutes.
[00:04:17.760 --> 00:04:22.400] Just bland and boring stuff like diversification and dividends.
[00:04:22.400 --> 00:04:27.840] So you won't be surprised to learn that the Fundrise Flagship Real Estate Fund is a complete snooze fest.
[00:04:27.840 --> 00:04:36.960] The fund holds $1.1 billion worth of institutional caliber real estate managed by a team of pros focused on steadily growing your net worth for decades to come.
[00:04:36.960 --> 00:04:37.600] See?
[00:04:37.600 --> 00:04:38.640] Boring.
[00:04:38.640 --> 00:04:39.840] That's the point.
[00:04:39.840 --> 00:04:46.880] You can start investing in minutes and with as little as $10 by visiting fundrise.com/slash Lenny.
[00:04:46.880 --> 00:04:53.040] Carefully consider the investment objectives, risks, charges, and expenses of the Fundrise Flagship Fund before investing.
[00:04:53.040 --> 00:04:59.120] Find this information and more in the fund's prospectus at fundrise.com/slash flagship.
[00:04:59.120 --> 00:05:00.960] This is a paid ad.
[00:05:03.920 --> 00:05:06.080] Rahul, thank you so much for being here.
[00:05:06.080 --> 00:05:07.680] Welcome to the podcast.
[00:05:07.680 --> 00:05:10.400] Hello, hello, and thank you for having me, Lenny.
[00:05:10.400 --> 00:05:12.320] I have so many questions for you.
[00:05:12.320 --> 00:05:14.640] We're going to have so much to talk about.
[00:05:14.640 --> 00:05:18.000] I actually want to start with your time before Superhuman.
[00:05:18.000 --> 00:05:23.680] When I was preparing for this chat, I actually asked you, What's the most pivotal moment in your career, in your life?
[00:05:23.680 --> 00:05:30.120] And you told me that other than starting Superhuman, it was selling your previous company, Reportive, to LinkedIn.
[00:05:29.440 --> 00:05:31.400] So, let me just start there.
[00:05:31.720 --> 00:05:32.920] What was that experience like?
[00:05:32.920 --> 00:05:37.640] What do people not know about this phase in your life, and just why was it so pivotal?
[00:05:37.640 --> 00:05:41.560] So, for folks that don't know, Reportive was my last company.
[00:05:41.560 --> 00:05:46.120] It was the first Gmail extension to scale to millions of users.
[00:05:46.120 --> 00:05:57.080] Basically, on the right-hand side of Gmail, we would show you what people look like, where they work, links to their recent tweets, their LinkedIn profile, and everything else that they were doing online.
[00:05:57.080 --> 00:06:03.480] So, if you were hiring, marketing, selling in BD, super useful.
[00:06:03.480 --> 00:06:14.760] It turns out we somehow attracted most of LinkedIn's daily active users onto this one free app, and I then ultimately ended up selling that to LinkedIn.
[00:06:14.760 --> 00:06:22.760] And that by far, as you said, was the most pivotal thing I'd done in my career prior to starting Superhuman.
[00:06:22.760 --> 00:06:29.000] Now, had I known that we'd amassed most of LinkedIn's active users onto one app, I would have sold it for far more.
[00:06:29.000 --> 00:06:45.800] But the actual pivotal moment was really who I got to work with, because I reported to LinkedIn's head of growth, Elliot Schmuckler, and he was responsible for scaling LinkedIn from 25 million members to, when I joined, north of 250 million members.
[00:06:45.800 --> 00:06:51.640] And during my first one-on-one, I learned the real secret behind virality.
[00:06:51.640 --> 00:06:55.080] And big hint, it's not about viral mechanics.
[00:06:55.080 --> 00:07:01.880] And overall, that acquisition experience gave me the time to figure out what was next and the resources to truly swing for the fences.
[00:07:02.440 --> 00:07:06.760] Okay, well, I have to follow this thread that you put out there of what the secret is to virality.
[00:07:07.080 --> 00:07:08.440] What did you learn there?
[00:07:08.440 --> 00:07:13.720] Well, in my first one-on-one, I sat down with Elliot and I said, Hey, I'm here to learn.
[00:07:13.720 --> 00:07:17.280] Please teach me everything that you know about virality.
[00:07:17.600 --> 00:07:27.120] And he said, Okay, well, hate to burst your bubble, but there is no such thing as a truly viral product.
[00:07:27.200 --> 00:07:28.400] I said, What do you mean?
[00:07:28.480 --> 00:07:29.760] How do you explain Facebook?
[00:07:29.760 --> 00:07:32.560] For that matter, how do you explain LinkedIn?
[00:07:32.560 --> 00:07:44.080] And he said, What I mean is no app has sustained a viral factor of greater than one for any real period of time.
[00:07:44.400 --> 00:07:49.680] Even Facebook in its heyday had a viral factor of about 0.7.
[00:07:49.680 --> 00:07:51.920] And he told me that lasted for perhaps a year.
[00:07:51.920 --> 00:07:56.720] So one person was creating about 0.7 new users.
[00:07:56.720 --> 00:08:01.200] And I double-clicked again and I said, Well, Elliot, what about the address book import?
[00:08:01.200 --> 00:08:04.560] This is one of the things that LinkedIn got famous or infamous for.
[00:08:04.560 --> 00:08:12.560] You could import your address book, and then it would spam/slash invite everyone who happens to be members of LinkedIn in your address book.
[00:08:12.560 --> 00:08:15.440] And then eventually it would just invite everyone to LinkedIn.
[00:08:15.440 --> 00:08:20.960] And he said, That's an amazing feature, but you have to remember not everyone is going to use it all the time.
[00:08:20.960 --> 00:08:27.840] So even that feature had a lifetime viral factor of about 0.4.
[00:08:27.840 --> 00:08:29.040] And that's considered good.
[00:08:29.040 --> 00:08:31.520] So 0.4 is good for a viral feature.
[00:08:31.520 --> 00:08:33.200] 0.6 is great.
[00:08:33.200 --> 00:08:36.720] Something like 0.7 is absolutely incredible.
[00:08:36.720 --> 00:08:40.800] You're in the stratosphere up with Facebook at that time.
[00:08:41.120 --> 00:08:44.960] So I said, well, okay, all of these things by definition are going to peter out.
[00:08:44.960 --> 00:08:46.480] There's going to be an asymptote.
[00:08:46.480 --> 00:08:51.440] None of these viral mechanics keep on compounding, which actually makes sense.
[00:08:51.440 --> 00:08:54.720] It would be a little absurd if things just kept on growing.
[00:08:54.720 --> 00:08:58.640] What then is the true secret behind virality?
[00:08:58.960 --> 00:09:02.280] And he said, it is word of mouth.
[00:08:59.520 --> 00:09:06.920] It is the virality you can't measure that isn't a mechanic, that isn't in a feature.
[00:09:06.920 --> 00:09:12.920] It is when one user spontaneously tells another user about your product.
[00:09:12.920 --> 00:09:17.000] And that really colored how I think about growth and virality.
[00:09:17.000 --> 00:09:23.240] Since then, it has shaped so much of what we do at Superhuman and so much of how I think about growing brands.
[00:09:23.240 --> 00:09:23.560] Wow.
[00:09:24.200 --> 00:09:25.320] You're such a great storyteller.
[00:09:25.320 --> 00:09:27.080] I'm just like listening here, captivated.
[00:09:27.240 --> 00:09:28.280] What is he going to say next?
[00:09:28.760 --> 00:09:29.640] That was fascinating.
[00:09:29.640 --> 00:09:37.960] I actually have a post that I'm going to that very much aligns with what you're talking about, which is titled Virality is a Myth, mostly.
[00:09:37.960 --> 00:09:43.080] And it's based, I forget, on this book where they do all this research on like actual viruses.
[00:09:43.080 --> 00:09:46.920] And it turns out they're not actually spreading in this like exponential way.
[00:09:46.920 --> 00:09:51.480] There's like one person that spreads it to a lot of people and it keeps happening.
[00:09:51.480 --> 00:09:54.520] And that's actually apparently what the data shows.
[00:09:54.520 --> 00:10:03.960] And I'm curious if you found this same thing, which is when people think of app as going viral, it's like one person with a massive platform sharing it and their audience adopts it.
[00:10:03.960 --> 00:10:06.200] And it's like, that's just one to many.
[00:10:06.200 --> 00:10:13.160] And then it just happens a couple of times and it looks like it's going viral, but it's like a person to many people, not many people to many people.
[00:10:13.160 --> 00:10:14.760] Thoughts on that?
[00:10:14.760 --> 00:10:26.040] Yeah, we've definitely found that there are whales, to use the gaming terminology, that one person is going to be responsible for inviting 25, 50, 100 people.
[00:10:26.040 --> 00:10:28.360] And they may have various motivations for doing that.
[00:10:28.360 --> 00:10:39.240] In Superhuman, as an individual subscriber, if you refer somebody else and they sign up, you both get a free month, which is a great incentive if you're paying out of pocket.
[00:10:39.240 --> 00:10:50.480] So we have people who send many, many hundreds of invites, and there are some people who essentially have free superhuman for life now due to how many people they've invited.
[00:10:50.800 --> 00:10:59.280] But of course, that incentive doesn't necessarily work inside of a company or inside of a team where ultimately it's the company paying for the product.
[00:10:59.280 --> 00:11:02.720] So you have to then come up with new motivations for those people.
[00:11:02.720 --> 00:11:10.160] And that's where there really isn't any substitute to having a genuinely multiplayer or a genuinely collaborative product.
[00:11:10.240 --> 00:11:15.040] That's one of the huge evolutions we've taken Superhuman through over the last probably about two years.
[00:11:15.040 --> 00:11:19.280] Early last year, we launched what we call Superhuman 2.0.
[00:11:19.280 --> 00:11:26.640] And the basic idea is we saw almost every single other app of Note become collaborative by default.
[00:11:26.640 --> 00:11:31.120] Figma, Notion, Loom, these are all multiplayer or collaborative by default.
[00:11:31.120 --> 00:11:42.720] Yet email, the one tool that we all use more than anything else, even more than things like Slack, was still firmly stuck in its single-player origins.
[00:11:43.040 --> 00:11:51.360] I want to come back to something that you mentioned that I kind of didn't come back to, and I think is really core to what you just shared, which is word of mouth being so important.
[00:11:51.680 --> 00:11:56.240] Like people talk about all these viral features and sharing contact books and all these things.
[00:11:56.240 --> 00:12:06.880] And your point is that takes you to a place, but really what helps a consumer-ish product spread is word of mouth people sharing with each other, which then the question is, how do you do that?
[00:12:06.880 --> 00:12:11.040] We're going to talk about a lot of things that you did to make Superhuman something people want to share.
[00:12:11.040 --> 00:12:13.840] But in the end, it's just like making something people want to share.
[00:12:13.840 --> 00:12:15.600] That's like the definition almost.
[00:12:15.600 --> 00:12:18.320] So then it's like, what makes people want to share stuff?
[00:12:18.320 --> 00:12:19.120] It's amazing.
[00:12:19.120 --> 00:12:20.280] It's helping them.
[00:12:20.280 --> 00:12:22.000] Something that is remarkable.
[00:12:22.000 --> 00:12:25.280] Well, it turns out, you mentioned remarkableness.
[00:12:25.280 --> 00:12:27.920] That is one of our core company values.
[00:12:27.920 --> 00:12:31.240] And if you think about what a company has to do, it has to grow.
[00:12:29.600 --> 00:12:32.280] How do things grow?
[00:12:29.680 --> 00:12:36.360] Well, let's take Elliot's advice at face value, and I believe it's true.
[00:12:36.360 --> 00:12:39.560] It's creating something that people share.
[00:12:40.200 --> 00:12:44.040] You mentioned one way of doing it, which is something that people want to share.
[00:12:44.040 --> 00:12:49.400] There's actually another way, which is simply creating something remarkable.
[00:12:49.400 --> 00:12:50.600] You use that word.
[00:12:50.600 --> 00:12:53.240] And that is one of the core values of Superhuman.
[00:12:53.240 --> 00:12:59.880] So we have create delight, create something that is so joyful that it really truly brings people delight.
[00:12:59.880 --> 00:13:09.320] We have deliver remarkable quality, something that is so striking, so compelling, and worthy of attention that people can't but help tell others about it.
[00:13:09.320 --> 00:13:16.120] And then we have build the extraordinary, which is a measure of the sort of efficacy or the innovativeness of what we want to build.
[00:13:16.120 --> 00:13:22.600] So that's another trick, which is literally baking these raw ingredients for growth into your company values.
[00:13:23.080 --> 00:13:24.680] I didn't know that was one of your values.
[00:13:24.680 --> 00:13:26.280] That makes so much sense.
[00:13:26.280 --> 00:13:34.360] Okay, we're going to come back to that because I think that is, there's so much to learn about how you think about product and how you think about building the company that builds the product.
[00:13:34.360 --> 00:13:39.160] But I want to actually start here with how this conversation came to be.
[00:13:39.480 --> 00:13:48.440] So the COVID hunt, Rajiv, tweeted months ago, he tweeted this, and we're going to show this if you're on YouTube.
[00:13:48.440 --> 00:13:52.680] Superhuman's product velocity feels like it's kicked into another gear as of late.
[00:13:52.680 --> 00:13:54.440] Does anyone else notice this?
[00:13:54.440 --> 00:13:56.920] And I saw that, I'm like, I completely have noticed this.
[00:13:56.920 --> 00:14:00.680] It feels like there's just feature shipping left and right, AI this, AI that.
[00:14:00.920 --> 00:14:02.840] It feels like you're just like a new company.
[00:14:02.840 --> 00:14:03.960] And I tagged you on the tweet.
[00:14:03.960 --> 00:14:04.840] I'm like, hey, we're cool.
[00:14:04.840 --> 00:14:05.800] What changed?
[00:14:05.800 --> 00:14:12.120] And you answered with a few things, and it just made it clear there's a lot to learn about what you did.
[00:14:12.120 --> 00:14:16.960] Because a lot of companies are in this phase, I think, of just like things aren't moving as fast as we want.
[00:14:16.960 --> 00:14:20.640] We used to be so much faster, we used to ship all these features, and now we don't.
[00:14:14.840 --> 00:14:26.640] And so I think this is a really cool, real case study, illustrative example that we can analyze.
[00:14:26.640 --> 00:14:31.520] So let me ask you this: what did you notice that told you something needed to change at Superhuman?
[00:14:31.520 --> 00:14:37.280] And then what did you change that actually had the most impact on your ability to ship and move faster?
[00:14:37.600 --> 00:14:51.120] I think what we noticed was this sentiment, and we felt it first ourselves, but we also started hearing it from the market, from our users, from our customers, that we've slowed down.
[00:14:51.120 --> 00:14:55.760] And as a founder, as a CEO, that's the absolute last thing you want to hear.
[00:14:55.760 --> 00:14:59.040] It's our job, after all, to speed things up.
[00:14:59.040 --> 00:15:09.920] And when I asked people what they mean by slowing down, they didn't mean the product, of course, the product wasn't working any slower, but that the pace of delivery seemed to have slowed down.
[00:15:10.240 --> 00:15:15.360] So I think to break this down, it's important to start by defining what we mean by a slowdown.
[00:15:15.360 --> 00:15:22.560] There's the kind of slowdown that is unavoidable in certain spaces, and then there is the kind of slowdown that is quite avoidable.
[00:15:22.560 --> 00:15:24.080] We actually had both.
[00:15:24.080 --> 00:15:34.640] So starting with unavoidable slowdown, you can classify anything that you build in a company into one of two categories: solution deepening and market widening.
[00:15:34.640 --> 00:15:42.880] Now, solution deepening means making your product better for its existing users, but not making it available to more users.
[00:15:42.880 --> 00:15:50.240] Whereas market widening means making your product available to more users, but not making the product itself any better.
[00:15:50.560 --> 00:16:04.920] And there are some spaces, there are some markets, there are some platforms where market widening is really fast and really easy, and there are some spaces, email is one of them, where market widening is really hard and really slow.
[00:15:59.600 --> 00:16:06.920] And when we started, we had a great deal of focus.
[00:16:07.160 --> 00:16:10.360] We only supported Gmail, we were only on the web.
[00:16:10.360 --> 00:16:19.560] And in those early years, we could pour every ounce of RD energy, every engineering dollar into solution deepening, making the product better for existing users.
[00:16:19.560 --> 00:16:20.760] And of course, users loved it.
[00:16:20.760 --> 00:16:22.600] It's how we got to product market fit.
[00:16:22.600 --> 00:16:24.280] It's how most startups do.
[00:16:24.280 --> 00:16:30.520] But at a certain point, almost every company then has to start investing in widening the market.
[00:16:30.520 --> 00:16:40.200] For example, the market of people who will use a new Gmail front end, but without a mobile app, does exist, but it is relatively small.
[00:16:40.200 --> 00:16:45.000] And this is something that every new email startup is going to learn sooner or later.
[00:16:45.000 --> 00:16:52.920] In order to keep on growing, you are going to have to need to add an iOS app, and then a Mac OS app, and then a Windows app, and then an Android app.
[00:16:52.920 --> 00:17:02.200] And then you'll soon want to support Office 365, but that's not one thing, that's actually three things, because you have to support Office 365 on desktop, and then on iOS, and then on Android.
[00:17:02.200 --> 00:17:04.920] And that's all much easier said than done.
[00:17:04.920 --> 00:17:13.800] I think we at Superhuman now know things about these APIs that literally no other company knows and I would not wish it upon my worst enemy.
[00:17:13.800 --> 00:17:21.320] So fast forward to today, and Superhuman now works wherever you do on every combination of Gmail, Outlook, Mac, Windows, Web, iOS, Android.
[00:17:21.320 --> 00:17:24.840] And this actually turns out to be a really great technology moat.
[00:17:24.840 --> 00:17:26.920] Almost no other email app can claim this.
[00:17:26.920 --> 00:17:29.480] It's taken many years of intense investment.
[00:17:29.480 --> 00:17:36.760] And I think we'll touch on this later, but it's one of the main reasons why we can sell into the enterprise because we now know everyone can use it.
[00:17:36.760 --> 00:17:37.960] But this is the hard part.
[00:17:38.520 --> 00:17:42.040] When you're doing that market widening, you're not solution deepening.
[00:17:42.040 --> 00:17:45.360] And so your perceived product velocity may decrease.
[00:17:44.680 --> 00:17:50.640] You can avoid some of these things with some smart technology decisions, but mostly you just have to grind through it.
[00:17:50.720 --> 00:17:53.360] And it is worth it to get to the other side.
[00:17:53.360 --> 00:17:57.840] Then there's the kind of slowdown that is avoidable.
[00:17:57.840 --> 00:18:02.960] And if I remember my answer to Rajiv's tweet, that was the kind I was talking about.
[00:18:02.960 --> 00:18:05.920] And in that case, it was our management structure.
[00:18:05.920 --> 00:18:07.360] Or who does what?
[00:18:07.440 --> 00:18:12.880] When we hired our initial executive teams, I followed very conventional wisdom.
[00:18:12.880 --> 00:18:18.560] I ended up with a set of VPs and eight, I think, direct reports, maybe even nine.
[00:18:18.560 --> 00:18:20.560] And I thought that's what you were meant to do.
[00:18:20.560 --> 00:18:23.360] That's how startups are meant to scale.
[00:18:23.360 --> 00:18:27.760] But as anyone who's been there knows, eight direct reports is a lot.
[00:18:27.760 --> 00:18:32.720] It's a lot of hiring, it's a lot of goal setting, it's a lot of OKRs, it's a lot of accountability conversations.
[00:18:32.720 --> 00:18:34.960] And fortunately, also, it's a lot of firing.
[00:18:34.960 --> 00:18:39.360] No CEO ever gets their executive team right on the first try.
[00:18:39.360 --> 00:18:50.320] So that time I had for the things that I think I can genuinely be world-class at, things like product and design and technology and marketing, that all began to rapidly disappear.
[00:18:50.320 --> 00:18:54.320] And as a result, the organization began to slow down.
[00:18:54.560 --> 00:18:58.400] Fortunately, I was also tracking my time very closely.
[00:18:58.400 --> 00:19:00.240] I had this crazy way of tracking it.
[00:19:00.240 --> 00:19:09.280] And at one point, I noticed I was spending six to seven percent of my week on these areas, these areas where I can truly be world class at.
[00:19:09.280 --> 00:19:10.720] So I had two realizations.
[00:19:10.720 --> 00:19:21.360] Number one, as CEO, once you get to a certain scale, and we were definitely at that scale, you can actually define what you want the role of a CEO to be at your company.
[00:19:21.360 --> 00:19:30.120] And number two, the superhuman opportunity deserves everyone who works at the company to spend as much time as possible in their zone of genius.
[00:19:30.120 --> 00:19:33.080] And so that includes me as well as everybody else.
[00:19:29.680 --> 00:19:35.640] So, what I did is I hired a really great president.
[00:19:35.880 --> 00:19:38.680] I went from eight direct reports to two.
[00:19:38.680 --> 00:19:49.560] And the amount of time that I spend on product design, technology, and marketing went up from six to seven percent to about sixty to seventy percent of my week.
[00:19:49.560 --> 00:20:02.040] Just to mirror back a few things: one is people may feel like you are not shipping as much as you used to because you're actually building things they don't care about, which is support for office and all these things that they don't need.
[00:20:02.040 --> 00:20:07.480] But the business needs to expand integrations with Microsoft and Android and all these things.
[00:20:07.480 --> 00:20:14.440] I think that's such a good point that it looks like nothing's happening when there's a lot of good stuff happening for other users that aren't you.
[00:20:14.760 --> 00:20:22.600] And then there's this point about people delegate and then they realize a leader who delegates hires all these execs and then like, this is not what I wanted.
[00:20:22.600 --> 00:20:23.800] Why have I done this?
[00:20:23.800 --> 00:20:27.080] And things, and you think it's going to speed up, but it slows down.
[00:20:27.400 --> 00:20:29.240] A couple threads here that are really interesting.
[00:20:29.240 --> 00:20:31.320] One is this time tracking thing.
[00:20:31.320 --> 00:20:33.480] I need to know what, how do you do this?
[00:20:33.480 --> 00:20:42.680] This is the fact that you knew like seven to eight percent or whatever the number you said, like to that granularity of your time you're spending on things you wanted was that low.
[00:20:42.680 --> 00:20:44.520] How do you do time tracking?
[00:20:44.520 --> 00:20:47.560] Let's not go super far, but just what's your approach?
[00:20:47.880 --> 00:20:51.800] So, this is a technique that I call the switch log.
[00:20:51.800 --> 00:21:04.440] And it's born out of the observation that your calendar says what you thought you were going to do, but it's really only your trail of work that describes what you actually did.
[00:21:04.440 --> 00:21:06.040] So, how can we capture that?
[00:21:06.040 --> 00:21:18.800] And actually, how can we create a system of work that isn't tethered to a calendar where you aren't at the behest of what some timetable says you do or you don't have to do?
[00:21:19.120 --> 00:21:21.680] So, I came up with the following idea.
[00:21:21.680 --> 00:21:25.760] What if I just did whatever the heck I wanted?
[00:21:25.760 --> 00:21:32.960] What if every single time I changed task, I just Slack DM'd my EA?
[00:21:32.960 --> 00:21:37.280] But this also works in Slackbot, like you can just, it just has to go somewhere.
[00:21:37.280 --> 00:21:45.280] I slack DM my EA and I said TS colon and then a few words for the task I was doing.
[00:21:45.600 --> 00:21:48.400] Well, that would create certain changes.
[00:21:48.400 --> 00:21:54.480] Instead of having to constantly look at the calendar and think, oh, should I stop this task, start that task?
[00:21:54.480 --> 00:21:55.680] I can just do what I want.
[00:21:55.680 --> 00:22:01.680] Like, if what I feel right now is, oh boy, I really need to prepare for Lenny's podcast, I'll go ahead and do that.
[00:22:01.680 --> 00:22:12.880] And if I get bored or distracted eight minutes in, which sometimes happens, because something else just bubbles up to the top of my mind, well, there's a reason that my body is bubbling it up to the top of my mind.
[00:22:12.880 --> 00:22:20.400] I also practice transcendental meditation, so I'm very keen on the idea of being aware and listening to what's bubbling up.
[00:22:20.400 --> 00:22:32.160] And so it's okay for me to then go and attend to that thought, as opposed to start to expend my focus points or my discipline or willpower on the thing that I thought I was meant to be doing.
[00:22:32.160 --> 00:22:37.760] All I'd have to do is I'd go back to Slack, TS, colon, dealing with this other thing.
[00:22:37.760 --> 00:22:40.400] And by the way, you should obviously turn up for your meetings.
[00:22:40.400 --> 00:22:44.320] I'm not saying just like blow through your meetings and not turn up for your one-on-ones.
[00:22:44.320 --> 00:22:45.680] Definitely do those things.
[00:22:45.680 --> 00:22:52.080] What I'm saying is, do what feels right for as long as it feels right to do.
[00:22:52.080 --> 00:22:55.200] Then at the end of the week, you can see where your time is going.
[00:22:55.200 --> 00:23:02.360] And I realized at one point that I was spending only, in those days, like 5% of my time on recruiting.
[00:22:59.680 --> 00:23:06.680] Whereas perhaps I should be spending 20 or 30% or more of my time on recruiting.
[00:23:07.000 --> 00:23:14.680] But the biggest thing was I saw I was only spending 6 to 7% of my time on product, on design, on technology, and marketing.
[00:23:14.680 --> 00:23:16.920] And these are things where I know I'm really good at them.
[00:23:16.920 --> 00:23:21.160] I should either be teaching people how to do them or doing them or some combination of both.
[00:23:21.160 --> 00:23:22.840] That's probably the best thing for me.
[00:23:22.840 --> 00:23:28.680] It keeps me really happy, very joyful, keeps me sharp, but it's also scaling the organization.
[00:23:28.680 --> 00:23:30.600] And so that's how we had that kind of an insight.
[00:23:30.600 --> 00:23:37.160] Once you have this Slack log, you can then graph it and chart it and see where your time is actually going.
[00:23:37.480 --> 00:23:38.600] How cool.
[00:23:38.600 --> 00:23:44.360] Clearly, this is an app opportunity or like an agent opportunity where you're just telling this thing every time.
[00:23:44.360 --> 00:23:48.120] It's essentially tracking context switches, which we're always hearing.
[00:23:48.120 --> 00:23:49.800] Try to not avoid context switches.
[00:23:50.120 --> 00:23:52.520] Yeah, I think context switches are fine.
[00:23:52.520 --> 00:24:04.760] I mean, there's definitely this idea that for every interruption you have, the brain does take roughly 21 minutes on average to recover, to get back to the efficacy before that you were disturbed.
[00:24:04.760 --> 00:24:06.040] And it's a big deal, of course.
[00:24:06.040 --> 00:24:07.400] I'm building productivity software.
[00:24:07.400 --> 00:24:13.160] We design superhuman to minimize the amount of distraction and disruption that's possible within the app.
[00:24:13.160 --> 00:24:20.920] But if you're working on something and at the back of your mind, something bubbles up, you have to attend to it in one way or the other.
[00:24:20.920 --> 00:24:26.440] Sometimes I just write it down and I have a actually, I don't have my notebook with me, but it's really big.
[00:24:26.440 --> 00:24:32.440] I have like a gigantic, whatever, twice the size of A4 is, I guess, A3 sketchbook.
[00:24:32.440 --> 00:24:34.680] And I always have a 4-H pencil.
[00:24:34.680 --> 00:24:38.440] So whenever one of those thoughts comes up, I just scribble it down.
[00:24:38.440 --> 00:24:41.960] Or I actually stop what I'm doing and I attend to that task.
[00:24:41.960 --> 00:24:44.200] Because there's a reason it's bubbling up right now.
[00:24:44.200 --> 00:24:49.920] And I'll let you know exactly the type of paper and pencil, 4-H pencil, A3 paper.
[00:24:44.920 --> 00:24:50.720] Very basic one.
[00:24:51.840 --> 00:24:53.360] Okay, this is going to be a theme.
[00:24:53.360 --> 00:24:54.400] You mentioned meditation.
[00:24:54.400 --> 00:24:55.360] You said you do TM.
[00:24:55.360 --> 00:24:57.600] So you do 20 minutes in the morning, 20 minutes.
[00:24:57.760 --> 00:25:00.880] Do you do it that style or you do a longer session?
[00:25:00.880 --> 00:25:03.920] I do about half an hour in the morning, including rest time.
[00:25:03.920 --> 00:25:06.240] The physical rest component of it is very important to me.
[00:25:06.240 --> 00:25:10.080] So it's 20 minutes of the actual meditation, then 10 minutes of rest.
[00:25:10.080 --> 00:25:12.960] And I do that in the morning as well as in the afternoon at around 3 p.m.
[00:25:13.200 --> 00:25:14.640] And you just carve that out on your calendar.
[00:25:14.640 --> 00:25:16.400] You know, everyone knows Rahul at 3 o'clock.
[00:25:16.400 --> 00:25:17.680] He's going to be out.
[00:25:17.680 --> 00:25:18.640] Absolutely.
[00:25:18.640 --> 00:25:24.640] And my EA knows, they are the one who's organizing the calendar and making sure things happen when they need to happen.
[00:25:24.640 --> 00:25:29.520] They also know that nothing can override this TM block.
[00:25:29.680 --> 00:25:32.480] Without it, I genuinely start to fall apart.
[00:25:32.480 --> 00:25:39.040] But with it, I'm able to access some very deep competencies that I didn't have before.
[00:25:39.040 --> 00:25:41.600] I've been doing this now for about four or five years.
[00:25:41.600 --> 00:25:49.840] And initially, I simply felt happier, occasionally even more euphoric, coming out of a really great meditation session.
[00:25:49.840 --> 00:25:54.960] But over time, I found that my ability to focus was increasing.
[00:25:54.960 --> 00:26:02.240] I could hold attention on something for much longer, but I also was able to become much more creative and much more expressive.
[00:26:02.560 --> 00:26:08.320] These are well-known side effects, as it were, or intended effects for some people of TM.
[00:26:08.640 --> 00:26:17.040] And interestingly about TM, if you compare it to other forms of meditation, they don't have quite the same impact across quite as many executive functions.
[00:26:17.040 --> 00:26:25.520] So there's something particularly interesting that's going on with transcendental meditation as opposed to other forms that folks are still trying to unravel and figure out.
[00:26:26.160 --> 00:26:32.200] Folks want to, if they're inspired and they want to check out this form of meditation, any advice on where they could go learn?
[00:26:32.520 --> 00:26:33.560] Absolutely.
[00:26:33.560 --> 00:26:34.120] A lot.
[00:26:34.120 --> 00:26:37.640] But in summary, have a coach teach you.
[00:26:37.640 --> 00:26:42.760] I had many false starts myself with meditation, trying the various apps, learning from books.
[00:26:42.760 --> 00:26:44.920] None of it really worked for me.
[00:26:44.920 --> 00:26:56.200] What worked was having one-on-one teaching from someone themselves who had been taught one-on-one, the yogic or the Raj tradition of teaching.
[00:26:56.200 --> 00:27:03.000] And this person in particular had also been a venture-backed founder multiple times over.
[00:27:03.000 --> 00:27:10.840] And so they're very well aware of the kinds of stresses that I tend to be under, and all of his clients are mostly in technology as well.
[00:27:10.840 --> 00:27:19.560] If you're in the Bay Area, this person's name is Laurent Valasek, and they run an institution called the Peak Leadership Institute.
[00:27:19.560 --> 00:27:30.920] And this is all about how we can live a more integrated and whole life, integrating wellness practices like meditation, but for the purpose of unlocking peak performance in life and in business.
[00:27:30.920 --> 00:27:31.800] Thank you for sharing that.
[00:27:31.800 --> 00:27:33.160] That is very actionable.
[00:27:33.160 --> 00:27:35.400] We're going to link to that in the show notes.
[00:27:35.400 --> 00:27:37.800] Okay, I'm going to try to bring us back on course.
[00:27:37.800 --> 00:27:41.720] The other thing you mentioned that I think is really interesting is hiring a president.
[00:27:41.720 --> 00:27:51.160] A lot of founders and leaders might be hearing this and be like, going from eight reports and doing all these things I don't want to spending most of my time on the product and design and marketing, amazing.
[00:27:51.160 --> 00:27:58.680] What did this president take off your plate and what is their responsibility that allowed you to do the stuff you wanted to do?
[00:27:58.680 --> 00:28:07.800] The biggest thing was taking off the operations and the management of the executive team and the rest of the company.
[00:28:07.800 --> 00:28:16.000] So think of the president role in Superhuman as an operationally, extremely challenging and very growthful role.
[00:28:16.000 --> 00:28:22.240] Like it is, it's perfect for someone who wants to go on to be a CEO in their next role.
[00:28:22.560 --> 00:28:35.040] And instead of hiring and firing that team, instead of managing and setting their goals, instead of the accountability conversations, someone else is now doing that.
[00:28:35.040 --> 00:28:50.240] In addition, because that's not the only job, in addition, they're also a very strong thought partner when it comes to corporate strategy, when it comes to where do we take Act One, our email product.
[00:28:50.240 --> 00:28:52.880] How far do we go down the multiplayer path?
[00:28:53.120 --> 00:28:56.080] How aggressively should we lean into AI?
[00:28:56.400 --> 00:29:00.080] What's a reasonable gross margin in a world with AI?
[00:29:00.080 --> 00:29:04.880] Are we, from a financial perspective, okay, dipping now and then coming back later?
[00:29:04.880 --> 00:29:07.440] When should we start building our second product?
[00:29:07.440 --> 00:29:10.000] How do we think about our RD strategy?
[00:29:10.000 --> 00:29:12.000] Should we keep on hiring in the Bay Area?
[00:29:12.000 --> 00:29:18.080] Or, as we've done for many of our recent hires, should we continue hiring in Latin America?
[00:29:18.080 --> 00:29:20.880] Should we consider other time zones as well?
[00:29:20.880 --> 00:29:22.320] And so on and so on and so on.
[00:29:22.320 --> 00:29:26.080] I mean, I'm just randomly coming up with questions, but the list is truly endless.
[00:29:26.080 --> 00:29:33.040] It is another way to think about it: it's like a grown-up co-founder.
[00:29:33.040 --> 00:29:38.640] The two people I co-founded the company with, Conrad and Vivek, they've long since gone from Superhuman.
[00:29:38.640 --> 00:29:45.680] We're now a 10-year-old organization, and I'm one of those rare founders that is persisting and thriving actually 10 years in.
[00:29:46.000 --> 00:29:54.880] That said, the journey never gets easier, it gets different, and you still need that co-founding energy around you.
[00:29:54.880 --> 00:30:03.960] And I have a handful of people in the organization who are in their roles providing that kind of energy, that kind of inputs, and who thrive off doing so.
[00:29:59.840 --> 00:30:05.720] And then the president role is definitely one of them.
[00:30:06.920 --> 00:30:08.680] Incredibly interesting.
[00:30:08.680 --> 00:30:10.440] There's so many, so much there.
[00:30:10.760 --> 00:30:14.840] One, just a couple of things I'll share, and then I want to move on to a different topic.
[00:30:14.840 --> 00:30:21.800] One is just, it's cool, the solution to helping you move faster and do the work you want to do is org design.
[00:30:21.800 --> 00:30:25.640] That feels like a really doable thing.
[00:30:25.640 --> 00:30:38.600] If you're finding you're not spending time on things you want to spend on time on and things aren't moving as fast as you want, it's essentially you can find people to take on things that you don't want and shift the way that the org is structured and that could solve a lot of problems.
[00:30:38.600 --> 00:30:39.880] That's what it did for you.
[00:30:39.880 --> 00:30:41.560] And then I think it's also really interesting.
[00:30:41.560 --> 00:30:50.760] There's this lesson here of as a founder, if you're just feeling like, I don't know, depleted or just like not, don't have the partner you want, you could bring someone on that could be that person.
[00:30:50.760 --> 00:30:51.800] Absolutely.
[00:30:51.800 --> 00:30:52.520] Yep.
[00:30:52.520 --> 00:30:52.920] Okay.
[00:30:52.920 --> 00:30:53.640] There's so much there.
[00:30:53.640 --> 00:30:57.000] That was much more of a rich area than I even expected.
[00:30:57.000 --> 00:30:58.680] I want to zoom out a little bit.
[00:30:58.680 --> 00:31:06.280] And there's a couple themes that came up again and again when I talked to folks that you've worked with, investors and superhuman.
[00:31:06.280 --> 00:31:13.800] And the two themes are contrarian thinking in terms of building the company and strong attention to detail.
[00:31:13.800 --> 00:31:16.360] Let's spend a little time on attention to detail.
[00:31:16.360 --> 00:31:21.000] And like I said, this is one of the things that came up again and again when I was asking people about you.
[00:31:21.000 --> 00:31:23.800] So I have this quote from Ed Sims.
[00:31:23.960 --> 00:31:25.240] Maybe your first investor?
[00:31:25.240 --> 00:31:26.840] Were they your first investor?
[00:31:26.840 --> 00:31:29.800] Yeah, there's a bunch of people on Twitter who are going to fight for that.
[00:31:29.800 --> 00:31:35.880] But to get the record straight, Ed Sim did actually write the first three checks into Superhuman.
[00:31:35.880 --> 00:31:38.600] First three checks, like subsequent rounds.
[00:31:38.600 --> 00:31:41.160] Well, yeah, I mean, quick sidebar on that.
[00:31:41.560 --> 00:31:46.320] He runs Boldstart Ventures alongside his partner, Elliot Durbin.
[00:31:46.960 --> 00:31:53.920] And they have a particular interest in backing second-time founders, but they'll also back first-time founders.
[00:31:53.920 --> 00:31:58.240] And they love application and infrastructure areas like Superhuman.
[00:31:58.240 --> 00:32:00.160] So we were like the perfect investment.
[00:32:00.160 --> 00:32:04.240] He also wrote a check from his previous fund into Reportive.
[00:32:04.240 --> 00:32:07.040] And I think I'd made him like 5x that money.
[00:32:07.280 --> 00:32:11.040] Nothing to write home about, but definitely I'm going to back this guy again, right?
[00:32:11.040 --> 00:32:15.360] And so I went to him and I said, Hey, listen, and this is going to sound crazy.
[00:32:15.360 --> 00:32:16.720] I want to take on Gmail.
[00:32:16.720 --> 00:32:17.680] He said, Do you have a deck?
[00:32:17.680 --> 00:32:18.640] I was like, Yeah, here it is.
[00:32:18.640 --> 00:32:19.760] One slide, here it is.
[00:32:19.760 --> 00:32:22.480] And it was a screenshot of Gmail with most of it scribbled out.
[00:32:22.640 --> 00:32:23.520] I want to build that.
[00:32:23.520 --> 00:32:25.520] It was going to be amazing.
[00:32:26.000 --> 00:32:28.240] So he said, Cool, we're in.
[00:32:28.560 --> 00:32:29.760] Can I wire you the money?
[00:32:29.760 --> 00:32:31.520] And I said, No, I don't even have a bank account yet.
[00:32:31.680 --> 00:32:34.400] I come back two days later with a bank account.
[00:32:34.400 --> 00:32:37.920] And he's like, Cool, I want to wire you 750K.
[00:32:37.920 --> 00:32:41.120] And I said, I don't even know what I'm going to do with that money.
[00:32:41.120 --> 00:32:42.240] I'm not paying myself.
[00:32:42.240 --> 00:32:43.520] I won't for a while.
[00:32:43.520 --> 00:32:45.680] We don't have any employees.
[00:32:46.000 --> 00:32:48.240] I can't think of anything I want to spend it on.
[00:32:48.240 --> 00:32:50.880] Tell you what, I'll just take 250K.
[00:32:50.880 --> 00:32:52.160] And he was like, What?
[00:32:52.240 --> 00:32:54.800] No, yeah, I'll just take 250K.
[00:32:55.120 --> 00:32:57.680] We start having the conversation around venture economics.
[00:32:57.680 --> 00:32:59.200] I'm like, yeah, you know, it's fine.
[00:32:59.200 --> 00:33:00.240] We'll figure it out.
[00:33:00.240 --> 00:33:02.480] And then a few months back, I took another 250K.
[00:33:02.480 --> 00:33:10.960] And a few months back, I took another 250K as I began inventing ways and finding channels to deploy capital properly.
[00:33:11.280 --> 00:33:12.240] I love this story.
[00:33:12.240 --> 00:33:13.440] I love all these stories you're sharing.
[00:33:13.440 --> 00:33:14.720] I've never heard before.
[00:33:14.720 --> 00:33:15.840] And by the way, Ed is awesome.
[00:33:15.840 --> 00:33:19.520] We're talking about him coming on the podcast, maybe breaking our VC rule.
[00:33:19.840 --> 00:33:29.120] So, specifically, the story he shared with me that is maybe an example of you and your attention to detail is he said that you created your own font because existing fonts weren't good enough.
[00:33:29.120 --> 00:33:30.000] Is that true?
[00:33:31.080 --> 00:33:32.040] Kinda.
[00:33:32.040 --> 00:33:32.440] Okay.
[00:33:32.760 --> 00:33:38.280] The font that we use today is a modified version of Adele Sans.
[00:33:38.280 --> 00:33:48.520] And the story there is: I looked at all of the major font families, and honestly, none of them was what I would call truly excellent.
[00:33:48.520 --> 00:33:50.680] And that may sound like an odd thing to say.
[00:33:50.680 --> 00:33:56.120] So, let's, if you will, permit me to talk about typography and email for a minute.
[00:33:56.440 --> 00:34:05.880] So, the first thing we did was we took our UI and we laid it out in about 15 different styles using examples of the major font families.
[00:34:05.880 --> 00:34:11.160] We actually printed these out and we left them on a desk in the middle of our office.
[00:34:11.480 --> 00:34:23.400] Sometimes with design, you want to tune in to your immediate, most visceral response, but sometimes you want to truly let a design marinate.
[00:34:23.400 --> 00:34:24.600] And this was the latter.
[00:34:24.600 --> 00:34:26.440] So, we let these designs marinate.
[00:34:26.440 --> 00:34:29.400] We let these font choices percolate.
[00:34:29.400 --> 00:34:31.640] And like I said, none of them was truly excellent.
[00:34:31.800 --> 00:34:36.040] Number one, I was looking for a font that was in and of itself gorgeous.
[00:34:36.040 --> 00:34:44.200] Number two, I was looking for a font that could also convey a message of any kind without overpowering the sentiment of that message.
[00:34:44.200 --> 00:34:49.480] For example, does the font work when this is inviting you to a party?
[00:34:49.480 --> 00:34:54.840] Many fonts, including almost all serif fonts, are actually too somber or too sober for that.
[00:34:54.840 --> 00:35:01.640] Or to pick another extreme, does the font work if it is informing you of somebody's passing?
[00:35:01.640 --> 00:35:03.800] Many fonts are just too jaunty for that.
[00:35:03.960 --> 00:35:07.720] You wouldn't want that kind of message in Comic Sans, for example.
[00:35:07.720 --> 00:35:14.280] And number three, I was optimizing for a font that made reading speed and comprehension really fast.
[00:35:14.280 --> 00:35:20.240] And number four, I was looking for fonts that made email addresses themselves look great.
[00:35:20.560 --> 00:35:23.360] So I discarded all the 15 because they weren't good enough.
[00:35:23.360 --> 00:35:31.120] And after searching high and low, I came across a font called Adele Sans, which is designed by a foundry called Type Together.
[00:35:31.120 --> 00:35:32.720] It's type-together.com.
[00:35:32.800 --> 00:35:34.320] They have a whole bunch of lovely fonts.
[00:35:34.320 --> 00:35:35.520] Go check them out.
[00:35:35.840 --> 00:35:39.360] And if you go through my list, number one, Adele Sans is gorgeous.
[00:35:39.360 --> 00:35:41.120] I think each character is a work of art.
[00:35:41.120 --> 00:35:42.400] It's beautifully formed.
[00:35:42.400 --> 00:35:50.080] Number two, Adele Sans is, I would say, upbeat, it's optimistic, yet it's serious enough to convey any kind of message.
[00:35:50.080 --> 00:35:54.880] It has just the right amount of personality, yet not too much personality.
[00:35:54.880 --> 00:36:02.240] Number three, Adele Sans is also unusually narrow, and that actually fits email particularly well.
[00:36:02.240 --> 00:36:09.600] One of my pet peeves with Gmail, which by default uses Arial, is that the lines are as wide as your window.
[00:36:09.600 --> 00:36:15.040] So if you're in a wide screen, then the lines get really arbitrarily long.
[00:36:15.040 --> 00:36:25.120] And the problem with really wide and really long lines is that they decrease reading speed, because by the time you've reached the end of one line, your eyes have lost track of the start of the next line.
[00:36:25.120 --> 00:36:29.920] And Arial itself has fairly wide characters, which further exacerbates that.
[00:36:29.920 --> 00:36:42.960] So at Superhuman, if you've used the product, you know this, we fix the line length or the typographical measure to the optimal length for reading speed, which depending on the font is around 90 to 120 characters.
[00:36:42.960 --> 00:36:51.360] And Adele Sans is quite narrow, so it actually lets us do this on quite small windows with a fairly dense line.
[00:36:51.360 --> 00:37:00.920] So, we get a lot of information on fairly small windows without getting a very long typographical measure, optimizing for reading speed and for comprehension.
[00:37:01.240 --> 00:37:07.640] And then, number four, finally, Adele Sans has a very unusual treatment of the at symbol in an email address.
[00:37:07.640 --> 00:37:15.160] It actually puts the base of the A in the at on the same baseline as the rest of the text.
[00:37:15.160 --> 00:37:25.800] So, for example, if your name has an A, my name does Rahul at Voras, three A's or two A's and an at, they're all actually on the same baseline.
[00:37:25.800 --> 00:37:31.000] It's a small thing, but it makes the email addresses look incredibly natural.
[00:37:31.000 --> 00:37:41.320] If you look at that and then you actually look at email addresses laid out in other fonts, those other fonts look really clunky and awkward because the A is kind of shifted around and it just looks a bit silly in my opinion.
[00:37:41.320 --> 00:37:42.840] Now, Adele Sams isn't perfect.
[00:37:42.840 --> 00:37:51.080] So, we then worked with a type designer on some of the specific details that there are some of the glyphs which get a little pincery, as it were.
[00:37:51.080 --> 00:37:54.840] And what we use today is very close to retail Adele Sams.
[00:37:55.160 --> 00:37:58.520] And this was pre-launch, or this was after you'd already launched?
[00:37:58.840 --> 00:38:03.320] We probably had about 10, 15 users' appetite.
[00:38:03.320 --> 00:38:11.160] So, I think that's pretty contrarian, unique to be this focused on the font and the typeface before you even launch.
[00:38:11.160 --> 00:38:13.160] This was like, is this even going to be a thing?
[00:38:13.160 --> 00:38:14.440] Will anyone even care?
[00:38:14.440 --> 00:38:17.480] And I think this says a lot about the way you think about product.
[00:38:17.800 --> 00:38:20.840] Oh, yeah, that I mean, that thought never crossed my mind.
[00:38:21.000 --> 00:38:29.960] I think we'll probably come to it later, but the idea that is this never going to be a thing, I think that's a dangerous thought.
[00:38:30.280 --> 00:38:35.240] We can't start thinking that way, because at what point do you stop second-guessing it yourself?
[00:38:35.560 --> 00:38:36.120] Interesting.
[00:38:36.120 --> 00:38:39.000] So, you're like, you were confident this was going to work.
[00:38:39.000 --> 00:38:43.320] So, because I am so confident it will work, I will make, I need to get this right.
[00:38:43.640 --> 00:38:50.000] There's also just, you know, this trap founders fall into of just spending too much time perfecting a thing that never works.
[00:38:50.000 --> 00:38:53.040] And there's always advice, launch early, launch often.
[00:38:53.520 --> 00:38:54.240] Thoughts there.
[00:38:54.240 --> 00:38:55.600] Just like, how do you find that balance?
[00:38:55.600 --> 00:38:57.120] What's your advice there?
[00:38:57.440 --> 00:39:06.480] How much to spend time ahead of launch really does depend on the markets and the structure, the nature of your business model.
[00:39:06.480 --> 00:39:12.800] For example, let's say you're building a marketplace in a greenfield opportunity.
[00:39:12.800 --> 00:39:16.880] So imagine Lyft or Uber in their heyday.
[00:39:17.200 --> 00:39:22.080] And there's a strong network effect because the more cars you have on your platform, the shorter waiting times are.
[00:39:22.080 --> 00:39:27.040] Therefore, people are going to preferentially use your app versus the other person's app.
[00:39:27.360 --> 00:39:29.760] That's when there's no time to spare.
[00:39:29.760 --> 00:39:33.200] That's when you probably shouldn't even be sleeping.
[00:39:33.200 --> 00:39:36.720] You're going to hire the most aggressive, maniacal people possible.
[00:39:36.720 --> 00:39:42.160] You're going to work 120-hour weeks because every marginal minute actually does matter.
[00:39:42.480 --> 00:39:50.640] Every marginal minute in the market, growing compounding is going to make your next year even better.
[00:39:50.960 --> 00:39:57.520] That's actually not true of all startups, and it certainly isn't true of something like Superhuman.
[00:39:57.520 --> 00:40:10.560] Yes, working harder is always better, and we work tremendously hard at Superhuman, but not to the point where it made sense to release something that didn't work.
[00:40:10.560 --> 00:40:20.560] I'm reminded of a story of a founder that was in White Combinator told me about their demo day experience.
[00:40:20.560 --> 00:40:25.760] And they used Mailbox, which some folks may remember, was also a startup.
[00:40:25.760 --> 00:40:29.440] And Dropbox famously acquired them for about $100 million.
[00:40:29.560 --> 00:40:42.120] And the reason that they were well known, apart from the acquisition, is they were the first to popularize swipe to archive or swipe to Markdown, which of course is now standard in Superhuman and every other app.
[00:40:43.080 --> 00:40:49.800] So this founder was using Mailbox and was having an amazing demo day.
[00:40:49.800 --> 00:40:55.800] They're working in the room, they're meeting investors, they're pitching their photography app in this case.
[00:40:55.800 --> 00:41:05.160] And he went home that night and went to his laptop, fired up Mailbox, and sent off a bunch of follow-up emails.
[00:41:05.160 --> 00:41:07.800] He waited a day, didn't hear back.
[00:41:07.800 --> 00:41:10.760] He waited two days, didn't hear back.
[00:41:10.760 --> 00:41:13.480] On the third morning, he figured something was up.
[00:41:13.480 --> 00:41:20.120] So he fired up Gmail, went to his sent mail, and you guessed it, there were no sent mails there.
[00:41:20.120 --> 00:41:23.880] So something had broken with Mailbox.
[00:41:23.880 --> 00:41:28.920] So he's cursing to himself, trying to remind himself everything's going to be okay.
[00:41:29.240 --> 00:41:33.720] Sent all the same emails from Gmail manually.
[00:41:33.720 --> 00:41:35.880] And they all came through.
[00:41:36.840 --> 00:41:44.680] But then one of the investors said, hey, by the way, you might want to check your email client because I've been getting some of your emails twice.
[00:41:44.680 --> 00:41:46.440] And now he goes back into Gmail.
[00:41:46.520 --> 00:41:52.200] He sees that, yes, actually, the original emails that were queued up in Mailbox have now indeed been sent.
[00:41:52.200 --> 00:41:56.440] And some of the investors, unfortunately, most of the investors, he actually pitched twice.
[00:41:56.440 --> 00:41:58.360] Now, is this the end of the world?
[00:41:58.360 --> 00:41:59.000] No.
[00:41:59.000 --> 00:42:00.440] An investor can overlook that.
[00:42:00.440 --> 00:42:02.920] Probably a good thing that you're trying new apps.
[00:42:02.920 --> 00:42:04.280] But was it horrifying?
[00:42:04.280 --> 00:42:05.760] And was it terrible?
[00:42:05.840 --> 00:42:07.240] Like, was it really scary?
[00:42:07.240 --> 00:42:08.440] Absolutely.
[00:42:08.440 --> 00:42:10.040] And imagine this wasn't investors.
[00:42:10.040 --> 00:42:21.200] Imagine this was a customer, someone who you were trying to convince to buy your thing and that you knew what you were doing and you had attention to detail and you had everything just buttoned up and under control.
[00:42:14.840 --> 00:42:22.320] Well, now you've lost face.
[00:42:22.400 --> 00:42:24.000] Now you look foolish.
[00:42:24.000 --> 00:42:34.560] And that's why when you have mission-critical products like email, where you are interfacing with customers, with candidates, with investors, it turns out to really matter.
[00:42:34.560 --> 00:42:36.240] Email is mission-critical.
[00:42:36.240 --> 00:42:40.560] So it's not something where you can simply launch with a half-bates product.
[00:42:40.560 --> 00:42:42.720] This is such an important nuanced take on.
[00:42:42.720 --> 00:42:50.400] There's always this debate: how much to focus on craft and user experience, how much to focus on time to launch and get it out and speed.
[00:42:50.400 --> 00:42:58.400] And what I'm hearing here, which I completely agree with, is it depends on the market you're in and the criticality essentially of how of your product.
[00:42:58.400 --> 00:42:59.840] So if it's email, it just needs to work.
[00:42:59.840 --> 00:43:00.640] You need to get that right.
[00:43:00.640 --> 00:43:01.600] You need to spend all the time.
[00:43:01.600 --> 00:43:03.120] You need to get that right.
[00:43:03.120 --> 00:43:08.800] This reminds me of something else that one of your early investors shared with me, Bill Trenchard from First Round Capital.
[00:43:08.800 --> 00:43:14.080] He talked about how speed was the thing that you just dialed up as a lever to like 11.
[00:43:14.080 --> 00:43:18.720] That's where you just, we will make this the focus, speed, speed, speed.
[00:43:19.040 --> 00:43:27.520] And I think maybe the lesson there is just you pick the thing that you think will most differentiate you, make you significantly better than what's out there.
[00:43:27.520 --> 00:43:37.360] So I guess just thoughts and just how to decide, how you decided speed was the thing you were going to obsess with, and just, I don't know, advice for folks that are trying to decide where to dial up things to 11.
[00:43:37.680 --> 00:43:39.280] Bill is right, and I agree with him.
[00:43:39.280 --> 00:43:41.280] You have to pick something.
[00:43:41.600 --> 00:43:44.320] Knowing what to pick is the trick.
[00:43:44.320 --> 00:43:50.240] And in the early days of Superhuman, I read a book on positioning that really influenced my thinking.
[00:43:50.240 --> 00:43:54.240] And it is, I believe, called Positioning the Battle for Your Mind.
[00:43:54.560 --> 00:44:01.960] And it struck me how the most well-known brands have stood for one clear thing, like they have a clear position.
[00:44:02.280 --> 00:44:13.240] And so in order for Superhuman to be memorable, I believed that we needed to occupy a clear position that was unique and which was available and which reinforced our product strategy.
[00:44:13.240 --> 00:44:20.920] In the first year of Superhuman, therefore, I interviewed hundreds of potential customers about their experience with Gmail and with Outlook.
[00:44:20.920 --> 00:44:26.280] And predictably, almost everybody said that email takes way too much time.
[00:44:26.280 --> 00:44:33.480] But interestingly, many people also said that Gmail and Outlook were way too slow.
[00:44:33.800 --> 00:44:39.000] And that was how I first thought that speed could be an interesting position for us.
[00:44:39.000 --> 00:44:44.040] I then asked myself, is the position of speed unique and is it available?
[00:44:44.040 --> 00:44:54.440] And the answer was overwhelmingly yes, because almost no software was being sold or has ever been sold on the value proposition of speed.
[00:44:54.440 --> 00:45:02.040] The last time I could remember anyone trying to do this was when Google launched Chrome, and obviously that went incredibly well for them.
[00:45:02.040 --> 00:45:13.800] And you may remember they had slow motion videos where they were comparing Chrome render web pages and showing that was faster than an actual strike of lightning.
[00:45:13.800 --> 00:45:15.800] And no one had done it since then.
[00:45:15.800 --> 00:45:20.280] And I then asked, well, does speed reinforce our product strategy?
[00:45:20.280 --> 00:45:22.680] And again, the answer was overwhelmingly yes.
[00:45:22.680 --> 00:45:25.480] I knew that our competition was not going to be startups.
[00:45:25.480 --> 00:45:27.000] It was incumbents.
[00:45:27.000 --> 00:45:37.000] And I also knew that incumbents generally struggle with speed, because by definition, they have massive scale and usually entrenched architecture.
[00:45:37.000 --> 00:45:47.680] And then finally, I did what I call the cocktail party test, which is to look at cocktail parties and to watch how people pitch your product to other people.
[00:45:47.680 --> 00:45:49.920] And in our case, the pitches were simple.
[00:45:49.920 --> 00:45:53.120] People would say, dude, you have to use it.
[00:45:53.120 --> 00:45:54.800] It's really fucking fast.
[00:45:54.800 --> 00:45:55.680] And that's it.
[00:45:55.680 --> 00:45:56.800] That was the pitch.
[00:45:56.800 --> 00:46:00.800] And that's how I knew that speed would be a really great position for us to start with.
[00:46:01.120 --> 00:46:07.120] I'm excited to chat with Christina Gilbert, the founder of One Schema, one of our longtime podcast sponsors.
[00:46:07.120 --> 00:46:08.320] Hi, Christina.
[00:46:08.320 --> 00:46:10.400] Yes, thank you for having me on, Lenny.
[00:46:10.400 --> 00:46:12.480] What is the latest with One Schema?
[00:46:12.480 --> 00:46:18.400] I know you now work with some of my favorite companies like Ramp, Vanta, Scale, and Watershed.
[00:46:18.400 --> 00:46:25.920] I heard that you just launched a new product to help product teams import CSVs from especially tricky systems like ERPs.
[00:46:25.920 --> 00:46:34.800] Yes, so we just launched OneSchema File Feeds, which allows you to build an integration with any system in 15 minutes as long as you can export a CSV to an SFTP builder.
[00:46:34.800 --> 00:46:43.360] We see our customers all the time getting stuck with hacks and workarounds, and the product teams that we work with don't have to turn down prospects because their systems are too hard to integrate with.
[00:46:43.360 --> 00:46:47.760] We allow our customers to offer thousands of integrations without involving their engineering team at all.
[00:46:47.760 --> 00:46:59.360] I can tell you that if my team had to build integrations like this, how nice would it be to be able to take this off my roadmap and instead use something like OneSchema and not just to build it, but also to maintain it forever?
[00:46:59.360 --> 00:47:00.400] Absolutely, Lenny.
[00:47:00.400 --> 00:47:05.120] We've heard so many horror stories of multi-day outages from even just a handful of bad records.
[00:47:05.120 --> 00:47:11.120] We are laser focused on integration reliability to help teams end all of those distractions that come up with integrations.
[00:47:11.120 --> 00:47:18.960] We have a built-in validation layer that stops any bad data from entering your system, and OneSchema will notify your team immediately of any data that looks incorrect.
[00:47:18.960 --> 00:47:24.720] I know that importing incorrect data can cause all kinds of pain for your customers and quickly lose their trust.
[00:47:24.720 --> 00:47:26.560] Christina, thank you for joining us.
[00:47:26.560 --> 00:47:30.440] And if you want to learn more, head on over to oneschema.co.
[00:47:29.920 --> 00:47:31.960] That's oneschema.co.
[00:47:33.240 --> 00:47:46.760] The next area I want to spend time on, and I imagine we'll have much insight, is some of the contrarian ways you approach building superhuman that a lot of companies never thought about doing that you did that worked out for you.
[00:47:46.760 --> 00:47:51.400] So the first is manually onboarding every single new user.
[00:47:51.720 --> 00:47:58.200] Sure, startups have done this, like, you know, founders bring on some folks and then like, cool, show it, show it to them, and then they stop doing that.
[00:47:58.200 --> 00:48:00.680] And then it's like self-service or sales teams.
[00:48:01.640 --> 00:48:08.120] How far did you scale this manual onboarding phase of your company?
[00:48:08.120 --> 00:48:09.640] Like, how many people did you have onboarding people?
[00:48:09.640 --> 00:48:11.720] How many people did you manually onboard?
[00:48:12.040 --> 00:48:20.520] Yeah, so for folks that don't know, in those early days, we insisted on one-to-one concierge onboarding, and it was absolutely the right thing to do.
[00:48:20.520 --> 00:48:24.440] You couldn't use superhuman unless you went through the onboarding experience.
[00:48:24.440 --> 00:48:26.120] And now it's almost the reverse.
[00:48:26.120 --> 00:48:29.560] Almost every new superhuman customer goes through self-service.
[00:48:29.560 --> 00:48:31.240] The onboarding experience is still there.
[00:48:31.240 --> 00:48:34.440] But again, it is absolutely the right thing to do.
[00:48:34.440 --> 00:48:40.440] To answer your question, at peak, we had about 20 people doing manual onboarding.
[00:48:40.440 --> 00:48:41.800] Okay, so it's not that many people.
[00:48:41.800 --> 00:48:43.080] That's really interesting.
[00:48:43.080 --> 00:48:49.480] Because I always imagined it was like a massive team, but 20 people can do, can handle a lot is the takeaway there.
[00:48:49.480 --> 00:48:55.480] What was the scale, I guess, where you stopped manual onboarding, just for folks that are like thinking about doing this and then went to stop?
[00:48:55.480 --> 00:49:03.720] So I think the reason to stop is that there will always be certain personality types who do not want to go through a one-on-one onboarding.
[00:49:03.720 --> 00:49:07.080] And at a certain point, those people will become very important.
[00:49:07.080 --> 00:49:11.720] And you will need to be ready with a world-class self-service option.
[00:49:11.720 --> 00:49:16.480] When we started building self-service, it seemed nearly impossible.
[00:49:16.640 --> 00:49:35.280] In fact, it was terrifying because it's difficult to overstate how much the entire DNA of the company was built around this idea that we would onboard users manually.
[00:49:35.280 --> 00:49:40.640] And after all, we did so much in our one-to-one onboardings, and there's only so much that software can do.
[00:49:40.640 --> 00:49:44.080] Now, we did, after a lot of grind and persistence, eventually figure it out.
[00:49:44.080 --> 00:49:49.440] And we have a world-class self-service experience today, but we did not at the time.
[00:49:49.760 --> 00:49:53.840] So the flip side is, why would you even do this to begin with?
[00:49:53.840 --> 00:49:55.280] Well, we found two things.
[00:49:55.280 --> 00:50:03.760] Number one, the user metrics are excellent for things like engagement, retention, product market fit score, NPS, virality, for all of those metrics.
[00:50:03.760 --> 00:50:12.320] I think you will significantly beat your industry benchmarks if you go to the effort of one-on-one onboarding your early customers.
[00:50:12.320 --> 00:50:20.240] And it becomes so powerful to have that early cohort of super fans when it comes to things like building a brand.
[00:50:20.240 --> 00:50:26.240] And if folks remember that conversation from way up at the top, what is it that creates true virality?
[00:50:26.240 --> 00:50:27.760] It's not viral mechanics.
[00:50:27.760 --> 00:50:28.960] It's word of mouth.
[00:50:28.960 --> 00:50:29.840] It is brand.
[00:50:30.000 --> 00:50:32.640] This is how you can kickstart a brand.
[00:50:32.640 --> 00:50:47.600] And number two, in a world where you can easily and quickly raise funding, like for example, the zero interest rate phenomenon era, you can actually use dollars to avoid building a first-time user experience and all of the normal growth loops that you would then have to build.
[00:50:47.600 --> 00:51:04.920] You would then instead focus all of your engineers on finding product market fit or in solution deepening or in market widening, but not, for example, on a first-time user experience, not, for example, on activation because you have humans doing activation for you.
[00:51:05.240 --> 00:51:17.080] And by contrast, I saw other companies often competing spend almost half their engineering dollars on those things, on self-service flows for products that ultimately did not find product market fit.
[00:51:17.080 --> 00:51:24.600] So makes sense to do if you really want to create that brand, which I think all consumerist companies need to do.
[00:51:24.600 --> 00:51:31.160] And if there is a, you know, there is money falling off trees for whatever reason, which we did have for a period of time.
[00:51:31.160 --> 00:51:33.960] Arguably, AI companies have that again today.
[00:51:33.960 --> 00:51:39.960] So if you can weave this into your strategy, I think you should, but you should also know when to stop.
[00:51:39.960 --> 00:51:41.000] Super interesting.
[00:51:41.000 --> 00:51:46.280] So I guess some factors to think about, because I wanted to ask you, when should people consider doing this?
[00:51:46.280 --> 00:51:47.960] If they're hearing this, they're like, this is awesome.
[00:51:48.120 --> 00:51:51.800] So many problems solved if I just have somebody onboarding every new user.
[00:51:51.880 --> 00:51:52.760] Everyone's activated.
[00:51:52.760 --> 00:51:53.560] Amazing.
[00:51:53.880 --> 00:52:03.080] So some of the variables you're sharing is: do you have like cheap cash to invest in, say, like it doesn't have to be 20 people, it could be a few people to start.
[00:52:03.080 --> 00:52:09.880] And then if there's like an LTV kind of ACV element of just like, are you going to make enough from a new customer?
[00:52:09.880 --> 00:52:11.240] I imagine that's a variable.
[00:52:11.480 --> 00:52:14.040] Is there anything else you think founders should think about?
[00:52:14.360 --> 00:52:15.000] Absolutely.
[00:52:15.000 --> 00:52:16.360] You don't want to lose money doing this.
[00:52:16.360 --> 00:52:19.960] And we always made money doing onboarding, to be clear.
[00:52:19.960 --> 00:52:31.240] It's just that at a certain point, that the mass market, whether it for us as enterprise or all of the prosumers in the world, you hit a top of funnel width.
[00:52:31.240 --> 00:52:37.160] It needs to be wide enough where manually onboarding no longer makes sense.
[00:52:37.160 --> 00:52:37.800] Awesome.
[00:52:37.800 --> 00:52:38.360] Okay.
[00:52:38.360 --> 00:52:40.040] Let's talk about product market fit.
[00:52:40.040 --> 00:52:43.720] I know that everyone, when they think of Rahul, they think product market fit.
[00:52:43.720 --> 00:52:48.720] You wrote this epic first round post that described the way you guys approach product market fit.
[00:52:48.720 --> 00:52:53.200] We're not going to spend a lot of time on describing it because people can look it up.
[00:52:53.200 --> 00:53:06.720] So let me just ask you this: just what are, I don't know, a couple things that you think people still don't understand about finding product market fit, getting to product market fit, considering it's the most important thing you got to figure out as a founder, right?
[00:53:06.720 --> 00:53:09.680] If you don't find something people want, nothing else matters.
[00:53:09.920 --> 00:53:11.600] Anything there you want to share?
[00:53:11.920 --> 00:53:20.160] The core ideas are still weird enough that I'll start there, which is number one, you can measure product market fit.
[00:53:20.160 --> 00:53:23.360] Number two, you can optimize products market fit.
[00:53:23.360 --> 00:53:29.920] Number three, you can systematically, even numerically increase product market fit.
[00:53:29.920 --> 00:53:36.560] And number four, you can even have an algorithm write your roadmap for you.
[00:53:36.560 --> 00:53:40.080] And that is a roadmap that is guaranteed to increase product market fit.
[00:53:40.080 --> 00:53:45.760] Now, if that sounds crazy, I would be the first to admit it doesn't seem like that should be true.
[00:53:45.760 --> 00:53:48.320] But go check out that post.
[00:53:48.320 --> 00:53:52.960] I think it is still the most widely shared post on first round review.
[00:53:52.960 --> 00:54:07.920] It's called I think How Superhuman Built an Engine to Find Products Market Fit, or just Google the Superhuman Products Market Fit Engine, and you'll see the algorithm laid out there, fully explained, and why it works.
[00:54:07.920 --> 00:54:19.600] And I'd say the second thing is to get to products market fit, you have to deliberately not act on the feedback of many of your early users.
[00:54:19.920 --> 00:54:27.280] And this is at the same time as listening to people intensely and building what people want, right?
[00:54:27.280 --> 00:54:30.360] That's what we're here to do: to make something that people want.
[00:54:30.680 --> 00:54:32.120] But it can't be all people.
[00:54:29.840 --> 00:54:33.160] It can't be everybody.
[00:54:33.320 --> 00:54:36.280] And the question becomes: how do you listen to them?
[00:54:36.280 --> 00:54:41.640] And then, even of what they say, what do you pay attention to and what don't you?
[00:54:42.280 --> 00:54:45.240] All of that's covered in the product market fit engine.
[00:54:45.560 --> 00:54:51.240] Okay, I gotta follow this thought on algorithmically building your roadmap to increase product markets.
[00:54:51.240 --> 00:54:55.080] They talk about just what that one would do that.
[00:54:55.080 --> 00:54:59.400] Well, I mean, that's really the meat of the engine.
[00:54:59.400 --> 00:55:04.040] So let's see if I can condense it here in a very easy to grok fashion.
[00:55:04.360 --> 00:55:10.360] So let's assume, for the sake of argument, that you can put a number on product market fit.
[00:55:10.360 --> 00:55:11.880] And it turns out you can.
[00:55:11.880 --> 00:55:16.280] Very simply, you're going to ask people, how would you feel if you could no longer use this product?
[00:55:16.280 --> 00:55:17.880] You give them three responses.
[00:55:17.880 --> 00:55:20.120] One of them is very disappointed.
[00:55:20.120 --> 00:55:21.960] The other is somewhat disappointed.
[00:55:21.960 --> 00:55:23.400] And the other is not disappointed.
[00:55:23.400 --> 00:55:26.600] Very disappointed means I would be like devastated.
[00:55:26.600 --> 00:55:29.400] I love this product or I need this product.
[00:55:29.720 --> 00:55:40.120] And what Sean Ellis found, Sean Ellis, if you don't know him, is the guy who coined the term growth hacker and he instrumented, benchmarked this initial question.
[00:55:40.120 --> 00:55:54.120] What he found is that the companies that struggled to grow almost always had less than 40% very disappointed, whereas the companies that grew the fastest almost always had more than 40% very disappointed.
[00:55:54.120 --> 00:56:03.480] And this question, this metric, is way more predictive of success than something, for example, like net promoter score.
[00:56:03.800 --> 00:56:06.680] Okay, so far, so easy.
[00:56:06.680 --> 00:56:09.800] How do we make this number go up?
[00:56:09.800 --> 00:56:14.760] Well, you want more people to be very disappointed without your product.
[00:56:15.440 --> 00:56:24.240] And the trick here is not to act too much on the feedback that the very disappointed people are giving you because they already love your product.
[00:56:24.240 --> 00:56:37.360] Also, not to act at all really on the feedback that the not disappointed people are giving you because they're so far from loving your product that they are essentially a lost cause, but to focus on the segment of the somewhat disappointed people.
[00:56:37.360 --> 00:56:42.800] They kind of love your product, but something, and I would wager something small, is holding them back.
[00:56:42.800 --> 00:56:50.000] So you then divide them into two camps: the camp for whom the main benefit of your product resonates, and the camp for whom it doesn't.
[00:56:50.000 --> 00:56:51.360] And what do I mean by that?
[00:56:51.360 --> 00:56:54.880] Well, you go back to the people who really love your product and you basically ask them why.
[00:56:54.880 --> 00:56:57.520] What is it about my products that you really love?
[00:56:57.520 --> 00:57:05.360] In the early days of Superhuman, it would have been speed and keyboard shortcuts and the overall design aesthetic, as well as the time that we were saving you.
[00:57:06.000 --> 00:57:15.360] You then go back to the somewhat disappointed users, and in the superhuman example, I would simply ask, wait, do you like superhuman because of its speed or for something else?
[00:57:15.360 --> 00:57:36.560] And if it's something else, well, and this is hard to do, but politely disregard those people and their feedback, because even if you built everything that they asked for, they're still pulling you in a different direction, and the thing that they like the most from your product isn't actually what the people who en masse love it the most for is.
[00:57:37.200 --> 00:57:48.720] So you have then articulated the sub-segment of the sub-segment that it makes sense to pay attention to, and there's another question in the engine to figure out what they don't like about the product.
[00:57:48.720 --> 00:57:58.480] Now you have a list of things people love, you have a list of things people don't love, and you can work down that list to make the product market fit score go up.
[00:57:58.480 --> 00:58:13.640] And basically, at the start of every planning cycle, I advise spending half your time doubling down on what people really love and half your time systematically overcoming the objections of the somewhat disappointed users, but specifically those for whom the main benefit resonates.
[00:58:13.960 --> 00:58:15.720] That was an excellent summary.
[00:58:15.720 --> 00:58:18.440] I know I said we wouldn't spend a ton of time here, but I'm really glad we did.
[00:58:18.440 --> 00:58:19.560] That was really helpful.
[00:58:19.560 --> 00:58:20.280] Let me ask you this.
[00:58:20.280 --> 00:58:21.880] I know you used this initially in the early days.
[00:58:21.880 --> 00:58:24.280] Are you still operating this way in some form?
[00:58:24.600 --> 00:58:31.000] We don't run the engine as is for superhuman as a whole.
[00:58:31.000 --> 00:58:35.320] There are enough subcomponents of superhuman now that are almost individual products.
[00:58:35.320 --> 00:58:43.160] For example, superhuman for sales, our multiplayer and collaboration features, how we think about the enterprise, AI is its whole thing.
[00:58:43.160 --> 00:58:46.600] But we do sometimes run it on those individual pieces.
[00:58:46.600 --> 00:58:53.720] For example, we'll ask a salesperson the product market fit engine as it relates to superhuman for sales.
[00:58:53.720 --> 00:58:59.320] And as we think about starting new products, we would absolutely deploy the product market fit engine.
[00:58:59.320 --> 00:58:59.880] Awesome.
[00:58:59.880 --> 00:59:04.360] And the way you ask this question is an in-product interstitial sort of survey pop-up thing?
[00:59:04.600 --> 00:59:06.200] You can do it however you want.
[00:59:06.200 --> 00:59:10.760] The way Sean initially benchmarked the number was via email surveys.
[00:59:10.760 --> 00:59:13.240] I think email surveys work just fine.
[00:59:13.240 --> 00:59:23.240] The key thing is, and this applies to any survey methodology, if you're going to change the method of surveying, all of your old numbers are invalidated.
[00:59:23.240 --> 00:59:25.320] So it's just a new baseline going forwards.
[00:59:25.320 --> 00:59:25.720] Got it.
[00:59:25.720 --> 00:59:28.680] And we had Sean on the podcast, and he describes this method in detail.
[00:59:28.680 --> 00:59:31.160] So folks want to explore this John Ellis test.
[00:59:31.480 --> 00:59:32.360] Listen to that podcast.
[00:59:32.440 --> 00:59:33.320] We'll link to it.
[00:59:33.320 --> 00:59:39.000] Okay, next topic that I'm excited to get your take on is game design versus gamification.
[00:59:39.000 --> 00:59:43.080] This is one of the more unique ways you think about designing product.
[00:59:43.080 --> 00:59:48.160] And when people hear you talk about this, they think it's like, oh, gamification, making things like games, oh, Zynga, Farmville.
[00:59:48.160 --> 00:59:49.120] I don't want to do that.
[00:59:44.840 --> 00:59:55.760] But you actually have a really different perspective on how to make, why you need to think about game design as you design products.
[00:59:55.760 --> 00:59:57.520] Talk about your insights there.
[00:59:57.840 --> 01:00:09.440] Yeah, well, I strongly believe that we should make business software like we make games because when we make products like we make games, people find them fun.
[01:00:09.440 --> 01:00:10.880] They tell their friends.
[01:00:10.880 --> 01:00:12.240] They fall in love with them.
[01:00:12.240 --> 01:00:18.320] It's another way actually of backing into where we opened this conversation, which is you're making a brand.
[01:00:18.320 --> 01:00:20.240] You're giving reason for word of mouth.
[01:00:20.240 --> 01:00:24.560] It's actually an altogether different kind of product development.
[01:00:24.560 --> 01:00:26.080] So how do we do this?
[01:00:26.080 --> 01:00:28.560] Well, as you've said, it's not gamification.
[01:00:28.640 --> 01:00:30.160] That doesn't work.
[01:00:30.160 --> 01:00:33.920] Game design works, but game design is not gamification.
[01:00:33.920 --> 01:00:40.400] It's not, for example, simply taking your product and adding points, levels, trophies, or badges.
[01:00:40.400 --> 01:00:46.640] And to understand why gamification does not work, we actually have to start with human motivation.
[01:00:46.640 --> 01:00:52.640] And there's a very interesting study from Stanford, I think, that demonstrates the difference perfectly.
[01:00:52.640 --> 01:00:58.880] In the 1970s, these Stanford researchers recruited children who were aged three to four years old.
[01:00:58.880 --> 01:01:02.640] And all of these kids were generally pre-interested in drawing.
[01:01:02.640 --> 01:01:07.600] Some kids were told they would get a reward, a certificate, with a gold seal and a ribbon.
[01:01:07.600 --> 01:01:12.640] And some kids were not told about any reward and they did not even expect one or didn't know of one.
[01:01:12.640 --> 01:01:18.160] Now, each child was then invited into a separate room to draw for six minutes.
[01:01:18.160 --> 01:01:21.280] And afterwards, they would either get the reward or not.
[01:01:21.600 --> 01:01:29.120] And over the next few days, the children were observed to see how much they would continue to draw by themselves.
[01:01:29.120 --> 01:01:35.400] So the children with no reward, they spent 17% of their time drawing.
[01:01:35.720 --> 01:01:42.760] But the children who expected a reward, sadly, they only spent 8% of their time drawing.
[01:01:42.760 --> 01:01:46.840] The very presence of a reward halved their motivation.
[01:01:46.840 --> 01:01:48.120] So what's happening?
[01:01:48.120 --> 01:01:54.040] What's happening here is researchers differentiate intrinsic motivation and extrinsic motivation.
[01:01:54.040 --> 01:01:59.160] With intrinsic motivation, we do things because they are inherently interesting and satisfying.
[01:01:59.160 --> 01:02:04.760] And with extrinsic motivation, we do things to earn rewards and to achieve external goals.
[01:02:04.760 --> 01:02:09.720] And that's the problem with rewards, is they just massively undermine intrinsic motivation.
[01:02:09.720 --> 01:02:11.880] And that's why gamification doesn't work.
[01:02:11.880 --> 01:02:18.920] And when gamification does work, it's because the underlying experience was already designed like a game.
[01:02:19.080 --> 01:02:21.880] What makes something, I guess, like a game?
[01:02:21.880 --> 01:02:26.360] I know Superhuman is really good at this, of just like your inbox zero quest that you're on.
[01:02:26.360 --> 01:02:29.080] I guess just to make that a little more real, what is game design?
[01:02:29.080 --> 01:02:29.880] What does that mean to you?
[01:02:29.880 --> 01:02:31.960] Like, what makes it feel like a game?
[01:02:31.960 --> 01:02:39.240] Well, many folks don't know this, but before I was a founder, you can probably tell, I was actually a professionally a game designer.
[01:02:39.240 --> 01:02:43.400] And as it turns out, there is no unifying theory of game design.
[01:02:43.400 --> 01:02:51.400] To create games, what we need to do is draw upon the arts and the science of psychology, mathematics, storytelling, interaction design.
[01:02:51.400 --> 01:02:57.320] And at Superhuman, we've identified five key areas that we really care about.
[01:02:57.320 --> 01:03:01.400] Goals, emotions, toys, controls, and flow.
[01:03:01.400 --> 01:03:05.240] And across these, we've identified many principles of game design.
[01:03:05.240 --> 01:03:12.360] And one example principle would be: make fun toys and then combine those into games.
[01:03:12.360 --> 01:03:16.960] So, a question I like to ask is, are toys the same as games?
[01:03:17.120 --> 01:03:18.640] They do seem different.
[01:03:14.520 --> 01:03:23.840] For example, we play with toys, but we play games.
[01:03:23.840 --> 01:03:27.120] A ball is a toy, but football is a game.
[01:03:27.120 --> 01:03:31.360] And as it turns out, the best games are constructed out of toys.
[01:03:31.360 --> 01:03:31.920] Why?
[01:03:31.920 --> 01:03:36.240] Because then they are fun on both levels: the toy and the game itself.
[01:03:36.240 --> 01:03:42.880] So, for example, in Superhuman, one of our favorite toys is the time autocompleter.
[01:03:42.880 --> 01:03:48.880] If you use Superhuman, this is the thing that appears when you hit H, when you snooze or set reminders on emails.
[01:03:48.880 --> 01:03:50.480] You can type whatever you want.
[01:03:50.480 --> 01:03:53.520] It can be gibberish, and it does its best to understand you.
[01:03:53.520 --> 01:03:59.760] For example, if you type in 2D, that becomes two days, 3H is three hours, 1MO is one month.
[01:03:59.760 --> 01:04:06.160] And the Time Autocompleter is fun because it indulges your playful exploration.
[01:04:06.160 --> 01:04:11.200] In onboardings, it wasn't long before I saw people asking, what can it do?
[01:04:11.200 --> 01:04:12.080] Where does it break?
[01:04:12.080 --> 01:04:13.280] How does it work?
[01:04:13.280 --> 01:04:16.480] What happens if I keep on typing in a series of tens?
[01:04:16.480 --> 01:04:19.120] Well, it turns out that's October the 10th at 10:10 p.m.
[01:04:19.440 --> 01:04:21.040] Or how about the series of twos?
[01:04:21.040 --> 01:04:24.640] Well, that's February the 2nd, 2022 at 2 p.m.
[01:04:24.960 --> 01:04:33.520] And then you start trying more complex inputs like in a fortnight and a day, and that works, which is a pleasant surprise.
[01:04:33.520 --> 01:04:38.400] And it's not long before you find more pleasant surprises, like time zone math happens without you thinking about it.
[01:04:38.400 --> 01:04:39.760] You can just type in 8 a.m.
[01:04:39.920 --> 01:04:42.080] in Tokyo, and it turns out that's 8 p.m.
[01:04:42.160 --> 01:04:45.280] Eastern time, and you no longer have to do the time zone math.
[01:04:45.280 --> 01:04:52.320] And then most people were really delighted to find out that if you really want, you can snooze emails until never.
[01:04:52.320 --> 01:04:55.040] I.e., you can literally type in never and the email will never come back.
[01:04:55.040 --> 01:04:59.080] And it had like a little shrug emoji at the same time.
[01:04:59.400 --> 01:05:02.520] So, you know, is this toy going to win awards?
[01:04:58.800 --> 01:05:02.920] Nope.
[01:05:03.240 --> 01:05:04.680] But is it fun?
[01:05:04.680 --> 01:05:06.680] Actually, surprisingly, yes.
[01:05:06.680 --> 01:05:11.720] So what I would encourage people to do is think about the features of their product.
[01:05:11.720 --> 01:05:15.080] Do those features indulge playful exploration?
[01:05:15.080 --> 01:05:17.640] Are they fun, even without a goal?
[01:05:17.640 --> 01:05:21.160] And do they elicit moments of pleasant surprise?
[01:05:21.160 --> 01:05:27.960] If so, you have a toy and you can combine that with other toys and actually start to build a game.
[01:05:28.280 --> 01:05:36.520] If people were to listen to this segment of the podcast, they would never guess we're talking about B2B software and email, which I love.
[01:05:36.840 --> 01:05:40.520] Let's talk about pricing strategy and your approach to pricing.
[01:05:40.520 --> 01:05:49.080] Another very contrarian approach that you guys took where you charge $30 a month for email that was free, that people don't need to pay for anywhere.
[01:05:49.080 --> 01:05:49.960] And it's worked.
[01:05:49.960 --> 01:05:51.880] And now a lot of companies are thinking of it this way.
[01:05:51.880 --> 01:05:54.520] You've even raised your prices recently.
[01:05:54.520 --> 01:05:57.960] What have you learned about pricing strategy that you think might be helpful to folks?
[01:05:58.280 --> 01:06:06.520] I always say the same thing when it comes to pricing, which is before you figure out pricing, you must first figure out positioning.
[01:06:06.520 --> 01:06:10.760] And Superhuman is the best email tool on the market.
[01:06:10.760 --> 01:06:13.400] We fortunately have the metrics to show this.
[01:06:13.400 --> 01:06:23.160] One of the cool things about selling an email tool is you can compare the 30 days prior to using Superhuman to the 30 days after, or the year before to the year after.
[01:06:23.480 --> 01:06:25.400] And we do that, obviously.
[01:06:25.400 --> 01:06:35.880] We're able to show that people get through their email twice as fast with Superhuman, that they respond one to two days faster, and that they save four hours or more every single week.
[01:06:35.880 --> 01:06:44.960] Because of that, we're very confident in saying that Superhuman is the best email tool on the market and that we're building it for high-performing teams and high-performing individuals.
[01:06:44.520 --> 01:06:47.840] In other words, we serve the high end of the market.
[01:06:48.320 --> 01:06:52.720] Once you understand your positioning, you can then move on to pricing.
[01:06:52.720 --> 01:06:59.600] And one of the best books on this is a book called Monetizing Innovation by Madhavan Ramanjam.
[01:06:59.600 --> 01:07:02.720] And Madhavan covers a lot of ways to develop pricing.
[01:07:02.720 --> 01:07:08.240] We used one of the easiest methods, which is the Van Westendorp price sensitivity research.
[01:07:08.240 --> 01:07:15.600] And in the early years, we asked, I think it was around 100 of our earliest users the following four questions.
[01:07:15.600 --> 01:07:21.440] Number one, at what price would you consider Superhuman to be so expensive that you would not consider buying it?
[01:07:21.440 --> 01:07:28.480] Number two, at what price would you consider superhuman to be priced so low that you'd be worried about its quality and you wouldn't buy it?
[01:07:28.480 --> 01:07:38.800] At number three, what price would you consider superhuman to be starting to get expensive so that it's not out of the question, but you'd have to give some thought to buying it?
[01:07:38.800 --> 01:07:44.960] And number four, at what price would you consider superhuman to be a bargain, a great buy for the money?
[01:07:44.960 --> 01:07:50.560] Now, most startups orient around price point number four.
[01:07:50.560 --> 01:07:55.600] This is especially true for greenfield opportunities, marketplaces.
[01:07:55.600 --> 01:08:05.760] You've got to set the transaction value around price point four, basically when you want as many people to sign up as is humanly possible at the top of the funnel.
[01:08:06.080 --> 01:08:12.960] But the price point that supports our best-in-class, best-in-cate position is actually the third one.
[01:08:12.960 --> 01:08:21.200] It starts to feel expensive, but then you sit down and you think about the time that you spend an email, the ROI, and you still buy it anyway.
[01:08:21.200 --> 01:08:27.520] And it turns out that the median answer for the third question was $30 per month, and that's how we picked our price.
[01:08:27.520 --> 01:08:32.280] And once we picked our price, we then do a quick gut check on market size.
[01:08:32.280 --> 01:08:40.520] You know, for example, we're a venture scale company, but at the time, the question that we had to ask is, could we grow into a billion-dollar valuation?
[01:08:40.520 --> 01:08:45.080] Well, let's assume that at that point, our valuation is 10 times our ARR.
[01:08:45.080 --> 01:08:47.480] So our ARR would have to be $100 million.
[01:08:47.480 --> 01:08:51.080] Well, that would be 300,000 subscribers at $30 per month.
[01:08:51.080 --> 01:08:55.880] And that is conservatively assuming no other ways to increase ARPU.
[01:08:56.040 --> 01:08:57.240] You mentioned price increase.
[01:08:57.240 --> 01:08:58.680] You can also go at market.
[01:08:58.680 --> 01:09:01.160] You can sell new products and so on.
[01:09:01.320 --> 01:09:09.240] We asked ourselves, without those tricks, do we think we can get to hundreds of thousands of subscribers?
[01:09:09.240 --> 01:09:11.240] And we answered emphatically yes.
[01:09:11.240 --> 01:09:13.560] And so we went ahead with that price.
[01:09:13.560 --> 01:09:14.040] Okay.
[01:09:14.040 --> 01:09:16.760] There's a couple more things I want to chat about in the time that we have.
[01:09:16.760 --> 01:09:18.280] And then I know you have to run.
[01:09:18.280 --> 01:09:20.520] One is around AI and the work you guys are doing there.
[01:09:20.520 --> 01:09:21.720] I know that's been a big unlock.
[01:09:21.720 --> 01:09:24.520] And then two, the stuff you're doing in enterprise.
[01:09:24.520 --> 01:09:29.080] And then if we have time, there's a question I want to ask that I think is a really interesting way you guys operate.
[01:09:29.080 --> 01:09:30.760] So let's talk about AI first.
[01:09:30.760 --> 01:09:35.560] It feels like there's this being in the right place at the right time.
[01:09:35.560 --> 01:09:43.000] It feels like you guys, like, we've been building this for a while, and then AI just unlocked another stage in what you're able to do with email.
[01:09:43.000 --> 01:09:52.200] I guess just talk about what you've done and how you think about AI integrating into what you're doing, how it's enabled you to kind of take off again.
[01:09:52.520 --> 01:09:59.240] It's true that sometimes startups boil down to being in the right place at the right time.
[01:09:59.240 --> 01:10:03.720] And we actually had a massive AI launch recently, about two weeks ago.
[01:10:03.720 --> 01:10:08.680] But even before then, we had multiple flagship AI features.
[01:10:08.680 --> 01:10:14.520] Our first AI feature was write with AI, jot down a few words, and we'll turn them into a fully written email.
[01:10:14.520 --> 01:10:17.440] We actually match the voice and tone in the emails you've already sent.
[01:10:17.440 --> 01:10:24.000] So unlike Copilot, unlike Gemini, unlike basically every other email app, the email sounds like you.
[01:10:24.320 --> 01:10:28.640] And this AI feature is way more popular than I expected it to be.
[01:10:28.640 --> 01:10:33.760] On average today, users are using it 37 times per week.
[01:10:33.760 --> 01:10:40.320] Number two, our next AI feature was auto-summarize, which shows a one-line summary above every conversation.
[01:10:40.320 --> 01:10:43.120] And as new emails arrive, it updates instantly.
[01:10:43.120 --> 01:10:46.160] Again, unlike Copilot and Gemini, it's pre-computed.
[01:10:46.160 --> 01:10:51.600] One of the things we do is we go above and beyond to make these features really premium and feel amazing.
[01:10:51.600 --> 01:10:56.080] The next AI feature after that was instant reply.
[01:10:56.400 --> 01:11:02.240] Imagine waking up to an inbox where every email already has a draft reply.
[01:11:02.240 --> 01:11:04.720] You would simply edit and then send.
[01:11:04.720 --> 01:11:08.000] And sometimes you wouldn't even need to edit.
[01:11:08.000 --> 01:11:19.680] And I can share, because we just finished this analysis, that over 2024, the percentage of emails that are AI written and sent with Superhuman has grown four times just in one year.
[01:11:20.480 --> 01:11:25.200] Then if I remember correctly, the feature after that was Ask AI.
[01:11:25.200 --> 01:11:34.960] Email, of course, is this treasure trove of critical information, things like project statuses, customer communication, meeting updates, deal execution, and so much more.
[01:11:34.960 --> 01:11:40.000] And for over 40 years, we've had to rely on what we hilariously call search.
[01:11:40.000 --> 01:11:47.120] You have to remember senders, guess keywords, scan subject lines, and now you can just ask, where is the Q1 off-site?
[01:11:47.120 --> 01:11:49.680] Or what are my flight details?
[01:11:49.680 --> 01:11:56.880] Or what is the top five most positive customer responses to the Ask AI launch?
[01:11:56.880 --> 01:12:08.920] A task, by the way, which previously used to take me 20 or 30 minutes to read through all the emails and then create that report, now happening in less than five seconds.
[01:12:08.920 --> 01:12:13.080] And recently, we, like I said, announced our biggest evolution yet.
[01:12:13.080 --> 01:12:15.800] And Superhuman AI is constantly helping you.
[01:12:15.800 --> 01:12:17.400] It's organizing your inbox.
[01:12:17.400 --> 01:12:19.960] It's also making sure you never drop the ball.
[01:12:19.960 --> 01:12:23.320] So we have things that we call auto labels.
[01:12:23.320 --> 01:12:29.240] You can now write a short prompt like job applications or requests to review work.
[01:12:29.560 --> 01:12:36.440] And you can then immediately see when emails match that prompt when people apply for a job or they ask you to review work.
[01:12:36.440 --> 01:12:42.760] With auto reminders, if your email needs a response, Superhuman will now automatically set a reminder.
[01:12:42.760 --> 01:12:44.520] You don't have to remember to do that.
[01:12:44.520 --> 01:12:46.360] Then you'll never drop the ball again.
[01:12:46.360 --> 01:12:49.160] All you need to do is hit send.
[01:12:49.160 --> 01:12:59.560] With auto drafts, Superhuman will now automatically draft your follow-up emails for you and will soon be drafting replies to basically every email that needs a response.
[01:12:59.560 --> 01:13:09.080] And finally, with what we call workflows, you can now turn email into repeatable, automated workflows.
[01:13:09.080 --> 01:13:19.320] For example, I often get emails from people who are interested in working at Superhuman, and I would normally reply to that candidate, and I would let them know that the team will take a look.
[01:13:19.320 --> 01:13:28.120] I'll then forward the original message, including any resume or any letter, to our head of people in operations and ask her to reach out if interested.
[01:13:28.120 --> 01:13:32.120] With workflows, I can now automate this entire process.
[01:13:32.120 --> 01:13:37.160] And you can imagine sort of creating a little flowchart of what has to happen.
[01:13:37.480 --> 01:13:45.280] Not only does that save a huge amount of time, with workflows, you don't even have to be in your inbox.
[01:13:44.760 --> 01:13:47.600] In fact, you don't even have to be working.
[01:13:47.920 --> 01:13:53.360] You could be on vacation while superhuman AI is working for you.
[01:13:53.680 --> 01:13:55.440] This sounds like product market fit to me.
[01:13:55.440 --> 01:13:56.800] This all sounds wonderful.
[01:13:56.800 --> 01:13:58.080] Like it just makes sense.
[01:13:58.080 --> 01:14:06.720] This is the stuff we've been promised: our underwater cities and flying cars and then just email that just works magically and replies for us and all these things.
[01:14:06.960 --> 01:14:08.720] So I love all these things you're doing.
[01:14:08.720 --> 01:14:25.120] For folks that are building with AI, I'm curious to just, what's maybe been the biggest surprise, either good or bad, building so deeply on top of AI models that you think might be helpful for folks to just like, watch out for this or, hey, check this out.
[01:14:25.440 --> 01:14:36.400] I think for me, the biggest surprise has been how unpredictable the user love has been in terms of what they love and what they don't love.
[01:14:36.400 --> 01:14:38.880] For example, Write with AI.
[01:14:40.480 --> 01:14:42.240] This sounds like a commodity feature.
[01:14:42.240 --> 01:14:43.840] And on surface level, it is.
[01:14:43.840 --> 01:14:47.920] Every email app, every writing surface has a Write with AI feature in.
[01:14:47.920 --> 01:14:50.240] I would wager ours is the best at emails.
[01:14:50.240 --> 01:14:52.480] And surprisingly, that's what we do.
[01:14:53.120 --> 01:15:00.320] But the surprising thing was just how much people love it and how often it gets used.
[01:15:00.320 --> 01:15:06.960] 37 times per user per week is still mind-blowing to me.
[01:15:07.600 --> 01:15:08.960] I had not expected that.
[01:15:08.960 --> 01:15:11.040] So that's the most surprising thing.
[01:15:11.040 --> 01:15:20.960] And on the flip side, there were certain AI features where I did expect a ton of usage, but we didn't quite get the usage that we were perhaps hoping for.
[01:15:20.960 --> 01:15:30.920] And hopefully, I'm not an AI Kramer, but basically, everything I thought would work out well, people use it less than I thought they did, and everything where I was like, I don't know, but let's build the thing.
[01:15:29.600 --> 01:15:32.120] People love that.
[01:15:32.360 --> 01:15:37.480] So maybe I should just create an anti-me to do AI roadmapping.
[01:15:37.800 --> 01:15:39.320] That's in a simple agent right there.
[01:15:39.320 --> 01:15:41.240] Whatever Rahul says, do the opposite.
[01:15:41.240 --> 01:15:41.720] Yeah.
[01:15:42.040 --> 01:15:44.360] Okay, another, maybe a last topic.
[01:15:44.360 --> 01:15:47.080] I know that you guys are starting to move into the enterprise.
[01:15:47.080 --> 01:15:52.040] When people think of superhuman, they think of just, you know, it's like consumer-y, it's like for people.
[01:15:52.040 --> 01:15:56.040] And you guys are doing a lot of work to make it a B2B enterprise product.
[01:15:56.040 --> 01:16:06.600] For founders, maybe that are starting to think about this, transitioning from PLG to sales-led and B2B enterprise-y, what have you learned about just what it takes to get to that point?
[01:16:06.600 --> 01:16:10.280] And just what does that sales motion look like for you guys?
[01:16:10.600 --> 01:16:18.920] In some ways, it's very like selling to prosumers, except these users are not coming from Gmail where prosumers would normally come from.
[01:16:18.920 --> 01:16:20.440] They're coming from Outlook.
[01:16:20.440 --> 01:16:24.760] And Outlook users have very different expectations to Gmail users.
[01:16:24.760 --> 01:16:36.920] For example, Outlook users expect their email app to also be a fully featured calendar app, whereas Gmail users are happy with those two things being entirely different.
[01:16:36.920 --> 01:16:44.200] So as a result, we've invested in calendar very heavily and we continue to do so.
[01:16:44.200 --> 01:16:47.800] And there's only so much I can say that, but it's pretty exciting.
[01:16:50.600 --> 01:17:03.960] Outlook users are also used to certain safeguards, like if you've used Outlook in an enterprise, warnings when a recipient is external to your domain or what Outlook users might know as sensitivity labels.
[01:17:03.960 --> 01:17:09.720] And as a result, we've built support for external recipient indicators and sensitivity labels.
[01:17:09.720 --> 01:17:15.000] But in some ways, it's very different to selling to prosumers because there are other stakeholders involved.
[01:17:15.040 --> 01:17:22.240] For example, we've built support for enterprise mobile management by implementing Microsoft InTune.
[01:17:22.240 --> 01:17:28.880] We recently sold one of the big three strategy consulting firms, which is super exciting.
[01:17:28.880 --> 01:17:36.320] I can't say which one, but they love Superhuman and they have thousands of people internally using Superhuman.
[01:17:36.320 --> 01:17:43.520] But we, and this is after a year, they've been piloting for a year and then accelerating over the last few months.
[01:17:43.520 --> 01:17:59.600] We only just got them the mobile app, believe it or not, because at an enterprise like that, there are significant controls on what a allowed, compliant mobile app can and cannot do.
[01:17:59.600 --> 01:18:10.160] For example, IT needs to be able to control which apps can save attachments or which apps you can copy and paste text into from email.
[01:18:10.160 --> 01:18:13.680] And for many enterprises, those controls are super important.
[01:18:14.000 --> 01:18:14.400] Wow.
[01:18:14.400 --> 01:18:14.720] Okay.
[01:18:14.720 --> 01:18:20.960] So it sounds like essentially just building all these features that large companies need is kind of the road you're on right now.
[01:18:21.280 --> 01:18:21.760] Exactly.
[01:18:21.760 --> 01:18:29.120] And there's two stakeholders: there's the users, which are actually quite different because they're Outlook users, and Calendar is one of the main ways that manifests.
[01:18:29.120 --> 01:18:30.800] And there's a whole bunch of other stakeholders.
[01:18:30.800 --> 01:18:33.920] IT is one of them, but there are others as well.
[01:18:33.920 --> 01:18:42.240] For example, companies this large have workplace management groups who want to see analytics of how people are working, how they can make their teams more efficient.
[01:18:42.240 --> 01:18:46.960] And so it truly is a multi-threaded sale with multiple stakeholders.
[01:18:47.440 --> 01:18:55.920] We had a linear on the podcast, the head of product from Linear on the podcast, Non, and he actually, I don't know if you heard that episode, but he talks about how they decide what to prioritize.
[01:18:55.920 --> 01:19:02.680] The thing they never build is middle managers needing to track how their reports are doing and things like that.
[01:19:02.680 --> 01:19:06.440] So that's an interesting opportunity for you guys, maybe, to cut stuff.
[01:18:59.680 --> 01:19:06.840] I don't know.
[01:19:07.080 --> 01:19:08.840] Anyway, I want to end on one more nugget.
[01:19:08.840 --> 01:19:10.440] Okay, I'm glad we have time for this.
[01:19:10.440 --> 01:19:15.560] So you shared that you have this system internally at Superhuman for making decisions.
[01:19:15.560 --> 01:19:19.080] You call it single decisive reason.
[01:19:19.800 --> 01:19:20.840] SDR.
[01:19:20.840 --> 01:19:21.960] What is that?
[01:19:22.600 --> 01:19:30.200] SDR is a thinking tool that I picked up from Reid Hoffman during my time at LinkedIn.
[01:19:30.200 --> 01:19:39.480] And the idea here is that for important decisions, you should be able to identify one, one reason that on its own supports the decision.
[01:19:39.480 --> 01:19:48.200] And it's based on the observation that all too often we rely on a collection of weak reasons to justify decisions.
[01:19:48.200 --> 01:19:50.120] And it's very, very easy to do this.
[01:19:50.120 --> 01:19:52.440] Imagine you're contemplating a decision.
[01:19:52.440 --> 01:19:55.080] You write a list of the pros and the cons.
[01:19:55.080 --> 01:19:58.840] There are three pros, but let's say there are 10 or 15 cons.
[01:19:59.160 --> 01:20:08.920] The sheer number of cons, the efforts of thinking them through, the time it took to write them down, is going to affect you, consciously or worse, subconsciously.
[01:20:08.920 --> 01:20:17.080] And this is especially true I've seen in group settings, which just in general are a little bit more risk-averse and a little bit more consensus-driven.
[01:20:17.080 --> 01:20:29.240] So whenever anyone is making a decision, and they bring that decision to me, and they say, well, we want to do this because of XYZ, and there are multiple reasons, I've asked them, what's the SDR?
[01:20:29.560 --> 01:20:32.440] What's the single decisive reason?
[01:20:32.440 --> 01:20:37.800] If they can't yet isolate it, that tells me they haven't yet figured out why they want to make the decision.
[01:20:37.800 --> 01:20:39.480] It doesn't mean the decision is wrong.
[01:20:39.480 --> 01:20:44.680] It just means that they haven't figured out the singular reason why we should do the thing.
[01:20:44.800 --> 01:20:50.800] They can then go through their list of reasons and ask, is this alone enough to support this decision?
[01:20:50.800 --> 01:20:54.080] Meaning, if this was true and all the other things were not true, would I still do it?
[01:20:54.080 --> 01:20:57.520] And sometimes we still do, but actually sometimes we don't.
[01:20:57.520 --> 01:21:11.040] And we realize that a collection of weak reasons alone means that, for example, the outcome is less likely than we thought it was, or it was hiding a really strong reason on the other side of the decision.
[01:21:11.360 --> 01:21:12.480] That is very cool.
[01:21:12.480 --> 01:21:20.320] So this is just when someone comes to you with a decision, the way you use this idea is you ask them, what's the single decisive reason?
[01:21:20.640 --> 01:21:21.840] Pretty much, yeah.
[01:21:21.840 --> 01:21:26.720] And what they can't do, I mean, obviously this happens, people are human and natural.
[01:21:26.720 --> 01:21:30.560] They'll usually start mentioning three or four things, and that's fine.
[01:21:30.560 --> 01:21:37.120] And then I will say, okay, but if only one of those was true and you're still advocating for this decision, what is it?
[01:21:37.440 --> 01:21:39.840] And I think that's just a bar for a good decision.
[01:21:40.320 --> 01:21:41.600] Why is that so important?
[01:21:41.600 --> 01:21:50.160] Because you found that just like a bunch of low-quality reasons just don't add up to a good reason to do something.
[01:21:50.480 --> 01:21:53.520] Multiple reasons, which is ironic.
[01:21:53.520 --> 01:21:57.040] But that's my SDR for why SDRs work, which is yes.
[01:21:57.360 --> 01:22:04.960] Multiple low-quality reasons rarely add up to a high-quality reason to do something.
[01:22:04.960 --> 01:22:09.760] But there are also other things as well, which is any decision you take has an opportunity cost.
[01:22:09.760 --> 01:22:12.960] Any feature you build is another feature that you didn't build.
[01:22:12.960 --> 01:22:20.240] And if we're going to build this for a collection of weak reasons, whereas we could build that for one strong reason, I'd much rather build that for one strong reason.
[01:22:20.240 --> 01:22:24.800] Now, this is all other things being equal, and these things often end up being quite complicated.
[01:22:24.800 --> 01:22:27.200] But you can apply SDR all the way down.
[01:22:27.200 --> 01:22:28.320] I mean, you just did that to me.
[01:22:28.320 --> 01:22:30.040] What's my SDR for SDR?
[01:22:31.000 --> 01:22:32.520] There we go.
[01:22:29.680 --> 01:22:36.840] Rahul, is there anything that we haven't covered that you wanted to cover?
[01:22:37.000 --> 01:22:43.160] Is there any last piece of wisdom you want to leave listeners with before we let you go?
[01:22:43.800 --> 01:22:45.320] I feel good.
[01:22:45.320 --> 01:22:47.720] So I think we covered a lot.
[01:22:47.720 --> 01:22:49.720] Thank you for asking amazing questions.
[01:22:49.720 --> 01:22:50.920] This is really fun.
[01:22:50.920 --> 01:22:51.800] This was incredible.
[01:22:51.800 --> 01:22:55.240] Okay, so let me just ask you this then: where can folks find you online?
[01:22:55.240 --> 01:22:57.000] Where can they check out Superhuman?
[01:22:57.000 --> 01:22:59.640] What should they know before they try it out?
[01:22:59.640 --> 01:23:01.880] And then just how can listeners be useful to you?
[01:23:02.200 --> 01:23:05.400] If you want to find me online, I'm generally on X.
[01:23:05.400 --> 01:23:10.600] That is X.com/slash Rahul Vora, R-A-H-U-L-V-O-H-R-A.
[01:23:10.600 --> 01:23:11.880] And my DMs are open.
[01:23:11.880 --> 01:23:13.480] So feel free to ping me.
[01:23:13.480 --> 01:23:16.200] If you're going to do that, I would suggest also emailing me.
[01:23:16.200 --> 01:23:20.120] That's rahul at superhuman.com.
[01:23:20.440 --> 01:23:22.920] And hopefully I'll see your message soon.
[01:23:22.920 --> 01:23:27.480] If you haven't tried Superhuman, then gosh, what are you doing?
[01:23:27.480 --> 01:23:33.880] This is my call to you to do so because your time is worth more than whatever you think it might be.
[01:23:33.880 --> 01:23:37.960] So go download Superhuman, give it a shot, invite your team.
[01:23:37.960 --> 01:23:39.240] The metrics are real.
[01:23:39.240 --> 01:23:50.440] I know they sound like the kind of metrics that startups make up, but getting through your email twice as fast, responding one to two days sooner, saving four hours or more every single week.
[01:23:50.440 --> 01:23:51.640] They're all real.
[01:23:51.640 --> 01:24:03.560] Actually, speaking of which, the consulting firm I mentioned earlier, because they're so into data and into analysis, they wanted to corroborate those numbers for themselves.
[01:24:03.560 --> 01:24:04.360] And so they did.
[01:24:04.360 --> 01:24:13.880] They ran their own internal case study on Superhuman and they were like, yeah, you're saving our partners 3.3 hours per person per week.
[01:24:13.880 --> 01:24:18.240] And there's only one other tool that we've bought that does that, which is ChatGPT.
[01:24:18.240 --> 01:24:18.960] So thank you.
[01:24:18.960 --> 01:24:19.760] We love Superhuman.
[01:24:19.760 --> 01:24:20.640] We're rolling it up.
[01:24:20.640 --> 01:24:25.200] If that sounds interesting to you or your company, please do give it a shot.
[01:24:25.200 --> 01:24:26.720] That is super cool.
[01:24:27.040 --> 01:24:35.440] Reflecting back on what I imagined this conversation would look like, a lot of contrarian thinking and attention to detail, I think that's exactly what it was.
[01:24:35.440 --> 01:24:36.640] Ruli, you're awesome.
[01:24:36.640 --> 01:24:38.720] Thank you so much for being here.
[01:24:38.720 --> 01:24:39.760] Bunny, thank you.
[01:24:39.760 --> 01:24:40.560] Bye, everyone.
[01:24:40.720 --> 01:24:42.000] Bye, everyone.
[01:24:43.280 --> 01:24:44.800] Thank you so much for listening.
[01:24:44.800 --> 01:24:51.200] If you found this valuable, you can subscribe to the show on Apple Podcasts, Spotify, or your favorite podcast app.
[01:24:51.200 --> 01:24:57.520] Also, please consider giving us a rating or leaving a review, as that really helps other listeners find the podcast.
[01:24:57.520 --> 01:25:02.880] You can find all past episodes or learn more about the show at lennyspodcast.com.
[01:25:02.880 --> 01:25:05.120] See you in the next episode.