I find enterprise RPA licences create both a commercial and operational lock that typically stretches into a two- to three-year practical horizon. Vendors sell one-year minimums, auto-renew, licence-linked pricing and orchestrators; exiting requires months of redevelopment, tester and business-hours, and often paid vendor migration support.
- Enterprise RPA deals almost always create a commercial and an operational lock that outlasts the written term.
- Licence pricing split across bots, orchestration and connectors turns an annual fee into ongoing vendor-managed costs.
- For 10–200 person companies, SaaS connectors plus a consultant or a fixed-scope build usually reduces migration risk.
- If you must buy enterprise RPA, force a short initial term and require machine-readable exports and escrowed configuration.
- Negotiate pre-purchased migration days and staged acceptance tied to migration obligations to cap exit developer-hours.
- The true exit cost is developer and tester time to rebuild, rewire and revalidate workflows, not the licence line alone.
Signs this is happening in your business
- Your ops team opens the vendor console first to investigate routine failures instead of the business system.
- Vendors or contractors reply “that’s orchestrator behaviour” when asked why a process failed.
- Invoices list per-bot licences, orchestration fees, attended seats and rarely used connector charges.
- You postpone upstream process fixes because the automation masks the underlying problem.
- A core system change breaks several automations and you must bring in an external developer.
- New hires learn the vendor console as the operational tool rather than the primary business system.
- You dread renewal because the expected price step-up would force headcount choices.
If several of these are true at the same time, the problem is usually the process rather than the people running it.
What this is costing you a year
(Team hours per week x hourly cost of employees x 52) = annual payroll loss
- People doing this work4
- Hours each per week6
- Hourly cost of employees$45
- Weeks52
Annual payroll cost of four people spending six hours weekly on manual repetitive work.
Find the number before you spend anything
Run the formula above on your three most repetitive processes. If any of them clears a year of a salary, that is the one to bring to a call.
How long do RPA vendor contracts lock you in
For a 50-person company with a few people doing repetitive work, commercial terms and operational dependence usually extend your real decision horizon to two to three years. Vendors sell one-year minimum licences with auto-renew and centralised orchestration; moving off the platform requires months of redevelopment, testing and vendor cooperation.
- Commercial lock: one-year minimums, auto-renew and notice periods.
- Operational lock: dependence on the vendor’s orchestrator and connectors.
- Migration horizon: months of redevelopment and testing.
What typical enterprise RPA contracts look like and their renewal mechanics
Enterprise RPA contracts start with a pilot and then convert to production licences with annual minimums, automatic renewal clauses and defined notice windows. The pilot often masks the recurring costs: converting to production commonly unlocks orchestration fees, connector charges and higher licence tiers that drive the true recurring spend.
- Pilot: limited scope and temporary pricing.
- Production licence: annual minimums and feature gating.
- Auto‑renew: renews unless you give notice within the window.
- Price change: vendors routinely reserve the right to increase fees on renewal.
How licensing models create long-term financial lock‑in
Vendors split charges across unattended runs, attended seats, orchestration and premium connectors, so licence exposure grows as you automate more. Once running, cancelling a licence becomes an operational decision because you must replace both the runtime behaviour and the licences that enabled it — and that replacement carries developer and tester cost.
- Per-run licences: billed per automated instance or routine.
- Attended seats: charges for people who trigger automations.
- Orchestration fees: ongoing central control costs.
- Connector fees: vendor-only links to your other systems.
Operational lock‑in vectors you actually feel in the office
Operational lock-in shows up when your team uses the vendor console for control, when runbooks and alerts live only inside the vendor system, and when troubleshooting requires vendor know‑how. Proprietary workflow formats and vendor-only connectors mean cancelled licences still demand developer-hours to recreate the same behaviour elsewhere.
- Orchestrator dependence: vendor console becomes the control plane.
- Proprietary workflows: exported logic needs vendor tools to read.
- Vendor-only connectors: third-party systems link only through vendor glue.
- Managed hosting: vendor owns access, backups and operational runbooks.
Real exit costs and realistic timelines
Leaving an RPA vendor is a migration project: catalogue, export, rebuild, retest and run in parallel until stable. Expect timelines measured in weeks for a handful of automations and months for larger portfolios, and budget developer‑days, tester‑days, business validation hours and negotiated vendor support days.
- Export and audit: days to weeks to catalogue existing automations.
- Rebuild: developer-days per workflow depending on complexity.
- Test and validate: business owners sign off each workflow.
- Dual run: run old and new in parallel until stable.
- Vendor exit support: pre-purchased migration days reduce risk.
Lock-in starts the day your team uses the vendor console to operate the business instead of your core systems.
How that compares to SaaS connectors and hiring a dedicated automation hire
SaaS connector services provide browser-configured links priced monthly and are usually simple to move away from, though they have transaction limits and fewer governance features. Hiring an automation specialist or taking a fixed-scope consultant gives you ownership because routines, documentation and code live with you, which makes migration a personnel issue rather than a vendor negotiation.
- SaaS connectors: quick to deploy, low lock‑in, transaction limits.
- Dedicated hire: upfront salary, full ownership and portability.
- Fixed-scope consultant: one-off cost with delivered handover.
How this fails in practice, and the exact sequence you will recognise
Failure usually follows the same sequence: a pilot shows quick wins, demand expands faster than governance, licence tiers and connectors are purchased, and later a price increase or a core system change breaks automations. The vendor bills for professional services and the organisation discovers the exit work only when it tries to leave.
- Pilot deployed to show quick wins.
- Business teams request more automations.
- Connector and orchestration purchases accelerate costs.
- Core system change breaks automations and requires vendor help.
- Costly fixes and renewal windows cement the choice.
Negotiation levers and contract clauses that actually reduce lock‑in
You reduce lock-in by insisting on concrete contract rights: a short initial term, machine-readable export guarantees, configuration escrow and pre-purchased migration days. Tie staged acceptance to measurable delivery gates and cap early-exit fees so migration effort and cost are predictable rather than open-ended.
- Short initial term: 6–12 months if you can negotiate it.
- Escrow/source access: configuration held in escrow with triggers.
- Export guarantees: machine-readable export with delivery timelines.
- Migration support days: pre-purchased days for knowledge transfer.
- Termination caps: fixed, limited early-exit fees.
Identify your biggest operational bottleneck
Most owners already know which process is the problem. What they do not have is the annual figure attached to it. That is a 15-minute conversation, not a project.
Practical contract language to ask for now
Ask for clauses that require a machine-readable export of all workflows within a fixed number of days after termination, a migration assistance schedule with fixed-rate days and a maximum cap, and configuration held in escrow with spelled-out trigger events and delivery timelines. Put delivery dates and penalties in writing.
- Machine-readable export: defined format and delivery timeline.
- Migration assistance: pre-purchased days, fixed rate, maximum cap.
- Escrow triggers: failure to support, insolvency, or termination.
Decision rules for a 10–200 person company
If you automate a handful of high-frequency tasks and want portability, choose SaaS connectors plus a consultant or a fixed-scope build. If you need central orchestration, compliance controls and forecasted scale across departments, enterprise RPA can make sense — but only with short commercial terms, escrow and migration guarantees, and technical leadership in place.
- SaaS + consultant: best for speed and low lock-in.
- Fixed-scope build: best when you want a handover and portability.
- Enterprise RPA: justified for cross-department scheduling, compliance and scale.
An annual licence with auto-renew and proprietary connectors is a multi-year operational decision, whether the CFO realises it or not.
What to do tomorrow
Make a short inventory: list the automations you rely on, who owns them, where runbooks live and which ones require vendor tooling. Ask your vendor for a machine-readable export of one proof-of-value workflow and a written migration estimate; if they resist, treat that resistance as a material risk to your CFO. If you want help, see Services.
- Inventory one: pick five automations to audit this week.
- Request export: get a written export and migration quote.
- Decide: choose SaaS/consultant or enterprise RPA based on scale and governance.
When enterprise RPA is the right buy for you
Buy enterprise RPA when you have predictable, high-volume needs across departments, compliance that requires a central control plane, and the budget and headcount to support ongoing licence costs. If automations will touch multiple core systems, need central scheduling, or must meet rigorous audit trails, enterprise licences are defensible.
- Requires: cross-department scale, compliance needs, long-term budget.
- Not for: single-team automations, small volumes or one-off fixes.
Where I’ve seen this work well
It works when a company buys a short pilot, demands an explicit migration plan before converting to production, and ties licence purchases to delivery gates. With that discipline the vendor console never becomes the operational source of truth and migration work is planned. See my Portfolio and case studies and About the author.
- Pilot with migration clause prevents hidden lock-in.
- Staged payments tied to migration deliverables protect you.
- Pre-purchased vendor support days smooth exits.
If you need advice rather than build work
If you need a vendor risk assessment, migration clauses written, or an automation inventory, I run short advisory engagements that deliver a decision brief and negotiation plan; see Tech consulting for scope. If you want delivered automations with full handover, I offer fixed-scope builds where routines and documentation belong to you; see Custom build.
- Decision brief: vendor risk, migration cost and negotiation points.
- Fixed-scope build: delivered automation and full handover.
- Fractional technical leadership for longer programmes: see Fractional CTO.
Next step if you want a contract-risk assessment
Book a short call through How to work together and I will review your licence lines, sample workflows and the renewal date. The outcome is a written shortlist of negotiation clauses and a migration cost estimate you can use immediately.
- Prepare: licence summary and renewal dates.
- Outcome: negotiation levers and a migration cost estimate.
Where businesses waste the most time
- Re-keying customer dataStaff duplicate entries, causing errors and delaysAdd a direct connection so data entered once appears across systemsA person still checks: A person spot-checks new records for exceptions
- Chasing invoice approvalsApprovals are delayed and staff spend hours on remindersAutomate reminders and route invoices to the right approver using simple rulesA person still checks: Approver signs off on flagged invoices and exceptions
- Manual report assemblyPeople compile numbers from several systems, causing slow decisionsCreate a scheduled routine that assembles numbers and delivers a draft reportA person still checks: Manager reviews and interprets the compiled report
How this compares with what you already run
| Operational area | The manual way | The automated way | Annual business impact |
|---|---|---|---|
| Order entry | Staff re-type orders from emails | Automated connection creates orders | Reduces payroll for that role |
| Invoice processing | People check and match invoices manually | Automated reading and matching, human approves exceptions | Shortens cycle time and lowers late-payment costs |
| Customer onboarding | Manual profile creation and setup | Automations perform setup tasks, human verifies | Frees staff for revenue tasks |
| Monthly reporting | People compile spreadsheets from systems | Automations gather and prepare reports | Cuts report prep time, speeding decisions |
| Support triage | Agents route tickets by hand | Rules and connectors pre-sort tickets | Reduces response time and escalations |
What the end-to-end workflow looks like
- Receive invoiceInvoices arrive by email or portal and are stored in a shared folderAutomated capture reads and files invoices
- Extract key fieldsInvoice date, amounts, supplier and PO number are identifiedAutomated routine extracts fields and writes them to a central record
- Match to purchase orderSystem compares invoice data with purchase ordersAutomated match flags exceptions
- Route for approvalInvoices are sent to the right approver based on rulesAutomated routing delivers invoices to approvers
- Approve or resolve exceptionsApprover checks details and either approves or asks for correctionStays human
- Schedule paymentApproved invoices are scheduled for payment on the payment runAutomated scheduling places invoices on the payment list
- Record and archivePayment and invoice records are stored for auditAutomated entry into the accounting system and archive
The metrics that tell you it worked
| Metric | What it tells you |
|---|---|
| Hours saved per week | Total manual labour hours removed from the team by automations, measured weekly and summed across people. |
| Cycle time (days) | Days from initiation to completion of the process; automation should shorten this measured from start to finish. |
| Manual errors per month | Count of human data-entry mistakes caught downstream each month. |
| Approvals pending over SLA | Number of approvals outstanding past the agreed turnaround time. |
| Automation failure count | Number of times an automation fails and needs human intervention each week. |
| Time to restore | Hours it takes to recover a broken automation after detection until resolution. |
When this is the wrong move
- You have only a handful of simple tasks and need portability: use SaaS connectors or a fixed-scope build.
- You lack technical leadership and cannot enforce migration clauses: a long licence will create hidden operational debt.
- You need occasional, low-volume automations where transaction-based SaaS pricing is cheaper than annual licences.
- You expect major process change in the next 12 months: avoid locking into a vendor that forces expensive rewrites.
The mistakes that cost the most
- Automating a broken processTeams automate the current workflow without fixing upstream issues; automations embed inefficiency and increase maintenance.
- Accepting indefinite auto-renewThe organisation misses the renewal notice and pays another year; by then the vendor controls operations and exit costs rise.
- No migration planContracts lack export guarantees; when the decision to leave comes the team realises workflows must be rebuilt from scratch.
- Letting the vendor own runbooksRunbooks and monitoring live in the vendor console, so your staff cannot operate without vendor tools and support.
Frequently asked questions
Can you avoid lock-in entirely when buying enterprise RPA?
No. Enterprise RPA always creates some operational dependence. You can limit it by negotiating short terms, escrowed configuration and paid migration days, but orchestration and vendor connectors will still create practical barriers to a quick exit.
How long does migration actually take for a mid-size automation programme?
Expect several months for 50–100 automations. The work includes cataloguing, rebuilding workflows for the new environment, regression testing and parallel running; budget developer and tester time plus business validation hours.
Are SaaS connectors reliable enough for mission-critical tasks?
They are reliable for many high-frequency, low-complexity tasks and are easier to move away from. For complex, high-security or highly regulated processes you may need enterprise features that SaaS connectors do not provide.
What is the cheapest path to reduce licence lock-in right now?
Inventory five critical automations, get a machine-readable export for them, and negotiate pre-paid migration days or a capped termination fee. These steps are low-cost and materially reduce your immediate migration risk.
Should I hire an automation specialist or use a consultant?
Hire a specialist if you need ongoing iteration and ownership. Use a fixed-scope consultant if you want a one-off build with handover and minimal ongoing licence risk.
Stop paying salary for robotic work
Bring your messiest process to a 15-minute audit and we will map where the hours actually go, live on screen. You leave with the number whether or not you work with me.