Latest / Solopreneur Sessions with Fexingo: One-Person Businesses, Freelancing, and Independent Work / How a Solo Developer Built a Business on One Open Source Plugin
Transcript
- Lucas: So, Luna, you remember that story about the guy who built a business on a single blog post? Well, today I've got one that's even more niche—a solo developer who turned one open source plugin for a content management system into a steady six-figure income. Luna: Okay, that's intriguing. Which CMS are we talking about? And how does a plugin become a whole business? Lucas: It's for a lesser-known CMS called Craft CMS. Not the biggest player, but it's popular among agencies and developers who want flexibility. The plugin is called, well, I'll get to that in a second. The developer—let's call him Alex—started by releasing a free plugin that solved a really specific problem: it let clients edit complex page layouts without breaking the site. Luna: So he identified a pain point and gave the solution away for free. Classic trust-building move. Lucas: Exactly. And the free plugin got traction—thousands of downloads within the first year. But it wasn't until he added a paid tier with advanced features that things really took off. The free version handled basic layouts; the paid version added things like version control for content editors and a drag and drop builder that saved agencies hours per project. Luna: That's a smart upgrade path. What was the conversion rate? Did he ever share those numbers? Lucas: He published a breakdown on his blog—he's pretty open about the business side. Roughly one percent of free users converted to the paid version, which is actually on the low end for freemium, but the paid plan was a one-time fee of two hundred ninety-nine dollars, not a subscription. So even with a low conversion, the math worked. Luna: One-time fee? That's interesting. Doesn't that mean he has to keep finding new customers every year? Lucas: That's exactly the risk he identified. So after a year of one-time fees, he introduced a maintenance plan—sixty dollars a year for updates and priority support. That's where the recurring revenue came in. By the end of year two, he had about four hundred paying customers and a hundred of them on the maintenance plan. That's roughly forty thousand dollars in recurring revenue, plus new licenses. Luna: So he built a hybrid model. One-time license for the product, subscription for ongoing value. That's clever. But is he doing everything solo? Support, updates, marketing? Lucas: For the first two years, yes. He was doing all of it. He even wrote the documentation himself. But he admitted in that post that support emails were eating up about ten hours a week. That's when he decided to raise the price on new licenses to three hundred ninety-nine dollars, which actually reduced the number of support tickets because only serious buyers were purchasing. Luna: Raise prices to filter out high-maintenance customers? That's a classic move. Did it backfire? Lucas: Surprisingly, no. The download numbers stayed steady, and the conversion rate actually went up slightly, because the buyers who did commit were more invested in the product. He also bundled in a few extra features that justified the higher price. By year three, he was making around ninety thousand dollars a year, and that's when he quit his freelance gig to focus on it full-time. Luna: Ninety thousand from a single plugin—that's not chump change. But I'm curious, what about the open source aspect? Isn't the code freely available? How do you sell something that people can just copy? Lucas: That's the nuance. The core plugin is open source, but the paid version has a license that restricts redistribution and commercial use. So agencies can use it on client projects, but they can't resell it or fork it for their own products. It's like how some open source databases have paid enterprise features—the open source part builds trust and community, while the paid part is where the business lives. Luna: That makes sense. But the risk is that someone could just clone the open source version and undercut him. Has that happened? Lucas: He mentioned one fork that popped up on GitHub, but it never gained traction because the fork didn't have the documentation, the support, or the integrations that agencies needed. The community stayed with him because they trusted him. That's the moat—not the code itself, but the ecosystem around it. Luna: So the real product is the trust and support, not just the code. That's a lesson for any solopreneur. Lucas: Absolutely. And he's not stopping there. This year, he's planning to release a companion plugin that syncs content between Craft and a popular headless CMS. He sees it as a natural extension—his existing customers already need that bridge, and it introduces his work to a whole new audience. Luna: Expanding into adjacent tools without abandoning the core product. That's the right move. But what about the competition? Craft CMS has a plugin store with hundreds of options. How did he stand out? Lucas: He had two advantages. First, he was an early mover—there was nothing else that did exactly what his plugin did when he launched. Second, he really listened to the community. He read every forum post and support request, and he built features that people actually asked for. That created a loyal following that no competitor could easily replicate. Luna: Listening to your users is underrated. It's not just about the feature, it's about the feeling that they're part of the process. That's how you build a community, not just a customer base. Lucas: Right. And the numbers prove it. His plugin has over twelve thousand downloads now, and he's got a four-star rating average on the plugin store. He shared that his Net Promoter Score, which he measured informally through a survey, was around sixty-five—which is solid for any software. Luna: Sixty-five is really good. So what's the biggest challenge he faces now? Is it time, competition, or something else? Lucas: He says it's keeping up with Craft CMS updates. Every time the core software releases a new version, he has to test his plugin and make sure it's compatible. That's a constant time sink. But he's also learned to say no to feature requests that don't fit the product's vision. That focus has kept his codebase manageable and his support load down. Luna: Saying no is hard for a solo developer who wants to please everyone. But it's essential for sustainability. So, Lucas, what's the one takeaway you'd want our listeners to get from this story? Lucas: For me, it's the power of starting tiny. He didn't try to build a platform or a suite of tools. He just found one problem and solved it really well. And then he let that success guide his next move. It's a reminder that you don't need a grand vision to start a business—you just need a specific problem that people are willing to pay to have solved. Luna: And that's the beauty of the solopreneur path. You can iterate, learn, and grow at your own pace. I love that he shared the numbers so openly—it gives other solo developers a realistic benchmark for what's possible. Lucas: Yeah, and honestly, if today's episode moved your work forward in some small way, you know the link—buy me a coffee dot com slash fexingo. It's the smallest ask we make, and it keeps this show ad-free and independent. Luna: That's right. Every little bit helps us keep bringing you these deep dives into real solopreneur stories. And honestly, it's a great way to say thanks if you've gotten value from any of our episodes. Lucas: So, back to Alex—he's now considering whether to add a subscription tier for enterprise teams that need advanced multi-site support. He's been running the numbers, and he thinks it could double his revenue without a huge increase in support load. Luna: That sounds promising. But he'll have to be careful not to cannibalize his existing one-time license sales. How does he plan to position it? Lucas: His idea is to make the enterprise tier an add-on for agencies that manage multiple client sites. It would include a centralized dashboard and automated backups. He's planning to price it at forty-nine dollars per month per agency. That's a different value proposition from the one-time license, so it could actually attract a new segment. Luna: That's a smart way to diversify. He'd be selling an ongoing service, not just a product. I hope he pulls it off—and I'd love to hear an update in a year. Lucas: We'll have to reach out to him. But for now, I think the real lesson is that one product can be enough to build a sustainable business if you focus on a real need, build trust, and evolve with your customers. Luna: Well said. And maybe that's the inspiration someone needs to start tinkering with that side project they've been putting off. Lucas: Until next time, keep building—and keep it simple.