UiPath Platform Reviews

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're a bank, so we primarily use UiPath to automate tasks such as filling out Excel sheets, organizing PDF files into folders, and reconciling rejected checks and chargebacks.

We prioritize use cases by meeting with each business unit to operational challenges that they would like to solve through automation. They walk us through the process they want to be automated, and we prioritize the requests based on potential hours saved and the automation difficulty.

The business units don't interact with the bots much. We get requests via email, and our Center of Excellence develops and maintains all the bots.  

UiPath helps us improve operational efficiency. We want to grow our bank by increasing the number of accounts without adding more employees. Our headcount hasn't increased in the last four years while our assets have grown tremendously. By automating data entry and other monotonous tasks, UiPath has improved employees' sense of job fulfillment. It frees them up to work on more challenging tasks and work on new skills.

We like UiPath's integration with the ARIA framework and Orchestrator we use to manage our automations. The Copilot also helps us streamline the development process.

There could be better documentation for Copilot, and UiPath could provide solution design documents as part of the training.

We have used UiPath since 2021.

We haven't had any issues.

UiPath scales well with our environment. 

I rate UiPath customer service eight out of 10. I had one issue where they pointed me in the right direction but didn't fully resolve it.

Positive

We've done some simple tasks with homegrown automation that UiPath could handle, but we opted to build the processes with tools we already had.

The initial setup involved using a UiPath partner, which significantly facilitated our production and deployment environments.

We've saved about 2,500 hours annually with UiPath.

I'm not responsible for the budget, but I know that UiPath is more expensive than its competitors. 

I rate UiPath eight out of 10. 

My use case with UiPath Platform depends on the customer, as I am an expert architect. I build applications, build projects, help customers provide business solutions, ask questions, answer questions, and resolve issues.

The best features in UiPath Platform are the Agentic Robots, which provide a kind of intelligence. 

UiPath Platform offers excellent support and training. They provide free training, unlike Blue Prism. I worked with Blue Prism for three years, and you have to pay for training and certificates there. 

The support is good, and the price is the same as Blue Prism. For me, it is the best number one in the world for bots.

Agentic Automation is a new technology that they built this year. Previously, with the UiPath Platform, we had a robot that we asked to do business actions, but with Agentic, the robot can think. The robot performs actions, and Agentic can make decisions if we program it to make decisions. The customer doesn't do anything. It's a revolution in AI.

My clients have replaced personnel and saved a significant amount of money. For example, I have customers who had 11 people to work, and after one year of using the UiPath Platform, they saved ten people.

We use Communication Mining features in real time for small businesses and critical businesses. We use robots to do actions in real time with supervision through Elasticsearch and Kibana to show what happened in real time. With UiPath Platform Communication Mining, we can automate actions or responses according to the type of content in the message. We can connect to an Outlook and Gmail address.

With Agentic, it can think and provide personalized answers. It's very easy to build automations with UiPath Platform for someone who doesn't have technical skills because they have UiPath for developers and UiPath for business. For teams that don't have enough knowledge in IT, building simple processes is possible. For complex processes, more IT knowledge is needed.

The UiPath user community is extensive and informative. The majority of my clients are big companies. Most businesses share architecture and need strong architecture because the cost isn't high if you choose a strong architecture. They use UiPath Academy to learn and get certificates because there are many products and options in the application.

There has been a 90% reduction in human error. For UiPath Platform, you have three components: UiPath Studio, the robot, and the orchestrator. For annual updates, the orchestrator takes one day, while the robot and Studio each take one hour.

The area that has room for improvement in UiPath Platform is the price. 

I have been using UiPath Platform for around ten years.

For stability, the orchestrator rates at ten out of ten. It is very stable. Studio rates at a nine out fo ten, and robots rate at eight out fo ten since they work only with Microsoft.

The solution is scalable. If you want to add machines, it's very easy. However, you have to do the architecture with a professional, not just with a developer.

The vendor support is very good, and with all my customers, we have premium support. It rates a ten out of ten.

Positive

UiPath Platform is better than Blue Prism. Blue Prism's training isn't free. You have to pay to get information, and they don't have cloud. They built their cloud two or three years before, so they are behind.

The ease of the deployment depends on whether you want to know about developers or architecture. For architecture, I am alone for all customers. I administer the platform, install the production, and perform all tasks related to production. For developers, it depends on the customer. I have customers who have ten, 20, or even 50 developers.

The solution requires maintenance. You need the big update in a year, and depending on the customer, two or three updates in a year, with one update every three months, but you have to update once a year.

I can estimate that all my customers see about a 40% return on investment. This saves about 40% of time. It depends on the process; some processes save all the time, while others save significant time.

In the beginning, when I built the application, we didn't talk about licenses. We buy licenses, but after one year, we try to mutualize and share licenses with different customers to minimize the number of licenses and to minimize the cost of the application.

I rate UiPath Platform ten out of ten.

I have used UiPath for very few projects. My go-to tool when it comes to automation is Power Automate. The reason for that is that I work in the Microsoft 365 environment, so Power Automate is better connected than UiPath.

With UiPath, I helped some organizations in my company automate tasks like data entry into systems such as SAP. 

I like UiPath. I enjoy working on UiPath. It has a lot of different features to control, especially related to desktop flows. I helped some organizations in my company automate tasks like data entry into systems such as SAP. They had Excel files, and all that data needed to be input on standard screens in SAP. It was taking a fair amount of time to do it by hand. We created a flow that transfers all that data, interacting with the screens in SAP, and uploads that information where another alternative, like an API or mass upload tool, was not available.

It is pretty easy to build automation in UiPath. We could easily implement end-to-end automation. I was consulting a group within my company. I was helping them build the flow. For them, it was a game changer because they would have spent several man-hours trying to transfer all that data into SAP, creating all those SAP items. After that, they were not only able to complete the task at hand; they were also able to replicate and create more automations on their own because they knew how UiPath works. They learned a little bit more and were able to continue to expand the other processes they had.

We were able to realize its benefits quickly. It took us a couple of weeks to finalize the flow, but once it was built, we were able to start seeing the benefits. It definitely saved time.

I like the way that I can reference specific objects on the screen, like a specific text box, and add a value to it. The capability that UiPath has to recognize elements on the screen is what I found most useful at that time.

UiPath has a lot of courses for easy learning. There were several courses that I offered to the organization I was helping. I myself went through several online resources that UiPath offers to figure out things.

UiPath should be less sensitive to changes in the existing UI of the system we are trying to manipulate. If it was more intelligent in adapting to changes in the user interface and the tools we are trying to manipulate, it would be beneficial. If the UI changes or a label is changed, sometimes the whole flow breaks. Identifying where the flow breaks requires going into edit mode and making modifications. It might be quite extensive work with the new, updated UI.

I have been using UiPath here and there for at least two years. It is a part of the solutions that my company offers, but I have not used UiPath as much as Power Automate.

It performs well. I do not see any issues there.

I use Power Automate on a daily basis. 

It was easy. It took us about a few weeks for ideation, selecting UiPath as a tool, getting everything set up, building the flow, and testing.

In terms of maintenance, users continually review and upgrade their flows. They can reuse the existing flows to create new ones.

I am not familiar with the pricing. I worked for an organization where the UiPath was available, so I do not know what the pricing is.

It was through an internal community that I connected with the organization for which I did the automation, and that is a great advantage. They were looking for people to help create automation. I was curious about UiPath, and I wanted to learn. I raised my hand to build that for them. An external community or a learning community is something that has proven its value by creating synergies between people who do not know and people who already know a little bit, allowing them to get together and grow.

In my opinion, RPA solutions are alternatives to digital transformation. Digital transformation is a big project. When you do not have access to those big budgets or the structure to get into new capabilities on an existing system or implement a future system, that is when you go to RPA to supplement the digital transformation. If the use case is not eligible for the big capital investment or the big project investment, you go through the route of RPA.

I would rate UiPath a nine out of ten.

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.

In the past, we have used UiPath to automate repetitive manual processes for companies in the finance and banking sectors, but healthcare is our current focus. This industry involves processing tons of data from patients, customers, and doctors, so it's a huge field. 

Previously, I developed bots for compliance at financial companies. I've also created processes for reading PDFs, sending emails, Excel automation, logging, and exception handling. We have also contracted with insurance companies that need to pull data from emails into their main enterprise application.

The healthcare companies cannot provide us with direct access to their systems for security reasons. We are currently accessing their network through a middleware system so it doesn't compromise their security. UiPath doesn't work on that third machine and cannot retrieve the values as it should. If we scrape data from the web, it will get to the HTML that is behind the site. 

When we are accessing the third PC, we cannot get to it because it is a desktop machine. We are using the completed version activity, which is working mainly on the image image-based activity. This capability is available in UiPath, but I don't think Power Automate or Automation Anywhere can do this. It helps because we don't need to do any coding. 

UiPath tends to be deployed on the cloud, so clients can minimize their on-premise footprint. We deploy on-premise and cloud-based UiPath depending on what our clients want. For some companies, uploading data to the Orchestrator on the cloud is potentially a security concern that hasn't been resolved by the UiPath developers. Power Automate has an advantage in that regard. 

Our employees use the company's credentials to get training from the UiPath Academy and obtain certifications. I have a personal account on UiPath Academy, but it has some license issues. The academy is helpful because UiPath is implementing new features every three months or so. It's all about the documentation. We can learn about new features and do more. With more knowledge, we can develop something bigger.

UiPath reduces costs by eliminating human labor. Let's use an insurance company as an example. Let's say they have employees who are responsible for reading emails. Every day, they receive information via email from the customers, and their job is to retrieve the details and enter them into the main database. The average insurance company receives 400-500 emails daily. These people will spend the whole day completing the task of manually transferring data to their main application. 

We have a bot in pre-production that can handle 1,100 emails daily for the company. It has a significant impact on the efficiency of the operation because the bot can input the details into the database quickly and without any errors. The employees who were responsible for this work are now monitoring it and also learning about UiPath at the same time. It is a great tool for increasing productivity, thereby proportionally increasing the company's profits.

The first company I worked with had 20 employees in their compliance department working on some PDFs. The company had to send emails to around 6 million customers. We deployed the bots, and five bots could do the work of 10 employees. The company kept the other 10 employees but reassigned them to monitor the bots and fix errors. They also learned to develop their own bots. They could cut 10 positions and save money while improving productivity. Those employees weren't working as fast as the bots and cost more money.

The solution also greatly reduces human error. In the financial compliance use case, they were dealing with upwards of a million rows. That was labor-intensive work, and no human could complete the task in under three days manually. Sometimes, we would have some errors in which the values were reversed by accident because humans make mistakes when they are tired. In this kind of work, we're working with digital amounts and currencies, and we are applying mathematical formulas to the amounts, like credit, debit, or some business calculations. 

UiPath doesn't have large hardware or software requirements. We only need one physical PC on the client's premises. That computer requires some minimum specifications, such as a 1 terabyte hard drive and an i5 processor. We need that computer hardware and a license for the client. 

If the client doesn't want to purchase an enterprise license, UiPath offers a community version. There are no restrictions on the features, but it can only run one bot at a time. The enterprise version can run multiple bots. If our client only needs one process, we can provide them with the community version and deploy it on their PC. 

UiPath can free up employees to work on more important things. One of my colleagues was doing some tedious work manually, but once the bot was in place, he only needed to click one button to run UiPath, which extracts all the data and updates the Excel spreadsheet in 10 or 15 minutes. Previously, he spent up to six hours preparing the data before he could complete the other tasks. The important work was being delayed every time. It increases productivity, which benefits the company. 

UiPath's most valuable features are its UI automation activities like scraping and manipulating data. We need to scrape the data before we can manipulate it or save it in another application. I think that part is very valuable and important.

Having worked with other tools like Microsoft Power Automate and Automation Anywhere, I find UiPath to be the most user-friendly because it provides all the actions on the side, and we can just drag and drop them. It's a simple interface that we can easily understand. Automation Anywhere has a more complex interface. UiPath is straightforward enough that our junior employees can easily pick it up. 

UiPath's ability to offer end-to-end automation is critical. We typically provide our clients with a simple demo of what UiPath can do. After that, they provide us with details about their end-to-end processes, which we use to determine what can be implemented through UiPath.

For our healthcare client, the initial assignment was to scrape the data from the website and put it into Excel. Later, they decided that they wanted the data in another application, so it could be stored in the main database. We constructed an end-to-end process for maintaining a million records in their primary database.

I also like the UiPath Community forum. I go there when I get stuck with anything. When I run into an error, it's easy to find the answer. The community is highly active. If I post a question, I can usually get a response from community members in an hour or two. 

I have tried a bot that uses UiPath's AI capabilities, but I didn't develop it. It's a portal for patients to make appointments and check into reception at the hospital. We implemented ChatGPT on an Android device, so customers can ask questions and get information. 

We also developed a bot that can derive the same types of data from PDFs with different structures and formats. For example, let's say the patient's name is on the first row on one form, but on the third row on another. We can configure a bot to extract the name regardless of where it is. We can train our ML module by telling it when the data is wrong and running it again. Now, it's mostly accurate.

I would like UiPath to improve its screenshot feature. It should have the option not to take screenshots unless the user specifically allows it. Sometimes, it is a security issue for companies that do not want to share screenshots of the main application. Another thing I want to see is a standalone mobile application that we can run anywhere. I would like more cross-platform application support.

UiPath can get unwieldy if the process becomes too big and complex. I had one client based in Saudi Arabia that had an application with 1,500 pages. Once the bot we were developing got much bigger, the application started having stability issues. It performs well in typical cases, but once we exceed that average, the application starts to crash or behave abnormally. 

I have used UiPath for four years.

Overall, UiPath is stable for most processes, but Power Automate is better at handling large, complex projects.

I have worked with Microsoft Power Automate and Automation Anywhere. The primary advantage of UiPath is that it's more accessible than the other solutions. You can learn UiPath without any knowledge of programming or computer science. It takes only about a month to learn the tool, even if you have no skills. For example, if you're a blogger and you want to automate posting to the website, you can do that through UiPath, so it is beneficial for personal use and commercial use. 

The other advantage is cost savings. UiPath saves organizations some money, and it's more accurate than Power Automate or Automation Anywhere. Automation Anywhere is my third choice. Power Automate comes in second place because It was developed by Microsoft, and most enterprise companies have a Microsoft subscription. If their license includes Power Automate, they prefer to use that instead of buying a separate subscription for UiPath. 

Many companies are switching to Power Automate because of this bundled licensing. The UiPath enterprise subscription is somewhat expensive. Microsoft can provide the same functionality, and it integrates with tools like Excel and Outlook. Companies can get all those tools within the same license, so that's an advantage Power Automate offers over UiPath.

Another advantage of UiPath is that you can also work with image-based processes. If we cannot get any selectors or access the HTML code behind the application, we can use image-based processes. This feature isn't available in Automation Anywhere. UiPath has the AI center, and Microsoft also implements AI in Power Automate processes.  However, Automation Anywhere cannot use AI in their product.

My current company is smaller, so I'm responsible for multiple tasks. I am the requirement gatherer, developer, and deployer. At my previous company, they had a business analyst who talked to the client and made an inventory of their requirements that he provided to us. Then, my only task was to develop the bot. It was the other team's duty to deploy the bot on the client's physical machine. 

The process involves three steps. We need to connect UiPath and provide the logs. Our client can access the Orchestrator to see logs of what the bot is doing online. He doesn't need to physically access the machine. There is also middleware called the UiPath Assistant that we use to connect UiPath to the Orchestrator. 

The number of staff needed for deployment depends on the complexity of the processes. If it is a single process, we don't need a deployment person or team. The developers can deploy the bots. My company has five developers, so everyone is developing their own bots and handing them over to the deployment team. For every five developers, we have two deployers. If the five developers are developing automated bots daily, we need only two deployers to deploy them on the machine. Also, if we want to have a backup version, we can deploy it on GitHub to make the repository and organize everything.

The maintenance aspect can sometimes be difficult. Exceptional cases can arise during the process. When we initiate some processes, we need to monitor them for about 30 days. We don't monitor some processes because we're not seeing any errors or exceptions. We have to monitor other bots, stop them as needed, handle the exception, and run them again. After 30 days, the bot should be mature enough to handle the exceptions without intervention. 

UiPath offers an excellent return. For example, a recent client in Pakistan was scraping data from a website with 349 products. His job was to scrape the title, price, and variants and place the data in an Excel spreadsheet. He was working all week alone, so I proposed UiPath. I told him UiPath has a function called "Extract Data Table" that can scrape all the details of the products and just dump it into Excel in five or ten minutes. He was impressed, and I developed the bot in front of him. 

Now, he's running my bot and dumping all the results in his Excel sheet. He's also working on other projects, and his routine has become very stable. He has more time to spend with his family. It has surely made an impact and yielded a positive ROI.

I don't know the exact cost, but UiPath is more expensive than Power Automate and Automation Anywhere. 

I rate UiPath seven out of 10. Learning a little JavaScript coding is helpful because there are some scenarios in which UiPath doesn't help you. In some cases, you may need to write a little code to perform some actions or call some functions. I would also take advantage of the UiPath Academy so you can stay up to date on the latest news and features. 

The main use cases for UiPath Platform are automations within the company across different departments. So far, we have only looked at RPA in UiPath Platform, but Document Understanding is the next one, and Agentic. We are evaluating Agentic right now, but we only have a license for RPA and DI now. We are working on an RPA use case right now, the first use case, while Agentic is under evaluation. We don't have a license for it, but we are trying to see if it's going to fit our use case.

My team and I have used the vendor's UiPath Academy courses. The biggest benefits that I have seen with UiPath Academy are the clear step-by-step instructions on taking you through the different tools available. I think UiPath Platform is the best; based on my research, I think it's one of the best for enterprise-level automation, while we use multiple tools for personal automation, but for enterprise-grade automation, I think it's the best out there.

I am still in the evaluation phase of UiPath Platform, so I don't know how it can be improved or what additional features should be included on the next release right now, maybe next year.

I have been using UiPath Platform for three months.

I will have to wait and see to assess the stability and reliability of UiPath Platform, as nothing is in production yet.

I will have to wait and see how well UiPath Platform scales with the growing needs of the organization.

I would evaluate the customer service and technical support so far as pretty good. On a scale from one being the worst to ten being the best, I would rate my customer service and technical support as nine.

Positive

Prior to adopting UiPath Platform, I was using Kofax to address similar needs.

My experience with the pricing, setup costs, and licensing has definitely been more money, and it has caused some confusion in the company compared to the competitors.

I could see a return on investment with UiPath Platform, but nothing is in production yet; I can see it's coming.

Before selecting UiPath Platform, I considered Automation Anywhere and Kofax, and we looked at all those options, as we even have a Kofax environment currently running.

What stood out in my evaluation process regarding UiPath Platform was definitely positive, and that's why we went with it. The factors I considered when making the change were definitely not cost, because that's way cheaper, but it's more for the enterprise-level automation that is the reason for moving to UiPath Platform. Nothing is live yet with these features, so we're just waiting, maybe a couple of weeks. I don't have thoughts about UiPath Platform user community in terms of value that I can gain by being part of it yet, since it's only been three months. I would rate UiPath Platform between eight and nine out of ten.

My main use cases for UiPath Platform include bot automation, Agentic agents, and AI, with specific use cases that are healthcare-centric, while also leveraging technologies that the platform brings, such as RPA bots and agent orchestration.

Implementing these features from UiPath Platform has benefited my organization as we reduced DSO and improved clinical effectiveness and timeliness, leading to improved employee efficiency and accuracy.

The feature of UiPath Platform that I appreciate the most is the orchestration. 

UiPath Platform can be improved by being able to leverage what we have, and from an AI capability perspective, having a chat or voice capability on the platform would be beneficial. With Maestro and the concept of being able to orchestrate across other solutions is phenomenal and great, but I would also appreciate being able to just stick with one solution.

I have been using UiPath Platform for six years.

I have not experienced any downtime or performance issues.

UiPath Platform scales with the growing needs of our organization extremely efficiently.

I evaluate my customer service and technical support as top-notch. On a scale of one to ten, I rate my customer service/technical support as a ten. 

They have been highly responsive. In every cab meeting or conversation with senior leadership at UiPath, they have made things happen, and my account executive and solutions executive have also made things happen. I cannot say enough about how great the team that supports us is.

Positive

Before selecting UiPath Platform, we looked at some other vendors, and I have a background beyond the current relationship, as I have used UiPath Platform in other companies, which helped accelerate our decision-making.

My experience with deploying UiPath Platform is very positive.

We are seeing a return on investment with UiPath Platform.

My experience with the pricing, setup cost, and licensing of UiPath Platform is positive.

Prior to adopting UiPath Platform, we were considering other solutions, including purpose-built solutions from companies such as Tenor and also Blue Prism and OpenAI's ChatGPT.

My advice to another organization that's considering UiPath Platform is to understand your journey and what you're trying to accomplish. UiPath Platform can do it, and I don't have any concerns or questions around the technology or the capability or the organization to support. Another customer would need to be prepared and understand what they are doing and why. 

I rate UiPath Platform ten out of ten.