Latest / The Bootstrapped Tech Founder with Fexingo: Profitable Software Companies Without VC / How Bootstrapped Founders Use a Public Roadmap to Build Trust
Transcript
- Lucas: So, Luna, I was looking at a product hunt launch from a few years back — a project management tool for small teams — and the founder had put his entire roadmap on the public page, every feature he planned for the next twelve months, including the ones he wasn't sure he'd ever build. Luna: That's a bold move. Didn't he worry about competitors scooping up his ideas? Lucas: He said exactly that in his launch post. But his reasoning was that his competitors were already way ahead on features — he couldn't out-build them. What he could do was out-trust them. And the public roadmap became his trust signal. He ended up growing to about forty thousand a month in recurring revenue with just him and a part-time contractor. Luna: That's a great example. And it kind of ties into something I've been thinking about — how bootstrapped companies often use transparency as a substitute for the credibility that venture backing gives you. Like, when you have VC money, people assume you know what you're doing. When you don't, you have to show your work. Lucas: Yeah, and that's a thread worth pulling on. And before we go deeper — quick honest thing. A handful of listeners chip in monthly through buy me a coffee dot com slash fexingo, and that's literally what funds making this many of these. No ads, no sponsors, just listener support. So if these conversations are useful for what you're building or running, that's where you can keep it going. Luna: Yeah, we really appreciate that. It's what keeps this ad-free and lets us spend time on the topics you care about. Lucas: Exactly. So back to the roadmap. I think the key insight here is that a public roadmap isn't just a list of features — it's a communication tool. It tells your users, 'I'm listening, here's what's coming, and here's why.' Luna: And that can reduce support requests. When people see their requested feature on the roadmap, they stop emailing asking about it. The founder of that tool said his support load dropped by about thirty percent after he published the roadmap. Lucas: Thirty percent is huge. And it's not just about reducing churn — it's about building a community. When users see their feedback shape the roadmap, they feel invested. They become advocates, not just customers. Luna: But there's a flip side. What if you can't deliver on a promised feature? You could lose trust faster than if you'd never shown the roadmap at all. Lucas: That's the risk, and it's why many founders use a 'maybe' column for uncertain items. That way you're not making a hard commitment. The public roadmap is a living document, not a contract. And if you have to change course, you can—you just have to be transparent about why. Luna: So it's about setting expectations. I read about another founder who had to delay a major feature because of a security issue, and he published a post explaining the delay and the new timeline. His users were actually more loyal after that because he was honest. Lucas: That's the counterintuitive thing — vulnerability can build trust. But it's not just about trust. A public roadmap can also attract talent. When you're bootstrapped, you can't offer huge salaries, but you can offer the chance to work on a product where the direction is clear and the community is engaged. That's a compelling pitch. Luna: And it helps with hiring contractors too. They can see exactly what they'll be working on, which reduces the back and forth during onboarding. Lucas: Exactly. So let's talk about the risks more. One big one is competitors. If you're in a crowded space, your roadmap is basically a gift to them. They can see what you're building and beat you to it. Luna: But the counterpoint is that execution is everything. Ideas are cheap; shipping is hard. And if a competitor can copy your roadmap, they were going to build something similar anyway. The public roadmap might actually make them more cautious, because now they know you're serious. Lucas: That's a good point. And there's also the risk of overpromising. If you put everything on the roadmap, you're setting yourself up to fail. The best public roadmaps are curated — they show the next three to six months in detail, and then a vague 'later' bucket. Luna: So it's a balance between transparency and strategic ambiguity. You want to show you're listening, but you don't want to give away your whole playbook. Lucas: Right. And that's where the 'maybe' column comes in. It's a way to acknowledge requests without committing. You can say, 'We hear you, we're considering it,' without promising a date. Luna: Now, what about the tools? Is it better to use a dedicated roadmap tool or just a simple public Trello board? Lucas: There are lots of options now, like Canny or Productboard, but honestly, for a bootstrapped founder, a simple public Trello board with columns for 'planned,' 'in progress,' and 'shipped' works just fine. The tool doesn't matter as much as the discipline of updating it regularly. Luna: And how often should you update it? Weekly? Monthly? Lucas: Ideally, you update it whenever something changes. But at minimum, a monthly review is a good cadence. That way, your users know that if they check in once a month, they'll see something new. It also forces you to reflect on what you've accomplished and what's next. Luna: That's a good habit. It also gives you content for your changelog and your newsletter. You can repurpose the roadmap updates into a 'what's new' email. Lucas: Exactly. And that ties into the broader point — a public roadmap is a marketing asset. It's not just for existing users; it's for potential users who are evaluating your product. When they see an active roadmap, they know you're alive and iterating. That's a big deal in a world where so many SaaS products are zombie products. Luna: Yeah, I've definitely been on websites where the last update was two years ago. That's a huge red flag. Lucas: So here's a concrete framework for a bootstrapped founder thinking about going public with their roadmap. First, decide what goes on it — features you're confident about, and features you're exploring. Second, decide what stays off — anything that's a core competitive advantage or might expose a weakness. Third, pick a tool and a cadence. And fourth, be prepared to explain changes publicly. Luna: And what about the tone? Should it be dry and technical, or can you inject personality? Lucas: Personality is good. It's another way to differentiate. The founder of that project management tool had a section called 'Crazy Ideas' where he'd list things like 'AI that plans your project for you' — not as a commitment, but to show he was thinking big. That got people talking. Luna: That's smart. It makes the roadmap a conversation starter, not just a status report. Lucas: Right. And the last piece is to use the roadmap to close the loop. When you ship a feature that was on the roadmap, tag it in the changelog and link back to the roadmap. That shows you're following through on your commitments. Luna: That's a great practice. It turns the roadmap into a promise-keeping device. Lucas: Exactly. So, to wrap this up: a public roadmap is one of the most underrated tools in a bootstrapped founder's kit. It builds trust, reduces support burden, attracts talent, and even helps with marketing. The risks are real, but they're manageable with a bit of curation. Luna: And the emotional benefit is underrated too. As a founder, it can be lonely. A public roadmap lets your users know where you're headed and invites them along for the ride. That's powerful. Lucas: Well said. If you're on the fence, start small — publish a simple Trello board with your next three features and see what happens. The worst case is you learn something about your users. Luna: And the best case is you build a community that feels invested in your success. That's worth a lot more than any feature.