UiPath Platform Reviews

UiPath offers direct integrations with multiple platforms that we need, like Google Drive, Slack, Visio, etc. For Slack, UiPath automates the process when we upload a new file, document, or a new version of it. It automatically sends an email or any other sources that we automate through it. That is our main use case.

We upload a lot of content for our website or internal work on Google Drive. When a team member uploads content, we do not get a notification from Google Drive that a document has been uploaded by someone unless they share it. With UiPath, we have automated it so if someone uploads a document in a Google Drive folder, we get an email on a certain email address that a document has been uploaded. Or, when there is a version change, we also get an email. So, we have automated these kinds of processes using UiPath.

It is mainly the automation process for internal tasks. All our direct integrations are for internal work, mainly email triggers that we built using UiPath. These are very useful.

The direct integrations are most valuable. You can directly link your account to multiple platforms, such as Google Drive and Visio, without using an API.

We have used the Orchestrator's trigger creation workflow to create multiple triggers for our automation processes.

It could be improved with tutorials or documentation-wise. Some of the features of the artificial intelligence or Orchestrator have been a little confusing for me. So, I would like an easy YouTube video tutorial or quick demo call. It would be much better for every user if they could introduce that.

Around six to seven months ago, I started using UiPath.

UiPath has always been up so stability is not a problem.

It is really scalable, even for large businesses. We are pretty small, but as you grow, UiPath has great options for scaling up.

We currently have two people using it: the co-founder and me.

I haven't needed to contact their support yet.

We previously used basic process automation platforms.

We switched to UiPath because it offered better features that we needed. For example, its direct integrations are pretty useful. It has every integration that we directly need so we don't need to use APIs or code anything. It is simple and direct. That is the main reason that we use UiPath.

It was straightforward from the process of registering your account to creating an organization, then doing the integrations. The process was really easy and did not take too much time the first time. I think it took us an hour to deploy.

We are on the Community plan, so it has great return on investment.

UiPath has saved our staff time. Using the automation of UiPath, it triggers an email or notification for a process that we have created. This keeps us informed at all times. However, if we don't use it, content may get missed and we would lose a lot of opportunities.

The pricing is good. They offer a Community edition that we currently use, which is free. Their paid pricing is pretty affordable for businesses as well.

I went to review websites and saw that UiPath is great.

In case you are not going to drag and drop APIs, they should definitely go and have a look at direct integration. 

I would rate the solution as nine out of 10.

We are a service-based development company and we implement automation for our clients. UiPath is one of the RPA solutions that we use for this.

A recent use case that we implemented for a client involved a macro in an Excel sheet. The macro contained approximately 1,000 lines, and it was being used in an Excel spreadsheet about 10 pages long. They had dropdowns within the sheet that had to be set, depending on the action. They also had to work with some of the logic themselves.

With UiPath, we implemented a solution where the bot will create a task. It first checks to see if all of the necessary conditions are there. If they are, then the bot will automatically run the macro. If instead, some of the values are missing and user input is required, then the bot will create a new task to request the missing items from the user. It uses the UiPath forms and the client will receive an email to say that a task has been created and that it will be completed once the necessary values are selected.

Finally, once all of the values have been selected, the bot will run, use the input, and complete the execution of the macro.

A second use case for us was done using the Action Center. In this case, our clients send emails, and we have API calls that are done in response. Once an email comes in, a message ID is created and assigned to it, then it is turned into a Queue item. At that point, the user is presented with different actions that are dictated by the content of the email.

Depending on the user's selection, there are three or four paths that it can take. Ultimately, the bot will send an ETA and some request data to the appropriate parties, which is controlled by yet another process.

Using UiPath for automation is a little bit costly but it saves a lot of time, and it also reduces human error. When humans perform tasks, there are a lot of errors that come about. However, when a bot performs the same task, the number of errors is significantly reduced. This is the reason that companies are implementing UiPath and undergoing a digital transformation.

In our experience, bots run with minimal errors, in the one or two percentage point range. Of the thousands of items that they process, very few will result in an error. Humans, by contrast, normally have an error rate of 5% or 6%.

It is very easy to develop automation using UiPath, and I would rate it a four out of five in this regard. This is true whether it is IT automation, UI automation, desktop automation, or otherwise. We have even performed Citrix Automation recently, where we used remote runtime. In that case, we had access to a lot of features and this made our work very easy to do.

This product enables us to implement end-to-end automation. Some of our clients use the process mining feature, which includes task capture. Then, based on that, they generate the process design document (PDD). After they have the PDD, the bot is designed using Studio, and then it is ready for deployment. Deploying a bot includes publishing it using Orchestrator, and once it is running, Orchestrator monitors it. From end to end, UiPath is part of the process.

This is important to us because some of our clients are not very technical. They have ideas of what they want to do, so they walk us through the steps in a process. During that time, we will begin using the task capture capability to record what they do, making it easier for us to gather ideas and requirements. The whole process is an easy way to capture good use cases for the client.

Most of our clients are now opting for cloud-based deployment. This is important to them because they don't have to store everything on their on-premises servers. Essentially, they don't have to waste any space.

One of the features that I like is that the bot will continue to work on other tasks, even if one task is blocked because it is waiting for user input. For example, it's very good because whenever we need to have user input, we don't need to use the attended automation. Just because the user is not available to select the actions, it will not break the bot. Rather, the bot will work on other tasks. Once the person manually completes the required action, the bot will resume the pending task.

It is very easy for us to get selectors by using the UI Launch Explorer. I have used other tools that require we visit the webpage and get the selectors manually. This means that we have to inspect the page and find the elements. However, with UiPath, we have the selectors readily available using UI Launch Explorer.

Another good feature is the UiPath Academy. Whenever a new feature is released, we learn about it from the Academy. I would rate it a four out of five in terms of helpfulness for getting employees up to speed. When we review the new courses that they release, we can quickly get a complete idea of the feature that they are presenting.

The UiPath forum is very helpful. It is the best forum available for any of the tools that we have. I would rate the UiPath forum a five out of five.

One of our clients is using the UiPath Apps feature, and although it is easy to use, they are having some issues with it. For example, when they deploy an update, it is pushed to the cloud and then it will break an hour later. There have been two or three such issues and ultimately, they result in a high priority ticket to fix the problem.

I have been working with UiPath for approximately four years.

With respect to stability, the general system is stable. This includes the robots, Automation Cloud, and the Action Center. However, we have had a lot of downtime with UiPath Apps. It had been one or two days per month when our processes were getting blocked and although many of these issues are resolved, last month we had recurring issues with downtime.

The technical support team is very helpful. For anybody with a license, there is an option to raise a ticket based on priority. The support team tries to fix such problems very quickly.

Overall, the support team is very good and I would rate them an eight out of ten.

Positive

I have explored two or more other RPA solutions. One of them is Automation Anywhere, and another is Microsoft Power Automate.

When I explored Power Automate, it didn't have many features. It is a product that is still growing but when I looked at it, UiPath had more features.

In the case of Automation Anywhere, it's a little bit more difficult to work on. As an example, Automation Anywhere does not have ready-made selectors. There is no equivalent to the Ui Launch Explorer so we have to go to the webpage and find the elements by ourselves.

One advantage to Automation Anywhere is that it's a little bit less costly.

Using the Apps feature for one or two of our clients has sped up the time required to develop bots for them. Also, because it is a drag-and-drop interface that only requires a small amount of coding, making it work is much easier.

Our clients dictate the deployment model, whether it is on-premises or cloud-based. One of our clients uses Amazon but the majority of them work using virtual machines that are running on their in-house servers.

The automation saves time and money for our clients, although the amounts vary and are based on the specific solution. As an example, in an email task that we automated, the bots replaced a team of people. On average, the automation saved 28 hours per day for that task.

In general, several hours can be saved per day for each automation.

Due to the reduced costs and other benefits, our clients are ready to create more bots.

UiPath is a little more costly than competing solutions such as Automation Anywhere. 

The cost for licensing is handled by our customers that use the bots.

I have not personally used the AI functionality when creating automations, although some of our clients use features such as Document Understanding for invoice processing. They also use the ML Trainer. These features help them to automate processes that are more complex. For example, when they have 20 or 30 invoices coming in each day, the bot is trained to look at them and it makes the job very easy to do. Also, when the accuracy drops, the bot can wait for input in an attended fashion. This has helped a lot of our clients.

I would rate this solution a nine out of ten.

I use it for automating activities and processes in my company, and for discovering new automation opportunities. UiPath is my main tool for automating every process in business operations.

One of my main use cases for UiPath is around service desk and support center operations. I use it to take tickets from customers and users and automate answers using UiPath's machine learning. It links the questions to documentation where we already have answers.

I also use it for automating invoices with the pricing and other information and sending them to customers when they buy an item.

In addition, when somebody subscribes to a newsletter I have set up a process to send an email in reply.

Using the solution we can do task mining and process mining. The automations make everything easier for my business and for the other businesses where I implement them.

For example, one of my use cases is for a doctor's office to help manage the patients by handling their inquiries and automating the invoices. I have also set up processes to help with research and prescriptions. All these processes are automated and run without any human involvement.

And it has helped my business operations a lot. It's helping us detect all the performance issues and data threats. UiPath Insights helps us to prevent these issues from happening again. It's powering up our operation. We can analyze all our departments in one place and get the best usage from them using Insights.

We fully depend on UiPath for the three departments: sales, marketing, and service. Many of our sales operations are done by UiPath, such as generating invoices, research, and engaging with clients through the help tickets they submit, as well as through the email communication we do. 

And one of the most important benefits is the ability to identify new opportunities in my employees' workflows. It is able to record and discover what my employees do and we are able to create automations as a result. 

Digital transformation is another main focus. Through the UiPath Marketplace, I can get expert virtual employees who do very expert jobs and tasks without having to hire somebody or bring them into the office as an employee. It's all automated by the software. I can discover, build, manage, and engage with the robots. My employees can easily manage all the robots and the processes, increasing the collaboration among us.

All of this makes it easier to store and move data from Google Sheets to my own sheets or my CMS on WordPress.

It saves a lot of time. It has really transformed my operation from a situation where we were always pressed for time and had slow response times to customers. With UiPath, we have increased our customer satisfaction scores and get tasks done faster than ever. My employees are now using the time they used to spend on certain tasks for things that require more thought. It has transformed business operations 180 degrees, making everything easier, helping the business to grow faster, and improving performance. We have control of the front-end work as well as the back-end processes.

For me, the most valuable feature is the solution's ability to discover automation opportunities.

The Document Understanding feature for extracting information from documents or images helps reduce manual work, saving people from having to scrub data from PDF files or images. UiPath extracts all the information and stores it.

In addition, its AI and machine learning make everything easy, as do the Data Service tools, because they don't require coding to create automations. I can do everything without coding knowledge.

And the UiPath user community is the best. The people there are very friendly and helpful, and engage with each other. UiPath has done a good job building a good forum and a good blog, and making the community members interact with each other. The community is one of the reasons UiPath is my choice. It is a strong community.

I like most of the UiPath tools, but the UiPath Academy, in particular, wasn't my favorite part. It didn't have enough onboarding guidance when I started. The learning curve for the courses in the Academy was very difficult in the beginning. I had to turn to Google and YouTube to learn from other people, experts, and the community. The community was friendly, but the academy wasn't that helpful for me. I think it needs to improve on the information it provides to make it easier for beginners to learn, to help decrease the learning curve.

Also, the user interface needs to be more customizable, and the debugging tool doesn't work well enough. It needs some improvements.

I have been using UiPath for one year and eight months. I have several websites and three startups, and I also implement UiPath and automations for other companies.

It's stable. It has 99 percent uptime. 

Sometimes, when we are dealing with a large set of data, it becomes slower. I don't know if it is something to do with UiPath or something else, like the operating system or the connections. It is almost always stable, but when dealing with large data, it becomes a little buggy and slower. Sometimes it freezes and I have to turn everything off and restart it.

Their support staff has good knowledge about whatever I raise, but they are late in responding, at times. I have had to turn to the community more. When I can't find an answer, I turn to them and only after them to support. It should be the other way around. I should be turning to the support group and then, if needed, to the community. 

One good thing that I have found is that UiPath responds to the community and the recommendations of users. When we recommend something, they put it on their roadmap and they make plans for it in their app. They are engaging and friendly with users and the community, but they are late in responding.

Positive

I started by using Blue Prism but only for three or four months and then I left it and turned to UiPath. I couldn't find answers to my questions when I was using Blue Prism. I couldn't find a professional community to engage with or to get help from. This was the reason I started turning to UiPath, after reading a few reviews from several websites and some of the community posts. The UiPath community was providing good information about every capability of the solution. In my experience with Blue Prism, I couldn't find any valuable communities out there. With UiPath I found the opposite. 

Even now, I find it good to engage with the UiPath community. Whenever I need an answer to something or an explanation about a use case, I always turn to them.

They have to reduce the price a little bit for basic users, startups, and small companies.

We are partners with UiPath and Automation Anywhere. We use this solution for IT services and for the education sector.

OCR Tesseract, by default, is the good OCR search engine to extract data from a digital PDF. For any Unstructured document with a normal noise, background letters, either UiPath Document Understanding or AbbyyReader fails to extract the exact values. Very difficult to depend on Computer Vision too as a third party tool for small to mid-range business purpose. Hence, a combination of AI/ML with a good OCR Engine is required for UiPath to go forward.

UiPath Orchestrator is definitely a plus point in the product. This helps in all formats of UiPath version ranging from PoC till Product Deployment.

The OCR functionality for this solution could be improved. It should have a better capability to read unstructured documents. The next generation of OCR is ICR and UiPath does not have this. This would enable us to read and search through documents.

We have used this solution for two years. 

This is a stable solution. 

This is a scalable solution. 

The technical support is not that satisfactory. We have to find the answers by ourselves through non-community groups. 

Neutral

The initial setup is straightforward and the deployment was easy. 

It was implemented in-house. 

The return on investment is really good. I would rate it a three out of five.

We're an official partner of both AA and UiPath and both of them carry the same weight with a very marginal difference but there is a difference in cost. Currently our clients are looking for cost optimization post-pandemic and UiPath comes at a high price point. 

I would rate this solution a six out of ten.

We have deployed a chatbot in our system.

Designing a chatbot would usually require some language coding and it would have to be deployed with certain front-end languages. But UiPath gives us the ability to automate this functionality with drag-and-drop features. That is the very best part, where UiPath is doing an amazing job. It doesn't require any language coding or front-end coding to create the user interface.

Because it is easy to use, it saves a lot of time for the developer. When it comes to programming, UiPath has made all the manual work, such as verifying and correcting errors, and even repeating processes, less complex and less time-consuming. If you were to try to choose a coding language and use it to streamline things and design a bot for automation, it would take more time. Doing that would take 15 days to learn the language and to code with it. There would be a certain number of errors that you would have to deal with, as well. There might also be a backend required. UiPath can easily save you 10 to 15 days, automating in two to three days, maximum.

It gives you the ability to automate workflows and large processes that would take a long time to do manually. With the help of UiPath, the time it takes to get those tasks done is reduced and it reduces human error. In addition, it saves you money because you don't need to hire people for the tasks that have been automated.

There is also the benefit of not having to hire an engineer to program things. If you had to hire an engineer there would be the expectation of a payment package. There would also be the time spent on dealing with errors the engineer makes, and this person might also require mentors. UiPath decreases the spending of time, energy, and money, especially.

UiPath also saves our organization time because the automation cloud handles infrastructure, maintenance, and updates.

One of the most valuable features is that it provides you with the ability to learn the system and understand the concepts through specific demos. UiPath provides you with education, through the UiPath Academy, on the basics of how to use the software and for what purposes you can use it. It is a very good thing that they provide education with it. That makes it easy for us, as developers, to gain the knowledge we need.

Another good feature is that it comes with an embedded recording functionality. You didn't require an external screen recorder. The embedded screen recorder enables you to record things so that you can remember them over time.

In general, it is easy to build automations using UiPath. You just drag and drop according to your needs, and you can automate things in a single go.

One thing I don't like about UiPath is that it does not have a very good user interface for a newbie. It's not that the user interface itself is bad, but when I started using it, it was very difficult for me to understand the tool and how to use it. It has N functionalities and a user has to learn the particular things that these functionalities are used for.

The user interface should be a little simpler than it is right now, as it is very complex.

I have been using UiPath for more than a year.

In terms of scalability, this software can grow with the industry, especially since more companies are focusing on automation. Here in India, for example, there are many companies, like KPMG, focusing on the field of automation. Software like this can help them to scale more and more in building their automations. The software can really scale up well, as long as the user interface is improved.

Their support system is very good. If you have a problem and you reach out to their support system, they are quick to reply. Problems are solved within 24 hours of reaching out to them.

Also, you can use the UiPath user community instead of contacting support. There is value to the user community because people help each other there. Because we are concentrating on development in my company, we tend to not be as active on the community side, but whenever we do use it we get help from them.

Positive

I have only been exposed to this software. I graduated and started working in the RPA domain by using this software.

It wasn't that complicated to set up. 

The pricing and licensing are pretty decent. If you are using it as an automation developer, it comes in at under $500 a month. Still, the pricing can be reduced, but the service and functionality are solid. 

I have heard from some of my colleagues that there are many subdivisions of the pricing and some of them are between $1,500 and $2,000 a month. That is expensive. But overall, my colleagues say it is a cost-effective program in the long run.

If you are working in the RPA domain as an automation developer, you should look at UiPath because it gives you many functionalities. Also, the education aspect of UiPath is a very cool feature because you don't need to rely on other software to learn it. Thirdly, the bot-building process is very smooth. 

UiPath is a fast, time-saving, money-saving, energy-saving solution. Using UiPath has been the best experience. I would recommend it. You can choose this software without any second thoughts. It can provide a good return on investment to your business.

We primarily use the solution for operations processes in our corporate investment bank. For example, screen scraping, querying from databases, or any transactional processes. Those are what we're really looking at the most.

The orchestrator is very valuable for us. The ability to have processes, especially transactional processes, be fed into and triggered from there is excellent. I really like the ease of use that allows not just typical developers to use the Studio version, but also StudioX, which allows citizen developers with little to no coding background to be able to automate their own process. Studio limits a lot of the coding you would generally do in Visual Basic and offers a pretty easy use case for people who want to get into development, who might not have that background.

I’d rate the ease of automating within UiPath at an eight or a nine out of ten. Maybe even a perfect ten. They make it very simple. It's a really good platform and for everything I've used it for so far, I can't think of how I would do this X, Y, or Z differently. I really like it.

In terms of our adoption of it, we just started using it this year. We haven't had a large volume of bots delivered and put into production, however, with what we're using, we have a lot of proof of account sets and use cases that are getting pushed along that are going to save the company time in man-hours.

It's going to save the company a lot of potential risks in terms of manual error. It's also something that can be used to automate processes that are very heavily related to compliance procedures as well, where you don't want as much manual touch for the same reason and you don't want to risk, even if it doesn't take that much time for a person. With automation, you remove the risk of somebody making an error.

We don’t have a crazy amount of metrics. We're really in the process of adopting it into the organization. I'd say within the next year, we're really going to be seeing a very large adoption of it.

We have seen direct savings in costs. Every project we deliver in time save has an associated cost reduction to it. If you're saving, for example, four hours a day on a manual process, you're saving that money. You’re also saving on anything that's related to risk. I don't have any hard numbers on the amount of time that's been saved, however, it’s been positive.

Our teams have used the UiPaths Academy courses. It’s helped make the process of getting employees up to speed with UiPath very straightforward. It's one of the better learning platforms I've seen. Between them and Alteryx, they both have very good learning platforms.

What's really important is that you don't need to wait for instructor-led training, which is infrequent. We have it sometimes, still, even when we’re having it a few times a year it gets expensive. The online training, which covers most of the same material, is a really good way for people who don't want to wait for the instructor-led training and want to immediately get their own feet wet.

The Academy is very comprehensive. It's well structured and training is easy to follow. I've used other tools that have been much harder to follow online. This one I really like.

The biggest values that we’ve seen From UiPath Academy are ease of use and ease of scalability. The solutions you make based on the infrastructure that's built around it can be made to be very scalable. There's so much that depends on other terms, such as the data that we have on our own processes, that it's going to be the yes or no, whether or not a process we build can be scalable automation for other teams. As long as we get the data and the processes lined up in the right way, we can make very scalable processes, which is good as that's more cost savings for fewer bots and that's really like what we want to see.

There are some external dependencies. When we have APIs available, UiPath does have that option that we can hook into APIs. That's really where I'd like to be down the line, more like hooking into APIs, data warehouses, so that you don't have to worry too much about the screen scraping functionality, even though that's a great big part of what it does.

I would really like the ability to bring OCR connectors into StudioX, if possible. Right now we're only using OCR and Studio as that's where the plugins are available. I don't know enough about the back end of what makes this feasible versus not feasible. However, at the moment, with StudioX, you can only really read and digitize PDFs. If they can bring in the OCR connectors, they'd allow citizen developers to be able to read in a larger breadth of documents that they would generally need Studio to do.

I've been using the solution for about ten months. 

The product is as stable as it can be for the processes we use to expand on that. We do a lot of screen scraping and web scraping a lot. I want to move away from this in the future. However, the stability of those bots is going to ultimately be reliant on how that webpage looks.

We're looking at very specific parts of the website, such as the HTML tags. If those stay stable and we build our identifiers on those sites to be relatively dynamic, the process will be fine. 

We do plan to increase usage.

The idea is to train up more citizen developers. We need to strike a balance between getting the tool out to the citizen developers and making sure that they're following the governance procedures as well. There's also a little bit of risk of it due to the fact that you give people licenses to build and then they can build something on their desktop. They can just, without going through the proper governance, run it. Therefore, you need to make sure things go through the correct governance. That's why we're trying to make sure we have a very good system in place so that when we grow and are training system developers, everything they do goes through the correct controls and governance process.

We're planning to keep building the users over time. We really want to start looking in the next year from more of a top-down perspective, across larger organizational issues where we can make more scalable bots rather than strictly or mostly automating one-offs. We're looking for where there's more commonality across different businesses that do similar processes, and maybe access similar data sources.

I'm not sure exactly how many people are using it across the organization currently. My guess would be at this point there are 75 to 100 users. However, I could be completely wrong. I'm just guessing, as I don't know all the citizen developers, and who in the operation's teams are using it.

I have not used technical support, however, some people who work for me on my team have. I manage a small team of developers. They have worked with UiPath consultants who are on contracts with our COE. They've been extremely helpful with working out some kinks that they've come across in their projects. 

I haven't used blueprints on my Automation Anywhere. We used to use Automation Anywhere and we are moving off it in favor of UiPath, though I never used those other tools myself. I use ALteryx and it has some RPA abilities, although I use it much more for just basic data transformation workflows. I have coded RPA bots and Python before. What I like, with UiPath, is it's still a tool that's based on code - Visual Basic, VB.NET. However, the coding is really for the most part restricted to your data manipulation, working with variables. The control flow that you normally would need to code in Visual Basic is all drag and drop. I really like that versus straight coding. It still gives you that flexibility of a lot of development environments, however, you can have that drag and drop canvas that allows you to really not need to program as much of that control flow. 

We moved towards UiPath as it's cheaper per bot and it enables more of a citizen development model as well. Automation Anywhere bots were only developed by our COE at the time and UiPath COE's going to use them also, however, they're allowing users in operations to use both Studio (if they have the taste for it) and StudioX. It gives a lot more citizen development capabilities for more advanced functions and automation-type stuff, whereas previously, you would normally need somebody on your team who happens to know BBA to do it. 

In the past, if you have someone from the team who knows BBA and makes something, and they leave and their code breaks, you're screwed. However, if you have a StudioX bot, if it breaks, it's going to be much easier to look into the issue and fix it. It's also supported by our C0E's tech infrastructure. Those are the main driving points for shifting off as well.

I was not involved in the initial setup. I've interacted with UiPath only as a user. I was one of the first users, however, I had nothing to do with deploying the tech infrastructure and developing the governance and controls. I'm just a developer.

We have seen a return on investment. Every project we've delivered that has some sort of time savings to it has had an intrinsic ROI. I don't know the total ROI across the organization, however. I work in one specific part of the company and it's been adopted in a few places. I don't know the total ROI that's been delivered yet.

It's my understanding that it's delivered close to a full headcount so far, in terms of productivity of capacity. There are approximately eight hours a day of time-saving for every workday of the year. That's where we are right now, as we've really just begun adopting it. We're not really deployed into production, and the larger-scale projects aren't in place yet. So far, the projects have been smaller tactical builds that we've been using and it's been delivering up around eight hours of time saving a day. 

I don't know the pricing enough to really comment on it. I know we're getting a better deal in automation than what we had with Automation Anywhere bots, at least per bot deployment. However, I don't know what the licensing costs are.

We do not yet use the Uipath apps feature or their AI functionality in our automation processes. That said, with AI, we're bringing it in and we're definitely planning to use it in the future.

I'd advise new users to make sure you have the controls and governance structures, first and foremost, and you want to make sure those controls are going to be in place and understood before you start deploying licenses to users. I make sure that everything is going to be done and compliant with the audit. As somebody who works in financial services, which is a very heavily regulated industry, that's something that really needs to be kept in mind. You don't want to develop what are essentially just user tools that are not going through the proper controls and treat it like a lightweight software development lifecycle project. You need to make sure those controls are in place, and yet, don't do it too much to the point where it's going to deter the users. At the end of the day, we're not making software, however, we still need to strike that balance.

I'd rate the solution at a nine out of ten. Nothing is perfect. I know you UiPath wants to improve the stuff that has not been perfected. I'm not going to say it is a ten out of ten, even though I'm struggling to think of what I don't like. Something that would be very helpful for UiPath is to go back to try to build OCR in StudioX. That would be ideal. Also, being able to implement different types of loops in the Studio would be great. Right now, you can only do a four-loop in a repeating loop. If we could implement wall loops, that would be nice. 

My experience in using UiPath, in general, is in developing traditional bots, assisted bots. There are the typical mundane applications that we're trying to remove in order to add value to customers. 

The solution is used for extracting information from documents and consolidating data, maybe from various Excel sheets. I've used applications, such as PDF, Tableau, and a number of different entities as well. It varies.

I haven't really followed up so much in-depth, however, I know that a lot of the end-users that I've worked with and talked to, that have removed some of the processes, think it’s great. I've got many more strategic types of tasks to do. The one thing users look forward to when they come to work is when something’s been removed from their plate, one piece at a time.

Collectively, I find the UiPath features really complement each other. If you have one tool or another resource available, you're really able to get it into a solution.

They've implemented their stuff very well, considering how fast they've come up with new tools. Usually, it’s a messy situation, however, with UiPath, I've not found that to be the case. It's pretty impressive, the rate at which new tools are released and how well they're thought out, and how usable they are.

From an employee morale perspective, the company is getting positive feedback.

We’ve seen some reduction in human errors and time savings. Depending on what it is, your time savings could be two to three to ten times more in terms of time saved. It’s easy, too. Error reduction is absolutely almost down to nothing.

In terms of cost savings, some of this was done pretty casually, so the numbers are maybe not official. We’ve got 20 data samples, and we're timing it exactly. However, when it comes to time savings, there's always been a very significant amount.

When it comes to ease of use, some of the tools they're providing are in discovery or task capture. You can go out and send this off to somebody and it's pretty self-explanatory in a half hour. Prior to that, people might be using different steps with built-in Windows pieces, which is horrible for capturing automation. If all you have is a hammer, everything looks like a nail. Therefore, adding in this ability to annotate the screenshots with ease, that alone in the development process helps significantly. I'm really liking the discovery tools that complement the product.

All these discovery tools are making building automation easier, from an analyst perspective. It removes the wheat from the chaff and narrows things down, and you begin to see what you need. By clicking on different elements, you can see where they can annotate. It saves a lot of back and forth and time. Not only does the subject matter expert not have to spend time away from their work, you're also not going back and forth and trying to clarify items any longer. It makes things more compact and it’s easier to get to the end goal.

I completely trained on my own as a developer with the UiPath Academy. I was able to do it for free. It's the only onboarding I received. I had nobody else to go to, except for the videos and the forums.

The greatest value of UiPath Academy is that it is free. Now, it’s completely about motivation, and not cost-prohibitive. You just need to be motivated to learn and you can jump in. You don’t have to spend something like $800 and have maybe a company sponsoring you to get started.

People, in their careers, can become relevant again. If they are in a dying industry or disrupted industry, they can get into something that's growing rapidly. If you have a computer, and a decent internet connection, you can have a new career in a fairly short amount of time.

The forum's a great place, however, for a new person, it was better some years ago. It's grown too fast, and it's not that nimble. Previously, if you asked questions, the response time was quicker.

Since I've learned UiPath, there's so many more people rushing and getting into it. With the demand for RPA jobs, the ratio of expertise to novices is very, very low. Before you had a small community and you had a lot of experts and just a few new people trickling in at a time. The influx of new people, it's just growing factor by factor. Where previously there was one person that only had a few questions to answer, now maybe that ratio is now 20 or 30 people. You're not going to get the answers that you need as fast. Luckily, the quality of the Academy is so good, if you look around, you can eventually figure things out.

The issue is that, with so many people, a lot of questions are getting asked before anyone even looks to see if an answer is already there. It tends to make it harder to find relevant, real questions that need to be answered. There are people who are not doing the due diligence and looking at the tags and spending a little extra time before throwing the question out. It makes that part hard to manage.

With people that have already been up-skilled, or already been skilled in the past, UiPath needs to find a way to send some sort of notification to them when items update or change. They need to send out a message to experienced developers to say: “Hey, look at this and push it out."

If you're not going to the Academy and looking for something new, there needs to be some sort of way to say: “Hey, you've been certified. You haven't been in this course. You should look at these things.” I started looking at the Academy and found new elements. When I mentioned something, like, "What's that?" the new guys were aware due to the fact that it was in the Academy from when they started and was not there when I finished.

Basically, just having some sort of mechanism for spreading awareness to existing developers, or pushing something out to them, maybe even through the interface, would be helpful. Whether it’s a little highlight or a little icon to alert users to “hey, here’s something new, something pushed out.” And it’s not just something where you have to go in and read some boring five or six pages of notes, to know that this thing is there. It needs to be visual.

I started using UiPath, which started with training, in the fourth quarter of 2018.

It's a very stable product. I haven't had any issues. If I found or thought something was unstable or something, it usually ended up being me, or an operator error.

I've seen UiPath scaled. Personally, I haven't had issues one way or the other, however, I've heard good things. That said, I can't speak too much on it from the perspective of personal experience.

I have had some interaction. They had a pretty good SLA, in terms of response time. Of course, that has nothing to do with actual solution time. That said, what I remember with everything was that nothing stood out. Usually, you remember some anger or something. I didn't have anything like that.

I'm certified in Automation Anywhere as well. Right now, Automation Anywhere always has two products out, in the sense of getting ready to move into their A360 with the newer product. They're just trying to get that product to maturity. Right now, we have different deployments. Automation Anywhere is cloud-native. 

While they're both RPA, they each have I think a different niche, depending on what the customer needs. 

As a developer, the learning curve in version 11, the prior version, had an easier learning curve compared to UiPath. Automation Anywhere has an edge, in terms of ease of learning for business users and citizen developers.

360 has made the learning curve harder. It's going to add more features, more flexibility. And with that comes a learning curve. Still, the learning curve might be a little easier. 

My deployment experience was not just through UiPath. If anything, I'm pretty agnostic to any platform. I was an analyst, and I was involved with, in general, putting items into production, and going back and forth with developers, and seeing if there were any issues or problems.

I've talked to other developers, and I haven't heard of any particular issues or problems, with UiPath, or anything that was more than just human error or an oversight.

If you're smart about it, you understand what your needs are, you can get an ROI out of it without having to go get the full-blown solution. You don't want to drop $20,000 on an orchestrator unnecessarily. You can ease into it, into adoption, without dropping a lot of money. Maybe some attendant bots, and an unattended locally on a large scale, in a small area.

If you do that and start easy, you'll get a return on investment. Eventually, when we start scaling, we'll pay for the orchestrator. You'll need that when you start getting a lot of bots, and it becomes like herding cats. It gets crazy. That's what you need an orchestrator for. While you can avoid a cost at a certain point, you're probably getting diminishing returns, and then it's going to be more costly to manage something all over the place. It's best to start small and then add on. 

We haven’t been using an orchestrator. It’s a bit like having your hands tied behind your back, as you're not using some of the features that are available with that. However, it still provides these workarounds. You are able to still do some really robust work. It's been great.

We are using, more or less, the more recent versions of the solution.

Before starting with UiPath, a company needs an understanding of the culture at their company. You need to ask if your employees are resistant to change. Certain companies where people are entrenched in their ways, or scared of bots taking their job will be worried. A company needs to lean in and give them an understanding of expectations and pay attention to them before starting. Just pushing it might throw people off.

The personalities of people are the biggest factor. I used to come from a lean Six Sigma background. When companies bring in these Six Sigma programs, it's the same thing - resistance. People say “oh, you're the job cutter.”

People throw that out as automation, and I say, "Hey, people have been automating since steam engines. It's been consistent. It's just the face has changed a little bit. It finally hopped back onto computers. However, automation has been nonstop." 

You just have to realign and adjust yourself. You can’t be resistant to change. Change could be a good thing. Not all things are, however, workers need to be rational and think about it. If your company doesn't move faster, adapt quicker, then your company's going to go away, and everyone will be gone. It’s competitive. That's sports. That's business.

Overall, from what I've used, and what I've touched, and some of the things I've seen without actually putting my hands on it, I'd give UiPath a nine out of ten.

I'm just not the type to give out tens so freely. I haven't gone deep and wide enough to touch everything. From what I've seen before, if you span that out overall, I'd probably put them up in the nine range, personally.

Our use cases have evolved over time. We have use cases for screening and onboarding candidates, feeding new hires into the payroll system, and timekeeping. Right now, we are working on a document understanding use case. It is going to help us read supplier insurance forms.  

UiPath has enabled us as an organization to perform an array of tasks with more proficiency and efficiency. Automation is very important to our organization now and UiPath has played an immense role.

UiPath makes building automations incredibly easy. The platform is very robust and it is scalable. UiPath also has a strong community, which has helped democratize RPA in a true sense. The community and expertise can be leveraged quickly to meet a common goal.

The UiPath Academy has helped us move forward more efficiently. It is a great source of information and knowledge for both new users and those taking the advanced courses. I see the UiPath Academy evolving in the future.

One of the features I've found valuable is UiPath Studio. We have a huge development team of about eight to ten people and they are currently working with it. We also have a citizen developer program that is leveraging StudioX. 

Orchestrator is important for us as well. 

These features are valuable because they allow different groups of people to complete their tasks. UiPath is a robust platform. It helps us cater to different audiences. 

The licensing model is sometimes very confusing and could be simplified for customers. That would help us understand, gauge the offer, and work it into our existing infrastructure. 

We started using UiPath in 2017. We have had a great journey with it. UiPath has helped us scale faster, especially with RPA implementations. It also helped us evolve through our automation journey. 

My impression of the stability is that it's like any other software. We have never had a problem with UiPath and the platform has been stable enough to enable us to scale a lot. 

We have been happy with UiPath's scalability so far. I would give it a nine out of 10. We are currently deploying about 95% of our automations through UiPath. We are very into it and plan to expand from there. 

Yes, we did use a different solution but I cannot disclose which. However, I can say this much: we decided to switch because of the community UiPath has built. Also, the platform and product are packaged correctly. Everything is laid out well and it seems like UiPath understands what businesses need. 

The initial setup was straightforward and easy. UiPath has an incredible team in place. They help us every now and then. It did not take us much time to go through the initial setup and get the solution deployed. 

We have realized savings in the millions of dollars overall.

The pricing structure is very complicated. Someone from the organization has to sit down and set aside some time to fully understand it. 

Yes, we did evaluate other options but I cannot disclose which. 

Start your journey with UiPath. Engage someone from UiPath and have them go through the journey with you.