Vertical CRM software or customise?


Share on LinkedIn

Photograph courtesy of atomicjeep

As new generations of CRM system have become ever more flexible the potential to rapidly customise software to meet needs that may be far removed from the vanilla package has increased dramatically. This has created a dilemma for many potential purchasers of CRM as to whether it’s better to go with a vertical solution, already adapted to their specific industry needs, or customise a ‘best of breed’ general application.

While there are reasons why customising a mainstream application may be a good option – vertical solutions, while strong in industry specific functionality, often lack flexibility and breadth of functionality – It’s rarely a straightforward decision. Here are some of the things to bear in mind:

Does the vertical solution really fit your needs? While there may be a vertical solution available for your industry it may not fit your actual business model or support your core requirements. Just because you are in the widget industry doesn’t mean the objectives for your project will be met by a widget industry specific CRM application.

What are the trade offs? Vertical solutions tend to meet a specific set of needs well, but are often weaker in terms of general functionality. Being as clear about what capabilities are not available is as important as those that are.

How long would it take me to customise a mainstream package? This is a critical consideration. If a mainstream package can quickly be customised to accommodate the industry specific elements then this is likely to be the better option. I can think of a lot of industry specific solutions which are different more in name than substance. On the other hand there are solutions out there that could take man years of work to emulate. Being able to tell the difference is key to making the right decision.

What else does the vertical vendor offer? A vertical vendor may offer a lot more than just the software. Expertise on industry best practices and benchmarks for example may be of considerably more value than the software itself, and these probably won’t be available through a mainstream supplier.

Is your mainstream vendor able to deliver? Successfully customising a generic CRM application to your specific needs demands a set of skills many vendor don’t have. It requires excellent requirements definition capabilities as well as the ability to deliver quality code into testing. Get these wrong and you can be bogged down in rounds and rounds of testing and changes before you get it right.

Are you ready for a ‘development’ project? The demands of a development project are significantly higher then when you are implementing largely ‘out of the box’. The resources – internal and external – the timelines, the complexity and associated risks, are much higher if you choose to extensively customise a package.

The flexibility of mainstream CRM software offerings has enabled them to encroach heavily on many vertical markets. The ability to rapidly customise systems has meant that users have been able to benefit from the functional richness of the mainstream offerings while satisfactorily addressing their industry specific needs. These decisions need to be made with care however. It’s easy to underestimate how complex development projects can prove to be and it’s easy to get mired in an implementation that overruns or fails to deliver the original vision. Boringly, perhaps, these risks are generally best addressed through effective planning and requirements gathering, and (forgive me mentioning it) independent CRM advice if you need it.

Republished with author's permission from original post.


Please use comments to add value to the discussion. Maximum one link to an educational blog post or article. We will NOT PUBLISH brief comments like "good post," comments that mainly promote links, or comments with links to companies, products, or services.

Please enter your comment!
Please enter your name here