Latest / The Bootstrapped Tech Founder with Fexingo: Profitable Software Companies Without VC / How Bootstrapped Founders Build With Public Roadmaps
Transcript
- Lucas: Luna, I want to talk about something that sounds almost anti-competitive for a bootstrapped software company—publishing your product roadmap in public for anyone to see. Luna: You mean just laying out every feature you're planning, with timelines, so competitors can copy you? Lucas: Exactly. It feels like giving away your playbook. But a growing number of profitable bootstrapped founders are doing it—and they're seeing real benefits in customer trust, reduced churn, and better prioritization. Luna: Okay, I need a concrete example. Who's doing this well? Lucas: Let's talk about a company called Plane—it's an open-source project management tool that's bootstrapped and profitable. They've had a public roadmap since early 2024. But the example I want to zoom in on is a smaller player: a $4 million ARR SaaS tool called Canny, which actually makes customer feedback and roadmap software. Luna: So Canny eats its own dog food. That makes sense. Lucas: Right. Canny's founder, a guy named Andrew, decided in 2025 to move their entire internal roadmap to a public Trello board. Not a polished marketing page—just a raw board with columns: 'Under Consideration', 'Planned', 'In Progress', and 'Shipped'. Every card had a link to the customer conversation that inspired it. Luna: And what happened? Did competitors start cloning features? Lucas: Maybe. But Andrew told me the bigger surprise was a 22 percent drop in churn within six months. Customers who had been lurking, wondering if their pet feature would ever get built, could now see exactly where it sat in the queue. A lot of them stopped cancelling and just waited. Luna: So the transparency actually bought them time. Customers became more patient when they understood the trade-offs. Lucas: Exactly. And there's a second benefit: support tickets about 'when is X coming' dropped by nearly 40 percent. Because the roadmap was the answer. Customers could check it themselves instead of emailing support. Luna: That's a huge operational saving for a small team. But I imagine there's a downside—what about disappointed customers when you mark something as 'won't do'? Lucas: That's the tricky part. Canny handles it by tagging items with labels like 'Definitely' and 'Maybe'. If something is a 'Maybe', they explain why—usually tied to revenue or strategic fit. And they link to a public discussion where customers can argue for it. It's not a black box. Luna: So it becomes a conversation, not a rejection. I can see how that builds loyalty even when you say no. Lucas: Exactly. And here's another angle: public roadmaps help with hiring. When potential employees see that a bootstrapped company is transparent and customer-driven, they're more likely to join. Andrew said three of his hires in 2025 mentioned the public roadmap as a reason they applied. Luna: That's a recruiting edge you don't get from a secret Jira board. But what about the risk of competitors cherry-picking your best ideas? Lucas: It's a real concern. But bootstrapped founders argue that execution matters more than ideas. If a competitor copies your roadmap, they still have to build it well, and they don't have your customer relationships. Plus, you can use the roadmap to signal what you're NOT doing—which might steer competitors into dead ends. Luna: Okay, so let's get tactical. If I'm a bootstrapped founder listening, what's the first step to go public with my roadmap? Lucas: Start small. Don't put your entire internal roadmap out there. Pick the next three to six months of features you're confident about. Put them on a simple public board—Trello, GitHub Projects, or a tool like Canny itself. Label each item with a status and a rough timeframe: 'this quarter', 'next quarter', 'under consideration'. Luna: And what about the language? Should you promise dates? Lucas: Never promise dates. Use words like 'targeting' or 'aiming for'. And if you slip, just update the board and explain why. Customers appreciate honesty more than precision. One founder I spoke with said he wrote 'We thought this would take two weeks, but it's taking six because we had to rewrite the database layer.' Customers actually thanked him for being open. Luna: That's wild. Normally you'd hide a delay. But here, transparency turned a negative into a trust-building moment. Lucas: Exactly. And there's a final piece: once you ship a feature, tag the original requesters in the update. Canny sends an automated email to every customer who voted for that feature saying 'We built it.' That creates a dopamine hit of reciprocity. People feel heard. Luna: So the public roadmap is really a customer retention tool disguised as a planning tool. Lucas: Exactly. And it's especially powerful for bootstrapped companies because you don't have a huge sales team to nurture relationships one-on-one. The roadmap does that at scale. Luna: I want to push back a little though. Doesn't this only work if you have a product that customers are already passionate about? If you're early stage with ten users, a public roadmap might look empty and hurt credibility. Lucas: That's a fair point. In the very early days, you probably don't have enough signal to make a public roadmap useful. But once you have maybe fifty paying customers and a handful of feature requests coming in each week, it starts to make sense. Even a simple list of 'we're considering these five things' can start the conversation. Luna: So the threshold is when inbound requests become frequent enough that you need a way to manage expectations. Lucas: Exactly. And if you're worried about looking empty, you can include a sentence like 'We're a small team, so we prioritize based on impact. Here's what we're currently exploring.' That honesty builds trust from the start. Luna: Alright, I'm sold on the concept. But walk me through a specific week in the life of a founder maintaining a public roadmap. How much time does it take? Lucas: Andrew from Canny said he spends about thirty minutes a week on it. He reviews new requests, moves cards between columns, and writes short updates. The key is not to over-engineer it. No fancy design, no long essays. Just a bullet point and a status. Luna: Thirty minutes a week for a 22 percent churn reduction and a 40 percent drop in support tickets? That's an incredible ROI. Lucas: Right. And here's the thing—once you have the roadmap, you can also use it to guide your sales conversations. When a prospect asks for a feature, you can show them where it sits on the roadmap. It closes deals faster because they see momentum. Luna: So it's not just retention—it's acquisition too. I think we're onto something that more bootstrapped founders should try. Lucas: If these conversations are useful for what you're building or running, you know, we keep this podcast ad-free and listener-supported. Honestly, if today's episode was worth a coffee to you, that's the link—buy me a coffee dot com slash fexingo. Luna: Yeah, it's a small way to say this content matters. And it really does help us keep going. Lucas: So back to the roadmap. One more tactic I love: some founders add a 'recently shipped' column at the top to show velocity. New customers see that you're actively building, which reduces the fear that you'll go out of business or stop innovating. Luna: That's smart. It signals life. And for bootstrapped companies, that's often a bigger concern than feature depth. Lucas: Exactly. So if you're a bootstrapped founder on the fence, here's my challenge: pick one board, add three features you're confident about, and link to it from your app's help menu. See what happens in thirty days. Luna: And if you do it, let us know. We'd love to hear about the experiment on a future episode. Lucas: Absolutely. That's it for today. Lucas and Luna, signing off.