In this episode of Startups For The Rest Of Us, Rob and Mike talk about the current status of Bluetick. They discuss the Google approval process, external/internal motivations, current roadblocks, and Mike’s future with Bluetick.
Items mentioned in this episode:
Rob: Mike, which program do Jedi use to open their PDF files?
Mike: I don’t know what.
Rob: Adobe Wan Kenobi.
Mike: Oh God.
Rob: In this episode of Startups for the Rest of Us, Mike and I talk about Bluetick, where he’s at, and maybe where he’s headed. This is Startups for the Rest of Us Episode 448.
Welcome to Startups for the Rest of Us, the podcast that helps developers, designers, and entrepreneurs be awesome at building, launching, and growing software products, whether you’ve build your first one or you’re just thinking about it. I’m Rob.
Mike: And I’m Mike.
Rob: And we’re here to share our experiences to help you avoid the same mistakes we’ve made. To where this week, sir?
Mike: I strained my back somehow about a week or so ago, so sleeping the past five or six days has been rather rough. It’s on the left side. When I try to sleep, it gets really, really tight throughout the course of the night and it wakes me up. It’s been rough getting any kind of measurably good sleep for pretty much the entire week.
Rob: That’s a bummer. How did you strained up?
Mike: I have no idea. I think I was just alive and that was it.
Rob: Just. I was just old and I moved.
Mike: That’s a good way to put it. The thing is, I just woke up and it was like that. It got progressively worse over the course of two or three days or something like that. It was bad for about four or five and then it slowly gotten better over the last two or three.
Rob: Strained back is no good and no sleep is no good. You’re going back to your pre-CPAP machine days aren’t you?
Mike: Yeah, pretty much.
Rob: We’ll get into some of that more in this episode. We’re going to talk about, as I said in the intro, what’s going on with Bluetick and you and such. Before that, we have some good comments on recent episodes. In Episode 444, you and I went off on Gmail desktop clients. Carl posted a comment saying, “I switched everyone over to Mailbird last month,” everyone at his company. “We switched away from Office 365, Dropbox, and GoDaddy’s email service, and switched to G Suite Solutions. I needed to find an alternative to Outlook and I found Mailbird. It works great, love the Google integrations. My only complaint, one of my coworker’s complaints is that capability of right-clicking to create new folders does not exist. Not a deal breaker, just a complaint.”
What was the one I was using? I don’t remember now. It was Mailplane, like an airplane. When I right click, I often do right-click, paste as text or paste and match style or whatever, because I’ll be copying something that’s all weirdly formatted and I want it to go in the format of the email. In Mailplane, that’s disabled. Not a deal breaker, but I have to flip over into Atom, your […] text editor, I paste it in there then I Shift Command-A Command-C and then go back and paste it in. It’s this extra step that when you’re in a Chrome browser, you can right click, paste the match style, and then it’ll just go in. How about you? Are you still using the desktop Windows client you were using?
Mike: Yeah, I use it on occasion. I flip-flop back and forth between them because it’s an IMAP client and it’s got all that stuff. It’s nice to be able to use one or the other when I need it. The one that I did find with it was that I use the labels feature. I will take things and put them into, I refer to more folders than anything else, but in Gmail it uses labels for that. The one thing I find is that, if I go to use the shortcuts to move it into a folder or apply a label to it, some of my labels, depending on the folder, overlap.
For example I’ll have a customers label but there’s a customers label underneath a couple of different products. When I started typing it out, it doesn’t show me which customers label it is because it basically drops everything before the slash. I have no idea which customers label it actually is because it just doesn’t show me. I still use it on occasion but once I get into those use cases, it becomes a barrier for me. It makes it more difficult. I don’t know why they don’t show the whole thing, but whatever.
Rob: It’s weird. When we bring these things up, it’s like, “That’s kind of a nitpick. Right click, paste and match style, is that really that big of a deal? Is it the labeling?” It can be. It can become that. For me, it’s not that big of a deal, but label stuff, that gets in the way of your workflow and it can get in the way of the perfect solution unless you get used to the new way they do it.
Mike: Like I said, I flip-flop back and forth between them a little bit. I did notice when I was using it that I could shut it down and I would just have Gmail closed, but I’ve noticed that recently I’ve been having Gmail open again. With that, I know that I’m actually just going to close that tab entirely right this second because I forget to do that. Email can be distracting and disruptive. That’s a problem that I’ve uncovered with my workflow, is that when that is open, I tend to get pulled back into my email quite a bit. When that happens, I’m not as productive.
Rob: For sure. Another comment on Episode 447. Paul Mendoza was commenting on the Google verification stuff that you’ve been struggling with for several weeks. He says, “I’ve been dealing with Google verification stuff for months, you can see my day-by-day interactions with Google here. We just got a response from the security vendors, but our app still isn’t approved but I’m sending them emails almost everyday.” He has a URL. You can come to 447 if you want to check that Google verification status. He feels your pain, apparently. It’s not just something that you have manufactured in order to create drama and good radio on the podcast as you’ve been known to do. You haven’t been on […].
Rob: We got another couple of comments, because 447 we started diving in, we typically do our chit chat at the top end of the episode. When we talked about the Google stuff, we wound up spending 18 minutes just talking about that because I was asking questions and going through it. We’ve got some compliments like, “Do more of that. You guys aren’t digging into Bluetick enough,” was the comments, “or your own projects enough.” Part of the impetus for today’s episode was comments we’ve received but also, I think it’s been something that’s been on our minds for a while.
We have always liked doing updates, sharing what we’re up to, and what we’re working on, but it can be hard when it’s not good news. It’s hard to show up week after week and try to have an update of what you did in the past week if you didn’t get anything done or if things are going backwards. I think we tend to do update episodes every few months and I feel like this one today is really just a conversation about where you are, where Bluetick is, how you’re thinking about things, and try to find out more about what’s going on and even to give advice.
We talked for a while before this episode started and you’re bringing up things that I was telling you how I would approach them. We haven’t necessarily always been a ‘big advice for each other’ podcast. It’s a lot more answering listener questions. I think that can be helpful today, too, for you to hear how I would think of approaching different problems or how I have approached them in the past because I’ve done some of this stuff as well.
Mike: Do you want to relabel this as Mike’s therapy session?
Rob: Yeah, it’s going to be 50 minutes and I’m going to bill you […].
Mike: That’s actually cheaper.
Rob: Cheaper than you thought it would be.
Mike: Cheaper than a regular therapy session with […].
Rob: Indeed. Bluetick today, you’ve been working on it for two or three years, and it’s still not supporting you full time.
Mike: I went back and I started looking at my funnel metrics and stuff where I started tracking some of that stuff. I’ve got data in here from November of 2017 and that’s when I started tracking the numbers that I have here. I think that was shortly before I flipped the switch and said, “I’m just going to start billing people. If you’re not ready, then you can either cancel or that’s the end of the free trial or whatever that we have for you.” Obviously, my memory is kind of fuzzy as to exactly what state those things were at at the time so I don’t remember whether it was November of that year or what have you.
Rob: Was that November 2017?
Mike: Yes, November 2017. The reality is it’s not nearly where I would think that it should be if things were going well, the product had product market fit, and I was actively growing it. It’s just not. It’s not enough to support me full time. I don’t necessarily need it to, but at the same time if it’s going for an extended period of time and it’s not making enough money to do that, then why continue?
Rob: Yeah. It’s a waste of time and effort, opportunity cost, could you be working on something else that would be dramatically more lucrative whether that something else is a different product, or whether that something else is consulting, or heaven forbid a salary job? Not that you’re going to go do that, but you have skills. You’re a developer. You can write code. That’s a very valuable skill. To be wasting, I don’t mean wasting time on a day-to-day basis, but having 18 months, you’ve been charging for it, and to be only ramen profitable and not full time income is a struggle. It’s not just that you don’t have full time income but it’s not headed in the right direction anymore. You basically peaked at some point last year in terms of MRR.
Mike: Yeah and it’s more floundering than anything else. It’s not on a tailspin and I’m not bleeding out customers every single week or anything like that. It’s not tanking quickly, but it’s certainly not growing quickly, either. It’s really just meandering; go up on some months and then go down on some months. I have some customers who’ve been around since the very beginning and there are customers who will stick around for three to six months and then that’s it. I don’t feel like I’ve delve into the numbers of how long people have stuck around for and what the amount of revenue that I’ve gotten from each customer is enough, I just haven’t. It’s because I’ve spent a lot of my time on other things.
I feel like I have a hard time prioritizing where I should spend some of that time. Objectively, I think it’s like, “You should spend all of that time on marketing activities, analyzing what your current customers are doing, and who you should be targeting as those customers. One thing I struggle with is the fact that Bluetick has a very good use case for cold email and I don’t want those customers. I have a hard time justifying adding a lot more customers on there that are using the tool for that.
Rob: Is it an ethical thing? You just don’t like cold email?
Mike: Yeah, mostly.
Rob: Or a moral thing? Wait, what ethical is this? External and moral is internal. You’re internal code is like, “Meh. Not a fan of it.” Is that the idea?
Mike: The problem is that it depends on the customer. There are some customers that I’ll talk to, I’ll do a demo for somebody and I hear what they’re doing and they’re doing cold email. I’m like, “It’s not just a great tool that you have, but it’s also a great service. You’re doing great things with it and you are trying to make the world a better place,” versus some of the people just doing the cold email. They’re really bad at it and they’re doing things that are shady or scammy. I’m like, “Yeah. I don’t want those as customers,” but at the same time the tool works exactly the same for both of them.
How do I filter one out versus the other without having a conversation with every single one of them and how do you do that in the marketing that you put out such that you are catering specifically to a type of person who has a certain mindset?
Rob: I hear you. There are ways around it. You have options. You could, on your homepage, just be like the best tool for warm email interactions and then you could put in the FAQ, “This is not for cold email.” You could put it in your terms of service, “This is not for cold email.” You can have flags if people go in it, you see patterns of people doing cold email type things that you flag and you say, “Hey, this isn’t for cold email.”
We had to do this with Drip. People can’t use Drip for cold email. We had to build things and communicate that along the way. It was a pain. It was a lot of work and some people got really pissed off. Some people came in, signed up, uploaded their cold list and started emailing. Our system would automatically block them or they’d get enough complaints that are email spam. Dude would block them. That’s what you have to do if you really don’t want to do it.
The struggle is, with Drip, it will get you blacklisted. So, it’s a big problem for the business itself. With Bluetick, it’s not because they’re using their own inbox. You’re not going to get Bluetick itself, your IP doesn’t get blasted. You have to decide, “Hey, if ethically or morally or whatever, I only want to service certain type customer,” then you can do that. Just make it clear upfront.
It sounds to me like is it an excuse? If you accepted all the cold email, would Bluetick be where you want it to be? Or if you just focus on the warm email use case and ignore the cold email, would Bluetick be where you want it to be?
Mike: I don’t want to say it’s an unfair question, I think the question is a little bit off because it’s more a matter of holding me back from doing the marketing which would acquire those types of customers. It’s not about accepting them as customers or trying to turn them away or whatever. It’s more about holding me back from doing the marketing. I think it’s a very valid question about is that an excuse? I have a whole load of things I’ve looked at and thought about that comes to mind is, […] every single one of them is like, “Is that just an excuse?”
If you looked back at the stuff I did with AutoShark and then with Bluetick, I’ll […] frankly a lot of excuses along the way with AutoShark. If you think about objectively the stuff I’m going through with Google right now, there’s a huge question mark of this $15,000–$75,000 for a security audit. I’m apparently at the end point with Google where all I need to do is get this security audit and get a letter of—I forget what it is—authentication or something, this audit letter that I have to send into Google that says, “Yes, Bluetick is all up to snuff and we don’t have to worry too much about security vulnerabilities for the product,” but at the same time, is that another excuse?
If the products were much further along or had more customers and was making a substantial amount of revenue, would $15,000–$75,000 matter? The answer is no, it wouldn’t. The problem is I can’t point at Google and say they’re killing my business when the reality is the business isn’t making enough money. Really, that’s just the driver that says, “Here’s a hard line that you can’t cross unless the business is making enough.” If the business was making enough, that wouldn’t matter. The actual amount of whatever that is going to come out to would make no difference or whatsoever. So, is that an excuse?
I was saying in a way it kind of is, but at the same time I could almost point at anything that I’ve come across and say, “Is this an excuse?” Anything that comes up on the business as to why something is not working, you could ask that question and I think it’s a valid question to ask. I don’t have a good answer for some of those things. I just don’t.
Rob: That’s the thing. The cold email versus warm email thing, you don’t want to market it because people are using it for cold email. There are solutions to that. If I were in your shoes, I would decide, am I willing to let people do ethical cold email and warm email? If the answer is yes, then that would be on the website. That would be in my onboarding. I would mention that in every demo. I would probably do demo only for now in your shoes because you don’t have such an influx of trials. I’m guessing that you can’t do some type of demo with everyone at a minimum of screencast, 15 minutes of screencast that seriously talks about, “Look, we only do ethical cold email.” Just make that part of the whole deal. If that’s your hard line, then take the hard line and then move forward. That’s one option.
Second option is to not take the hard line and just say, “Hey, this is legal and it’s not going to hurt my IPs so I’m okay with people doing that.” That’s the second option.
Third option, shut the product down. It’s to realize, “Boy, I really built a product that people are going to misuse,” and the nuclear option would be to shut it down. Now that’s tough. I don’t know if I can come up with an easy fourth option. I feel like the ethical cold and warm is a perfectly viable non-nuclear option, and again, to just communicate that in every onboarding sequence.
Some people will sneak through, unfortunately. The good news is, it won’t get you on a blacklist like it did with Drip where we get on the blacklist and it’s like this, “Oh, […],” moment where a bunch of us were running around trying to figure out how to ban this customer and this and that. You’ll just have to have a conversation with that customer and say, “Look, by our judgment or by my judgment, you’ve gone over the line. I need you to migrate away or I need you to improve your things.” You can get a conversation with them where they say, “How do I improve my cold email?” You say, “Here’s a good example of a super ethical one. You only hit them four times over the course of a month, not 17 like you’re doing,” and blah, blah, blah.
All of this is work. It all takes work and that’s a crappy part. It’s the same thing with the Google approval, I think, that it totally gets in your head it seems like and it becomes this road block where really, it should be a speed bump that you look at your options. I say should. You’re going to encounter these over and over. I feel like if you look at the mess of speed bumps rather than roadblocks, knowing that there’s almost without exception, there’s always a way around it.
There are a few exceptions that are not. You can get sued into oblivion. You can get seriously injured. There are these extreme things where you can’t work or where your business is completely decimated because the whole platform just blocks your IP. There are certain exceptions but I don’t see that. Aside from Google disapproving you here in the next week or two, everything else you’ve mentioned to me is a speed bump, but I feel like it impacts you more than that.
Mike: That’s absolutely true. As you were talking through that and shifting the marketing to saying much more of it is ethical cold email and warm email, I actually got excited. I was like, “That’s exactly it.” I think that there are other ways to force that as well. I was talking to Josh from Referral Rock. He said that one of the things that they had done early on was that they charged a setup fee and that works really well for them. I was thinking about doing that as well and trying to figure out how can that work in there. That fits in really well with the idea of pitching it more towards the ethical cold email and warm email for people and then forcing people to do a demo.
That’s part of what the setup fee would be and making sure that they’re doing things the right way, that they’re not just spamming a ton of people just because they have the technical capabilities to. Honestly, that would make me feel a whole heck of a lot better about it. I was actually trying to figure out, “How can I justify this setup fee and how can I do that stuff?” I think that it falls directly in line with that. It makes total sense as to how that could happen now whereas before, I struggled a little bit with how do I present it or pitch it or make sure that people are doing the right things and everything is going well for them. I’ll say it’s like software augmented by services to some extent.
Rob: Absolutely. I feel like that’s one issue but it’s not as if we can now, “Alright and that’s the whole session, Mike, you’re all good,” because there are some deeper issues going on. It seems to me like the two biggest issues that I see with Bluetick and what you’ve been up to, number one, I don’t understand how Bluetick is any different than any of the other tools. I don’t think you’re differentiated. You can convince me otherwise but I don’t feel like there’s anything Bluetick can do that three or four other tools can’t do. That’s a problem because you’re picking up crumbs at that point.
The second thing that feeds into that is you have struggled to ship things. Whether it’s health issues, the distraction from the Google approval, I know you’ve had sleep issues for a long time. You talked at the last podcast about how you had a five- or six-hour workday. Two hours of it was with calls, then your kids were going to get home, and you’ve spent an hour on the Google thing. Your workday was just poof. Gone. You’re not shipping new features. You’re not shipping marketing.
When you look at the people who are making progress in these early stages, they’re shipping something every week. You look at Derrick Reimer. Even though he shut Level down, he was shipping features, he was shipping emails, he was shipping blog post. You look at Peter Suhm, who is the founder of Branch, which is a TinySeed company, was just announced today, he’s doing the same thing. He releases a blog post almost every week and he ships new features to Branch almost every week. You’ve struggled with that going way back.
I think that’s where we talked a little bit offline before this. You have reasons but you were saying to yourself like, “Are they reasons or are they excuses?” The health issues, there’s testosterone levels a few years back, there’s CPAP, there’s all that stuff. It impacts your motivation and that means that you haven’t shipped enough stuff fast enough to differentiate Bluetick and everyone else that you’re competing against is moving, I would say faster than you. You never catch up. Again, my impression is they are better tools, they just have more features, and they do more. So, how can you possibly grow an app that isn’t differentiated in any way?
Mike: A lot of them have definitely caught up in terms of the features. Some of them even started out further along than I was at the early stages. My difference in feature was intended to be the fact that Bluetick does not miss emails, whereas I know that people who were using the Gmail API, those types of customers tend to miss emails here and there. I feel like a lot of those problems have tended to go away. I don’t know whether that’s because the Gmail API has just gotten better in terms of what data that they’ve been sending or the frequency, but I don’t hear about those problems nearly as much as I used to.
Maybe the tools have just gotten better and they’ve fixed those problems. I don’t really know the answer to that because I don’t use those tools on a regular basis. But the fact is you’re right. I’m not shipping things nearly as much as I could or should be. There are certain things where I’ve gone through and I’ve reengineered something or changed how something works, and I’ve got all these data that is going through the system. I’m terrified in some cases of breaking stuff.
I’ve been going back-and-forth recently with one of the vendors who supplies the component that I use for synchronizing with IMAP. They won’t give me access to the stuff where I know for a fact it breaks and I can’t test it. I can’t put an automated test in place and they won’t give me a way to do it. I’m just like, “I don’t know what I’m supposed to do here,” other than switching to some other component which again is non-trivial work. Is that an excuse?
Rob: It’s a problem but you’re going to encounter a problem almost everyday as an entrepreneur. If they become, they should be speed bumps. You could mock up an interface of some kind. Again, we had a bunch of APIs that we interfaced with Drip and we couldn’t hit the production or staging APIs so when our unit has ran, they would hit a mocked up interface. There’s a better word for it, but you know what I’m talking about.
You could feasibly break things but that’s what integration testing is for, and then you just have a checklist of like, “These are the five things that I’m always worried about breaking because I can’t test them well.” Those are in a Google Doc or a Trello board or whatever. Every time you do a big push or everytime you modify that code, you test those things. That’s how I would think about it. Again, it’s not perfect but it makes it into a speed bump. It makes it into a bump in the road rather than an actual road block.
Mike: The specific issue with that piece of it and the problem that I have with that, there are certain things that come up on occasion and I literally can’t do that because they’ve marked the class that I need to use as internal and sealed and there’s no interface for it. I literally cannot do it. The only way that I found to get around it is to create a constructor that uses the internal private constructor for it and basically fake the data, but I’m looking at obfuscated code at that point and I don’t know what the hell half of it does. I think all of this particular example is kind of immaterial, I agree it should be more of a speed bump than a road block. Going down the rest of that specific example is more of going down the rabbit hole more than anything else because it’s not the only thing.
Rob: The thing is, when these things come up, it’s not going to be perfect. I know that sounds silly to say, but you’re an engineer, you’re left brained, and you want every I to be dotted, every T to be crossed, every edge and corner case to be handled. Mike, your software is going to break sometimes. There is […] software that is doing seven, eight, nine figures a month and the stuff breaks. You can build a company with software that isn’t 100%. My guess is your software is going to be pretty dang good because you’re a developer and because you’ve been doing this most of your life, but at a certain point, you can’t let perfect get in the way of good and in the way of shipping.
Mike: And I do. I absolutely let that get in the way. I don’t know why it’s so hard for me to just let it go. There are some things where I can just say, “Oh, we’ll just do this. Yes, […], go ahead.” Then there are other things where I’m like, “No, it has to be right.” For whatever reason, I fixate on those things.
Rob: That’s the problem. If you can’t identify when you’re fixating, then tell yourself stop and approach this from a different mindset. What would XYZ person do? How should I think about this differently is probably a better question that when you find yourself fixating to stop yourself and have the introspection to say, “What is the hack to get the solution? What is the 95% solution to this? What are the three or four options I have?” We’ve talked about a few topics here and then each one, you see, I’m just breaking them down into what are your choices here?
You’re choices with this API or whatever or it’s the component that you don’t have internal access to and it’s sealed and whatever, Mike, here are your options. You can completely shut your entire company down. Honestly, let’s look at them. You could shut the company down because of that. You could build a solution that is 80/20 or 95/5, however you want to phrase it. That’s like the one I said earlier which has been attacked together. It’s not going to catch everything and you have a checklist, and that’s probably good enough for now. Or you can spend a lot of time fixating on it. You can fight with the guy over email, you can try to reverse engineer it.
Mike: I can replace the component.
Rob: That’s great, you could feasibly do that. You could rewrite the whole thing yourself.
Mike: No, I wouldn’t do that. I would find a different vendor where I can rip that out and replace it with something else, that’s what I would do. I would absolutely not going down that road.
Rob: But that is an option. What’s funny is you could replace it with a different one. You’re going to spend time reworking your code or you could just rewrite the whole component yourself. It’s ridiculous but it is an option. Those are your five or six options. When you look at them, some of them seem like the dumbest thing ever like shutting your business down or writing the component yourself; don’t do those. It’s obvious, those are dumb. But the other three, if we look at them, black and white mindset and try to think about them. Which of those gets you to full-time income? Which of those gets you to $10,000? Yeah, there’s a little bit of risk with the one I’m suggesting, but that turns it into a speed bump rather than a road block.
Mike: One of the challenges I run into with this is that I don’t really have a mastermind group anymore where I can bounce ideas off of people and they call me out on a weekly basis that says, “Hey, you’re not working on this,” or, “You said that you’re going to have this done. You’ve been working on this for three weeks. This should’ve been done a long time ago.” I don’t have that external forcing function anymore. I think that’s been a big challenge for me.
Rob: Yeah. You’ve talked about in the past. You’ve told me that you feel like you’re more extrinsically motivated, that having someone who’s keeping you accountable is the way you work best versus being intrinsically motivated. And that’s fine. There are successful entrepreneurs on both sides of that. This is not something that precludes you from being one. You lost your mastermind or it broke up how long ago?
Mike: A little over a year and then I started a new one but we’ve only met I think three times total.
Rob: In a year?
Mike: It was over the course of three months or so and then we haven’t had a call on five or six months, I think.
Rob: For all intents you’re not really part of a mastermind at this point. You ended a year ago. Now, didn’t your revenue peak around that time?
Mike: Yeah, it did.
Mike: I know.
Rob: A correlation?
Mike: Correlation, causation. That’s a valid point too. That’s an excuse.
Rob: Don’t say it. You’re going to say, “It’s hard to find a mastermind and it’s hard to be part of one.” I would say, “All right, Mike, you have choices. Shut your company down, number one. Number two, don’t be an entrepreneur anymore. It is a choice. Number three, email Ken of MastermindJam—mastermindjam.com—and try to hook with a mastermind. Four, keep doing what you’re doing. Don’t do a mastermind and expect your future results to be the same as they have been,” is probably what I would say.
Mike: Some of these things like the other thing that it could potentially be solved by us having a cofounder. I have talked to you about this before. I’m not opposed to having a cofounder or having somebody else who works in the business with me, but at the same time it’s a question of finding the right person and all that other stuff. But again, is that an excuse? Is that what I really want? The answer is I don’t know. Is that an excuse? Probably. Is it what I really want? I don’t know. I’ve gone out in that road before and I think things worked out fantastically with you, with Microconf, the podcast, and everything else, but my past experiences have not been all sunshine and rainbows.
Rob: That’s a tougher one because finding a cofounder is hard. You can’t rush that. That’s not an easy thing to do. I do think it could be a fit for you given that you would work better with someone pushing you on and you’re feeling accountable to that.
Mike: I totally agree with that. But most of the people that I know of, that I know well enough to say, “Yeah, I wouldn’t mind going into business with them at all,” most of them have their own things going on. It’s hard to find somebody who is in that same position because I’ve got Bluetick that is substantially far along at this point. One thing that I’ve run into when you have employees or contractors or whatever, is I feel like they’re not just motivated, but they’re way less critical of the boss’ performance or decisions and things like that because they’re like, “Oh, well. That person is the person in charge. I don’t want to challenge them as hard as I probably could or would if I truly believed in this other direction versus the one that they’ve chosen or decided to go in.”
Rob: Yeah, but that’s just a minor speed bump. I’ve worked with contractors and employees and I’ve had cofounders. It’s just something you get over. I think the deeper issue comes back to the two things that I said, number one, Bluetick is not differentiated. Number two, it’s because you’re not shipping enough. It sounds like you struggle with indecision quite a bit where you’ve ruminated on a question for a long time, for days or weeks, and sometimes just can’t break out of that to make the decision to move forward. So, you get stalled.
And then the motivation thing. You told me offline that you were bored, you weren’t motivated. At times you know what you should do, “I should go build this feature,” but you’re not motivated to do it. Is that right? Talk about that. Is it a health thing? I guess you don’t know. If you knew you would fix it, right? You don’t know if it’s lack of sleep. You don’t know if it’s low testosterone. You don’t know if you just don’t want to do the idea. Do you have any thoughts or even more background for people?
Mike: My doctor took me off of my testosterone and it wasn’t because it was too high, it was because one of my other blood tests came back, it’s too high. He was like, “This is way outside of the normal range so I’m going to take you off with testosterone for four weeks to see how that plays out.” I was about a week-and-a-half into it and I was like, “I have to take some of it right now.” The downsides or drawbacks of having it, having low testosterone is you get depressed, you have a hard time focusing, you can’t get things done, you can’t really think straight. That was happening to such a severe degree, I was like, “I have to take it today just to put myself at least a little bit back on track.”
I’m going to call him and try and see if we can cut this whole thing short because it is extremely detrimental to me right now but I don’t have any answers, I wish I did. There’s a lot of things where I’m just like, “This is boring to me.” Some of it has to do with the work that needs to get done. Again, is that an excuse? Is that just a reason that I’m using to justify not feeling bad about getting the work done? I get that, as an entrepreneur, not everything is always going to be fine. You’re not always going to enjoy everything.
There are some things that you like to do versus there are things that you need to do. If you can outsource those things that need to be done that you don’t like doing, great. I don’t feel like I’ve been in a position where I can outsource everything that I hate doing because there’s financial research and things like that.
Rob: You’ll never be able to do that. Even when HitTail and Drip were growing like crazy, I still came in and did a bunch of crap that I didn’t want to do. With TinySeed, I have more resources than I’ve ever had and there’s still crap that I’m dealing with that I don’t want to do. But (a) I tried to minimize it, and (b) I tried not to let it clog the top of my to do list. When it’s sitting in that Trello board I’m like, “Oh my gosh, I do not want to look at health care plans and setting up a 401(k) for us.” But it’s like, “I’m going to power through it, suck it up, and get it done. Then I’m going to come out the other side and reward myself by doing something super fun, make it some swag or something.” I don’t know. You can’t avoid that. You can’t avoid it entirely. You can minimize it.
We’re building businesses that we want to be a part of, that we want to run. We’re building it for our lifestyles. That’s great, but that doesn’t mean that 100% of the time, it’s like a trip to Disneyland. I know you know that. I’m being a little facetious, but that’s the thing I think you’ve struggled with a lot. There’s this indecision piece. You’ve expressed to me like, “I’m not motivated to do this thing.” Whatever it is, I know that’s what has to get done. I think you’ve got to figure that out because without that, you can’t move forward. You have to be motivated some days even through the struggles.
We have a mutual friend who runs a SaaS app, who has pretty major health issues. He struggles, he works four hours a day, and it’s tough for him to travel. There’s a lot of stuff that it’s just hard. It’s hard for him, but he runs a successful SaaS app, lives off, and has a few employees. He shows up everyday. In those four hours, I bet he’s pretty damn effective by the fact that his SaaS app still grows.
Mike: I haven’t found a system, I guess, that works for me in terms of preventing me from wasting time on the stuff that I don’t want to do or procrastinating to get those things done. I don’t want to stay here and say, “Oh, well. I just need to find the right system,” because I don’t think that’s the right way to go, either, or the answer to it. I do feel maybe I just need to experiment more and say, “Okay, try this for a week or try that for a week,” and be very deliberate about trying to get things done and shipping things, as you said, versus just showing up to work every day and a lot of motion without forward progress. I feel like I’m thrashing a lot. I don’t have an answer to that. Maybe the problem is that I’ve thought about what the answer to that is without actually doing anything to try and figure it out.
Rob: Yeah, not taking action. I think effectiveness is what you’re summarizing. Thrashing is the opposite of being effective. If this founder we’re talking about works four hours a day but gets a full day’s work done, he’s highly effective. Some people can work 10 hours. If they’re not effective, their business doesn’t move forward. We’ve talked about this in the past. The 80-hour-a-week startup people, I think, are probably not effective. That’s the reason they work 80 hours.
There’s a few exceptions but there’s a lot of younger folks. I used to work longer hours when I was younger too. It’s just not picking the right stuff to work on and then not focusing on that stuff, not wandering off to answer email, jump on Twitter, go to Reddit, really focusing. I think you can get a full day’s work done in 4–6 hours. Your full day’s work would have been 10 years ago, I believe, with the personal growth, experience, and stuff that a person can be more effective with less time.
There’s a couple things that I’ll throw out. One is that I feel like you should consider whether you want to keep doing this, to continue doing Bluetick, whether you want to continue being an entrepreneur. Here’s the thing. If you’re working in a contract job or if you were working a salary job, a lot of these issues go away because daily you would do a daily standup, or weekly, or whatever. You would have accountability. That external motivation would be there for you to ship stuff. That would make a lot of these go away. That’s a pretty nuclear option. In the interest of time, we probably shouldn’t go down that today. I do think it’s something for you to take a step back and just think about longer term.
Mike: Counterargument to that would be if I worked, did the right thing, and got Bluetick to a point where I was able to hire people to put on a team, that exact same result would come out of it.
Rob: Yeah, okay. That’s fine. That’s fine but you’ve got to get there. At the rate you’re going, you’re not going to get there.
Rob: I don’t disagree with you, Mike. This is Startups for the Rest of Us. The whole point is that we want to help people start businesses that give them personal freedom. The whole point of this podcast and everything we do is to feel free, to do what you want to do, and work on which you want to do. That would be my answer as well. It’s just, you have to figure out how to get there because you’re not making progress there now.
The second thing I would think about which is a less nuclear option, if we’re talking about options, it’s to go one step further than our mastermind and to find someone who would do a daily standup with you. Every morning, five minute phone call or five minute Slack. They keep you accountable. You subscribe to that. When you say, “These are the things I did yesterday. This is what I’m going to do today.” The next day, you come and you do the walk of shame if you didn’t get that done. You celebrate if you did and that extrinsic motivation is something that you think will help to do that.
What do you think about that is that, does it not matter? Because you’re so tired you can’t get anything done? Is the extrinsic motivation enough if someone was breathing down your neck? Would that be enough? Or do you think no? “I’m still too damn tired. I just have health issues and I shouldn’t do this.”
Mike: I would certainly try it. I would say, it’s pretty immature for me to say that it would or wouldn’t work. I suspect that it would. I seriously contemplated trying to find a way to get a one-on-one business coach or something like that, somebody who’s going to hold me accountable. You’re right. A five minute thing like that on a daily basis could be plenty. I don’t know. Without trying it, I can’t say for sure one way or the other. My inclination is to say, “Yes, that would work,” but it would also need to be somebody who is, I don’t want to say willing to yell at me because I don’t want to be inundated with thousands of emails saying, “Hey, I’ll yell at you.”
Rob: Sure because you don’t need yelling. You do need positive and negative encouragement and feedback.
Mike: I think that’s certainly worth exploring. I would say, it goes further than my thoughts about having a business coach who holds me accountable on a weekly basis because I think a daily basis would probably be better. That’s mainly because I feel like I could waste a lot of time during a whole week whereas from a day-to-day, I can’t. I don’t want to say the stakes are higher but the deadlines are sure. I’ve always found myself to be somebody who works extremely well with tight deadlines and time pressure.
Rob: Yeah, external motivation.
Mike: Yes. When I was doing consulting, the […] gets subcontracting through, they’ve held me in with a bunch of stuff. I stopped consulting from them probably a year-and-a-half or two years ago, but every single time I get an email from them it’s because something’s on fire. They want me to deal with it. I actually got to a point where from one customer to the next, every single one, everything was on fire and burning to the ground. They needed somebody to go in and fix it. I was their person because I was really good at it. I just got burned out with the travel. That was what the problem was. It wasn’t that I didn’t enjoy doing those things but I got burned out with the travel. The customers tended to be the same from one to the next. And the problem was repetitive. It got to a point where the problem was the same thing over and over. Then, I just got bored.
Rob: Yeah. Consulting is like a hamster wheel. You want to own something. You want an equity in something that has a longer lasting thing than just […] per hour.
Rob: Yeah, that desire.
Mike: Right. That was a big reason for me leaving and decided to do Bluetick instead because I wanted something that was going to need much more of that Rob’s flywheel as opposed to the hamster wheel.
Rob: Yeah. Obviously, we can’t solve stuff like these in a day. You and I talked about you taking some time to think about this, three weeks, four weeks where you think about both of what we’ve talked about today, some stuff we talked about offline, but really, do soul searching and figure out. I think there’s big questions here. It’s like, Mike, do you want to do this and do you want to do it bad enough that you’re willing to change? What you’re doing now isn’t working so you have to change it. Are you going to be willing and able to start looking at every problem as a speedbump rather than a roadblock?
Is this the right fit for you? Whether it’s this being entrepreneurship, Bluetick, it’s just those two. Does Bluetick have the potential? If you feel like you’re gaining your momentum and motivation to take a hard look and say, “How long will it take to get Bluetick to a point where it is differentiated?” My assessment is that, until you’re differentiated enough that you’re like, “Nope, we do this and no one else does,” or “We do this better than all these other tools.” Until you get to that point, you just don’t win many sales.
Mike: I totally agree with all that. I don’t even have to think too long about that one aspect of those. Do I still want to be an entrepreneur? For me, the answer is absolutely yes. The question for Bluetick is what does that look like moving forward? The reality is, the situation is I’ve got basically a seven month deadline at this point. I think you said there were some questions about how that shakes out with Google. I kind of know the answers to some extent. I still don’t have all the information, but I’ve gone past the last stage of Google’s verification with the exception of the security audit. That’s all that needs to be done. That’s the piece where I don’t know how much that’s going to cost. I don’t know what they have to go through or what other things I’m going to have to change. I’m still waiting to find out what that’s going to cost.
Then, I have to make a judgment called the end of it to say if it’s $15,000 and I’m going to make that $15,000 back in a reasonable time frame, not a big deal. Even if it was $75,000 or $100,000. If I were going to be able to make that back within three or four months, it’s not a big deal. If I’m in a revenue standpoint where it’s not going to happen in six months, eight months, ten months, then, no. I can’t justify even continuing with the product to that point. I don’t know what the price tag on it is right now. It’s a question of how far can I get in the next six to seven months to the point where I know how much revenue I’m going to be making three or four months down the road to be able to justify putting the cash out for that security audit.
Rob: You understand that while the security audit is one thing like we’ve talked about today, there are bigger issues. It’s shipping. Let’s say you pass the security audit and you pay for it. Bluetick is still not growing. Bluetick is still not differentiated right now. The reason again, going back, is you haven’t been motivated, or you’ve been bored with it, or there’s been health issues. There’s been all these things along the way. If that doesn’t change, it doesn’t matter what happens with the Google audit.
Rob: We talked about you taking some time to think about it and actually stepping back from the podcast here for about three or four weeks. Give you some clarity.
Rob: Some time alone. I know, give you a chance to maybe find clarity. These are hard decisions. This is retreat level kind of stuff where it’s a lot of thinking.
Mike: Yeah. The weird thing is these aren’t nothing we’ve really talked about. So far, things I haven’t thought about or considered over the past couple of years, it’ s just like I haven’t really taken the time to step back, objectively look at things, and take a hard look. I mean, if I do look at stuff and how things have gone, one constant that has been throughout the whole thing is me. Is it me? That’s a hard thing to say and the hard thing to admit to as well.
The question, can things change? Or will they change? Or do I want them to? I think that I want to. It’s just a question of how is that going to happen? How do I make sure that I don’t go through this process and come out of it and say, “Yeah, I’m motivated. I’m amped up. Let’s do this,” then put in time and effort for six months, then fall back into the same patterns again, I’ll say? That could happen. I don’t know but I need to step back.
Rob: That’s for sure. You know, Mike, I’ve always respected your technical chops, your intelligence, your writing, and you just have a lot of positive qualities. You’ve accomplished stuff in your life but you’ve definitely gotten in your own way. You’ve gotten in your own way more than I think you want to or should have. I think if you can start thinking about it, in terms of, how do I not do in the next six months what has happened in the past six months? We’ll see.
I’m going to be holding down the fort here for a few weeks. It’ll be good to hear from you. I’m sure people will be waiting with bated breath. We’ll have an episode, I don’t know, will it be 452 or 453? It’s the return of Mike. We get to hear from you, what you’ve been thinking about, and stuff.
Mike: Yeah, I don’t know. We’ll see what happens. I got to talk to my doctor and go back on a testosterone because it’s just, my God.
Rob: It’s kind of […].
Mike: It really is. You wouldn’t think that that does it. It was like, “Oh, that can’t possibly be that bad.”
Rob: I would totally think, any chemical in our body, when it gets that out a whack, it has these negative impacts that can be pretty brutal.
Rob: Well, thanks for delving into this today. I know this is not easy stuff to talk about. I appreciate your openness, honesty, and willing to delve into it. I’m sure the listeners do, too. This has over and over been voiced. This is like one of the favorite aspects of our show is when we do these things. We talk pretty open and raw about what’s going on.
Mike: Yup. I guess with that, why don’t you take us out then?
Rob: Yeah. If you have a question for us, call our voicemail number at 888-801-9690 or you can email it to us at firstname.lastname@example.org. Our theme music is an excerpt from We’re Outta Control by MoOt. It’s used under Creative Commons. Subscribe to us on iTunes by searching for Startups and visit startupsfortherestofus.com for full transcript of each episode. Thanks for listening and I’ll see you next time.
In this episode of Startups For The Rest Of Us, Rob and Mike talk about what KPI’s to look at when launching, key metrics you should track, and what they should be.
Items mentioned in this episode:
Mike: In this episode of Startups For The Rest Of Us, Rob and I are going to be talking about SaaS KPIs that you should focus on from day one. This is Startups For The Rest Of Us episode 434.
Welcome to Startups For The Rest Of Us, the podcast that helps developers, designers and entrepreneurs be awesome at building, launching, and growing software products. Whether you’ve built your first product, or you’re just thinking about it. I’m Mike.
Rob: And I’m Rob.
Mike: And we’re here to share our experiences to help you avoid the same mistakes we’ve made. What’s the word this week Rob?
Rob: Well, I got my tan on in Mexico. I mentioned that last episode. We got out of Minneapolis for about eight days and it was good. It was interesting that that my two boys got so much sun the first day. They got a little sunburn, but it wasn’t bad. They then the next two days had fevers and it was almost like they had sunstroke, because we have been out in the sun so little since whatever, October.
It was a trip. I was like, did they get vitamin D overload? What was the deal? But they both got sick. It was Mexico. Several of us had stomach issues, but the boys didn’t and they had this different reaction to things. They were all hot and they were tired with headaches. It was definitely like sunstroke attributes.
Mike: Interesting. I wonder if it’s just a byproduct of living in California first of all.
Rob: What do you mean living in California?
Mike: Well, because you live in California and then you moved to Minneapolis. Suddenly you’re not getting any sun and then you go back. It’s almost like dying of starvation or thirst, you suddenly get it, and then you get sick because of it.
Rob: Totally. The thing was, my boys tan really well. Before we went to Mexico, they looked grey. They looked like this really odd grey color, because again no sun exposure because it’s so cold. It’s super sunny here in Minneapolis, but it’s just so cold. You don’t go out without coverage. Your face is typically the only thing showing. If you’re going to be out for an extended time, you have gloves on, you have stuff over your arm. It was a fun trip overall and I’d recommend it.
We actually went to this smaller town called Sayulita. It’s about 45 minutes north of Port of Aorta. I know you mentioned you’ve never been to Mexico. For your first trip, maybe do go to Cancun or Port of Aorta. Those places are fine, we’ve gone there. Once you go there once, it’s super touristy, it’s packed with people and you’re not among the locals. You’re just a bunch of other vacationers. You’re hanging out with other tourists.
Whereas Sayulita is small and it’s 45 minutes north. It was a much better experience. It felt slightly more authentic and we still had access to what we needed in terms of food and such, but it did feel just like a better experience. Folks listening, if you haven’t checked it out, I recommend it. How about you, what’s going on?
Mike: I’m in the process of going through the scholarship applications that came in.
Rob: For MicroConf, right?
Mike: Yes, for MicroConf. I really think that if I were going to make any predictions right now, that this would probably be the single biggest mistake that I will make for the entire year. I forgot to include the email address field until basically like 2/3 or 3/4 of the way through it and I didn’t notice it until then.
Rob: You have a scholarship application like a Google form or Typekit, you send an email to the MicroConf list, you send people to come apply for scholarships, they give all this information, and you have no email address form?
Rob: That’s nuts. There’s no way to map since it’s third party. I was trying to get you the link back because when they click through the Drip email, there’s going to be their subscriber ID and the URL, but there’s no way to go back and try to get that matched up or anything.
Mike: No, not from a Google Form. The thing is, it’s not even that I actually forgot it, it’s that it disappeared because I copied the application form from last year. I don’t know what happened. I must’ve clicked something and accidentally deleted it or something, I don’t know. I didn’t notice until well into it and I was just like, “Oh my God.” I’m in the process right now of going through and trying to figure out how to reach each of these people. The nice thing is, because it’s an application, it asks for a lot of information.
Most of the ones that are missing, I have at least Twitter account information for it. I can send them a message and try and get in touch with them through that. Then other ones I’ve been able to map back to some of the different email lists that we have. The one really helpful piece of information is that I ask where they heard about it from and if they say email list, then I can go look at the email at list.
If they say that they heard from a certain person, I think there was only one, possibly two that I’m not sure how I’m going to be able to get that information. But I think for the most part, I’m going to be able to clear it out. It’s just going to take time and effort though. That’s the part that sucks.
Rob: That’s the thing. These are those fixable problems that are a ton of ground work to get done. It’s like, “I could have saved myself hours taking through this thing if I’d remembered to put the email address.” I have done this plus way worse. These are things that happen as you’re moving fast and doing a bunch of stuff. That’s brutal.
Mike: Oh well, I got to do what I got to do, though.
Rob: Yeah. My guess is you will never ever again forget to put an email address on a form like this.
Mike: Like I said, I don’t think I forgot. I think it’s accidentally deleted.
Rob: It deleted itself, yeah. From my end speaking of applications, the TinySeed application process ran for a month from mid-January to mid-February. I guess around four weeks. We got just under 900 applicants. It was a lot more than I thought. I was ambitious in hoping we’d get 400. I had heard through the GreatFind that a lot of more well-known accelerators get 500 to 700 depending on location. I’m sure Y Combinator gets more than that I’d imagine. It’s a big number and it’s what I’m very happy with.
It also creates what we call a good problem to have. The good problem is we have a lot of applicants. The bad problem is, I’ve been sifting through almost 900 applicants for the past two weeks. It’s just a lot of work. I’m not complaining obviously because this is what I would want to be doing, but it’s definitely going to be a process to get through all these. I already started having conversations with founders as I mentioned a few weeks ago. It’s going well.
Mike: Awesome. The only other thing on my side is that I’ve got an upcoming webinar that I’m going to be doing for hr.com which is kind of, I don’t know, you look at those 2-letter domain names and you’re like, “Wow,” it’s nice that I was able to finagle that. I’ll be doing a webinar for them on personalized email strategies to drive traffic, engage leads, close deals, and more. That will be on April 29th and I’ll link it up in the show notes in case anybody’s interested.
Obviously because it’s for them, their audience tends to be people who are reaching out to HR professionals in that particular space. They have a couple of different audiences, but one of them is the HR reps themselves, and then the other one is people and vendors who are trying to get in touch with HR people. This is basically aimed at those people who are trying to get in touch with the HR reps. It’s more of a general presentation that I’m putting together for them. It could very well be applicable to people who are listening.
Rob: We will link that up in the show notes.
Mike: I know I did the intro today, but what are we talking about?
Rob: Actually, we designed the entire outline around a listener question. I’ll play the voicemail in a second, but it’s about what are the key performance indicators or KPIs. By the way, I hate that term. I feel like it’s such an MBI, I hate it. It’s a shorthand that everyone understands. What are the numbers, the metrics that you should be tracking when launching and growing a SaaS app. Let’s dive into the voicemail here.
Adam: Hey Rob and Mike, I’m Adam Hawkins. Thanks for running the show, it’s been awesome. I’ve learned a lot from you over the past few episodes and I appreciate that both of you mention metrics and discuss these app businesses. One of you mentioned that you needed to have X thousand visitors on your landing page to pull your funnel in a previous episode. That really got me thinking of a fellow bootstrapper. Here’s my question, what are the KPIs and target values in launching in SaaS? I’m kind of thinking something along the lines of numbers that will keep me on track in launching my own SaaS. That’s all for me. Thanks guys and keep up the good work.
Rob: The first thing I want to say about this is, when we make statements like you need X thousand people to hit your landing page to validate or whatever. Often that’s a rule of thumb and it’s something to start from, but please don’t take that as gospel. I think in the past we’ve said you need 30 people, or you should talk to 30 people and have them say yes to your product, and consider that validated.
With Drip, I only did 10. It just depends. It’s all a spectrum. It’s like a risk tolerance. These numbers are not set in stone. None of this stuff is set in stone. With that said, there are rules of thumb. From doing this for 15 years, you start to see patterns and you know that a metric is out of whack if, let’s say I have a SaaS app that’s $50 Bucks a month, I ask for a credit card upfront, and my trial to pay is 10%. I know that is way too low and we have a major problem in our funnel.
That’s what we’re going to talk through today. These loose ranges when I see an app performing at 40% versus 60%, how we think about that, and how it indicates where you might have an issue in your funnel. It really helps you figure out what to focus on, because at any given time, you’re going to have one or more things that are just going sideways with your business. It’s just the nature of doing startups. You’re always that duck on the pond where above the water, you look like you’re just gracefully moving along, and under the water you’re just paddling like crazy to stay afloat. Your numbers are sideways and you got to figure out what do you focus on.
That’s really the point of this episode. It’s to try to give you some guidance so that you’re thinking about it as someone with a background. Even if this is your first time that you’re kind of taking the wisdom and the rules of thumb from us. Basically, folks who have seen these SaaS apps, seen a lot of numbers, know what a healthy SaaS business looks like, and know where to focus on to help improve them.
Mike: Yeah. As you said, these are guidelines and general patterns. It doesn’t necessarily mean that if you are in this range, then things are going great. I think one of the big drawbacks of using this information as gospel is the fact that you never really know whether or not you have room for improvement or how much will you have room for improvement. If you have this general range, let’s say it’s between 2% and 4% for any given number, and let’s say you’re smack in the middle at 3%, that seems reasonable.
There’s probably other areas in your business that you should be focusing on, but is it possible that that number could be 6% or 8% depending on your type of business or the vertical that you are in. The answer is absolutely yes, it could be that high, but you don’t really know unless you are directly comparing yourself against other businesses that are similar to yours.
Again, these are general guidelines. They are helpful in terms of determining whether or not you should continue to focus on that area. Maybe you should, but chances are good that if you’re in the general ballpark, I’ll say that there’s other things you should be going to look at before you come back and try to optimize and double down on whatever that particular thing is to improve it.
Rob: That’s the thing, if you’ve ever gotten a piece of mail from your city water quality control board, they’ll show you all the lead and this and that, and then they’ll show you the acceptable ranges, because without the acceptable ranges, you have no idea what the numbers mean. It’s like one part per million of lead. Does that mean anything to you? It doesn’t to me, so then you want to see the acceptable range, or if you get a blood test, Mike. I know you’ve never had any test on you.
Mike: Of course not.
Rob: I’m curious. You’ve talked about it on the show, that’s why I’m bringing it up. I get a blood test every few years or whatever. There’s all these numbers that mean nothing without that guideline on the right that this is the normal range. That’s really what this is trying to do. I don’t want to over couch this and say, “These numbers? We’re just going to ballpark them and it don’t really mean anything.” They do mean things, but there’s always the caveats of, if you’re selling a $19 a month SaaS—I will try to call those out as we go through because I’ve sold $19 a month SaaSes—and then if you have one that’s $500 a month, the numbers are going to be different. We’ll try to talk through those differences as we go.
Mike: We’ve talked about KPIs and various metrics in a few other episodes. The first one was episode 112 where we talked about the startup metrics for Pirates and that’s based on AAARR. Is that what it is? I forgot.
Rob: Yes, something like that. It’s either AARRR or AAARR, I forget which it is.
Mike: I think it’s AARRR. There’s another one, Episode 187 where there is a whole slide deck that we went through from Andrea’s Cleaner. That slide deck is around 150 pages or so. It’s really in-depth. There’s a lot of good information in there. It specifically talks about the fact that your KPIs are going to change over time and very early on, there are going to be data points that you’re looking at. You have to be really careful about how you interpret them because the numbers are probably going to be much smaller, and your product market fit isn’t quite right yet.
There’s a lot of caveats to those very early numbers. We will call them out as well, but that’s something really important to keep in mind when you’re trying to figure out whether or not you should optimize something more or move on to something else. The third episode is Episode 231 with Ruben Gamez where you and him at the very end of the episode started talking about some of these general ranges that we’ll rehash in this episode.
Rob: I’ll be interested to see how close the ranges are. We literally did it off the cuff in that episode, and I’m kind of getting into it off the cuff again today. I’m hoping that the ranges are pretty close. What I’d like to do is start at the top of the funnel. Going from unique visits to your site and just go all the way down the funnel. Visits-to-trial, trial-to-paid, turn, blah-blah-blah, and go down the line.
So, starting at the top of the funnel with unique visitors. This is an interesting one because I don’t think there is a KPI for this. You want the most unique visitors you can get that are targeted at your website in any given month. I have had software products that get literally 1500 unique visitors a month that sold upwards of $4000 or $5000 a month in software. Now, it was not SaaS, it was a $300 one time purchase. The traffic was targeted, it was in a pretty tight niche, and it obviously converted quite well.
Whereas most SaaS apps I know, you’re going to be priced between let’s say $20 and $100 a month for your starting tier if you’re doing self-service. You really want to start getting into that 5000-10,000 uniques a month to try to start scaling it up. The challenge here is, if we’re talking about day one and you’ve just launched, unique visitors doesn’t have much meaning yet. What you really want to do is you’re still trying to validate your product, you’re trying to find product market fit, driving more traffic, trying to split test, and look at these aggregate numbers isn’t helpful yet.
In the early days, you should probably couch all of these metrics with that. In the early days, your numbers are going to be so small. When you have 10-20 customers and one of them turns, that doesn’t really mean you have 5% or 10% churn rate. It does technically, but it’s meaningless because you don’t have enough numbers to accurately measure things. I think that is another thing. Early day KPIs are different than later day KPIs. Early day KPIs are really how many people am I talking to? Do I think we have product market fit? Is churn going down? These are marketing resonating.
There’s a lot more qualitative questions that I ask in the early days than in the later days. You’re looking at more quantitative, because you’re just past that point. It’s hard to say for everyone, but I feel like when you hit about somewhere between 5000-15,000 MRR, that’s where I start to shift into that. You probably have 100-200 customers. That’s where you can start having numbers that are more easily measurable and you can start seeing trends instead of seeing these very spiky results because the numbers are small.
Mike: I think one of the interesting things about the number of unique visitors is that, as you said, all those not edge cases but those different factors that play into it like price point, how long it’s been around, do you have product market fit, all that kind of stuff. One of the really challenging things when you’re that early on is that a link on Hacker News, for example, can drive traffic through the roof and it is untargeted traffic. It’s good to get it and it’s nice to see that there are more eyeballs coming to your site, but what it does is it really heavily skews your metrics, because those people aren’t necessarily there as interested people, they’re there because you got a PR bump and that really seriously starts skewing your metrics.
You really have to be careful when you’re looking at everything else just because if you’re only averaging let’s say 3000 views a month, and then suddenly you get an incoming link and you end up getting 5000 over the course of a couple days, that 5000 is going to overshadow your typical 3000. And because it’s untargeted, your visitors trial and your trial-to-paid, all those numbers completely gets out of whack because of that. It skews them. It makes it a little bit more challenging to figure out what is my actual visitor-to-trial rate. You have to look at that and say, “Well, how well targeted was that traffic? Do I apply a percentage to that?” Well yes, 5000 people, but maybe only 0.5% or 1% of them were actually targeted then you multiply out from there and figure out what your actual visitor trial rate would be.
Rob: Yeah. The nice part about all these metrics but specifically visitor trial is, the more visits you get and the more trials you get, just that the further along you get, it does standardize. I used to be able to look in Google analytics or whatever dashboard I was running and just instantly know if it was a good number. My range for this is for SaaS, I want to specifically say that. For info products or for onetime purchases, you can get dramatically higher numbers, but people signing up for SaaS apps with a credit card upfront, I want to be between 0.5% and 2%.
The difference there could be a lot of things. It can definitely be your messaging and your marketing. It can be the quality of your traffic. It can also be your price point and that’s a big one. If I had an app that was $10-$20 a month for the lowest pricing tier, I would want to be closer to that 1.5% and 2% number of unique visitors translating into trials with a credit card on file. If I’m selling something that’s $50-$100 a month as the lowest tier, I’m going to be looking between 0.5% and 1%, 1% would be a pretty nice number to get on that.
Something else to think about is this is for one funnel. That’s like the visitors and turning into trial. You can also have a longer funnel that visitors turning into email subscribers and then you know how many email subscribers, over time, turn into trials. You can look at that number. If you have a good converting landing page, let’s say you’re sending either ad traffic or SEO traffic, and you’re trying to squeeze for an email address, and your offering something of value to folks with download in exchange for that email, I want the range to be between about 15% and 25% of people entering their email address on the landing page. I’ve had upwards of between 40% and 50% for certain calls-to-action with the really targeted traffic, but that’s pretty exceptional. If I’m below 15% I’m a little concerned and if I’m below 10% then I’m doing something wrong. The traffics mismatch or the call-to-action isn’t very good. If you’re going to do that, it’s a longer funnel, it’s a longer journey, but you need to then look at your email numbers in aggregate and see how many of these are turning into trials over time.
That’s where you need a good system with good tracking like Drip or I believe ActiveCampaign could do this. I’m not sure that Mailchimp, I haven’t used it in so long, I’m not sure that it’s easy to do that with Mailchimp. If you are going to go that route, you’re going to want to dial in the analytics at least to the point where you can have a relatively good insight into how many new subscribers are converting into trials. One other thing, if you’re not asking for credit card upfront and your unique visitor-to-trial rate is 5%, I’d say 5%-15%, but 5% is actually too low. I think I’d want to be more in probably 10%-20% range is where I feel comfortable. This one I have done very little because I tend to ask for credit card upfront. I have done tests with it and such, but I’ve talked to a bunch founders who run credit card free trials and that does tend to be the range.
Number three, the next KPI is of course trial-to-paid conversion. If I’m asking for a credit card upfront, I want between 40% and 60%. If I’m at 39%, I know that I have a problem. If I’m at 58%, I know that I’m doing quite well. I mean that’s really towards the top range. There was a time when Drip bumped above 60% at different times, then you know you’re kind of killing it and your onboarding is doing really well. When I took over HitTail, I acquired that in 2011, it was credit card upfront and the trial-to-paid was 15%, and so you know that there’s a major problem in onboarding. That was one of the first things that I cleaned up.
That’s why these ranges are fairly important is that you know you’re so out of whack there that if you fix that, you’re going to be going to be in a better position. If you’re not asking for credit card upfront, trial-to-paid, I would want to that one between let’s say 5% and 15% is probably a relatively decent mark. I mean I would want to be between 8% and 15% myself, but you’re just kind of a lot lower when you’re not asking for credit card, that’s kind of the nature of the beast.
Mike: One of the things that I think is probably the most challenging with trying to find out or to track some of this information is that when you’re very early on, these numbers are very misleading when one person cancels. If you’ve got 10 customers or 20 customers, having one or two customers cancel is a huge deal. One or two people who come through the funnel that don’t convert, let’s say you’ve got four of them through and not one of them converts, that’s 0%. Even having a couple after that, it doesn’t really put the number back to really where it should.
You have to eyeball those things and try to capture as much information from people who are leaving or not following through with the trial to figure out what it is that drove them away. Why did they not actually decide to follow through and sign-up for the service or continue using it. Use that information to try and figure out what it is that you’re supposed to do because the numbers are not going to be enough, especially early on.
Now, that’s not to say you shouldn’t track those numbers, just that they’re going to be misleading early on. Over time, it will get better, but those first few that come through, first 100-200 that come through, is going to be hard. You have to talk to people to figure out what the reasons are for them to move in one direction or the other.
Rob: Exactly. The numbers aren’t going to tell you the whole story. Especially in the early days. That’s something you got to dig into. The fourth KPI we’re going to talk about is churn. I’ve seen people look at churn as a blanket number. It really obfuscates what’s going on underneath. If you go to Amazon and you see that the average rating for something is 2.5 stars, but there’s actually 101 stars and 105 stars, I guess that would actually average to 3%, but you get the idea. 100 0 stars and a and 100 5 stars in average is 2.5%.
If you just have the 2.5%, it looks like a crappy product, but as it turns out with five and zero, the zeros are probably either misunderstanding, or there’s something wrong, there’s more information under that data. Churn I feel is the same way. If you look at your churn across your entire customer base, you’re missing some information. What I’ve typically seen the most success with is to look at your first 60-day of churn, and then your post 60-day churn, and separate those numbers out.
Sometime it’s up to 90 days, but really, a lot of people do an extended trial where they might enter their credit card. When the trial expires, they pay one month. They never get set up. They never get onboard and then they churn, but really what they did is they were kind of like a trial that didn’t convert to paid. I started seeing these patterns, it was before HitTail, but when I got into HitTail and really dig into the numbers, it was a huge difference. Literally in the first 60 days, especially if you’re asking for credit card upfront, but it can happen both ways, you might see churn upwards and a per cohort of between 20% and 40%.
It can be a huge number of people that are canceling there and 40% I start to feel uncomfortable, 20% I actually don’t feel terrible about that for 60 days. Then post 60 days, you want to get your churn obviously as low as possible, but I feel most comfortable in let’s say for lower priced products that are not enterprise, not annual contracts, I think between 5% and 8%. If you’re at 9% or 10%, it’s pretty brutal, 8% is about the top in where I feel comfortable. Realistically, if you’re a big SaaS app, I think WP engine probably has negative churn at this point.
I remember Jason saying in the early days, they had 2% churn. I’ve had apps that have 2% to 3% churn in that post 60-day, post 90-day mark. That’s where you want to get to. The problem is, the lower your price point, the higher your churn tends to be. That’s why a lot of folks go up market, a lot of SaaS apps do. If you can, you want to get to net negative churn where you do churn out 2%, 3%, 4% but just the growth in your existing customer base of people upgrading actually wipes out the churn. It’s a crazy thing. I’ve seen it firsthand. It just catapults your growth. Those are my loose numbers that I keep in mind when I’m looking at churn rates.
When I see someone come through with a 12% monthly churn rate, I think that’s the first thing I would attack. If I see someone come through with a 3% churn rate, I think that’s amazing. I believe you have a product market fit depending on how many people you’re putting through your funnel. Let’s look at your other metrics to figure out where we should focus position not be on churn, if your number is that low.
Mike: One thing that we should probably drill into a little bit is the idea of that negative churn, because I think that some people might get confused about that. It’s not that you’re gaining more users than you have actually signed up. Although in some cases that may actually be true, because if somebody comes in and then they invite somebody else on their team, initially they sign up with one account and then they may fall into a different tier. That’s part of where that negative churn comes from because people are essentially upgrading to a higher tier paid accounts.
Whether they’re adding users, or going to a new pricing tier, each of those things can qualify. A question for you Rob, because I’m actually not sure about this, does it qualify if they upgrade from a monthly plan to an annual plan? I don’t think that it does.
Rob: No, it doesn’t. The annual plan should be divided by 12 and added to your MRR anyways. It’s not net revenue. It really is actual MRR that I’m looking at. I’m glad you brought this up because I should have couched this when I was talking about churn and the churn you should focus on is revenue churn, not user churn or customer churn. Revenue churn is when you look at, we started the month with $100,000 in MRR and we lost $10,000 in MRR, so that’s a 10% revenue churn.
First is we started the month with 1000 customers who are paying, 1000 credit cards on file, no matter how many users are within each account. We started with 1000 customers paying us and we ended the month with 900. That’s 10% user churn or customer churn. I’ve always looked at both. By far, the most important is revenue churn. I don’t think you could have negative customer churn, because you can’t add more customers than you signed up, but you can have a net negative revenue churn. That’s where you only lose a small amount of revenue from people canceling, but the rest of your customer base is either so large or they naturally move up tiers and pay you more for stuff.
Drip is a great example of this. As people’s lists grew, they naturally moved up in tiers automatically. There was just a natural movement towards paying more to your ESP. Those are the kinds of businesses that can have negative churn. Slack probably has a negative churn rate, because teams do tend to grow. Yeah, companies go out of business, there are layoffs now, but there are layoffs from time to time in your customer base.
In general, teams that sign up Slack and start paying, I’m guessing these are startups that are adding more and more people and Slack charges $6 or $8 a month per person. I would guess with the stickiness of Slack, they’re kind of gross churn is very low. I bet their net churn including expansion revenue is what it’s called, as people expand and hire tiers is quite substantial. That’s the holy grail of SaaS.
I know people say, recurring revenue is the holy grail of software, and that’s why SaaS is such a big thing. Net negative churn is the holy grail of SaaS if you want to get into it, because that just snowballs and it means that if you do nothing, your company grows. It’s crazy to even think about it when you actually look at charts, and you look at how the numbers work out, you look at graphs of it, once you hit net negative churn, you don’t need to do much. I shouldn’t say you don’t need to do much, but you need to do a lot less to grow a lot faster is what happens.
Mike: Is that where the passive income comes in?
Rob: Passive income, money wisely. Let’s run through the last few pretty quickly. The fifth thing is MRR and that’s just your monthly recurring revenue. As we said earlier, it can get tricky if you have annual plans, you’re supposed to technically divide by 12 that annual plan and then add it onto your MRR. Hopefully you have a software that can do that like Baremetrics or ProfitWell. MRR was the number that I tracked religiously. Every night I would get an email after billing ran and it would tell me what MRR was, what the daily billing was, and all that stuff.
It’s kind of a no brainer when you think all of us track it and it’s something that talks about the health of your business. The other one is MRR growth. I always looked at this as dollar rather than percentage. A lot of people talk percentages, but it’s like when you’re at $1000 MRR, or you’re at $100,000 MRR, the percentages obfuscate so much stuff. Truly, how many dollars did you add and you want to look at not just net add, but you want to look at how many did you lose to churn, how many did you add from new customers, and how much did you add from expansion revenue. Seeing those three different numbers and then the net. There’s four different numbers that you can get into and a lot of people who are really into their SaaS numbers know these numbers cold and know where they want to be with them.
The last one is ARPU, average revenue per user. I like to call this ARPC, which is average revenue per customer, because frankly when I’m charging people money, I think of them as customers, not users. Like Drip, one account might have 20 users in it, but to me that’s a single customer. It’s apples to apples, but it’s just a terminology thing. Average revenue per user, average revenue per customer.
Frankly, if your average revenue per user is $10 or $20 a month, you have a nice little business. You can grow that to something, but the odds of you growing that to a multimillion dollar business are very low. I’ve seen businesses with very low churn, good trial-to-paid, and average revenue per customer of $10 or $15 a month. I think that’s going to be a great 30K MRR business. That’s not a bad business to have, but you’re going to struggle to get past that 30K or 50K mark. If you want to build something into a 7-figure business, not across the board, not unequivocally but in general, you need that average revenue per customer to be upwards of that $40, $50, $60 and up price point.
You want to be in triple digits. You want to get there eventually. You don’t have to be there on day one, but aspiring to get into that $100 to $500 per month, per customer. That’s where you can scale, it’s so much easier to scale a business into that seven- and eight-figure range. Because you have the money to acquire customers, the payback is fairly quick. If most people are paying you $200 a month, you can spend quite a bit on ads and salespeople. Frankly, churn will be lower. It’s always counter intuitive to say this, but lower priced products, lower ARPCs tend to lead to higher churn.
Mike: Something we didn’t talk about when we were talking about the revenue churn between the first 60 days and then post 60 days was that, if you do any sort of a pricing change that can have a massive impact on what your revenue churn looks like. If you raise prices, let’s say by 50%, make things simple. If you raise prices by 100%, you double your prices. If you lose less than half your customers, then technically you’re coming out ahead because you’re making more money. In theory, your infrastructure costs have probably gone down. The obvious downside of that is, potentially losing customers after that first month or after you initially make that change, assuming you didn’t grandfather them. At least be a little cautious of or cognizant of, because that that can seriously change some of those numbers.
It’s not something you have to worry about, as you’re launching, but down the road when you are calculating these numbers and try to figure out how to grow the company, those are things that you should at least bear in mind when you’re trying to figure out if you’re running into financial issues and you need to be able to make more money. You can just do some calculations and say, “Well, if I raised by 10%, this is how much we could get, and how many of those customers are we going to lose the because of us raising those prices.”
The other thing that I was thinking about was that, all of this information sounds great to be looking at, but how do you actually go about tracking it? There’s a lot of different tools out there that you can use. Sunrise KPI for example is one. We can look this up in the show notes. CYFE is another one. Honestly, the simplest thing to do, instead of going in and trying to figure out a bunch of different tools and things to integrate, you can just use a spreadsheet. Whether it’s a Google doc or Excel spreadsheet, it doesn’t really matter. Throw your information in there, maybe update it. You can do it as much as once a day, but you could also do it once a week or once a month, and it really gives you a sense of where things are at and what you should be focusing on. If you’re not plugging this information in and at least looking at it, then you’re never going to do anything about it. That’s the big problem that most people run into is they just don’t even look at these things or they don’t update them and keep track of them.
Rob: Yeah, that makes sense. I mean, I’ll admit with pretty much all, I think without exception, all the SaaS apps I’ve ever run, I’ve built a little scrappy page and these are just simple queries. You should have all the stuff in your own database, I’m imagining. I always did and it’s a little bit of a pain. Churn can be a pain to calculate that can take some time, but I remember hacking together a dashboard with most of these numbers in a few hours, one evening.
I was listening to music and have the lava lamp on sipping Bourbon and I just hammered through these one at a time. I really don’t have a very impressive life, do I, Mike? It’s kind of sad that that would, but it was a fun night, I’ll admit. Because once I had that, I was looking at that thing every day. It was super cool. Then by the time we were launching Drip, I remember telling Derrick, “These are the numbers I know I need. Let’s figure them out,” and it did take him probably a day to get the initial version done.
We had to kill a day of developer productivity to do it, but it was really nice to (a) be in control of those, to (b) have a all in one place, and to have them displayed in exactly like the order that I wanted. I mean, we even have trailing 7-day trials, how much each day it had, have it trailing 30-day. Then we modified it and adjusted it over time. The other cool thing is that whole dashboard and admin area became a nice training ground for new developers. We’d bring in like a junior dev or whatever. You may not want them to push production code into your app right away, because it could break something for customer, but that becomes a nice playground to be like, “Hey, let’s add this number or let’s tweak this,” and it becomes this code base that can get screwed up. If the admin console crashes or has some weird thing that happens in it, it’s not the end of the world, because it’s just us using it. That was kind of also a bonus to having that all built out.
Mike: I’ve daily email sent to me from Bluetick just to see a lot of those different pieces of data.
Rob: It’s a good way to do it. I always had it as a shortcut on my browser but it’s same thing, and that’s your pulse. We actually called it, the page that displayed all this, we called it Pulse in Drip. I always thought that was a pretty fitting name, because it’s the pulse of the business.
Mike: Got it, cool.
Rob: Forty minutes on SaaS Metrics, KPIs. I think the next episode needs to just be all jokes. You and I need to just talk about movies and jokes.
Mike: I don’t know if that’s going to be a very compelling episode.
Rob: That would be even worse than this one. All right. Let’s call it a wrap. I guess I’m the wrap guy today.
Mike: Yes, you are.
Rob: This whole episode was outlined based on a single listener question. If you have a question for us, you can voice mail number at 888-801-9690 or email us at email@example.com. Our theme music is an excerpt from We’re Outta Control by MoOt used under Creative Commons. Subscribe to us in iTunes by searching for Startups, and visit startupsfortherestofus.com for a full transcript of each episode. Thanks for listening. We’ll see you next time.
In this episode of Startups For The Rest Of Us, Rob and Mike answer a number of listener questions. The topics include defining product market fit, using cheap developers, when to quit, and more.
Items mentioned in this episode:
- The Quiet Light Podcast w/ Rob Walling
- Closer Sharing
- Sean Ellis: 40% “very disappointed”
Rob: In this episode of Startups For The Rest Of Us, Mike and I discuss the definition of product market fit using inexpensive developers, when to quit, and more listener questions. This is Startups For The Rest Of Us episode 409.
Welcome to Startups For The Rest Of Us. The podcast that helps developers, designers, and entrepreneurs be awesome at building, launching, and growing software products whether you’ve built your first product or you’re just thinking about it. I’m Rob.
Mike: And I’m Mike.
Rob: We’re here to share our experiences to help you avoid the same mistakes we’ve made. Where this week, sir?
Mike: Do you hear that?
Rob: The silence behind you?
Mike: Yes. The kids went back to school. Oh my god, it’s so awesome.
Rob: You’re right. It’s nice that they’re not in the house except for […] of the day or eight hours of the day with buzz time.
Mike: Yes, yes. It is. There are certain cartoons that they watch that could not end soon enough because they’ve watched the same episodes over and over. I’m just like, “Oh, please. Let it stop.”
Rob: Totally. Our kids go back next week. Although by the time that this airs, they’ll have gone back, but as of the time we’re recording, they’re not back in school yet. I’m definitely looking forward to that.
Mike: Yup. What’s up with you?
Rob: Well, I’ve been listening to a few books. As always, I kind of have my audio queue full at all times for when I get through all the podcasts episodes for the week. One I listen to is called Brotopia. It’s about kind of the Silicon Valley boys club and I enjoyed it. It’s by Emily Chang. It really brings a lot of stuff to light. I’m very glad she wrote it. I wasn’t surprised by a lot of it, I was surprised by parts of it in a bad way, just about stuff women have had to deal with in Silicon Valley.
There was a small portion that I felt like, I mean, literary 5-10% of it where I was like, “Okay, I feel like you’re taking this a little too far.” Or, “This is a little over the top.” Or, “This particular argument or example just feels like a little bit sensationalist,” but all that to say, solid 80-90% of it, it was like, “Oh my gosh, yeah.” Things are beginning to change but it’s not nearly enough. I appreciated that book. I think it’s something interesting to read or listen to if that kind of stuff interests you–and it should. Diversity inclusion is something that everyone is thinking about these days or should be.
Another book that I listened to that I didn’t think I would like actually. But I’m a huge fan of Paul Simons—Simon and Garfunkel in particular. There’s a new biography called, Paul Simons: The Life. I figured that anything before Simon and Garfunkel, like his growing up and anything after Simon and Garfunkel would not be that interesting to me. But it turns out it was well-written, it was fascinating, the story, and just the way he reinvents himself every album. […] is painful process of being a maker in what he does. I loved just hearing about creators and how much—it’s the struggle. It’s the struggle of creating things and how hard that is. Anyway, it’s highly recommended if you’re at all into Paul Simon or want to meet and like the artist’s journey, kind of biographies.
The last one is just a fun diversion. I buy a lot of books thinking like, “I’m going to go out on a limb here. It’s not typically what I love.” But it’s by David Spade and it’s called, A Polaroid Guy in a Snapchat World. I’m not a David Spade fan, in particular. The only movies that I ever saw him in were like Tommy Boy. I think he was in two Chris Farley movies. David Spade was on Saturday Night Live in early ‘90s, I believe. I have not followed him, I have no connection to him, but man, this book was funny. He just turned 50 years old and he just talks about kind of being in 5 television shows, and 24 movies. He’s a famous person. He just talks about life in LA, and Instagram, growing up, and other things. It’s funny. I enjoyed that. I feel like at first, it kind of set off in a beaten path. It was something that I could listen to that would take my mind off of work, which is something you’ve talked about a lot, how you read fiction to give your mind a rest from it.
Mike: Yeah, very cool. I haven’t read any of those few books. But I’ve run across Brotopia before, at least I’ve seen mentions of it in a couple of places. It’s interesting but as you said, I wouldn’t expect a lot of the things that are talked about in that to be necessarily surprising because there’s a lot of stuff that’s come out of the Silicon Valley culture that is just unacceptable, to be perfectly honest about it.
Rob: Yeah, it’s pretty over the top.
Mike: What are we talking about this week?
Rob: This week we are answering some listener questions. We have one question that we’ll kick it off with. It’s about using inexpensive developers. An anonymous listener wrote in, he said, “I discovered some of your videos on YouTube and the principles that you teach specifically the idea of an MVP have turned my thinking upside-down and got me really stoked. I’m a lead developer for a government contractor and I have been for 12 years. I believe that good software cannot be pounded out by cheap labor. I’ve seen too many programmers not willing or able to separate concerns like DRY Code–Do Not Repeat Yourself Code, and otherwise make unmaintainable convoluted messes. On the other hand, I need help for my on-the-side startup and cannot pay anywhere near the $100,000 a year for good developer in the States. I’m considering trying cheap overseas labor and I will attempt to review a code and set a standard to keep the code base at an acceptable level of quality. I have a couple of questions.”
This is good stuff because we often, Mike, we often get the questions of, “I’m non-technical. How do I find somebody else? How do I validate?” But this person is technical and so this is a boat you and I have both been in. It’s interesting, right? Because back in, between 2005-2010, I was very much in this boat. I knew you have had folks working on both Audit Shark and Bluetick.
He has three questions. The first one is, “Have you tried this and do you have lessons learned?” Second question is, “I’ve heard you say don’t worry about scaling it until you prove your market. Would you take that as far as hiring cheap developers to write unmaintainable code for your first iteration of the product, assuming the code actually works, of course. Building, kind of a crappy, and repeat, and then rewriting it later.” The third question is, “How have you approached hiring developers?”
We may not be able to in-depth answer all of these. We have talked about hiring developers in the past. I actually talked about it on the Quiet Light podcast, in specific where I went to 5 or 10 minutes of just that topic. Maybe let’s send people over there or they can search the back catalog because we have transcripts of every episode. If you go to startupsfortherestofus.com, type in hiring, you can grab some old episodes from iTunes and you can listen to that. Maybe we just tackle the first two in this episode.
The first one, have we tried what he’s suggesting, kind of hiring cheaper than $100,000 a year labor, and what are our lessons learned from that.
Mike: Yes, I have. Lessons learned is that your expectations for them should be lower than if you were paying more. You can find developers as cheap as $5 or $10 an hour, but you’re going to get what you pay for. I found that when I went above $20 an hour, I stared to get better developers. You’re able to get a wider variety of in-depth experience as well. If you go to the lower levels, you’ll just find somebody who says, “Oh, I can do front code and I could do backend code,” but they can neither one of them very good or they’re really good at one and they’re just terrible at the other. They can do it, they just are not good. You’ll find that the code is completely unmaintainable, and it’s very difficult to work with even if you lay out like, “Here’s the entire process of exactly how to do everything.” It still is just probably not going to work out very well.
That said, leading into number two, not scaling until you prove the market which you take that as far as hiring cheap developers to write unmaintainable code for the first iteration of your product. That’s a harder question to answer because it depends on how long it takes them to get there. The mistakes that they make are going to bite you and there’s two different ways. One is, whatever rewrite you have to go through, and the second is the goodwill that you’re earning with your customers. Because if you’re going through and you’re continually breaking things that used to work, they’re going to get angry with you. It’s just going to make your life more difficult in terms of trying to build the business and build revenue because they’re going to leave, they’re going to churn out because like, “Oh, this product, it breaks every other minute or every other day whenever something new goes in. It’s just a complete mess.” It’s going to be hard to go that route.
I would definitely, if you can afford it, hire slightly better developers, pay more than you probably think that you can potentially afford, or at least you thought that you can afford because it is going to be worth it. You’re not going to find that you’re going to get a $15 or $20 an hour developer. You can get two of them and they will be just as effective as a single developer that’s at $40 or $50 an hour. You’re better off going to better developer route even though you’re probably going to get less code because of the fact that they’re going to do a better job at it.
Now, obviously, there’s wide range of skills between people. Some people may charge $40, some people may charge $80 and they could potentially be similar in skillset not likely, because people tend to know what their value is but definitely, at the lower levels, everything’s like a total crap shoot. Once you get into the middle of $40, $60, $80 an hour, it changes quite a bit. There’s a, I’ll say, an order of magnitude. Difference in capabilities in somebody who’s below $20 versus above $30 or $40.
Rob: Yeah. His statement of, “I really believe that good software cannot be pounded by cheap labor.” It’s like, yeah, don’t be too dogmatic about that because cheap is relative, right? I was charging $125 an hour as a contractor. People would go to hire me and then say, “Well, I can hire someone for $50 and they’re cheap.” Is $50 an hour cheap or is $5 an hour cheap? Keep in mind that this is not absolute. I like your point about—and I’ve found the same thing—$5, $10 an hour, it’s going to be a mess. Know that going in if you’re going to build something like that with $5 or $10 amount.
I have found that decent developers in the $15-$25 an hour range much like you were saying. The interesting part is they maybe good developers but they tend to have something else that leads them to only charge that much. They might have kind of a chaotic personal life, or they might not be able to work as many hours as you need them to, or they might be just a little more sporadic on the hours than you want them too, or they might not be detailed on other things. You can find a good developer who’s cheap. There’s probably something else they’re not super reliable or something like that. That’s a thing to keep in mind is, it’s all trade-offs.
I can think of 20 reasons why any startup that I’m going to start is going to fail. Even back in 2005-2010, when I was much more in the same boat as the original question that asker here, yeah, I was taking risks. I hired a bunch of people that were in the $15 range. Some of them were really good, and some of them were terrible, and I just had to vet them. I found PHP developers, I found ColdFusion developers, I found Classic ASP developer because I had a bunch of different code bases, and I didn’t have the bandwidth to do this. Can this work? Yes, it can, but it’s not going to work the first time. The best developer for $20 an hour is not going to magically drop into your lap. You’re gonna have to look, and you’re going to have to vet, and you’re going to have to put in the work.
I’d say, don’t be too dogmatic about, “Oh, someone need to be making about $100k a year in order to be a good developer.” That’s not true especially not true if you go around the world. But even in the US, you can find good side labor with people who are paying less than $100k a year especially if you hire a junior or mid-level and are able to train them up. That’s a whole other story but we did that with Drip. We took two developers right out of code school so they literally had, I don’t know, six weeks to two months of coding experience. They have done a little on the side. Could they write great code from the start? No. But we had a bunch of safeguards in place. Derek did a lot of code reviews and he kept a close eye on the code base and the code base grew—it’s very large now, and it’s still a very solid code base with a lot of tests covered. Yes, this is possible.
Second question is, “Would you take it so far as hiring to develop unmaintainable code for your first iteration of a product?” My answer is probably not. Personally, I wouldn’t do that. I care too much about not having to rewrite the product because once you start getting momentum, and you start getting a few K in MRR, the last thing I want to do is go back and spend six months rewriting the thing. I’ve seen companies do it. It is agonizing. It kills the founders, not literally, but it is so painful to do.
If I’m going to do it from the start, I would just tackle a smaller problem and I would try to tackle part of the MVP without software at all. You’ve heard us talk about this. Use excel spreadsheets, use emails, there’s a bunch of other interfaces, use cheap virtual assistants to do the grunt work. There are ways to do this without building software. As developers, we think software is the answer to everything. In most cases, it is not. There are some when you need it to be.
If you’re building the next Google, yes, you need software. But I’d say in 80% of the cases where someone says, “I’m going to build my MVP,” and they assume that means software. They’re actually incorrect. You can do a lot of things. You could sell a lot of people on idea, or on mockups, or on the excel, email version of something without ever having to write a line of code. That’s the thinking I’d be doing at this point.
Mike: Yeah, I was going to mention that as an add-on for his second question was that, the first iteration of product doesn’t necessarily need to be software. How far are you down the road of the validation process? I think that once your past validating it and you decided to pull the trigger on it, do it the right way. Hire the developers that you need as opposed to the developers that you can just afford. You need to get good developers in there doing it.
Rob: I’ll even say, I’ve hacked things together myself. I think of the, what is now Founder Café, which is our online community for bootstrap software founders, go to foundercafe.com to learn more about that. But the original version of that, it had a different name altogether, called Micropreneur Academy, I was a software developer. I could’ve built online learning platform. There weren’t very many that were any good at that point. Moodle was in its early days, 2008, 2009. I hacked it together. I hacked it together with WordPress, and plugins, and theme, and that was really it, and I hacked some PHP. It wasn’t great. In the end, we had some technical dab but it was years later, it had already been built up and do a pretty nice business at that point. I’m not saying build a SaaS app that way, but there are workarounds you can look at to make that happen. Thanks for the question, Anonymous. I hope that’s helpful.
Our next question comes from firstname.lastname@example.org. He recorded an audio question so he jumped to the front of the line. It’s a long question but he gives a lot of background, and I appreciate it because oftentimes, people will send short questions, and then we have a lot of questions in our mind about, “Well, they didn’t give this detail or that.” It’s a couple of minutes here, but hang out, and then Mike and I will weigh in.
“Hey guys. My name is Dan Webb from Closer Sharing. Before I get to my question, I just want to say thank you to both of you. Thank you for all you do. I’ve learned a bunch from you guys. I’ve been listening for a few years now. When I first started listening, I tore back through the archives and learned a bunch and have been listening ever since. Thank you, guys, for sticking with it and teaching a lot of people a lot of stuff. Thanks.
Before I get to my question, let me give you a little bit of background. I have a startup. It’s called Closer Sharing. It’s a sermon podcasting platform. It’s a podcasting platform specifically designed for churches, allows the volunteers to quickly and easily use our recorder to record, and tag, and post the sermon each week, and list it on their website, and just takes the pain out of it, of hosting, and getting on their website and all that. We officially launched the product in January of 2017—a little bit over a year and a half ago. I have tried to grow it.
Right now, I currently have seven customers. We have an MRR of $200 a month. We really bootstrapped the thing building it. We only have an outflow of $175 a month who we are in the black. Out of those seven customers, all are original, I have had no churn whatsoever, so everybody that’s using it really likes it. Some have been on it the full year and a half. The latest sign-up was a couple of months ago.
There is no churn. I think it is a good product for the people who get on it. The trick is getting people on it. I have tried cold emailing. I’ve tried Facebook Ads, I have tried conferences. I tend to walk away from each one with one customer. I went to three of them. It really became obvious to me, one of the mistakes I was making a couple of podcast ago when you were talking about SaaS marketing, and I have not been trying to really connect with people and teach them anything. I’ve been just—as I’ve heard some people say—ask him to marry me on the first date sort of thing. I have a series of blog posts in my head that I feel like I should write and get out on my blog, and start sending people to them, and getting people to know me, but I haven’t done that yet. Probably my next project.
We’re well in the year and a half in, I was listening to your last podcast about funding, and some of that made me think as I’ve been thinking maybe I should just say, “Hey, it’s been a year and a half. I’ve only got seven customers. Maybe I should kill it and shift to something else. But then again, I have seven customers and I like them and I like to continue to provide the service for them. But I don’t want to be that guy that’s just clinging to my startup just because I’ve built it. I would like to know if it’s a viable product. I do have a whole list of futures that could make this platform really great, but I don’t want to keep building on it if it’s not a viable product.
My question is, should I keep spending my nights and weekends on this thing—I have a full-time job—and continue to grow really slowly? Should I possibly look for some sort of funding, so I could spend more time on it and possibly grow it quicker? Should I just kill and walk away and work on another product and try to develop it into a business? I’d loved to hear you guys’ thoughts on these things. I appreciate all you do. Thanks, guys.”
Rob: Tough question, huh, Mike? What do you think?
Mike: I think that’s a really tough question. I do hear a couple of things in there in terms of working on the weekends and wanting to build features. I think that that’s very natural for any developer to want to do because that’s comfortable, but at the same time, I think I would go back and I would start looking at metrics in terms of how many people you’re getting in front of, and how many trials sign-ups you’re getting, how many actual sign-ups you’re getting, I don’t know if there’s a free trial or anything like that, but those are the types of things that I would probably look at first, and see if there are obvious places where—like your sales funnel is just simply not working.
If you’re not getting 1000 or 2000 uniques a month, then that’s probably the place to start and try and figure out, “How do I get more traffic?” Because there’s this whole funnel that has to be in place in order for you to be able to build a business. That’s longer-term stuff. I want to make sure that I emphasize that there’s a difference between that type of stuff and then shorter-term stuff that you can do which you’d mentioned that you’ve done some Facebook ads and some cold emails and things like that. But I don’t know if you really have much on the website in terms of what you’re offering to people. I think the blog post sounds like a good idea in terms of education but I’m not seeing email newsletter sign-up list or anything like that on the website.
It’s more of a, “Come buy this product.” And there’s really not much in terms of education about how the churches that would invest in this type of products will deliver better sermons or would engage more with their church members. I think that’s what you need to key in on this because that’s what’s going to be important to them. The professional sound, they’re not going to care nearly as much about that as you are. You have to ask yourself, “What is it that’s actually important to them? How can they connect better with their members? How could thy reach more of them? How can they be more convenient to them in a digital age where people don’t necessarily need to show up at a certain time to see a movie, they can just stream it On Demand.”
That’s what you’re trying to cater to. That’s one of the problems that they’re probably having. Offer advice and solutions and different techniques and things like that in the form of educational material, and then try and build up that early part of the sales funnel. I would absolutely try and contact them directly as opposed to just sending emails because those are very easy to ignore. Pick up the phone, I mean, it’s probably not that difficult to reach them. I would imagine that most of their phone numbers are available.
If you’ve got people that you’re cold emailing, you’d probably have a way to find out who they are, and get a phone number for them, and call them and ask them. Talk to them and say, “What are your problems around this and around building a community?” because it really seems to me that’s what your product is trying to do. How do you engage with them and getting the information directly out of their mouths is going to be very helpful? I wouldn’t just call 5 or 10. I would call 50 or 100.
Put a line in the sand at some point in the future like you’d ask about whether or not you’d kill it. “What is your line in the sand? How much more effort do you put into this?” and really put the pedal down to see what is going to work. “How much effort can you justify putting into it?” and then once you’ve hit that, “Have you hit whatever your goals are or do you see a light at the end of the tunnel?” in either of those cases, you can keep going. But if you get there and there’s nothing else you can try, or you can’t think of anything else, I would kill it at that point.
Rob: I feel like this is such a tough market because some churches don’t tend to adopt. Some churches adopt technology but a lot of them do not. The older churches with aging congregations are just unlikely to need podcasting. You’re dealing with such a small subset of the entire market. If you think about, in the world, the number of people who, period who listen to podcasts is very small. My mom and dad don’t know how to do that. If you just break that down into a subset, and do a subset of like, “Now it’s churches, and now it’s churches who have people maybe under age 40, or age 50 who also know how to use podcasts.” Those are the only ones that have any type of need for this service. It’s a very small market and it’s a market where obviously, in conversations, I’m sure that he’s learned that they are just not that interested in adopting it. That’s the first problem.
The second issue, Dan, is you have a top of funnel problem, it sounds like. If you had 1000 or 10,000 unique visitors to your website each month, you think you would convert them? I don’t know. But generating visitors is going to be really hard to do. If you’ve been doing for two years and only have seven customers, that’s a bad sign. That’s a sign that something’s not resonating here. I think a big question I would ask myself is, “Are you tired of working on this? Are you done yet? Are you still excited to invest time?” not even, “Do you still believe it can work but are you excited to get up and think about this problem and try do to it?” I would stop building features altogether. You shouldn’t be coding anything which doesn’t sound like you are.
Your biggest problem is, it sounds like might be driving traffic, or maybe driving traffic hasn’t worked at all and it’s only been in-person conversations, in which case ask yourself, “Is a $29 a month product worth doing high-tech sales for?” because for me, it’s not. It’s going to grow very slowly. You need $100-$200 a month minimum, to make that kind of approach work. I really don’t think funding will fix this.
This is not a problem of, “I need money to scale or I need to put in more time to get to a point where this product is worthwhile.” It seems that you have a worthwhile product already. You’ve a lot of cool features. More time to market? What would you do? It sounds like you have tried a bunch of stuff. I mean, you haven’t tried everything, maybe you didn’t try enough of it, didn’t have the budget, but I’m cautiously skeptical that if you have $100,000 in your bank account tomorrow, and you could go full-time on this for, let’s just say, nine months and had some budget for stuff, I don’t see this taking off like a rocket ship based on how you’ve described.
I think my biggest piece of advice, given what you’ve said and looking at the website, it seems like a pretty cool tool in all honesty. You have features like automatic intros and outros, professional sound without the work, automatic feeds, is there another vertical that could use this? Should it be horizontal? Should it go across all verticals, basically? Should you not limit it to churches, is what I’m saying.
Right now, you’re marketing to churches, is that too limiting, and is there either another vertical that would have so much more uptake on this or just open it to everyone, and then poof, you become the ‘how to start a podcast superfast’ service. Maybe you make it a little cheaper but sign-up for six months or a year at a time and you pay upfront. I don’t know if that’s the direction but that’s where I’d be looking. Are there already services that do that? Because at that point, if you could get into that space, now you have affiliate potential because you have people who teach other people how to podcast. Would they potentially refer you for an affiliate commission? That’s a bigger space is people trying to start their own podcast. Could you go after businesses or startups or whatever?
Again, this is something I would either try to research, do some customer development, put some digging into that because I feel like that’s a space where there are more likely going to be folks who will actually adopt this, and consider jumping on this train because it seems that you’ve built a decent piece of software–at least from the marketing side. It looks pretty interesting and has some features I haven’t seen elsewhere, but I don’t the competitive landscape. That’s probably where I would look at or shut it down. That’s the other option that I see.
I always hate to make a recommendation like that because I feel like the founder knows better than anyone else. They often need to see […] that’s where having a mastermind would help, right, of people who’ve been along in the journey. But to hear a formative voice and then make a recommendation that, you should check your product down, it’s tough. It’s tough for me to say that but, I think that’s a more viable option than trying to scale this up in the church space or raising the funding.
Last question of the day came from Twitter. It came from @chelso and he said, “Regarding episode 406. What is your definition of product market fit?” and then I started tying and then thought, there’s always so much nuance to a question like this, and Twitter is not the place to do this. This is either a blog post or it’s a conversation like this. I think product market fit is not a binary thing. I definitely think it’s a continuum and I think you kind of ease into it.
There is a nice measure that Sean Ellis created. It’s this survey you can send out that says, “How would you feel if you could no longer use this product?” insert product name here. The four options are; very disappointed, somewhat disappointed, not disappointed–it isn’t really that useful, or NA–I don’t really use the product, or I no longer use the product. If you get more than 40% who say they would be very disappointed, that is how Sean Ellis has defined product market fit. I think that would be the most common definition. I have run this exact survey on some of my products.
I know Hiten Shah has run this exact survey on, not only his products, but on a bunch of other products. He’ll run it on Google Analytics. He’ll just ask a bunch of people, and I don’t know if he uses a mechanical trick or how he does that, but Google Analytics definitely has product market fit, at least according to his slide deck and some talking he’s done. We will link to SlideShare, this Hiten Shah presentation in the show notes so that you can take a look at the work that he did.
I’ll leave it there, Mike, so you can weigh in. I have additional thoughts and kind of my own personal thoughts of when I saw Drip–what it looked and felt like before product market fit as we were getting there, and then once we had it, from my perspective. I do want to weigh in, but I don’t want to sit here and monologue and not let you weigh in.
Mike: True. This is probably not going be much different from other people on what they would comment but you’ll know it when you see it. I know that’s kind of a hand-wavy type of thing but there are some people who will look at metrics–so Sean Ellis has that product market fit survey. If you’re more than, I think he said that 40% are, I forgot what the exact percentage was, but certain percentage say that they are either somewhat disappointed or very disappointed that they would go away.
Rob: 40% said they would be very disappointed if it went away. 40% or more then, by his definition, you have product market fit.
Mike: Right. Like you said, that’s a very, I’ll say, exact in definition. I won’t necessarily say that that’s the only definition. It’s kind of my view of it. I like the way Rob phrases like, “There’s a continuum of it.” That’s why I say you’ll know it when you see it because if you’re involved in the startup from beginning to end or wherever you’re trying to figure out like, have you gotten to product market fit, you’ll know it when you see it because things will start to tick up and it will be obvious that you’re on the right track. Because it’s a continuum, you’re never going to be like, “We have perfect product market fit.”
You think things can always improve, they can always get better, and the market’s always changing, your product’s always changing, your marketing messages are going to be always changing–these things that interact with one another that you’ll never have this perfect product market fit. Even if you did, it’s very likely something that something is going to change and throw it all out of whack in 18 seconds.
Really, what you have to do is, if you don’t have the data, if you haven’t run a survey like this, you kind of have to go off of a gut feeling. My general view on it is that if you take the product and you put it in front of people who are in what you believe to be the correct target market, and they actually are, do you win much more than you lose? Are those people going to sign-up and say, “Yes, I would like this,” Or, “No, we’re not just interested.” Because that will tell you one of two things, either one, you’re pointing at the wrong market or your product is not good enough and it’s just not doing what people need it to do.
The second piece, which I didn’t mention yet, is that those people will have to actually stick around. You can explain to them, “Hey, this product will do X, Y, and Z for you. It’ll make all these problems go away.” But if you don’t also deliver on it, they’re going to churn out. You have to figure out ways to make them stick around. Those are two different competing things and sometimes, your things should make them stick around or going to be more features–sometimes it’s educational, or onboarding, or something like that. That’s a slightly different problem than product market fit. Somebody may believe that they need a particular solution, and they’ll pay for it, but then they don’t use it.
Think of any weight loss program on the planet. People buy into that stuff and then they don’t use it. Why don’t they use it? Is it a product market fit problem or is it a customer retention problem? That’s a hard thing to figure out because if they churn out, if they stop paying for it, if they stop using it, then is it because other things got in the way or the product doesn’t actually do what they needed it to do? There’s an attribution problem of, “Why did they churn out?” If it’s because it wasn’t actually a good product market fit and they bought into the messaging, but it didn’t solve their problem, then you don’t have product market fit. If they churned out because they just don’t have the chops or time or anything like that to actually do it, then that’s a slightly different problem–that’s a retention problem not necessarily a product market fit problem.
Rob: This is why it’s a good conversation to have. I won’t talk about weight loss stuff because I don’t even know if product market fit applies to that in particular. I mean, it does, but I don’t think about it in terms on that one. I think of a SaaS app, a retention is a product market fit problem, in my opinion. That if someone’s not getting on-boarded, not using it, then the need isn’t deep enough, and you haven’t found that fit with the market. The question that I ask, the way I frame it in my head is, “Have you built something people or businesses need?” That’s the question that I’ve asked.
I think Paul Graham says, “Have you built something people want?” I think it’s a great way to phrase it but have you built something that people or businesses need? Let’s stick to businesses because we talk a lot about B2B SaaS here. If you built something people desperately need, and they start using it, can you still fail, or can you still grow slowly? Yes, I believe you can even with product market fit because if the market’s too small, and you tap out, that’s one way.
If your market’s only $10,000 a month then you can own the whole market and really just tap out very quickly. Or if your market is huge but you can’t reach them in a scalable fashion, that’s a totally different problem than product market fit. I think there’s different problem than product market fit. I think there’s being able to build something that people need, and businesses need, and then there’s the ability to reach them in a scalable way and get them onboarded in a way that doesn’t kind of break the bank.
The three questions I think about, in order. The first one you have to ask—this is before you’ve built anything— “Is a problem you’re choosing to solve worth solving? i.e., is it much of a pain point for people?” then you’re going to start building it or you’re going to start validating it. Customer development even before you build it. You need find out, “Are people willing to pay for a solution to this problem?” Then you propose a solution and that’s where you hit that very first milestone is problem solution fit. You’ve proposed a solution to a problem. Does anyone care? Is it worth building at all? Are people willing to pay for that? And then product market fit is almost this, it’s kind of a twisted question or it’s a weird way to think about it, but it’s like, “Have you solved that problem well? Have you solved better than the alternatives? Is the problem worth solving? Are people willing to pay for it?”
You can build a good product but if you can’t reach the people and get them to sign-up, you’re going to really have a problem. I almost feel like problem solution fit is one, product market fit is the next, and then there’s this one, market marketing fit. I just made that up today because I was thinking, “Can you reach your market?” is almost the question there.
I remember when Drip started to scale up, at first it was like, people were churning, churn was high, trial to conversion rates were low and then they just flipped. Trial to conversion went up, churn started plummeting, and we started growing very quickly even with fewer trials that we’ve had in previous months. That’s when I knew, we are a product market fit, or at least I thought, and sure enough I did that survey, the very disappointed thing. I remember thinking it was going be really high because everyone was like, “Well, Drip is so great. Everyone’s switching.” and blah blah blah. We got like 43%, 46%, somewhere in there. I remember being disappointed by that because I thought, “Oh, man. I thought more people would be very disappointed.” but as it turns out, it’s really hard to get above 40%. That’s why Sean Ellis sets the bar where it is.
Mike: I think one of the things that you explained probably better than I did because I didn’t actually put a label on it was that, when I said, if you put the product in front of people who are in your target market, basically, that’s bypassing the problem of the product market fit piece of it and trying to ascertain whether or not you have a problem solution fit. Because by doing that, you’re making an assumption that you already have product market fit and you’re able to get the right people there.
If you don’t have that, if you get what you think are the right people, and you put it front of them and they don’t buy, then you probably do not have that product market fit. It’s just kind of a little subtle thing that I, I guess I talked about there, but I didn’t really explain like that. Applied to the previous piece and you’re just trying to avoid the whole marketing side of things. You just say, “Are we actually solving the right problem for the people that you think need that?”
Anyway, I think that will about wrap us up. Chelso, I hope that was extremely helpful for you. If you have question for us, you can call it into our voicemail number at 1-888-801-9690 or you can email it to us at email@example.com. Our theme music is an excerpt from We’re Outta Control by MoOt used under Creative Commons. Subscribe to us in iTunes by searching for startups and visit startupsfortherestofus.com for a full transcript of each episode. Thanks for listening. We’ll see you next time.
In this episode of Startups For The Rest Of Us, Rob and Mike answer a number of listener questions. The topics include videos vs text, finding mastermind groups, and trials versus demos.
Items mentioned in this episode:
Rob: In this episode of Startups For The Rest Of Us, Mike and I talk about the benefits of using text versus video, how to find a mastermind group, how to start running joint ventures, and more listener questions. This is Startups For The Rest Of Us Episode 374.
Welcome to Startups For The Rest Of Us, the podcast that helps developers, designers, and entrepreneurs be awesome at building, launching and growing software products, whether you’ve built your first product or you’re just thinking about it. I’m Rob.
Mike: I’m Mike.
Rob: We’re here to share experiences to help you avoid the same mistakes we’ve made. What’s the word this week, sir?
Mike: Not much. Just the end of the year has come and gone. It’s the first week of the new year, I’ve been spending a lot of time lately working on a website redesign for Bluetick, which is about halfway done. Nothing’s live yet but I’ve been working through website design itself, email copy for the automation emails that are being sent out, and then also the website copy. Coming along pretty well. The next week or so is gonna be involved with finalizing and all that stuff, and then implementing it on the website. Once that’s all done, I’ll start doing a much bigger marketing push, I think.
Rob: That’s cool. You’re gearing up for this because you’re live and you’re trying to drive more traffic and want more of it to convert, is that why you’re focusing on this site right now?
Mike: Yes. The main focus on the site right now is because if you come to the site and you’ve never seen the product before, what I’ve heard from people is that it does not give them a good feeling of trust like, “Oh, this is a legit company,” which I totally get. If you go to the site, there’s not a whole lot there, and there’s not detail. It doesn’t even really, I guess, give you the inclination that you should reach out and contact the company or sign up for a trial account or something like that just because you go to a competitor’s website and there’s tons of information there, there’s articles, testimonials, and things like that. It just looks a lot more professional versus the Bluetick website, which to-date, I’ve relied more on word-of-mouth, and people coming in through after hearing me on a podcast or something like that. It’s just not conducive to more of a hands-off sales funnel, I’ll say.
Rob: Right, that makes sense. Yeah. It does feel, when I come to this site, bluetick.io for listeners out there who haven’t been there, it feels like a WordPress theme or like a bootstrap, kind of a basic template. As you said, I think you have good content here but it’s like you said, you don’t have the articles, and the blog, and all this other stuff that other companies that have been around longer might have, so it does seem like just a smaller operation.
Mike: Yeah. Also, it’s not real specific about exactly what it does or how it works for them. It doesn’t answer really any objections. It doesn’t really tell a story or craft one that would have resonate with whoever’s reading it. There’s a lot of things that need to go on to the site right now that are just not there. I’ve known for a long time that that stuff needs to go there, I just haven’t sat down and focused on that stuff because I really haven’t had time yet.
Rob: Well, yeah. It’s a matter of priority. It’s like you’re trying to get the code read, and then you’re trying to get the bugs fixed in, and you’re trying to scale, and then you try to get people onboarded, you gotta email the list, you gotta write this email. At a certain point, this is where I still struggle quite a bit with unsolicited advice. People used to email and be like, “Hey, the Drip website. It would be so much better if you did this.” It’s like, “I know. I know, of all people, I think about this all the time, like 20-hours a day. Yes, even when I’m sleeping.” Your unsolicited advice is actually not helpful. It makes you feel like you’re smart but people would send screenshots and say, “You should change this. Have you thought about organizing?” I said, “Yes. We have. We thought about that and either we didn’t do it very deliberately, we had a good reason for not doing it that you don’t understand because you don’t work in the business 50-hours a week. Or we have thought of it, we just haven’t had time. We haven’t prioritized it yet, and there are more important things.” That’s where I could understand where the marketing side has maybe fallen to the second or third place on your list.
Mike: It wasn’t even second or third. It was like eighth, or tenth, or something like that. My list of things to do is 10 miles long. It’s not even a mile long, it’s 10-miles long at this point. It’s just going back through and trying to figure out, “Okay. What should I really be working on next?” At this point, it’s the website. Once that stuff’s in place and once more of the marketing emails are in place and do a better job of explaining what the product does, and kind of move people through that educational side of things then I think they’d be in a much better position. How about you?
Rob: Last week, as I mentioned, I was in Florida, which was great. It was nice to get away. There was a big, obviously the polar vortex came through in Minneapolis. There were days where the highs were in the negatives, like -3, -4, and it feels like it was -25 or -30 at one point. It’s a pretty nice time to be in Florida, but I made it back, and kind of getting started again at the new year here. Not much to report on the work front just because ships and features in late December, and we’re gearing up for some new stuff now.
One thing that I just want to throw out unrelated to Startups, except for that it is a startup, is the thing that I’ve discovered in the past like 10 days that has just been life changing, it’s Instacart, do you have it where you live?
Mike: I don’t know. I’ve never used it. I’ve heard of it probably at one point.
Rob: I hadn’t either. Yeah. I don’t particularly like grocery shopping. It always takes time and especially I have to try to do with two or three kids tagging along. The fact that we live in a major city now, in Minneapolis, but really enjoyed like having Bite Squad around where I can order food and it’s delivered. But Instacart, it’s a grocery shopping app, and it’s just well-implemented, super easy to use, 1-2 hour delivery windows depending on the time of day and how busy it is. I can do my entire, what would normally be let’s say, a 75-90 minute drive, and in the snow, it’s like super cold, you don’t want to get out of your car because it’s four degrees and you’re lugging a kid with you, and I can do it from my computer in 10 minutes. It’s just freaking game changing. I’m pretty stoked on it now. I’ve only had maybe two or three deliveries so far. I’m having a tough time seeing going back to doing it the old way. It’s not expensive either. We usually did this subscription where it’s $150 for the entire year, and then, you just get unlimited. You don’t pay any delivery fees.
Mike: Got it. Okay.
Rob: Yeah, it’s a trip. If it comes to a place near you, and I don’t just look at it as a convenience, it’s a time thing. To save that time once, maybe twice a week. We eat a lot of fresh foods. I can’t just shop two weeks out. When I was in college, and I bought all macaroni and cheese, and ramen, we could shop for like three months at a time, and it wouldn’t go bad. The fresh stuff, I literally line up at the grocery store at least once a week, and sometimes twice. I just sent an order through for all fresh fruit, and berries, and bananas, and all that stuff. It’ll be here in the next 120 minutes.
Mike: Oh, really. It’s like you order and then it’s there in like two hours.
Rob: Yeah. You can select a time window, you could select the one-hour time window later in the evening or tomorrow, or whatever, or sometimes, depending on how busy it is, and of course middle of the day on what is it, Thursday, it’ll literally be here within two hours when I click Buy Now.
Mike: That’s interesting. We’ve talked about this a little bit, I think. But I used to work at Wegmans Food Markets. We implemented a system like this back in 2000.
Rob: Yup, you had talked about it.
Mike: Yeah. The difference though was that you would drive to the store and pick it up. You put everything in your cart, you shop, and then you specify like, “Oh, I’m gonna come pick it up at such and such time.” You have these like 10 or 15-minute time slots. You can just pick one and you just show up and they’d have everything ready for you. You just show up at the designated time. They’d ask your name, and that was the end of it. They’d load up your car, you don’t even have to get out of your car.
Mike: It’s a little different though. This is also different than, what was it, Webvan.
Rob: Webvan and Peapod. Where it just tanked horrendously.
Mike: Peapod is newer. It was Webvan that ran out of business back in the day.
Rob: But Peapod did then too. I think someone bought the brand. They revitalized it because both of them raised a lot of money around ‘99-2000. But they were trying to warehouse everyday. They were trying to be like Amazon, or like a big grocery store distributor, whereas Instacart is more like Uber where they don’t own anything, yet drivers go shopping, and put the stuff in a cart, and bring it by. They just knock on the door, hand me a few bags, and it’s like, “thank you.”
Mike: It’s much more like a localized services business. More like running errands for you, although the errand is very specific.
Mike: Productized service.
Rob: I know. That’s what it is. So far, one of the concerns obviously would be like, “Well, are they gonna pick good produce? Are they gonna pick good if you order salmon? Are they gonna pick the crappy salmon?” So far, I haven’t had any issues. You can tell that they have some type of onboarding, they teach people to get the good stuff. I’m sure if you rate them poorly, like, “Yeah, the fruit was bad,” then there’ll be some issues there. I think that’s another difference is back in the day, I don’t know how much recourse you would have had with someone sending you bad fruit.
Mike: Yeah. That would have been a little difficult. The way Wegmans said it was like, they would actually have the butcher over at the butcher shop like pick up the meats and stuff for you. You knew that the people who were doing it were pretty experienced with what they did.
Rob: Right. Cool. Let’s transition into the episode here. We have several listener questions we’re gonna talk about today, and of course, per usual, our voicemails go to the top of the stack, so let’s kick off our first question. It’s about being pre-product market fit.
Harold: Hi. My name is Harold and I’m a co-founder of StackTome, a SaaS product for ecommerce retention advertisement. There are three product-market fit I’m looking for ways to get warm lead customers. I have couple of questions. When it comes to driving traffic to the site, I was wondering if you have seen educational videos instead of text content among sites like YouTube being successful. I find it more [00:10:03] traffic coming from search, mostly through content, while some content I find useful, I can’t find alternative quick videos explaining the marketing concepts. Also, what would you recommend for getting into mastermind groups [00:10:20] marketers that would be post product-market fit [00:10:24] Thanks for your always honest feedback and sharing your knowledge, I’m always learning something new each time I listen. Cheers.
Mike: I guess, to recap, and Rob, correct me if I’m wrong in my understanding to this, but the two questions that he had were essentially how should you approach developing content for the website to drive traffic? Should you focus on video, or should you focus on text, in order to gain more attention when you’re in pre-product market fit? The second one is, how do you find people to join a mastermind group with, is that right?
Rob: Yup, that’s right. To be clear about the video versus text, he wasn’t asking about conversion, he was asking about trying to drive traffic, will it rank, I think it’s will it rank better in search engines, basically.
Mike: Yeah. My understanding is that Google is still ranking video higher than text. But one thing you have to be a little bit careful of is to make sure that you’re providing some sort of transcript for it. That helps Google index the videos because otherwise, it has no way to know what is the actual content of the video, what are they saying. There are ways to provide that information to Google’s crawlers so that it will show up. The searches, that’s one thing I would definitely do.
The other thing that does come to mind though is that if you’re pre-product market fit, I would actually do outbound stuff. I would try to find and identify people who you think would be good customers and go after them, as opposed to trying to attract them and get them to come to you. Because really, that’s the situation that you want to, I guess, double down on once you know who your ideal customer is. But if you’re not at that point yet, you have to choose from outreach, otherwise you’re kind of throwing spaghetti at the wall and seeing what sticks.
Rob: Yeah. That’d be my sentiment as well. I think you can mess around with the video versus the text thing. I have heard success stories of video working better because it’s not something that everyone does. But you have to get into video, there’s like video site maps, as you said, you want transcripts. May just be better, I don’t even know if you wanna host it on your site at that point, you may just want to have it on YouTube, because YouTube videos rank really well in Google, obviously because Google prefers them over other things.
There’s a whole specialty of learning video SEO and how to rank using video. I would agree with you Mike, I just don’t think that’s necessarily worth diving down that rabbit hole, yet. Because I bet you could kill a month just learning about it and probably two to three months experimenting with it. I think there are more valuable things that you could be doing right now, even outbound stuff like you were saying. I could see running paid acquisition if you have any budget at all because you want instant feedback. You want instant customers or not. Customers or rejections, as they say.
Whereas this video SEO stuff, you’re building for the 3, 6, 9, 12-month timeframe. You wanna get to revenue faster than that. You wanna get to product-market fit faster than that. I would be scratching and clawing at anyone using a app. I just think of SEO and these types of strategies there is it’s just a longer term play. The bad thing to do, but if you limit it on time and budget, which I’m guessing you are, I wouldn’t be focusing on this.
Mike: Yeah. At most, what you just said is about the iteration cycle and being able to adjust quickly versus taking that long term approach which is valid later on. But, right now, it sounds like that’s not the way to go.
Rob: Yup. Then for his second question, it was how to find a mastermind group, and our very own Ken Wallace with mastermindjam.com is kind of our go to recommendation for folks looking to get matched up with fellow masterminders, both in the SaaS space, there are ecommerce entrepreneurs, there’s info marketers, there’s all kinds of stuff. Go to the site, you submit your name and your time zone, and a bit about yourself. I’m sure you categorize yourself in some way like SaaS or info, whatever. Then you get matched up. Ken has written an algorithm, and he also does a lot of manual stuff with it as well. There’s a small fee to getting matched up, but in my opinion, well worth the effort. There’s been a lot of successful groups that have formed out of using Ken’s service.
Mike: What’s next?
Rob: Next question is our second and final voicemail of the episode and then we’ll get to some emails that came in. This one is a question about the moral imperative of business.
Daniel: Hi Mike and Rob. This is Daniel calling in from Charleston, Oregon. Love your podcast, thanks for all the time that you put into it. Keep it up. Definitely in the want-epreneur category, tried a couple of products to myself, haven’t really seen success for me. The challenge is the golden handcuffs consulting business is too good to really make the dive deep in the product. But the question I have for you guys today is around the moral obligation of business and just to be hearing your perspective on income equality, social equality, and kind of the bootstrap startup vision is build a business and sent it to a hyper-competitive space that eventually throws off a bunch of cash. What do you feel is your moral obligation to reinvest that cash back in the community, people around you, your local geographic vicinity, and help address the growing problem of income equality. Thanks so much, bye.
Mike: I think for this question, when you’re talking about bootstrap startup, there’s actually two answers to this question, not just one. There’s an answer that is applicable before you get to the point where your business is making a fair amount of money and throwing off access capital.
There’s the second answer which is after that point. The first one is, I would say, before you get to the point where the business is throwing off that extra money that you can deploy as you see fit to do whatever, above and beyond to paying all the business expenses and paying yourself a reasonable salary and potentially giving you extra money to be able to put away the additional profit from the business at that point.
You don’t have any of that. Before you get to the point where that has happened, you’re not in a position to really do anything. I don’t feel it’s fair to put yourself in a mental state of mind where you feel obligated to do things for other people. Your real focus should be getting the business to that point and until you do, there’s really not a lot else you can do.
I think that if you tried to put other people before you, you’re just gonna run into a problem where everyone is always going to be coming before you. You’re never gonna pay yourself. There’s entire books that are written about this. I think there’s one called Pay Yourself First or something along those lines. That’s the phrase that goes with it. But until you’re there, it is not really justifiable in my opinion to attempt to do those things.
There’s a difference between spending a little bit of time helping people here and there but to make that your main focus is definitely not a route you should go down. Once you’re after that point, then the situation I think changes pretty dramatically. I wouldn’t say that there’s a moral imperative but depending on your own personal judgements and your own personal beliefs, I do feel like it is worthwhile going down that route. There’s actually a lot of benefits for you to, I don’t wanna say share the wealth or anything, but help other people because at one point, you were there where they’re at.
We could probably talk, at great length, about this but that’s the type of people you run into at MicroConf as well. I think that Rob, you probably agree with me on most of that stuff in terms of being able to help other people and the additional benefits that you get from it. It’s not really just about the money at a certain point, as long as your business is providing for you, then you can kind of do whatever you want with the money afterwards especially if you are already putting money aside to save. It feels great to be able to help other people who are further behind you because you were there at one point as well.
Rob: Yeah. I think part of this is a somewhat personal choice and I think part of it is how you view being part of a society in general or a community, maybe a better way to say it. I like the way you framed it, Mike. You can help people without going and volunteering at the local soup kitchen or without volunteering to train people how to learn computers in your local area.
You can help people by educating them on how to start startups. You can start a podcast and give content away for free that helps build this community of bootstrap founders. It helps raise kind of all of our standards of living, all of our quality of life, and it helps create jobs, and all that stuff. This doesn’t really have to come in the form that I think a lot of people think about.
My personal belief, I have always been as generous as I possibly can with my money and with my time. Since I was in college, I’ve given money to charities even when I didn’t have much money. As I started making more money, I still give quite a bit of money away each year. I have always spent a lot of my time helping whether it’s having lunch with an entrepreneur, whether it’s you and I doing the podcast for free for years, whether it’s blogging and giving away knowledge.
Yes, there are outlets, obviously, I wrote a book and I sold that for $20 a copy. You and I do host a conference but the amount of time that we have essentially given to this community far, far, far outweighs the monetary, the per hour cost or whatever that we would make, the wage we would make given all the time we’ve given away, it would not be a wise business decision to do that.
We have done some of it because it’s fun for us and some of it because, I think, you’d agree with me, I truly do enjoy giving back and helping people in the emails that we both get where it’s like, “Boy. There’s something you did,” whether it’s FounderCafe or MicroConf or the podcast, “it has changed my life and here’s how.” I receive dozens of those emails and those have a lot of impact on me. It’s a lot of mental impact. All that to say, I don’t know that I would preach that everyone has to adopt this point of view, but my point of view is that I always wanna be able to give back.
I have invested in a company in Fresno called Bitwise Industries, that is a for-profit but it’s educated thousands of folks in the local Fresno community which has a real wealth disparity. There’s a big digital divide there. They’ve educated thousands of people on how to program and how to use computers. I hired Derek out of Fresno although there wasn’t a digital divide with him. But then we hired three more people, created a bunch of tech jobs. Bitwise itself, I don’t even know how many people it is now. 50, 60 people.
There’s good to be had in a way that everyone wins. I think that’s how I think about it. I so much enjoy more funding a company like Bitwise or doing what we do with MicroConf and FounderCafe and this podcast because I feel like it’s win-win. We’re not just taking money that we earn as entrepreneurs and giving it to somebody. We’re actually starting a sustainable business. That’s what we’ve always wanted to make sure that MicroConf was sustainable, it’s why we brought Xander on so that we could do it year after year. It’s why we’ve really streamlined the podcast production because we wanna be able to continue doing it even when we have other things going on.
I think turning it in, again, I think like an entrepreneur. It’s like a person who turns systems into profit in essence. I want some of that profit to give back to whatever community is, whether it’s the bootstrap startup community, whether it’s the community I live in, but it needs to be a win for me as well in a small way. It doesn’t mean,”Oh, we need to get rich off it.” But I do think that making it into something sustainable, that’s how I’ve always thought about it.
I really like what you said about the kind of the pre-sustainable business. Because when I was scratching and clawing, I was freaked out about money, I was just trying to get whatever it was, Hittail revamped or the real tough financial year I had with Drip. I couldn’t even think about any type of moral imperative of helping other people because I was trying to take care of me and my family.
But once I get past that point, then yes, my mind is freed up. I absolutely give very generously to a lot of things, whether it’s charities or the sustainable businesses that hopefully are kind of doing some good in the world. Thanks for the question, Daniel. I hope that was helpful to hear our thoughts on it.
Our next question is from Stefan Debois from surveyanyplace.com. He says, “Hey Mike and Rob, I listen to your podcast for several years now, not since the beginning, but close to it. I really love it because it has so much actionable stuff. On one of the latest episodes, you guys talked about content marketing at the end of the episode, and I remember Rob saying he would not advice for startups to make it their number one tactic, for example, creating a blog and publishing content. But he would recommend doing something else like joint venturing with players in your field that already have an audience. I assume he’s referring to guest blogging, joint webinars, etcetera.” I’m gonna step out real quick. Two of those, guest blogging and joint webinars, correct. As well as integration marketing which I’ve talked about in the past which is where you integrate and then you both co-promote. Alright, back to his email. “It would be great to dig a bit deeper into this topic such as how exactly would you recommend doing this. If you had to start Drip or another SaaS company right now, how would you apply this given all your learnings? Thanks for your help. Keep up the great work. Stefan.”
Mike: I think one key point to keep in mind is that, as part of his question, he said, “If you had to start Drip or another Saas company right now, how would you apply this given all your learnings?” There is a point at which doing this kind of stuff is too early. You’re not far enough along where it makes sense to go down that road mainly because it’s not gonna make sense for whoever it is that you approach to do a joint webinar or guest blogs.
With guest blogging, you can certainly write articles and as long as they are relevant to the audience of the person that you are guest blogging on their site, and they are receptive to that kind of thing, then sure. You can totally do that. But when it comes to something like a joint webinar, you really can’t do that unless you have something that is tangible and benefit that is going to be given to that person’s audience, whoever it happens to be.
The other thing is what are you offering the owner of that audience? What are they getting out of it? Is it really just educating their people? Are you promoting your products or is it just an educational thing where you’re explaining how to do something or about a particular topic or a technique or something along those lines.
But again, none of this stuff you can do until after you’re at a point where you have a product that is functional and you have people who are onboarded and paying and you kind of know what your ideal audience looks like. Because otherwise, you’re approaching people that their audience may not necessarily overlap with yours.
Those are the things that I will keep in mind when trying to go down this road. Until you’re at that point, none of that stuff applies, you’re just not going to go anywhere.
Rob: Right. The thing to keep in mind is this is where it’s nice to have a nice little email list because if you are gonna do, I’m gonna say mostly stick to joint webinars and integration marketing. If you’re gonna do that and if you have a list of 10,000, 20,000, 30,000 people, for the most part, you’re gonna be able to say, “Look, let’s do a joint webinar. You email your list. I email mine.” Or you do vice-versa where you give a webinar to their audience and they give it to you. You can just trade straight across. You don’t have to mess with affiliate commissions. Just get the benefit of the traffic and so did they.
The same with integration marketing. The bigger the list you have, the better off you are in getting people interested in doing some type of joint promotion with you. If you have 300 people on an email list, it is much, much less likely that someone’s gonna wanna do a joint promotion with you.
With that said, in the early days before you can build up that list, you’re going to want to use affiliate commissions. If you do approach someone to do a joint webinar or to do integration marketing, you can say, “Look, we pay 20%, 30% of affiliate commission and here’s the link.” That’s how you’re gonna get them interested. Because then at that point, they can at least count on some type of revenue stream.
The way I did it back with HitTail, which is 2013-2013, is I looked around in the space and I looked at complimentary products, and so HitTail was a long tail SEO keyword tool. I looked at rank trackers and other keyword tools that didn’t use the same approach that we did. I, at the time, just cold emailed a bunch of them. I remember I made this list of seven or eight SaaS apps that weren’t these big behemoths, I didn’t email SEOMoz or anything.
Once that appeared to be more startupy or bootstrapped or whatever and all of them wrote back and said they wanted to do it. I was overwhelmed by that. I expected to get one out of that. I wasn’t able to do JVs with all of them. I think we were even just doing JV mailings. We were just gonna email each other’s list and kind of recommend a tool. I, of course, tried out any tool recommended, and then they did the same thing. Our lists were about the same size. We did no affiliate commissions at the time.
I’m not saying that’s gonna work in every niche but that’s something that I did. Then with Drip, when we started doing JV webinars, it was much more about relationships. That was in my wheelhouse. I just emailed people who I knew in the MicroConf space, in kind of our community. We did joint webinar I’m pretty sure with Brennan Dunn. I know we did one with Rubin for Bid Sketch. There were several others. But that was a lot easier. It depends on if you have a network in the space or if you’re going cold. But I’ve made either one work. It is something that you can do.
In terms of integrations, we start to build the integration and then create a nice landing page for it and then you email the company and you say, “Hey, can we do co-promotion?” With that, it really is gonna depend on the size. Because Basecamp and Stripe are not gonna co-promote with you. You’ll get lucky to even get listed in their directory at this point. But if you get someone who, it doesn’t have to be a tiny little company, if you get ahold of someone in marketing at even a decent sized startup, they will at least have the question of, “Well, how big is your list?” If you say, “I have 20,000 or 30,000 people on an email list.” It can raise an eyebrow. It can get you a mention. Maybe it’s just a single mention in an email newsletter they send out but they may have 100,000 subscribers. It can get some traffic toward you. That’s how I would think about doing it these days.
Mike: As a general rule, when you’re trying to find people to do these sorts of co-marketing efforts with, try not to go after somebody who has a list that’s more than twice your size or less than half yours. If you stick within that range, whatever that size happens to be, you’re probably gonna have much better results.
Because if somebody is much larger than you, they’re not going to want to do a joint marketing campaign with you unless you know who they are and you have developed a relationship with them. If they’re less than half your size then it’s probably not going to do a lot for you. That’s the thing that I would keep in mind as well when you’re trying to find people.
Rob: That’s a good point. Our last question for today is from Rusty Shackleford and he says, “Can you give me some insights on when to provide a trial versus a demo for apps that rely heavily on user-provided data? I’m developing a medical records SaaS. I’m keenly aware that it’s a waste of time for a prospective client to do a trial of my product when they would need to enter so much of their own data. Most likely, in addition to entering that data into whatever product they’re currently using. Would you suggest providing demos where I lead them through examples versus a trial of my product?”
Mike: I think of this particular case, if you’re dealing medical records and you have the objection or hurdle that somebody needs to overcome to start using your app is that they need to provide the data, I would lean much more heavily on the demos than on trials. I’d push them directly towards a demo whether that’s signing-up directly on the website or getting them onto an email list and then sending them to a sign-up form where they can sign-up for a demo, maybe ask them for information through a survey or something along those lines. Push them through that way. I would not go to trial route.
If you go with the demo route, what you can do is then you can directly address that particular problem during the demo itself and say, “Hey, we understand that in order to get you set-up, this is what you need to do. The next step after this is to decide if you wanna move forward with the product or not, and move to a trial. If so, send us this data and we’ll put it in for you.” Essentially, you’re doing onboarding for them and you eliminate that objection upfront.
You can try pushing that off to them which is really what you’re doing if you send them to a trial without you interacting with them which is going to raise that as an objection and they’re gonna say, “Well, I don’t really wanna do this,” versus if they have other things going on, they’re just not gonna do it is really what the bottomline is. Especially if they have to change whatever their current processes are versus if you talk to them, you have that conversation, get them to buy into the concept and what they can get out of the product after they start using it.
If they buy into that story, they send you that data, you take care of that leg work for them and once that data is in place inside of their app, then it’s ready for them to use. They don’t have to do all of that extra work. It just makes it easier for them to overcome that hurdle. If you don’t have a good import mechanism or good ways to just pipe the data out of other apps, it’s gonna make it really challenging to get people to go from a trial to a paid conversion. Because they’re just not gonna do the work is really the bottomline.
Rob: Yep. In general, I lean towards demos over trials. The problem is it doesn’t scale very well. As you scale up, that’s why you resort to having a trial. But relying on the customer themselves to orient and find their way around inside your app enough to understand the value, whereas you can explain that value in 10-15 minute demo, I bet in the first 5 minutes of your demo you can give more value than someone poking around inside your trial. Aside from the fact that your app sounds not complex, but there’s a lot of kind of onboarding necessary, a lot of work on their part, there’s no way I would consider letting people in for a free trial.
Mike: For some of the medical records, there’s subtle questions that people are gonna have which revolve around trust issues which you’re not gonna be able to really overcome very well with a free trial.
Rob: Right. Then they’re gonna have this account with no data in it. It’s gonna look terrible and you’re gonna have an account full of data that you can demo them. You’re gonna show exactly the value that they’ll receive. In your instance in particular, I’d definitely do demos. In general, when you’re bootstrapping and starting up, all during customer development, I recommend doing demos because you’d get so much more information from them.
If you’re still pre-product market fit, I recommend doing demos because you’re gonna find out why people do or don’t sign-up. They’re going to be more likely to get in touch with you if they decided to cancel or not get onboarded because you already have a relationship with them.
Post-product market fit if you can still do it, I know at certain points it makes sense to go with self-service trial sign-up but the dirty little secret is as much as I don’t like demos, I’d prefer to get in and dig around with an app and try it out, most people want a demo. They would much prefer someone to walk them through an app rather than try to poke around and do it themselves.
We had done a few experiments where we had just trials versus funneling people into demos and we converted the demos into paid accounts. It was like 2X, 2X the rate of just letting people get onboarded themselves even with all the help that we’re giving them via email and apps. You’re gonna convert more. People are gonna get more value out of it.
In general, I think it’s just a better way to go. There are obviously exceptions to this. There are tools like, let’s say, even like HitTail, it was a high-volume, high-return tool. It was an SEO keyword tool and people would come in, try it out here and there, and it was super easy, and at the end, it was a one-click set up. You literally just walk into something and it would pull keywords out.
A demo would be interesting but only for high-value account because some of those accounts are paying $10 a month and at that point, it just doesn’t make sense to do demo. There are exceptions to this but as a rule, I would go demo as the default and then figure out, “Well, is this one of those exceptions where I should really just have a self-service trial available,” or you have both options. That’s what Drip has today. You can still sign-up for trial if you still wanna poke around but there’s a big push of course to get people into demos because of all the reasons that I’ve stated here.
Mike: I think that about wraps us up for today. If you have a question, you can call it in our voicemail number at 1-888-801-9690 or you can email it to us at firstname.lastname@example.org. Our theme music is an excerpt from We’re Outta Control by MoOt used under Creative Commons. Subscribe to us in iTunes by searching for Startups. Visit startupsfortherestofus.com for a full transcript of each episode. Thanks for listening. We’ll see you next time.
In this episode of Startups For The Rest Of Us, Rob and Mike answer a number of listener questions. The topics include finding product/market fit, organizing notes for maximum effect, and growing from $100k to $1M.
Items mentioned in this episode:
Rob: In this episode of Startups for the Rest of Us, Mike and I talk about finding product market fit, organizing notes for maximum effect, growing from $100,000 of ARR to $1 million and more listener questions. This is Startups for the Rest of Us episode 348.
Welcome to Startups for the Rest of Us, the podcast that helps developers, designers, and entrepreneurs be awesome at building, launching, and growing software products whether you built your first product or you’re just thinking about it. I’m Rob.
Mike: And I’m Mike.
Rob: We’re here to share our experiences to help you avoid the same mistakes we’ve made. What’s the word this week, Mike?
Mike: As I said on the last episode, I kind of finished up almost the tech stuff that I’ve been working on and started switching over to working on the website marketing stuff and currently targeting a public launch date of August 1st. I’m kind of greasing the wheels of the marketing pipeline at the moment and doing everything that can possibly be done in the amount of time that I have.
Rob: Very nice. It’s about three and a half weeks from now.
Mike: Yeah, above three and a half weeks from when this episode goes live.
Rob: From whenever we record.
Mike: Yeah, whatever. Something along those lines.
Rob: It’s a few weeks. You must feel pretty good about it then. You must be pretty close to getting things out the door.
Mike: I do. There’s still a few things that need to be taken care of between now and then so I’ve realized that as I’m putting together the website itself to do some price turning, that there are certain things that need to be in place that are not there yet just so that I can charge different amounts based on different things. Maybe they’ll be there. Maybe they won’t when it goes live but if I need to toggle stuff on the backend, or do certain things, or just give people stuff that they normally shouldn’t have access to for the time being, then that’s probably not a big deal. I’m just finding those little edge cases here and there and reworking some things as necessary to make that happen.
One thing that I’ve realized over the past couple of weeks is that I added a customer, I think a week or two ago, and they had this massive mailbox that went back for years and years and had like almost 750,000 emails in their mailbox. The system generally held up pretty well. I’m pretty pleased with how that stuff is going right now.
Rob: That’s exciting. It’s nice to have some confidence going into a launch like this. You didn’t just up and build a product and have no one use it, not know if they get value, not know all the bugs that you have because you inevitably will until people use it. No app survives first contact with the real customer without having bugs.
You’ve taken this slow launch approach of trickling people in, getting your 20, 25 early customers in. That is obviously a more conservative way of doing it than the Silicon Valley pay $500,000 for some massive launch party. I realized that’s a strong argument. A lot of people don’t do that.
But even if you have a lot of funding, you want to move really fast that you staff up, and you build quickly, and then you just do this big splash launch. You’re like, “Alright, product hunt, man. Product hunt’s going to do it.” But then, if you product hunt and you haven’t already had 20, 30, 40 people touch this app, you just don’t know what’s going to happen.
As engineers, we know all the pitfalls and ways things can go wrong. While this is a slower, more calculated and more conservative way of doing it, this is obviously the approach that we espouse on the show. It’s that more careful, calculated, repeatable way to do it. It’s how I’ve launched a bunch of apps and how you’re launching Bluetick here.
Mike: I think the interesting thing is I’m looking at the app now and I see places where clearly things will start to break or slow down just because of performance and depending on what it is, sometimes, I just look at it and say, “I’m going to let this go.” Versus other times where like, and this mainly has to do with data sorting, paging, and making sure that you’re not returning too many things on the browser.
Those are few places where I’ve looked at and just said, “It can handle it. It’s not great. It’s not awesome user experience, but it works, so for the time being, I can just push it off and I’ll fix it later especially if customers start to run into it or it becomes a big deal. But it works, it’s not going to fall over. I’m not going to stop everything and put it on hold for another month or two to fix those things. I may as well just push it out there.”
Rob: You’re always going to have some part of your app that feels that way. There’s always a page or two that you’re embarrassed about, that you’re concerned it’s going to break, that’s too slow for large accounts. That will never stop.
Mike: I have a single-page application.
Rob: Oh Mike. Listeners can’t see me putting my head into my palm. For me, I’m actually working from Chicago this week. I’m with my son. We’re at his cello camp. We used to go to Oregon for this but now that we live in Minneapolis, it makes sense to come to Chicago. To be honest, it brings back memories, I was at the Oregon cello camp last year. I was signing life changing Drip acquisition documents on my iPhone with my finger from inside the halls of a music building on a small college campus that no one’s ever heard of in Central Oregon. It was just this.
I remember feeling overwhelmed and I couldn’t think straight. We’ve been talking about this for a year and doing negotiations for six months and then I keep thinking to myself shouldn’t I be calm, cool, and collected like at my home office with my laptop but no, I was running in and out. I dropped the kid off at cello, a lesson or a group thing, and then I ran outside and then I read on my phone, oh my gosh, this piece fell through. I’d get a thing to sign to override this and to sign over. It was exhilarating. It was also super stressful. But being here reminds me of that because it is the one year anniversary of the Drip acquisition just a couple of days ago.
Mike: Today, now you can sit there without the dirty looks from the other parents.
Rob: I know. That’s right. It’s Suzuki method of teaching cello and strings and so the parents were supposed to heavily participate and I actually had to talk to a couple of the teachers and I said, “Look, I have something going on right now. I’m in the process. My company’s being acquired. I need you to cut me some slack for a couple of days here.” That was fun.
Let’s kick off today’s episode with a voicemail question. Note to the listeners. If you want to get your question to the top of the stack, send a voicemail because we don’t get very many of them and it’s always cool to hear people’s actual voice. It’s just a better experience for everyone. It feels like The Collin Show. With that said, someone sent us a voicemail with a question for you, Mike, about Bluetick.
Andrew: Hi Mike and Rob, this is Andrew calling from Australia. Mike, I’ve got a question for you in relation to Bluetick. You talk a lot about product market fit. Have you found with Bluetick that you’ve had a general type of customer or have you found already that Bluetick has started to be suited for either a particular industry vertical, a particular customer type in terms of size of the company, or to some other characteristic in terms of the groupings of your customers? Love the show and hope to hear you guys answer this question on air. Thanks. Bye.
Mike: From the customers that I’m working with right now, they fall into a certain set of categories. I’m not saying that these categories of people, the customer profile that I currently have for the people that I’m working with right now is the long term ultimate customer base, I guess, of Bluetick. It’s just what I found so far and what seems to be successful.
They fall into a couple of different buckets. The first one is startup founders who are trying to validate an idea and most of them are trying to do cold outreach and get in front of customers or try and reach out to people that they think would be a good fit for their software. They plug people into Bluetick and it does essentially cold outbound outreach for those people and try to get those conversations started. That’s one group.
A second group is podcasters, to be honest. People who are running podcasts and are trying to get sponsorships for their podcast are using Bluetick to do that outreach to people they think would be a good fit and then start those conversations and then enter into the individual emails back and forth to try and get them to buy into a sponsorship for those podcasts.
A third category is small businesses who have an inbound lead funnel. Most of these are services based businesses where somebody will fill out a form on their website and the customer is approaching them and then they need to fill that request and probably ask for more information or try and get them to the next step. But what they’re finding is that a lot of people will fill out a form on their website or request information and then go dark or go silent.
What Bluetick does at that point is that because it’s a warm contact, it will help bring them back to the table. Very similar to Rob, you guys in Drip have this feature where you can send out a broadcast email and then several days later you can reschedule that same email to go out with a different headline if the person doesn’t open it. Bluetick, because of the way that it works, after the first attempt, if it doesn’t receive a response from the person, it will try again and again and again.
Those additional steps in the email sequence tend to aggregate together and give you a much higher response rate than if you just sent out one email, waited and if they didn’t respond, then you kind of walked away from the conversation. That’s the profile that I’m currently finding success with and people are comparing other products to Bluetick. There’s a lot of different cold outbound tools out there or tools that will remind you, “Hey, you sent an email to this person and they didn’t respond.” But Bluetick aggregates those things together, not just their features, but also the fact that it’s got a mini CRM built into it and helps you give a bigger picture of the whole thing.
That’s where I’m at right now. I don’t know if that completely answers the question but there’s a few different buckets that they fall into and I haven’t found one specifically that is better or substantially worse than the other.
Rob: Yeah, that’s cool. I go back and forth on this. As an entrepreneur, early on in your entrepreneurial journey, it’s like I stuck to apps that really had a tight vertical niche and I feel like that is a good way to keep things simple, you know where to find them. I like that approach. However, there are tools that in order to grow to a reasonable size, they’re in such a competitive space that I guess it could be argued that you could say that Bluetick is advanced follow up in sales for podcasters. You could start out that way and then expand. Land and expand is what it’s called and then go horizontal.
I think it’s too early to decide that right now. Podcasters may be too small of a niche, although it is growing.
Mike: It’s interesting that you say that that’s a small niche. I agree with you that it is but they talk to each other a lot. I get a lot of referral in that. I think that’s partly why I’m getting traction there. It’s because they talk to each other and they’re saying, “How do I solve this problem of getting sponsors for my podcast?” And then they say, “Hey, use this tool. It’s really helpful.”
Rob: That’s the thing. I say it’s a small niche but small is in quotes. If you would’ve build this to let’s say it tops out $30,000, $40,000, $50,000 a month, which I think there are enough podcasters to do that for sure. That’s small compared to a multimillion dollar app or some Silicon Valley exit. But that’s a heck of a lifestyle business if you want to keep it that way.
If you own the niche and you’re the name in doing and then you add things in that that really help podcasters find sponsorships, and then you could even branch out into, well, conferences need sponsorships. That’s the whole reason you built Bluetick, originally, was to help with getting sponsorships from MicroConf.
There are other things you could easily translate into so we’re definitely getting, I’m getting ahead of you on this or ahead of ourselves and I don’t think we need to make this decision or the distinction yet but I do think it’s an interesting conversation that you probably have or should have going in the back of your mind of do I need to go vertical because there’s so much competition. Because you have to be different somehow. You don’t just want to be one of many apps that’s doing the same thing.
You either want to go vertical with it and build the best one for that group of people or you want to have a feature or two that really make you stand out where they say, “Well how are you different with the five other apps that do this?” And you can say, “Well, it’s this and that and this is the approach we take. It’s the light way to CRM.” Or whatever it is that you’ve built in that’s different, that you at least have a talking point and aren’t just a commodity.
Thank you for the question. I like that one. I appreciate it. Our next question is from Aaron Cordova. He’s asking about notebook organization. He says, “How do you organize your notes? I’ve recently started note taking with an iPad Pro and a pencil. Do you have a page per day? Do you organize by topics?”
I used to use my notebooks both for longer term notes and thinking and things I was thinking through and I use it for to-dos. I tried so many to-do apps over the years and I finally switched to Trello. I can’t go back now because Trello keeps it on the cloud, have a record that never goes away. I can never lose it. I can access it from all my devices. I really like to-dos being in an app somewhere and Trello is finally the one that broke me with that.
Now, my notes are really just in a black, a Moleskine notebook and I do not do a page a day because I don’t write in my notebook everyday. I still use Evernote for some work things. I use Trello for to-do lists and I use my notebook when I am on an airplane, when I’m deep thinking, when I’m trying to hash through a problem because paper and pen is just I think so much better with that than sitting in front of a computer because there’s no distraction.
If I were to flip through my notebook, I definitely date my pages and I put a topic at the top. If I’m going to be thinking through one problem, or taking action notes from a book that I’m listening to, or trying to think of what else I’ve written on my notebook recently, I tend to put things in there I want to say for a long time. If I know that it’s just super scratch brainstorm-y stuff or it’s, I don’t even know, like a grocery list or something that I know I’m not going to care about in a month, then I don’t put it in my notebook. My notebooks, I keep them pretty much forever. I have notebooks going back ten years and I do flip through them and I have some fascinating insights that when I look back and think, “Man, your view of the world was so different back then.” Or maybe the world was genuinely so different. Just the founder community and the entrepreneurial community and my aspirations for it.
All that to say, I don’t organize by topics because I just flip to the next page, I put a date, and then I flip through. This means that I don’t particularly have a great organizational system. When I remember, “Oh, I remember Derek and I talked about this and I noted that down.” I have to think in my head. I bet that was about six months ago. And then I do, I flip through the notebook and I find the page.
While it’s not the most efficient way to get there, what I really like about it is the serendipity. Typically, when I’m flipping through that notebook, I’m reviewing like six, eight months worth of thoughts that I have forgotten about. Actually, the act of looking through them often will remind me of like, “Oh yeah, there was this feature we were totally going to build.” Or “Oh yeah, we never implemented that one thing.” Or “I never got back to that person.” It’s like all this stuff that isn’t urgent and doesn’t keep coming back on the radar, but it was a really good idea four, five months ago.
For me, my notebook is more of a time capsule. It’s for deep thinking and thought process. That was actually why I don’t like Evernote for it, because Evernote, I know it’s great if you want to search or any of these note taking apps. Great, if you want to search and you know what you’re looking for, but if you just want to kick back with a cold beer in one hand and a notebook on the other and you just want to flip through and read things almost like a dead tree or paperback book, that’s the experience that I relish and that’s what I love about my notebooks.
That was more information you probably ever want to hear about it and maybe a unique use case. I’m curious to hear what your take is on this.
Mike: I’ve tried Evernote and Trello. I still have my Evernote account. I just don’t ever use it and there’s things in there that I don’t go back and find or look at. The problem I found with both Evernote and Trello is that if I’m using it for any sort of to-do list or task management or anything like that, I end up with so many things in there that it just really falls apart. It’s too general purpose.
What I tend to do is it’s broken down based on what it is that I’m doing. Usually, what I’ll do is I’ll either start with index cards for a set of daily tasks that I need to do and get through and I can just mark them off as I’m getting through them. Occasionally, what will happen is that something will stay on an index card for too long and it will end up on the next day’s index card or the next week’s. If things end up there for too long, what I do is I essentially end up promoting it to some other place.
Sometimes, I’ll have a notebook where I will write down short term notes about something I’m working on, whether it’s really complicated or has a lot of things that I need to keep track of and I’ll write them down on paper. But at some point, like you’ve marked off a bunch of stuff and then you end up with 5 to 10 pages worth of stuff but half the pages are all crossed off, it doesn’t really make sense anymore and you can’t move them around.
At that point, I start moving things over into tools. For anything that is a bug or feature related, it tends to end up in FogBugz. Most of my general purpose tasks, or if it’s a marketing task, or related to a specific project, it usually ends up in my teamwork account. If it’s some sort of a thing that needs to go on a shared list that I use for home stuff, I use something called AnyList. I have a paid account that I share with my wife because it’s a family account so we’ll put our grocery list and things like that on it. It works really, really well for that.
Outside of that, I will also use Google Docs for taking long form notes about a particular problem that I’m working on where I don’t want to write it down if it’s not just a really quick thing or if I need to think about a lot of stuff, I’ll put it in Google Docs.
And then for mental brain dumps at the end of each day or at the end of each week, I have a journaling app that I have a subscription to called Penzu. That system works really well for me because each of those tools tend to be focused on a particular type of problem that it’s solving and it has the tools and the features and all the things that go with it that allow me to keep things organized within that context. Once I start crossing the borders between different context, the tools tend to fall apart. You can use FogBugz for marketing tasks but you don’t really necessarily want to be paying for a FogBugz account to give some contractor or somebody who is not going to touch any of your development stuff. Giving them a FogBugz account is kind of pointless so it’s easier to put that stuff in the teamwork.
I have a tendency to feel like this type of problem, it’s going to be different for everybody. That’s why there’s so many different to-do list apps and note taking apps because everybody works differently and you ultimately settle on something that works for you. The other 99 apps that you tried didn’t ultimately work out. I feel like this is a very context sensitive problem in terms of the type of person you are.
Rob: Yup. And the process you use and how you want to handle it. I agree. Thanks for the question, Aaron. I hope that was helpful. Our next couple of questions are from John. He says, “Hi Mike and Rob. I’ve been listening to your podcast for about a year and I get bummed when Stitcher doesn’t have your podcast ready to listen to every Tuesday before I ride to work. I have a couple of questions. First is what are your thoughts on pay what you want pricing? I’ve created a software called Breakneck Install which is a downloadable application that helps developers quickly create an installer for their application.
There are giants in the market and my product can’t compete with them. I don’t feel like I could charge near what they do which is more than $500 per license. I thought of trying to pay what you want model. One of the benefits I see is not having to worry about licensing issues such as maintaining and creating backend infrastructure to deal with licensing. My fear is that I try this and then decide to go a traditional pricing model which may make future customers unhappy. Do you have any thoughts on this?”
Mike: I think for a product like this where you’re trying to build an installer, it almost feels to me like what you’re going to run into is the market is going to be split between these people who are just starting out and they’re trying to build a product but they don’t have any money so you’re not going to get them to donate money to your cause.
It’s not going to be a viable source of income. If it’s something that you want to do because you have the money laying around and you want to put your effort into something like this, then that’s fine but I wouldn’t look at pay what you want pricing for something like that to really be able to make a dent in your bottom line and be able to let you go full time on it. I just don’t think that it’s going to happen.
There are also a lot of open source alternatives out there that would make something like this difficult. You’re absolutely right when it comes to installers, most of them tend to be very expensive and what you’ll find is that the people who don’t have the money will go for the free open source versions. And even if you give them a paid option that is a pay whatever you want, it seems to me like you’re probably not going to get very much money from that. They’re not necessarily going to be willing to pay software maintenance and things like that.
You’re going to spend a lot more time fixing bugs and addressing individual issues than you are trying to build the product where if you were just selling it to smaller businesses that had revenue and the capabilities to pay $500 to $1,000 per license, you’d be able to make a business out of it.
Rob: I have mixed feelings about this. I’ve never done it so I can’t speak from experience. I can only speak from the experience of entrepreneurs who I’ve seen done it and who I’ve talked to. It can work but you need a really large install base. You need a lot of people downloading so you can’t just say I have a few hundred downloads a month and expect that you’re going to be able to do pay as you go and make any kind of money from it.
The problem is that if you do pay as you go and someone pays you $10, how much support do you now owe them? If they start asking for feature requests, if there are bugs that they discovered, if they’re demanding, if stuff goes sideways, it becomes a challenge. I can see a lot of problems with this and my gut is that it’s not going to work unless you are getting, I don’t know what the number is, but it’s thousands and thousands of downloads per month, because a bunch of people are going to pay you nothing, and then a few are going to pay you a small amount.
When podcasters try this, when other small, downloadable WordPress plugins or whatever try it, they don’t tend to get a lot of money. I don’t know that I agree with your fear that if you were to have pay as you go for now, that you can’t undo that later without making future customers unhappy. I think what I would say is I’d rather call it a beta, or an early access, or put some moniker on it and I would say, “It’s pay as you go while it’s an early access.” Even if you already released it and it’s not an early access anymore, that’s what I would do so that if you decide that you don’t want to go pay as you go anymore, that it just doesn’t work out financially, you can always undo that and it’s a pretty easy thing.
I’ve seen apps go from free to paid before. If you grandfather people who already have it, I don’t really know what complaint future potential customers could have other than, “Oh, I should’ve downloaded it last month instead of waiting till now.” There’s a time where I tripled the pricing of DotNetInvoice from $100 to $300, and a couple of people emailed me and said, “Hey, I was in the process of thinking about buying it. Can I still get it for $95, or $98, or whatever it was?” I gave it to them. It was like two or three people.
One I later regretted, he actually turned out to be the worst customer, the first toxic customers that we had but that’s beside the point. I don’t know. It’s easy enough to try. I see your point. I think if you have something that can’t compete in the marketplace like going freemium or pay as you go is often not the right answer. The right answer is make something that can compete in the market place. Have a differentiator or just set a cheaper price.
If this thing really does do a good chunk of what developers need, they can only get it for $500 elsewhere, then what about charging $99 or $199. You don’t necessarily want to be the low price leader but is there a space in the market. You think about Infusionsoft, Eloqua, all these really expensive marketing automations and Drip came in at the beginning, a lighter weight product that was easier to use and less expensive. I do think that there’s an angle that could be added there as well.
Mike: I think the lower price point is definitely an angle that you can go at because there are certainly ways that you could charge a couple of hundred dollars for an installer. I do like your idea about letting people know, “Hey, this is pay as you go for the time being.” And then make it a point that it is something that you can undo later and move to some other one. Just be upfront and clear to people like, “Hey, this is the pricing for now and it’s going to change. We just don’t know what it is yet.”
Rob: Our next question is about growing from $100,000 of ARR to $1 million. This is from Pawel Brzeminski. He says, “Hi Rob and Mike. I’ve been listening to the podcast for years. I really respect what you’ve done and that you’re sharing all this knowledge with the rest of us. I found your podcast immensely helpful in launching my own SaaS app, which is called Snap Projections. How do you think about growing a self fronted SaaS past $100,000 ARR? So that’s about $8,000 or $9,000 a month. What do you specifically pay attention to in terms of marketing, sales, operations, hiring? Any specific tips on growing in a vertical niche versus horizontal? What would you do differently right now?” It says more of a question for Rob but it would be interesting Mike’s take as well. “Anything specific to watch out for?” His background on them is that they have two people on board, more than 120 clients/customers, relatively low churn, and they’re operating in a niche of financial services applicable to Canada only.
Mike: I’ll be honest. I don’t know how qualified I am to actually answer this question so Rob, why don’t you throw some things out there and maybe there’s something I can think of, I’ll just piggyback on it.
Rob: For sure. It’s a really broad question but I appreciate it. It’s almost like what are the things to watch out for because they’ve already had a decent amount of success obviously to get to even that $8,000, $9,000, or $10,000 mark. It’s like what’s the difference to get to seven figures or what has to change between then and now?
What my experience with this is that it’s going to depend on how big the market is that you are in. I’d bring up Drip because that’s the most recent thing I’ve done. We were in a position where we were in such a large space that we didn’t have to change anything in terms of our market. We didn’t have to go from vertical to horizontal or do any of that because there were enough people who wanted it that we needed to do it. We needed to execute on marketing and hiring in essence. Keeping developers going to build features but really, the product, once we had product-market fit, has always been really solid.
I think that’s the first question to ask. If you really are in a niche of financial services in Canada only, it’s like is the market even big enough to get you to a million or are you going to have to either go into another vertical or go more horizontal and serve a lot of vertical niches or just not even be vertical at all. That’s one thing to think about.
I think you can definitely get to seven figures with a very small number of employees or contractors, somewhere between 5 and 10. I think one thing to watch out for is hiring too quickly or trying to hire ahead of revenue because you want to get there faster. It’s a lesson that I learned. It doesn’t necessarily, especially hiring developers, it doesn’t necessarily make that revenue move faster. If you’re already at that $10,000 point, I always would try to look at what is my bottleneck? Why are we not growing faster? Is it because our product needs more features or is it because we’re not marketing or selling enough?
My next hire would be either a developer, or it would be a marketer, or a salesperson, or we’d start doing demos, or whatever. When we were in that $10,000 to $20,000 MRR range, maybe we just hit $25,000, that was when I realized that not having someone who could talk to people on the phone and essentially do customer success/sales, that was a limiting factor for us and that’s when we brought Anna on. That was a game changer for us. That was a bottleneck for us in that $20,000 to $30,000 range.
You may be there but then again, you may be that salesperson and that’s not a limiting factor and it’s more of your market’s too small and your development team is moving too slow or whatever and they need more help. That’s the thing I think that you need to think about at every point is whether you’re at $10,000 or you’re at $50,000, what is your limiting factor? What’s going to double your growth next month or add 50% of your growth to next month because you want growth. The bigger you get, you have to accelerate growth.
When you’re at $10,000, growing at $1,000 a month is actually a victory. At the time you get $20,000, $30,000, you want to start growing at $5,000 a month so you need to think differently about how am I going to 5x growth between those two points. That often means you’re either growing wider, building features faster or dumping more money in the marketing or getting into paid ads, finding a new channel, because that can be a big piece of it. You may just need more people on the top of the funnel. That may be a thing or you may need to close more people that are in the funnel.
That’s why I use all those rules of thumb that we’ve talked about in the past. If you’re already converting 40% to 60% of your trials to paid and you’re asking for credit card up front, then that’s fine. I would push that aside for now and I wouldn’t try to improve my on boarding and I would say, “How can we just get more people to the top of this funnel?” But if your churn is 10% per month, well then, “How are we going to cut churn by making a product better and by retaining more people?”
It’s looking at each of these things and just bouncing from one to the next and you improve one and then you put more people in top of the funnel and you realize, “Oh, now this other thing is broken.” And you just hop from thing to thing. That’s kind of a brain dump of how I thought about it but I hope that gives us some things to chew on.
Mike: I like everything that you just said there. It boils down to recognizing where the bottlenecks are going to be. One thing that comes to mind is you mentioned something about limiting yourself to just Canada for example, because that’s where the company is based right now and those are the people that they’re targeting. But does the customer profile need to change? Are you targeting one type of customer and you need to move to a different type of customer?
Let’s say small financial planning companies versus individual financial planners. Does your customer profile need to change in order to be able to get more revenue per customer in a way that’s going to help the business grow or are you going to max out? Again, that’s just a limiting factor. Not necessarily through geographical border but the customer base that you currently have and that you’re going after.
That all boils down to the same thing. Is there that limiting factor that you’re going to need to overcome? Whether it’s that or whether as you said, the bottlenecks in the marketing funnel, customer acquisition, all that stuff. It’s finding those bottlenecks.
Every lawyer, even my lawyer has done this before. He will look at legal agreements and he will take things from different legal agreements that he’s seen based on how they’ve been used in the past. If one of his customers got screwed over by a particular piece of legal jargon, he will sometimes take that and put it into his legal agreements to make sure that his customers and clients don’t get the short end of the stick when it comes to interpreting the documents that he’s put together.
Based on how experienced your attorney is, they’re going to have a wider wealth of knowledge, the longer they’ve been in business and the more agreements that they’ve seen and they’re going to be able to use those to craft the one for you. Maybe you get two or three different lawyers from different firms involved, it seems like it would be overkill but it’s always an option. I’m sure that larger businesses tend to have legal teams so that they can get that kind of experience and breadth and put together something that covers them from every possible angle.
That’s the way to ultimately get rid of it all. It costs a lot of money and it’s again, for me and my experiences, not something that I spend a lot of time or money thinking about in the early days of an app because there is less exposure at the time but you have to evaluate it for yourself.
Mike: An interesting hack for this to find out how much exposure you have is to go to an insurance company and ask them for a quote for liability insurance and find out how much that quote is and then use that to decide whether or not you need to go out and get something crafted from an attorney to help cover you. That seems to me like a pretty good way to get an independent gauge of how risky what you’re doing is.
For example, back when I was doing enterprise level consulting, we would be given admin access at the domain level on somebody’s network and some of these companies were like Johnson & Johnson, Pfizer, NASDAQ, those types of companies. Our insurance rates were outrageous. They were like $500 to $1,000 a month for insurance. It was only two or three of us. That was absurd but my wife’s got insurance for her business and it’s only, I forget, like $100 a month or something like that. It’s ridiculously low.
Depending on what you’re doing and how much risk and exposure you have, the insurance company will charge you more. Just getting a price quote from them would be a good way get an independent verification of how much risk there is without you having to sit down and do a ton of work on it. You’re going to have to provide them with paperwork and documentation and they’ll have an auditor review it but you could use that to help out.
Rob: Yup and if you’re going to do that and get a quote, I would recommend a company that I worked with before. They just made the process really easy. It’s foundershield.com. They themselves are a startup. It’s kind of just an insurance broker but they operate, like, I’m guessing they have some funding because they operate like you would want a startup to operate rather than some stodgy old business insurance company.
Mike: Matt, hope that helps. I think that’s probably the place to wrap it up for the day.
If you have a question for us, you can call it into our voicemail number at 1-888-801-9690 or you can email it to us at email@example.com.
Subscribe to us in iTunes by searching for Startups and visit startupsfortherestofus.com for a full transcript of each episode.
Our theme music is an excerpt from We’re Outta Control by MoOt used under Creative Commons.
Thanks for listening. We’ll see you next time.
In this episode of Startups For The Rest Of Us, Rob and Mike talk about how to recover from coding for months without talking to customers. Based on some questions a listener sent in, the guys give advice to the classic problem of spending all your time developing and not enough time talking with customers.
Items mentioned in this episode:
Mike: In this episode of Startups For the Rest of Us, Rob and I are going to be talking about how to recover from coding for months without talking to customers. This is Startups For the Rest of Us episode 347.
Welcome to Startups For the Rest of Us, the podcast that helps developers, designers, and entrepreneurs be awesome at building, launching, and growing software products, whether you’ve built your first product or you’re just thinking about it. I’m Mike.
Rob: And I’m Rob.
Mike: We’re here to share our experiences to help you avoid the same mistakes we’ve made. What’s going on this week, Rob?
Rob: Well, I am back from Sweden. I had a great time attending and speaking at Brennan Dunn’s Double Your Freelancing Conference in Europe. He said it was going to be the last DYF conference he throws and then he’s going to only do small retreats after this so it was cool to meet up with him and his crew.
And then I spent a couple of days with Sherry in Stockholm. We had left the kids at home and we had a great time seeing the sights, painting the town red, and I got a good amount of work done. It’s crazy when you’re in a new environment. I was basically taking the days off, “vacation days,” but there was still stuff going on back here, back in the office so a couple of hours a day, 90 minutes or so, I could just hammer out a ton of email and Slack replies.
I had some really good ideas because I had the headspace to think about stuff so I noted them down and I’m starting to put those in the queue right now. It was actually a productive, I wouldn’t even say it goes far as to say as it was a workation, it was more like a light vacation with a bit of work sprinkled in. That’s, to be honest, my ideal thing because I think when I don’t work for like a week, I feel disconnected and I get bored just travelling and being in places without having something to occupy my mind.
Mike: I’d imagine that’s a lot like retirement as well. I’m not one who just likes to take extended vacations just for exactly that reason. I find myself getting bored.
Rob: Yup. I think that’s where having hobbies, like I do investing, which is fun, but I can only do so much of that in a day and think about it for so long before I need to do the next thing. After the conference was done, we would go see one sight and then we’d go to lunch and then Sherry and I would come back in the afternoon which is when this time zone was waking up and Sherry had a few calls and she was still doing quite a bit of consulting and stuff. It was good. It was a nice mix. I really enjoy that stuff.
I also enjoy getting away for retreats. Like we’ve talked about in the past, taking a full two, three days but seven complete days for me without thinking at all about the things I’m most passionate about, which is a lot of what I work on, is always a hard stretch.
Mike: Cool. On my end, I finally got the two step sign up process for Bluetick all squared away. There’s definitely edge cases in there that I just said, “Look, I’ll deal with this later.” Instead of making the whole thing bulletproof, I made it basically just work. I know that there’s going to be cases where something is going to come up and somebody goes to sign up and it’s going to break. I’m just going to have to figure it out at that point because I don’t really have the time to try and capture every single edge case.
Right now, it’s just going to show some generic messages if it goes sideways and certain ways that I just don’t know about because I don’t know all the different ways that Stripe for example, could say, “Hey, this card isn’t going to work.” I got that all squared away and finally got started working on the marketing and sales websites. I got the price and page all set and I’m working on the tour. I got to create a couple of videos to add in there, probably put one on the home page then work on flushing all the rest of the tour and figuring out whether I want to do just one page for the tour or I want to divide it up into several of them based on what different situations people are in.
I’ve got a bunch of different notes that I’ve aggregated from various customer discussions that I’ve had and different things that they’ve either keyed on or asked about during demos and putting those into specific places in the tour and try to essentially walk somebody through the decision making process for it.
Rob: Good for you, man. That’s exciting. I know it took a lot longer than you wanted to but it’s got to feel good to have that behind you and be able to pull the next thing off the list.
Mike: It is. The thing I don’t like about doing the stuff on the tour side of things is that it’s a completely blank slate and I’m not a designer. I’m sitting there, going through and trying to figure out how should the page be laid out and what should I say in certain areas and how should one thing lead into another. For whatever reason, it’s really hard for me to do that. I can conceptualize what I need to say but doing the layout for it, that’s the part I’m having a hard time.
Rob: Yeah, that is hard. I haven’t done that in years. When I used to do it, I wasn’t very good at it. It’s such detailed work. It’s tough. That’s what you got to do when you’re scrapping being bootstrapped and you’re counting the days until you can hire someone else. Get a contractor, even if it’s a contractor, get somebody because they’re so much faster at it and the end product will look better too.
Mike: Plus it’s all in WordPress. There’s only so much that I can do in WordPress. I’m just going to make do with what I’ve got and then after that, just look for a designer at some point down the road, when I actually have the funds for it.
Rob: For me, my other point of update is we’ve had some recent questions on the podcast about books, or resources to learn how to build a SaaS app and someone had pointed out the PHP spark framework, which I think is pretty cool.
There’s another one in the works now. It’s Marcus Wein. He’s in Austria and he’s working on a SaaS guide book for Ruby on Rails. I actually met him at Brennan’s conference. We talked about stuff and then he cooked up this idea and put up a landing page while we were there. I thought that was cool. He’s getting to work on that book and the URL for that is saasrailsbook.com.
If you’re interested in the fundamentals of how to build a SaaS app and are willing to either learn Rails to do it or you already know Rails and you want to just learn how a guy who’s built dozens and dozens of them would architect it and then all the things that he would think about, go ahead to saasrailsbook.com.
What are we chatting about today?
Mike: Today, we’re going to be diving into a problem that a listener had sent in to us. His name is Zac and he has a product called neverlate.io. He started working on it. He spent about three months working on it and has a basic MVP all set up but he fully admits that he made this classic mistake where he spent several months in his basement working on it and has come out of it and now he’s ready to try and find customers but he has no customers to go to or to show it to because he spent all that time working on the product itself rather than doing any customer development.
He’s tried a couple of different things to generate some traffic. He’s tried some AdWords. He’s talked to a few different people but really, he’s at ground zero at this point and he’s wondering, “What do I do here? What do I do to try and move this forward and make it work?”
Rob: The URL again is neverlate.io. It is an appointment reminder service. Right now, it is very horizontal. It doesn’t say appointment reminders for XYZ niche. It’s just a broad appointment calendar plus it can send automated text messages. I guess that’s it. It doesn’t look like it makes phone calls either. Anyways, I’m just looking at the home page. Obviously, I haven’t used the app, just trying to give the listener an idea of the business. It starts at $29 a month for up to 200 appointments a month and it has a $50, an $80, and a $500 tier.
Mike: This reminds me a lot of Patrick McKenzie’s appointment reminder app. Maybe, that’s where the idea came from. But to give a little bit more details on this, I’ve gone back and forth with him just to ask a couple more detailed questions. When he came back, he basically told me the product is functional but he doesn’t have a customer list. He doesn’t have a channel where he can start to do customer development. As you said, the bottom price point is $29 a month.
In terms of his target market, he’s a little bit unclear on where to go with that. He knows certain ones that he’s probably going to skip so he’s inclined to skip massage therapists, for example, because he doesn’t think that they’re going to be willing to pay more than like $10 a month. And then in terms of sign ups, he’s gotten some from AdWords. He spent about $50 or so in AdWords and he is getting people to sign up for trials but it’s not a lot and obviously AdWords can get very expensive.
In terms of lifetime value, he really doesn’t know yet. He’s thinking maybe a year or so of service so around $350 for lifetime value of a customer. His base question is really just what do I do at this point? Should I spend more money on AdWords? Should I do something else? What are my options and what are your recommendations about where to go with this?
Rob: We have an outline here but to kick us off, you’re in a real tough place because you basically have no customers, no list, and you have a me too product. There’s nothing that differentiates this product that I can see from, I won’t say a slew of others but I bet if I search, I can find a half dozen apps that do exactly what this does. Definitely back against the wall at the present.
Mike: I think that’s probably a situation that a handful of listeners have found themselves in over the years, probably more than a small handful, where you’ve built something and you get to a point where like, “Okay, yeah, I’m ready to take this to people and show it to them because I’m no longer embarrassed about what it is or what it looks like.” But you haven’t gotten far enough down the customer development road to figure out who it is you’re going to talk to.
I think in this case, your first priority is to prove, one way or another, whether or not this idea is going to be viable for you to execute on. I’ll put “prove” in air quotes because you’re really never going to be 100% sure that it’s going to work but you can get an idea of it. You can start looking down the road and you start doing that customer development and try and figure out does this look like it has legs or am I just wasting my time and money to try and to get this to work?
Along that lines, I think the first thing to do is really set a time line. For something like this, it seems like a six months time line is probably an appropriate timeline to set for this. Especially if you’re working on the side, if you are working on it full time, probably less since you have a fully functional MVP, take that time line, set it aside, and say, “Okay, I’m going to do X things during this time.” And set goals for that entire time line.
The first goal that I was thinking you would set up for six months, months one and two should really just be focused on trying to get a certain number of customer discussions, whether that’s five per month of five per week. Really, you can set your own pace and schedule at that. But you’re trying to figure out can I reach these people? How do I reach them? Once you start having those discussions with them, you learn more about who they are, what they do, how much time they spend in different areas, especially trying to solve this particular problem, whether it’s something that they’re willing to pay for.
Once you have that information, you ask yourself, how much are they willing to pay? Obviously, you ask them as well. But you want to find out, are they willing to pay for it, how much, and listen to the language that they’re using. Really, these first two months are just spent doing these customer discussions. Yes, if you can get them to a trial or on to a paid account, that’s great, but that’s not your goal here. Your focus should be getting a certain number of customer discussions because that’s going to give you an idea of how easy or difficult it is to continue doing that down the road.
Rob: Right. If you can’t get into these customer discussions, which are really about learning, as you’ve just said, rather than trying to build revenue, if you can’t find anyone who’s willing to talk to you, that’s a very, very bad sign. It’s a sign that you’ve built something that people just don’t care about, don’t need, don’t want, which is going to be something you could very well run into with any product that you launch. At that point, you have to decide am I willing to essentially continue to add things to this that actually make it unique so that I’m the only app that does this in this way, or to pick a niche and niche down.
Like you said, you don’t want to do massage therapist and I don’t blame you. Is there a group? Is it medical or dental because they have HIPPA so they’re really expensive and so they’re the $500 a month and up and you offer only HIPPA compliant so it’s important reminder for medical and dentist office. There’s probably some others in that. This is where you have to do this research. This is not the time to run Facebook ads to a landing page and see who converts and play it that way. This is an app where appointments are brick and mortar type of things. I can’t think of an online audience like designers, or photographers, or developers, or entrepreneurs, there’s certain audiences that are just online a lot.
Appointment reminder, if you can figure out a way to target an online audience, great, but if not, then you have to go through these much more manual steps. I don’t really see an angle here where you’re just going to rent some Facebook ads and convert people to trial and split test your way out of this. For the whole six months, you’re going to be learning that these first two months are going to be critical. They’re going to, like Mike said, tell you whether or not you should continue.
Mike: Along with that, in these first two months, you’re trying to figure out who that target audience is. I think early on, Zac had said he was probably going to skip massage therapists. Maybe there’s some data he already has to indicate that they’re not willing to pay for that. That’s fine. But are there other professions or other verticals that you can target and try to have those discussions with them and see if that’s going to work, see if that’s an initial traction channel that you can start to establish.
If it is, great. You can move on to the next steps in months three, and four, and five, and six that we’re going to lay out. Your focus at this point is trying to figure out who those people are and if you can establish a recurring channel of them to have those discussions with. If you can’t, then maybe it’s time to pivot to a different channel, a different vertical, or can the whole thing.
I probably wouldn’t can it after trying to find one vertical. If you go to massage therapists and they say, “No, we’re just not interested.” Okay, great. Go to dentists and then maybe pivot over to a solo practitioner doctor’s offices, for example, or plastic surgeons, or something along those lines. Each of those could be a one to two month effort but you’re trying to figure out is there a place where you can get customers on a recurring basis, at least in the early days?
If you go through several of those iterations and you still can’t find them, then that’s the point where you need to re evaluate your position and decide whether or not to just cut your losses and move on.
Rob: For months three and four, assuming that months one and two are successful and you figure out a niche or a group that you’re going to target, months three and four, your KPI is the number of paying customers after you’ve had a direct discussion. This is very, very much not scalable but what you’re trying to do is to learn objections. You’re trying to overcome them via discussions. You’re trying to close deals. It’s still learning but you’re trying to start making the rubber meet the road and actually get some revenue.
What you might find is that you get through three and four and you can’t get enough paying customers to make it worth your while and you have to go back and repeat months one and two and find a new group to target.
Mike: The whole point of this particular piece of it, I don’t know if some paying customers is like the sole thing that you should focus on. Getting them into the app and getting them active and using the app, that’s probably a much more important first step. Obviously, you want to keep them as paying customers and get them to convert from any sort of free trial that you put them in into a paying customer. But even if they don’t, you’re still going to learn from that. The focus is really finding a certain number of people that you can put into it.
Again, you can set those numbers yourself. You can base it on how many conversations you’re actually having because obviously, if you only have 5 conversations a week, you’re not going to get 10 customers a week. That’s simply not going to happen. From that, you can back that off and put people into the app and learn those objections. You can overcome them by talking to them. A lot of times, people will have a question that if they’re on your website and they have a question in their mind, it draws doubts for them. They will not sign up because of that.
When you ask them, “Hey, would you like to sign up for an account right now?” They’ll say yes or no. If they say no, you can ask, “Well, why not? What’s stopping you? What is it that’s holding you back here?” Those are the things that you want to write down. Every single question that somebody asks, you want to write that question down. That way, you can go back to that and over time, you’ll get a base of let’s say 20, 30, 50 people you’ve talked to. Start aggregating the number of questions that they ask and which questions they ask. You can identify which of the questions were most prevalent, which ones the most people had and use that in your marketing copy once you get to months five and six, which is where you are trying to land the paying customers or on board people without having those direct discussions.
Rob: That’s month five and six. It’s moving out of the I’m talking to everyone, I’m doing demos for everyone, and I might able to start getting people to overcome their objections and sign up for a trial just purely based on a marketing website.
Take these timelines with a grain of salt here. We heard from Jordan Gal last week and he was giving demos for six months, eight months. It wasn’t just the two months we have here or I guess we have four months. One and two, finding the audience and three to four is overcoming objections, and five and six is moving towards the more automated way. Their journey took longer. They have a more complex product, probably harder to explain, harder to demo. Appointment reminders tend to be fairly, I think it’s pretty easily understood by the prospect so perhaps you’d have an easier time or perhaps you’ll have a tougher time getting to five and six because again, your product isn’t differentiated from others that they could find with a Google search.
That’s the idea here. This third step, this third piece is trying to move towards having more automated things in flow and maybe you don’t remove demos altogether, maybe you figure out you have people self select that if they’re in the lower pricing tiers, then they sign right up and if they’re going to pay you three figures a month, it’s probably worth having a conversation with that person. You have a contact that’s linked. Even if you show your pricing, you still have some type of thing, how many appointments per month and immediately, you get a paying customer and have an idea that it’s worth reaching out to them with a calendar link, trying to set up a conversation.
Mike: With each of these sets of two months, months one and two is really about trying to get a certain number of customer discussions going and then month three and four are putting people into the app through those direct discussions and then five and six is getting those customers onboarded without having those direct sales discussions. That’s really just a logical progression. As Rob pointed out, your timeline may vary quite a lot. It could be closer to a year or it could be closer to two months. It depends on how complicated your app is, how far along it is, how many people you’re able to have those conversations with early on, how quickly you get traction, and it also depends a lot on what your schedule is.
If you’re working on it full time, you’re going to be able to move faster. If you’re working on it on nights and weekends, you’re probably not going to be able to schedule 25 calls during the week. It’s just not going to happen because you have a full time job and you’ve got other responsibilities. During the work week, it’s going to be very difficult for you.
But all of this is really just establishing this logical progression so that you can determine whether or not this idea that you have or the product and the MVP that you put together is going to go anywhere so that you’re not wasting too much time trying to make something work that’s simply not going to for you.
I think that’s another key distinction that we’ve made on this podcast before, which is that even though something could be a great idea and it is reasonably well executed, it may not be the right idea for you. If it’s not something you’re passionate about or you don’t want to do or you’re just not interested in it, you’re not going to do it as well as if it was something that you were extremely interested in and extremely motivated to do. You’re going to push things off and not be as motivated to move people forward in the sales funnel and do the website, coding, and everything else.
It’s going to be harder for you. Maybe it’s just not the right fit. Maybe some other product would be a better fit. Again, these are all things that you need to evaluate as you’re going through this process.
Rob: We call that in the biz, product founder fit. As you said, is the product a good fit for you, for your personality, for what you want to do for the customers you want to work with, for the features you want to build. It’s a bit of an amorphous concept and it’s hard to know upfront but what’s nice is that Zac said, right off the bat, “I don’t think I want to work with massage therapists.” That’s like, alright, good. It’s a good thing to know that. Don’t go after that market because you’re probably going to find out that you’re not, even if you found success, you’re not going to enjoy it. You’re not going to stick with it for the long term.
Mike: I think that’s an interesting side conversation. Even if that would work, do you want to do it? I think in some cases, the answer to that is probably not. There’s certainly groups of people that I would probably not want to work with or probably would not enjoy and everybody has their own either biases or people that they know in certain industries, they’re like, “I just don’t want to deal with any of that stuff.”
Again, it may work out. It’s just like marketing tactics. There may be some things that you’re really comfortable doing and the next person may not be comfortable with that at all.
Rob: Yeah, there was an app I almost acquired. I’m trying to think. It may have been after HitTail, or I still owned it but it had grown to where I thought it was going to grow and I was looking at other avenues before Drip. I looked at acquiring a bunch of different apps. One of them was going to put me marketing to and having a customer base of designers UX and usability folks. I had no reach into that market. Obviously, I have an understanding of what they do but I am not in that target market.
It was Ruben Gamez from Bidsketch who asked me, “You’re doing a market pivot by going from an SEO tool, which is at least marketing technology, into something that goes after a completely different audience, is that something that you want to do for the next three, four, five years?” Frankly, I have no qualms with working with designers and UX people, I think it would have been an interesting adventure but it would’ve been a huge learning experience for me.
I thought, “If I do this, I’m going to have an uphill battle to learn a whole new space and to learn what are all the sites where people hang out? Where are the blogs? I already know this from MarTech. That is one of the reasons that I wound up doing Drip. Because it’s not the same as an SEO keyword tool but it is another marketing SaaS and I already knew so much about the space because of my heavy involvement in evaluation of tools from my own personal use. It was just a different thing.
I think I still would’ve been successful. It probably would’ve taken longer had I done that. I would educate myself about a market, make myself a name in that market, which I really, really don’t have. And so, it’s just something to think about as you go through your ideas.
Mike: I think one of the last questions that Zac came up with was should I spend more money on AdWords or should I just abandon that and go do something else? I think, Rob, you’re probably in agreement with me on this one. But AdWords is probably not the way you want to go, especially if you don’t have a lot of money to throw into this because you’re going to spend money trying to learn. It’s not that spending money to learn is a bad thing but you’re going to probably spend much more money than you would if you had some customer discussions first and you waited until month three or four to start pumping up the sales funnel a little bit.
After you’ve gotten some of the terminology a little bit, you’ve narrowed down the market a little bit, if you’re just throwing money out there to try and figure out where the market is, it’s going to be very expensive to do that.
Rob: Yeah. The tough part is since the audience is brick and mortar, it’s going to be expensive and hard to find them. There are tools where everybody’s online and they’re always signing up for new things. You can do the curiosity play and get them to sign up and you have a low price point and you could test an idea with ads landing pages in more broader scope stuff if you had the money to do it. I don’t see an avenue to do that here. Just by nature of the potential audiences that we can come up with, I think you’re right.
I’m in agreement that AdWords is probably not where you’re going to get a bunch of learning at this point. Maybe you could run AdWords just enough to get that trickle of calls that you want. And again, it’s going to be expensive to get that trickle going. But if you have no other avenues, yeah, maybe AdWords or Facebook ads, or some type of paid acquisition, but if you can pay $10, $20 to find someone to get on the phone with you, who has some inbound interest, that’s interesting but you know you could just as easily do some cold outbound email or cold phone calls and perhaps get the same result with less money but more time.
Mike: That’s really what this is all about. It’s striking that balance between how much money you have available and how much time you have available. If you have more time than money, don’t do paid ads. Have those customer discussions, learn who it is that you need to target. If you have a lot more money than time, spend on AdWords and learn who but it’s going to be dramatically more expensive without having those customer discussions to guide you.
Rob: If you got value out of today’s show, we would really appreciate a five star review in iTunes, or Stitcher, or wherever you partake of this glorious audio adventure. You don’t even have to write a sentence saying how cool we are. You can just hit the five star button and we really appreciate it. It helps people find our podcast, gives us motivation to keep going.
If you have a question for us, you can call our voicemail number at 8888-0196-90 or email us at firstname.lastname@example.org.
Our theme music is an excerpt from We’re Outta Control by MoOt. It’s used under Creative Commons.
Subscribe to us in iTunes by searching for Startups and visit startupsfortherestofus.com for a full transcript of each episode. Thanks for listening. We’ll see you next time.
In this episode of Startups For The Rest Of Us, Mike and Rob talk about why some products fail and others succeed. Based on a listener question they lists reasons for both sides while also revealing some old failed product ideas of their own.
Items mentioned in this episode:
Mike [00:00]: In this episode of ‘Startups for the Rest of Us,’ Rob and I are going to be talking about why some products fail and others succeed. This is ‘Startups for the Rest of Us’ episode 334.
Welcome to ‘Startups for the Rest of Us,’ the podcast that helps developers, designers and entrepreneurs be awesome at building, launching, and growing software products whether you’ve built your first product or you’re just thinking about it.
Rob [00:26]: And I’m Rob.
Mike [00:27]: And we’re here to share our experiences to help you avoid the same mistakes we’ve made. What’s going on this week, Rob?
Rob [00:30]: Kind of the same old stuff. Just hiring a few more folks. We had two new developers start last week, and I think we have two or three open job recs right now. Doing a little bit of MicroConf prep with yourself and Zander. Kind of finalizing the schedule and some sessions. And, you know, fighting the good fight.
Mike [00:49]: It’s amazing how much the little things for MicroConf eat into your time. I mean, there’s all these little things that you think will take five minutes or something like that and they end up eating through twenty or thirty.
Rob [00:58]: Right. Yeah. There’s been a little bit of evening work and some thought and schedule crafting that’s gone on. But, overall, can’t complain given that we’re basically putting on two conferences back to back. I don’t feel like it’s anywhere near even the same amount of work that we used to put in five years ago on the conference.
Mike [01:16]: Right. It seems like it’s not twice as much work to hold the two conferences back to back either. At least not yet. I mean, we haven’t been onsite for it so that could certainly change things.
Rob [01:23]: Yeah, that’s true. And what’s nice about that is, like we’ve talked about in the past, we opened enough tickets that we just about sold out of both conferences but not quite. And I think that’s exactly where we want to be. I think we’ve sold four or five tickets in the past week across the two conferences, and that’s the ideal pace I feel like. Is that last minute folks who want to come who hear about it late I would really like for them to still be able to buy tickets and we’ve never had that really at any MicroConf in the past. So, it’s been kind of nice to see that.
How about you? What’s going on?
Mike [01:55]: Well, kind of related to MicroConf. I’ve been working on my working on my MicroConf talk a little bit. And outside of that, I’ve obviously been putting time into Bluetick and right now I’m working out some UI and workflow issues related to allowing people to self-onboard just because there’s certain parts of the setup process in onboarding that are a little bit more complicated. So, we’re reworking the UI a little bit to make it easier for them to do that and just kind of give them a wizard to walk them through it and anticipate where they’re going to run into issues. Because we’ve seen enough demos in onboarding sessions where this is obviously a problem and getting it the point where people can do that without our help and assistance is definitely going to be worthwhile.
And then kind of related to that is I’m working on recording some video walkthroughs of different parts of the application to show people how to use it so that I don’t have to walk people through those demos myself. Just based on stuff that I’ve learned that people have asked about and said, “What does this do?” Or, “How does that work?” And looking at places to key those videos in so that it’s obvious that if you need help here’s a little button just click on that and it will walk you through this particular piece.
Rob [02:55]: Yeah, that’s a really good way to go. I think that’s kind of become the blocking and tackling template. For this I know it worked really well for us in the early days of Drip. And it still does. I think the videos I recorded two years ago are still live. Or someone may have re-recorded them because we changed our top nav and we were like they get out of date.
And that’s the one bummer with videos is you have to re-record the whole thing as soon as you change one part of the app. You can’t just edit text or replace a screenshot. But recording a sixty- or ninety-second video that’s really tight can go a really long way for brand new people just getting oriented with a specific feature. And in Drip we actually embedded it right at the point they needed to consume it. They were also in the KB but there were only three or four constructs in the beginning. It was broadcasting campaigns and I don’t remember what else. But right as you got into a broadcast it’s like, “What’s a broadcast?” And then there was a sixty-second video of me talking about it. How to use it, how to set one up. Boom. Done. And we got some good feedback about that early on.
Mike [03:48]: That’s basically the approach that I’m using. It’s like right at the places where they need that information, that’s where the videos are and you’ll just be able to click on a little button that has the video embedded into it and it’ll just pop up over the page or something along those lines. We’re still kind of working that out. But, as you said, the one concern that I have is that there’s still parts of the app where the UI is changing and I know that those pieces are going to get out of date and it’s like, “Do I really need to worry too much about that?” Right now, I’m just going to say heck with it and record them and if they get out of day, they get out of date. And if we need to go back and re-record some of them then we will. Or I will.
Rob [04:23]: Yeah, that’s the way to go. One piece of advice there is I would consider only having the videos easily accessible during the blank slate phase. That’s where there’s zero data on that page and that’s when someone’s just trying to get started. They can watch the video or they can dive right in. Once they have one or two of these things set up, the odds of them needing to watch that video drop dramatically. At that point, you could potentially have a little link out to a KB or something.
I don’t know that you need to go so far as to – for the rest of the time that someone uses the app, you always have some link available for them to drop it in. Because you only need that the first one or two times tops that you’re going to set this up.
Mike [05:04]: That’s an interesting approach. I can certainly embed it on certain pages directly where if the page loads and there’s no data behind it, then show that video. And then otherwise up in the top corner or something like that, have a little help icon that they could click on.
That’s something I have to think about whether or not having that extra button there that’s kind of hidden or out of the way where people can just click on that and say, “Get help for this page,” for example. I wonder how much value that adds.
We found that the blank slate approach has worked really well. We got a lot of positive feedback about it. And then it kind of goes away once you’re past the blank slate which tends to be when you don’t need it anymore. So, that’s one way to do it that we’ve found to be quite good.
Mike [05:52]: Cool. I’ll definitely take a look at that.
Rob [05:54]: So, what are we talking about today?
Mike [05:55]: Well, today’s episode is based on a listener question from Matesh. And there was a conversation that kind of went back and forth so I’ll sort of paraphrase things here. But essentially he was asking about why some early ideas failed, specifically related to us. But I thought that it might useful to listeners for us to address that in a broader sense and talk about why different products fail and why different products succeed. And different ways that you can mitigate that and identify whether or not you’re on the right track or the wrong track.
Rob [06:23]: Sounds good. Let’s dive in.
Mike [06:25]: When you’re looking at the success and failure of different products, I think that there’s two very broad categories that things fall into. And the first one is whether you launched it or not. Clearly, if you never launched something then it’s not going to succeed. And that’s kind of a whole bucket of failures. There’s plenty of hard drives out there that are probably just littered with projects that people have started and then never finished. I think it’s pretty clear that there’s tons of reasons why those things failed. Most of it’s just people didn’t spend the time on it and follow through with it. But I think that we just kind of ignore those and move on to ones where people have launched it but, for whatever reason, it didn’t succeed.
Rob [07:00]: Okay. But before we do that, I have to tell you about at least one of my projects – it was probably circa 2005, 2006 – and I never launched it. But I still think this idea is as bad as it was the day I conceived it.
I always wanted to be able to follow artists and bands and directors and writers. Like I love Aaron Sorkin’s writing. And I wanted to go to one place to paste them all in or select them from a list and then, whenever they release something new, I would hear about it. You would think this would be fairly easy but I found myself keeping this big text document of all these band names and then these writer names and authors. And then I would periodically go through it and past them into Amazon and look and then I’d past them in here and there. And then I was just like I don’t think there’s really a good service for it. I think Bandsintown may do that now but I’m not sure it tells you about CD’s.
But anyways, I went through and I built the dot net and I hooked it up to the Amazon API and I did all this stuff. And then I realize this is an awful idea. This is something that some big venture funded company would do and try to create a big buzz around and raise a bunch of funding and then they’d go out of business and someone would come and pick up the scraps. Although I wish this existed and in a really palatable format.
Mike [08:10]: I think what you’re looking for is indieshuffle.com.
Rob [08:13]: Yeah? Does it do it for all the things I mentioned?
Mike [08:16]: I don’t know. You’d have to probably look at it and figure out whether or not. There’s probably little things that you were looking for that either are there or are not.
Rob [08:24]: Got it. So, this is cool for music?
Mike [08:27]: Yep.
Rob [08:27]: But it doesn’t have any of the other stuff. I follow authors who write fiction and nonfiction. And I follow, like I said, writers and directors so I would need film. Mine was going to be all that because you could, of course, use Amazon to look for those as new products came out. A new book or a new DVD at the time because there wasn’t streaming.
I’d imagine there’s either a service out there doing this now or there’s three different services. One for each genre.
Mike [08:52]: Yeah. Indieshuffle, I believe, is primarily aimed at music only. But there’s probably ones out there that are similar for those other spaces.
Rob [09:00]: Totally.
Mike [09:01]: Interestingly enough, I have an idea that I started back in 2005. I wrote out all the designs for it and it literally became a multibillion dollar business. It was named Lighthouse but the idea was essentially file sharing made easy so that you could just drag stuff into a folder and it would automatically share it on other machines. Sound familiar?
Rob [09:19]: Dropbox.
Mike [09:20]: Yep.
Rob [09:21]: Yeah. Now to be fair there were like 30 Dropbox competitors even when Dropbox came out. So, you could very well have been the 31st. Because obviously, the idea was one thing but Dropbox getting out ahead, raising the $10 million and execution is what took it ahead.
Mike [09:36]: Oh, totally.
Rob [09:36]: But it is fun to know. I almost acquired a business that did exactly – this was a Dropbox competitor – and the guy wanted a crazy multiple. But it was basically that. It had all the apps and all the stuff. It was kind of like a virtual thumb drive is what we were thinking of at the time.
Good thing you never launched that one because without raising a bunch of funding I’m not sure that you could have ever gotten that off the ground to the extent that they did. Because it’s the freemium model that allowed them to really get the traction, right?
Mike [10:00]: Right. It was 2005 when I wrote the design document for it and it was like an almost forty-page design document for it. But I never followed through and actually wrote it. I still wanted to tweak things out and figure out whether it was going to work or not. And at the time I was transitioning over into doing consulting because I’d left my full-time employment at the time. So, I was doing a lot of consulting and traveling and I just didn’t have the time to work on it.
Then fast forward like two or three years to 2008 is kind of when I went back to it. I started working on it and I think I probably wrote like a code for a week or two, and then I stumbled across Dropbox. And I’m like, nope, that’s it.
Rob [10:37]: Let’s say you had tried to build it in 2005. Do you remember how expensive servers were and storage and all that crap? It would have taken you literally millions of dollars to build it to any type of scale that would have paid. It was not a bootstrappable business even if you were ahead of Dropbox. Just purely for the cost of everything.
Mike [10:58]: The market that I was specifically looking to serve was magazines where they need to collect digital materials and files from graphic artists and they need to get those to their office. The problem was that most of those people had to use FTP servers and a graphic artist just does not know how to use FTP. They had problems with it. So, I was trying to make it easy for them to share their files. And there’s a general use case scenario that Dropbox came out and addressed at the consumer market. It’s interesting how that whole thing ended up playing out.
Rob [11:31]: Totally. What do you mean they don’t know how to use FTP? I think your wife takes offense at that.
Mike [11:35]: No. The thing is, she was actually the one who enlightened me to the problem because she was working with all these people who needed to send files to her. And they couldn’t figure it out. She was working at the magazine and they were trying to send her files and they just couldn’t get them or they didn’t’ get them in time. There was a lot of issues with FTP. You send the file and there’s no notifications behind it either. So, obviously, Dropbox has the notifications and stuff built into it.
There were all these ancillary things that went into that in transferring the files and making sure that people knew about them and there were deadlines and stuff like that. But, I don’t know. It’s interesting to look back on that stuff.
Rob [12:11]: For the listener wondering what we’re talking about, Mike’s wife used to be a graphic designer for a magazine. It was obviously a problem within her purview there.
Cool. So, let’s dive in. I totally sidetracked this whole episode so we could talk about these old, crappy ideas. Well actually, your idea was a good idea. Just one that would have taken a different approach.
Mike [12:30]: It kind of leads back to some of the reasons why something doesn’t get off the ground. It does relate to the episode, both of those things do. But I guess to kind of step back and go back on track, there’s a difference between launching and not launching. Once you’re past that, things also break down into a couple of different categories. And the first one is, did you get any paying customers or not? Because there’s a big difference between a product that gets zero customers and gets at least one. And there’s a lot of reasons why something might get no customers. Obviously, the most prevalent one is probably you didn’t do any marketing or you weren’t able to talk to people.
There’s also the quality problem issue. Your product has to be good enough for people to want to pay for it. Has to have the features that they need. Had to be solving a problem for them. And if it’s not doing any of those things then you’re not going to get any customers.
Rob [13:15]: Yep. Isn’t this startup founding 101 these days? Product building. The first step is figuring out what the problem is to be solved. So, there should be some conversations. And this only became popular really around 2007, 2008. Before that we just went off and everybody just built stuff and hoped people would use it. And then Steve Blank really bringing his customer development approach to the forefront. And that was the first time I heard about asking your customers in advance. And it was like, “Whoa, you can do that? What does that even look like?” And then there were several books written for our work group because one of them where Tim Ferriss did the ad words in advance of offering the product for sale. But there were six or seven books that had talked about that before that came out. And that was when it was like this really makes a lot of sense to try to do as much validation as possible up front to ensure that you are in fact solving a problem.
Mike [14:08]: That’s the first bucket of potential failures. The next one is: if you’ve achieved paying customers but the product is still losing money. Essentially you’ve got negative margins. And there’s a bunch of different reasons for products that fall into this category. They could range from your infrastructure or your hosting costs being too high. Your cost of acquisition is too high compared to your lifetime value. That means that your cost to acquire a customer is more than they are worth. It may cost you $50 to acquire a customer but if they’re only going to give you $25 over the course of the lifetime of that customer, it’s really not worth being in that business. You can’t sell at a loss and make it up on volume.
There are other situations where if it’s a product high service, for example, you might be selling something for $100 and then you’re farming out the work, but it costs $150 in labor to deliver whatever that is to the customer. And, again, you’re in the situation where’s you’re trying to deliver something, and you’re just simply not charging enough. And even in those situations, you can’t necessarily just raise prices and expect the problem to be solved. There’s certain types of problems or situations where the customer is simply not going to be willing to pay more money for something. They have this in their head that they can afford “X” and if you go to “X+5” or “+10” they look at that and say it’s not worth it to pay to have that problem solved at that price point.
Rob [15:27]: This is where I would guess if you had actually launched that Dropbox competitor, this is what you would have found if you tried to bootstrap it. You would have had to charge enough that you wouldn’t have been able to get – well, if you’d gone after magazines that’d be fine. That’s a whole other issue. But let’s just say you had gone after the consumer market like Dropbox did, you would have probably wanted to charge $5 a month or whatever. $40 or $50 a year and you wouldn’t have had the organic growth and the big exponential growth curve that Dropbox did have because they were doing that freemium model up front.
So, one thing to think about here is if you do raise a big bucket of money and you decide that you want to grow this thing super-fast and get the volume, it’s a lot more of a riskier bet because you’re not getting your money up front. But that’s how these companies get to the $100 million and eventually the billion dollar valuations.
With that said, I’m doubting – if you’re listening to this – that that’s where you want to go. So, you really do need to pay attention to unit economics. I heard someone at one point say that they wanted to start a competitor to Kissmetrics and Mixpanel. And I told them, “Do you realize they spend” – I forget what the amount was. It was like a quarter of a million dollars. It was more than a quarter of a million bucks a year and this was in the early days. This was before they scaled up. It was a quarter million a year just kind of table stakes just for all the hardware. Or even the EC2 credits. Or whatever it was they were doing because it’s just such a resource intensive business. So, diving into these analytics platforms or something with a lot of queues where you’re sending email – as I know all too well from having worked on Drip all these years – there can be real infrastructure costs. There’s a difference between a crud app like Basecamp or invoicing software or something and switching over to something that really gets a lot of requests per second, 1,000, 2,000, 3,000 request per second. There’s a true marginal cost per customer that you add.
It’s not something you’re going to be able to predict exactly. But it is something to keep in mind and do a sanity check of like, “Is there anything here that’s really going to scale up exponentially in terms of server load or in terms of support costs as I grow this app?”
Mike [17:25]: And sometimes those aren’t very easy or straight forward to calculate. I remember some offhand comment about it was either Kissmetrics or Mixpanel where one of the early versions of the app, they had 25 servers running in order to support nine customers. Which is more than one server per customer. And if you look at the price points that they’re charging you really can’t afford to have two to three servers per customer at the price points that they currently had. It’s just simply not possible. So, if you’re trying to develop a competitor to it, your hosting costs alone are going to kill you. There’s no way that you’re going to be able to make that work.
That said, they did get funding, and they’re able to scale it based on the fact that they’re able to drive those prices down. It’s a starting point. But, again, not everybody’s going to be able to be in a position where they can get that money and invest it to be able to drive those costs down as far as they need to go in order to make the business work long term.
Rob [18:16]: So, you’ve talked about the first step was never launching. The second one was zero customers versus one or more customers. This third one is getting paying customers but realize that it’s losing money. I think we have two others that we want to cover in terms of the ways that products can fail. What’s the next one?
Mike [18:32]: The next one is you have what I would call a mediocre success. It has paying customers but it’s got a marginal profit. And by marginal, I mean it’s almost not worth your time to do. The product is at least break even and it is making money but maybe it’s only making a couple thousand dollars a month. Maybe it’s $2,000 or $3,000 but, again, even if it’s making $3,000, if you’re spending thirty hours on it, is that worth your time? I think that’s an individual question you have to answer but if it’s paying you $10 an hour for your time then it’s probably not. If it’s paying you $50 or $100 or $200 an hour for your time then I would consider that probably more than a mediocre success. But there’s also overhead associated with running more than one product at a time and having each of them be a mid-range success that is simply not meeting your needs full-time. And the context which in it’s going to be harmful.
But, going back to the products that are a mediocre success, there’s problem solution fit. If it’s not a problem that people really need solved or it’s a nonexistent problem, chances are good that you can get some people to pay for it. But you’re not going to get large scale numbers of people. You’re going to get those people who it’s a really painful problem for and they’re willing to pay for it. But that could just be because they don’t know what some of the alternatives are out there or they haven’t done their research. And you can very quickly fall into a situation where people are using your product for something it simply wasn’t designed to do.
Rob [19:54]: Another thing that could be wrong when you have some paying customers but essentially a marginal profit and you’re not growing is you don’t have product market fit. So, you’ve built a product but you’re offering it to the wrong market or audience or there is not market or audience for this. And a related piece of that is market positioning where it might be related to your pricing or how you’ve portrayed it against competition but you really need to dig into why is your product better and for whom. And it might not be differentiated enough against the competitors and new products really need that.
People need to be able when they hit your website to think, “What bucket does this fit it? Is this invoicing software or proposal software or email marketing software?” And if you have just a description that is what the product does, everybody’s trying to figure out what bucket you fit into. As we’ve talked about in the past, creating a new bucket or creating a new product category is very expensive. HubSpot kind of did that and I think they might have said it took them $5 million before they were able to – he said they had to raise millions and millions of dollars before they were able to really define that product category. And I think that it’s a common mistake people make and one that I made with Drip in the early days was not wanting to position this against other competitors. Or just put it into a specific space like this is email marketing software but here’s why it’s better. Or this is marketing automation but here’s why it’s better.
I kind of wanted to be this new unique thing and all the headlines were just so vague and nondescript that people were having a tough time understanding. So as soon as we went with the, “This is marketing automation but it doesn’t suck,” That was the headline for so long. That really put us in a good position because people then realized, “Okay. So, you’re not going to own this entire market but you are going to own this portion of people who hate the other providers that are there.” So, that was a big product positioning fit for us. And I’ve seen other products be able to do that as well.
Mike [21:44]: The other thing that what you just talked about does is that it allows people to mentally identify who your competitors are because if they can’t do that then it’s going to be difficult for them to compare and contrast what you offer versus what some of the other ones offer. And sometimes you want to be able to specifically define who your competitors are and you can use market positioning to do that. But you can also take a particular market and either go upscale with it or down scale with it.
With Drip, for example, it was essentially pitched as Mail Chimp but more advanced. It was not quite advanced to the level of Infusionsoft or Marketo or things like that. It was more for a small business scenario then for a large enterprise or for somebody who’s just working out of their home office. And, obviously, that has changed over time but that was the position that you started in and that served Drip, obviously, very well.
Some other reasons you might be having some mediocre success is that you have poor design, which if your UI is not very good, it can affect some of your adoption rates. If somebody hits your website and they look at the screenshots of the product and it doesn’t look very good, then they are probably less inclined to purchase it. Even if you’ve gotten a base of customers who used it and the reason they used it is because they were experiencing the pain so much that they just had to have a solution. And they didn’t really care what it looked like. But, as you start to expand your customer base, people are going to care. They’re going to start taking those things into account. If you have misspellings in your UI, for example, that’s going to reflect on them. They’re going to say, “If you can’t get even just these basic things right on the surface, if it’s a complicated product in any way, shape or form, what sorts of problems are going to be underneath the covers?” So, you have to keep those types of considerations in mind.
Poor design decisions can lead to essentially a high churn rate which high churn is simply a symptom of something else. It could be support, it could be onboarding, it could be poor design, it could be quality, it could be downtime issues. There’s lots of different things associated with that. But at its core, high churn rates are associated with some other problem. And it could just not be even a technical problem. It could be that you are marketing to the wrong people and those are not the type of people that are going to stick around. It could be a symptom of a market targeting problem.
Rob [23:54]: Right. Back to poor design. You can point to apps that are successful that have poor design, and I will tell you, yeah, they were early. They were the only choice at the time. Or they really did a lot of heavy outbound sales, and the people who they talked to didn’t know any better. So, a lot of the email marketing or marking automation or big sales like sales force CRM stuff, yeah, the UI’s aren’t great. But you’re not them. You didn’t start ten years ago. You’re starting today. And today UI is a huge deal unless you’re in a very tight niche where you’re kind of the only player. So, this is something that you definitely need to pay attention to.
And in regards to churn, you’re right. It is a symptom of something. It’s often a symptom of crummy support or no product market fit or there’s a bunch of reasons that can happen. But all of this stuff is going to keep your grown flat. And that’s exactly a good way to have paying customers but essentially marginal profit assuming you are working on this a lot.
If you think about the micro-businesses I used to run – like DotNetInvoice or beach towels or apprentice line jobs – those had paying customers but they were highly profitable in the sense that the money that came in, I spent almost no time maintaining things. It was really all work done up front, and the money that came in was mostly profit. Maybe it was only a couple grand a month like you said but I wasn’t spending thirty hours a month on it. So, if you cobble a few of those together, you can actually kind of nice little lifestyle making $10,000 a month with a handful of these small apps not investing the time.
But that’s not really what we’re talking about here. We are talking about you having the intent of growing a SaaS app and working on it most of your free time and getting it to ten, twenty or thirty thousand because we’re guessing that, probably if you’re listening to this, that’s the goal that you have.
Mike [25:31]: The last one we’re going to talk about in this particular category is the high cost of acquisition but also a corresponding high lifetime value. Let’s say that your cost of acquisition is $1,500 and your lifetime value is $2,000 but you’re getting $100 a month from each person. Well, it’s going to take you fifteen months to get back the money that you’ve paid to acquire that customer which means that you have to spend a lot of money up front to get a return that is going to put you $500 in the black but it’s not going to start until another fifteen months after you acquire them. And that’s a very difficult position to be in. That’s why some companies go out and they raise funding to be able to start putting money into that funnel to help them figure out how to move that up, how to lower their costs of acquisition. And they’ve proven that it’s a profitable business model. They really just need to make the numbers work.
And if you’re in a position like this, it’s very difficult to do that because it’s going to stunt your growth. It’s going to make it a long slow slog in order to make that into a profitable product which defines this as a mediocre success.
Rob [26:32]: There are a lot of hurdles that you have to get through if you look at this list that we’ve just talked through. Just getting something launched is a pretty big deal. I know that we used to always talk about on the podcast how that’s not the finish line like most people think. That’s maybe the 40% marker and these days, the further things get and the more competitive they get, I think that may be even earlier. It’s so much easier to get to launch today than it was five years ago just given the tools that we have and all the resources and things like Heroku the platforms as a service. I used to have to spend a lot more time doing that stuff even the marketing tools as well. And then just getting zero versus one customer is a big hurdle. And then getting to the point where you’re marginally profitable. I think we’ve seen a lot of folks get there these days. It’s a hard place to be in because it feels like by that time you’ve worked so hard on the app and you’ve spent so much time building and launching and promoting and then you get to the point where it’s making $1,000 a month top line and it’s $500 a month in hosting costs and you’re still spending twenty hours a week developing on it. It can be tough. It can be a long slow ramp of death, if you will.
I think there are a bunch of other potential reasons that an app can fail but once you make it past this point where you have customers and marginal growth, if you can make it past that, those are the apps that we hear about. Those are the apps that we talk about. Those are the folks that do the attendee talks or the main stage talks at MicroConf. Or that you hear interviewed on podcasts. That’s kind of that final hurdle. I shouldn’t say final because, obviously, there’s so much more beyond that. But it is a point where you just feel like you’ve done something that so few people have done. It’s a big bridge to cross to get past that product market fit or get to that point where growth really does start coming easy. And it’s almost magical when that happens and you see that growth curve go up. And you think to yourself, “Oh my goodness. How did we get here?” Suddenly you go from scrambling from customer to customer to the point where 7K MRR growth per month. You look at that and you say, “Yeah, that was an okay month.” Or you can be disappointed with that. It sounds insane when you say that out loud but you do get to the point where that is the norm or less.
I just want to encourage you. If you’re listening to this, it does sound like a long road, but there is hope. There is a point where you get there and it just feels like everything’s hitting on all cylinders. You’re always going to have stress; you’re always going to have the next feature you need to get out or the competitor that’s ripping you off. But there does hit a point where you’re going to feel proud of yourself. You’re going to feel like you’re kicking ass and that’s where you want to get to. That’s the goal.
Mike [29:01]: That sounds like a pretty perfect place to stop for today’s episode.
Rob [29:04]: Thanks again to Matesh for writing in. And if you have a question and you’d be interested in hearing us discuss it on the show and maybe even turn it into an entire episode, call our voicemail number at 888-801-9690. You can email us at email@example.com. Our theme music is an excerpt from ‘We’re Outta Control’ by MoOt. It’s used under creative comments. Subscribe to us in iTunes by searching for “startups” and visit startupsfortherestofus.com for a full transcript of each episode.
Thanks for listening and we’ll see you next time.
In this episode of Startups For The Rest Of Us, Mike interviews Justin Jackson about launching 100 projects in a year. Justin talks about the goals and idea behind his MegaMaker project. He talks about some of the products he has come up with and how he went about marketing those products.
Items mentioned in this episode:
Mike [00:00] In this episode of ‘Startups For the Rest of Us’ I’m going to be talking to Justin Jackson about launching a hundred projects in a year. This is ‘Startups For the Rest of Us,’ episode 296.
Welcome to ‘Startups For the Rest of Us;’ the podcast that helps developers, designers, and entrepreneurs be awesome at building, launching, and growing software products, whether you’ve built your first product or you’re just thinking about it. I’m Mike.
Justin [00:25]: And I’m Justin.
Mike [00:27]: And we’re here to share our experiences to help you avoid making the same mistakes we’ve made. How you doing this week Justin?
Justin [00:32]: Well, like I was saying the kids just got out of school, which just feels hectic. It’s amazing how much we rely on the kids being occupied all day. And so now it’s like they’re out. Now what am I going to do?
Mike [00:43]: That’s actually a really good way to put it, and I’ve never quite phrased it verbally before, but it’s nice that the kids have school to preoccupy them for six or seven hours on most days of the week.
Justin [00:54]: Now there is a theory. I don’t know if this is real; but there’s a theory that schooling, public schooling, really came about because of the Industrial Revolution. Because you couldn’t have parents working all day and then have kids just running around. So I don’t know if this is true or not, but that’s what I’ve heard is that a lot of public education came out of just needing to occupy the kids while mom and dad are in the factory for 12 hours a day.
Mike [01:17]: I would actually guess that it’s probably a direct result, not necessarily of the Industrial Revolution, but of child labor laws that prohibit the kids from working.
Justin [01:25]: See now we’re getting down.
Mike [01:28]: So that’s probably it. But anyway, great to have you on the show. For anyone who is not familiar with Justin, Justin lives in Vernon, BC, which is in British Colombia. Which, to me, I call it Canadia on occasion just because I live so close to the border. I used to live in Buffalo, NY, and I mean literally you could hit a golf ball and hit Canada.
Justin [01:44]: Well there you go. Do you have some Tim Hortons there?
Mike [01:46]: Yes we did have Tim Hortons. So went there on occasion.
Justin [01:49]: So you’re basically like 30 percent Canadian.
Mike [01:52]: I guess. I don’t know if I’d admit to that publicly on a podcast with thousands of listeners. But I did want to have you on the show because – just talk a little bit briefly about your history. And you’ve been the former Product Manager at Sprintly, and in 2015 you kind of struck out on your own to make your own stuff. You’ve been kind of around the block, I’ll say. You’ve got three different podcasts that you’ve run, Product People, Build and Launch, and now you’ve got Mega Maker that you’re working on. And then you’ve also got a bunch of ebooks that you’ve written, there’s Amplification, The Hacker News Handbook, The Product Hunt Handbook, Marketing for Developers; I’m sure that there are several other ebooks, and other podcasts that I’m probably missing in that list. So why don’t you, I guess fill people a little bit more in on some of the highlights for anything that I might have missed.
Justin [2:34]: I got started in the software business in 2008, working for a email service provider in Edmonton. And I kind of started my ground level just answering customer emails and doing customer support, but kept poking my nose in everything. I was interested in design and development and marketing. And eventually I worked my way up to being Product Manager in that company. And it’s actually a good definition of a Product Manager. They’re people that kind of sit in the middle of all those other categories. And then after that I went to work for a startup called Sprintly in Portland. And did that for about 14 months or something like that. And then Sprintly got sold and I had this decision to make. I could go out and find another big consulting client, go out and get a job, or I could stop working and make my own stuff. And I’d been kind of building little side projects on the side up until last November, and decided okay, I’m going to do this. And so I went to my wife and I said, “Hey honey, what do you think about this idea of me not going and working anymore, but just working on a bunch of little things and maybe trying to make a 100 projects in a year, and then documenting it on this podcast called Mega Maker?” And she said, ‘No.” And I was –
Mike [3:58]: So executive preapproval was denied.
Justin [4:00]: Yeah. No approval there. And I was like, “Please.” I was just begging her. And so the deal we struck was I said if I can make a living, if I can keep paying our bills, keep food on the table, et cetera, let me do some exploration here. And the whole idea wasn’t to like maybe go out and start a big startup. The whole idea was I had been working ever since I was 22 up until 35, working full-time for other people. And I just want instead of kind of jumping feet first into starting a company or trying to build something really big, I just wanted to explore a bunch of different things. So my wife has called this kind of like my early mid-life crisis, and it’s actually probably a pretty good description. I just wanted to try out a bunch of stuff and in some ways, to learn new product skills, learn new marketing skills. And also, just to kind of maybe figure myself out a little bit. After working full-time for all those years, let’s try something else out. Let’s learn a little bit about myself.
Mike [5:02]: That’s awesome. So how did you go from the answer of “no” to “maybe let’s see how things go for a little while”? Because it seems like there’s a gap there that you might have glossed over some stuff. Did you trade one of your kidneys or something like that?
Justin [5:14]: Well, obviously it was a conversation and I just said, “Honey, I think I can make this work.” And one of the reasons I felt confident is I’d just released Marketing for Developers and it had done quite well. I think by that point—just doing some math off the top of my head—I mean it’d probably done about $30,000 in sales or something like that. And so I felt like I’ve got this one product that seems to be selling pretty well, and I think that will give us some leeway to go and try some other things out. And my goal, revenue-wise was if I can bring in $10,000 a month just from doing whatever, I think we’ll be okay. And each month it was like an experiment in how am I going to make money this month? And there was a few months where it was scary. Like in May. May was the month where I decided I wanted to work on some software products. And so my buddy Marty and I, we had built a bulk SMS application called Network Effects. And then we said for the show, we wanted to launch two products at once and kind of examine the response to each of them. It’s kind of like split-testing product launch. And so we launched this other software product called Remote Workers, which was an online community and what I call a reverse job board for remote workers. So we were working on both of these, but because I was heads-down working on those I hadn’t been trying to make any money. So I kind of lifted my head and was like, “Whoa. I haven’t made any money this month, what am I going to do?” And I think I just toughed that one out because I knew that I was going to do a big sale in June. I did a deal with the app Sumo. And so I was like, “I think we’ll be okay.” So we just kind of toughed it out through May and then made it to June. To answer your question, every day my wife says, “So when are you going to go get a job?” And I’m like, “I’m not getting a job. This is way too much fun. I’m going to keep going as long as I can.”
Mike [7:08]: I guess what I wanted to drill into a little bit was whenever somebody is starting to kind of go down that entrepreneurial path, as soon as the question or decisions start to come up around, how are you going to make money and are you going to get a quote-unquote “real job,” then most people see that as a stable form of income and the merits of that statement are debatable at best. But most people look at that and say, “We have to have a serious conversation about it.” That’s what I want to drill into this, like what was that conversation like? Because I think that a lot of people listening to this are on that path and you have to have your spouse on board in order to be an entrepreneur. There’s really just no other way to do it. Or you’re divorced. It seems like those are the two paths that people would end up on.
Justin [7:51]: I mean I think one thing that made it easier is that we had kids quite young. We were married when we were 21 and we had our daughter Sadie when we turned 22. And before that, before 22 I had all through college, all through high school, I had run my own little business. I had a video production and Web design business in high school and college. And when we had our daughter we made a decision that I would not do my own business and that I would work full-time until all the kids were in school. And so this year our youngest, we have four kids and our youngest was in grade one, full-time. And so because that transition had happened I said, “Hey, you remember that conversation we had? Well, now all the kids are in school and now I have this opportunity. Sprintly’s just been sold. And I could go do something else. Why don’t I try to do that thing we talked about 15 years ago, and let me try to do my own business again?” And so that was part of the conversation. And the other conversation is I said, “If this doesn’t work out I’ll just go and look for a job or look for another client.” But I said, “I think I could probably go out and find something else if I really needed to.”
Mike [9:03]: And I think that that’s something that can be comforting to the spouse is if you are in a position where you are in demand; they want you to come work for them. And if you ever needed to you could fall back on that and you could go out and get a job in relatively short order. And I think that that’s applicable to probably a lot of the people who are listening to this podcast. And especially if you’re in the tech world, just because there is so much demand for tech talent that if you are talented, if you are publicly visible to a lot of people, then it makes it easier for you to find full-time employment to fall back on if you really needed it.
Justin [9:35]: I mean I think everything’s a risk. I think employment kind of lulls you into sleep in some ways. And not recognizing how risky it is. Employment is just as risky as anything else; that you could get laid off at any time. And at least when you’re running a business you’d know your own financials. You’d kind of know what’s coming down the pipe. But employment, you could just show up one day and be like, “Sorry, you’re gone.” And client work is even kind of worse in some ways. In some ways you kind of what’s coming down the pipe. But other ways, just like, “Man, this could disappear at any moment.” So I think there’s pros and cons to all of them.
Mike [10:10]: Well, sorry for that little side track there, but I thought it was important to drill into that initial conversation because I think a lot of people are going to have to have that conversation early on when they’re starting to build a product. But I wanted to have you on the call today so that we could talk about your Mega Maker project. And I guess, could you summarize very quickly exactly what the Mega Maker project is so that the listeners have an idea?
Justin [10:31]: I had this idea that why don’t I try to build 100 things. And some of these would be small little products, some of these will just be creative things for me to explore on my own. And I’ll document it on this podcast called Mega Maker. So it’s kind of like a lab. It’s like my marketing and products lab. I’m working on all sorts of little things. So as an example, we’ve got this little SMS app, what would it be like to run this as a full-time business and to really feel that? That’s a big part of this whole experiment is to experience things without committing too much. I’m going to try this out, try it on for size, see how it feels. That’s interesting. And then kind of looking at everything. So, for example, one thing I’ve learned over the past just six months is that most of my revenue still comes from things like Marketing for Developers. People really go to me for product marketing advice, product marketing teaching. And the lion’s share of the money I’ve made so far has been there.
Mike [11:37]: So it’s kind of like this gives you the ability to launch a mini product and get a feel for how much traction it gets without committing three month, six months, nine months to a single thing, which may or may not pan out or you may have to do a lot more validation on. I mean if you keep these small enough you can throw something out there, see how it goes, and it’s not just that you can see how it goes but you can see how well it does in relation to the other things that you’re building, which gives you a much clearer picture of how well it could do.
Justin [12:07]: Yes. But the other thing that I’ve been really thinking about, and it’s almost more important to me right now, is we talk a lot about product market fit. I’ve been thinking a lot about market/founder fit and product/founder fit. For example, serving some markets, you don’t really know what it’s going to be like until you actually start doing it. There’s some things I’ve launched where I’m like, okay. As an example, one idea I had was about 70-80 percent of my audience is software developers. What if I tried to bring some other types of creative people into the audience? What if I reached out to artists and musician and artisans? Let’s just see what that’s like. What I discovered is I really liked those people but it’s not really a market I want to serve. So there’s not a fit there. There’s no founder/market fit there. Likewise, there’s product/founder fit. And I think this is a question a lot of people don’t ask themselves, especially before they launch like a SaaS a business; is do you really want to run that kind of product? It’s a lot different running SaaS than it is downloadable software, than it is info products. They’re all very different. They all feel very different. And this has been an opportunity for me to try some of that stuff on. Like what would it be like to run this product every single day? What would it be like to serve this market every single day? And actually the third one that I’ve been thinking about a lot lately, this idea of company/founder fit. And what I mean by that is kind of like company structure. Rob Walling just had this quote I read about how to get above seven figures in SaaS revenue. You really need to have a team. And I’ve been thinking a lot about that, too. Up until now I’ve been just working by myself or partnering up with people. What would it be like to have to hire a team, to pay salaries, to be a leader, to be a confidant for employees, to bear the weight of providing for all these different families?
Mike [14:06]: Because you have to be—like if you hire somebody full-time, you’re essentially responsible not just for their job and their benefits and stuff like that, but in some cases if they’re married and they have kids, you’re responsible for their welfare as well. So it makes it, in my mind it’s much more challenging to run those types of scenarios. And I’ve done it before and I’ve had to let people go where I knew that they had a wife and kids and they didn’t have another job lined up. And it sucks. It’s very difficult to be in that position. And I think it’s something that you have to slowly work your way into. It’s not something that you can just jump into and be able to just day one know exactly what you’re doing and feel confident about it. I mean, working your way up towards it is probably a better solution. I know that there’s obviously the VC funded startups and stuff don’t have that luxury, they just kind of jump in head first. But as a bootstrap company I would hate to be in that position where you have to hire ten people and then half of them don’t work out, or a quarter of them don’t work out.
Justin [15:00]: And these are the things. I think a lot of product people are so desperate to build something that gets product/market fit, and that’s hard. Finding something that—a product that fits with a good market, a market that’s able to pay you, a market that had demand for that thing that you’ve built. I mean, that alone is really hard. But there’s these other vectors, which is like, does this even fit me as a person? A lot of us are kind of running away from something. We’re like we don’t want to work for the man anymore. We don’t want to work for clients anymore. And so we run towards product. But often we run towards product and we end up serving a customer base that we don’t really like, or building a product that we’re not really passionate about, or creating a company that we now have to run. We then become that boss that we really didn’t like.
Mike [15:49]: I have wrote about that a little bit in my book because I met somebody who had a seven figure business and he hated it. He didn’t want any part of it but he was so involved in it that there was no way for him to really get out of it. It was a services business, but at the same time he was so involved on the relationship side of things that it would have been almost impossible for him to sell it. So he kind of had no option. It was kind of like being locked into a job that you just didn’t like.
Justin [16:14]: Exactly. And so this is all the exploration I wanted to do with Mega Maker. So at the beginning, season one, it feels very much like watching a guy have a mid-life crisis. Instead of going out and buying a Lamborghini, I’m making things. And the story that everyone talks about from that season is, I said what would it be like to go to a restaurant and design a menu item for that restaurant and then actually make it and then market it? Go through the whole product development process, not for software, but with something like food. Because I had never done something like that before. And so I convinced this restaurant to let me do a Friday lunch special. It’s a barbeque restaurant. They didn’t have a burrito on the menu and I love burritos. So I said let’s try to make a Mega Maker burrito. There was kind of two goals with it: one was to just experience what is involved in making a food item at a restaurant, and two, how can I apply some of the things I’ve learned doing marketing and sales for software products to marketing this lunch special? And that story, I can’t even remember the other episodes, but that story is still the one that people come up to me at a conference or whatever and say that whole thing was insane. That was just me exploring stuff. Just figuring stuff out. You know when you’re running a tech event, like a conference or something, you need to get people in the seats. That’s the most important thing. And so I was like I’m going to make a list of everyone who is going to come on Friday and order one of these burritos. So I had a spreadsheet where I was calling people, emailing people saying, “are you coming, how many burritos are you going to order?” So I had this running total because I wanted to make sure that we were above 60.
Mike [18:00]: So you were essentially brute forcing your sales. Like a lot of bootstrap software entrepreneurs, they’ll brute force their way to like 20-30-50 customers in the early days. And you almost have to. That’s because you don’t know what traffic channels are going to work for you. So you contact everybody you possibly know in order to get the [crosstalk]
Justin [18:16]: Totally. And the whole time I was also telling the story as it was happening. I was doing clips on Snapchat. I was doing little YouTube videos. Just sharing the whole experience. And then the Friday came and it was like insane. We ended up selling 80 during the lunch hour. The restaurant was just packed out the door, you can’t get a seat. I was in the back actually making burritos. And so I got to experience everything. And it made me realize, one, I never want to do that again. But two, in terms of like product marketing there’s this great clip from that episode where this guy calls me over. I’m recording it and he says, “Do you realize why people came here today?” And I’m like, “I don’t know. They like burritos.” He’s like, “No, man. People are here because of the story. They wanted to come and be a part of the story.” And that kind of marketing is completely applicable to the product world. I think a lot of times people get interested or engaged because of the story and they’re kind of following along and they’re like that’s how they become a customer; is they were just following along with the story. So there were some parallels that were interesting.
Mike [19:28]: Now you’ve mentioned marketing. Obviously that was a one-time event. You got a bunch of people there and, yes, they’re involved in the story. But how do you go about marketing for some of these other projects that you’re launching, because, obviously, if you’re doing 100 of them in a year, that averages out to roughly two per week. So one every two and a half to three days, it doesn’t really give you a heck of a lot of time to do marketing for these. Do you do any follow-on marketing? Do you do advance marketing for some of these different projects that you’re launching? I know that not everyone is aimed at creating revenue or generating revenue for you, but at the same time there’s got to be some base of people that you want to launch it out to, or that you want to get it in front of, because there’s really not much point of creating something if nobody’s going to every look at it or use it.
Justin [20:11]: I was having a conversation with Lars Lofgren. We were just talking about marketing. He and I have known each other for a long time. And so we were just talking about marketing. And he said one of the best things a marketer can do is realize that they’re not going to be good at everything. You’ve really got to play to your strengths. And just hearing him say that, someone I really respect, it almost gave me permission to say, “that’s great, I can really focus on these things that I’m really good at.” And still sharpen the ax as much as I can with things that I’m not super great at. But really double down on the things I’m good at.
Mike [20:45]: And I think that’s important to know what your own limitations are. Not just on the product side of things, because obviously if you don’t know how to use a particular piece of technology you can probably figure it out. But sometimes it’s worth just paying somebody else to do it. But that also translates over onto the marketing side because sometimes it’s better to just pay someone else to do something that you really just don’t like. Which could be successful but you don’t want to do it because you’re just not good at it and you’re not as comfortable with it.
Justin [21:09]: And that’s why in the book, Marketing for Developers, I give so many different channels and so many different techniques because I just want people to be able to choose. When I was doing the customer research for that, a lot of folks would say, “Well, Justin, I’m just not good at writing blog posts.” And so for people to be able to choose and kind of explore different things and then find the one that they’re really good at. That’s where you should invest all your time and money; is in the thing that you’re really good at. And then either hire out those other elements or just don’t focus on them.
Mike [21:41]: So I guess going back to the heart of the question though, how much marketing are you actually doing for each of these individual projects?
Justin [21:47]: It really depends. I mean some of these are just things I need to get out of my system. So Network Effects, we launched on BetaList. We wanted to get a ten person paid beta in both. So ten person paid beta in Network Effects, and ten person paid beta in remote workers. We launched on BetaList for that, got enough people in and now we’re just like basically getting their feedback. What are you using it for? What do you really like about it? Are you willing to keep paying? It’s $9 for Network Effects and then the plans are similar to MailChimp or whatever.
Mike [22:20]: Is that like an onboarding fee for that?
Justin [22:21]: Yeah, it’s basically because with SMS you have to pay for the number. Unless you get a custom number it’s not very useful. And so we wanted to get people in, getting a custom number. And so mostly it’s just to help pay for some of our costs. But it also is just a great way to figure out who’s really serious about this. And, like I said, over ten people paid for that beta. And then the people that stuck around, I think there’s like, of that group, there’s about three that have stuck around. We’re like really working with them to figure out what do you guys need? What are you using this for? Some of them are using it like every day or every week. And we’re like we’ve got to focus on these folks. Who are you, what are you doing this, how are you using this?
Mike [23:03]: So like customer development –
Justin [23:03]: Customer development.
Mike [23:04]: One-on-one [crosstalk]
Justin [23:05]: Exactly. Exactly. And when we’re ready to really kind of turn things on, in my mind, it’s like you do a BetaList launch and then you get enough people to come and try it out. Really figure out who you’re focusing on, and then launch to the waiting list. Again, kind of figure out, why are people signing up? That’s the big question. Why are people signing up? And once you can figure that out, then after that I do a Product Hunt launch, and then it’s looking into other strategies like ads, SCO, et cetera.
Mike [23:35]: So you keep saying ‘we’ a lot. And maybe that just applies to this particular scenario. But are you working on a lot of these by yourself, or do you have partners for some of them, teammates, people that are working with you, either part-time or full-time on a regular basis, or is it just more one-off projects?
Justin [23:49]: It’s me for almost all of them except the bigger projects I’ve partnered up. And so my buddy Marty Dill, who’s an awesome developer here in Vernon. So when the idea for Mega Maker came around I said, “Hey Marty, you want to team up and build a few things?” I’ll find it for you, but I have this agreement that I sign with people I want to team up with. And basically it says we’re going to work on this project for six months, and if we decide to turn it into a business we both get like 50 percent ownership, and then we move forward from there. If this doesn’t turn into a business within six months, then we just let everything fold and we move on. I mean, it’s been audited by a lawyer and everything else. It’s just a way of saying, okay, this is the purpose of right now, we’re just testing out an idea. We’re building the initial thing together, and then when it comes to turning this into a company, we’ll both get equal shares.
Mike [24:43]: It kind of forces the conversation up front, I guess, too.
Justin [24:46]: Yeah. I started signing these because I was doing even small little partnerships, like I built a WordPress plugin with Carl Alexander, and we’re good friends but I had seen enough partnerships go real bad that I thought, “let’s start signing something upfront from day one.” And it gives it such a great framework because it’s like, if this doesn’t work out in six months, we just move on. If this does work out and we want to turn this into a business, then we create the corporation, we both get 50 percent of the shares, and then we treat it seriously. We treat it like a company. And there’s a few other kind of conditions in there as well. But I found it a really great way to get started on projects knowing that we’re both kind of protected and we can both kind of trust each other for that period. And then it kind of gives us a way of moving forward if we decide to take it from there.
Mike [25:35]: So one of the other things that comes to mind is while you’re going through and launching a lot of these different projects, one thing that—I’ve experienced this myself, but I’ve seen it happen to other people, is that when you start on something, that’s kind of the high point. When you’re embarking on a new endeavor and everything’s new and everything’s exciting, but then three months, six months down the road you start to get tired, you lose focus, you lose your motivation, I’ll say, to continue. I would imagine that for a lot of these projects that doesn’t happen on an individual project basis because the timeline for them is so short. But throughout the process of this, you’re doing a 100 of them in a year. Has that come into play for the project as a whole, or you really have low points for individual projects?
Justin [26:18]: Totally. Here’s the stage I’m at right now. So if we look at the timeline, it starts off and I’m just exploring everything. Every idea that pops into my head I put it on this list. You can see the list at Megamaker.co/list. It’s just a Google Doc. And anything that pops into my head I’m like, “I’m going to do that.” And I put it on the list. And it’s exciting that I’m exploring all of these things, I’m trying all of these things, I’m starting; and starting’s way easier than continuing, right?
Mike [26:44]: Or finishing.
Justin [26:44]: Or finishing. And so that was the beginning. And some of these are bigger things that I really wanted to explore. Like for example, going after a new market was interesting to me. That’s something I really wanted to explore. So even especially like physical makers. For a long time the term maker just applied to people that made handmade furniture and art and sculpture. Lately, digital makers, people that make apps and software have taken that term as well. But for a long time it was just physical makers. And I thought I wonder if they could be my audience, too? And what I’ve realized is, do I really want to go out and interview people that are making their own coffee tables or running their own Etsy shops? At the beginning I thought that would be exciting to me. But now I’m realizing that, no, that’s not going to be exciting to me. And so the point I’m at right now is I’m like, okay, at the beginning Mega Maker was about everything, and my life was about just exploring everything. Now, we’re six months in, it’s time to start focusing. It’s time to start closing down some projects, stopping some things and simplifying. And so I’m still planning on making 100 things through this year, but the show, Mega Maker, is going to be a lot more about products and marketing, software, digital products, similar things to what I’ve done before. Because I’m realizing I went out and I explored a bunch of stuff, but I’m coming now, back to one, the things that I feel like I’m good at, two, the things that are making money. And I guess those are the big things. Am I good at it and is it making money? Do I really like the people I’m serving? Truthfully, I was trying to bring these other customers into my world, but truthfully most of the people that listen to Mega Maker are my same audience. Mostly software developers, designers, product people, entrepreneurs. And so I’m going to start doubling down on those, stopping some of these projects that didn’t feel like a good fit.
Mike [28:40]: So did you find it difficult to complete some of those projects, or was it more of an after the fact that you decided this isn’t something that I really should go after because of the results of it? Was it more because of how you felt early on in going after it? Because I think with the list that you’ve got going, you can look through that and kind of pick and choose what it is that you work on. So chances are good you’ll probably be excited about it at the time. But it sounds to me, like throughout the process of this, you’re also kind of dialing things back and you’re trying to figure out what it is that you want to work on moving forward as well.
Justin [29:14]: Yeah, I mean, it was a bunch of things. One thing I realized is at the beginning I was just like a kid in a candy shop. And I had freedom for the first time in my life. I wasn’t working full-time. I’d always had side projects but now I could give all my time to these things. And I just started way too many things at once. So I’ve gone back to just like working on one thing at a time. Right now I’m working on a new book called Jolt. And it’s 20 surprising marketing tactics, things that most people don’t talk about. It’s going to be really good. It’s going to be exactly for that group of people that I’ve already connected with. So right now I’m trying to not focus on other things and just work on Jolt. Like every day, try to get some writing in. Every day try to finish another chapter. And I’m hoping to launch it July 15. And when that’s done I’ll focus on the next thing. So one thing at a time. And there were some things I just didn’t want to finish. And I think that’s okay. Especially if you start a software project and you’re like, “Man, this is not a good fit for me.” Carl and I just had this conversation because we’ve been maintaining this plug-in and it’s still selling pretty good, but I noticed like he was always the one to answer customer support emails first and I just was never getting to them. And part of it was I just wasn’t excited about it anymore. It just wasn’t a good fit for me. And I just said, “You know what, Carl, you just take this 100 percent. I’m okay with removing this from my plate.”
Mike [30:42]: There’s a certain amount of—I guess it goes into the feelings of procrastination for something, around the fact that you just simply don’t want to do it and you’re not interested in it. Because you haven’t prioritized it. So it doesn’t mean as much to you or you are dreading doing it. I think you said it much earlier in the episode, something about how a lot of times entrepreneurs are running away from something and that brought you to the idea that make sure that what you’re running towards is also something that you want. It’s not something else that you’re going to what to run away from.
Justin [31:11]: Exactly. And because of that we have to be willing to quit some projects. We have to be willing to either let them die or give them away, or sell them, or something. And I think that’s the piece that most of us struggle with.
Mike [31:27]: Yeah. Walking away from that stuff is hard though.
Justin [31:30]: Walking away from it. For example, this next phase of Mega Maker, I have an online community for Mega Maker and I know that this next phase is going to tick some people off. Some people are going to be like, “What? This isn’t about the thing you said it was going to be about in the beginning.” And I’m like, “Well, I have to change this. I have to keep narrowing this down to something that’s going to work.” And so having to upset people is really hard. Like say, I’m sorry, but I’m going to be changing the product, or I could be changing the focus or we’re going to move this way.
Mike [32:02]: Well, I think that’s also one of the traps that people fall into when they are launching a product. Because if you never actually launch it then you never have to worry about disappointing people.
Justin [32:11]: Exactly. The other thing I’ve learned is you get really good at launching and getting over those fears the more you launch. And so part of my message from the beginning, both with Build and Launch, and now this is kind of like version 2.0 of what I was doing with Build and Launch, the message from the beginning is, start small and start now. If you’ve never launched anything, don’t go out and try to launch the next HubSpot. Launch something super, super tiny, and then get that done. Get it done in a week and then launch a two week project, and then launch a three week project. And the more you do that the better you get at getting over that sense of dread, that sense of fear. And you just learn so much each time. And so the dread that I used to have from launching things, I still get nervous, like before this Jolt launches I’m going to be feeling the exact same thing everyone else is; like is anyone going to buy this, did I do the right things, am I targeting this the right way? But I don’t feel the same kind of anxiety as I used to. It’s a lot easier the more that you do it.
Mike [33:13]: That’s very much, I guess, it aligns very well with what Rob Walling came up with, which was the stair step approach. Which you can kind of apply to this, where his was more about the types of products that you’re building. But this is also about becoming more comfortable over time with doing the same thing, launching things over and over.
Justin [33:30]: I think the one thing that I really want to impress on people is that there’s no one path to success. And I think a lot of folks are trying to follow other people’s paths to success. And one of the things that I wanted to explore was this idea of you know what, I’m going to go and just try a bunch of different things and figure out what’s the right fit for me? And I think anybody can do that. You don’t have to make 100 things. But be willing to kind of try things out, look at your strengths and evaluate whether it’s really a good fit for where you want to be. Especially make sure that you’re not running into the same thing that you’re running away from.
Mike [34:14]: And I think that that’s probably a really fantastic note to leave off on. So Justin, tell the listeners where they can find you and if they want to follow on the Mega Maker story or if they just want to sign up for your email list or follow you on Twitter, et cetera, where can they find you?
Justin [34:27]: I’m right at Justinjackson.ca. On Twitter and Snapchat, I’m the letter M, the letter I, Justin. That’s M-I Justin. And Mega Maker is megamaker.co.
Mike [34:41]: And we’ll link all of those up in the show notes for everybody. Well, Justin, I just wanted to say thank you very much for coming on. I hope that this was educational for the listeners. And I really do appreciate you driving home that point at the end there about finding what is right for you versus what everybody else is doing. I think that’s a very, very powerful piece.
Justin [34:56]: Beauty, Mike. Yeah, it’s been a pleasure, man.
Mike [34:58]: I think that about wraps us up for the day. If you have a question for us you can call it into our voicemail number at 1-888-801-9690. Or you can email it to us at firstname.lastname@example.org. Our theme music is an excerpt from “We’re Outta Control,” by MoOt, used under Creative Commons. Subscribe to us in iTunes by searching for ‘startups,’ and visit startupsfortherestofus.com for a full transcript of each episode. Thanks for listening, and we’ll see you next time.