Latest / The Bootstrapped Tech Founder with Fexingo: Profitable Software Companies Without VC / How Bootstrapped Founders Use Internal Tools as a Second Revenue Stream
Transcript
- Lucas: So there's this pattern I keep seeing among bootstrapped software companies. They build something internal—a dashboard, a reporting tool, a little automation script—and after a while they realize other people have the exact same problem. Luna: Right, the 'scratch your own itch' thing. But usually that's how the core product starts. You're talking about a second product? Lucas: Exactly. A second product that's born from an internal tool. It's not the main business—it's a side effect. And for some founders, it becomes a meaningful second revenue stream without distracting from the core. Today I want to look at one specific example and the conditions that make it work. Luna: Let's hear it. Which company? Lucas: There's a small project management SaaS, let's call it Planwell—not the real name, but the story is real. They had about 50 employees, mostly remote, and they were managing customer health with a mix of spreadsheets and a half dozen SaaS tools. It was a mess. So their head of customer success spent a weekend building a simple dashboard that pulled data from their CRM, support tickets, and usage logs into one view. Luna: That sounds like every company's story. The 'weekend project' that becomes the thing everyone relies on. Lucas: Exactly. Within a month, the whole company was using it. And then a friend who runs a similar B2B SaaS saw it and asked if they could license it. That friend offered to pay $200 a month for access. Luna: And that's the moment. The lightbulb goes off. Lucas: Right. So Planwell's founder thought about it. They could have said no—keep it as a competitive advantage. But instead they decided to spin it out as a standalone product. They cleaned up the code, added multi-tenant support, and launched it as a separate SaaS. Today it generates about $300,000 a year in revenue. Not huge, but it's pure profit margin because the R&D was already sunk. Luna: Three hundred thousand with basically zero customer acquisition cost. Every customer came from word of mouth. That's the dream. Lucas: It is. But the key is that Planwell didn't let it distract them. The internal tool team was just two engineers who split their time—maybe 20 percent each. The main product kept growing. So what made this work? I think there are three conditions. Luna: Okay, lay them out. Lucas: First, the tool has to solve a universal pain point. Customer health monitoring is not specific to Planwell. Every B2B SaaS with a retention model needs it. If the tool is too specific to your own workflow—like a custom integration with your weird ERP system—it's not portable. Second, it has to be low maintenance to support. Planwell's tool was simple. A few API calls, a database, a web front-end. No real-time streaming, no complex compliance requirements. That meant support was minimal. Luna: So you're not building a monster. Keep the surface area small. Lucas: Exactly. And third, the core business has to be stable enough to absorb the distraction. If you're still struggling to find product-market fit on your main product, spinning out an internal tool is a death wish. Planwell was already profitable and growing 15 percent year over year. They had slack. That safety net matters. Luna: I think the risk people don't talk about is feature creep. You launch the tool, customers ask for more features, and suddenly you're building a whole new product instead of focusing on your main business. Lucas: That's a real trap. Planwell avoided it by setting a hard rule: the internal tool would never have more than 10 percent of the company's engineering time. The product had a clear scope—customer health dashboard and nothing else. No integrations marketplace, no API for third parties, no analytics module. When customers asked for those, they said no. And they kept the pricing simple: one plan, no tiers. Luna: That takes discipline. Especially when a customer is waving a check for a bigger deal if you just add one more feature. Lucas: Absolutely. But the flip side is that by keeping it lean, they kept support costs low and margins high. Their gross margin on that product is around 85 percent. Compare that to the main product which is maybe 70 percent because of more customer-facing features and onboarding costs. So the internal tool actually became the more profitable product per dollar of revenue. Luna: Interesting. So it's not just extra revenue—it's better margin revenue. Lucas: Right. And there's another benefit: the internal tool often improves the core product indirectly. Because it's a dashboard for customer health, the main product team started using it to identify churn risks. They found that customers who didn't use a certain feature in the first week had a 40 percent higher churn rate. That insight led to a change in the onboarding flow. So the tool fed back into the main product. Luna: That's the flywheel. The tool makes your core product better, which makes customers happier, which gives you more data for the tool. So it's not just a side hustle—it's strategic. Lucas: And the way Planwell structured the team is worth noting. They didn't hire new people. The two engineers who built the tool were already on the core team. Their time was split, but the founder made sure the core product always came first. If a critical bug hit the main product, the internal tool work stopped. Luna: That's a good rule. I've seen companies that spin out a tool and then hire a separate team, and suddenly you have two products competing for resources in a way that hurts the original business. Lucas: Exactly. The separate team dynamic can create internal friction. Planwell's approach was more like an internal skunkworks. No separate P&L, no separate OKRs. Just a side project with guardrails. And because it was never a core focus, the founder never had to worry about it becoming a distraction. Luna: I want to talk about the decision to spin it out at all. Some founders would say 'this tool gives us a competitive edge, why sell it to competitors?' What's your take? Lucas: That's a fair question. Planwell's founder told me they debated that. But they realized the tool wasn't their moat—their moat was the project management product itself. The customer health dashboard was useful but not unique. Plenty of companies could build something similar. By selling it, they got revenue and also built goodwill in the B2B community. Plus, the tool was so specific to their own stack that competitors would have a hard time copying the exact workflow anyway. Luna: So the moat wasn't the tool, it was the integration with their own product. Competitors buying the tool would still need to build that integration themselves. Lucas: Right. And that's a good test: if the internal tool is tightly coupled with your core product, you can sell it without giving away your secret sauce. If it's a standalone generic tool, you might be arming competitors. So the decision depends on the architecture. Luna: Let me ask about the numbers. Three hundred thousand a year—how many customers is that? Lucas: About 120 customers at roughly $200 a month. So it's a niche product. They didn't try to go mass market. They kept it in the B2B SaaS space, priced at a level that made sense for small to mid-size companies. The sales cycle was almost nonexistent because referrals did the work. Luna: So the growth engine was purely word of mouth. That's the bootstrapper's dream. No paid ads, no sales team. Lucas: Exactly. And that's partly because they didn't market it aggressively. They mentioned it in a few blog posts and at a conference. The rest was organic. That's a sign that the product truly solves a pain point—people tell each other about it. Luna: One thing I'm curious about: did they ever consider selling the tool to a bigger company? Like an acquisition offer? Lucas: They did get an offer about two years in. A larger analytics platform wanted to buy it for $2 million. The founder turned it down. His reasoning was that the tool was too valuable as a strategic asset for the core business—the insights it generated were worth more than the cash. And he didn't want to deal with the transition. So he kept it. Luna: That's a surprisingly disciplined decision. Two million dollars is life-changing money for many founders. Lucas: It is. But he saw the tool as a long-term play. And he was already profitable, so he wasn't desperate. That's the advantage of being bootstrapped—you can afford to say no to offers that aren't aligned with your vision. Luna: I think a lot of founders listening might be sitting on an internal tool they haven't considered packaging. What's the first step you'd recommend? Lucas: First, audit your internal tools. Ask your team: what's the one script or dashboard that saves you the most time? Is it something other companies might use? Then talk to a few peers in the industry—off the record—and see if they'd pay for it. If you get a yes from even two or three, you have a signal. Then scope it as minimally as possible. Strip out everything that's specific to your company. And set a rule: no more than 10 percent engineering time. If you can't build a basic version with that constraint, it's too complex. Luna: That's a good checklist. I'd add: make sure your core business is stable first. If your main product is still in the danger zone, don't even think about it. Lucas: Absolutely. And remember that this isn't a pivot. It's a side product. If it ever starts to overshadow the core, you have to make a conscious choice. But for Planwell, it worked beautifully. They got an extra $300K in profit, better customer insights, and a stronger community reputation—all from a weekend project. Luna: And speaking of community reputation, that's actually a nice thread to something I wanted to mention. These conversations we have every day, digging into stories like Planwell—they're possible because listeners support the show directly. We don't run ads, and we keep the podcast independent. A handful of listeners chip in monthly through buy me a coffee dot com slash fexingo, and that literally funds making this many of these episodes. Lucas: Yeah, it's a small group, but it makes a big difference. It means we don't have to shape the content around sponsors or worry about ad reads. We can just follow the stories that matter. Luna: Exactly. So if you get value from the show, and you want to keep it ad-free, that's how. No pressure, just the reality of how independent media works. Lucas: And we wouldn't be having this conversation about Planwell if we had to chase ad revenue. So thank you to those who do contribute. Now let's get back to the practical side. Luna, you mentioned the risk of the tool overshadowing the core. What's your advice for founders who are already in that situation—the internal tool is growing faster than the main product? Luna: I think you have to be honest about the trajectory. If the internal tool is clearly a bigger opportunity, maybe it should become the core. But that's a rare case. More often, the founder is just excited by the new shiny thing. My advice: give it a separate brand and a separate team, but keep the economics independent. And set a time box—say, six months—to see if it can sustain itself without cannibalizing the main business. If it can, great. If not, wind it down. Lucas: That's a pragmatic approach. And it's consistent with the bootstrapper ethos—don't let ego drive decisions. The numbers should tell you what to do. Luna: Exactly. So to wrap up: internal tools can be a fantastic second revenue stream, but only if you keep them in their lane. Solve a universal pain, keep maintenance low, and protect your core. Lucas: And audit your own company today. That little script your team built might be worth more than you think.