Startups For the Rest of Us

Rob Walling:
I remember being stressed in the early days, early, early days of Drip, that we aren’t moving fast enough, right? But I knew Derek was a baller developer, but I knew he also wrote really maintainable, high quality, scalable code. And so if it took an extra few days or an extra few weeks on a larger project to ship something, I was willing to live with that because I wanted long-term to have a code base in a company that would scale. Unlike some companies that we see where you get this non-technical founder who hires a Dev or has kind of a minority technical co-founder, and they drive them and push them to write code faster and faster and faster. And the code is, and then they get to a million, 3 million, 5 million in ARR and they stop. They lock up. You can’t build features because nothing is maintainable. You can’t add new things because you break old things. There’s no unit tests, there’s just low quality code. 

Welcome to another episode of Startups for the Rest of Us, I’m Rob Walling, and today I answer listener questions. Some text questions from all the way back in January of this year, so it is at 10 months and I sprinkle in some video questions as well. Before we dive into that, we are running the next edition of the State of Independent SaaS survey and report. Through MicroConf we’ve run the survey a couple of times and then we decided to take a last year off because the information coming through wasn’t changing. The survey is about 40 questions. It takes less than 10 minutes to complete if you have your metrics handy. And then we take that data from what usually winds up being between 600 and 1,000 independent SaaS companies. These are bootstrapped and mostly bootstrapped SaaS companies, and we compile a report with all the key findings and helpful industry benchmarks that you don’t get anywhere else. 

The survey closes soon. We could really use your input. All the data is kept anonymous and every survey response we get makes the report that much better. Head to stateofindiesaas.com to complete the survey, and we’re going to enter everyone who completes a survey into a drawing for a free ticket to MicroConf US 2024 in Atlanta. That’s more than a $1,000 value. I know it’s a lot for me to ask you for 10 minutes out of your busy day, but it really would go a long way towards making this year’s report the best yet. We are mixing it up this year asking different questions and pulling out different findings than you’ve seen in the past. So even if you’ve filled out a prior survey, it’d be amazing if you could head to stateofindiesaas.com and complete it. 

Before we dive into that. Tickets for MicroConf Local in Austin, November 14th of this year are on sale and they are going fast. If you are a Bootstrap SaaS founder in the Austin area, you don’t want to miss out. The location is the WP Engine HQ and the guest of honor is Bernard Wang, the co-founder of Clear Scope. We’re also going to have founder by founder, which is an amazing source of networking and building new relationships. You can head to MicroConf.com/locals to get your ticket today. Tickets are only $50, so if you’re in the area, it is 100% worth your time to check out this event. Our very own Tracy Osborne, whom you’ve heard on the show, will be MCing the event and doing a fireside chat with Bernard. It’s just a couple hours in the afternoon of November 14th from 3:00 – 6:00 PM. With some conversation, some meeting of other founders in your area, and a nice happy hour at the WP engine headquarters. Microcomp.com/locals to grab your ticket. 

And one more thing, we’ve recently reopened the doors for our online community, MicroConf Connect. MicroConf Connect is our virtual hallway track. It’s a vibrant community of SaaS founders helping each other and discussing wins, challenges and frankly how to grow faster. A couple months ago we paused new signups to improve the platform based on your requests. With MicroConf Connect 2.0, we’re rolling out three membership tiers packed with new perks like weekly coworking, exclusive discounts, a searchable content library and more. Whether you’ve been a member of Connect or not, you really should check it out MicroConfconnect.com. 

And with that, let’s dive into my first listener question. The person who wrote in asked to be kept anonymous and he and I, it looks like have a long email chain starting back in 2020. But in this email, which came in January of 2023, so about 10 months ago, he says, “Rob, I like to imagine if I had a podcast that reached thousands upon thousands of entrepreneurs, I’d want to know if I was impacting them. While I’m quite certain you already know this, we’ve been exchanging a couple emails every year for the last three-ish years, and whenever I have a question I want to send to the pod, I like giving you an update. Last we spoke, I had launched a new product with zero MRR that’s now $5,200 of MRR and my original product is at $3,000 of MRR. This doesn’t include one time sales. With all of this, I crossed more than a quarter million dollars in revenue for 2022”. 

So that’s a great update. That’s why I want to keep him anonymous is because he’s giving me real revenue numbers. But it’s so cool to hear about listeners growing their business and using the tactics and the motivation that come from this podcast to do it. So now let’s dive into his question. “My question for you is, with the economy starting to tighten up, I feel myself not only tightening up too, but wanting to get as much cash as I possibly can. What I mean is that five years ago making $300,000 seems so out of touch, but now that I’m here, I want more and I feel bad for it”. This is Rob jumping in. This is called hedonic adaptation and it’s that we adapt to the amazing luxuries that we earn over our lives and those just become necessities at a certain point. Back to the email, “in my head, I’m blaming the economy because I think I might need the money, but it also just feels like greed as a one man show, $250,000 to $300,000 a year is more than I need, but as I make more money, I want more things. Maybe there’s nothing wrong with that, but it feels wrong. Have you gone through something similar? When is it enough? Thanks, Rob, from someone that has followed the stair step approach. It’s been a long but very rewarding journey”. 

Yet another person who’s embraced the stair-step approach to what amounts to pretty amazing success. So this is an interesting question and obviously a philosophical one. What’s interesting is that at a certain point around 2009 or ’10, so it was a long time ago, that’s when I was making about $120 to $150,000 a year and I was working like 10 hours a week. And enough was enough. I didn’t feel like I needed more money because it paid our bills, it made the house payment, and I loved the relaxed pace of life that I could maintain. And then we had our second son. I was able to hang out with him hours and hours a week and we would walk around town or I would walk around town with him strapped in a baby Bjorn and really just enjoyed that time. For me eventually I got bored and wanted to start something bigger, and that’s when I bought HitTail. But it was also, there was an incredible 18 months where I launched the Micropreneur Academy, which is kind of a precursor to MicroConf Connect. 

I wrote, Start Small, Stay Small. Started Startups for the Rest of Us, and we started MicroConf. All four of those things happened within 18 months. So it was an incredibly fruitful period in my career, and the reason I was able to do that is because I wasn’t working full-time anymore and all of a sudden I had all this time each week to just tool around and be creative and launch things. So for me, the motivation to up my entrepreneurial game or do the next thing wasn’t about money. It was about ambition and boredom and challenge and learning and creativity. I wanted to do something new that really challenged me. Now, at the same time, my wife and I had a couple conversations where I asked her specifically, I said, “what would we do with more money?” And I think I talked about this in the SaaS playbook or I’ve talked about it on this show before, but she sat down and was like, “if we had an extra couple thousand dollars a month, we would get an apartment on the coast”. 

And not only would that change our quality of life, because we didn’t love living in Fresno, California. It’s not necessarily our soulmate city, but living on the coast was something that we wanted to do. And so just having more money gives you more options basically. And she said, “we could be generous with that apartment and we could be more generous with our money and we could go see family more”. And she came up with all these things that weren’t just luxuries and they weren’t frivolous. They were things that really made sense. And suddenly I was like, “you know what? I don’t need to be a millionaire, but if I made another $1,000, $2000, $3,000 a month, I became motivated that we could do good with that money. And whether that good meant improving our own lives and the quality of those and enjoying those days more, being able to spend more time with your kids or sometimes maybe it’s less time with your kids and hiring someone to be with them so you can stay sane or whether it’s to help other people to give back however you see it. 

Money did become a motivator for me. But not to my detriment, it was actually a positive thing. And that was where I bought hitTail, I grew it and by the time I sold it all the revenue I made from HitTail as well as the sale price was a million dollars. And I had never, you’ve heard my story, a construction worker whose dad was an electrician. I just never encountered that type of money, and that was a shift in my life where I realized, “oh, money does make things easier and money gives you options”. Money gives you options to where if bad things happen, if your car gets hit-and-run, if your car breaks down, if a landlord screws you and keeps your security deposit, if someone steals something from you, any of these losses, all of which I’ve encountered, used to be a huge deal. Catastrophic, right? 

I don’t have these thousands of dollars to repair my car. Having more money made me more relaxed in life. And so that’s the way I think about it these days. And I actually gave a MicroConf talk called 11 Years to Overnight Success and it’s on YouTube and in it I talk about how I was seeking freedom through entrepreneurship. That’s really what I wanted was to own all of my time. And once I achieved freedom, I realized how tenuous it was because I often say I was the original indie hacker. I had nine different websites, applications, eBooks, and each of them made between $1,000 and $5,000 a month. But at any given time, some of them would get smacked by Google and I would lose interest in one or it would just, but bad things would happen. A competitor would come and suddenly I didn’t rank for the terms I needed to rank for and it made me realize that my freedom was tenuous and I had this nightmare of having to go back to consulting and salaried work and I really didn’t want to do it. 

So for me, then I said, “all right, I want to make a little more money, but I really want to lock this in”. And so I built HitTail. It was doing 20 to, it was about $30,000 a month actually at its peak, but then it had major platformers because it relied on Google and it would just get beat up about every year because it was pulling from an undocumented API. I just felt like at any given time, the rug could be pulled out from under me. And that was a huge source of income and revenue and again, I thought, I don’t want to have to go back to consulting. So that’s why when Drip started taking off, I was like, “this is amazing. I’m making more money than I ever could have imagined”, but I still felt like the rug could be pulled out. 

There was still platform risk with sending a lot of emails when our IPs got banned and we had customers threatening to leave. I remember thinking at some point, I do want enough money in the bank that it just doesn’t matter. And some people call it fuck you money, I call it sunset money. It’s enough money to be able to just ride off into the sunset. And that at a certain point became the goal as we started talking about selling Drip. So all that said, that’s how I think about money and the moment that the drip sale happened and the money went into the bank account, I do remember a feeling of existential contentment in a way that wasn’t about, ‘oh my God, I’m going to go buy Lamborghini. I’m going to buy a huge house’. It was, “wow, we never have to work again”. And that was quite a realization. And it’s a calm, a deep, deep inner calm that has stayed with me since then, and that was seven years ago now. 

And so I’ll be honest, that’s how I think about money. I don’t think these days I need more, more, more. I do realize that while we are obviously well off, I see friends of mine, I have friends of mine who fly private. I have friends of mine who fly first class everywhere they go. I have friends of mine who spend a lot of money on things that I think would be foolish for sharing how to spend money on at our level of affluence. So I do sometimes noodle on, I don’t need those things, but I do see the advantages of continuing to grow our net worth. If for no other reason, then to be able to ensure the future of our kids and to be generous. We’re pretty generous people in general and we give away a lot in terms of time and money. So that’s how I think about it. 

So I think some people would say, yes, your desire for money, coming back to that person who emailed, that your desire for money is wrong. I don’t necessarily agree with that. I think if your drive for money causes you to mistreat other human beings or to ignore your family or to burn your relationships, I think you’re making a very bad choice. But if you’re not doing that and if you have a healthy desire for something, each of us is motivated by different things. In fact, Sherry did a really good talk at MicroConf Europe about micro and macro motivations, and she and I had a long conversation and came up with, I think it was seven different archetypes, motivational archetypes. And for example, one of them was a list checker who likes to have a list and check things off. And then there was the time traveler who lives in the future, and that’s more of what I do. 

Then there was, I forget what this one was, but it was like the moneymaker. It was someone who’s motivated by money. Then there was the people person, which is they start companies because they love people and building the team and building the company serves that need in them. So I think you might want to give some thought to that. Is this a healthy motivation? I don’t think wanting to make more money, if you were doing it from a place of challenge and motivation and you do feel like you’ll put that money to good use or invest in the stock market and be more generous or not, you buy something with it. If it’s a healthy motivation, I have a tough time telling someone that they’re “wrong” to desire this. If you find it being unhealthy though, right? If it’s really grinding on you, if it’s really stressing you out, if it’s burning relationships, if you find that you’re making bad decisions because of it, that’s a problem. 

And that’s where personally I would tell you what I would do if I had those feelings and those thoughts, I would talk to a therapist or a friend or an advisor or whatever. But for me, I’ve had different therapists over the years and that’s something that I would dig into. Therapy is just a conversation, right? You’re just talking through with someone who knows how humans work and has some thoughts and ideas about how you can get better at thinking. And so I would be working through that with an unbiased third party in essence. So thanks for that question. Frankly, it was a longer answer than I thought I would have, but it turns out when you think about money and motivation, there’s a lot more to it than you might expect. Next question is sales funnel focused and it is a video question.  

Speaker 2:
Hi Rob. This is Zalia from France. I read in your playbook that most of the time in your sales funnel you put the fact to ask the email of a potential customer before actually performing a demo, and I was wondering if there is a specific reason for that. Because in my case, I was trying to lead first my potential customer or people interested to a YouTube video in which I present my product and I also performing a demo and only in the comment section of this video to put a link in which potential and interested people can send me their email. So what do you think about this? Is it a fine way to do or is there a reason to do another way? Thanks a lot.  

Rob Walling:
Yeah, so this is a good question. So there’s a couple schools of thought here, right? In my book, what I talked about was if someone comes along to request a demo, I want to route them to the appropriate demo based on how much they’re going to be able to pay me or how much they will be paying me. I’m not going to do a demo for someone paying me $49 a month unless it’s really early on in the app, and I’m trying to learn. If someone is going to pay me, let’s say $250 or $500 a month, and I’m willing to do a one call close at that point. And so that’s what I was talking about in the SaaS playbook where someone enters how many email subscribers they had, because this was for Drip, and that would instantly tell me how much that they were likely to pay me if they migrated to Drip. 

And if they were going to pay me a lot of money, then they went straight to our Calendly, which these days would be a SavvyCal link and they could get on our calendar for a demo. But if they were only going to pay us $49 or $99 a month, they were instantly routed to a video demo. We did not gate that with an email form. We didn’t force someone to give us their email address in order to watch the video demo. And I will say, you mentioned putting it on YouTube. I hate YouTube for this purpose. I love YouTube for marketing. I hate YouTube for internal company stuff like this because YouTube, the interface is so cluttered. There’s all these suggested videos, there’s distractions and there’s ads. So I would look at a platform like Vimeo, which is inexpensive. Or Wistia, which is designed for this type of thing, but it’s more expensive. Or any, I mean, there’s Sprout video, there’s a bunch of platforms like this that allow you to self-host and not have to deal with the crappy interface of YouTube. 

That was a side comment. But in a perfect world, yes, you would absolutely get the email address of prospects before a demo, during a demo because then you can stay in touch with them. The idea is once someone books a demo, you should have their email because they get a calendar invite. Before they watch a video demo, it’s kind of up to you. I never wanted to put friction in front of watching a sales demo, essentially a 9-minute or a 10-minute commercial for our product. I kind of wanted whoever wanted to watch that to watch it, and we would embed the video demo on the page and then we had calls to action on that page to sign up for a trial. Your approach of putting them in a YouTube video and then in the comments section to put a link where people can send you their email sounds convoluted. 

I’ve never heard of anyone doing it. It sounds like kind of a lot to ask someone to do. I would either hack together a quick page, whether it’s in your CMS or your marketing website or whatever, and just embed a video and then you can have an opt-in form there, or you can have a signup for a trial. Whatever your call to action is for the video demo, that’s what I’d be looking to guide them to as a next step. So thanks for the question, Xavier. I hope that was helpful. 

The next question is from Tamon and they ask, “Hey Rob, I’m writing to ask you a question that I think you might have insight into. I’ve co-founded a company with my friend. We’re both developers and we’ve built paid apps for Slack. We’ve got some early traction, but we can’t seem to get past $4,000 MRR. We’ve tried many marketing things, but none really worked. After four years”. Yeah, it’s a long time. “We kind of want to give up. We know how to build products, we don’t know how to sell them. Do you think it is in any way possible to outsource marketing / sales? Everyone’s saying development can be outsourced”, which it can be “and that you don’t need to know how to code to build a startup, but does it work the other way too? I’m glad to hear your thoughts”. So kind of, not really in this early stage would’ve a very, very difficult time advising you to outsource marketing sales. Founders need to learn marketing or sales depending on if their tool is one that’s going to be sold via marketing or via sales almost without exception. In fact, when I look at the fastest growing companies in TinySeed, if I were to take out of 131 investments and we’re about to do another, I don’t know 20 or 25, so I have to update my numbers, it’ll be north of 150 soon. 

But all that said, if I were to take the top 10 say fastest growing TinySeed companies, without exception all 10 of those, the founders either head up the marketing or sales or they learned enough to get them to the point where they could hire someone really good and they had one or two or three proven marketing approaches by that time that were working reasonably well. Such that a new hire didn’t have to do that founder level thinking of which marketing purchase should we try. And if nothing’s working now, how do you expect to hire someone to figure that out when they’re not a founder? I really don’t think this is a viable option in most cases. In all honesty, what you’ve built sounds like an amazing step one business, stair step method. You built an app on a platform and it probably gets all of its traffic from one source, which is the Slack app store if I were to guess, and you just can’t get your collection past $4,000. 

That sounds almost exactly like what I did with DotNetInvoice back in the day. It sounds very similar to when I see people doing it with Shopify apps and Heroku apps, unless some people make it past it, but at a certain point you naturally plateau. And then adding more marketing to this kind of app, which is usually pretty low-priced, my guess is these Slack apps you’re charging $10, $20, $30 a month, and at that low price point, you don’t have any budget to do any marketing approaches that work. I mean, you can do SEO and content and affiliate marketing. There’s a handful that are cheap enough and I talk about them in the SaaS playbook, which ones are cheap enough that you can do at these very low price points. But it’s like four approaches, five approaches tops out of 20. 

So when your average contract value is this low or average monthly revenue per customers is this low, you don’t have a ton of options to work with. So what I would do is I would either look to just sell these and get the cash and move on to bigger and better things, or I would keep building or acquiring more of these until I had bought out all of my time, this is step two of the stair step approach, and get it to $6,000, $8,000, $10,000 a month MRR. Then I quit my day job. Now I have all my time to myself and I’m able to then build what I want. And for me, the next step of course is standalone SaaS. That may or may not be the direction you want to head. But yeah, after four years wanting to give up, I understand that I would feel similar. 

I will say that you’ve built an asset, I don’t know how many apps are involved and how complicated it is, but let’s just say for the sake of argument, you’ve built one Slack app to $4,000 MRR. So on an annual basis, that’s $48,000 MRR, and let’s just say for easy math that you have $8,000 a year in expenses. So your seller discretionary earnings or SDE, which is kind of like net profit is $40,000. You should be able to sell that for four to five times so 140 to $200,000, maybe six times 240,000. The issue with six times I think is that you have platform risk because you are on Slack. But man, you’re so small, platform risk should be less of an issue. But you get the idea, I’m just ball parking here, don’t take these numbers for gospel. But if you talk to a quiet light brokerage or [inaudible 00:23:28] International or acquire.com, one of these either brokers or marketplaces, you can get a decent amount of money for it. And that is a luxury we have these days is that SaaS multiples are good enough that it makes even singles, base hits like this, potentially worthwhile. So thanks for that question Tamon. May not be the answer that you wanted to hear about not being able to outsource marketing, but those are my honest thoughts. My next question is about how do I know how good my technical co-founder is?  

Speaker 3:
Hey Rob, first of all, I want to say thank you. I absolutely love the podcast and it’s been so helpful on my entrepreneurial journey. So please, please keep it up. Here’s my question. I’m asking it partially because I’m looking for an answer, but also because I think it would just be interesting to see your response and I think it would be helpful to other podcast listeners. So my question is how as a non-technical co-founder do you recommend evaluating the performance of your technical co-founder and understanding what good looks like? I’m developing a SaaS app and I have a technical co-founder who seems really good and I definitely trust him and he’s accomplished in his career, but I just find myself as a inpatient, non-technical co-founder, always trying to get it done faster and not knowing what good looks like and what is reasonable to ask for. So I’m wondering if this problem resonates and if you’ve seen it before, and if you have any hyper tactical or specific insights or ways that you would recommend evaluating the performance and understanding really what good looks like. Yeah, that is my question. I am looking forward to your response. Please keep up the great work. I love the podcast and will keep sharing it with all my entrepreneurial friends. Have a good one.  

Rob Walling:
I think about this on a few levels. As someone writing the code for your product, there’s speed of shipping code. Then of course there’s code quality and the stability and scalability of that code, the ability to modify it in the future. And then there are the soft skills. The interpersonal communication, does he hit deadlines that he says he’s going to? Does he communicate those properly and all that. Soft skills, I’m going to leave it to you. You guys are in communication. I’m going to assume that you can evaluate those. Speed is tricky because you might say, “oh, we’re moving slowly”, but in fact he’s building something that’s very difficult. We are building it very well, and so the only way I know to evaluate speed is to have another person look at it and estimate it of this is the code base or we’re writing in this language with these frameworks and this is the feature we’re trying to build and have someone weigh in on, oh, that should be a week’s worth of effort or that should be a month. 

And it doesn’t have to be exact. Someone’s not going to tell you, “oh, it’s 12.5 hours”, but they might tell you “in my app, I could do that in about half a week”, or “I could do it in a week” or “I could do it in three weeks”. And so you can get an outside perspective without talking to your co-founder on that one. If you know of a super senior Dev who has estimated a lot of things in their life, you could just have this conversation and show these are some things that we’re trying to build. Here’s the problem though, or I say something I would caution you in. Is oftentimes if someone’s really good, they might be a little slower and you might need to put up with that to have high code quality with high maintainability, and that’s just something that you have to do as a trade-off. 

I have 100% made that trade-off in certain instances. I remember being feeling stressed in the early, early, early days of Drip that we aren’t moving fast enough, but I knew Derek was a baller developer, but I knew he also wrote really maintainable high quality, scalable code. And so if it took an extra few days or an extra few weeks on a larger project to ship something, I was willing to live with that because I wanted long-term to have a code base in a company that would scale. Unlike some companies that we see where you get this non-technical founder who hires a Dev or has kind of a minority technical co-founder, and they drive them and push them to write code faster and faster and faster, and the code is shit, and then they get to a million, 3 million, 5 million in ARR and they stop, they lock up. 

You can’t build features because nothing is maintainable. You can’t add new things because you break old things. There’s no unit test, there’s just low quality code. So that’s the thing you have to be careful with is if the code is super high quality and really, well let’s say maintainable, it’s modular, that takes time. And so I think that’s a hard thing to evaluate. Code quality, you could have someone just review his code, whether it would be weird for you to be like, “I’m going to have an outside person review your code”. But you could have someone look at it and not tell him. That feels a little weird to me if you’re checking up on your co-founder, but you have to use your judgment on that and realizing that different people have different measures of quality. And scalability and long-term maintainability, you kind of won’t know. 

You won’t know for years feasibly. That’s the problem that we see with some folks who are non-technical founders and they hire out their development to an agency or to a freelancer. Nothing breaks, nothing’s bad for the first six months and then at 12 months, 18 months in, it’s like, “why are there’s so many bugs?” It’s because the code quality was shit. But you just don’t notice it in the early days because you go back and you fix those, but eventually you hit the point where quality just grinds to a halt and it will grind your whole business to a halt. So realistically, no easy answers here, but soft skills, you should be able to evaluate. Speed, I think a third party, if you’re particularly worried about that, I think talking to someone and saying, “how long would it take you to build this in Python or in Ruby?” 

And obviously you can go to Clarity.fm. You could hire someone on Upwork as someone who’s $150, $200 an hour and use them as an outside consultant. Again, whether you talk to your co-founder, it would feel weird to be like, “Hey, I’m checking up on you”. But whether you talk to them or whether you just go straight to a source or if you’re in MicroConf Connect, there’s a bunch of developers. And you work your network at a MicroConf in person event or whatever, kind of sanity check and take things with a grain of salt, I think you can get a reasonable approximation that might help you sleep better at night. So thanks for that question. Hope it was helpful. 

My next question is from Steven Davis, longtime listener of the pod, and he has written in before. And this is from March of this year, so about seven months ago. “I know you’ve covered no-code several times, and I know you’re a vigorous champion of SaaS, but if you are a SaaS builder, what about self-hosted no-code tools? I’ve been looking at some of the tools in the Linode marketplace. I kind of stumbled into this recently. To me, these offer an interesting trade-off between roll your own and SaaS, no-code offerings. Easier to customize, easier to scale, lots of caveats, but the price hikes and performance of SaaS, no-code can be challenging and you code what you need to and nothing else. WordPress is the grandfather of this, but there seems to be a growing set of options. Sendy is a proprietary but self-hosted email tool. There is the self-hosted Reddit forum, but they aren’t looking at this from a business perspective. Lots of them are open source, so you have to be careful about licensing and maintenance risks if it is closed source. You can look up open source Airtable or notion that they aren’t as polished, but they are on your machines”. 

Such an interesting suggestion from Steven, and I think Steven is particularly looking to get around the platform risk that you face when you build on Airtable or Notion or with Zapier. It’s really hard to migrate off of them. I think the biggest concern I would have is the same concern I have with Basecamp’s new offering, or I guess it’s 37signals offering Once. Once.com where they say you pay once and you host it yourself. I used to do that 20 years ago and it sucked. I hated hosting my own stuff. I hated, the updates would break things like WordPress is a grandfather of this. I actually wish I was not on WordPress. But I have, what do we have, two websites on WordPress? 

One is this podcast website because it still is the best platform in my opinion to host podcasts. The other one is robwalling.com, and there’s reasons that those are still on WordPress. But I’m twice a month I’m getting emails of this WordPress plugin that you have has a virus in it, and so you need to update it immediately. So then we have to do a staging environment and then we have to update it and then we have to test and hope nothing breaks and it’s a maintenance headache that I wish I didn’t have. And in fact, that’s why all of our other websites, like you go to tinyseed.com, microconf.com, you go to startsmall.com, saasplaybook.com, sherrywelling.com, zenfounder.com. Those are all on Squarespace. Do I think Squarespace is God’s gift to website builders? No. But do I ever get an email that one of my plugins is out of date or that the theme is broken or they’re doing an upgrade to my SQL and I need to go get my Gemini theme update? No, I don’t have to deal with it. 

So for me these days, and it has been for probably the fact… Because I used to tinker with this stuff, probably about the past, I made the switch about 15 years ago to where… I mean I used to have a server in my closet that served our source control and we used Vault or what was Microsoft’s one back then? Oh, I can’t even remember the name of it. But SourceGear had Vault and I would serve it off of that server, right? That’s like 20 years ago, it’s just crazy town. And I hated doing that. I hated having to worry about all that. So I see the appeal of hosting your own no code, it’s easier to customize, it’s easier to scale, you code what you need, exactly what you said, and you don’t have the platform risk, right, because you have the code. 

My concern is these days, I’m not in the business of maintaining custom code for this purpose. It’s a black box and I just want it to work. Look, if I was building a SaaS company, I wouldn’t want to build an Airtable or Notion as my Wiki. I wouldn’t want to maintain my own. The only custom code I want to maintain is my actual product. I don’t even want to build my own knowledge base. I don’t want to build, there’s a bunch of ancillary things around building a SaaS product, and there’s a reason there are SaaS offerings for those because it takes all of the security and the maintenance and the feature development and other things away from you. But of course with that, there are trade-offs. You pay the subscription, and you have this platform risk that they could screw you, they could raise prices, they could feasibly go out of business. 

There’s all these things, these problems, with SaaS as a model. But going back to pre SaaS and imagining installing and maintaining, I didn’t even get into maintaining the OS on the servers and having to keep that upgraded. I mean, I guess if I was on a shared hosting account or like a VPS or something that was maintained by them, that’s a hosting provider, that’d be fine. But anyways, so it is definitely an interesting idea, Steven, and I have not heard of this prior to you mentioning it, so I appreciate you bringing it up on the show. But for me, my vote would be a no because I just want all of that taken care of. As a reminder, head to stateofindiesaas.com. Take about 10 minutes and please complete that survey so we can put together an incredible report for you and be entered to potentially win a free ticket to MicroConf US 2024 in Atlanta. Thanks so much for listening this week and every week. This is Rob Walling signing off from episode 686.

Rob Walling:
And I’ve always wanted to avoid the lottery ticket approach, the big promise of, “You can be a millionaire tomorrow. Here’s an example of this person who did just that, and I’m going to teach you how to do that,” when in fact that’s bull (beep), when in fact it’s survivor bias, when in fact that’s one person out of 100 who each launched five products, and this one person got lucky and so it’s not repeatable, and I (beep) hated that stuff when I was coming up. 

It’s another episode of Startups For the Rest of Us. I’m Rob Walling, and today I’m talking about seven things you should never do. And I want to caveat this with, it’s for the most part you should never do. I use never in the title as a way, of course, to get you intrigued. But I’m not the person who puts never in all caps on social media and says things like, “In your designs, you should never have buttons with rounded corners because I say so and you never should.” We used to get these comments when we were building Drip. It was just insane, the confidence with which people would proclaim their opinion as fact. So I’m not going to do that here today. 

I use never kind of tongue in cheek. I think it’s for the most part, you shouldn’t do it. It’s a best practice. It’s probably 95% of the time you shouldn’t do these things. And some of these are things you’ve heard me talk about before, like bootstrapping a two-sided marketplace, or going B2C instead of B2B. This entire episode was inspired by a listener voicemail that I’ll play in just a minute. But before we listen to that, on this very podcast, we’ve talked about how in the US, Section 174 is really destroying our ability for software companies to write off expenses for software development, and instead having to depreciate that over many years. If you’ve just finished your taxes this fall, you probably saw them go way up with a lot more paperwork, and Section 174 is really the culprit. 

And previously, you may have been a signer or at least heard about the former letter that our broader MicroConf and Twitter community sent to Congress in April on this issue. Well now, several business groups, everyone from the small software crowd, to biotech startups, to big companies like Boeing are coming together on a new formal letter to Congress. 

So I’d encourage you if you want to get this fixed before the end of the year, which I think all of us in the software space should be worried about, go to ssballiance.org for the link to the new letter. Even if you already signed the one in April, this is the next phase, and I’d encourage you to check it out. 

An important note, this is for us headquartered companies, but you do not need to physically be in the US or be a US citizen to sign. So really, it’s US domiciled entities. 

The deadline is tomorrow, Wednesday, November 1st. So if you’re hearing this podcast before, then head to ssballiance.org. 

Before we dive into the episode, I want to invite you to MicroConf Remote. MicroConf Remote is our virtual event that we host twice a year. This next one is focused on early stage marketing. It’s on November 1st and 2nd. If you’re interested, head to microconf.com/remote. It’s a very inexpensive event, and talks will include the bootstrap startup marketing checklist, when early stage SaaS companies should hire a copywriter, and how to hire one that doesn’t suck. Building a sustainable customer acquisition funnel, SaaS email marketing, plus our patented Founder x Founder speed networking to get you introduced and connected with other founders in our community. Again, that’s November 1st and 2nd of 2023. Microconf.com/remote if you’re interested. Even if you can’t make it, if you buy a ticket, you will get the videos after the event. Hope to see you there. So let’s dive into the meat of the episode, and I want to kick us off by listening to the voicemail that Dan from Austin sent in.  

Dan:
Hey Rob, it’s Dan from Austin, Texas. I’m listening to the September 19th episode, which is great, and there was a couple comments that really got me intrigued. You said don’t start a B2C software company, and you also said, “Hey, don’t start a two-sided marketplace,” with a few caveats for both. 

But I’ve heard you make these arguments before, but as you said those things with such confidence, I was nodding my head and I thought, “Man, I’d really love to hear some more things like that.” What are five other things that you think for the most part, founders just should not do based on all your experience? And if you had, I don’t know, some stories or some anecdotes about those things or arguments, I think that would make for a really entertaining episode. So I thought I’d toss it out there and just say thanks for the pod. We appreciate it.  

Rob Walling:
Mark your calendars. I think Halloween 2023 is the day this podcast went big time. Because if you recognize the voice of that voicemail, it was friend of the pod Dan Andrews who runs the Tropical MBA Podcast with Ian Schoen. I appreciate Dan writing in with this great episode idea. 

I’ll admit, prior to this, I haven’t sat down and tried to think of a bunch of things you shouldn’t do, but they just come up when I get questions, or I see something a founder is doing and think that’s an anti-pattern in my mind. 

So in software engineering, there are design patterns that help you architect things and are general best practices, and then an anti-pattern or a dark pattern is something that you shouldn’t do, right? These are things, anti-patterns against what we would recommend. And so I think these seven things that for the most part you should never do fall in that category of anti-pattern. 

I did pull a couple from my book. I remember I had a section in there about mistakes that founders often make, so there’s a couple in here from that. And then there’s a couple others that I thought of as I was outlining this episode. 

So I’m going to skip one that Dan called out, which is the two-sided marketplace. I feel like I’ve railed on that so much over the years. You know the reason I have? Is because so many people write in, or apply to TinySeed, or email me, or DM me and say, “I have this idea and it is,” insert name of the next two-sided marketplace here. And I’m always like, “Great, how much funding are you raising?” “I’m going to bootstrap it.” Don’t bootstrap a two-sided marketplace unless you already have one of the sides. This is Rob’s rule of two-sided marketplaces, we’ll call it. 

I’m going to stop there. I always get carried away with this. And I’m no longer answering questions about two-sided marketplace. If you want to do that, find two-sided marketplaces for the rest of us. It’s a new podcast, I’m sure we’ll spring up. It’s just one of those things that talking about them is I think not helpful to the rest of the people who are bootstrapping, who are stair stepping, who are starting SaaS companies, info products, and all that. 

So with that, I’m going to move to number two of the seven, which is starting a B2C application. And again, I jokingly say tongue in cheek say never. Not that you never should. Obviously there are B2C applications that work, but what are the downsides of B2C? 

Well, it’s low price point, it’s high churn, it’s high support demand, and it’s high and entitlement and less technical users. And all of that for the ability to charge someone $7 a month, or $50 a year, or $30 a year in a lot of cases. When you go B2C, you get the worst of all the worlds, and you don’t get enough money to be able to do any marketing other than free marketing. It has to be viral, it has to be content/SEO, or it has to rank in an app store, which I include as SEO. B2C apps are very, very difficult to actively grow like you can with B2B, because with B2B, the prices are higher. And what’s the second order effect of a price being higher? You can afford more marketing approaches. I covered this in my MicroConf talk about pricing. I covered this in the pricing chapter of the SaaS playbook. 

I have owned multiple B2C products, some of which were eBooks, and some of which were software. And it quickly became obvious to me this was not the path I wanted to go down. And what was funny is that the very first MicroConf in 2011, I talked about this, about how bad it was… I’d never heard anyone say, “Don’t start B2C apps.” And I talked about it in my talk. That very same event, I think it was the next day, Patrick McKenzie, patio11 was talking about how B2C is tough and was talking about all the struggles he was having with Bingo Card Creator. And it quickly became a pattern of, “I think B2C is probably not a great choice.” 

Look, if you want to build something fun, little tool, utility to 1,000 to 5,000 and deal with the high churn, it’s fine. Do it. Again, it’s not never, it’s for the most part you should never. And can you do a fun experiment? Can you scratch your own itch? Can you solve your own problem and then go and want to just share that with the broader world? Of course you can. I wouldn’t say… Do stuff that’s fun, right? If it’s a hobby or you’re doing it for a lark, you go do that. 

I want to close this section out with a story from a friend of mine who had an iOS app. And I don’t even remember what it was honestly. It was like a B2C, some type of calculator or something that consumers downloaded, and he would frequently get people who would threaten him and say, “Add this feature or I’ll give you a one star review in the iOS App Store.” Or he had reviews he would screenshot and send to me. I believe his app was 3.99, let’s say, $3.99. And it would be a two star review and it said, “Would be worth it if it was 1.99.” And I remember I was just like, “Sir, this screenshot embodies everything that I think about building B2C apps.” 

So the third thing that you should for the most part never do is build a second product because your first one has stopped growing. I’m going to point you to an entire 50-minute episode of this podcast. It was four episodes ago, episode 681. I had our very own Ruben Gamez on the show, and we ran through… This is actually the show that inspired Dan to send the voicemail. But we ran through the pros, the cons, which there are a lot of, and really the mistake or the myth of the second product. 

That’s what we were trying to touch on is there is often this grass is greener mentality that, “If I just had a second product, then it would do this,” or, “It’s the same code base, I could just fork it off, and I don’t think about the hundreds and hundreds of hours I’ve spent building the domain authority and doing all the other things I’ve spent doing it.” 

So I’m not going to belabor the second product here. You can go back and listen to 681 again if you want to be refreshed, but that is the third thing that I think you should never do. 

Number four is one that I tried to do myself unsuccessfully. And this is one, you should never do it if you’re bootstrapping really. And again, you should almost never do it if you’re bootstrapping. Have I seen one out of 1,000 work? Probably, but these are my rules of thumb. And it’s create a category. 

So this is where you go out and define a new category of software, where you are trying to be so clever and be novel such that you have no competition, and you build out the space, you create the demand. If you’re familiar with the five stages of customer awareness, when you create a category, everyone is unaware or maybe problem aware if you’re lucky. So the education that you have to bring… And if you haven’t seen the five stages, just Google an image, but it’s in order from least aware to most aware is unaware, problem aware, solution aware, product aware, and most aware. And so when you create a category, you are in the top two of those. It’s unaware. And maybe if you’re lucky, problem aware. 

So to get people to be aware that there’s a solution, no one’s searching for that solution. To get people to be aware that there are products that do it when no one’s searching for those products, it’s a tremendous amount of effort, skill, expertise, time, and money to do this. So should you never create a category? No. 

So I tried to do this with Drip actually in the early days. I didn’t want to build another ESP. I felt like it was super crowded. That’s email service provider. So I didn’t want to build a MailChimp, or a Constant Contact, or an active campaign, just felt like it was too crowded. And so I tried to be really clever. And instead of just saying, “We are email marketing,” or, “We are marketing automation,” our headline described what the product did. And I don’t honestly remember exactly what it was, but it was something like, “We send automated emails at the right time to your customer’s prospects,” and blah, blah, blah, and it was about being clever and automating. But people couldn’t put you in a category. They would think, “So are you like MailChimp? No. I guess that’s email marketing. Are you marketing? But you’re for customers? So are you like customer.io, or are you kind of a CRM thing?” People would be confused. 

And as a result, I mean we basically plateaued at eight or nine grand. You’ve heard the story, didn’t have product market fit, and eventually I realized we should move ourselves into an existing category of software, and what we should do instead is carve out a corner of that using positioning. And so that’s when the headline changed to lightweight marketing automation that doesn’t suck. 

So the category is marketing automation. Our positioning is that we were lightweight, and that we were great to use, and we were reasonably priced, and we were on the customer side because we didn’t suck, right? It wasn’t old software. 

That was the moment where for us, things started taking off. That’s when Drip found product market fit. Now we had to build some features in order to get there, but that was the key so to speak, that unlocked the growth that became Drip. 

There are exceptions. There are times when you should create a category. Think of what Dharmesh and his co-founders did with HubSpot. This is before the CRM. They created inbound marketing, and they basically created this inbound marketing hub where it was a combination of Google Analytics, and I think it was like a website builder, maybe some lightweight email marketing. But it was this bundled tool. It was a bunch of tools you could get individually, and you and I as developers could comp them together. But if you’re not a developer or you’re not really into MarTech, this was an easy way to get it all in one place. And so they had to define that because it didn’t really exist. People didn’t know what to call it. 

And so if you go back to the book Inbound Marketing by Brian Halligan and Dharmesh Shah, those are the co-founders of HubSpot, and they raised a kajillion dollars to do this, and I talked to Dharmesh about this at one point. He and I were speaking at the same event and I said, “You created a category, congrats. So few people do that. When should you do it and when not?” Or, “What did it cost?” I think was the question I asked. And memory fails, but something to the effect of, “You need $5 million and two to three years.” Maybe he said 10 million in three years or something, but it was more money than I had. It was more time than I wanted to spend. 

They wrote a book, they started inbound.org, which was like a social news site for inbound marketing. They went all in on defining this term, and Dharmesh had a pretty decent audience at the time, and it was still this massive uphill battle. 

I think Intercom faced the same thing and then Drift came in. These are the chat widgets. And Drift for a long time, I don’t even remember what category they were trying to create, but they were trying to be different than Intercom. And I think it all kind of is one category in people’s minds now, but Drift raised a kajillion dollars based on David Cancel’s amazing reputation as a five-time entrepreneur, and it still took them years if you watched them grind that out. 

So creating a category involves not selling in an existing category. It involves, “I’m a builder, I’m a maker. I have this great idea for something brand new that doesn’t have a two word phrase that describes it.” That’s how I think about it. Or maybe it’s I guess an acronym, or a three word phrase like customer relationship management, CRM, email service provider, ESP. 

When you go beyond that, when you start using four or more words, this is Rob’s completely made up rule of category creation. But when you start needing four or more words or a complete sentence to describe what your product does, you’re in the danger zone in my opinion. 

Now, someone could give a counter example and say, “Well, what about chat AI, PDF thingy, where you allow me to chat with my PDF? How many of these are out there?” Chat CSV, whatever AI, ChatGPT wrapper people are using these days to allow you to do something? Do those create a category? 

And my answer is most of those wrappers are a single feature, and so you’re not trying to describe a complex piece of software. You can literally have a headline and it describes everything it does. All it does is allow you to chat with your PDFs. You don’t need a category, because it’s not complex software. 

But the moment I tell you, “Okay, you have a form, and you’re going to collect email addresses, and they’re going to go into a list. You’re going to be able to send broadcasts and sequences to those people. You’re going to be able to tag them when they buy something or when they do something else. There’s integrations with payment providers and landing page.” You need a category for that, because it’s not just a single feature. 

I had an app called HitTail, it was an SEO keyword tool, that was the category. But the one sentence description was, “HitTail tells you keywords you’re already ranking for that are low hanging fruit to increase your ranking.” All right, obviously that’s a very long description. I could tighten it up, we could workshop it. I can make it shorter. But you get the idea. It was just that. It was a single feature. 

So it fit in a category of SEO keyword tools. I could also describe it as that feature, and that’s how I think of these AI wrappers is they are just a single feature. Now the moment your software does two, three, four, five things, you can’t put that in a headline. So what do you do now? That’s where buyers usually need categories to figure out what your software does, and so they can bucket you and compare you against other categories. 

Here’s the other thing. I’m not talking about five, 10K lifestyle businesses, five 10K a month. I am talking about, how do we build a million dollar or multimillion dollar startup? Much in line with my latest book, The SaaS Playbook, which talks about building a multimillion-dollar startup without venture capital. 

There are always these niche, tiny exceptions where could I go B2C, or have a second product and try to… I don’t know, create a category wouldn’t be the thing, but be outside of a category maybe is another way to phrase it. And can I get that to 5K, 10K, maybe 20K a month? Or if I have some massive Twitter following, and I do a product hunt launch, and I get a little lucky that I can get it up to 50K a month, these are all possible. 

They’re very unlikely. They’re not repeatable. They rely a lot on luck. I like to rely on hard work and skill. I like to talk about things that are repeatable, and that through execution you could do over and over and over. And so that’s why I’m talking today about things like creating a category, which is an anti-pattern if you’re bootstrapping because it’s expensive, takes so much time, and for all the reasons I’ve already covered. 

As a founder your plate is full. So when you have to hire devs, there’s no time to search for that perfect culture-fit, get-things-done developer. Lemon.io’s new product, Lemon Hire saves founders time by connecting them with a pipeline of more than 80,000 senior engineers. Each dev is filtered through a 4-step vetting process, is available to interview within 48 hours of being selected, and is backed by a 30-day replacement guarantee.Find your ideal candidates fast with Lemon Hire.

Claim a special discount for Startups For the Rest of Us listeners by visiting lemon.io/hire. When you sign up make sure you mention “Startups” to receive $2000 off your first hire.

The fifth thing you should probably maybe never do if you’re bootstrapping is translate your application into multiple languages. And I mean spoken or written languages, not coding type languages. This one, I see it much less often, I’ll admit, than the others, and this is probably less important. I won’t spend too much time on it. 

I have seen multiple people, and in fact, there was one app that I bought where at its peak, this SaaS app was doing, think it was six, seven, $8,000 a month, single digit thousands. And yet they had translated the application, all the error messages. I think they even translated the entire marketing website into three or four different languages. 

And it was such a bizarre use of time and energy. It was kind of like a weird form of procrastination. I think about it like that, where instead of doing what’s actually going to move the needle, instead of doing the thing that makes me uncomfortable, which look, maybe it’s talking to customers. Who’s grinding out another big feature? I’m going to go watch TikTok, and I’m going to watch some YouTube, and I’m going to listen to an audiobook, or I’m going to go on my Trello board and stare at it, or I’m going to go translate my app into multiple languages because I think that’ll move the needle. It really feels like an odd form of procrastination and it’s a huge waste of time, unless you’re at the point where you have tapped out your entire market. 

So I’m going to use the English-speaking market, or the US market for that matter as an example. If there are tens of thousands of people or businesses that could buy your product, and you’re doing five or 10K MRR and you’ve plateaued, figure out why you’ve actually plateaued. The reason is not that you’ve consumed the entire English-speaking market and you now need Spanish. Even if someone, three people requested we translate it to Spanish. The odds of you being able to translate it well, translate your entire application, just invest the dozens, hundreds of hours to… It’s somewhere, and it’s not hundreds. I mean it depends on how many many English strings you have in there, but to invest the amount of time, the effort, the energy to translate your entire app, and then translate your entire marketing website. And then, are you going to do support in the new language in Spanish? Are you going to translate your knowledge base into Spanish? Are you going to have a separate domain or the same domain? Are you going to market in Spanish? Are you going to do SEO, content, cold outreach, integrations, partnerships, attend events, all the 20 B2B marketing approaches I talk about? 

When you translate into another language, you spread your focus. In all the conversations I’ve had with every founder I’ve ever advised, invested in, been involved in, anyone who asks my opinion, one founder convinced me that they should translate it, that it was the right time to do it. And I think he was right, and it was a really good conversation. It was similar to the conversation I talked about when we talked about second products in episode 681, where Jordan Gal just had really good reasons. I said, “You know, you’re right. You are the exception right now to my rule of thumb.” And I’ve had one founder be the exception to this translate to other languages rules of thumb. 

He had tremendous market pull. Parts of his site were already ranking in Latin America. This is an English to Spanish translation. And he had some incredible resources. He already had a support person who was bilingual. It was like everything that I just said, every objection I just talked about, he had an answer to, and he had either thought of it, or he happened to have a good way to do it. And he was running a team of people. He wasn’t at 6K MRR. He was orders of magnitude above that and growing very fast. 

And the other thing was that he had customers, but his customer’s customers often spoke other languages, even if his direct customers spoke English. So the people buying from him spoke English, and their customer’s customers sometimes did not. And so he was thinking about doing, I think it was like two or three of the most popular languages in the world, and he was getting multiple requests for this, and he was getting some not only inbound, but starting to rank in these other engines. And most of his support, he could still do in English. And I’m only using English as the example because these are the companies I deal with. Obviously, your native tongue would be the English equivalent in this example. 

The sixth thing that for the most part you shouldn’t do is to treat symptoms instead of finding root causes. I realize this one’s a little meta, but the biggest example I see is churn. Churn is usually a symptom that you have something else wrong in the business. Usually. There comes a time when you’re doing tens of millions a year or maybe a month, and optimizing your churn by having people upgrade to annual plans, or making people give you a reason before they cancel, or offering a discount, or a subscription pause, or other options like that, those will reduce churn. 

And at a certain point, that makes sense to just do it blanket, and it will lower your churn, make your business better. 

The problem is I’ve seen founders who are doing, again, they’re early. 5K a month, 1K a month, 20K a month. And they’re churning too high, and so they start implementing these anti churn tactics forcing everyone to go annual, or making that the default, or making you have to call them on the phone to cancel, or just whatever. Putting up some type of friction to get churn down. 

And what that does is it actually masks the root cause of that churn. That root cause is usually that you don’t have product market fit. You have not built something people want and are willing to pay for, or you have weak product market fit. There’s a bunch of things we could go down in terms of the root cause. But by attacking the symptoms, treating the symptoms, you are doing a disservice to your customers. You’re doing a disservice to yourself because you’re not learning. 

And to be honest, the reason people do this is because the learning and the figuring out what’s wrong and then fixing is actually really hard. This is a hard part of being a founder. The easy part is let’s build a fun product, come up with an idea, and launch it on Product Hunt, and put it on Hacker News, and tell our friends about it, and get some people in. And boy, it got hard, huh? Everyone’s churning out. Well, guess I’ll move on to my second product. Let’s make this one a, B2C, two-sided marketplace in a new category that I can translate into six languages from the start. Anyways, I’m being facetious here obviously. 

So this one comes out of me seeing founders, aspiring founders posting on Twitter usually, a conclusion they’ve come to about reducing churn. “Look at this thing I tried. Churn was high, now it’s low.” And usually, I don’t think you’re actually attacking the real problem. 

Another thing is split testing too early. “I’m going to split test headlines because my conversion rate on my website is low. My visitor to trial,” often it’s like well, maybe the whole website. You just haven’t built something people even want to try out. And that’s the root cause, and it’s hard to figure out what that is. It’s easier to look at a tactic like churn reduction or split testing, and implement that thinking that’s going to save you. But usually, what you’re doing is you’re messing around with a local maxima rather than a global maxima actually jumping up another level, which if you get to the root cause, you can start to attack. This frankly could be a book chapter, multiple podcast episodes, because finding root causes of these things, it’s challenging. But that’s why I do see people treating those symptoms. Maybe it’s a form of procrastination or maybe it’s just a form of not knowing any better. It’s asking the wrong question, right? It’s, how do I reduce churn? Where it’s like I guess that’s the question, but really the quick easy answer is the tactic, “You can try these five things to do it,” but the hard answer is usually digging in, finding the root cause. 

My seventh thing that I think you shouldn’t do if you want to build a multimillion-dollar startup and bootstrap it, is to launch a bunch of products. And I have quotes in the outline that says, “Hoping one sticks,” end quote. 

I’m a builder. I love the idea of building 12 products in 12 months, 52 products in 52 weeks. Building and shipping is a dopamine rush. It’s amazing. Getting your new product, or feature, or ChatGPT wrapper or whatever into the hands of people on Product Hunt, and Reddit, and Hacker News, and your friends. And look, I’m not mocking. I know earlier I was joking about Product Hunt and Hacker News launches. Those are a mixed bag, but they’re not a bad thing. If I was launching a product today, I would 100% want to get on these social news websites. I do take them with a grain of salt in terms of actually gathering customers that will stick around, but I do think there’s some value there. It’s probably a topic for another podcast episode. 

But the idea of launching a bunch of products, hoping one sticks has a couple problems, pretty major problems for me. One is you don’t learn very much. Because if I launch 10 products and one works, it’s unlikely I’m going to know why. It’s really likely I got lucky. And again, I don’t like to teach approaches that need or rely on luck. I’ve been doing this for… I don’t want to sound too old, but let’s say in the neighborhood of two decades. And I’ve been successful at it for less time than that, but I’ve been talking about it on this podcast, my blog, my books and everything for whatever it is 15 years, 17, 18 years. 

And I’ve always wanted to avoid the lottery ticket approach, the big promise of, “You can be a millionaire tomorrow. Here’s an example of this person who did just that, and I’m going to teach you how to do that,” when in fact that’s bull (beep), when in fact it’s survivor bias, when in fact that’s one person out of 100 who each launched five products, and this one person got lucky, so it’s not repeatable. And I (beep) hated that stuff when I was coming up, when I was trying to become a successful entrepreneur, and I could just smell snake oil. And the further I dug in, the more I found out that the person promoting the approach had gotten lucky, hadn’t really built the business they talked about. 

And so the idea of learning, and not just being successful, but knowing why you’re successful, and knowing that you could repeat that again, or actually repeating it again showing that you have the skill to do it multiple times. This is something I’ve always held onto pretty tightly. As someone who has been both a doer and a teacher, not just a teacher, not just someone who had a middling success and then claims I started the biggest startup and had the biggest exit anyone’s ever talked about. I’m really sensitive to the people out there who oversell what they’ve actually done. And the folks who oversell what they’ve actually done usually got lucky, and usually don’t know why they’re successful. That’s the problem. 

So let me tell you some people who are not in this camp, so people who are successful and I think could do it 20 more times if they had the time. 

Jason Cohen, Heaton Shaw, Rand Fishkin, Ruben Gamez, David Cancel, Dharmesh Shah, I can go on. There’s more than that, right? There’s people in TinySeed who I have a lot of respect for who I know could do this again. 

And they learned what it took. They had to grind, they had to make mistakes, and then overcome those mistakes and figure out, what is the thought process? What is the approach? What is the troubleshooting? If you never make mistakes, are you smart or are you just lucky? If you make mistakes and overcome them, you learn. You become just a little bit better as a founder. 

And so that’s the first thing I don’t like about this oping one sticks is I don’t think there is much learning in launching and getting lucky with one out of 10, one out of 20, and then writing that. If that were to be successful, I question if you can ever do that again, if you just caught lightning in a bottle. So the lack of learning and really truly understanding why you’re successful, I think is one thing. 

The other thing is oftentimes in most cases, I’ve talked to literally thousands of founders now, many of whom are successful and some of whom are not. Most of the time, the thing you initially launch with is not the same product that gets you to product market fit. Most of the time, you launch with something you think the world needs, and you miss the mark. Sometimes by 5%, sometimes by 95%. 

But great founders then ask the right questions, have hypotheses. They just pivot around. They add a thing, they make a guess, they change their positioning. They don’t just willy-nilly do it, but they learn, and they take those learnings, and they build them into the product, and the positioning, and the marketing, and the sales, and slowly they grind to the point where they’ve built a business that people want and are willing to pay for and are saying, “Shut up and take my money.” 

Sometimes that process takes months. Sometimes you get lucky. I know there’s someone out there, one in 1,000, who what they launched actually did get them to product market fit. We see those examples on Twitter. Right? We see the examples on Product Hunt or Reddit, and we say, “Oh my gosh, they did it. I can do this too. It’s totally feasible,” and it is totally feasible. One in 100, one in 1,000, whatever. There’s some minuscule number of times where it’s truly what you thought the market needed was what they actually needed. 

Most of the time, it takes you six months to get there from launch, 12 months, 18 months, 24 months. It takes a long time, and it takes a lot of grinding and there’s a lot of uncertainty. And that, in my opinion, is the worst part of being an entrepreneur, the worst part of starting any company. And let’s specifically say SaaS companies or products that people want, the worst part is the uncertainty when you still don’t know if you’ve built something people want and you’re willing to pay for. 

And so that’s the part that people want to avoid because it’s painful, but that’s the part that I believe makes you a great founder. Those are the moments, those are the days, weeks, and the (beep) months that you grind it out, and you come out the other side if you find it, if you suddenly see your churn plummet, trial to paid going through the roof, and people searching for your brand name in Google, and you’ve caught the rocket ship, you’re starting to catch what I call escape velocity. Once you’ve made it there, you can look back and be like, “Wow, that was hard and it took a long time, but I’m a much better founder for it, and now I know why I’m successful, and I think I could do this again.” I love having that confidence, right? The repeatability of it. 

So again, this is the second point. The first one was hoping it sticks doesn’t teach you anything, doesn’t make you a better founder. But the second thing is it’s a disservice to a lot of those ideas, because I think a lot of ideas you launch, and you get the bump, and you get the dopamine rush, and everybody turns out, and you don’t then know how to market. You never make it past the starting line. 

To me, launching a product is the starting line. People who think about it as a finish line have never built a multimillion dollar product, because really launch is the starting line where you start to learn, you start to learn what you’ve done right, and mostly what you’ve done wrong, and usually you’ve done quite a bit. And that’s where you then gain the skills, right? That’s where you gain the skills of, which marketing approaches do I try, which do I try first? And you actually start doing repeatable things that if they work, will be skills that you take with you for the rest of your life. 

I think if you’re of the mindset that you should launch and see what sticks, I think you’re probably given up too early. We certainly are doing your product a disservice, because it could be successful with work, with the grind. And I think you’re doing yourself a disservice because you’re never going to learn the nuts and bolts, the blocking and tackling, as Dan Andrews would say, of building a business, and that grind and actually getting there. 

Look, when I say grind, I don’t mean 70-hour weeks. I just mean doing things that are hard and you kind of don’t want to do. They’re new, they’re uncomfortable, and they’re uncertain, And you might waste time because you might try a marketing approach and it doesn’t work. But then iterating, and building those features, and getting to product market fit is incredibly rewarding. And that’s the process that can take you from being a wantrepreneur, a brand new entrepreneur, to someone who knows how to build great products and great companies. 

So I hope you enjoyed those seven things you should for the most part, never do, especially if you’re bootstrapping. I really appreciate Dan Andrews writing in with that voicemail. I had a fun time putting these together. Thanks for listening this week. And every week if you keep listening, I’ll keep making these. This is Rob Walling, signing off from episode 685.

Rob Walling:
It’s another episode of Startups For the Rest of Us, I’m Rob Walling, and today with Dr. Sherry Walling, we walk through our key takeaways from MicroConf Europe 2023. This event was held just a couple weeks ago in Lisbon, Portugal, and you’ll hear us give an overview of it, but really dive in to the keynote talks and pull out, I’d say actionable or at least thought-provoking takeaways as well as give our overall thoughts of the event. 

Before we dive into the episode, I want to invite you to MicroConf Remote. MicroConf Remote is our virtual event that we host twice a year. This next one is focused on early stage marketing. It’s on November 1st and 2nd. If you’re interested, head to microconf.com/remote. It’s a very inexpensive event and talks will include the Bootstrap Startup marketing checklist when Early-stage SaaS companies should hire a copywriter and how to hire one that doesn’t suck, building a sustainable customer acquisition funnel, SaaS email marketing, plus our patented founder by founder Speed Networking to get you introduced and connected with other founders in our community. Again, that’s November 1st and 2nd of 2023, microconf.com/remote if you’re interested, even if you can’t make it, if you buy a ticket, you will get the videos after the event. Hope to see you there. And with that, let’s dive into our conversation. 

So Dr. Walling, thanks for joining me on the show and for joining me on stage at MicroConf Europe in Lisbon last week. You and I shared the stage and emceed the event for the first time ever.  

Dr. Sherry Walling:
Co-emcees. We’ve never done that before. We’ve done a lot of professional collaborations, but that was our first co-emcee gig.  

Rob Walling:
I had a great time. How about you?  

Dr. Sherry Walling:
Yeah, it was pretty fun.  

Rob Walling:
We had some witty banter.  

Dr. Sherry Walling:
I don’t think we embarrassed ourselves, which is, you know.  

Rob Walling:
Unusual.  

Dr. Sherry Walling:
It’s always positive, in front of 120 people.  

Rob Walling:
No, but we had-  

Dr. Sherry Walling:
Strong performance.  

Rob Walling:
I had an absolute great time. I was thinking before we recorded this that I wanted to say this sentence that’s going to sound like hyperbole, but this is one of the best MicroConf Europe’s we’ve ever hosted without exaggeration. I remember a few landmark years, this is the 10th year, ninth event because we skipped Covid. In certain years you remember as being amazing, as having incredible energy and the attendees all being on the same page and just this positive group energy flowing. And that’s how this year felt.  

Dr. Sherry Walling:
As the kids say, it had a good vibe.  

Rob Walling:
Had a good vibe. I was trying to… You asked me, “Why do you think it had that?” And I went through all these reasons and I honestly think one of them is that this is such a small thing, but you could step out of the venue, we’re in the meeting space, we’re focused, and then you took 20 steps and you were basically looking at the ocean, they call it the river right there. I guess technically it is, but I mean it’s this huge body of water and you were in the sun and it was, whatever it is, 78 degrees Fahrenheit outside and it just felt like you could quickly recharge and escape the feeling of say, being at an event and suddenly be outside talking with founders, drinking coffee, having those amazing Portuguese pastries.  

Dr. Sherry Walling:
Yeah, I mean as a psychologist, that’s not a small thing at all. That’s a huge thing to have a little bit of contact with nature, a little bit of sunshine and just a general environment that feels relatively relaxed but also very alive and awake. You don’t feel like you’re just sitting in a room all day getting bombarded with facts and information, but that you’re really present and that when you feel that diminished energy, you can go out and recharge really quickly and easily. And I think that’s why I’ve really loved the MicroConf Europe’s that I’ve attended because you and Xander and the team have done such a nice job of having them in really beautiful places.  

Rob Walling:
And that’s something that I think is perhaps a little easier in Europe because in the US where we’ve had it, let’s say downtown Denver, downtown Minneapolis, and then Vegas before that, you’re always in the middle of a city and we’re not next to a lake or a body of water, versus where we were in Dubrovnik and now in Lisbon, you’re just right by the body of water. And so I think that’s a factor. Here’s the thing, here’s not the number one factor, it can’t be because that rules out like 99% of venues and there are only so many venues available at certain prices and certain places where people can get to on airplanes. But it definitely is a factor for me, I think  

Dr. Sherry Walling:
I think one of the benefits of having it in a place like Lisbon is people can combine the attendance at the event with a little mini vacation, which is actually what we did, which we’ve done in different versions over the years with our family mostly. But this is the first time that we have done a little mini vacation, just the two of us attached to a MicroConf Europe event. And I think that’s why you were so relaxed and had a good time is because we had a few days to play first. And again, I think that’s a really nice way to just build in a little bit of play and relaxation and fun, whether you’re a founder going by yourself to an event and you just add a couple days to explore or you’re able to bring your partner or even your family. Taking advantage of events that are hosted in really beautiful spaces, writing off your ticket, just sort of double dipping on your time and energy and travel is a really lovely way to use the event.  

Rob Walling:
Well, this is not tax advice, we definitely wrote off our airplane ticket. I agree. I mean, you and I had three days together just at the beach and downtown Lisbon and the Commerce Plaza. I won’t embarrass myself and try to pronounce the Portuguese name for it. Going up to the castle, St. George’s Castle. It’s my second time in Lisbon, you’re first, but it was such a nice lead up to relax, even though we both had talks to give. Usually what happens is if we take three days to chill out before it’s like, oh, I got to write my talk, oh, I got to work on my talk. But we didn’t, we had them done enough that we didn’t have to worry about it, so.  

Dr. Sherry Walling:
So the setting and the context of the event were really lovely. I think just facilitated an openness and a calm and people’s eagerness to just jump in and be present because it was so inviting. It was just such an inviting venue.  

Rob Walling:
And we changed the format or we continued to lean into the adjustment we started making in 2021, in which we used to do nine talks over two days, and now we do about five talks and with the extra time, it’s all founder connection. We call it founder by founder, where folks have a timer and they meet one another and they have conversations. We had an entire afternoon session that was just outings. You could either do like a walking tour slash scavenger hunt in downtown Lisbon or you could get on speedboats.  

Dr. Sherry Walling:
I heard the speedboats found a submarine, they were surprised by a submarine .  

Rob Walling:
Producer Xander really pulled it out on that one to be able to pull a submarine out of the water. But that continues to be from the attendees in the reviews, in the comments that it’s almost like no amount of time connecting founders is too much.  

Dr. Sherry Walling:
I really celebrate this shift for the MicroConf organization because MicrConf’s always been very focused on strategies and tactics and helping people have the tools that they need to move their businesses forward in the ways that they want to. But when MicroConf started, there wasn’t the sort of barrage of available information that there is now. Now there’s YouTube channels and podcasts and lots of great information for founders about writing marketing company or hiring or any of the kind of technical parts of running and growing a business. 

And I think the talks at MicroConf are still really valuable. You do a nice job of curating them. But what people are really longing for that they can’t get in other places is that face-to-face connection, is making a new friend, making a new contact, having an experience with someone who has a very similar background, set of values, drive. So I think that emphasis on growing relationships is a really, it’s a value add. It’s one of those things that people don’t maybe see automatically as a value add. But when you walk away from an event, probably the most lasting over the course of your life benefit of being in an event like that is the people that you meet and the network and the friendships.  

Rob Walling:
If we were to come onto this podcast and say, “MicroConf, it’s all about just coming and meeting people and hanging out.” And there’s a bunch of introverted, I’ll say a lot of engineers who listen to the show, not solely, but a bunch of introverts.  

Dr. Sherry Walling:
Right, it sounds terrible.  

Rob Walling:
Right? I don’t want to do that.  

Dr. Sherry Walling:
I don’t want to do that.  

Rob Walling:
But I believe people come for the talks and they stay for the community. That’s what keeps people around, because if we just had talks year in, year out with no community, no one would stick around. Speaking of talks and shrinking from say nine talks down to, we’ve done between four and six, and five seems to be the sweet spot. So almost cutting our talk count in half essentially has meant that we don’t necessarily do just tactical talks anymore like, here’s how to write copy, here’s how to do this. It’s so much more about frameworks, things that you can apply to any situation. So higher level thinking than tactics and founder stories. And we usually have one or maybe two founder stories out of five. But the frameworks in this event, I think I was struck by, and there were three right off the top of my head. 

One was Michelle Hanson who kicked us off, she’s the co-founder of Geocodio, and she had, Frameworks For Making Product and Strategic Company Decisions. And she even talked about having a framework and then overlaying another framework on top of it within, it was the business model canvas and laying, I forget her other framework, the Parker framework maybe, inside the framework. And people were kind of mind blown of like, oh, it doesn’t, you can kind of bastardize these things, combine two of them and just do… Whatever framework you have, just use that one, whatever framework you want, use that one but just be consistent with it, was a big part of her message  

Dr. Sherry Walling:
Frameworks on frameworks on frameworks. It was very meta level while also being very applicable. And I think she did a nice job of identifying how people are actually using frameworks, they’re just maybe not recognizing it. And so when you pull the curtain back a little bit and do that metacognitive process of thinking about how you’re thinking, then automatically you have the material for a framework. So it was a very helpful talk. And then you were second, you followed that up.  

Rob Walling:
Which sometimes I’m going in with just a banger talk and I’m like, oh, this is going to crush it. And other times I’m like, I think this is good, but it really depends on how people receive it. And so mine was about the five stages of customer awareness and basically overlaying that over content marketing. And so it was a framework applied to content marketing. Because everyone says, “Do content marketing, create content…” Profit? What happens after that? And at a certain point it clicked with me through some other sources that have talked about it, Powered By Searches talked about it a bit and there’s other people who’ve talked about it, but I had never seen a real deep dive into B2B content marketing through the lens of the five stages of awareness. And the moment that I really believed that the talk was going to resonate is, I got up on stage and I said, “Show of hands.”, Before I said anything, “Who here has heard about the five stages of awareness?” And it was like five people out of 120. And I said, “Ah, this is great.”  

Dr. Sherry Walling:
Got an idea for you.  

Rob Walling:
I was concerned it was going to be like 80%, and I was going to be like, okay, well we can kind of skim through that part. Now the money is in this later part of applying it to content marketing, which I’m guessing most people had not doing. But given that they hadn’t heard about the stages, which are unaware, problem aware, solution aware, product aware, and most aware, given that they hadn’t heard of those, it allowed me to almost meta educate on, here’s a concept and a framework you may have never heard of and now I hope to blow your mind by applying that concept-  

Dr. Sherry Walling:
With some tactics.  

Rob Walling:
To something you’re already familiar with. Yep, that was the mix.  

Dr. Sherry Walling:
Yeah, your talk was really a really nice representation of MicroConf values because it had that big picture framework thinking, and then lots of screenshots and strategies and practical application and examples, which I think people took a lot away from.  

Rob Walling:
As well as a picture of me holding our eldest kid, who’s 17 now and off to college, but I was holding him and when he was like, what? Five months old? Reading C# Business Objects book. And then I flashed to today, and I had used that photo at the very first MicroConf that I had spoken at.  

Dr. Sherry Walling:
Oh, wow.  

Rob Walling:
Yeah, it was in my talk in 2011. It was a couple years… It was whatever, three, four years old at that point. But the thing I was trying to drive home was, A, this is really what this community is about. We are about business, but we also temper it with what’s really important, which is our relationships and our families. But I wanted to also show of, this is how long we’ve been doing this, that this child in this talk from 2011 is now off to college, and that felt… Talk about representing MicroConf, right?  

Dr. Sherry Walling:
You put some reps in.  

Rob Walling:
Yeah. And then day two, well of course there’s a great evening event hangout, happy hour, but day two was kicked off by our very own Einar Vollset who went deep on AI.  

Dr. Sherry Walling:
He did such a nice job of identifying a real world problem and then taking the audience through the process of how you would use AI in an iterative fashion to work out that problem. And it was a fairly technical problem, so not necessarily something that I was deeply familiar with, but the logic made a lot of sense and he sort of showed in real time how you would query AI, what adjustments you would make to get better results based on the query results from the first round. And I found it to be just a really helpful way of thinking about how to use AI as an asset.  

Rob Walling:
Yes. Speaking of encapsulating high level thinking with tactics, that’s what that talk was, right? And it was about, to set the stage for those who didn’t see it, it was about essentially categorizing, if you have this huge list of leads that you want to reach out to, you want to contact, how do you get more information about them? And honestly, how do you figure out what your best leads might be, using AI based on shared traits that they might have with existing leads you’ve contacted that have converted. And so it was a ChatGPT demo of, here’s a big list of CSV of my best customers. And then trying to reverse engineer that and say, now here’s a million email addresses or a million companies, how do you find the best ones out of that? So almost like doing lookalike audiences a bit, but I’m not doing it, I don’t think we’re doing it justice, but I mean it was like 30, 35 minute deep dive into that, and it certainly impacted a lot of folks.  

Dr. Sherry Walling:
People used the mind blown emoji.  

Rob Walling:
I used the mind blown emoji. I was like, “Whoa, this can do this?”  

Dr. Sherry Walling:
You weren’t the only one.  

Rob Walling:
And then we had a Quiet Light, live business valuation, something we’ve never done.  

Dr. Sherry Walling:
So people submitted their businesses and then Quiet Light did a live back and forth conversation with the founder around all of the important metrics that would be considered in valuation, as well as the person’s motivations for selling or just what, they went through the whole your first phone call to a broker about the potential sale of your business.  

Rob Walling:
Yeah, and I thought it was super insightful if you’ve never sold a business to know what types of things they value. And the good part was David Newell with Quiet Light would ask the question, then he would get an answer, and then he would just think out loud and say, “Well, here’s how that’s going to affect valuation. Here’s how that’s going to affect the motivation of a buyer. That’s good or that’s not good. That’s going to impact it positively or negatively.” 

And as you said a little bit about the psychology of it too, and so as he was asking questions, since I’ve sold a few businesses, I was like, “Oh yeah, no, this makes perfect sense.” And then at the end he’s like, “Here’s the range. Here’s about what I think this business is worth.” And that was neat. It was a really nice… And then there was Q&A after that, so it was like a 30 to 40 minute session that I think was probably super helpful for those that have… You don’t sell many businesses in your life, and so if you haven’t done it or you did it poorly the first time, I think this was a nice demonstration of how to think it through.  

Dr. Sherry Walling:
A real-time case study. And again, that emphasis on frameworks, like how to think about this, what are some strategies that help you think about it?  

Rob Walling:
And then we had three attendee talks this year, which is where attendees can submit a topic and get up on stage, and these are 12-minute talks, and I wish we could talk about all of them, of course, but I was impacted by Sophie, thisissophie.com, I think is her domain or her business.  

Dr. Sherry Walling:
This was her first talk on stage.  

Rob Walling:
That’s why I was so surprised by it, because she just-  

Dr. Sherry Walling:
She nailed it.  

Rob Walling:
Crushed it, yep.  

Dr. Sherry Walling:
Her talk was about how to help your company be known for something very specific. So it was a product marketing talk, but it was again, really a framework for thinking about how to nail the one thing that will be really sticky for your company as far as recognition by your customers.  

Rob Walling:
Yeah, it was good. She didn’t use the word positioning I don’t think at all in the talk, but that’s really what it was, is like how do you position yourself and anchor yourself in your prospect’s minds, by doing one thing differently and doing one thing really well? It was a pretty good use of 12 minutes.  

Dr. Sherry Walling:
Yeah.  

Rob Walling:
In my opinion.  

Dr. Sherry Walling:
And there was another attendee talk, I know we don’t have time to maybe talk about all of them, but Johannes put up a slide that I thought was the heart of MicroConf. So help me remember the technicality here, but he put up a slide that showed a graph comparing the projected income that he would’ve made from consulting, beginning in I think 2007, something like that. And he looked at his actual income at that time and then projected it forward, and he compared that to the income generated from the business, the app that he started, and of course it was much lower at first, but then there was this inflection point where his income shifted from being from consulting, dollars for hours, to revenue from this app. 

And it was such a cool just way to look at that shift over time, because for me, that’s sort of the heart of what MicroConf is about, as his income or as his revenue grew with his app, so grew his freedom, so grew his flexibility, so grew his hours spent with his family. And it was a very nice way to tell the story of shifting from something that feels so financially sound and lucrative to this very measured, careful risk over time that eventually also becomes very lucrative. But there’s this middle place of languishing between consulting money and hoping that that app is going to start making enough to cover expenses.  

Rob Walling:
It’s the common story, is the most common story in the MicroConf space. I have a picture of that slide and I will try to get it into the show notes for this episode. But yeah, it was Johannes Akhison, I don’t know how to pronounce his last name, and there was a third line or bar on that graph, it was exactly what you said, and the third one was all the revenue from the product plus the value of the company now. He started mapping out, I think it’s worth whatever the multiple is, and that put him even further ahead that he has this asset that he’s built, it wasn’t just about income. It really was… He put the slide up and you and I looked at each other and you’re like, “That’s it, that’s MicroConf.” That whole slide out, it was great. And then you took the stage, so we have two talks left. You took the stage, talk about frameworks, holy moly. Motivational archetypes, and you threw out, was it six or seven different archetypes of what motivates us as founders?  

Dr. Sherry Walling:
Yeah, I think people often think about motivation is just the emotion to get their work done, and it of course is a much deeper, more complicated story than that. It involves our personality, our life history, elements of what we’re coming to this point in our lives with. And so I pulled together a few different archetypes. One is the money maker, of course, somebody who just is after the money, they want the wealth, they want the security that’s what motivates them and drives them. There, of course is the people person, so the person, the founder who’s really motivated to create an extraordinary experience for the humans around them, whether that’s their employees, their customers. So I went through several different archetypes and I think it was a really interesting talk. My hope was to help people think about motivation differently and to give them some material for self-reflection so that they can better understand what motivates them and then what happens when their motivation is stuck or a little bit dried up, how do we reconnect to motivation? It’s much easier to reconnect to it when you understand it very deeply.  

Rob Walling:
Right, and you coined, I think coined terms, you talked about micro motivation and macro motivation. And micro motivation is the day-to-day, and that’s the cold plunge, Trello board, Pomodoro techniques, get up at 4:00 AM, drink coffee, it’s all the tactics.  

Dr. Sherry Walling:
Get your butt in the seat, do your work.  

Rob Walling:
Macro motivation, you were framing as, but how do you stay motivated over the years that it takes to do this? And that’s what you then focused on. But that concept alone between micro and macro, I think most people don’t think about, because you can put things in place to get you in the seat every day, but man, as you burn out, you can’t do the years, you can’t do the reps. And so I think the archetypes that you came up with are something that we should revisit in a book or in a deep podcast episode or something, because there’s something there, and it allowed people in the audience to say, “Oh, I’m part money maker and part time traveler, where I live in the future.” And able to think to themselves, okay, these are my motivations, I need to hang onto those to stay motivated in the longterm.  

Dr. Sherry Walling:
We also talked a little bit about how motivations change as your company grows, which I think is an important piece of that conversation. It’s not static, it’s really dynamic and it’s an interdependent between who you are and what your company is doing and what your company needs. So yeah, more on that later at some point.  

Rob Walling:
And then our last talk of MicroConf Europe 2023 was from Steven Craven and he told his founder story, him and his co-founder story, of going from launch, to 50K of MRR in a week. And they had an existing audience… The company’s called Stridus and it’s software for personal trainers. They had an existing audience, but it wasn’t huge. It was like single digit thousand emails and I believe maybe 10,000 Instagram followers, somewhere in that 10 to 15,000. But they just did, they executed on a B to C-ish launch with a B to prosumer audience. Really, right? Because personal trainers, I would not say are straight B2B, they’re more like B to Prosumer. Anyways, they just executed really well, and he told the story of them acquiring the business and then having the audience and building, having this amazing launch week.  

Dr. Sherry Walling:
It was a great talk. It was very motivational, very inspirational, helped people see what could be possible. It was also kind of a stressful story, which is also very representative of how these big launches go.  

Rob Walling:
Yeah, he said, he showed a picture of a Porsche 911, and he’s like, I had worked for years, I had an agency and saved and saved to buy that car, and I had to sell it to pay the bills of his company at one point. And it just breaks your heart where it’s like, oh, you could say, oh, poor baby had to sell his nine 11, but he earned that 911, it’s not like his daddy gave it to him, right? He had bought it with his… We know what that feels like to have to make a sacrifice like that. And that’s where MicroConf today, in terms of the content, the talks, focuses a lot on frameworks that can be applied, but also founder stories, and that’s where Steven’s story came in. The other four were about, AR’s was maybe a bit more tactical. And then Michelle, you and I did framework talks that I think are high level and can be applied for years, and I think those frameworks should live on, to be honest.  

Dr. Sherry Walling:
Tactics, strategies, inspiration in relationship.  

Rob Walling:
I mean, that’s it. We covered the four, right? The acronym, S-T-I-R, strategies, tactics, inspiration in relationships  

Dr. Sherry Walling:
STIR?  

Rob Walling:
I know, It’s like the… It really is. I came to Xander with that at one point.  

Dr. Sherry Walling:
You might need to work on that a little bit.  

Rob Walling:
I was like, RITS, SRIT, STIR and he’s like, “Oh.” I was like, “Dude, I feel so bad about having an acronym.” And he’s like, “No, this will actually help us.” He said, even internally, it’ll help the team know what we’re planning events around, so STIR it is. Well, Dr. Walling, really appreciate your time on this early Monday morning.  

Dr. Sherry Walling:
Yeah, thanks for including me in the MicroConf experience. It was a great event. You and producer Xander and your new team member, Sonia, nailed it. You did great.  

Rob Walling:
Thanks. Thanks again for emceeing and doing that amazing talk. And these days, if folks want to keep up with you, you’re putting out some great content on YouTube, youtube.com/sherrywalling, and Sherry is spelled like the wine, as well as sherrywalling.com. Thanks again for coming on the show.  

Dr. Sherry Walling:
Thanks for having me.  

Rob Walling:
Thanks again to Dr. Sherry Walling for joining me on the show this week. She is @sherrywalling on Twitter, I’m @robwalling. If we’re not connected, please give me a follow. Thanks for listening this week and every week. This is Rob Walling signing off from episode 684.

Rob Walling:
Problem is if you just listen to your customers and build what they tell you. A, you’re going to build a bunch of crappy features that are disparate and all over the place. And B, they’re pretty much going to have you replicate whatever competitor they switched over from because that’s the tool they used. If they’re non-technical, they don’t think about innovation and how to improve on it. They just think what got the job done at the prior tool. Welcome back to another episode of Startups for The Rest of Us, I’m Rob Walling. Today I answer listener questions ranging from the value of going to in-person events, trying to get feedback from customers who may be reluctant to give it to you, whether to bring on a partner and more listener questions depending on how much time we have. As a reminder, audio and video questions go to the top of the stack. 

You can always ask a question by going to startupsfortherestofus.com and clicking ‘ask a question’ in the top nav. Before we dive into the episode, I wanted to let you know about our MicroConf Mastermind program. If you listen to this show, you know that I’ve talked a lot on this podcast about how important masterminds have been to my own success, but finding the right founders for your mastermind group can be very hard. Over the past few years, my team at MicroConf has successfully matched more than 1,000 founders into mastermind groups by looking at revenue, team size, strengths, goals, and several other data points to make sure your peer group is the right fit. Once you’re matched, you’ll also have access to our mentorship series, a three-month program where you can connect with some great minds in sales, business development, marketing and more. If you’re looking for accountability, honest feedback about your business and the opportunity to make new friends that care about your company and your success, you can learn more at microconf.com/masterminds. My first three questions of the day are from the same person, Tom.  

Speaker 2:
Hi Rob. My name is Tom. You’re one of the greatest source of knowledge when it comes to bootstrapping a SaaS. I always listen to your podcast, hear something insightful and apply it to something I’m doing and it brings great returns or teaches me something. I’ve been working on my SaaS in a pretty specific niche in which I have pivoted a couple of times. Previously, I was getting no feedback from my users, so I decided to pivot by going from having a free trial to totally removing that free trial. First question, it is still really hard to get feedback from my customers even though they’re paying. Almost like pulling teeth. It comes in really slowly and it’s all over the place, meaning most features sound like it’s specific to that customer. There’s no common denominator. How should I pick which features to build? Do you think if I increase pricing, I might have a better chance of getting feedback? Maybe the customers don’t know what they want or what is valuable to them unless I just build it for them to see and use.  

Rob Walling:
Thanks for the kind words Tom, as well as the question. This is an interesting one, it’s certainly something that people face. I have a few thoughts on it. I think that it really, really depends on the space that you’re in or really the customer that you’re serving because if you’re serving product people, software engineers, designers, they will give you feedback. They will have a lot of feedback about how you should re-architect your top nav because it doesn’t make sense to their “expert eye” and tell you things like how you should never have a button with rounded corners or you should ALWAYS have a button with rounded corners. Doesn’t sound like you’re catering to product people. If you’re catering to construction CEOs, lawyers, anyone who is non-technical, insurance agents, they know when they have problems, they’re not going to know the solution and they’re certainly not going to know the way to implement a solution in your product. 

So I think the way I’d be thinking about this is there’s no way they’re going to tell you what features to build, but what people will say is, “I have this problem and can you add a button to do it” right or “can you add a setting to do it?” And of course you always have to think about, well, is that the right way to solve it? But if you’re not even getting that, and I think your quote was, “it’s like pulling teeth. It comes in really slowly and it’s all over the place”. So this is where in the early days it sounds like you haven’t yet… You either solved everyone’s problem, maybe you don’t need to even write code anymore. Think about that. If churn is low and when people sign up, they convert from trial to paid and you’re solving a problem, why do you need to build any more features? 

It’s an interesting thing as a builder that we tend to think that adding more features is going to move all the needles in all the directions. Realistically, if you’re not losing deals to competitors and your churn is low, stop building. This reminds me of the SaaS app I owned right before Drip called HitTail. It was mostly a feature. It was an SEO keyword tool that you installed a JavaScript snippet on your website and it looked at where you were already getting traffic from but weren’t quite ranking for, and it made suggestions. It was kind of one feature, these days that would be a feature of Ahrefs or SEMrush or Moz. We just stopped building new features at a certain point. The product itself became mature and that was a luxury because it meant I didn’t have to write code and it meant I didn’t have to hire developers to do it. 

But the thing is if you’re churn is high, meaning you haven’t yet built something people want and are willing to pay for, or if you are losing deals or customers to competitors. Well that’s a place to look right? Is oh, look around at the competition. You don’t have to copy what they do, but you at least know which problems are they solving. So if you have competitors that do what you do plus three or four different adjacent things, do you start peeling those off? If you have built your own category and you’ve created a category where there is no competition, that’s a challenge and that is why doing so is such a hard road to travel because people can’t bucket you. They don’t instantly look at your software and say, “oh, well you’re an email service provider” or “you’re ACRM” or “you are a cold email tool” or “you’re a thing that I ran my business on” or “a way I build landing pages”. 

These are categories in each of our heads. If you have gone off and are attempting to create your own category and it’s truly a novel tool and your churn is relatively high and people aren’t telling you what to build, it’s likely you just haven’t solved a problem that people are willing to pay for basically. And I feel like you as the founder, if that’s the case, you have to have some type of vision for what you’re doing and why it’s important. And there’s this balance when we’re building, I know everybody says, talk to your customers, listen to your customers. The problem is if you just listen to your customers and build what they tell you, A, you’re going to build a bunch of crappy features that are disparate and all over the place. And B, they’re pretty much going to have you replicate whatever competitor they switched over from because that’s the tool they used. 

If they’re non-technical, they don’t think about innovation and how to improve on it. They just think what got the job done at the prior tool. This was a big problem for us in the early days of Drip, people would come over for Mailchimp and all their feature requests were just things that Mailchimp already did. Each of those I had to evaluate, do we build that or do we say no because it was not a foregone conclusion. So this is where founder vision and your kind of own filter of where you think you’re headed in the space needs to come into play. You had a second part of the question, which is do I think if you increase prices, you might have a better chance of getting feedback? I don’t think so. I don’t know. If you can increase prices and you don’t increase churn, then do that whether you get feedback or not because then you’ll make more money. 

And then as I said in the SaaS playbook, the second order effect is now you have more money to market, you have more marketing approaches available. But I don’t know, I guess you’re thinking raising the price might improve the quality of your customers. I don’t know. I’m struggling with that. I don’t think it’s going to have an impact honestly on people giving you feedback. If you are in fact serving non-technical folks. I think your last sentence of your voicemail was “maybe the customers don’t know what they want or is valuable to them until I just build it for them to see and use”. If they’ve never built a product, if they’re not developers, designers, that’s probably correct. And so what you have to do though is you can’t just make [inaudible 00:08:09] to build. You have to find what is the problem they’re trying to solve? What is the job to be done of your tool? 

And if you already solved that pretty well, you get to decide, well, do I just add more people to this tool and grow it? Again, HitTail went up to $25,000 or $30,000 a month. It was a great little business. Had high churn for reasons we could go into, but if you don’t have to keep building then don’t. Or if you realize that they are solving other problems with other pieces of software, you could start to add those categories in and build out a bundled product that could essentially save them money if they start canceling other services and they give more money to you and they can cancel these other services. And now for Tom’s second question.  

Speaker 2:
Next question. I have a customer who wants to become a partner. He is probably the most responsive and engaging of my customers. Initially he wanted 10%, which is the amount I was thinking also for an advisor type of role. However, he wants 40% now for a bigger role. Basically being a product owner doing sales, demos, et cetera. I think the most I’m willing to give him would be 30%. He wants to build this, he says with features specific to him, I’m not sure if I want this. This is what happened with my previous partner who was in this industry that my SaaS is built for and I had to redo a lot of things to make it usable for other customers. Should I bring them in and what should I give and should I give in and give him the 30% or should I just keep building features based on my customer’s feedback even though it’s pretty slow?  

Rob Walling:
Okay. So there’s no way I can give you advice on what you should do, right? This is your company, this is your equity. And without knowing every detail, I could never venture to say you should do this, but I can tell you based on what you’ve said, how I would think about this. So if someone is going to come on as an advisor and is not going to work on or in the business, usually advisor shares are 0.5% to 1%. I’ve heard of up to, well there are some internet influencer people who are basically affiliate marketers that will take more than that, but even that number getting up, 5% 6% starts to get high. So when you say that he wants 10%, that is a lot of equity in a company and I wouldn’t personally be giving that away unless someone was putting in a lot of time on the business or they were buying in, they were actually putting cash into the business. 

And so when I think about someone wanting 30% or 40%, there’s a big… It depends. Are you doing $1,000 a month right now, $1,000 MRR? Are you doing $50,000 MRR? Are you doing a million? Because a business is worth is based on your revenue and the growth and a bunch of other factors. And so if you could raise funding right now, not sell. Liquidating a company is always a lower price than what you could raise funding at. So if you can raise funding at let’s say a $5 million valuation, maybe you could liquidate the company today for a million or 2 million, but realizing that the investment in your growth is betting on the future, right? So they’re saying, “we bet that you are going to get there to where you are worth $5 million”. So in this case, if he’s putting in time and/or money, you would probably be thinking about the fundraising valuation. 

And if you look around at Accelerators for example, they will fund TinySeed, Y-Combinator, Techstars, 500 startups. They’ll fund a company doing a few thousand dollars a month at a $900,000 to $2 million valuation. So like 1 – 2 million, it gets a little lower, little higher, but those are the valuations. So when you think about giving someone 30% of a company, if this has the potential to be a multimillion dollar company, that’s a lot. And so I would want to be very certain that their equity vested over four years with a one-year cliff, so they got zero equity upfront and then it would vest over those four. And I would want for 30% that person’s got to work full-time on the company or as much as I am, I guess if we’re both nights and weekends, then maybe that’s where it is right now. But yeah, you have to be really certain, you’re giving them a 30 year company. 

This person better be baller and there can be no doubt. They have done what you want them to do in the past successfully, grown companies, done all kinds… Way more experience than just, “oh, I want to do this and I’m willing”. For me, that’s not something I’d be willing to give away that much equity for. Frankly, I don’t know many people that I would be willing to give away that much equity in my company. Again, it depends on, but if he’s willing to put in cash and buy into the business and whether it’s give equity or advice, that kind of changes this and it also changes based on your stage for sure. So it’s a big question and I hope my thoughts were helpful. And now let’s move on to Tom’s third and final question.  

Speaker 2:
Last question. There’s a trade tool coming out for the industry that our SaaS product serves. My potential partner doesn’t think we should go to it until we think we have achieved product market fit. He thinks we’re 90% of the way there and wants a really polished product before we go. He doesn’t want to preview any potential features we have on our roadmap to potential competitors. I think we should go anyways, not to do sales, but to talk to people and network. What do you think? Again, thank you for your time and everything you do.  

Rob Walling:
Me, I’d probably go to the trade show. I think learning is so important early on. I am less concerned about competitors and features, unless I have some super crazy innovative thing. If I’m at a trade show, aren’t I going to be able to tell if they’re a competitor or not anyways? Usually you have a badge with a company name, and I should know my competitors, so I would think I just wouldn’t give them the demo. And I don’t know, upcoming features is, roadmap features, is another thing. I mean, I actually used to not give away roadmap features because there were a few players that were basically watching what we were doing and try to replicate it. And so I didn’t want to give them the heads-up. But without that, I’m usually less worried about competitors replicating my features and trying to I guess out innovate me because if you’re the one innovating than they can never get ahead of you. 

I love the idea of getting into a trade show and talking to real humans and seeing real reactions of real potential customers. Even if you know you’re at 90% product market fit and you have to say, “Hey, we are building this stuff right now that’s going to do X, Y, Z here’s the next couple things”. And that’s what it takes to get them excited. I want to see if they get excited, right? I think there’s a ton of value in face-to-face. As much value as there is in doing Zoom jobs to be done interviews or Zoom mom test interviews, the next highest fidelity beyond that is in person. So I’m a big believer in them. I’ve done a couple of them in my startup journey and they were always fun, exhausting, and I learned a ton. So that is my take. Obviously you have to make your own decision, so thanks for those questions Tom. 

Finding the perfect software engineer for your team can feel like looking for a needle in a haystack and the process can quickly become overwhelming. But what if you had a partner who could provide you with over 1,000 on demand vetted senior results oriented developers who are passionate about helping you succeed. And all that at competitive rates. Meet lemon.io. They only offer handpicked developers with three or more years of experience and strong proven portfolios. 

With lemon.io, you can have an engineer start working on your project within a week instead of months. Plus you won’t waste your time on candidates who aren’t qualified. Lemon.io gives you easy access to global talent without scouring countless job boards and it’s more affordable than hiring local talent. And if anything goes wrong, lemon.io offers swift replacements. So it’s kind of like hiring with a warranty. If you need to grow your engineering team or delegate some work, give lemon.io a try. Learn more by visiting lemon.io/startups and find your perfect developer or tech team in 48 hours or less. As a bonus for our podcast listeners, get a 15% discount on your first four weeks of working with a developer. Stop burning money, hire dev smarter. Visit lemon.io/startups.  

Speaker 3:
Thank you, Rob, for your podcast. I just listened to number 671, and I usually do that while I’m working out. And you usually have a good nugget of information or something that slaps me upside my head to say, “Hey, keep going”. I have a e-commerce marketplace website that I’ve built, not SaaS but WordPress, and I even gone through the whole process of having somebody build it, didn’t like it, and I went and learned WordPress over the last decade and built it again myself. So I think I’ve added some skills, some hard work into it. And then I sit there and do some videos that go along with my website. It’s called tweetperks.com. And so I felt that I done a good job, but then I listened and you said it’s not luck. This is podcast 671 over the last decade and I’ve done minutia of that in video, and that’s one of my strong points is video. 

So I need to keep going with it, keep pushing. I see there’s a light at the end of the rainbow there or light at the end of the tunnel, bucket at the end of the rainbow. I’m not sure what’s in the bucket. My goal is to be acquired and then be able to provide for my family and then do some angel investing. I’m at the age where I’m retired from most of my work stuff. But this is something I do and what I’ve been doing for the last 10, 12 years, building this website and enjoying it. But I really need to keep it going. And you on your podcast, keep me energized, give me a nugget, a slap upside the head now and then, and it’s something that I needed. So thanks very much. I appreciate it and keep up the good work and maybe someday I’ll get on your podcast when I’m acquired.  

Rob Walling:
Thanks for sending that in. Nothing to respond to here other than I really appreciate it and I always love hearing folks getting motivated by the content that I’m putting out. So if you do in fact get acquired at some point, please reach out and we’ll see if it makes sense to bring you on the show. My next question is from Olivier and it’s about thoughts on pre-launch discounts.  

Speaker 4:
Hi Rob. It’s Olivier from [inaudible 00:18:03] a catalog of embeddable widgets. We have built an MVP for [inaudible 00:18:07] and now I’m focusing on building a pre-launch landing page. Visitor can sign up to our email list by answering one or two questions and then when you’re done, we intend to propose a limited time pre-launch discount. Since it’s my first time building a SaaS product and I don’t have a particular network advantage at the moment, I’m a little bit weirded out by charging our customers in advance. Your new book, the SaaS Playbook, which is incredible by the way, inspired me to do a Kickstarter even though it does not seem to work well with software. Finally, our company is based in Canada, and I was wondering in which currency to charge our customers. Looking forward for your feedback. And keep doing what you do and take care of yourself, the community needs you around for as long as possible.  

Rob Walling:
Thanks for that question. Thanks for the kind words about SaaS Playbook. I’m hearing it is incredible, of course makes my heart sing. If you haven’t left a five star view on Amazon, I would totally appreciate it. I’m trying to get to 100 5 star views. But to answer your first question, it’s about a limited time pre-launch discount and you don’t want to charge customers in advance. Yeah, I never charge customers in advance. I know we have some folks who do pre-sales. There was a debate for a while about should you pre-sell or should you just get pre-commitments? I always got pre-verbal commitments and then I let people try the product. And then I remember the first 10, 20 customers of Drip I said, “I’ll start charging you when you get value out of it”. And the nice part, I was super involved with them, and in terms of onboarding and getting them going. And the cool part was I could then start to realize, oh it does take a couple of weeks to basically try Drip out. To get in, write the emails, add the JavaScript widget, do the whatever else, and that started informing how long our trial should be. 

So it was actually helpful research for me. So I don’t feel like you need to charge from day one upfront. I do think you need to be pretty mindful about who you let in because you will get some people who will waste your time or who I guess won’t have opinions that will match up. Some people get really opinionated early on that you should take it in a direction. If you’re like, you know what, that’s not where we’re building. Those are the folks you’re looking to have conversations with to figure out which direction are you going to take it because there’s going to be a lot of disparate information, a lot of conflicting information, a lot of noise. And if you let five different customer types in, it’s going to be all over the place. And so trying to focus on one or two ideal customer profiles, or ICPs, I think will be a benefit to you. 

One other comment is you mentioned having a pre-launch limited time discount. I would tend to maybe not do a discount and to instead say, “what else can I give them to keep the price what the price is?” But say you get complimentary onboarding, you get a free copy of my book, you get one-on-one call with me and someone else to help with strategy sessions. There’s all these things you can add. I just don’t like discounts. I think discounts are, this is going to sound mean when I say it, I think discounts are lazy. I think discounts are easy to knock some money off it, give them a lifetime discount, whatever it is. If you need to do it, you need to do it. I won’t say I’ve never discounted anything. We totally have. Well, here’s an example actually. On my Kickstarter, and then when I was selling my book pre-launch before it was printed, instead of saying, “oh, you just get the book cheaper”. 

I said, “well, you can buy bundles”. That’s it. I didn’t sell the book individually. So you got, instead of paying let’s say $25 for the hardback or the paperback, instead of discounting that down to $15 or $20, what instead I said is, “oh, if you buy the paperback or the hardback, you also get the audiobook and you pay $30”. So it’s actually an upsell in a way, if you think about it. I got five more dollars and I get to give them a digital copy of the book. That’s the kind of stuff I’m talking about. Now you don’t have to bundle it exactly like that, software is different. But that’s the thinking that I like to go into time… I love time limited deals. I love the time pressure, I love the rewards, but I like to think what more, what else can I give them rather than how do I make my stuff cheaper? 

And then Olivier’s last question was, well inspired you to do a Kickstarter, which is crazy. I haven’t really heard people do that for software, so I’m curious how that turned out. But you said finally your company’s based in Canada and wondering which currency to charge. I guess it’s where are your customers based, if they’re all Canadian than Canadian dollars? And if there’s going to be a mix, certainly if they’re going to be in the US, you probably want to charge USD. It’s just a stronger currency, so why not take advantage of that? Because we’re used to paying in USD. And then the question is, well, what about my Canadian customers? Do I charge them in USD or Canadian dollars? And that one, I honestly don’t know what I would do. I would prefer to charge everyone in one currency of course. I don’t know how many problems that’s going to cause you until you try to do it. 

I don’t know how many complaints you’re going to get until you try to do it. Are you going to feel really expensive to Canadian companies or people that are buying this? Maybe. And if that’s the case, then you kind of have to charge two different currencies. But that’s probably something for you to either ask in something like MicroConf Connect, where there are more than 5,000 other bootstrap founders who have thought about exactly this, right? And people who have tried and failed and made mistakes, and get input. I think there’s a pricing channel in there for example, and this could be a good question to ask and get several viewpoints from folks who have tried this and been successful. So thanks for the questions, Olivier. Hope that was helpful. My next question is anonymous and it’s about productized services and pausing.  

Speaker 5:
Hi Rob and whoever else is on the show this week. I would love to hear you guys’ opinion on productized services and pricing. Recently, I became aware of some designer websites where they’re selling unlimited requests, but they fulfill them one at a time for a subscription fee that they allow their customers to pause, and they’ll track the days. So if you pause on the 15th, you’ll get 16 days remaining when you un pause it until you have to pay the next month. I love this idea because then it lowers the budget required for some companies to hire you. However I’m afraid that if I were to adopt such a policy or a thing, if I were to make a productized service which I’m considering doing, that the income would be very volatile. What are your guys’ opinions or concerns about this? This is my first foray into this kind of work. That’s all I got. Thanks so much.  

Rob Walling:
Okay, so productized services. If you’re wondering what my thoughts are there, I like productized services. I think they’re a great stepping stone. Nice step two business on your way to creating a standalone SaaS, if that’s where you want to go. My thoughts on pausing are that I wouldn’t start a business that allowed pausing. That just means it’s really a high churn business. It is a business that probably shouldn’t be a subscription in reality, and you’re forcing it into the subscription model. And to adopt a pausing feature really does dilute the benefit of recurring revenue. And you essentially no longer have that if people can just pause it all the time. So should I say no one should ever do that? No. I’m sure it’s a necessity. I’m sure if you build this type of business, it becomes something you want to do because otherwise your churn is 20% a month and that feels painful. 

But also pausing is churn, if you think about it. If you’re looking at revenue churn, which is what I remember, then the moment someone pauses they’re no longer paying you. And then later on you can either count it as like… This is weird because you basically have a customer, if you count them as a customer, that’s paying you $0. And so it would be churn down to or contraction revenue down to zero, and then expansion up to whatever they’re paying you. That would probably be the technically correct way to do it. I don’t know of any metrics tool that will actually do that correctly, you probably have to finagle around with things. So for me personally, I don’t love it. I would be looking for a business that is more of a true recurring base. One other thought you can think about is doing annual only and then people pay for the whole year. 

And if they were going to pause it during the year, if they only need it five, six times a year, they just pay the price for the whole year. And that means they don’t have to deposit because when they aren’t getting value, they don’t cancel. And then they come back and it’s just this resource that they have for a full 12 months. And that’s how I would think. It’s not to combat churn per se, but it’s to kind of even out their needs so they don’t feel like they’re getting taken advantage of in the months that they don’t use it. But if you pay for a whole year and you don’t use it for a month here and there, it doesn’t feel the same way. So thanks for that question. Hope it was helpful. 

My last question of the day is about equity, it’s about advisor equity and anonymous asked, “do you have any episodes on working with fractional CTOs and how much equity to grant? I’m trying to determine this question with a startup in MVP / beta at pre-revenue”. So usually, I mean, this is kind of an advisory role it feels like. Well if they’re fractional CTO, you don’t have to give many equity. And I do wonder why you would do that. Is there a compelling case to do that? Will they not work with you unless you give them equity? Or are they lowering their rate in order to get equity because that’s a good deal for you. And if they’re not, then don’t give them equity. But if you get to the point where you’re going to give them equity, usually I think of it as an advisory portion of shares, which is usually as I said earlier 0.5 to 1%, and it usually vests monthly over two years. I’m saying usually, these are rules of thumb. There is no cliff on these, and that’s how I would think about it. 

Again, that’s how the rule of thumb works. You can obviously adjust it up or down depending on the value that they bring to the business. So thank you for that question to round out this episode. Hope you’re having a great week this week. Hope this episode maybe sparked something in you as you’ve listened to it, to want to go and market it harder, to build another feature, to onboard another customer, and to keep pushing forward in your own business endeavors. It’s great to be with you this week and every week. This is Rob Walling signing off from episode 683.

Rob Walling:
This is Startups For the Rest of Us, I’m Rob Walling. This week I talk with Alex Theuma, the founder of SaaStock. We talk about a myriad of topics around trying to bootstrap an event and how hard that is, the pros and cons of large events versus small startup events. And at the end we share a couple memorable mishaps or war stories from years of running events. I’ve actually wanted to attend a SaaStock for the past few years, and there always seems to be a scheduling issue on my end that has kept me from attending. Just to check it out, a big event with a lot of people, multiple stages to see and experience what I’ve heard a lot of folks talk about. So hopefully this episode of the show brings you some insight, some inspiration, and maybe a little motivation to check out SaaStock in the future. 

Before we dive into the episode, I wanted to let you know about our MicroConf Mastermind program. If you listen to this show, you know that I’ve talked a lot on this podcast about how important masterminds have been to my own success. But finding the right founders for your mastermind group can be very hard. Over the past few years, my team at MicroConf has successfully matched more than a thousand founders into mastermind groups by looking at revenue, team size, strengths, goals, and several other data points to make sure your peer group is the right fit. Once you’re matched, you’ll also have access to our mentorship series, a three-month program where you can connect with some great minds in sales, business development, marketing, and more. If you’re looking for accountability, honest feedback about your business and the opportunity to make new friends that care about your company and your success, you can learn more at microconf.com/masterminds. Alex, thanks so much for joining me on Startups For the Rest of Us.  

Alex Theuma:
I am very excited to be here, Rob. Thanks for having me.  

Rob Walling:
Absolutely. It’s a long time coming and as folks heard in your intro, you’re the founder of SaaStock, which I think is interesting overlap with MicroConf, or not even overlap, but just we’ve traveled such a similar path in building our events. And this podcast SPR out of a blog that became a, should we all get together in a room? So we started a MicroConf in 2011 in Las Vegas and it seems like from what I know about your story, perhaps you have similar early stages. And for folks listening, we’re going to talk about SaaStock. Really, I like inside baseball. 

You’re an entrepreneur and a founder, and that’s what this show’s about, is being an entrepreneur and founder. So we’re going to hear stories about things you’ve learned, missteps, even just thinking about bootstrapping a SaaS, we talk a lot about. How the hell do you bootstrap a conference? Just so few of us do it, right? So with all that said, I’d love to hear the early stages, how did you bootstrap a first event and get people to come? Because when you don’t have a brand name, no one will give you the time of day. People are not buying airline tickets and they’re not booking hotels.  

Alex Theuma:
Yeah, yeah, yeah, good question. Yeah, I think we’ve traveled an almost identical path in building MicroConf and SaaStock, right? So you’re right, it came from a blog. I started a blog called SaaScribe in 2015. The idea there was to create a community driven blog for SaaS founders that are growing their businesses, SaaS companies that are growing their businesses. I thought I identified a gap in the market there and to get some experts and influencers to create some content as I’d never run a SaaS business myself, so I’m not the authority to tell people how to do it. So instead, I recruited people to write content for us without charge. I mean as in I didn’t pay them anything. They did it for the good of SaaS and we get their name out of there and they bought into the why. So we had the blog and three months later it kind of took off a little bit. 

It resonated, I was getting a lot of emails from people saying, “I like what you’re doing. I’m rooting for you,” this sort of thing. Three months later, I started the podcast, The SaaS Revolution Show, which is happening still eight years later. And then a few months later, then I started doing local meetups, and it was then when I was having the face-to-face conversations that people were saying, “Hey, look, we’d like a bigger thing.” We’ve got 120 people here today in one of the meetups, which was great, and people travel from all over the UK. It’s like, “We’d a big thing in Europe and you seem to be the person that is probably primed to do it.” I was like, “Oh, really?” Yeah, I’m looking for a way to get into this full-time because I was really enjoying it. I had a side hustle… well, that was the side hustle. 

I had a full-time job, but this was the thing I was trying to explore as to could this help me become the entrepreneur that I finally wanted to become after many years of issuing many ideas. And so that groundwork, I think to your question about how do you bootstrap it and get the credibility and authority. It was from doing the blog posts or running the blog, getting on people’s radar, interviewing founders on the podcast and VCs, that enabled me to have a little bit of authority and credibility. To the point where I think it was in November, maybe a little bit before in 2015, where I met with, I think it was Nick from ChartMogul at the time and their business subscription metrics platform for SaaS businesses. And I had a conversation with him at another conference, I believe it was Web Summit, and said, “Look, people want me to build this SaaS conference in Europe. I’m thinking about doing it.” And he said to me, “Look, if you do it, we will sponsor.” 

I didn’t forget that. And then I kind of went forward with the project. I was starting to build the website, I found the venue, I found the date. As soon as I had that, I went back to Nick and said, “You said you were going to be my… sponsor this, I’ve got a date venue. It’s happening in the RDS in Dublin.” And he came back and said, “Yep, we’ll do that.” And he put his money where his mouth was and became our first sponsor. Maybe one month later, I closed a deal with Patrick Campbell, who was the main competitor, ProfitWell, of ChartMogul. And effectively from there, we were customer funded bootstraps from that point on. And when we started selling tickets in January, so we waited over the Christmas period, the audience was the people that had come to the meetups that was subscribing to the newsletter, reading the blog, that was listening to the podcast. 

And so there was an active audience there of people that had wanted and asked for this conference. I think the first day we sold like 37 tickets, and I saw this spike of revenue and I was like, “Great people actually do want this thing.” So that enabled me to have the runway really to I guess build this for the next nine months and pay myself and then eventually start to bring some other people onto the team. But there certainly were a couple of months where it was very close coming to the end of the month where I was running out of money and I was like, “Oh, I’m not going to be able to pay myself next month.” And then suddenly you get a deal in at the end of the month and like, “Phew, stress over, I can feed the family.”  

Rob Walling:
Right. Well, it seems like you were ahead of us when we started because I didn’t realize that most events, all events need sponsors in order to make them happen. I was under the impression that, “Oh, when people charge a thousand dollars for a ticket or $500 for a ticket, they sell those tickets and that pays for the event.” But no, they’re all subsidized by sponsors and without sponsor subsidy, you have to charge way more. The events are just much more expensive. And so we figured that out the first year and then the second year realized that we’re going to sell sponsors. But you were ahead of that game. It sounds like the sponsor was the first thing. I wonder if that comes from being… because your background is in sales, right? Like enterprise sales?  

Alex Theuma:
Yeah. Yeah, I think so. When I left sales or selling other people’s software, I was like, “Oh, so glad to see the back of sales. I’m done 11 years of sales, I’m done.” But obviously the first thing that I had to do as an entrepreneur was sales and generate revenue. So I wasn’t quite done, but it was quite different when you’re selling your own product and it’s something that you passionately believe in, and also you had to make it work, right? Because I left my job to go all in on this. Gemma, my partner was six months pregnant or something like that. We had no income in the household, so I had to make it work. 

So there’s nothing like something like that to give you that drive, a deadline of knowing when you’re going to run out of money. So I got into it and just I guess through the conversations… And I can’t really remember Rob, whether it was a real deliberate strategy, but to go after the sponsors first. But it just so happened that I had that conversation with Nick, which then gave me, I think it was like 12,000 euros or whatever, to then plot on for the next few months. And then again started to get that in, and I think we ended up or I ended up doing about 35 sponsorship deals for the first year. And it was about 50/50 revenue on sponsorship and tickets for the first year.  

Rob Walling:
That’s incredible. Wow. And there’s this old saying, “Start an event, they said. It’ll be fun, they said.” After we ran the first MicroConf, closing party night, I was telling everyone, “Never doing this again. This is it for us.” For us, it was a side project. We bootstrapped it, we made money on it, made thousands of dollars that first year, but it was definitely not something that I wanted to do again because of how stressful and how much work it was. And I was like, “I cannot justify this.” So then people were like, “No, you have to do it again. This was the best event I’ve been to.” 

It really resonated with the folks. I mean, our first event was 105 people. It was a very small event. So I’m curious to hear your experience of, for you, after running that first event, were you wide-eyed, like, “Oh my gosh, this was so much more complicated and difficult than I thought it would be.” Or did you go in eyes wide open in the sense of, “Yeah, it’s going to be tough.” And when you came out the other end, you’re like, “Well, we broke even or made some money. That’s a big win and we’re going to do it again next year.”  

Alex Theuma:
Yeah, good question. It sort of makes me smile because certainly the first event, I was walking around super tight. I didn’t sleep the night before. I think I actually probably had a panic attack the night before. And in largely, I think it was because we did lose a good amount of money, it was about 60,000 pounds, something like that. And I was like, “Okay, well, we’ve lost all the money. I’m aware I’ve lost the money. How am I going to pay that back?” And so I didn’t sleep very well at all. And then I went to the event and then the event was running, so the event was running kind of without me. After I’d done the opening remarks, you’ve got the production company that’s running the event. Everything seemed to be working fine. I’m walking around speaking to people and everybody’s like, “Alex, you look terrible. You look terrible. Are you not having a good time? You look terrible.” 

Without them knowing the reason that I looked terrible was because I hadn’t slept the night before because I’ve lost this money. But when the event was done, everybody, I remember having a pint of Guinness outside the RDS and speaking to people and just trying to come to the terms with, “Okay, we’ve lost money. We need to figure this out.” And everybody was like, “This is amazing. What’s the plan? Next year double in size, do this, et cetera, and so on.” And I was like, “Well, look, I know one thing for sure is I’m not taking a holiday tomorrow. I need to go back to the sponsors and start selling them on next year again.” And that’s pretty much what I did. So over the next 30 days, I rebooked about a hundred thousand pounds worth of repeat revenue from the sponsors. 

And then that gave me a little bit of, more peace of mind around how I can pay back some of the loss from this cash in the bank as such, and then just repeat. And that’s what we did. We basically, I put the finger in the air and said, “Let’s double in size next year.” And we almost doubled in size year-on-year. And again, it was just another 12 months of hard work and actually 12 months on one event, you don’t need to do that, right? We’re kind of now more on a six-month cycle per event, but I used to spend 12 months, five tweets a day than doing… you’re kind of doing everything, recruiting the speakers, doing the sales. That’s what you had to do for the first event. Now I’ve got a team of people doing that, so you don’t need to work six months on it.  

Rob Walling:
Are you tired of searching endlessly for highly skilled software developers, CloudDevs is your solution. Gain access to over 8,000 pre-vetted senior devs distributed across their Latin America and global talent pools. All of their remote developers work within your time zone and can get onboarded within 24 hours. The CloudDevs team can help you recruit full-time or part-time hires, as well as project-based freelancers. And every hire comes with a week-long free trial, making sure you get the right person for the job. All of our listeners get a 15% discount on their first month of collaboration. Hire trusted tech talent efficiently without breaking the bank by visiting clouddevs.com. 

So I want to ask you a bit about your thoughts on pros and cons of event size or event type. And the couching of this question is most people listening to this podcast are familiar with MicroConf, our flagship event in the US. It’s in Atlanta here in April. It was in Denver last April, and then we have a flagship Europe event. It’s in Lisbon actually in a couple of days as we’re recording this. We are single track, we are 150 in Europe and we peaked at 300 in the US and then COVID, so now we’re at about 250, I think Denver was, and hopefully Atlanta will be that as well. And we have five or six speakers and we have a lot of activities and networking and this and that, two and a half day event. 

And there are certain pros and cons of that format. The pros, it’s super intimate. There’s a lot of other stuff versus a SaaStock, which I think you were saying it’s several thousand attendees, it’s multiple stages. There’s a bootstrapper stage, there’s a venture stage, a growth stage, whatever, all these different tracks. In your mind, what are the pros and cons of that model, of these contrasting these two models? Because I don’t believe either one is better than the other, but I do wonder as someone who runs a big event and has now for many years, how do you think about that?  

Alex Theuma:
Yeah, it is a good question. I guess from the very first SaaStock, I did think about how do we grow this? I wanted to have a growth business and not just have the conference that… and there’s nothing wrong with this, but that was kind of the same size doing the same revenue each year. I wanted to think big, but also I think during every single event, and certainly in the early years walk around and people are saying, “This is the perfect size at 700, don’t grow any bigger.” At 1500 they said, “This is the perfect size, don’t grow it any bigger.” And I think they stopped-  

Rob Walling:
We get that too.  

Alex Theuma:
Yeah, they stopped-  

Rob Walling:
We get that at 150.  

Alex Theuma:
Yeah, they stopped saying that. Well, 150 apparently is the perfect size where people, everybody can connect with each other, right?  

Rob Walling:
It’s Dunbar’s number [inaudible 00:14:56].  

Alex Theuma:
Yeah. You certainly sort of lose that at SaaStock, but by design, I’ve always thought, “Okay, as we scale the event, how do we keep the people happy that perhaps smaller events and what do we do there?” So there’s a lot of curation and actually SaaStock, if you deconstructed it, could be many mini events and one big event put together. So on the first day we do this thing called SaaS City, which is a one-day accelerator for your SaaS. I think this year it’s about 10 different workshops with probably 50 to 60 people per workshop. Then we do pub crawls, and then there’s an opening party with about a couple of hundred people. So with the workshop sort of size, there’s nothing really daunting about sitting with 50 of your peers in a day long workshop that’s being led by some of the best experts in the industry. 

Then at the main event itself, that’s when it gets a little bit more of the scale, but then we look to have all these different stages in terms of content for everybody. So like you said, the bootstrapper stage, that’s a stage for about 150 people. And again for an audience of bootstrappers and generally those that are doing anything from zero to a hundred million. But I would say the majority of our speakers will be under 10 million in revenue and be sharing stories of how they got to 10 million. We’ve got a few, Gregory, I can’t remember his surname, the CEO of MuckRack, they’ve got to 50 million ARR. Great to be able to share those kinds of stories as well. We have an accelerate stage, again, for those that are really just at that really early traction stage. We’ve got the expo, which is obviously a big part of it and the showcase. 

And then what happens, there’s a bit of an ecosystem that’s grown around SaaStock now. So last year, as far as I knew, there was about 20 different side events that are happening around SaaStock in various parts of Dublin. And that includes actually, and I don’t know necessarily how I feel about it, but I think more positive is that people are running their own events. Well, SaaStock is on to capitalize on the fact that we’ve got the audience there and we’re not getting any financial benefit from that. But actually having more side events, I think, and a bigger growing ecosystem, I think really does add value and gravitas to the event. So there’s con there that we lose a bit of sponsorship revenue potentially and that they’re taking the audience out of our venue. But the pro is I think the more side events, so I believe it kind of helps with the gravitas of the event. 

But pros and cons in terms of size, well, I think certainly a con, if we start with that. For some people it can be overwhelming and if you maybe be more of an introvert or not a natural kind of networker, perhaps it can be a little bit overwhelming. When you come in and there’s a buzz, there’s the noise, there’s thousands of people, it’s like where do you start? And maybe you start with just watching a bit of content. But we do try to facilitate all these connections through our smaller events and through the networking app and so on, so you can meet the right tribe. We also do lots of dinners, smaller dinners, whether you’re like CMO, CFO,-CEO, sort of dinners, et cetera, to put people together as well to kind of help with that. I think someone like the pros, if you are used to a smaller event and single track, obviously there is much more I think available if you’re looking at a menu, a la carte menu, you can pick and choose what you want and where to go and what talks to see. 

And even if you’re a bootstrapper, watch a few talks in the bootstrapping stage, but pique your curiosity to look at some of the venture backed companies that have made it to a hundred million and sort of consider. I’ve had a number of conversations with those that are really anti VC over the years, would never take VC money and bootstrap to 30 million in revenue and then finally took VC money. And I don’t know whether they’re happy or not about that, but they did some secondaries and stuff like that. But people do change, and I think SaaStock gives you that optionality to think about that and say, “Well, maybe bootstrapping is right for me now. Maybe we can change in the future and I can speak to VCs, get feedback on the product and so on.” 

So there’s a few things there, but I think there’s a lot, the main pro is a lot of optionality, and you can just do the small stuff if you just want to do the small stuff. But I would always say spend some time before you go to the event and be prepared. I think if with a 150 person event, you could probably just rock up and ideally almost speak to everybody there and not do too much kind of prep. And with an event SaaStock, try and figure out who you want to meet, what talks you want to see, carve out your own agenda. And that’s the benefit of having all these options that you can create your own agenda and not just the one that we put on.  

Rob Walling:
And as someone like yourself who is programming these events, I know you have a team doing that. And when I say program, I mean you pick the speakers and you help them figure out what to talk about. And so you are in essence a taste maker, just like being, you have a podcast, you have a blog, you can set the agenda of what a lot of founders here just like this podcast does and MicroConf does. And I’m always pretty deliberate about what do I think people need to learn this year? And sometimes there’s fortuitous like, “Oh, I recently heard about this amazing speaker and whatever they speak about is going to be great.” 

But oftentimes it’s like, “I think this is a pertinent thing that founders aren’t thinking enough about.” So maybe five years ago or three years ago, it would’ve been like, “People should know enough about Web3.” They don’t want to be sick of it, but I think SaaS founders should know enough. So there should be a talk about that, for example. MicroConf didn’t do that, but AI may be a thing, a topic of today or whatever. I’m curious how you think about that. What do SaaS founders need to know? How do you know what they should maybe be learning at this event?  

Alex Theuma:
Yeah, yeah, good question. So yes, we do have a team that does that. I still advise, and I still use my position to email and book speakers and do introductions and so on. But effectively in terms of our process, so let’s say after one conference finishes, part of the processes that we get on customer calls and get feedback and what did they like, what didn’t they like. And then there will be a sort of research process in terms of what are the current topics for the year and for the agenda. Ahead we will put a steering committee together or a mixture of VCs, bootstrap founders, some operators, and the person who runs our content program. And David will speak to these folks on a regular basis and say, “Who should be speaking? Who are you following? What topics should we be covering? What are you seeing out there in the market?” 

And gathering this data and then compiling this data to then give us a list of options of these are the topics, these are the themes. We also survey our attendees post customer research calls to ask them what are their biggest problems that they’re facing? And if we see a commonality in trends, then we say, “Okay, well look, if you’re saying your biggest problem is fundraising, if we put a lot of content on fundraising and solving this problem, hopefully there’s a real compelling reason for you to come to the event, right? Because we’re actually talking about problems that you have and how to solve them as well, right?” So I think it’s these things and then you mentioned AI, for instance. So definitely we’ve got… actually one of the topics is AI, we’ve got workshops on generative AI. I think it just makes sense. 

It’s certainly one of the buzzy things this year, it’s super topical. We have been to conferences this year, which are similar to ours where AI wasn’t mentioned at all. It’s just the typical, here’s how we got to 200 million stuff, which was still good content, but actually not talking about what’s happening today and in the future and what people need to be considering. So we do need to do that. We haven’t always done that, process hasn’t always been there, but now that’s a little bit of the insight to what it looks like. And just to ensure that we’re not missing any elephants in the room there and just kind of covering the things that people want to hear about.  

Rob Walling:
Last question as we wrap up. I have some more stories from MicroConfs. I’m not going to mention names, but we have had a bottle of hot sauce thrown at a speaker while they were on stage. We have had a sprinkler go off in the middle, of lights heated it up, it went off in the middle of the event, people running out. I have t-shirts made with these things on them, if you know you know, there are others. We had an MC fall off the back of the stage while she was MCing. We have a great audio of that. I mean all these are crazy scary when they happen, but then they make the stories. Just like growing a SaaS company, you get these stories of the crazy customer, the time Russian hackers invaded your this and that. I’m curious, as we wrap, if you have one or two of those, again, no need to mention names, but just some crazy stories because it’s inevitable I think as you run events like this that those happen.  

Alex Theuma:
Yeah, yeah. I would say no major disasters that I’m aware of, but one from last year was interesting. I don’t know if it’s a crazy story, but our friend Patrick Campbell, he did a talk where all he said was the word churn for 20 minutes.  

Rob Walling:
I’ve heard about this.  

Alex Theuma:
Yeah. And it really divided-  

Rob Walling:
There were mixed reviews, weren’t there?  

Alex Theuma:
Really divided audience.  

Rob Walling:
Because it was like an art piece.  

Alex Theuma:
Yeah, yeah, yeah. So the slides were really good, but people were just like, “Yeah, is he really doing this?” And the room was packed, right? But shall we say, I think the majority didn’t really like it too much and we’re not repeating that, but it was bold. We also kind of knew it was going to happen and we’re like, “We’re not sure if you should do that.” But we went with it anyway. So I think that’s one that was pretty interesting and bold by Patrick. And that’s not the reason he’s not coming back this year, but he’s obviously sold his business to paddle and I think he’s busy doing other stuff.  

Rob Walling:
Pretty busy, yeah, I’ve chatted with him.  

Alex Theuma:
Another quick story. I think this was probably like 2019 or 2018, but we do speaker dinners and I have to do two of them. I do one on Monday for the speakers on Tuesday and one on Tuesday for the speakers on Wednesday. So it’s quite a lot of food and often a little bit of alcohol consumed, although I’ve been a bit better at that. Certainly last year after one of the speaker dinner, perhaps on the Tuesday night, went on until midnight and then a good group of us then went on somewhere else. And then before I knew it was probably about 3:30 AM and I found myself with a bunch of speakers who were speaking the next day doing shots in a local nightclub, not feeling great when we were doing the shots. 

And then we probably rolled in about 4:00 AM. I had to be on stage at like eight 30 with one guy that was with me. I could barely open my mouth, it was so dry. And he was fine, he was finished, he was just like… it didn’t affect him whatsoever. And then one of the other speakers that was with us, he then had to speak that morning. I saw him after his talk and he said he vomited at the side of the stage and then one of the other guys that was with us turned sober after that experience. So it was some night. And then I did think to myself, “Is it responsible for me as the conference organizer to be out drinking with the speakers at that time in the morning?” So I haven’t repeated it, shall we say.  

Rob Walling:
Yeah, it’s an interesting thing because, I’ll admit, the first few years of MicroConf, I would often stay up till 4:00 AM 5:00 AM with people because it’s so fun and you’re hanging out and then it would take its toll. I never did it with speakers, I would’ve always been like, “Oh no.” But you do learn these lessons. In retrospect, it’s like obviously you don’t want to do that, but you’re in the moment and you’re hanging out and you’re friends and you’re just like, “Oh, we’ll just have one drink.” So I can imagine that makes a pretty incredible story.  

Alex Theuma:
Didn’t happen to us yet.  

Rob Walling:
Yeah, didn’t repeat it for sure. Alex Theuma, thank you so much for coming on Startups For the Rest of Us. Saasstock.com if folks want to see what you’re building and dig in further and SaaStock on Twitter or X, that’s your account. Any other places folks should head to?  

Alex Theuma:
We’re on LinkedIn. I would say we’re pretty active on LinkedIn and a little bit on X, now I’ve got to get used to saying that. But come to saastock.com, the next conference is 16th through the 18th of October in Dublin. If you haven’t been yet, you’ve got to come once in your life.  

Rob Walling:
Sounds great. Thanks again for coming on the show.  

Alex Theuma:
Thanks Rob. Great to be here. Thank you.  

Rob Walling:
Thanks again to Alex for coming on the show, and thank you for joining me again this week. I’ll be back next week answering some listener questions, still trying to get caught up on that front. Talking about things like bringing on a partner, attending trade shows, offering pre-launch discounts and other questions sent in by folks just like you. This is Rob Walling signing off from episode 682.

Rob Walling:
Welcome back. It’s another episode of The Startups For the Rest of Us. I’m Rob Walling, and in this episode, Ruben Gamez comes back on the show by popular demand and we talk about why launching a second product is usually, but not always, a bad idea. This episode idea comes to us from a listener who sent in a great suggestion about covering this topic. It’s one of those topics you could try to cover in six, seven minutes, like a typical listener question, but it deserves a lot of time. As you can see, this episode is longer than a lot of our standard episodes because there was a lot to fit in. But before we dive into that, tickets to MicroConf US in Atlanta are now on sale, Atlanta, Georgia, April 21st through the 23rd of 2024. Leanna Patch is returning to co-host with me. My hope is that she does not fall off the back of this stage, again. Rand Fishkin will be speaking and it’s generally going to be an awesome event. 

Hope you can join us in atlanta microconf.com/us, if you want to find the full speaker lineup and buy your ticket. This event will sell out all of our in-person events have been selling out. So if you think you want to come to Atlanta and hang out with me and a couple hundred of your other closest bootstrap founder friends, buy your ticket soon. With that, let’s dive into my conversation with Ruben. 

Ruben Gamez, welcome back to the show.  

Ruben Gamez:
Great to be here.  

Rob Walling:
Yeah, it’s always good to have you. By popular demand, you’re back on the show this time to talk about when we should and shouldn’t launch a second product. This topic was actually raised by a listener, Daniel Hoyman, sorry if I’m mispronouncing your last name. But Daniel has written in many times over the years with great suggestions for the show and was talking about a comment, an offhand comment I made a couple hundred episodes ago, to be honest. It was an episode with Jordan Gal, I think it was 499. I quickly said something like, “Oh, launching a second product, it’s usually a bad idea, but you, Jordan Gal, convinced me at the time that this was one of those cases where it’s a good idea.” Daniel was like, “Have you ever thought about recording an episode that actually walks through the pros and cons?” 

Daniel, is the CEO and founder of Intelligent Editing at intelligentediting.com. And, after being a single product company for 14 years, he is actually building a second product as well, has decided it’s the right time. So I wanted to bring someone on the show who, much like you and me and Jordan, have been faced with this decision themselves because I think every founder eventually is faced with it. The question is, what info do they have in their head to make this decision? Because I view it a little bit like a siren song of I’m in a white label, I’m going to translate my app to other languages, these things that are common mistakes in my head. So that’s why you’re on the show, man. Thanks for joining.  

Ruben Gamez:
Yeah, great topic. It comes up a lot. I see it with founders from time to time, so it’ll be good to go over.  

Rob Walling:
This is one of those where I have developed over the years, a default stance, it’s not an always. All caps always, all caps nevers, I don’t do those, but I have a, you really need to convince me why this isn’t the case or why this isn’t how you should proceed. I feel this way about launching a second product. Usually you probably shouldn’t. The odds are good it’s going to take away your focus and be a distraction. We all have shiny object syndrome as entrepreneurs and we want to chase that next thing and the grass is always greener, right? Similar with, I already mentioned, like white labeling. You launch, everyone’s going to approach about white labeling. Almost always a waste of time, not always, but most of the time. Translating your app into another language, I hear this all the time. Probably four or five times a year I’m talking to a TinySeed company and they go, “I want to translate it into Spanish or Portuguese.” 

I say things like, “Are you prepared to do support in Spanish, to market in Spanish, to have all your documentation translated into Spanish, to have the app itself and the error messages translated in this?” It’s just on and on and on. It’s really this Pandora’s box. But again, Jordan certainly convinced me. He was asking my opinion as an investor advisor at the time and I remember at the end of the call being like, “I think you should do this. You obviously feel very strongly and it seems like it could be the right call,” and in his case it was. You have been faced with the same decision. So I’m curious, do you also have a default stance when you come to this or is it purely case by case if founders approach you and ask if they should build a second product?  

Ruben Gamez:
Yeah, when somebody asks me, usually to me I’m leaning towards you probably shouldn’t do it. Most of the time it’s a bad idea. What I noticed, and I don’t know if this is what you’ve noticed too, it’s usually more of a reactive thing. They’re reacting to something. They’re reacting to slow growth or… In some cases it makes sense if there’s massive platform risk and you have to react, that’s sort of like a good time to react to that in that sort of way. But it’s often like they plateaued or they’re stuck and they can’t figure out how to grow past and they suspect that maybe they tapped out the market, that comes up a lot as well. Things like that.  

Rob Walling:
Yeah, that’s what usually bothers me, is it’s usually someone who doesn’t want to face the real problem head on and they’re trying to find another route around it rather than saying, “No, I just need to market more, sell more, change my pricing, find product market fit,” whatever it is that they’re looking for, this shortcut around it, in a grass is greener way.  

Ruben Gamez:
Yes, exactly. That’s the thing, it’s not a shortcut and it’s not easier than the problem that they’re facing, usually.  

Rob Walling:
Right. This is interesting to set the stage here, can we tell the story a bit of BidSketch and SignWell and how you bootstrapped BidSketch nights and weekends, you launched it I believe in 2009, so you’re like SaaS OG, bootstrap SaaS OG here, and you grew it to a point where it was a great income. You own a 100% of the business and then you had a big decision to make at a certain point involving… I mean it was like a rewrite, it was second… It eventually evolved. Can you talk through that piece of it? I don’t remember. Do you remember what year it was even? Was it like 2016, 17?  

Ruben Gamez:
Yeah, I don’t remember the exact year. Part of it was that BidSketch was around for a long time. When we started BidSketch, there was no category of proposal apps. There was for the enterprise, but it looks very, very different. It was like a lot of consulting and the software side of it was very different, to this day it’s still like that. There was nothing in… My initial thought was something like FreshBooks, a little bit more like that but for proposals. So we went into it and there was nothing. When you go fresh into a category like that, there are a lot of things that you need to figure out and do and some things you get right, some things you get wrong. Over time we had just going through several different teams and not paying down technical debt enough really. We ended up in a spot where we had an older code base and it was harder to release the types of features that we needed to and we needed to really rethink the product. 

We should have probably done that earlier because we had learned so much. Everyone in the category and most of the apps that, especially early in the category, they eventually just dropped out and failed and weren’t around. But there was so much that needed to be figured out. Nobody knew what it looked like. By the time we figured out, okay, this is what this base looks like, it was time to sort, all right, let’s approach it with everything that we’ve learned and have a product for this market. That’s when I started thinking about all of the… Because we did a lot of research at that point and we were thinking about how to approach the rewrite, how to approach the next version of BidSketch. Then it was about, well while we’re doing this, there’s also this need here and we integrate with e-sign services, but we get asked to just add that into BidSketch. 

In the category, it’s a very basic version of E-sign. The thinking was we can better support the full document signing process for our existing customers as a strategy and then open up the market as well and compete in the e-sign market. So be in a bigger market and use everything that we’ve learned to just build a better product. So we started off with that approach. My first thought was let’s build the e-sign features, specific features first and then add the document. There’s so much overlap between the products, add the document creation features next. But once we started building the e-sign features, the market started pulling us in a very different direction and there was a decision at that point to continue with the original vision or just go into the e-sign market by itself.  

Rob Walling:
This is something that was so impressive to me as you went through it because you and I have talked once a month for 13 years, 12 or 13 years. So I followed this journey along with you and I was so impressed with the fact… I remember you went back to basically refactor BidSketch and you had devs working on it for something like six months, rewriting code, adding unit tests, upgrading because you were on an old version of Rails or whatever. At a certain point you’re like, I’m going to change course. You didn’t get caught in the sunk cost fallacy. You had a bunch of sunk costs and you’d made the best decision but then you said this is not the right decision anymore. A big part of it was this market pull of I think we need to make it a standalone app and then we’ll build everything else in. Then you were pulled yet in another direction of it was pretty obvious that this market wanted something that maybe you hadn’t envisioned early on. 

Do you want to describe to someone listening what that feels like? There are some folks who don’t know what market pull feels like. What did that feel like? Was a lot of requests for something? Or how would you describe it?  

Ruben Gamez:
You’ll get a number of requests for certain types of features from certain types of customers. The thing is that it doesn’t always… So we have shifted product strategy twice. The first time I’d say it was really just a volume thing. It was just most of the requests that were coming in were taking us in a different direction and the types of customers that they were coming from looked a lot less than what I had envisioned and what we were serving with BidSketch. So that combination just made it clear this is a different thing. The next time it was less of a volume thing, it was less clear that everyone wants this because it’s not so much about that. In our case it was these really high value customers are requesting this and there’s this opportunity and we’re not getting a ton of this, we’re getting some of it, but there’s something there. It’s investigating that and seeing how big that opportunity is and what it really looks like and that sort of drove the next one.  

Rob Walling:
Yeah, that makes sense. So then you found yourself with BidSketch, which is a proposal software and it’s a SaaS, it’s still doing great and generating tens of thousands a month in revenue and SignWell, which is electronic signature. Now you have two products technically under one corporate umbrella, but really it’s almost like two companies really, not technically, but they’re two completely separate domains and all of that. I guess, through your experience, and we’re going to dig in a second to… We’re going to generalize this and go to the pitfalls and exceptions of when it does make sense or not to do a second product, as well as maybe some goals behind that. But for you now that you find yourself in this situation running two products, you have a single dev team, do you feel like it’s complicated? Do you feel good about where you are or do you wish that you could focus on just a single product at this point?  

Ruben Gamez:
I feel good where we are now because we are mostly focused on a single product, is how it is really. BidSketch is just a more mature product and if I was devoting equal energy towards growing both of them, then it would be a really tough thing. I don’t think that works that well. But all my energy when it comes to thinking about growth and getting business to the next level and all that is focused on SignWell. That’s why that works.  

Rob Walling:
Right, in a sense you have two products technically, but BidSketch really more is in… It’s a stable product that just keeps running. I am not going to say autopilot. That doesn’t exist. There is no autopilot. Eventually your marketing falls off. Everything decays, right? Your tech stack gets older. You can’t find developers for it. The security stuff’s introduced and security flaws and blah blah blah. So it’s not true autopilot, but it’s maybe as low maintenance as you can have it. Is that pretty accurate?  

Ruben Gamez:
Yeah, it’s much more low. As soon as you stop adding a bunch of features and all that, a lot of the risks goes out of the product. So you fix a bunch of bugs, it just gets very stable and then it’s really just about making sure that you support the newer customers that are coming in and upgrading.  

Rob Walling:
I want to point out here, there’s different ways to add a second product. Sometimes you add a second product and that product far outstrips the first one in terms of revenue growth, all this stuff, which is what has happened for you with SignWell. That happened with me with Drip. I had HitTail. HitTail was doing $25,000, $30,000 a month, great lifestyle business. I was like, I’m going to start another one of those because HitTail really was… It was like a feature. It didn’t have ongoing development basically, so it was as autopilot as probably about you could get aside from the marketing. So I was going to launch another one of those, it’ll be fun and then suddenly Drip takes off and now it’s like what do I do with this other thing? So for me, I held onto HitTail for a few years and then I wound up selling it in 2015. 

So usually one of them gets all your attention, but there are folks I know who will launch two and then hang on to both of them and have them be equal attention split, try to 50/50 their attention. I think that’s pretty dangerous and that actually maybe gets to our first pitfall here. What are the pitfalls of doing this? Why is our default stance that you probably shouldn’t do it? It’s focus, because as bootstrapped entrepreneurs or mostly bootstrap entrepreneurs, even if you had a team of five, ten, 20 people, if you put all those people on one product, it’s going to grow faster, it should grow faster. But if you split that focus between two, it’s so hard. 

Dude, I even remember… So Leadpages acquired Drip. They had 170 employees and I remember getting in there and they had Leadpages and they had Center, which was this product, they were trying to get off the ground. Some people there kept saying, this split focus is hurting us. Some people thought it was a great idea for diversification and for whatever other reasons and other people were like, “It’s really hurting us.” I was like, “Split focus? There’s 170 of you. You have $38 million in mentor funding.” But you know what, it was split focus, even at that scale.  

Ruben Gamez:
Right, I remember when Leadpages came out with Center. Around how many people did they put on that product?  

Rob Walling:
I don’t honestly know exact numbers, but I know they had an early access where they got a 100 or 200, and got them on and they tried it out and they didn’t have product market fit was an issue and that’s what they kept spinning on was trying to figure out where do we fit in the market? Because really it was Clay Collins, CEO, had a vision and it was trying to start a new category. It was supposed to be the Center, it was the marketing automation, but it didn’t send emails, so it was like the center of your stack. So it was like Segment, but I think it kept state, it’s hard to… So you hear me trying to explain it, which tells me there is no category. It wasn’t Zapier, it was like Zapier plus Segment for marketers. So it was this new category and as we know, that’s hard to do.  

Ruben Gamez:
Right, that’s super hard. Yeah, no, I was thinking more in terms of the internal team, like how many… It was split, right, how many?  

Rob Walling:
Yeah, engineering team was, I think, probably between six and ten engineers. Then they had a marketing squad of four or five people that I think were coming over from Leadpages. If I were to guess everyone who did some work on it, even though some were split, it was probably 20.  

Ruben Gamez:
Yeah, okay. Then because they care about this new thing, like the executive team leadership and all that, they’re thinking about it and they’re working on it. Yeah, definitely splits the focus right there.  

Rob Walling:
There’s two things going on with that example. There’s splitting focus, second product, and then there’s category creation, which we could probably record a whole other podcast about how hard that is. But let’s just take the example of a mostly bootstrap founder with a team of five, a team of ten, a team of 20 whatever. To split focus, especially when… If your first product is working and there’s still room to grow it, I’m always like, “Don’t do this because you’re just going to leave growth on the table.” But if your first one stalls and it isn’t growing anymore, what then? Should you focus on that first product and keep growing it or do you split focus?  

Ruben Gamez:
I think it depends on the core reason why the growth has stalled. Yeah, it’s really hard to generalize in this case, but a lot of times really when people’s growth stalls, they often don’t know. I think you need to investigate and you need to… As best as you can. Sometimes we just don’t know for sure, but as best as you can tell, just stop working on the symptoms or thinking about the symptoms like, oh, our churn is too high or we’re not getting enough signups or whatever. Well yeah, of course that’s a symptom. What’s the core reason? What’s going on here? It’s like, oh, I think we’ve tapped out on this market is a common one. It’s like really, have you?  

Rob Walling:
That’s usually not true, yes.  

Ruben Gamez:
That’s right.  

Rob Walling:
No, I see it where there’s a million potential customers in a market, someone has 500 customers and they plateaued or they have 50 customers or something and they’re like, “Oh, I’ve tapped out the market, need to check out the Spanish market.” It’s like, no, you don’t. Solve the problem. What’s the actual problem?  

Ruben Gamez:
It’s more likely that they’ve exhausted the marketing channels in the way that they’ve gone about marketing or sales or whatever, their current approach has been exhausted. Yes, okay, maybe if you’ve tapped that out, that’s something else, but are there other channels? Can you bring in somebody that can help you on the growth side, whether it’s somebody internally or somebody to help on the consulting or an agency or whoever? You have to start making bigger changes. It’s hard to get there just doing the same stuff or just slightly different versions of the same thing if you’re really plateaued. So yeah, I think there are a lot of things at play there and it all comes down to, for me, the reason why growth is stalled.  

Rob Walling:
I think that’s a good take on it. I guess the last thought I have on focus and splitting focus, because I want to get to our other topics, but splitting focus of the team is one thing. Most people don’t realize… I’ve had people say, “Oh, I have this code base and I built it for CRM for realtors and it would totally work for mortgage brokers. So what I’m going to do is I’m going to go, I’m going to register another domain and I’m going to start the prep, because the codes the same. So it’s not really that much work.” I’m always like, “You realize the code’s about 10% of the business.” Just even if you’re going to do SEO, you’re splitting your domain authority. All the links you’ve built, you’re starting from zero, start the Google timer over. All of your marketing, any cold outreach, any brand equity you have, any traffic you have, now split. 

Your support team now has to… You don’t need double the support people, but they have to now know two products. You’re making two decisions about what features to build into which products. You’re splitting your dev team. On and on and on, it is way more than you initially think about. It’s the iceberg problem, right?  

Ruben Gamez:
Yeah, and I did that in the early stages when I was doing BidSketch and SignWell. That’s what we were doing because we had to. It was too early in the SignWell days, but even then it was just clear this is not sustainable. It just wasn’t.  

Rob Walling:
Right. I can imagine someone hearing this and saying, well, I’m not going to register two domains. I’m going to have two products under one umbrella, right? I am going to keep the same domain. So you could have had BidSketch.com and you have two products, much like I think of Intercom almost having two. They have what four products, five?  

Ruben Gamez:
Yeah.  

Rob Walling:
It’s like they have the chat and they have the support, and they have the this and that. HubSpot is similar, where HubSpot is an umbrella and then they have all these different tools under it. So that wouldn’t split as much, but it still comes back to splitting focus and being a lot to bite off. You do have to market those individually. You have to position them individually. You are fighting battles on multiple fronts. I think of it as, I always say, like two-sided marketplaces, here’s my advice, don’t, that’s because you’re… It’s like they’re starting two SaaS apps at once. It’s just you’re fighting things on two fronts. I think two products will make it tough, but there are exceptions. There are exceptions to it. So you did it and I guess I would ask you, you made an exception, you have a two products. Was it the right choice for you?  

Ruben Gamez:
Yes, for us it was the right choice. I could have gone either way with it as far as I went in a completely different direction, but I could have just kept it with BidSketch and just truly made it version two and gone in the other direction with the original. I think it would’ve worked out. There isn’t a clear right or wrong choice sometimes. You can have multiple paths that can work or you can have paths that are just going to be a lot more risky and difficult and all. I think just being deliberate and knowing what you’re getting yourself into and why is a big part of it.  

Rob Walling:
Why was your choice the right one, in retrospect? If someone else is facing this same choice, what were the factors that made it make sense for you and that have led to it being the quote-unquote “right choice”?  

Ruben Gamez:
There was a significant amount of time and energy and work put into the decision and identifying the problem, or the problems, the things that we were trying to solve for. So it was clear after a while that there was opportunity, a lot of opportunity, and I iteratively tested things along the way. So even though I felt… It’s not like you do all this work up front and then you say, “Okay, this is what we’re doing,” and then heads down and just go in that direction and don’t look, right? I was constantly evaluating and thinking about, okay, is this right? Do I need to make adjustments? So it turned out to… It worked out. A lot of the reason why it worked out was because of the reason I was just deliberate. I was able to identify real opportunities and then verify that those opportunities were real and kept checking myself throughout the process and then just changed whenever I needed to change.  

Rob Walling:
That’s the thing, there are always exceptions to these. You are particularly a deep thinker and someone who challenges and is willing to challenge their own hypotheses. So when you come to me with a conclusion or close to a conclusion, I’m always like, I’ll ask you questions, but I’m pretty sure you’ve answered all the questions I’m going to ask you already in your own head. That’s your personality, right? There are folks on the other end who just wake up in the morning and there’s a dream where they’re like, I think I should launch a second product. Every question I ask them about, “I haven’t thought about any of them,” right? They haven’t validated. They haven’t really given a thought. So I think this part of it, a little bit of this, is knowing yourself, are you someone who just bounced, bounced? 

Are you the indie hacker who’s in the trap of launch, it didn’t take off immediately on Product Hunt, I’m just going to give up and go to the next thing because it’s not working? It’s a siren song of over and over because you get the launched dopamine, but you don’t actually put in the work to really grow the product. If that’s more of where you fall, then really listen to our advice to not do it. But if you don’t and you are more of a [inaudible 00:24:19] person, or even if there are some folks the other-  

Ruben Gamez:
Or you lean the other direction, right, like too strongly, right? The opposite, yeah. You should probably examine it and think about it, yeah.  

Rob Walling:
Right, because don’t we have friends who have started one product and tried to grow it for years and years and years and they’re at 2K MMR after six years. There it’s like, I don’t know if you need a second product or you just need to kill the first one. But some people stick with stuff too long, right? So maybe you could break it loose. I’ll give you another counter example. I have two more in my head, but one is Jordan, right? Jordan Gal who it was just-  

Ruben Gamez:
Yeah, I was wondering what did he tell you that convinced you?  

Rob Walling:
So to set the stage, he had built CartHook, which was cart abandonment emails. I believe it was just for Shopify. I don’t remember if it was just for Shopify or for all e-com, but whatever it was, someone abandoned their cart, then they would send them emails. He’d gotten it up to low tens of thousands MRR. Then he found out… They either found or somehow got wind that there was an unpublished Shopify API that allowed you to modify their checkout and modifying it… Because their checkout was garbage basically, and you couldn’t change it. Everybody knew it was garbage, right? It was built in 2007 and it had never been updated or whatever, so it didn’t have upsells. It didn’t have all the conversions. Anything you’d want on a checkout, it just didn’t have. So he saw this huge opportunity. It’s like we’re going to get in there, we’re going to write code against this unpublished API. 

Then we’re going to work to… Once it’s published, we’ll be one of the first ones and we’ll get approval to basically be an app and people are clamoring for this. So he was then in some maybe Facebook groups or whatever slack groups where these… A lot of them, it’s a lot of D2C physical products, right, they’re just selling through Shopify. They all wanted post-purchase upsells, or during purchase or post-purchase upsells and they could add this in using this. So he’s like, “The people I’m talking to are losing their minds if we could add this to Shopify.” I was like, “I don’t know man. The cart abandonment emails seem to be working. Why would you go do this?” We talked for probably 45 minutes and he just kept saying… And this is it, Jordan, his intuition is pretty good. You know what I mean? When I say pretty good, I mean really good. I’m understating. His intuition of where the gap is… There’s certain founders you know, whether it’s… I don’t know if they’ve had it their whole life or they learn it. 

I think you and I have good intuition, Jordan, there’s certain folks we know. That was a piece of it, he had this very strong gut feeling that it was a green open field. It wasn’t a grasses greener. It wasn’t a that that’ll be easier. It’s I want to get there first and I want to own it. That was really the conversation and I asked him all the questions that we’re talking about here. Is it just hard and not growing? How are you going to do it? Are you going to sunset the other one? How are you going to focus on two? It was all those questions and he was like, “Look, we’re going to put some engineering, we can build this.” This was another thing, how long does it take to test this? When will you know? Will you know in a year or will you know in two months? I believe he said it would be two months of engineering, maybe three. I was like, “That’s a lot of time at this early stage.” 

But he had runway. He had raised a fund strapped a very small round for me and some other folks’. This is pre-TinySeed. It was that line of thinking where I was like… Then I said, “What if this fails? What’s the flip side? What if this works? What if this fails? Is there asymmetric upside if this works?” The answer was, “Absolutely.” The entire company… I mean, the end of the story is eventually I think they just sold off or gave away their cart abandonment element of it and the post-purchase upsells just took… Just the cart, the checkout replacement took off like a Cinderella story basically.  

Ruben Gamez:
Right, yeah. I think maybe shut it down. It was so… It was making money.  

Rob Walling:
The cart abandonment?  

Ruben Gamez:
Right.  

Rob Walling:
Yeah.  

Ruben Gamez:
Maybe sold it or was seriously considering, yeah. But compared to the difference between how well the new product was doing versus the old, it wasn’t even worth putting that much time into figuring out what to do with it. I think you’re right. I think he might’ve partly sold it. No, that’s interesting to hear because I was talking to Jordan a lot during that time as well. We talked regularly. I remember when that happened. I remember thinking similar things like, oh, okay, you’re doing-  

Rob Walling:
Shiny object.  

Ruben Gamez:
Yeah, you’re doing pretty good. But you’re right, it’s funny because it was him, because he doesn’t have a history of just jumping to the next thing and just building out and his intuition is really good, I was like, okay, there’s probably something here, this could be really interesting. So I thought the same thing. But I think that brings up a really good point as far as I think a lot of people who have a problem with it and add products sooner than they should do feel like they have an opportunity that they see, but it’s more than that. It goes back to partly how good is your product intuition, and this is based off of your history? What have you seen and where do you lean? Do you lean towards just moving on and not finishing things and not pushing things through or the opposite? Depending on those answers, you really need to examine that more or push yourself more to do something new if it’s the other way.  

Rob Walling:
Right, and get outside feedback. Because what did Jordan do? He talked to you. He talked to me. I know he talked to other people and he got input. You did the same thing when you were launching SignWell. You talked to a bunch of people, including me, and you were trying to get outside, not confirmation, but outside information about what am I missing? Why is this good or bad? Two other things I just said about Jordan’s decision was in addition to his vision or his intuition is like, does it have asymmetric upside if it works? Is the downside if it fails, not catastrophic? And, how quickly can you test this or how quickly will you know? Because usually, yeah, another product is six months, nine months. That’s a really long time. You better be damn sure that it’s going to work.  

Ruben Gamez:
That’s why in decisions like that where it’ll be a while before you know, so you have to invest time, energy, money or whatever for a while, and the opportunity cost there is that you’re not growing your other thing or whatever. When the feedback cycle is slow like that, that’s when it pays off to put in more work upfront and that’s work in these conversations, doing little tests or doing whatever. If the feedback cycle is fast and you’ll know in a week, you don’t even have to talk to anybody, just try it and it’ll be a week before you know and then you move forward or whatever. It really depends on how long that feedback cycle is.  

Rob Walling:
On the point of feedback cycle… There’s one more example and then I want to get to our strategies or goals behind adding a product and then we’ll wrap. One more example. I know of several other examples, but you and Jordan, and then Stratosphere is the third example. Stratosphere is a TinySeed company. You can see them at stratosphere.io and their H1 is the all-in-one data visualization platform for investors research platform. It’s a rolling thing. When the AI stuff started getting popular… When the AI stuff. When ChatGPT and everything was buzzing six, eight months ago, they built finchat.io. My memory is they built and shipped it in six weeks. It was very fast and they got instant traction. It was one thing that, the downside if it didn’t work was not that much. I remember again, they brought it up and I was like, no, the second product, why are you doing that? 

All the stuff we’ve said here. They were like, it’s not going to take that long to test, the asymmetric upside if this really does catch, it would be the only thing doing this, and if it catches, it’s going to be astronomical. In addition, they already had… They’re not just a ChatGPT wrapper. What they did is with Stratosphere, they have all this proprietary data that they’ve cleaned that you can only get through their API or their interface and FinChat is a chat interface to that proprietary data. So even at that point, if it works, I suggest, it’s just another interface into what they’re already building. And, long-term… We talked early on. I said, “Well, what if this works? Can you merge this all back into the same product? Is this just a different price point, for instance, on your pricing page? Or is it…” Because right now it’s a separate domain name. But we talked through that possibility. It’s not like it’s some way far out of left field thing that really needs to be its own thing. 

It could feasibly come back and be part of the home base if it works and if it doesn’t, it was a fun experiment. So that was another one where at the end I said, “Assuming we live up to these things, I sign off.” Not that I needed to sign off, they were going to build it, whether or not it did. But it was another example of, I think, speed, being able to test it quickly.  

Ruben Gamez:
Yeah, which is a big deal in situations like this. One quick thought that I had, a question for you, was you talked about asking for feedback from others. We’ve seen this a lot where founders basically make up their mind and are talking to others and they’re asking for feedback, but all they’re really wanting to hear is people say, “Yeah, I think it’s a good idea.” The ones that don’t, they either… I’m not sure how it’s explained in their mind, they’re either not seeing the vision or whatever, and then any little confirmation, they take that and they run with it. What do you think? Do you have any thoughts about not falling into that trap or what being good at asking for feedback and taking that feedback looks like?  

Rob Walling:
Yeah, and why I have it is because some point in my history ten years ago, say 15, I was exactly the person you described where I would have a vision for something, I would ask for feedback, and then I would argue with all the feedback because I felt like, oh, you’re attacking my idea, I’m going to defend it because I know I’m right. Then at a certain point, I switched. That was seven, eight years ago, whatever. So I feel like I’m on both sides of that, A&R and my team may disagree with that statement that I’m better at it. No, I just feel like I’m better. What I’ve realized is it’s not… I used to think about it black and white of I have this idea, I’m going to ask for feedback, and if it doesn’t fit my idea, then either they’re wrong or I’m wrong. 

The idea is wrong or they’re wrong. That’s not actually what it is. Here’s what I do these days. I’ll come up with an idea. I present it to A&R, to producer Zander, to producer Ron. They’ll give feedback and I’m like, oh, with creativity, with growth mindset, that tweaks my idea. I’m going to change my idea. I’m not just going to scrap my idea, it’s a (beep) idea, it didn’t work because of their feedback. It actually will tweak it and make it better. So the format of a YouTube video, for example. I was like, this is how we should structure our YouTube videos. Then someone started… They were like, well, you need a story, you need a hook, you need a teaser at the end, you need this and that. I was like, oh, you’re improving. You’re improving it. It’s not, I should scrap my whole outline. It’s, I should just tweak it. That’s a trite example. 

But similarly, if I came to you with a business idea and I was like, I’m going to build an ESP for realtors or whatever, and you started having thoughts around it, it shouldn’t be, I should do it or not. It shouldn’t be this black and white thing. It should much more be around am I able to take your feedback and creatively incorporate it into my idea? Or if I’m really getting bad signals, I should just scrap it all together. Does that make sense?  

Ruben Gamez:
Yeah, I like that. I hadn’t thought about it in that way, but that’s a really good way to think about it.  

Rob Walling:
How about you? What’s your advice for someone who maybe tends to fall in that trap of I lock onto my ideas and I really don’t take outside feedback, even though I ask for it, I act like I’ve taken outside feedback, but I have my mind made up already? How do we get around that?  

Ruben Gamez:
That is tough because I can’t think of a time where I’m thinking in that sort of way. But, I can talk about how I think about it when I am getting feedback, and maybe that can be helpful.  

Rob Walling:
Yeah, because you’re really good at it. Ever since I’ve known you, and I think we’ve known each other for 15 years, maybe a little more, you’ve never been defensive about your ideas. You’ve always taken feedback in stride and you’re able to identify quickly usually, oh, that is actually a better idea than I had, or that makes my idea better. You’ve had that knack since I met you. So yeah, talk us through how you do that.  

Ruben Gamez:
So I don’t believe that my idea is finished or is perfect to begin with. So I think of it more as a starting point, that’s the first thing. I really like something that David Cancel, I heard him say a long time ago, which was the way that he thinks about it is that if he has an idea or anything for a feature, for a product or whatever, he figures that it’s wrong and he’s just trying to figure out how wrong it is. Is it 90% wrong? Is it 10% wrong? So I like that sort of mindset and it mirrors the way that I tend to think about it. The other thing is that it’s good to get multiple data points from multiple people, then consider their context, their experience, and then think about how it relates to mine. So I think about all those things when I’m taking in feedback because the context is really important. 

So as long as I feel pretty good about the people that I’m getting the information from and the feedback that I’m getting, then I can feel pretty good about integrating that or whatever, or at least considering it. Then the other thing is if something really bothers me, if somebody said something that I didn’t expect and it’s rubs me the wrong way or I have a bad feeling about it, that to me is a sign that I should examine that more. There’s something there that I’m like, I’m too married to this part of the idea. You know what I mean? I’m not willing to evaluate every part of it or something like this, to me, it’s a red flag, danger.  

Rob Walling:
Emotional, you have an having emotional reaction to it, which isn’t helpful.  

Ruben Gamez:
Exactly, right. That’s a good sign for me to take a look at what’s happening there and really try to consider it.  

Rob Walling:
It’s a very insightful, mature way of thinking about it rather than reacting, doing the self-examination. So as we move to our last segment here, obviously we’re running long on time and I’m intentionally just letting it do that. Let’s talk about if you decide that adding a second product is viable and it is the right way to go, let’s talk maybe about strategies doing that, behind doing that and goals, maybe the goal of adding a second product. I already talked a little bit about the indie hacker trap, I think, of launching, bouncing to the next, to the next, to the next. That doesn’t fit at all with a strategy, that usually is just a reaction to something. But you had a note in… We have a little outline we’re running from, and you have a, quote, “Portfolio of products” or quote, “Diversification” right, behind adding it. Talk me through that. Do you think that’s a good reason to do it? You think that’s a mistake?  

Ruben Gamez:
So this is something that I’ve seen go around a lot with in the indie hacker circles, which is they’re talking about a portfolio of products. You’re the OG of portfolio of products, like you did this way back in the day.  

Rob Walling:
In 2008, yeah.  

Ruben Gamez:
Yeah, that’s when I found out about you and what you were doing. I was like, oh, this is cool, and you were doing a lot of that. The other thing is diversification and the portfolio products seems to be the reason why that’s done is because of diversification. So it’s almost a fear-driven way to approach product and it misses… So that’s behind it, which is like a red flag. Then misses a really big component of SaaS, at least, which is momentum and building… If you split your effort and your energy, time, money, all that, amongst multiple products, it’s really, really, really hard to get any one of them to a scale and level that you probably want to get to because things get easier as you grow more, you add more revenue, it builds on itself. Momentum is a really, really, really big deal, and it’s hard to describe until you’ve felt it, but you’ll never get to the momentum that you need to get into build a million dollar SaaS business or whatever if you’re doing that.  

Rob Walling:
Yeah, and that’s the thing. I mean, you’re referring, I had somewhere… It depends on how you count exactly, but about nine or ten different revenue streams, different products. Almost all of them… Most of them were software. I had one content website. I had an e-commerce website. I had some eBooks, and then I had software. Some of it was one-time sales, some of it was SaaS, some of it was B2C. This is where I learned all the lessons, right, that we started talking about at the MicroConf, like don’t do B2C, raise your prices, et cetera, et cetera. I found exactly that. It was fun. I talk about the stair step method all the time, right? Step one is just cutting your teeth, doing something small, making a $1,000, $5,000 a month. Step two is having usually multiple of those step one businesses, doesn’t always have to be, but usually it’s multiple to get to that magic number, maybe $8,000 for some people a month, maybe $10,000 maybe $12,000, $15,000 whatever. 

So step two is building, I’d say a small portfolio of products. You get a little diversification. You get some more learnings, and you get to buy out your own time. You own all your time. Then you go after the big standalone. That’s the progression that I see and I think most people will follow. Now, there is this flip side, the indie hacker lifestyle dream that you’re talking about. Well, you get the portfolio and you’re perpetually traveling or you’re just working the four-hour workweek. That’s not a bad thing, but to your point, it hampers momentum. You will rarely, if ever, get to that seven figure goal, if that’s something you want to do. Honestly, there aren’t that many people. There are not thousands of people doing that. There are a handful of people that are truly doing that, I built a big Twitter following and now everything I launch people jump on. 

If you want to try to be the Tom Cruise of indie hackers where there’s like, oh, there’s one star that does this or there’s four we can name and everyone else it’s like… But how many hundreds, no, thousands of founders do you and I know who have done this other path of getting to that point of having that SaaS and focusing and building it? It’s just a more viable thing. We’ve talked probably more about indie hacking than we even should have with this, but I think that’s where a lot of the multiple product stuff comes in. That’s not where Daniel Hoyman with Intelligent Editing is not going. He has a 14-year product and truly is talking about adding a second product line to his company, which again, it is just a different conversation. 

But I mean, let’s say you add the second product. I guess we already talked a little bit about starting a whole new business where it’s a new domain, but let’s say you add the product to your lineup to where you can cross-sell the two of them. That’s a benefit someone could talk about. What’s the pros and cons of that and when does that make sense, I guess?  

Ruben Gamez:
Yeah, there are companies that do this successfully. It’s a proven way to go, but it’s not easy. It’s harder to sell even a new solution to the customers that you have. It’s almost like designing a new tier, a new plan, that people would upgrade into, but it’s a little bit more of a jump there than just upgrading to a different plan and adding new features. So if you think of Intercom, they’d famously do this, their pricing is a mess because of it. Zoho, I think does this pretty well.  

Rob Walling:
HubSpot.  

Ruben Gamez:
HubSpot, right. So there are these products that get there. I think moving in that direction too early is a mistake. That’s one of the more common mistakes, probably driven by a lot of the same reasons why people just do a separate product to begin with. Assuming that people will buy the product from you just because they’re already a customer is another mistake.  

Rob Walling:
Right, that you think you’re just going to sell a copy of the new one to every existing customer or some huge, huge percentage, right?  

Ruben Gamez:
Exactly, right.  

Rob Walling:
Yeah, there’s a really interesting article blog post by Jason Cohen, it’s called The Elephant in the room: The myth of exponential hypergrowth. He talks a lot about how exponential… He’s looking really at the word, and that part is fine, that he’s saying it’s not actually exponential. But there’s one slide later called the Elephant Curve that is very interesting. It’s basically about how every product eventually tops out, that maybe you top out at 500K ARR and maybe you top out at 5 million and maybe top out at 50 million, and it depends on your goals. But if you want to be HubSpot, which is we want to go public, and your HubSpot marketing, inbound marketing tool, basically tops out at 50 million or 100 million, that’s not enough. So remember they made not a pivot, but an additional… CRM was their big thing they went all in on seven, eight years ago. They really won a lot of the space from, well, from all the other players and from Salesforce. Though you’re saying, people do this too early though, is the problem.  

Ruben Gamez:
Right, all the companies that we mentioned that have done it successfully, they’re of a certain scale and trying to build a certain size company. The way that you described it was right, that it’s not… At some point, these really big companies that are often VC funded and they need to go towards going public or something like that, just where they’re playing is not enough to get them there, so they need more. So you often see that with these companies, but this is a very different position that a lot of startups are in when they start to think about this sometimes. It just goes back to all the same things too, you have to be spread thin and resources, time, focus, all that. It makes the rest more difficult.  

Rob Walling:
You had a note here that I’m curious, it’s under moving to a bigger market, breaking out of a niche, expanding the market. Obviously we’ve talked about a few successes here with HubSpot and these others, but you talk about some failures with Moz. Did they try to build a second product? I don’t remember this.  

Ruben Gamez:
Yeah, so this is the whole, like, this is future, this is the next thing, right? Yeah, Moz, their thing was like there were going to be a marketing suite. There weren’t going to be a suite for SEO. There were going to be marketing. Rand talks about this in his book to where he’s like, that was one of his biggest mistakes and he was believed so much in this vision that he just went off and spent a lot of time and money and all that focusing on just building this thing. Yeah, so that just didn’t work out that well for them because of that reason.  

Rob Walling:
Yeah, no, that makes a lot of sense, I think that-  

Ruben Gamez:
It is tricky to make work.  

Rob Walling:
Yeah, and I think he talked about they didn’t validate it enough. I think if I recall. I read his book, it’s probably five years, so I’m going from memory. This is Rand, so he’s very self-deprecating and has a lot of introspection. I remember him saying something like, “I was the founder. I had the vision and Moz worked and I thought I had the golden touch,” I’m paraphrasing, “So my next thing, I thought I had the golden touch, and was going to be right. And when we did it, it didn’t work out and it was because I had some hubris.” Oh look, all of us do this at one point or another, and I think that’s why we’re recording this episode is to let you know, hey, just because you got one, right, it doesn’t mean that you shouldn’t really think through trying to expand to a second product. But obviously it can work right, as it did with CartHook and Stratosphere and with SignWell and with others, so.  

Ruben Gamez:
Yeah, there was one really interesting one real quick with FreshBooks that I saw that they did, because they were invoicing and they went into… Now they’re cloud accounting. What they did was they created a product and called it something different, it wasn’t even FreshBooks. They put it out in the market and started testing it and getting signups. Once they started seeing growth going in the direction that they thought, okay, we have something here, then they were like, okay, rename this is FreshBooks, the new thing. So I thought that they took a very interesting approach to doing the new product.  

Rob Walling:
That’s a nice way to do it. Very elegant. Well, Ruben Gomez, thanks so much for joining me on the show. Not only joining me on the show, but going over time. I know we have a busy schedule and we’re already over our allotted time. Folks want to keep up with you, you are earthling works on Twitter and of course BidSketch.com and SignWell.com, if they want to see two of the best SaaS apps on the internet today.  

Ruben Gamez:
That’s right. Thanks. Yeah, I’m mostly on Twitter, but I post infrequently on there.  

Rob Walling:
Sounds good, man. Thanks again for coming on.  

Ruben Gamez:
All right, thanks for the invite.  

Rob Walling:
Thanks again to Ruben for coming on the show and to you for listening this and every week. As a reminder, I am on a drive to get 100 five star reviews for the SaaS Playbook in Amazon and/or Audible. If you’ve read the book and you feel like it deserves five stars, please head to your local Amazon or Audible site and give it that five star rating. I’d really appreciate it. This is Rob Walling signing off from episode 681. 

Ruben Gomez, thanks so much for coming back on the show.  

Ruben Gamez:
Oh, did we start? Sorry. Okay.  

Rob Walling:
Yes.  

Ruben Gamez:
That was such a smooth… Yeah, smooth transition.  

Rob Walling:
Cut, cut, take two. All right, so now it’s going to be me saying, “Let’s dive into the episode” and then I’m going to say, “Ruben Gomez, welcome back to Startups For the Rest of Us.”  

Ruben Gamez:
Did you do that? Sorry, I thought you were telling me what you’re going to do. I’m like, okay, cool, let me know.

Rob Walling:
It works this way for products too. Pay attention to the problem customers describe, not so much the solution they propose. This is an encapsulation and a really intelligent rephrasing of something that Derek Reimer and I started talking about probably I’d say 2014, 2015, which is your customers will come to you with featured ideas. Don’t build those features, dig in and find out what is the job that feature is trying to accomplish. 

Welcome back to another episode of Startups For The Rest of Us. As always, I’m your host, Rob Walling. And this is the podcast where we dive deep into building real companies for real customers who pay us real money where we’re not constantly on the venture treadmill needing to raise money every 18 months or go broke. We’re not anti-funding, we’re just anti the narrative that the only way to build an incredible software company is by raising funding. 

Today is a Rob solo adventure. I’m going to cover some topics that have been on my mind lately, including listening to problems, not solutions. Listening to your customers instead of a customer doing what it takes and maybe a few more topics based on how the time winds up. And one more thing, we’ve recently reopened the doors for our online community, MicroConf Connect. MicroConf Connect is our virtual hallway track. It’s a vibrant community of SaaS founders helping each other and discussing wins, challenges, and frankly how to grow faster. 

A couple months ago we paused new signups to improve the platform based on your request. With MicroComp Connect 2.0, we’re rolling out three membership tiers packed with new perks like weekly coworking, exclusive discounts, a searchable content library and more. Whether you’ve been a member of Connect or not, you really should check it out. microconfconnect.com. 

My first topic of the day comes from Twitter. I just refuse to call it X. I’m sorry. I saw a tweet from Ruben Gamez, Earthlingworks and he was quote tweeting sequence film. Sequence underscore film. Sequence was quoting comedian, Bill Hader on receiving feedback. And there’s a little video clip that’s, I don’t know, a minute long and it’s pretty insightful. But the quote that they post in the tweet is, “When people tell you something is wrong, they’re usually right. When they tell you how to fix it, they’re usually wrong. And Bill Hader is talking about being a standup comedian or being a writer in film and how people can tell you when a joke doesn’t land or when a concept doesn’t land. 

But knowing how to fix it requires something that I’ve talked about many times on the show, which is that creative spark and taste to be able to find the right solution because there are infinite ways to try to make a joke or a scene better. And most of them won’t land. 

So how do you find one or two that makes it really scream? And usually people giving you feedback are not those that are also creating. It is this interesting thing where you are on the outside and I’m listening to a podcast. And if I’ve never recorded a podcast, I have a certain amount of taste to say, “Oh, this is good or this is bad based on my taste, or this is high quality and this isn’t.” But for me to then suggest, “Here’s how I would change it. I would add different music here. I would’ve asked this question. That’s another level. That’s that Ira Glass level of your ability, your skill through hard work has to catch up to your taste. 

And that’s what Bill is calling out here. When people tell you something is wrong, they’re usually right. And when they tell you how to fix it, they’re usually wrong. So why is Ruben Gamez retweeting this? Because he says it works this way for products too. Pay attention to the problem customers describe not so much the solution they propose. This is an encapsulation and a really intelligent rephrasing of something that Derek Reimer and I started talking about probably I’d say 2014, 2015, which is your customers will come to you with featured ideas. 

Don’t build those features, dig in and find out what is the job that feature is trying to accomplish. Over and over we would receive different feature requests from folks who are trying to do complex workflows and they would come in and say, “I have an email sequence in Drip and I want to be able to have an if-then L statement and add a tag between them and then branch based on that. Can you add that to this screen?” 

And we even had people mock-up the email sequence screen to work for their exact use case. Derek and I would get together and it never felt right. It was like that solution is terrible, but this problem is real. This person is this marketer, is trying to accomplish something that is very difficult or impossible with our current setup. So how do we build this in? And we mold it over four months, at least six months, maybe a year. And we took all these disparate points of feedback and you’d get that one and then you’d get one that was quite a bit different. But it was like, “Well, these are similar,” and that someone wants to do something off the cuff and they want branching decision-making. 

How do we build that into the product in an elegant way? And of course, after six to 12 months of building and growing and we hired another engineer, it started culminating in the sense that we need something probably visual to allow people to do all of this stuff. And that was when we started looking around realizing, “Oh, there are actual visual workflow builders in email marketing and marketing automation and they allow you to do some of the things these folks are asking plus more.” 

And that was a big lightning strike realization for me where I realized that a swath of problems, a swath of requests, could all be fixed with one feature. Now it was a huge feature and took Derek five months full time to build, which if you’re looking at it from a big company perspective, that’s actually very fast. And if you’re looking at it from a startup perspective, it’s agonizing that it takes that long. But that was our visual workflow builder in Drip and it solved literally 50 feature requests that had come through in the span of a year. And all these feature requests could have been individual settings, an individual toggle, an individual hack to a screen. 

This is, in my opinion, what separates great product people from average. I wouldn’t say mediocre, but an average product person will listen to something and say, “Oh, the customer wants this. Let’s go build it and let’s add that checkbox. Let’s add that slider. And let’s hack this screen because It’ll get us to what this customer needs. Not looking ahead 10 moves, only looking ahead one move on the board.” And that’s what Ruben Gamez is talking about here is your customers are not going to have the product sense to be able to design your product. They don’t have the vision for what it needs to look like. They don’t have the vision for what the UX needs to be to keep the elegance in. They see a problem they have and the shortest path to a solution. And they’re not worried about maintenance or the user interface getting crafty. 

They’re not looking three, five, 10 years down the road like you as a founder should be. So just one more reminder again in the words of Ruben Gamez, “Pay attention to the problem customers describe not so much the solutions they propose.” 

My second topic of the day is a quote from one of the co-hosts of the Comic Lab podcast. I like listening to podcasts that are not in the startup space. Comic Lab is two comic artists who have made a living doing Kickstarters and Patreon. Their comics are quite funny, especially Dave Kellett. I’m a huge fan of Drive and of Sheldon. Sheldon is just tasty, goodness, nerdy humor that my sons and I have read and love. And the thing I like about this podcast is they talk about things like ventriloquism doesn’t work in comics. They talk about things like kerning and about drawing thought bubbles versus speech bubbles in comics, panel construction, thumbnails. These are things I have no understanding of and will never need to because I have no aspiration to be a comic artist. 

But so many of the principles that they talk about as two 20-year professionals who have made it in a space that is very competitive and I would say is similar to startups. And the fact that there’s a lot of people that want to do it and a few people who actually do it, and even fewer who can make a living at it, and even fewer who can make a living at it for 20 years. So listening to them talk about the lessons they’ve learned, and realizing the massive parallels between that and starting up. And also taking some thought lessons, some thought experiment lessons away from them I think has been beneficial to me. 

One of the quotes that co-host, Brad Geiger said was don’t listen to a customer, always listen to your customers. What he means by that is the squeaky wheel. There’s often one person who is so squeaky and so loud about a thing and they can convince you that just because they’re being loud and repeating it over and over that you should do that. So in their world, it’s making a T-shirt with this particular character on it or it’s publishing a book, collecting whatever particular strips on a theme that you could collect. 

And in our world, it’s listening to that customer who is just so convinced that if you built this one feature that they need so badly that it would just blow your market wide open. In fact, they’re so shocked. They’re shocked it already doesn’t do this. Really surprised that your product doesn’t do this massive edge case feature that you’re probably never going to build. But boy, they just know. They’re a business person and they’ve run a business for 20 years and they just know that that feature. 

It’s only going to take two or three months of development is going to make or break your business. And that’s a case of don’t listen to a customer, always listen to your customers. If five customers are starting to request this or 10, or 50, this is where being a founder or a product owner in any form requires a little bit of some science, but it has to have some art in it as well, right? There’s that founder gut. There’s the vision for your product mixed along with the actual hard left brain data that you’re getting. 

This is where you have to balance that. And this is why finding product market fit specifically and then even the first few years of product development are so challenging because it’s a ton of decisions, hundreds of little decisions that you’re making, they’re very hard and they set the tone of your product and of your company. And you’re making them with dramatically incomplete information. It’s not like you have 50% of the information. You have 10, 15% if you’re lucky. 

And that’s why if you take someone who does product management at a large company or a mature product that’s been around for 10 years and you put them in the spot of we don’t have product market fit or we have five customers get us there to where we’ve built something that people want and are willing to pay for. Usually they won’t succeed because they’re too used to having so much data and they’re used to making hard decisions with mostly complete information. But in your shoes, whether you’re on day one of your company or day 1000 a few years in, you’re still probably making a lot of hard decisions with incomplete information. And that’s why listening to your customers rather than a customer was a good reminder for me to hear from Brad Geiger. 

Well, the exact application of it obviously differs between writing a comic strip and building a product. It can be especially hard when let’s say you have 10 customers and one customer says something over and over. It’s like 10% of your customer base. You just don’t have enough data to know if that’s the right way to go. And that’s why in that early phase you do have to think about how do I trust my gut and what’s my vision of the product? And that has to play a pretty big role in guiding where you are headed because if you let customers guide you, most of the time, they’ll just have you rebuild MailChimp or Basecamp or HubSpot. 

They’ll just have you replicate that because that’s what they’ve used and that’s what they know and they’ll just keep suggesting those features and pretty soon you will have just a clone of another product. You have to ask yourself along the way, “Am I properly integrating my own vision for this product along with listening to my customers?” 

Finding the perfect software engineer for your team can feel like looking for a needle in a haystack and the process can quickly become overwhelming. But what if you had a partner who could provide you with over 1,000 on demand vetted senior results oriented developers who are passionate about helping you succeed. And all that at competitive rates. Meet lemon.io. They only offer handpicked developers with three or more years of experience and strong proven portfolios. 

With lemon.io, you can have an engineer start working on your project within a week instead of months. Plus you won’t waste your time on candidates who aren’t qualified. Lemon.io gives you easy access to global talent without scouring countless job boards and it’s more affordable than hiring local talent. And if anything goes wrong, lemon.io offers swift replacements. So it’s kind of like hiring with a warranty. If you need to grow your engineering team or delegate some work, give lemon.io a try. Learn more by visiting lemon.io/startups and find your perfect developer or tech team in 48 hours or less. As a bonus for our podcast listeners, get a 15% discount on your first four weeks of working with a developer. Stop burning money, hire dev smarter. Visit lemon.io/startups. 

My next topic is about doing what it takes. Sometimes you have to roll your sleeves up and you have to grind. And sometimes it’s grinding for five hours on a Sunday afternoon and sometimes it’s grinding 60-hour weeks for two or three months when it really needs to get done. Now, that’s not necessarily a sustainable pace, but there have absolutely been many, many times during my career, especially as I became an entrepreneur where I had to work harder than I wanted to. I wanted to work 40-hour weeks and instead I worked 60 sometimes a little more when I was working a day job and working nights and weekends. 

I get questions from time to time. Sometimes they’re directly to me and sometimes they’re on this podcast about how to balance that, about how it’s difficult. And frankly sometimes I get questions about how do you even manage it and balance it all. 

Not me in particular, but how does a founder. How do other bootstrappers go about making this happen when doing what it takes can be hard and it can push you past a comfort zone. So to demonstrate this, I want to tell you a story. So as you know, over the summer I did a Kickstarter for The SaaS Playbook. That went really well, sold a few thousand copies, and once the Kickstarter ended, I wanted there to be an opportunity for people to be able to purchase the book because the day it ended, there was still all this traffic to the Kickstarter page and all this traffic coming to saasplaybook.com, which is where the book lives. It’s the home of the book. 

And while the Kickstarter was on, there was a button that said, “Go back to the Kickstarter.” But the day it ended still getting hundreds of uniques a day, I want to be able to take pre-orders that are after the Kickstarter, right? So the Kickstarter had exclusives. It was a limited and one time print run of hardcovers. But when the Kickstarter ended, you could basically, I think pay the same amount and get a paperback copy that would come after the book was released. 

So I was taking pre-orders. And while the Kickstarter was fulfilled by a professional fulfillment house, because of course it was thousands of copies of the book, the paperback copies, I figured they might sell 100, 200 paperback copies, which it is feasible to have an assistant as we had back then who comes to our house, drives our kid to school and then can help with little packing needs like that. She’s a part-time local assistant. And it’s totally feasible to have someone print shipping labels, pack up books and get them fulfilled. 

So that’s what I did. I took pre-orders on The SaaS Playbook. It uses Squarespace cart and I ordered a couple hundred copies of the paperback print on demand from Amazon. And I waited until the book was released. As the release date of the book approached, because obviously I wanted to fulfill all the Kickstarters before shipping out anyone who had ordered after that. As that date approached, our assistant who had been with us for a couple years, decided to move on. 

She’s headed off to a master’s program and she decided it was time for her next act and we wished her well. So I thought no problem. I have a 17-year-old in the house. He’s going to college in the fall, but certainly I can pay him $2, $3 a package to just fulfill… It’s about the same as you pay at a fulfillment house to print these and fulfill them. Again, if there’s 100, he makes two or $300 just sitting around listening to podcasts and watching YouTube and filling these out, doing it on a weekend day. 

This is a great gig for him and it means that I don’t have to do it because I don’t particularly want to pack a bunch of books. And then as the timing approached and everything actually landed, the Kickstarter was fulfilled effectively the day that my son left for a two-week writer’s camp during the summer. And so suddenly it’s me and my 13-year-old. Sherry was here too, but she’s not going to fulfill books. So I asked my 13-year-old, “Will you help me fulfill these?” And he said, “No, not really. Seems like a lot of work.” 

So I asked myself, “Do I wait two weeks?” Some people had ordered what a month and a half, two months prior for these books and it didn’t feel great to wait another couple of weeks to fulfill it. And I asked myself, “Do I try to hire someone on Craigslist? Do I try to find a local college kid? Do I just wait and not fulfill these yet?” There are all these options. And one afternoon Sherry went to trapeze as she’s apt to do. For those who don’t know she does a lot of circus training. That’s her hobby. 

I sat down and I thought, “You know what? I’m going to fulfill maybe 50 of the orders just to see how hard it is and if I can get a system down, I’ll convince my 13-year-old to help me with it.” And so I sat down and I massaged the CSV. Man, it was like 30 minutes just doing that to get the CSV out of Squarespace and get it to work, and the shipping software that I’m using. So I’m messing around 30, 45 minutes. 

Finally, I do it bulk prints, a bunch of labels. So then I’m sitting there and I think I was watching YouTube or I was listening to podcasts and I was like, “I have all these labels and I have all these envelopes and these books. I can totally just listen to it. It’s like doing the dishes. It’s just a rote thing. You pack, pack, pack. I was even writing notes if someone will say in Minnesota or California since I’ve lived there. I was like, “Hey, California represent.” It was a fun thing and I was able to write notes on it and say, “Hey, see on the Twitters.” 

I’m packing these books and before I knew it I was maybe 90 minutes in and I had packed up 50 books. But still had a bunch more address labels. Maybe I was a couple hours in. I realized this isn’t fun per se, but this feels good to get this done. And is this the best use of my time? Can’t I pay someone two or $3 to pack these books? In a perfect world, yes. But the way it was working out, it was going to be hassle to do it, right? Because again, lack of assistant, lack of 17-year-old. I could go try to hire someone. It’s a one-off job on and on and on. It’s that thing of do I just do what it takes to ship these books? 

And so that’s what I did. Honestly, at a certain point my back started hurting because you’re doing the same thing over and over. It took me about five hours, all told start to finish to get everything packed, labeled, boxed up for the post office. And during that time I thought a lot about how I used to do this when I worked construction. As an electrician, I used to prefab things where you prefabricate, you attach a box to some MC cable and you make a hundred of these. And then when they’re out in the field, they can just grab one. It’s a certain length. It’s marked with tape and they don’t have to do it on the job site and you are sitting in a warehouse doing it and so you can do it very efficiently. 

It’s just fabrication, right? It’s like manufacturing of something. And that’s what this felt like. It was a rote process. And while I didn’t necessarily enjoy doing it, nor do I consider it something I would do again, nor do I consider it the best use of my time. I just did what it took to get it done. And I’m going to be honest, a lot of the founders that I see that succeed, they just do what it takes to get done. 

Now, maybe they’re not packing and shipping books. Again, I’m not saying, “As a startup founder, you need to be willing to pack and ship books because that’s not the point of this.” The point is that even though today I run two successful companies, we’ve raised $42 million. We’ve invested in 130 SaaS companies. MicroConf has this incredible audience. Even though all that’s in place, I’m never above taking the trash out. I’m never above doing the dishes. I’m never above packing books when it needs to get done. 

I’m going to be honest, so many of the founders that I see who are wildly successful, they do what it takes to get it done. When I look at what Jason Cohen was doing in the early days of WP Engine, now this is 12 years ago now, he just did what it took. He didn’t say, “I’m above that or since I’m a third time founder I’m not going to do grunt work.” He did the grunt work. He had the conversations,.he validated the idea. He wrote some code before he hired developers. He did what it took. When I watched Heath Shaw do his most recent effort, FYI, he was grinding on that trying to find product market fit for a couple years. 

When I look at TinySeed founders who are building these incredible multimillion dollar businesses and we have quite a few of them now, I won’t say every single one of them we know is willing to just grind and go all in and do what it takes. But a lot of them are. And this is not something that you have to do every day, all day for the rest of your life. This is not 60 hour weeks, 12 months a year, but this is not five hours packing books every Sunday, five hours checking your support queue every Sunday, five hours writing content every Sunday. 

But does this need to get done once in a while? Probably in the life of a business, especially when you are at idea stage and you’re just grinding, and you think, “I don’t know if I really want to do this.” If you’re not sure if you want to do it, you probably shouldn’t because I talk about how success is made up of hard work, luck and skill. Luck is something you really can’t control directly. 

Skills are something that you can build over time. But the other thing that you can really control is putting in hard work. And when I think about the nights and weekends that I put in when I was getting started and how I didn’t really want to do that, but the end goal of quitting that day job and having enough income that I didn’t have to beholden to someone else and I didn’t have a boss, it was worth it. 

So when I would stay up till 1:00 AM, I’d get off at five or 6:00 PM. I’d come home, I’d eat dinner. And if Sherry was out, I would stay up till 1:00 AM working on stuff, working on website copy, writing some code, doing support, and then I’d get up and go to work. Did I do that endlessly for years? No, I didn’t. But being willing to sometimes just do what it takes to sometimes work a little harder than maybe you’re used to is the quality that I think more entrepreneurs need to embrace. 

I can imagine someone listening to this thinking hustle culture, work all the time. Again, that is not what I’m saying. But at certain times, there’s a time and a place where you have to buckle down and do what it takes to be successful. I hope you enjoyed the three topics for today about doing what it takes, not listening to a customer, always listening to your customers and paying attention to the problem customers have not solutions. 

I’ll tell you a problem I have. I don’t have 100 five star reviews on Amazon or Audible. If you have read The SaaS Playbook and you think It’s worthy of a five star review, I would really appreciate it. If you go to amazon.com or amazon.co.uk or Audible, wherever you bought the book and leave a five star Review, it would mean a lot to me and it helps me tremendously in being able to spread the word about the book. 

I believe The SaaS Playbook across the Kickstarter and all the other sales through the website and the Amazon ecosystem, and Apple Books, and all that, I believe it’s north of 5,000 copies sold now. I think it might be north of 5,500 if I’m honest, which is pretty dang good for a self-published book. I’m looking to continue to push that forward. I truly appreciate any support you’ve lent. I know many of you listening to this back the Kickstarter or have since bought the book from saasplaybook.com or Audible or Amazon. And again, I’m on a drive to get to 100 reviews on Amazon and Audible. I truly appreciate any help you can lend. With that, I’ll wrap up this episode. I will talk to you in one week. This is Rob Walling signing off from episode 680.

Rob Walling:
It’s another episode of Startups For the Rest of Us. This is one of these 0.5 episodes where we insert announcements and things that are not normal startups for the rest of us full episodes, we tend to drop these now and again on a Thursday. Today’s episode is all about the future of MicroConf, where I make seven announcements about new things that we are doing in the upcoming year. I’m really excited about what we are up to over the next 12 months. The last time we did a future of MicroConf announcement was four years ago. In 2019, we announced the launch of MicroConf Connect, of our YouTube channel, of our video vault. We announced MicroConf locals. There were several other super interesting things in that announcement, all of which have come to fruition. 

So when we make this proclamation and we look ahead and like Babe Ruth, we call our shot of what’s going to happen in 2024, I hope that you can get excited about this as well. Everything we’ve developed here and are planning on launching is from feedback from folks just like you, from podcast listeners, from folks in MicroConf Connect, from folks at our in-person events. So without further introduction, I’m going to roll the audio. It’s seven announcements packed in to five and a half minutes. And if you have any questions, comments, or thoughts once you’ve heard them, you can head to Twitter, @robwalling and @microconf. 

Whether you’ve been part of MicroConf for years or you’ve just recently joined our crew of misfits, you know that we’re all about helping you build and scale your SaaS company. From our humble start as a 100 person event in Las Vegas to where we stand today impacting more than a hundred thousand bootstrap founders around the world through MicroConf Connect Mastermind Matching, our in-person events and all of our other offerings, MicroConf has played a huge role in igniting a global movement for software entrepreneurs. And in 2024, we’re kicking it up a notch. Today I have seven announcements for you, so let’s dive in. First up, big news for our online community, MicroConf Connect. We’ve leveled it up and are reopening the doors to new members. MicroConf Connect is our online community and virtual hallway track. It’s a vibrant community of SaaS founders helping one another, discussing wins, challenges, and how to grow faster. 

A couple months ago we paused new signups to improve the platform based on your requests and the good news, applications reopen next week. The wait list is already 1500 strong and with MicroConf Connect 2.0, we’re rolling out three membership tiers packed with new perks, like weekly coworking, exclusive discounts, a searchable content library and more. Announcement number two is that the state of independent SaaS report is back. We took last year off because frankly between 2020 and 2022, not a ton had changed with the companies that we were serving. But the bootstrap SaaS landscape has since been shaken up by the rise of remote work, no code and AI. This has fueled a new wave of entrepreneurs and created new ways for existing startups to level up. So with that, I’m excited to roll out our completely revamped state of independent SaaS survey and report. 

Teaming up with DemandMaven, we’re going to offer go-to benchmarks for the bootstraps SaaS world. Over 2000 founders have taken the survey to date, and this year I hope to add your experience to the report. Next, we’re putting the power in your hands to bring a MicroConf local in-person event to your city. Until now, we’ve picked locations based on our assessment of which cities could use an in-person event, and in 2024, you get to decide. We’re going to run a community voting campaign to help choose which cities we visit next. With almost 100,000 entrepreneurs globally engaged with MicroConf, your city shot at hosting the next MicroConf local means you’ll need to rally founders in your community to get the most votes. Announcement number four is our debut course, Starting Up From Idea to Traction. It’s designed to kickstart you on your entrepreneurial journey as you launch your SaaS product. 

I know that many of you are stuck in startup limbo full of ideas, but unsure how to get started. And this video course tackles exactly that guiding you through idea generation, validation and finding early traction. Whether you’re a first timer, a pivoter, or a serial entrepreneur, this course aims to help you take your next SaaS venture to escape velocity. Also, in 2024, we’re going to help you find a co-founder. Almost every day we hear from folks in the MicroConf community who are looking for a co-founder. We know that finding the right partner in crime can be a make or break moment for your startup. Whether you’re a tech wizard with zero marketing chops or a sales pro looking for someone to build your product, we will help you find someone that compliments your skill sets, your goals, and your personality. Drawing on years of experience observing co-founder hits and misses, we’re designing a data-driven matching service to help you find your ideal co-founder because we know that the right partnership can have a huge impact on your success. 

Announcement number six is Team Sync by MicroConf. We’re hosting an event where you can host your team retreat. We’re merging two needs into one in-person event. So first, you’re going to soak up best practices for managing a remote team, curated by our team of experts in remote work and second retreat into your own team huddles. We’ll handle logistics while you focus on strategy and connection. Ideal for remote SaaS teams of five or more, this will be a game changer for team coherence and productivity. Next up, we’re going to start hosting exclusive intimate experiences called MicroConf Platinum Events. Imagine getting tailored advice about selling your company while sitting poolside with 15 other seven or eight figure founders or boosting your enterprise conversions during a trek to the bottom of the Grand Canyon. We’re rolling out small curated experiences that combine unique settings with laser-focused business goals, meet like-minded, high achieving founders and experts ready to elevate your game. 

And of course, we’re going to keep running our annual flagship conferences, MicroConf US and MicroConf Europe, as well as MicroConf Remote, which is our online conference that focuses on early stage SaaS marketing in the fall and SaaS sales in the spring. And of course, we also have our Mastermind Matching podcast and YouTube channel. And if your SaaS is growing, but you’re looking for the perfect amount of funding and mentorship to help take you to the next level, TinySeed is our investment fund and startup accelerator aimed specifically at bootstrap SaaS founders. So there it is. That’s your glimpse into the next era of MicroConf. 

I know I’m biased, but I firmly believe that our community of misfits is one of the best in the world. My team has spent the last several months working nonstop to nail down this pretty incredible lineup focused on helping you be more successful faster. I hope you’re as excited as I am to see these play out over the next year. I can’t wait to continue helping you find success on your founder journey in 2024. All of these programs will be launching over the course of the next year. So head over to futureofmicroconf.com to sign up to be notified as they launch.

Rob Walling:
In a phased launch, you get them in, you realize, “Oh, pricing’s screwed up, don’t have the features.” And then you correct that. You launch to the next few 100 people. I’ve done it myself. I’ve seen other folks do these phased launches. And that is, I would say a much, much more optimal way to bring a product to market. 

Welcome To this episode of Startups For the Rest of Us. I’m Rob Walling, and this is the podcast where we talk about building amazing, bootstrapped, and mostly bootstrapped companies to change our little corner of the world. We believe that you don’t need venture capitalists to start your company. We’re not anti venture capital, but we’re anti the narrative that the only way to start a tech company is to raise buckets of funding. This week I’m answering listener questions on topics ranging from building mock features. It’s a really interesting Twitter thread I want to talk about in this episode, how to recover from a failed launch, creating content for your SaaS tool that is outside of your expertise, and more. 

Before we dive into that, I’m on a mission to get to 105 star ratings on Amazon for my new book, The SaaS Playbook, Build a Multimillion Dollar Startup Without Venture Capital. If you have bought the book and you enjoyed it and you think it deserves five stars, it would be amazing if you could go to amazon.com and whether it’s dot com or whether it’s your country’s extension of Amazon, a five star rating and maybe a comment, would really help me out. 

I kind of chuckle because as I record this, The SaaS Playbook is the number one new release in the venture capital category of Amazon. I think because it has the word venture capital in the subtitle because the subtitle of the book is Build a Multimillion Dollar Startup Without Venture Capital. And the book has already been a number one new release and bestseller in several different categories ranging from entrepreneurship to, there was one really esoteric one that I don’t remember, but it was kind of a subcategory of another tech entrepreneurship thing, and today, it’s venture capital. So again, would really appreciate it if you could potentially give me a review there. 

And one more thing – We’ve recently re-opened the doors for our online community, MicroConf Connect. MicroConf Connect is our virtual hallway track. It’s a vibrant community of SaaS founders helping each other and discussing wins, challenges, and frankly how to grow faster. A couple months ago we paused new sign-ups to improve the platform based on your requests. With MicroConf Connect 2.0 we’re rolling out three membership tiers packed with new perks like weekly co-working, exclusive discounts, a searchable content library, and more. Whether you’ve been a member of Connect or not, you really should check it out, Microconfconnect.com. And with that, let’s dive into listener questions. 

My first one is not a question, but a comment from listener Tom who is commenting on episode 671 all about hard work, luck, and skill, where I talked a lot about how success is a combination of these three things, hard work, luck, and skill. Tom says, “Just a thank you for your podcast keeping me going, slapping me upside the head sometimes to keep focused and persevere.” And thanks for that note, Tom. I always love hearing from listeners even if they don’t have a question and they just want to thank the show for keeping them motivated. 

Because that’s how I think about it too, I don’t think of it as Rob is keeping me motivated. It’s the show. Startups for the Rest of Us is its own entity, its own flywheel, that keeps going every week and it delivers value back to me in terms of motivation to keep shipping and I hope that it delivers value back to you in terms of strategies and tactics to implement to grow your startup faster in terms of motivation and inspiration. Whether it’s me talking about solo topics or me interviewing someone on the show, I try to bring a variety of topics and thoughts and concepts to the show to keep it feeling new and to help you get where you’re going faster. So thanks for that comment, Tom. 

The next topic I want to cover is from Twitter from Ab Advany, and we will link up this thread in the show notes, but I was impacted by the genius of Ab’s approach and we were talking about it in the TinySeed Slack and several people commented about how they’re either doing this or would consider doing this, and I think it’s a really clever hack. The tweets go like this, “Mock features for B2B SaaS. It’s one of the techniques I’ve used in the last 10 years to sell $6 million worth of software licenses. When you were selling software above $1,000 a month, there is a weird dynamic happening that doesn’t occur with lower pricing.” And Ab continues, “We would build mock features that the buyer would demand before purchase, but were almost never used by the super user or end user of the product.” 

Let me give you a very specific example, and this is me chiming in. I used to call these checklist features. So when we were growing Drip, people would say, “Do you have split testing because we need to split test everything?” And eventually we built split testing and 1% of our users used it, but everyone thought they wanted it. Aspirational features, or checklist features, is what Ab is talking about. Ab continues, “A buyer who wanted to buy the software for $10,000 a month on a two-year license, so if you do the math on that, that’s a quarter of a million dollars. This buyer requested that there be an ability to build a report generator with 20 different kinds of filters, and we said we can do that, but we only built it as a mock feature in the following way. We added a button deep inside the software that only specific customers could see. When clicking it, they could request a report with all the filters. After submitting, we showed it will take 48 to 72 hours to generate. You will receive an email when it’s finished.” 

This is so great. “But guess how many times the feature was used in the two years the customer licensed our software? Zero, nada. We have built more than 50 of these mock features in the last 10 years. Some were requested and we would then manually execute them, but most were never used. These kinds of mock features only work if the buyer isn’t the same person as the end user or the super user. Most buyers don’t know their own users and come up with ridiculous demands during the sales process. Mock features are an easy way to increase your closing rate.” 

So I really appreciated that thread. I think it’s a great idea, and again, it doesn’t work when you’re building software for $100 a month or when you’re selling to the end user. But if you are selling to some corporate procurement person, Ab is 100% correct. I’ve seen it myself. Ridiculous checklist requirements are very common, and I thought this idea of building mock features was too smart not to share on the show. 

My first question question of the day is from Laszlo Kiss about how to recover from a failed launch.  

Laszlo Kiss:
Hi Rob, this is Laszlo. I previously asked you about better to further development game platform or get into the SaaS business. I followed your suggestion and my own feelings and began to concentrate on my SaaS project named Real Feedback. It’s an AI powered user feedback chatbot. However, I made some mistakes with the launch. It gained significant traction initially, but I launched too soon, so the product wasn’t very stable yet and the pricing plan weren’t properly figured out. Since then, I’ve improved the product and that fired my first users, but the initial hype has completely disappeared. Do you have any strategies for recovering from a failed launch like I had? I would really appreciate any advice on relaunching and regaining momentum after messing up the initial release. Please let me know if you have any suggestions.  

Rob Walling:
As always, voicemails and video questions go to the top of the stack. Thanks for this question, Laszlo. It’s tough to have a failed launch like that. It’s not uncommon. Most of us don’t have product market fit. None of us really have product market fit before we launch, and that’s why the way around this is to start marketing the day you start coding such that you have a list of 500, 1,000, 10,000 people interested in your app such that you don’t have to do the public launch until your product is ready, until you have an idea that you do have some product market fit. And so if you’d had that launch list, you could have trickled out to 50 people or 300 people. In a phased launch, you get them in, you realize, “Oh, pricing’s screwed up, don’t have the features.” And then you correct that, you launch to the next few hundred people. 

I’ve done it myself. I’ve seen other folks do these phased launches. And that is, I would say a much, much more optimal way to bring a product to market rather than try to do the big product hunt, Reddit Hacker News launch where this is what you run into, and now you find yourself in a more challenging situation. I’ll say it’s certainly salvageable. The way I would think about it is, I now have a better product and I now have my pricing dialed in more and I’m ready to take it to market. 

And so, if there were other launch avenues that I could tap into, let’s say you didn’t do a product not launched, then now I would launch it. Alternatively, just market it like every other SaaS product. People think that a launch is so important and in fact, so many of the products that we see being successful had mediocre launches at best, or maybe they didn’t do some big launch. They really just started cold calling, cold emailing, they started content, SEO, integrations, partnerships, all the blocking and tackling that it takes to grow a SaaS app. 

So can a launch get you a few customers, a few dozen customers, a few 100 customers? Maybe. But you don’t need that to build an incredible 6, 7, 8 figure SaaS company. So I wouldn’t take it too hard in terms of the launch failing. I would chalk it up as a learning experience. I hope that folks listening to this podcast will learn from it and I would get to work on marketing the product. 

One last thought on this is with Drip, we did do a Drip 2.0 launch, because the 1.0 launch happened in, say, November of 2013, and we peaked at 8 or 9,000 MRR and then plateaued because to your point, our pricing wasn’t figured out, our features were not there, we didn’t have product market fit, and we spent the next nine months agonizingly moving towards product market fit, and eventually we had it in August of 2014. And I wanted to do essentially another launch to the world, and so I called it Drip 2.0 and I described our journey. I described how we built something people didn’t want early on, and then how we found product market fit and how we saw trial to paid accelerating and our churn plummeted and it was very obvious that we had it. 

And so, I launched Drip 2.0 and I hit the product hunt and our original launch email list and, frankly, my personal email list. And all the places that you would do a launch, I hit them again and I said, “This is Drip 2.0. Here’s what I learned and here’s why this is interesting.” I’m really relaunching something that’s not totally different, but that now is a much, much better product, and something that you’re more likely to be interested in. So that’s another alternative, is you can do this like 2.0 launch or revamp launch where you say, “Oh, remember how we launched and that thing wasn’t that great? Well, it is great now because we learned a bunch and encourage people to give another try.” 

My next question is from Zach asking for advice for a consumer vitamin product. “Hey Rob, I’ve fallen in love with a product to scratch my own itch. It’s absolutely a vitamin.” So you’ve heard me say aspirin and vitamins, aspirins solve a desperate pain point and vitamins are nice to haves. “It’s also consumer facing, not for businesses. It’s completely free for now. Maybe I can add display ads if enough people use it. I know there are a lot of red flags here. The early feedback is pretty positive, but some mixed feelings. Do you have any advice for navigating a consumer facing vitamin product? My itch has been scratched, but it’s hard to know how much energy to put into a product like this.” 

This is kind of within my policy of not answering questions like this on the podcast. And I don’t mean to be glib about it, but I can’t help you, because consumer facing products are a completely different world. I have owned a couple of them and they are not in my wheelhouse and they’re not something I enjoy dealing with. The churn is way too high. If you’re not Netflix or Disney, they’re very, very, very difficult to grow. And no matter how much I say this, people continue to do it and that’s fine. But this show, my expertise, I just can’t help you. 

And especially if it’s consumer vitamin. Are there some that are successful? Have I seen some get huge traction because of virality or because they figured out Instagram ads? Of course. In your shoes, I would not ask me. I would look for an expert on that topic. Is there a podcast, YouTube channel on someone who builds consumer vitamin products, because they’re going to know so much more about it than I will. And I have kind of this, it’s a little bit jokey stance on this podcast, but I’m kind of serious about it. I’m not going to answer questions about two-sided marketplaces about bootstrapping them unless you already have one side of the marketplace, because my answer is just don’t. 

And same thing with a consumer vitamin product. I can’t give you advice, because my advice is don’t do it. It’s scratch your own itch. That’s great. Don’t put any more time into it and start a B2B SaaS. Do the stair-step approach. Do one of the other approaches that I’ve seen be so much more repeatable and work for so many more people rather than going down this path that I have seen fail for myself and hundreds if not thousands of other aspiring founders. So I do appreciate the question, Zach, and obviously I wish you the best of luck, and I’m guessing there is a chance that you can make this work, but unfortunately I’m not the person to weigh in on this because I just can’t help you like I can with B2B SaaS. 

My next question is from Jordan Riddle.  

Jordan Riddle:
Hey Rob, this is Jordan Riddle. I’m in Columbia, South Carolina. Just want to say thanks for everything. I’ve been following you for a while and it’s been really helpful. My question is about coming up with organic content for my SaaS tool. So I’ve created a tool that’s not really in the space where I have worked before. So I’m struggling with creating content because I don’t know a whole lot about this space, but I still feel like it’s a useful SaaS tool. So what I want to know is how you just juggle creating content and where the best bang for your buck is of coming up with organic stuff, if I should do it myself, if I should get a part-time job and then hire a writer to do it for me. Just looking for some insight on what’s the best way to go about that. Again, thanks for everything and I look forward to hearing from you.  

Rob Walling:
Thanks for the question, Jordan. It’s a good one. I’m sure it’s something other people have run into. So first off, I want to say this is the challenge of starting a tool catering to folks that are outside your profession. Now, I know a lot of folks who do it and are successful. Some of the approaches they take is they don’t necessarily create content, they do cold outreach, they go to in-person events and trade shows, integrations and partnerships. It’s the 20 B2B SaaS marketing approaches I outline in the SaaS Playbook. And they execute on all of those. They don’t do the content and SEO plays because they aren’t an expert. So that’s one way to think about it. 

Another is to hire a writer, as you said. You said get a part-time job so that you can hire a writer. So it depends on what your financial situation is, but certainly if you’re catering to accountants or salon owners, you can find an accountant or a salon owner with some spare time or someone with knowledge of these topics, whether it’s on Upwork or a writer’s marketplace, and you can find folks with expertise in these fields. Another option that I’ve seen is to bring a co-founder on for whether you have the developer entrepreneur, then you have the subject matter expert, and that subject matter expert has that expertise in accounting, bookkeeping, or in interior design. And that is a relatively common founder combination that I see in the MicroConf and TinySeed communities. 

So I guess to summarize, you have a couple options. One is don’t create content, just do all the other marketing approaches or just pick one other frankly and execute on that to where you don’t need the expertise to create the content. The second one is, yes, hire a writer with subject matter expertise, not a generic writer who’s going to have to learn it like you would. And I would not encourage you to, say, use ChatGPT or other AI because I think without the expertise yourself, it’s going to write really bland content. Because the content I see around topics that I know and understand, I can see through it pretty quickly. I think the AI generated stuff, it just isn’t there yet. And so if you don’t have that last 20% to get it, again, it’s 80/20, Where AI can maybe get you 80% of the way there. But if you don’t have the last 20% yourself, I think it’s a tough road. And if you’re competing against other people who actually have the expertise and are trying to rank for these SEO terms or folks who are doing the content pop where they’re trying to get virality on the Hacker News, the Reddits and such, I just don’t think you’re going to do it with AI generated content at this point without human involvement. 

I will say that one of the very first businesses that I built, in fact several of the businesses I built, I didn’t need content for. And we see a good chunk of TinySeed companies, which is a sample size that I have, or maybe it’s just all my investments. I think I have 151 B2B SaaS investments. There are a lot of them that don’t use content and they use the other marketing approaches. And so, I wouldn’t necessarily say that that is the one way to go. If you can make it work, it’s a great scalable, sustainable flywheel to build, and there’s a reason a lot of people go in on it, but it’s not a hard requirement to build a great company. So thanks for that question. I hope it was helpful. 

My last two questions are a little different than the ones I often answer, but I was intrigued by them. This first one’s about being an employee of an early stage startup and the last one’s about consulting and contracting, which I think a lot of us think about, especially early stage founders who maybe are trying to quit the day job and get to working full-time on their startup. I think hearing more about these topics can be helpful. 

So this first question is from Tyler and he asks, “I’m just joining a seed stage startup with a lot of traction. I’ll be basically the third full-time hire, and I have a sense that the business is looking for an acquisition during my tenure, which is likely if they’ve raised funding. It’s a small engineering team. It’s just me. I’m excited about what an acquisition means for my equity and also for my resume. And I’m also curious about what a typical acquisition looks like for a small team of a recently acquired SaaS. As anything in business or software goes, I’m sure the answer is it depends, but I’d appreciate it if you could lend insight on this situation. Say a small company gets acquired and has a solo engineer with equity, does that engineer usually get hired to the acquirer? Do they ever get contractually obligated to stick around for equity to vest, i.e. to help with a smooth transition, or is it usually a clean break? Are the single trigger/double trigger clauses the only mechanism at play here? Or do businesses have some other way to determine what is required of the team? Personally, I’m excited to experience any outcome. I’m just curious how you would conceptualize your future if you were me and assuming a desired acquisition actually happens, of course.” 

So yeah, I think it’s an interesting question. Of course it depends, but realistically, in almost all of the acquisitions that I see, maybe it is truly all, but in 99 plus percent, the acquirer wants the team. The acquirer wants the team. It’s very unusual that they just are acquiring technology, and unless you’ve built some amazing novel tech, the team is one of the most valuable pieces of it. So the first question, does the engineer usually get hired to the acquirer? The answer is usually yes. Do they ever get contractually obligated to stick around for equity divest? So that’s going to depend on your equity agreement with your current employer. 

When I have issued equity in the past, I have made it fully vest if we were acquired, because I wanted my people to own that equity or own those options or be able to purchase the options when the acquisition came through such that they were not compelled to stick around by agreements we had already made, but that the acquirer, if they wanted them to stick around, could make them an offer for additional stock options or additional incentives to stick around. So I have heard of founders being contractually obligated to stick around in order for equity to vest. It’s often called a key person clause where in order to get the full purchase price, you stick around for a year or two years or three years, but usually, not in all cases, usually what I’ve seen is that for employees or engineers, they are offered a new grant of stock options in the acquiring entity and then that starts vesting over usually four years. And so that really is the motivation to stick around. 

It obviously depends on your specific agreement and how your options are vesting, and if they don’t have that acceleration clause and you have options that are in the middle of vesting, let’s say you’re two years into your four year, I suppose the acquirer could elect to have all of your stock vest instantly and then issue you new, or they could just say, “Well, we’ll roll that into the acquiring company.” Could that happen? Yeah. Have I seen it happen? Not a lot. I also think the size of the acquisition is going to dramatically impact this. If you’re part of a company, as you said, where you’re the only engineer, it’s going to be different than if there are 1,000 engineers. But thanks for that question, Tyler. I hope it was helpful. 

Last question of the day comes from Jay Lee asking about consulting for software engineers.  

Jay Lee:
Hey Rob, huge congrats in your new book, The SaaS Playbook and thanks always for your podcast. So my name is Jay, I’m from Southern California, and I had a quick question about consulting. So it’s not about SaaS, but you do mention consulting quite a lot, especially related to your early days. As someone who is a software engineer and my background is from big tech, I know pretty much nothing about consulting. I know it’s about helping people and giving advice, but what is consulting? Could you give us a one-on-one breakdown? How do you find your clients? Do you just start in your network? What’s the pay like? Can a junior engineer or a mid-level engineer also be a consultant? And generally things like that, because I would really like to know what my options are aside from just engineering. Thanks so much.  

Rob Walling:
Thanks for the congrats on the book, Jay. So when I use the term consulting, really I did some consulting. I did a lot of contracting. And the way I think about it is if you’re a software developer, contracting is where you’re writing code for dollars per hour. And so originally I was writing code for $60 an hour, and then I started blogging and making a name for myself around 2005. Suddenly I had people coming directly to me. I could go get retail rates of $100 an hour, and then it was 125. And then I think by the time I stopped contracting, consulting, it was 120, 150 an hour. 

Now, if you go to an agency these days and you’re going to contract for them and just write code dollars for hours, basically you could call it you’re a 1099 contractor, the rates are going to vary, but you’re going to get lower rates if you go through an agency versus finding clients yourself. And you’re also going to get a lower rate if you go onto a marketplace like an Upwork. But Upwork can be a great source for finding new clients. So I often use consulting and contracting interchangeably. They aren’t exactly the same. I think consulting is more about giving advice and not implementing, and contracting is usually about someone who is doing the work. It’s a software developer who is writing code. And I did a bit of both, but certainly what paid the bills was contracting. 

And then Jay, you asked about how do you find your clients? Do you start with your network? Yes and yes. What’s the pay? It depends on where you live. It depends on the kind of work you’re doing. Honestly, you can charge $10 an hour if you live in the Philippines, and you might charge 150, $200 an hour if you live in Los Angeles. Can a junior engineer or a mid-level engineer be a consultant? Yes, they can. I think to start off with, you want to find people who need software development or web development or whatever your expertise is. They need help with that. And this might be big companies, it might be small companies, or it might be someone who’s looking on Upwork to have you do a little one-off project. One-off projects sound amazing and like you’re going to have a bunch of freedom, but realistically it’s so feast or famine. 

I used to work project basis and I would make $15,000 in one month and then I’d make $0 in the next month, and that wasn’t a great feeling. And I would be stressed of when’s my next project coming along versus if you can find someone who can put you to work for 10, 20, 30 or full-time every week. Honestly, you’re less of a consultant contractor and you kind of become, you’re not an employee per se, but it becomes more of a consistent income for you. That’s what I think of as being self-employed, you’re not actually in control of your own schedule, but you’re not an employee. It’s kind of being in between. There’s employed, there is entrepreneur, and there’s being an investor. Those are the four links up the chain. 

And being employed, we all know what that means. Self-employed is when you’re selling dollars for hours, whether you’re consulting, whether you’re a contractor. If you’re doing it individually and let’s say you’re running a full service organization where you have 30 developers working under you and you are now just doing sales and operating the company. That’s when you’re an entrepreneur, when you’re leveraging other people’s time to generate revenue. If you’re still leveraging your own time as a consultant or a contractor, that’s when you are self-employed. And obviously being a SaaS founder, that’s where I would say, “Oh, you’re an entrepreneur there because now you’re leveraging technology in order to make more money than you could make by charging dollars for hours.” 

So the only reason I’m weighing in on this is because I did this myself and I moved from W2 employment to being a freelancer/contractor/consultant, which I’ll just say they’re different, but they’re kind of all the same thing for the purpose of this conversation. And that helped me transition to having products full-time because I was stair stepping on nights and weekends while I was doing this. And then I was able to dial back my contract work from five days to four days to three days as my product scaled. And it was a nice balance for me where I didn’t have a boss, per se, I did have a client or two, but it was a good in-between for me. And that doesn’t work for everyone. I hear some people say they just can’t manage it all and it’s too hard to work on your own products that aren’t really making much money when you can bill $150 every hour for 40 hours a week. It is hard to say no to that contract work, because the money is “easy” compared to building your software product or building up revenue for a SaaS product. 

So there are trade-offs there. I’m guessing there have to be better podcasts or YouTube channels for this particular question. If you really want to get into, “Hey, how do I transition from full-time work to being a contract or consulting developer?” I don’t know any off the top of my head, because it’s just not an interest I have these days. But I would certainly look around whether you ask on Twitter, whether you head to Apple Podcasts or YouTube to look for folks, like What is the Startups for the Rest of Us equivalent show for folks who are in your situation and looking to get into that self-employed contractor freelance game. So thanks for the question, Jay. It was a good one. As I said, it’s a little different than I often answer on this show, but I felt like a lot of folks might be thinking about the same thing. 

And with that, I’ll remind you that I am on a quest to get 105 star Amazon reviews for the SaaS Playbook and would really appreciate if you loved the book and you feel like it’s five star worthy, heading into Amazon and giving it that five stars. Thanks for joining me this week and every week. This is Rob Walling signing off from episode 679.

Rob Walling:
Platform risk exists in a lot of apps and it certainly exists in the stair-step approach, and what I don’t say is, “Then don’t do it because there’s some risk.” Realize what you’re getting into and realize the risk is there. Think about how to potentially mitigate it or just live with the risk and realize, “This is not a 20-year business. This is a business that’s going to get me to the next step to where I could potentially get away from the platform risk.” 

Welcome to Startups For The Rest Of Us. This is the podcast where we talk about building companies that are unlikely to change the whole world, but very likely to change our little corner of it. 

I’m Rob Walling, I’m your host and this week I’m going to be answering listener questions. Before I dive into those, I wanted to ask if you have read the SaaS Playbook, my most recent book, saasplaybook.com. If you could go to Amazon and leave a five star rating for me, the ratings go a long way towards helping other people discover the book and they’re a strong signal to folks who may have never heard of me and are considering buying the book based on the name and the cover and a recommendation. And in fact, it looks like there’s one or two folks who have something out for me because I believe I have a two star review that says something to the effect of, “This book is really light on actionable information,” and I chuckle because it’s just a very dense book and it’s full of self-promotion and the book fell apart. 

“I got the book and it just fell apart at my house.” And I’m thinking to myself, if I knew who this person was, I would just send them another copy. But I genuinely think they’re either out to troll me directly or just in general are trolling Amazon authors. I don’t know. If the book falls apart, email Amazon and they’ll send you a new book. But with that said, it would be amazing if I could get a few more five star reviews and help out the average on this new book. 

Before we dive into the episode, I have two announcements for you. The first is that TinySeed applications for our fall 2023 accelerator batch will be open from September 4th to the 16th. We are funding companies in two batches. We have our Americas and our EMEA batch, that’s Europe, Middle East and Africa. And if you have at least $500 in MRR and you are looking for the perfect amount of funding as well as world-class mentorship, you can’t get anywhere else, and a tight-knit community, unlike any you’ve been part of, head to tinyseed.com/apply. If it’s from September 4th to the 16th, applications will be open and you can apply there. It usually takes about 10 minutes. If they’re not open, you can enter your email to be notified when we open the doors. I hope to see your application. 

My second announcement is that while some of you might have spent the summer vacationing or spending time at the lake, our team at MicroConf has been gearing up for one of the biggest announcements we’ve ever made. The last time we made a major announcement was in 2019. I don’t want to jinx it, but there are some pretty amazing things coming down the line to help you build, launch and grow your SaaS business. If you want to be the first to hear about it, head over to futureofmicroconf.com and sign up for our announcement event. It’s going to happen on September 14th, 2023. You won’t want to miss it. 

And with that, let’s dive in to my first listener question.  

Speaker 2:
Hi Rob. Big fan of the podcast. I have a question for you. I recently made my first SaaS product. I am not a developer myself. I teamed up with a team of student developers. I realize now that I’m in over my head. I didn’t know that so many things could break and that it would be so challenging to maintain a SaaS product over time. I have some early traction in the sense that I have a few people placing test orders and quite a lot of interest, but I want to exit this thing as soon as possible because I’m pretty sure that if I keep it I’m going to drop it and it’s going to break. 

My question is are there any communities or platforms where you can sell SaaS products that are only half done or what would you do in my situation? Thanks.  

Rob Walling:
Thanks for the question, Max and for keeping it succinct, Max actually sent a second voicemail that gave me more context, but that really, you don’t need to hear all of that, and he did a really good job of keeping it as a succinct question that I can answer on the show. Probably the only additional piece of information he gave that is necessary for you to understand the problem is the product itself is in Dutch, the market of people who could potentially buy it is obviously a lot smaller than if it was in English. 

Definitely a tough position Max, and frankly there aren’t any places. Basically you don’t have any value until you have customers or I should say very, very little value. Could I imagine paying a thousand dollars for a code base with a few customers? Maybe. If you found a strategic who really needed this, and again it being in Dutch in that case is a challenge because it really limits who you can sell to, but realistically, products sell based on revenue, traction and growth and until you have that you have nothing. 

If I were to do a hot take on Twitter, I would say you have zero value until people are paying you money. That’s not totally true, but mostly it is. And I don’t have a great recommendation of a place you can go to sell this, to be honest. What I do like about your question is you talked about how complex it is to build and run a SaaS app and people don’t believe me when I tell them they should stair-step and everyone wants to start a SaaS app and a lot of people run into what you’re running into and I feel your pain and I’m sorry that you’re having to learn this lesson this way. I’m sure it’s tough. I’m sure it’s a hard process for you to be going through. With all that said, the only recommendations I could make in terms of selling this, there are a handful of these side project marketplaces, acquire.com is the big one. 

You could of course list it there. Do I think you’ll sell it or get any traction? Probably not, but it’s worth it. It’s a marketplace and you can list it at an asking price. There used to be some others. There was 1kprojects.com, sideprojects.com are the other two and I believe one of them acquired the other or merged with the other and it’s a totally different domain name now, and I’m not going to pull up Google and go looking for these, but if you go to Google and search for those domains, you’ll likely find a couple other sites that are small and basically it’s Indie Hackers. It’s usually people who have indie hacked and launched on Product Hunt and they have $200 in MRR and they’re like, “I’m willing to sell this for a few thousand dollars.” Those are the types of marketplaces that I could recommend for this. 

And of course there’s communities. There’s MicroConf Connect. We actually stopped taking new community members into Connect over the summer as we retooled and revamped some things, but we are going to be relaunching that in the next couple of weeks. Had to microconfconnect.com, if you are interested, you can get on the wait list to hear more about it. But a community like that of other SaaS founders, you could feasibly go in and specifically look if there’s a Dutch channel or I believe there is a buy sell channel in MicroConf Connect where you could bring up this kind of thing and outline what you’re looking for and potentially get feedback or find a buyer. It’s a tough spot to be in. I feel your pain Max and I hope that was helpful. As a reminder, if you want to send a question in to be answered by me and potentially a guest in a future episode, startupswiththerestofus.com and look in the top nav for ask-a-question, audio and video questions go to the top of the stack. 

Although I will say in this episode, I do want to get to a few text questions since there are so many audio and video questions in the queue, I wanted to sprinkle a couple in. The next question is from Andrew and he says, “Hey Rob, I enjoyed your episode with Tara Reed,” so you can tell how old this text question is. That’s back when Tara and I talked about No-Code, the pros and cons of it. Back to Andrew’s email. “I recently sold my startup and I’m looking to start my next business. I’m not technical and No-Code is intriguing to me. One thing you didn’t seem to address is platform risk. If you build your business on a No-Code platform, what happens if the No-Code platform closes significantly raises prices or changes how it operates?” This is a great point Andrew, and what’s interesting is I believe this email’s almost a year old now. 

Sorry about that. That’s the backlog we have with text questions. But shortly after that episode with Tara Reed, I actually had a conversation on Twitter where someone else pointed this out as well, that platform risk is such a huge risk with No-Code. And a few months after that I recorded a YouTube video on the MicroConf channel, that’s microconf.com/youtube and we’ll link it up in the show notes, but it’s called The Number One Mistake No-Code SaaS Founders Make. And in it I talk about how Bubble had dramatically raised their prices and people were furious because migrating off of Bubble is really hard. Migrating off a No-Code is really hard. Compared to AWS, not that that’s a breeze, but if you have code that can run on any server, you can move from Heroku to AWS to GCP to Azure to your own homegrown Dell Box sitting in your bedroom connected to a fiber connection, which of course I wouldn’t recommend. 

But you get the idea. Moving code-code from place to place while it’s a pane is totally doable. No-Code’s not portable as far as I know. There’s no standard. You don’t export to XML or to JSON and move it into another No-Code platform. It’s all proprietary and it has massive platform risk. If they dramatically raise prices as several have done, if they change how they operate, which Airtable does about every month or two, they break, they don’t break it, I’m overstating it, but they break how our podcast and our video production systems work because they changed their top nav and they changed the left nav and they forced us to only have a left nav and we don’t really want to, but it’s No-Code and we can’t do anything. You are 100% at the mercy of the No-Code platform when you are building on it. 

I appreciate you writing in with that, Andrew, because we did miss it in the initial conversation. Since then have obviously done quite a bit of talking about it, but I did want folks to know, and I should add one other point here, that doesn’t mean you shouldn’t build something in No-Code. Platform risk exists in a lot of apps and it certainly exists in the stairs-step approach. And what I don’t say is, “Then don’t do it because there’s some risk.” Realize what you’re getting into and realize the risk is there. Think about how to potentially mitigate it or just live with the risk and realize, “This is not a 20-year business, this is a business that’s going to get me to the next step to where I could potentially get away from the platform risk.” Thanks again for that email Andrew, I appreciate you weighing in. 

Finding the perfect software engineer for your team can feel like looking for a needle in a haystack and the process can quickly become overwhelming. But what if you had a partner who could provide you with over 1000 on-demand, vetted, senior, results oriented developers who are passionate about helping you succeed and all that at competitive rates? Meet lemon.io. They only offer handpicked developers with three or more years of experience and strong proven portfolios. 

With lemon.io, you can have an engineer start working on your project within a week instead of months. Plus you won’t waste your time on candidates who aren’t qualified. 

Lemon.io gives you easy access to global talent without scouring countless job boards and it’s more affordable than hiring local talent and if anything goes wrong, lemon.io offers swift placements. It’s like hiring with a warranty. If you need to grow your engineering team or delegate some work, give lemon.io a try. Learn more by visiting lemon.io/startups and find your perfect developer or tech team in 48 hours or less. As a bonus for our podcast listeners, get a 15% discount on your first four weeks of working with a developer. Stop burning money, hire dev smarter, visit lemon.io/startups. 

My next question is from Franz about bookkeeping.  

Speaker 3:
Hey Rob, Franz here, longtime listener, started listening during the Hit Tail era. My question is, I’m not from the US, I’m not familiar with any the tax laws and everything there. How do I go about bookkeeping? Just background, just start my own SaaS, just took the plunge recently. Apparently I need a US entity to open a Stripe account, I did that, now I have a Stripe account, but now it’s think about, “What about bookkeeping like taxes in like March or April?” How do I go about it? Do I do it myself? It’s simple enough. Or do I get somebody to do it? And if I get somebody, that would take a chunk of money from my very early stage startup, do you have any suggestions how to go about that one? Thanks.  

Rob Walling:
This is a question of whether or not you want to take time away from your startup or money away from your startup. And if you don’t have funding and you are on a shoestring budget, paying for a bookkeeper can be a challenge to justify. I’ll admit that in the early stages of say, Drip, I was doing the books, wasn’t the best use of my time, but I just didn’t have the budget to pay someone like Bench. You go to bench.co and it’s 250 to $350 a month for them to do your books. I actually did hire a couple different bookkeepers on Upwork with varying degrees of success. Sometimes I had math errors in my books, other times categorization errors, and I was frustrated with my books for a very long time and eventually I just plunked it down. I actually talked to my CPA, my accountant and he started doing it for I think it was about $180 a month and I just bit the bullet and I moved on and I never looked back. 

I think in the very early stages of a startup where there’s almost no money coming in and mostly no money going out, signing up for Bench or Xero, which is X-E-R-O, linking up a credit card and a bank account or a Stripe account for that matter and letting most of it auto categorize and going in and spending 20 minutes a month, 10 minutes a month if you really don’t have much going on, I don’t think that’s the end of the world. The thing to be aware of and to be careful of is when that turns into a few hours a month and you’re still justifying to yourself that you should be doing it. By the time it’s complicated enough for you to be spending a chunk of time on it, you should have enough revenue to be able to go and hire a service. 

And Bench themselves, I’ve heard mixed reviews, I’ve heard some real positive reviews and other people it hasn’t worked for. I think it really does just depend on the bookkeeper you get in any given month. There are definitely services out there that are less expensive. There are zero approved bookkeepers and I think if you expect to pay a hundred dollars to $200 a month to do your books, that’s probably a reasonable expectation. I think in the very early days I would do it myself until it became a little annoying and then I would hire it out at that point. My next question is from John Potter and he says, “Hey Rob. I’m the non-technical co-founder of a bootstrap SaaS for accountants. I’m an accountant by trade, so I’m unfamiliar with how to set up the ideal marketing engine.” It’s good you’re listening to this podcast. I would also recommend purchasing the SaaS Playbook at saasplaybook.com and reading Traction by Gabriel Weinberg. 

His email continues, “I plan to focus my sales and marketing energy on my network first, but I will need to reach out to cold contacts eventually. I do plan to have a self-serve sales motion for a long time with no sales reps. Could you walk me through a few ways to set up a marketing engine for someone who has little marketing experience?” 

All right, John, here’s I think a big mistake that you’re making is if you’re going to sell to accountants, self-serve is 99% not going to work. Pretty much it’s not going to work. I never say never and always and these kinds of things, but I cannot imagine trying to sell to non-technical folks, especially folks who are busy and bill by the hour. We’re talking legal, accounting, consulting, non-technical consultants, coaches, you are going to want to demo to handhold and to get them on board. 

It doesn’t have to be enterprise sales, it doesn’t have to be five call closes, should be a one call close frankly, but I don’t think you will succeed without having some type of sales process. Accountants are just going to want to talk to someone and it doesn’t have to be complicated. It doesn’t have to be a long process. With that in mind, I literally wrote an entire chapter of the book, saasplaybook.com, it’s $10 on Kindle or on PDF and I talk about the three factor framework, which is that each marketing approach has these three factors that dictate whether you should try them or not. The first is speed. Is it slow or is it fast? Meaning does it work tomorrow or does it work in a year? SEO is slow, cold email could feasibly work quickly. It may or may not, but it could feasibly. 

The second is scalability. There are things like a Product Hunt launch that are not scalable. You can do them once and you get a few customers and that’s it. Versus SEO content, cold outbound, there’s things that really scale up. Often those ones are perhaps more expensive or more hard to get right, but the scalability of those is a far cry from something like answering questions on Quora or doing a Product Hunt launch. The third factor is cost. We could say that if you’re writing your own content, it’s free. We know that’s not totally true, but let’s just say in answering questions on Quora, which is something I did in the early days of Hit Tail and the early days of Drip and even a little bit in the early days of TinySeed, and I did that myself. The cost in effect was zero, but it was my time versus ramping up AdWords or paying a third party to do cold email outreach on your behalf. 

Those three factors are different for each marketing approach. And in my chapter on marketing, I go through the 20 B2B SaaS marketing approaches and then I talk about how to use the ICE framework to prioritize them based on the impact you think they might have, you’re going to take a guess at it, the cost to do it and ease of implementing it. And I basically walked through a framework that would make no sense to walk through here on a podcast, but is it foolproof? Is it 100% going to tell you exactly what you should do in what order? No, of course not. Being a founder is making hard decisions with incomplete information and figuring out which marketing approach to try first is a hard decision that you have no data on until you try it. And using a framework like I’ve outlined, and there are others like go look at Sean Ellis and his book, I believe it’s called Hacking Growth. 

He talks about ways to think about growing your company. This is just a matter of getting educated and realizing that there is no one right answer. There’s going to be a lot of gut feel in it, but you have to mix that gut feel with rules of thumb. And my rule of thumb is a three factor framework and Sean Ellis’ is different and Gabriel Weinberg’s, in Traction, is also different. These are just frameworks and mental models to help folks who haven’t marketed for learn, which marketing approach should I try first? And then you get to decide if I pick a marketing approach, like cold email for example, do I go and learn it or do I hire a productized agency, for example, Postaga, they’re a TinySeed company and they have a done-for-you outreach product as well as a SaaS app that you can use for your outreach, but do you hire someone like that who has sent tens of thousands, hundreds of thousands of emails and LinkedIn outreach and do you hire them to do it? 

Usually it’s budget, do you have the budget to hire them? So that you can test this and feel good that if it doesn’t work, the channel probably doesn’t work because the person or the team implementing it knows what they’re doing. They have a pretty high success rate. This goes back to the bad instrument or bad player analogy I mentioned on a recent solo episode where I talked about my 13-year old who is an amazing violinist. He’d been playing for 10 years and he picked up an old clunky violin. It was his first or second violin. It sounds terrible. He played it and it sounded awful because it’s just a toy, it’s like a hundred dollars thing and the strings are barely real strings. 

And if you walked into the room, you wouldn’t know is it that he has a bad instrument or is it that he doesn’t know how to play? And then of course he picks up a full-size violin. Sounds amazing. And that’s when you know that it was a bad instrument. With marketing approaches, if you try and approach and you’re doing the work yourself and the marketing approach doesn’t work, you don’t know if it was a bad instrument or a bad player. And I often encourage founders that I’m advising if you have the budget, try to find someone who’s good at this to test it out, to dip your toe in the water and to put your best foot forward such that if it does work great, and if it doesn’t, which is honestly the more likely outcome, then at least you know that you took the best shot you could. 

But oftentimes budget stands in the way and hiring someone good to do a marketing task is hard. It’s not as easy as snapping your finger and finding someone amazing. And sometimes it can be hard to know are they good at what they do or not? There’s some complexity here, but I hope that gives you an idea, John, thanks for the question.  

Speaker 4:
Hi Rob. Hi Steve. We met briefly, MicroConf in 2019 in Croatia. I was working on a different set idea back then, which unfortunately didn’t work out, classic, rookie mistake, building something that I thought somebody wanted, but turns out they didn’t. But that’s fine. I learned a lot. I’ve since moved on and I’ve had a new idea. It is essentially a SaaS tool for property finders in the UK, but particularly focused on foreign buyers trying to buy property in the UK. This time around, I’m going to do it differently. I’ve run a few Facebook ads to see if there’s any interest to try and get some emails to build a launch list. And that’s been really successful. We’ve 500 plus emails from foreign customers or foreign target customers, and that list is growing daily, I think that’s probably going to get to about a thousand. 

My question is what’s the best way to approach launching the new products to said thousand lead list? We’re obviously going to do an MVP. Is it 50 users at a time? Or the usual question of how big should the MVP be? And then final question, because I know a lot of our users are essentially coming to us through Facebook or Facebook leads, they’re obviously using their mobile phones. Now my question is that in terms of getting them to our sales website and buying and starting their subscription, what’s your views on Apple Pay? Can it work? Should it work? Does it work for subscription businesses like the one hopefully that we’re going to get going? Love the content and hopefully see you again soon. Cheers. Bye.  

Rob Walling:
Thanks for that question. I think there’s some good stuff to dig here. I actually recorded a YouTube video called, How to Build SaaS from Scratch in Eight Simplified Steps. It’s also on the MicroConf YouTube channel, and we will link it up in the show notes. One of those steps is the phased launch, and if you have a tiny little launch list of 30 people, 50 people, there’s no reason to phase it. What I mean by phases is breaking it up into chunks exactly as you have mentioned. But if you have a product that you’re not sure if you have product market fit yet, or even you’re concerned that you don’t have the features that you want or that it’s just not anything more than an MVP, then if you add thousands of people on an email list and you put them all into your product, they’re just going to bleed out. 

You’re not going to retain any of them. Everybody’s going to churn, no one’s going to convert. And the idea of phasing your launch is to let in a group of users to let them try it out. And this is not beta. This is early access. This is something you charge for. They’re not beta testing the product. You should have the bugs worked out, but you’re trying to find out do they need it? Do they love it? What else do you need to build in order to retain as many as possible? Then you rinse and repeat. Yes, if I had a list of 500 people, I probably would break it up into chunks of 50 at least to start with. With Drip, we had 3,400 people on an email list, and I think I started doing it in, I think the first launch was to 300, and then we did another 300, and I realized we could totally handle it. 

Then we went up to like four or 500, and I believe by the end we were doing 600 at a time for the last couple. And I just increased it as my comfort level improved, my comfort level with the product, my comfort level with our conversion rate, my comfort level with our ability to support it and to close deals frankly. Again, I have that YouTube video where I talk more about this and I have a YouTube video where I talked all about the Drip launch. I believe it’s titled, From Launch To 7K MRR, and it’s also on the MicroConf channel. And I probably spent 10 or 15 minutes talking about how we did it, and that was within six months of doing it. The data was fresh in my mind at that point. And then your second question was about using Apple Pay. 

I’m going to be honest, I’ve never used it and I’ve never heard, I don’t know of many SaaS apps that do it right. Most of the time that’s a mobile app. Now, can Apple Pay work for subscriptions? Of course. Now, I want to be clear here that Apple Pay is different than having an iOS app in the app store. In that case, Apple’s going to take 30%, but using my Google-fu, I have looked at Apple Pay, which again, I haven’t used, but it says that Apple Pay takes no fee. This is where you just allow someone to buy your app or charge a subscription, which Apple Pay supports according to the Apple website, and you still pay the typical charge, the 3% credit card charge, but Apple Pay is a layer on top of that. I guess a concern of mine as I think this through is can I administer that? 

Because we used to need to upgrade or downgrade subscriptions or refund subscriptions or do all types of craziness with it. And if I don’t have a dashboard where I can do that, and it’s all the customer themselves doing it through iTunes, I don’t know if that’s how it’s managed or not. Steven, in your shoes, that’s where I would want to see the entire flow from the start to the finish of how do they subscribe, how do I administer those, how do they cancel, upgrade, downgrade, do I have the flexibility that I want when using Apple Pay, or is it going to be easier and better for me to spend whatever three, four days upfront to really build out a top-notch custom, Stripe integration or Braintree or Paddle, whoever you want to use, such that I have full control? And that I don’t know because I just haven’t evaluated the two options side by side. But if you do and you have something to report back, feel free to send it, questions at startupsfortherestofus.com and we can educate the entire community with your findings. 

Those are all the questions we have time for today. Thanks so much for joining me again this week. I think I’m going to answer more listener questions next week as well to try to work through some of the backlog. I hope you join me for that episode. This is Rob Walling signing off from episode 678.