Latest / The Bootstrapped Tech Founder with Fexingo: Profitable Software Companies Without VC / Why Bootstrapped Founders Should Build a Public Roadmap
Transcript
- Lucas: If these conversations are useful for what you're building or running, there's a quiet thing we do on this show that I want to flag. We deliberately don't run ads on The Bootstrapped Tech Founder. Not because we can't find sponsors — we can — but because the whole point is to have an honest conversation about building a profitable business without outside money. And running ads is, in its own small way, taking outside money from a different kind of investor. So we keep it clean. If you find value in that approach and want to support it, the link is buy me a coffee dot com slash fexingo. That's it. No tiers, no perks, just a way to keep the thing going on our own terms. Luna: I think that's rare and worth saying out loud. Most business podcasts are 10 minutes of content and 5 minutes of mattress ads. This one stays all content. Lucas: Exactly. And today's episode is a perfect example of a tactic where bootstrapped founders can use a free tool to do something that would cost a fortune in a vc backed company. Luna: You're talking about building a public roadmap, right? Lucas: Exactly. A publicly visible product roadmap — and I don't mean a vague 'we're working on stuff' Notion page. I mean a detailed, updated weekly, with specific features in 'planned', 'in progress', and 'shipped' columns. The kind of thing that makes customers feel like they're inside the company. Luna: I've seen a few SaaS companies do this. Canny.io comes to mind — they're a bootstrapped feedback tool that famously used their own public roadmap to grow. I think they hit $10 million in ARR with zero salespeople. Lucas: That's the canonical case. Canny's entire go to market was: users request a feature, Canny builds it, users see it happen in real time on the roadmap, they tell their friends. No demo calls, no outbound emails. The roadmap became their sales engine. Luna: But doesn't that tip your hand to competitors? If you're a bootstrapped company with limited resources, the last thing you want is a well-funded competitor seeing exactly what you're building next. Lucas: That's the number one objection I hear. And it's valid. But the data from companies that do this — Canny, Buffer, ConvertKit, now Kit — shows that the retention lift far outweighs the competitive risk. When customers see a feature they asked for appear on the roadmap, their likelihood of churning drops by something like 18 to 25 percent. A competitor knowing your next feature might cost you some advantage, but losing a quarter of your customers costs you everything. Luna: So how do you decide what goes on the board and what stays internal? Lucas: There's a simple heuristic. Put anything on the public roadmap that customers have explicitly asked for and that you are at least 70 percent sure you will build within the next six months. Leave off anything that is a secret competitive weapon — like a pricing change or a new market entry you don't want to telegraph. And never put a date on anything unless you're certain. The worst thing you can do is promise Q3 and deliver Q4. That erodes trust faster than having no roadmap at all. Luna: So it's more about direction than deadlines. Lucas: Exactly. Status labels like 'planned' and 'under consideration' give you wiggle room. Customers forgive a shifted priority more than a missed date. And the psychological effect is huge — when a customer sees their request move from 'under consideration' to 'planned', they feel ownership. They become an advocate. They start defending your product in online forums. Luna: I want to talk about the tactical side. How often should you update it? And where should you host it? Lucas: Weekly is the gold standard. Canny updates theirs every Monday morning. It becomes a ritual — customers check it the way they check their email. As for platform, you can use dedicated tools like Canny or Productboard, but I've seen founders do it with a simple public Trello board and it works just as well. One founder I know put his roadmap on a Trello board with four columns: 'backlog', 'planned', 'building', 'shipped'. He embedded it on his pricing page. His churn dropped 18 percent in two months. That's not a theory — that's a concrete number. Luna: That's wild. And the pricing page is an interesting placement — your most price-sensitive visitors see that you're actively building. Lucas: Exactly. It signals: 'This product is alive. It's getting better. If you buy now, you're not buying what it is today — you're buying what it will be next quarter.' That's a powerful message for a bootstrapped company that can't outspend competitors on marketing. Luna: What about the risk of feature request overload? If you open the floodgates, won't you drown in suggestions? Lucas: You will. But that's actually a feature, not a bug. The signal you get from a public roadmap is which requests have the most upvotes and comments. It's market research done for you. And you don't have to act on all of it. You can set a threshold — say, only move a request to 'planned' if it has 50 upvotes or if it's from a paying customer. That filters out the noise. Luna: I've seen some companies go a step further and allow customers to vote with their wallet — like pledging a higher plan tier if a certain feature ships. Lucas: That's an advanced move. Some bootstrapped founders use a public roadmap with a 'fund this feature' button. It's essentially pre-selling. If enough customers commit to upgrading once the feature ships, you de-risk the development cost entirely. That's a vc free way to fund product development. Luna: Let me play devil's advocate again. What if you're in a very niche B2B space where your competitors are also bootstrapped and watching your every move? Does the calculus change? Lucas: It does, but not as much as you'd think. In a niche space, your customers are probably already talking to each other. If you don't share your roadmap, they'll speculate. And speculation is always worse than transparency. A competitor might see your plans, but they'll also see the customer engagement behind those plans. That engagement is hard to copy. Luna: Good point. So the roadmap itself is a moat — not because it's secret, but because the community around it is hard to replicate. Lucas: Exactly. And there's one more tactical piece I want to mention. Use the 'shipped' column as a marketing channel. Every time you move something to 'shipped', write a short changelog entry. Send it to your email list. Tweet it. The shipped column is a content engine. It proves you deliver. And for a bootstrapped company, proof of delivery is the best sales tool there is. Luna: I love that. It turns product development into a narrative. Customers feel like they're on a journey with you. Lucas: They are. And that's the whole point. A public roadmap is not just a project management artifact — it's a relationship tool. It says: 'We are building this together.' And when you're bootstrapped, you don't have billions of dollars to buy that relationship. You have to earn it, one feature at a time. Luna: So if someone listening wants to start today, what's the first step? Lucas: Create a public Trello board with three columns. Call them 'planned', 'building', 'shipped'. Pick your top three customer-requested features that you're fairly sure you'll build in the next three months. Put them in 'planned'. Then set a recurring calendar reminder every Monday to update it. That's it. You don't need a fancy tool. You don't need a launch announcement. Just start doing it. Within a month, you'll see the effect on support tickets and customer sentiment. Luna: And the effect on your own focus — seeing a public board forces you to actually ship. Lucas: That's the hidden benefit. The public roadmap is a commitment device. Once that Trello board is out there, you have a social contract with your customers. And that's a powerful motivator to finish what you start. Luna: Alright, I'm sold. I'm actually going to set up a board for my side project this week. Lucas: Do it. And let me know how it goes. I might even feature it on a future episode.