UiPath Platform Reviews

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 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.

We mostly use it for unattended bots. We are a construction company. Our RPA team does more of the complex processes for users. We take high-end complex items, that are redundant, off of the users' hands, then we host it on our servers.

We have a bunch of unattended processes, about 284 processes.

RPA isn't necessarily taking away tasks from employees, but rather moving them from processing-type employees to analysts. For example, if we had billers doing a very redundant task, then we moved that to RPA. Then, the billers do more customer face-to-face work and analysis, e.g., solutions through Salesforce. So, we have those employees who were previously billers move up to better positions where they can do more analysis and human interaction.

The solution has reduced human error. We don't need to go back and fix stuff. Customer representation is also huge. Quality of work is one of our mission statements. Having that repetitive test always being 100% every single day, month, and quarter, and whenever we send specific invoices from our server support, has been really helpful. It increases that quality formation.

There are a lot of job positions that we never really thought that would get created. Freeing up those experienced employees from sitting down and processing a lot of stuff throughout the whole day and moving them up to customers, we started discovering new talents and skills, especially with the younger employees since you are basically freeing up their time to discover new skills that they weren't even aware of. You are investing in them, showing customers that you have a new generation of fine employees who can do a bunch of new skills out-of-the-box.

The orchestration is the most valuable feature, e.g., how stuff can be organized. This is in addition to the fact that we try to move stuff to an unattended base where there is no user interaction. We are moving more to 100% automation rather than putting a human in the loop.

The UiPath Academy is mostly used only by technology associates and power users in each department who show interest in RPA. The academy has improved on the onboarding system that we have for RPA. So, if we see potential with someone, whether it is interns, power users, or even IT professionals around our department, then the UiPath Academy is definitely a good way to go. It kind of eases up the onboarding when determining who is outstanding or could potentially join our RPA teams.

The biggest value of the UiPath Academy is the ease of use. A lot of different platforms can be too complex. The user-friendly platform definitely helps with the ease of its steps. 

While it is the best tool ever, we decided that the user interaction might not actually be the greatest thing ever. 

I have been using the solution for three years.

I am very happy with the stability of it. 

I wish that there might be a better, easier method of updating our platform, especially for on-prem. I believe most of their customers are cloud-based. So, they don't have to worry about updating their Studio versions or Orchestrator. Being on-prem, it can be difficult because we must reach out to have that version. We can't just plan on our own. We are always at least a six-month step back versus the current version.

We have been scaling it as much as we can, especially with how we are trying to scale how big our team is as well as trying to control that specific workspace and workforce that we have.

There are currently five developers using it.

There were a couple of times with the on-premises version that there were complications, since it is not on UiPath's cloud. We have had a lot of complications where we are dead in water. There were a couple of conditions where we weren't able to get someone up to speed on whatever. The support is not as quick to respond as we had hoped. 

We did talk to our account executives about this. It is definitely a work in progress. I know that they have recommended that we move to the cloud, but it is not attractive enough for us to see if it is actually worth moving to the cloud.

We have been with UiPath from the start. We used to have a lot of in-house C# libraries that we curated. RPA was like overpowered macros similar to what we already had. That is why we knew how to deal with it. 

The initial setup was straightforward. We did it through the on-premises by connecting our SQL database, etc. 

The deployment took around three hours.

The initial setup was with their tech support, and that was definitely great. After that, if we had any hiccups, that was where the complications happened.

The main focus was improving efficiency. Once you focus more on redundant paths, having a bot doing it over and over again, that eliminates human error every now and then. There is definitely a huge ROI in that. Our main focus was low-hanging fruit. By low hanging fruit, I mean the redundant processes that users are just annoyed by when they go in every day and have to do it. There has definitely been a huge ROI because we are trying to free up a lot of the project managers for construction to do more focused stuff there rather than job cost details.

We have probably saved the time of 10 full-time employees. For daily tasks, we are saving an average of four hours per employee.

It is one of those things where you pay for convenience. Pricing-wise, UiPath is definitely way more expensive than other solutions that we have seen, especially since we also have Microsoft Power Automate, which is one of the latest tools. UiPath is on the higher end, but it is one of those decisions, "Is it worth the investment? How much are you getting as an ROI?" That is usually how the conversation goes.

Back then, the main competitor was Automation Anywhere, who wasn't necessarily as user-friendly. The main idea was that UiPath was more user-friendly with more forums. It seems like there was a community for it. Whereas, Automation Anywhere was a bit more complex. 

We are using a bunch of other tools to also see the differences. Everything runs so quickly that technology always needs to be up to speed. Companies, like UiPath, are always running so fast to compete in this area. We are also trying to see who is actually the best. UiPath has definitely shown us that, but it also comes with its price.

They are always trying to look for, as much as possible, in-house creation of back-end processes. This means less clicking and tapping on the keyboard for the robot, which is always better. UiPath definitely blends all that together, which is great. It is literally bridging all our platforms together, which is what I love about it.

With UiPath and RPA, the sky's the limit. There is potential for a bunch of things that you can do. When we started, as a construction company, we were thinking that RPA might not be as useful as we might think and make a bigger difference than our in-house solutions. When RPA came out, we thought it was mostly for companies like EY and PWC, e.g., more for financial auditing since there is so much data. However, we definitely benefit from it as a construction company. There is so much potential, whether it is low-hanging fruit or high complexity. It is definitely a win-win for any company, whatever industry you are working in.

I would rate UiPath as eight out of 10.

We have worked on multiple use cases, but most recently, we have worked on a payroll system. Previously, every month, we had to manually get certain details from HR, and we used to do the pay run for all employees in the organization. Now, we automatically extract the required information from the current system by using UiPath. We then prepare a sheet by using Excel, and the entire Excel sheet is processed by a bot. The final sheet is sent for the payslips for the entire organization, and the entire pay report is sent to the bank for payment details.

Automation reduces dependencies. When I have a process that is done by humans, there are dependencies. For example, I need to make sure that the required number of people are available in different shifts. Any process that is done by a human has to be split into eight to nine hours of work. After every eight hours, I have a replacement happening for the same work. So, multiple people are working in different shifts. In addition, any work through humans can only be done from Monday to Friday, or I have to get the team over the weekend. Making our team work over the weekend requires special permissions or approvals. With automation, I am at ease. I'm not dependent on anybody. UiPath is easily accessible from mobiles for the orchestration part. So, if I have a critical process that I need to execute and get the results, I can do it from my mobile. Even when I'm traveling, I can get real-time statistics. 

Previously, I used to get a request at any time to do the pay run for an employee. If the employee was on a leave on that particular day or was not available, I used to miss my target or deadline. Now, we are not dependent on anybody. We are completely independent. If I get a request, the robot is automatically going to process it automatically. I don't even have to tell the robot to run a process after getting a request. All my rules and validations are taken care of by automation before the deadline. If I'm away from the office, my robot can automatically trigger a process on receiving a request. So, we are able to meet all the deadlines, targets, and standards set by the company within the given timeframe.

It has helped in minimizing our on-premises footprint. We work for multiple zones and across the globe. If I have a UiPath architecture, I can deploy it anywhere. Irrespective of the country or continent or zone, I'm able to use the same deployment or the same architecture at multiple locations. It has reduced my cost of infrastructure and maintenance. The cost of everything has come down. Previously, we used to have servers country-wise and continent-wise, but now, we don't need multiple servers and multiple teams to maintain them. I can do things from a single location with a limited set of resources.

The majority of our processes are in the unattended mode, but we do have certain processes in the attended mode where certain end-users provide me the real-time information. We have designed a process where we give a specific form to the user. When the form is filled by the user, a process is automatically triggered, and the robot starts processing. It gives real-time statuses and information to the end-user in terms of what we are doing, how are we doing the calculations, and how are they going to get the benefit by opting for certain features within our organization. I can run my processes in the attended and unattended mode. So, I'm able to trigger both modes of automation very easily.

I am able to keep my customer data integrated. With humans, a data leak can happen, but in the case of robotics, my data is very secure.

The way the processing happens is also very smooth. For example, if I'm on leave or on a break, and a customer calls at my help desk, I won't be able to respond. Now, we have chatbots or robots running throughout the day. When the executives are not there and anyone calls the customer support team, customers are able to get a resolution. They don't have to keep calling or wait. Automatically, the bot is able to respond to their queries and concerns. We have been able to reduce the response time. My customers are pretty much satisfied with it, and they don't have any complaints. Previously, the satisfaction level of the customers was not that great.

The best part of automation is that we can easily integrate multiple technologies within a single tool. I can do it at ease with all of my data flow. Automation is happening across the globe, not only in my organization. Every time we do automation, we feel that there is something overlapping in every process. If I automate a process for my organization and your organization, 50% of the things would be the same. I can very easily maintain common things in automation tools through common libraries or common components. For the remaining 50% of things, we use different technologies. We are integrating optical character recognition (OCR) technologies for document processing. We are also using multiple machine learning methodologies to do pattern matching. We are using artificial intelligence to give a response that is comparable to a human response. 

We use its AI functionality in our automation program. We get multiple requests, and they can be through telephone, emails, or documents. When a request comes through the telephone, the robot or automation is designed to convert that to text. When a request comes through a document, we are using AI features. The document might not have a proper structure, and a customer can give any set of data in any format. So, we have built a special template or format, and this AI is helping us to extract the document with the most accurate results possible. We are getting an accuracy of 95%. With this, dependency is also gone. A human has to properly go through a document. Then, we have to convert the data to the file and process it. With AI, irrespective of the size of the document, which can be 100 pages or 500 pages, we are able to exactly locate the data that we're looking for, and we are able to extract and then process it through automation. We are able to smoothly integrate multiple things within a single process.

Its AI functionality has enabled us to automate more processes. It takes a human 23 minutes to process a 500-page document. With AI features, it hardly takes 7 minutes to process the same document. There is a great reduction in the time taken to do the same task, which is a huge benefit. With AI, I can look for, find, and extract specific information in a particular document, and then I'm able to process the information at ease. I can have documents in different formats. For example, each insurance customer or service provider can have different formats. A human would have to scan through multiple pages to reach the conclusion that this is the right data. AI can easily process different formats, whereas a human being has to be trained for different formats. Humans might also understand something and forget something, but that's not the case with AI or automation tools. They always remember the instructions given to them, which has drastically helped us in making our processes more accurate.

It has contributed to end-to-end automation in our organization. End-to-end automation helps us in completing things in a shorter span of time and utilizing resources in a better way. Previously, for every step of a process, we used to have a different team. We had a separate team for the following:

• Requirement gathering
• Answering the queries for the customers
• Responding to the queries by the ticketing system
• Responding to emails
• Processing particular processes at the backend
• Supporting the infrastructure in real-time

Now, all these things are done by robotics. I only need a few people to maintain my infrastructure. 

We use the UiPath Apps feature, and it has definitely helped us. If there is something that is not available within our team, we can directly use all the apps and features given by UiPath. We don't have to dedicatedly set up a team to design that app. If I have to design a new app or a chatbot for my customers, I can easily integrate the UiPath Apps feature instead of recruiting people, training them, and expecting them to give me the output. UiPath provides help and documentation, and if I require any licenses or support, UiPath's team is always available to assist us.

The UiPath Apps feature has increased the number of automations that we can create. It reduces the time to create automations. We can easily create automation. For a small process, we're able to roll out one automated process every 21 days. We are able to roll out an automated and complex end-to-end process every three or five months to our customers. Previously, it used to take us at least six months to one year to roll out the new features or new functionality to customers, but now, the time has drastically come down. 

It speeds up or reduces the cost of digital transformation. Every time we automate, we are able to speed up automation. We are able to do more things, and more people are working on automation. By using new features that UiPath is bringing and the learnings from my past experience, we are able to automate very quickly. Four and a half years ago, a process used to take four months. Now, it only takes 25 days for me. They have added many features, and I don't have to sit and design those features. They are constantly providing new features in their quarterly releases, and I can simply make the best use of them and implement them in my process.

Previously, I needed people in different shifts, and every human being might not have the same speed or enthusiasm. Humans also need breaks. A robot works throughout the day, and it has a consistent processing speed, so we are able to process more and more. I can plan a target with my robot, and I am able to achieve that. If I'm adding new customers, I just have to integrate one or two more licenses, which is very easy. I can easily create or configure a new robot and start processing. With humans, I have to train them again and again, whereas with automation, once a process is ready, I can use it in multiple robots. I can use it for 25, 50, or 100 robots very easily. I can scale my process rate very fast.

Previously, we were able to process 5,000 customer requests in a month. By using automation, we are able to do the same amount of work within 10 days or even within a week. If we add more human resources, it increases the cost for my organization, whereas, with robotics, I can configure 10 robots or 100 robots. It doesn't increase the cost a lot for my organization, and I can process everything that I want. I don't have any backlog.

It has freed up the time of our employees. This additional time has enabled employees to focus on higher-value work. I am utilizing resources in a much better way, and I am able to give them the work that is interesting for them or is relevant to their growth. When people in my team started working, they found the job interesting. After working for more than two to three years on the same thing, they don't feel that they're doing something new or learning something new. By using automation for a lot of things, I am able to train my team on the new things or technology that they are interested in or want to work with. I am also able to give the work that they're looking for. It is bringing more satisfaction, not only from the customers' perspective but also from my team's perspective. I am able to keep the same resources in my organization for a longer period of time because they're very happy. They are not dissatisfied with the organization.

It has definitely reduced human error. Our accuracy is 99.2%. With humans, our accuracy was 96%, and by using robotics, we have brought the accuracy to 99.2%.

It has also reduced the costs of our automation operations. In the initial year, we saved 10% of the day-to-day operational cost that we had when we were doing things manually. In the second year, it was 30%, and it has increased in the subsequent years. So far, almost 60% turnaround in the business profit has been reported.

It has saved costs for our organization. Previously, for a process, I had to train, for example, 100 people and keep them in multiple shifts. I also had to give them multiple facilities to be a part of the organization, whereas with robotics, I only have to design the process once, and I can use it in any number of bots, such as 10, 25, or 50. It also helps in scaling at no extra cost.

By using automation, we need fewer people for support operations. If the customer queries are taken care of by chatbots, my data and patterns are being analyzed by using AI and ML, and the scanning of the documents is taken care of by OCR, I need very few people for support operations. I need only 10% of people for providing support around the clock.

We are using the entire automation process most commonly. We are also doing scheduling. Our processes are running on a fixed date, so we are also using schedulers or timers. 

We are also using AI technology. We have AI Fabric, and we are doing the entire extraction part of the document through UiPath, which is very helpful. We're able to do everything within this single tool, and we are not dependent on other tools. We don't have to license more tools from the market and go to multiple tools to do the same work. Within this single tool, we have every feature that we need for our organization. 

It is a very simple tool to work with for anybody. Simplicity is the best in UiPath. It also has the best community support. If we are looking for any solution, we can directly reach out to UiPath at any point in time. 

The new features or functionalities that come with UiPath upgrades don't work perfectly in the initial days. Their new releases are not stable. We always find some set of issues. I have to work with the UiPath team for a week or so to resolve the issues, and then I'm able to use it. The stabilization should be there. We expect UiPath to reduce the number of errors before rolling out new features to end-users or customers.

In addition, many times, the apps or activities that we use within UiPath for designing are no longer compatible when a new upgrade happens or the version is changed. We want UiPath to look into it.

I have been using UiPath for almost four and a half years. 

It is one of the very stable tools. We don't see any breakdowns happening within the tool. 

We only have to design the process once, and we can use it in any number of bots. It helps in scaling at no extra cost. After we design a process, we can reuse it in subsequent designs. I just have to work on the things that are not already designed. So, there is a 10% to 30% reduction in the new processes that we design. Scalability improves with each and every design.

There is a user base of 100,000 users who are benefiting from automation at the moment. With manual processing, if I had a team of 1,000 people, then with automation, I would need 50 people to automate all processes. I would have four to five solution consultants or solution architects and around 15 to 20 developers and testers. There would also be people who are doing the business implementation, giving guidance to the customers, and doing the production rollout and handover preparation for the customers. 

Our usage is increasing. With every new process that we design, we are able to integrate more and more. Previously, we only used to integrate with OCR, and now, we are also using chatbots, AI, and ML. So, our processes are increasing, and we are definitely expanding.

The support that we get from UiPath is one of the best. We are a direct channel partner for the product. Every time UiPath comes up with new features or functionalities, they come and demonstrate that feature and help us to understand them so that we can help our customers with their implementations. We get direct support and the licensing, pricing, and certification benefits from UiPath.

It was pretty straightforward for us. We were able to build the entire infrastructure within a week. This includes getting licenses, doing the installation, and configuring the robots. We found the UiPath documentation very helpful while doing the installation and configuration. 

If I design a process today, I can deploy a process to production within 30 minutes of time. It is very quick. In terms of the implementation strategy, we go to the customer and understand their pain points. We then identify the processes that can be automated and tell them about the benefits and the timeframe for implementing a particular process to their server. We also tell them when will they start seeing the result and how they can achieve what they need by using multiple integrations of the tool. They don't have to spend multiple licenses on different tools. Everything can be done within a single tool.

We use a tool called TFS. With a single click, I can deploy my process from development to QA. In the same way, I can move my process from QA to UAT, and then with one more click, I can move it from UAT to production.

As solution architects, our role is to help the design team understand the design that has to be built. They take care of the design and testing. For the production rollout, we have an infrastructure team. We also sit with the business team to make them understand the process, how robotics works on a day-to-day basis, and what are the things that they have to monitor. Whenever we design a process, we make sure that all the complexities are handled. We are also handling all the compliance, and the integration is done smoothly. After a process is designed and approved by our business team, our accuracy stands at 99%.

In terms of maintenance, it doesn't require expensive or complex application upgrades or IT application support. UiPath is pretty simple. The basic infrastructure works in most of the servers, and we don't need frequent upgrades and maintenance. It is very easy to maintain.

We have seen an ROI. In the initial year, we saved 10% of the day-to-day operational cost. In the second year, it was 30%, and it has increased in the subsequent years. So far, almost 60% increase in the business profit has been reported.

There is no additional cost apart from the standard licensing. There is a one-time cost for the infrastructure setup.

We did evaluate multiple RPA tools such as Automation Anywhere and Blue Prism. In terms of the ease of designing, the ease of use, and from the cost perspective, we found UiPath to be the best tool for our customers.

Anyone who wants to automate processes should understand the process, its complexity, and the volume of the processing or the number of transactions to be processed. You should do proper analysis before you select the tool and licenses.

UiPath provides a lot of benefits and reduces the cost for an organization. It is one of the best tools in the market. The support that we get from UiPath is one of the best, and most of the features provided by UiPath are simply amazing.

Initially, people are hesitant to use automation because they don't know what automation can do. Anybody who uses the technology in the right way will get lots of benefits from any technology. Your implementation strategy has to be proper. You should check the feasibility of using a particular technology with existing processes in the organization and the benefits you can get.

It helps us in reducing the time, and we are also able to bring more business to the company. By making my processes digital, I'm bringing more revenue to my company. We visit a customer's site and try to find out the processes and pain points. After that, we analyze the entire solution within UiPath and tell the customer about the best solution and what would be the reduction in time as compared to the normal process.

I would rate UiPath a nine out of 10.

We have a lot of use cases for UiPath including automation of processes and reconciliation.

Building automation using UiPath is easy.

It helps our operational efficiency by saving time and reducing costs. Manually processes that take an hour can be done in five minutes using UiPath.

The most beneficial feature of UiPath for our workflows is the seamless database connectivity.

UiPath facilitates end-to-end automation for well-defined processes. This eliminates interruptions caused by manual steps within the workflow.

The UiPath User Community is large. There is a lot of interaction and sharing making it easy for us to find answers to any issues we may have.

The biggest benefits we have seen using UiPath are the cost and time savings.

It has helped save around ten percent of costs.

The UiPath Academy courses are great. They have a lot of helpful courses.

UiPath has reduced human error by 70 percent.

UiPath excels at integrating with a wide variety of systems, including on-premises systems, legacy systems, and web pages.

The high cost of UiPath licensing significantly reduces the value we get from the solution. A large portion of the cost savings we achieve are negated by the licensing fees.

I have been using UiPath for four years.

I would rate the stability of Uipath eight out of ten.

I would rate the scalability of Uipath eight out of ten.

The technical support is great with the premium service for enterprise-level clients.

Positive

I'm certified in Automation Anywhere and currently use Microsoft Power Automate. However, UiPath seems better suited for enterprise-level automation. Unlike Power Automate, UiPath is system-agnostic. It can connect to any system, regardless of platform, making it highly versatile. On the other hand, Microsoft Power Automate prioritizes integration with other Microsoft products. Connecting legacy systems with Power Automate often requires purchasing premium connectors and potentially hiring an expert for configuration.

The deployment took around two weeks to complete.

We engaged Deloitte as our consulting firm for the UiPath implementation. While we handled a significant portion of the on-premises work ourselves, their team provided some technical assistance. Overall, I would rate their services a six out of ten.

UiPath promises a 50 percent reduction in operational costs, but the high licensing fees may consume most of those savings.

I would rate the cost of UiPath eight out of ten with ten being the most expensive.

I would rate UiPath eight out of ten.

We have around 15 users that work with UiPath for the attended bots.

UiPath Orchestrator requires regular maintenance and updates.

I recommend UiPath. The only negative area of UiPath is the licensing fees. 

I am a consultant working on RPA solutions in general. UiPath is one of the solutions that I am using.

The use cases depend on the clients. I have done automation of sending mail with invoices in it. We have used it for analyzing PDF documents, getting information out of these documents, preparing in three different languages depending on the client, and sending invoices by email.

We are also checking VAT numbers on the EU side to validate the client's VAT numbers and related data. We have automated the generation of reports out of SAP for two different managers and teams. We have also automated including specific signature images within PDF documents and sending them to the related service or email address.

We have mainly used UiPath to focus on processes related to the finance department. The targeted processes are the ones that are the most repeatable and require a lot of effort but there is no real focus and attention from the user. Because of its repeatable nature, the risk is that users do not pay attention to the process itself and make mistakes.

Generally, we do not implement end-to-end automation. The idea is not to automate an end-to-end process but to automate a part of the process that takes a lot of time and resources. That is the focus point, so it is not a matter of having an end-to-end process implemented. It may occur, but often, it is a part of the process where the focus needs to be reliability or time and resource consumption.

The benefit for our clients is time and reliability. They quite often see the benefits in terms of the reliability of executing the process, even reporting mistakes or errors that happen during the execution of the process. That is something quite valuable for them.

Usually, it takes our clients at least one month to realize the benefits. If the processes are executed on a daily basis, then it is quite fast, but there are processes that are triggered every month or every quarter. In that case, it will take at least a month or a quarter to see the benefits. Once it is executed, there is quite an immediate benefit. On the other hand, it takes time to analyze the process because often processes or procedures that are written are not in sync with what is executed by the user. We have to modify them. Often, by questioning the end user, you end up finding the shortcuts and implementing them, so the analysis takes more time, and the implementation takes less time.

UiPath reduces human error. That is one of the main reasons why automation is done for customers. Two main reasons for automation are reliability and resource availability. 

UiPath saves time for our customers, but it is hard to know how much time it has saved because it varies from process to process. For example, the process of validating the VAT numbers on the EU website used to take two or three resources every quarter, whereas now, it is reduced to less than half an hour. These time savings are valuable, but the added value is reliability.

UiPath has not had a lot of impact on the digital transformation because the processes that are requested to be automated are already digital. The reason for automation is to speed up the process or make it more reliable. There is no real impact on the digitization of processes.

In terms of the reduction in the on-premises footprint, I am not always aware of the eventual use of the processes that I am implementing for the clients with the bots. I see that some of the bots are not used anymore because they have their own application that includes a big part of what has been automated on their side. It depends on the way they use it and how often they use it because I have bots that are running every day, and I also have bots that are running once a quarter. The ones that are running every quarter are harder to evaluate because people are not always able to see the resources released from executing those processes. Because they are executed every quarter, they are usually not measured. Our clients generally go for automation for reliability.

Specifically in the recent versions, the ability to change the interface is valuable. One of my clients had to upgrade the SAP version and move to a web-based UI. This was handled by isolating the UI interaction within the library for the targeted SAP on the client side. I upgraded that library to handle the web-based, and the bots worked fine after that without modifying anything in them. The usage of libraries is very important for me because it helps a lot in this kind of upgrade, specifically because SAP is used across the company. It is impacting a lot of different businesses within the company.

It is quite intuitive and fully handled by a visual interface. It is no big deal for me. I have been a developer in the past, and I have used Visual Basic and C#. If I need to specify something exceptional, it can be done. It is not a big deal. For me, it is very easy. There is a competitor with an open-source solution called OpenRPA, but for me, UiPath is far better and more intuitive.

There should be the ability to customize the building blocks instead of having to specify everything in every step. We should be able to combine these building blocks to make specific processes faster.

There should also be some kind of templates, similar to Power Automate. Power Automate provides templates for a specific context.

I have been using UiPath for two and a half years.

I am absolutely satisfied with its stability.

I did not have to worry about it so much because usually, my clients want to take control of their bots. They want to execute it when they want, so I have had no experience with the scalability of UiPath. 

I have not contacted their support. When I am developing, I try to make a bot quite stable. I am aware of what is happening and what it is doing, and I can notify people with logs or names of different events that are occurring during the process execution. I know exactly what is happening and where. It is quite easy and fast to diagnose and fix if there is an issue, but it is not often that I have to intervene in production. If a process is designed correctly and safely, not much intervention is required. Clients look for this kind of stability because that will save the time that they will have to spend fixing things in the production environment.

They have a UiPath Community, but I have not used it often. If there is something blocking, I go over there, but generally, I find the solution to the issues through my colleagues.

It has always been on-premises. The setup is quite straightforward. If there is some kind of Orchestrator to be installed, it is more difficult, and it takes more time. Usually, they want to have someone internally to handle the Orchestrator. I am more focused on the bots and the triggers for these bots to be executed. I am not that often involved in the implementation of the infrastructure of UiPath for the operational side.

Bot development duration varies. It depends on the process, but it can take a few weeks to several months. I have bots that were developed in two or three weeks, and I also have bots that took at least six months because they were quite heavy and complex. Generally, it does not take longer than that because then it will not be as valuable to the clients. If it takes more than six months, it is better to have it developed in their own software.

Bot deployment is quite straightforward for most of my clients because, during development time, I take care of environment parameters. So, deployment is quite straightforward. It is a matter of deploying and pressing a button to have the package deployed. We then set parameters in config files, but it does not take a long time to have it deployed.

Bots usually do not require any maintenance, but if the source of data has been upgraded or modified or the UI has been modified, they might require some maintenance. Usually, once the process is running and every source is stable, there is no need for maintenance. When the data source changes or the infrastructure changes, such as the main server being moved or renamed, then there is a risk over there, but it is not a big deal to adapt.

Generally, two or three people might have to investigate the cause of the issue. If the issue is inside the bot, it is not a problem. One person is enough. If it is related to external data sources or infrastructure, it may take two or three people depending on the segmentation of the clients' people in their departments and services.

I do not know about the exact price because I am not selling anything. I propose several solutions to the clients, and the client does choose one of them. If UiPath is chosen, they contact the official reseller in the country. In one case, I had the prices in front of me, and it was not expensive for the service it was providing.

I would recommend it depending on the needs. UiPath can do a lot of things, and I have covered only 20% of UiPath functionality. Based on my experience and the needs that I had so far, UiPath has been quite valuable.

I would advise defining your use cases. That is the rule for everything. Once you have the use cases analyzed, you can specify what is needed, how you would do it, and what is the best solution to have it implemented. One thing that I am doing is that I am mixing solutions, where, for example, UiPath interacts with Python processes that I have developed. Python processes provide information in files. Web scraping is not difficult in UiPath, but it is quite heavy. In Python, it is faster to develop and use than with UiPath. It also depends on the number of iterations and resources available to execute it. It is a matter of the quality of a particular functionality in UiPath. UiPath relies on the .Net framework, and it has its own limitations. It has quite a heavy set of libraries and frameworks. It is a matter of balancing what you are expecting of it.

I would rate UiPath an eight out of ten. It is a good product. It is well-designed and well-executed.

I find the solution easier to use than other platforms and it's a user-friendly way to automate.

I work with Excel files, and I find it helps make it easier to work with the files.

The ease of building automation is okay. I just use the community version, however, I have found it's much better than others. Their community version is more user-friendly than many options. I really appreciate the useability of document processing. I mostly use the solution for document processing and invoice comparisons. It's simple. 

I've used the user community and have been in touch with one person who was very helpful. They've helped guide me. I've gotten positive responses and good answers. It's helped me learn how to do comparisons between two Excel files, for example. 

I've enrolled in UiPath Academy courses. I've also enrolled in Coursera courses. I'm still in the learning process. They have good tutorials.

I've used some of the AI processes. It is very efficient to use the AI functionality. We've gotten very good responses and results so far. We have found the responses we're getting are good. It helps with creating more efficiencies. 

It has helped speed up digital transformation. 

UiPath has helped to reduce human error. We're able to build effective automation. We're creating software boards where the bot will do what we say and pull what we are trying to pull.

The solution does help us save time.

I'm still learning the solution; it has yet to help me save money.

I'm not sure how UiPath is at data scanning. I need to look into this further.

They need to work on security.

I have used the solution for about one month.

I haven't faced any stability difficulties, at least on the community version. 

I've never contacted technical support.

I've used Power Automate and ElectroNeek. I found there were a lot of issues with ElectroNeek and Power Automate. For example, they are not good with ChatGPT or data scraping. They are also not as user-friendly.

The solution was very easy to set up.

The implementation took only ten to 15 minutes. It was my first attempt to set it up. Aside from an internet issue, I had no problems. 

I handled the initial setup myself. 

I don't have any insights into the pricing of the solution. I'm using the community version. If I like it, I will buy the paid version.

I'm an RPA developer who started working with the solution. I recently worked with Power Automate. I'm familiar with the UiPath community version. I'm not extremely familiar with UiPath as I haven't used it for very long.

I'd rate the solution nine out of ten - at least, for the community version. 

We use it for various purposes like account management, finance, HR, and procurement.

We can complete all tasks within a single, unified platform. Whether it's documentation or deliveries, there's no need for multiple tools—it's all streamlined and straightforward. There's been a decrease in human errors which means we can skip the manual revalidation process. It's remarkably efficient, freeing up more than fifty percent of employees' time.

The standout features are data scraping and data analysis. It enables us to implement automation seamlessly from start to finish. It is user-friendly and significantly speeds up the development process.

The primary concern revolves around the high costs of licensing. It would be beneficial for them to develop plans or packages, especially for countries where people are more budget-conscious. Adjusting the pricing strategy could make the platform more accessible to a broader audience. It would be beneficial if there were options to extend the data storage period, coupled with dashboard views and analytic features for a more comprehensive and streamlined experience.

I have been working with it for seven years.

I would rate its stability capabilities eight out of ten.

Scalability is a strong suit; it can effortlessly expand its capacity and functionality to meet specific needs.

Support is somewhat dependent on the presence of a distributor in our region. Dealing with issues often involves going through video communication numerous times. The current setup, due to security reasons, makes troubleshooting challenging without direct access. Having direct access to support through the account holder would make things more convenient. I would rate it four out of ten.

Neutral

We utilized Automation Anywhere, Blue Prism, and similar options before settling on UiPath. Initially, the prices were acceptable, but lately, they've hiked up.

The initial setup might seem complex at first, but once you get used to it, it becomes more manageable and straightforward.

The deployment time varies, usually taking half a day to two or three hours, contingent on the infrastructure. Maintenance typically requires only one person.

It is quite an expensive solution.

We transitioned from WorkFusion to UiPath due to the superior functionalities offered by UiPath.

It's crucial to evaluate not only the technological aspects but also the pricing structure when choosing a platform. Overall, I would rate it eight out of ten.