Robotic process automation for systems that will never get an API

Two costs run in parallel. Development for a moderate process — one system, clear rules, a handful of exceptions — is typically three to six weeks. Platform licensing is separate and annual: unattended runtimes and orchestration are the usual line items. For a process consuming only a few hours a month, the licence often makes the case unviable, and we will tell you that before you buy it.

A simple data-entry bot against one stable application takes two to three weeks including testing. Anything crossing several systems, handling documents or carrying a long exception list runs longer, mostly because of exceptions rather than the happy path. Assessment and process definition add about a week before the build starts.

Unattended suits high-volume back-office work that runs to a schedule with no human in the loop — reconciliations, bulk uploads, overnight reporting. Attended suits work a person triggers during a conversation, such as pulling records together while a customer is on the line. Licensing and infrastructure differ, so the decision is made during assessment.

The bot fails, and monitoring tells you before the business does. Selector repairs usually take hours rather than days if the automation was built with stable anchors. Most clients keep a small monthly capacity for exactly this; vendor upgrade cycles for the target applications are worth knowing about in advance.

Yes. A common first engagement is a review of bots already in production: what still runs, what fails silently, what duplicates something the ERP now does natively. You get a list of bots worth keeping, repairing or retiring, and we can then work inside your existing Orchestrator rather than standing anything new up.