UiPath Platform Reviews

We use it mostly for our sales and for our clients, with relatively simple, stand-alone robotic solutions. Some are attended and some are unattended. We use it for reporting in our finance and HR departments. 

We have automated processes for our clients that, before, took somebody three days to do, and now they're done in minutes. That says everything. It's extremely useful for saving time and avoiding mistakes. Those are the two main efficiency factors that we have seen with our clients. Repetitive projects, where someone has to copy a lot of data from one place to another and then work with the data, are very prone to mistakes. We can completely eliminate mistakes and save people a lot of time so that they can do more interesting tasks. We have developed programs that reduce human error by 100 percent. There are no errors, once they are automated.

And it absolutely accelerates the process of digital transformation. There is no doubt that it is getting faster and faster. We are thinking about combining RPA solutions from UiPath with ChatGPT or whatever else comes along, to see if we can make them work together. This will be the future.

It enables us to implement end-to-end automation. We have projects where it automates the entire process from one end to the other. Very often we have "human-in-the-loop" within them, because some decisions have to be made, but they are almost end-to-end solutions.

End-to-end automation is extremely important. Usually, when we start with a new client, we start with a smaller process as a type of proof of concept, so that they can see what is possible. Then, we extend it up and down until we have an end-to-end solution. We have seen that it's better to develop a process step-by-step, and not try to do everything at once. But in the end, we have an end-to-end solution.

The UiPath community is used by our developers. They ask questions and receive responses. They are definitely active there.

We have had issues with Ingram Micro. It happened that we ordered licenses and we received something else. It takes a relatively long time, two and sometimes even three weeks, after the order until we receive licenses, and clients are sometimes a little bit impatient. This is something that should be accelerated.

I have been using UiPath for almost four years.

UiPath is a stable solution. One of the reasons we left the Foxtrot solution was that it was unstable. If we had the same process running 10 times, we could get three different results. But with UiPath, we have never had any issues regarding stability.

It's scalable.

We have discussions sometimes with people from UiPath about solutions and things that we have done already. That is working quite well. The support is very good.

We participate quite frequently in UiPath webinars, especially when they are presenting new versions or components or pricing models for the software, so that we keep everybody up to date on the latest developments. They develop things very quickly. It's difficult to keep up with the speed at which they are developing new solutions.

It is very straightforward to implement. The setting up of a license is something that is done within an hour. It's the development that takes more time. Most of our clients are large, multinational companies.

UiPath itself does not require any maintenance, but solution maintenance is required if something changes for one of our clients.

Everybody is afraid of the licensing fees in the beginning, and because we are in Romania where salaries are still significantly lower than in Western Europe, that means that licensing fees have a bigger impact on costs for the company. But we are also working more and more for companies outside of Romania, where that is less of an issue.

When we come up with an offer in which the licensing fees are getting a little bigger, clients are more reluctant. That is another reason that we prefer to start with something a bit smaller until they get acquainted with the solution and see the advantages.

We looked at other solutions. We started with something called Foxtrot RPA, which didn't work well at all. We also compared UiPath with Automation Anywhere. But UiPath offers a better variety of possibilities, it's more flexible, and it's very easy to program if you are a developer and know other programming languages. UiPath offers StudioX for people who do not have any experience with development, but it's still a little too complicated.

We are not using a lot of the abilities that UiPath offers. We have made some attempts to use Document Understanding and we would very much like to do project mining, but we haven't had a client that is interested in that yet.

I would recommend that you start by implementing a small, standalone process, something that is not part of a big process. Automate that small process first to get used to how it works and see what can be done with RPA in general. And only then start with more complex processes. The latter take more time to develop, and clients don't like to wait.

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.

It depends on the task that is assigned to me, but mainly, I'm using it for PDF automation and Java API-related automation. It is being used for extractions of PDFs and automation of the APIs to get a better and more rapid response.

UiPath helps a lot in everything related to automation. We have lots of tasks, and we need to get accurate results. Our experience of automating using UiPath has been good. It is easy to get good information or good output from the data.

Its AI capabilities are very helpful for automating more processes. If we want to extract something, we can easily use it. Its AI capabilities make it easy to automate a process and get accurate results.

It works well with all languages, such as Python, Java, C++, etc. It also works with APIs. It is helpful to understand the APIs to extract the data. 

It enables us to implement end-to-end automation. 

It has improved productivity and reliability and saved a lot of time. It has also reduced human error. It has reduced human error by 30% to 50%, and it has freed up employee time by 40% to 60% depending on the task or use case of an employee.

It has reduced our on-premises footprint a little bit.

It is a very easy and stable product. 

It saves a lot of time. It increases our productivity, and it also helps with project reliability and scalability.

The courses available on UiPath Academy are helpful if we want to go deep into the UiPath scripts or tools. UiPath Academy is also helpful when we want to learn something new that is available in the new versions or improve our skills and knowledge.

The user interface needs a little bit of improvement in terms of performance. Sometimes, it slows down, but it depends on the OS that you have. If you are running it on Microsoft Windows, it is slower than on macOS or Linux.

I've been using UiPath for the last two to three years.

It is very stable. I would rate it a 10 out of 10 in terms of reliability. The tool is very secure. If a user wants to run it on a Mac, it works flawlessly.

It is very scalable. I would rate it a 10 out of 10 for scalability.

We are using it for multiple departments. We have IT consultancy and IT services, as well as product teams. In my company, there are about 5K people. Some of them are end-users, some are developers, some are admins, and some are testers.

For any issues, we can take the help of the UiPath customer support and the UiPath community.

When we have some issues with the deployment tasks and automation tasks, customer support helps a lot, and they always try to resolve issues in a short time. Their technical support is incredible. They are always ready to help with customer queries and they try to resolve them within hours, not days. Sometimes, they resolve them within 30 minutes, but it also depends on the issue or priority. I would rate them a 10 out of 10.

Positive

This is the first tool that I have been using for the last two to three years.

It depends on the project size. If the project is complex, it takes time. In my opinion, it is straightforward if you know how to use it. If you don't know how to use this tool, it is very difficult. On average, it takes half an hour to one hour.

In terms of maintenance, it requires some maintenance, which is taken care of by the admin side. They have to make sure that it is up to date.

It is very cost-effective, and it gives an ROI. It saves a lot of time as well as money. It helps to build client relationships and improve customer feedback. There is a 20% to 30% saving on costs. It has saved $5,000 to $6,000 per year.

The time savings depend on the task and the size of the process. We can save 10% to 50%.

Its price is moderate. It is neither very expensive nor very cheap. Everything is good in terms of pricing.

I would recommend it to every developer or software engineer who wants to work on the automation review task. 

Overall, I would rate UiPath a 10 out of 10.

Our primary use case is creating automation for day-to-day activities for our internal use, especially for performance management and reporting. Apart from that, we create some automation applications for our clients as they're using UiPath. That's another use case.

We prepare database reports where a lot of product data is consumed. Creating reports or reporting used to take a lot of time and effort for us. UiPath has been very helpful for us in quickening this process and making it efficient.

It enables us to implement end-to-end automation. With our data and reporting tasks, there were a lot of repetitive tasks that needed to be done, which sometimes can be irritating. UiPath has completely taken over this process. So, right from the input of data to the extraction of reports, the complete end-to-end process is covered by UiPath. I don't have any complaints.

With UiPath, our automations are getting better and better. UiPath is driving performance, innovation, and growth across our entire organization. With report automation being our main use case, we saved a lot of hours, and we have also reduced a lot of overhead costs with UiPath. With automated data processing, errors are minimal. The error rate is almost zero, and the time taken is pretty quick. Our efficiency has improved, and that has been a major benefit for us.

We have been using the cloud version of UiPath. So, our on-premises footprint has definitely been reduced.

It has helped us move a lot closer to 100% digital transformation. Our reporting is automated, and we are almost 100% digital now. There is also an overall reduction in the cost and employee time.

It has reduced human error. The error rate is minimal or nearly zero. It's 100% smooth for us. In the past, we would have overlooked or missed certain data points, and during our final report collaboration, a mismatch would happen, but that is completely reduced with UiPath. 

It has freed up a lot of employee time. It has also made our work much more efficient. Earlier, if seven employees were doing a particular task, only three employees are required now to do that task. So, other employees can focus on something else now. 

It has saved about two working days or 16 hours a week. With the amount of data that we work with for reporting, it was a very hectic task for us. We had a lot of data sheets, Excel files, etc. UiPath has saved us two days of manual work per week.

It has saved costs. We were a team of seven who were handling reporting. We were taking reports and consolidating everything, whereas now, only three of us are required to do that. The remaining four can focus on something else. That much time and cost have been saved. This has resulted in us focusing on some other aspects of our business and bringing in more revenue for us. These are some of the overheads that have been completely saved by UiPath.

One feature that is particularly very likable is the My Workspace option under the Orchestrator menu. We can easily arrange and/or segregate all the folders there. The My Workspace option has been a very big positive for me. I've been able to streamline my work and do structured work with this My Workspace option. It's one of my favorite features. Apart from that, I like the integration services offered by UiPath. There is also the Studio option with good features, but I have used Studio very less. It's basically used to design specific automations and applications.

UiPath is very straightforward for creating automation. Especially in the UiPath Orchestrator and UiPath Studio, you can just drag and drop items to create an automation flow. It's that easy. For example, for the reporting automation, I designed the automation flow by using the in-built features. I did not type any command or code. I just picked a feature and dragged and dropped it to create and implement the flow. It was that easy for me.

The UiPath community is very vast, which is a very major plus for us. Whatever doubts we have and whatever knowledge transfer needs to happen can happen pretty quickly with the UiPath community. I find it very useful. Apart from the UiPath community, there is an Academy option where we can take up some courses, and we can do some certifications. That is also very good. I have personally not taken any courses, but I'm aware there are courses because my teammates did the certification courses. So, in terms of value, UiPath is an all-rounder for us because apart from doing automation, we get a whole lot of other things. It's very good.

They can improve the in-app guides and in-app tutorials. One instance where I faced a challenge with UiPath was during the initial week of using UiPath. It can be a little complex to understand at first. The in-app guides or the in-app tutorials could be much more elaborate and detailed. That would have made my entire journey smooth, but that did not happen.

The AI functionality could be improved. We used its AI functionality as a base for our reporting automation. It's not 100% perfect. It's still evolving. We used AI to predict the data modeling and report structure, but it wasn't accurate all the time. It's an evolving functionality, and I hope that it gets corrected over the course of time. The basic functionality is on par with any other software in the market, but it's not helpful for simplifying complex workflows and modules. The AI functionality has also not been helpful in increasing the number of automation, but UiPath, in general, has been very easy to use and helpful for doing more automation.

I have been using UiPath for about eight or nine months.

I haven't faced any issues so far. It has been smooth. I would rate it a 10 out of 10 in terms of stability.

I believe that any automation software, including UiPath, is scalable. It's a cloud-based solution, so it's definitely scalable for us. With UiPath, we have been able to do more automation and reduce our overall manual work. Our manual work now is very limited. It has definitely helped us scale up in terms of revenue, efficiency, and performance.

They're definitely very knowledgeable. Until now, I haven't had any complaints about them. Whenever we have any doubts, we just email them our queries with certain documentation, if needed. They get back to us immediately. They are also patient. It's not like they're in a hurry. They're very patient. They make sure that our query is completely resolved before moving on. I would rate them a 9 out of 10.

Positive

In my previous organization, they used a software called Freshworks. It was for automating our reports and sales processes, but I personally did not like that software because it was a little bit complex for me, and it was also costly. There were very few integrations that were offered in that particular software. We were not able to get the results that we needed. So, we looked into different solutions, and that's when I recommended UiPath to my team.

In terms of performance, UiPath has been very reliable. It's a complete cloud solution. The Freshworks software was not a cloud solution. We used it on-premises, but UiPath is a complete cloud solution for us. It's a very reliable and stable solution. We hardly face any downtime, server errors, or something like that with UiPath. That has been a very noticeable difference for me. Apart from that, in terms of complexity, UiPath is not at all complex. It's a structured solution. You choose A, and you can come to B, and you can come to C. It's very structured, which is something that was lacking in Freshworks.

I was involved in its implementation. It was not a complex process. It just required me to sit with the UiPath team and get it implemented. We did not need an elaborate team or effort. Within 15 to 20 days approximately, we were able to set up everything and get it running completely. The implementation process was very smooth.

Its maintenance is also very easy because it's a cloud-based solution. We just need to keep it updated all the time. That's the only thing. We have employed just one person to take care of the maintenance.

It was a combination of the in-house team and UiPath specialists. Their initial training team was very knowledgeable, and they were very pleasant in addressing all our queries with respect to how to design applications, how to create automation, and things like that.

We have definitely seen an ROI. Four employees are now not needed to do reporting. We have been able to transfer them to other projects. It has given some returns within four to five months. We have reduced our overall work time by around 30%. We have been able to use that saved time for other things helpful to bring in more sales, automation, etc.

Our inbound revenue is going up. We have seen a 20% increase in our overall revenue after the introduction of UiPath, but I cannot directly pinpoint that to UiPath because there are other factors as well.

I was not involved in the pricing negotiations, but as far as I understand, my team was happy with the pricing. So, I assume that its price is moderate and competitive. It isn't highly-priced.

To anyone looking into getting this solution, I would advise getting UiPath instantly and integrating it with your business to proceed further. If not UiPath, I would definitely recommend trying any other automation solution because that is the need of the hour. We are humans after all. Manual work is prone to error and less efficient. An automation solution can definitely help you scale your business quickly. UiPath is one of the top ones when it comes to automation. It's a tried, tested, and trusted solution. So, I would suggest going with UiPath, but if you have any concerns about it, you can definitely try other solutions.

Considering the UiPath community, UiPath Academy, and UiPath's all-around capabilities, I would rate it a 9 out of 10.

Our primary use case for UiPath is robotic process automation and automation fabric with document understanding AI.

Usually, after six to twelve months, our customers start implementing end-to-end processing with UiPath but they often start off with small tasks.

There is a clear value in being part of the UiPath community. We get money from UiPath for discounted licenses. Our customers hire us to implement their professional visions, and we're paid by the hour.

UiPath improves our customers' organizations. The effects of this growth usually start small. For example, we may notice that specific records are transferred in less time or with less manpower. Then, as the growth continues, those people become more involved in all aspects of the company.

The solution has a large impact on minimizing the on-premises footprint for our customers.

The Academic courses are vast. It provides our clients with the opportunity to start on their own and become somewhat independent. We use the courses as a huge resource to train our customers.

Usually, after six to 12 months, we start introducing our clients to more complex processes where the document understanding or AI fabric capabilities of UiPath are useful.

UiPath speeds up the digital transformation for our clients.

It helps reduce human error. This is mostly seen after UiPath has been implemented because people are not usually willing to admit their mistakes.

UiPath definitely frees up on average three to five percent of employee time per month. We have had small instances where the solution replaced a full SE with only one process.

The solution can reduce costs in retraining people on old or mundane processes, and it can also reduce costs by automating certain processes. This in turn can free up resources so that we don't have to invest in retraining people to do those same processes again. Automation eliminates the need to hire new people to do the job or carry out the process. After 18 to 24 months, many of our clients find that they don't need to hire more people to keep up with their growing business.

The simplicity of creating automation from a low code level is the most valuable feature of the solution.

UiPath's built-in automation is very easy to use. Our organization educates and provides lessons on how to use its automation and the feedback is that UiPath is easy once the introduction is complete. The solution is comparable to other software in this market.

There has been a huge improvement in Linux, Microsoft, and Mac support recently. However, we still struggle with the implementation in Citrix environments. The solution works with Citrix, but there is room for improvement. 

UiPath releases a lot of new features multiple times throughout the year causing our customers to fall behind. It would be fine if there was only one release a year.

I have been using UiPath for six years.

We are a technical partner, so we have direct support. If we post the questions well formed to the support team, we get a quick answer from them.

Positive

We use Automation Anywhere, Blue Prism, Power Automate, and our own products during the typical analysis quadrants. UiPath is the solution we use 95 percent of the time.

The main difference between UiPath and other RPA tools is the vision. While other tools focus on automating tasks, UiPath focuses on developing citizens who can automate tasks. This means that UiPath is the best tool for organizations that want to invest in their employees' skills.

The initial setup is straightforward. I give the ease of deployment a ten out of ten.

The implementation is completed in-house.

UiPath is not the cheapest solution, it's more or less the most expensive one, but we get what we pay for. I give the pricing an eight out of ten for its competitiveness.

I give the solution a ten out of ten.

We use UiPath to make processes. In addition to UiPath Studio, the platform that develops processes, UiPath includes other applications like Orchestrator, AI Center, Test Suite, Action Center, etc. 

I had the opportunity to work with UiPath Studio to develop and deliver processes to clients and scheduled them in production using the Orchestrator. I had the chance to automate many platforms in Excel, emails, et cetera. I developed around 20 processes.

I work with many medium-sized and large enterprises and a few small ones. Typically, the clients send us their PCs, and we work on their infrastructure. My clients usually have many departments, and all of them use UiPath. I use Orchestrator in the cloud, but clients, like banks, prefer the on-prem version because of security constraints. For me, there is no significant difference between the Orchestrator in the cloud and on-prem. We can schedule and maintain robots. They have essential common functionalities.

I work with many clients who recognize the impact and return on investment from using UiPath to develop automated processes. We always use the UiPath Academy courses. You can get a certification, and when we have questions that can't be answered on the forum or YouTube, we return to the courses. The courses are a way for the developers to understand the nuances of the product or do some workshops. The Academy combines theory and practice for each application, and in the end, we get a certificate. 

The AI Center can optimize many hours and lines of code. You can train your data on the Orchestrator in place with patent code, which takes more time. I compared the custom AI model and UiPath's presets, and we saved many hours. For example, my client had a difficult process that took lots of time to develop with Python and integrate into UiPath Studio. At first, they decided not to create this process with UiPath, but ultimately, they could develop it using Document Understanding with OCR and AI Center.

UiPath cuts down on human error and has included many updates in the latest release to reduce errors. Generally, our robots are rules-based so that we can see an important reduction in human errors. Automation generally speeds up tasks by about 50% because a person can control the robots in place to do all the jobs that robots do.

The amount of employee time saved depends on the bot. For example, if the robot is scheduled daily, and the task takes three hours, it frees up three hours. It depends on the complexity of the job and the time an employee spends on it. 

Enterprise clients can potentially save millions of dollars or euros per month. It depends on the client and the complexity of the process. We have a center of excellence that develops around 100 processes in large organizations. Smaller enterprises save a little bit less. In terms of cost savings, it's about 60 percent.

UiPath has a large user community that shares information. We can help each other find solutions, and the community publishes custom open-source libraries to help other UiPath developers. Members of the community also organize many events. Throughout the year, people from UiPath present new products and updates to the community, and community members help educate us about the latest features and how to use them in our existing robots.

I like the structure of the selectors. They're robust. With other software like Automation Anywhere, we always have problems with recorders, plugins, et cetera. UiPath is more powerful and efficient. UiPath Studio has features like the Excel package, selectors, and recorders. 

There are also many types of recording features. UiPath Studio's most interesting feature is the REFramework. UiPath's frameworks help developers handle exceptions efficiently.

Another critical feature of UiPath is end-to-end automation, starting with the design part of the process with many applications like Automation Hub, Task Capture, and Task Mining. We can use Task Capture in the community version, and they help with the design and conception of products at the start of the project. 

Then, we can use UiPath Studio, UiPath StudioX, or UiPath Web to develop the process. Afterward, we can use Orchestrator to schedule and maintain our developed processes. Finally, we have other products that can help us integrate business end users, such as UiPath Insights or UiPath Apps. With UiPath, we can assist automation in many industries or areas of applications.

I used the Document Understanding feature and developed a custom model to use in the community version. I had the opportunity to test the AI Center. The AI Center can make our robotic process classic RPA. 

AI Center allows us to evaluate and add intelligence to our classic RPA developers. We can add our custom classification model with drag-and-drop functionality in UiPath Studio. I like the integration between AI Center and UiPath Studio. Many of our clients are mature in RPA and want to use the AI Center or integrate artificial intelligence into their IT code.

The reporting part of Orchestrator could be improved. For example, UiPath could automatically email us if there are errors. Adding this feature would help us.

I have used UiPath for three years.

UiPath is stable. 

UiPath is scalable.

I rate UiPath support eight out of 10. They're available when you need them, and you can schedule meetings with them, too.

Positive

I also use Automation Anywhere for other clients, but I prefer UiPath because of the robust selectors and AI elements. UiPath can handle exceptions better, whereas Automation Anywhere lacks REFrameworks, which helps us handle exceptions. It's more difficult. 

UiPath has end-to-end automation, with a suite of other products that help us digitize internal and enterprise processes. UiPath has other advantages, like the community and the forum. 

Deploying UiPath is easy. It takes about 20 minutes or less to get UiPath running. You find the AI and download the latest version, then you start. The newest version is connected directly with the Orchestrator. 

One person can usually install it by themselves, but it depends on the number of computers. If you install it on one computer, that takes 30 minutes, but if we have more, you might need more people and more time. After deployment, UiPath requires some maintenance. The number of people necessary varies. For example, in some sectors, we have a team for maintenance and one for development, but developers might maintain their own processes in some instances.  

I don't have hard numbers on hand, but our clients generally see a 50-60% ROI. 

The UiPath license is a little expensive, but we get a lot of good features for the price. 

I rate UiPath eight out of 10. UiPath is the leader. It's the best automation software I've used. UiPath has rich documentation and a large user community. Developers can always find help in the forum. UiPath is a robust software solution that yields a high return on investment.

I recommend first trying UiPath Studio and UiPath products in general to experience all the features. Sometimes, we don't realize all the available features to help us solve our problems.

We started out with a lot of unattended use cases and then moved into using attended bots to help users. I've been with two separate companies. One was a financial services company. However, there was a lot of support for external clients. In the company now, we're doing a lot around the back office, HR, finance, and supply chain. UiPath just runs the gamut of all different kinds of use cases.

It's definitely made it easy to build automation. We have a team of about four or five developers. One of them was straight out of school, and they had never really had professional experience. We've also taken a couple of developers that were more into custom code and converted those over to using UiPath. It's interesting to see the level of excitement when you use a tool like UiPath from someone who is straight out of school and can convert over. 

We enjoy the constant innovation. It's coming out with new things that we can use and new features all the time. RPA has been around for a while now; however, the fact that we're adding integration services, adding apps, and all these other features, makes it possible to expand our use case.

We use UiPath to automate processes that deal with a good environmental cause. For example, for the company, however, we get invoices for bulk fuel. Our company sends out a lot of trucks, and a lot of customer engineers to actually service equipment. All this was manual, and a lot of not knowing how much we were paying. We automated that, and then the next step of that process is, "Okay. Can we start figuring out exactly how much money we spend on fuel, now, let's try to figure out ways to lessen that?" I could see how that could be environmentally friendly as we're trying to reduce consumption.

The user community is interesting. I've met a couple of people here and had really good conversations. It's interesting in the virtual world that we live in now, where everybody's just a face on a screen.

We've used UiPath's Academy. Being a solution architect, I'm not hands-on with code every day. I got certified as an RPA associate so that I could better understand what the developers are working on and using. When I'm designing solutions, I have a better knowledge of what's possible. I've taken a lot of the courses on UiPath Academy.

We're actually looking into a document to understand the use case. It's essentially car titles, and we're struggling. We've used several different OCR engines to try to train the model and try to improve it. For us, a little more direction on how to actually achieve this would be useful. We've been struggling for a couple of months now trying to get it working and getting it to the level we need it.

I've been using the solution for five or six years. 

The stability is great. I compare it to what I would think the best in class is. It's like Microsoft releasing patches. I've had fewer issues with UiPath updates than I do with my Office client on my computer. Therefore, it's very stable. 

We've had it where we had an update, and it did break some of our robots, and we had to go and do some troubleshooting, yet that's only been one time. It's pretty good overall. 

It remains scalable for us. We're not a huge shop yet as far as the number of bots, so it remains to be seen. It will be interesting when we try to reorganize our Orchestrator to make it more scalable. I can't really answer that one yet, as we haven't really tried to scale a lot.

Technical support is great. It's easy to reach out to them. It's easy to get feedback. As with any organization, a lot of times, the first answer is, "Go read the FAQ." I usually respond, "Well, I've already read the FAQ. That's why I'm asking." This is normal. Once you get past that, they're really ready to jump in and help.

Positive

I started out in 2016 looking at what was the best solution for the company. We looked at several of the top options. They're still the top ones today if you look at Gartner, Forrester, and publications like that. I used some of them. I've used Power Platform and other low-code tools like Pega and Appian. There are a lot of different tools in this space, and they all bleed into each other. 

I've been with two companies that focus on UiPath. It's just the constant way they try to keep up and keep innovating has made them a bit different than other options.

I was not involved in the initial deployment of the platform. I came in about a year ago. Since then, we've done things like automating month-end close processes, automating a lot of manual processes from moving from an old legacy HR system to Workday, and integrating with Workday. There have also been several other different smaller use cases like that. That said, for the implementation of the main platform, I wasn't here for that part.

The deployment of automation depends on how it's built and how you structure your UiPath Orchestrator, which has changed a lot in the last one or two years. They've got this concept of modern folders now in UiPath.

It's taken a lot of effort to transform what we did previously into what we're trying to do today. We very much had one tenant for one automation or a group of automation. Now, we're trying to do more. We ended up with a lot of tenants. Now, we're trying to consolidate into fewer tenants with these modern folders and trying to understand how that all works.

We have definitely seen an ROI. The team has talked about a million hours returned back to the business for other activities. It took a few years to get there, however, now it's every year. 

The pricing changes every day, however, it's not unlike any other SaaS platform. Sometimes it's hard to understand. That said, I'm more on the technical side. Some of the big questions are unattended versus attended since there's a lot more cost to unattended. When we get into document understanding, it's the number of OCR models, and the models you use that increases cost.

I looked into the other two big ones in this space. One of them, and this was in 2016 or 2017, didn't have a concept of attended automation. They thought it should all be unattended and no one should touch it. It should just run. That was really a barrier for us since one of the big value propositions is just automating those small tasks that people do to free up more time. Attended automation eliminated them.

One of the other ones we looked at couldn't support us. It was a proof of value, proof of concept type exercise, and they couldn't give us the support we needed to execute it. It was pretty easy to disqualify them when they couldn't go through that pre-sales motion to really get us. Why would we want to sign a contract? Why would we want to move forward? 

Potential new users should focus on the business driver or the business use case and find the best tool. UiPath lives in this space of RPA, low-code, AI/ML. There will probably always be three or four of these tools to choose from at any enterprise or sizable company. How do you pick the right one? It's really about what the business is trying to do.

I'd rate the solution eight out of ten.

Support is good, reliability is good, and innovation is great. There are just some things they could get better on to catch up with some of the other players in surrounding technologies. UiPath started as RPA. Other companies started as integration platforms. I know we're getting into connectors and things like that. It just keeps moving in that direction.

We use it for admissions policy and also for other financial items such as 1099 reporting from the IRS and things of that nature. There are some manual refreshes of systems and Excel documents that we have automated.

It is currently deployed on-prem, but we are looking at the cloud option. We are using version 2019, which is probably one of the oldest ones. It's pretty old. We're looking from a perspective of whether we upgrade it before we move to the cloud or whether we move to the cloud and upgrade.

We have seen quite a bit of benefit. We used to hire temp staff labor in order to do our admission policy, and now, we don't have to hire them. That would be five part-time people that would come in seasonally. For three or four months, we would have five people just cranking away the admission work. We don't need that anymore because of automation.

There have been time and financial savings. On the other side of the house, some of them are attended bots. We've saved the organization about 140,000 clicks. People don't have to click 140,000 times anymore. As a small estimate, we saved the organization about 250 hours last year. If everything goes to plan, this year, we're looking to save about 450 hours from the financial side of the house. We're only scratching the surface of it, and there is always room to grow.

We're still working through it. We recently stood up our system developer space. We have about 16 processes. We're still new at it and still in the beginning phases. We're really looking forward to pushing that envelope. Currently, we have a hybrid of attended and unattended automations. It's about an even split.

The GUI is valuable, and it's extremely stable. I've had six or seven Studios open at the same time working on different things and nothing has crashed on it. It's very stable software.

I love the community. The community is awesome. That has been very helpful. It provides value in terms of just being able to bounce ideas and understand. Sometimes, I try to do one thing, and I just want to know how to do one thing, but that's where the community can help broaden and look at it from a different perspective.

They say that everybody can do it, but not everybody can do it. You need to have some form of technological understanding about it, and just because we can automate something doesn't mean we should automate something. That's where I think there's a marketing thing. I understand where they're going with it, but it's not necessarily how real life is in my perspective.

I am not looking for any additional features. I haven't even used all the features. I'm still learning the platform as it stands and figuring out what's still available. 

I have been using it since 2019.

From a system perspective, it's stable on my end. It just works. That's the best part about it. It just works.

Scalability gets a little bit sticky. That could be just because of where we sit in the organization, I don't manage that relationship of licenses. I only get so many licenses and I'm like, "Well, can I get more?" It's definitely a limiting factor, but I don't know if it's us limiting it from a cost perspective. 

I haven't had to use their support. I go to the UiPath community for most of my questions. 

We used Microsoft Power Automate. It was okay. I totally prefer UiPath.

I was involved in its initial setup. UiPath was not complex, but we, as an organization, made it complex. 

We used a partner AKOA that got bought out by Roboyo not too long ago. So, we did use a partner to implement it. In terms of whether it was smooth or not, it was okay. Our school made it hard.

Our experience with them was good and helpful. It was a good way to go through it. Now that we know more, I would've changed the engagement slightly to get a little bit more consulting in the sense of the COE, governance, and other similar things around it. That's because for the most part, getting the system up and running was relatively simple, but now, with the whole other pieces of it, we're starting to feel some of that effect. It's now about how do we look at it from a different angle.

We definitely have a return on investment in terms of hours and soft cost perspective. We are saving 250 hours and don't have to hire five temps. I can't give the metrics for ROI, but from a time savings perspective, ROI is definitely huge.

We did evaluate other options. We evaluated Automation Anywhere, Blue Prism, and UiPath. It was about a year-long evaluation period between all of them, and UiPath was clearly the winner. It was clearly out there as the leader in that space, and that's why we chose them. 

From our perspective, the GUI was really helpful and very different from the others. Automation Anywhere touted more of just invoicing, but we didn't want it for invoicing. We wanted it for multiple things. UiPath really showed the breadth of what you can expand across.

To someone evaluating UiPath, I would definitely advise finding a partner. Find a partner with whom you can partner and who understands the use cases of what you're trying to do and achieve from an organizational perspective. Without that, you're not going to get an ROI. 

I would also advise managing expectations. It's fairly easy to use, but it still requires technical abilities. Don't think that it's something that you can just plug and play and do whatever you want. It's not going to work that way. It's more about the person and the change in mindset. If a person is open to an automation mindset, RPA is a really cool function, and UiPath solves that particular mindset. Without it, it's an uphill battle. Even from our perspective, from an education side of the house, getting our educators to be okay with automation is tricky.

We haven't yet used UiPath's AI functionality. We are definitely looking into it to see how we can start taking advantage of the AI pieces of it and advance that side of the house. Currently, we are trying to change the automation mindset. I'm a big RPA evangelist in our organization, and I am trying to promote things like automation. People are on board with the thought of it but not necessarily on board with the action of it. So, we really have to understand their process when we get into their process, and some people are apprehensive to share that information. It's the other parts of the piece that we have to deal with.

We have used UiPath Academy courses. It was useful to know the use of the product, the use of the GUI, understand how things move and change, where the checkmark boxes you need to check are, and all other uses. Now with the new versioning, it looks like a more curated function. It's a lot nicer. Previously, UiPath Academy was just a bunch of courses, and you didn't know where to start. The curation for developers or users is going to help people navigate through the UiPath Academy.

Overall, I would rate UiPath a nine out of ten.