Packages vs Bespoke Development

Packaged application package vendors have a well-rehearsed set of arguments as to why their "commercial off-the-shelf" (COTS) approach to providing software is the best. In the world of bespoke application development there are no pervasive voices giving the other side of the argument. Here are our thoughts on why you should consider the bespoke route to satisfying your application requirements:

• » You get the software functionality that you want, implemented in the technology that fits best with your existing systems.
• » You do not have to pay for functionality you will not use.
• » You do not pay high customisation charges to add features that are missing from the package.
• » You can allow your business processes to work as now rather than fit them to the whims of the package.
• » You can build a flexible application that you will be able to extend in the future as and when it suits you rather than being forced to accept the enhancement path that is followed by the package vendor.
• » You have little influence over the direction of a package vendor - their approach will be to satisfy as many potential new customers as possible.
• » A bespoke application is an asset that can be sold, licensed and exploited if you see fit.
• » A bespoke application costs you the same no matter how many users and processors you add to it or extra transactions are processed.
• » Support arrangements for a bespoke application can be tailored to meet your needs.
• » A bespoke application will be designed to fit well with your existing applications and infrastructure reducing the effort of building and supporting new interfaces that would be required for a package installation.
• » A bespoke application will be developed in line with your application development and graphical user interface standards.
• » The scope of a bespoke application development project can be changed if needs dictate it.
• » You own the source code of an application - package vendors do sometimes drop support for a package or even go bust.
• » Training and documentation is tailored to your specific needs.
• » Unlike a package, which has to maintain backwards compatibility, a bespoke development can take advantage of new software capabilities and enhancements in technology.
• » Package vendors will often spend as little as possible after releasing a package in order to recoup the costs of developing it.
• » A package vendor may not allow you access to your data held in their database (for example for additional reporting or data warehousing requirements) due to either not publishing the data model or prohibiting access in their licence terms.