What is our primary use case?
I create robots for clients of our company. We have an insurance client that asked us to help with sending letters by email and extracting documents related to insurance, between their insurance agencies.
We also do e-signatures using an API with a server to get digital signatures for all the customers of a bank. And with other banks, we have worked on onboarding clients. We have all the information about them and we do subscriptions for them.
We also have a lot of clients that ask for filters and updates in Excel files.
How has it helped my organization?
Employees who were doing the same tasks every day are happy to have time to do innovative things and stop doing tasks that a robot can do. They feel free from those unwanted tasks. These kinds of tasks are often boring, and employees can make mistakes. They spend a lot of time doing them without any benefit, because it's something they do every day. There is no innovation when they have to do those tasks. The most important part is that we can help employees in these situations.
The benefits include managing employees' time. A robot can work at night or even on the weekend, whenever you schedule it to run. It's helpful because employees can let it do their jobs when they are at home. There are also fewer errors because when you give a robot a formula, it does all the iterations in the same way. Even if there is a special situation or an exception, the robot can help itself get through it. So it helps with an employee's time and efficiency, and they are happy about that.
There are two kinds of robots that we deliver. One type of robot works independently, giving our client's employees time while the robot does its work. And there are other robots that do work but need a human to verify things. But even that type of robot reduces the work, leaving only the validation.
And when we start discussing RPA with a client, we can see the difference in the costs. We ask them how much they spend on a task or how much time it takes, because even hours have a cost. We then give them the difference. If a robot does that task, it will spend X amount of time on it and you will save this much money. It depends on the project, but sometimes we save them 30 or 40 percent of their time or even more.
What is most valuable?
The scraping for data extraction is very important. There is also a connection with all Microsoft tools, like Outlook, Excel, Word, et cetera. And OCR, the Document Understanding feature, is important because we have clients that ask us to read data from scanned documents.
UiPath Orchestrator is also important to help us schedule our bots.
In addition, UiPath is a low-code solution, which is very useful and helpful. Given the features and solutions it offers, it's quite easy. The ease is a seven out of 10, or even more. The challenge for us is connected to the demands of the client. Sometimes we work with banks, sometimes with insurance companies, and the challenge is to know what they really require before we start developing. We need to know the exceptions that we might face. But the development part is quite easy thanks to the UiPath Academy and the forum. It's not that hard.
We can even teach our clients a little bit about the use of the UiPath. It's easy and doesn't require an IT engineer. They get excited to use it.
I started my use of UiPath with the UiPath Academy and I'm still learning there because there are updates and new features to learn about. The Academy is very helpful with its videos and explanations, and with the questions at the end of the lessons. I like that it allows me to learn on my own time. It's very constructive because things are explained well and I like that I don't have to be at a school to learn it.
Also, the UiPath community is very good. Anytime I have a problem, or something blocks me, I post a question on the forum and people spend a lot of time helping me. Even if the first solution doesn't work, they come up with another one. When I started working with UiPath, there were only a few people who knew the platform and I had to wait days and days to get an answer, and sometimes I wouldn't get one. But over time, I feel the difference because there are more people in the community and they are more responsive and very helpful.
What needs improvement?
We have the new license, the Flex Plan with Automation Suite, but we don't have practical examples and we have found it a little bit difficult when dealing with it. We could use more specifications about it and practical examples. Sometimes clients ask us questions, but, even on the UiPath forums, we don't have answers. We have to spend a lot of time trying to find them. Practical responses about installations and the differences between the kinds of installations would be helpful.
Buyer's Guide
UiPath Platform
August 2026
Learn what your peers think about UiPath Platform. Get advice and tips from experienced pros sharing their opinions. Updated: August 2026.
914,109 professionals have used our research since 2012.
For how long have I used the solution?
I have been working with UiPath for almost three years.
What do I think about the stability of the solution?
It's very stable. I haven't faced a problem with UiPath Studio. I would give it a 10 out of 10 for stability.
What do I think about the scalability of the solution?
It's scalable. I would rate it a nine out of 10 on this aspect.
How are customer service and support?
I have needed their help too many times but they have been so helpful. They respond with emails, and sometimes I even talk with them on Google Meet. They are responsive.
How was the initial setup?
We have worked with UiPath on-premises, on Azure, and on a private cloud. That's where we use it the most. An on-premises setup is easy to do, and on a private cloud, it's not complicated. But with the Automation Suite, it is complicated and we asked UiPath to help us.
When we deploy it for our customers, we ask them to prepare the production environment for us so that it is already ready. For deployment, we have an architecture and an infrastructure engineer. Sometimes we need the infrastructure engineer if something is complicated about the infrastructure. We work with the IT department of the client and our infrastructure engineer.
For unassisted robots, we take the robot from the development machine or the test machine to the deployment machine. For clients using Orchestrator, we create the robot, the job, and we execute the robots from Orchestrator.
Maintaining UiPath is not difficult. One engineer can handle it, for now.
Which other solutions did I evaluate?
I did some research on Power Automate, but I haven't worked with it. I only saw the interface and some examples. We are planning to learn more about Power Automate and the differences between it and UiPath, but for now, we are only working with you UiPath.
What other advice do I have?
My advice is to use the UiPath Academy and do some practical exercises. And when working with your client, ask all the questions that you have, including exceptions and real cases. Technically, everything is good. Just attend the Academy and use the forums and everything will be okay.
Disclosure: My company has a business relationship with this vendor other than being a customer. Partner