What a Licence Costs

Licence cost looks like the simplest line in an automation budget and behaves like the least predictable. The headline figure is knowable; what it becomes in year three depends on a pricing model whose behaviour under growth is rarely examined.

Reviewed August 9, 2026. Pricing models change frequently; verify against current terms. A product-side example of how workforce software approaches this topic is available in this practical guide.

The four models

Per bot or per runtime. You pay for concurrent execution capacity. Predictable, and it punishes breadth — ten small automations may need more capacity than one large one, so the cost per process is worst exactly where small automations accumulate. For broader background and an independent point of comparison, see GitHub Automation.

Per user or per developer. You pay for who builds and manages. Cheap while one person does it, and it becomes a barrier to the thing you eventually want, which is more people able to maintain automations.

Consumption or per transaction. You pay for volume processed. Aligns cost with use, which is attractive, and it means success increases your bill — a process that grows 40% costs 40% more, and the saving does not necessarily grow with it.

And platform or tiered subscription. A bundle with limits. Predictable until you cross a threshold, at which point the step is usually large.

Every model punishes something. Knowing which thing matters more than the headline rate.

The questions that reveal year three

What happens if volume doubles? Under consumption pricing this doubles a cost line; under per-runtime it may cost nothing until a capacity threshold.

What happens if we build five more automations? The scaling question, and the one most affected by model choice.

What happens if a second person needs to maintain it? Under per-developer pricing this is a purchase, which quietly discourages the redundancy that prevents a single point of failure.

What is the renewal uplift? Ask for it in writing. An introductory rate with an unstated renewal is the oldest arrangement in software.

And what happens if we use it less? Some models allow scaling down and some do not, which matters when an automation is turned off.

What is outside the licence

Consistently, and it belongs in the total cost.

Support tiers. The included level is frequently a queue. Response times you can rely on are a separate line, and the difference is material for something running unattended.

Environments. Development and test may be chargeable, and building without a test environment is a false economy that shows up as production incidents.

Connectors. Some integrations are included and some are premium, and which ones is discovered during implementation rather than during evaluation.

And professional services. The build is usually separate from the platform, sometimes from a partner rather than the vendor, at a different rate.

Making it comparable

Two suppliers with different models cannot be compared on headline price.

Model your own three-year scenario. Current volume, expected growth, number of automations, number of maintainers. Ask each vendor to price that scenario rather than a generic one.

Ask for the year-three figure in writing, including renewal uplift.

And ask what their existing clients' costs did between year one and year three. They know, and the answer is more informative than the quote.

The trap in cheap entry

A low first-year price with an aggressive renewal is a common structure and it is not always a bad deal — it can be a reasonable way to reduce your risk on an unproven project.

It becomes a problem when the switching cost has grown in the meantime, which it does with every automation built on the platform. By year three the automations are the lock-in, not the contract.

Which is an argument for keeping the logic documented in prose independently of the platform — so that if you do move, you are rebuilding from a specification rather than from an implementation nobody can read.

The short version

• Four models — per runtime, per user, consumption, tiered — and each punishes something different
• Per runtime punishes breadth, per user punishes redundancy in maintainers, consumption means success increases the bill
• Ask what happens if volume doubles, if you build five more, if a second maintainer is needed, what the renewal uplift is, and whether you can scale down
• Outside the licence: support tiers, environments, premium connectors, and professional services
• Model your own three-year scenario and make each vendor price that rather than a generic one
• Cheap entry with aggressive renewal is common; by year three the automations themselves are the lock-in