Why Free Plugins Should Always Provide Support - ManageWP

Why Free Plugins Should Always Provide Support


A few weeks ago I wrote a post entitled Is WordPress SEO by Yoast Broken? It attracted a lot of attention for a number of reasons, not least the issue of free plugin support.

In the post I discussed a number of problems that I had been experiencing with Joost de Valk’s famous plugin. Since it is free, I did make it clear that I never expected anything from Yoast in terms of support.

However, I also made the point that a plugin with problems and no support is a plugin that will eventually be abandoned by its users (please note that I do not intend to imply that Joost provides no support). Simple logic dictates that if something doesn’t work, people will not want to use it – a broken product is still broken, even if it is free.

With plugins, bugs will inevitably pop up as more sites use it and WordPress itself develops. There is no doubt that support is integral to the ongoing functioning of a plugin.

But how can one provide support for a free plugin? Is that even sustainable? And if so, how?

The Point of Free Plugins (From a Developer’s Point of View)

As far as I can tell, there are three different kinds of plugin developers:

  1. Those who develop plugins for themselves and release them on WordPress.org so that others can use them too.
  2. Those who develop plugins for themselves and release them on WordPress.org with the aim of monetizing their venture at some point in the future.
  3. Those who develop plugins with a clear plan for monetization.

I have no problem at all with any of these approaches. Personally speaking, I would put myself somewhere between the first and second group. With the help of my programmer I develop plugins to deal with the challenges that WordPress presents to me.

I figure that I might as well offer those same solutions to others – after all, why not? I also know that, while I don’t have any sort of grand plan, I might one day be able to make a little bit of money from the goodwill that I build up.

In my opinion, plugin developers that fall into the first group that I described are pretty rare. Even the most altruistic among us will tend to have some notion of monetization down the line, even if it is nothing more than a vague twinkle in their eye.

The way that I see it, that first group are the only ones who can get away with not providing support for their plugin.

It’s got nothing to do with owing anything to the end user – after all, the plugins are free. But it’s got everything to do with building a brand and a reputation, which will be important later on when the time to monetize does come.

Free Support: So Many People Miss the Point

Let me make something abundantly clear at this juncture: no developer of free plugins has a responsibility — moral or otherwise — to provide free support for their plugins. As far as I am concerned, they can do whatever they choose.

I will however qualify that statement: if a free plugin developer has no intent of offering any kind of support for their plugin(s), they may want to consider taking them off of WordPress.org.

Why? Because people download plugins with the expectation that they work, just like people buy cars with the expectation that they can actually drive them. Users expect a functioning plugin, so if they end up receiving something that negatively affects their site or is buggy, they’ll (understandably) be unhappy.

In a way, uploading a faulty plugin to WordPress.org is tantamount to making a false promise. When a plugin is in the WordPress.org repository, people should be able to have a reasonable expectation that it will be free of crippling issues. Releasing a plugin that is bogged down in bugs that will never be fixed betrays the basic trust that users should be able to have in WordPress.org.

That is why I believe that plugin developers have a moral obligation to take reasonable measures to prevent such a situation from arising. Although a free plugin developer certainly may not be willing to provide support on every issue, if they’re uploading their plugin to WordPress.org then they should be sure that common bugs are ironed out as and when necessary.

When Is Support Necessary?

Moving on from there, I believe that any plugin developer who intends to profit from their plugins (either now or in the future) should offer support. It’s an issue of practicality.

That support can either be free or paid, but it should be there. Yes, even paid support can help. Even if it is a small barrier to some, it at least provides an avenue to fixing users’ problems. The important thing is that the people using a plugin should have somewhere to turn when issues arise (as they invariably will).

Support is an integral part of customer service – especially when it comes to software. Because it will deal with issues that make the plugin unusable, support is often as important as the product itself and relies upon it in an integral fashion.

Without some support, the plugin can be more of a hindrance than a help. After all, what is the point of a plugin that is so buggy that nobody can actually use it? Support is not an end in itself, of course, but it does serve as a means to making sure that a product is actually usable.

This isn’t about the moral arguments for providing support – it is about creating a brand and a reputation that you are proud of.

It is a matter of efficacy. That brand and reputation will translate directly into higher earnings when the time does come to monetize.

Taking this long view is important because that is where the money is to be made. You can’t rake in thousands a week after the release of a free plugin – it just doesn’t work that way. Earnings will come with a long term plan for monetization, but if you don’t provide stable support, there will be no long term. If you do not provide support and people run around the internet complaining about your buggy plugin, you will have a serious problem on your hands.

On the other hand, if you do provide support, people will trust you as a developer and trust that your plugins work. That helps build a solid base for success.

Developers Should Never Feel Compelled to Offer Free Support

I should add a caveat to all of this: while I believe that you must offer support for your plugin, that support does not need to be free. Free support for free plugins is not a sustainable business model. Hell, it’s not a business model at all – no money is being exchanged.

Of course, that does not mean that free support is always a foolish option. On the contrary, you may very well choose to provide free support in the short term in order to help improve your plugin and build up goodwill (that’s what I do). If you do, I say bravo.

That said, if you intend to create something substantial (and profitable) out of your plugins but feel that free support is something you cannot afford to offer, that’s okay. But here’s the key point: in my opinion, if you don’t provide free support on at least bug-related issues, you must provide a premium support option.

Big name WordPress plugins such as Easy Digital Downloads do this – and it works.

As far as I am concerned, the fact that you offer the premium support in itself is all that is necessary.

No free plugin user should complain that free support isn’t available, and if they do, they should just be ignored. If they like the plugin enough, they should be willing to pay for the premium support. If they are not willing to do that, they should delete the plugin and move on.

What Do You Think?

In this post, I have presented an argument for my view that plugins (even if they are free) need to provide support. There are two big reasons for this.

First, I think that you should provide some kind of support to maintain trust with users. When people download a plugin, they reasonably hold the expectation that it will work as advertised. If it does not, that is an issue. Support can deal with the problems that pop up and thus ensure that the plugin works as promised.

Second, if you aim to one day make money from your plugin, it is a smart and practical move to provide support. If you can provide free support, great! If not, premium support is okay too – it will ensure that you keep happy the people willing to pay you money.

Regardless of your opinion on this topic, I would like to hear from you. What do you think? Do plugin developers have an obligation to provide support for their free plugins? Is offering support a savvy business move? Let me know in the comments below!

Tom Ewer

Tom Ewer is the founder of WordCandy.co. He has been a huge fan of WordPress since he first laid eyes on it, and has been writing educational and informative content for WordPress users since 2011. When he's not working, you're likely to find him outdoors somewhere – as far away from a screen as possible!


  1. Miroslav Glavic

    Plugin authors should provide support. If I want to have my website do xyz, I have so many plugins to choose from.

    Many plugin authors do crappy plugins, just the basics. Just because they are not getting paid for it.

    Your plugins are like your resume/CV.

    When your plugin has a conflict with another plugin I am using…I am going to tweet/e-mail/contact you and tell you about it.
    I don’t want to receive a “go to premium support if you want to e-mail me”.

    If I want the plugin customized then I will hire you. How can I pay you if the free plugin is not working?

    I have recommended many theme/plugin authors based out of support. I am not expecting you to call me or spend the next week e-mailing back and forth. If I wanted that then I’d go for premium or buy “hours” off you.

    If you can’t even support the code then how can I trust the code in your plugin?

    Go to the support forums and answer questions. It’s like when you buy a car, you test it first.

  2. Noumaan Yaqoob

    I think what we should keep in mind is that when a plugin author releases a free plugin, they are also depending on the community for support. For example, users reporting bugs, submitting patches, answering questions. We have seen lots of great plugins who evolved that way and became essential for many WordPress related businesses. Not only plugin authors should provide support, I feel that users should also support the plugins they use and there are many ways to do that.

    1. Tom Ewer

      Fair point Noumann — it *should* go both ways. Unfortunately, that’s not always the case.

  3. Wil Brown

    I’m in agreement with Loius. “Fixing bugs is very different than providing technical support for usage of a working plugin”

    Developers should feel obliged to fix any errors in or caused by their plugins.

    But of course there’s a muddy grey line between what your plugin is supposed to do and what the user is trying to make it do.

    There has to be a cut-off point somewhere and that should be at the developer’s discretion.

    I’m in favour of “free” plugins and premium support.

  4. mommaroodles

    If ever there was a plugin, which I felt needed more support from the author, since it has been known to have a ‘crippling’ effect on many people’s web site is the W3 Total Cache.

  5. Louis Reingold

    When was the last time you needed technical support for your iPhone?

    No user actually wants support. They want an easy-to-use product that just works.

    Support is a last resort.

    Build products that JUST WORK.

    That’s what I try to do. Doing that is really tough and that’s why I do provide support. But my main focus is on improving the usability of my products so users will never need support in the first place.

  6. Louis Reingold

    Fixing bugs is very different than providing technical support for usage of a working plugin.

    1. Tom Ewer

      I think you’re opening up a whole new can of worms there 😉

      I can see where you’re coming from, but if technical support is necessary for a user to be able to use a plugin, shouldn’t that be on offer? Otherwise what’s the point of releasing the plugin?

      The flip side to that argument would be that if only 5% of users need technical support and you don’t have the resources to offer it, it’s good for the majority of people to have the plugin out there. Having said that, I still think you should be clear in stating that technical support (beyond bug issues) is not on offer (unless perhaps they pay?).

  7. MikelPerez

    I completely agree that creating free plugins and offering free support is not a viable business model. The only way to make it profitable is to use the free plugins as an entry-point product to a commercial funnel.

    Other than that, I have to say that WordPress.org is not the most friendly environment for plugin creators to offer support. They should immediately notify you when a new thread related to your plugin is created, but right now they don’t. Only if you manually check the “support” section and subscribe to open topics are you notified. Definitely something they should change, IMO.

    1. Tom Ewer

      Hi Mikel,

      I agree entirely with your thoughts regarding WordPress.org. It’s definitely something that should be addressed sooner rather than later.



  8. Crazely

    Yeah I believe it too. Free plugins are complete waste of time, if they do not provide any kind of support. I mean what the point in developing them if you are unable to redress issues that are bugging people’s lives.

  9. ajaydsouza

    I’ve been actively supporting my plugins for several years. I monitor the forums almost daily and help out users where I can.
    Support has always been free till date with few users offering a donation in order to receive support via email.

    That being said, I agree completely it isn’t a sustainable business model, but I have built a decent user base currently and believe it’s time to move to a better support plan, i.e. premium support if users really want it and ideally premium plugins. Of course, I don’t think I’ll ever give up on free support, but it’s always going to be at my time and convenience.

    1. Tom Ewer

      You sir are a model of how to support free plugins :-)

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>