RPA development
We have a manual process that needs automating
You have identified a manual process that suits automation but need help with all or part of the development. We do not only advise on how to build it yourselves. When it makes sense, we take responsibility for the development and get the robot into production.
Does this sound familiar?
Someone in finance, HR, or administration spends hours every week on the same thing: Moving data from one system to another, fetching receipts, keying the same information in twice, sending the same emails. The rules are known, and everyone agrees it should be a robot.
But nobody has the time or experience to build it. Power Automate Desktop may be installed, but no environment has been set up for unattended runs, and nobody knows how the robot should handle errors at three in the morning.
This is often not a large transformation project. A well-scoped automation can remove one specific recurring task, provided it is built properly and put into production.
Anders on the task
Anders Jensen
Microsoft MVP and UiPath MVP
We do not only advise on how to build it yourselves. When it makes sense, we take responsibility for the development itself and get the solution into production. And you keep full ownership of the robot.
What an RPA project can include
We work primarily in Power Automate Desktop and Power Automate cloud flows, and we can take on every step or only the ones you are missing.
From process to robot in production
- Setting up the Power Automate Desktop environment, including the VM and the technical setup for unattended runs.
- Analysing and designing the process, so the robot is built on the right version of the workflow.
- Developing one or more robots.
- Testing with the people who know the process, and fixes based on what they find.
- Error handling and logging, so you can see what the robot did and when it failed.
- Go-live and handover.
- Ongoing support and further development as the process changes.
Automating finance and accounting processes
Finance departments and accounting firms have many uniform routines where the rules are known but the work is still done by hand. They often make the best first robots.
- Mapping the existing process as it is performed today.
- Developing Power Automate solutions for specific accounting or payroll routines.
- Testing and handover to the staff who will use the robot.
- Subsequent changes and troubleshooting when systems or rules change.
How we have helped others
The examples are anonymised, and the figures describe the size of the job, not a calculated saving.
-
Complete RPA programme in the public sector
A programme of more than 120 hours covering environment and VM setup, three separate robot areas, testing, fixes, and go-live. From an empty environment to robots in production.
-
Three robots from idea to production in about a month
Three robots in an administrative process, developed, tested, and put into production in about a month, including error handling and handover.
-
Automations for an accounting firm
Several Power Automate solutions developed and delivered to an accounting firm, including later changes to payroll routines and troubleshooting when the systems changed.
Price and format
It starts with a short call: Which process, which systems, and what the robot needs to do. From there we assess the scope and propose an hour package with an RPA specialist from our network, who builds with you or for you. If you would rather learn to build yourselves, a workshop day or our Power Automate Desktop company course is a good place to start.
Recommended: With an approved specialist
Hour package
from DKK 29,500 excl. VAT
See all prices, programs, and termsWrite to us
Briefly describe what you want to achieve, or what is causing trouble. You know the price level up front, and we reply within 24 hours.
Message sent.
We reply within 24 hours. A receipt is on its way to your inbox.
Frequently asked questions
How long does it take to build a robot?
It depends on the process and the systems. A well-scoped robot can be in production within a few weeks. A programme with several robots and a new environment can run over a couple of months. We give an estimate after the initial call, not before.
Do we need a virtual machine for the robot?
For unattended runs, where the robot works without a person at the screen, yes. We help set up the VM and the Power Automate Desktop environment so the robot runs on schedule and reliably.
Do you build for us, or with us?
Both. In most cases we guide you while you build, so the knowledge stays in-house. If there is nobody to build, we build for you and hand over the solution with documentation.
What happens when the process changes?
Robots need maintenance when systems are updated or rules change. That is why we build in error handling and logging from the start, and many clients keep an hour package for changes and troubleshooting.
Proudly working with
