#13 - Scaling Growth - Gustaf Alstromer, Ed Baker, and Josh Elman
23 Jun 2017 · 35 min
Gustaf Ahlströmer, Ed Baker, and Josh Elman discuss how growth teams evolved from viral hacks like the Zodiac Photo Album to data-driven organizations. They explain how Facebook, Uber, and Airbnb each picked a North Star metric, built cross-functional teams, and shifted focus from pure acquisition to retention and engagement.
Chapters
Hey, this is Craig Cannon and you're listening to Y Combinator's podcast. Today's episode is about scaling growth. It's a conversation between Gustaf Ahlströmer, Ed Baker, and Josh Elman. Gustaf is a YC partner and prior to that he worked on growth at Airbnb. Ed worked on growth at Uber and Facebook, and Josh is a partner at Greylock. The conversation was recorded at the Scale-Up Offsite, a private event hosted by Y Combinator Continuity and Greylock Partners in April 2017. Okay, here we go.
What's pretty cool is we have 2 guys who've been living the center of building up these growth teams for the past 7 or 8 years. Ed joined Uber to start the growth team when it was 5 people, and then over the 3.5 years became VP of both product and growth for all of Uber. Gustav joined, and the Airbnb growth team was him and 2 other people. when he got started a few years ago, and that has scaled to over 100. So it's fun at a Scale-Up offsite to talk about scaling. We've mostly been talking about scaling organizations. This is a chance to talk about how do you scale the organization that continues to scale your users. What's fun for me is I've known Ed and Gustav now for most of a decade kind of in this growth world, and we were all started back when sort of this idea of a growth team, this idea of a team that's focused on this sort of intersection of product and marketing to build stuff was pretty novel and almost didn't even really exist. And we were all kind of doing it in the social world. And I remember Ed started a company in 2008 called, you know, Friend.ly. There was Domingo and then Friend.ly. You know, Gustav started a company in 2007 called Heyson and then went over to Voxer. And these were like, how do we get to like millions of users in the early days? So I'm curious if you could just kind of talk about this heyday of social viral growth explosion. And sort of what are some of the key kind of crazy things you learned then that have really helped you as you think about growth today? Adam, if you want to start.
Sure. So yeah, I guess 2007, summer of 2007, when Facebook launched the platform, was I think part of that explosion of just crazy viral growth, spammy apps on the Facebook platform. That was actually the first— those were the first apps I built that reached tens of millions of users within months' time. And I think it was a great platform on which to just experiment with a lot of different ideas because it was so easy to build these simple Facebook apps and just run lots of A/B tests. And so much of, I think, figuring out how to grow something is— it's a combination of an art and a science. And by running lots of experiments, you start to build an intuition for the types of things that work and don't work. That's great.
What were some of the early tricks you found that made you go super viral? You were pretty famous back in those days.
Yeah, I mean, you were at Facebook back then, right? So I think Facebook created new rules after I found some loopholes.
Almost often, yes.
There was one I remember. I think the most viral Facebook app— I'm hesitant to even admit this, but it was called Zodiac Photo Album. And the way it worked was literally with one click, it would create a photo album with 12 photos in it, one for each zodiac sign. and then show all of your friends who had that zodiac sign in each of the 12 photos and tag all of them. And I think we were allowed to tag like 20 people per photo, so it would show up to 20 of your friends per zodiac sign times 12. So with one click, you'd tag 240 friends, and all 240 people would get an email saying, Ed just tagged you in a photo. So that has a very high response rate. People kind of want to see when they're tagged in a photo. They would go, they'd see, oh, it's a Zodiac photo album, create your own at, you know, the Zodiac app. Within, I think within 24 hours, we had tagged tens of millions of people in photos.
Incredible.
I think including Zuck. And then I heard the platform team shut it down shortly after that.
Now, I wonder if those days are over of kind of those crazy viral pops. And then Gustav, you were really central to a lot of the early experimentation on mobile. I remember we first met when Voxer was blowing up, and you guys had figured out some really unique ways to blow up using notifications and inviting. Can you remind us, how did you get to this world of growth, and how did you figure out stuff in those early days, especially on mobile, which people think is a lot harder even than social was?
Before Voxer, I was at a company called HeySun, which I co-founded. product, like a messaging product on mobile that we couldn't grow. So we spent a lot of time trying to learn how to grow. When I joined Voxer a couple of years later, the first approach, the first thing I kept in mind is like, we need to think about growth. At the time, back to the early question, I think there's a couple of— growth becomes important when they have new platforms. So you have Facebook platform, you have the mobile platform, you have Google SEO, there's a bunch of larger platforms that makes people actually care about investing in them. At Voxer, the iOS platform, which key to those things were the address book and push notifications. Those are things that kind of like weren't there in the very beginning. Once they started happening, people started exploring what you can do with those things. With Voxer, when I joined, the most important thing— so Voxer was a walkie-talkie app on iOS and Android. You push a button, you start speaking on the other end. We found that the amount of friends that you have when you open the app for the very first time on the app and how you display them was actually absolutely key to whether they were going to use the app or not. So we spent basically the first year optimizing those things. Like basically, how many people do you have when you open up the app for the first time? And how do you get to a list like that right when you open the app? Well, you match phone numbers with address books. Spend a lot of time investing in matching phone numbers with address books, not that different from Facebook platform. And we kind of tried to optimize how many address books and how many phone numbers we got from people. And we're doing this in the best interest of the users. Like, you wouldn't end up using the app unless you actually saw friends on the app. So that was basically the goal. This was all in the best interest of the users, and sometimes you forget why you do things.
So Ed, I remember your company got acquired by Facebook, and you kind of jumped into a little bit more mature growth team at Facebook. You'd been kind of virally hacking and building these things on the platform. What was sort of the adjustment to go from kind of being in this sort of experimentation mode to something that was a little bit more mature? But what did you see when you observed kind of that mature Facebook growth team?
Yeah, so one thing I saw was I was finally working at a company that had an amazing product that people loved, and I had just never actually built that myself before, so that was pretty cool. And with that came amazing retention, amazing engagement. Facebook was already at a size where retention and engagement were bigger drivers of the North Star metric, MAUs, than new user acquisition. Everything I had worked on in the past was all about how do you get those first million users. At Facebook, it was how do we keep the users we've already acquired, keep them engaged, minimize churn. And to me, that was one of the biggest differences. And most of the growth team at Facebook at the time was actually focused on friending because we discovered at Facebook that friending was the number one driver of retention and engagement. So then there were teams on the Facebook growth team that were basically focused on things like PYMK, people you may know. and other ways of causing people to form more connections. So I think that was one big takeaway. The other one, we can talk about it later, is just the way the team was structured. Anu got into that a little bit, like their different functions as the team grows.
Actually, can you walk us through that? Now is actually a good time to kind of think about how was that structured, because then I want to get into this transition to these sort of different real-world companies.
Sure, sure, the real-world companies, yeah. Well, so one thing I learned at Facebook was I really liked how the growth team there was structured with all functions. So product, engineering, analytics, design, and even marketing.
Mm-hmm.
So those 5 functions were all critical to work together All within that growth org. When I was at Facebook, I think the growth team was around 500 people or so.
Oh, wow.
But across all those different functions. In fact, all of analytics back then was part of the growth team. I took a lot of those learnings when I went over to Uber and started our growth team there with just initially a 5-person team. Kind of picked one person for each function. But I think that was one of the big takeaways from Facebook.
Well, and, you know, that's a perfect transition because when I've been talking to a lot of people about sort of what the real success of Uber and Airbnb— I mean, Joe gave a great talk about sort of why Airbnb has become so important in the world— but a lot of people have said it's kind of, we took these hotels and transportation, which were sort of old-world real businesses, and applied a lot of these digital growth technology and learning to them. And so, kind of talk a little bit about what it was like going into Airbnb and starting the growth team with 2 people, and Uber and starting the little growth team. And like, what did you see there, and how did you kind of start that, this sort of practice from what you'd learned before?
Sure. So, I think the— I can't speak for Ed, but like, I think the initial idea of a growth team is that there's some function of the company that really cares about metrics. They really optimize for the goals. And some time ago, this was unusual in startups. Most people did not look at metrics when they made product decisions. They did not experiment. So instead of making everybody responsible for that, you made one team responsible for that, and that ended up being the growth team. I think really great companies today, they have everyone caring about metrics, using experimentation, and doing all those things that growth teams do to make decisions. I think things have changed a little bit, and the role of the growth team as kind of the team that evangelizes those things have changed a little bit. When I joined Airbnb, a lot of people joined at the same time that had experience from all those things. So pretty quickly I got a lot better set of tools than I had ever had at Voxer around experimentation, around support from data science. That just, I would say in some sense, made all the infrastructure of doing a growth team at Airbnb really, really easy compared to my previous experience. I learned a ton from all those people and it's been pretty incredible. But yeah, in the very beginning, we, like everyone else, had— Airbnb had always been an incredible product and as a company, we along those years have learned to identify and optimize every single step of that experience. A lot of it is, of course, offline, but of the stuff that we do online, it's a lot of things that we can do to measure and make the user experience better. That's what we've been doing. I think the role of the growth team have changed from being that evangelizing team that do all of it to evangelizing to the rest of the company so that everyone do product in a very similar way.
I'd say at Uber, there were 3 big differences from Facebook when I went over there. in terms of forming our initial growth team. So the first was it's a 2-sided marketplace. And when we came up with our North Star metric, I remember having conversations with that small team of 5, one of whom, Mike Pau, is sitting in the audience here.
Can you define North Star metric? You've used that a couple times. I think that's actually really important for sort of the growth discussion.
Definitely. So at Facebook, it was monthly active users. It's basically the one metric that If you talk to— the way I like to think about it is if I talk to anyone on the growth team and ask them what number are we trying to grow, they would be able to say it's that number. And if they're not working on something that ultimately is growing that number, they're probably working on the wrong thing.
Okay.
So that's kind of how I like to think about it. And it's helpful to set goals. We'd set every half, we'd kind of have, this is our 6-month goal, but then we'd track our progress every week and see, are we on track? And there's, of course, seasonality and stuff. It's not just a straight line.
Yeah.
But you could kind of see, like, how are we doing versus our goal? So at Uber, when we came up with our North Star metric, we had to consider there are 2 sides of the marketplace. So it's not just monthly active riders. Ultimately, we decided on trips, weekly trips, as the North Star metric. Because for every trip to take place, you need riders and you need drivers. And so by having trips as that North Star metric, you could then break that down into the supply side and the demand side. And you need more riders, more drivers, and you can do growth accounting on each side of the marketplace to say, well, to get more riders, you need more new riders, reengage churned riders, and minimize churn of your existing riders. And same thing on the driver's side. So that was one thing, was agreeing on this is our North Star metric in a 2-sided marketplace. So that was a bit different from Facebook. I'd say a second thing was because Uber is a real-world company, there were several parts of that funnel that you can't just measure online. Whereas on Facebook you can track every click, every pixel, all of that stuff. With Uber, there are steps of that funnel where it involves a driver going in and getting their vehicle inspected or uploading their documents and ultimately downloading their iPhone app, going into their car, and doing that first trip. For me, it was super eye-opening when I did my first trip as a driver. I walked out to my car. I'd done everything. I was activated. I walked out to my car. I walked back to my house because I got so nervous about doing that first trip. And that's when it suddenly hit me. This is why so many of our first— our drivers who are activated never do that first trip. So that real-world component added kind of some extra challenges in terms of, one, how do you measure it? And two, what are some things you can do to influence the way people behave in the real world? And then the— let's see, I said 3 things and now I mentioned 2. So, 2-sided marketplace, the real-world component to it, and I'll come back to the third when I remember it.
Your different North Star metric. Well, and so as these teams have scaled now, you know, way up, you know, you talk about data analytics, design, product, sort of internet marketing.
Oh, that was the third, by the way. Paid acquisition.
That's what I was going to actually ask you.
Facebook, we didn't really do very much paid acquisition, but at Uber, we had an entire performance marketing team. Well, initially it was a one-person team, but ultimately became a team where we would actually spend money to acquire both riders and drivers.
Well, actually, I was going to— that's exactly right. In our social worlds, we're all about these organic— how many people can we organically get into our products? And if we spend a dollar on user acquisition, we always seem to say a dollar too much. And, you know, the boards are like, how do you get more free virality? But I think, you know, both Uber and Airbnb, because your businesses people actually pay for, how do you think about paid acquisition differently than this sort of organic acquisition? How do you train a team to sort of understand that and think about that differently?
Do you want to start?
Sure.
So let's see, I would say A lot of those platforms that you are doing growth on, Google, Facebook, they are turning— the opportunity of doing free growth there is getting smaller and the opportunity of doing paid growth better is getting larger. So most good growth teams should invest in paid marketing. I think that, in my experience of seeing, looking at other companies, what they've been doing, large companies that do paid marketing, they tend to integrate that with the product team and the engineering team. So there are engineers and product managers supporting supporting those teams. They call it ad tech or something like that. I'm sure both Uber and Airbnb are at that stage right now where basically most of the leverage you'll have at scale is going to be through engineering, data science, and product management. That's a different world than when you start off. When you start off, you have a smaller team.
I'd say the way I think about paid acquisition is It can just further accelerate growth. Uber would have kept growing even if we had never done any paid acquisition, but especially in a competitive market, it kind of makes sense to pay up to what that rider or that driver is ultimately going to be worth. When you're in a situation where the faster you grow, the better, because as you get bigger and bigger, there are a lot of other efficiencies that kick in. So the whole network becomes more efficient once you have more liquidity. So there's value to getting there as quickly as possible. It's kind of tricky to know exactly how to calculate the LTV of a rider or a driver in a 2-sided marketplace because the riders pay the drivers and some of that money goes to Uber. So how much is a rider worth versus a driver worth? And we had a team actually focused on that exact question, a team of data scientists And it was more complicated than I understood, but basically there are certain markets that are more supply constrained where a driver, the incremental driver is worth a lot more. Other markets that at a certain time of year might be more demand constrained where you might be willing to pay more for the rider, and that varies over time and by geography.
A quick comment on that, I would say most companies that grow really, really large, they do it on figuring out one platform. So, they are really good at online marketing, they're really good at SEO, they're really good at virality or the Facebook platform or something like that. It's rare that you have like, I figured out all the platforms. So, I would think about the product that someone have, the product that you have and which of these platforms is it the most suited to. Is it most suited to search? Is it most suited to display? Is it most suited to virality? It really depends on the product, I would say.
Interesting. And where do you guys see any upside right now in sort of the marketing or growth world? I mean, it seems like a lot of these channels have gotten pretty saturated. Facebook's gotten relatively expensive to be buying on. Google's various platforms and video— I've heard a lot of people talking about video ads are sort of the new place. Even people are actually going and advertising on TV. Where do you guys just think about sort of where those growth opportunities sit out there now?
I mean, I come back to build a great product. Because if you have that product-market fit and the people using your product Love it. All of the channels are out there today that will allow people who love a product to share it with their friends. So I think that's actually the most important thing and then everything else will follow.
Yeah, I mean, I would— I don't think there's anything short-term that will remain successful for a very long time. So the best advice is invest for the long-term, whether it's SEO, whether it's paid marketing, whether it's virality. Take a couple of years to look out and see where do we want to be. Aim for— look for channels that actually do have true scale, channels that have hundreds of millions of people discovering products through those channels. Then invest for the long term. Engineering and data science is critical to be successful, in my opinion.
I'm surprised neither of you mentioned Instagram. The tip I got yesterday at F8 talking to a bunch of Facebook folks is, They think Instagram app install ads are significantly underpriced relative to Facebook. If you guys go back and start buying on Instagram, you might be surprised at how it does. One of the unique things, again, in the social viral world, we grew, scaled on the internet. You guys also have to grow city by city. What are some of the things that you did to set up teams for growth that could actually do growth in a city that could customize it for the city, or how much did you try to make it sort of a centralized playbook that you'd control from the mothership?
So, I mean, every city would have its own city team beginning with a launcher. Again, I mentioned Mike in the audience. He was a launcher, then was our general manager in Boston, and then started— basically headed up product for the growth team. So it was really valuable to have the person who was running product for growth be one of these ex-operations people. Working with all the city teams was really important in terms of just making sure that product and operations were integrated. We now have a team at Uber called Product Ops. It's basically a team that is that bridge between the product team and the operations team. As much as possible, we tried to just have a playbook. One thing that was helpful with Uber being a global business and I'm sure you guys see this as much, if not more so, at Airbnb, is when we would launch in a new city, there would already be a lot of pent-up demand. We'd see a lot of people trying to use Uber in a city before we'd launch in that city. So there were certain things we could do to kick off that flywheel. But I'll share one example of something where we actually did something very different to the product in another city, and this was back when we were in China. We found that it was hard for drivers to sign up to become Uber drivers in China because of the firewall. There were latency issues and just signing up online. A lot of drivers had phones but didn't have computers and it was just hard for them to sign up. So one of the engineers on our China growth team built a WeChat bot. WeChat is like a messenger. messaging app, or the Facebook of— sorry, the Facebook and also the internet of China, really. And so we built this WeChat bot where as a driver you could take a picture of a QR code and then it would just start asking you questions. What's your name? What's your birth date? What's your driver's license number? And people would quickly be able to sign up to become a driver. And we'd have these onboarding sessions with hundreds of drivers, if not even more than that, showing up in one room all on WeChat signing up, which was amazing until WeChat started blocking us because they were owned by Tencent, which had invested in our competitor. So that's one example of something we had to do very differently in a different market.
I would say there's 2 things I would call out. One is translation. So absolutely key to have a way that you can translate content across languages. It's often overlooked and it's like A huge growth driver. A lot of people don't speak English and need the experience that you're offering in a different language. The second thing is what I call product gaps. If you look at your product globally, there are some parts of your product that won't work in some countries, whether it's authentication like Facebook Connect, whether it's payment mechanisms, search, SEO, and just identify those gaps. There are not that many countries in my experience that are dramatically different. There are maybe 5 or 10 that are quite different than US. But most countries are not that different.
Cool.
And just last thing, because growth is all about experimentation and often experimentation against instincts, what is one great case where you and your growth team really either believed something was going to make a huge impact and then were disappointed when it didn't, or where someone just did an experiment and even you, you were like, oh, this is never going to work, and then it blew you away?
So we have actually institutionalized this thing. We call it the experiment review. Every 2 weeks, the growth team gets into a room and we show experiments that we've shipped and gotten significant results on in the last month, say. And the engineer will go on stage, show the experiment, show the control and the experiment. Before they show the answer, they'll ask the audience, what do you guys think? How many here think control? How many think experiment? And it turns out that we Most of the times we disagree, which is exactly the point you're trying to make by doing experimentation, that predicting product decisions is really tricky. I would say this happens all the time, and if it doesn't happen, then you're not taking big enough risks. You should be seeing that things are counterintuitive. Sometimes when they're very counterintuitive, having experience of seeing a lot of experimentations makes you ask the right questions. Oh, maybe the metrics is wrong this time. That happens as well.
Thank you.
But yeah, things should be really counterintuitive. I'll give one tidbit on advice. If you have a website and you have people coming to your website and you have accounts, don't log them out. Just keep people logged in for as long as you can. There's really no benefit in automatically logging people out after a couple of months, after a couple of days in terms of growth. So I would look to Amazon for some advice on how they've done things.
One thing I found interesting is often it's the small things. Smallest tweaks that can make the biggest impact. And there's not necessarily correlation between how much work you put in and how much of a step change it makes, or sometimes an inverse correlation. So I'll share one interesting example from Facebook. We were looking at the signup, basically the funnel and the viral metrics by region. And we noticed that Japan was our least viral country. And when we dug in and tried to understand why, we saw that very few new users were actually sending invites to any of their friends. And we had a small team in Japan. I spoke with the country manager there and he said, you know, people just think it's rude to send invites. So no one's going to— it's like a cultural thing, but people don't want to— intrude on their friends and send invites. So we brainstormed a bit and we decided to literally make a copy tweak. And instead of calling them invites, we called them announcements. And we would say as part of the, you know, sign-up flow, you'd import your address book to find your friends. And then instead of saying invite all your friends, we said let Facebook now announce to all of your friends that you're on Facebook and this is where they can find you. And Japan went from like our least viral country to our most viral country.
Wow.
And when Zuck saw that, he was excited and thought, why don't we do this in some other places as well? But it was literally just a copy tweak to make people more comfortable with sharing the product they were using with their friends.
That's great. I've been talking to some mobile developers that even the difference of invite versus add somebody, which is sort of vaguer, if you press— if you change your language from invite to add, people will send the SMSs out to their friends invite them to a service at a much higher rate than the word invite. So these really subtle things they don't expect. We have time for like 1 or 2 questions from the audience. Anybody has any?
There.
Mainly for Ed, you talked about the North Star and you said at Uber it was about the number of rides, but you could have easily been optimizing for crazy retention and zero growth, new user growth or new rider growth or all new rider growth and to Anu's last comment, horrible retention. So how did you balance out knowing what your almost sub-North Stars were so that you could have the best North Star, if that makes sense?
Totally. Yeah, that makes a lot of sense. And it actually changed over time. So early on, we were kind of in land grab mode where it was all about new user acquisition, new riders, new drivers. But we would look at growth accounting. So you'd say, well, the total number of active riders or active drivers equals last week's active number plus any new users you get minus any users that churned plus any users that re-engaged. And you can look at each of those 3 things, kind of the magnitude of each. And early on in the growth curve, when you're kind of at the bottom of that S-curve, the new user acquisition number is probably going to be much larger than the churn or the re-engagement. And so it makes sense to focus the most on growing that number. But as you get bigger and bigger, as your active user base gets larger, the churn as an absolute number goes up because it tends to remain a constant percentage or roughly a constant percentage of the absolute number. And then at the same time, new user acquisition gets more difficult because you've already reached out to so many new people. So if you just monitor, look at the growth accounting and kind of see those are the levers, which ones can have the biggest impact. Early on it might be new user acquisition, but later on it's probably going to be retention and re-engagement. But that said, you kind of need that retention from the beginning. Because if you're just like— I've grown plenty of things in the past that haven't had retention, and it's fun while it's going like this, but if that retention is not there, ultimately it's not really going to help.
Is that like Zodiac calendars?
Exactly, that kind of stuff.
So Ed, earlier you told a story of like the challenge of getting people to go from registering as a driver to actually like overcoming the nervousness to go out and do the first trip as a driver. I'm interested in what are some of the experiments you ran there and what you learned about how to actually get people to do that in the real world.
Yeah, definitely. Definitely. So, you know, I'll just mention one example is we saw that sometimes like a driver, a new driver would log in and might not get a trip request right away. And sometimes that driver might just be waiting for a really long time because they're a brand new driver And maybe they're waiting somewhere, maybe they are waiting in front of their house and there just isn't a bunch of stuff happening right there. Or there's another driver who's more experienced and who knows if you wait a block away from here, they're more likely to get a request. So one of the experiments we ran was, what if we make sure that that first experience is better? Are there things we can do to kind of get that driver hooked? That's one example. We also experimented with, are there ways we can get potentially existing drivers or other people to get on the phone with a driver and talk them through that first trip? The team's experimented with a bunch of different things like that.
Fritz.
Just to kind of probe on something Gustav alluded to regarding growth organizationally, do you guys think that the right steady-state outcome is for all teams to become growth-oriented and have growth people inside of them or to have a separate standalone team that's kind of fully vertically integrated? And if the latter, what conflicts have you seen between, say, marketing, who's focused on owning the homepage and the language and the brand kind of goals or lifecycle who thinks that they own retention versus growth, and likewise with product groups that feel like they own a product and customer experience that they're trying to get, with you guys kind of hacking away at that?
So I would say that ultimately the company becomes a growth team in the sense that you use data to make your decisions. You basically look at the data because it gets so hard to predict what Are the right product decisions to make, like once you make optimizations. So ultimately at Airbnb, all the larger teams are using data to validate the experiments. And that's kind of the idea of a growth team for us means where you sit in the funnel. You're at the top of the funnel, you're finding users that are not already using Airbnb. In other companies, growth teams is a smaller organization that kind of evangelizes that to the rest of the product team. But Airbnb, really the entire product team is now a growth team. The goal of the data team that had built these tools is to get everybody to use them. They are literally measured by how many people are using experimentation frameworks.
We actually merged the product team and the growth team about a year ago at Uber largely for those reasons, especially as we started focusing more on engagement and retention. within the growth team, and that's kind of what the core product team was working on as well. It just made more sense to bring it all together.
And I would just add, as you talk about your lifecycle and your homepage copy teams and everything in brand, that actually when they kind of merge together and they sort of have the orientation where really growth and marketing are sort of one thing as opposed to 2, you understand sort of everything we do is in the spirit of growth, even if it is driving our brand or other stuff. rather than trying to keep them separate and contentious, is with that merging. We have time for one more question.
Question for Ed. Uber was super aggressive in China and growing. Were there any really crazy things you guys discovered or hacks there that maybe people could use back here?
I'm sure there were, but I probably can't talk about them. I mean, not actually— I don't have any super crazy ones that are coming to mind right now, but I probably shouldn't talk about any of the stuff that worked really well, just given that we're probably still doing it if it did.
Sorry about that.
Awesome.
Well, thank you. Hopefully you'll be scaling your orgs and your user bases together. Thanks, Ed and Gustav, a lot for this.
All right.
Thanks for listening. So if you want to read the transcript or watch the video, you can check out blog.ycombinator.com. And as always, please remember to subscribe and rate the show. See you next time.
More from Josh


#119 with Josh Elman - How To Get The Benefits of Entrepreneurship Without Starting a Company



