What is our primary use case?
We do workflow automation for some of the functions such as form-filling or filtering data accession on the client's web application. We use UiPath RPA for data accession and other processes. We have done workflow automation that:
- Opens a client's website.
- Filters out the current data.
- Lists out all the records that need to be processed.
- Opens each record.
- Enters the details gathered from a spreadsheet or somewhere else.
- Submits the application.
It does that for all these users that have been filtered out. That's why we're using UiPath.
How has it helped my organization?
We're able to automate manual processes and save the effort of our employees. We're also able to save our and our clients' time. With these automations, we could also save the time of healthcare workers and patients. For example, we did automation of insurance claim processing, and based on the feedback that we received, they said that insurance claiming is safer and faster as compared to the previous manual process. For example, previously, if they were processing 100 insurance claims per day, they can now process 250 to 300 claims with automation.
UiPath helps to implement end-to-end automation. We don't have any tool other than UiPath for automation. We build the bot through UiPath and run it on the client's application. We don't have any other automation tool. This end-to-end automation makes up 95% of our business. End-to-end automation is the only thing that we're doing in our current company.
When we started and got our angel funding, we planned to build our own RPA tool for workflow automation. We did the development for almost six months, but we faced a lot of issues. We then decided to use a top, third-party RPA tool. So, we decided on using UiPath. We now have seed funding. UiPath was a savior when we were starting out. Otherwise, we would have faced a lot of issues, and even the company might not have grown without UiPath. UiPath has helped us a lot because they have years of experience building the RPA tool, and they have a lot of features to make the development process smooth.
We have been using NLP for understanding the signature in one of our documents. We just want to get the text out of the documents that have been uploaded to our claims application. For this, we use the UiPath AI functionality. If UiPath doesn't have the AI feature, we might have to get help from the cloud vendor providing AI, but because the AI is built into UiPath, it supports document understanding or language analysis that we're doing. Because AI is integrated with it, we don't have to learn anything, other than UiPath, to get the task done.
One of our workflows is extracting text from images and PDFs. We use UiPath document understanding for that. If they didn't have this feature, we might not have been able to create a workflow for the client for running a process. UiPath has helped us implement more workflows and do more processes.
UiPath has definitely reduced human error. We did have some unattended automations with UiPath but not everything can be automated. Some issues might arise that need to be resolved by a human, but 100% of the things do not need to be done by humans. Because of that, human error gets reduced. For example, we have thousands of documents that need to be classified based on the text they have. If we give that task to humans who have to handle more than 20,000 documents in a day, they will get exhausted and might make errors in classifying the documents. With UiPath automation, it can be done without any human errors. It definitely reduces human error.
UiPath has freed up employee time. The workflow automations that we have done save the time of our employees and our clients. We save approximately two to three hours per day per employee. In a week, there are 10 to 15 hours, and per month, it comes out to be about 100 hours.
UiPath didn't save the cost for us because we're not using UiPath to run the workflow. We just build the workflows and give them to the clients, but it has saved the cost for the clients. For us, it reduces the development effort. It has a lot of tools to build applications.
What is most valuable?
When it comes to UiPath, the custom robots that we can run in an EC2 instance and the on-premise support are valuable. UiPath has cloud as well as on-premise support. We have some companies that ask to run the application on our own server, so we just install UiPath in our own system and enter the UiPath key. We're running it on-premises on our own bare metal server. We can also do asset management where we can store the credential for the client's application that will be used in a runtime environment. We like credential management.
We also have queue support in UiPath. We can just put the data in queues, and it'll be processed in a transaction manner.
With UiPath, development is easy because they have their own Studio. We just run UiPath Studio, drag and drop the components that we require, and connect all the dots. When we're doing website automation or web app automation, we can use their UI-based Studio and grab the elements from the web application using XPath, which makes the development easier. However, for that, the initial setup is required to be done in a certain way. After we have done the setup, which includes running UiPath Studio and connecting the robots, everything is easy.
We did the UiPath courses for onboarding. We onboard many developers regularly, and every developer has to complete the course before getting started with the development. UiPath Academy was useful for learning about UiPath and getting started with the development. If we had started development without UiPath Academy courses, we wouldn't know which tools are beneficial for which use cases. Otherwise, we would've ended up using unwanted features for the use cases, which would have increased the development time. UiPath Academy gives us a list of features and tools. We get to know which tool would be suitable for a particular use case. This way, it reduces the development effort.
What needs improvement?
In the UiPath Community, a few questions get resolved and a few questions remain unresolved. UiPath has a big user community, but it needs to grow more. For example, during development, we might face some hurdles or hiccups while doing some of the tasks that we don't do on a daily basis, such as executing some API calls and getting some data. We faced some issues related to that, but when we searched for or asked about such issues in the UiPath Community, out of 10 questions, five to six questions remained unanswered. We had to resolve them on our own. So, UiPath needs to improve its community. They can offer some kind of reward for answering the questions asked in the community.
It would be helpful if UiPath could provide developers to help us with the on-premises setup. Without that, we have to figure out how we do the setup.
Its cost could also be better. We need to have a license for every robot, and it isn't possible for us to be able to run UiPath in our on-premises environment based on our usage. Even if we need to run a robot for an hour, we need to get a license for one year.
Buyer's Guide
UiPath Platform
July 2026
Learn what your peers think about UiPath Platform. Get advice and tips from experienced pros sharing their opinions. Updated: July 2026.
908,877 professionals have used our research since 2012.
For how long have I used the solution?
We have been using UiPath for three years.
What do I think about the stability of the solution?
UiPath has good stability. They have monthly software updates, but they haven't caused any issues with our system. We didn't face any issues so far because everything runs smoothly. It's 99% stable.
What do I think about the scalability of the solution?
UiPath is scalable. Because our setup is on-premises, we manage the Orchestrator or Studio as our own. When it comes to running the bots or workflows, every time we want to run more automations, we just buy a new robot and attach it to the pool. They run smoothly. UiPath is 95% scalable.
We have about 200 users using UiPath. It's deployed at only one location.
How are customer service and support?
I've contacted them. They're definitely helpful. Whatever issues we have had, they try to debug and resolve them as soon as possible. They're good. I'd rate them a nine out of ten.
Which solution did I use previously and why did I switch?
We didn't use any other solution previously. We started with UiPath.
How was the initial setup?
It's on-premises with the AWS-managed cloud. While setting up the on-premises environment, UiPath documentation helped the most. Without that, we wouldn't have been able to set up the on-premises environment. We had the help of the DevOps team for setting up UiPath with AWS services because we ran our UiPath environment in the AWS cloud in our account. For 60% to 70% of tasks, we used the UiPath documentation, but for setting up the reusable services and scalable machines, we had to take help from the DevOps team for the setup. If UiPath had a team to help us set up the instance in the cloud, it would have been better.
It definitely requires maintenance. They have a monthly patch for the features and software updates. We need to install those patches. We have two to three people who are involved in maintenance.
What was our ROI?
We have definitely seen an ROI. We're investing a lot in the UiPath license. It gives us two to three times more than what we invested. We're giving the workflow solutions to clients, and they're giving us the money for the workflows that are running. The UiPath is running smoothly, and we're getting two to three times more than what we invested in UiPath.
Which other solutions did I evaluate?
We thought of Automation Anywhere and IBM RPA. That's all. These were the ones for which we planned to do a PoC and evaluate.
What other advice do I have?
I'd advise going with the cloud version of UiPath instead of the on-premises environment because it'd save the development effort and the setup time and cost. In the cloud environment, you can also run the bots on a usage basis. Going with the cloud version of UiPath would save a lot of time.
Overall, I'd rate UiPath a nine out of ten.
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.