Hitting a 5-figure MRR with an open-source portfolio

This is very inspiring.. adding value by opensource strategy. Also hats off to Caleb for staying lean moneywise.. That's what lots of people ar missing.

It's all about passion

While everyone still hoards "proprietary" code like it's 2005 gold, Caleb quietly proved open-source is the sharpest distribution weapon alive. Give the painkillers away, charge for the maps and upgrades—boom, 5-figure MRR.

The weakness exposed? Chasing moats in isolation while your "secret" rots unseen. True leverage was never the code. It was showing up naked with value first.

Mind blown.

honestly the money advice is the most underrated part of this whole post. everyone's obsessed with growth and hiring but caleb just quietly stacked cash and stayed lean.

also the audience thing is real - he wasn't starting from zero, he'd already spoken at laravel conferences. that head start mattered a lot.

question for anyone who's done this - how do you build that initial trust in a community when you're completely new?

bana pek inandirici gelmedi bunu nasil yaptiği biraz daha hayat hikayesi gibi olmuş yada şans diyebiliriz. ben denesem olmaz

Really strong example of how open source can be a distribution engine, not just a product strategy.

The code is free, but the trust, community, and attention around it become the real leverage. That’s what makes the courses, components, and ecosystem products possible.

Also appreciated the honesty that in open source, the moat often isn’t the software itself — it’s staying relevant and continuing to earn trust.

Interesting approach. Have you run into stability issues over long-running agent sessions? I’ve been experimenting with runtime monitoring and drift detection, and reliability over time seems to be a major challenge.

Caleb's line "Listen to the signals around you. People often tell you what they want, and it's surprisingly hard to listen to them and follow through" hit me hardest.

I launched a prayer app for churches a year ago and ignored every signal users were sending me. Pastors said the UX was confusing. Small group leaders said they needed privacy controls. I heard them and kept shipping features instead. A year later, I killed the whole thing and rebuilt from scratch as SoapBox Prayer. Just launched on Product Hunt this week.

The thing I wish I had understood earlier is that Caleb's advantage is not just charisma or Laravel audience — it is the courage to act on signals other founders explain away. I spent months telling myself "pastors don't understand modern apps yet" when the real answer was "my app was built for me, not for them."

The other part of his story I envy is the audience head start. I had zero audience when I launched. No conference talks, no agency cred, no Twitter following in the faith-tech space. Open source and community-first sounds simple until you realize everyone telling you to "build in public" already had a public to build to.

For founders reading this without an existing audience: Caleb's playbook is still the right one, you just have to do the audience-building step first. It took me a year of failing before I realized I was skipping the foundation.

Congrats Caleb. Five-figure MRR from open source is the dream and you have clearly earned it.

The moat question is the most interesting tension here. The code can't be a moat in open source, but what Caleb built around it is much harder to replicate: a learning ecosystem, a premium layer (Flux UI), and years of trust with the Laravel community from conference talks and consistent shipping. That ecosystem IS the moat. The audience-first ordering deserves more attention too. Building for people you already understand is fundamentally less risky than building first and hoping to find users later. Caleb skipped the painful discovery phase because he'd earned credibility in the community where his tools would live. That's a compounding advantage from investing in relationships before code.

The moat question is the most interesting unresolved tension in this piece. The code itself can't be a moat in open source — that's by definition. But what Caleb actually built around the code is much harder to replicate: a learning ecosystem (courses, ebooks), a premium layer (Flux UI), and a trust relationship with the Laravel community that took years of conference talks and consistent shipping to establish. That surrounding ecosystem IS the moat, even if the underlying code isn't.

The audience-first ordering also deserves more attention than it usually gets. Building for people you already understand is a fundamentally different risk profile than building something and hoping to find an audience later. Most of us do it the wrong way around — we get excited about a technical idea, build it, then spend months trying to convince strangers it matters. Caleb skipped that painful discovery phase because he'd already earned years of credibility in the community where his tools would live. That's not luck — that's a compounding advantage from investing in relationships before investing in code.

This is pretty incredible. Tech is no longer a moat - so might as well go open-source because if your idea is easily steal-able anyways, you were never competitively differentiated enough. Still, good to keep secrets sometimes

Interesting platform with a lot of valuable discussions around building and growing projects. Always good to see people sharing real experiences and insights.

Open source can be such a powerful moat when done right you build trust and community first, then monetize around the edges. The hardest part is usually finding that sweet spot between keeping core features free while creating enough value in premium offerings that people actually pay for them.

This is such a refreshing take. What stands out most is how simple the core idea is: build something genuinely useful, stay close to your audience, and don’t rush to overcomplicate the business side.

Also love the honesty about charisma and audience—it’s something people often ignore, but it clearly played a huge role here.

The “don’t spend money” advice hits hard too. Feels like a reminder that freedom comes more from control than from revenue alone.

Really inspiring journey 👍

I think the part about "don't spend money" hit me the hardest. Most founders do the opposite. They raise a tiny bit of cash and immediately hire three people and rent an office. Then they die six months later.

You built an audience first, then the product. That is the reverse of what most people try. They build something nobody asked for, launch to crickets, then wonder why Twitter is not magically sending them customers.

The "natural charisma" thing is interesting too. You are honest about it being an advantage. Most people pretend charisma does not matter. But it does. A lot. I have seen developers with better products lose to worse products just because the founder was awkward and could not sell.

One question though: how do you balance open source (free) with making a living? You mentioned sponsorships and courses. But do you ever worry that someone will just take your open source work, wrap it in a paid service, and compete with you? Or has that not been a real problem yet?

Anyway, congrats on the five figures. That is huge for open source. Most people are out here begging for donations. You actually built something sustainable.

Followed you on Twitter.

open-source to MRR is the road I'm on too - building a sprint planner and the paid conversion is where it gets hard. what flipped it for you?

The "keep it real" advice sounds simple but it's the hardest thing to actually execute. Most founders — myself included — have a natural tendency to build what they find interesting rather than what users are telling them they need. The gap between "I think users want X" and "users are literally asking for X in every support message" is where most products die. The open source moat problem is real and underrated. You solved it the only way it can be solved: by being so far ahead on the vision that by the time others copy the current version, you're already building the next one. Curious how you think about the line between "staying ahead" and "burning out trying to stay relevant" — that tension seems like the defining challenge of your model.

That is a really inspiring breakdown. It’s rare to see people talk about the actual transition from maintaining open-source projects to building a sustainable business model around them. The point about building trust through transparency is spot on - it definitely makes the "selling" part feel a lot more natural.