Configurable vs. Customizable: The Difference in Software and Why It Takes Months Off ERM Implementation

The last time you implemented a new software solution for your business, did it feel like the IT implementation team put down roots in your office? You were likely experiencing the impact of software customization. You don't have to suffer through lengthy ERM implementation.

Customization has long been the enemy of speed in software implementation. Across industries and enterprises – from ERPs to CRMs to ERM-GRC – software companies promise truly customized solutions and then send implementation teams to make it all happen – sometimes over the course of months or years before the project is complete.

One small shift in the mindset – from customization to configuration – can make all of the difference and shave months off of the implementation time for ERM-GRC software.

What is the difference between configurable and customizable?

Take a moment and consider the differences in the definitions of these two terms:

1. Customization - to modify or build according to individual or personal specifications or preference.
2. Configuration - the way a software program is set up for a particular task; the specific settings for a program.

By definition, configuration is “setting up” or selecting the appropriate settings to meet your business needs and objectives. Customization is “building” or “modifying.” It’s like the difference between assembling your TV in the living room from all of the necessary parts vs. mounting it on the wall, turning it on and telling it what streaming services you’re using and what channels you like.

Customization is like buying furniture at IKEA – assembly required. That assembly will lead companies to hire fleets of technical experts who will ensure that their software meets the exact specifications of their current workflows and processes. Unfortunately, that leads to months and months of implementation time.

What if ERM implementation could be achieved in days or weeks?

This is where sourcing a highly configurable piece of software makes the difference. You may assume that you need customization to meet your business objectives. That is a myth. Instead, a highly configurable software solution can achieve the same result.

Simply being configurable may not be enough to meet your business workflows. That’s why it’s important to ask questions about the options within the software you’re reviewing. What does it do out of the box? And what configuration choices can you make about how it works? 

When the software developer has the depth of knowledge necessary to anticipate your business’ needs, a configurable solution can achieve the same results as a customized software. The key is expertise and imagination. The developer must determine which elements a user might need or want to customize and then give users the tools to set those preferences.

 We built Procipient^® with configuration in mind

When we meet with potential customers, one of the first things they want to know is about the implementation timeline. When we share with them that implementation for Procipient^® ranges from hours to a few weeks, many can’t believe it.

Configuration is what makes it possible. When they select our software platform, they have what they need to align with their business objectives. The implementation is a series of clicks and choices configuring the product – not hours of writing complicated code to customize it.

We can achieve our customers’ goals through configuration, and we achieved the depth of configuration needed to meet a wide variety of customer specifications through:

1. A bias toward configuration.We’re not interested in racking up hours and fees dragging out implementation. We want our customers to be up and running and realizing the ROI on their software as soon as possible.

2. Vast knowledge of GRC and ERM best practices.We truly understand the requirements for risk management and governance. We cut our teeth in the highly regulated financial sector with banks and credit unions. We have also provided solutions for manufacturers, utilities, insurance companies, food companies and even testing and certification firms.

3. Customer input and feedback.We value the feedback we’ve received from customers over the last 20 years and put it into use for our ERM-GRC software. We listen, and our software reflects customer needs.

4. Experience with competitor software. Every time we found a non-configurable roadblock in a competitor’s software, we took it as an opportunity to give users a choice. They could select which process or method will work best for them.

Contact Us

If you're interested in an ERM solution with a smooth and fast implementation, contact our team to get a demo. See how the difference between customization and configuration can change your ERM implementation timeline.