Latest / The Bootstrapped Tech Founder with Fexingo: Profitable Software Companies Without VC / How Bootstrapped Founders Decide What to Build Next
Transcript
- Lucas: So there's a moment every bootstrapped founder hits, usually about eighteen months in, when the product is covering rent, but the growth has flattened. And the question that keeps you up at night isn't 'how do I get more users', it's 'what do I build next'. That's what we're digging into today. Luna: And I love that you frame it as a decision, because it's easy to think 'just build more stuff' is the answer. But I've seen founders build themselves into a corner with a bloated product. Lucas: Exactly. So I want to start with a concrete story. There's a solo developer, I'll call him Marcus, who built a time-tracking tool for freelance designers. Not sexy, but it solved a real problem. He got to about two hundred thousand dollars in annual recurring revenue, and then growth stalled. His instinct was to add a whole suite of project management features. Luna: Because that's what the market seems to want, right? Everyone's comparing you to the big guys. Lucas: Right, but instead he did something counterintuitive. He set a rule for himself: only build what at least three paying customers have explicitly asked for in the last thirty days. No more. He kept a public roadmap, but he gated it behind that rule. And within six months, he'd shipped four small features that directly reduced churn among his most valuable users. Luna: So the rule is about demand validation, but it also forces you to listen to the people who are already paying you, not the ones who might pay you someday. Lucas: That's the key distinction. A lot of bootstrapped founders I talk to are building for the imaginary user who's going to come after they build that shiny new thing. But the data is right there in your billing system. The customers you have are your best signal for what to build next. Luna: And what counts as a 'request'? Like, does a tweet count? Or does it have to be in a support ticket? Lucas: Marcus was strict: it had to be in a support ticket or a form on his site, and the customer had to describe the problem in their own words, not just say 'I want a feature like Trello'. That forced him to understand the underlying need. He actually wrote a blog post about it, and he shared a spreadsheet where he tracked every request, the number of customers who asked, and the estimated revenue impact. Luna: That's a level of rigor most of us don't have. I'm guilty of just going with my gut. But the spreadsheet approach makes sense because it's a tangible way to prioritize. Lucas: And that's the thing, the spreadsheet is the tool, but the mindset is what matters. You're essentially running a tiny internal market for ideas. Each request is a vote, but not every vote is equal. A customer on your highest plan who's been with you for two years should weigh more than a free trial user who churns after a week. Luna: So how do you weigh those votes? Is it just about revenue, or do you factor in the strategic direction you want the product to go? Lucas: That's the tension. If you only follow customer requests, you end up with a product that's a pile of features with no coherent vision. But if you only follow your vision, you risk building things nobody wants. The best approach I've seen is to have a clear product thesis—a one-sentence statement of what your product is for and who it's for—and then use customer requests to test and refine that thesis. Luna: So the thesis acts as a filter. If a request aligns with the thesis, you consider it. If not, you maybe park it. But how do you handle requests that are clearly outside your core, but keep coming up? Lucas: That's where the 'no' gets powerful. Marcus had a rule: if three customers ask for something outside his core, he'd add it to a 'future possibilities' list and then he'd go back to those customers and explain why he wasn't building it, and what he was building instead. He found that most of them were okay with it, because he was transparent. A few even upgraded because they appreciated the clarity. Luna: So saying no actually built trust. That's a great takeaway. But what about the bigger question of 'should I build a whole new product'? That's a different beast than a feature. Lucas: For bootstrapped founders, a new product is often a trap. You're splitting your focus, your customer base, and your support time. I've seen founders launch a second product and end up neglecting the first one, which is their cash cow. The only time it makes sense is if the new product is so adjacent that it's almost an extension of what you already do. Luna: Give me an example of 'adjacent enough'. Lucas: Think of a guy who built a tool for freelancers to send invoices. He saw that his users were also struggling with contracts. So he added a contract template feature. That's not a new product, it's a deepening of the same workflow. A new product would be jumping into, say, accounting software—a totally different domain with different regulations. Luna: So the line is about workflow versus domain. That's a useful heuristic. I also wonder, how do you avoid the 'sunk cost' trap? Like, you've already built the foundation for something, so you feel like you have to finish it. Lucas: Oh, that's a killer. I've seen founders pour six months into a feature that no one asked for, just because they'd already started. My rule of thumb is: if you haven't had at least three customer conversations that validate the core assumption within the first two weeks of building, stop and reassess. The cost of sunk time is real, but the cost of a half-baked feature that confuses users is higher. Luna: And you can always repurpose the code later. But the user confusion is harder to undo. Lucas: Exactly. Another angle: some founders use a 'build in public' approach. They share their roadmap and ask customers to vote on features. That's great for engagement, but it can also create a popularity contest where the loudest voices win, not necessarily the ones that align with your vision. Luna: So you need to be careful about democratizing your roadmap too much. The votes are data, but you still need to be the editor. Lucas: Right. The way I think about it is like a restaurant. Customers can tell you what they're craving, but the chef decides the menu. If you just give people everything they ask for, you end up with a weird fusion place that doesn't do anything well. Luna: That's a good metaphor. So what's a practical framework for deciding what to build next, specifically for a bootstrapped founder with limited time? Lucas: I like a simple three-step process. First, collect every request in one place—spreadsheet, project management tool, whatever. Second, score each request on two axes: impact on revenue or retention, and alignment with your product thesis. Third, for the top two or three, do five thirty-minute customer interviews before you write a line of code. Luna: The interviews are the part most people skip. They think a few support tickets are enough. But I've seen interviews completely change what I thought I needed to build. Lucas: Absolutely. In the interview, you ask open-ended questions like 'walk me through your last week using the tool' and 'what's the one thing that frustrates you the most?' You'll hear things you never get in a ticket. Marcus told me that one interview revealed that his users were spending thirty minutes a week manually exporting data to a spreadsheet for their own reporting. He built a simple export feature that took him a day, and it increased retention by ten percent. Luna: Thirty minutes a week times fifty users is twenty-five hours a week of manual work. No wonder they were sticky once it was automated. Lucas: And that's the kind of win that doesn't show up in a feature request. It only shows up when you listen for the problem, not the solution. A lot of customers will ask for a 'reporting dashboard', but what they really need is a way to stop copying data into their own spreadsheet. Luna: So the takeaway is: don't just build what people say, build what they're trying to accomplish. That's a much more reliable signal. Lucas: And it's a skill you can practice. I'd say spend a week just watching how your existing customers use your product. Look at session recordings, note where they pause, where they get stuck. That's gold for deciding what to build next. Luna: Before we wrap, I want to circle back to something you said earlier about the spreadsheet and the customer interviews. That's a lot of process for a solo founder who's already stretched thin. How do you keep it lightweight? Lucas: Honestly, it doesn't need to be fancy. A simple table with columns for 'customer', 'request', 'date', and 'aligned with thesis' is enough. The act of writing it down forces you to be intentional. And the interviews don't have to be long—fifteen minutes each, once a quarter, with your top five customers. That's, what, a little over an hour of your time every three months. Luna: That's manageable. And it's directly tied to the decision-making, so it's not busywork. It's the highest-leverage hour you can spend. Lucas: One more thing. When you do decide to build something, scope it to the smallest thing that could work. Don't build the full vision. Build the core that solves the problem, ship it, and then iterate based on usage. Marcus's export feature started as a simple CSV download. Six months later, it had evolved into a full integration with Google Sheets, but only because customers actually used the CSV. Luna: So you let the usage guide the roadmap, not the other way around. That's a much healthier way to grow. Lucas: Yeah. And I think that's the key message for this episode: your existing customers are your best product advisors. They're paying you, so they're invested. You just have to listen in the right way. Luna: And if today's conversation helped you think about your own roadmap, I know we'd both appreciate it if you considered supporting the show. There's a link in the show notes where you can buy us a coffee, and it genuinely helps keep these episodes ad-free. It's buy me a coffee dot com slash fexingo if you're interested. Lucas: Yeah, no pressure at all. We just appreciate you listening. And on that note, I'll leave you with this: the next time you're tempted to build something, ask yourself who's asking for it, why they're asking, and whether it moves the needle for the people who already trust you with their work. Luna: That's a great way to think about it. Thanks for joining us, and we'll catch you next time.