UiPath Reviews

We use the solution as an automation platform that even those without coding knowledge can use for automation-related tasks, such as PDF and Excel extractions. We're an IT services provider and use the tool for insurance data and other client requirements.

UiPath significantly improved our organization's productivity and strengthened our client relationships.

The solution reduces the cost of digital transformation, and we can now expect to see a 300-400% ROI. Doing so did not require expensive or complex application upgrades or IT support. The complexity of performing automations depends on the project size and ranges from very easy to moderately difficult on larger projects.    

The product reduced human error, improving the quality of service we can offer our clients and resulting in higher output accuracy. 

UiPath freed up employee time due to reduced errors, less human involvement, and less manual work. The time saved depends on the project size, but generally, it's approximately 40-50%.  

UiPath is straightforward and easy to use, even for those without coding knowledge. 

The solution's drag-and-drop functionality and templates save a lot of time.

We can easily build automations, removing humans from the loop, reducing human error, and saving time, to deliver positive outcomes for our clients.  

The solution enables us to implement end-to-end automation, which is excellent for reducing human error as there is no human involvement. It also reduces our dependency on humans and rapidly provides us with extracted data without manual work. End-to-end automation is essential because it allows us to carry out projects even if no team members are present, making it easier to conform to client deadlines.    

It would be good if the product could work locally, without depending on the internet, as connectivity issues can cause problems.

We have been using the solution for two years. 

The solution is highly stable; I rate it 10 out of 10 for stability.

UiPath is very scalable; I rate it 10 out of 10 for scalability.

The technical support is excellent and responsive. 

Positive

UiPath is the first RPA solution I've ever used. 

I was involved in the development, testing, and deployment. The initial setup was neither remarkably straightforward nor complex; it was moderate.

Our ROI is in the region of 40-50%. 

The product is very affordable, not costly at all.

The solution is very cost-effective for us.

We evaluated a few options, including Microsoft Power Automate, but it's a little more expensive than UiPath. UiPath also looks more modern, has a vast developer community, and excellent customer support.

I rate the solution 10 out of 10. 

Being a part of the UiPath user community is valuable; sometimes, when we encounter issues or have queries, we can quickly get a response from the community.  

My team and I have used the vendor's UiPath Academy courses to improve our skills and knowledge of the solution. This was especially useful when I first started to use the tool, as I needed to gain experience in RPA. Anyone can take a UiPath Academy course and learn to use the platform without any additional hassle or training, regardless of coding skills and previous experience.  

My advice to others evaluating the solution is that I rate it very highly, and it's great for automating manual work. 

We started with a pilot for our payroll department. It essentially takes the transactions that come into our payroll department on Fridays and Mondays, and sorts through those transactions. If there are any discrepancies or errors based on the defined criteria, it notifies the payroll department, and they can rectify those. Otherwise, paychecks don't process. 

Other than that, we have some data migration between Excel spreadsheets that we do, and we have contracts that we host on a web server that, if they don't have transactions for the same period of time, we have the automation go in and close those contracts out so the transactions can't go against them.

This was pretty much our first experience with automation. There wasn't anything prior. As far as UiPath is concerned and how automation has transformed the agency, we've found that hundreds of thousands of hours are being saved every year now, thanks to these processes. On a division-by-division basis, hundreds of thousands of dollars are being saved every year.

The wide variety of activities that are available for third-party applications has been quite useful when it comes to APIs. It's allowed us to leverage the other applications that we use within the agency. We can actually utilize the UiPath Suite over things like Microsoft Power Apps, Blue Prism, or Automation Anywhere, where they didn't have the capability to really interact with a bunch of third-party applications. 

UiPath helps save taxpayer dollars, which is a good, socially responsible, cause.

The UiPath community is very good. Eight to nine times out of ten, if I have a question or I'm stuck, I can go to the forums, and I can find experts, or I can find YouTube videos, and I can talk to other people. The contractors that we've worked with in the past were super helpful, and everybody's cooperative. Everyone wants to share ideas. At the end of the day, we all want just to make everyone's lives easier.

I've used the UiPath Academy's courses. I was thrown right into the fire. This was thrown on my plate, and they said, "Hey, you're going to be working with the contract; you got a month to spin up an automation." 

I learned while I did; however, as our center of excellence has grown within the agency, we've decided to adopt some new developers into the program, so we don't have to run into that same issue with new people. With the two or three that are coming up to be trained for the end of this year, it's definitely proven a lot of value, since we don't have to sit around and have people sit over shoulders for projects. It allows them to take their time, go through it, and practice. For me, going through some of the advanced courses, for the most part, I found them very well run and have been satisfied with them.

One thing that I would really like to see is some migration processes between environments. Right now, we either rely on a very rough CI/CD pipeline and/or manual efforts to transfer packages from one environment to another. Having some in-suite migration process would make our lives so much easier. 

The education aspect is probably the hardest part of getting people on board. Our server administration is separate from the rest of our CoE. We have to rely on them, and they're not necessarily privy to the UiPath Suite in general. Making it easier for them would make our lives easier, thus making our customers happier.

We've used UiPath for about two and a half years. We adopted it in late 2019, or early 2020.

We host on-prem, so I can't speak for the cloud support, though I've heard only good things. As far as stability is concerned, in terms of everything that we've moved into production, the only reason anything's ever broken, the only reason anything has ever not worked in general, has been due to agency oversight of people changing things without notifying the proper teams. As far as the UiPath's concerned, I would say it's pretty close to 100% stable.

The scalability question is hard to answer. The bottleneck is the fact that we are in the public sector, and we're dealing with a lot of state bureaucracy. We're limited in scalability, due to constraints that are outside of UiPath. I will say that as time has progressed and the more this technology's been adopted - including education and business awareness - the technology itself is very scalable. What's holding it back is general knowledge and public knowledge.

Most of the technicians I've worked with have been very helpful. Even if they don't have the answers, they're usually pretty good at getting back to me within two to three days and have relatively good answers. Or, if they can't answer it, they might steer me in a direction that will help me. 

As far as our accounts are concerned, we actually just received a couple of new tech advisors that deal with our agency. The team has been nothing short of fantastic to us. There have been times when we'll have our weekly meetings where they won't have the answer for us, and they'll say, "I'll get to you by next week." There have been times he gets back to us an hour after the meeting, and have detailed everything, or scheduled a call, so we can work on something together. That's been fantastic.

Positive

I did not previously use a different solution. 

I did the development, and I worked with our administrative team to deploy that automation.

It was straightforward. The education part and trying to have our center of excellence be centralized and having people all on the same page takes time. It came down to that whole migration where we are either working with a third-party application or system, like GitLab or some CI/CD pipeline, to get those packages migrated, or doing it manually led to a lot of hiccups throughout the course. 

What could have been done in a matter of hours or maybe a day or two, ended up taking, for almost every one of our automations, about a week or two, thanks to meetings, communication, and lack of education.

We have two environments. We have our Test DEV, then we have our production.  Once the developer completes the testing, it's sent over to our BAs; our BAs test it, then they verify that information with the customer to ensure the results are satisfactory. We then contact our server administrators, migrate the package over, and discuss the run time with the customers. 

Also, all of them, up to this point, have been unattended, so they're able to select a time and a date, whether it be daily, or weekly, or whatever that case is, and a time. We settled on a Thursday implementation date, no matter what, and the server administrators above the back page, then it goes on from there.

As far as consultants were concerned, they worked with us on the initial pilot. Everything else was done in-house. We have taken a step back to readdress our statement of work and how we plan on governing RPA going forward. We are working with a consultant company now to deal with more of the administrative overhead that was involved with this. However, we do plan that moving forward all development and deployments will still be held in-house by our developers and our administration.

My understanding is we are expected to hit the ROI that we're projected to hit next year. Even this year, with only three automations running for the entire year, we were able to cover our costs in that aspect essentially.

There are no more than five automations in full swing, and we would like somewhere between 15 and 20 next year. Likely, the ROI will continue to snowball. 

One of the automations that we put live essentially monitors updates to vendor contact information and conversations that are held with the vendors in our agencies and uploads that to a web database. Then, those conversations are logged in an Excel Spreadsheet that managers like to keep updated. This is roughly saving, on average, about 40 hours a week. Multiply that by 52 work weeks, and it's a lot of savings. It's roughly the cost of two full-time salaries that we are saving.

I am not super privy to pricing information. 

In the beginning, we were choosing between Blue Prism and UiPath, and keeping Microsoft Power platforms on the side burner to possibly automate things that were specifically within Azure and AD. 

While those three were being measured and worked through, we had to go through the bureaucratic chain of state government. It turned out that the UiPath suite, in general, was covering the bases we needed to cover with the third-party application integration. At the same time, the ease of getting everything up and running, the fact that we had a one-stop shop, and we didn't have to buy all these extra additional components just to make simple automation was worth it. Then, just talking with different industry leaders, contractors, and consultants, everybody suggested UiPath when it came down to Blue Prism and UiPath. That was the route we went.

We have yet to use the AI's functionality.

If you were a company looking to expedite as well as remove the monotony of a lot of the work that gets done, especially in the public sector, this is a good option. You likely have the same thing written down probably five times in 16 different places. Getting rid of that workload to free up people for doing other things, is the way to go. 

The most important aspect of all of this isn't having an amazing developer. It isn't having your great server admins or whatever the case is. It's making sure that the people you want to work with are educated and on board before it even starts. Making sure that people understand what RPA is and what UiPath can do for them is the most important thing. Our biggest roadblocks and the biggest things that have sprung us forward are all based on that educational aspect.

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

If you asked me that question two years ago, I probably would've been closer to a six out of ten. The product improved, and the overall competence in the industry, and within the company in general, has improved across the board. The people I've worked with, including our tech advisors or sales rep, are great. There's a lot more confidence and stability. It's definitely given our agency a sense of confidence, and it's much easier to see where this is going. The results are what we've imagined. Everything seems to be much more real at the tail end of 2022. We're hoping this will be stable for our agency in 2024 as well.

I use this solution to download investor suspenses from 35 different investors in warehouses and populate those suspenses into our loan origination system. Once those suspenses are cleared, we get purchase advice to receive money and give capacity back to the warehouse lines to continue lending. 

We have 10 operational robots as well as other automations. These automations include populating interim servicing payments that come into the LOS, so we have a historic record of it. I am working on a project to reduce the amount of new folders or maintain existing ones. This helps us reduce the cost of document storage in our LOS. 

We make use of UiPath's user community to see different people's insights, exchange ideas, and identify features that could work well for our business. We also make use of the UiPath Academy.

This solution has reduced our expenses by $30,000 a month. It has helped us reduce the costs of labor and continue to grow and scale.

One of the most important features of UiPath is the transactional basis of how it works. I can see which ones are successful, and which ones are not, and then have the bot take care of 98% of it. Our staff only deal with the exceptions and this has led to greater job satisfaction.

This solution has empowered us to take care of and create new integrations and help facilitate different processes and workflows to continue to streamline and scale our business.

In the future, we'd like to make use of the machine learning capabilities that UiPath offers and AI to scrape data off of different documents, log into different websites and populate the information where relevant. 

UiPath's AI functionality enables us to automate more processes overall. It allows us to pull information from various documents and populate it into different systems. This has enhanced the user experience. 

UiPath could be improved by offering overall solutions instead of just having the RPA process. 

We have been using this solution since 2020. 

This is a stable solution. The bots in the system are stable and function according to their instructions. They only stop when they encounter a new scenario they have not dealt with before. 

This is a scalable solution. We're also looking to expand our center of excellence to be able to take on all of UiPath's functionality and features.

I deployed the software and the Orchestrator Studio. I run eight or nine virtual machines that I have our LOS on and created processes where the LOS can feed the work queues so it takes care of different processes on schedule every day. The deployment took four months. 

We worked with different contractors to complete the deployment. 

I was allocated $50,000 to buy bots and create processes. I created about six or seven processes and then we calculated the savings. For the 50 grand, we had realized $1.5 million of savings. Although we don't always achieve this, it is possible to get a $7 return on every dollar spent. 

We evaluated many other tools including Automation Anywhere. One of the things that I love about UiPath is that the whole community and the company continue to deliver new cutting-edge tech. Every month we have a preview of new releases. It's not just one thing being released, there's a whole plethora of things and functionality being released.

On a scale of one to 10, I would rate UiPath's solution overall an 11. I would advise others to just get started. It'll more than pay for itself and you'll be amazed at the capabilities and functionality that you'll soon have in your arsenal to execute different projects. 

We provide RPA solutions to different companies in FinTech, finance, and other fields. We are mainly working on their recently launched product called UiPath Apps, and I'm designing apps with UiPath Apps.

I'm not from an IT background, but I'm still able to do development by using UiPath because of their minimum coding approach. They have a drag-and-drop facility. You just need to create the logic. You just need to imagine the data workflow, and then without using any code, you just create a workflow in UiPath Studio, and it'll start working.

It has been helpful in automating repetitive tasks and invoice processing. We are getting very good results, and we are continuously improving the processes in our office.

We are able to remove all repetitive tasks. We are using RPA for HR, salary generation, interview process, appointment, etc. We are using RPA everywhere. We are in the top five just because of RPA. It's very important for us.

UiPath Apps has increased the number of automations we create while reducing the time it takes to create them. We have saved approximately 30 minutes because with the use of UiPath Apps, we are not going to open any browser, and we are directly launching our processes by using UiPath App. There is no third-party integration. That's why the process is quite fast.

We have some automations that require collaboration between the robot and humans. The representative sitting in front of the system is now free for other work. The repetitive tasks are done by the robots. If there is any error in the workflow, the robot sends a message to a representative. The representative only needs to get involved when there is an issue, and the robot will start again. So, most of the time, our representatives are free for other work, and most of the work is done by the robot. It has reduced 50% to 60% of day-to-day office work. People have a lot more time to do other important tasks.

Our AI department with 20 to 25 members uses its AI functionality, which has enabled us to automate more processes. With the help of AI, we are able to do more complex automation. We are also able to process unstructured data.

It speeds up digital transformation and reduces the cost of digital transformation without requiring expensive or complex application upgrades, or IT application support. It's all included in the same price.

It has definitely reduced human error. We are now able to improvise our document understanding. We are also able to read handwriting with 90% to 95% accuracy. There is no intervention of humans in the onboarding process, and HR is now free for other work. The joining process, appointment letters, document verification, and other things are automated. Previously, just the document verification would take an hour for a single employee. They're now using their free time to upscale and broaden our company's business. They can take on extra work or projects during their office time.

It has been quite good in terms of employee satisfaction. We have a rating of 4.8 out of 5 in terms of employee satisfaction.

It has reduced the costs of our automation operations by 5% to 8%. It's not much because there are very few people involved in the HR department for the onboarding process.

It has saved costs. The organization is able to reduce the number of non-skilled people. That's quite impressive. They are saving a lot. They are hiring only skilled people. Previously, they needed four to five people for all the repetitive tasks, and now, a single person can do that work.

Their AI center is quite good. It provides a very efficient way to work.

UiPath Apps is a recently launched app by UiPath. It has lots of great features, such as direct integration of data in their UIs. It's very easy to display the required data, and the integration of the processes is also easy. It's easy to integrate the processes or workflows designed in the Studio with UiPath Apps. You don't need any coding or complex scripts behind this.

We are using the UiPath Academy. We are doing some on-premises training and online training to give the intro about RPA to our employees. UiPath Academy is completely free. The idea of role-based learning is very impressive and effective. If you are a developer, you just go and click on role-based learning. You will get all the data in a format required by a developer to learn and get to things.

The UiPath community is quite impressive. We get the answers within minutes or seconds. It depends upon how to post or publish on the committee forum. When I compare it to other industries, the UiPath community is categorized according to the technology. They have every category. For the UiPath App part, they only have the UiPath App experts. Similarly, in the Studio part, they have only studio experts. The UiPath people are already available in the forum. If you didn't get your answer, you will get the answer from the company itself.

I have been working on UiPath Apps for the last six months, and there are a few things to improve. The tables are not working properly. There are issues with the table display and the filter function in the tables. There is also an alignment issue. You can't edit the alignment of buttons.

There is also a lack of tutorials. They have a lot more functions, but there aren't enough tutorials to know how to use all the functions. They have free training in UiPath Academy, which is good, but the way of training is not impressive. They're using the textual format. They are providing lots of documents to read. It would be more effective if they were in video format. It takes more time to read and understand the content in text format.

It has been four years. 

It's completely scalable. We have approximately 150 users. We are mainly a UiPath organization, and it's being used daily. Our company started in 2017 or 2018, and we are only providing the RPA solution. In the last five years, we are one of the growing industries in India. We are in the top five companies in India in RPA.

I would rate them a 10 out of 10. Even their software developers are ready to take the questions. Many times, I've also talked to the developers from UiPath about our doubts and problems.

Positive

I have worked with Automation Anywhere. I switched because of the ease and less complexity of UiPath. It's easy to use and easy to install.

I have also tried Blue Prism. Blue Prism is more complex. It's even more complex than Automation Anywhere.

It's simple. It's a one-click installation. It takes a few minutes or even seconds.

It can be deployed by a single employee. The solution architect can deploy it.

Before searching anywhere else, just go for the UiPath Academy training. You will get all the things there. After finishing the training, you can switch to YouTube and other resources. The UiPath Academy is sufficient to teach you about any launched product.

I would rate UiPath a 10 out of 10.

My company's major use case for UiPath is to create automations for web and desktop applications. For example, we use it to automatically download content from another page or PDF. It's creating automatic programs to help us download data from the website or application.

For our organization, it has made our work a lot easier. Before UiPath, the tasks that we are automating were done manually and they were very time-consuming. Things were inefficient and many errors and bugs popped up. With the automation that UiPath has provided, the time required for those tasks has dropped significantly. A task that required four or five hours is down to 15 or 20 minutes, with zero or a minimal number of errors. That is one of the major impacts that UiPath has had. It has improved our overall efficiency.

The time we have saved can be invested in other aspects of our business, like lead generation or preparing the website. UiPath automation has saved us a solid amount of time.

Within a week of deployment, we were able to see results.

Another feature is the ease of creating programs with UiPath. Other RPA solutions are not that easy to use. Any person who is a beginner using this platform can learn it very easily. The deployment time and implementation time are greatly reduced when it comes to training our employees on this software. We are able to do our work much more quickly and efficiently with UiPath.

One thing that I personally like very much is the drag-and-drop capability in UiPath. I don't have a coding background. One of the major selling points of the solution is that it requires very minimal coding to create a program. It's very easy to drag and drop to create the required fields from the tool. That is one of the key and interesting features. The entire user interface and user experience is enhanced because of low-code and no-code abilities.

Other similar software solutions that involve coding take a lot of time because once you start coding there are errors that pop up. With the drag-and-drop feature there is nothing like that. It's instant. When you drag and drop you can see an immediate preview of what the output will look like. Work that would take two to three hours is done in 10 to 15 minutes, so that much amount of time is saved when creating a workflow.

Another feature is the Activities menu. It's a type of log system in which I am able to check what activities have happened. It keeps me updated.

The things that I use in UiPath are very comfortable for me and I find it very useful. I'm pretty satisfied with the current feature list. I don't think anything else is required.

There are two editions of UiPath. One is the free Community version and the other is the paid Enterprise version. I have used both. The feature updates in the Enterprise version are very regular and the support is quite fast. That's not replicated in the Community version. They could bring both versions to an equal level so that people who are just starting, with limited staff and a minimal budget, can use the entire feature list of UiPath in the Community version. 

Apart from that, in terms of the features and the simplicity of the product, it's on par with all the other top solutions out there.

I've been using UiPath for 15 or 16 months.

They do monthly product updates and, after an update, the system doesn't lag or crash. It's pretty stable for the updates that they provide. 

Until now, I haven't faced any bug, software, or performance issue with UiPath. It has been a smooth ride and I hope it continues like that.

I believe it is a scalable solution.

In our organization, it is deployed across multiple departments. Different departments use UiPath for different purposes. In our department there are 12 end-users of UiPath, but I'm not sure how many users there are in the other departments.

I don't think, in the near future, we plan to increase the number of users because, for our bandwidth, these people are using it concurrently. But when our business grows beyond a particular limit, obviously, the number of users will increase, but that won't be for another six or seven months.

For the Enterprise solution, the technical support is a 10 out of 10, but for the Community edition it's a six out of 10. It's not that quick with the Community edition. They respond after 48 hours when you raise an inquiry, but with the Enterprise edition, it's instant.

Positive

We didn't use a different solution. We took a manual approach before.

I wasn't part of the deployment, but since it's mostly a cloud-based product, I don't think maintenance is required. All the updates are over the air.

We have definitely seen a return on investment by using UiPath. We have saved a lot of time with it and that has ultimately resulted in our employees focusing their time on other important aspects of growing the business.

The main reason we went ahead with UiPath was the pricing. As I mentioned, they have a free version as well as the paid version. And the pricing of the paid version was not that high. It's low- to mid-level pricing. They maintain the pricing to cater to small and medium-level companies.

Aside from the standard licensing fee, there was an additional training fee but that was optional only. UiPath has its Academy where we could attend courses on how to use the software, but if you want additional training, you have to pay extra. We did that and took some additional training on UiPath to feel confident.

I don't use the machine learning and AI capabilities in UiPath because they require a little bit of coding, which I'm not very familiar with.

But one thing that I have personally taken out of my experience with the solutions is that people with less coding knowledge or with no coding background should definitely consider using UiPath. It reduces a lot of the dependencies needed to produce automations. In the past, people like me who are not from a coding background, had to be dependent on others, and a lot of manual work was required. But with UiPath, I get to do it myself. I'm not depending on anyone else. That way, there is no time constraint for me. That is the major piece of advice that I would give to people without a coding background: You have complete control and can get things done in your own time. It is much more efficient and simple.

Try the Community version as soon as possible and get used to the entire workflow of the product and then make a decision. It is pretty easy to understand the entire workflow. Play around with it and you will fall in love with the package.

All the features are very good. It's a cool application to use and it's one of the best out there in the marketplace.

I own the robotics process automation program for our life safety segment. I also own the mergers and acquisitions project management for our life safety segment. We've started out by using UiPath specifically for mergers and acquisitions when migrating customer data from the acquired companies to our standard ERP. We're also implementing sales and use tax, filings, and things like that as well.

With our most recent robot, we transfer information from acquired companies to our ERP. Typically, it would take about six temp associates for about four to six weeks to clean the data and move it into the ERP. About three weeks of that would be actual data entry. With this product, we took that three weeks of data entry, times six people, and rolled it down to 12 hours of robot running. It was a pretty significant amount of savings for us.

Citizen development is great. With it, it's easy to develop or have self-developed robot intelligence. For example, instead of having to hire a developer, you can make the robots do what you need using the UAPs studio tool. This has been the most valuable aspect. StudioX specifically for our newer citizen developer is useful and I really like using Studio for myself.

We have seen a reduction in, for example, time, and not necessarily in human error. For example, we did an interesting analysis. We wanted to see what the human error rate was for entering data, and, due to the fact that our ERP is Microsoft Dynamics 2012, capturing some of that data is a little bit harder. We structured error rates based on entry. What we did was we created a robot to go back and check all their entries to see if they were missing anything. Oddly, the errors that people were making were nominal. I don't see any data that showed that we necessarily reduced error rates. It was really the people aspect of the process where there were time-savings based on the needed amount of human input. We've been able to reassign workers to more valuable tasks where we can't assign robots yet.

We do about four to five acquisitions a year and those are typically six-week processes for each one of them. We could say that we save about 25 weeks of labor in a year, and that robot will be about a week's worth of labor. Therefore, we save about 24 weeks of labor.

We've been taking some UiPath Academy courses. We've actually found it more helpful if we chose UiPath South American Developers to teach us to build as we're building. For my team specifically, it's been really helpful to have an expert involved to say "this is the use case that we want to do" and have them walk us through building a specific robot. That way, it's real-life experience versus a video-based session. While the academy is helpful, hands-on experience is just much more valuable.

UiPath Academy courses affected the process of getting employees up to speed. It affected it a little bit. It probably more affected our decision to use UiPath over Automation Anywhere, or even the Microsoft RPA program. Just the fact that there was so much available content that we could lean on if we needed to was huge. The others had content, however, not anything close to UiPath's capacity.

The on-prem orchestrator was an issue for us. When we bought it, it was a mistake. Our IT team thought it would be the best option for us, however, it's way more complicated to use. Out of the box, it feels more complicated. That said, once you get to know it, it's fine, however, it was incredibly hard to set up on our enterprise systems. Whereas, with the cloud deployment, we were live and up and running in an hour.  The initial setup took us about two weeks. That was a little bit of heartburn. It would be helpful if UiPath could offer some sort of support outside of a ticketing system.

I've been using the solution for about three months.

I've been pretty impressed with the stability. We've had a couple of minor issues that our developers helped us figure out. It's programming and nobody on my team are programmers. Some of it could be just user error, however, overall it seems like a very stable platform.

The scalability is really unlimited. It boils down to the organization's ability to implement a governance model quickly and successfully. I know UiPath has a governance tool or some kind of a framework, however, it is one of those pieces where it's way more expensive than us using our regular service channel tool that we already have implemented to do those submissions and approvals, et cetera.

In our organization, the users include two developers - me and then one of my assistants.

The only interaction we've had with technical support was during installation. The ticketing system and not being able to physically talk to somebody were difficult to deal with during the implementation process.

The on-premises implementation was a bit difficult. We knew that we were going to have to pay developers to help us develop the robots, however, getting stuff installed, our only method of support was submitting a ticket and the turnaround time on that took a while. Our UiPath rep helped escalate what she could. It would be ideal if there was a setup hotline or something that we could call right away. Sometimes it's just easier to talk to somebody than emailing back and forth. That's probably the biggest area for improvement.

We handled the initial setup ourselves. We do almost everything internally. We have our own IT team, including myself. Our solutions architects set it up with us. What we ran into in terms of problems was that the instructions were really not very good. We weren't able to appropriately install it as the instructions that came with it just weren't comprehensive enough. In terms of the instructions that were published online, we found a couple of instances where they were saying to use functions that didn't exist. These might have been a little out of date. Eventually, the ticket team was able to help identify that. I would grade the setup probably a C-minus, and everything else an A-plus.

We're so early into the implementation, the ROI is a wash right now. That said, our one robot has paid for our development time, and then someone will be able to use it on future acquisitions. We will likely see ROI within a year.

You can buy enhanced support, however, it's an additional $30,000 USD a year or thereabouts. That's just too expensive, honestly. The competition didn't charge for that. We also felt pretty confident in our IT team's ability to be able to dissect the instructions and install it. However, the instructions just weren't that good. We had one of our top engineers working on it and it took a lot of effort to get it installed correctly.

The pricing, in general, is fair. It's a little bit more than some of the competitors, however, it's a little bit more flexible than some of the others. There's value there. The OCR pricing is out of market. We need it, however, we're actually going to use some third-party bolt-ons due to the fact that UiPath is way too expensive.

We looked at Microsoft and Automation Anywhere. We also looked at help systems and Brick is one that we currently use and one of our segments, however, they're only a five-person company, which is pretty small. I wouldn't even put them on the same level. We were looking for shared services. We were looking for the best in class so we could take a solution enterprise-wide. In the end, we boiled the options down to Automation Anywhere, UiPath, and Microsoft, and UiPath was the winner.

In terms of Brick, they don't have a citizen developer model at all, so their developers have to do it. They are less expensive and they're a little bit more turnkey where they do it for you, however, they're really novice. The methodology that we've really bought into it was the community developer, as we want to empower our associates to figure out what works for them to improve their work-life balance. Using a service like theirs takes that away as we have to do the due diligence and figure out what fits in the bucket, what doesn't, as opposed to just empowering the person to do it. That was the key to why we chose UiPath.

The sales process was way better with UiPath. Our UiPath rep was far more knowledgeable about the product than the other options in that we ultimately had more confidence, knowing that whatever we needed, UiPath would help take care of, which was huge. My organization's a little bit disjointed. We try to go after what we feel is going to be impactful without a whole lot of due diligence. That's why, with UiPath, having that resource to lean on was helpful.

We use attended automation right now. Primarily this is due to the fact that the ERP system that we have really can't function unintended. It's a Citrix space environment and it has some odd security protocols where it'll shut down or refresh out for so many hours and it's not planned refreshes. It's hard for us. It's almost random. It's hard for us to build an unattended robot to deal with that. I'm sure we could, however, right now, we want to start with attended robots as we know what functions we need. We decided to go that route and eventually we'll add unattended.

I'd advise new users to make sure they have team buy-in for the concept. That doesn't mean necessarily getting the team to know exactly what they're going to be automating. You just need to make sure that they understand it's not about replacing people. Rather, it's about making their jobs easier. That was key for us. That said, most of my team was overworked, and they were glad to take on the project of lightening their load. Most organizations would benefit from making sure the communication is solid in that regard, however. 

I'd rate the solution at a nine out of ten. With better technical support, I would give them a perfect ten.

I am an API developer and I use UiPath for development. I use it to develop solutions for banking problems, like banking automation.

For example, in my previous company, I used the API for developing automated reporting solutions that take a lot of Excel files, check their data, and try to generate a web page containing many graphics based on the Excel data. It's basically translating the data on the web and it's made automatically every month. 

For my current company, it's a banking company, and I'm working on the banking solution. It's a process of verification of the user identity or the client's details. This process is based on taking the ID card of the person and digitalizing the data. It's a technology meant for reading data from documents. After reading this data, we automatically take this data and put it into the database and create accounts for the user or do a lot of automated things. 

At my current company, the use case is for the process of managing the relationship between the client account and any fees. A robot always checks if there is something to pay for the client and can take the fee automatically if that is the case. Then there is a transfer of money based on the request.

For example, when someone wants to do a transfer they add the money and sign a paper. This paper contains the information of the client's account, including details such as the client name, the account number, and the amount of the transfer. We take the data and the robot automatically takes the data and, via the web, goes to the apps of the bank in order to search for the client, search for the account, say the amount, and take the proper amount from his account, et cetera. We're able to save steps as everything is automated.

The actual company has three environments. There's one for development, one for pre-production, and one for production. Every element has two UiPath robots and one Studio. We have in total three studios and six robots, and each one has its own lessons. 

In the first, there was only one robot and one studio. They upgraded the solution from one studio one robot to three studios and six robots and they have found a good benefit in that. They know that it will give them more opportunities and more advantages within the banking environment. They made an investment in this technology to make their work easier so that they could be the best in the market of banking. It's helped them become more efficient.

There is an additional library that I discovered that allows me to work with the previous version of UiPath. There are some libraries that are new on the UiPath Studio, which are also helpful.

In terms of the ease of building automation using UiPath Studio, I must say that I used Automation Anywhere once as well. However, the way the UiPath connects the idea for development makes it so easy to build with the components that we can just drag and drop in. It's the easiest way to develop a solution and is an easier tool to use.

UiPath helps implement end-to-end automation starting with process analysis, then robot building, and finally monitoring of automation.

Being able to implement end-to-end automation is important for me. As much as they make me work, they make the work easier for me. For example, I use it to make the connection between ABBYY Studio, a solution for OCM, and writing scripts inside. I try to launch the script and take the output of the file and try to do a lot of things to make a connection between UiPath Studio and ABBYY Studio. UiPath Studio has given us a strong and new plugin, that we'll put some parameters around and we are done. It makes things easier like that. The features added into the latest update are helping a lot.

UiPath Studio has helped minimize our on-premise footprint in that there's less staff required. Previously, the company had three or four people doing the same thing. Now, only the robot does it. The four people are doing something else now. It's allowed them to focus on other tasks. The robot did not replace them, however. They still work in the same company, however, they are focused on doing different jobs - specifically jobs that can't be automated. They work on jobs that require a human operation, human intervention, and that's it.  The employees are happier too. The current company recently won an award based on employee happiness. In 2021, they were awarded excellence in employee condition. Automation hasn't made them bitter or changed their work ethic.

Robots started doing a lot of tasks that four people take one week to finish, except they can do it in one day. It's saved lots of time. For example, if we have 52 weeks, every week the robots can do a week's task in one day. A human may only be able to do 52 tasks in a year, whereas a robot can overperform by roughly 86% over the course of a year. 

UiPath speeds up and reduces the cost of digital transformation. The robots are extremely helpful, as they can work 24 hours a day, every day. They can do processes faster than people. It makes everything ultimately speed up.

The product has reduced human error. Even the robots make some errors, however, at least we are aware of them. The errors end up being fewer than that of a human counterpart. The issue with human errors is that we can't know if and when an error is made. At least with the robot, if it makes an error, the person is blocked somewhere and therefore we know that the robot missed something or it found a wrong account number, for example. The robot will notify us of an error whereas a human might miss it completely. 

Between version 19 and version 20, the Orchestrator tool interface has changed a lot. It totally changed. The menu changed, the place of the button changed. It took me a week to understand and to make myself used to this new interface. In the end, I found it's a good change and it's helping so much in understanding what the robots are doing in terms of checking logs, extracting some data there to make some analysis, and giving reports to the director.

The scaling could be better. There are so many parameters and options to check and so much to do before the solution is ready to use. Not everyone knows what to do at the outset and it's all a little bit complicated.

I've been using UiPath for one year and a month. The company may have been using it for longer than that.

While the stability is fine, with a license that needs to be paid yearly, UiPath will put out a new version annually. That way, when companies go to renew, they often need to upgrade or pay for a new license. The product does this to keep earning money year after year. 

For me, having the ability to scale automation without having to pay attention to infrastructure is okay, generally, however, even though I find that the company can use the tool to make the process automate well, I don't have so many people working with process automation. There are now just a few people developing in the APA and the licensing is still expensive and clients aren't excited to do anything even if it's a good solution for automating the process.

If you have a lot of money, you can put it all in UiPath and make the robot far bigger. I heard about a company located in Qatar that has 3600 robots. They buy it every year. It's a banking company and every year they pay for it. They are not using all of the robots, however, they've given their developers full reign of the environment.  

In my current company, I'm the only one using it. Many companies actually spend a few years testing it before they officially start using it. However, the company does plan to increase usage and does plan to add three or four more people to the team who would be working with me. I would manage them and provide training as we expand. 

There's a third party that takes responsibility for troubleshooting. They made the environment, and they are in charge of everything. Personally, I go first to the UiPath forum if I need help. I've found a lot of answers there. If I don't find something useful or helpful, I write an email to the third-party provider so that they can take charge of the problem and solve it.

They are good. There are three people who assist me typically. One is from the Middle East, one is French and the other is from India. Their way of communication, their way of giving information, and giving support have been great.

Both companies I have worked for that use this product have never used an automation solution before. 

I have worked with the solution for two enterprises. One was a Canadian company. I implemented the solution for them. I met the organization's boss, and I also put the training together too. I made the environment and I developed the solution and did the full implementation. 

The second, which I am actually working for, is a combination between Europe and Africa on the main. In both companies, the solution is already implemented and I work with it. The solution was started by another department. We don't share or manage the site of escalation or choose which kind of installation. The installation in this case is on-premise. We have constructed on our IAS, local server, and that's it. It's on the server, and we're not using UiPath's cloud.

The initial setup is good. There are no problems. Setting up the robots is also good. For the Orchestrator, sometimes I face some issues surrounding not UiPath, but the OS. For example, installing the Orchestrator on Windows 10, version 19.02, it's not the same process as it would be with Windows 10, version 20.82. Sometimes the visuals of the operating system change and it affects the installation too. This is well documented in the UiPath community. You'll find that many people face problems while working with the Orchestrator.

The deployment sometimes took me two hours. Sometimes I come across an issue and it takes more time. However, often, it can be deployed in 30 to 50 minutes if all goes well.  

With the installation for a Canadian company, I have a very simple installation experience. The environment was already prepped and ready and I just needed to start the installation. 

There is an IT team that does perform the maintenance as required, for example, if there are any updates or upgrades. I don't handle that aspect. I'm only a developer.

We might study potential ROI in the summer of 2022. We're still on the development part and therefore we still can't make reports. We don't have statistics.

There can be costs related to digital transformation. There are two ways this can happen. The first is when the robot is using an internal application, the application made by the company. There often is some modification to the interface of this app. There are some options that become available only for the robots. The second is when the robots use the websites of external companies. Internally, we made some changes to the robots to ensure they work well. In terms of the expense and how much it costs, the information is managed by another department. I don't have information about that.

I can't speak to the exact price, however, recently I heard in a meeting that one license for Studio Path costs 2,825 Euros per year. This price is approximate and may fluctuate.

The license is always per year. They don't show the pricing on the internet. You must contact the support or a seller. 

For the company I currently work with, I was in the meeting that chose the automation solution and they put the UiPath blueprint and Automation Anywhere on the table. The company wanted to choose between them. They found that, in terms of money, performance, and popularity, UiPath was the best. That is why they choose UiPath.

We are not resellers. We are customers and end-users.

For now, I am fine with UiPath Studio and I will likely keep developing automation solutions on this tool.

For the attended robots, we are not using them yet. We are only using unattended robots. First, we must make the financial employees understand how robots work. They need understanding or training as a first step before we can use attended robots in development. We are going to use attended robots in the future, however, for now, we're focused on unattended robots.

We don't yet use AI functionality. We're going to start using artificial intelligence and also the machine learning solution of UiPath via AI sensors. We'll use it to measure credit and to gauge the likelihood of clients paying, however, for now, we are not yet using AI features.  

We are also not using UiPath apps.

UiPath Studio has reduced the costs of our automation operations, although I don't have an exact statistic that reflects this.

Sometimes, when you come to a company and you tell them that you will make a robot to do their job, the first thing they will start thinking is "we're going to lose our job. They're going to fire us." With that mentality, they often aren't cooperative. 

For example, in a Canadian company I worked for when I was working on the process, the parts of the activity for Excel automation, I kept notifying them that they should keep using the same name of the file so the robots can read the file. However, I would get files in different names with letters off or symbols in them as if the staff was trying to get the project canceled by trying to show the robot wouldn't work. However, over time, as they came to understand no one would lose their position, they became cooperative. They weren't happy at first, however, they came to embrace the project.

UiPath has a huge marketing strategy, and they have been the first in the world with a lot of this technology. If a company wants to integrate automation into its processes, it will likely start looking at UiPath first.

If a company is considering UiPath, they should know exactly which process should be automated. When you know what kind of processes will be automated, they will understand better if they need attended robots or unattended robots, and then can proceed with a purchase. What one recent company did is they went and bought one studio and one robot. Then, later, after understanding which process was going to be automated, they figured out that they needed three studios and six robots. It's better to know which process to develop to make it automated, then later go to buy solutions for it.

We will still always need human workers. Of course, there are some tasks that can be automated 100%. However, in the end, and specifically in the banking domain, we always need humans to understand some things that make the work easier. if we combine automation, things like robots, and human intervention, then we can get great results.

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

We are using this product to develop automation in the billing section of our website. We are integrating bots so that they can do the basic listing and then our salesperson can take it from there.

The biggest improvement has been in cost. We have been operating it for about eight months for about $8,000. Earlier, it was taking us somewhere around $30,000 to $40,000, so that is a big improvement.

The other part has been accuracy. Before, when we had employees for the same process, there were some minor errors, as well as some time issues. But with this system, I believe the accuracy has been at par, although there are several times when we have had to reframe or do some minor modifications in the AI to make the model work for a new set or variety of clients.

The reduction in human error means we get more leads into the hands of the right salespeople who can work on them. Fewer errors means time savings.

With time, the AI automation has improved. Specifically talking about the kind of business that we do, which is putting things into the right sections so that the right people are taking the right leads, even in some complex cases, we have seen accurate results from automation. AI is doing its job.

AI has also enabled us to automate more processes. Earlier, we had different sets of protocols for differentiating among the different kinds of inbound information we were receiving. Since deploying this automation, we have automated a large chunk of the reception. The accuracy has been maintained and the time has been reduced significantly. We are able to convert the leads in a way that gives us more to work with from the leads we get.

The automation-creation process is quite easy and the accuracy is quite good. That last aspect is critically important because we have used RPA to replace one of our employees and we are taking on a lot of responsibility. The most important thing that we require is accuracy and we have been getting that so far.

The end-to-end coverage is important because each and every part of the input we are receiving from our customers—and they're highly valued customers—is information that goes into our software via automation, and we do not want to miss out on any types of leads.

The UiPath Academy courses have been great at giving an overview of the solution and allowing employees to learn things at their own pace. Other users out there also helped our technical staff, so they have added value. The biggest benefit was that at the time our technical staff was getting used to the product, they felt that there was a scarcity of people who knew about how to execute things. Having this UiPath course was a little helpful because it gave them the initial confidence they needed to start doing things, whether it was right or wrong, and they kept getting feedback and improving.

The only concern is it's a bit tough to understand the first time, and you have to invest in the technical improvement of your team in general.

About 6 Months.

There's no need to worry about the stability.

The only concern is as we move towards scaling it. What happens if the system goes off? Although it's not a big concern, we have been getting reassurance from UiPath that they have a solid backup of everything.

With RPA, scaling is not an issue at all. Once a bot has been trained to do a specific thing using ML, multiple bots can be added for the same automation process, as many times as we want. Scaling is not a concern.

We have not used technical support.

Positive

In terms of our decision to go ahead with this product, although we had received a recommendation that we should be moving forward with it, we were severely concerned about whether doing things over and over would take us the same amount of time, in terms of the technical ability and the workforce, or whether it would be easier. After having a technical call with UiPath, we quickly knew that it would be easier. That was a crucial part of our decision.

The initial setup was easy, but making the AI understand, and using the machine learning algorithms in it, took a long time. It took more than we expected it would take. The UiPath team had us understand that it would be functional after one or two months, but it eventually ended up taking about four months. That was more time than we expected, but the initial setup was easy and straightforward.

We used a consulting firm. There were three meetings over the duration of the two-month contract. The advices we received we about our model selection with regards to pricing and data storage capability.

We have been using it for eight months. For the first four months, I do not believe we were saving time because we had to intervene a lot of times with help from the vendor as well. But from that moment onwards, once the integration was operating smoothly, we started saving time.

We do a regular analysis each month and we have been seeing constant growth. A month is a good amount of time to see the progress of a newly implemented solution.

Previously, we were not using automation operations. I believe we have now reduced costs significantly, which justifies the cost we are paying for the service.

Pricing is good if your venture is looking for growth in 1-10 million size of customer domain.

yeah we got in touch with the IBM team for their automation tool.

Building automation takes some time. The first time, it took us a month, but after that, it was easier. The next time we build an automation, it's a kind of reciprocal of what we did the previous time. The first time involved some help from other resources, but from that time and onwards it has been going well.

The innovation did not happen as fast as we thought it would for the first half. We had to recruit some IT guys to our technical team so that our entire team could become familiar with the process. The innovation potential is there. It helps to get very familiarized with the solution. But for the first few months, the innovation part was delayed. The technical level required to handle it smoothly was not there on our team.