top of page

Embracing Flexible Automation Subscription Models for Greater ROI


Public-sector healthcare has made significant strides in digital transformation and the adoption of new technologies, including Artificial Intelligence (AI) and Intelligent Automation. These advanced tools have been employed with some success to streamline operations and improve patient care.

However, the growing concern of excess bot capacity within the NHS has been increasingly attributed to long-term, inflexible subscription models and wastes precious funding which could be targeted towards reducing waiting lists, elective recovery and patient care.

This article will discuss how embracing a 'consume-as-you-go' model can alleviate this issue, increasing ease of access to technology and contributing to a faster and larger return on investment (ROI).

The Problem

Excess Bot Capacity and Inflexible Subscription Models

The adoption of intelligent automation and robotic process automation in the NHS has aimed to improve patient experience, reduce administrative workload, and optimise resource allocation. However, the long-term, inflexible subscription models currently in place can lead to excess bot capacity. This overcapacity results in the NHS paying for unused resources, ultimately wasting financial resources that could be better allocated elsewhere but as they have been purchased in silos and restricted contractual terms over many years, there is no advantage to vendors in supporting their efficient use.

The solution seems to be ICS level automation programmes but in reality this means multiple bot instances across the ICS that are unable to talk to one another or share excess capacity. It offers no benefit at all.

Inflexible subscription models can also hinder the adoption of new technologies, as healthcare organisations may be reluctant to invest in additional subscriptions if they are unable to adapt or scale their current offerings. This could delay the implementation of cutting-edge solutions that could further optimise patient care and operational efficiency.

The Solution

Consume-as-You-Go Subscription Models

A consume-as-you-go subscription model could revolutionise the way the NHS accesses and utilises automation technology. This flexible model allows healthcare organisations to pay only for the resources they actually consume, rather than locking them into long-term, inflexible contracts.

This approach offers several key benefits:

  1. Cost Efficiency: By only paying for the resources consumed, the NHS can optimise its spending on automation technologies and ensure that investments are used effectively.

  2. Scalability: A consume-as-you-go model enables the NHS to scale resources up or down based on demand, ensuring that they can adapt to changing needs and avoid excess capacity.

  3. Ease of Access: With a flexible subscription model, the NHS can more easily adopt new technologies and innovations without the fear of being locked into long-term commitments or overpaying for unused resources.

  4. Enhanced Innovation: The ability to quickly and easily access new technology enables the NHS to stay at the forefront of digital healthcare and continuously improve patient care and operational efficiency.

  5. Faster ROI: A consume-as-you-go model can lead to a faster and larger ROI, as the NHS can immediately capitalise on the benefits of automation without being burdened by long-term contracts or excess capacity. There are many examples of an ROI in year 2 but automation should be delivering ROI in the first six months.


Excess bot capacity in the NHS is a growing concern that can be directly attributed to long-term, inflexible subscription models. It is only a matter of time until the recent waves of national funding are asked to publish the benefits of recent investments and its likely to be left wanting.

Could there be a better way of enabling automation technology across the NHS that promotes the responsible use of public funds?

There is... I'm building it and it's coming soon.

Watch this space!

248 views0 comments
Post: Blog2_Post
bottom of page