UiPath Platform Reviews

We primarily use it for delegating access permissions to help desks, for example. We use it to automate certain things, like onboarding new users, or deprovisioning leaving users. When we add somebody to a group, it triggers some kind of automation workflow. Lastly, we use it to sanitize data entry, so to make sure that capital first letter in the street name is used, certain zip codes aren't allowed, others are, etc., so data is controlled.

It helps mitigate the risks. With traditional native active directory delegation, it becomes real messy, real fast. You lose oversight on who has access where. We are an acquisition merger company, so we let go of certain companies and onboard new ones. With native delegations, you lose track of who has access where. With Active Roles, we can always see who has access and what they can do in a very granular way. You can modify the street name but you can't modify the city for example. Or you can modify the picture, but not the names and so that granularity is not available normally.

This product has eliminated a lot of tedious IT tasks, especially when people leave. There are about 10 or 15 actions that Active Roles does, scripted, in the same way, each time. It used to literally be a list of things that the admin would do, like: hide the mailbox, disable user, remove the groups, etc. Also, the auditing history that it keeps is very handy for us. We have a change record of what's been done to a user, who did it, and when they did it, which really helps us out.

We really needed this kind of product for its Active Directory delegation. We could not allow everyone to have native access to our Active Directory. The delegation bit was really the trigger. Automation is also a major reason we use UiPath. There was just so much room for human error that we wanted to script activities rather than rely on the admins to know what to do. This is especially important now that we are outsourcing many activities and dealing with a changing audience. In order to make sure that everybody does the same thing at the same time, tools like these make sure that you do everything in a structured manner.

The value for us is that it resembles the native tools that most people have grown accustomed to. Most people come from another company where they may not have used Active Roles. Active Roles resembles traditional tools like Microsoft's, which is really good because it eases the way people interact with the tool.

AD and AAD management features are really good. They're better than native tools; they offer an added value. They show more fields than traditional tools, such as password age and status of things that you normally wouldn't see. We still have the mailbox and user information all on one screen, whereas in native tools, you need two tools to show that information.

Active Roles works with policies and access templates, as well as workflows, which are really powerful. While it comes with a lot of example policies and access templates, there are zero built-in workflows. I would personally love for it to come with 10 to 20 sample workflows that achieve a certain task but are not enabled by default. In that case, I would be able to just look at those to see how it's done. I could clone them, copy them, and modify them to how I want them. Then I would be good to go, rather than having to reinvent things from scratch.

The solution is very stable. Even if components lose connectivity, or the database dies, as soon as it comes back up, it just reconnects and goes.

It covers all we would like to do. It's scalable; you can make it replicate databases. We don't use a lot of those features, but it is very scalable.

It needed a bit of getting used to, in terms of where you set what, but once you get the hang of it, it's really straightforward.

I think we're just paying for mitigating risks. There is the risk of leaving all authorized access behind and the risk of having Active Directory pollution. With that comes a risk of people getting access that they shouldn't have or having multiple accounts for the same thing. There's no money or value added from using the solution, but there is risk management. That is really what you pay for.

We did consider using the Microsoft solution because it's free and built-in, and that's what everybody does. However, when you grow beyond a certain ping, or scope, you find out that it just does not cut it anymore. We also considered using other tools, but at the time, I think Active Roles was very much alone in this world. I have to admit, now there are other vendors available, which I don't have any personal experience with, but on paper, they seem to do a bit of the same thing. At the time, though, there was simply nothing else that could even come close.

I would rate UiPath as nine out of ten. There's always room for improvement. This is definitely, really up there.

We are trying to focus on using UiPath for our mission. A lot of people use RPA for things that happen everywhere, such as in financial or HR. We are a bit different. We are trying to focus on things which will improve what our customer are doing.

For example, one of our customers is a bank. Therefore, we are focusing on improving their relationship with the bank's customers by using RPA. While there are use cases everywhere, we are focusing on trying a company better and more streamlined at their core.

The robot (in the bank example) focuses on improving the way a customer interacts with the bank. The robot facilitates the monthly interaction that customer the bank by providing information to the bank, processing information much more quickly, helping the customer and bank at the same time. The bank doesn't need to spend a lot of time or resources looking at the information coming in. The robot can process the incoming information, validate it, and do lot of the work which had been done before. It is a win-win on both sides of the relationship.

We are seeing RPA use cases everywhere. Pretty much every one of our customers has some type of RPA that we are talking about as turning into a pilot or have already moved forward with as an RPA solution.

One example is we created a robot to use with DocuSign, which is fairly industry standard.

It has a core tool set of things in use to quickly put together an automation, whether it's interacting with an application or website. It gives you the tool kit that you need to quickly put something together. Very often, we can create something in a very short time frame, like in less than a day, and show it to someone. Then, they can see the immediate value of the solution.

UiPath was easy to use when I first came into it. Though, I have a software developer background, so a lot of the concepts were very easy for me.

UiPath has a whole bunch of online courses in the UiPath Academy. These are very helpful on understanding the capabilities of the tool and some of the nuisances of it. 

It takes a bit of thought to find the right thing that fits into RPA at this point. However, with the things that we are branching into with natural language processing and imaging things, there will be more possibilities and opportunities.

UiPath should continue to grow and integrate with things that we can interact with, particularly with other enterprise solutions out there. They should continue to have out-of-the-box things that we can just take and work with.

I have seen a lot of improvement in the stability and scalability in UiPath over the last year or so. There have continued to be new releases with new updates, along with new technologies that help. Therefore, the maturity of the product has gone a long way in getting to a stable, scalable product.

Going forward, I would like to see more stability in the robots. When I create a robot, then I want it to work for quite some period of time. I've had some situations, where things will update, change, and the robot is broken. Part of this is making a more stable implementation easier.

We have put together a couple installations using Orchestrator. We haven't had the need for huge scalability yet, but it seems that the platform is there and has the capability for it.

One of our customers is a very large financial institution that has a lot of automation, because they have millions of customers. Then, some of them are smaller who are just trying to put their toes in. Even at our very large customers, there are still opportunities for improved, additional automation. However, the maturity across our customers is very diverse.

UiPath has always been there to answer the questions that we have or help staff when we need it.

Our customers ask us about the solution because of the government mandates.

Compared to the other RPA platforms, like Automation Anywhere and Blue Prism, UiPath is much easier to set up. This is the value that a lot of our customers have seen, because it is so easy to set up, you can set up and install something on your own computer, use it, then run with it, and finally, play with it.

That is a huge advantage: You don't have to set up a large infrastructure just to do RPA now. Of course, Orchestrator is a little bit more complicated, but then I've had a much easier time setting up Orchestrator than I have had with some of the other leading RPA products previously mentioned.

The biggest thing for a lot of our customers is ROI. It takes about a year to see ROI, but it does vary based on use case.

One of the use cases that we are looking at is for a large government agency. They are taking people out of doing reports and putting them back in the field. In a cost constraint environment that we are in, this is critically important.

Some of the things that we've done have cut down tasks that took four hours to 30 seconds. So, there is a lot of benefit. Our customer are experiencing very large benefits from automation.

Go download it, install it, and play with it. You can't do this with any of the other platforms.

There is an easier level of entry for UiPath.

While you can easily automate with RPA, the tasks someone does repetitively and is likely to make mistakes, thus eliminating human errors on a lot of things, but at the same time automation is only as good as you make it. So, humans are creating the robots at this point, and obviously there is still a possibility for errors. However, in processing workload, you will definitely cut down on the errors happening there.

We have a lot of maps worldwide which order some stuff from my department, and this is the compiled path. This goes into our database, then it comes to us. 

It uses data that we have already in the company, which is just sitting there waiting to get picked. You just have to tell a robot that a human does this, now you do it. We have so many processes which could be done like this. Right now, it's just scratching the surface. We are really exciting about it.

The product is very intuitive and easy to use, and I am not a developer.

The product is stable with no downtime.

The product can scale and meet our needs going forward.

I haven't used UiPath's technical support.

The UiPath Academy is good. I started there and learned how to use the tools.

The initial setup was very complex. We had the data, but we had to streamline it. You can build a robot in 30 minutes, but the robot needs to get the data correctly. This was hard to do because the laboratory in the U.S. uses the system one way, then the Chinese lab does it another way, so we have to streamline those before we can use the robots. 

Therefore, I should have looked at the data beforehand, since it took too long to get the data to be recognized correctly. We have learned from that experience.

The product has saved us on time.

Data scraping. I use UiPath for extracting Twitter and TripAdvisor reviews from hashtag and comments. Then, I analyse the positive and negative data to a table using Python script which uses natural language understanding.

Earlier, we used to extract data using a Python script which uses Beautiful Soup library. Now, we can easily scrape data using a simple tool. It's not only just scraping data, but our non-coder or non-programmer staff is also very happy with this tool. 

This tool covers all segments of people in the industry. Our software engineering intern was also able to perform and design a sequence which could extract review tables from TripAdvisor.

I love the ease and smoothness of the tool. The company has its own academy in which you can learn from fundamentals to advanced level. Each time you complete a level, they praise you with a certificate so that you keep being motivated. Personally, I have half completed level three. The tool can be accessed easily either when you want to schedule a task on VM or on your own computer. Generally, I do data scraping and automation tasks, for example, I scrape the Twitter data using hashtags. I scrape +ve and -ve tweets to an Excel file up to some pages and then analyze the text into +ve and -ve tweets using natural language text understanding.

The first thing I dislike is it is not available in a Linux environment. I prefer to work on Ubuntu and would have liked if it is available for Linux systems. Secondly, There is very limited content on ReFramework on UiPath Academy. Assignments cannot be done just by reading the text. There must be a demo for ReFramework projects.

Suppose you have to work on open source development or Open Source project for a networking community. It requires to have a Bash. You cannot do that in windows. If you are running a script on daily basis for checking malware or something like that on your home networks using Linux (with the support of a GUI tool), you could automate it using UiPath if you had a Linux version of the UiPath RPA.

Secondly, when you learn for certification from the academy you have to pass level 3 in between. Which requires a good hands-on with re-framework.The academy lacks practice material for the same.

• Automating applications that the client requires in the project
• Mostly automating day-to-day tasks which are like user-setup, user termination and password-reset in an application. 

We use the 2018 version. The community of UiPath is very supportive and active; that makes it very much understanding.

It made automation very easy with the help of experts from UiPath. Using this tool made a very easy way to automate the applications that our organization uses daily like time filling. For the beginners, UiPath provides a platform which helps them to have a better understanding of UiPath. Also, it has a community edition that helps to have a good hands-on experience for a beginner.

The OCR capability of UiPath makes it special as this feature was not in my previous automation tool. When I started using this tool, it made it compatible with automating some complex applications like reading PDFs, virtual machines and some more Citrix applications that were hard to automate using other tools. Its recording feature is also one of the best features along with its pricing as it charges money as per robot usage by the Orchestrator.

The tool is perfect as it is a full-on package, but yes it needs some improvements like when we use the OCR feature of the tool it works, but when we try to fetch the data from the image which is of low resolution, its accuracy of fetching the data decreases. Sometimes the data gets some garbage values added to the data that is fetched. This needs some improvement. Also, if the page has some dynamic background, then fetching the data becomes harder.

Our platform, it's called Cevitr. It's a best-of-breed platform through which we offer automation as a service. In our world, we have two kinds of robots. Our robots have a personality. Jo is our robot. Jo is a gender-neutral term that can be John, that can be Josephine, that can be Joe. We have two variance of Jo. Simple Jo, which does the normal routine repetitive mundane stuff, and Smart Jo, which is more focused with the AI and cognitive capability. Both of these are part of our co-platform offering, Cevitr Jo.

We offer UIPath as one of our core technologies on a platform, through which we offer automation as a service. There are multiple use cases for our end customers on UiPath. It's one of our core offerings as a core product on a platform. I think UiPath as a production, it's obviously one of the leaders in the RPA space and there are quite a few technology features outside which are quite good for us. But I would say one of the key differentiators of the product itself is the community enablement of the platform. If you talk about how they enable write from their training, it is being opened for everybody to be able to enhance their skills to the new UiPath Go!, where people can come and collaborate and create and put compliments for others to share. The whole community enablement of UiPath is a fantastic way for customers to benefit and move forward.

As a product, the stability that it brings in, the volume of transactions it's able to handle, and some of the leading feature functionality in terms of AI and cognitive capability. It's absolutely brilliant.

We are focused more on the unattended space. That's where our predominant offering is. Though in the newer version of UiPath, there are new features coming up in the attended space, which we might have a look at. From a cost point-of-view, since it's a platform offering, we are able to offer it as a service so it's not a price per robot that we typically charge our customers. It's a slightly different model.

I think from a feature functionality point of view, it's an evolving product. There will be more features added. Every product is going up. I think from a UiPath perspective, it is evolving as we speak. But I think where it could really improve is being able to create a development platform that is easier to use. Today, as an end user, if I have X number of developers, each of them have to have a studio environment to be able to use. Typically, that's not a license model. But if that is more easily accessible to the development teams. Without constraints, it would be easier for us to use this platform more widely among our customers. So, I think, from a licensing point of view, studio environment should be more easily accessible. But other than that, from a feature functionality point of view, I think it's pretty comprehensive.

We've been quite pleased with the stability of UiPath across platforms and even things like Citrix. There, we have found UiPath to be quite good so far.

It has been able to handle certain volumes with ease. We believe that it is one of the products, which is  quite scalable. The tech support so far has been good. But like I mentioned earlier, what we find is the community. It's brilliant. 

If there is a standard problem that we have, we probably aren't in the first people in the world to have faced it so we can very well go to the community forums and ask questions and get them clarified. 

It's pretty straightforward, like most of these products. RPA is a technology. It's been around for a few years so it's very easy to deploy to end customers. Even the installation for usage isn't that technically complex, but we had to have had to cross certain boundaries to make it extremely robust on the platform. We have done those investments and made it seamless as possible.

ROI is for our end customers. With the technology like this powering our platform, we're pretty confident that we can give quite a good reasonable ROI to our customers.

We have a best-of-breed platform. It has other products in it, as well. UiPath is one of our key products and platform. What we want to give our customers is a comprehensive portfolio of end-to-end capability. This is across simple RPA to more robust AI-based process automation scenarios. To be able to do that, we have to have a best-of-breed capability. You know, we will be plugging in the right components. UIPath is a core component of that.

We are early in the journey with UiPath, We've had it for a few months, and I would say on our basis, I would definitely give it an eight. We are very happy with the product so far and we hope to do much more with it.

My primary use case is automation. I worked in multiple companies with the same product on the same profile, and most of them were automation. The actual business use case would vary from company to company, and project to project as well.

One feature that I personally found valuable was the orchestrator. It is a pretty mature platform as of now, and it was three to four years back when I started to first use it. It has matured quite well. They had a major change a couple of years back. Our company transitioned from an older approach to a newer modern approach that they deployed. The orchestrator platform was very well-suited to the new approach - as was the development studio. It's really easy to use and intuitive. That has matured quite well as far as I can tell. These two are what I liked the most about the product.

UiPath’s ease of use and quick deployment times were great as the cloud orchestrator, which did not need much of a setup.

To build automation using UiPath is fairly simple. The studio is quite easy to use. Even now, with the community edition, it’s great. If we want to learn to start or try out something, we do not have to wait for licenses or anything else. That said, we can also get an enterprise trial. If we want to do something, learn something, even during our personal time, we can just download it. They also provide a free orchestrator version as well, so it becomes quite easy to learn and develop. 

The building, deployment, and manual deployment processes, for small-scale projects, are very easy. If we need to build something, we just publish it, and it generates the NuGet package. It's very easy to deploy there.

The materials and the training courses are all pretty well-structured to get started with.

UiPath Academy courses have assisted in the process of getting our team up to speed. The basics were there even when I started out. I was not initially an RPA developer. I was into server operations before this. The UiPath Academy training really helped a lot with the initial courses, where they give you a tour of the platform and each and every activity. For audiences who are not much into software development, these courses can guide them towards that. The building blocks got us up to speed. They have very good courses there.

Regarding the Academy, it is a great learning platform for basic tasks. However, for more complex information, I turn to UiPath Forum. Sometimes I need some Python or C# scripts or am building custom libraries there. That gets shifted onto different platforms like Stack Overflow. We Google other platforms as well for the other types of queries.

UiPath Forum is a pretty good place in terms of the user community. Most of the queries that are posted generally get answered. Sometimes, even for smaller issues, we do not go directly into UiPath support and we first try to resolve the issues via what we find in the UiPath Community. Overall, it’s a pretty good place to solve our issues, and the community as of now is pretty active.

We saved time in our IT department since we started to use this solution. UiPath handles infrastructure for the orchestrator and its maintenance. There's a pretty good amount of time saved as we had initially had a server on-prem deployment as well. However, it became cumbersome to deploy multiple databases and they have some Elasticsearch requirements and security updates that need to be regularly maintained and in sync with UiPath. Due to this infrastructure overhead, our time could be consumed maintaining everything. Without them handling the infrastructure, we'd be maintaining instead of building automations and deploying them. We realized that an automation cloud would be a better option which is why we switched.

UiPath reduced human error. That said, we do not track errors in the process. It's a good metric to track as well, however, we currently do not track it.

It reduced employees’ time on certain tasks. The main purpose of automation is to save us the number of hours that the project will take. There are many other parameters, however, the time saved is one of the big ones. 

A weakness with Academy is that, with the current updates that they have, the newer updates, the courses are not up to speed. Nowadays, Academy does not feel that intuitive and does not give sufficient information about the product to the customer.

In our current use cases, we do not need much user interaction. One shortcoming with UiPath Apps is that it cannot directly integrate with the orchestrator platform itself. For example, if we need to fetch any assets, values, or cue data from the orchestrator itself, it's basically a web platform. Even if we develop apps and want to do something based on that data, they do not have direct integration with the orchestrator. We need a separate bot, which will then interact with the orchestrator and then pass it back.

If we need ten to fifteen users who might simultaneously use apps, and we want to run a process for each of these users, then we might need fifteen licenses to do that. That is something that has been holding us back from using it, as it does not have direct orchestrator access. We need a separate bot to get the data to perform some actions.

Scaling and licensing need major improvement. I know that they have released something called Serverless Cloud Robots, where the bot machines do not need infrastructure. However, we do not generally want to run the bots or the data in the UiPath cloud as well. There are some hiccups that do happen when we run bots on another machine. That said, it might be a good feature and we can scale up and scale down more effectively.

I've used the solution for nearly four years now.

The stability has been quite good for a couple of quarters now. We had some issues two or three quarters ago, where there was a downtime of around thirty minutes which impacted assessment. After that, for the last couple of quarters, we have not seen any issues regarding the platform itself. It is pretty stable.

The product allows scaling up, however, when we deploy and run the bot, the bot does not actually run on the orchestrator. The orchestrator is just a management platform. When we need to scale up bots, what we would need to do is spin up new virtual machines. We need those virtual machines in order to scale up. This, along with the licensing affects the ability to scale.

If someone does not have a license, it cannot scale up. When comparing it to something like AWS offers, or any other cloud service, where you can rapidly scale up and rapidly scale down based upon our demands, that is currently not possible with the UiPath. We do not get to easily scale up. We need to plan in advance as to when we run our automation, what time we need to offset the loads, and which automation gets priority at that time. That becomes a bit of an issue.

As of now, scaling is a bit cumbersome, whether we are scaling up or down, and the licensing also revolves around scaling.

We use both attended and unattended automation. In the case of attended automation, scaling is a bit tricky. We need to consider licenses. Very few need the same automation to run on one hundred machines. If we do, then we would need to find a way to manage these one hundred licenses as well. It again comes down to cost.

Our thought process is that whenever possible and where we need to scale, we try to avoid human interaction, and we try to convert our bad pieces into attended automation. If some automation requires a manual login due to regulatory compliance or maybe due to capture, what we do is have these login paths that we take in as unattended input. Then where it’s possible, we would run it as an unattended mode and maybe then pass on the output to the attended mode.

We have support from UiPath, however, I'm not sure what model we are on. 

The support is not as responsible as we would expect. It's not bad, but it's not good.

The response time, the overall solutions that they provide, and the workarounds are okay. It's a mix of everything. We've had somewhat of a mixed experience with them.

Neutral

UiPath handles infrastructure, maintenance, and updates for the Automation Cloud - the infrastructure being the orchestrator infrastructure. The robot infrastructure is handled by us.

I was involved in the initial deployment of UiPath in our organization's deployment process. The deployment process is pretty straightforward with automation cloud data, so we did not need to worry about that. The administration is pretty straightforward as well. They have all of these access models, folders, and groupings. It's very easy, even for a new user that needs access to a particular box to run. It's also easy to maintain.

In terms of deployment on the cloud, there is no overhead. The administration process is simple. Maybe it took us around two to three days of initial setup. Most of the time was spent brainstorming on how we would need to structure our use case. That was what took the majority of the time. Once we decided on that, it was pretty easy. It can be done in one day. The process is also ongoing as the requirements change and the roles change, and it always requires some sort of maintenance, taking out users, taking in new users, et cetera. However, that's pretty easy.

In terms of the deployment of individual bots, it is pretty easy. The manual deployment is also pretty simple. We deploy it from the studio. We get a bundle package and we upload it at the studio level as well as the orchestrator, and it's done. This is a straightforward model. We do have a CI/CD pipeline setup for enterprises where we avoid manual deployments. In that case, we do not use UiPath CI/CD. We do use Git and pipelines to push our packages directly to UiPath.

I can't speak to if there has been an ROI or not.

The licensing could be more flexible. They might have a different enterprise cost strategy for each of the licenses. The license is rigid in that you cannot generally scale up. To scale up, we have to have a license procured before we can run a bot there.

I am not involved in the comparison between Uipath and its competitors, such as Blue Prism, Automation Anywhere, or any other platform.

We do not really have clients in healthcare, however, my previous company has mainly evolved into what I can say is a pharmaceutical supply chain. The company is an ordering platform for pharmaceuticals. I'm not sure whether I can consider that as a healthcare pharmaceutical or supply chain use case.

I had done some trial POCs around the UiPath Apps feature. We did some basic trials within our team, however, we do not have any end-users who actively use UiPath Apps.

We're still at an early stage in terms of using AI in our automation via UiPath. We tried out some POCs, and I'm also just getting training on that as well. We do not have any production use cases right now that go into full AI or ML.

In general, they have a good ecosystem of developers. It would be easier to set up and use it. However, if a new company has heavier workloads and needs scaling capability based on time, they’ll need to calculate their requirements. For example, if I process 1,000 to 2,000 transactions per day and I need ten robots to do this and it's fixed every day, then it's fine. That said, if I have varying workloads, where the workload is the last week of the month and the workload is very high, maybe I’ll need twenty or thirty bots to accommodate this workload, while, for the rest of the month, I’ll just need around five bots. That's twenty-five bots that I’ll need to purchase, with many idle most of the time. That is one issue that needs to be planned correctly during the initial stage. 

Overall, I would rate UiPath eight out of ten.

We used to maintain a lot of Excel sheets for lead generation and other activities. UiPath helped us to automate those processes and clear our workloads so that we could focus on other main tasks.

It saved a lot of time on tasks that could be quite redundant. Fetching data and maintaining the machines and regularly updating them. That's the only thing that I was using it for. Using UiPath saved me about 10 to 12 hours on a weekly basis.

It allowed me to delegate mundane tasks to personal automations and to focus on more important tasks. By not having to do tasks that don't add value or skills, I could focus on tasks that were more important and that added value to my skills or targets. That brings much more satisfaction.

Also, the ability for employees to delegate mundane tasks to personal automations meant that we did not have to hire a person dedicated to doing those particular tasks. We could use the tool to do those tasks. It helped save those costs. On that front it helped in business operations.

UiPath was quite useful in terms of getting data from thousands of webpages online and arranging it in a predefined format. You can easily create robots and define operations in UiPath.

I come from a non-technical background. You need a little bit of technical knowledge to use it. We had a demonstration of how to use the platform, but it's easy to use. It helps in automating tasks which otherwise you would have to do manually.

The desktop Assistant tool provides a personal automation launchpad so that you can easily access and run automations. That's important because you don't have to go to someone every time you face a problem, or every time you have to run an automation process. It helps make you independent so that you can do your own tasks.

Other things I like about it include:

• Its dashboard is quite easy to use and you don’t need to have a programming background to understand it.
• You can record screens in Excel and download it from the cloud.
• You can also get quite a load of data from the web and use it for your processes without any manual effort.
  

For me, it was quite an effective tool because I hadn't used any automation tool previously. It was quite new for me and it took time to adjust to it and understand it. At times, some processes took longer with the tool, initially. But when you do them on a regular basis, you understand it better and it takes much less time. Setting up the systems could be difficult initially. It would be better if it were more user-friendly for non-technical users.

I used UiPath for less than one year.

It's quite stable and reliable. We had no issues.

I wasn't involved in the initial setup of UiPath in our organization, but I think it took less than a month to deploy it. It's also an ongoing process after deployment. There are a lot of things that need to be done.

About 10 to 15 people were using it in our organization. The users were mainly in IT where they were using it for central management and other automation purposes.

The fact that we didn't have to hire a resource specifically for doing certain tasks is how the ROI could be calculated. It also saved time for the existing employees.

There is a trial version available. You can go for the trial version first and then buy it and scale it per your needs. Try this tool. Go for it. It's definitely worth a try. If yours is a large organization, try the Community Edition first to get the hang of it. After that, move on to its Enterprise version.

What I learned from using UiPath is that there are tools available in the market that can essentially make your life a lot easier. You don't have to worry about doing certain tasks, maintaining them, continuously updating them. Their backups are always available, even if you lose something. They are always easily accessible on any device.