Automation
RPA: robotic process automation
Overview
Automate desktop and browser tasks using tools like UiPath or Automation Anywhere (data scraping, form filling, report generation).
Delivery
RPA: robotic process automation Delivery Process
Discover
We map your business, your users, and what winning looks like before a single pixel.
Design
Direction, identity, and interfaces: shared early and reviewed with you at every step.
Build
Engineering in weekly slices you can see, click, and comment on as they land.
Launch
QA, performance, SEO, and deployment handled end to end. Nothing left to chance.
Grow
Support, iteration, and new capabilities as your business scales beyond launch day.
Details
Typical timeline
Per bot or process
Best for
Deliverables & Scope
- → A written process map of the task being automated, showing every step, decision point, input and output before any code is written
- → Working bots built in UiPath, Automation Anywhere or Python with Selenium, depending on which fits your existing licence and IT rules
- → Scheduled unattended runs with retry logic, error screenshots and a log file you can read without a developer
- → A dry-run period on your real data with a side-by-side accuracy comparison against the manual process
- → Documentation, a runbook for your operations team, and a recorded training session on restarting and troubleshooting the bot
Post-Delivery
- → 30-Day Bug Warranty
- → Source Files & Ownership
- → Handover Training Session
Investment
RPA: robotic process automation Investment & Pricing
Indicative starting ranges - every project is quoted to its real scope.
FAQ
RPA: robotic process automation FAQs
How much does RPA cost per process or bot?
Most single-process bots land between $3,000 and $15,000 USD, or A$4,500 to A$20,000. Simple form-filling or report-download bots sit near the bottom. Bots that touch multiple systems, handle unstructured documents or need OCR and exception queues sit higher. We quote per process, so if you want three bots you get three line items and can stage them across budgets.
How long does it take to automate a process?
A single well-documented process takes 3 to 6 weeks. The first two weeks go on discovery and recording the manual steps, because automation fails on processes nobody has fully written down. Processes with heavy exceptions, scanned documents or unstable third-party screens take 8 to 12 weeks. We will tell you in week one if your process is a bad fit rather than discovering it in week six.
Who owns the bot and the automation code?
You own the automation project files, the source code and the documentation outright. If we build in your UiPath or Automation Anywhere tenant, everything lives in your account from day one. If we build standalone Python, we hand over the repository. No runtime licence fees go to us, though you may still need to pay the RPA vendor for their own platform licence.
What happens after the bot goes live, and is support included?
We include 30 days of bug fixing after go-live. If the bot misreads a field or crashes on a record type we should have handled, we fix it free. When the target website changes its layout or your ERP gets an upgrade, that is maintenance work, not a bug, and it gets quoted separately. Most clients take a small monthly retainer for exactly that reason.
Should we use a licensed RPA tool or custom code?
Licensed tools like UiPath and Automation Anywhere win when you have an IT team, compliance requirements and many bots to manage centrally. Custom Python is cheaper and faster for one or two processes, and there is no per-bot licence. The tradeoff is real: custom code has no visual orchestrator, so your operations team cannot edit it without a developer. We will recommend against an expensive platform licence if you only need one bot.
What happens when the target website or app changes its interface?
The bot breaks, and that is a genuine limitation of RPA rather than something we can design away. Bots drive interfaces the way a person does, so a moved button or renamed field stops the run. We build in stable selectors, fallback locators and alerting so you find out within minutes rather than at month end. Repairs typically take a few hours, but they are recurring and should be budgeted for.
Paired Services
Complementary Services for RPA: robotic process automation
Ready to start your project?
Start this project