Lecture 4 - Building Product, Talking to Users, and Growing (Adora Cheung)
Thanks for having me. Um, so today I am going to be talking about how to go from zero users to many users. Um, uh, I'm just assuming that you have many great ideas in your head at this moment, and um, you're kind of thinking about what the next step is. So I wrote this up um, early this morning, and a lot of this is based off of mistakes I've made in the past. Um, so as Sam mentioned, I went through YC in 2010 and uh spent a number of three years basically going back and forth, pivoting a bunch of times, starting over a bunch of times, um, and have learned a lot about what not to do if I were to start another startup after Homejoy, um, if that should ever happen.
A lot of it comes from failure and just telling you about what you shouldn't do, um, and kind of making generalizations of what you should do from that. So just a reminder that this is sort of, you know, all advice you should take as directionally good guidance, like it's all, it's like, it's kind of in the right direction, but every business is different, you are different, I'm not you, and so, um, just take everything with, you know, that in mind.
So since this is a college course, you know when you start a startup, you should basically have lots of time on your hand, um, to concentrate on the startup. And I'm not saying you should know quit school or you should quit work. What I'm saying is you should have a lot of time compressed, time in a row, um, really dedicated to immersing yourself in the idea and developing problems or developing the solutions to the problem you're trying to solve.
Um, so for example, if you're in school, you know, it's better to have one or two days straight per week on working on your idea versus, you know, spending 2 hours here and there every single day during the course of the week. Um, it's sort of like, I think this is in class, so uh, it's sort of like coding. Like there's a lot of context switching, and just being able to really focus, um, uh really, really focus on immersing yourself is very, very important.
So like I said, I sort of first, when I wrote this up, was thinking what are what are the things that most people do or most people do that, um, is not the correct way to do a startup? Um, and sort of the novice approach I think is what you see here, which is, you know, I have this really great idea, I don't want to tell anyone about it. I'm going to build, build, build, build. I'm going to maybe tell one or two people, and then I'm going to launch it on, you know, I'm going to launch it on TechCrunch or somewhere like that.
Um, then I'm going to get lots of users, but what really happens is because you did not get a lot of that feedback and stuff like that, you know, maybe you get a lot of people to your site, but, um, no one sticks around because you didn't get that initial user feedback. And then, you know, if you, you know, if lucky enough, you have some money in the bank, you might go buy some users, but sort of it just whittles out over time and you just give up.
It's sort of a vicious cycle, and you know, I actually did this once, and I did this while I was in YC. That was, you know, like when I went through YC, I didn't even launch a product. Like I didn't even launch in TechCrunch, which is the thing that you should definitely do. Um, and so you don't want to ever get into that cycle because, uh, you'll just end up with nothing good.
So the next thing is, uh, you know, you have an idea and you should really think about, uh, what the idea is really solving. Like, what is the actual problem? And so their problem statement should, you should be able to describe it in one sentence, and then you should think, how does that problem relate to me? Am I really passionate about that problem? And then you should think, okay, it's a problem I have. Is it a problem that other people have? And sort of verify that by, you know, just going out and talking to people.
One of the biggest mistakes I've made is, you know, we started, uh, my co-founder and I, who is also my brother, he and I started a company called Pathjoy in 2010 and our goal was basically to, you know, we had two goals in mind: one is to create a company that made people really happy and, uh, and, um, create a company that was very, very impactful. And a good proxy for that is to just create a huge, big company.
So we thought, okay, here's what we're going to solve: make people happier. And our, we first went to the notion of who are the people that made people happy? We came up with life coaches and therapists. So it seemed kind of obvious to just create a platform for life coaches and therapists.
What happened as a result though was that, you know, when we started using the product ourselves, we, you know, we're not cynical people by any means, but life coaches and therapists are just not people we would use ourselves. Um, it was sort of useless to us and so it wasn't even a problem we had and certainly wasn't something we're super passionate about building out. Yet we spent, you know, almost a year trying to do this.
If you just start, you know, from T equals Z, just like think about this before you even build any product, I think you can save yourself a lot of headache down the road from doing something you don't want to do. So say you have a problem and you're able to state it. Where do you start? Like, how do you think of solutions?
Um, so the first thing you should do is think of what the industry that you are getting yourself into. Um, whether it's big, whether it's huge, you should really immerse yourself in that industry. And there's a number of ways to do this. One is, you know, to really become a cog in that industry for a little bit. And so it might seem a little counterintuitive to do this because most people say, you know, if you really want to disrupt an industry, you should really not be this, you know, player in it.
You should, you know, it, you know, someone who's spent 20 or 30 years in an industry probably does, you know, sitting their ways and is just used to the way things work and really can't think about what the inefficiencies are, the things that you can "quote unquote" disrupt. But however, as a new, like coming into the industry, you really should take, you know, one or two months just really understanding what all the little bits and pieces of the industry are and how it works.
Um, because it's when you get into the details, that's when you start seeing things you can exploit, things you can really, things that are really, really inefficient and provide, you know, huge overhead costs that you can cut down. Um, and so an example of this is, you know, when we started at Homejoy, we, we, we decided to go, we started with the cleaning industry. And when we started, you know, we just were cleaners ourselves and we started to clean houses. And what we found out really quickly was that we were very, very bad cleaners.
Um, and so as a result, you know, we said, okay, we got to learn more about this and we went to buy books. Um, and, uh, we bought books about how to clean, which helped maybe a little bit. We learned a little bit more about cleaning supplies. Um, but it's sort of like basketball, you know, you can watch and you can learn or you can watch and read about basketball, but you're not going to get better at it if you don't actually, you know, train and, you know, throw back a basketball round and throw into the hoop.
And so we decided one of us basically had to go and learn how to clean. And so we went, um, or get trained by, you know, a professional, some sort of professional training program if that existed. And that meant we actually went to get a job at a cleaning company itself. And the cool thing was that, you know, I learned how to clean, um, from, you know, training for the few weeks that I was there at the cleaning company, but the even better thing was that I learned a lot about how a local cleaning company worked.
And in that sense, you know, I learned why a local cleaning company could not become huge like Homejoy is today. Uh, and that's because they have, you know, they're pretty old school and they have a lot of things, um, just from anywhere from booking the customer to, um, optimizing the cleaner schedules, uh, was just done very inefficiently. And so there's, so, so, so, when you go, if you are in a situation like mine, where you know there's a service, there's a service element of it, you should go and do that service yourself.
You know, if you work, if your thing is related to restaurants, you should become a waiter. If, if, if it's related to, you know, painting, you know, become a painter and kind of get in the shoes of your customers, um, from all angles of what you're trying to build. Uh, the other thing is there's also a level of obsessiveness that you should have with it too, as well. Like, you should, you should be so obsessed to know like what everybody in the space is doing.
And it's things like, you know, running a list of all the potential competitors or similar types of companies, um, Google searching it and clicking on every single link and reading every single article from like search result number one to 1000. You know, I found, um, all potential competitors big and small, and if they're public, I would go read their S1. I would go, I would go read all their quarterly financials. I would, you know, sit on the earnings calls.
Um, there's, you know, most of these you don't get much out of it, but there's just these golden nuggets that you'll find once in a while and you, you won't be able to find that unless you actually go through the work of, you know, getting all that information in your head. Um, so yeah, you should become an expert in the industry. Um, there should be no doubt, uh, when you're building this that you are the expert so that people trust you when you're building this product.
The second thing is identifying customer segments. So, you know, ideally at the end of the day, in the endgame you've built a product or a business that everybody in the world is using, uh, but realistically, like in the beginning, you kind of want to corner off a certain part of the customer base so that you can really optimize for them. And that's just, you know, it's just a matter of focus and a matter of, you know, just, you know, catering towards whether it's teen girls or whether it's, you know, soccer moms.
Um, you'll just be able to, you know, like I said, focus a lot on their needs. And lastly, um, before you create the product, before you put code down, you should really storyboard out the ideal user experience of how you're going to solve the problem. Um, and that, and that's not just meaning, you know, the website itself. It's meaning, you know, how does the customer find out about you? You know, whether it's, you know, it could be through an ad or, through a word of mouth or whatever.
So they find out about you, they come to your site, they learn more about you. What's all that text say? What are you communicating to them to the actual when they sign up for the product or they purchase the service? What are they actually getting to? After they finish using the product or act, after they finished using the service, what's, you know, they're sort of like an evaluation period, like they leave a review or, or they leave comments or whatnot.
Just being able to, uh, go through that whole flow and visualize in your head like just envision what the perfect user experiences, um, and then put it down on paper and then put it into code and then start from there. Um, so you have all these ideas in your head, now you kind of know what the core customer base you want to go after is, and you know like everything about the industry. What do you do next?
So you start building your product. Um, and you know, the common phrase that most people use today is like you should build a minimal Viable product, and I underlined viable because I think a lot of people skip that part. Um, and they just go out with a feature and then the whole user experience in the very beginning, um, like is flat. So minimal viable product, viable product pretty much means you know what is the smallest feature set that you should build, um, to solve the problem that you're trying to solve.
Um, I think if you go through the whole storyboard experience you can kind of figure that out very quickly. Um, but again, you have to be talking to users, right? You have to potential user, you have to be seeing what exists out there already and what you should be building to solve their immediate needs. Um, and the second thing is before you put in things in front of a user, you should really have your product a simple, you know, product positioning down.
And what I mean by that is that, you know, you should be able to go to, you know, a person and you should be able to say, "Hey, you know, this does X, Y, and Z" within a sentence. Um, and, and so for example, you know, at Homejoy we started off with something actually super complicated. We're like, we're an online platform for Home Services. We started with cleaning and you can choose, you know, blah, blah, blah, blah, and it just went off for paragraphs and paragraphs.
Um, when we present, we went to, you know, potential users to come on our platform, they just get kind of get bored after the first, first few sentences. And so what we just, what we found out was that, you know, we really needed this one-liner. The one-liner is very important, and it kind of describes the functional benefit of what you do. You know, in the future when you're trying to build a brand or whatnot, you should, you should, you know, be able to describe, you know, what are the emotional benefits and stuff like that.
But you're starting with no users, you really need to tell them what they're going to get out of it. So we simply, after we changed our positioning to "Get your place cleaned for $20 an hour," then everyone got it. Um, and we were able to get, you know, users on the door that way. So you have a MVP going out there, now how do you get your first few users to start trying it?
Um, so your first users should be, you know, the obvious people, the people that you're connected with. Uh, you should use it obviously. You and your co-founder should be using it, your mom and dad should be using it, your friends and co-workers should be using it beyond that. Um, you want to get more user feedback and so you, and I've listed here of some of the obvious places to go to.
And depending on what you're selling, you know, you can take your pick of the pick of the draw here. Um, so online communities, um, there's, you know, on Hacker News now there's the show hn, that's a great place, especially if you're building tools for developers and things like that. Local communities, so if you're building consumer product, you know, there are a lot of influential local community mailing lists.
Um, uh, especially those for, you know, parents. Um, so those are places you might want to hit up too. Uh, okay, so when you go to, uh, by the way, Homejoy, we actually tried all of these. So, um, we used it ourselves that was fine because I mean, we were on a cleaner, so that was pretty easy. Um, and then our parents lived in Milwaukee so we were based in Mountain View, so that didn't work. Friends and co-workers are kind of like in San Francisco and elsewhere.
Um, so we didn't have too many of them use it, so we were actually, um, ended up in a dead end of um, not being able to convince many people to use this in the beginning. Uh, so what we did was, because we're in Mountain View, some of you guys might know on Cter Treet, they have, uh, street fairs there during the summertime and so we go out and basically chase down people and try to get them to book of cleaning. And almost everyone would say no.
Uh, until one day, um, we just took advantage, you know, it was a very hot and humid day and what we noticed was, you know, and this is like in any, any fair people, you know, there might be arts and crafts and things like that and random people will, you know, gravitate towards that. But everybody gravitates towards the food and drink area, especially on a hot day. So what we did was, okay we need to, we figured we need to get in the middle of that and by getting in the middle of that, we just took water bottles, froze them, and then we started handing out free, free bottles of water that were cold.
And people just came to us. We, I think we basically guilt trip people into booking cleanings. Um, but the proof in the pudding was that I figured most of the people were guilt tripped into doing it, but uh, when they went home they didn't cancel on us or some of them did, but uh, majority of them did not. And so we felt like, I thought, okay that's good, I got to go clean their houses, but uh at least, you know, there's something we're actually solving here.
Um, so, uh, and you know, I don't suggest I think showing up at the fairs or, I know another startup in the last batch, I forgot their name right now, but they, uh, they showed up, they were selling shipping type products or trying to replace shipping products or, or the concept of mailing stuff. And so they would show up to the US Postal Office and just like find people who were trying to ship products and just take them out of line and try to get them to use your product and have them ship before him.
Um, so you just have to go to places where people are going to really show up and you know your provision rate is going to be really, really low. But to go from Z to 1 to 3 to 4, um, these are kind of things you might have to do. Okay, so you got some users using you, now what do you do with all these users? Um, customer feedback. So one of the first things you should do is make sure there's a way for people to contact you, so support Homejoy and, uh, if you put hook up a phone number, one really good idea is to, uh, make sure that, uh, you have voicemail or something like that so you don't have to be picking it up all the time.
Um, but in any case, a way for people to get inbound feedback is good, but really what you should be doing is going out to your users and talking with them. You know, get away from your desk and just get out and do the work. It's, it seems like a slog and it's going to be a slog but this is where you're going to get the best feedback ever for your product and this is going to teach you on what features you need to completely change, get rid of, or what features you need to build.
And so one way to do this is to send out surveys, you know, to get reviews after they've used the product. Um, this is okay, but generally, you know, people are only going to respond if they really love you or they really hate you, and you never get like the in between. Um, so kind of get the in when and not get all the extremes is to go out and actually meet the person that is using your product.
And, um, it's not a good idea to, you know, I've seen people go out, meet the user and they sit there, and it's like a laboratory and it's, it's like an inquisition almost. You're kind of just like poking and poking and poking them, like why didn't you do that? That's not going to give you the best results. What you should really do is make it into a conversation, get to know them, give them to feel comfortable because you want to get them at a level where they feel like, you know, they should be honest with you to help you and improve things for you.
So I found that actually taking people out for drinks and stuff like that was a very good way to do that. Um, not sure if all of you are old enough to do that, but you can take them for coffee. Um, so another way, another thing you should be tracking is, um, how are you doing in general from like the macro perspective and one way to do that is, the best way to do that is, um, by tracking customer retention.
That is the number of people that came in the door today, how many are coming back tomorrow, the next day, and so on and so forth. Um, usually over time you're kind of looking at, you know, monthly retention. So, you know, people who came in the door today, are they still using it next month, and so on, so forth. The problem with that metric is that it's, you know, it takes forever to collect that data and you don't have, sometimes you don't have a month or two months or three months to figure that out.
So a good leading indicator is actually, um, collecting reviews and ratings like five-star, four-star reviews, or collecting some notion of NPS, which is Net Promoter Score. Um, so you're basically asking them from a rating from 0 to 10, um, how likely are they to recommend you to a friend and calculating the NPS. And so over time, what you'll see is, as you're building in new features, you should be able to see that the reviews or the retention is going up over time, which means you're doing a good job. If it's going down, you're doing a bad job.
Um, and if it's kind of staying the same, that means you probably need to go out and figure out what new things you should be building. Um, the other thing is I'll get to the qualitative thing um, later, but the one thing you should be wary of is, um, the honesty curve, which is some people will just lie to you.
So I was going to just let's just do, so I mean this is like degrees of separation from you and this is like level of honesty, like so here this is your mom, this is like your friends are friends, and here's like random people. So I don't know if you can all see this, but um, so your mom is going to be, you know, she should use your product but she's G to be proud of you anyway. Um, and so she'll like maybe be honest like this much and your friends will, you know, they'll be pretty honest with you and give you feedback because they care about you, by the way this is assuming it's a free product that you're giving them.
And then over time, like as you get more and more random these people don't even know who you are. Um, it doesn't go like this really, but it kind of goes like this, uh, where people don't care about giving you feedback, they just like, okay, here's a survey type thing. Um, and so you should take this into consideration when getting user feedback.
Now let's say you make, you pay, it's a paid product, right? Well, let's just do this in green. So the paid, you know, your mom is going to be like down here. Like she's just going to lie to you and say, you know, she's just going to feel sorry and say this is a great product, of course. Um, but then you kind of, it goes like this, right? Which is to say that, you know, your friends are kind of going to give you the right, um, they want to support you and give you the right feedback, but it's actually these random people out here that, you know, if they, if they really don't think what they paid for was worth it, they're going to really tell you, um, because you know it's money out the door.
And so this is another way of saying you're going to get the best feedback. Like this is obviously, you know, down here you're going to get more feedback, um, if you just make someone pay for it. So that's not to say you should, you know, the first time out make people pay for it, but it's to say that you should very, if you're going to build a product that you're going to eventually need to, you know, they're going to pay for the software or for the hardware, whatever, you should do that, get to the point where you can do that very, very fast.
Um, because then that's when you get the real meaty stuff to help you in the future of how you can get more paying users in the door. All right, so you're getting a lot of feedback and what do you do before you officially launch the product? Um, so what you want to do is you always want to be building fast, right? And you want to be optimizing for this stage of growth that is, you know, you might have 10 users at this point, don't, there's no point in trying to build features for the point when you have a million users, right? You want to optimize for the next stage of growth which is going to be 10 to 100 users like what are the features you really need for that?
And um, just go with that. Um, sometime and in basically on the slide is just many ways of stating that notion manual before automation. Um, one of the things that I found when building a marketplace is that process is very, very important, um, over time as you scale. But you need not try to automate everything and create software to just, you know, have robots just run everything. What you really should do to understand what you should build is to manually do it yourself.
Um, and, and an example of this is, um, when we started taking on cleaning professionals onto our platform, we would have them, um, we would ask them a bunch of questions, um, over the phone and then in person we ask them a bunch of questions too and then they would go to a test clean and then they would, you know, get onboarded to our platform if they were good enough. Uh, and so this took us doing all the question askings for that many candidates, you know, we had about a three to five percent acceptance rate.
And so you can imagine all the people we were talking to in the beginning of the funnel that never even made onto the platform. But what happened over time was that we learned certain questions, um, that we were asking, uh, were that were indicators of whether they were going to be a good or bad performer on the platform. We, um, through just like data collection and just, you know, looking at everything, um, we could just ask on an online form. So that's when we put on, put in an online application, they could apply and then we would ask them maybe several other questions during the interpersonal interview.
Um, so it's if you try to automate things too fast then you run into this problem, potential problem of, you know, not being able to move quickly on trying to iterate, you know, with things like questions on an application and stuff like that. Um, and this third point here is temporary brokenness is much better than permanent paralysis. Uh, by that what I mean is you know perfection is irrelevant during the stage.
Um, you should when you get to the next stage of growth like what you're trying to maybe perfect in this one stage is probably going to not matter anyway. And so do not worry about all the edge cases when you're building something. Just worry about the generic case of who your core user is going to be and then as you get bigger and bigger and bigger, the volume of those edge cases will increase over time and you'll want to, you know, build for that.
And lastly, beware of the Frankenstein approach which is great, you talk to all these users, they give you all these ideas, you know, the first thing you're going to want to do is go build every single one of them and then go show them the next day and um, make them happier. Uh, you should definitely listen to user feedback, but when someone tells you to build a feature, you shouldn't go build it right away. What you should really do is, you know, get to the bottom of why they're asking you to build a feature.
It's usually, usually what they're suggesting is not the best idea, but what they're really suggesting is I have this other problem that you've either created for me while using the product or, you know, I really need this problem solved before I'm ever going to pay to use this product. And so figure that out first instead of piling on a bunch of features, um, which then hides the problem altogether.
So you have, uh, so, so you have a product that you're ready to ship. And, um, so some people at this point will continue building their product and not ship it at all. And, um, I think the whole idea of being stealth in, you know, perfecting the product to no ends is, um, is the idea that, you know, uh, imitation is, um, is, is cheaper than innovation in terms of time and, um, and money and capital.
And so I think everyone should just always assume in general like there's going to be, if you have a really good idea, no matter when you launch, someone's going to, someone's going to be, you know, someone's going to fast follow you and someone's going to execute, um, as hard as they possibly can to catch up with you. And so there's no point in holding out in all that user feedback that you can get by getting a lot of users.
Um, because you feel like, you know, you feel paranoid that someone's going to do this to you. Um, and I hate to keep harping on it, but this is things I see today with founders is something I went through as well. Um, and I think unless you're, unless you're building something that requires hundred, like tens of millions of dollars just to start up, there really is no point in waiting around to launch your product.
So say you have something that you feel ready to get lots of users on. Um, so what do you do at this point? So I'll look at my time, um, 20 minutes, okay. So I will go over, um, various types of growth in the next slide. Um, but the one thing to note here early on when you are trying to get, um, when it's just you and your co-founder and maybe like a couple other people building, um, you're not going to be, you know, create a team just for growth.
It's going to be one person and one person only and so you need to really focus and you need to, you should only, you're going to be tempted to try like five different strategies at one time, but really what you should do is take one channel and really execute on it for an entire week and just focus on that. And then if that works, continue executing on it until it caps out. If it doesn't work, then just move on. Um, by doing this, you will feel more certain that, uh, that, that that channel that you were working on, that initial hypothesis is wrong.
Um, you'll be, you know, then if you tried only working a third of your time on it over the course of, you know, three or four weeks. Um, so learn one channel at a time. Second is always be, when you find channels that work, you find strategies that work, always be iterating on it. You can potentially give it to some, like create a playbook and give it to somebody else to iterate on it.
Um, but these channels always change, you know, anything from Facebook ads to, you know, even Google ads to, you know, the distribution channels, um, the environments that you don't control change all the time and so you should be always iterating, optimizing for that. And lastly, um, in the beginning, you're probably not when you see a channel that fails, you know, just get rid of it and go on and move on.
There's many other things to try, but over time go back to those channels and um, and look at it again. So and what I mean by that is an example is in the beginning at Homejoy, we had no money. Um, so when we tried to do um, we tried to buy users from um, Merry Maids or not from Merry Maids, that's just an example of a competitor. We tried to buy Google ads um, to get users in the door quickly, and what we found was that, um, Mary Maids, Molly Maids, all these other national companies, they have more money than us.
They were making a lot more money on the job than us and so they were able to pay for users at a much higher, um, at a much higher CAC, a much higher they were able to acquire them at a much higher cost than us. And so we couldn't afford that and we had to go to another channel, which turned out to be something else. Um, but today, you know, we make more money on the job.
We're much better at certain things and so we should probably revisit the idea of buying Google ads and buy, you know, going to the STM channel. Um, and so what that's what I mean by that, and the key to all this is creativity. Uh, performance marketing, you know, or marketing or growth in general, um, can be very technical. Um, but it's actually technical and you have to be creative because if it wasn't, if it was really easy and bland, you know, like everyone would be growing right now.
Um, and so you always have to find like that little thing that no one else is doing and, and, and do that, um, to the extreme. So there are, uh, three types of growth. Um, when, yeah, three types of growth. Um, sticky, viral, and pay growth. And hopefully I'll get enough time to talk about all of this.
Uh, so really briefly, sticky growth is trying to get your existing users to come back and pay you more or use you more. Um, second is viral growth. So that's when people talk about you. Um, so you use a product, you really like it, then you tell 10 other friends, um, they like it, that's viral growth. And the third is paid growth.
So if you happen to have money in the bank, um, you're going to be able to perhaps use part of that money to, to, to buy growth. Um, and the central theme I'm going to go through is sustainability. There's a lot of, um, by sustainable growth, I mean, you know, you're basically not a leaky bucket. Money you put in or time you put in, um, has a good return on investment on it.
So sticky growth is, like I said, getting your existing users to keep buying stuff. Um, so the only thing that really matters here is that you deliver a good experience, right? Um, if you deliver a good experience, people are going to keep wanting to use you. If deliver an addictive experience, people are going to keep wanting to use you.
Um, and the way to measure this and to really look at this and how you're doing over time of whether, you know, you are providing, um, good sticky growth is to look at, um, the CLVs and retention cohort analysis.
Now does anyone not know what cohort analysis is or should I go over it? Okay, so I'll go over it. Okay, so CLV is, um, some people call LTV is called customer lifetime, which is basically the amount of the net revenue that a customer brings in the door for you over a certain amount of period.
So a 12-month CLV is how much net revenue does a customer, um, give you over 12 months, and sometimes people look at 3 months and 6 months and so on and so forth. Um, so when I say cohort, basically what you're looking at is this is time. So let's just call this, yeah, time. So this is percent of users coming back to you.
So at time zero, right, a period zero, we're at 100, I'm 100%. So, so um, cohort is, is another name also for like customer segments and stuff like that. So you can, like, you might look at the female versus male cohort, um, you know, people in Atlanta, Georgia versus people in Sacramento, California.
Um, but, uh, the most common one is by month. Um, so cohort equals month and let's just say for this exercise we are looking at, um, like March of I don't know, 2012. So March 2012, 100% of people, you'll have like maybe n equals 100 people. So 100% of the people, obviously, are using your product because you know that's the definition.
Now month one, month later, um, you might have, you know, the scale is not right but 50% might come back and so you come here. Now in the second month, how many people that came in March come back in the second month or two months later? And that might be, you know, down here. And so over time, you'll have a curve that looks like this.
There's always some initial drop-off. You know, the reasons why people don't stay after the first use is, you know, it wasn't worth it, um, had a bad experience, stuff like that. And then over time, what you want is you want this to flatten out over time so that your turn basically goes to 0%. That means you attrition out less, less, and less users over time.
And these over here kind of become your core customers. These are ones that are like sort of staying with you for a long time. And now, cohort analysis, or, you know, using this as a way to show if you have sticky growth or not is now say you're say you know, say we're one year later and you've built a bunch of stuff, right? You graph out the same thing and hopefully what you'll see is that you have a curve like this that is in the first period even more people than 50% came back to you and more and more people are sticking with you.
A really bad, you know, retention curve looks like this which is like after the first use they just hate you so much no, like no one even comes back. It's just like zero right? And I don't know what kind of business that is. I mean it's obviously a shitty business but, I can't explain a good business that has a retention curve like that.
Um, so anyway, so over time as you are thinking of strategies to increase this curve, like keep making it go up and up and up, um, uh, you want to basically look at this analysis, um, over time to see if that, uh, strategy is working for you.
Okay, does that make sense? Okay, cool. Um, the second kind of growth is viral growth and like sticky growth you need to also deliver