Bespoke or off-the-shelf software for your factory?

The choice between off-the-shelf and bespoke software starts with your production process, not a software package. Which functions are already well covered? Where does your machinery need specific integration? And will you still be able to access your own data? For factories and machine builders, these questions often matter more than the initial licence fee.

At Vlegel Technology in Genk, the software engineering team for machines, data and AI, we look at the whole chain: from machine signal to application. Off-the-shelf where it fits, bespoke where it is needed. A hybrid approach is an option, not a goal in itself.

Off-the-shelf software: useful when the basics fit

Off-the-shelf software can be a sensible choice for functions such as stock management, reporting or user management. There is no need to develop them from scratch. The supplier usually handles product updates and support, while development costs are spread across multiple users.

But available does not mean integrated. Check whether the package supports your process without cumbersome workarounds. Look into its API, export options, licence terms and connections to MES or ERP too. A dashboard is worth little if the underlying data is hard to access.

Bespoke software: focused on what really differs

Bespoke software makes sense when specific process logic, machine integration or data processing does not fit an existing product well. For example, you can define how machine statuses map to production states, or how a digital checklist fits into a workflow.

That freedom comes with responsibility. Development, testing, documentation, security and maintenance all need ongoing management. Bespoke software is not automatically scalable or free from lock-in: without transferable code and clear agreements, you can just as easily become dependent on a single development partner. Nor is off-the-shelf software inherently less secure; access control, updates and configuration matter just as much in both cases.

Foresco: a hybrid approach in practice

Foresco, an industrial company in the timber sector based in Genk, initially chose off-the-shelf software for energy monitoring. After implementation, the data proved hard to access and integration with other systems was difficult. That limited the scope for further development.

Vlegel then developed a hybrid solution: 80% based on a flexible low-code framework, complemented by 20% bespoke development. The system combines energy monitoring with OEE measurements and digital checklists. That split describes this application, not a fixed formula for every project.

The lesson is not that hybrid is always better. It is about which components you can reuse and where bespoke development is needed. A low-code platform also needs assessing for data access, extensibility, licensing and the option to switch later.

Be explicit about integration and data

Before choosing a package, map out which machines and systems supply and use data. OPC UA can provide access to machine data; MQTT can publish and distribute messages. Check what your equipment actually supports. A protocol alone does not resolve differences in meaning, timestamps or data quality.

A Unified Namespace (UNS) can help make data available in a shared, recognisable structure. Agree on naming conventions for machines, lines, statuses and measured values. That way, each application does not need its own interpretation and separate connections. A UNS does not replace historical data storage, access control or management agreements.

If you want to use AI for analysis or support later, that consistent data foundation matters. Keep the boundary clear: AI only reads and makes suggestions; a person reviews and decides. Do not give an analysis application write access to machine controls.

Decide based on the full lifecycle

Compare not just purchase and development costs, but also integration, licensing, maintenance, updates and migration. Ask for demonstrations of critical connections and data exports before you choose. Document who is responsible for faults and changes. Choose off-the-shelf when it fits the process well, bespoke when essential requirements are missing, and hybrid when that split remains technically manageable.

Not sure which approach suits your factory or machine? Let's talk it through for 15 minutes. We will discuss your existing systems, the data you need and where off-the-shelf software stops being a good fit.