UiPath Reviews

We mainly use UiPath for automation testing processes. I am from delivery and project management, and I have a team member under me who is developing automation processes for me.

We had five members on our team when we started in 2019, and now we have 70 people in-house. We have achieved a very good scale in the last five years. We started with UiPath, and we have started adding other tools over the last one and a half years. Till mid-2023, we were just on the UiPath platform, but now we've expanded to other tools. We are the only organization across the globe that has achieved certifications in Document Understanding.

The most valuable features of UiPath are test automation, test suite, test manager, and document understanding.

Communication mining and process mining can be enhanced in UiPath. UiPath should improve its licensing because its competitors offer a cheaper and more sustainable model for even small-scale industries. Any company that wants to adopt UiPath has to pay straight away and then use it.

I have been using UiPath since 2015.

We haven't faced any issues with the stability of the solution because it is continuously evolving and upgrading. In some instances, we found that some solutions we had built in the past were failing, but that could be quickly fixed with their suggestions.

I don't feel any other tool has that much accuracy and stability of the applications. UiPath is a very scalable solution, and we can integrate it with any other application.

I rate the solution’s scalability an eight to nine out of ten.

UiPath's support team has to improve a little because their responses regarding production incidents are not too quick. Initially, they try to resolve issues by email and connect on a call if that doesn't work. I think they have to improve a lot in this area. I rate the solution’s technical support a six or seven out of ten.

Neutral

In my previous organizations, I used Robot Framework and Power Automate.

The initial deployment of UiPath is easy.

We have several in-house experts who can deploy the solution. If we struggle with something, we seek the help of all the resources in our team. Mostly, we don't take any external help for deployment. If required, we reach out to UiPath for something that is missing or not working. However, that is just 2% to 3% of the complete processes. We manage the rest, 98% of the process, among ourselves.

Compared to other RPA tools, UiPath is a much more expensive solution.

UiPath's implementation depends on the process and budgeting. If clients have a good budget, we proceed with UiPath. Otherwise, we suggest some other solutions. Sometimes, we need to minimize the time frame to do the repetitive task. Manually, people take a longer time to process any files. We are automating the processes to streamline them and minimize the team members' costs and efforts.

If we have multiple tools involved, we have to put a lot of effort into analyzing them. If we directly go to development without thinking or analyzing, we lose time and effort. That's why it is very important to analyze the tools in depth. If the processes are straightforward, we suggest some improvements, which would be much easier. If multiple applications are involved, it takes a longer time. The complex process also requires some improvement, and based on that, we suggest whether to go ahead with UiPath or not.

The solution enables us to implement end-to-end automation for 90% of the processes. End-to-end automation is always important for us because it creates business for us. When we implement UiPath for the client, each client will be satisfied and happy with us, and we can get more business.

UiPath's user community is very helpful. We learn about different technologies and aspects when we get involved with the user community. Sometimes, we interact with problems that we have never worked on. We learn about such challenges and their solutions because of the solution's user community.

If you are struggling somewhere, you can post the issue on the user community forums and get an immediate response. With UiPath support, we have to wait for 24 hours to get a resolution. We get quick responses in community forums because experts respond to us. Compared to other solutions, UiPath's community forum is much stronger.

Most of our resources are first going ahead with UiPath Academy courses. After that, we give training because that is a basic point to start with. We are even onboarding the freshers. We ask them to go through their Academy courses, and after that, we allocate an in-house mentor. It will be much easier for us after they have an outline in their mind regarding the processes they have to go through. Once they finish it, we have an internal assessment and a training team that will assist in complex use cases.

The biggest benefit of UiPath Academy is its proper outline and structure in terms of education. Anyone who can follow will at least get 40% to 50% of the learning from there. After that, they will learn a lot based on their practices. They can practice some examples from there if the basic concept is clear. The courses are structured in such a way that even kids can also start with them. The courses in UiPath Academy are well structured and planned.

We cannot add the solution's AI functionality for every project. Around 50% of the projects we have done so far are related to AI. AI is helping a lot in terms of AI Center. The AI functionality helps connect with each application and for documenting. The solution’s AI functionality has enabled us to automate more processes overall.

Other than licensing costs, the solution reduces the cost of digital transformation. Our complete business depends on UiPath. As a solution-based company, we are automating the processes. We don't have manual resources except the project manager and business analyst to analyze the processes. Our complete business depends on the solution's automation or the AI model.

UiPath has freed up employee time for us. We have delivered two projects to a European-based client. UiPath has freed 90% of employee time in one of the processes and 85% in the other. It was a very big logistic company where we implemented UiPath using a Document Understanding to extract all invoices and feed them into the application. Earlier, they used to allocate these tasks to nine resources. Now, one resource can handle everything.

We have been expanding into other tools for the last year, but UiPath has been beneficial and has saved us overall costs. We don't have any licenses with us. We just provide the solution. We deploy UiPath on-premises or on the cloud, depending on the end user's requirement.

UiPath is usually deployed across multiple locations and departments. Maintenance will be required for UiPath in terms of new functionality during upgrades. I would recommend the solution to other users.

We always suggest to every client and whoever reaches out to us not to proceed with UiPath without having proper knowledge. We say this because of the licensing cost and several factors involved. If the processes are just one time, it's not recommended to use them. Overall, the learning is good. If anyone wants to try UiPath, they should first explore smaller processes and then proceed to the bigger ones.

Whenever new upgrades are available, sometimes they break the functionality, which we have faced a few times. If you are using version 12, stick with that and disable the updates directly from UiPath. First, try on the smaller instances, then proceed with the bigger ones. Otherwise, some production activity might fail.

Overall, I rate the solution an eight out of ten.

We managed over 500 global tasks worldwide, leveraging UiPath to automate procurement, financial accounting, customer service processes, and customer relations.

We evaluate resumes through the RPA and ChatGPT four. We also arrange service for customers who need repairs to their devices through automation we developed using UiPath.

UiPath enables end-to-end automation. The end-to-end automation is important because it allows us to reduce our testing and reporting time from 28 hours down to 15.

UiPath has helped us shorten the time for our supply chain and revenue report generation. By using UiPath Document Understanding the OCR can read the PDF documents and automatically drop the file into the ERP system significantly reducing our time.

UiPath has streamlined our operations by digitizing our documentation and converting it to easily accessible PDF files. This has significantly reduced our physical footprint, eliminating the need for paper storage and manual document handling.

As a partner of UiPath in our region we are required to take all the Academy courses so we can better service our clients and share our use cases.

We have 1,000 clients around the world, each with unique invoice formatting preferences. Our AI system efficiently sorts these invoices based on their specific formats. By automating more processes through AI, we've significantly improved efficiency. For example, while standard OCR takes a minute to process a PDF invoice, our AI system does it in just two seconds.

UiPath has helped speed up our digital transformation. We have created a large data lake to help with analytics.

We require human verification for the final invoice numbers. Using UiPath the number of human errors has been reduced to one percent.

UiPath has saved ten percent of our employees' time by automating the invoicing process, translating the invoice language, and emailing it to the original user.

UiPath helps save costs. We can keep the license costs down by using one API license to convert all our PDF files into Word.

UiPath is well-suited for automating tasks within Oracle applications and can be deployed on-premises or in the cloud. This flexibility is particularly advantageous when dealing with sensitive data that cannot be migrated to the cloud for security reasons.

UiPath needs to improve its integration with Microsoft products such as Office, SharePoint, and PowerPoint.

I have been using UiPath for two years.

UiPath is stable.

UiPath can scale to our needs.

The technical support is good. We rarely have to use them.

Positive

For general automation needs, we choose Microsoft Power Automate due to its cost-effectiveness compared to UiPath. However, for Oracle-centric automation, where stability is paramount, we rely on UiPath.

The initial deployment was complex. Many settings within the orchestrator need to be set before running a job. Once we implemented UiPath we had our user team keep an eye on it for one month to ensure it was stable, scheduling only attendee jobs before moving onto more complex automation.

In our region, we have a team of 15 to 25 people for the deployments and a smaller team of five in North America.

We implement UiPath in-house.

UiPath is expensive compared to the competition. We pay a license fee that is over 20,000 USD.

We evaluated Automation Anywhere, Power Automate, and UiPath. Automation Anywhere and UiPath are more expensive than Power Automate.

I would rate UiPath a nine out of ten.

We do require the assistance of IT to help increase our digital transformation.

Maintenance is required when updates are made to a process or component. Our team of 25 is responsible for the maintenance as well.

We use the solution for robotic process automation. We use it across the value chain for our business. We've used it in accounts, including cash management, and in HR for management tasks and IT for password resetting. 

The automation has been quite useful. It's been helpful in our journey towards transformation. 

I've used this solution for a while and I utilize the whole tool and get a lot of benefits out of it. 

It helps save time. We've had efforts that would take more than four hours a day, yet, when done through UiPath, it takes less than a minute.

The useability is very good - even for non-technical people. I'm an accountant by education and now I'm also an automation expert by profession. Its interface is user-friendly to those of us who are non-technical.

Anyone who wants to automate any task that is rule-based and repetitive can do it through UiPath.   

We can use the solution for automation emails or notifications.

It enables end-to-end automation. We developed a use case where people from different business units have large amounts of data, Excel files, we've made it so that we can combine it and enter it into the ERP system. Everything can be checked via the rule book and can create the report and send back the information to the customer. It simplifies the data and organizes and compiles it for them. Users have gotten the benefit of five FTEs by using UiPath. It saved many man-hours. 

I haven't used the UiPath Community too much. I often Google questions to find answers. It is a good place to go for development work, though. 

It reduces our footprint. We historically did have many items on-prem. I like it on-prem and on the desktop.

It can reduce the cost of digital transformation. Where processes can have faster response times, UiPath helps with efficiency. However, if the response time of the application is slow, and we need to provide workarounds, it isn't helpful in that it hasn't efficiently helped us save time.

UiPath reduces human error by 100%. Whatever you give to the robot, it will do it correctly. That said, it needs to be programmed correctly - if it's programmed wrong, it will do it 100% wrong. If it's programmed right, it does it 100% right. 

It's freed up human time. It's not well-utilized in that sense. It should be available to everyone so that they can find ways to save time by creating their own automation according to what they need.

There are a few shortcomings. For example, even in their latest version, there are still older features even though they've introduced new ones in parallel. They should do something where they update the solution and then close off the older version after a year or something like that. That might help with standardization. 

Sometimes it is very useful for automation. However, sometimes it is really, really frustrating when it is unable to manage the more dynamic items. When an element is stable, it's great. When it comes to changes to IDs or the dynamics of the website, it lets us down in front of our customers. It needs to be better at handling volumes of data. 

Automation on the cloud has had issues. It can be slower. 

The Academy classes could be improved. There should be a portal for use cases. There should be more business examples.

They should offer different licensing tiers, especially for daily individual users. 

I've been using the solution since 2016, more than five years. 

It is a stable product. There were some issues while interacting with different applications. For example, with Microsoft, we have issues with One Drive. When UiPath is working on a file, it cannot quickly get to the file. We need to move the file to a local drive before processing the data. Microsoft applications seem to give it trouble. 

We have multinational business units. Company-wide, maybe 500 people are using it. Where I am, there may be a team of ten people working with it and 50 to 60 automations. The solution is in multiple locations and departments. 

The solution is scalable. It depends on how an organization wants to utilize it. 

Technical support is very flexible, however, they do not respond quickly. Sometimes they just tell us "this is how it works" and we have to try to explain our framework.

Neutral

I have also tried Blue Prism. I didn't work with it much; I just studied it theoretically. 

I also tried to work with Power Automate. Initially, it wasn't very good, however, later, it began to echo the style and functionality of UiPath.

UiPath is easy to use and easy to get started with. 

The deployment was a long journey. I was one of the first people in Pakistan to use it. Now, once you get a license, you can deploy it in two weeks. However, it depends on the complexity of the processes in terms of deploying automation.

We have around ten people maintaining the solution. It requires a lot of maintenance. If anything needs to be changed in the target application, it needs to be incorporated into the robot. 

Someone told us you do need three to five years before you get an ROI. However, in our first year, we were able to save more than 8,000 hours. 

The solution is on the expensive side. 

There should be standardized packages. If an organization already has a license with UiPath, UiPath should offer special licenses to each employee so that each employee has their own UiPath automation capabilities for each of their individual tasks.

There should be regional packages and costs. Different regions cannot necessarily afford UiPath. What is affordable in Europe may not be affordable somewhere else. 

We're a UiPath customer. We serve internal customers with robots.

We do not use the UiPath AI functionality, however, we are on a journey towards building our own internal solution. 

I'd like to see UiPath cut the cost of their license. For end-to-end automation, for developers, I understand why it needs to be expensive, however, for day-to-day users, it should be cheap. 

I'd recommend the solution to new users. 

I'd rate the solution eight out of ten. It's still the best out of all related products.

We are using it to extract information from invoices. We have different types of invoices from about 180 vendors and we need to automate extraction from about 6,000 invoices. We receive invoices via email and are using automation to extract the invoice, put it into a folder, extract information from the invoice, and then enter this information into a SAP-based solution. Not every detail is taken from the invoice, only the relevant portions. 

We have already developed it and it's in the testing phase, where what is being tested is sending the money to the vendor.

For example, if we have purchased something for £1,000 from a vendor and they have sent us an invoice, we extract all the information, confirm that the purchase has been done by looking at our records, and then we have to submit it to the accounts office. That office will create the payment invoice for the vendor.

It now takes about half an hour for each invoice to be processed versus taking two to three days to do the same invoice manually.

And while I wouldn't say that UiPath enables end-to-end automation for everything, for invoice processing it does. Cash to payable is one of those things that UiPath is able to do from end-to-end, right from the point of getting the invoice from the client to the end where an email is sent to that client saying, "Your invoice has been processed. We have transferred X amount of money to your account." In some cases, especially when invoices are handwritten, we face small problems but, other than that, we are able to do it.

And the turnaround times in creating automations are much less compared to when we were using Automation Anywhere. With that solution we were not able to do it as quickly as we can using UiPath.

We did a PoC for an HR company that was giving appointment letters to about 100 people across its franchise. They wanted to give them out in one go and wanted some way of automating the process. UiPath had the tools that we could use to manipulate it enough and send the appointment letters in 15 to 20 seconds.

And automation has absolutely freed up employee time. Now, people are only looking at exceptional cases most of the time, where automation is not possible. They aren't looking at most cases. Productivity has improved to a great extent compared to what it was before automation. People are going home on time and getting their leaves on time and getting to spend quality time with their families. They are happier compared to how things were.

In addition, there was a lot of human error when people were entering information into the computer. Especially in an accounting situation, if someone inputs a four instead of a nine, it's very difficult to figure out where things went wrong. But with UiPath, there is no more inaccuracy or typos.

What we like about the product is that we are able to customize a lot of things quickly because UiPath already has certain APIs and tools available that we can integrate with our system to extract information. For example, if you have to open Word or extract information and put it into tools like SAP or Salesforce, those things get done quickly and efficiently.

I have been using UiPath for about a year.

UiPath is always uploading new versions of its software. So far, we haven't had any problems related to UiPath crashing or anything like that. The stability has been satisfactory. It's good, decently stable software.

It is very scalable. You can scale it up to any amount that you want or scale it down, depending on the kind of processes that you're doing. 

We have automated the number of robots that we use. Every day we look at how many invoices we have to process. Suppose that today we have to process 5,000 invoices. In that situation, we use all 10 robots. If the next there are 15,000 invoices, two more robots will be activated to take on that load. And it works in reverse. If there are fewer than 5,000 invoices, we have eight robots working on them. It took us a while to automate that aspect.

The support is a little bit lacking, response-wise. Just like in banking, where they give you a relationship manager, they should provide someone who is responsible for a project. That person would be responsible for responding to your queries quickly and efficiently. What happens now is that I have to wait for them to come back to me and it takes a lot of my developers' time to figure out how to do things. Support could be better.

Neutral

We did a project for a company that wanted to identify certain vendors to talk to but they needed to know which vendor would give them the best price. They needed to do a comparison but they were spending tons of time evaluating the vendor information. We used Python to do this, not UiPath. We made it possible to do the comparison quickly and efficiently so that when they speak to the vendors they know exactly what to talk about. It improved their resource allocation because they had 15 people doing this work. Now, there are only two people doing it. The other 13 people have been deployed to other sections and other types of work.

Even though Python is very powerful, you need to do a lot of coding. We wanted software where we could minimize coding, a low-code solution.

We looked at UiPath, Automation Anywhere, Blue Prism, and Kofax. But out of all of them, we found that UiPath was a more wholesome product. It's not that the other software products don't have good features, it's just that UiPath has a lot of tools that can be used quickly and efficiently.

Right now UiPath is on the cloud, but eventually, it will be on-prem. When we signed the agreement with them, we told them that we would do it on the cloud and they had to provide us with the storage and cloud space. They were very accommodating about that.

We were able to deploy the first automation in about two weeks. It's not just setting things up, but also making sure that it is working. The users also needed to evaluate things using their tools and data. So the setup was not that bad. Within two weeks we were all set up and ready.

It is worth the cost. We did costing for our invoicing project and we are seeing between 20 and 25 percent ROI.

The price of UiPath is too high. From their website, what I see is that if you can buy one license it will cost about 5,000 rupees here in India. And for enterprise solutions, they are charging about 800,000 rupees for about 100 licenses, which is quite high compared to similar software solutions.

The ease of building automations depends on what the client wants. Some processes can be done very quickly and efficiently, but some need a lot of tweaking to meet the requirements of the client and they take a little time. But as a general rule of thumb, it is quite efficient actually. Some take very little time and some can take a couple of weeks.

The UiPath user forums are good, but there's nothing new in them. Whatever they are saying, we have already done it. There isn't much new information there. For example, UiPath has a tool known as Document Understanding, using Computer Vision to do a lot of the processing. We were stuck a little bit but the user community was not able to give us much insight mainly because Document Understanding was very new. It still is quite new and people have not explored it enough to give their feedback. We were flailing about, trying to figure out what to do and what not to do, what works and what doesn't. We were more or less on our own.

In our company, we try to make sure that prospects have gone through the UiPath Academy on their own. For us, it is mandatory that they do so to have at least a basic idea of what UiPath can do and, during interviews before we hire them, we try to test them on some of the use cases. We don't want to spend time teaching them about it. We assume that if they have gone through the Academy courses, they are well-versed in what is expected.

We are a services company. In terms of how we use UiPath, we handle a lot of the financial processes, including our customer billing, our time tracking, and our time reporting exceptions - such as looking at who has not submitted a timesheet. When this exception happens, there are automatic emails that go out using the RPA, from UiPath. 

The whole process from our inventory, which is our asset, is automated. With the asset, which is the time that our people spend on clients, we make sure that we capture what we need to create and send invoices out. The whole collection and AR process, including making sure that we get the money and send reminders to clients, that whole process, is automated - with human intervention, as needed.

The solution has decreased the processing time of the client's invoices for IT. Just IT. Not the rest of the organization. That said, just there, that’s 600 hours of annual savings in one department. On top of that, we’ve decreased processing time by 90%.

The automation cloud offering helps to decrease the solution's total cost of ownership. More than that, it creates agility so companies don't have to worry about delivering the infrastructure team and setting up sellers and all the things that they need to do to get to the stage of actually installing the software and internal security. That all takes time to go through. With the cloud, you avoid all that. You basically create agility for the clients to jump onto automation and not wait for all these things. It can be frustrating sometimes in large companies. That's why we tell clients to avoid all these headaches. With the cloud, you’ll get going very quickly within a matter of a day or so.

RPA is not the only thing we do. We do a lot of ERP, CRM, all of these things. Traditionally, we are a full-service organization for clients and their journey to the cloud. Everything's going to the cloud. There are some organizations that still have on-premise ERPs to migrate from the on-premise to the cloud. When those fundamental applications are going to the cloud, automation is a no-brainer. We would always promote the cloud version over on-premise.

The RPA is the most valuable aspect. The power of machine learning and AI along with the document understanding capability that UiPath has is great.

By implementing that portion of the solution, we get clients to 95% accuracy in reading invoices for processing into the ERP. While running basic automation will continue, the world is moving towards intelligent automation, which is with all the machine learning and AI.

Overall, the solution has saved costs for our clients.

It has reduced human error. Machines can do anything faster, cheaper, and of a higher quality than humans can do. That is just a universal fact. I don't think we have measured the accuracy, however, there's no doubt accuracy has gone up. The client recognizes that the accuracy rate has improved.

We're not talking about removing errors. In some cases, errors may happen. However, when I say we’ve seen a 90% efficiency rate, it doesn’t mean the remaining 10% are bad decisions. We're talking about how it could not read those things. The confidence level is low, and therefore, it's kicked to a human to review. It did what it's supposed to do, which is to flag for human review, which is how processes should happen.

The solution has allowed the employees to focus their time on other higher-value work. That's what we pitch to our clients. We never tell clients that oh, you can lay off people. We do not tell the clients that that's what they should do. Rather, we advise clients that what they can do with automation is free up people's time. That means either freeing up a portion of the time or fully freeing time or completely reassigning a job. 

After automation, you may have to reorganize your department. However, with the freed-up time, departments can focus on the most important thing, which is what can they do to create focus on the customer and create an experience for the customer, where the customer feels they want to be connected with your brand.

I have a case where I was talking to the CEO of a big restaurant company. HR, payroll, finance, all those areas that reported to him. He also handles customer experience. I told him about automation and the power of automation and how it will free up people's time. He said, “So what you're telling me is I can free up a portion of my staff so they can focus on all these customer complaints we're receiving?" For him, that is going to be a game-changer.

UiPath has also positively affected the employees themselves. They've become a little bit more satisfied with knowing that they can focus their time on higher-value work. In most cases, initially, there'll be fear for them. They don't know what automation is, and why they're doing it, and what it's going to do to their position in the company. That fear will always be there with humans. That's why leadership needs to focus on change management and communication. Those things become very, very important. Once you do it right, people will actually feel happy. They will no longer have to say "Oh, no, I don't have to stay until six o'clock, seven o'clock every day to finish the SaaS." Now it's much easier. They can focus on the things that they truly enjoy, which has nothing to do with the heads-down work that they do all the time.

We use the solution's AI functionality in our automation program for our clients. For simple processes, you don't need AI. However, the complex process where machines need to mimic the human thought process requires AI. AI is not perfect. It's not a holy grail that is going to solve all problems. That's not the case. We have to be careful. However, if you use it right in the right way, then you can truly solve complex problems.

I’m not sure if the solution's AI functionality enables us to automate more processes overall. It's hard to say. For me, the way I look at technology is that it is not a hammer that's looking for a nail. You have to look at your business needs and then figure out what technology will best fit or solve the problem. It could be simple AI, or, maybe in some cases, you need more advanced AI. I would look at it as what's the right technology for what purpose. That's the way I look at it.

We do use UiPath’s Academy. We have several people that we've pushed through training and certifications through the academy. It’s helped get those employees up to speed on the solution.

Also for us, as we are a services company, that gives us a stamp of quality seal in order to market our services better as we are certified and qualified.

UiPath continues investment in machine learning and AI. That's one thing they have to do. The fundamental thing UiPath needs to understand is the competition, the market, is not Automation Anywhere or Blue Prism. Rather, big competition is coming from Microsoft.

It's around the corner and Microsoft is going to come in a big way. I’d advise them of the parallel of Power BI. Power BI three years back was not a good tool. Other tools, like Tableau, were the kings of the BI space. Fast forward three years and today we do a lot of BI for clients. Almost every client of ours is migrating to Power BI, like Power BI's matured to 80% of Tableau, and that's good enough for them. On top of that, Microsoft was throwing free licenses to their customers. When you do that, versus buying $2,000 a pop or $1,500 a pop from Tableau, users line up behind the free tool to reduce their costs. Microsoft is doing that with Power Automate now. I just talked to a client, a big client, a $10 billion company, where they were at Blue Prism. They just told me that Microsoft just gave them 70 free licenses. Now, they are forced to bring Microsoft Power Automate into their RPA strategy even though before, they were not considering that.

UiPath should take several steps forward to be prepared for this competition and create differentiation with capabilities that Microsoft does not have. The innovation within UiPath is going to be very, very crucial. However, the most important thing is to clear the differentiation in the messaging. That's very, very important. They should be ready and arm their partners with information about why UiPath and not Power Automate.

I've been around the industry for 35 years, and I've seen lots of incumbents getting blown away in various technologies at various times. The big power comes down hard. UiPath has got to be ultra nimble to not get crushed.

We started working with UiPath in 2018. We partnered with UiPath in late 2018. It's been about a three-year journey so far. 

In terms of stability, I've not heard anything bad at my level. That means no bad news is good news.

We do plan to scale beyond the client's IT department and to the rest of the organization. When they scale it up to the rest of the organization, and this organization operates in 25 countries, they have over $190 billion in assets in these countries that we can add efficiencies to. The scale of efficiency that we will get with what we did will be huge. That’s the next step is to roll it out to the rest of the organization.

General scalability is an issue when it comes to processing large data sets. However, with the right creativity, you can solve those things due to the fact that you can have the right infrastructure to catalyze or do whatever you have to do to create scalability. We are used to doing that. We deal with ERPs and we create architecture and design the environment in such a way that it can scale. That said, you need to know how to do that. 

Technical support is very good. We're very pleased with that. When we ran into problems with a client, with the document understanding, initially the success rate was not very high. Then we had to reach out to the support and they actually jumped in and assisted us and told us what we needed to do. Once we did that, then things took off and we got to 90% accuracy. Initially, it was only 50%. Therefore, for us, it's been good.

We did not previously use a different RPA solution.

We did partner with Automation Anywhere,, however, ultimately, we didn't do anything with them.

The initial setup is straightforward.

We're a consulting company, and we work with several clients. For some deployments, we were able to do the first deployment in 30 days. With other clients, it took about three months or four months, depending on the use case or the initial use cases that they picked.

Different companies operate differently. I always advise clients that they need to pick simple use cases and deploy them first before they go into complex stuff. Sometimes clients make the mistake of picking their most complex use case and say, "Oh, let's try that." No, that's not a good way. It's not a good way to embark on a journey that's long-term.

You've got to think big, start small, and be agile. If you get a complex use case at the beginning, you lose agility.

We looked at Blue Prism, Automation Anywhere, and UiPath. The momentum was with UiPath. I knew where the momentum was and how we needed to align ourselves. That's why we did UiPath.

We looked at where the market demand is. For example, Blue Prism. We knew that Blue Prism is a lot more IT-centric, IT heavy, programmer heavy, which defeats the whole purpose of self-service automation. It's never going to succeed in the marketplace today as we promote self-service for everything.

That's why we didn't want to waste our time with Blue Prism. UiPath obviously has the community edition, which was brilliant. Basically, they saw a gap in the market. That's a parallel to what we do, for example, in Vtech space. Also, for example, Tableau is a good tool. So many people love Tableau. They've used Tableau. You had the established players in BI space like MicroStrategy and Oracle OBIEE, however, they were very IT-centric and Tableau came in and beat them. They sold out into the business and you could download, pay $2000 and download a license and start creating your dashboards. I was glad that UiPath took a similar approach by creating a community edition, and then letting end-users download and then play with it.

We basically help clients think through their RPA strategy, their automation strategy and figure out what the right technology would be. We are a reseller. If it makes sense, we'll resell and we'll advise clients regarding UiPath for their RPA journey. We also use the solution ourselves. We have automated certain things, certain processes within the company. That becomes a practice round and a learning ground for our people so that when we go to clients, we can take some of these ideas and do to the clients as well as reaping the right expertise.

I'm not sure if we are using the UiPath apps feature or the applications feature. In my role, I just lay the strategy and the team executes it.

A lot of times things stall. In company setups we see a lot of cases where they did a few automations, a few bots, and then things stalled. That's a problem in the industry and the way to solve that and truly embrace the art of the possible is with automation. To get there, you need to execute across senior leadership. Without that education, they just don't put their weight on their departments to do the journey. Education is one thing that is very important. They understand the art of the possible.

Another important aspect at the outset is having RPA as a corporate strategy. Pushing to make it a corporate strategy is really going to help. That way, you can stall it for some time, however, eventually, it will have to get done. Otherwise, they are left behind when your competitors take advantage of the agility. There needs to be a center of excellence and companies need to develop internal capabilities. If they don't have capabilities, then they fear not knowing how to handle something. Those are common problems. And those need to be overcome.

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

For a current client, we have around 22 to 25 use cases, and it's all based on the financial side of things. The client is in finance, and we have use cases all of which are comprised of different tools, including SAP and their in-house CRMs. It's about automating the process where we take some data from the CRM tool and upload it to SAP. It also involves uploading the files to the FTP server. 

For example, one use case is where the applications used are Oracle, and SAP, and STP. We just download the data from Oracle. There are different files that we download from Oracle and upload to the FTP server. From that FTP server, there is a different team that takes those files and creates a Tableau dashboard. 

UiPath Studio helped us automate many processes that have helped us save money. Even though the tool price is there and the license costs are there, it has given good ROI. For example, automating a process can reduce the work to half or maybe 60%. We divert efforts to different work. Therefore, it has been pretty useful in terms of savings and quality control.

For example, one client had a focus on quality control. There are instances where employees make some minor errors that could lead to major losses to the organization from the department's point of view. We automated that process and it gave us more return in terms of quality control. Fewer errors ultimately were made which saved the company from losses.

UiPath has a full suite of capabilities. It has, for example, an end-to-end automation suite. From a development point of view, it is pretty helpful to have access to all of the activities on offer that anyone can understand. 

The Studio as well as the process mining are great. Document understanding is another useful feature. It has eliminated the business analyst side where you have to go through each department and find out which processes are there, and take a different tool to get those all processes in one place and create a process workflow. All of this can be done with process mining. 

With document understanding, we have the capabilities of having UiPath understand and create documents, which previously was quite a lengthy endeavor. You just have to install it and follow the steps. It will automatically take a screenshot and create a document for you and then create a brief description of it. 

It’s easy to build automation using UiPath Studio. From a developer's point of view, it is easy due to the fact that you don't need much of a coding language or coding background. You just should have a clear logic behind it. If you're clear with the logic, a layman can handle the task. They do have Studio X features, which is for the layman who doesn't have any background, who doesn't have any coding or developer's background. They can automate their own work. Even an SME who doesn't know anything about automation could automate small tasks.

It’s great that we can scale automation without having to pay attention to infrastructure. That is very important actually. For example, scaling automation plus giving attention to the infrastructure can be a little hectic and time-consuming. If there is any way where we could reduce this work or optimize it, it would be great from the implementation point of view.

UiPath enables us to implement end-to-end automation. Right from the start, you have document understanding and process mining as well as the Orchestrator, which helps you with getting an overall view of the bots in our organization.

End-to-end coverage is the most important thing, due to the fact that, if it is end-to-end, we don't need to go to the market and look for any other application. If you can get end-to-end, you don't need to go for other products which simplifies everything. It's easy for us to maintain and work with it instead of having to integrate and manage multiple systems, multiple products, and multiple applications.

UiPath has helped minimize our on-premise footprint. It has helped us with quality control savings. We have saved many efforts previously requiring full-time employees. It’s one of the most important factors when we work for clients. If a client is hiring us to automate many processes, there are different intentions of doing it. If we are able to help them reduce cost, reduce and do some quality control, it is important for them. For example, previously, if work required ten employees, we have been able to reduce that down to six or sometimes four personnel maybe.

The UiPath Studio has reduced human error. It has helped us with quality control very often. In the past, mistakes have cost us. It has saved costs as well as saving us money related to fines or penalties.

The solution has freed up employee time. Instead of doing the same mundane work every day, we have just automated that part and now the employees have more free time to do more meaningful work. In terms of hours, from a department's point of view, we have saved around half, that is four hours per day, maybe about 80 hours per month. The additional time enabled employees to focus on more important work.

We have found that the product has reduced the costs of our client’s automation operations. With my previous client, we calculated an average of 40% in reduction of personnel and 40% in cost savings. UiPath has saved us money across the organization. The average saving is likely around 40% to 45%.

I'm pretty much happy with all of those tools. I don't have anything in mind that I could see improvement.

While UiPath Studio helps speed up the cost of digital transformation, in a way, it requires expensive or complex application upgrades or IT support, as it needs an entire setup. That setup requires support from different departments, and that comes with a cost.

I came across one problem while upgrading. We were upgrading from the 2019 version to the 2020. There was one thing that was not mentioned either on the website or documentation, and we had to take support from UiPath. The documentation needs to contain each of the scenarios which could occur while upgrading the solutions. As it is now, this is not the case. That said, when we ran into issues, UiPath Support helped us through it.

I've been using UiPath for five years now.

We've had outages once or twice. For that, they have a workaround. If a server goes down, we should have a backup server for it. If that's the case, it is just a few steps needed to migrate or we can take the setup from another server. That's it. It's pretty good in general. 

The scalability is fine. For example, if the bot count is about zero to 100, we have the capacity. And if it goes beyond that, then we have to increase the features of the systems and servers. It could take time if we scale beyond the limits, however, it's still possible. It just requires an upgrade. 

What's required is managing all the infrastructure and getting all the permissions from the client which is what could take time. Scalability can be an issue when it goes beyond the mentioned limit.

In the current organization we're working with, it's totally unattended bots where no user is actually using this tool. That said, the bots are in production, which works 24/7. No user is having this access to the tool. It is all unattended bots.

In the previous organization, there were 58 to 70 users as we had attended bots. They were using bots in their daily routine.

It's a routine for us to use this product every day and deploy this solution. We are definitely looking at increasing it and scaling. We have a lot of work in the pipeline.

I've contacted technical support many times and they are very helpful. Based on the severity and priority, they do help us on priority and they are very helpful in terms of responding, supporting, and maintaining. If they can't help us by email, even after giving clear instructions, they'll bump you to a different level and help. It can be just like spoon-feeding us. They are very patient and try to be very clear.

We were doing automation, however, it was just .com and .net. We used to write five lines of code just to click on one button, which is just an activity right now we have in UiPath. We switched to UiPath to do end-to-end processes which would require large amounts of code if we kept doing what we were doing.  

I've implemented UiPath from scratch many times. 

The process is quite straightforward. You just have to have the installer and just click install, and then after a few steps, it is done.

Setting up just UiPath Studio hardly takes ten to 20 minutes or maybe one hour if you're facing some complexity. Setting up an Orchestrator with all the robots could take a while.

Our implementation strategy is based on whatever the customer's requirements are. Different clients have different requirements. My previous client, for example, didn't want the cloud as they were pretty concerned about the security as they deal with financial data and they don't want the data to go to the cloud at all.

Clients have the option of on-premises or cloud. Based on that, we just go with the requirements. Some clients want attended bots due to the cost, and some want unattended bots due to the features. 

In terms of maintenance and deployment, how many people you need depends on how many processes you have with the client. Right now, with the current client, we have 22 to 25 processes that we have automated. We are just three users who are developing, testing, maintaining, and supporting this project. However, it varies and often depends on the process and client and how many bots.

For maintenance and support, you don't need many people. For development, if they're at 10 people, five or four could do the work in terms of support and maintenance.

We handle the deployments for our clients. 

While the clients might have released some reports, I don't have much knowledge about ROI. 

I do know about the prices of attended and unattended bots as well as Orchestrator. 

There are costs related to Orchestrator, Studio, and attended bots. There are also infrastructure costs, and, while implementing this tool in any organization, there are different costs attached to it.

The price for the attended bot is between $1,800 and $3,000. The unattended bot was $8,000 last year.

Orchestrator is around $20,000.

We looked at Automation Anywhere and Blue Prism, however, about five years back, where UiPath, Blue Prism, and Automation Anywhere were the leaders in the market, at that time, just UiPath had the free training and Intuit training for their tool. The other tools didn't have any training, or if they had, it was paid. That's why we chose UiPath, which ended up being the best out of the three anyway.

The company I work for is a UiPath partner.

There have been multiple companies that I've been working with. Two remain the same. I've been using different tools as well. It's been on and off with UiPath.

We are not using the latest version of UiPath. The latest version is 2021. We are using 2020. This is due to the fact that the client that I'm working with has a stated policy as to using a minus one version. They believe it could not be a more stable version for any product. 

At this time, we don't use the SaaS solution or the AI functionality. However, I have enrolled in AI training to better understand it. We do not yet use the automation cloud or UiPath apps either.

In terms of employee satisfaction, from the experience I had from interacting with the client and different users, they are happy as well as sad. They are happy in terms of moving away from the mundane work that has been taken off from their hands. They are, however, both sad and afraid that they could lose their job.

I'd advise users, if they're a layman, to go with the training. Just start with the training from the UiPath website itself, in the RPA Academy. That is sufficient for anyone to start with. They have all the courses that start right from scratch for every role, be it business analyst, solution or product developer, et cetera. In six months, even starting from scratch, you can excel on this product.

With UiPath, it really is possible to optimize so many things. 

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

We primarily use UiPath for end-to-end automation. We develop both attended and unattended bots and we use the Orchestrator module, hosted in Azure.

Some of our typical use cases involve automating operations like downloading files online, analyzing and capturing details, saving them in another location, transferring them, and uploading them in other forms.

The app studio feature has increased the number of automations that we create while reducing the time it takes to create them. For example, we have a limitation when it comes to transferring files from one server to another server. However, we were able to resolve it by using a remote desktop on the UiPath server. I don't need to log into another system or another server; instead, I log in and use the remote desktop from my PC. It's really cost-efficient and it saves me a lot of time. It's superb.

UiPath helps us to implement end-to-end process automation starting with process analysis through to monitoring, and this is very important to us. Whether we are automating processes for external customers or internal purposes, there is an automation lifecycle that we follow. The end-users do not have much knowledge about automation, so we have to complete it from end-to-end.

It starts with analyzing the process to see if automation will work. We then develop it by trying to replicate what the user does manually. Once it has been developed and the functionality replicated, we test and tweak it for approximately two weeks. If everything goes well during this time, the process moves to production. In production, processes are continuously monitored.

The testing is a detailed process that involves finding the problems, then implementing error handling using try/catch statements and other methods. It is done in a continuous, agile fashion where we develop, publish, trial, error handling, monitoring, and then it starts again. When a process is pushed to production, when a change is made, it does through this lifecycle again.

How UiPath has improved the way our organization functions is clear when we look at one of our use cases. We need to have notifications about documents that describe the release of products. Our bot will start by filtering documents online using keywords, download the appropriate documents, then check to make sure that each is complete. If there is a problem then emails are automatically sent to the appropriate department.

From this point, we transfer the file into another folder and upload the current version to the release team. They will only receive what they need, rather than having to go through the document themselves. Prior to this, they needed to check it on their own and analyze everything. With this work being done by the robot, it relieves us of two person's workloads. What used to take three people to complete, is now done with one.

In terms of saving time, for our use case that involves the release documents, we save between 80 and 100 hours per week, so monthly, you can multiply that by four.

The time saved by our employees sometimes allows them to focus on higher-value work or in other cases, when we don't need the persons, we can reduce the workforce and then hire people in different roles, such as new developers. Overall, this helps us to improve our workforce. For example, we can branch into more areas, rather than do the same thing for many different customers.

With respect to employee satisfaction, if somebody loses their position then they may not be happy. However, it is important to remember at the same time that we may open a new position because of this opportunity. This allows the person to move, find new opportunities, focus on new things, and develop themselves. To me, this is a win-win because we are more focused on generating new types of business.

UiPath has definitely helped us to reduce human errors. This is a benefit to us because, before this, we used to get customers complaining quite often. However, we have reduced the complaints. We still need to have the customer complaints section but now, we have reduced it from five people to one. The robot is not 100% error-free, but it's between 90% and 99.9% error-free. With so few complaints, we don't need as many people to deal with them.

Overall, UiPath's process analysis and optimization have increased our productivity.

The most valuable feature for me is the UiPath Studio.

It helps a lot. I wouldn't really say it's code-free; however, I would say that it's 90% code-free. It's very easy to use, with most of the actions performed using the drag-and-drop interface. When you do write code, it's a very small amount of the time.

The library activities are really helpful. With the help of the library and with the help of the forums, developers can focus and it is easy to learn. It helps in terms of time-to-value.

I also find Orchestrator to be helpful. The Studio and the Orchestrator together are like your body and your soul. Without both parts, it won't function. You need to have Orchestrator to run the Studio. Right now, today, we have a problem with our Orchestrator and it's not working. I can't use Studio because it's connected and without access to my Orchestrator, I can't do anything.

The academy courses help in the process of getting employees up to speed with the solution by providing them with the fundamental knowledge and the opportunity to practice. When you start doing it, you may face errors and again, with the docs, you may gain more knowledge. When you start to use the forums, you get more knowledge, and it all helps. But, if you only rely on the forums, I would say that it would help only 60% or 70% of what you get compared to taking the academy courses. In the end, you will only get better by doing it, and then going to the forums when you have problems.

The testing and release schedule for Studio should be improved because we find that with two releases per year, one of the versions is stable and the other one is not. It would be better to focus on a single release, but make sure that it is stable. We have had problems in the past with this and we don't need any unstable versions. For example, version 20.4.2 was not stable but version 20.10.2 was very good.

Technical support and customer care are areas in need of improvement. 

We have been using UiPath for between six and seven months.

We are in Switzerland and normally, we use local support. When they cannot resolve an issue then it is transferred to the US team and we get support from them directly. In our experience, the support in Europe is not sufficient and we prefer to speak directly with the UiPath headquarters. We find that here, the people do not have enough knowledge.

We have had a lot of problems and for example, we have an issue right now where our Orchestrator doesn't work. We have had to wait about a week for the ticket to be escalated to headquarters, and because of delays like this, we are not always happy with customer care. The product is good but the technical support can improve.

We had issues where the first person tells us one thing, but a second person says that it's wrong and it needs to be done another way. Then, a third person speaks and presents another idea. This all takes a lot of time before a fourth person explains that everything is wrong and it has to be done another way. A lot of the time when you have these kinds of problems, you just have to start from scratch.

It can be frustrating because we had spent almost three weeks upgrading our system to the 20.10.2 version and now, we face the same problem. We have not been able to properly run our system for between three and four weeks.

I have not personally used another RPA solution but I have colleagues who have experience with Automation Anywhere. We primarily use UiPath but there are some developers in the company who regularly work with Automation Anywhere.

We did not switch from one product to another. Rather, they are used for different reasons. For example, I have heard that when it comes to performing file transfers, Automation Anywhere makes it quite easy and they do not have the limitations that UiPath does.

On the other hand, I feel that the AI in UiPath is doing better. We have lots of workflows and activities in UiPath and I strongly prefer it as a product.

I wouldn't say that the initial setup is complex, although when you are just beginning with a new environment, it is not that easy, either. Because it is a new thing, you will need to learn in the beginning.

We followed the guide and found that the installation was not very tough.

UiPath saves us costs, but there is more to it than that. It saves us in terms of time spent on manual tasks, but on the other hand, we pay UiPath. On yet another hand, with the money we save, we are open to new opportunities and new business.

Overall, I am very happy with the ROI.

The price of UiPath is a little bit high, although there are no costs in addition to the standard licensing fees. Overall, it is not too costly, but slightly high.

We have not yet used the AI functionality but we are trying to. We have not developed any uses cases yet but it is something that we are working on. We will be taking some courses on it first and after that, we may try some internal use cases.

We have advanced our technical knowledge by using this product. For example, we now use JSON config files, rather than using Excel.

One of the biggest lessons that we have learned is that it is nice to have a good solution design before starting development. There were times where we tried to do something one way but a problem occurred, so we had to solve it by trying different features, then testing and running it again. A lot of time is spent during this process. Now, we have learned to focus more during the design, then start to develop it.

My advice for anybody who is implementing UiPath is that it works really well in Windows, so they have to have a Windows machine if they want to start developing.

I would rate this solution an eight out of ten.

We are a diagnostic laboratory that receives tissue samples from all over the country daily. To manage these, we implement UiPath for Document Understanding to process requisitions from clinical providers. This information is then loaded into our laboratory information system, enabling us to carry out the diagnostic process. We have a dozen bots operating across various functions, assisting in tasks such as screening resumes in HR and data entry on patient information.

Automation has increased our productivity. In my three years at the company, the number of employees working on data entry has grown from 15 to more than 50. We needed an alternative because we couldn't have 150 employees in one room doing data entry. UiPath has improved our efficiency by 60 percent and reduced errors by 87 percent in the assessment process. 

In healthcare, our top priority is to eliminate as many mistakes as possible. A mistake in our business can kill someone. Our second objective is to build better security measures to protect patient privacy and the sensitive information we handle. We also hope to improve efficiency and help our employees work better. It has helped take people away from mundane tasks and allowed them to focus on what truly needs their expertise.

We've achieved some of these outcomes so far, but we've only been automating for a year. I came to this event last year knowing nothing about UiPath, but I met some people and hooked up with a partner to get started. I met some people. We got hooked up with a partner who could help us get started. Then, I started hiring developers. We're still early on in this relationship, but we've already seen tremendous gains in efficiency and error reductions. 

Document Understanding has been particularly helpful, and so has UiPath's ability to interface with other applications. AI is the next phase. Document Understanding can only process about half the documents that come in. We need the AI component to start helping so that the half we can't process has a methodology on what needs to be done with it. 

AI automation is a high priority. A year ago, I was the chief operating officer, and now I'm the chief innovation officer. Our CEO saw that we needed to have a dedicated technology group looking for solutions, and he asked me to move into this role. I have seven full-time developers on my team who are specifically looking for things to automate. When I saw the demonstration this morning, my mind was blown. They're doing so many things that we could do that will take us to the next level. We can have AI interact with our pathologists and assist them in diagnostic research. We can apply UiPath across our billing processes and everywhere.

While not a negative remark toward UiPath itself, our initial partner was limited in helping us achieve our goals. We are now directly working with UiPath support, which has been exceptional.

We have been using UiPath for about a year.

The solution is very stable.

I think it's we I think we we I think I don't have any barriers in my head of what we can do do or not do with it.

I rate UiPath support 10 out of 10. It's outstanding. Working with them has been a game-changer. 

Positive

We did not use any different solution before adopting UiPath.

We initially worked with a partner who was limited in aiding our objectives, leading us to work directly with UiPath support.

We saw a 60 percent improvement in efficiency and significantly reduced errors.

I rate UiPath 10 out of 10.