We are partners with UiPath and Automation Anywhere. We use this solution for IT services and for the education sector.
Associate Director at Techwave.
Automation platform that offers good ROI but could be improved with enhanced OCR functionality
Pros and Cons
- "The return on investment is really good"
- "The OCR functionality for this solution could be improved. It should have a better capability to read unstructured documents. The next generation of OCR is ICR and UiPath does not have this. This would enable us to read and search through documents."
What is our primary use case?
How has it helped my organization?
OCR Tesseract, by default, is the good OCR search engine to extract data from a digital PDF. For any Unstructured document with a normal noise, background letters, either UiPath Document Understanding or AbbyyReader fails to extract the exact values. Very difficult to depend on Computer Vision too as a third party tool for small to mid-range business purpose. Hence, a combination of AI/ML with a good OCR Engine is required for UiPath to go forward.
What is most valuable?
UiPath Orchestrator is definitely a plus point in the product. This helps in all formats of UiPath version ranging from PoC till Product Deployment.
What needs improvement?
The OCR functionality for this solution could be improved. It should have a better capability to read unstructured documents. The next generation of OCR is ICR and UiPath does not have this. This would enable us to read and search through documents.
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.
845,406 professionals have used our research since 2012.
For how long have I used the solution?
We have used this solution for two years.
What do I think about the stability of the solution?
This is a stable solution.
What do I think about the scalability of the solution?
This is a scalable solution.
How are customer service and support?
The technical support is not that satisfactory. We have to find the answers by ourselves through non-community groups.
How would you rate customer service and support?
Neutral
How was the initial setup?
The initial setup is straightforward and the deployment was easy.
What about the implementation team?
It was implemented in-house.
What was our ROI?
The return on investment is really good. I would rate it a three out of five.
What's my experience with pricing, setup cost, and licensing?
We're an official partner of both AA and UiPath and both of them carry the same weight with a very marginal difference but there is a difference in cost. Currently our clients are looking for cost optimization post-pandemic and UiPath comes at a high price point.
What other advice do I have?
I would rate this solution a six out of ten.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Disclosure: My company has a business relationship with this vendor other than being a customer: Customer/Partner/Reseller

Software Development Engineer at a tech vendor with 1,001-5,000 employees
Enabled us to develop a chatbot for our website via drag-and-drop, without language-specific coding skills
Pros and Cons
- "Designing a chatbot would usually require some language coding and it would have to be deployed with certain front-end languages. But UiPath gives us the ability to automate this functionality with drag-and-drop features. That is the very best part, where UiPath is doing an amazing job."
- "One thing I don't like about UiPath is that it does not have a very good user interface for a newbie. It's not that the user interface itself is bad, but when I started using it, it was very difficult for me to understand the tool and how to use it... The user interface should be a little simpler than it is right now, as it is very complex."
What is our primary use case?
We have deployed a chatbot in our system.
How has it helped my organization?
Designing a chatbot would usually require some language coding and it would have to be deployed with certain front-end languages. But UiPath gives us the ability to automate this functionality with drag-and-drop features. That is the very best part, where UiPath is doing an amazing job. It doesn't require any language coding or front-end coding to create the user interface.
Because it is easy to use, it saves a lot of time for the developer. When it comes to programming, UiPath has made all the manual work, such as verifying and correcting errors, and even repeating processes, less complex and less time-consuming. If you were to try to choose a coding language and use it to streamline things and design a bot for automation, it would take more time. Doing that would take 15 days to learn the language and to code with it. There would be a certain number of errors that you would have to deal with, as well. There might also be a backend required. UiPath can easily save you 10 to 15 days, automating in two to three days, maximum.
It gives you the ability to automate workflows and large processes that would take a long time to do manually. With the help of UiPath, the time it takes to get those tasks done is reduced and it reduces human error. In addition, it saves you money because you don't need to hire people for the tasks that have been automated.
There is also the benefit of not having to hire an engineer to program things. If you had to hire an engineer there would be the expectation of a payment package. There would also be the time spent on dealing with errors the engineer makes, and this person might also require mentors. UiPath decreases the spending of time, energy, and money, especially.
UiPath also saves our organization time because the automation cloud handles infrastructure, maintenance, and updates.
What is most valuable?
One of the most valuable features is that it provides you with the ability to learn the system and understand the concepts through specific demos. UiPath provides you with education, through the UiPath Academy, on the basics of how to use the software and for what purposes you can use it. It is a very good thing that they provide education with it. That makes it easy for us, as developers, to gain the knowledge we need.
Another good feature is that it comes with an embedded recording functionality. You didn't require an external screen recorder. The embedded screen recorder enables you to record things so that you can remember them over time.
In general, it is easy to build automations using UiPath. You just drag and drop according to your needs, and you can automate things in a single go.
What needs improvement?
One thing I don't like about UiPath is that it does not have a very good user interface for a newbie. It's not that the user interface itself is bad, but when I started using it, it was very difficult for me to understand the tool and how to use it. It has N functionalities and a user has to learn the particular things that these functionalities are used for.
The user interface should be a little simpler than it is right now, as it is very complex.
For how long have I used the solution?
I have been using UiPath for more than a year.
What do I think about the scalability of the solution?
In terms of scalability, this software can grow with the industry, especially since more companies are focusing on automation. Here in India, for example, there are many companies, like KPMG, focusing on the field of automation. Software like this can help them to scale more and more in building their automations. The software can really scale up well, as long as the user interface is improved.
How are customer service and support?
Their support system is very good. If you have a problem and you reach out to their support system, they are quick to reply. Problems are solved within 24 hours of reaching out to them.
Also, you can use the UiPath user community instead of contacting support. There is value to the user community because people help each other there. Because we are concentrating on development in my company, we tend to not be as active on the community side, but whenever we do use it we get help from them.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
I have only been exposed to this software. I graduated and started working in the RPA domain by using this software.
How was the initial setup?
It wasn't that complicated to set up.
What's my experience with pricing, setup cost, and licensing?
The pricing and licensing are pretty decent. If you are using it as an automation developer, it comes in at under $500 a month. Still, the pricing can be reduced, but the service and functionality are solid.
I have heard from some of my colleagues that there are many subdivisions of the pricing and some of them are between $1,500 and $2,000 a month. That is expensive. But overall, my colleagues say it is a cost-effective program in the long run.
What other advice do I have?
If you are working in the RPA domain as an automation developer, you should look at UiPath because it gives you many functionalities. Also, the education aspect of UiPath is a very cool feature because you don't need to rely on other software to learn it. Thirdly, the bot-building process is very smooth.
UiPath is a fast, time-saving, money-saving, energy-saving solution. Using UiPath has been the best experience. I would recommend it. You can choose this software without any second thoughts. It can provide a good return on investment to your business.
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.
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.
845,406 professionals have used our research since 2012.
Automation Engineering Manager at a computer software company with 51-200 employees
Saves costs, makes it easy to build automations, and reduces human error
Pros and Cons
- "UiPath saves costs for our customers’ organizations. That would just be the cost savings from RPA bots. I haven't really dug into the cost savings of the ancillary products, however. I know that one of my clients is using the test suite now after I had built a proof of concept for it, and they've fully implemented it. I'm sure there's going to be a lot of cost savings there as well."
- "The license model changing every year can be a little bit frustrating. It's hard sometimes when things go from being robot-based to being runtime-based."
What is our primary use case?
We primarily use the solution for legacy data transfer, UI automation, CRM and ITSM automation, and call centers. Specifically, in call centers, using UiPath forms and form render has been really helpful.
What is most valuable?
I love developing in Studio. For my clients, the approachability of the orchestrator is really valuable. It takes a little bit to learn the licensing structure and layout at first, however, once they get it, it's pretty smooth sailing from there. The modern folders have become a great thing for any enterprise that's looking to automate using an orchestrator as a server.
I like to automate in Studio as I'm familiar with it. I honestly just like the platform so I like automating with Studio.
I really enjoy Document Understanding. I like how it all integrates together. Some of the stuff I've seen now with just the connectors and the way you can scale implementations is really exciting. While I do like Studio, I also like how it works with the rest of the platform.
We most recently built an unintended bot that saves them about $500,000 a year worth of GS 14 labor.
UiPath saves costs for our customers’ organizations. That would just be the cost savings from RPA bots. I haven't really dug into the cost savings of the ancillary products, however. I know that one of my clients is using the test suite now after I had built a proof of concept for it, and they've fully implemented it. I'm sure there's going to be a lot of cost savings there as well.
In terms of ease of building automation, it depends on the process. For anything that's ultra-low or a low-level complexity, it's very simple. Once you start getting sprawled out into larger automation that very much becomes object-oriented programming and is basically making a workflow. That's when you really need to take hold of programmatic concepts. You need to be a strong scriptor to be able to make the best RPA bots.
Our clients have reduced human error. That's one of the things that I tend to talk about the most. The bots can get work done faster, however, the reduction of human error is probably more valuable in some cases than just speeding up work.
In terms of UiPath Academy, everybody's used it. I've used it myself. My entire team has used it. All of our engineers are some sort of Pearson VUE certified now. Most of us have the Advanced Developer. A few of our younger junior developers have the associate, the RPA associate, however, they're working on getting the Advanced Developer and they lean on the Academy pretty heavily.
The biggest value in the Academy is the videos, which are pretty helpful. Sometimes you have to slow it down, however, for the most part, the way it goes through concepts, especially for somebody that doesn't have much programming experience, the videos tend to go through some of the more elementary things like variables arguments. That can get a little bit boring for programmers since they've been through that 100 different times. That said, that’s really where the strength lies as it does target a large group of different employees. As an engineer, I might pass by some of the boring stuff, however, I will still find things later on in the training where I'm like, wow, I actually never knew that.
What needs improvement?
The license model changing every year can be a little bit frustrating. It's hard sometimes when things go from being robot-based to being runtime-based.
Some federal users are still on the 2019 orchestrator or even a 2018 orchestrator. However, by being on them, they can't take advantage of modern folders. This issue is, once they get upgraded to 2020, and they start using modern folders, essentially you shouldn't really be using plastic folders anymore. Some of their frustrations aren't really long-term frustrations. Orchestrators have gotten really popular over the last few years. There are certain things that have made it so much better. That said, we're still in that transition where clients have been using classic folders and then they upgrade and they're going to have to change everything. Hopefully, they don't have to do it more than when they upgrade past 2020.
One of my clients upgraded their production environment from the 2019 orchestrator to the 2020 and everything was in plastic folders and I advised them to switch to modern folders and it was a pain. Once it was taken care of, it was great. It's just that it took a lot of convincing to tell them why it was better.
For how long have I used the solution?
I've been using the solution for three years.
What do I think about the stability of the solution?
It's pretty stable. The biggest issue is just that more companies need to really adopt a change management system, whether that's through Service Now or is built-in change management, those alerts need to be going to the RPA center of excellence.
There are things that will change or break the UiPath bot sometimes. They're very stable and they've become more stable if there's a change management system. Automated testing can make it so you can catch things that have changed with applications with RPA testing before they've occurred and then you can fix things quickly.
What do I think about the scalability of the solution?
The scalability was tough a few years ago, however, now it's exponentially easier with modern folders and the orchestrator.
How are customer service and support?
I've worked with UiPath support. I would put them at a seven out of ten as they need to be a little bit more timely. There have been issues with a client where support has taken a really long time to get back to us or they haven't updated our support ticket, even though we've advanced. Maybe it was an isolated incident. I have worked with support before where that hasn't happened. I felt like I got in a bad run of working with the support folks and the client was definitely not pleased.
Which solution did I use previously and why did I switch?
I actually don't have experience with other RPA solutions. I came from a web development background and I went straight into UiPath and now the way that it's scaled out and now that I work in the federal government, UiPath has such a large piece of the market share. I've never really seen a need to learn any other automation solutions. I may learn Power Automate at some point, however, I would really prefer to stick with UiPath.
How was the initial setup?
The solution is pretty straightforward. I've run through complex issues, mostly the NuGet package and it's different with every customer. As far as the UiPath platform goes, it's pretty straightforward to deploy bots. It all depends on how an agency has its group policies set up for security and sometimes that causes issues. It's just about learning new ways to solve different problems that may be unique to an agency or may not be.
In the government, deployment takes a little longer. I would like to think development usually doesn't take that long, however, it's like going through ATO, especially if it's an unintended bot. Sometimes it can take like a few months. It just depends if they've got a center of excellence stood up or not. For example, if they've got an CI/CD pipeline or just a standard development life cycle, a lot of people don't have that set up and then it ends up taking longer as they have to go through ATO. It’s variable. Unfortunately, it's just a lot slower to get them deployed than in the private sector I think.
That’s no fault of UiPath. It's usually group policy security systems and things like that. I've had to talk to a lot of security folks and help walk them through things that need to be changed.
What about the implementation team?
We've been implementing our UiPath as well.
What's my experience with pricing, setup cost, and licensing?
I don't really have too much to offer about the pricing part of it. I don't really work on that side of the business. I would say my only gripe about the pricing would be something like a Studio Pro license being more expensive than a Studio license, just to essentially get something that links Test Manager. Some people might've found that a little bit hard to swallow. From what I've heard, Studio Pro is going away and Test Manager is just going to come into Studio. That would be the only thing I've noticed that I thought was a little silly. Everything else is typically not really my side of the business.
What other advice do I have?
We have everything on-prem in our demo environment and the customers I work with typically have the on-prem offerings as well.
I have used UI path apps in our demo environment. I do not have any clients that are using it.
We have an AI center in our demo environment, however, I don't have any clients that are using it. I do have a client that's actually in the process of installing it right now and getting it through their governance model. That's as close as it would've come for our customers using the AI center.
To those considering UiPath, I would say, just go ahead and do it. RPA is pretty awesome. It's easy to get solutions out. There still needs to be a good bit of work done on the Citizen Developer Model, however, at the same time, as far as getting a team of engineers in there to automate things, if you get good RPA developers, you can get things automated really quickly. People can help you with your standard development life cycle. You just need to jump in.
I would rate UiPath solutions at a nine out of ten. The only reason I wouldn't give it a 10 is that, in terms of the installation of the product, sometimes the documentation leaves a lot to be desired. Sometimes it's tough to work through installation issues without actually contacting support. I do wish that was a little bit more streamlined.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Senior software engineer at a financial services firm with 10,001+ employees
Helps to minimize our on-premises footprint and makes it easy to build processes
Pros and Cons
- "Previously, nobody could automate the process. The design and implementation allowed clients to handle their own data, for example, for transfers and items like that. We were able to digitize entirely from end to end. Now, the customer doesn't have to come to the bank and they don't need a pen and paper. They just have to log on and fill out the details of their request."
- "While the solution speeds up the cost of digital transformation, doing so requires expensive or complex application upgrades or IT app support."
What is our primary use case?
I work for a banking company. We use UiPath for tracing and collecting customer's credit information.
We also use it to deploy a bot when clients have specific requests for changes to their information or accounts. We're able to change their service via these requests. We can also remove some processes of manual intervention.
We've deployed bots across various processes. We have been able to remove human intervention for multiple processes and have seen a general improvement in terms of cost-effectiveness.
We used to handle dashboards manually. Now we've turned customers into kind of specialists in that, whenever they want to change something, such as adding debit, or opening/closing accounts, changing addresses, et cetera, they can handle it. They no longer have to push that request through us and have us intervene. They can do it themselves using the bots.
How has it helped my organization?
Previously, nobody could automate the process. The design and implementation allowed clients to handle their own data, for example, for transfers and items like that. We were able to digitize entirely from end to end. Now, the customer doesn't have to come to the bank and they don't need a pen and paper. They just have to log on and fill out the details of their request. Being able to share this new data is important. If there are manual aspects, we can now handle them for the customer. We don't have to have them worry about doing tasks manually.
What is most valuable?
We can use browsers like Internet Explorer for our automation. However, we've been able to use Excel as well with just a few hiccups in the beginning. UiPath really helped us with this change by disabling some elements at the managerial level. It was a big learning experience for us.
We are able to use codes to do a lot of checking to see that we are getting enough data and that we are able to filter it correctly.
The ease of building a process is pretty good and simplifies things. Normally it takes three to four hours to complete a process. That includes everything, including generating reports and sending the data. There are, of course, multiple steps involved in the process. We've gotten that down to about six minutes. We're able to better focus the work and, at the same time, we're able to use a lot of bots to get things done.
We can scale the solution well. We've already deployed four more bots for various processes. We're actually able to have good control of each bot. We're able to put things into a proper standard format and then send the information where it needs to go without having to handle the process manually. It would go so much slower without the bots in place without having to go back to the customer. There's no longer a needs to do anything manually here. There was a concern that customers would not be able to manage the process that's automated by the bots, however, in the end, everything was clear and it was easily handled.
The solution enables us to implement end-to-end automation, starting with process analysis, then robot building, and finally monitoring automation. We're involved from the very beginning to design the process from step one. We're able to test everything out before moving to production and that allows us to make sure everything works. End-to-end coverage is first and foremost. The visibility we have is really powerful.
We were able to deploy in parts, as we didn't have global production. At first, we didn't know how to manage everything. Once we went live, however, we were able to monitor it all. We could send reports to show what was happening, and if there were any concerns, we could go and directly look at those areas.
The solution helped to minimize our on-premises footprint. I always look for capabilities to deploy from the cloud. It changes as the customer needs to decide how to ultimately deploy. However, the cloud is able to handle anything an on-prem option would. We are able to handle the entire volume using one cloud. Our bots are able to be on the cloud and online.
Attended automation has helped to scale RPA benefits in our organization by automating department roles and specific processes that require human/robot collaboration. Previously, we were concerned with data loss and not being able to attend to the browser. We were not able to do even the simpler stuff.
We were able to upgrade to an updated version, from 19.4 to 20.4 which had some more UI and automation. We were able to upscale our entire quota. We're able to do workarounds if we need to.
We can speed up our automation processes and automate faster with UiPath.
The automation cloud offering helps to decrease the solution's total cost of ownership by taking care of items such as infrastructure maintenance and updates.
The solution speeds up the cost of digital transformation.
The solution has reduced human error. We've been able to reduce errors and have gotten more quality data instead of just more data. That way, if there is a mistake or something goes wrong, we can check the error against the quality data and resolve issues more effectively.
It has also freed up our employee's time. They can better deliver on big and innovative processes. We used to handle a lot of high volume tasks at the end of the month mostly and that's since tapered off. We'll have to see at the end of this month how much time savings we've accumulated.
Our employees can now focus on more high-value work. Employee satisfaction is high as well. In a bank, we do have a high volume of transactions every month, and previously, each would have to be checked and verified and balanced by someone manually - even if most would be dismissed as canceled transactions, et cetera. With automation, our employees no longer have to look at everything themselves. They can be wiser about what interventions they have to make every month.
Overall, the solution has reduced the cost of our automation operations. As a developer, I cannot speak to exact amounts, however, as that's handled more by project managers.
So far, the solution has saved the company costs. We're very customer-focused in our organization. Deploying these kinds of innovative solutions allows us to better serve while offering our customers better services as well. It's become like their personal service manager. We've done this without ballooning costs.
What needs improvement?
While the solution speeds up the cost of digital transformation, doing so requires expensive or complex application upgrades or IT app support. You will need IT. That said, I haven't had a chance to explore mine in any detail.
There need to be more warnings for when there are issues within the automation especially when it comes to exceptions. We're not easily made aware of problems. The sooner we understand what the exception is, the sooner we can adjust things.
For how long have I used the solution?
I've been using the solution going on 25 years now.
What do I think about the stability of the solution?
For the most part, the solution is stable. We did encounter one problem when we were testing. Apart from that, we did not encounter any issues.
What do I think about the scalability of the solution?
The solution has helped us to scale. For example, if we have no idea from where to start, but we know the process test and know the application is involved, we're able to start building. We can go and test and try out options without having to put anything into production right away, so we can refine and validate the data.
The solution itself is highly scalable. We have three worker bots running at the same time. Users, however, can scale it up however they want to.
I'm not sure if the company has any plans to increase usage or put more bots into production.
How are customer service and support?
We have a team that lets us know if there are any changes coming up in relation to the infrastructure. If there are any changes that will affect the bots, it will not be done suddenly. We'll be able to ensure nothing is overly affected.
In terms of technical support, if something is not working as it should, they do need to review it. They do help us with technical validation.
Which solution did I use previously and why did I switch?
We did not use a different solution before we adopted UiPath.
How was the initial setup?
The initial setup was complex to a certain degree. The documentation was unclear. In the beginning, we weren't really comfortable with the approach or the process.
There were two types of processes happening at once during the deployment. We did each process twice, and each took two or three hours, so it was about one day to get everything going for each deployment, and then we did a final run-though. Likely, in total, it took us about 12 days or so.
We tend to have a specific process that we go through for every implementation we do. We'll go through how many bots are needed and what to do. We also do testing for all types of situations. We have a process designer who is involved and assists with the setup.
In terms of maintenance, we don't need anyone to run the operation. We have three to five people that after a month of production, have a good enough understanding to handle any outstanding tasks, whatever they may be. If there are issues, such as, for example, if Internet Explorer is not working, they are able to troubleshoot and manage the solution.
What about the implementation team?
We did not use an integrator or installer to assist in the deployment process.
What was our ROI?
We have seen an ROI.
What's my experience with pricing, setup cost, and licensing?
I always work to design my solution in such a way that is the most cost-effective.
You do need to pay the full license cost in order to use UiPath, so you need to be strategic to get the most out of it.
Our company handles costs internally as we do not directly deal with a vendor.
Which other solutions did I evaluate?
We did evaluate other options for data capture before we chose UiPath.
What other advice do I have?
We are customers and end-users.
At this time, we do not use the AI functionality within UiPath. Our solution is not impacted by anything generating artificial intelligence.
The automation speeds up the time to value and we see very quickly how much the solution is able to positively affect the business aspects. It's been really helpful for us overall. The processes have been profitable.
I'd advise users to really focus on their input and output size. You'll be able to validate your data. It will help you transform your processes. You just need to figure out where you want to simplify and where you want to maximize value.
We've learned how to standardize processes. We've realized how important it is to always try to be very clear when creating automation.
I'd rate the solution at a nine out of ten.
Which deployment model are you using for this solution?
Public Cloud
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.
RPA Developer at a engineering company with 10,001+ employees
Reduces human error, while offering end-to-end automation and easy development
Pros and Cons
- "The easy development process is very useful for us."
- "I had a problem with one thing, and that was exporting activities packages between the test server and the production server."
What is our primary use case?
Currently, I'm dedicated to working within a finance organization. It develops processes in the scope of five months. I do not use the solution in a contact center environment. I work on projects for shared services.
How has it helped my organization?
It's FTE-saving. Since the beginning of this year, I have covered more than four FTEs. That means that for half a year, I saved three FTEs. That's a huge benefit.
What is most valuable?
The easy development process is very useful for us. I know how to use it, and I'm able to prepare and add to a solution in one or one and half weeks. It depends, of course, on the process, however, largely, if it's a simple process, it could be developed from the beginning very quickly.
It's very important that I can create end-to-end automation using UiPath. Thanks to that, the business is free to do more advanced processes and is not overloaded by less important, repetitive tasks.
I've noticed that UiPath has reduced human error. The first benefit is FTE saving, however, the second is quality of work. Human work, if it's repetitive, it's very often related to human errors. That said, if something is programmed really well and automated it works without the need for human intervention.
What needs improvement?
I had a problem with one thing and that was exporting activities packages between the test server and the production server. I'm not sure that it's my own issue, or a general problem from the global perspective of UiPath, however, I have a lot of problems with packages, using the test server and production server.
For how long have I used the solution?
I've used the solution for quite a long time. I started using UiPath at the beginning of 2017. It has been more than four years.
What do I think about the stability of the solution?
The stability is good. Everything works well and I don't have any production bugs. I only have positive feedback, It works and there are no unexpected errors.
What do I think about the scalability of the solution?
The scalability depends on the developer. If we have an advanced developer, it is really easy to scale. If someone's preparing, for example, components, it is quite easy. From UiPath's perspective, it is easy to scale, however, that said, everything depends on the person who uses it and how familiar they are with the product.
How are customer service and technical support?
I had a chance to contact UiPath when UiPath licenses needed updating. I had close contact. I wrote a ticket and I had contact with them in less than an hour. I was quite pleased with their response time.
Which solution did I use previously and why did I switch?
I made the right decision to go with a solution that can scale automation without having to pay attention to the infrastructure and to develop my skills in terms of RPA.
I had to do tests with Blue Prism and UiPath. Currently, I use UiPath, as I find it's much easier to use than other RPA tools. For example, I really like Orchestrator, from a user perspective. The control of both is really easy as it's centralized in NonProduction Orchestrator, and it's really easy to operate it. There's general ease of development. In Blue Prism, for example, if you want to develop something, first you need to prepare the object layer, and after that, you can go to the business layer and connect it in one solution. In UiPath, we create just a component and connect components together which is more logical.
How was the initial setup?
I was not exactly involved in the initial setup as when I joined the company, UiPath had already been set up. Therefore, everything was prepared to start development. That said, for a few months, I worked in UI as a consultant for external clients. During that time I had the chance to install UiPath for external clients. In that sense, I've been involved in the installation of UiPath previously.
The initial setup's level of difficulty depends on a client's needs. At first, we need to think about the strategy of the client. In general, UiPath provides different types of architecture and it's generally straightforward.
The setup could take weeks if you need, for example, to order servers. However, if servers are already on-site, we can begin the installation. As I recall, I set up Orchestrator in a few hours.
What was our ROI?
We have calculations for that and we are on the right path. There is an ROI when using UiPath, however, I thought it would be higher. That said, we can calculate costs related to the UiPath environment and compare it to the automated processes created and we can see we are on a good path. It's hard, however, to provide exact numbers at this time.
What's my experience with pricing, setup cost, and licensing?
I'm not sure if UiPath has sped up or reduced the cost of digital transformation. It's a tough question, as the license for the solution is too expensive right now. In Western Europe, it may be okay to pay such money for a license, however, where I work now, in Poland, the license cost is too high for the local market.
What other advice do I have?
We have a connection to ServiceNow. In ServiceNow, there is an approval process to publish UiPath processes on the Production Orchestrator, and that's easy. I'm able to set schedules or run a process model from our Production Orchestrator.
We have different servers for development, including a different server for Orchestrator and a different server for production. However, everything is in my company environment.
At this point, I only use unattended automation. Currently, there are no projects for attended automation as it's more for the business side. I am just a developer from the IT side. I am not involved in any business department.
I'd advise those considering the solution to find a really good developer and maybe a solution architect. Some time ago, UiPath had marketing such as, "everyone could be a developer," and so on. That said, it does not work like that. UiPath developers should have a large IT background. During my career, I've seen a lot of projects fail due to developers' lack of skills.
My biggest takeaway from the solution is that automation is a process that doesn't have a start and end point. It's an ongoing process.
Overall, I'd rate the product at an eight out of ten. If the licensing price matched the local market's capabilities, I'd give it higher marks. I would like to start deploying the UiPath solution in Polish companies, and there is huge scope to do it, however, for now, it's too expensive.
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.
RPA Consultant at a tech services company with 11-50 employees
The end-to-end coverage is important, as our clients prefer one tool to meet their needs and plans
Pros and Cons
- "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."
- "The only thing missing is something to track the development cycle. We use third-party tools to do that."
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.
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 technical 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
Consultant with self employed
AI Center speeds execution and provides a good savings on time
Pros and Cons
- "It has a very easy drag and drop process and logic base setup. Previous projects were taking a lot of time. However, when we used UiPath on the same projects, instead of a process/task taking a day, it was now taking anywhere from 10 minutes to five hours."
- "I would like UiPath to give free trial licenses for more features, like AI Center. UiPath currently offers two licenses for the trial version. However, if I need to practice in AI Center, then I need four to six licenses."
What is our primary use case?
I am currently involved in healthcare-related projects and wholesale/retail-related projects. Previously, I was involved with banking and financial services, healthcare, and retail.
My current company is using a combination of the UiPath tool and SAP automation.
In my previous company, I used the UiPath tool for many projects.
How has it helped my organization?
It has a very easy drag and drop process and logic base setup. Previous projects were taking a lot of time. However, when we used UiPath on the same projects, instead of a process/task taking a day, it was now taking anywhere from 10 minutes to five hours.
There is almost no human involvement. For example, in banks, a bank manager will receive so many loan applications. We create some bots to check the requirements after validation and do the follow-up work. The manager is only checking boxes for the final approval request.
In the banking sector, I am using AI Center and creating some workflows. Some machine learning is needed to create these workflows in AI Center. This gives us a 94% accuracy, which is good accuracy.
What is most valuable?
Document Understanding is a good feature. It is a combination of artificial intelligence and machine learning. We have created some workflows using Document Understanding. We are using its machine learning to do some language analysis, semantic analysis, and invoice processing. UiPath currently provides some language conversions, such as German to Russia and Russian to German. However, it does not offer Russian to German, English to German, German to English, Russian to English, and English to Russian as well as some non-trainable languages.
Document Understanding has been one of the best features for invoice processing. For example, companies require some keywords in invoices. While normal frameworks take much of time, we upload the invoices using Document Understanding, then determine the keywords required for cross referencing. The cross reference is very fast. It will capture the amount and put that in an Excel format. This is a very good feature.
A valuable feature of UiPath has been the REFramework. In banking, we need to log in to the website with a user ID and password. Once, we did that wrong and the workflow stopped. Using REFramework, there is exception handling. Stability depends on the correct configuration of error handling, so this is the best feature.
It has some Citrix recording options.
The AI Center feature has been very good. It supports many machine learning languages and skills. It speeds execution and provides a good savings on time.
I like the certifications offered by UiPath Academy.
What needs improvement?
I would like UiPath to give free trial licenses for more features, like AI Center. UiPath currently offers two licenses for the trial version. However, if I need to practice in AI Center, then I need four to six licenses.
For how long have I used the solution?
I have been using UiPath since 2018.
What do I think about the stability of the solution?
The stability is very good.
What do I think about the scalability of the solution?
There are no limitations for Windows.
We have over 500 activities in UiPath right now.
How are customer service and support?
I haven't used the technical support so much. My colleagues use it sometimes, depending on their problem. The speed of their response depends on the type of plan, normal or enterprise, that needs support. I would rate them as 10 out of 10.
There is also social media support through Twitter and LinkedIn.
The user community is very good. I am a member. If a developer has any doubts when working on a project, then a lot of people in the community are ready to give immediate answers.
How would you rate customer service and support?
Positive
How was the initial setup?
We have faced challenges when installing market-related data. We need to dig deep when we are installing it with Orchestrator and/or VMware. All the documentation is available, but it needs to be prepared in advance. Whereas, we work in real-time.
What about the implementation team?
I have been involved with many client installations for UiPath and Orchestrator. We do standalone installations for single node and multi-node systems, like Linux. Linux is not fully supported, as compared to Windows. UiPath deploys well on Windows.
What was our ROI?
My previous company had good ROI using UiPath compared to other tools.
What's my experience with pricing, setup cost, and licensing?
UiPath Academy is free of cost.
The UiPath Community Edition is enough to implement any complex workflows.
The price for attended robots is good.
Some features are very costly, like Document Understanding. That is why in India many customers are not using the Document Understanding license. This is a premium feature and its licensing costs are high compared to other tools.
Which other solutions did I evaluate?
Compared to other tools, UiPath provides a good, rich environment.
I am using AutomationEdge, which is similar to UiPath, but a small tool. It provides the same features as UiPath, but it is not as popular a tool. The UiPath Academy videos are very good and better than those offered by AutomationEdge. While AutomationEdge also has a free learning course, you must watch their videos from start to finish. UiPath has no restrictions on its learning, which is good and the best option. For example, when you are an advanced learner, you want to go to advanced training courses. However, AutomationEdge makes you start from scratch, even as an advanced user of RPA.
Some processes are faster in AutomationEdge than in UiPath for insurance-related organizations.
I am also using Automation Anywhere, which is a popular tool in comparison to UiPath. However, feature-wise, UiPath is easier to use because Automation Anywhere requires complicated coding knowledge, though some of their features are very good. While UiPath requires some coding knowledge, it is not as high level as Automation Anywhere.
UiPath is the number one tool in my opinion. I would recommend choosing UiPath for someone looking to purchase an automation tool for the first time.
What other advice do I have?
UiPath has very good accuracy. I would overall rate this solution as 10 out of 10.
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.
Principal Solicitor at Consortium Legal
If a human had to do what this robot does it would be impossible; the digital transformation is quite dramatic
Pros and Cons
- "Regarding the ease of building automations, I'm not sure how it's done because I'm not a programmer myself, but it's great. Just looking at how fast they moved once we had the program settled in — it was quite fast. For this particular process, which is assembling a document, talking to DocuSign, sending out emails, and so on, the deployment of production was like "today." It was quite quick."
- "I could use more standardized features, retail-style, things that I could use off-the-shelf. Right now, all this requires quite a bit of adaptation in bespoke work with UiPath, which they've done very well. But looking at it after having used it, I would get stuff that is prepackaged from them, if they were any."
What is our primary use case?
We have developed a product for a court of arbitration. UiPath provides the automation engine behind it. Our product is a platform that is live online. It allows a party to provide some contract information, and the robot assembles a document and communicates with DocuSign, our signature provider. It then sends out a correspondence to the other party and manages the signature process for a bespoke contract for an arbitration agreement.
This is a service that we provide to the world, pro bono, as it were, to promote arbitration and the adoption of a particular arbitration clause. It's accessible to all. Parties can log in and it helps them to negotiate and conclude an arbitration agreement in a mediated fashion. The robot sends out email on behalf of a third-party, a court of arbitration, and it helps the parties get that agreement done.
It's about concluding an arbitration agreement before the dispute goes any further.
How has it helped my organization?
It helps us in providing added value to the clients and to the community at large. It's a marketing thing for us, in the widest possible sense, rather than something that we use in our practice.
But in terms of reducing the cost of digital transformation, if a person had to do what the robot does, it would probably be impossible. It would be impossibly costly. If one person had to handle the communication, instead of the robot, and try to negotiate each addendum, nobody would do it because it would take days or weeks for a lawyer to manage, and it would be prohibitive. Yet, all of a sudden, we have this service that is so cheap in many ways that it can even be provided for nominal user fees. It's quite dramatic.
I would also imagine that processing time is reduced by many orders of magnitude. As a professional, if I had to manage an addendum like that, it would take me weeks. And it takes about seven minutes or so, if all goes well.
What is most valuable?
What I have found interesting is that our product acts as a human would but it's not intrusive. It doesn't require any real integration or interface with one's own systems, in any meaningful way. Obviously, you need access, an account to log in, but it otherwise acts as a human, and that makes deployment quite smooth. It doesn't require you to change anything in your system. I found that very useful.
Regarding the ease of building automations, I'm not sure how it's done because I'm not a programmer myself, but it's great. Just looking at how fast they moved once we had the program settled in — it was quite fast. For this particular process, which is assembling a document, talking to DocuSign, sending out emails, and so on, the deployment of production was like "today." It was quite quick.
In terms of the ease of management of automations using UiPath, I don't dare poke into it, as a non-technical person, but it looks manageable. I have someone who does not do RPA normally, who doesn't do this type of programming at all, but that person knows where to look for errors and doesn't get lost. It's reasonably accessible.
What needs improvement?
I could use more standardized features, retail-style, things that I could use off-the-shelf. Right now, all this requires quite a bit of adaptation in bespoke work with UiPath, which they've done very well. But looking at it after having used it, I would get stuff that is prepackaged from them, if they were any.
For how long have I used the solution?
We launched with UiPath in June.
What do I think about the stability of the solution?
The stability of the solution is okay.
The downside of the upside, when I said that it works like a human, is that in some cases, if it interacts with a website that is changing, then it's like a human. You need to adapt it to the changing environment in which it works. That's an inevitable fact of life, that it interacts with other apps. It can also interact through APIs, but you want it to be very flexible, you want it to be an agent, like a human. The downside of that is that if something changes with a website, then of course, you have to change the robot and tweak it a little bit. But that's the only issue that has required our attention so far.
What do I think about the scalability of the solution?
Our product is a public-facing instrument and we have had no problem with the number of users, so we have not seen any issues with scalability.
In terms of potentially increasing our use of UiPath, we're exploring a number of solutions actually, for practice management and actual lawyer work. These would be in-house solutions, rather than public-facing. We have a few ideas that we have run by them and we are waiting for feedback.
How are customer service and technical support?
We've had no problem with the customer support. We were in direct contact with the whole team. They have always been quick to respond. I would rate them a 10 out of 10.
Which solution did I use previously and why did I switch?
We would use regular Microsoft automation features. I would have a flag on a particular correspondence, or a particular rule for attachments. We would use little bits and bobs of automation that are available, but we did not have any bespoke solution.
We went with UiPath because they made themselves known in the sector and it was a question of the vision that they communicated. There was a modest vision of providing solutions to very discrete problems, not revolutionary solutions to everything. Rather, they focused on whatever helps in a particular organization. We liked that. It matched our understanding of legal tech as well. It needs to be supportive of whatever little bit of help you need, rather than providing you with an environment that engulfs you with everything. We liked that approach, and when we approached them they were very receptive.
How was the initial setup?
The initial setup process was okay. I'm a non-technical person, but I was able to manage it.
It took quite a bit to figure out what we wanted from it, the flow and the logic of it. After we agreed on that, on the concept, actual production took two or three days. Of course, somebody had already done a proof of concept, although that was not based on a final brief. We danced around and changed it a bit.
For maintenance, we have somebody in tech that we pop questions to, and our maintenance of the server is done in-house as well.
What was our ROI?
We have realized return on our investment. It was a joint project with UiPath so we had special arrangements in terms of licensing, but it was very well received in the market. It was very beneficial for us.
Our product is something that we launched in June, and the robot has been featured in general business publications, in the Kluwer Arbitration Blog, and the Resolver, which is the Chartered Institute of Arbitrators magazine, as well as the Romanian Arbitration Journal. Essentially, everybody knows about it. It is one of the most popular UiPath robots out there; the most featured and interviewed robot in the wild. We were quite pleased with the publicity.
What other advice do I have?
My advice is to think about it very carefully and know exactly what everybody is doing every day in the office, the little bits and pieces. Really look at that seriously, because there are so many things that we do in a software environment that are very amenable to automation, and it saves a lot of time. Think very carefully about the particular needs of your office and look into it, because it can save you a lot of money.
It's clear that this is the future.
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.

Buyer's Guide
Download our free UiPath Report and get advice and tips from experienced pros
sharing their opinions.
Updated: March 2025
Popular Comparisons
Microsoft Power Automate
Automation Anywhere
Blue Prism
ABBYY Vantage
Automate
Tungsten RPA
Pega Robotic Process Automation
WorkFusion
Robocorp
IBM Robotic Process Automation (RPA)
Nintex RPA
VisualCron
Blue Prism Cloud
SAP Intelligent RPA
AutomationEdge
Buyer's Guide
Download our free UiPath Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- I am evaluating Blue Prism and UiPath for RPA for my company. Which one do you recommend?
- What Is The Biggest Difference Between UiPath And Automation Anywhere?
- IBM digital business automation with UiPath vs IBM RPA with Automation Anywhere?
- How do I choose between UiPath and Microsoft Power Automate?
- What are the differences in features and capabilities between ABBYY FlexiCapture with OCR and UiPath AI?
- RPA Governance and Business Continuity requirements for a large multi-national corporate financial services provider
- Can anyone help with this error when migrating my orchestrator community process to orchestrated enterprise UiPath?
- Which one to choose, Power Automate or UiPath, for unattended and attended bots implementation for a simple RPA use case?
- Can UiPath support the SaaS model for process mining?
- Seeking comparison between blue prism and uipath