Latest / The Bootstrapped Tech Founder with Fexingo: Profitable Software Companies Without VC / How Bootstrapped Founders Use Internal Tools to Build Second Products
Transcript
- Lucas: If these conversations are useful for what you're building or running, you're in the right place. I'm Lucas. Luna: I'm Luna. And today we're talking about something that sounds almost too good to be true: discovering your second product already built, sitting inside the tools you made for yourself. Lucas: Exactly. A lot of bootstrapped founders obsess over the next feature, the next integration, the next customer segment. But there's a pattern I've seen a few times now where the highest-margin product a company ever launches wasn't planned at all. It was an internal tool that escaped. Luna: Escaped—I like that. So we're talking about a specific case today, right? Lucas: Yeah. There's a company called Stile—small B2B SaaS, about fifty employees, project-management software built specifically for design teams. Profitable from year two, no VC, very much in our wheelhouse. And about three years ago, their engineering team ran into a problem. Luna: What kind of problem? Lucas: One of their bigger clients—a design agency with about eighty users—needed to sync Stile projects into their own internal dashboard. Standard API request, except the client's system used a weird authentication protocol Stile didn't support. The Stile team could have said no, or charged a huge integration fee. Instead, one engineer built a lightweight API gateway in a weekend. Just a thin translation layer that sat between Stile's API and the client's system. Luna: And that gateway became the second product. Lucas: That gateway became Gatewise. The engineer showed it to the team, and within a month, three other clients asked for the same thing. The founder—her name is Mira—told me she almost said no to those requests. She thought it was a distraction from the core product. Luna: I bet a lot of founders would have done exactly that. 'We're a project-management tool, not an integration layer.' Lucas: Right. But Mira had a rule she picked up from a previous startup: whenever a piece of internal infrastructure gets used by more than one team without being promoted, you should至少 look at it. So she let two engineers spend another week polishing the gateway, added a simple admin panel, and put a price on it: $200 a month per instance. Luna: And it took off? Lucas: Slowly at first. They didn't market it. They just mentioned it when clients complained about integration headaches. But within eighteen months, Gatewise had forty-seven paying customers, and the remarkable thing is the acquisition cost was effectively zero. Every single customer came from an existing Stile relationship, or from a referral by a Stile customer. Luna: So the customer acquisition cost is basically zero, and the margin on a $200-a-month product that's already built has to be enormous. Lucas: Mira told me the gross margin on Gatewise is ninety-one percent. Compare that to Stile's core product, which is around seventy-two percent, because they have hosting costs, support staffing, and a bigger development team. Gatewise runs on a couple of small servers and requires maybe five support tickets a month. Luna: Ninety-one percent gross margin. That's the kind of number that makes you question why every bootstrapped company isn't combing through their internal repos for product opportunities. Lucas: I asked Mira exactly that. She said the hardest part isn't the technical work—it's the mindset shift. Founders are trained to think of their product as the thing they sell. Internal tools are invisible by design. They live in a company's private GitHub repos, often undocumented, held together with duct tape. Luna: So how do you spot which internal tools are worth productizing? Because not every script or dashboard is a business. Lucas: Mira gave me three signals. First, the tool solves a pain that your customers have told you about verbally, even if they never asked for a product. In Stile's case, clients kept saying 'we wish your API worked with our weird system.' That's a signal. Second, the tool is used regularly by people who aren't the original author. If only one engineer touches it, it's probably too idiosyncratic. But if a few people rely on it, that's a sign of broader utility. Luna: And the third signal? Lucas: The tool has what Mira calls 'accidental configurability.' Some internal tools are hardcoded for one use case. But if the tool was built with a few knobs—maybe a config file, a couple of environment variables—it's easier to turn into a product. Gatewise happened to have a config file because the original engineer wanted to test different authentication flows. Luna: That's almost lucky. But I suppose you make your own luck by building tools that are slightly more general than they need to be. Lucas: Exactly. And the interesting thing is that Gatewise didn't cannibalize Stile's core product at all. In fact, it made Stile stickier. Clients who used Gatewise were less likely to churn because they'd invested in the integration. The second product actually reduced churn on the first product by about twelve percent, according to Mira. Luna: So it's a defensive moat as well as a revenue stream. I love that. But I'm also wondering—what's the mistake founders make when they try to do this? You mentioned one earlier. Lucas: The mistake is over-investing before validation. Mira told me she's seen founders take a useful internal dashboard and spend six months building a full SaaS product around it—billing, user management, documentation, a marketing site—before they had a single paying customer. They treat it like a startup inside their startup. Luna: And what's the smarter approach? Lucas: Ship it as it is. Charge for access. See if anyone pays. Gatewise launched with a five-minute setup guide written in Markdown and a Stripe link. No onboarding flow. No self-serve portal for the first six months. Mira's philosophy was 'if they can't figure out the API documentation, they're probably not our customer anyway.' Luna: That's refreshingly minimal. I think a lot of teams would have over-engineered it. Lucas: Right. And there's one more thing that makes this pattern especially powerful for bootstrapped founders. Because you're not taking VC money, you don't have the pressure to hit a massive TAM with your second product. It can stay small. Gatewise will probably never be a hundred million dollar business. But it adds a reliable, high-margin revenue stream that lets Stile take more risks on its core product. Luna: So it's almost like an internal hedge fund. The profits from the second product subsidize innovation on the first. Lucas: That's exactly how Mira describes it. She told me that Gatewise's margin is what allowed her to hire a dedicated research engineer for Stile—someone who spends half their time just exploring new features with no immediate revenue expectation. She couldn't have done that on Stile's margin alone. Luna: I want to ask about a practical next step. Say a founder is listening and thinks they might have an internal tool worth productizing. What's the first thing they should do this week? Lucas: Mira recommends an audit. Spend two hours walking through your team's internal tools—scripts, dashboards, automation, connectors. For each one, ask: does this solve a problem a customer has mentioned? Is it used by more than one person? And could we charge for it with minimal changes? If you get three yeses, put a price on it and offer it to the next customer who brings up the pain point. Luna: That's actionable. And it doesn't require a big bet. Lucas: No, it doesn't. And if today's episode gave you a useful lens for thinking about your own codebase or product strategy, that's exactly what we hope for. These conversations stay ad-free because listeners like you support the show—buy me a coffee dot com slash fexingo. It really does make a difference. Luna: Yeah, I think that's part of why we can dig into stories like Stile's without worrying about sponsors. Keeps the focus on what actually works. Lucas: Absolutely. So back to the audit idea—Mira also said something I think is worth highlighting. She said the best internal tools to productize are the ones your team complains about using. If they're grumbling about a janky internal dashboard, that grumbling is market research. Luna: Because if your own team finds it painful, your customers will too. Lucas: Exactly. The internal complaint is a leading indicator. One of Mira's engineers hated the way Gatewise's original config file worked—it was a YAML file with no validation. So when they productized it, they spent exactly one day adding a simple web form that generated the YAML. That one day of work became the feature that most customers mentioned in their first positive review. Luna: So the productization process is almost like editing. You take something that exists and you trim, polish, and surface the parts that matter to someone outside your team. Lucas: That's a great way to put it. And it's a very bootstrapper-friendly approach because it starts from a position of strength. You're not guessing at market need. You have real evidence that the tool works, because your team used it. Luna: I'm curious about the long-term horizon for Gatewise. Does Mira see it eventually becoming the primary business, or is it always going to be the second product? Lucas: I asked her that. She said as long as Stile's core product is growing, Gatewise will stay a secondary stream. But she also acknowledged that if Stile ever hits a plateau, Gatewise gives her an option. It's a hedge, not a plan. And for a bootstrapped founder, having optionality is the whole game. Luna: Optionality without dilution. That's a pretty good summary of what we talk about on this show. Lucas: It is. And on that note, I think we've got a solid takeaway for anyone running a bootstrapped software company: look at what you've already built. The next product might be hiding in plain sight. Luna: And you don't need a VC to find it. Thanks, Lucas. Lucas: Thanks, Luna. And thanks to Mira at Stile for sharing the numbers. We'll be back next week with another story from the bootstrapped trenches.