As far as I am concerned, having a website without having a CRM/sales system behind it is like having a shopfront with no shop. People can view your products, but they can’t offload their hard earned cash. Why do that to yourself?

Unfortunately it seems that companies need to literally see people banging on the store door (via hits, emails, phone calls etc.) before they will open the store. How many customers have you missed in that time? You’re paying for the store location, so why not fit it out inside?

Salesforce announced at Dreamforce that they are taking this view to another level. Your website should be linked into the core of your company. Every process your company runs should be accessible (and deliver value) to the customer at all times. Zdnet give it good coverage, but I think Smoothspan explains it best. The basic premise is know your customers, and then deliver the best experience you can to them. CRM’s have always tried to get close, but it requires a company to be completely online and committed.

I have now been working with CRM systems for 5 years. It is only recently that I have seen the industry  (finally) mature to a stage where it is no longer engaged in a straight up feature war. This has been driven by two things; a maturity of product offerings and a recognition by customers that they should be making decisions based on an analysis of their own requirements, rather than a feature comparison matrix. To this end, here are my top 5 criteria for selecting a CRM system:

Usability - Without this, nothing else matters. If your users will not adopt and use your selection, it’s a waste of time and effort.

Alignment - What do you want to do with your CRM system? If you are looking to manage contacts & contact activity, you’d consider a completely different slate of products than you would if you were looking to customize a product to support your entire business process.

Product delivery - SaaS vs. client/server is a big consideration. Do you need an offline client, or is a plugin enough? If so, how robust does it need to be? This could direct you toward a client/server solution. Do you have an IT department and any in-house expertise? If not, could direct you toward a SaaS product.

Integration needs - While it is easier than ever to integrate SaaS products with other systems, some scenarios definitely call for an on-premise solution. This could be a limitation of your current software packages that you rely on but have no interface into.

Pricing - Do you have capital up-front? Do you want to buy your solution? If not, SaaS products are much easier to get started with. In some cases though, they can end up costing more in the long run. There is also a great price difference in different SaaS products and even within themselves based on functionality.