UiPath Platform Reviews

We are using it to automate business processes in the organization.

UiPath has impacted our operational efficiency quite a lot. There are a lot of scenarios where it has helped the end users. We also have benefited financially from it. We have streamlined the processes to an extent. We initially started with a basic data migration process, and now, we have our own intelligent automation and hyper-automation framework. We just get the requirement, put it in the framework, and start automating. We have progressed a lot.

UiPath enables us to implement end-to-end automation. There are certain instances where we do not get end-to-end automation, but those are the things that are out of RPA's capabilities.

End-to-end automation is important because we can showcase our capability more efficiently in front of our management and the client. We can show that something can be 100% automated if there is a use of 100% automation.

They have UiPath Academy. When UiPath was new, we did not have any online resources to go and learn. The YouTube community was small. There were no courses on Udemy or any of the online platforms. The offline platforms were also minimal. UiPath Academy was one place where we could go and learn and prepare for the exam. I got certified when UiPath certifications were free. I have done all the learning from UiPath Academy. As I move up in my role and responsibilities, if I want to learn a few more things, UiPath Academy is still the best place. You get a very crisp and clear understanding of everything.

We use UiPath’s artificial intelligence and machine learning capabilities for hyper-automation. In my understanding, RPA in the initial days was limited to redundant process automation, whereas now, the use of AI Fabric and other components makes the automation more intelligent. We can add decision-making to existing automation. There were many processes where we had stalled the process just because the next step was a decision-making step, and someone had to come and make a decision to move forward. Now, we have our own AI team to build the code that can make decisions on behalf of a person and also learn from the existing behaviors. That helps quite a lot.

UiPath saves time. It saves about 50% of the time. It never saves 100% of the time because we also spend a lot of time maintaining and doing enhancements to the process. Processes are never stable.

We have integrated it with multiple tools. The outcome has been very good. There have been challenges at times with the development, but the integration has been smooth so far.

Computer Vision is one good feature. AI Fabric is another good feature. The holistic Orchestrator platform is another feature that is very useful.

The RE Framework provided by UiPath is quite extensive. It solves a lot of problems and gives us a lot of time back. We do not have to create our own framework.

UiPath is more user-friendly than other RPA solutions that I have used. UiPath also has the biggest community.

Automation Hub needs to improve a lot. About two years back, it kept on crashing. It has improved a lot. We use it but not to a great extent. We try to build our own dashboards by using any of the data analytics tools.

It should give real-time data, and the integration with the servers is not that great. It can be because of the infrastructure that we have.

They can also consider integration with other automation tools because nowadays, a company does not have one automation tool or RPA tool. A company has multiple RPA tools. They can think of integrating the data from other automation tools in one automation hub so that it becomes centralized.

I have been using UiPath for close to seven years.

UiPath is quite stable. I would rate it a nine out of ten for scalability. It does crash sometimes. That could be because of the infrastructure we are using.

The reliability of any process that goes to the end user is tested with a set of data. We do rigorous testing because, at the end of the day, any error in production ends up in a financial loss, so we test the automation that has been built to quite an extent.

I would rate UiPath a seven out of ten for scalability. No technology is 100% scalable. As technology evolves, new features, such as GenAI features, need to be added. Scalability-wise, it can never go to a ten. Another reason why I rated it a seven is that I want Automation Hub to be scaled to its full potential. It has not been scaled up properly. I have got this feedback from different people across the organization.

The organization I belong to works on the use cases for building automation for given processes. We have around 15 developers doing this work.

I would rate UiPath support a ten out of ten. They have been quite supportive when we have raised any query with them.

I have been in the automation field for the last 12 years. I started with RPA with Blue Prism. I have worked with almost all main RPA tools such as Power Automate, Automation Anywhere, etc. I find UiPath to be the most user-friendly. There is the ease of having all the activities in the same panel. You can have the Studio setup and you can review the code as well with the analyzer. It gives a lot of flexibility when you are developing.

The one feature that is very good is that the marketplace is open. People can build their own set of activities and post them there, which is very useful. I myself have built a lot of activities. I have also used activities by other developers to complete my work. The marketplace is very helpful.

UiPath has the biggest user community. Its community is bigger than Power Automate, Automation Anywhere, and Blue Prism. Other than the community, there are also several groups. There are a lot of developers. If you are stuck with any issue, which is quite common, someone will have a solution for it.

Developing automation with UiPath is much easier compared to Power Automate, Automation Anywhere, and Blue Prism.

The deployment is handled by another team. I do not handle the deployment because the infrastructure team handles it. It should be a one-man job. It is not that difficult.

The deployment duration of a process depends on how big the process is and how much time and resources it requires for development. Usually, it takes two to three weeks. It can also take ten weeks depending on the process. 

All tools require maintenance in terms of upgrades, but that is probably handled by UiPath. We only maintain our own processes. If there are some changes to the selectors or any of the UI components, we have to update the project.

With RPA, it takes one or two years to see an ROI. It is not cost-efficient till then. When you start building hundreds of processes and utilizing the full capacity of the bots to work 24 hours, you get a good return on investment. Initially, it was expensive, but as we scaled up, we could see an ROI. We have seen a good profit.

Initially, the ROI is less. It is about 5% to 6% per year, but as the processes mature, the headcount reduces, and the human intervention also reduces. It eventually moves to 30% to 40% ROI.

It is the most user-friendly RPA platform, but it is also the most expensive RPA platform.

I would recommend UiPath to others because it is the most user-friendly. It is also developer-friendly because of the community. It also works across systems. These are the three reasons for recommending it.

We run a roadshow across the organization to understand which processes are redundant. We try to understand which part of a process can be automated by using the general RPA automation and only one tool. We also categorize them in terms of what can go under intelligent automation where a certain amount of decision-making is required. Another category is hyper-automation where we try to understand how to include different tools, such as machine learning code, AI code, NLP data set, or data mining set. If we have an existing tool for data mining and process mining, the final steps can be automated. These are three major criteria. For basic automation, we try to assess the type of automation. Is it desktop automation? What kind of resources are required? Do we need an attended automation or an unattended automation? Based on my experience, almost all of them are unattended automation. We then try to pull in the use cases, prioritize them, and start automating.

UiPath keeps on enhancing its product. Four years ago, there was no AI Fabric or Automation Hub, and now, we have all those things. They help a lot in delivering the project and having a prototype view for all the projects that are running.

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

We primarily work with banking clients at a high level, automating solution points, nodes, and bot processes to reduce demand. For example, if a task was previously performed by a hundred people, we have now limited it to around five to ten people by implementing automation to closely monitor the bots in real-time to ensure their effectiveness.

Building automation using UiPath is easy and in most cases can be done with a single click. There is no need to write coding. We can insert and delete columns or remove duplicate frames easily. 

We have already implemented a couple of solutions, one of which is a maintenance automation database. The users of the database want to send emails with attached files and other artifacts, and previously this was done manually. Each day, up to 300-500 items were manually processed by 50-60 people who would navigate to a separate application, search for the file, upload it, and send the email. This was a tedious task and accuracy and reliability were questionable, requiring manual verification. This process was repeated monthly for around 10,000-12,000 items, taking around 25-30 days to complete. We automated this process and provided a high-level solution initially, which was later built, bought, and deployed. The bot we created is capable of processing 900-950 items per day, meaning that all 10,000 items can be processed within eight to ten days. This reduces the processing time by one-third and the cost from 100 to around 12 months, as we only need three to four rotational shifts to monitor the bot. Sometimes the bot may disconnect or encounter issues beyond our control, but we address these promptly to reinstate the process. This is the work we are doing in our organization.

End-to-end automation is a crucial aspect of completing tasks within the specified time frame. Clients do not want to wait for extended periods, such as a month or two, and prefer to see progress at least one-third or one-fourth of the way through. This ensures that clients are not preoccupied with a single task and can focus on improving their business while also increasing accuracy. UiPath aims to provide clients with a high return on investment from both the software build and business development perspectives. This is achieved by delivering effective solutions that meet clients' needs.

We are satisfied with UiPath's community. Occasionally, we encounter some queries or doubts, such as whether we should use a particular feature or MAC code, or whether we can use a certain file. While we cannot always rely on direct support for such minor issues, we found that the UiPath community can be a helpful resource. We search for similar issues that other users may have faced and posted about, and we often find solutions to our questions in a timely manner. Overall, we find the UiPath community to be effective and useful.

UiPath has helped our client reduce their on-premises footprint. This decision is purely based on the client's interests and has nothing to do with our personal or company interests. Generally, clients prefer cloud integration as they want their systems to be up and running 99.9 percent of the time. However, sometimes they may opt for on-premises solutions based on the CDRT of a particular application, which refers to the sensitivity of the data involved. We have some limited automation that deals with sensitive information, such as credit-related automation, which the client cannot access. In such cases, clients may prefer an on-premises solution, but overall, cloud integration is becoming more important.

With the implementation of AI, we can utilize UiPath for automation, which is more dependable.

UiPath reduces the cost of digital transformation.

Our clients are highly satisfied with the nearly 99 percent reduction in human error achieved through the use of UiPath. This includes both individual and team errors. However, during the development phase, some human input was necessary to create rules for the bot to follow. Any potential issues were identified and resolved during testing by our IT and testing teams. Overall, our clients are pleased with the system's reliability and performance.

The architecture of UiPath is a unique feature compared to other solutions. 

The ease of integration is a valuable feature.

Debugging files is easy to do using UiPath.

Some of our customers have experienced performance issues after the latest update.

The licensing cost is high and has room for improvement.

Some of the APA integrations are complicated and have room for improvement.

I have been using UiPath for four years.

In general, UiPath is a stable platform. However, the performance tends to slow down frequently after updates.

UiPath is scalable.

The technical support and documentation are good.

Positive

In 2017 and 2018, we utilized Blue Prism in the preliminary stage. However, we subsequently discovered that it was not appropriate for our clients due to its intricate architecture and high cost compared to UiPath. UiPath, on the other hand, offers a more user-friendly experience by integrating everything into a single platform.

The initial setup can be described as neither straightforward nor complex. I give the initial setup a five out of ten. We experience smooth operation once we finish setting up and deploying. If a person has three to four years of experience and is familiar with all the necessary processes for deployment, I believe that only one or two people, excluding the developer and tester, are needed to deploy the entire package to the host. Sometimes even just one person can handle the task, but we can assume two people will be sufficient. They will be deploying the product on the cloud, as there is a single package that has been moved from the latest enrollment.

We implement UiPath for our customers.

UiPath has been instrumental in saving our customers money, which is the primary reason why they have adopted it. Instead of using the traditional method, UiPath's automation has streamlined processes for over 10,000 products, leading to a reduction in manpower by almost 90 percent. This has significantly decreased the turnaround time from 28 days to 12 days, making clients exceedingly satisfied and unwilling to risk their business due to potential delays. As a result, UiPath has provided us with a tenfold return on investment.

The licensing cost is high.

I give UiPath a nine out of ten.

UiPath does not require maintenance, however, it does require a person to monitor the bot and ensure that it is functioning properly.

UiPath's architecture is simple and straightforward. I recommend the solution.

My main use case for UiPath Platform is to build automations on that, mostly to solve our automation use cases.

I have found many features in UiPath Platform valuable, particularly for financial use with its built-in OCR capabilities for document scanning. We have built automation for automatic bill validation using this feature. Document verification features are particularly valuable.

We have implemented AI integration features of UiPath Platform. We have also utilized the analytics component for tasks such as scraping data for product prices and job postings. Based on the fetched data, we have built automation with AI components.

The code-free automation engine of UiPath Platform saves considerable time by eliminating human intervention. All validations and data fetching are handled by UiPath Platform, removing the need for manual automation. The analytics capabilities of UiPath Platform assist in decision-making processes, especially when comparing product pricing from multiple vendors to determine competitive market rates.

In my opinion, while using UiPath Platform for quite a long time now, I don't see many issues, but for a newcomer, the learning curve is somewhat tricky. The documentation exists, but it would be beneficial to have more video resources covering the new UI and AI features for newcomers who are starting with this platform.

I have been working with UiPath Platform for more than three years.

I would rate the stability of UiPath Platform around eight. It is mostly available, but I have encountered errors once or twice in my career. We have reported these to the team, and they provided solutions. When there is downtime, they inform us about the expected resolution time.

For the scalability of UiPath Platform, we initially served a very small scale, but now we have scaled significantly. For our use case, I believe it's scalable, though I'm not certain about its performance in larger enterprises.

I would rate the technical support from UiPath Platform at ten. Whenever we require support, UiPath team provides direct access to a TAM through Slack. We can directly contact the TAM of UiPath, and they work to identify and resolve issues as quickly as possible. The support integration is excellent.

I would rate UiPath Platform's pricing at four. For us, hiring engineers would cost more, and there would be possibilities of human errors. UiPath Platform helps us reduce these issues, which justifies the pricing.

I am working with the code-free automation engine of UiPath Platform. We have implemented a hybrid model for deployment, with some parts on-premises and most in the cloud. We work with a hybrid cloud architecture using AWS, OCI, GCP, and Azure, though I'm not certain which specific cloud handles particular deployments as this is managed by our DevOps or security team.

Overall, I would give UiPath Platform a final mark of nine points.

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 are primarily looking to solve business challenges related to processing unstructured documents.

Currently, we have not realized the business outcomes as we have not implemented the solution yet. The goal is to increase efficiency, throughput, and accuracy. UiPath AI and automation have not yet helped free up staff to work on other projects or tasks. In terms of environmental, social, and governance solutions, it is not applicable.

The Studio and the Test Manager have been valuable as they made testing with QA easier. We've been able to rerun numerous test cases quickly. From the UiPath platform overall, I find these features valuable.

The product documentation needs improvement as it tends to be self-contradictory and sometimes hard to access since we are on an older version. 

There is also a need for more consistency in product support and customer service.

I have been using UiPath for five years.

UiPath has been pretty stable since we are mostly on-premises. However, the stability is to be determined when we move our full infrastructure to the cloud. Outages could occur with SaaS solutions.

It has scaled with us efficiently despite the initial complexity in understanding licenses, runtimes, and utilization. No significant issues have been encountered yet.

There have been ebbs and flows with customer service. We are at Premium Plus, now called Enterprise Success. Initially, there wasn't much value, but there has been some improvement. Dedicated support provides more assistance and better outcomes.

Neutral

I'm familiar with Automation Anywhere and Blue Prism, each of which offer different pros and cons. UiPath, being the market leader, differentiates itself with its capabilities and portfolio. It is easy to use from day one, flexible, and their vision is helpful.

I can't provide specifics as to ROI. That said, in general, we achieve financial benefits and a positive ROI on our implementations most years.

Pricing and licensing are challenging as they can be difficult to understand. They make it hard to determine utilization and necessary licenses for runtimes. Comprehensive components need to come together for a clear picture, making renewals and contract negotiations complex.

We have considered Automation Anywhere and Blue Prism as alternate solutions.

I would rate UiPath a seven out of ten.

We currently use UiPath to process birth certificates. One of my tasks was to apply OCR to the birth certificates and use a named entity recognition model to extract details like the names of the individuals, parents, and the place of birth. The project requires us to handle certificates from all 50 states, and every state uses a different format. 

We're supposed to be doing intelligent automation, but we're not there yet. I work in the applied analytics and statistics section, and we're supposed to find ways to inject more advanced analytical methods into some of these places where we can automate. Our IT department has a CoE that conducts intake processes. They use Automation Hub to review each process, and the executive governance board votes on it. I don't know how they decide internally because I'm not part of that. 

Automation through UiPath provided a framework and a low-code solution, which generally improved the process. It reduced the burden on the workers, freeing them to do what they wanted. 

It is also utilized in identity governance, especially within IT environments. For example, say I want to install a particular piece of software on my computer. There's a process to request access, and it goes through an approval chain. Ultimately, it gets to someone who has to click a button or provision an account. Someone will get an email and copy-paste the stuff from the email into another system and click "provision." 

And when an employee leaves or switches job roles, they no longer need access to a particular system anymore, so you must remove that access as soon as possible. Automation helps. Governance is one area that we would like to use it in more.

UI automation is helpful for interacting with legacy systems, mainframe systems, and various web applications. Someone might use all those things during their jobs, and many of them don't necessarily have APIs, either.

Although improvements have been made, such as auto-healing, there is room for improvement. Changes in the UI can break automations. If you upgrade from Windows 10 to 11, you may need to rewrite some of those UI selectors completely. That is probably the biggest weakness that I can think of.

I have been using UiPath for four or five years.

The solution can be fragile, but there have been significant improvements over the years. The unified target framework, which considers strict, fuzzy, and image matching, helps to stabilize the application somewhat.

UiPath has been able to perform as our organization grows or as the demands on UiPath increase.

In my previous job, I interacted directly with UiPath support, and they were always effective. Currently, support is accessed through IT, which escalates issues if needed, so I have less direct interaction with customer support.

Positive

I've used Python and VBA and experimented minimally with Selenium, but they're not as strong when it comes to UI automation. I've also used Power Automate for Microsoft products. Sometimes, I want to automate Outlook, but I don't want to ask the security to enable the UiPath activity to pull emails. 

We've saved time and reduced human error. 

I rate UiPath eight out of 10.

Our primary use case for UiPath revolves around document imaging, specifically scraping data off documents and digitizing them. We only use it in our accounting department and haven't expanded it to the rest of the company. We've seen some success with the projects on the financial team, but we might be resource-constrained to get other departments involved. It's hard for them to adapt to new technologies. 

UiPath has improved the accuracy of data entry from our invoices. Processing thousands of invoices is time-consuming. One outcome we've achieved is expanding the data collection from the invoices. They were only capturing dollar amounts, but these invoices have tons of other information that was just going to waste and could be analyzed. Now, we're capturing the data and analyzing it. It will be a significant benefit, considering how we do business.

We've advanced our green initiatives by recycling invoice paper after digitizing it and reduced the costs of pulling this information into our system.

The most valuable feature is the general automation that UiPath offers, especially in improving data collection which allows for a more comprehensive analysis of information on invoices.

There is a need for better autopilot features to enhance the functionality of UiPath.

I have been using UiPath for about a year.

UiPath is stable so far.

UiPath can scale as our business grows.

Customer service and support have been excellent. I would rate it highly for their responsiveness and supportiveness.

Positive

Previously, we used a service that scanned documents and sent them back in EDI format. We switched to UiPath because the previous solution couldn't handle certain document images unless they were in native PDF form.

The initial setup seemed straightforward.

We used corporate for the setup. Corporate used UiPath as a partner for support.

While there hasn't been a financial return on investment yet, the team is happier not having to manually enter invoices, which is a qualitative benefit. However, I foresee a financial return in the future.

UiPath's licensing seems straightforward, and the pricing is comfortable for the corporate leadership. They made an outright purchase, knowing the full cost and expectations.

I rate UiPath 10 out of 10.

We primarily use UiPath to move data and consolidate data formats efficiently. We are involved in claims management within healthcare. We are also exploring DevOps tooling and CI/CD pipelines, and automated testing.

UiPath has significantly improved how we claims. We provide this product for our customers directly, so we want to ensure they reap the benefits of the automation program. We serve as a product team and make sure that our products are directly open to the customers. Although we are not extensively using AI yet, there is significant interest in the org. We aim to recommend automations to users and intend to develop AI capabilities down the line.

Our teams are heavily using integration service, especially following our cloud migration. Having further insights and program visibility is crucial for longevity.

It would be helpful to be able to double-click and drill down into the data we see in the APIs and get a little more interactivity, especially in the Studio and Studio Web. I want to be able to pull in fields dynamically.

I have used UiPath since 2021, so it has been about three years.

UiPath is relatively stable. I've seen a few bugs in some of their newer tools and Integration Service. There are some issues with feature clarity across platforms, but it's not necessarily a stability problem. Occasionally, cloud may experience downtime, but stability is always reliable. 

Most of the scalability issues from an implementation fall on the customer's side because they don't understand how to scale out their VM presence or set up systems in a way that relies on siloed teams. They're using it on-premises and have to manage the instance with teams outside of their automation team. I haven't had any scalability issues in the cloud. The cloud might go down once a year, but I haven't had issues scaling it, and if it has an outage it's normally not long enough to make a dent.

I rate UiPath support seven out of 10. UiPath's support is quite reliable and significantly better than most alternatives. Some competitors don't get back to you or have meaningful solutions.  

There's room for improvement. They could make their online support pages easier to navigate. They're integrating support with Automation Cloud, which will make raising a ticket more seamless. When you open the ticket, it should automatically provide them information about your deployment.  They're good about following up with you, but getting solutions for some products takes time. 

Neutral

I have always worked with UiPath, sometimes using other platforms such as Salesforce and Power Platform when they better fit specific needs. However, they are not as suitable for making enterprise scale automation.

The on-premises deployment when we started in 2019 was somewhat complex. It's different for every customer, whereas the cloud is consistently distributed the same way, and you can customize it for your business.  

We work with an implementation partner for staff augmentation and architectural support, with a proactive offshore development team experienced in best practices. 

I rate UiPath eight out of 10.