UiPath Reviews

I did a proof of concept for a music industry client. It went well, and the client adopted UiPath. 

UiPath improved lots of features, like sequencing, recording, etc.

I had some issues with the ERP Automation features, and the setup is complex. 

UiPath is stable. 

UiPath projects are highly scalable. There are lots of customization options and ways to easily scale your existing bots. 

I haven't contacted UiPath support because the solution is stable and doesn't require support in most cases. The UiPath community is strong, and you can find answers from multiple places online. 

As a project consultant, I analyze the client's applications and set up everything for them. The initial setup is time-consuming. UiPath involves a longer setup process than other RPA tools.

I rate UiPath a five out of ten for affordability. UiPath costs a bit more than other tools like Blue Prism and Automation Anywhere. 

I rate UiPath a seven out of ten. UiPath offers many customization options. I would recommend it to clients who want to do high-quality processes and complex use cases. You also must consider your budget because the license cost is a little higher than average. 

I'm using UiPath for personal use. I'm trying to create an application in which all the work can be automated, such as financial, HR, and educational-related work so that we can have easy access to the details of candidates.

I'm using it for a small edge case and UiPath is able to solve it in a great way.

I'm very happy with the automation because it gives me more freedom to make things work on my projects.

With UiPath I have been able to increase productivity because the manual work has been reduced and everything is now automated with NLT and ML techniques. We aren't required to go into the specific aspects of every document. We get systemized documents that we can go through and get the details. The NLT is a major part of it for me because it can sense the text and make it more useful for me. It converts it in a way that I don't have to go through all the details.

It has reduced errors in a drastic way and that is something I really appreciate in UiPath. I would estimate the reduction at nearly 25 percent. Before, we were doing this work manually and it took a lot of hours. Now it has been reduced by 10 times and maybe more than that.

I like the automation tool in UiPath that helps in creating the bots. It helps me a lot in getting details from documents. Also, the ML/NLT models are good because they help with data recognition.

Creating automation is pretty simple. Everything is clearly mentioned. And the UiPath team has helped a lot with the learning curve. The user community is very helpful in solving issues. You can find different channels and YouTube videos for details. In terms of community, UiPath is doing great.

Many of the features were very complex in the beginning but with some experience, it has become a great tool for me.

I have been using UiPath for about six months.

It's stable.

We haven't required technical support because the community is very strong and every problem and solution is already there. And the UiPath solution team is also very strong.

Positive

We did not have a previous solution.

We took our time with the deployment. It was a planned activity and it was very straightforward. We didn't face any issues. We spent time reading the documentation and going through the videos about how to deploy things. The entire activity took some days, but the deployment, specifically, took around three or four hours. There were two of us involved.

There is a little maintenance. Sometimes we have to manage the storage and other things, but it's nothing major.

The pricing is fine and the features are good. Still, the pricing could be a little lower. With tools like AI/ML, if the pricing can be reduced, everyone will be able to adopt it.

I would recommend UiPath. For us, it solved our use cases, and we are really happy with it.

Our company uses the solution to automate formula-driven processes that are completed on a frequent basis. 

We create unattended bots to handle tasks for our finance, procurement, IT, and HR departments.  

At this time we do not use AI or ML.

UiPath has been instrumental to our success because we have an excellent relationship with our account executive and a lot of support from the leadership team. 

We have met with their C-Suites for one-on-one conversations and like that type of ownership. We appreciate their commitment and dedication to our success. 

The solution requires little or no code and can be operated with minimal technical skills. This lessens our dependency on third-party providers and allows use by citizen developers. 

AI and ML need further improvements to reach mature status. 

I have been using the solution for eight years. 

The solution is very, very stable with no issues when we deploy bots. 

The solution is very easy to scale. 

Technical support is stellar and available 24/7. There are no limitations on when support is available, including in the middle of the night. No organization is perfect and there is always room for improvement, support is rated a nine out of ten. 

The community forum is invaluable and very helpful for troubleshooting. For example, we sought support from different forums to learn how to use our in-house desk for L1 support.

Academy courses are used to upskill our team and keep up with the fast pace of new capabilities. The solution is always transforming and acquiring new technologies. 

Positive

I previously used Blue Prism, Pega, and Automation Anywhere. 

The initial setup is very straightforward and easy to use. 

Our team of developers and BAs are able to navigate the solution without requiring any handholding from the solution's SMEs.  

Our in-house team deploys the easier automations.

We work with multinational partners for more complex deployments. Our team is knowledgeable and has the same competencies as MNCs so that enhances the partnership. 

The solution has improved workforce efficiencies by 120% and reduced errors by more than 90%.

We saved several million dollars within three weeks of deploying the solution.

I love the flexibility because ownership is willing to work with us to make sure commercials are viable. They are committed to being our strategic partner and are reasonable in terms of our current appetite. 

Our company solely uses the solution. We find it to be more user friendly than other options. 

Most products are similar, so it comes down to commercials and that makes the solution much more cost effective than other options. 

You should consider using the solution because there is a reason why it is the market-leading RPA provider globally.

I rate the solution a nine out of ten. 

The beauty of RPA is that it has many different use cases. We use the product as a standalone and as part of a bigger solution. Obviously, the tool itself is designed to automate activities that humans would do. But as the tool is getting smarter, we are able to do more types of activities.

There were two big challenges in the early days. One was the complexity of the rules that you needed to adopt for a particular task and the other was the type of data that was being used as part of the business process. As we've gone along, the product has evolved and allows us to do more of the business process.

We are able to offer more automation to a business process than we could before. It's all about the business process and how much of that can be automated and what still needs to be handled manually. UiPath gives us the ability to do more with automation and need less human involvement.

We used UiPath to automate processes for a good cause, free of charge, during the COVID pandemic. We used it to build automations that would take care of activities that nurses and doctors were having to perform, to free up their time to treat patients. Reducing the admin they normally might have had to do, rather than being front-of-house and dealing with very ill patients, speaks volumes for itself. We freed up time for our nurses and doctors to treat very sick patients.

When it comes to reducing the on-premises footprint, what we've seen over the last two or three years, with the pandemic, is the move to the cloud being accelerated. The whole digital agenda was accelerated. What we're seeing now is that most of the organizations we work with are more open to using a cloud solution. However, it depends on each organization. Some of our government organizations are not allowed to use the cloud. They have to use on-premises solutions because of strict data rules. But more companies are now open to using the cloud and that has an impact on the total cost of ownership. They're not having to invest in services and that helps reduce TCO.

AI models are now being pre-trained. There's a risk there because, obviously, you are using someone else's data and someone else's bias. But if you put those aside and use the pre-trained models, it's going to reduce the time to value because you're not having to train models. You've got something that can be run out-of-the-box. To be honest, we will always build our own models rather than exclusively use UiPath's. For instance, they have an email reader. We tend to use their model in conjunction with our own and that has helped us reduce development time on our AI models and our training.

On the subject of human error, anytime you ask a human to do an admin activity where they're typing in data, there's an opportunity for human error to creep in. And that can cause catastrophic events, downstream. Where you have an automation that is guaranteed to enter data that is 100 percent correct, you're always going to reduce human error.

Automation can also be used where a decision is made. Sometimes, human decisions can be fallible. If you have a decision being made by an AI model, it's not going to have human bias. It can have other biases built-in, but you can see an improvement in some decision-making as well. What we have to understand here is the introduction of AI into RPA is still in its infancy and there's a long way to go in this area. But there are definitely improvements being made by the introduction of artificial intelligence. It depends on how you use it and how smart your understanding of it is, as well.

Automation is all about trying to reduce the touch time of a human in a process to free up their time. If the automation is implemented smartly, it does so. If it's poorly implemented, you can end up with people being given so many exceptions that the bot actually becomes redundant. But as a rule of thumb, of course, it does free up peoples' time.

Similarly, if it's deployed smartly there are some benefits in terms of cost savings. However, we're not using it because it's saving costs. We are using it for our staff who don't want to do manual activities. It's not just about dollars and saving time. It's also about our staff and not having to do menial tasks, which can be demotivating.

It's not about the tool, it's about the business process and which component works best. The most valuable feature really depends on the use case. My favorite now is Document Understanding and the AI models that are being pre-trained. That's allowing us to do more, out-of-the-box, without having to do custom programming.

When I ask my developers which product they would like to use when we are doing RPA, they always say UiPath because of its closeness to Microsoft's .NET. Again, what UiPath are doing is enabling more out-of-the-box functionality without having to do customization and coding. The developers, and I, would say that it's getting easier to use for simple automations. It still requires planning and thinking for more complex automations, but you are able to do more with fewer skills. 

UiPath has something called Citizen Developers, which is where they encourage people to build their own robots and the functionality available is greater. Whether that's a good thing or a bad thing is a question for governance.

UiPath's user community was one of the strongest aspects from an adoption point of view in the early days. The forums, the community, were always something that they invested heavily in, and that was a smart thing to do. The community is still strong. They have a Community addition and the feedback we get from some of our customers, when they first play with this, is that it's a friendly community. People are encouraged to play with UiPath, and if they get stuck, the community is willing to provide them with advice and guidance in a friendly way. Not all communities are the same, let's put it that way.

We actually teach the UiPath Academy courses. We are a UiPath-accredited trainer, but we have, at times, with smaller organizations, suggested that they take some of the training themselves. It's another great area of UiPath, in addition to the community. Their training is available free of charge. That has always been a strong point as well.

Their licensing is poorly constructed. It's too complicated and not well thought out. They also outsourced their support model, which sadly has become less friendly and more automated.

It's very much in the early days, but another area they can continue to look at is bots building robots—the ability to take a task capture and turn that into an automation. There are always concerns over that: Who's going to police the police?

I've been using UiPath since before it was called UiPath. It was previously called DeskOver. I worked for Capgemini and I worked with the product when the company consisted of 30 people in a room in the very early days. Capgemini adopted DeskOver and then it became UiPath as a growth partner. So I have been using it for coming up on 10 years.

UiPath is stable. Like any product in the early days, they were updating all of the time. That used to not sit well with our bigger customers because of their update plans. As the product has matured, it's become more stable and the release plan has become structured. You now get four updates a year. It has become more mature.

It's scalable.

The environments that it can be used in can be very complex, such as "multi-tenant," where a tenant is the protection of data from Orchestrator, where you have segregation or air gaps. We've done some projects with a defense ministry that are very complex and we've done some very simple ones.

Most organizations start small. There will probably be a pilot with a cut-down version of what is needed. As they grow and scale, they will invest in more tenants and in more infrastructure and more components of the platform.

I would rate their support at seven out of 10, but the dial is going the wrong way. Because they've outsourced their support, you're no longer dealing with the original product team. I had a very good relationship with the product team where I could almost pick up the phone if there were some proper technical problems.

Now, that is gone and we're having to deal with a third party. As UiPath have grown, they've needed to focus on their core areas and outsource other areas. But it's getting harder to get good quality support because my customers are no longer dealing with them directly, they're having to go through a third party.

Neutral

We started off with Blue Prism, which was originally designed, and still is, for back-office processes. What we used DeskOver for was front-office automations, almost like "your little buddy who sits on your desktop." As UiPath grew, it started to erode the Blue Prism market because it offered the ability to do both front-office and back-office automations. That's why it became number one. It recognized that there were two distinct markets: front-office and back-office. Blue Prism always has done back-office, and successfully, but never offered the ability to do front-office. Customers didn't want to invest in two different technologies as that would be too expensive. That's why UiPath stole the match and has never looked back.

Back then, 10 years ago, there wasn't much else to choose from. It was really "macros on steroids." The market was very different. It was Blue Prism or some of what were very young companies. Automation Anywhere was just coming in as well. 

But at Capgemini, we recognized UiPath, and we liked Daniel Dines, who was their CEO at the time and is now Co-CEO. We liked his enthusiasm and we liked the price point as well. They were from Romania, they were cheap, and they were eager. We were able to work with a company that, at that time, was very competitively priced. And we were able to get them to start building stuff that we wanted as well, as Capgemini was one of the big six. We had a lot of control over their roadmap in the early days.

Each organization we work with will have different design principles. As a general rule of thumb, we encourage investment in the cloud license model because it reduces the time that it takes to actually get the implementation up and running, and it simplifies things when it comes to TCO. However, there are organizations that are constrained by security, and therefore they can't go down that route.

I'm an architect by trade and my job is to oversee complex delivery and deployments. It's all about the architecture. An architect needs to work with the client, in the beginning, to come up with a plan and a solution that's going to be fit for purpose. In addition to architects, you need a project manager, some engineers to actually do the implementation, and you're probably going to need a tester to test and commission the environment.

The initial deployment has gotten better. When Orchestrator, which is the main administrative console, is built-in as part of the cloud offering, rather than having it locally, it makes a big difference. The cloud has made the time to set up a pilot and deploy into production much shorter than it used to be with on-premises.

Most IT projects probably take three to six months to deliver a success. Whether or not the payback happens straight away depends on the investment costs. The benefit of UiPath and RPA is the rapidity with which you can get automation into production and beginning to pay back. RPA has always been liked by people in the business because it is a rapid deployment rather than something more strategic that can take one, two, three, and sometimes, five years if it's a very large IT program of work.

ROI isn't just about the dollar. It can be other things as well. If a program of work with RPA and UiPath is deployed smartly, you can see a decent ROI. But that ROI also depends on the declarations by the business involved. How many times do they execute the process and how long does it take to do it? How many exceptions are there? How many people are involved in that process? 

Business often thinks that volumes are higher than they actually are, and they may forget that other people may have to be drafted in if there are peak periods. Due diligence in building a business case is important. What you also need to do is revisit it six months later or a year later: What did we declare? What did we actually hit? Did the bot fall over because of X, Y, or Z? It is a continuous improvement process, as well as ROI. If you get the two working correctly, you get a stronger ROI.

What we find is that some businesses who don't use our consultancy skills will try and do it themselves, and they will come across some of the pitfalls that we are fully aware of, but they may not be aware of because they're learning, and that has a big impact on ROI. If they try to go after a business process that's very complex, at the beginning, without the right skills in hand, they can suddenly find themselves in a downward spiral from a development point of view, where costs and time are overrunning. Before they know it, the declaration they set has passed and they've not been able to hit those targets. When that happens you start to see an erosion of confidence from the business side as well. It all comes together. It's all about strategic understanding and technical know-how.

We now have the challenge of cost. It depends on what you want to do. If you want a very simple robot to execute normal front-office transactions, I would recommend Microsoft Power Automate because it's free. If you are investing in more complex things, then I would always recommend UiPath. 

UiPath is starting to price itself out of the market. It's getting expensive. That's fine if they continue to push the envelope of what they offer, but it's all about perception. And the perception over the last two years with my customers is that it's expensive. I trust it, but it's expensive. 

We're seeing year-on-year price increases. There's a price point they're getting to that is about the value and they need to be very careful about that. 

UiPath, as an organization, has changed massively. When it IPO'ed it was a Romanian company and very much a European company. Now, it's an American company with American values, and I think there is a misunderstanding of the European market compared to the American market.

In terms of implementing end-to-end automation, it depends on the process. We can do more with the advancements that I've mentioned, but every business process is different. I always say to my team, "This isn't about the tail wagging the dog. It's not the technology, it's the business process, and whatever tool is right, whatever fits." There are still exceptions that need to be handled by people so we're probably not there yet with end-to-end automation. 

Most good-sized business processes have business exceptions that require involvement from people. It's what we call "human in the loop." Two or three years ago it was 80/20 between automation and human involvement. We're now probably at 85/15 or 90/10, with more of the process being automated without human involvement. That's because there are smarter bots using AI—the brain—to execute automation tasks that previously had to be handed back to a human for decision-making or some other activity.

On its own, UiPath doesn't speed up digital transformation. It's a tool. It helps, it's a contributor, but as a standalone, it doesn't. It needs other things.

I had a quick look back at what their offering was in 2019 and what it is today. That's a good way of looking at how well they've listened to their customers. They've been smart in not just providing RPA. All their components now are far more than just RPA.

They've recognized one of the biggest areas is process identification, that whole journey of identifying an opportunity and taking it through the life cycle, with things like Automation Hub.

Generally, the response I get from my customers is they're impressed with the number of solutions that are available under UiPath's Enterprise platform.

We automate everything using the UiPath solution. We have some ongoing stuff, e.g., generating test cases and testing some of our development platforms. We need to define all the parts, such as how to test the entire environment to determine if everything is working okay.

We utilize all our services on the cloud, then they can be easily used across all our offices.

We only use unattended automation.

If a product is about to go live, we heavily rely on coverage from UiPath. This is during the development phase. However, when onboarding to production, we use other solutions, which don't rely on automation, for monitoring purposes.

When we are in the development phase, we have multiple edge cases, like iOS, Android, and other platforms, checking in. For a tester, it is difficult to check every edge case. Instead, we define automation test tools in UiPath, then our automated work does everything for us. Once it is done, it gives us a detailed analysis about where the product is performing well. We get handy videos before going live so we can improve everything and ensure that our end customer will not be impacted.

Our bandwidth has been drastically reduced, by nearly 60 hours, because of this solution. We have reduced the number of testers by three. 

The most useful feature of UiPath is that it is very easy to use. 

It helps us a lot with digital transformation.

The UiPath solution doesn't currently provide unique testing for mobile devices.

I have been using it for around six or seven months.

To the extent that we are using the solution, it is pretty scalable.

We use a third-party for support of this solution.

When we were facing some small issues going to the cloud, we tried to get help from the community. The community has been very helpful. Everyone has been willing to provide some good information to other users.

Previously, we were using an automated script to test everything. Now, with UiPath, we are automating everything. 

We used the community to help us with the setup.

The vendor helped set this up and guided us how to do everything during the onboarding process. Therefore, we didn't have any issues with the setup.

UiPath has reduced human error by 20%. 

We have reduced our costs by approximately $200 a month.

Creating our digital transformation didn't require any additional costs.

The vendor gave us a 30-day money-back guarantee. We were fine with that. We saw improvement during that time and kept the solution. 

We didn't consider any other solutions.

I would rate UiPath as eight out of 10.

With federal governments, a lot of the use cases vary around what they're doing, however, it's just a lot of PDF, Excel, and Microsoft Suite automation and then interacting with their custom and web-based tools for subject information.

We don't use it a ton internally. We do more consulting services where we help other organizations get it set up. We're trying to look at maybe more internal ways to use it, however, most of what we do is external. That's just our entire model.

The typical spiel with UiPath is you're getting rid of the tedious and redundant work and you're saving time for people and bringing them up to do more human-oriented tasks.

Anything and everything under the solution has been very helpful for us. UiPath Studio is the most valuable for what we're doing simply due to the fact that it’s development software.

The most valuable part is how it interacts with the websites. A lot of the other automation solutions aren't doing that. A lot of what we do is involved in web-based automation and that's pretty key.

As a developer, the ease of building automation is great. I don't know if it's easy for the typical business user that I interact with. That's why there are professional services to develop and things like that.

We do use the UiPath Academy courses. UiPath Academy is great. It's one of the best online training platforms I've seen. That said, it’s an average user base that we're working with. I've had to teach people how to copy and paste. That level of user is not going to learn how to do variables and selectors and things like that.

The science of the software's easy enough to pick up if you know how to develop and I thought the Academy was fantastic at helping the learning process along.

The biggest value that the UiPath Academy offers is just the ability to train somebody up and know how to use UiPath in roughly a week.

The solution has saved costs for organizations. The exact amount is very tricky to quantify as I have multiple clients. It depends on which client we’re talking about. A lot of them are coming up in the beginning stages. My first client saved around 200,000 hours, which was significant. More recent ones may be in the tens of hours at this point. Those numbers relate to nobody specific, just a fledgling RPA program.

UiPath has reduced human error. That said there's plenty of bot error that occurs. You have to be aware of that if you are going to replace humans. I haven't honestly tracked it to see what the percentage is on errors on any of my projects, however, I would assume it is a reduction, and yet not quite 100%.

Right now, reducing errors is not yet important for our business and the businesses that we consult for. We don't really come across processes where there are so many errors. That's what we need to fix. It's not why people are using it. They're using it for the ROI value.

The solution has freed up employee time. It generally allowed the employees to focus on higher-value work and their level of satisfaction with the job.

I’m not sure if the Academy fulfills all of our needs in terms of staying up to speed with the solution. I haven't really gone back to the Academy after I first got through the development training to look at other solutions and stuff. I usually just rely on meetings with UiPath.

The stability needs to be improved, as does the scalability. 

We've used the solution for four or five years.

In terms of stability, that's where there's room for improvement.

It just comes down to a lot of selectors and items of that nature. Selectors can fail randomly and then start working again and can cause issues. That's been our issue with stability.

The scalability is directly tied to the stability. It's a lot harder to scale the solution to run on a lot of computers. Each of these has some unique issues when it comes to deployment.

With my current client, we have probably around ten users at this time.

Technical support is great. Also, the UiPath forum is super helpful, however, when I've used the license key, you got actual support and that's been really good.

I'm not aware of the company using a different RPA solution previous to UiPath. I personally only use UiPath.

The initial setup was straightforward. The deployments have taken six months to a year.

We have seen a return on investment from the companies that are utilizing this solution.

The individual robot and studio licenses are good. Usually what I see clients shake their heads at is the add-ons, the AI capability. Insights, for example, was very expensive. My client didn't want to get it due to the price.

Orchestra is usually acceptable as it's part of the package, however, the other stuff that's not studio or robot, usually, clients aren't, in my experience, interested in paying more.

We are primarily focused on UiPath due to the fact that that's what our clients are using, however, we're vendor agnostic. We support UiPath, Blue Prism, and Automation Anywhere as well. We have developers that are all trained in each of their usages. Whether we use them all at once or suggest them depends on the client. We have one client where they're using a bunch of them, however, most of our clients use UiPath I'm with the federal government, and UiPath is the only one that's really approved to do that. 

I'm not sure which version of the solution we're using.

We do not yet use the solution's AI functionality in our automation program.

I would advise new users to be patient due to the fact that it's going to take a while for it to get stood up. Also, when you are working with the federal government, there are lots of approvals. Other than that, new users should make sure they get use cases and have everything very well documented. Users need to understand all the decisions and the logic behind it. That's the main advice I'd give.

I'd rate the solution at a nine out of ten.

We're a revenue cycle management company for medical billing. We've reallocated our charge entry employees. We're using bots now to do the charge entry on medical claims and then also payment posting along with eligibility and AR. We've been able to reallocate about, just within this last year, probably eight employees. They've been reassigned to more valuable work - things that the bot can't do and actually requires a human to do. We've been understaffed, so it's actually worked out great for our company.

The ease of building automation isn't a problem. It seems to be very easy to do to a point. Our challenge is we work in a live environment. We're not able to use a test environment when we build things out. We have to go very slowly.

I'm not that familiar with the product, with the solution, however, the UiPath apps feature and OCR are great. That said, we're not using any of the apps currently.

The biggest benefit we've seen is the accuracy. Even just with employees calling in sick or not having enough staff. We’ve been able to fill those roles.

The robotics piece has been a huge thing. We're doing medical claims. We're always worried about claims not getting paid. This has been able to capture those claims so that people get paid the first time. One of the other things we track is how many times we touch a claim. For example, how many clicks. We couldn't do that before. That's been very valuable to us.

We’ve improved our efficiency in a way for sure. Even just our cost analysis has improved. When we do new contracts, we know what it's going to cost exactly.

I don't know if it's UiPath as much as just what we do is really complicated. Even the consultants that we've used with UiPath, even they've said, wow, this is very difficult what you guys do. There are a lot of moving parts, so it's not as much of a UiPath problem in terms of limitations. It's just our own processes.

Right now, I don't think I've been on there long enough to know if there are missing features or functionalities I’d like to be added.

I’m talking to people right now, to see how it can do things better or how we could use it more effectively. We’d like to discover what worked for other people.

We've been using UiPath for about maybe a year and a half tops.

I haven't had any problems or concerns right now concerning stability. The biggest concern I do have is that we've already invested six people in this. We're going to have a lot more that will, more or less, not have the robotic piece as part of their job. That work will be reallocated. I have about a hundred employees that UiPath could technically reallocate.

When I look at that, I worry about if something does happen or it doesn't work or there's no backup. Then, suddenly, I don't have employees. Right now, we can jump in and some humans can do the work if necessary. My concern is that in the future they won't exist. This hasn't happened yet. I hope it doesn't.

Scalability hasn't been a problem at all. We can just continue to add bots every time we need them. It's been easy.

We started with two. Three months later, we added another two. After another three months, we add another two. From our standpoint, it's great. My UiPath rep was shocked that I keep adding more, so that's good.

I have not used technical support.

That said, we had one issue with UiPath where something didn't work. We talked to them and it was taken care of within a couple of days.

My vendor is working with them. They mentioned there was an issue with insights that they are working through. Insights are still not quite functional, or there are some resources we need. However, the vendor is dealing with it directly. It's a work in progress. 

We did not previously use a different RPA solution. 

The initial setup was pretty easy. We didn't have any challenges with that. I contacted one of our vendors and they ran with it. We didn't have issues at all.

With the vendor, it took us about 30 days to deploy UiPath. After that, in terms of implementing bots, the first bot took us about three months. Once we did the first one, it just went really quick after that. We could reuse some processes which made it faster. There was a lot of reusing of the same. We were also internally understanding what information they need and how it works.

It was all new to us. I'm still learning the acronyms they use. We need to learn what they are talking about. We’re not IT-based at all. It's definitely different.

We had the solution implemented by a vendor. They implemented it all. We didn't have any challenges as far as that goes.

Our experience with the integrator was good. I would say that they didn't realize how challenging it was going to be or, at least, the person who integrated didn’t. At the same time, they know almost everything about my business now.

UiPath has saved costs for our organization. For example, we’ve allocated six employees that are paid around $40,000 a year and we've implemented six bots to do those same functions and they're around $8,000 a year. In a way, we’ve doubled our staff, and almost tripled our ROI.

We had a problem before with the pricing, however, for the most part, it's fine where it is now. My ROI is fine. It works great. I have zero complaints.

You have to do a package at a time. That's my only challenge, where sometimes I don't need that many licenses. 

When you first sign up, it's a package that can renew every five years. I don't necessarily need everything. I'd prefer just to pay for certain pieces. 

We did not evaluate any other options. We started using UiPath due to a referral at a neurological healthcare conference about four years ago. The speaker suggested UiPath. I actually didn't know of any other company until after we were on UiPath. We've since talked to others who have used other solutions and they mentioned that we made the right choice when we chose UiPath.

We started on-premise for the first six months and then we actually moved to the cloud.

We do not use their UiPath apps feature as of right now.

We are mostly using unattended automation.

We haven't really calculated the reduction in human error. We're just moving on to our Insights app. We're just getting ready to launch that, so we're not there yet. We don't know what that turnaround will be.

We do not use UiPath's AI functionality in our automation program right now.

Our teams have not yet used the UiPath Academy courses.

I'm a little concerned about having to bring on more people that are not in this industry. We're going to have to start them over from the ground up, which takes time.

When we first started, we wanted to know if it really worked. We got a certain budget and just started using it, and now I can say that yes, it does work. We can see that now that we've stepped back. We should have done it earlier. That's what I would tell people. I would definitely tell people to look at it first, before anything else. 

I'd rate the solution at an eight out of ten.

Currently, we are using it for reading emails. We download the attachments that we get in emails. After downloading those Excel sheets attachments, we process the data based on a few rules. The processed data is input into the SAP application. In the SAP application, based on the business rules, we process the data and commit.

It is very user-friendly in terms of building automation. We don't need to be experts in coding. We can learn it easily and build complex business tools in UiPath. We don't need prior coding experience.

It reduces the cost of digital transformation. Every day, we get 10 Excel sheets, and somebody has to sit and read the Excel sheet and load the data manually into the SAP application. Three to four employees are required for the same job, but if we automate this process, it can be done in a minute. It is easy, and we save time and cost.

It reduces the time taken for a task. If we are manually filling timesheets, we need to open the website, fill the timesheet, and submit it. It can take 10 minutes. With automation, it will take just a minute.

Orchestrator is very useful for deployment and publishing, maintaining queues, and running jobs.

In UiPath, REFramework is useful for different use cases with predefined code templates. There are well-established steps. There is a step for code marginalization. Similarly, there are separate steps for initialization and processing. For closing an application process, a step is there. So, it is very well modularized for getting the transaction data. If there is one exception or anything wrong happens with an application, it will log the exception in the orchestrator and send an email. It can also close your applications and end data processing. So, everything is well organized and separated, and we can log the exceptions separately in the queues as business exceptions or application exceptions. We can have the complete report of a particular queue.

For document understanding, there are so many features. I haven't used them practically, but to read a PDF, there are patterns and semi patterns. A wait option is also there for somebody to come and correct it. It can wait until somebody comes and corrects it, and then it will do the processing. So, all of the features are very useful in UiPath.

In exception handling, wherever exception occurs, the out arguments are not being passed. It would be good if there is a way to pass the out arguments. 

Sometimes, when an element is not there, UiPath gets stuck, and it doesn't even throw an exception. It stays stuck for hours until we go and check the logs. When this happens, we have to kill it. It happens in some cases, so an improvement is needed there.

I have been using this solution for three and a half years.

Other than the issues related to the exception handling and UiPath getting stuck, it is very stable.

It can scale well, but we don't really have a need to scale it. Currently, we are automating 15 projects. We are planning to use other functionalities of UiPath to automate extra things.

Currently, we have 1,000 people who use this solution. They are consultants, developers, and business analysts. A business analyst takes care of making design documents and solution documents. The RPA developers develop the code and test it. After that, for deployment, someone is there to take care of all technical things. After that, the support team is there to look after the deployment.

I didn't call UiPath support, but I know about them from my friend. We had called them for some issues, and they answered those very well. I would rate them a nine out of 10.

I have worked only on UiPath.

Its initial setup is straightforward. It is not that complex. We need to install UiPath Studio, and then we connect it to Orchestrator for getting logs, etc. It doesn't take more than an hour.

I took the help of my colleagues.

I'm not sure about licensing and pricing, but the pricing for their certification is a little bit more. Previously, we could do it for no price.

I would definitely recommend it to my colleagues and others. It is very user-friendly.

In terms of reducing human error, it is not up to the mark. It detects human errors, but it waits until we place the correct files for processing. For example, when comparing files, a human can detect two almost-similar addresses as the same, but a UiPath bot cannot do that. So, in some cases, it won't work as humans. It cannot decide. It works on predefined rules.

Considering its areas of improvement and the cost of certification, I would rate UiPath a nine out of 10.