Latest / The Bootstrapped Tech Founder with Fexingo: Profitable Software Companies Without VC / Bootstrapped Founders Turn Side Projects Into Profitable Companies
Transcript
- Lucas: Luna, have you ever noticed how many of the most profitable bootstrapped software companies started as side projects? Not the thing the founder was trying to build — just something they tinkered with on a weekend and accidentally turned into a real business. Luna: Yeah, it's almost a cliché in the indie hacker world. But I wonder — for every one that takes off, how many just sit there as a hobby, maybe making a few hundred bucks a month? Lucas: That's exactly the question. And today I want to look at founders who use side projects deliberately, as a strategy — not as a distraction. They treat them like experimental prototypes that either die or become a second revenue stream. Luna: So it's not just luck. There's a method to it. Lucas: Right. Let me start with a concrete case. There's a solo developer I know — let's call him Mark — who built a tiny reporting tool for a niche e-commerce platform. He spent maybe ten weekends on it, launched it for $29 a month, and forgot about it. Two years later, it's doing one point two million dollars a year in revenue. He still works on it part-time. Luna: One point two million from a weekend project? That's insane. But I guess the key is 'niche.' He found a specific pain point that bigger companies ignored. Lucas: Exactly. The platform had millions of merchants, but the reporting was terrible. He didn't try to build a full analytics suite — just one report that every store owner needed. That's the first rule of side projects: solve one problem for one type of customer, and charge for it immediately. Luna: So validation through payment, not just downloads or sign-ups. That weeds out people who are just curious. Lucas: Right. And it forces you to build something simple enough to launch fast. Mark's tool had maybe four screens when it launched. He added features later based on what paying customers asked for. Now, side projects like Mark's are great, but they can also become a distraction if you're not careful. So the question is: how do you pick the right side project, and when do you shut one down? Luna: I've seen founders who have three or four side projects running at once, and none of them grow because they're spread too thin. There's a cost to context switching. Lucas: Yeah, that's the trap. The founders who do this well have a framework. They ask: does this side project serve my main business in some way? Maybe it generates leads, or it uses the same technology stack, or it solves a problem they have internally. If the answer is no, they're much more likely to kill it early. Luna: Can you give me an example of a side project that directly served the main business? Lucas: Sure. There's a two-person team that runs a project management tool for creative agencies. It's their main product, does about three million ARR. A few years ago, they built a simple time-tracking widget for their own use. They realized other agencies might want it, so they packaged it as a standalone app. Now that time-tracking tool is doing eight hundred thousand ARR, and it feeds customers into their main product. Luna: So it's a funnel. The side project becomes a lead-generation engine that also makes money on its own. Lucas: Exactly. And because they already needed the internal tool, the development cost was sunk. They didn't build it as a side project — it became one. That's a smart pattern. Another pattern is using side projects to fund your main business. I talked to a founder who bootstrapped a five-million-dollar SaaS by first launching a consulting practice and a small WordPress plugin. The plugin made maybe two thousand a month, but it paid his rent while he built the real product. Luna: That's the opposite of the Silicon Valley narrative — take VC money, build for free for two years, then figure out revenue. He was cash-flow positive from month one because of the side project. Lucas: Right. He called it 'ramen profitability on steroids.' The side project wasn't going to be his life's work, but it bought him time and optionality. And when the main product started growing, he didn't abandon the plugin — he sold it to another indie developer for a low five-figure sum, which gave him a little extra runway. Luna: So it's not just about building — it's about knowing when to exit a side project, whether by selling it or shutting it down. That's a skill in itself. Lucas: Yeah, and that's the hardest part for most founders. We get attached. But the best bootstrappers have a kill criterion: if the side project isn't generating meaningful revenue or strategic value after six months of consistent effort, they sunset it. No zombie projects. Luna: Six months seems short. Some things take longer to find product-market fit. Lucas: That's fair — but remember, this is a side project, not your main bet. If it's not showing traction within six months while you're working on it part-time, the odds are it never will. The opportunity cost is too high. You could be using that time to improve your core product. Luna: I want to push back a little. What about the founder who built Buffer as a side project? Or the guy who built Nomad List? Those took a couple of years to gain traction. Lucas: Good counterexamples. But both of those founders were deeply committed — they weren't treating it as a side project in the sense we're talking about. They were essentially full-time on it after a few months. The side project as strategy approach is for people who have a main business they want to protect. If you're willing to pivot your life to the side project, that's a different conversation. Luna: Okay, I buy that. So what's the practical framework you'd recommend for someone listening who has a main SaaS or agency and wants to start a side project? Lucas: I'd say three things. First, pick something that scratches your own itch — but only if that itch is shared by a paying market. Second, set a hard time budget. I like the 'ten percent rule': no more than ten percent of your working hours go to side projects. Third, have a clear success metric. For me, it's a hundred paying customers or five thousand dollars monthly recurring revenue within twelve months. If I hit either, I consider doubling down. If not, I kill it. Luna: That's disciplined. But I imagine the temptation is always there to keep tinkering. Lucas: Oh absolutely. And that's why having a partner or a community helps. Knowing you have to report to someone — even just a co-founder or a mastermind group — creates accountability. The founders I've seen succeed with side projects don't do it in isolation. They have a friend who asks, 'Did you ship that feature yet?' or 'Did you hit your revenue target this month?' Luna: That makes sense. It's like having a gym buddy for business ideas. Lucas: Exactly. And on that note — and this ties directly into what we're talking about — we put a lot of thought into building a show that's genuinely helpful for founders like you. We deliberately don't run ads on these episodes. If you find value in these conversations and want to support that choice, the link is buy me a coffee dot com slash fexingo. It's a small gesture that keeps this ad-free and independent. Luna: Yeah, I love that we can just focus on the content without interruption. Every little bit helps keep the lights on. Lucas: Alright. Now, back to side projects. I want to talk about a specific mistake I see founders make over and over: building for an audience they don't belong to. Luna: What do you mean by 'belong to'? Lucas: They try to solve a problem for a market they don't have insider knowledge of. A developer builds a tool for dentists, but they've never worked in a dental office. They end up building features nobody uses and missing the ones that matter. The best side projects come from your own professional experience. Luna: So a developer who used to work in logistics builds a shipping calculator. That makes sense. But what if you don't have that kind of niche experience? Lucas: Then you partner with someone who does. Or you become a user first. There's a founder who built a tool for event planners because his wife was an event planner. He watched her struggle with spreadsheets and built a simple web app. That turned into a six-figure side project. He didn't know the industry, but he had a domain expert at home. Luna: So leverage your network. That's a good point — side projects don't have to be solo efforts. Lucas: Not at all. Some of the most successful ones started with two people: a builder and a domain expert. The builder codes, the expert validates and sells. And because it's a side project, they can split revenue fifty-fifty without needing a formal company structure upfront. Luna: That sounds like a great low-risk way to test a business idea. You're not quitting your job, you're not raising money, you're just seeing if there's a market. Lucas: Exactly. And if it works, you have a choice: keep it as a side income stream, or transition to full-time. I know a founder who kept his side project running for seven years while he grew his main agency. Eventually, the side project was making more than the agency, so he sold the agency and focused on the side project full-time. That's the dream scenario. Luna: But that takes patience. Seven years is a long time to keep something on the back burner. Lucas: It does. But for bootstrapped founders, patience is a feature, not a bug. You're not under pressure from investors to grow fast. You can let a side project develop at its own pace. The key is to not let it consume you. Set boundaries, track your metrics, and be honest about when to pull the plug. Luna: Alright, I'm convinced. I'm actually going to think about a side project for my own consulting business. Maybe something small I can launch in a month. Lucas: That's the spirit. And if you do, let us know how it goes. We'd love to hear from listeners who turn a weekend idea into something real.