In a previous post, we explored some questions you can use to evaluate open-source content-management systems for your business or nonprofit organization's website. One of the least considered factors that (should) impact decision-making is the amount of ongoing expense required to  support your open source CMS. Yes, I know what you are thinking ...

Doesn't Open Source Mean Free?

Well, yes. Sort of. While the software is free, there is ongoing maintenance and support needed which is (of course) NOT free.  Ongoing maintenance and support is especially important when you use a robust platform that gives you (or others on your team) the power to DESTROY your website! What happens when a mistake is made and most of your web site goes away? Who will retrieve it? And how quickly is that support available? You will absolutely need to have a firm experienced in your chosen CMS on contract to provide this support, or you will be in very serious condition if you have an emergency. And, of course, having support service contracted should be done before you begin the installation process. (You certainly don't want to be in the position of finding help AFTER a catastrophe has occurred.)

How Much Money Should You Budget for Supporting Your Open-Source CMS?

Maintaining open-source software varies greatly according to how extensively the software has been modified, how many community modules are applied, and the number of core system updates that are released. This is the baseline, and of course, does not account for providing training or phone support.

There are two great ways you can scope out what ongoing support might cost you:

(1) Search online. There are numerous online resources dedicated to the topic of supporting open-source CMSs. (Be sure to seek out details on the specific CMS you are considering as support models can vary accordingly.) There are also quite a few articles and posts focused around budgeting for this support. Here is one example I found of how you could estimate your open-source-CMS-support expenditure down to a weekly basis. The post was drawn based on updates needed in 2010, and averaged 7.25 hours per week. Multiply that by your IT professional's hourly rates, and you'll have an idea of how much you'll need to budget on the low end.

(2) Talk to local pros.  Most likely you will want to work with a local firm, with whom you can meet in-person as needed. By interviewing several potential providers, you will have the opportunity to explore varying support options. In addition, you'll be able to get multiple perspectives on the type and scope of support needed (based on the platform you choose and level of customization you desire). Do the firms you meet with offer packaged monthly services? Do they provide hourly support on an as-needed basis? What is the guaranteed response time, and will you be charged a premium for same-day service/priority support? All of these details will figure into your support budget.

Maintenance for open-source content-management systems is an ongoing expense which must be accounted for. Don't overlook this critical component of successfully managing and implementing a content-management system.