Mini CMS, Web CMS, Web Content Management

Caribou CMS 2.1 Improves Licensing for Multiple Subscriptions

Caribou CMS is now in v2.1. The main change from the previous release is in regards to the way the CMS vendor is now handling multiple licenses, as well as some new features.

In the past, you couldn’t have users with multiple active subscriptions to the same Caribou CMS package. Meaning that, every time you would want to buy a second license, it would be treated as an extension of the existing subscription and of the license you bought previously. But that is now history. Users now are free to have multiple license subscriptions at US$ 29 per month.

E-xact payment gateway integration is a brand new feature and allows subscribers to add E-xact eCommerce functions to their accounts. Caribou CMS includes a variety of other third-party payment gateway integrations as well, including PayPal.

More on CMSWire: Caribou CMS 2.1 Improves Licensing Model

cms, Enterprise CMS, Enterprise Content Management, Web CMS, Web Content Management

Implementing a CMS Costs More Than Buying a CMS

A recent report entitled “CMS Survey Report 2009 by and didn’t really shock me. It was a “Doh!” moment, really.

Why CMS Licensing Costs Are Only The Beginning

Perhaps, it is not always the case, but buying a CMS is only the beginning of your investment. You think that after spending all that time and money during the CMS selection process and sales demos, you’re done? Far from it.

Often, it costs a lot more to actually implement the damn thing and make it useful to the organization.Think of all the implementation work: from defining (the often, non-existent and ever-changing) business requirements and translating them into the CMS-of-your-choice language to building out your numerous websites, templating, programming, security and governance models, workflows, etc. I am being very simplistic in describing the scope here. Am not even gonna talk about ECM scenarios.

Add to that training, support, maintenance, customizations, add-ons, integrations with third-party tools, more training, content migrations, testing, QA, deployments. I could keep going.

Organizational change that comes with implementing every new solution may cost you another dime or two.

There is nothing more difficult to carry out, nor more doubtful of success, nor more dangerous to handle, than to initiate a new order of things.

//Unknown Niccolo Machiavelli

Half-a-million or so implementation dollars later, the end-users cannot stand the CMS and refuse to use it. In fact, they hate it (see the 18% number below).

Pains of Implementing a CMS

Right, back to the report. There are some interesting findings in the survey. The report is based on an online survey of more than 800 respondents (decent size sample) dating back to March and April 2009.

Highlights include:

  • A bit over 25% of companies surveyed use their CMS primarily for publishing
  • 53% are spending less than £5,000 on their CMS license annually
  • 18% of respondents rate their CMS as ‘excellent’ for ease of use
  • 60% use commercial CMS vendors
  • 31% use either open source CMS (24%) or ‘supported open source’ (7%)
  • The difficulty in using a CMS is deemed to be the biggest reason for an unsuccessful CMS implementation

On Selecting a CMS

  • 49% consider ease of use as the most important factor in selecting a CMS
  • Cost is deemed to be a priority factor for 37%
  • SEO friendliness is important to 30% when selecting a CMS
  • Ease of integration with other parts of the business and configurability with workflows is a more significant factor for larger companies than for smaller organisations when selecting a CMS
  • 75% believe that personalisation is important for a web content management strategy
  • 61% vote for blogging as being important (with social networking at 48%, viral marketing at 32%, micro-blogging at 27%)

The lack of support for Web 2.0 is thought to be the most negative aspect of current content management systems, with nearly half of organisations (47%) surveyed regarding this as a “downside” of their CMS.

I realize some of the numbers above may look slightly funny, but you get the idea.

For those of you in the midst of a CMS, WCM, ECM implementation, I’d recommend checking out AIIM’s preso How to implement ECM?