01
Process discovery
We sit with the people who do the work, map each step and exception, and count the volume and time it takes today.
FIG 01 · RPA Development
RPA development services for the systems that have no API
Software bots for the desktop and web applications your team still keys data into by hand, built only where an API won’t do, and built to keep running after the next screen change.
See how it works
FIG 02 · Quick answer
What are RPA development services?
RPA development services build software bots that click, type and copy data through applications the way a person would. Elgrith uses robotic process automation only where no API or connector exists, builds attended or unattended bots in Power Automate or UiPath, and adds logging, alerts and a maintenance plan so bots survive screen changes.
- A bot only where no API or connector exists
- API first
- Projects delivered since 2015
- 1,000+
- Clients across the USA, UK and India
- 250+
- Your code, repository and IP
- 100%
FIG 03 · Why it matters
A bot is the right answer only when there is no better door into the system.
From Microsoft Learn and Gartner, checked 24 Oct 2026.
01
No API
When Microsoft says RPA is needed
Microsoft’s licensing guide says RPA is needed for applications that lack a prebuilt connector and have no APIs to build a custom one. So we check for an API first.
Source: Microsoft Learn, types of Power Automate licenses (updated 22 Sep 2026)(opens in a new tab)02
1 at a time
Desktop flows per unattended bot
A Power Automate Process license allocated to a machine becomes one unattended bot that runs one desktop flow at a time. Parallel runs need one license per run, which shapes the design.
Source: Microsoft Learn, types of Power Automate licenses (updated 22 Sep 2026)(opens in a new tab)03
40%+
Agentic AI projects cancelled by 2027
Gartner predicted over 40% of agentic AI projects will be cancelled by the end of 2027, and warned of “agent washing”: vendors relabelling RPA, assistants and chatbots as agents.
Source: Gartner, press release on agentic AI projects (25 Jun 2025)(opens in a new tab)
FIG 04 · Decide first
RPA, API integration or an AI agent?
Most automation requests don’t need a bot. This is how we decide in discovery, before anyone records a click.
| API integration | RPA bot | AI agent | |
|---|---|---|---|
| Use it when | The system has an API or connector | There is no API, and the steps are fixed and rule-based | The input is messy and the next step needs judgement |
| How it works | Systems exchange data directly | A bot drives the screens like a person: clicks, keys, copy and paste | A model reads, decides and calls tools, with limits you set |
| What breaks it | A versioned API change, usually announced | A moved button, a new pop-up or a changed screen | Unclear instructions, missing guardrails or bad source data |
| Keeping it running | Low: contracts and monitoring | Ongoing: selectors, retries and an exception queue | Ongoing: evaluation, logging and human review |
| Where we build it | API integration | This page | AI agent development |
Many good solutions mix the three: an API for the systems that have one, a bot for the one legacy screen that doesn’t, and a model to read the documents in between.
Systems have APIs? API integrationFIG 05 · What you get
What our robotic process automation services cover
From the first process map to the bot that is still running a year later. We check feasibility before we build, and we hand over the runbooks with the bot.
02
Feasibility: API or bot
For each step we check for an API, a connector or an export first. A bot goes only where none of those exist.
03
Bot design
Steps, inputs, outputs, error paths and the hand-off points to a person, written down before the build starts.
04
Build
Attended or unattended bots in Power Automate desktop flows, or in UiPath where you already run it.
05
Testing
Runs against real but safe test data, including the awkward cases: blank fields, timeouts and locked records.
06
Deployment
Machines, credentials in a vault, schedules and triggers set up in your tenant, then a supervised pilot run.
07
Monitoring and alerts
Run logs, failure alerts and an exception queue, so a person knows within the run that something needs a look.
08
Maintenance
Fixes when a target application changes, under support terms agreed in your written scope.
Deliverables
10
deliverables, in writing
Included in every build, written into your fixed quote before work starts.
FIG 06 · Use cases
Processes we automate with RPA
The best candidates are high-volume, rule-based and stuck in a system with no API. These are the ones we see most.
Invoice entry
- Trigger
- Invoices arriving in a mailbox or folder
- Bot
- Reads the fields and keys them into a desktop finance system
Bank and ledger reconciliation
- Trigger
- Daily statement files
- Bot
- Matches lines against the ledger and queues the exceptions for a person
Legacy-to-legacy data moves
- Trigger
- A new record in one old system
- Bot
- Copies it into another old system that has no import
Report pulls
- Trigger
- A schedule
- Bot
- Signs in to a portal, exports the report and files it where your team needs it
Your ERP or accounts has an API?
Then a bot is the wrong tool. Our ERP team connects it directly.
ERP Development
FIG 07 · Consulting
RPA consulting: which processes to automate
We score each candidate process before quoting a build. A process that fails two or more of these usually needs a fix, an API or a person, not a bot.
06principles
Rule-based
Every decision can be written as a rule. If a step needs judgement, a person or an AI step handles it.
High volume
Enough runs a day or month that the build and upkeep pay back in hours saved.
Stable screens
The target application doesn’t change every month. Frequent releases mean frequent bot fixes.
Structured inputs
Inputs arrive in a known shape: forms, files or fields. Free text and scans need a document-reading step first.
Known exceptions
The odd cases are known and few, and there is a clear place to send them.
A named owner
Someone in your team owns the process and decides what the bot should do when it changes.
FIG 08 · Bot modes
Attended vs unattended bots
The mode decides the license, the machine and who is watching. In Power Automate, as Microsoft Learn describes it (checked 24 Oct 2026):
04principles
Attended bots
Run on a person’s own machine while they work, started by them. The Power Automate Premium user license includes one attended bot.
Unattended bots
Run on their own on a machine, on a schedule or a trigger. Each Process license is one unattended bot that runs one desktop flow at a time.
Machine requirements
Unattended desktop flows need an available machine with all users signed out, and they can’t run with elevated privileges. We design around both.
Hosted machines
A Hosted Process license supports one Microsoft-hosted bot, so you don’t manage the machine. Hosted machine groups can scale runs up and down.
FIG 09 · Platforms
Platforms we build on
We pick the platform you can run and afford after we leave. We don’t hold partner status with any RPA vendor, so the recommendation follows your licenses, not a sales target.
04principles
Power Automate desktop flows
Our default for teams already on Microsoft 365: desktop flows for the screens, cloud flows for the triggers and approvals.
Power Apps and Power PlatformUiPath
Studio for building and Orchestrator for running bots at scale, when your organization already runs UiPath. Platform choice is confirmed in your written scope.
No platform license at all
For a single web application, a small scripted browser automation can be cheaper to run than an RPA platform. We say so when it is.
Or no bot at all
When the vendor has an API or an export, a direct integration is faster and steadier than any bot.
API integration
FIG 10 · Reliability
Bots that survive change
Bots break when the screen changes. We can’t stop that, but we can make a break small, visible and quick to fix.
06principles
Robust selectors
Elements found by stable attributes, not screen positions, with fallbacks where the application allows.
Retries with limits
Timeouts and slow screens retried a set number of times, then handed to a person instead of looping.
Exception queues
Items the bot can’t finish go to a queue with the reason and a screenshot, so nothing is lost silently.
Run logs
Every run logged with what it processed, how long it took and where it stopped.
Alerts
Failures and unusual run times raised to the owner by email or Teams.
Runbooks and ownership
A runbook per bot: what it does, what to check when it fails, and who decides changes.
FIG 11 · AI
Adding AI to RPA
AI helps a bot read what it couldn’t before. It doesn’t make a fragile process safe, and an RPA bot renamed as an “agent” is still a bot. We keep a person in the loop wherever a wrong answer costs money.
04principles
Document extraction
Intelligent document processing reads invoices, forms and scans into fields, with a confidence score per field.
Classification
Emails and documents sorted by type or urgency before the bot acts on them.
Human in the loop
Low-confidence fields and high-value items go to a person to approve, and their answers are logged.
When you need an agent
If the task needs judgement across several systems, an AI agent with clear limits may fit better than a bot.
AI agent development
FIG 12 · UK
RPA for UK teams
For UK finance, operations and shared-services teams, we work through our London client-partnership centre, with delivery from our New Delhi HQ. Documentation is written in UK English, and working hours are agreed in your written scope.
03principles
Shared-service centres
Bots for the high-volume, rule-based work that UK shared-service teams still key by hand into legacy systems.
Data protection in the design
Bots touch personal data, so we keep access minimal and logs free of sensitive fields, with UK GDPR in view. General guidance, not legal advice.
Your organisation owns it
Bots, credentials and runbooks live in your tenant, so your team can change or switch them off.
FIG 13 · Plan
Planning the automation
Guides that help you choose the right kind of automation before you buy a license.
04principles
Bots that post to the books?
Direct links between your accounts and the rest of your stack.
Accounting software integration
FIG 14 · Measurement
What we measure once a bot is live
We report from your run logs, not from a spreadsheet of hoped-for savings.
| How we measure it | What we won’t do | |
|---|---|---|
| Runs | Completed, failed and partly completed runs per day, from the run log | Count a run as a success when items went to the exception queue |
| Exceptions | Items handed to a person, grouped by reason | Hide exceptions to make a dashboard look clean |
| Time saved | Handling time before the bot, measured in discovery, against items the bot finished | Quote a savings figure we can’t trace to your data |
| Breaks | Failures caused by a change in the target application, and time to fix | Promise a bot that never breaks |
FIG 15 · Process · 6 steps
Check for an API, then build the bot
A fixed written quote after a free call, then sprints with a demo every week, a supervised pilot and a hand-over with runbooks. You own the bots, the code and the documentation.
- Step 01
Free call
Tell us the process, the systems and the volume. We ask about exceptions and APIs, not just the clicks.
- Step 02
Process discovery
We map the steps, score the process and check every system for an API, connector or export.
- Step 03
Fixed written quote
A written scope and a fixed quote: which steps get a bot, which get an API, the platform and licenses you will need.
- Step 04
Build in sprints
Bot design, build and test against safe data, with a demo every week.
- Step 05
Supervised pilot
Real runs with a person watching, often attended first, before the bot runs unattended.
- Step 06
Run and maintain
Monitoring, alerts and fixes when target applications change, under terms agreed in your written scope.
FIG 16 · What you get
Everything included
Written into your fixed quote, so you know exactly what you are paying for before work starts.
10items
- Written scope and fixed quote
- Process map and candidate scoring
- API-or-bot feasibility for each step
- Attended or unattended bots in your tenant
- Credentials stored in a vault, not in the bot
- Exception queue and run logs
- Failure alerts to a named owner
- Runbook for every bot
- Hand-over session for your team
- IP assignment: bots and code are yours
FIG 17 · Tech & tools
The tools behind the work
Proven, well-supported tools, chosen for your project and set up in accounts your business owns.
- Power Automate desktop flows
- Power Automate cloud flows
- AI Builder
- Dataverse
- UiPath Studio
- UiPath Orchestrator
- Python
- Playwright
- SQL Server
- Azure Key Vault
- Microsoft Teams
- Excel
FIG 18 · Who it’s for
RPA for finance, operations and shared-services teams.
Bots for the systems you can’t replace yet, with a person still in charge.
3 audiences
Finance
Invoices, reconciliations and month-end, without the re-keying.
Bots that move figures between bank files, finance systems and spreadsheets, with every exception queued for a person to approve.
- Invoice entry
- Reconciliations
- Report pulls
- Approval steps kept
Operations
Legacy screens your team still types into every day.
Order entry, status updates and data moves between old systems that have no import and no API.
- Order and claims entry
- Legacy-to-legacy moves
- Scheduled runs
- Alerts on failure
UK teams
Robotic process automation for UK organisations.
Through our London client-partnership centre, with delivery from our New Delhi HQ. Documentation in UK English; working hours agreed in your written scope.
- Shared-service processes
- UK GDPR in the design
- Bots in your tenant
- Fixed written quote
FIG 19 · Working with us from the USA and UK
Built in New Delhi. Run on your hours.
Every project gets a point of contact in New York or London and an engineering team in New Delhi. Here is how today’s working days line up, live.
New York
North America
--:--ET
New Delhi team Your working day- Shared working time
- ≈ 3 hours today
- New Delhi is
- 10.5 h ahead
- Live calls, your time
- 9 a.m. to 12 p.m. ET
London
UK & Europe
--:--UK
New Delhi team Your working day- Shared working time
- ≈ 4.5 hours today
- New Delhi is
- 5.5 h ahead
- Live calls, your time
- 9 a.m. to 1:30 p.m. UK
Three ways to work together
- 01
Fixed-scope project
A written scope, one fixed price and a dated plan. Suits websites, apps and MVPs.
- 02
Dedicated team
Designers and engineers on your roadmap every month, billed monthly.
- 03
White label
For US and UK agencies: our work, your brand, unbranded deliverables.
Every engagement
- Fixed quote in USD, GBP or INR after a free 30-minute call
- NDA before discovery. You own all code, designs and content
- A working demo every sprint, not status slides
- Reply within one business day, calls inside your hours
Book a call
Calls on ET or UK hours
FIG 20 · Cost
What drives RPA development cost
We don’t publish prices. These are the things that move the cost of an RPA project, so you can decide what to automate first.
| Driver | Lower cost | Higher cost |
|---|---|---|
| Process | One process, few exceptions | Several processes, many exception paths |
| Systems | One target application | Several applications, including Citrix or remote desktops |
| Mode | Attended bot on a user’s machine | Unattended bots running in parallel |
| Inputs | Structured files or forms | Scans and free text that need document extraction |
| Upkeep | Stable target screens | Applications that change often |
Platform licenses are billed by the vendor and sit outside our quote; we tell you which ones the design needs. After a free call you get a written scope and a fixed quote.
FIG 21 · Rules and dates
RPA licensing and market dates (checked 24 Oct 2026)
What changed for RPA, and when. Checked at each source on 24 Oct 2026.
| Source | Date | What it says | What it means for your bots |
|---|---|---|---|
| Microsoft Learn, Power Automate license types | Updated 22 Sep 2026 | Premium includes one attended bot; a Process license is one unattended bot running one desktop flow at a time | Count parallel unattended runs before you buy licenses |
| Microsoft Learn, unattended desktop flows | Updated 31 Aug 2026 | Needs an available machine with all users signed out; can’t run with elevated privileges | Plan dedicated or hosted machines and non-admin steps |
| UiPath investor release | 30 Apr 2025 | Agentic automation where people, robots and AI agents work together | Vendors now bundle AI agents with RPA; check what you are paying for |
| Gartner press release | 25 Jun 2025 | Over 40% of agentic AI projects cancelled by end of 2027; warns of “agent washing” | Start with a narrow, measured process, whatever the label |
Sources: Microsoft Learn license types and unattended desktop flows pages; UiPath investor relations; Gartner newsroom. License terms change; we re-check them in discovery.
FIG 22 · Compare
UiPath or Power Automate?
| Power Automate desktop flows | UiPath | |
|---|---|---|
| Fits best | Teams already on Microsoft 365 and the Power Platform | Organizations already running UiPath, or large bot estates |
| Building | Power Automate for desktop, with cloud flows for triggers | UiPath Studio |
| Running at scale | Machines, machine groups and hosted machine groups | UiPath Orchestrator |
| Licensing | Premium per user for attended; Process or Hosted Process per bot | Set by UiPath; check your agreement |
| Our default | Yes, when you are on Microsoft 365 | When you already own it |
FAQ
Frequently asked questions
Straight answers about RPA Development with Elgrith.
An attended bot runs on a person’s own machine while they work, and they start it. An unattended bot runs on its own on a machine, on a schedule or a trigger. In Power Automate, the Premium user license includes one attended bot, and each Process license is one unattended bot that runs one desktop flow at a time (Microsoft Learn, updated 22 Sep 2026).
FIG 23 · Related
Keep exploring
AI Automation
Workflow & process automation with AIPower Apps Development
Power Apps & Power Automate buildsAPI Integration
Connect your apps, CRM & paymentsAI Agent Development
Custom agents, MCP servers and guardrailsERP Development
Custom ERP & ERP integrationsAccounting Software Integration
QuickBooks, Xero, Sage & Tally sync
Free 30-minute call
Automate the screens that have no API.
Tell us the process, the systems and the volume. We check for an API first, and after a free call you get a written scope and a fixed quote.
Pick a day for your call
OpenPick a day. You'll choose a time in your own time zone on the next step.