Today I managed to disappoint the same person twice, for two entirely different reasons.
Both conversations revolved around the WordPress plugins I develop, and both left me thinking about how differently people view software development, running a business and the value of someone's time.
It also reminded me of something I've believed for a long time: just because you can make money from something doesn't necessarily mean you should, or even that you want to.
Why I Don't Do Black Friday Discounts
The first conversation started with a fairly straightforward question.
Someone was interested in purchasing one of my plugins and wanted to know whether I'd be offering a Black Friday discount.
My answer was no.
I don't generally run sales or promotional discounts. Usually, the only time I offer a reduced price is when I launch a new plugin, and that's a relatively short introductory offer.
There are a few reasons for this, but the biggest is fairness to existing customers.
If someone buys a plugin from me today at full price, I don't particularly like the idea of offering it at a substantial discount a few weeks later simply because a particular shopping event has arrived.
I'm not suggesting there's anything wrong with Black Friday promotions. They clearly work for plenty of businesses, and I understand why companies use them.
They're just not something I want to build into the way I operate.
Unfortunately, the person asking wasn't particularly impressed with that answer.
They explained that I would lose potential sales and suggested that refusing to offer discounts was bad business practice.
And perhaps, from a purely commercial perspective, they have a point.
But that assumes my primary objective is to sell as many copies of my plugins as possible.
It isn't.
My Plugin Shop Was Never Really Part of the Plan
I run Really Useful Plugins, but the reality is that selling WordPress plugins was never intended to become a major part of my business.
Most of the plugins I've developed started because I needed something for my own projects.
Occasionally, someone else would see what I'd built and ask whether they could purchase it. If there was enough interest, I'd spend the additional time packaging it, documenting it and making it available commercially.
Eventually, this happened often enough that creating a plugin shop made sense.
But there's an important distinction between having a shop that sells plugins and wanting to build a large plugin business.
For me, the shop is an outlet for tools I've already created. It gives other people access to something that might solve a problem for them, and it generates some additional revenue in the process.
That's a perfectly reasonable arrangement as far as I'm concerned.
What I don't particularly want is to turn it into a business that demands an increasing amount of my time.
Every plugin sale brings potential support obligations. There's usually a noticeable increase in support requests when someone first starts using a plugin, and that's entirely understandable.
People have questions, their environments differ, and sometimes things don't work quite as expected.
But support takes time, and time is something I have to manage carefully.
So when I was told that refusing to offer discounts would cost me sales, my response was probably not what they expected.
I explained that I wouldn't be particularly concerned if I never sold another copy of that plugin.
That might sound like a strange thing for someone running a plugin shop to say, but it reflects the reality of why the shop exists.
I'm happy when people find my plugins useful and purchase them. I'm equally happy for the shop to remain a relatively small part of what I do.
I don't need every project to become a revenue stream, and I certainly don't need every revenue stream to grow indefinitely.
Then Came the Question About Static Cart
Later, the same person came across some of my videos and articles about Static Cart.
For anyone unfamiliar with it, Static Cart is an experimental project I've been building using the API provided by FluentCart, the e-commerce platform developed by WPManageNinja.
The question this time was when Static Cart would be available to purchase.
And again, my answer wasn't what they wanted to hear.
I currently have no plans to release Static Cart as a commercial product.
That's not because I don't think it has potential. In fact, I suspect it could be quite popular.
Early in development, I did consider whether it might become something I could sell. But the further I went with the project, the more I realised that commercialising it wasn't something I wanted to take on.
The reasons are largely the same as those behind my approach to the plugin shop, although with Static Cart, they're considerably more important.
An E-commerce Plugin Is a Serious Responsibility
There's a significant difference between supporting a small utility plugin and supporting software that forms a critical part of someone's online business.
If a utility plugin stops working, it's inconvenient.
If an e-commerce system stops working, people can lose sales.
That changes the expectations and responsibilities considerably.
A commercial release of Static Cart would mean properly testing it across different environments, dealing with compatibility issues, keeping up with changes to FluentCart, maintaining security and providing ongoing support.
And because the software would potentially be central to someone's ability to take orders and generate revenue, that support would need to be dependable and timely.
I simply don't have the capacity to make that commitment.
It wouldn't be fair to customers to sell them something so important without being confident that I could provide the level of support they might reasonably expect.
And it wouldn't be fair to myself to take on a substantial ongoing responsibility for a project that was never intended to become a business.
The person I was speaking with found this difficult to understand.
They felt I'd wasted my time developing something I wasn't planning to sell. They also felt I'd wasted theirs by publishing videos about something they couldn't purchase.
I can understand the disappointment of discovering an interesting project only to find it's not available.
But I don't agree that the development effort was wasted.
Far from it.
Sometimes I Build Things Just to Learn
Static Cart started as an experiment.
I wanted to explore what was possible using the FluentCart API, understand how the system worked and push my own knowledge of the platform further.
That's something I've always enjoyed doing as a developer.
When I start working with a new platform or framework, I like to understand it properly. I don't just want to know enough to complete the immediate task in front of me.
I want to understand how the different pieces fit together, what's possible, where the limitations are and how far I can take things.
Sometimes that means building something considerably more involved than the original learning exercise required.
Static Cart is a good example of that.
I was experimenting, testing ideas, solving problems and, perhaps most importantly, enjoying the process.
And I learned a great deal along the way.
That knowledge has value regardless of whether the resulting software ever appears in a commercial plugin shop.
I may well use Static Cart on my own websites in the future. If I do, I'll be responsible for maintaining it for my own use, which is an entirely different proposition from supporting installations across dozens of other people's businesses.
I'd also be delighted if another developer saw the project and decided to create something similar, or if WPManageNinja took inspiration from the approach and incorporated some of the ideas into FluentCart itself.
The fact that I don't intend to sell Static Cart doesn't mean I think the ideas behind it should go nowhere.
It simply means I'm not the person who wants to turn it into a supported commercial product.
Why Not Just Open Source It?
One obvious question is why I don't simply release Static Cart as an open-source project.
After all, I've released other projects as open source, so why not this one?
The answer comes down to responsibility again.
Static Cart was developed as an experiment. I haven't put it through the level of security auditing, testing and review that I would want before making an e-commerce-related plugin publicly available.
There may be issues I've not identified, including potential security vulnerabilities.
And while putting code on GitHub with a disclaimer might seem like a simple solution, I'm not particularly comfortable with that approach for software that could end up being used to run someone's online shop.
People might see a working demonstration, download the code and assume it's suitable for production use.
I don't want to encourage that when I haven't done the necessary work to establish that it's safe and reliable enough for that purpose.
So, for now, Static Cart remains an experiment.
That may disappoint some people, but I think it's the responsible decision.
Open Source Is Still a Big Part of What I Do
What's interesting is that much of my development work follows a similar pattern to Static Cart, although the resulting projects are often much smaller and easier to maintain.
Take UUPD, for example.
I originally built UUPD because I wanted a more efficient way to handle updates for my own plugins without having to bundle roughly 200KB of additional code into each one.
It solved a problem I had.
Likewise, UUPD-Licence-UI came about because I wanted to avoid repeatedly including a substantial licensing code bundle in individual plugins.
Both projects were driven by the same principles: efficiency, standardisation and making my development workflow easier to maintain.
They weren't created because I'd identified an exciting new market opportunity.
They were created because I needed them.
Once they existed, making them available to other developers seemed like a sensible thing to do.
And that's exactly what I've done.
UUPD is open source, as are the compatibility plugins I continue to release for it.
I'm aware that some reasonably large companies are using UUPD, and I'm genuinely pleased that other developers have found it useful.
But I have no plans to start charging for it.
It serves its original purpose for me, and making it freely available means other people can benefit from the same work.
That's a good enough outcome in my book.
AI Has Changed the Value Proposition Too
There's another factor worth acknowledging.
We're now working in a world where tools such as ChatGPT and Claude have made it considerably easier for developers, and even reasonably technical non-developers, to create their own software.
Many of the smaller utility plugins I've built could probably be recreated fairly quickly with the assistance of AI.
I'm comfortable with that.
It doesn't particularly worry me if somebody decides to build their own version of something I've created rather than purchase mine.
Of course, generating code and maintaining reliable software are two very different things. There's still value in having something that has already been developed, tested and supported.
But I'm realistic about the changing landscape.
If my entire business depended on selling small WordPress utility plugins, I might view that differently.
Fortunately, it doesn't.
The plugins exist because they solve problems, and the shop exists because some people would rather purchase a ready-made solution than build and maintain their own.
That arrangement works for me.
Not Every Project Needs a Business Model
By the end of these exchanges, I'd received somewhere in the region of 20 emails and at least two support tickets about the two issues.
That's a surprising amount of correspondence over a decision not to offer a discount and another decision not to sell a particular product.
It did make me reflect on whether I'd approached either situation incorrectly.
Perhaps I could have explained my reasoning differently, or been a little more diplomatic in some of my responses.
But having thought about it, I don't believe the underlying decisions were wrong.
I don't think there's anything unreasonable about choosing not to run Black Friday promotions.
And I certainly don't think there's anything wrong with developing software for the experience, enjoyment or knowledge it provides, without having a commercial release in mind.
There's a tendency, particularly in the technology world, to measure the value of everything against its potential to generate revenue.
If you've built something useful, why aren't you selling it?
If people want it, why aren't you launching it?
If it could become a successful business, why aren't you pursuing that opportunity?
Those are perfectly valid questions, but they assume that commercial success is always the desired outcome.
Sometimes it isn't.
Sometimes the goal is to solve your own problem, improve your understanding of a platform, simplify your workflow or just see whether an idea is technically possible.
And sometimes the reward is simply having built something interesting.
Doing Things on My Own Terms
I enjoy developing software. I enjoy exploring new tools, experimenting with ideas and finding better ways of doing things.
I also enjoy sharing some of that work with other people, whether that's through free open-source projects, commercial plugins, videos or articles.
But I want to remain selective about which projects become products and which remain experiments.
Because the moment you start selling software, particularly software that other businesses depend upon, you're taking on obligations that go well beyond writing the original code.
Those obligations are important, and I don't want to take them on unless I'm prepared to fulfil them properly.
So yes, I may lose a few sales by not offering Black Friday discounts.
And yes, Static Cart might turn out to be something that could have generated a worthwhile amount of revenue.
I'm comfortable with both possibilities.
Not every opportunity needs to be pursued, not every experiment needs to become a product, and not every successful project needs to be measured by how much money it makes.
Sometimes it's enough to build something because you wanted to see if you could.
And personally, I think there's still plenty of value in that.