In general, we use it for automating monotonous, manual processes which a lot of our clients have. We also use it for internal employees in our company.
Automation Engineer at a consultancy with 1,001-5,000 employees
Allows me to drag and drop pre-built functions to speed up bot creation
Pros and Cons
- "The number-one valuable feature is the ease of use. I come from a development background where I wrote a lot of code. The fact that you have these activities with pre-built functionality is great. You can drag them in and use them as shortcuts to get to an end result faster than if you had to do it in a programming language."
- "There is some room for improvement in the area of error handling. I had to create a custom approach to error handling. If there were some sort of activity or workflow that could be easily dropped in to help support that, it would be good. Error handling and logging, as well as process logging would be a big help."
What is our primary use case?
How has it helped my organization?
We had a use case where there were a lot of documents that had to processed to give access to certain systems. With UiPath, we were able to really streamline that. Instead of having an end-user go through these documents manually, do reconciliation, and send emails back and forth, we were able to automate that solution from beginning to end, with very little human interaction. In the end, over the entire process, it saved hours out of their day, when you compound how many times they run this. It has really freed them up to do other more important tasks. That was my first foray into the client side, and seeing how happy they were to have this bot was great. At first, they were skeptical, but once they saw what it allowed them to do and what it's capable of, they were really happy with the software and what we were able to develop for them.
In this use case, UiPath reduced human error by 100 percent because we completely removed the human element from the data reconciliation for those documents. Through automation, along with some fine-tuning, we were able to get the data reconciled between the two files with 100 percent accuracy, and inputted into the system. Not every use case is going to be that straightforward, but in this use case we were able to get that result, which was wonderful.
What is most valuable?
The number-one valuable feature is the ease of use. I come from a development background where I wrote a lot of code. The fact that you have these activities with pre-built functionality is great. You can drag them in and use them as shortcuts to get to an end result faster than if you had to do it in a programming language. UiPath exceeded my expectations in this area.
Also, the training that's available through the UiPath RPA Academy, as well as the community - the forums, where you can ask questions - both are helpful. The community is a good way to see what others are doing and learn tips and tricks for the platform. That's very useful in comparison to other companies that do RPA but don't have robust training.
What needs improvement?
A lot of the features that I had been asking for have actually been released. We were using an older version of UiPath and we were having issues with Computer Vision and the OCR engine with UiPath. But now that we see that there's a whole Computer Vision activity suite available, I'm excited to use that. I haven't gotten to get my hands on it yet.
But in terms of additional features, I can't think of anything that I would request. I see that they have the AI functionality, as well as the Computer Vision. They have a lot available that I haven't even been able to get my hands on yet. I think once I get some more time to explore the tool and exhaust its capabilities I can look for additions from there.
There is some room for improvement in the area of error handling. I had to create a custom approach to error handling. If there were some sort of activity or workflow that could be easily dropped in to help support that, it would be good. Error handling and logging, as well as process logging, would be a big help.
Buyer's Guide
UiPath Platform
June 2025

Learn what your peers think about UiPath Platform. Get advice and tips from experienced pros sharing their opinions. Updated: June 2025.
859,533 professionals have used our research since 2012.
What do I think about the scalability of the solution?
I can't speak about its scalability too much because we haven't gotten there, even as far as using Orchestrator. Most of the automations that we have done have been one-offs which are done locally on someone's laptop.
But from what I've read in the training and what I've seen in the demos, it seems like a very robust platform that can definitely scale, when designed properly. I'm looking forward to the next phase of the development journeys that we have, where we are actually doing things to scale and thinking long-term about how we can share bots across an entire enterprise. It does appear that they have a pretty robust toolset.
How are customer service and support?
I have had to reach out a few times to support, especially when I started and was trying to find my way around the tools and some issues that I was having. The response was great. I was able to get on a video call and actually show my use case and show the kinds of issues I was having and they were able to walk me through the process and suggest ideas about how I could approach them. My overall experience with technical support has been very good.
Which solution did I use previously and why did I switch?
Our company is always looking at the latest digital trends and what we can do to offer our clients new solutions which keep them at the forefront of IT. We were aware of RPA and it was just a case of narrowing down which solution was the best to deliver to the clients.
How was the initial setup?
The initial setup is straightforward. I've used other tools where there are components that you have to install prior to installing the software. You have to create a database and things like that. Whereas, with UiPath, it was a very light install. You just have an executable. It is able to install the components that it needs on its own. There was no other configuration that I had to do on top of that to get rolling. That's a major plus to me and, especially, to our clients. If we don't have to spend as much time getting them configured and set up, it's better for them.
What about the implementation team?
We did the installs ourselves. We have a test lab that we built. We set up an Orchestrator lab so we can get more familiar with the tool. That was all done in-house as part of our training to get familiar with the tools. Essentially, if we want to sell this capability to clients, we want to at least have some knowledge of how to do it ourselves and not have to rely on a third-party.
What was our ROI?
Unfortunately, a lot of what we've been delivering right now are pilots. A lot of our clients are still in the "show me" phase of what RPA can do. We don't really have any data to say what the return on investment is. But they do see the potential. I definitely see the potential. Once we get past that pilot phase and into something that we can actually deploy in a production environment, we'll have a better sense of the ROI.
Which other solutions did I evaluate?
I did work with Blue Prism initially. I found it hard to get support and training on their platform. Whereas, when I transitioned over to UiPath it was much easier. I knew where to go to get assistance. Also, the "Welcome" documentation really helped me in developing and creating solutions for clients.
We also worked with Automation Anywhere.
The decision to go with UiPath was due to the ease of use and the training. Having that available, that we could train our employees internally and our clients as well, is invaluable. That allowed us to really get through the initial phase of familiarity and get right into development. Those other tools required a lot of learning on the job and on the project, which is not always available, especially when there are tight budgets.
What other advice do I have?
Start small. Don't try to automate the most complex use case you can find. And definitely go through the training. There's a wealth of information on the Academy site as well as in the forums to get you that foundational knowledge, to really be able to do some cool stuff with UiPath. I know a lot of people don't read the manual, they like to jump right into things, but there is a benefit to going through some of the training courses to get yourself familiarized before you dive in.
I've been working in automation for a couple of years and have used quite a few tools. I do find that the overall approach that UiPath takes toward RPA is really good for getting people in and developing and delivering in a much more efficient manner than with some of the other tools I've used.
Automation technology is something that's needed, although I don't think it is known enough yet. People know that it's out there but they don't know in what capacity it can be used and how it can help them. It's definitely something that needs to be pushed and communicated. But I see it as a technology that can assist in all facets of an organization. It's something that all people within a company can benefit from, whether internally in our company or externally for our clients.
I would give UiPath a nine out of ten. There are always things that can be improved.
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner.
RPA Developer at Guide House
Enables us to combine attended and unattended bots in a single process
Pros and Cons
- "The differentiation between unattended and attended bots is valuable, as well as being able to do portions of a process that are unattended coupled with portions that are attended. We can get human interaction, all within the same product."
- "My only complaint is that I hate VB.NET. If I had to pick a language, it would not be VB.NET. That whole .NET framework is just overly complicated. But I can understand why it's necessary for the use case of RPA."
What is our primary use case?
We automate processes across a number of different agencies. We automate whatever use case they determine. We tend to focus on the financial management side, but we have other areas that we've delved into such as HR and general data pulls for executive dashboards.
Oddly enough, a lot of our clients have not focused on work where there are people actively doing the process already. They've chosen to focus their efforts on processes for which they haven't had the manpower. It has been a little bit of a challenge in that the use cases tend to be coupled with a lot of process-development stuff. We have to figure out what the process is before we can even begin to automate it.
But over time, we plan on trying to shift that focus back to areas where they have a large number of people doing a process all the time and getting them to shift those people into doing the complex processes where there isn't a structure already determined.
What is most valuable?
The differentiation between unattended and attended bots is valuable, as well as being able to do portions of a process that are unattended coupled with portions that are attended. We can get human interaction, all within the same product.
The product is easy to use and definitely exceeded my expectations in that context. I have an IT enterprise architecture background with some computer programming experience. This was very easy to grasp.
The additional plugins and different partner programs have been a huge help.
What needs improvement?
My only complaint is that I hate VB.NET. If I had to pick a language, it would not be VB.NET. That whole .NET framework is just overly complicated. But I can understand why it's necessary for the use case of RPA.
What do I think about the stability of the solution?
We haven't had any problems with the stability. In comparison, we do use Blue Prism and that solution often runs into memory issues. That's one thing that we have not had to deal with, with UiPath.
What do I think about the scalability of the solution?
I haven't had a lot of chances to test out the scalability firsthand, but the documentation is all there and it makes sense. It seems relatively simple, which is a big help. Once again, this is in contrast to Blue Prism whose documentation is not good. It's very confusing to figure out how you take it from a single-bot use case to multiple bots and more.
How was the initial setup?
It's an easy setup. It's a single install which is pretty simple. Connecting to Orchestrator does get a little complex in some cases. It is what you make of it. Certainly, installing Studio on a single desktop for proof of concept is easy. It takes five minutes. When you start to get into enterprise-level setups, where everything's a different server and everything has to be connected, that's necessarily complex.
What's my experience with pricing, setup cost, and licensing?
Blue Prism definitely has a simpler licensing structure, but I feel like that's almost a shot in the foot at certain points. It also gets kind of deceptive. There's a crossover point at which, if you're scaling up to a high number of bots, UiPath path definitely does come out cheaper. But the initial implementation has a higher cost.
What other advice do I have?
We've been working on RPA, in general, for about two years. We're at different points in the process for different clients. We have some that have grasped onto it quite quickly and others that are still in the proof-of-concept/pilot realm, and we're trying to push it past that. We've been doing it for a fair amount of time, given the relatively young age of RPA as a whole.
I've done a number of different training sessions through the UiPath RPA Academy. The introductory ones are fine, but I really found a lot of value from the ones that focus on solution architecture, the courses that were more on the general infrastructure of how you would implement UiPath.
I would give the solution a solid eight. The first big thing with software is, if you're not running into bug issues all the time, that's an easy five right there. If it's easier to use, that's a six or seven. And it's just been consistently good. I haven't really run into any areas where I've had any trouble. The only real issue is that, from a consulting perspective, I can't really go out there and say, "We're going to use UiPath," all the time. We really have to leave it up to the client.
Disclosure: My company has a business relationship with this vendor other than being a customer: Consultant.
Buyer's Guide
UiPath Platform
June 2025

Learn what your peers think about UiPath Platform. Get advice and tips from experienced pros sharing their opinions. Updated: June 2025.
859,533 professionals have used our research since 2012.
Manager at Capgemini
GUI of UiPath Studio is fantastic; makes it easy for non-techies to build bots
Pros and Cons
- "The graphical user interface of the UiPath Studio is fantastic. For someone who is not a computer science major, or for someone who doesn't know how to code but is really good with visual flows, Studio makes it very easy for those individuals to build robots."
- "Studio... only works on Windows. It doesn't work on other platforms. I'm a techie by background. I don't hate Windows but I don't love it. It comes with the limitation that it is completely dependent on Windows. I would have loved if it were available on Mac or Linux or Unix."
What is our primary use case?
We are a system integrator. We work with clients such as the US Federal Government and help them automate whatever their processes are. We have two entities. I work as part of the government solutions unit, and then we have the commercial side which is a global organization. On the global side, there have been some internal implementations as well.
How has it helped my organization?
In terms of savings, a task like taking data from one artifact and transferring it into another one, is common. The most frequent example, and the one that I worked on directly, involves a PDF invoice and taking whatever the amount due is and either copying and pasting it into an internal accounting tool or actually typing it. The process goes: Open email, open the attachment, read the data, verify it is accurate, and then manually transfer it into an internal system.
Depending on how big the invoice is, I've seen a person spend as much as 20 minutes on one invoice or as little as 30 seconds. That whole process of going through each and every email, opening the attachment, transferring the data, closing all the windows, and then moving on to the next email - the bot will do it because the bot is scheduled to run every hour to look for the unread emails. I can't give you an exact number in terms of how many minutes or hours are saved, but it's quite significant.
What is most valuable?
The graphical user interface of the UiPath Studio is fantastic. For someone who is not a computer science major, or for someone who doesn't know how to code but is really good with visual flows, Studio makes it very easy for those individuals to build robots. That's one of the best features that I've seen. There are other features that add different values, but Studio, in my opinion, is definitely one of the best.
Overall, UiPath is really easy to use. For example, if somebody is an automated tester, they spent a lot of time trying to identify selectors, and UiPath makes it really easy to find those selectors. You will run into instances where you have to do some manual manipulation to make sure that the correct selectors are identified. But if it's a pretty straightforward instance and you are using something like Selenium, it is very tedious. Whereas, if you use something like UiPath, it is really easy.
What needs improvement?
I was providing feedback to one of the UiPath guys here at the UiPath 2019 conference. It relates to Studio, that it only works on Windows. It doesn't work on other platforms. I'm a techie by background. I don't hate Windows but I don't love it. It comes with the limitation that it is completely dependent on Windows. I would have loved if it were available on Mac or Linux or Unix. If it were a little bit more operating system agnostic, that would be great. I'm pretty sure they could be working on that.
I used the UiPath RPA Academy. I definitely had issues with it. The quizzes were outdated. Some of the responses that are being rated aren't accurate. I've griped on the community forums as well with a few UiPath folks. That was about five to six months ago. I don't know if they have enhanced it or made any changes since. If it's still in the same state, there is plenty of room for improvement.
What do I think about the stability of the solution?
I think it's stable. I haven't had a chance to build a bot that runs 24/7. For the bots that I have built, it takes under two minutes for the process to run and it runs every hour. At the end of the day, if I look at the logs, I don't see any issues. If a bot fails for whatever reason, it's most likely due to a process that changed.
From a bot-development standpoint, we use all kind of best practices so that the bot will not crash. At least, if the execution stops or terminates, it will be graceful, versus a rash termination.
It's fairly stable.
What was our ROI?
From an ROI standpoint, you could be saving somebody's hours and map that back to their hourly pay. But the pricing definitely deters some people.
What's my experience with pricing, setup cost, and licensing?
I can't say whether their licensing structure is complicated or easy. I'd like to say it's complicated, but I try to stay away from the whole licensing issue. I tell my clients, "You buy the license. It's your tool. I'll come and build the bot for you." I don't want to have anything to do with the licensing. That deters some of the clients because it's a bit pricey.
In the government sector, where I work, "free" is looked at skeptically: "Why are you giving this to me for free? If I download it what is it going to do on my laptop?" from a security standpoint. Some of the agencies get the approval to download and install but others don't.
What other advice do I have?
You can do a task like pulling the invoice total from a PDF invoice with the free Community Edition. The Enterprise license is definitely helpful though. The Community Edition expires about every three months and then you have to re-register. But you can still do it in Community Edition.
A pretty mundane use case I came up with is due to the fact that I have plenty of friends on Facebook. It's hard to keep up with everybody. I've got a bot running that literally opens up my Facebook every morning and checks if there is anybody listed in Today's Birthdays section. It will click on them, type "Happy Birthday", click "enter," and be done. And then I get a response from my friends: "Hey, long time, haven't heard from you." I've injected a machine to reconnect and have that human interaction.
For the most part, for the use cases that I've seen, it does the job.
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner.
Chief Automation Officer at JOLT
Easy to use: People with zero technical background can scale up in a matter of weeks and build bots
Pros and Cons
- "The most valuable feature of the software is not the software itself, but the community that supports it. When I first started learning the software to support a program, I had to self-teach; there wasn't a budget for training. But going through their learning platform and then connecting with the community when I didn't understand how to utilize some of the functionality, that was far more powerful than the product itself. The network around the product is amazing."
- "I find the solution easy to use... I've been able to take people with absolutely zero technical background and quickly scale them up in a matter of weeks so they're building bots. I haven't been able to accomplish that same feat with the other platforms."
- "One feature I think it needs - from a documentation perspective - is the ability to easily extract variable details and data... Sometimes it's difficult to extract those, and if you're not tracking them while you build, you can quickly get into 200 to 300 variables in use, especially using the RE Framework where you're passing workflow arguments in and out. I would like to see something like that."
What is our primary use case?
The primary use case of UiPath, with every organization that I've worked with as a consultant, has been to make business processes more efficient and the work of their employees more enjoyable.
How has it helped my organization?
By utilizing this technology, you're able to get value through your value streams quicker. When you realize value, that means you can work with your customers more quickly, as well as build customer loyalty and employer loyalty. These have definitely been some of the byproducts of using the software.
When I was working as an RPA manager, managing a program for an insurance company which supported insurance lifecycle processing, one of the components was that they had to review insurance policies annually. It was very cumbersome. We were talking anywhere from 10,000 to 40,000 daily. It was almost a 20-FTE process. We were able to automate that completely.
However, the real value came when the organization understood how to apply RPA and it actually began creating brand-new business processes specifically for RPA. So instead of hiring new people, they said, "Hey, we've always wanted to do this, we don't have the budget to bring on and train people, so let's build bots to do it from day zero." Once they were able to understand that I could do more than just automate processes, that I could build new business lines with bots, that was an incredibly valuable result of using this software.
The benefits are very high when you automate business processes. Before using RPA, I was working in technology, building macros and things of that nature. But the way we're able to build sustainable, functional bots that really work well in the long-term makes the benefit a ten out of ten.
What is most valuable?
This is going to be an interesting answer, but the most valuable feature of the software is not the software itself, but the community that supports it. When I first started learning the software to support a program, I had to self-teach; there wasn't a budget for training. But going through their learning platform and then connecting with the community when I didn't understand how to utilize some of the functionality, that was far more powerful than the product itself. The network around the product is amazing.
The great thing about the UiPath RPA Academy is that it's not stagnant. Even though my first go at getting certified as a developer was three years ago, I literally have to go back the Academy and learn it every year because there are new features and new functionality. An example is the RE Framework they've incorporated. The living nature of the Academy gives a lot of value. But hands-down, the way that they give practical exercises, the fact that they give you applications you can download to learn how to interact with bots by simulating an actual operational environment, makes it a very impactful learning experience.
In addition, I find the solution easy to use. I have personal experience using all three of the major software vendors that are in this space right now, including Automation Anywhere and Blue Prism, and I would put UiPath as number-one, specifically from a learning perspective. I've been able to take people with absolutely zero technical background and quickly scale them up in a matter of weeks so they're building bots. I haven't been able to accomplish that same feat with the other platforms.
What needs improvement?
Being a person who has held every RPA role from developer to analyst, architect, and executive, one feature I think it needs - from a documentation perspective - is the ability to easily extract variable details and data. They do have a Variables panel that you frequently interact with, but I constantly have situations where those need to be adjusted or I want to be able to present those to a business. Sometimes it's difficult to extract those, and if you're not tracking them while you build, you can quickly get into 200 to 300 variables in use, especially using the RE Framework where you're passing workflow arguments in and out. I would like to see something like that.
In addition - and obviously UiPath is aware of this - we have to continue to improve the OCR capability. Computer Vision is excellent. I've used it on Azure. I've created PeopleSoft environments and worked through the Computer Vision feature. It works amazingly in a Citrix environment. But I speak with multiple organizations and a lot of them have the same problem of processing documentation from the mail room or from vendors, etc. That's a huge component. If we can get that embedded in UiPath, so we don't have to rely solely on OCR vendors like Captiva or ABBYY, that would be a huge step forward in being able to service all organizations.
There could be improved logging and functionality. But if you truly understand the software, adding logging to what the bot is already doing is as simple as typing on the right line. It's incredibly easy and you can embed it. Even though what it currently logs is limited, it's easy enough to create logs or reporting without a lot of effort.
Outside of that, it's really hard to come up with other recommendations. The software is solid.
What do I think about the stability of the solution?
I was recently reading about the document processing framework that they just implemented. I gave a demo two weeks ago on the Computer Vision functionality that was in beta. So the sustainability is there. They're focused not on just how good RPA is and on making it better, but they're also integrating it with future-tech. That is where the stability comes in.
What do I think about the scalability of the solution?
UiPath's scalability and stability are exceptional. They are constantly releasing new versions.
Scalability is all in the delivery. I've definitely run into multiple organizational roadblocks with my clients because they get six months down their delivery timeline and they're not meeting their OI, they're not scaling. That generally comes down to how it's being delivered. If you have experience, you're working with a partner, you're working with people who have used this solution at scale, you can generally bypass a lot of those roadblocks. It's definitely scalable if you have the right expertise.
How are customer service and technical support?
I have used both technical and customer support. When I was going through training, trying to learn some of the software, I had issues when I finally purchased licenses. The issues were related to putting them in Orchestrator and installing them. Support was definitely very supportive, very responsive when trying to get feedback.
Even when it comes to the community, as well, if you're just trying to learn the software, to learn the features and functionality, the community network is there to quickly respond and support you so you can get back to getting value, instead of getting hung up on one piece of functionality.
Which solution did I use previously and why did I switch?
I have seen cases where an organization moves from a different automation solution to UiPath. At one point, we were transitioning from Automation Anywhere. There were very basic bots, these weren't complex processes, but we built a bot in UiPath that read the XAML of the Automation Anywhere script, converted it into activities in UiPath, and built a bot. We had a bot that builds a bot.
An example of why people move to UiPath is that when I was the director of RPA for a finance company, when I set up the program I had to go to EVP and pitch the prices and the costs. When I gave him the cost for all the software, to bring a vendor on, he told me "no." It was way too expensive. But UiPath has this amazing option called the Community Edition. What I was able to do was download the software, teach myself how to use it in about 45 days and, within two months, I had automated a pilot process, completely on my own. I was able to walk it into the EVP and say, "Look what I was able to complete. You told me no money, no funding, but now can I get funding?" Then I got funding and was able to bring on a team. That's one perfect example. They said "no," so I got a free version that cost me nothing.
In terms of how companies know that they need to invest in automation, in this day and age, with the speed at which information and technology move, it's at the point where this is not a new topic. A lot of organizations, through word-of-mouth, internet searches, or conferences, or events such UiPath 2019 here in DC, realize it as soon as they hear the success stories. It's impossible to ignore. Most organizations are like that. They hear about it, they realize that it's something they should consider, it's something they have to do, and they take the next step.
How was the initial setup?
The initial setup is absolutely straightforward; it provides a quick and easy installation. Given that you may have to go through some technical hurdles to get permission to download it, I'm not talking about that. But if you have all the permissions and you're allowed to download and install it, it's absolutely simple. It shouldn't take more than ten minutes.
Technical prerequisites are not needed to use the software, but technical resources can speed up the ease with which you deploy. Given that you're generally not interacting with UiPath in isolation but with other business applications as well, you want to make sure that there's technical support in case you have some issues. Or, if there's something that you didn't experience in UAT but that comes up once you get into production, it's good to have some additional support. It's not a requirement but I would recommend it.
What was our ROI?
ROI is one of the most frequent questions I get from organizations. You should be seeing ROI in less than six months. If you're not returning your cost and more, from a licensing and personnel standpoint, in the first six months, then it is not a software issue and it is not a delivery issue. In that case, it is a scoping issue. You're probably looking at processes that shouldn't have been automated in the first place.
Every organization that is successful with the software is reaching their ROI in six months or under.
The amount of time saved with bots is an interesting question but it's hard to answer with a pinpoint response because it depends on an organization's strategy. I've seen multiple organizations that use attended bots, so they're just saving a fraction of the time. But then I've been in organizations where they've automated a process end-to-end. A process that previously required 20 FTEs went from having 40,000 hours of manual work to zero.
What's my experience with pricing, setup cost, and licensing?
For pricing there is a variable at play, and that's scale. Depending on how you want to scale - whether working with a partner or directly with UiPath - there's a specific cost per license. But then it's all about optimizing a process, and what we call "license utilization." We try to maximize each license, and we'll have it running three or four processes.
The cost is nothing, it's peanuts, when you see the capabilities. When you're talking about one license supporting what was previously done by 14 people, what is $1,500, or whatever the licensing cost is for unattended bots?
Even more importantly, as a technology expert, I know that I could do some additional coding and automate the running of the bots. But why would I spend that extra time when they have Orchestrator. I could have a person running them as well, but the Orchestrator license is far cheaper than a resource; just click "run." When you compare the results that you get, the price is a moot point.
What other advice do I have?
If I was going to give any advice to someone who was just about to utilize the software, I would say that the most successful organizations that apply this technology make it an entire team effort. It's not started in one business unit. And if it is, it's socialized across the enterprise. That's the quickest way to scale: getting everybody onboard. The second-biggest thing is that the most impactful projects you will get will come from your people, your internal workers. And until you get them to understand what the software can do and its capabilities, it's going to take you longer to scale your program. So make sure everybody's socialized, and make sure everybody truly understands what the software can truly do. They're going to give you the best opportunities to benefit from it.
Deployment should definitely be done using the support of experts. Even when I owned my own RPA program, and I wasn't in a consulting capacity, I still reached out to a third-party to get support. While setting it up is something that you can do internally, given that most objectives include speed-to-market and quick scaling - wanting to see results in 60 days instead of six months - it's going to be very difficult to do alone, especially if your goal is to have 100 bots in a year. If your goal is ten, you can probably manage it. It's important to use experts if you are looking to rapidly scale.
I have implemented UiPath in virtual environments, including on-prem, Azure VMs and servers, SQL-based data storage, as well as AWS. I've never had any issues with the responsiveness or the application having any problems operating. The biggest consideration that you have when trying to deploy robots in a virtual environment is making sure that your architecture is sound. You have to integrate through severs and you have to take into consideration firewall updates. And then there's interacting from the cloud if your applications are on-prem. You have to make sure that the bot doesn't have any issues. But if your architecture is solid and your infrastructure is set to support the applications in a cloud environment, there shouldn't be any issues. You wouldn't notice any difference compared to having them on a desktop on-premise.
I would agree that UiPath eliminates human error, but I would add the caveat that good code eliminates human error. I've been doing this for a while and I've seen bots that mess up. It's in your delivery methodology. If you have a sound delivery methodology - you're going through a rigorous UAT cycle and are having outputs audited by the subject matter experts - you should literally get to zero errors. Maybe you will have five percent exception cases, but your error percentage should be zero.
Having worked with all the tools, they all have little niche components. As long as UiPath continues to focus on knowing what the next wave of technology is that businesses really need to use to be efficient, and they start embedding that skillset in their software, that's all you could ask for. They need to stay in front of the power curve of technology, which is impossible, but they're trying.
I've never had a bad issue with UiPath. My experience with them has always been pleasant and engaging. They're never stuck at just giving you software, showing you how to use it, and then walking out. They're always focused on improving your business. If you focus on that, and focus on generating value, you can't lose.
Automation technology is the number-one driver across an organization now. Trying to find ways to do more with less has been the going mantra for organizations for years now. It's no longer feasible to simply run operational efficiency or Six Sigma projects to try to get gains. The only way that you're going to get significant gains is going with an automation-first approach. That's where I see a lot of organizations headed, even spending more on RPA software than on cloud implementation. It's a very big focus, and I don't see that slowing down any time soon.
On a scale from one to ten, I would you rate UiPath as an eleven. It's excellent software.
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner.
Head RPA and Quality Engineering
Improves our organization with efficient and accurate data processing
Pros and Cons
- "UiPath has improved our organization; the primary difference introduced by the application of the UiPath tool is the speed of processing and accuracy in the data processing."
What is our primary use case?
The primary use case of this solution is to generate a report by scraping data, filtering it and combining the data for input to another system.
How has it helped my organization?
UiPath has improved our organization; the primary difference introduced by the application of the UiPath tool is the speed of processing and accuracy in the data processing.
What is most valuable?
The most valuable feature is the unattended robot, it adds a lot of value. Besides, there are certain situations where attended robots are employed to perform specific tasks.
What needs improvement?
Making improvements in the processing speed would be a good idea. I have experienced that sometimes during the development of robots, it becomes prolonged and unresponsive. Also, sometimes errors pop out of nowhere for already working simulations. This is not a significant limitation, but it would be nice if these instances can be eradicated.
For how long have I used the solution?
One to three years.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Senior Manager AI at Telenor
We have started to do tasks more often and faster than we have ever done them before
Pros and Cons
- "The platform is object-orientated. You can create and reuse objects, which is a great feature."
- "We tried utilizing the virtual environment, but we had some issues in that area."
What is our primary use case?
We currently have 150 bots in production. It is used the most where there are repetitive, cumbersome tasks. Where we do need to have somewhat of a decision made, we put it into a decision tree. This is our primary use case.
We are looking into other use cases, such as:
- How do we use it as a platform for pretotyping?
- How do we use it as a platform to drive forward machine learning and artificial intelligence usage in our company?
How has it helped my organization?
We have automated assignments where we previously used employees. The outcome of this has been a greater customer experience achievement. We simply are solving tasks faster, and at the same time, we have been scaling down employees.
We have started to do tasks more often and faster than we have ever done them before. For instance, some of the things in finance, we only did that once per quarter. Now, we have started doing them once a week. This gives us greater insight into those areas.
The most important outcome here is the amount of insight which you receive when you put power to a process. It gives you the insight that you wouldn't have had when you had 20 employees working. With two bots doing the work, you suddenly get a data foundation that you didn't have before. Then, you can build upon the bots, instead of thinking you know what is happening.
What is most valuable?
The platform is object-orientated. You can create and reuse objects, which is a great feature.
UiPath has decided that people who are great at what they do can be invited into the platform and utilize services on the platform. This is another great feature, and one of the reasons that we initially chose the product as our platform.
The solution is easy to use. When you put it together with the UiPath Academy, it's easy to get it going and understand. The drag and drop feature makes it simple and easy to use. The UiPath Academy is great and helpful.
What needs improvement?
We tried utilizing the virtual environment, but we had some issues in that area. It's one of the areas that we haven't revisited over the last half year because our volume is that high for us. Thus, it is one of those things that we have sort of left on the side for now, but I do hear there is some great stuff coming with it.
What do I think about the stability of the solution?
We haven't had instability issues.
What do I think about the scalability of the solution?
It can scale.
How are customer service and technical support?
The customer and technical support are great. We have received fast, sufficient responses. There is easy access.
Which solution did I use previously and why did I switch?
We did not have a previous RPA solution.
We were in a place where we needed to do something differently. At the time, RPA was something different. So, we needed to sort of examine, "Could this help us?"
How was the initial setup?
The initial setup was straightforward.
What was our ROI?
We saw ROI in eight or nine weeks, so it was fairly fast. We have seen a lot of performance benefits, which I would rate as a ten out of ten.
The solution has helped to eliminate many human errors.
What's my experience with pricing, setup cost, and licensing?
Our licensing costs are roughly 1.1 million Danish krones a year.
We see some elements in the license model that we're trying to figure out how to utilize. There have been some elements in the license model where UiPath has helped us solve them commercially, and having a license model which is more focused on scalability would be a great feature.
If UiPath really wants to put Attended Robots out to everyone, there will be a cost issue. We have some that we are testing now and what their effect will be. However, these are the robots where the license model needs to change before we go full throttle in that direction.
Which other solutions did I evaluate?
We also looked at Blue Prism and Automation Anywhere. We selected UiPath based on its object-oriented approach.
There is something off in UiPath's licensing model. Their competitors have started targeting us now because they know that we have a lot of bots. They have different types of licensing models, and say, "Because you are having so many jobs with so many job bots, you can save money on the platform by using us instead."
What other advice do I have?
Play with it and have a playful nature. Acknowledge that you don't know what you're doing with it, then just acknowledge that you're going to make mistakes. The only difference between being good or great at this solution is your ability to learn from your mistakes, because you will be making mistakes. Also, you will be overpromising when working with this solution.
For automation technology, in general, the system landscape is quite wide. We are just starting to put RPA on the shelf for automation. We are pushing a machine-first approach. RPA is the sort of tool on the shelf now helping us become a more efficient customer-oriented company. It is a tool in the landscape with plenty of existing tools, but this is the one that is the most easily accessible for the business people.
We built ourselves some automated documentation, and it was fairly easy to copy. One of the things that people start doing is documenting what they're doing in an organization and updating the documents, then freely sharing them. We would like some sort of automated documentation, as this would be helpful.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
CISO at Siminj
The product is easy to use and has exceed our expectations
Pros and Cons
- "The most valuable feature is its time savings."
- "They need to improve features around legacy systems."
What is our primary use case?
We use it for customer-facing and internal processes.
What is most valuable?
The most valuable feature is its time savings.
The product is easy to use and has exceed our expectations. We have a mixture of technical and non-technical people.
What needs improvement?
They need to improve features around legacy systems.
We currently lack in experience. Hopefully, after another year, we will be more experienced with the product.
For how long have I used the solution?
One to three years.
What do I think about the stability of the solution?
UiPath has been stable all the way through. We have not experienced any issues.
What do I think about the scalability of the solution?
It scales very well.
How are customer service and technical support?
The technical support has been good to work with for the few cases that we had to raise.
How was the initial setup?
The initial setup was pretty straightforward. Including the Orchestrator, the setup took one to two months.
What was our ROI?
We have seen ROI. It has eliminated human errors and saved time for other teams at the company.
Which other solutions did I evaluate?
We looked at Blue Prism and two other vendors. Based on our comparison, UiPath was the better solution with better licensing.
What other advice do I have?
My team uses the UiPath Academy and find it good and helpful.
Automation in our business is a new thing.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
RPA Developer at Danfoss
The product is reliable and gets the job done
Pros and Cons
- "We use it in a very large way across the company. Last year, we implemented approximately 22 processes and saved close to 80,000 hours total. This year, we have already saved close to 6000 hours."
- "You don't need to know coding, as it's pretty straightforward. The graphical user interface is easy to use. It is drag and drop. You do need to understand the basics of what's happening, what you're doing, and how the technical things work. However, after a short bit of training, you can start doing stuff, and the more you learn, the better you become."
- "With Excel applications, it is not able to handle a lot of pop ups. It should be able to do this automatically. We just change the format of the file from XLSX to XLS, but it should be able to handle this automatically. Instead, when something pops up, it gets stuck there. This type of thing are small, but still the process gets stuck. I would like to see better integration of applications to avoid these issues."
What is our primary use case?
We use it to automate administrative functions, like finance and HR tasks. We are also automating a lot of things in our SAP systems, e.g. updating prices.
We use it for a lot of small tasks, like downloading something from an particular internal website (e.g., SharePoint in Office 365) and uploading it back, or for doing modifications, then loading them back.
How has it helped my organization?
We use it in a very large way across the company. Last year, we implemented approximately 22 processes and saved close to 80,000 hours total. This year, we have already saved close to 6000 hours.
What is most valuable?
You don't need to know coding, as it's pretty straightforward. The graphical user interface is easy to use. It is drag and drop. You do need to understand the basics of what's happening, what you're doing, and how the technical things work. However, after a short bit of training, you can start doing stuff, and the more you learn, the better you become.
There are so many workarounds. It allows you to do complicated things in such an easy way. UiPath has provided so many APIs that make it easy to interact with other databases or applications without even going into them. If I want to download something from a website, then I don't need to necessarily go into it, I can use the API function, which is very cool.
What needs improvement?
With Excel applications, it is not able to handle a lot of pop ups. It should be able to do this automatically. We just change the format of the file from XLSX to XLS, but it should be able to handle this automatically. Instead, when something pops up, it gets stuck there. This type of thing are small, but still the process gets stuck. I would like to see better integration of applications to avoid these issues.
We are also making a lot of manual changes in SAP. We are looking for a solution where we don't have to make manual corrections every time, similar to what UiPath did with some SharePoint websites.
For how long have I used the solution?
Less than one year.
What do I think about the stability of the solution?
The product is definitely reliable. It gets the job done. The difference is in how you design it. When you start as a developer, you tend to always take the longest route as part of the learning process. Once you get used to the product, you realize something can be done in two steps instead of five.
A lot of people rely on what I design, so if it doesn't work, I immediately get a call that 50 people are waiting for something. This happens, but rarely, as it works perfectly.
How are customer service and technical support?
Whenever we get stuck on something and are not able to proceed, then we get in touch with UiPath, who will help us out. Their technical support staff is pretty good. These things really help the user out.
Initially, I used the UiPath Academy when I didn't know anything. At that time, I went through the basic training, then I had to leave the academy to focus on automating our company standard products, like SAP.
What other advice do I have?
I have been working with this solution for 11 months. I did not know about this solution before working as an RPA Developer. Now, you can challenge me on anything UiPath related, and I will find a solution. It is so easy to learn new things. It has good usability.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.

Buyer's Guide
Download our free UiPath Platform Report and get advice and tips from experienced pros
sharing their opinions.
Updated: June 2025
Popular Comparisons
Microsoft Power Automate
Automation Anywhere
Blue Prism
Automate
ABBYY Vantage
Tungsten RPA
Pega Robotic Process Automation
Moveworks
WorkFusion
IBM Robotic Process Automation (RPA)
Robocorp
Nintex RPA
VisualCron
SAP Intelligent RPA
Blue Prism Cloud
Buyer's Guide
Download our free UiPath Platform 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
The purpose of RPA is not to scale down employees but it make them more productive and skilled to outperform decision making. This is a good article on how RPA is disrupting the businesses in the world.