Turn modular software components into revenue streams with the power of MACH

Software is usually broadly divided into “Commercial Off the Shelf” or packaged software, ranging from consumer-oriented products to big, customisable, enterprise software suites – or one-off software, typically developed for internal use.

With the approach to development and use of software championed by MACH, the lines are a bit different. MACH can likely end up creating a number of modular, reusable, and generally very adaptable components. This is where MACH has its most significant value: providing software that fits a given business and can be updated, improved, or modified easily when needed.

But it turns out that those components, or even a combination of components, can also have monetary value. Most of the time, unless all of them are combined, they will not be able to function in a freestanding manner, and as mere components, making them available to others is not the same thing as sharing an entire customisable system would. In other words, making components available doesn’t put anything proprietary at risk. It just provides another potential revenue stream to offset the cost of creating that software.

When code is productised, it will often have characteristics like being simple, intuitive and easy to install and configure. And, of course, built on the standards championed by MACH.

The lifecycle of this code, whether used internally or shared elsewhere, should maintain a disciplined approach. When code goes to the external world, it may be simplest to cede control. But when it is used or reused internally, MACH principles should be maintained.

The temptation is always to make “one little change” for a given purpose, which can quickly turn into many changes. But when maintenance or some broad update is needed, having multiple versions is a problem. The better approach is to recognise that new or different functionality may need to be incorporated into a given “product” so that it can perform multiple roles. But all versions stay the same, simplifying operations in the future.

It’s the long-term MACH approach to software with long-term benefits.