UiPath Reviews

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.

Some of our use cases for UiPath range all the way from development to operational support through to business enablement. Our biggest focus internally is to enable a business to do what they do best. We generally provide solutions through the use of UiPath to cater for streams, e.g., Procure-to-Pay, Hire to Retire, and quote-to-cash.

We are using it to build solutions that can heal themselves. So, we make sure that our operational team is aware as soon as something fails with the processes that we have built. If one of the use cases or failures has already been listed, we note the fix and try to implement that. If that doesn't work, then we hand it off to a human to look at the task. 

In terms of some of the use cases that we have in the business, we do quite a lot of ERP automation. So, we work with SAP quite a lot. We also have a lot of back-end data that we need to bring in and process as well. So, we use our SQL databases to perform tasks, e.g., allocating payments to bank accounts in our ERP system.

Because our development team is rather small, we try to create as many reusable components and solutions on the UiPath platform to make our day-to-day jobs a lot easier.

What has helped us the most from UiPath is that they haven't just provided us with a toolset or range of products, but actually provided us with a framework and hyperautomation lifecycle that we could use as a guideline throughout our own journey in automation.

UiPath has definitely assisted us in speeding up our digital transformation journey. We have been able to create a whole bunch of different components that we reuse throughout our solutions. This means that when we have great, new ideas that we want to implement into our solutions, we have now found ways to do it in such a way that we spend less time trying to implement the fixes or cool new enhancements and more time actually realizing the value. In doing so, we have also seen a reduction in cost and an increase in FTE savings.

From a development point of view, one of the most important, useful features in the deck is definitely some of the offerings that UiPath has in terms of UiPath Studio. Having the components for the Object Repository and Data Service available make your solution reusable and decrease your development time so you can go to market more quickly for products that you are offering clients. That has been really useful in our landscape. 

UiPath has gone a very long way to make sure their tools are easy to use and the products that they have in their end-to-end hyper automation lifecycle are easy to learn and teachable to people that you work with.

UiPath has a wide range of features that they have brought into their ecosystem. If I look at something quite specific that we would like to see going forward, that would be the integration between Data Service and Insights. It is great that we are able to visualize our return on investments using Insights. We can see a whole bunch of metrics and how our processes are performing. I think what would give us a lot more power is if we could link that to Data Service and actually pull through some custom information.

We have been using UiPath at the company internally for roughly just over five years. 

We have been a reseller of the UiPath product to our clients for roughly three years.

UiPath solutions are definitely very stable. It is very easy for us to build quality solutions and put them into production, then be able to trust the solution that we have put into production. For any automation center of excellence, that is quite important. You need to have a level of trust in your organization, inside of your environment and inside of your solutions. 

This also is attributed to the quality of our developers. We have strong, skilled developers. Without a product like UiPath, stability would not be such a great factor, especially if we had to go with a different approach or tool sets.

We have had a lot of experience trying to scale our solutions. Because of our automation journey, when we started out, we created processes that were very specific to the problems that we were trying to solve. They were actually quite static. The processes that we developed were aimed at addressing a problem specifically. As time went on, we started changing our design-thinking approach and our approach to designing and developing solutions, in such a fashion that we now try to create our solutions to be more dynamic. 

Because of the life expectancy of automations, and specifically RPA, a lot of experts would say that you need to go back after 6,12, or 18 months to reevaluate your solution and see if it needs to be redeveloped. What we have seen in our landscape is that if we try to make our solutions more dynamic, and actually cater for more than what we set out to cater for, having to enhance our solution later on takes a lot less development time. So, scaling out the solution has become immensely useful and our way of work.

We have roughly about 100 people within our organization directly communicating with our UiPath environment, either through our robotic assistance or bots, right down to the granular level of developing solutions. Some of the roles include our developers, operational support, and business users.

I would definitely say that the UiPath technical support is quite proficient. They help us quite quickly. Their responses always direct us to the answers that we are looking for. If they don't know the answer or can't assist us, they give us that feedback. They go ahead and find the answers or make the needed changes. They then come back to us and provide feedback. 

We have really enjoyed working with the UiPath team quite closely throughout our partnership. It has enabled our journey further. I would definitely rate them as 10 out of 10.

Positive

If I look at some of the other technologies and tool stacks that we have used to do RPA or automation, the adoption rate is a lot less. This is because of the way that developers need to struggle in some cases to get through the learning and usage of these tools.

I was not directly involved in the setup of the applications and ecosystem. From what I have been able to gather, we did have quite a lot of support from UiPath and the setup was quite straightforward. It took four hours maximum.

UiPath has definitely helped us realize some of our full-time equivalent savings (FTE savings) in regards to some of the reusable components that we have and have placed specifically in the business. With the offerings that UiPath has, we are able to easily see what our return on investment is, how we have structured and deployed our solutions, what we have deployed, how long it has been deployed, etc.

If we take a look at the last six months, we have about 105 processes that we have in production at the moment. If we single out a specific process that we have been working on and has been in production for quite a while, then measure that over the last six months, we can see that we have saved roughly about 380 hours on that process. Or, we have saved 380 FTE hours. That equates to roughly 77,000 rand. That has been quite a big savings. If you take the time saved across our 100-plus processes, we are looking at close to 2,100 hours that we have saved in the last six months. That has a financial value of between 500,000 and a million rand. 

UiPath definitely has reduced human error for us. Because a lot of our processes are quite focused within the financial space and we integrate it with our ERP systems, we have seen a reduction of human error come into play. We have also seen that the provisions made for human error have also been reduced.

In the RPA industry at the moment and in automation in general, UiPath's pricing model is the most consistent. So, if you are looking at year-on-year growth and pricing, or even if you are comparing solutions, each vendor has their own take on how they are going to generate profits and expand their return on investment. By far, UiPath is the most consistent with their pricing. They make it quite clear what they set out to achieve with their pricing and product. That makes their product so much easier to design for, as you don't need to change your pricing and go back to clients every time that you introduce a new aspect into the solution.

If I did have any advice or extra information that I could give surrounding the UiPath product, one of its strengths is that you know upfront what everything will cost.

We found that UiPath Academy courses that they provide, as well as the help through the forum, have greatly enabled us to more easily use this platform. Compared to other vendors and other tool stacks, it is a lot easier to use as well. 

If I look at the UiPath offering and compare it to Microsoft Power Platform, and while Microsoft Power Automate has definitely come a long way and done a great job of making its way into the market, there are still key differences between the two platforms. Because Power Platform is still relatively new, the resources and support are a little bit more tedious to get around than with UiPath. With the UiPath community, because of their extensive work that they have done within the community to build developers, you get a lot more support on forums. 

In terms of usability of the platforms, UiPath has been doing this for a lot longer. So, the user interfaces and all around user-friendliness of their platform definitely show, in the time that they have spent working on the product. 

If I look at some of the things that Power Automate offered before the latest updates in the UiPath offering, Power Automate was able to allow you to trigger processes completely differently to the way that UiPath does. UiPath has since taken a step up and released their integration services, which has helped bridge that gap quite a lot. Being able to link to a process is a lot easier than it used to be.

If I compare scalability, development time, and ease of use of Power Platform to UiPath, specifically around the RPA components of the solutions, there is definitely a noticeable difference. 

As an organization, we took Blue Prism, WorkFusion, Automation Anywhere, and those types of vendors and platforms into consideration when selecting our platform of choice when our center of excellence was formed. When making the decision at that time, the stakeholders involved decided to go with UiPath, mostly because of what they had to offer and their consistency.

The advice that I have to customers who are looking to start off their automation journey, or essentially take on a new vendor like UiPath, I would definitely say one of the challenges for us was getting our governance and standards right. As soon as we got that right, and we fixed our design-thinking approach, we realized how we could make sure our solutions were scalable. We then started seeing a higher return on investment. My advice would be to focus on the small things, make sure that you understand your processes and what goals you are trying to achieve, and then start with the beginning and end in mind. So, know where you want to end up and see how you are going to break your solution up into phases to be able to get there.

UiPath has had a very interesting impact on our environment. We have found it quite difficult to find RPA developers within our country, specifically those who have the skills that we need and can do what we do. So, we have had to rely on upskilling people as much as we possibly can to be able to deliver the solutions that we are delivering. In doing so, UiPath Academy has been quite helpful and handy, specifically because it is a lot easier to onboard a new employee or somebody who has less experience with UiPath. The training is free and easily available. If there are any issues or questions, the Academy team and the community are always around to support and answer any questions. 

What is quite impressive about UiPath is that they followed the same trend of having two major releases a year. I think those are the two most anticipated events that we have within our team as well. Because we have a roadmap, we know more or less what UiPath is planning and hoping to do. Our partnership enables us to have a closer view at that information. UiPath Insider Program allows us to see some of the previewed items as well. 

For those who aren't quite sure where they want to go just yet, keep an eye on the forums, blog posts, and UiPath in general. Look at their major releases before making any huge decisions. UiPath has a track record of consistency, and they have got some great reviews and implementations that I think we could really all learn from.

I would rate the UiPath platform as 10 out of 10.

We have two use cases.

One is for our claim accessing process, for which I have developed a process for logging into the client's application. It includes launching the browser and getting logged into the application by entering the username and password and handling two-step verification. Handling that requires some logic. Once logged in, it navigates to the claim status feed and selects the organization's and payer's details. It then enters the required details of the patients. These details are given by the client in an Excel document that the process reads. It searches for the values, one-by-one. If there is no record for the patient whose details are entered, it will throw an error stating that there are no claims present. It captures such exceptions and records them in a separate Excel file.

If that person's claim is present, it fetches 25 to 35 key details from that record and they are written to an Excel document. Once the process is done, the Excels will be sent as email attachments to the client.

The second process that I am currently developing is one where I need to get the data from Google Sheets. This process involves four or five practice management systems. It has to log into each practice management system and, for each one, it needs to schedule appointments based on the data present in the Google Sheet. The process involves navigating to the respective screens, filtering the details, and entering them in a CSV file. Based on that file, we have all the data related to patients' records. The process checks the patients' payment records. There are exception-handling routines and any errors are noted in an Excel sheet. Once all the patients' records have been completed, it closes the application and sends the data to the respective clients. It produces a log file in Excel as an attachment, as well.

Automation has definitely saved us time and money. For example, for data entry, if a person takes around eight hours per day to complete and upload about 200 sets of data, a bot can easily upload around 3,000 to 4,000 sets per day. It reduces the amount of time to get data uploaded. If a person uploads one record in three minutes, the bot can upload the same data in about 30 to 40 seconds. The bot provides much greater time- and cost-efficiency. It speeds up digital transformation.

It has also reduced human error. Among those 200 records that a person can upload per day, mistakes may happen in 10 to 15 records. Bots don't do things incorrectly at any point in time. Values are entered correctly in each field.

As a result, it frees up employee time. If a bot runs for eight hours, a person only has to look at it for a little while, because a bot will definitely do the process perfectly. That means we don't need a human to dedicate much time watching something run end-to-end. If the bot does the process properly for four records, it will definitely do the next 4000 records correctly as well. So there is not much time required of a human to watch the bot.

On the basis of costs in India, where I work, if a person earns 30,000 per month, the cost of the process they work on is 360,000 per year. A bot for the same process may cost 150,000 or 200,000 only. Automating is more cost-efficient than hiring a person to work on the process.

Among the most valuable features is the ability to read Excel and Word documents with API calls.

In the Google platform, I need to generate security-related things like an API key and an API secure code. That enables me to get the data into UiPath. The product is built such that only if all the security requirements are properly done am I able to get the required data.

UiPath is also the best tool for a beginner or someone who has no knowledge of programming. It is easy to learn quickly and to understand. You can get working in it much more quickly than if you had to acquire a programming background.

I would rate the ease of building an automation at 3.8 out of five, as I have only been working in UiPath for the past 11 months. I am now able to understand everything and can design the kinds of processes I need to build. There are many courses available on their website in the UiPath Academy where they completely show you how to do things. Within a short period of time—I spent the first three months in the UiPath Academy—I was able to understand things clearly, including descriptions of the Properties panels and every field. I understand the uses of these Properties.

Also, many of the Activities are pre-built, but if any activities or logical processes are not available, I can get them through third-party packages that are in the UiPath Marketplace. I am able to build automations quickly. In the worst-case scenario, if it's a large project, I can develop that project within two months.

I have used the AI functionality for PDF automations. In these processes, the bot is able to capture the data properly about 70 to 80 percent of the time. But if a document is not proper or it isn't handled the right way, the bot struggles to get the required data. UiPath has to work on this aspect so that the bot will be able to completely capture the data.

There is also room for improvement in the area of third-party integrations. In the last week I have gone through a video for an integration service, but it did not show things end-to-end. Rather, they just explained the connection details only. After performing the steps they showed, I was not able to get things working properly in my process.

I have been using UiPath for around 11 months.

The stability of UiPath is quite good. In some particular areas, the bot struggles a bit and we have to implement Human in the Loop. Those cases are where the bot can't do certain validations. But overall, the solution is stable and accurate in the results.

The scalability is a four out of five. 

At a certain point, we needed support from UiPath. The solution can be integrated with ABBYY. Getting an AABBYY license doesn't happen just like that. You need to get a trial license and it's a long process. We needed support from the UiPath team to get it done.

You can try to get a solution from the UiPath forum or from the documentation sections, but the UiPath support is the best. I have raised three or four support tickets over the year and they have helped me through each issue, completely, to the end. They respond within 24 hours. When you explain your issue to them, they create a step-by-step process to sort it out. And once I solved the issues, they inspected what I had done.

Positive

I used Microsoft Power Automate. I switched because Power Automate is not very user-friendly when compared with UiPath. And when it comes to integrations in the Microsoft product, most of the connectors are still in the preview state. In UiPath, all the integrations are active and enable you to get the desired result. Also, the Microsoft community does not have many active people handling it. With the UiPath community, you get an immediate response for any issue you have posted.

I use the UiPath forums if I have an issue and I'm unable to find a solution or develop my process. If I post it on the forum, in a maximum of two minutes I'll get an email response from other UiPath users, as well as from senior users who may have two or three years' experience. They politely answer my issues. I have also provided solutions to questions in the forum over the past two months. UiPath's user community is absolutely the best one.

The initial setup is completely easy and straightforward. It is just like installing software in a system by clicking "next, next, next." At the end of it, you have Studio in your system. 

If you need to allocate a particular system to Orchestrator, even that is a very simple process and there are videos available on the internet that show you how to set up the process quickly.

Instead of giving a monthly salary to a person, you can get a bot on a yearly basis. It is cost-efficient and will save you money. You'll also get a more accurate and stable result than if you had a human work on it.

Pricing is based on your process. If your process is fairly simple, it will not cost much.

UiPath has enabled me to build automations much more quickly when compared to other tools. If you go with Blue Prism or Automation Anywhere, you need to have some programming language skills to implement things. But UiPath is completely drag-and-drop.

I looked online at which is the best tool. I looked at many details, what each product provides, and decided that UiPath is a better solution as an automation tool.

Overall, UiPath has the best user community and the best, detailed videos. It is easy to understand, there is no coding at all, and even a beginner can create a process in a short period of time. It is also easily integratable. These are the points where it stands out against any other tools.

For us, in some use cases, end-to-end automation means a need for Human in the Loop. There are certain points where the bot is not able to validate things and a human is needed to verify whether the bot has done things properly or not. But bots are able to process 90 percent of an end-to-end process. For monitoring, UiPath has Orchestrator. If any error occurs, the data is immediately updated in Orchestrator and you can easily see the error and the cause, and you can easily resolve it.

In the UiPath Academy, UiPath offers the best content for each module and, after each video, there is a quiz so that we can show we have understood what we have learned from the video. There are also activities and a practice session where we can implement the use cases by practicing them in Studio. If we are stuck at any point after the practice, they have a solution area where they explain the steps you need to implement in Studio to get the desired results. They give sample workflows as well. I don't think any other software tool does this. They even provide detailed, step-by-step videos for third-party integrations.

We use Orchestrator, Studio, and Robot to work with automation in our finance department.

The product improves how our organization functions by automating tasks so users aren't having to spend time doing mundane things.

The most valuable feature is the unattended robots as they completely take tasks out of the user's hands.

In the next release of the solution, I'd like to see process mining to analyze business processes through event logs. It would help the end-users determine what processes need to or can be automated.

As for areas of the solution that have room for improvement, the usability for the end-users could improve so that they will be better able to program on their own. Coupled with process mining capabilities, that could remove the need to involve programmers or IT in the automation of simple tasks. The cloud platform could be improved so we would be able to deploy through that with sufficient security.

On a scale from one to five where one is not stable and five is very stable, I would rate the stability of the platform as a four. It is a four because I haven't seen any outages yet but we may need more experience with the product to be sure it is totally stable when we are completely live.

We have about four people are in our organization who are currently involved in our automation program and I can see that expanding as the company improves ease-of-use.

Our team has used UiPath Academy RPA training. On a scale from one to five where one is the least beneficial and five is the most beneficial, I would rate the UiPath Academy RPA training as a five. It is very good and very detailed.

We have also used customer support and it is good. When I called in they were helpful with answering questions that I had and they responded quickly. Usually, we had one person assigned to us that kind of helped us implement and who was familiar with our needs. This helped in several cases.

I was involved in the decision process to move to UiPath. We knew that we needed an RPA solution to take care of repetitive tasks that could be automated and we had been using solutions in other departments. We went through an RFP (Request for Proposal) process when the finance senior leadership wanted to see what RPA was about and how it could help in their processing. UiPath was one of three products that made it to the next stage of evaluations for this use case.

We did simultaneously use a different solution, which was Pega. UiPath was actually already being used in the company but the idea was to expand into the finance processes.

The initial setup process was straightforward. The complexity that we met with was because of the requirements of our own company. The setup, as far as the installation, was straightforward and simple. From the time we purchased the UiPath license until we had our first robot in production was about three months.

We did use a consultant for the deployment. The company was PwC (PricewaterhouseCoopers International Limited). On a scale from one to five where one is very bad and five is excellent. I would rate our experience with PwC as a three. They are not rated higher in our case because they didn't provide us with the best resources. They sent a younger team that seemed not to have really ever used UiPath.

We have only projected a total for return on investment and performance benefits from the solution through testing and past performance as we are not fully live yet. It will probably take six months to see the actual ROI when we know more about the performance benefits of full deployment. The solution has already helped to eliminate human error by about 25% and has saved our organization approximately 2,000 hours.

As far as pricing, I don't know what the company spends on the license. I do know about the robots. I think the attended robot is a little bit too pricey. With the unattended robots, we can put them on virtual machines — not really Citrix but regular virtual machines which are a little bit cheaper.

The vendors who were on our shortlist were UiPath, Pega, Automation Anywhere and Blue Prism. We chose UiPath because we already had the product in-house and we had already gone through all the security checks for the company requirements.

On a scale from one to five where one is very difficult and five is very easy. I would rate the ease of use of the platform as a three-out-of-five. I give it that rating rather than going a bit higher because it is a little bit difficult for the regular users to automate. In some cases, you have to be more of a programmer to automate successfully. Even so, it is better than other RPA tools.

On a scale from one to ten where one is the worst and ten is the best, I would rate the product over-all as an eight. It gets the job done, but there is still a lot of room for growth in the capabilities so that is why I think that eight is a justifiable rating.

The advice I would give to a colleague at another company who is researching RPA solutions is to read up on what RPA is and what it can do for your company. That is where I would start. Then try to go to as many meetups or conferences as you can to find out more about the products and how they are being used.

I currently work for a data center company serving real estate clients. Our primary use case for UiPath involves large-scale automation using Document Understanding to process invoices. 

I have two models running. One is for our general invoices, including everything we pay for people coming on-site at all data centers worldwide. There's a separate model for utilities. Accuracy in our utilities spending is crucial for our data center business, where power costs are passed on to customers. 

Currently, we still use traditional machine learning from when we initially developed these models three years ago. However, we are creating a company strategy to implement GenAI and deal with the legal implications. GenAI is something we're considering as an enhancement to our document processing and data collection. We're still trying to figure out how that happened. We're figuring out which documents and data to include in an internal model and draw conclusions from. 

When working with data, our top priority is ensuring that the data is updated, accurate, and well-maintained. There's a structure involved because a ton of our information is in SharePoint, which is a mess. We have two SharePoint sites for every employee.

Some large-scale invoice-related tasks were overwhelming our existing processes and attempts to handle them manually. We are in the data center industry and dealing with all these technology companies, but many processes in the real estate business are a bit more outdated. Many of our people are comfortable working in Excel, and some teams are highly siloed.  One significant challenge I've faced as a UiPath developer is acting as an evangelist within the company.  We want to demonstrate the platform's capabilities and get buy-in from these different teams across the enterprise to raise the level of what we're trying to do. 

UiPath has been helpful with that first step of getting the information off the invoice. I've been learning and expanding my skill set on the workflow side. Many of our automations have a workflow with a human in the loop doing manual review. I look forward to automating between different departments, and that's one thing I want to develop at this conference.

We used to bring on seasonal contractors during peak seasons, and now we no longer need to do that because the existing staff have more capability. That was a big thing when we started. Our accounting team was so busy for the two weeks before and the one week after closing. There was a tiny window when they could engage with any process improvement or look ahead at what we could change because they were so busy keeping up with how things work. We've freed up these people who are intimately familiar with our business and give them more time to apply that knowledge instead of filling out forms. 

We were processing about 2,000 invoices a month when I started. Now we're up to about three thousand. It took about 15 minutes per invoice to process because there were so many different elements. Working with Yardi is challenging. There was a big issue with getting these into Yardi and uploading them in batches. If one invoice in the batch failed, it would kick them all out. We spent all this extra effort troubleshooting and doing all of this. 

Now, the bot can execute this work and upload them individually. If there's a single error, it can be isolated and kicked out as an exception. Someone can manually review it, and the bot can keep putting the rest of the invoices into the system. We've also had a great ROI on the monthly reporting. We generated reports from around 50 sites every week and then distributed them to a long list of different people on different projects. It's straightforward to do and only requires 10 clicks for each report, but it saves massive amounts of time for people. Now, all I need to do is maintain a list of who should get the emails and what projects need reports to run. 

I love developing automations. I often directly help people by improving the part of their job that is time-consuming and dull. In addition to saving time, we reduce errors caused by manually typing things in. I've demonstrated that in different departments at our company.

We won an award for our ESG efforts. I developed an automation to help us report our ESG metrics because all of these customers want reports to give their shareholders about green initiatives. We wanted to take all the data on energy reductions in data centers and distribute it to each of our customers. We had a very complex template that we wanted to iterate on until we delivered the report. I developed a bot that could generate the source data and template of these files for our customers by data center and aggregate them. 

Before I joined the company, they had no automation solution. They tried to do this with mail merge, which struggled because of the variability across our sites. We wanted to achieve greater complexity and offer this table of information when it's available or update it when the final file we're generating varies significantly. We wanted to be able to convert a Word doc into PDF format and aggregate all of those different PDFs at the site level and aggregate those per customer. 

UiPath's Object Repository was huge. I could build these libraries because our industry works with many of the same systems. It's hard to integrate with Yardi's core CRM, and many of our automation efforts focus on getting information in and out of that system. The ability to build these libraries of reusable selectors has dramatically benefited me over the past couple of years. 

I'm excited about all the new stuff around document understanding because I think that is a large area. We can continue expanding and delivering large-scale automations.

The messages and alerts that Orchestrator generates are a little overwhelming. I'd like them to be filtered down to the most actionable things I need to look at. For many things, we set up an automation that will send an email summarizing things to the stakeholders for the automation. With any of these types of things, you're generating notices, emails, and things, so you want to focus on some things that need your attention. 

I started using UiPath while interning and pursuing an MBA. I've always been a huge fan of Excel, Visual Basic, and automation in general. I've been in my current role for about three and a half years, but I began tinkering with UiPath for a couple of years before that. 

I have not experienced any performance or uptime issues with UiPath.

In my current role, it's been challenging to demonstrate the need to grow and bring on more developers. We're processing a high volume of invoices, but the rest of the business has around 200 employees. We have large capital expenditures building these data centers but not a high volume of back office processes. 

I have not necessarily been able to evaluate what it would look like to grow with 20 automations. We could keep a steady pace of new smaller-scale processes and look for new large-scale opportunities, especially with some of these new technologies. However, I don't think we'll be a large enough business to need these massive deployments.

I rate UiPath support 10 out of 10. I have submitted tickets periodically for a specific issue, or when I'm trying to solve a new problem, I haven't faced before. I am the only UiPath-focused employee at my company. I can work on iterating, researching, and troubleshooting. 

 I've always been able to put in a ticket and get on a call with some people. They're able to connect me with someone and help me understand either the problem I'm facing or the fact that we've been able to have more calls recently about new potential. The online community is also an excellent resource for finding ways to approach and solve problems. Their support has been great.

Positive

Prior to UiPath, there was no different solution implemented at my current company. At a previous company, we conducted a comparison between Automation Anywhere and UiPath and opted for UiPath due to its greater flexibility, capabilities, and entry offerings. At the start of my career, UiPath was one of the first to offer free online training and a lower entry point for businesses just starting out.

Automation Anywhere followed suit. While reviewing them, I built the same process in both systems and presented it to our executives. Automation Anywhere seemed focused on the financial industry. It had some excellent features if that's what you were what you cared about, but I greatly preferred the UiPath's general flexibility, capabilities, and breadth of integration. I've done some small-scale things with Microsoft Power Automate. That tool is hard to work with. They try to make it easy for non-technical people, but it means that I have a hell of a time trying to get it to do what I want.

The initial setup was straightforward, and it was conducted in-house. We host our own virtual machines for running automations and we are a cloud customer.

The implementation was done in-house.

We've seen the greatest ROI from large-scale invoice processing, but small-scale operations have had great returns. Before automation, we were processing 3,000 invoices monthly, which took 15 minutes each. It still requires time to review them in the Action Center manually. 

UiPath's pricing and licensing have been reasonable and manageable for us. Despite challenges in constantly monitoring SharePoint folders, UiPath has worked well within our resources. We have a fully dedicated, unattended license for our invoice processing, which needs to be a top priority and is always running throughout the day. We have another one for all of our other scheduled automations, and we've been pleased with that so far.

I rate UiPath 10 out of 10. I'm incredibly impressed with the pace of new features that have come out. I have been working with UiPath for six years since I graduated college, and I'm blown away by what's coming out every year.

We use AI mainly around sales processing and document understanding. Our current use cases involve traditional automation, processing different orders, order formats, languages, and language translation, and creating actual orders in any ERP solution.

We've done a Communications Mining POC, and we think that's promising, but we haven't used UiPath's process mining because we have another solution for that. 

We were already using a competing automation platform when we implemented UiPath. UiPath is a more cloud-based solution. We're biotech regulators, so we're trying to adopt new innovations as quickly as they are released. Regarding challenges, we're trying to simplify and automate processes to achieve a higher value and make problem-solving more seamless.

We engage our employees in automation in two ways. At the enterprise level, it's more about making it easy for there to be a centralized intake of opportunities and focus on the value of what comes through. Citizen automation is about empowering and training them on how to use it so they can build more. 

Our organization has experienced productivity increases, financial savings, error reductions, and streamlining of many processes in finance and accounting with UiPath automation. It has helped free up staff time so that they can focus on more value-added work, and when automations don't function as expected, employees can be upset because they don't want to return to previous manual methods.

I don't know about shareholders, but employees who learn to build automation can do more value-added work. It makes them happy. Customers within the company can have people in their teams spend their time on more value-added work, and they have better transparency.

RPA is always good, and UiPath's Document Understanding is interesting. We used the old model, but the new modern Document Understanding is much easier.

UiPath could offer better support for operations. It has all these cool features, but when you still need to build and run these bots. You need to have more features that make it easier to run bots, and they require fewer people to maintain. 

We have used UiPath since 2020, so it has been nearly four years.

The solution is stable, with, for example, only a thirty-minute outage in three years.

It is scalable, but successful scalability depends on how you build automations.

We have premium support, which provides excellent customer service. Our technical account manager is amazing, and that's one reason we keep paying for premium support. 

Positive

We previously used Automation Anywhere and switched to UiPath because it was easier for developers to use and could integrate with more products.

It was complex because UiPath didn't have a biotech-specific offering. We were the first biotech company to use this, so we had to develop a product that would work for companies under regulation. We needed something called delayering. We had to educate UiPath on what it means to do this for health care and biotech.

UiPath helped us save around 500,000 thousand hours. Over our entire automation journey, that amounts to an estimated $25 million worth of productivity hours.

The pricing is very expensive, making it challenging to continue using UiPath when competitors like Microsoft offer cheaper alternatives like Power Automate. Why continue to use UiPath when you're paying three to five times more? 

I would rate UiPath a nine out of ten.

We use UiPath for intelligent automation integrated with machine learning models.

We previously did many of these processes by hand, and our team found that frustrating because it took a lot of time. There was a chance we could have errors in reports that are critical to the organization. UiPath processes are around 90 percent accurate. Since we implemented UiPath, it has become essential to our organization, and we cannot live without automation now.

UiPath has helped us reduce our on-prem footprint. Its AI functionality has helped us automate more processes while speeding up digital transformation and reducing costs. UiPath has saved team members' time, allowing them to spend more time on valuable tasks instead of tedious, repetitive jobs. 

What I like the most about UiPath is that we can build custom activities. If we want to customize functions based on our logic or use case, we can do that. 

We also like the UiPath community. It's the best help you can find online. If you have any issues, you go to the UiPath forum to find answers to existing questions. If you can't find the answer you're seeking, you can post your question and get an answer quickly. The UiPath Academy has some hands-on activities to practice, and they offer a certification. It's a great way to grow your knowledge. One drawback is that the cost of the certification exam is pretty high. 

The most valuable features are document processing and integration with AI/ML models. Using the solution's AI functionality was a bit challenging initially, but once we researched how to use the intelligent automation, it was fairly simple. Overall, building automated processes is easy. The end-to-end automation capability is crucial for large organizations because it reduces time and energy. 

We use intelligent automation for things like document processing. There is a validation center where the ML model extracts some values, and we can validate if it's correct. That aspect could be improved a little. The percentage of values extracted without validation could be increased. It's currently an attended process, but they should give you the option of making it unattended. 

I have used UiPath for more than four years.

I rate UiPath eight out of ten. 

I rate UiPath 7.5 out of 10 for scalability. 

I rate UiPath support eight out of 10. 

Positive

I have used Automation Anywhere. It's also a good solution that's easy to use, but I like UiPath a little more.  I prefer UiPath because I've done more projects on it.

Deploying UiPath is straightforward. The implementation took a few months because our use case was so complex, and we had to optimize the processes to make them more efficient. Our development team has four people. After deployment, the bots require some maintenance. Admins need to update the automations and ensure the bots are running. 

We've realized considerable time savings with UiPath. We were previously reading and inputting information from documents manually. One document took almost two or three hours. UiPath automation brought that down to two or three minutes. 

UiPath is relatively expensive. It's not expensive if you only need to automate one or two processes, but if you need to use more, it's somewhat costly. There's also a free community version.  

I rate UiPath eight out of 10. My advice for new UiPath users is to complete the training first. Get all the knowledge you need to implement automation before you start working on it. 

We needed a solution for users that had too many manual tasks. We're in a large bank, and there are tasks like account opening or other items that can be automated using the UiPath system. It can handle auditing as well. 

We've been able to increase productivity time by using UiPath. It saves time and costs. 

Previously we used the classic activity. UiPath modified the activity and it made it easier to do the development and create accurate products for the customers.

It's easy to build automation using UiPath. There are a lot of ways to make an automation, compared to other tools, like Automation Anywhere and Power Automate. It's very flexible. We can use different codes and use Excel modifications. It's very comfortable to use. 

In UiPath, we've developed a developer foundation and developer processes. If there are modifications to what has been done or ideas for new ways to do something, we embrace that. 

We can implement end-to-end automation. It's important for us. We do need to study the process and then create a process that is a better solution. Our users can study the whole process and come up with solutions and best practices for building automation. The best way to do it is to have one person handle the end-to-end automation so that there is no confusion in the process.

The UiPath Community is helpful for users. It's an advantage. It helps share knowledge. We're able to find the best solutions for issues with it. 

We've used the UiPath Academy courses. It helps users to study UiPath: what it is, how to use it, and how to build solutions effectively. It's great for users who want to study and be more confident in the development process. 

It has helped us reduce the cost of digital transformation. When we have more people, we need to pay more salary, and it takes more time. Using UiPath, we can save valuable time and reduce costs. What a man can do in one hour, UiPath can usually do the same task in half the time. 

It reduces human error. Sometimes people aren't in the right mindset. If they are tired, for example, they can make mistakes. However, a bot always does everything the same way. 

I'd like to see the accuracy improved. Sometimes the development works fine. Other times, it requires some small changes in the development. 

They could add enhancements in AI technology that could be helpful for everyday developers. 

I've used the solution for three years. 

The solution is stable for the most part. I'd rate it eight out of ten. Most of the time, it's working fine. However, sometimes we have small problems with the data connection or pushing data. It can be difficult to identify the orchestrated things. 

We have about ten people on our team servicing clients with UiPath bots. There are three senior developers. We have bots across multiple locations. 

I'm unsure if the solution scales well. 

We sometimes have to ask a lot of questions as the accuracy can be missing. When they provide us with a solution, there are options between classic and modern. It might take a while to fix things or if there are issues again and again the customers can sometimes be disappointed. 

Neutral

I've used Microsoft, Automation Anywhere, and Blue Prism. I'm most comfortable with UiPath and Power Automate.

Power Automate is developing a lot of its own solutions right now for Microsoft. I find UiPath more advanced than Power Automate and Automation Anywhere, which don't have as many features. Power Automate is the most comparable to UiPath. 

The main disadvantage to UiPath is the cost, which is really high. 

When we do the deployment, we have to take into account security, et cetera. It concerns us when we're talking about using the cloud. There may be particular processes we cannot do on the cloud. 

One good developer is all you need for maintenance. If you have to update the system or do a modification, we need to update UiPath. So there is maintenance required and a person does need to watch the process. We provide the maintenance.

Currently, our vendors are doing the installation. After it's installed, we provide all of the bots and processes. 

I don't have any metrics in relation to ROI. 

The licensing is very expensive for UiPath. Many clients are going with Power Automate or Automation Anywhere based on the high cost of UiPath. 

We're an end-user of UiPath. 

Currently, we aren't using AI technology in our solution. However, I like the idea of it. We'd maybe be able to resolve redundancies with it in the future. It may be on our roadmap in the future. 

I'd recommend UiPath. It's very accessible. I use a lot of products and this is the best product to give to customers overall. 

I would rate the solution nine out of ten.