Bespoke systems · JNAGA perspective
What is the hidden cost of a bespoke system?
Bespoke software can be valuable precisely because it fits important work. That fit has to be kept alive as the business changes.
Published 25 September 2026
Imagine a tailored workflow launches successfully. A year later, a supplier changes an interface and the business adds a new approval role.
The original build price says little about these changes. The business needs a maintenance owner, documentation, testing and a route for deciding which requests are worth implementing.
Look beyond the invoice for the build
Someone must manage access, data quality, incidents, backups, integrations and user questions. Changes in regulation, products, staff or customer needs may alter the system's fit. These are operating responsibilities, even when the code itself is stable.
A cheap first version can be expensive if nobody understands its dependencies. Equally, an elaborate build may create more flexibility than the organisation can use. The right size follows the importance of the workflow.
Keep the ability to change partner
Agree how the business will retain access to its data, documentation and source where appropriate. Clarify who can make changes and how another competent team could take over. This is not an argument against a trusted supplier; it is part of making the service durable.
Plan for safe updates and a way to test them before affecting live work. A small system still deserves a recoverable path when something goes wrong.
Include an eventual exit
A useful system may one day be consolidated, replaced or retired. Understand what records and processes would need to move. Considering that exit at the outset often leads to cleaner boundaries and less unnecessary dependence.