How I Turned a GitHub Issue into a Thriving Business

Hey there, Indie Hackers! I'm Martin, and I want to share how a simple GitHub issue evolved into my current business, Capgo. It's been quite a ride, and I hope my story inspires you on your own indie hacking journey.

The Nomad Life and an Unexpected Problem

Back in 2021, I took a leap of faith. I resigned from my CTO job, sold my shares, and embraced the digital nomad lifestyle in Lisbon, Portugal. With some savings in my pocket, I dove into building Captime, a mobile app for CrossFit timers.

Little did I know, this side project would lead me to an even bigger opportunity.

While working on Captime, I hit a wall. Updating my Capacitor app was a nightmare - existing solutions were either too expensive or didn't fit my needs as a solo developer. I was frustrated, and I knew I couldn't be the only one.

From Venting to Validating

In October 2021, I decided to voice my frustrations on GitHub. I outlined the problems I was facing:

High costs for small developers
Lack of affordable over-the-air (OTA) updates
Bloated features I didn't need
To my surprise, my post struck a chord. Other developers chimed in, sharing similar pain points. One comment particularly stood out:

"It would be brilliant if there was a Live Update only package for $50/month that included 5,000 Live Updates."

This feedback was gold. It validated my problem and hinted at a potential solution. I realized I wasn't just solving my own problem - I was onto something bigger.

Taking the Plunge

With this validation, I decided. On October 24, 2021, I announced my plan to build a module for downloading updates from a URL. The initial goals were simple:

Download data from a URL
Unzip the data
Replace the current code with the new one
Sounds easy, right? Well, it turned out to be anything but.

The Reality of Building: Blood, Sweat, and Code

What looked simple on paper turned out to be a beast in reality. The code required for this functionality was obscure and difficult to understand. I found myself deep in the weeds of Capacitor's inner workings, grappling with complex file system operations.

Many nights were spent in my van, hunched over my laptop, fueled by coffee and determination. Progress was slow, and there were moments when I questioned if I had bitten off more than I could chew.

But here's the thing about being an indie hacker - you're never truly alone.

Community to the Rescue

When I hit roadblocks, I turned to the developer community, particularly on Discord. The response was incredible. Fellow developers offered insights, helped debug issues, and provided much-needed encouragement.

This collaborative effort was crucial. It helped me overcome technical hurdles and reinforced my belief in the power of open-source and community-driven development.

With this support, things started to click. By November 22, 2021, I had a working version for iOS and was improving the developer experience. Soon after, I added Android support, persistence between app kills, and the ability to revert to the original app version.

Each new feature brought its own challenges, but also a rush of accomplishment. I was building something people wanted!

From Project to Product: The Birth of Capgo

By March 2022, what started as a simple module had grown into a full-fledged product. I announced the release of an auto-update mode, allowing developers to connect to their own backend or use Capgo's backend service.

The response was overwhelming. Developers were praising this solution, calling it a game-changer for their workflows. It was a moment of validation that made all those late nights worth it.

The Unexpected Pivot: Monetization

Here's where things get interesting. Initially, I had no plans to monetize Capgo. My goal was simply to solve a problem for myself and other developers. But the feedback I was getting made me reconsider.

Developers were actually expressing a willingness to pay for a solution that met their needs at a fair price. This feedback, combined with the realization of the ongoing costs to maintain and improve Capgo, led to a pivotal decision.

Taking the Leap: Capgo as a Business

On June 11, 2022, I made the announcement: Capgo would start charging for usage in 15 days. It was a nerve-wracking moment. Would people actually pay for it?

To stay true to the project's roots, I kept Capgo's core open-source, allowing free use of the plugin in manual mode or with a custom server. But for those who wanted the full service, there would now be a cost.

The response? It exceeded my wildest expectations.

The Results: From Side Project to Sustainable Business

The transition to a paid model was smoother than I expected. Within the first month, Capgo had paying customers. By the six-month mark, it was generating enough revenue to cover its costs and my basic living expenses.

Today, Capgo continues to grow. It's not just a side project anymore - it's a sustainable business that allows me to work full-time on something I'm passionate about.

Lessons Learned: What Worked for Me

Solve a Real Problem: Capgo was born out of a genuine need. I wasn't just building something cool; I was solving a real problem that developers faced.

Leverage Community: The support and feedback from the developer community were invaluable. They helped shape the product and spread the word.

Start Small, Iterate Fast: I started with a basic module and continuously added features based on user feedback.

Be Transparent: I shared my journey openly on GitHub and Discord. This transparency built trust and attracted early adopters.

Don't Be Afraid to Charge: If you're providing value, people are willing to pay. Don't undervalue your work.

Keep the Core Open: By keeping the core plugin open-source, I maintained goodwill in the community while still building a business.

The Indie Hacker Journey: It's Not Always Straightforward

My path from frustrated developer to business owner wasn't linear. It involved pivots, late nights, moments of doubt, and unexpected opportunities. But that's the beauty of the indie hacker journey - you never know where it might lead.

Capgo.app started as a solution to my own problem, grew through community support, and evolved into a business that serves developers worldwide. It's proof that with persistence, community engagement, and a willingness to adapt, a single GitHub issue can turn into a thriving business.

To all the indie hackers out there: keep building, keep sharing, and don't be afraid to solve the problems you encounter. You never know - your next frustration could be the seed of your next big opportunity.