There is a lot of terminology in the software market which can be confusing for non-technical people. The difference between custom, configured and out-of-the-box often trips up decision makers and makes it unclear as to what exactly is the best-fit for their organisation.
What is Custom ?
A custom solution is built according to unique needs, specifications and preferences by creating an application from the ground up while using Nimblex Configuration or out-of-the-box functionality. This option is chosen when an organisation has specific, non-standard processes and business requirements that need to be catered for individually as they don’t fit into the current range of Nimblex Core Solutions (e.g. Procurement-, Contract-, Risk-, Safety Management, etc.)
Custom Features and Functions
When we refer to a custom feature, we are referring to an add-on function that must be developed using code if it can’t be configured using the tools and capabilities already native to the Nimblex software package.
What is Out-of-the-Box?
Out-of-the-box (OOTB) solutions are also referred to as commercial-off-the-shelf (COTS) solutions. They get shipped as-is and require little or no configuration. OOTB software comes with predesigned, pre-packaged templates, forms, workflows, etc. already in place that are common to most users.
The software set-up and functionality are almost complete at the time of purchase; it is “ready-made” for the required purposes and can be up and going in a short time.
Our Nimblex Core Solutions fit this definition and can be set-up with fewer than 30 hours of configuration. In contrast to traditional OOTB or COTS products, Nimblex’s flexibility helps to future-proof your Nimblex solution because it can always be configured to shape around future requirements.
Out-of-the-Box Features and Functions
OOTB or COTS functionality refers to the native system properties, features and components that can be configured to turn your ideal functional requirements into a solid and best-fit solution.
A Weapon for Cybersecurity.
What is Configured?
How does it differ from Custom?
Configured functionality refers to native or out-of-the-box system properties, features and components that can be set to turn your ideal functional requirements into a robust and best-fit solution. “Customised functionality” can be referred to as the creation of new functionality using code whereas “configured” refers to changing settings and preferences of standard functionality to suit your needs.
Configured Features and Functions
Nimblex offers unprecedented configuration capabilities to adapt Nimblex Core Solutions for a specific purpose using native tools that come packaged with the Nimblex Platform.
There is no need to write code to make the changes. We are configuring the features that are already there in Nimblex to behave and look like you need them to.
The more complex your requirements or the more unique your business processes are, the more likely it is that an OOTB solution won’t fit the bill 100%. For example, a Nimblex solution may fit your need by 60% but can then easily be configured to fit your specific solution requirements a full 100%.
You would opt for a Nimblex Custom Solution if you:
- Can’t find what you are looking for within the OOTB or COTS offerings in the market.
- Have specific, non-standard processes and unique user stories, reporting and business requirements.
- Have budget and time constraints which don’t allow you to take the traditional code writing option for solution development.
A Nimblex Core Solution if:
- Your organisation’s requirements and business processes are mostly based on industry standards.
- Your budget doesn’t stretch to customisation.
- You are working within a time constraint.
The difference with Nimblex is our flexibility to configure any solution you want to best fit your needs, making it future-proof and highly functional without breaking the budget. Meanwhile, you experience a shorter delivery lead time and lower risk compared to more traditional software options.
Nimblex has increased and improved our efficiency by more than 40% and we are much better organised as a department.Aven Eddington
Principal OHS Consultant
Frankston City Council
A powerful solution without the traditional price tag.
|Implementation time||4 – 8 weeks||3 – 9 months||6 – 24 months|
|Flexibility of process automation and workflows||Configurable||Highly configurable||Limited to best practises|
|Features||OOTB set of features (can add)||Large library of features to choose from||Limited to best practises|
|Self-maintenance||Client can configure eForms, workflows, reports, etc.||Client can configure eForms, workflows, reports, etc.||Limited to administrative tasks|
|Integration||Advanced capability||Advanced capability||Limited capability|
|Life span of solution||Long: Low-code flexibility||Long: Low-code flexibility||Medium. Fixed code|
|Custom branding||Client’s branding||Client’s branding||No branding|