# RPA bots and robotic process automation without costly RPA licences

Source: https://saitai.lt/en/services/business-automation/rpa-bots/
Updated: 2026-11-01
Breadcrumbs: [Home](https://saitai.lt/en/) › [Services](https://saitai.lt/en/services/) › [Business automation](https://saitai.lt/en/services/business-automation/) › RPA bots

RPA (robotic process automation) is a software bot that does in a portal or system what a member of staff would: logs in, downloads a report, checks a status, moves data into your software. You need it where a system has no API or convenient export. We write the bot in code and run it on a server on a schedule, so there are no yearly RPA platform licences to pay. We have experience building data collection programs (scrapers) and integrations. A bot costs from €790 and goes live in approximately 1–3 weeks after agreement and access. Portals change, so we offer support alongside it – from €29/month.

Prepared by the Saitai.lt team · Updated 1 November 2026

At a glance

- **Price:** one bot from €790; no RPA platform licences needed; no VAT is charged
- **Timeline:** approximately 1–3 weeks after agreement and access
- **What it is:** a software bot that works in a portal through a browser instead of a person
- **Where it runs:** on a separate server we provide or on yours, on a schedule or triggered by an event
- **Control:** action log, error notifications, staff approval for key steps
- **Logins:** a dedicated bot account; passwords in an encrypted vault, never in the code
- **Support:** required: from €29/month – server and monitoring; fixes when the portal changes – €50/hour or within the €129/month plan
- **What we don't do:** automate portals with CAPTCHA or a ban on bots; work where you have no right to
- **Where we work:** remotely across Lithuania; meetings in Vilnius by appointment, arranged by phone

## A good fit if

- Someone logs in to a supplier, partner or industry portal every day, downloads orders, prices or stock levels and moves them into your own system.
- The system has no API, and exports have to be done by hand – daily or weekly, the same way every time.
- You need to check order, shipment or application statuses across several portals and know when something changes.
- A report is pieced together from several online systems into Excel or Google Sheets.
- You looked at UiPath or Power Automate, but for 1–3 bots the licences and upkeep seem too expensive.

## Not the best fit if

- The portal uses CAPTCHA or other bot protection, or its terms of use forbid automation – we don't build bots for these.
- Every login needs Smart-ID or another second factor – full automation won't work; the only options are a staff member approving the login, or another route (API, file export).
- The system has an API or convenient import and export – an API integration is then more reliable and cheaper to maintain than a bot.
- The software runs only on a Windows desktop, not in a browser, and can't export anything – classic RPA platforms are a better fit there.
- The task happens a few times a month – building and maintaining a bot would cost more than the time saved.

We have been building websites and business systems since 1998. Our experience includes scrapers – programs that collect data from websites and systems, analyse it, publish or archive it – and integrations with online stores, CRMs and accounting software. We don't name clients – our confidentiality agreements don't allow it.

## What you get

### A bot in code, not a licensed platform

We write the bot in code: it drives a headless browser (for example, with the Playwright browser automation tool) and follows the same steps a person would. You pay for the build and support, not for a yearly bot licence.

### Scheduled runs on a server

The bot runs on a separate server rather than a staff member's computer: every hour, every morning or when a new request arrives. Nobody has to leave a PC switched on.

### Log and notifications

Every run is logged: what was downloaded, what was moved, what failed. If the bot stops, the person responsible gets an email or Telegram notification.

### Secure logins

We recommend a dedicated bot account with the minimum rights it needs. Passwords are kept in an encrypted vault on the server – not in the code or in emails – and you can revoke access at any time.

### Lawful automation only

Before we build anything, we check that you have the right to work in the portal and that its terms allow automation. If the portal offers an official API or data exchange interface, we suggest that instead.

### Straight talk about support

When a portal changes its layout or fields, the bot stops – that's normal. We get the alert at the same time as you and fix the bot under your support plan.

### A person where it matters

Key steps such as submitting data or making a payment can wait for staff approval, while routine downloads and transfers run automatically.

## How much does an RPA bot cost?

One bot that does a clear task in one portal – logs in, downloads or checks data and moves it into your system – costs from €790. No RPA platform licences are needed. After launch we look after the bot: support at from €29/month covers the server, scheduled runs and monitoring, while fixes after portal changes are billed at €50/hour or included in the €129/month plan (up to 2 hours a month).

Price from

€790

Prices include all taxes – no VAT is charged (we are not VAT-registered). We put the price and timeline in the contract before work starts.

### What the price depends on

- How many portals or systems the bot works with and how many steps it takes in each.
- Whether data only has to be downloaded, or also entered, compared and moved to another system.
- How often the bot runs and how much data it handles.
- Whether login needs a second factor and how that will be handled.
- Where the result goes: Excel, Google Sheets, a CRM, accounting software or email.

### Additional costs

- Support is required because portals change: from €29/month (on a separate server we provide) or your own server.
- Fixes after portal changes – €50/hour or within the €129/month plan.
- If the output needs to be read by AI (for example, free-text documents), AI model API usage is billed at cost, with a cap.

## How long does it take to build an RPA bot?

One bot for one portal goes live in approximately 1–3 weeks after agreement and access. We test the first version on real data for a few days to catch the unusual cases too. Several portals or complex data matching take longer – we state the timeline in the quote.

| Work | Example | Price | Approximate timeline |
| --- | --- | --- | --- |
| One bot | downloading orders from a supplier portal into an online store | from €790 | 1–3 weeks |
| Several portals | status checks in 3 partner portals with notifications | after assessment | 1–3 weeks |
| Support | server, schedule, monitoring | from €29/month | monthly |
| Fix after a portal change | a new button or reordered fields | €50/hour | usually 1–2 working days |

## How we work

1. **Free assessment** (1–2 working days)
   You show us what your staff do in the portal. We check for an API or export, whether the terms allow automation, and tell you whether a bot is the right tool at all.
2. **Step-by-step spec and price** (1–2 working days)
   We write down every step, the exceptions and where the result goes. Price and timeline go into the contract; work starts once the 50% deposit is paid.
3. **Bot account and access** (1 working day)
   You create a dedicated bot account with the rights it needs and pass the passwords securely into the server vault.
4. **Programming** (3–10 working days)
   We write the bot, the log and the notifications, and set up the run schedule.
5. **Trial period** (2–5 working days)
   For a few days the bot works alongside your staff member and we compare the results.
6. **Launch and support** (12 months)
   We switch the bot to its schedule and keep an eye on it. For 12 months we fix programming faults free of charge, and when the portal changes we adapt the bot under your support plan.

## RPA, API or an AI agent? How to choose

| Criterion | API integration | RPA bot | AI agent |
| --- | --- | --- | --- |
| When to choose it | the system has an API or import | no API, but the portal interface is stable | free text has to be read or simple decisions made |
| How it works | systems exchange data directly | a bot repeats a person's actions in a browser | an AI model understands the task and uses tools or integrations |
| When the system changes | APIs change rarely and with notice | the bot needs fixing after a portal change | depends on the connections; answers need checking |
| Reliability | highest | good if the portal is stable | good with human approval |
| Price | after assessment; accounting integration – from €490 | from €790 | from €690 |
| Monthly costs | support from €29/month | support from €29/month plus fixes after portal changes | support from €29/month plus AI model usage |

## What can be automated: typical scenarios

These examples show how the solution works. They are not specific client cases – we don't name our clients.

### A supplier portal without an API

- **Situation:** For example, an online store logs in to a supplier's B2B portal every day, downloads prices and stock levels and updates its products by hand.
- **Solution:** Every morning the bot logs in, downloads the price list, compares it with the store's products and updates prices and stock. Large price jumps are flagged for review.
- **Outcome:** Fresh stock levels every morning with no manual work, plus a list of changes worth checking.

### Status checks across several portals

- **Situation:** For example, someone at a logistics or service company checks order or application statuses in different partner portals several times a day.
- **Solution:** The bot checks the statuses on a schedule, writes them to the CRM or Google Sheets and notifies the person responsible when a status changes.
- **Outcome:** One list with every status and alerts only when something changes.

### Reports from several systems

- **Situation:** For example, the manager expects a report every Monday that a staff member compiles from exports out of several online systems with no API.
- **Solution:** The bot downloads the exports from each system, merges them into one table and emails the report.
- **Outcome:** The report at the same time every week and hours freed up for your staff.

### Bank statements and payment matching

- **Situation:** For example, the accountant downloads the bank statement every day and checks by hand which invoices have been paid.
- **Solution:** First we check whether the bank offers an API or automatic statement export. If not, the bot downloads the statement once a staff member approves the login and matches payments to invoices.
- **Outcome:** A list of paid and overdue invoices without manual matching.

Show us what your staff do in the portal – we'll assess it for free

Tell us which portal or system the repetitive work happens in, how often and where the result goes. Within 1 working day we'll tell you whether a bot, an API or another approach fits and what it would cost.

## Frequently asked questions

### How much do an RPA bot and its support cost?

One bot for one portal costs from €790, with no licences needed. Support is from €29/month: server, scheduled runs and monitoring. Fixes after portal changes are €50/hour or included in the €129/month plan. No VAT is charged.

### How soon will the bot start working?

Approximately 1–3 weeks after agreement and access, including a trial period of a few days when the bot works alongside your staff member.

### Why not UiPath or Power Automate?

They are powerful platforms for large companies, but business licences are paid every year per bot or per user, and unattended runs on a server usually need pricier plans. For a small company with 1–3 bots, the licences often cost more than the work itself. Our bot is code: you pay for the build and support. If you already hold UiPath or Microsoft licences, it makes sense to use them.

### What happens when the portal changes?

The bot stops and reports an error – no data is lost or written incorrectly. We adapt the bot to the new version of the portal, typically in approximately 1–2 working days. That's why we only offer RPA bots together with support.

### Can you automate the VMI, Sodra or bank portals?

We look for the official route first: many government and banking services offer data exchange interfaces, file import or an API. If login needs Smart-ID or another second factor, a bot can't log in by itself – the only option is for a staff member to approve the login. We don't automate portals with CAPTCHA or a ban on automation. (VMI is the Lithuanian tax authority; Sodra is the social insurance fund.)

### Is it safe to give a bot our passwords?

We recommend a dedicated bot account with the minimum rights it needs. Passwords are kept in an encrypted vault on the server, never appear in the log, and you can revoke access at any time by changing the password.

## Related services

### [API integration](https://saitai.lt/en/services/integrations/api-integration/)

If the system has an API, connecting directly is more reliable – 1–3 weeks.

### [AI agents for business](https://saitai.lt/en/services/ai-solutions/ai-agents/)

When free text has to be read or simple decisions made – from €690.

### [n8n, Make and Zapier](https://saitai.lt/en/services/business-automation/n8n-make-zapier/)

When your systems have ready-made connectors – a no-code workflow, from €290.

### [AI solution support](https://saitai.lt/en/services/maintenance/ai-support/)

Server, monitoring and fixes when portals and systems change – from €29/month.
