What is our primary use case?
I am a service provider and developer who implements UiPath for our clients. But in the company that I work for, we also use UiPath to make invoices for ourselves and, mainly, for payroll activities.
We need to get reports from our HR tool and combine them with another source of information where employees are recording the hours they spent with various clients. We then create the documents needed for the IRS. In our case, all the users of UiPath are data entry specialists in different departments, such as HR, finances, and marketing.
How has it helped my organization?
UiPath definitely helps reduce the cost of digital transformation.
It also reduces human error. We can be sure, given that our test case is successful, that there are no errors when none are reported. This definitely helps businesses. Errors generally lead to work being postponed. When errors come back to someone at a given point in time, they can rapidly overwhelm that person. With automation working, this is no longer the case because everything is smooth. And if there are errors, they will resolve them one by one.
In addition, it definitely frees up employee time. That is the purpose of automation. Unfortunately, I can't share metrics about this. But the additional time enables employees to focus on more important work and that affects employee satisfaction. Repetitive tasks make people irritated about the nature of their work. When they can work on new tasks that are more complex and creative, it makes an impact on their job satisfaction.
UiPath saves costs in our organization because we don't have errors where it is deployed and because it has reduced the number of FTEs who do repetitive tasks. On average, within a small company, it can save up to 10 FTEs.
What is most valuable?
One of the most valuable features is that UiPath is easy to deploy, especially for medium-sized companies. It is also easy to scale.
Also, the fact that you can scale automations without having to pay attention to the infrastructure for doing so is quite critical. The infrastructure could require a lot of maintenance resources and affect costs, so that feature is quite important.
UiPath enables you to implement end-to-end automation, with its full range of tools, starting from Automation Hub, which is the initial point for gathering your processes from business lines. It's driven from employees or a center of excellence, and goes on to include implementation, and the reporting in Orchestrator is quite powerful as well. The end-to-end coverage is important, as clients always like one tool that covers their needs and plans.
What needs improvement?
The only thing missing is something to track the development cycle. We use third-party tools to do that. That is the only gap in UiPath.
Also, scheduling of UiPath robots could be improved. Scheduling is a feature for defining in what sequence, and on what machines, you want your automations to be launched. That area could be improved.
Buyer's Guide
UiPath
March 2025
Learn what your peers think about UiPath. Get advice and tips from experienced pros sharing their opinions. Updated: March 2025.
849,190 professionals have used our research since 2012.
For how long have I used the solution?
I have been using UiPath for more than three years.
What do I think about the stability of the solution?
Overall, the stability of UiPath is about average. We do have some instability, because of workloads that are too massive for Orchestrator, but it could be that it was not installed in the right way.
What do I think about the scalability of the solution?
Scalability is connected to the stability. The situation I noted when talking about the stability of UiPath happened for our largest client, where they already have 160 processes running. There are problems with the maintenance of such a large number of bots.
But in terms of increasing our usage, we are in a phase with our clients in which we are constantly enlarging the automation within their companies.
How are customer service and support?
UiPath support is definitely willing to help. They will usually propose a call, if they think that will be easier for solving an issue. Their services are quite good.
Which solution did I use previously and why did I switch?
We did not have a previous solution, except for Excel macros.
How was the initial setup?
It is relatively easy to deploy. Of course, it's not as straightforward as a simple application installation, but with the help of UiPath, in particular, or with the help of the UiPath Community Forum, which is quite enhanced with answers about installation, it's not a big deal to install it.
Taking into consideration internal IT restriction and internal IT resources, deployment can take up to two weeks.
Our deployment strategy usually involves convincing clients that they need to start setting up a center of excellence for automation and then there are lots of initiatives that need to be undertaken within the center of excellence. Among the most critical are awareness, dealing with IT stakeholders, and of course, the capabilities of developers. Taking care of those things will lead you to a smooth path for digitizing the first processes, which are low-hanging fruit. The further you go, the more you can then enhance your automation with the more advanced capabilities, like AI, Document Understanding, or chat bots, et cetera.
Deployment of one robot takes about three months and up to five people. We need an SME who knows the process that is being automated. In addition, there is usually a business analyst who tries to help optimize the process so that it will work better with robots. We need a developer, of course, and we usually have a data solution architect who helps to ensure that overall infrastructure is functioning. It also helps to have an automation evangelist on the business side.
We have two roles for UiPath maintenance. One is the IT maintenance guy who makes sure the VM is working correctly, and that we can easily scale from the infrastructure perspective. The second role is the operator, whose day-to-day tasks include scheduling the bots correctly, implementing quick deployments by creating assets in Orchestrator, and maintaining things from an RPA perspective.
What was our ROI?
ROI usually takes six to 12 months.
What's my experience with pricing, setup cost, and licensing?
Licensing is quite complex, and sometimes that's true even when we have to explain it to our customers. There may not be a way to do it more simply.
The only potential additional cost when implementing UiPath involves the third-party tools. It can be a quite big portion, of course, so you should consider that aspect. Examples would be integrating different systems within a company, systems such as Salesforce, SAP, or ServiceNow; all of the main CRMs that businesses use.
Which other solutions did I evaluate?
We looked at the main competitors, Blue Prism and Automation Anywhere. The decision to go with UiPath was based on contacts we have, clients who had already implemented RPA. We got better feedback about UiPath from them.
What other advice do I have?
The first thing to consider within your organization is whether it's easier to deploy it on-prem or via the cloud version. Then focus on how to structure your development team. It can be either entirely a third-party service provider, or in-house developers, or it could be a hybrid. The third thing to consider is what the cost center will be for RPA implementation in your company.
The marketing side of how easily you can build automations with UiPath is a bit exaggerated. You definitely need some programming skills to do very powerful automations with it. But it still provides various levels of development tools, meaning that you could have zero programming experience and still automate some processes in your company.
UiPath is definitely the market leader in RPA. The biggest lesson I have learned from using it is to start with the low-hanging fruit, and then go on to more complex stuff.
Which deployment model are you using for this solution?
On-premises
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor. The reviewer's company has a business relationship with this vendor other than being a customer: Partner