Skip to content
ODOOVATIONShome

Workflow and document automation

Robotic process automation

Robotic process automation (RPA) operates an application’s screens the way a person would, clicking and typing, for systems that have no usable API. We use it only where a cleaner integration is not available, and document how it can fail.

What does robotic process automation from ODOOVATIONS include, and what does it cost?

Process map, validation, retries, logs and ownership handover. There are three packages, from From USD 500 (≈ PKR 138,300), starting fee, each with a stated scope. Prices are launch offers in US dollars before taxes; a written scope confirms the final price before any work starts.

Is this the right purchase?

The problem it solves

An old desktop or web system has no API, so staff copy figures out of it every day, and replacing the system is not on the table this year.

Who it is for

Teams stuck with a legacy or vendor system whose screens are stable and whose task is repeated often.

When it is the wrong first step

If the application has an API or export, a normal workflow integration is cheaper and sturdier. If the screens change often, RPA will keep breaking.

What is included, and what is not

We deliver

  • A task walkthrough and exception list
  • The automation, within the tier’s workflow and app count
  • An exception log and screenshots of failures
  • A recovery runbook naming who restarts it and how

You provide

  • A recorded walk-through of the task
  • A dedicated user account for the bot
  • A machine or environment where it can run
  • Provides and owns the bot’s credentials
  • Keeps the run machine available
  • Tells us before the application is upgraded

Priced separately

Steps, volumes and exceptions are defined during scoping. Hosting, licences and API usage are separate.

Packages

Priced per bounded business workflows. Launch prices in US dollars, before taxes. There is no online checkout: choosing a package starts a conversation and a written scope.

Planning: 3–7 business days / 2–3 weeks / 3–6 weeks. Proposed planning range, confirmed after inputs and complexity review; not an advertised market average or an outcome guarantee.

Rupee figures are indicative, converted at 1 USD = PKR 276.6 (rate of 30 October 2026). Prices are set in US dollars; a fixed PKR quotation is given in writing.

How the work runs

  1. Step 1

    Observe

    Record the task and every exception a person handles.

  2. Step 2

    Build

    Script the steps with checks after each screen.

  3. Step 3

    Break it

    Test slow screens, missing data and a changed layout.

  4. Step 4

    Hand over

    Runbook, log location and a trained owner.

When it is done: Done when the bot completes the agreed test runs and stops safely on the exceptions. Unattended running depends on your machine and credentials staying available.

What the work looks like

Exception log (extract)Sample data
RunRecordStopped atReason
R-112INV-2041Save screenField "Due date" empty
R-113—LoginPassword expired
R-114INV-2043—Completed

Sample data. Format only. More samples in the ODOOVATIONS Flow Workshop.

What we measure

  • Records processed and records stopped for review
  • Stops caused by screen changes, which signal it is time for a sturdier integration
  • Staff time on the task, before and after, from your own count

Questions buyers ask

Screen automation breaks when screens change. We use it only when there is no API or export.

Talk to us about robotic process automation

Tell us what you need in a few lines. We reply with questions or a written scope; nothing is charged by asking.