Institute management
In daily use since 2020
Laravel · MySQL
I'm Kafi, a senior freelance developer. My robotic process automation services build bots in Python and Playwright that log in, read, copy and fill in systems that have no API, with logging, an exception queue and alerts, so the bot does the repetitive clicking and your team handles the exceptions.
Starting from $10/hr
Bot run · orders
1 exceptionROBOTIC PROCESS AUTOMATION
Robotic process automation is software that operates other software the way a person does: logging in, clicking, copying, pasting and filling forms. It is rule-based, so it is not AI on its own. When a language model reads a messy document or email before the bot acts, the combination is often called intelligent automation.
RPA is the right tool when a system has no API or the API does not cover the task, and the process is frequent and stable. It is the wrong tool for processes that change constantly, because bots depend on screens that can change.
Licensed RPA platforms suit large organisations that want a standard enterprise tool. For many small and mid-size businesses, a code-based bot in Python and Playwright is cheaper to run and easier to keep in your own hands. I will tell you honestly which fits.
| Code-based bots | Licensed RPA platform | |
|---|---|---|
| Licence cost | No per-bot licence | Platform licences |
| Flexibility | Any logic or integration in code | Within the platform’s blocks |
| Maintenance | Normal code, tests and version control | Platform-specific skills |
| Scale across a company | You manage it yourself | Built-in orchestration |
| Best for | Small and mid-size teams | Large enterprise programmes |
WHAT IS AN RPA SERVICE?
RPA stands for robotic process automation: software bots that operate other software the way a person would, by clicking, typing and copying. An RPA service builds and runs those bots for you. A general guide:
| RPA bot | API integration | AI automation | More staff | |
|---|---|---|---|---|
| How it works | Drives the screen of an existing tool | Systems exchange data directly | A model reads and decides | People do the task |
| Reliability | Breaks when screens change | Stable | Needs checks and approvals | Variable |
| Best for | Tools with no API | Tools with an API | Unstructured input | Judgement-heavy work |
WHAT I BUILD
Bots for the repetitive screen work that eats hours, built so someone else can maintain them.
Bots that log in to supplier, government or partner portals, download files and enter data.
Playwright · Portals
Records typed from spreadsheets, emails or PDFs into a system that has no import feature.
Forms · Entry
Reports pulled from several systems on a schedule and combined into one file or dashboard.
Reports · Schedules
Documents read with OCR and a language model, checked, and keyed into your finance or ERP system.
OCR · Finance
Old web or desktop systems operated by a bot while a proper integration is planned.
Legacy · Bridge
Orders, claims or support tickets read, validated and moved through your systems.
Orders · Tickets
Two data sources compared, differences flagged and routine matches closed automatically.
Reconciliation
Bots that check pages, prices or statuses on a schedule and alert you to changes.
Monitoring
Language-model steps for messy inputs, with rules and human approval around them.
AI · Approval
A simple screen showing what the bot did, what it skipped and what needs a person.
Dashboards
Fixes when a website or screen changes, with tests that catch the break early.
Maintenance
Replacing fragile bots with direct integrations where an API becomes available.
Migration
Describe what you want to build. I'll reply within a few hours and tell you honestly what it would take.
USE CASES
Pulling statements, entering invoices and reconciling records.
Moving job, quote and compliance data between systems.
Updating marketplaces, supplier portals and shipping tools.
Scheduling and paperwork steps. Regulated data goes through your own compliance review.
Tracking, booking and document handling.
Collecting data from tools without APIs.
HOW IT RUNS
Stable processes first, with exceptions planned from day one.
We record how a person does it today, including the exceptions.
Stable, frequent and rule-based, or an API that makes a bot unnecessary.
Playwright or Python, with secure credentials and clear logging.
What the bot skips, flags or sends to a person.
The bot and a person do the same work until results match.
Scheduled runs with alerts and a fix plan when screens change.
RISKS
Monitoring and alerts, and a switch to an API when one exists.
Unusual cases are logged and sent to a person instead of failing quietly.
Secrets stored safely, with minimal permissions.
Bots respect the terms of the tools they use.
A maintenance option and documentation.
A short audit before building.
TOOLS
Open tools, so no one is locked in.
PROOF
Real products in production, described without client names. Each one started with a conversation like the one you're about to have.
In daily use since 2020
Laravel · MySQL
Member, plot and transaction management in 2 weeks
Laravel
Manual admin work cut by 80–85%
Laravel · MySQL
FOR US BUSINESSES
I build code-based bots with Python and Playwright, so there are no per-bot licence fees. I work from Dhaka (GMT+6) with overlap hours, in US dollars from $10 per hour.
Price depends on the number of systems and screens, how often the bot runs, exception handling and monitoring. See also business process automation and workflow automation.
COST & TIMELINE
It depends on how many systems the bot touches, how stable those screens are and how many exceptions there are. A bot for one portal is a modest job; a bot spanning several systems with an exception dashboard is larger. You get a written estimate after a short call, and hourly work starts at $10 when you hire me directly.
Running costs are usually small: a server, and sometimes proxy or document-processing fees, billed to your accounts at cost.
Each system needs its own login handling and tests.
Frequently changing screens mean more maintenance.
More edge cases mean more design and testing.
Strict credential and access rules add setup.
Large daily volumes need queues and monitoring.
WHO IT'S FOR
Where bots give the clearest payback.
PRICING & PLATFORMS
Work with me directly for the best rate, or through Upwork or Fiverr if you want the platform's payment protection.
From $10/hr
Upwork
Fiverr
Long-term work starts at $10 per hour. Every project gets a written estimate before it starts, so there are no surprises.
FAQ · 12 QUESTIONS
Still unsure? Book a free call and ask me directly. I'll tell you honestly if I'm the right fit.
It is software that operates other software the way a person does, logging in, clicking, copying and filling forms, to carry out repetitive, rule-based tasks.
A bot is given the steps of a process and credentials. It opens the system, performs the steps on each item, logs the result and sends anything it cannot handle to a person for review.
Not by itself. RPA follows fixed rules. When a language model reads messy input before the bot acts, the combination is often called intelligent automation.
RPA does rule-based screen work. Intelligent automation adds AI for tasks such as reading documents, classifying requests or judging unclear input, usually with human review.
Pick a stable, frequent process, watch how it is done, build the bot with logging and an exception queue, run it side by side with a person, then switch over and monitor it.
I write it in Python with Playwright or similar tools, store credentials securely, add logging and retries, and test it on real examples. No licensed platform is required.
It removes repetitive data entry and copy-and-paste work from systems that cannot be integrated directly, saving time and reducing typing errors.
It depends on the systems, screen stability and exceptions. I give a written estimate after a short call, and hourly work starts at $10 when you hire me directly.
Not necessarily. Licensed platforms suit large organisations that want standard tooling. For smaller teams, code-based bots are often cheaper to run, and I will say honestly which fits you.
The technique applies to admin work such as scheduling and claims, but rules about regulated data vary and I am not a compliance authority. Your own compliance review decides what a bot may touch.
The bot fails visibly: it logs a screenshot and alerts you. I update it, and optional monthly maintenance covers these fixes. Where an API exists, I recommend replacing the bot with a direct integration.
You do. The code, documentation and credentials setup are handed over, and the bot runs on your server or account.
Tell me what you're building and where you're stuck. You'll get an honest plan, timeline and estimate, even if I'm not the right fit.