UiPath Platform Reviews

I have used UiPath for a city utility. The main purpose is if they want to dig in a particular location, they need to know how many pipelines are underneath the road, what the situation is regarding high-tension wires, gas pipelines, et cetera. For that, we needed to go to about 18 websites and scrape the maps from them into a local repository. We use UiPath to save that data from all the websites.

From there, there is an AI/ML solution that identifies the danger signals and notations on the map. It summarizes them and sends them to a mobile application used by a person who is at that location. That person can determine whether they are able to dig in that particular location or not.

UiPath reduces human error by automating a lot of manual steps. 

It also helps free up employee time. The amount of time depends on the use case. For the use case I described above, for the utility, the whole process of preparing one package would take one person two and a half hours. Automating it using UiPath and AI reduced it to two and a half minutes.

In terms of costs, for that use case, it has saved that company 30 to 40 percent.

Scraping with UiPath is easy, as is integration with some services. It's also easy to deploy solutions. 

Building automation takes place in a normal programming environment like Visual Studio. It's the same environment developers use. If you know development, building automation in UiPath is easy. Visually, it's all interactive and easy to work on.

The platform also has features for logging and monitoring things and communicating when there are errors.

The UiPath user community is a very good ecosystem with information about a lot of new features like AI, chat integration, and WhatsApp integration.

For training purposes and certification, we use the UiPath Academy. It's a very good resource and you get very good support from the community.

We also use the solution's AI functionality but so far only on low- to medium-complexity processes.

I would like to see them transition to the cloud and provide services there. That would be an improvement.

Also, it needs more integration with external services, and I would like it to have generative AI and more artificial intelligence features.

I have been using UiPath for about one and a half years.

The stability is good. I am satisfied with it.

The scalability is also good.

UiPath's technical support is good.

Positive

I used Automation Anywhere. I switched because our clients switched since UiPath is cheaper.

There is definitely ROI from using UiPath. Based on the fees and the load of the input, ROI will be calculated and used to decide whether the use case is worthwhile or not. It will be decided in the analysis and discovery phases. If ROI is feasible, only then will development take place.

With UiPath, there is an additional cost for Document Understanding. If the use case demands it, that feature should be used.

Even though our clients may have an Automation Anywhere ecosystem, they choose UiPath due to budget and cost. Apart from cost, both platforms offer almost all the features. However, from a technical perspective, Automation Anywhere has more utilities and components for building bots.

If it weren't for the cost, I would personally choose Automation Anywhere, on the technical side, because it has huge utilities and components for building bots. The move to UiPath is driven by budgets and costs.

As for end-to-end processing, when you are trying to come up with use cases for RPA, you will probably look at existing legacy applications that are not extendable. They won't have any more new releases but we still need to extract value from them. Use cases include reducing the processing steps and manual steps done, day-to-day, by people. End-to-end automation will help to stitch all the gaps and reduce the processing time.

UiPath is not cloud-based yet, so most of the work is done on-premises.

In terms of maintenance, one person on our support team monitors all the bots and attends to any problems.

I would recommend UiPath for small and medium-sized automation. If a company doesn't have a large budget, UiPath is the solution.

We primarily use UiPath for science-related automations.

The biggest benefit we get from UiPath is saving time. We work with small and medium-sized businesses that need to perform multiple mundane, repetitive tasks. UiPath reduces the time we spend on these tasks by about 60 to 70 percent. By automating low-level jobs, employees can focus on high-priority tasks. Automation has sped up our invoicing because we can process invoices 24/7. We saved more than $200,000 using UiPath.

UiPath helped us reduce our on-prem footprint. Using bots eliminates human error from most jobs if we develop the correct logic and business exceptions, but we still need humans working upstream. 

Building automations is quite straightforward. They offer free courses for developers, and we take advantage of those. The UiPath community has also had a tremendous impact on our operations.

The artificial intelligence and machine learning features are good, but there is some room for improvement. 

I have used UiPath for more than five years.

UiPath is stable. 

UiPath is scalable. 

I rate UiPath support an eight out of ten.

Positive

I have used several RPA tools, including Blue Prism, Automation Anywhere, and Microsoft Power Automate. UiPath is easier to learn and more user-friendly than other solutions. There are also lots of open-source resources you can use. Power Automate was included with our Office 365 license, so we use it for some things. However, it isn't our primary RPA solution. 

Deploying UiPath is straightforward and only takes a couple of minutes. One person is enough to install it. 

UiPath is quite expensive compared to Power Automate. That's the main difference, and we have to purchase a new license for every feature. 

I rate UiPath a seven out of ten. I would recommend it to others, but I can't give it a higher score because I'm not happy with the licensing model. That's what bothers me the most about UiPath. 

We used this solution to automate monitoring, implement robots, and monitor the robots. We use it for network monitoring, ticketing systems, and remediation activities. This is a SaaS solution. 

This solution is mostly used by network engineers in managed services. The engineers look after telecom networks, and they are the end users. For automation, a sizable team of developers, specialized automation developers, and solution architects used the solution. There were about 40 RPA developers and 10 solution architects.

We plan to automate some of the business processes regarding financial reporting.

We used this solution in the automation of a legacy Jira application that was used for CR management. We use the change request template, and we're able to collect data from various systems through APIs and submitting requests.

Since we started using this solution, our team has had more time to work on other tasks.

The solution has reduced human error by processing the data directly from the source and into the destination application without human intervention.

Our internal clients are glad that KPIs are increasing.

A lot of my colleagues have used the UiPath Academy course. There were also colleagues who used the course and weren't involved in the day-to-day automation process.

It really helps employees be aware of how the tool works, how they can better describe processes, and with what level of detail they need us to describe processes so we can automate their work.

One of the biggest improvements was that some of our colleagues who weren't technical and weren't working in the automation domain started to build their own robots to automate some parts of their work without help from our automation team.

UiPath's community is used by quite a lot of our developers to solve some issues and get resolutions faster. The community is quite big compared to other communities. We get more resources, and it's more active than other communities.

We use Attended Automation for some of the monitoring, like creating outlets based on network events. Attended Automation helped scale RPA benefits in our organization by automating department or role-specific processes that require human-robot collaboration. 

With the involvement of a lot of colleagues from different departments, mostly using Attended Automation, we have increased the awareness of automation and robot automation in the company.

I like the interface. It's simple to interact with. We can replicate and multiply the robots when we need to change something.

It's easy to build automations using UiPath. Colleagues who aren't very technical can develop their own automations.

The developer studio could be improved. There have been glitches, but it improved from year to year.

I have used this solution for three years.

We had some issues with stability because of some unattended robots. During execution, there were stability issues.

We didn't have many issues with scalability.

We have a good relationship with UiPath. We are in Romania, and they have an office here.

I would rate support an eight out of ten. 

Positive

The setup was easy. Within one month, we migrated from Blue Prism to UiPath and started implementing some robots.

We had a small POC to discover how it would fit in our infrastructure and how feasible it would be to have all the functionality from our previous tools. We rolled it out for a small department and migrated all automation to UiPath. Then, we gradually rolled it out to other areas.

Overall, the solution saved costs. Last year, it saved us between 8% and 12% of costs.

We increased the speed of delivery of automation, so it's a good return on investment.

We also evaluated Blue Prism. Due to its subscription pattern, it wasn't flexible enough for everybody to understand it and work with the tools. Licensing was a bottleneck.

Blue Prism didn't reduce the cost of automation, but it increased the number of automations we did in the same period by 30%.

I would rate this solution seven out of ten. 

My advice is that depending on the business domain where you want to implement the solution, it's more feasible for document processing and ingesting data in applications, not for executing commands in various application servers or infrastructure. 

Stability is an issue. In large deployments where you have a lot of robots, these issues can cause a lot of intermittent problems with the operation of the robots.

The solution helps our organization with filing sales and use tax returns. We mainly copy and paste data from Excel and process it in the solution. 

We do not use AI yet, but want to start looking into it. 

The solution has helped by decreasing the manual work required to file certain tax returns. A manual return takes about an hour but bots can complete the work in twenty minutes. This time savings has been a big help for our organization. 

The Studio is valuable because it helps us to build bots.

The Insights have been super valuable because they help us determine the benefits of our bots.

The Insights could be improved to be more user friendly and less reliant on code for building specific dashboards.

The Orchestrator could be improved to make it easier to manage folders where bots are stored.  

I have been using the solution since July of 2021. 

The solution is stable and we have no problems running bots. 

The solution is scalable and it is pretty easy to see how processes can be applied across multiple teams. 

The Community is very cool and it has been interesting to see all the various companies involved with the solution. There are many good ideas and it is valuable to hear from speakers. 

The Academy offers courses that are very helpful and assist in getting up and running. Instead of having to figure everything out, classes are available for learning Studio, StudioX, and Insights a bit quicker.  

Technical support has been fine but nothing special. I have only opened a few cases so far and support resolved those problems. 

Neutral

We did not previously use another solution. 

The setup and deployment was pretty straightforward. 

Many things come with the cloud platform so they can be a bit complex until you learn about them. I feel like we are learning new things on the platform every day. Once we learn a product, it is relatively straightforward. 

We implemented the solution in-house. We wanted to cover the lowest hanging fruit that would give us the most immediate benefit. 

With initial deployment completed, we have moved to taking our time to learn Studio and expand to more complex automations. We work with Tquila Automation who has been very helpful with development and learning. 

We have realized ROI because we have saved over 1,200 hours that would have been required for manual filings. This has been a big help because staff can instead focus on other things. 

The solution is definitely expensive but is a powerful technology that we do not expect for free. It is important to justify the business cost by explaining the ROI to stakeholders. 

We evaluated several options before choosing the solution, including Blue Prism. 

I rate the solution a nine out of ten. 

We use this solution for voice processing, user onboarding, offboarding, marketing, email consolidation, text form generation, text form ingestion, AP, and AR.

We are using UiPath's AI functionality although we have not been able to do much complex configuration. Theoretically, it works but as soon as we start adding different invoices, it's a very cumbersome, long, and human-centric process. Our company is planning to scale our automation efforts.

This solution is easy to use for the end user. The Academy courses make this possible as well as the community forums. I am a senior manager and my role is building the center of excellence. I learned how to write code on UiPath using the Academy and learned from my peers in community forums. 

This has been the biggest benefit. With other vendors, you had to pay thousands of dollars to learn how to use their solutions. With UiPath, you can learn on your own and expand your knowledge.

The task capture and task binding features have been most valuable. These features make it easier for a team who are not that familiar with RPA to successfully use UiPath. They generate the PDD the way it's supposed to be and capture the right screenshot.

The stability of the bots could be improved. The bots could be expanded to have more objects already prebuilt. It would be useful if it was clear to the end user that there are objects already built. It should be easily available or there should be a very simple search for objects. Many users don't know that Marketplace exists or that it gives you free bots. 

I have been using this solution for eight years. 

This is a stable solution and we have not experienced any crashes. The challenge we have experienced is when developers do not document requirements correctly but we have had no issues with the software itself. 

This is a scalable solution. 

Customer support is provided mostly by a consulting firm. We usually raise a ticket and get an answer. We would like the technical support to be sharper and faster rather than going through the consulting firm as this can take more than a week. 

I would rate the support for this solution a six or seven out of ten. This score could be improved if we had a single point of contact. 

Neutral

Before UiPath, we used Blue Prism. We switched due to the ease of use of UiPath as I could learn how to use it myself and teach the team. This training is free and also offers free software. 

If you are new to UiPath, the initial setup is not that straightforward. It is easier now that I have been working with the solution for a few years. The most challenging part of the setup is getting information on how UiPath connects with other systems. Only 1% of the community actually knows this. 

For the setup, our infrastructure team followed the instructions sent by UiPath. At that time, there was no cloud functionality. UiPath could offer better communication around the overall implementation and where data is stored.  The instructions are very easy to follow but the security approvals cause a lot of blockers. 

We have experienced ROI in two ways. Within the first three to six months, whatever we invested came back to us in terms of time-saving and money-saving. We have also seen an increase in client satisfaction in the sense that we can look up client information using attended bots. 

This tool makes it easy to build a team that can manage it because of the availability of the academy and certifications for upskilling. The courses are set up to ensure the user fully understands what the certification is about before they are awarded it. 

It's easy to use and the dashboards give me easy access to insights. This is why I always recommend UiPath to others. Some organizations can waste millions of dollars trying to set up other solutions. 

I would rate UiPath a seven out of ten.

My organization is an outsourcing company. We work with various clients. So, we have many use cases. The current use case I'm working on is related to invoice processing.

We don't use attended automation. We use its AI functions a bit. Usually, we work with document understanding.

Currently, I'm using the latest version. It is deployed on the cloud and on-premises. It is the UiPath cloud.

It is easy and fast to build automation using UiPath. All of our automations are created with UiPath. Usually, we do automation for SLA purposes. Most of the time, the clients don't have enough resources or humans to do the job, and they need automation to improve the SLAs.

It enables us to implement end-to-end automation, starting with the process analysis, robot building, and monitoring of automations. It is good for my company. With these benefits, we can implement it and help with the monitoring.

It has reduced a lot of human error. For example, in the project that I'm working on, people were putting the invoice information on a daily basis. There were more than 20 invoices per day, and each invoice had more than 100 line items. Humans would do a lot of mistyping on the number of packages or the number of items in the package. After we applied the document understanding solution there, we can handle around 90% of invoices, and all of them are correct.

It has absolutely saved us time. It has probably saved us more than 20% of the time. People now have more time.

I feel comfortable with UiPath. The thing that I like most is that UiPath has a very large community and a large ecosystem. So, it is easy to connect with other applications or platforms.

UiPath Apps is a great feature, but it still needs time to evolve. They need to add more features. It hasn't increased the number of automations we can create while reducing the time it takes to create them.

I don't like the sequence feature in the UiPath. It is difficult to analyze and read the code.

The variable management is really messy. When I look at the code, I don't know where the variable is and in which scope.

I have been using this solution for around five years.

It is stable.

It is scalable. We have had three enterprises that are really big with more than 1,000 people. The others are small companies.

In our organization, we have 12 people working with it.

I haven't contacted their support. I have been using UiPath's support indirectly. I just put a question on the community forum, and they answer it very fast.

In the previous version of UiPath, it was a nightmare to set it up, but now, it is really comfortable and convenient. Overall, it is fast, but the deployment duration also depends on the solution. If you design a good solution and follow the best practices, it is really fast. It takes a couple of hours at the most.

We always try to split a project into small parts so that we can test each part and apply it easily. I have seen that many people create very big projects, but when you complete them, you cannot test them. It takes a lot of testing from end to end, and we still can't test it completely. That's why we try to split a project into small parts. We can test each part independently, and after the integration, we can deploy with high confidence.

I am not sure how long it takes for our clients to see its benefits after we deploy it for them.

We have a maximum of five people for deployment and maintenance. We sometimes have issues with the infrastructure. In many cases, the infrastructure is handled by the client, and there is no support or cooperation between the RPA department and the IT department. Usually, they will be late, or they did not check our requirements to deploy the bot.

If you use the cloud model of the UiPath, it will reduce a lot of the total cost.

Its AI functionality hasn't enabled us much to automate more processes. Most of the time, when we propose those functions, we don't have an agreement with the client because of the license price. Currently, the license price is the major obstacle.

My advice would be to contact the UiPath sales team directly. I know that they have different license models for different clients and regions.

I would advise following the UiPath Academy and their best practices. That is enough.

They provide very valuable templates for automation purposes. It depends on your purpose, but you can apply the ones that are already there.

I would rate it an eight out of ten.

Initially, we had some manual test cases running in the background, where we tried to call our UI and do end-to-end testing of the login, checkout, etc. We now automate end-to-end testing using UiPath to reduce the workload. We use UiPath for process analysis and making robots, but not for monitoring. We already have other tools in our system to monitor each and every step of our process

We work in a hybrid environment, but we're increasingly cloud-based. We are not driving as much traffic to our on-premises system. 

We were hiring developers to write test cases and perform automation for us. UiPath significantly reduced the amount of employee labor needed while cutting down on human error. The error count in our system dropped by around 10 to 15 percent. 

This is a considerable win for us. Our clients are happier because they see fewer errors in production. End-to-end automation helps us deliver quality work to our customers. UiPath helps us analyze every connected case with automated robot testing. 

UiPath has a simple, creative UI, where you can check on all the automated tools. Everything is well documented, and you can easily get support from the UiPath team. Whenever we were stuck, their team was always there to support us. The community is huge and powerful. 

The entire process of setting up automations is smooth. We could easily deploy each case on our cloud platform and make things work.

We aren't scaling up UiPath because it doesn't provide a satisfactory way to log and monitor data. Instead, we use other tools like Automation Anywhere for large-scale operations in our production environment. We're building solutions that can handle a huge amount of data so we can monitor real-time issues. I don't think UiPath solves that case for us.

We've been using UiPath for around a year.

We faced some issues with scalability, so we use another RPA in production. 

I rate UiPath's support nine out of ten. We always get a response within six hours. UiPath also has a massive user community, so you can get instant support from anyone. We faced some issues when we built our first robots, so we got help from the community. When someone else has problems, we try to help them. 

Working in the community, you are recognized for your support, and you can learn a lot from others. There are some complex things about using UiPath that we don't understand. 

The UiPath community is friendly, and they respond quickly. At most, it takes around six hours to get an answer from the community, based on our experience. I believe that anyone who adopts UiPath will learn so much from the community.

Positive

We deployed UiPath through a vendor provider who helped us through the entire installation and everything in our cloud environment. Initially, we tried UiPath in our testing environment. Once we saw that it was stable and improved our productivity, we moved it to our production environment with excellent results. It took 10 months for us to deploy UiPath fully. 

We had two people working on the deployment. One managed the installation, while the second person handled monitoring and other development areas. 

We had two developers working 20 hours a week writing test cases manually, so UiPath saves us 40 hours of labor costs. However, we spend about that much on UiPath when you factor in licensing, infrastructure costs, and other expenses. The value we see is from the reduction in human error. 

I rate UiPath eight out of ten. I deduct two points because of the shortcomings in terms of scalability and logging. It's a nice-to-have solution in our case. I recommend trying UiPath out and seeing if it's suitable for your use case. You should go for it if it fits. It's not too costly and it will reduce human error while improving the quality of your product.  

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

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

We only use unattended automation.

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

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

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

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

It helps us a lot with digital transformation.

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

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

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

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

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

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

We used the community to help us with the setup.

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

UiPath has reduced human error by 20%. 

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

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

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

We didn't consider any other solutions.

I would rate UiPath as eight out of 10.