I studied MSc Computer Science and later a Postgraduate Diploma in Business Administration. I started my career as a programmer, moved into software architecture, and then into engineering management. My last full-time role was as Technical Director at a fintech startup called Backbase. I spent about a decade in the fintech startup/scaleup world.
Along the way, I always kept side projects going, partly to keep my technical skills sharp, but also because I simply love programming. I tried monetizing a few of these projects, but my career took priority at the time.
In 2021ā22, I decided to take side projects more seriously and push for a second income stream. I eventually came across Cloakist on MicroAcquire (now Acquire.com), which was making about $2k MRR. Cloakist allows you to connect any webpage with a custom domain. I acquired it, grew it significantly, and spun out related products like Sotion, AliasLinks, and ZerpHost.
Building for three years alongside full-time work was exhausting. I even stepped down to a lighter job to make space, but it led to burnout. So, as of July 2025, after 10 months of slow progress, Iāve gone full-time indie
It was risky. Revenue didnāt yet cover living expenses, but with a small financial buffer, I made the leap. Today, Cloakist and Sotion together generate more than $12k MRR.
By the time I became Technical Director, the career path ahead (VP ā SVP ā etc.) felt like more of the same. I wanted new challenges, independence, and to own my own time. After going through burnout, the motivation to go solo only grew stronger.
I also had practical considerations: I have a wife and two teenage boys, so financial stability was crucial. I knew I couldnāt afford a long runway with repeated failed experiments. Thatās why acquiring a business with traction appealed; it gave me a head start.
Running my own SaaS apps also meant I could design my schedule to be more flexible with family. And because the products are subscription-based and relatively automated, they donāt demand constant firefighting.
My past side projects taught me to avoid over-engineering. As a software engineer, itās tempting to obsess over architecture or clean code, but what really matters is delivering value to customers and growing the business. That shift in mindset made all the difference.
When I acquired Cloakist, it was very barebones. Many onboarding steps were manual, day-to-day operations werenāt automated, and it only supported a few platforms.
My first steps were automating processes, improving onboarding, and investing heavily in SEO. That paid off in the long run. I also saw an opportunity to niche down: I built Sotion, a spin-off focused specifically on Notion websites. Sotion eventually surpassed Cloakist in revenue.
Cloakist and Sotion are built with React/Next.js, Node.js, Tailwind, and Supabase as the database. Hosting runs on AWS, with Cloudflare for caching.
We use Stripe for billing, Sidemail.io for emails, Crisp for support, Feather.so for blogging, and Fathom Analytics for privacy-friendly tracking. Itās a lean, modern stack that balances flexibility with reliability.
With my newer products, AliasLinks and ZerpHost, I've started using PHP Laravel, which has been an awesome ecosystem to build on.
I've hit many technical challenges while building. Here are a few of the worst:
AWS costs spiraled at one point, forcing me to re-engineer core infrastructure.
With 30+ platform integrations, changes on their side often break things, sometimes even customer sites, requiring a fast response.
Hosting customer websites means dealing with bad actors. I had to build monitoring and response processes for phishing or fraudulent sites.
Cloakist and Sotion both use a SaaS subscription model with monthly and annual plans. Pricing is tiered by both the number of websites supported and feature depth. That way, we capture both customers who want āmore sitesā and those who want āmore advanced features.ā
Revenue growth comes from:
I mentioned that I doubled down on SEO when I acquired Cloakist āĀ well, that has been the biggest driver of growth. It includes documenting use cases, ranking for key terms, and creating useful content around the platforms we support. Word of mouth and organic traffic keep compounding over time.
Early on, Indie Hackers and X gave encouragement, visibility, and credibility, but long-term, my customers werenāt really there. Cold email campaigns didnāt deliver much, and I havenāt tried paid ads ā my hunch is they wouldnāt work well for this type of SaaS.
So the growth engine is mostly SEO + consistent product improvements that improve retention. Balancing product, marketing, and support as a solo founder is tough, so this mix has been really helpful.
My advice: Start SEO sooner. It compounds massively and is even more relevant with AI discovery that will likely surpass traditional search.
Competition came and went, but the biggest scare was when Notion launched its own website publishing.
It ate into Sotionās market share but also grew awareness. We adapted by focusing on unique features like membership management, which has become a key differentiator.
Here's my advice:
Consider acquisition as a path; it reduces risk and gives you traction from day one. That was my single best move.
Focus on the core product. Keep it lean, deliver value, and expand only as you understand your customers better.
Think in terms of workālife integration, not balance. Set aside time for focused, high-impact work, and ignore the noise. Most tasks can wait, and half wonāt matter later.
Practice feature discipline. I learned not to chase every customer request. Stick to your productās core value proposition and only expand where it truly matters.
SEO is one of the best long-term bets you can make. Start early, document everything, and let it compound.
Automate early. Stable, hands-off systems buy you time to focus on growth.
Lastly, I'll say this: I wish Iād started years earlier. A career gave me experience, but the freedom I have now is priceless. Worst case, you can always get another job.
Right now, my focus is on stability and independence: maintaining MRR, steady growth, improving conversion, and boosting retention. Long-term, Iād like to sell Cloakist and Sotion, and maybe start over again with another SaaS.
My current apps are B2C/SME-focused. Next, Iād like to move into B2B SaaS, whether thatās via acquisition, a spin-off, or a fresh build.
Working solo has been amazing, but I do miss team interaction. Thatās why I spend ~20% of my time consulting, which gives me variety and balance.
The vision: Sell my current SaaS in a few years, then start and grow a new B2B SaaS product.
You can check out my holding company with all current and past (failed) products. My most active products are sotion.so and cloak.ist. And follow along on X, where I post about my journey.
Leave a Comment
Really enjoyed reading this ā especially the part about resisting the urge to over-engineer. Iāve been through the same trap myself: as engineers, itās so tempting to perfect architecture when what really matters is helping users make progress.
Thatās actually why we built LiteTracker ā a project management tool born after Pivotal Tracker was discontinued. Instead of starting teams off with a blank board and leaving them to design their own workflow, LiteTracker bakes in proven agile structures from day one. The idea is the same as you described: keep it lean, keep it useful, and let teams focus on shipping rather than reinventing process.
Thanks for sharing your story ā itās motivating to see how youāve turned side projects into a sustainable business. š
Bruceās story shows how buying and growing a small SaaS can be a safer path than starting from scratch. By keeping things lean, focusing on SEO, and resisting over-engineering, he turned side projects into $12k MRR and the freedom to work on his own terms.
Inspiring story, Bruce š. Iām just getting started on my first micro-SaaS (BusinessAdBooster), so hearing about your path to $12k MRR is motivating. Curious ā if you had to start over again from zero, would you still acquire a SaaS, or build one from scratch?
If I had to start from zero, Iād still definitely look at acquiring again, it gave me momentum and revenue from day one. That said, building from scratch teaches lessons you donāt always get through acquisition, so both paths have real value.
And now that my main product is stable and brings in sufficient revenue, I have more time to build new things from scratch.
Nice stuff this. Question - did you acquire all cash? Or take financing?
Thanks! I used cash and a small bank loan to finance the acquisition. Important point to note is that the business was already generating enough cash flow to easily cover the bank loan.
Really? But how is that possible?
This article feels so timely. Iāve been thinking more about acquiring vs. building to help kickstart my side hustle side quest. I like the point on avoiding over-engineering and focusing on delivering value and business growth.
Glad it resonated! I think that balance and avoiding over-engineering while focusing on customer value really makes a difference early on.
Really enjoyed this, buying a micro-SaaS after years of side hustling is a calm, low-risk path to freedom. The way you picked a narrow problem, tightened ops, and focused distribution (instead of trying to rebuild everything) is exactly how these bets compound.
Curious on two fronts: what single signal told you it was safe to quit (net profit trend, pipeline, or runway)? And in the first 30 days post-acquisition, which lever moved revenue most; pricing cleanup, onboarding fixes, or one dependable channel?
P.S. Iām with Buzz; we build conversion-focused Webflow sites and pragmatic SEO for product launches and small SaaS. Happy to share a tight 10-point GTM checklist if useful.
Deciding when to go all in will be different for everyone. For me, because I have a family to support, I had to be able to cover all our living costs. The signal for me was when I had enough confidence that the projected ARR (less expenses) would be sufficient.
Thanks! For me, because I have a family to support, I had to be able to cover all our living costs. The signal for me was when I had enough confidence that the projected ARR (less expenses) would be sufficient. I needed a reliable foundation. In the first 30 days, the onboarding tweaks had the biggest impact.
But Iām curious, what have you found to be the strongest early lever in your own projects?
This is an inspiring journey really shows the value of focus, lean growth, and automating early š
Reading about your SEO and retention strategies reminds me how important it is to keep both product and workflow organized.
In my experience with Teamcamp, having a clear system for managing tasks, customer feedback, and project priorities makes it much easier to balance multiple initiatives without losing track.
Thanks for sharing such a detailed breakdown. itās full of actionable insights for solo founders and indie hackers alike!
Thanks so much! And I totally agree... having a clear system in place makes a big difference, especially when youāre juggling multiple initiatives as a solo founder. Glad you found the breakdown useful!
This is such an inspiring and grounded journeyāthank you for sharing the real, unglamorous parts (burnout, financial risks, feature discipline) along with the wins.
A few things that really stood out to me:
The decision to acquire rather than build from zero is often underāappreciated, and your approach shows how it can reduce risk and accelerate momentum.
Leaning into SEO + retention as compounding growth levers is wise, especially for solo founders.
Your emphasis on resisting overāengineering resonates deeplyāso many projects stall when perfect code becomes the enemy of shipping value.
Congratulations on crossing that threshold into full-time indie work. Your story makes it feel more real for others considering the leap. Wishing you continued momentum, and Iāll be following along to see where you take Cloakist, Sotion, and future ventures!
Really appreciate that:) Acquisition over building from scratch definitely helped me de-risk and focus on growth. And yes, resisting over-engineering is a constant discipline, even today 3 years later! Thanks for the encouragement, it means a lot.
Love the breakdown of moving from full-time to indie ā really shows the real grind behind $12k MRR. Two points Iāve noticed from similar journeys that often get overlooked:
1ļøā£ Revenue vs. Burn Balance ā The leap you made works because you treated your buffer like a runway, not a cushion. Many indie founders underestimate how psychological safety with a buffer can accelerate growth decisions.
2ļøā£ Compounding Systems Early ā Your note on automating early is gold. Iāve seen founders who ignore micro-automation waste weeks monthly just on ops. Documenting everything + automated workflows early doesnāt just save time ā it creates repeatable growth leverage that scales faster than additional hires.
One extra angle: For B2B spin-offs, the sweet spot is high-touch micro MRRs first, then systematize onboarding before scaling. That way, you lock in retention before chasing volume, which aligns perfectly with your long-term exit strategy.
Curious ā when you moved to solo, how did you prioritize consulting vs. product iteration without fragmenting focus? Thereās a subtle art in balancing that which most founders miss.
The great thing about SaaS is that any time you spend improving the product is beneficial to all users, helps with retention, and improves stickiness. So even if you go through periods where you are focusing on other stuff, the business still keeps growing because of your previous efforts.