Latest / The Bootstrapped Tech Founder with Fexingo: Profitable Software Companies Without VC / How Bootstrapped Founders Use a Public Roadmap
Transcript
- Lucas: So Luna, I've been thinking about something a lot of bootstrapped founders wrestle with, which is how much of your product plans you should share with customers. And there's a really interesting experiment I came across recently from a solo developer who runs a small project management tool. He decided to publish his roadmap publicly, and the results were pretty surprising. Luna: Public roadmap, as in just putting it on the website for anyone to see? That sounds a little scary, honestly. Isn't that just inviting competitors to copy you? Lucas: That's the instinct, right? But what he found was that it actually cut his feature-request emails by about forty percent in the first quarter. And the reason isn't that people stopped asking for things, it's that they could see whether their idea was already on the list, or they could see why it wasn't. That alone defused a ton of tension. Luna: So it's kind of like showing your work in math class. People might not love that the answer is 'no,' but at least they can see how you got there. Lucas: Exactly. And that's the core of it. A public roadmap is less about announcing features and more about managing expectations. When you're bootstrapped, you don't have a sales team to absorb all those conversations, so anything that reduces the back and forth is huge. Luna: Yeah, I can see that. But what does a good public roadmap even look like? Is it like a Trello board with a bunch of cards, or is it something more polished? Lucas: It can be as simple as a page on your site with three columns: 'Now,' 'Next,' and 'Later.' That's the framework a lot of indie founders use. The 'Now' column is what you're actively working on this month. 'Next' is the two or three things that are clearly up after that. And 'Later' is a parking lot for things you're considering but haven't committed to. That's it. Luna: Okay, so it's not a timeline with dates. That seems smart, because the moment you put a date on something and miss it, you've got angry customers. Lucas: Right, and that's the biggest risk. If you overpromise on timing, you're setting yourself up for failure. This founder made a point of never putting dates on his roadmap. He'd say things like 'this is the order we're thinking about,' not 'this ships in September.' And that's crucial because as a small team, you need flexibility. You might discover a bug that takes two weeks, or a customer need that jumps the line. Luna: But doesn't that make the roadmap kind of vague? If there are no dates, is it really a roadmap or just a wish list? Lucas: It's more of a directional guide. The point isn't to hold yourself to a date; it's to show customers that you have a plan and that you're thinking about the product in a structured way. And the side effect is that it builds trust. Customers see that you're not just flying by the seat of your pants. Luna: Makes sense. So what about the fear of competitors? I feel like if you're a bootstrapped founder in a niche, the last thing you want is to hand your roadmap to a bigger company. Lucas: That's a real concern, but most competitors have their own backlogs and their own priorities. They're not going to pivot their whole product just because you posted a roadmap. And honestly, the bigger risk is that your customers don't know where you're headed and churn because they think you're stagnant. A public roadmap signals momentum. Luna: Okay, that's a good point. So you're saying the roadmap is as much about retention as it is about feature requests? Lucas: Exactly. When a customer sees that you're building a feature they've been wanting, they feel heard. And even if the feature they want is in the 'Later' column, at least they know you're aware of it. That's a lot better than silence. Luna: So, let's get practical. If someone wants to start a public roadmap, where do they put it? Is a blog post enough, or do you need a dedicated page? Lucas: A dedicated page is better because it's something you can update regularly and link to from your support docs or your signup flow. The founder I mentioned actually put his at the root of his site, like yoursite.com/roadmap, so customers could find it easily. And he'd reference it in his email signature and in his onboarding emails. Luna: And how often should you update it? Is it a set it and forget it thing? Lucas: No, you have to keep it fresh. He updated it every week, sometimes just moving a card from 'Now' to 'Done' and adding a new one to 'Later.' That consistency is what made it feel alive. And he sent a short monthly email to his list summarizing what had changed on the roadmap. That turned the roadmap into a marketing asset, too. Luna: That makes sense. But I'm curious, does this work for every kind of software? I feel like if you're building an API, the expectations are a bit different. Lucas: API businesses actually benefit a lot from public roadmaps because developers want to know what endpoints are coming before they build on top of your platform. But the same principles apply: be clear about what's coming, but don't promise dates unless you're really confident. Luna: So, I'm thinking about the donation thing we've had on the show. It's like a public roadmap for the podcast, in a way. People know what we're planning to cover, and they can support if they find it useful. If today's episode was worth a coffee to you, that's the link, buy me a coffee dot com slash fexingo. Lucas: Yeah, that's a nice parallel. And we really do appreciate that kind of support, it's what keeps this show ad-free and focused on the topics you care about. But back to the roadmap, there's another angle that I think is really valuable. Luna: What's that? Lucas: A public roadmap can actually help you say no to feature requests. Instead of having a one-on-one conversation where you have to explain why you're not building something, you can just point to the roadmap and say 'it's on the list, but it's not in the next couple of quarters.' That's a lot easier than saying 'no' outright. Luna: That's a good point. It's almost like the roadmap becomes a boundary-setting tool. You're not rejecting the customer, you're just showing them where things sit in the queue. Lucas: Exactly. And it also helps you prioritize internally. When you have to write down what's in 'Now' and what's in 'Later,' you're forced to make decisions. You can't just say 'we'll think about it.' You have to actually think about it and commit to an order. Luna: So what happens when a customer asks for something that's not on the roadmap at all? Do you add it to 'Later'? Lucas: That's a good question. The founder I talked to had a simple rule: if it's a good idea and fits the product's vision, it goes on the 'Later' list. If it's not a fit, he'd just say 'that's not something we're planning to build, but thanks for the suggestion.' And because he had a public roadmap, that 'no' wasn't personal. It was just a business decision. Luna: I love that. It takes the emotion out of it. So, what's the downside? There has to be a catch. Lucas: The main downside is that you're publicly committing to a direction. If you change your mind, customers might be disappointed. But as long as you're transparent about why you're changing course, it's usually fine. And the other risk is that customers might start treating the 'Later' column as a promise. So you have to be clear that nothing is guaranteed until it's in the 'Now' column. Luna: That reminds me of how open-source projects handle roadmaps. They're always like 'this is what we hope to do, but it depends on contributors.' Lucas: Exactly, it's the same spirit. And for bootstrapped founders, it's especially important because you don't have a big company's marketing budget to create a sense of momentum. Your roadmap is your PR, your customer support, and your sales tool all in one. Luna: So, how do you get started? What's the first step for someone listening who wants to try this? Lucas: Start small. You don't need a fancy tool. Just create a simple page with three columns and list five or six things you're thinking about. And then commit to updating it every week, even if it's just moving something to 'Done.' That's really all it takes to get the benefits. Luna: And do you have any examples of companies that do this really well? Lucas: There are a few. I remember one email marketing tool for small businesses that has a public roadmap and they're really good at using it to show progress. They even tag items with 'in progress' and 'shipped' so customers can see things happen in real time. That kind of transparency is powerful. Luna: Nice. So, what's the one thing you want listeners to take away from this episode? Lucas: A public roadmap is not about telling your customers what you're doing; it's about showing them that you're listening and that you have a plan. It turns feature requests from a battle into a collaboration. And that's the kind of relationship that builds a loyal customer base. Luna: That's a great way to put it. I'm actually excited to try this with my own side project now. Lucas: If you do, let us know how it goes. We love hearing how these ideas play out in the real world.