RPA bots for the screens with no way in.
Automate repetitive screen work in desktop applications and portals that lack a suitable API. Our robotic process automation services build bots for data entry, downloads and routine checks, with logs and exception handling. We review access requirements and screen stability before recommending RPA.
- A free 5-day audit comes first
- We sign an NDA before we see anything
- Fixed price before you commit
- You own all the code
Portal bot
Example
Last night's order updates from supplier portals
- Logged in to 6 supplier portals with its own account
- Typed 87 order updates into the old desktop system
- Saved a screenshot of every step
2 orders now show a later delivery date. Tell the sales team?
An example with made-up figures. The buttons send nothing.
How RPA works.
We watch the routine
We sit beside the person who does one screen-based task and write down every login, click, field and rule they follow.
A bot does the clicking
A software robot signs in and works the same screens in the same order, at any hour, and records every action it takes.
Odd cases come to you
When a screen shows something your rules do not cover, the bot stops and passes it to the right person with a screenshot.
RPA use cases.
Pick the screen your team spends the most time on. Each tab shows the clicking it takes today and what the bot does in its place.
- Today
Someone logs in to the same portals every day
With a botEvery portal checked, every update copied across
A bot signs in to each supplier or customer portal, reads order status, downloads documents and types the updates into your own system. A changed date or a missing document goes to a person before it reaches your records.
Every portalchecked each time, including the ones people forget
Start a project - Today
The old desktop system has no way in
With a botEntries keyed into the old system without anyone typing
Your core system may be too old to connect to anything. A bot types into its screens field by field, as your staff would, and checks that each entry saved. You keep the system, and your team stops retyping.
Field by fieldthe same way every time
Start a project - Today
Government filings are typed in by hand
With a botRoutine filings entered from your own records
The bot fills in returns, registrations and renewals on the government portal from the figures you already hold. The bot stops before it submits, so a named person checks and approves each filing.
Approvedby a person before anything is submitted
Start a project - Today
Bank statements are downloaded one by one
With a botStatements fetched from every bank, ready for finance
A bot signs in to each banking website, downloads statements and remittance details and files them where your finance team works. It reads and downloads; payments stay with your people.
Waitingfor finance, not chased by them
Start a project
How you stay in control.
Giving a robot your logins calls for firm limits. Every bot we hand over runs inside these four.
Your rules set what the bot may touch
You list the screens it may use, the fields it may change and the steps that always need a person. Anything outside that list stops and waits for someone you named.
- You choose who approves what
- Every exception flagged and logged
- Most steps can be reversed
Your logins and data stay yours
Bots run inside your own cloud account, and their logins stay under your control. What they read on screen goes only into the systems you chose.
- Bots and their logins in your cloud account
- NDA, MSA and DPA cover every bot
- Each bot has only the access you grant
It uses the screens you already have
Nothing on your side has to change. The bot works your desktop software, portals and banking websites as they are. Where a system can be connected directly, we do that instead, because a direct link breaks less often.
- Desktop software, portals and websites
- A screenshot of every step
- Each bot script stored in your name
You see every run
A dashboard shows how many items each bot finished, how many it passed to a person and why. If a portal changes its layout and a bot stops, you see that there first.
- Items handled, counted from the first day
- Stopped runs shown as they happen
- A full log of every click
RPA project timeline.
Each stage stands on its own, so you can stop after any of them. In week three a bot is already working your own screens while your team checks its entries.
01 ยท Week 1
Audit
We sit with one team, record the screen work they repeat and rank three tasks by the hours a bot would save.
You end withA plan and a fixed price.
02 ยท Weeks 2 to 3
Trial
We build a first bot for one task and run it on test logins where they exist. Your team checks every entry it makes.
You end withProof it works, or a clear no.
03 ยท Weeks 4 to 8
Build
We give the bot its own logins, add your approval rules and exception list, and test it on real cases until your IT and security people are satisfied.
You end withA bot your IT team has signed off.
04 ยท Weeks 9 to 10
Go live
The bot works beside your team first. You compare its entries with theirs on the dashboard before handing the task over.
You end withFigures to decide the next bot.
After launch we watch every bot and update it when a portal or screen changes, which they often do without warning.
Free AI readiness audit.
Pick the team that lives in portals and old screens. On day five you know which of their tasks a bot can take, the hours it would save and the price of the first bot.
What you hold when it ends
Free, 5 days
- A list of the screen work your team repeats today
- The three tasks where a bot saves the most hours
- A fixed price and a timeline for the first one
Keep the task list and the plan, even if another team builds the bots.
What our clients say.
From clients in the US, Portugal, New Zealand and the UK.
RPA questions.
What it costs, how your logins stay safe and what a bot does when a portal changes.
When is an API integration a better choice than RPA?
A supported API is often easier to maintain than a bot that depends on screen layout. RPA is useful when suitable APIs are unavailable and the screen workflow is stable. We review both options, including access permissions, exception volume and maintenance requirements.
How much do RPA services cost?
The price moves with how many screens and systems the bot works, how many exceptions it has to recognize and how often those screens change. The free 5-day audit ends with a fixed price, so the figure is on the table before any work starts.
When is RPA the right choice, and when is it not?
A bot earns its place when a system can only be reached through its screens, such as an old desktop program, a portal or a banking website. If a system can be connected directly, that is quicker and breaks less, so we do that. If a step needs reading and judgment, an AI agent suits it better. The audit says which fits each step, and why.
What happens when a portal changes its screens?
The bot notices that a screen no longer looks the way it expects, stops and tells you, instead of typing into the wrong field. The screenshots show exactly where it stopped, and we update it.
Is it safe to give a bot our logins?
Each bot gets its own login with only the access it needs, kept in your cloud account under your control. Every action is logged with a screenshot, so you can always see what the bot did and when.
Who owns the bots once they are built?
You do, from day one. Each bot, its own login and its script sit in your cloud account under your name, with full documentation. End the contract and the bots stay with you, with nothing extra to pay.
How do we work with a team based in India?
You talk to a founder from the first call. Our hours overlap the US and UK business day by 3 to 4 hours, and we reply within 4 business hours in the tools you already use.
Free project estimate
Start your RPA project.
Share that screen with a founder on a 30-minute call. You leave knowing whether a bot or a direct connection suits the task, roughly what it would cost and what we would build first. If neither is worth it, we tell you.
What you get back
- An indicative budget range
- A realistic timeline
- What moves the cost up or down
- A reply within 4 business hours
- Answered by a founder
- NDA on request, before you share details
Tell us what you need
A few lines is plenty. You get a number before any call.