UiPath Reviews

We are using Orchestrator, attended robots, and unattended robots.

Our primary use case for this solution is in the financial industry.

We do not yet run our automations in a virtual environment.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a four. The whole interface needs some TLC because it can be a bit tricky.

We have used the UiPath training and it has improved a lot since we first tried it. When I used it a while ago, it had its problems. I think it came due to the fact that it was not developed by native English speakers. For example, they had questions that were simply wrong. It has improved a lot and now it is beneficial. I think that the biggest challenge is for them to stay up to date.

From the point that we purchased our UiPath license until we had our first robot was approximately four and a half months.

This solution has saved us time, but more importantly, it has saved us money by not paying certain fees or certain penalties. With respect to saving money, the last amount that I saw was six figures. Legally, I am not allowed to say more.

Being in the finance business and having certain audits, this solution helps to make sure that we have validations and checks in place to help us to do our processing quicker. Also, with invoices, normally when you pay them by a certain date you get a certain discount. So, we've managed to significantly increase the savings we get just from having invoices processed earlier or on time.

In terms of eliminating human errors, we have one process where we've eliminated errors completely. The average is that we eliminate errors by fifty to sixty percent.

The most valuable feature in Orchestrator is the scalability.

The most valuable feature of unattended robots is that they are always available.

They have added a lot of new features over the past months, and things are a little more complicated. In the interface, sometimes you just have the screen full of windows and figuring out what goes where can be a bit tricky.

We would like to see improvements in Studio such as syntax highlighting and documentation functionality for audit purposes. That would be great.

With respect to the stability, on a scale from one to five, I would rate this solution a four. There are a couple of things that break the robots, and it has to do with the technology itself. The user interface and other components are prone to error, and it's not one hundred percent automation. This is something that you take into consideration when you do RPA. They have also had a couple of updates over the past years where they made significant changes that basically broke the robots.

We have more than a hundred people involved with RPA.

So far, I have only used the ticketing through email support, and it is sometimes frustrating. I've only just learned that there is telephone support. It is hard for me to rate customer service because I was looking for telephone support, thinking that it was not available.

In general, there is room for improvement support-wise.

We are in an industry that is heavily targetted by low-cost countries, so in order for us to stay competitive, we had to do something. When we did our research, the two obvious solutions were RPA and AI.

When we started, it was with Blue Prism, and we learned from the issues we had. When we were looking at what we could do as an AI, UiPath started to emerge and started to become a big player. We then looked at capabilities and the licensing model, and at the time there were two vendors that had pretty similar capabilities.

These two were Automation Anywhere and UiPath. Automation Anywhere had a very high initial investment requirement and UiPath didn't, which is why we stayed with UiPath. I believe that you had to buy at least a hundred licenses for Automation Anywhere, whereas with UiPath you can buy one or two.

It looks like we made the right choice.

The initial setup of UiPath was straightforward. The approvals on our side slowed things down. If it were not for that then we could have been up and running in six weeks.

We implemented the solution ourselves.

We only automate processes where we expect to see ROI within twelve months. As such, most of our processes have an ROI between six and twelve months.

We evaluated Blue Prism and Automation Anywhere before choosing this solution.

We are in the process of moving this solution to the cloud.

From a cost perspective, it is very hard to get ROI with an attended robot. The price is too high.

My advice to anybody who is researching this solution is not to overthink it. RPA is a technology that you learn by doing it.

This is a very strong product. I think that there is a lot of good investment and a lot of good attention out there. This is the best or one of the two best tools out there. They are listening to what the market wants and just need to be careful not to get greedy. That said, there is always a little bit of space for improvement.

I would rate this solution a ten out of ten.

The primary use case of UiPath, with every organization that I've worked with as a consultant, has been to make business processes more efficient and the work of their employees more enjoyable. 

By utilizing this technology, you're able to get value through your value streams quicker. When you realize value, that means you can work with your customers more quickly, as well as build customer loyalty and employer loyalty. These have definitely been some of the byproducts of using the software.

When I was working as an RPA manager, managing a program for an insurance company which supported insurance lifecycle processing, one of the components was that they had to review insurance policies annually. It was very cumbersome. We were talking anywhere from 10,000 to 40,000 daily. It was almost a 20-FTE process. We were able to automate that completely.

However, the real value came when the organization understood how to apply RPA and it actually began creating brand-new business processes specifically for RPA. So instead of hiring new people, they said, "Hey, we've always wanted to do this, we don't have the budget to bring on and train people, so let's build bots to do it from day zero." Once they were able to understand that I could do more than just automate processes, that I could build new business lines with bots, that was an incredibly valuable result of using this software.

The benefits are very high when you automate business processes. Before using RPA, I was working in technology, building macros and things of that nature. But the way we're able to build sustainable, functional bots that really work well in the long-term makes the benefit a ten out of ten.

This is going to be an interesting answer, but the most valuable feature of the software is not the software itself, but the community that supports it. When I first started learning the software to support a program, I had to self-teach; there wasn't a budget for training. But going through their learning platform and then connecting with the community when I didn't understand how to utilize some of the functionality, that was far more powerful than the product itself. The network around the product is amazing.

The great thing about the UiPath RPA Academy is that it's not stagnant. Even though my first go at getting certified as a developer was three years ago, I literally have to go back the Academy and learn it every year because there are new features and new functionality. An example is the RE Framework they've incorporated. The living nature of the Academy gives a lot of value. But hands-down, the way that they give practical exercises, the fact that they give you applications you can download to learn how to interact with bots by simulating an actual operational environment, makes it a very impactful learning experience.

In addition, I find the solution easy to use. I have personal experience using all three of the major software vendors that are in this space right now, including Automation Anywhere and Blue Prism, and I would put UiPath as number-one, specifically from a learning perspective. I've been able to take people with absolutely zero technical background and quickly scale them up in a matter of weeks so they're building bots. I haven't been able to accomplish that same feat with the other platforms.

Being a person who has held every RPA role from developer to analyst, architect, and executive, one feature I think it needs - from a documentation perspective - is the ability to easily extract variable details and data. They do have a Variables panel that you frequently interact with, but I constantly have situations where those need to be adjusted or I want to be able to present those to a business. Sometimes it's difficult to extract those, and if you're not tracking them while you build, you can quickly get into 200 to 300 variables in use, especially using the RE Framework where you're passing workflow arguments in and out. I would like to see something like that.

In addition - and obviously UiPath is aware of this - we have to continue to improve the OCR capability. Computer Vision is excellent. I've used it on Azure. I've created PeopleSoft environments and worked through the Computer Vision feature. It works amazingly in a Citrix environment. But I speak with multiple organizations and a lot of them have the same problem of processing documentation from the mail room or from vendors, etc. That's a huge component. If we can get that embedded in UiPath, so we don't have to rely solely on OCR vendors like Captiva or ABBYY, that would be a huge step forward in being able to service all organizations.

There could be improved logging and functionality. But if you truly understand the software, adding logging to what the bot is already doing is as simple as typing on the right line. It's incredibly easy and you can embed it. Even though what it currently logs is limited, it's easy enough to create logs or reporting without a lot of effort.

Outside of that, it's really hard to come up with other recommendations. The software is solid.

I was recently reading about the document processing framework that they just implemented. I gave a demo two weeks ago on the Computer Vision functionality that was in beta. So the sustainability is there. They're focused not on just how good RPA is and on making it better, but they're also integrating it with future-tech. That is where the stability comes in.

UiPath's scalability and stability are exceptional. They are constantly releasing new versions.

Scalability is all in the delivery. I've definitely run into multiple organizational roadblocks with my clients because they get six months down their delivery timeline and they're not meeting their OI, they're not scaling. That generally comes down to how it's being delivered. If you have experience, you're working with a partner, you're working with people who have used this solution at scale, you can generally bypass a lot of those roadblocks. It's definitely scalable if you have the right expertise.

I have used both technical and customer support. When I was going through training, trying to learn some of the software, I had issues when I finally purchased licenses. The issues were related to putting them in Orchestrator and installing them. Support was definitely very supportive, very responsive when trying to get feedback.

Even when it comes to the community, as well, if you're just trying to learn the software, to learn the features and functionality, the community network is there to quickly respond and support you so you can get back to getting value, instead of getting hung up on one piece of functionality.

I have seen cases where an organization moves from a different automation solution to UiPath. At one point, we were transitioning from Automation Anywhere. There were very basic bots, these weren't complex processes, but we built a bot in UiPath that read the XAML of the Automation Anywhere script, converted it into activities in UiPath, and built a bot. We had a bot that builds a bot.

An example of why people move to UiPath is that when I was the director of RPA for a finance company, when I set up the program I had to go to EVP and pitch the prices and the costs. When I gave him the cost for all the software, to bring a vendor on, he told me "no." It was way too expensive. But UiPath has this amazing option called the Community Edition. What I was able to do was download the software, teach myself how to use it in about 45 days and, within two months, I had automated a pilot process, completely on my own. I was able to walk it into the EVP and say, "Look what I was able to complete. You told me no money, no funding, but now can I get funding?" Then I got funding and was able to bring on a team. That's one perfect example. They said "no," so I got a free version that cost me nothing.

In terms of how companies know that they need to invest in automation, in this day and age, with the speed at which information and technology move, it's at the point where this is not a new topic. A lot of organizations, through word-of-mouth, internet searches, or conferences, or events such UiPath 2019 here in DC, realize it as soon as they hear the success stories. It's impossible to ignore. Most organizations are like that. They hear about it, they realize that it's something they should consider, it's something they have to do, and they take the next step.

The initial setup is absolutely straightforward; it provides a quick and easy installation. Given that you may have to go through some technical hurdles to get permission to download it, I'm not talking about that. But if you have all the permissions and you're allowed to download and install it, it's absolutely simple. It shouldn't take more than ten minutes.

Technical prerequisites are not needed to use the software, but technical resources can speed up the ease with which you deploy. Given that you're generally not interacting with UiPath in isolation but with other business applications as well, you want to make sure that there's technical support in case you have some issues. Or, if there's something that you didn't experience in UAT but that comes up once you get into production, it's good to have some additional support. It's not a requirement but I would recommend it.

ROI is one of the most frequent questions I get from organizations. You should be seeing ROI in less than six months. If you're not returning your cost and more, from a licensing and personnel standpoint, in the first six months, then it is not a software issue and it is not a delivery issue. In that case, it is a scoping issue. You're probably looking at processes that shouldn't have been automated in the first place.

Every organization that is successful with the software is reaching their ROI in six months or under.

The amount of time saved with bots is an interesting question but it's hard to answer with a pinpoint response because it depends on an organization's strategy. I've seen multiple organizations that use attended bots, so they're just saving a fraction of the time. But then I've been in organizations where they've automated a process end-to-end. A process that previously required 20 FTEs went from having 40,000 hours of manual work to zero.

For pricing there is a variable at play, and that's scale. Depending on how you want to scale - whether working with a partner or directly with UiPath - there's a specific cost per license. But then it's all about optimizing a process, and what we call "license utilization." We try to maximize each license, and we'll have it running three or four processes.

The cost is nothing, it's peanuts, when you see the capabilities. When you're talking about one license supporting what was previously done by 14 people, what is $1,500, or whatever the licensing cost is for unattended bots?

Even more importantly, as a technology expert, I know that I could do some additional coding and automate the running of the bots. But why would I spend that extra time when they have Orchestrator. I could have a person running them as well, but the Orchestrator license is far cheaper than a resource; just click "run." When you compare the results that you get, the price is a moot point.

If I was going to give any advice to someone who was just about to utilize the software, I would say that the most successful organizations that apply this technology make it an entire team effort. It's not started in one business unit. And if it is, it's socialized across the enterprise. That's the quickest way to scale: getting everybody onboard. The second-biggest thing is that the most impactful projects you will get will come from your people, your internal workers. And until you get them to understand what the software can do and its capabilities, it's going to take you longer to scale your program. So make sure everybody's socialized, and make sure everybody truly understands what the software can truly do. They're going to give you the best opportunities to benefit from it.

Deployment should definitely be done using the support of experts. Even when I owned my own RPA program, and I wasn't in a consulting capacity, I still reached out to a third-party to get support. While setting it up is something that you can do internally, given that most objectives include speed-to-market and quick scaling - wanting to see results in 60 days instead of six months - it's going to be very difficult to do alone, especially if your goal is to have 100 bots in a year. If your goal is ten, you can probably manage it. It's important to use experts if you are looking to rapidly scale.

I have implemented UiPath in virtual environments, including on-prem, Azure VMs and servers, SQL-based data storage, as well as AWS. I've never had any issues with the responsiveness or the application having any problems operating. The biggest consideration that you have when trying to deploy robots in a virtual environment is making sure that your architecture is sound. You have to integrate through severs and you have to take into consideration firewall updates. And then there's interacting from the cloud if your applications are on-prem. You have to make sure that the bot doesn't have any issues. But if your architecture is solid and your infrastructure is set to support the applications in a cloud environment, there shouldn't be any issues. You wouldn't notice any difference compared to having them on a desktop on-premise.

I would agree that UiPath eliminates human error, but I would add the caveat that good code eliminates human error. I've been doing this for a while and I've seen bots that mess up. It's in your delivery methodology. If you have a sound delivery methodology - you're going through a rigorous UAT cycle and are having outputs audited by the subject matter experts - you should literally get to zero errors. Maybe you will have five percent exception cases, but your error percentage should be zero.

Having worked with all the tools, they all have little niche components. As long as UiPath continues to focus on knowing what the next wave of technology is that businesses really need to use to be efficient, and they start embedding that skillset in their software, that's all you could ask for. They need to stay in front of the power curve of technology, which is impossible, but they're trying.

I've never had a bad issue with UiPath. My experience with them has always been pleasant and engaging. They're never stuck at just giving you software, showing you how to use it, and then walking out. They're always focused on improving your business. If you focus on that, and focus on generating value, you can't lose.

Automation technology is the number-one driver across an organization now. Trying to find ways to do more with less has been the going mantra for organizations for years now. It's no longer feasible to simply run operational efficiency or Six Sigma projects to try to get gains. The only way that you're going to get significant gains is going with an automation-first approach. That's where I see a lot of organizations headed, even spending more on RPA software than on cloud implementation. It's a very big focus, and I don't see that slowing down any time soon.

On a scale from one to ten, I would you rate UiPath as an eleven. It's excellent software.

We're a tech consulting company that works for insurance companies. We use UiPath for tasks related to payment processing, deductibles, and denial of coverage. We check each part of the process to ensure that the patient has met a set of criteria. We're checking the deductible to see if it has been met, and we update the notes on the platform. UiPath is useful for all of our clients regardless of the industry. For example, we have used it for payroll and payment processing at Citibank and Doshi Bank. 

A bot can run 24/7, reducing the human labor required. That is UiPath's major advantage. It reduces the number of manual tasks while also improving and enhancing human labor. A manual task that took 10 minutes in the past can be completed in two or three. We are saving a lot of time. 

Let's say we have eight people doing a particular task eight hours a day on a five-day work schedule. Once we automate that task, we can run the bot 24 hours a day Monday to Sunday. Automation reduces our costs and human error. The accuracy and data security are high. It's beneficial all around.

Uipath facilitates data sharing between systems. We have some shared folder packs that enable us to share the data from one system to another. This functionality can be important, depending on the project and type of data. We use some encrypted features. If we want to share data in encrypted mode, we can put it in an Orchestrator folder on-premises so only those with access can see the data. 

The business will share the data, including employee and patient records. All the data is shared within the database.  Either the employees can send data over, or they can access the data from that particular folder. UiPath offers a central portal for managing patient information. We've done a lot of things to extract and utilize patient information, ensuring that it can be accessed by the appropriate teams. We have to train our bots to capture the right information, like the patient's name, address, ID, location, etc.

UiPath is good for data scraping and extracting information from websites. UiPath is approachable, and it makes life much easier by automating repetitive tasks with the help of drag-and-drop flexibility, eliminating human interaction. The drag-and-drop APIs make it easy to get data from the API quickly.

I also like UiPath's security features because it gives us lots of tools to secure sensitive information. We can encrypt the customer data and store it in UiPath on-premises. We can also control access so that only authenticated users can obtain the data. 

Citrix and email automation could be improved. We can use the features, but the accuracy isn't 100 percent. 

I have used UiPath for the past five years. 

I rate UiPath support eight out of 10. They provide us with assistance while we are developing bots. We can send the Orchestrator logs to UiPath to find out where a process is failing. For example, a web-based process might be using an old particular password. The support team will notify us that we need to update the password in the production environment. 

Positive

Before we implemented UiPath, we tried Automation Anywhere. I like UiPath the best because it has capabilities like Document Understanding, AI, fabric, etc. UiPath has more features than Automation Anywhere. When we did a POC of Automation Anywhere, we found that the data scraping wasn't as accurate when working with PDFs. 

The deployment may be straightforward or complex, depending on the project. Before each project, we have a testing phase of about seven to eight days. We have a 10-day monitoring period. In that 10-day period, the developer is also involved with the support. We have a different support team that takes care of most of these things, like deployment and monitoring the processes. If something goes wrong, they have to open a ticket and reach out to the developers. 

Our implementation process involves checking all the business requirements. We look at the software and machines our clients use and the steps involved. Once we know the business requirements, we start working on the modules. We determine how many modules we need and the amount of time it will take to develop them. 

After that, we have a daily scrum call. If we have issues, we reach out to the business, and they will come back with a solution. We need to undergo this initial development phase before starting anything. Once the development is completed, we have multiple process design documents detailing the processes and steps. We also work with third-party integrators. About seven or eight staff members are involved. 

This solution does not require much maintenance once it is deployed and we've granted the access required. Once we've ensured the process is running and done the initial updates, we don't need to maintain it.

I haven't calculated the ROI, but I've heard that other people have seen 60 to 70 percent return on what they invested.

The pricing depends on the project and how many hours we will charge. 

I rate UiPath nine out of 10. There are still a few areas that require improvement. Before implementing, I suggest doing a POC so you can evaluate other tools side by side to see which one is best. 

We are a partner of UiPath and a system integrator for our clients.

For most clients, we tend to begin by focusing on areas with the highest potential for automation. This typically includes finance, procurement, or HR functions, with the first two being the most common choices. These areas are chosen because their processes are generally stable and repetitive, making them ideal starting points for RPA implementation.

However, our experience doesn't end with just one client. We've had numerous engagements, including with large, multi-company groups. Once one division like the "glass division" successfully implemented RPA, it often sparked interest in other divisions like the pharmaceutical division. Demonstrating a solid proof of concept makes it easier to scale the technology to diverse use cases across the organization.

Ultimately, overcoming the initial hesitation and showcasing the tool's benefits is crucial. Once the value becomes apparent, a shift often occurs, transitioning from a client-driven demand to a proactive push from various departments eager to eliminate tedious manual tasks.

While we haven't encountered any major technical roadblocks, understanding the potential for automation has been the primary challenge for users. Initially, we also faced some learning curve hurdles during the first few projects. However, as our internal expertise matured, approximately 80 to 90 percent of use cases have been implemented smoothly with minimal or no support from UiPath. It's clear that effectively identifying tasks suitable for automation versus those requiring human intervention has been the key hurdle. From a purely technical standpoint, the capabilities have been readily achievable.

While UiPath facilitates end-to-end automation, its feasibility heavily relies on the specific use case and associated tuning costs. The decision to automate isn't solely driven by cost reduction, but also by the number of tedious tasks it can alleviate for employees. Clients are often eager to free their workforce from such repetitive drudgery, especially if the task is long-standing and well-defined. In these scenarios, full automation often presents a compelling value proposition.

The UiPath user community exists on two levels. First, there's the general UiPath user community, managed by UiPath itself. This broader community offers a valuable resource for learning, sharing experiences, and finding solutions. Second, once a UiPath instance is set up within a specific client's environment, a smaller user community emerges within that client's organization. While this internal community may seem less significant, its role in supporting individual users in tackling automation challenges is crucial. By sharing their experiences and overcoming difficulties, these internal user communities can act as "roll cages" for individual functions, providing guidance and support regardless of the specific challenges encountered.

Initially, our focus was solely on on-premise solutions. In fact, up until last year, I hadn't encountered a single client who had implemented their RPA solution on the cloud. This was primarily because we catered to a mainly small business clientele. However, the landscape has shifted significantly, with more and more cloud-native solutions emerging. This shift has been driven, in part, by the cost-effectiveness of cloud-based options. One of the major roadblocks to cloud adoption in the past was the pricing of the orchestrator. While it might be suitable for supporting large client bases with thousands of users, it wasn't cost-effective for smaller businesses with only 100-200 users. Fortunately, UiPath has introduced a new approach, allowing us to purchase orchestrator instances tailored to specific user base needs. This, combined with the inherent benefits of a cloud-based platform, has made the cloud a much more attractive option compared to 2019. In conclusion, cloud computing is now a critical factor in the RPA landscape, and the adoption of cloud-based solutions has become significantly easier. This shift has opened up new opportunities for businesses of all sizes to leverage the benefits of RPA technology.

We started with five or six people trained online by UiPath and the different certification programs available in the UiPath Academy courses were helpful.

UiPath has helped to drastically reduce human error to almost zero by automating all the structured data that used to be done manually by people. This has improved the quality of work for our clients.

UiPath has helped free up employee time. Previously, we analyzed each potential use case to determine its priority. Before committing to a specific case, we built a business case to assess its potential benefits. This involved analyzing how much time automation could save, the associated cost savings, and the number of transactions it could automate. We performed this analysis during the design and assessment phases of our workflow. Following this process, we would gather the data and present it to management for approval before moving forward with automation. The amount of time saved depends on the individual use cases but they are significant. What used to take hours now takes seconds.

UiPath has delivered cost savings for our clients' organizations, not through mere implementation, but through thorough assessment. We start by demonstrating the technology's value through small-scale projects, then scale up. At this point, we gather a list of potential use cases, identify the number of users who could benefit, and pinpoint the manual tasks ripe for automation. Only then, with a business case in hand, do we proceed with full implementation. This careful approach ensures that when use cases are deployed, they translate into meaningful time savings and reduced manual workload. As a result, our clients typically see cost savings in staff reductions of at least 30 percent.

UiPath is an efficient and user-friendly tool. It allows us to record and capture actions, which it then translates into underlying code. This makes development incredibly fast. The centralized orchestration feature is also a major advantage.

Clients are often convinced by its features and marketing. In some cases, when competing with Blue Prism and Automation Anywhere, UiPath has won out due to its faster time to market. This was especially true during the early days of RPA when clients were still experimenting and wanted to try multiple vendors. UiPath's flexibility and strong support, both during evaluation and implementation, were also key factors in its success.

We sometimes use the AI functionality mainly for document scanning but at the time it was poor and had room for improvement.

The operation costs have room for improvement. 

I have been using UiPath for over four years.

UiPath is a stable solution.

We haven't encountered any scaling issues, and UiPath is theoretically scalable for up to 10,000 bots. We've successfully implemented over 100 use cases for a large client with multiple subsidiaries, receiving no complaints.

The technical support is good.

Positive

The initial setup is straightforward and UiPath worked with us for every deployment.

We implemented UiPath for our clients in-house.

We evaluated Blue Prism and Automation Anywhere. Blue Prism and Automation Anywhere are not as user-friendly as UiPath and they don't have the same user community.

I would rate UiPath a nine out of ten.

Previously, we distinguished between Automation Anywhere and UiPath based on their bundled offerings. Automation Anywhere included category two AI capabilities with their RPA solution, while UiPath focused solely on RPA and didn't have much presence in the AI space at the time. Although UiPath could integrate with other AI vendors, this wasn't a significant interest for our clients.

Most deployments we completed for our clients were central.

We use UiPath to automate routine tasks in our organization.

Building automation using UiPath is easy.

We have used UiPath to automate sustainable production tasks for some clients. The automation saved our clients time.

The UiPath user community is a place where we can learn more easily.

Since implementing UiPath, it has saved our clients a lot of time.

We can use UiPath Academy courses to learn about the product and apply that knowledge in our organization.

The AI functionality in UiPath enables us to easily improve our more complex automation processes.

The AI functionality has helped us automate more processes.

UiPath has helped reduce human errors by 90 percent in our automation.

UiPath has helped free up 50 to 80 hours per week of employee time.

It has helped us reduce costs by 80 percent by automating routine tasks.

Integration with third-party tools, machine learning models, and document processing are all valuable features.

The price always has room for improvement.

I have been using UiPath for two years.

UiPath is stable.

UiPath is easily scalable.

I previously used Microsoft Power Automate. Although both tools are popular, UiPath is easier to integrate with third-party tools and more accurate.

The initial setup is straightforward. The deployment took one and a half hours.

UiPath's cost is moderate.

I would rate UiPath a nine out of ten.

The maintenance required is minimal.

We have UiPath deployed in one location.

I recommend UiPath.

I work for a telecommunications company, which involves various processes in different areas. For all the company's needs, I primarily utilize UiPath. We have employed it to automate tasks such as packet installation, software attribute utilization, and coupon allocation. These are time-consuming tasks that involve a significant amount of data, making it impractical for a single person to handle. Therefore, we assign these tasks to a bot to expedite the process.

Building automation using UiPath is straightforward. As a developer, I have colleagues who want to learn simple automation quickly, and UiPath is one of the best solutions for this, thanks to its tutorials and the UiPath Academy courses.

Our organization is beginning the implementation of end-to-end automation using UiPath. The implementation is easy and enables users to interact with the testing, thus saving a significant amount of time.

The UiPath User Community is one of the best aspects of the solution. The community is extensive, and everyone is willing to assist by providing information and guiding us in the correct direction.

We quickly realized the benefits of UiPath once we implemented it, including cost savings. We began automating areas where we encountered difficulties, and within the initial three months of automation, we started witnessing the advantages. After completing the necessary courses, we were able to automate quickly.

UiPath has helped our organization minimize its on-premises footprint, which is important for the implementation of the RPA in our day-to-day activities.

I have taken several UiPath Academy courses, and they are easy to follow.

UiPath has accelerated our digital transformation, leading to reduced costs and time. Our customer IT team has provided invaluable assistance throughout the process.

UiPath has eliminated human errors when dealing with large amounts of data. One of the first automation we needed to have done was one that, if not processed at that time, would risk losing money, time, or even a partner. So what we did was automate the task that consumed most of our time. By the end of the day, we were able to complete the task and ensure all the client information was corrected.

UiPath has freed up our employees' time, allowing them to focus on more important tasks. 

The RE framework is a valuable feature because it offers the possibility of working with a large amount of data without the need to transmit all the information. 

AI can become more intelligent to facilitate the ease of automation.

I would like UiPath to support the Python language. It is easy to develop in Python, and there are thousands of libraries available that I can use within its environment. Such support would greatly expand my capabilities for performing my RPA activities.

I have been using UiPath for one year.

I encountered some stability issues initially when I had limited knowledge. However, I now find it to be quite stable. UiPath stands out as one of the best options in our market when it comes to stability, thanks to its frequent updates and bug fixes.

UiPath truly emphasizes the capability to scale.

The technical support is good and has responded to all of our questions.

Positive

The deployment was handled by two people from our IT group.

UiPath offers a significant return on investment due to the rapid realization of its benefits.

UiPath is reasonably priced for being a leader in the market.

I have evaluated Laiye UiBot, Hover Corporation, and OpenRPA.

I prefer OpenRPA because one of its advantages is being open source. That's great. Additionally, it offers great features, such as quick comparison capabilities with Velocity. This impressed me. Another notable aspect is the ability to code in various languages and run them independently. This allows me to seamlessly integrate with my workflow and agents. I can execute the code in my environment and directly communicate with the robot, which is a fantastic feature.

Compared to UiPath, OpenRPA is slightly faster, open-source, and allows for the incorporation of work codes, but UiPath offers greater functionality. 

I give UiPath a nine out of ten. The design and appearance of UiPath are excellent, and its functionalities are perfect. The impressive aspect is how people create packages and new automation using the solution. I have nothing negative to say.

UiPath is currently deployed in one location within our organization.

We have a dedicated maintenance team of two individuals who are knowledgeable and have not encountered any difficulties.

I suggest utilizing the Community forum to acquire knowledge about UiPath because it contains a wealth of information beyond what is found in the documentation itself, and the support provided there is exceptional.

One of the use cases is related to material billing. For the material billing process, previously, when a vendor invoice came into our SAP system, our staff had to write invoice data and process the invoice. We transferred this process to RPA. We now have only one robot focusing on this project. It handles about 120 invoices in a month.

We have not yet used UiPath's AI functionality in our automation program. We are always thinking about using AI and machine learning in our development, but we have not had a project in which we could use AI. We might use it in the near future.

It is deployed on-prem, but we are thinking about changing it to the cloud.

It is easy to build automations by using UiPath. One of the projects was related to reporting or getting some information from the websites. To do our purchasing, the department needs a summarized report containing prices in email. We converted that into an RPA project where the robot accesses the website, reads the specific numbers, creates a small report in Excel format, and sends it as an email to our department. It took us three days or so to implement this automation. It was an easy project.

UiPath enables us to implement end-to-end automation. One advantage is that robots can work 24 hours. It enables people to add some value to the company. They can think about some places where they can improve or they can reduce costs. They have enough time to think about it. Before RPA, they used to take a lot of time to do the same work.

Our on-premises footprint has been reduced. For our invoice use case, our staff used to print out the invoice to check the numbers and enter the data. We eliminated that and reduced our paper usage by approximately 20%.

UiPath reduces the cost of digital transformation. We are using the SAP system, and there is a cost if we want to implement any automation. There are consulting companies that can write the code, but they are very expensive. With UiPath, we can automate our processes and eliminate or reduce that cost.

It has reduced human error. If the invoice is correct and the data is correct, what the robot writes into SAP is also correct. It has reduced risks and errors.

Employee time has been freed up. It saved us the time of one staff member. We were able to shift that person to another department because of the time savings.

UiPath has saved us costs. We could shift one staff member to another department. We did not have to hire one more staff member, so it has saved that cost.

The development part is very simple. It is easy to use. Our development time for a project is approximately two weeks now. It is good because even though you can develop the code in SAP, it takes a lot of time. When the demand is high, we can deliver in two weeks. It has helped us to tell our organization that RPA is easier and faster than the usual code route.

We have used UiPath Academy courses for process mining. For RPA, we have some KPIs for developers to complete their education. In UiPath Academy courses, they have an option for the Turkish language for videos, but they are always in English. They should correct that.

UiPath should integrate more machine learning and have more machine learning processes. In their development system, they have some machine learning tools, but they should increase them. With robots and structured data, in my opinion, we can use machine learning. The robots should also use machine learning to create some AI models.

Its price should be reduced.

We have been using UiPath for two years.

At the beginning of the project, there were some issues, but now, it is stable.

It is scalable. For the RPA part, we have 5 robots, and we have 40 projects that are live. We have about 100 projects that are to be implemented.

I would rate them an eight out of ten.

Positive

We did not use any other solution.

In our department, we have three employees for implementation. We do not take the help of any consulting company.

Its price could be better. They should reduce its price.

The insights module, process mining, document understanding, and other modules should come as one package because when you buy a module, it usually is not enough for a project, and then you have to buy another module. They might already have bundled these. I have not checked it recently.

To those evaluating this solution, I would recommend seeing it as one package. Before implementing it, the organization should also be ready for it because, with automation, people have concerns about losing their jobs. Organizations should have a clear understanding that robots are coming to save time.

Overall, I would rate UiPath an eight out of ten.

We use UiPath to automate activities that are typically done on a computer by an individual. It's used to automate purchases involving a large volume of transactions for hundreds of organizations. 

UiPath has improved customer confidence and helped us cut costs. We can complete tasks faster and reduce our backlog. A fast turnaround time keeps our stakeholders happy. It also improves accuracy. We can customize and optimize the processes. 

Before UiPath, we had a five-person team. It took them each around six hours to complete 200 tasks. We cut that down to one hour by implementing automation, so it took only five employee hours to do the same amount of work that formerly required 30. It also saves energy consumption because the same result can be completed in far less time, so the employee's computer isn't running continuously.

We can reduce our on-prem footprint because we can store our data in the cloud and use UiPath to automate cloud-based data solutions. The cloud is more accessible, and various tools can access the cloud database, whether you're using a mobile phone or desktop. 

The UiPath Academy helped prepare our team to use the program. The introductory course taught them everything they needed to know to start working. UiPath also has a huge community that has been helpful when we have issues. Most of our questions have already been answered.

We've used some of the AI features. For example, machine learning is built into the document understanding system. We're working on integrating ChatGPT, but that's not mature yet. APIs are available, but we are still not integrated. The ChatGPT APIs can make our automation more complete and compliant. 

We can do complex automations with UiPath. For example, we can automate processes that need to be authenticated to run and integrate processes with the AI engine. UiPath didn't require any upgrades. We could run it on our existing infrastructure. 

The user interface is intuitive and easy to understand. This automation increases the ease of operation for the employees. 

Building automations can be a little complicated. There are so many variables and commands. We're also trying to integrate new technology like ChatGPT. Although ChatGPT has many APIs, they're not sufficiently integrated. If UiPath could add more API integration and tutorials in the academy, it would help us utilize them more effectively.

We have used UiPath for four years.

UiPath is stable, but it's crucial to understand new features when upgrades are released. Updates can cause problems because sometimes we don't know how to use the new features.

UiPath is scalable.

I rate UiPath support nine out of 10. We don't typically require support because we can usually get all the answers from the UiPath community. 

Positive

We also tried Automation Anywhere. It has a more user-friendly and attractive interface. UiPath has more features, a larger user community, and is more capable of handling integrated processes. I think Automation Anywhere is a better fit for small businesses and startups. 

The deployment was straightforward. We purchased the license, downloaded the software, and installed it, then we programmed our bots. The deployment can be completed by one person in two days. 

The software is on-prem, but the data is stored in the cloud. The solution is installed on a server that multiple people can use. Regarding maintenance, there are only routine updates. The bots themselves need to be maintained, monitored for performance, and optimized. Sometimes you need to modify them when we have additional requirements. 

The ROI is excellent because you can significantly reduce your staff's working hours. You'll start to see a return after one or two years. 

Large enterprises can negotiate a better price, but UiPath is comparable to Automation Anywhere if you're a small company. Automation Anywhere is affordable for small integrations. There are various kinds of licenses, and the return for a small company could be positive. Still, the architecture and usage-based licenses are costly. As the volume increases, it may become unaffordable for smaller businesses. 

I rate UiPath nine out of 10. It's a great solution, but it isn't easy to use, and you need to learn a lot. I recommend taking advantage of the free courses and other resources available.