2 min read

Out-of-the-box versus build your own

By Dave Francis on Oct 9, 2020 9:38:03 AM

Topics: kinodb

You need a new application - perhaps to replace a legacy or unsupported system, or to meet a new business opportunity.  Do you look for an existing system which is the best fit, or have something built, either by a third party, or in-house?

Let’s explore the procure something option first.

If you are part of the project team, maybe the solutions architect or the systems analyst, you will first need to understand the business requirements.  In fact, regardless of the selected solution, you will always have to start here.

After understanding the business problem and documenting functional and non-functional requirements, the next item on the to-do list is to research the market to see what out-of-the-box solutions exist.

If you have a commodity requirement that is met by a standard package, that's great, but if not, this is where the challenges start.  Any pre-built application will require a certain amount of configuration (to meet your business process), or worse (because it will cost more and will become more difficult to support when the application needs an upgrade), customisation.

This is where the proverbial square peg and round hole make an appearance.  To keep costs down, your strategy may dictate that you adopt the “vanilla” application with a little configuration.  But this may require your business process to be modified to fit the design of the IT system, which is far from ideal.

So, you procure the best possible fit; then a new challenge arises.

Some time has passed since the initial request and inevitably the requirements have now changed.  In a worst-case scenario, the solution is no longer fit for purpose.  In a best-case scenario it can be modified with some further configuration (hopefully avoiding the dreaded customisation).  But you cannot be certain that costs will not go up.

If this sounds familiar, then fortunately there is an alternative option.

With kinodb, the low-code platform from datb, not only can you get the application you need, but you can also future-proof your application.

A kinodb application can be built in weeks.  The same functional and non-functional requirements that you gathered for your out-of-the-box solution remain valid and these will form the basis for the development project.

A proof-of-concept covering core requirements can be delivered in days to validate the solution, after which a series of iterations will refine functionality and deliver the solution to match your business process.

With kinodb, you’ll get exactly the application that you need as your product is custom to your business.  It will have exactly the functionality that you specified, it will do exactly what you need it to, and it can be changed as requirements change over years to come.

As kinodb applications are defined in metadata rather than as code, they don't go out of date.  We constantly update the platform to ensure that it supports the latest IT services (databases, hosting, browsers, etc.) so that applications continue to work seamlessly; we have customers using systems that were built 16 years ago!  These applications are still running on the latest browsers, databases and devices, including mobile devices that didn't exist when the applications were written.  This is the opposite of legacy software.

kinodb delivers applications that complement your business process, rather than change it.  They can be delivered faster than a “vanilla” application can be configured, and will always work.  They may cost significantly less, too.

The “alternative option” can deliver a far better outcome for your business.

Dave Francis

Written by Dave Francis