UiPath Reviews

We are a services company. In terms of how we use UiPath, we handle a lot of the financial processes, including our customer billing, our time tracking, and our time reporting exceptions - such as looking at who has not submitted a timesheet. When this exception happens, there are automatic emails that go out using the RPA, from UiPath. 

The whole process from our inventory, which is our asset, is automated. With the asset, which is the time that our people spend on clients, we make sure that we capture what we need to create and send invoices out. The whole collection and AR process, including making sure that we get the money and send reminders to clients, that whole process, is automated - with human intervention, as needed.

The solution has decreased the processing time of the client's invoices for IT. Just IT. Not the rest of the organization. That said, just there, that’s 600 hours of annual savings in one department. On top of that, we’ve decreased processing time by 90%.

The automation cloud offering helps to decrease the solution's total cost of ownership. More than that, it creates agility so companies don't have to worry about delivering the infrastructure team and setting up sellers and all the things that they need to do to get to the stage of actually installing the software and internal security. That all takes time to go through. With the cloud, you avoid all that. You basically create agility for the clients to jump onto automation and not wait for all these things. It can be frustrating sometimes in large companies. That's why we tell clients to avoid all these headaches. With the cloud, you’ll get going very quickly within a matter of a day or so.

RPA is not the only thing we do. We do a lot of ERP, CRM, all of these things. Traditionally, we are a full-service organization for clients and their journey to the cloud. Everything's going to the cloud. There are some organizations that still have on-premise ERPs to migrate from the on-premise to the cloud. When those fundamental applications are going to the cloud, automation is a no-brainer. We would always promote the cloud version over on-premise.

The RPA is the most valuable aspect. The power of machine learning and AI along with the document understanding capability that UiPath has is great.

By implementing that portion of the solution, we get clients to 95% accuracy in reading invoices for processing into the ERP. While running basic automation will continue, the world is moving towards intelligent automation, which is with all the machine learning and AI.

Overall, the solution has saved costs for our clients.

It has reduced human error. Machines can do anything faster, cheaper, and of a higher quality than humans can do. That is just a universal fact. I don't think we have measured the accuracy, however, there's no doubt accuracy has gone up. The client recognizes that the accuracy rate has improved.

We're not talking about removing errors. In some cases, errors may happen. However, when I say we’ve seen a 90% efficiency rate, it doesn’t mean the remaining 10% are bad decisions. We're talking about how it could not read those things. The confidence level is low, and therefore, it's kicked to a human to review. It did what it's supposed to do, which is to flag for human review, which is how processes should happen.

The solution has allowed the employees to focus their time on other higher-value work. That's what we pitch to our clients. We never tell clients that oh, you can lay off people. We do not tell the clients that that's what they should do. Rather, we advise clients that what they can do with automation is free up people's time. That means either freeing up a portion of the time or fully freeing time or completely reassigning a job. 

After automation, you may have to reorganize your department. However, with the freed-up time, departments can focus on the most important thing, which is what can they do to create focus on the customer and create an experience for the customer, where the customer feels they want to be connected with your brand.

I have a case where I was talking to the CEO of a big restaurant company. HR, payroll, finance, all those areas that reported to him. He also handles customer experience. I told him about automation and the power of automation and how it will free up people's time. He said, “So what you're telling me is I can free up a portion of my staff so they can focus on all these customer complaints we're receiving?" For him, that is going to be a game-changer.

UiPath has also positively affected the employees themselves. They've become a little bit more satisfied with knowing that they can focus their time on higher-value work. In most cases, initially, there'll be fear for them. They don't know what automation is, and why they're doing it, and what it's going to do to their position in the company. That fear will always be there with humans. That's why leadership needs to focus on change management and communication. Those things become very, very important. Once you do it right, people will actually feel happy. They will no longer have to say "Oh, no, I don't have to stay until six o'clock, seven o'clock every day to finish the SaaS." Now it's much easier. They can focus on the things that they truly enjoy, which has nothing to do with the heads-down work that they do all the time.

We use the solution's AI functionality in our automation program for our clients. For simple processes, you don't need AI. However, the complex process where machines need to mimic the human thought process requires AI. AI is not perfect. It's not a holy grail that is going to solve all problems. That's not the case. We have to be careful. However, if you use it right in the right way, then you can truly solve complex problems.

I’m not sure if the solution's AI functionality enables us to automate more processes overall. It's hard to say. For me, the way I look at technology is that it is not a hammer that's looking for a nail. You have to look at your business needs and then figure out what technology will best fit or solve the problem. It could be simple AI, or, maybe in some cases, you need more advanced AI. I would look at it as what's the right technology for what purpose. That's the way I look at it.

We do use UiPath’s Academy. We have several people that we've pushed through training and certifications through the academy. It’s helped get those employees up to speed on the solution.

Also for us, as we are a services company, that gives us a stamp of quality seal in order to market our services better as we are certified and qualified.

UiPath continues investment in machine learning and AI. That's one thing they have to do. The fundamental thing UiPath needs to understand is the competition, the market, is not Automation Anywhere or Blue Prism. Rather, big competition is coming from Microsoft.

It's around the corner and Microsoft is going to come in a big way. I’d advise them of the parallel of Power BI. Power BI three years back was not a good tool. Other tools, like Tableau, were the kings of the BI space. Fast forward three years and today we do a lot of BI for clients. Almost every client of ours is migrating to Power BI, like Power BI's matured to 80% of Tableau, and that's good enough for them. On top of that, Microsoft was throwing free licenses to their customers. When you do that, versus buying $2,000 a pop or $1,500 a pop from Tableau, users line up behind the free tool to reduce their costs. Microsoft is doing that with Power Automate now. I just talked to a client, a big client, a $10 billion company, where they were at Blue Prism. They just told me that Microsoft just gave them 70 free licenses. Now, they are forced to bring Microsoft Power Automate into their RPA strategy even though before, they were not considering that.

UiPath should take several steps forward to be prepared for this competition and create differentiation with capabilities that Microsoft does not have. The innovation within UiPath is going to be very, very crucial. However, the most important thing is to clear the differentiation in the messaging. That's very, very important. They should be ready and arm their partners with information about why UiPath and not Power Automate.

I've been around the industry for 35 years, and I've seen lots of incumbents getting blown away in various technologies at various times. The big power comes down hard. UiPath has got to be ultra nimble to not get crushed.

We started working with UiPath in 2018. We partnered with UiPath in late 2018. It's been about a three-year journey so far. 

In terms of stability, I've not heard anything bad at my level. That means no bad news is good news.

We do plan to scale beyond the client's IT department and to the rest of the organization. When they scale it up to the rest of the organization, and this organization operates in 25 countries, they have over $190 billion in assets in these countries that we can add efficiencies to. The scale of efficiency that we will get with what we did will be huge. That’s the next step is to roll it out to the rest of the organization.

General scalability is an issue when it comes to processing large data sets. However, with the right creativity, you can solve those things due to the fact that you can have the right infrastructure to catalyze or do whatever you have to do to create scalability. We are used to doing that. We deal with ERPs and we create architecture and design the environment in such a way that it can scale. That said, you need to know how to do that. 

Technical support is very good. We're very pleased with that. When we ran into problems with a client, with the document understanding, initially the success rate was not very high. Then we had to reach out to the support and they actually jumped in and assisted us and told us what we needed to do. Once we did that, then things took off and we got to 90% accuracy. Initially, it was only 50%. Therefore, for us, it's been good.

We did not previously use a different RPA solution.

We did partner with Automation Anywhere,, however, ultimately, we didn't do anything with them.

The initial setup is straightforward.

We're a consulting company, and we work with several clients. For some deployments, we were able to do the first deployment in 30 days. With other clients, it took about three months or four months, depending on the use case or the initial use cases that they picked.

Different companies operate differently. I always advise clients that they need to pick simple use cases and deploy them first before they go into complex stuff. Sometimes clients make the mistake of picking their most complex use case and say, "Oh, let's try that." No, that's not a good way. It's not a good way to embark on a journey that's long-term.

You've got to think big, start small, and be agile. If you get a complex use case at the beginning, you lose agility.

We looked at Blue Prism, Automation Anywhere, and UiPath. The momentum was with UiPath. I knew where the momentum was and how we needed to align ourselves. That's why we did UiPath.

We looked at where the market demand is. For example, Blue Prism. We knew that Blue Prism is a lot more IT-centric, IT heavy, programmer heavy, which defeats the whole purpose of self-service automation. It's never going to succeed in the marketplace today as we promote self-service for everything.

That's why we didn't want to waste our time with Blue Prism. UiPath obviously has the community edition, which was brilliant. Basically, they saw a gap in the market. That's a parallel to what we do, for example, in Vtech space. Also, for example, Tableau is a good tool. So many people love Tableau. They've used Tableau. You had the established players in BI space like MicroStrategy and Oracle OBIEE, however, they were very IT-centric and Tableau came in and beat them. They sold out into the business and you could download, pay $2000 and download a license and start creating your dashboards. I was glad that UiPath took a similar approach by creating a community edition, and then letting end-users download and then play with it.

We basically help clients think through their RPA strategy, their automation strategy and figure out what the right technology would be. We are a reseller. If it makes sense, we'll resell and we'll advise clients regarding UiPath for their RPA journey. We also use the solution ourselves. We have automated certain things, certain processes within the company. That becomes a practice round and a learning ground for our people so that when we go to clients, we can take some of these ideas and do to the clients as well as reaping the right expertise.

I'm not sure if we are using the UiPath apps feature or the applications feature. In my role, I just lay the strategy and the team executes it.

A lot of times things stall. In company setups we see a lot of cases where they did a few automations, a few bots, and then things stalled. That's a problem in the industry and the way to solve that and truly embrace the art of the possible is with automation. To get there, you need to execute across senior leadership. Without that education, they just don't put their weight on their departments to do the journey. Education is one thing that is very important. They understand the art of the possible.

Another important aspect at the outset is having RPA as a corporate strategy. Pushing to make it a corporate strategy is really going to help. That way, you can stall it for some time, however, eventually, it will have to get done. Otherwise, they are left behind when your competitors take advantage of the agility. There needs to be a center of excellence and companies need to develop internal capabilities. If they don't have capabilities, then they fear not knowing how to handle something. Those are common problems. And those need to be overcome.

I'd rate the solution at a nine out of ten.

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 are developing processes with UiPath for clients in the government and banking sectors. 

UiPath is flexible and has various automation capabilities. I like PDF automation, and we have multiple other tools, such as the AI Center and Document Understanding. There is more than one way to automate the same process. We can broaden our experience and use our imagination.

UiPath facilitates our digital transformation. We have an auditing team for our client that was manually collecting data every month from eight websites across different Indian states. We also have to validate the files we get. It takes a person three days to do that manually, but UiPath automation allows us to complete the process in a day, and it's more accurate. There were no errors, which is what the audit team requires. The banking sector is undergoing changes, and by using automation, the banks are improving.

The solution reduces human error in cases where we have Excel automation invovling some formula that needs to be copy-pasted, or we need to fetch the data from PDF to Excel in a particular column. It's easy to make a mistake when both keys are next to each other.  For example, we may make an error while writing "S is equal to A," and we might ignore it. A UiPath bot will perform that without making an error. If the process is properly designed and trained, we'll get the correct output. 

I appreciate UiPath's ability to automate complex processes. It's the best thing. The Action Center, Document Understanding, AI Center, and all the other components of UI Path are also good. I prefer UiPath over other automation tools.

It's easy to build processes in UiPath. I am from an engineering background, but UiPath is a low-code solution, so it's easy for a user with a nontechnical background to understand.  It's simple to explain things to business users. If I need to explain things to my clients, it's easier for them to understand how UiPath works. 

I have developed multiple end-to-end processes, including SAP, web automation, Excel, Outlook, PDF, and directory automation. For example, we might extract the information from the PDFs in a folder. A recent one involved invoice process automation. Invoices for rent and expenses needed to be processed for nine websites, which were automated in UiPath. It included SAP, web, and Excel automation.

The UiPath community has been helpul in cases involving clomplex logic. By getting in touch with the UiPath community, we could see all the new things that have been developed or released in the latest versions. We have community meetings. 

I've also obtained multiple certificates through the UiPath Academy. There are foundational and advanced courses. I was certified in solution architecture, fundamentals and methodology, SAP automation, administrator automation, AI Center, and Document Understanding

The time needed to learn UiPath depends on how much time you're willing to spend practicing. I completed the UiPath foundational and advanced courses in a month because I was working on it day and night, practicing with the different tasks we got online. Some of my colleagues took three or four months.

We use UiPath's AI features for Document Understanding. We have to train the AI model repeatedly so that it extracts the data correctly from the PDF. We correct it when there are mistakes so that it trains the model. Similarly, we have the AI Center, where we can choose from different models available from the UiPath or create our own.

A lot of the UiPath processes are capturing information from government websites. It's difficult to capture the correct format, so we need to use a third-party application to capture the information correctly. It would be better to have that capacity with UiPath, so we don't need another product. 

I have used UiPath for more than two years. 

I rate UiPath seven out of ten for stability. The stability varies from machine to machine. If you have enough RAM and CPU, it should be fine. Sometimes it lags on computers with older processors. I'm using an i7 11th generation, and it works perfectly fine. Also, sometimes there are issues in new versions, but it runs smoothly in the latest stable version. 

I rate UiPath support seven out of 10. The response speeds and the solutions they provide are excellent. I have contacted them multiple times to open up cases. Recently, a URL was not working due to some architecture issues, and they responded within two hours. 

Neutral

I have done one process on Automation Anywhere, but it was only an Excel automation.

The implementation varies from process to process and the availability of the process team. I have done processes on various timelines. It sometimes takes a week if the process is small. A few took around three or four months because the scope was larger. It covered 10 to 12 human steps and involved manipulating data in SAP and Excel. It doesn't take as long if it's a simple process that involves moving a PDF, copy-pasting, or bulk emails. It depends on the process length and the testing needed before we can move the process into production.

I handle the deployment because the infrastructure team does all the installation and orchestration. I have admin access, so I can publish and upgrade packages and maintain the licenses, machines, bots, queues, etc. It is all published in the Orchestrator and run on the production machine. Maintenance is required of ther are changes in a URL or some input. 

I rate UiPath nine out of 10. UiPath's license costs more than other tools, but once it is all set up, it's easy to use and is effective at multiple types of automation. If you don't have experienced developers, you can learn to use the UiPath Studio to develop some basic code.

I am a consultant working on RPA solutions in general. UiPath is one of the solutions that I am using.

The use cases depend on the clients. I have done automation of sending mail with invoices in it. We have used it for analyzing PDF documents, getting information out of these documents, preparing in three different languages depending on the client, and sending invoices by email.

We are also checking VAT numbers on the EU side to validate the client's VAT numbers and related data. We have automated the generation of reports out of SAP for two different managers and teams. We have also automated including specific signature images within PDF documents and sending them to the related service or email address.

We have mainly used UiPath to focus on processes related to the finance department. The targeted processes are the ones that are the most repeatable and require a lot of effort but there is no real focus and attention from the user. Because of its repeatable nature, the risk is that users do not pay attention to the process itself and make mistakes.

Generally, we do not implement end-to-end automation. The idea is not to automate an end-to-end process but to automate a part of the process that takes a lot of time and resources. That is the focus point, so it is not a matter of having an end-to-end process implemented. It may occur, but often, it is a part of the process where the focus needs to be reliability or time and resource consumption.

The benefit for our clients is time and reliability. They quite often see the benefits in terms of the reliability of executing the process, even reporting mistakes or errors that happen during the execution of the process. That is something quite valuable for them.

Usually, it takes our clients at least one month to realize the benefits. If the processes are executed on a daily basis, then it is quite fast, but there are processes that are triggered every month or every quarter. In that case, it will take at least a month or a quarter to see the benefits. Once it is executed, there is quite an immediate benefit. On the other hand, it takes time to analyze the process because often processes or procedures that are written are not in sync with what is executed by the user. We have to modify them. Often, by questioning the end user, you end up finding the shortcuts and implementing them, so the analysis takes more time, and the implementation takes less time.

UiPath reduces human error. That is one of the main reasons why automation is done for customers. Two main reasons for automation are reliability and resource availability. 

UiPath saves time for our customers, but it is hard to know how much time it has saved because it varies from process to process. For example, the process of validating the VAT numbers on the EU website used to take two or three resources every quarter, whereas now, it is reduced to less than half an hour. These time savings are valuable, but the added value is reliability.

UiPath has not had a lot of impact on the digital transformation because the processes that are requested to be automated are already digital. The reason for automation is to speed up the process or make it more reliable. There is no real impact on the digitization of processes.

In terms of the reduction in the on-premises footprint, I am not always aware of the eventual use of the processes that I am implementing for the clients with the bots. I see that some of the bots are not used anymore because they have their own application that includes a big part of what has been automated on their side. It depends on the way they use it and how often they use it because I have bots that are running every day, and I also have bots that are running once a quarter. The ones that are running every quarter are harder to evaluate because people are not always able to see the resources released from executing those processes. Because they are executed every quarter, they are usually not measured. Our clients generally go for automation for reliability.

Specifically in the recent versions, the ability to change the interface is valuable. One of my clients had to upgrade the SAP version and move to a web-based UI. This was handled by isolating the UI interaction within the library for the targeted SAP on the client side. I upgraded that library to handle the web-based, and the bots worked fine after that without modifying anything in them. The usage of libraries is very important for me because it helps a lot in this kind of upgrade, specifically because SAP is used across the company. It is impacting a lot of different businesses within the company.

It is quite intuitive and fully handled by a visual interface. It is no big deal for me. I have been a developer in the past, and I have used Visual Basic and C#. If I need to specify something exceptional, it can be done. It is not a big deal. For me, it is very easy. There is a competitor with an open-source solution called OpenRPA, but for me, UiPath is far better and more intuitive.

There should be the ability to customize the building blocks instead of having to specify everything in every step. We should be able to combine these building blocks to make specific processes faster.

There should also be some kind of templates, similar to Power Automate. Power Automate provides templates for a specific context.

I have been using UiPath for two and a half years.

I am absolutely satisfied with its stability.

I did not have to worry about it so much because usually, my clients want to take control of their bots. They want to execute it when they want, so I have had no experience with the scalability of UiPath. 

I have not contacted their support. When I am developing, I try to make a bot quite stable. I am aware of what is happening and what it is doing, and I can notify people with logs or names of different events that are occurring during the process execution. I know exactly what is happening and where. It is quite easy and fast to diagnose and fix if there is an issue, but it is not often that I have to intervene in production. If a process is designed correctly and safely, not much intervention is required. Clients look for this kind of stability because that will save the time that they will have to spend fixing things in the production environment.

They have a UiPath Community, but I have not used it often. If there is something blocking, I go over there, but generally, I find the solution to the issues through my colleagues.

It has always been on-premises. The setup is quite straightforward. If there is some kind of Orchestrator to be installed, it is more difficult, and it takes more time. Usually, they want to have someone internally to handle the Orchestrator. I am more focused on the bots and the triggers for these bots to be executed. I am not that often involved in the implementation of the infrastructure of UiPath for the operational side.

Bot development duration varies. It depends on the process, but it can take a few weeks to several months. I have bots that were developed in two or three weeks, and I also have bots that took at least six months because they were quite heavy and complex. Generally, it does not take longer than that because then it will not be as valuable to the clients. If it takes more than six months, it is better to have it developed in their own software.

Bot deployment is quite straightforward for most of my clients because, during development time, I take care of environment parameters. So, deployment is quite straightforward. It is a matter of deploying and pressing a button to have the package deployed. We then set parameters in config files, but it does not take a long time to have it deployed.

Bots usually do not require any maintenance, but if the source of data has been upgraded or modified or the UI has been modified, they might require some maintenance. Usually, once the process is running and every source is stable, there is no need for maintenance. When the data source changes or the infrastructure changes, such as the main server being moved or renamed, then there is a risk over there, but it is not a big deal to adapt.

Generally, two or three people might have to investigate the cause of the issue. If the issue is inside the bot, it is not a problem. One person is enough. If it is related to external data sources or infrastructure, it may take two or three people depending on the segmentation of the clients' people in their departments and services.

I do not know about the exact price because I am not selling anything. I propose several solutions to the clients, and the client does choose one of them. If UiPath is chosen, they contact the official reseller in the country. In one case, I had the prices in front of me, and it was not expensive for the service it was providing.

I would recommend it depending on the needs. UiPath can do a lot of things, and I have covered only 20% of UiPath functionality. Based on my experience and the needs that I had so far, UiPath has been quite valuable.

I would advise defining your use cases. That is the rule for everything. Once you have the use cases analyzed, you can specify what is needed, how you would do it, and what is the best solution to have it implemented. One thing that I am doing is that I am mixing solutions, where, for example, UiPath interacts with Python processes that I have developed. Python processes provide information in files. Web scraping is not difficult in UiPath, but it is quite heavy. In Python, it is faster to develop and use than with UiPath. It also depends on the number of iterations and resources available to execute it. It is a matter of the quality of a particular functionality in UiPath. UiPath relies on the .Net framework, and it has its own limitations. It has quite a heavy set of libraries and frameworks. It is a matter of balancing what you are expecting of it.

I would rate UiPath an eight out of ten. It is a good product. It is well-designed and well-executed.

We're a tech consulting company that works for insurance companies. We use UiPath for tasks related to payment processing, deductibles, and denial of coverage. We check each part of the process to ensure that the patient has met a set of criteria. We're checking the deductible to see if it has been met, and we update the notes on the platform. UiPath is useful for all of our clients regardless of the industry. For example, we have used it for payroll and payment processing at Citibank and Doshi Bank. 

A bot can run 24/7, reducing the human labor required. That is UiPath's major advantage. It reduces the number of manual tasks while also improving and enhancing human labor. A manual task that took 10 minutes in the past can be completed in two or three. We are saving a lot of time. 

Let's say we have eight people doing a particular task eight hours a day on a five-day work schedule. Once we automate that task, we can run the bot 24 hours a day Monday to Sunday. Automation reduces our costs and human error. The accuracy and data security are high. It's beneficial all around.

Uipath facilitates data sharing between systems. We have some shared folder packs that enable us to share the data from one system to another. This functionality can be important, depending on the project and type of data. We use some encrypted features. If we want to share data in encrypted mode, we can put it in an Orchestrator folder on-premises so only those with access can see the data. 

The business will share the data, including employee and patient records. All the data is shared within the database.  Either the employees can send data over, or they can access the data from that particular folder. UiPath offers a central portal for managing patient information. We've done a lot of things to extract and utilize patient information, ensuring that it can be accessed by the appropriate teams. We have to train our bots to capture the right information, like the patient's name, address, ID, location, etc.

UiPath is good for data scraping and extracting information from websites. UiPath is approachable, and it makes life much easier by automating repetitive tasks with the help of drag-and-drop flexibility, eliminating human interaction. The drag-and-drop APIs make it easy to get data from the API quickly.

I also like UiPath's security features because it gives us lots of tools to secure sensitive information. We can encrypt the customer data and store it in UiPath on-premises. We can also control access so that only authenticated users can obtain the data. 

Citrix and email automation could be improved. We can use the features, but the accuracy isn't 100 percent. 

I have used UiPath for the past five years. 

I rate UiPath support eight out of 10. They provide us with assistance while we are developing bots. We can send the Orchestrator logs to UiPath to find out where a process is failing. For example, a web-based process might be using an old particular password. The support team will notify us that we need to update the password in the production environment. 

Positive

Before we implemented UiPath, we tried Automation Anywhere. I like UiPath the best because it has capabilities like Document Understanding, AI, fabric, etc. UiPath has more features than Automation Anywhere. When we did a POC of Automation Anywhere, we found that the data scraping wasn't as accurate when working with PDFs. 

The deployment may be straightforward or complex, depending on the project. Before each project, we have a testing phase of about seven to eight days. We have a 10-day monitoring period. In that 10-day period, the developer is also involved with the support. We have a different support team that takes care of most of these things, like deployment and monitoring the processes. If something goes wrong, they have to open a ticket and reach out to the developers. 

Our implementation process involves checking all the business requirements. We look at the software and machines our clients use and the steps involved. Once we know the business requirements, we start working on the modules. We determine how many modules we need and the amount of time it will take to develop them. 

After that, we have a daily scrum call. If we have issues, we reach out to the business, and they will come back with a solution. We need to undergo this initial development phase before starting anything. Once the development is completed, we have multiple process design documents detailing the processes and steps. We also work with third-party integrators. About seven or eight staff members are involved. 

This solution does not require much maintenance once it is deployed and we've granted the access required. Once we've ensured the process is running and done the initial updates, we don't need to maintain it.

I haven't calculated the ROI, but I've heard that other people have seen 60 to 70 percent return on what they invested.

The pricing depends on the project and how many hours we will charge. 

I rate UiPath nine out of 10. There are still a few areas that require improvement. Before implementing, I suggest doing a POC so you can evaluate other tools side by side to see which one is best. 

One of the use cases I've worked on involved uploading a small book containing mathematical formulas, images, and other content to a website. We converted the book's introduction into an XML file and utilized UiPath to seamlessly upload all the information onto the publication website via a step-by-step process using notes.

Another use case involved generating reports by scraping data from specific websites, particularly in the banking sector. The information gathered from one website was then uploaded to another website. These automation tasks included handling schedules, duplicative tasks in Excel, and automating financial processes. This encompassed tasks such as fetching data from databases, manipulating the data, and updating the database accordingly. Furthermore, reports were generated and distributed to users both via email and Excel files.

The automation processes also extended to extracting data from various sources, such as PDFs, images, and tables, showcasing the versatility of the automation solutions implemented so far.

While we haven't incorporated AI or machine learning into our automation programs yet, I have acquired knowledge about these technologies through the Academy.

It empowers us to implement end-to-end automation, a crucial capability for our needs. Achieving full automation is pivotal, and building a process from start to finish ensures a comprehensive, 100% automated solution.

The UiPath user community is beneficial, especially when new features are introduced. For instance, with the recent addition of mail integration, the community provides valuable information. In cases where we encounter challenges using specific properties of activities in the APAC, the community forum becomes a reliable resource to discuss issues, seek solutions, and stay informed about various processes and functionalities.

It helped us in entirely minimizing our on-premises footprint.

I've seized learning opportunities through the UiPath Academy, where my initial learning journey began. I continue to rely on the Academy for various courses and continually update my knowledge.

It is expected to accelerate our digital transformation, enhancing the speed of various tasks over time. While I cannot provide insight into the cost implications, the positive impact on speed is noticeable when it comes to digital transformation efforts.

It has significantly minimized human errors, especially in tasks involving extensive document processing and repetitive jobs.

It has contributed to time savings for us. With the ability to automate the monitoring process for any website, we can now sit back and relax.

We have achieved cost savings by implementing automation. Utilizing automation allows us to streamline the tasks currently handled by multiple team members. With automation, we can allocate just one team member to monitor the automation board, resulting in reduced costs compared to the expenses incurred for seven individuals performing their specific tasks.

I find the pivot feature particularly noteworthy as it enables seamless connection to any source system, allowing for data retrieval from diverse sources. Whether dealing with conventional or unique source systems, UiPath's pivot feature empowers us to connect, extract data, and efficiently integrate it into the system. Additionally, I've been impressed by the task mining and task capture functionalities. This feature provides insights into the entire process, making it a compelling addition. The document understanding feature is perhaps the most significant and useful use case for UiPath. It allows for extracting data from both structured and unstructured formats, providing versatility in handling various document structures.

Creating automation with UiPath is straightforward, whether you're building them or simply learning how to use the tool. It offers a trial version that's accessible for two years, making it convenient for anyone looking to learn and apply the platform. The simplicity extends to the process itself; setting up conditions and building automation becomes easy and intuitive. Regardless of the complexity of the task, UiPath enables the creation of goal-based automation, ensuring efficiency and effectiveness in achieving specific objectives.

When dealing with a VPN connection, automating the process becomes essential. However, challenges arise when attempting to automate multiple VPN connections.

I have been using it for more than four years.

The stability of the automation depends on how we establish the rules for a specific automation task. When we define a set of rules for rule-based automation, it tends to operate smoothly without lagging or getting stuck. The automation remains robust as long as the established rules are adhered to, even when there are changes in the user interface of the system.

I would rate the scalability capabilities eight out of ten.

We reached out to tech support when encountering challenges that we couldn't resolve independently. Although direct contact with them has been limited to the initial stages, such as during the license purchasing process, we have relied on the technical team's assistance for troubleshooting and problem resolution.

The initial setup was relatively straightforward.

We have the flexibility to deploy both on-premises and on the cloud. The ease or difficulty of deployment is somewhat contingent on the client's machines. Various client systems may have specific restrictions; some are more stringent, while others have fewer limitations. The complexity arises when certain systems impose restrictions, especially concerning data source connections. The number of systems to be deployed dictates the need for a team knowledgeable about effectively integrating the software into diverse systems, but mostly two individuals are enough. Overall, I find the deployment process to be quite straightforward and maintenance to be easier compared to other alternatives.

The pricing is quite reasonable. I believe it is more affordable compared to other automation tools such as Automation Anywhere, which is often considered out of budget.

My suggestion would be for any user interested in learning about UiPath to start with the trial version before committing to the implementation. Overall, I would rate it eight out of ten.

We use UiPath across a diverse range of functions and departments, encompassing accounting, human resources, loan servicing, employee progress tracking, and loan origination.

Our primary objective has always been to navigate the cycles effectively, ensuring that we can manage fluctuations without the need for constant hiring and downsizing. It's all about maintaining a consistent workforce over time.

The most valuable component is Studio—it's the cornerstone of our automation efforts. Recently, we've delved deeply into Insights, which has proven to be incredibly beneficial. Our key focus is on eliminating time-consuming tasks and enhancing reliability, especially in repetitive processes, which is where automation has proven to be a significant asset.

Simplification and adaptability for smaller businesses would be a welcome enhancement.

I have been using UiPath for approximately six years.

It is highly reliable, and we didn't have any issues with it.

When it comes to scalability, one aspect to consider is understanding the licensing for on-demand bots and related components. There have been some challenges, mostly on our side, particularly concerning high-density servers. 

The ideal scaling strategy involves adding more instances to these servers. We have opted for standalone virtual machines for each partner, and while this approach offers scalability, it does require the manual setup of additional machines, which can be a slower process for a small IT team like ours.

I contacted customer support only once when we encountered an issue related to changing the institution name within an application. Fortunately, the support team was able to resolve the matter successfully. I would rate them ten out of ten.

Positive

We were using a software called Winautomation, which wasn't very robust. So, we made the decision to switch it, which has been a beneficial change.

The initial setup was relatively straightforward. The main challenge we encountered was obtaining security approvals when transitioning to on-cloud.

Initially, there was just one automation tool in place. Our first step was to rebuild that process using UiPath and then we engaged with various business teams to explain the concept of RPA and gather input to create an initial backlog. Afterward, we collaborated with management to prioritize the tasks and determine the order in which we should proceed.

I find the licensing structure to be perplexing, and it frequently changes. The inclusion of AI units, raw document units, and Cloudmont licensing, along with various sub-licensing options, can be quite complex and non-intuitive.

We were considering a few alternatives, such as Blue Prism and Automation Anywhere. The primary goal was to find a solution that we could commit to for the long term. Ultimately, it appeared that UiPath, which is an industry standard, was the best choice. I also had previous experience with it at a previous company, which made the transition more comfortable for me.

Overall, I would rate UiPath ten out of ten.

Our primary use case is more of a reactive ad hoc use case to solve business problems on the fly. We can build automations to update thousands of records. 

We're putting a little bit more money and resources into it, and we're starting to go down more of the unattended automation path to actually do more end-to-end processes. 

The use of AI has freed up time and resources for other tasks in our company. We are a little bit more of an ad hoc approach right now. I just finished up a new cross-set of processes about two weeks ago that allowed us to onboard a client. I wouldn't have been able to without this automation. It would have taken a couple of months of several people's time to get them to get all this work done in the back end. 

It is helping. It provides value where we wouldn't be able to do certain things without it.

The broad functionality is the most valuable feature because it can interact with many different factors, and there are several ways to solve a problem. 

There's not just one cookie-cutter way to achieve what you need to achieve. You can get there in various different ways. That's a key aspect for me.

From the UiPath product perspective, this might be a problem because we're on-prem, but they add new functionalities pretty rapidly. It feels like there are releases constantly, and I don't want to update it too often. 

I feel like I'm behind even though I might not be. Sometimes, we'll go a year without doing any major upgrade to Studio or Orchestrate or anything. 

That's more of a personal problem, but that's because there are frequent updates to understand.

We started using UiPath about three years ago. We're a small company, an 80-employee bank, in Denver, Colorado. 

We're smaller than a typical RPA client. Our development is probably underutilized compared to larger institutions. Still, we thought it was important to get in the game early and start establishing the foundation of an RPA environment.

The stability is good. We have run into some issues that they believe are more related to their environment than to the application itself.

We're in the process right now of scaling. It is a scalable solution.

The customer service and support have been amazing. It is honestly the best product support. 

I have no complaints about the support. I don't even get worried when I have a situation. I might need to open a case. I like partnering with them. It's a good experience.

The initial setup was difficult because I didn't have a lot of past experience setting up a new program. This was a whole new program for us. Not only was it installing things, but it was also wrapping your head around how to set up properly so that we can get out of this.

It was a little challenging, especially with the on-prem solution and working in Citrix, to make sure these different servers were talking to each other properly, but overall, it was not too bad.

We're on-prem right now, so we're not even in the automation cloud. We're looking into that in probably the next year. The UiPath platform has been great for getting to understand those products a little better.

I see a return on investment. Even with underdeveloped automation, we definitely have a good ROI. 

If people don't understand the benefits, they might think it's a bit pricey, but for me, it's very cost-effective.

We looked at Automation Anywhere and Blue Prism. It was three years ago.

I work in banking. We are highly regulated in our server infrastructure, so we decided to do a VDI environment that works in Citrix. 

At the time, UiPath seemed like the best product to work with Citrix which was a large reason why we chose UiPath. 

We wanted to make sure we were getting something that was going to play nicely with our environment. It has proven to be true to this day. 

We feel like we chose the right vendor.

Overall, I want to give it a ten out of ten. I have to give it an honest nine just because I haven't used other RPA solutions. But I love UiPath.

If you're going to go in, go all in. We didn't go all in at the beginning, and we should have. We're playing a little bit of catch-up because of that. My advice would be to go all in and be organized with your approach.