How to choose a process automation platform, and what to check in the licence

Process automation platforms are bought for years and built on for longer. Once your processes run on one, moving is a project in its own right. That makes the selection unusually important, and unusually easy to get wrong, because demonstrations show the simple path and price lists show the first year. This guide covers what to evaluate, how these platforms are licensed, what to scrutinise in the contract, and how to run a selection that produces evidence rather than impressions. If you are still deciding what kind of automation you need, start with our guide to RPA, process orchestration and low code.

What should you evaluate in a process automation platform?

• Process complexity. Can it run your longest, most exception heavy process end to end, with parallel paths, deadlines and escalations, not just a straight line approval?
• Case management. Can it handle work that does not follow a fixed path, where the next step depends on what has happened, and keep everything about one case together?
• People in the loop. How well does it route work to people, manage queues and workloads, and let a person review, override or approve what software has done?
• Audit and compliance. Does it record every decision, by person, rule, bot or AI, in a way an auditor or regulator would accept?
• Integration. How does it connect to your core systems: standard interfaces and APIs first, with bots as a fallback rather than the plan?
• AI and agent governance. Can you control which AI models and agents are used, what they can do and see, and keep a record of their actions? Can you bring your own model, or are you tied to the vendor’s?
• Deployment and data residency. Cloud, private cloud or on premises, and where your data and any AI processing physically sit. Our guide to UK AI data residency covers the AI side.
• Skills and delivery. Who will build on it: business teams, a central team, or a delivery partner? How available are the skills, and how steep is the learning curve?
• Total cost. Licences over the full term, environments, infrastructure, delivery, support and the cost of the people who will run it.

How are process automation platforms licensed?

There is no standard model, and most contracts combine several. The common ones are:

• Per user. Named or active users, sometimes split into builders, workers and occasional or external users at different prices.
• Per application or process. A price for each application or process in production, regardless of how many people use it.
• Per bot or digital worker. Common for RPA, often split between attended and unattended bots and the orchestration that runs them.
• Capacity or consumption. Transactions, cases, documents processed, compute or AI usage, increasingly common as AI features arrive.
• Platform tiers and editions. A base platform with higher tiers unlocking capabilities such as process mining, document processing, advanced AI or extra environments.

Each model rewards a different pattern of use. Per user pricing suits a small number of heavy users and punishes wide, light use. Per application pricing suits a few large processes and punishes many small ones. Consumption pricing suits uneven volumes and makes budgeting harder. The right model is the one that fits how your use will grow, which is why it is worth modelling year three before you sign year one.

What should you scrutinise in the contract?

1. How cost grows with success. Model the cost if automation works and use doubles. A good first year price on the wrong model becomes an expensive platform.
2. True ups. How usage is measured, when it is counted and what happens when you exceed your entitlement.
3. Minimum commitments and term. What you commit to regardless of use, for how long, and whether you can reduce it.
4. Environments. How many development, test and production environments are included, and what more cost.
5. AI features. Whether AI capabilities are included, charged per use, or need a higher tier, and how that is likely to change.
6. Renewal uplifts and price protection. The cap on increases at renewal, and whether discounts survive it.
7. Exit and data. How you get your process definitions and data out, in what format, and with what help.

These are the clauses where the long term cost is decided, and where there is usually room to move if you know where to look. We spent decades on the vendor side of enterprise technology building deals like these, so we know how the licences are put together and which terms a vendor will actually move on. Talk to us before you sign.

How do you run a selection that produces evidence?

1. Pick two or three real processes. Include your most complex one. These become the test for every platform.
2. Write a short, process led RFP. Describe the processes and outcomes, ask each vendor to show how they would run them, and require pricing in a consistent format over the full term, including environments, AI and support. Long feature checklists reward the longest list, not the best fit.
3. Shortlist two, then run a proof of value. A time boxed build of one real process on each shortlisted platform, with your data and systems, measured against criteria agreed in advance: build effort, how exceptions are handled, audit, integration and how your people get on with it.
4. Negotiate with the evidence. A proof of value on two platforms is the strongest commercial position you will have. Use it before you choose, not after.
5. Plan the operating model. Decide who owns the platform, the standards, the backlog of processes and the measurement of value before the first process goes live. Our business case guide covers how to measure value honestly.

Choosing or renewing an automation platform?

Tell us about the processes you want to automate and where you are in the decision. We will give you an independent view of what to evaluate, how to structure the selection, and what to watch for in the licence, with no platform of our own to push.

1. Tell us where you are. The processes in scope, the platforms you are considering or already own, and your timeline.
2. We structure the selection. A process led evaluation, a proof of value on your own work, and a like for like view of the full term cost.
3. We negotiate and help you deliver. We negotiate the licence terms that decide the long term cost, then work alongside the platform vendor and delivery teams through to go live.

Name *

Company *

Work email *

Phone (optional)

Details

Talk through our selection

Prefer email? Reach us directly at hello@c4cgroup.co.uk.

Frequently asked questions