UiPath Platform Reviews

In terms of product testing, I use it in the product with the test suite to mount the test manager and then follow with the requirements. After that, I create the test cases and I'm running them on different platforms on the web so that I can proof back from the web with test suites.

I use the different tools of UiPath. However, in the future, I’m hopeful UiPath will help us to expand into different countries. right now, I use it personally. Soon, the entire company will be using it as well.

The automation of the cloud offering helps to decrease the solution's total cost of ownership.

The document understanding is great. I interact with different documents of people. The IDs of one are different from a document or a PDF. For example, our contracts, et cetera. It can understand the differences.

I’m not quite sure about the ease of building automation using the solution just yet. It seems to be moderate. Not too easy or difficult.

The solution has helped our organization save costs. It’s likely saved us about $10 million.

UiPath has helped us reduce human error. That’s had a partial impact on our business. Our techs understand the different types of processes and competencies it can help with. Regular users cannot see this just yet.

It has freed up employee time. It’s allowed for a focus on higher-value work. Employees seem happier. It’s an easy tool to use and deploy.

We’ve used the UiPath Academy courses. All employees take the course and learn about it. You still need more education afterward, however, the biggest value of the Academy is the knowledge. I've got people who are new in the company and I can just say "take these courses." It's accepted by everyone as part of the process.

The graphics could always be improved.

I've been using the solution for three years. 

The stability of the solution is good. UiPath has a different release each year at the moment.

The scalability is great. You have a manual so you don't have to do the courses. You can read through it.

We have about 200 users at this time. We have different areas in the company that uses UiPath. For example, the administration uses that tool. You have a test suite and you can have development using the UiPath Studio as well.

Technical support has been great. Whatever my query is, they are able to answer it.

We did not use another RPA solution before UiPath.

The initial setup was straightforward and simple.

The deployment took about one month.

The pricing and licensing have been great.

We did look at different automation tools before choosing UiPath. We looked at Blue Prism and Automation Anywhere, however, we ultimately chose UiPath.

The UiPath Academy courses were a big selling point. Also, its ease of use. Automation Anywhere and Blue Prism were so difficult to understand. UiPath is more interactive and it's more visual.

We're a UiPath partner. 

I've used both cloud and on-premise deployment. Right now, I am using the cloud. 

At this point, we do not use UiPath's apps feature.

We have not used the solution's AI functionality in our automation program yet.

If I were to advise anyone on using UiPath, I'd let them know it's easy to use. You have manuals and courses to help you navigate the solution. The new releases make it so that it continuously gets easier. 

I would rate the solution at a ten out of ten.

We're still building up the program, but right now our primary use case is for report review. We're looking to branch that out more.

It's reviewing reports. I worked for a bank and there are reports of transactions from the previous day. UiPath was looking for anomalies for fraud and things like that.

It's still very early on but we have caught a few instances of fraud that we would not have if we weren't using UiPath. 

UiPath has reduced human error. We're very early, so it's not a big impact, but we did find a few instances of fraud that we would not have found without it. 

We see time savings for our users in the sense that they now can do more tasks that should have been done all along but weren't getting done. That's more where the gains have been this far.

I like the whole ecosystem. They're not just looking at the automation tool, they're looking at automation from end to end. 

It's pretty easy to build automations. I have a coding background so it's not particularly challenging for me to use Studio, but for a person who does not have that coding background, I think that the Visual Builder guides you through the process pretty easy.

UiPath Academy is a good training program for people without that coding background. It's good to get them into the mindset of how exactly flows works of automation.

The Academy offers us familiarization with Studio and how it functions.

The API integrations need improvement. They should build a better framework for the ability to integrate with other external APIs.

I have been using UiPath for less than a year. 

I would rate the stability an eight out of ten. 

It's pretty straightforward. It either runs or it doesn't. Occasionally it does crash and we've had to restart services and whatnot to get it going again.

We haven't been using it enough to see how it can scale. 

There are two ITs who use it in my company.

We have plans to increase usage. 

We don't really see our staff as being good candidates for citizen development. There are a few that could, but we do plan to expand out into other departments as far as gathering ideas and implementing processes for other departments.

Their support is pretty average. It's not good or bad. It's off-shored. There are always difficulties with cultural differences and language barriers. They know what they're doing but sometimes it takes a while going around in circles to get the question that you're asking across. That's pretty normal. Most companies are the same way. I would say all companies have huge room for improvement there.

The initial setup was pretty straightforward. It was easy. The installation instructions walk you through the process. We didn't run into any problems. It took less than a week. 

We also looked at AntWorks and Blue Prism. We went with UiPath because of the maturity of the product that seemed far more mature than its competitors. The product seemed more thought out.

Based on our experiences, I would say you have to have employees that are dedicated to doing this. This can't be done as a side project.

I would rate UiPath a nine out of ten. Nothing is completely perfect. The stability of it could use a little bit of improvement. The support is not great. UiPath is very good, but no one is perfect.

We've got mostly finance use cases including a lot of accounts receivable and stuff like that. Then, there is a lot of work where I do trading settlements, so a lot of settlements as well. The back office automation's there, too. We're still getting used to it and still getting started.

We've been able to expand up to citizen developers, and have been able to show them how to do various things. It's easy to pick up, so a lot of citizen developers are learning it now, and with little to no coding experience. It's been great.

The recorder has been great. Just being able to really start your automation there, and just modifying them a little bit and then getting them really in production has been helpful.

The solution has saved costs for the organization. For example, I used to do back-office stuff, and I was able to move to more of an IT role. That was definitely a savings there, and obviously, no one had to automate it after me or do it manually after me.

We have found that the solution has reduced human error as now it's a bot doing it. It's really reduced errors due to the fact that no one has to check each time to ensure the work is error-free, and, in general, there are a lot fewer errors. 

The solution has freed up employee time. For example, as I mentioned, I myself have moved off of back-office tasks and, in doing so, the company did not have to hire someone after me. We've likely saved 10,000 hours in a year. We're really happy with that result. The additional time has enabled employees to focus on higher-value work. People can now just quickly audit it and then move on to something more important.

The Academy is great to use. We've been able to learn a lot from there. That's what our citizen developers will look at as they get more familiar with the product, and as we show them how to develop items. It has positively affected the process of getting employees up to speed on the solution. A lot of them have little to no coding experience and the Academy has helped by showing them what they need to learn. The biggest value is if they have little to no coding experience, it'll really start from the basics and teach them from there. You don't have to teach them all the variables and stuff like that.

While I like the Academy a lot, it could maybe go deeper into some of the topics. The basic ones, such as Excel, which is already a decent course, could maybe go into more specifics. My issue is that, while the basics are good, getting into the weeds a little more could be very helpful. It's hard to specify exactly what is needed, however.

We've used the solution for about a year now. We're still getting used to it. 

Our stability is great. You rarely have any downtime, once you build it. There's obviously the support, however, I'd say it's pretty minimal.

We're trying to work on scalability at the moment. It's there, however, we have a lot of different departments that do a lot of different things and that's where we need to really work on scaling. It has nothing to do with UiPath. It's just about getting everybody trained up on everything on our side. That said, we can see how it is possible to scale in the future. We do plan to increase usage.

Currently, we have about ten users who are familiar with UiPath. It's not too many. They are either developers or just everyday users that support it.

In terms of technical support, from the perspective of tickets, et cetera, I would say they are pretty good. We've only done a few upgrades so far. We've only had it for a year, and so far, in that time, support seems great. They have been helping us out on everything.

We did not previously use a different RPA solution.

I can't speak to the initial setup, as we had an outside party handle pretty much everything. I actually joined after they onboarded us and everything, and therefore wasn't a part of the process at all.

We have two to three people that handle maintenance tasks, on top of the AI.

We had an outside party do the deployment. It was a consultant. They did it for us.

I don't have any insights into the licensing process. 

While I joined after UiPath was implemented, my understanding is the company did look into a couple of other options, just to see their capabilities.

I would advise potential new users to go for it. The Academy offers a great starting point. It's a great tool. I would recommend UiPath.

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

We use attended and unattended bots, Orchestrator, and Studio for development.

We're seeing increasing adoption of Studio because more people see how easy and straightforward it is to use a lot of the features. It helps that UiPath training is free. Our entire team, including our salespeople, have gone through the training. It's free and it makes a big difference. For the salespeople, they're able to talk more intelligently about RPA.

On a scale of one to five, judging how beneficial it is, I would rate the training a five, for sure. In fact, I have taken a lot of ideas from their training to educate my customers about RPA. When it comes to RPA, a lot of it is education because some of them don't know exactly how automation can be done. I've told UiPath that I use their training in my presentation, and it is great.

We are working with a technology company called Rammer, Rammer.ai. What the Rammer software does is listen to conversations to learn the details of what is being discussed. A third-party system is used to transcribe the conversation into text, then Rammer will learn the details without much training. It knows the topics, it understands what is talked about the most, talked about the least, how much we are adhering to the script if it's a call center use case, or if it is a simple meeting use case then it knows who is assigned what tasks, it recognizes the follow-ups, and it knows the summary of the discussion. All of this is summarized in a nice, consumable manner. So now, when a bot knows all of this information, it goes into Orchestrator, logs all these activities that are picked up by unattended bots downstream, and they trigger all those processes back. So it's a massive consumption of all of those heavy use cases.

We have not yet run automations in a virtual environment, although we do have customers who are asking for it. We are not sure if we will need UiPath's help for this yet because we haven't tried it.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate it a five. Really, it depends on how clearly we understand the requirements. So a lot of times we are able to find process gaps, which wasn't the case earlier before we started thinking about automation in this manner. I would say the ease of use is actually dependent on some of those factors as well.

Usually, starting is the biggest challenge for most people, and I think this is because it is in a trial environment and there is a lack of documentation, with multiple people doing one part of a small subset of a task. There are these challenges and then if none of them are documented, you need to figure out the process flow. From person one, where does it go? This can change when people can do multiple things.

It becomes a very complex web to understand and navigate through. We need to understand the task and how it should be performed. For developing the robot, it's very important to have the clarity upfront, otherwise, we cannot code them. That is the biggest challenge, I feel.

From the point that a UiPath license is purchased until the first bot is ready is almost immediate. This is because we usually start with a PoC on a small scale, just to see if automation with this approach makes sense. By the end of the PoC, we'll normally know exactly how many bots are needed. Sometimes it is on us, more than the customer when we cannot estimate every process that is outside of the departments and division that we work with because we just work at finance. For example, we can't just estimate what marketing would use, and so on. That will sometimes delay things.

The attended and unattended classification and simplicity are great, and it's easy to explain to people. Right off the bat, the task performing the lowest granular entity is very clearly defined, which is something that I like.

I really like that I am able to tell the story, using Orchestrator, how humans work, how bots work, and how humans and bots work together. Orchestrator really tells a lot more than just being a simple task manager.

In future releases of this solution, I would like to see more packaged solutions.

We would like to see intelligence built into the core. Specifically, we would like to see the recognition of human to human conversations. That intelligence would be great because we have some very important use cases in that space that we are seeing. Our focus is moving closer to one hundred percent in that space, as all of our new work is related to conversations.

UiPath should offer an on-demand cloud-type model where you can get bots for five minutes, ten minutes, an hour, or whatever duration you need.

With respect to the stability, on a scale from one to five, I would rate this solution a five.

We don't see many failures, and this is partly because of our approach. We start by creating something called a heat map, which I learned in some of the training from UiPath. The training clearly explains how to handle errors. It includes which process to automate fully and which processes should be automated partially, with a human in the loop.

We start with the right approach. We understand the process and we have the heat mapping that gives us full clarity of where the exception flows are and how to handle them. So when you do that, it becomes second nature to handle those exceptions. We are pretty comfortable, and we are applying the best practices, which adds to the stability. 

Talking about our own people, we have roughly sixty-five who are either developers or architects. For our customers, the number is growing all the time. The requests for training and setting up workshops for them comes to us every week, basically from different customers. We don't know the extent of automation beyond the people we work with because there are other vendors like us who are also there, so we don't have the exact number but what is refreshing to see is that even VP level or senior-level employees are interested in learning. They ask us if we can hold a workshop for their entire team, whether they're doing the development of bots or not. Hopefully, that will increase the numbers, but right now I don't have an estimate on the total number of customers. I only know on our side.

We have tremendous support from UiPath. We can say that from our perspective, we are very fortunate to be in the Pacific Northwest and that team is one of the best. It doesn't matter if we are big or small, they help everyone. So every time we have an issue or a challenge, whether it's engineering, presales, architecture, or development, we get all the support.

Our customers usually don't know much about RPA, so one of our jobs is to educate them on it to get them interested. Gradually when they understand, it moves forward.

In the majority of cases, the initial setup of this solution is simple to medium in terms of complexity. We are finding very few complex scenarios at the moment.

I think the overall architecture is simple. It is very clear and very straightforward. UiPath's product team is doing a great job in is creating a lot of very out of the box integrations and analytics, and that always helps. That is good, but I think if people are not trained yet and they think that it's easy, drag-and-drop, and simplistic, those folks struggle a lot.

We've seen that people think "Oh yeah, it's just some scripts and drag and drop so we can do this easily" and that misconception exists. We don't treat it as an easy scenario, so we gave it all the respect that proper Python code, a data science problem, or a highly complex situation deserves. When you approach it that way, it's at best at a medium complexity.

In general, we treat it right in the middle. It's not that straightforward, but the architecture is simple enough that the development complexity is medium. That's the simple and medium combination.

When it comes to ROI, for some scenarios it's immediate on the day you go to production. Doing the math, if it is automating thirty hours of work in a week, it is going to be the moment you turn on the switch.

Sometimes when the expectation is set at a different level, the KPIs are different. It may be that the customer is looking to have an "X million" dollar cost saving. It just depends on how you're defining the KPIs. So in those scenarios, obviously it'll build up to that saving.

A lot of people talk about the total cost of ownership as being a real saving or real value for products. So there are just all these different layers of complexity in that. I mean in theory it is immediate at the moment you turn on the switch, but then you need to consider the bigger picture, and it's not a straight answer. It'll be different.

The most important tip that I would share with respect to the licensing is that you should not think of a bot as being able to do only one thing. You should always consider the downtime and utilize the bots properly. That's the way you can have exponential ROI from just that one simple investment.

Even though these bots don't really cost much, you still want to say there are resources like a dedicated machine that is there, there are electricity and all kinds of resources that also go into it. So the overall cost, we should look at that. If a bot is doing ten hours' worth of work in five minutes, there are twenty-three-plus hours work that the bot can actually do. So, think of orchestration.

Some of our customers have tried different solutions. There are some customers who have even tried a lot of competing products and they're not satisfied. They have a very low expectation from what automation should or could do. So for us, that's even harder in terms of educating them.

People who don't know anything about this kind of automation, sometimes it's a little bit simpler to just run them through an hour or two of our workshop, but people who already know about it may have set their mind in a certain manner. Sometimes for those customers, the customers with experience in other solutions, are usually a little bit more difficult to convince. They have doubts that have come about because of whatever they've been using, and they don't fully understand the capabilities because UiPath does things very differently from others.

So on both ends, education is a challenge.

We are very excited about the new things that have been announced recently. There is the integration with AI, with AI fabric. There is Studio X, which has pre-built APIs with Microsoft Office and all the other Salesforce integrations that they've come up with. These are very exciting because that will increase adoption even more. People already understand unattended and attended automation, and now with Studio X being available so easily, and with analytics being part of its fabric, it's going in the right direction.

We have a very nice step-by-step flowchart that explains how to approach or what processes to automate first of all, and what are the chances of change or variations and all of that. While we are developing this, we at least are following the best practices from all the training that we received to ensure that we have taken that int consideration and we have not picked the process that is hard to automate, or which should not be automated. Then, it's more of a system change or any transformation that the customer should do first and then do automation. Basically, we should not do automation for the sake of it.

At my company, we don't work with any other RPAs. When it comes to customers choosing this solution, it should depend on the use case. If there is a strategic advance that they need to get and they need to really think of analytics and intelligent automation, UiPath makes a very compelling case. I think that it is important to choose your solution wisely and do it based on your use cases.

From a cost perspective, there is a big difference between the attended and unattended bots. One is twenty-five percent the cost of the other, which is a massive difference. Our customers use both, and we like this a lot because the way we utilize attended and unattended bots are the right way to do it. If you need to do multitasking and handle a lot of tasks, the choices vary.

Specifically from a pricing point of view, I think it is justified. When I first heard the price, and obviously I didn't ask about the duration or subscription levels, I thought it was a monthly price. Hearing that, I thought that it was cheap. Later, I was told that it was an annual fee. So for me, I understand that my customers can afford this price, and I am happy with that.

I would rate this solution a ten out of ten.

Currently, I'm dedicated to working within a finance organization. It develops processes in the scope of five months. I do not use the solution in a contact center environment. I work on projects for shared services.

It's FTE-saving. Since the beginning of this year, I have covered more than four FTEs. That means that for half a year, I saved three FTEs. That's a huge benefit.

The easy development process is very useful for us. I know how to use it, and I'm able to prepare and add to a solution in one or one and half weeks. It depends, of course, on the process, however, largely, if it's a simple process, it could be developed from the beginning very quickly.

It's very important that I can create end-to-end automation using UiPath. Thanks to that, the business is free to do more advanced processes and is not overloaded by less important, repetitive tasks.

I've noticed that UiPath has reduced human error. The first benefit is FTE saving, however, the second is quality of work. Human work, if it's repetitive, it's very often related to human errors. That said, if something is programmed really well and automated it works without the need for human intervention.

I had a problem with one thing and that was exporting activities packages between the test server and the production server. I'm not sure that it's my own issue, or a general problem from the global perspective of UiPath, however, I have a lot of problems with packages, using the test server and production server.

I've used the solution for quite a long time. I started using UiPath at the beginning of 2017. It has been more than four years.

The stability is good. Everything works well and I don't have any production bugs. I only have positive feedback, It works and there are no unexpected errors.

The scalability  depends on the developer. If we have an advanced developer, it is really easy to scale. If someone's preparing, for example, components, it is quite easy. From UiPath's perspective, it is easy to scale, however, that said, everything depends on the person who uses it and how familiar they are with the product.

I had a chance to contact UiPath when UiPath licenses needed updating. I had close contact. I wrote a ticket and I had contact with them in less than an hour. I was quite pleased with their response time. 

I made the right decision to go with a solution that can scale automation without having to pay attention to the infrastructure and to develop my skills in terms of RPA.

I had to do tests with Blue Prism and UiPath. Currently, I use UiPath, as I find it's much easier to use than other RPA tools. For example, I really like Orchestrator, from a user perspective. The control of both is really easy as it's centralized in NonProduction Orchestrator, and it's really easy to operate it. There's general ease of development. In Blue Prism, for example, if you want to develop something, first you need to prepare the object layer, and after that, you can go to the business layer and connect it in one solution. In UiPath, we create just a component and connect components together which is more logical.

I was not exactly involved in the initial setup as when I joined the company, UiPath had already been set up. Therefore, everything was prepared to start development. That said, for a few months, I worked in UI as a consultant for external clients. During that time I had the chance to install UiPath for external clients. In that sense, I've been involved in the installation of UiPath previously.

The initial setup's level of difficulty depends on a client's needs. At first, we need to think about the strategy of the client. In general, UiPath provides different types of architecture and it's generally straightforward.

The setup could take weeks if you need, for example, to order servers. However, if servers are already on-site, we can begin the installation. As I recall, I set up Orchestrator in a few hours.

We have calculations for that and we are on the right path. There is an ROI when using UiPath, however, I thought it would be higher. That said, we can calculate costs related to the UiPath environment and compare it to the automated processes created and we can see we are on a good path. It's hard, however, to provide exact numbers at this time. 

I'm not sure if UiPath has sped up or reduced the cost of digital transformation. It's a tough question, as the license for the solution is too expensive right now. In Western Europe, it may be okay to pay such money for a license, however, where I work now, in Poland, the license cost is too high for the local market.

We have a connection to ServiceNow. In ServiceNow, there is an approval process to publish UiPath processes on the Production Orchestrator, and that's easy. I'm able to set schedules or run a process model from our Production Orchestrator.

We have different servers for development, including a different server for Orchestrator and a different server for production. However, everything is in my company environment.

At this point, I only use unattended automation. Currently, there are no projects for attended automation as it's more for the business side. I am just a developer from the IT side. I am not involved in any business department.

I'd advise those considering the solution to find a really good developer and maybe a solution architect. Some time ago, UiPath had marketing such as, "everyone could be a developer," and so on. That said, it does not work like that. UiPath developers should have a large IT background. During my career, I've seen a lot of projects fail due to developers' lack of skills.

My biggest takeaway from the solution is that automation is a process that doesn't have a start and end point. It's an ongoing process.

Overall, I'd rate the product at an eight out of ten. If the licensing price matched the local market's capabilities, I'd give it higher marks. I would like to start deploying the UiPath solution in Polish companies, and there is huge scope to do it, however, for now, it's too expensive.

We primarily use UiPath for outsourcing. Customers call us when they need extra people to fill positions, on a temporary or permanent basis, similar to a temp agency.

The biggest use case that is running right now is that we get job openings or requests from a lot of different third-party brokerages, customers, clients, vendors, et cetera. They all arrive through different platforms. We get an email saying there's a request, please check it out and let us know if you have someone to fulfill the position, and the request is implemented through UiPath. It's automated. We've created all of the mailbox folders based on the sender and the subject, so we know which customer or which broker it is. Then, we make the email follow a link to the information for the job opening or the inquiry and we put it into our Salesforce system.

There are a couple of smaller use cases as well, where we have task operations that have to be done weekly or daily. Mostly it's reading emails or reading schedules and making changes in files.

The automation of job inquiries has a lot of sufficiency on how we operate as we used to have multiple people need to be available throughout the day to manually check if an email with an inquiry came in, and that would require them to drop work and open the email, check it out and maybe take action immediately. Now that the robot is running and taking care of the need for filtering through all the results for them, employees can stay focused on the other tasks that they have. They don't have to keep an eye on a second monitor every time and drop everything they're doing to read an email only to decide what is relevant or not.

I understand work has to be tested. It hasn't impacted the entire company yet as I've been here a little short of a year now and we haven't made that big of an impact just yet. 

The most valuable aspect of UiPath is the community in terms of the way they open up their platform to the community and make it freely available for people to try and to practice. The amount of feedback from that community makes it very easy for us to get into UiPath and if you're trying something that you've never done before, you at least have some insights. There's almost always someone who has done it before or who has asked the question. I would say the community is one of the biggest extra treats for UiPath. 

From a technical perspective, I like the learning curve in the Studio and in the orchestrator - or the Cloud Platform as they call it now - due to the fact that it's easy to get into. It's easy to grasp the basics and to get started. You can scale up as fast and as far as you'd like or need to for your customer. It can do everything. You don't have to learn everything in advance to be able to work with it. It makes it really approachable.

Building automation can be really easy. The biggest challenge is to find the easy use cases as the use cases in the company can get quite complicated quite fast. That said, using the recorder in the Studio and then converting that to work in a mobile office is quite easy. I started in 2016 or 2017, and between then and now there's been a lot of changes. It's always been easy for developer-minded people to get started. However, now with the introduction of StudioX, it is even more focused on the different users and they have a different entry point for them. What I like about UiPath is that the training is really comprehensive. You can almost just record what you do by hand and then StudioX will translate that into a robot and then you can fine-tune it to make it more robust. Smaller costs can be easier steps. Just press record, do what you do, and then you're able to work with teams. 

Scaling automation without having to pay attention to infrastructure does make my job a lot easier for now. What I do see in companies is when they've taken the first steps and they start to scale up, a lot of them have policies or ways of working in place where they want to stick to the ways that they know. A lot of time I see customers will, in the end, do it by themselves anyway, so they use all of the upscaling functions that are available as they want to do it the way that they always did. 

UiPath enables us to implement end-to-end automation starting with process analysis, then robot building, and finally monitoring of automation. However, while it does facilitate end-to-end automation, it does take a lot of the development and running and monitoring of the robots on itself. That is something that is facilitated really well by UiPath. The process discovery and the analysis is rather newish within UiPath. Maybe it's not as well integrated into the community platform.

At this time, UiPath has helped to minimize our on-premises footprint as it is a cloud-based solution. It's important that the on-premise footprint has been minimized as it makes it easier for us being a small company. We have 160 people working for us in the Netherlands and then a couple in the Caribbean. Bringing new technology in like robotic process automation and then asking from the IT department to get me free service and results of my configuring and have all the discussions about what goes where, how the security works, how to find the work, who gets access, et cetera is easy. This is due to the fact that UiPath is offered on a cloud basis and I don't have to do all that on-site work, which allows me to get to building and talking about RPA quicker. 

The fact that the vendor handles infrastructure, maintenance, and updates saves time for our IT department. It helps us to implement a lot faster. The client companies can have a reliable cloud solution to help them do at least the first steps to get them acquainted with the product. It makes it a lot easier. It helps me a lot, and it helps our customers in starting out as well.

UiPath has decreased the time to value in that since it's cloud-based, I can deliver faster than I would be able to do on-prem. If we have an idea, or if we want to scale up, we can do so faster in the cloud solution than I could on-prem.

The product lowers the overall total cost of ownership by taking care of things such as infrastructure, maintenance, and updates, however, I'm not sure what would happen if we scale up.

The automation Cloud Platform has definitely helped reduce the time it takes to create automation. It brings a lot of things together. It's easy to use for clients and customers. It makes it easy to bring different disciplines together, so I don't need to think about how to reuse my code, or how to explain to the customer, and I don't need to share the processes to be able to release, run, and monitor and to get reports on the results. 

UiPath has reduced human error. There are fewer errors and the processes are less error-prone and once the technology has proven itself within the company, within the customers, people start to trust the robots to do what they do. Employees don't need to check the work that had been done as they know that if the robot reported that it was done correctly, then it was done correctly. In that way, it has saved a lot of time by not having to check anything. 

It has also freed up employee time. It's a three-person team and it saved them a couple of hours a week doing the work that they used to do. It saved them a lot more focus as they didn't have to monitor the email inbox all the time. They were able to apply more focus to the other things that they were doing. That said, it's hard to quantify the gains. However, overall, it has made them happy. That's one guarantee. They absolutely love that they gave the mundane work away to the robot because it was bothering them to be monitoring an email inbox all the time. It's given them the time to focus on cases that match the right people to the right inquiries or openings. I don't have any metrics on it, however, anecdotally, they tell me that it helped them to do the rest of their work better as they could apply more focus to more important tasks and placements are better attended to. There's much more focus and attention and better matches being made.

The solution has saved costs for our organization.

I'm trying not to sound negative about it as I like them a lot, however, the process mining and the process mining features stem further away from the development of the robots and the monitoring. The development, run, and monitoring are really closely knit, or really close together, and then process discovery is starting to get there. It's on its way, however, I don't see that it's as closely connected as the other three parts.

The automation operations have not brought down any company costs. Automation operations have gotten more expensive due to the fact that we added UiPath to them. That said, you do get gains at a different branch of the company. We didn't replace anything with UiPath. We weren't able to skip a step or program or tool, which makes it an added cost.

More documentation would be helpful, as they change rather quickly. There are two yearly stable releases and then a couple of community releases and data releases in between. Sometimes not all documentation is changed as quickly as the features are. Sometimes you can find something in the documentation that is not the answer, or not available in the product anymore. That's simply a side effect of how fast they develop the product. 

Sometimes it's not entirely clear what features are, for example, available in their community edition, or in the on-prem, or in the cloud. The difference between the on-prem and the cloud has become clearer in the past few weeks, however.

I've been using the solution for three years now. 

I started out at my previous company with systems integration. We started out with discovering robotic operations, discovering the tools, and suppliers. We chose UiPath and one of the competitors, as we found them to have the best suit with our customers. That was the end of 2016. That's when I started doing training in UiPath and started doing some custom integrations.

Now, I switched to a new job at a different company where they want to start an RPA practice as well and they chose UiPath solely for RPA.

From the operations standpoint, the stability of the cloud it's very good. I haven't had any issues with stability. The Studio will crash at random times. I've identified two scenarios where I'm able to make the Studio crash every time by just doing the same actions.

However, other than that, the automation was really stable, and I haven't had any issues or incidents. In Studio, I'd say it is good enough, however, there is some room for growth there.

Scaling automation without having to pay attention to infrastructure is a bit pro for UiPath as I'm starting an RPA practice. We don't have a lot of infrastructure engineers to build the project yet. Therefore, a lot of the time, with new customers as well, it will be a bit of a one-man show. Yet, what we can do is communicate to the platform and then make sure the infrastructure is there and then implement the platform and build a business analysis basically in an un-built realm. I have to do a lot of things by myself, so the fact that UiPath brings in the Cloud Platform and the Studio and it's all integrated and you can scale up without having to have too much. You need to know something about infrastructure to understand what it does for you, however, you don't have to do it all by hand. I don't need like three or four DP-trained individuals to be able to scale up or scale out. It's helped me get further faster.

Once you build the infrastructure and you know what you're doing and you know where you want to go with your platform and scaling, it's rather easy.

The only people really using it at this time are me and six trainees. There are a couple of ops people as well that are able to log in. We might have a total of ten people on the solution.

It's not being used too extensively now, however, that's for a large part due to the fact that most of my colleagues are working with our customers, so there are not too many internal processes or tasks. However, we do have plans to increase its priority as the tasks that we do have are at some points largely repetitive. We do a lot of operations and maintenance for our customers as well in different fields, so we are mainly looking at that for further automation opportunities.

Technical support has been pretty good. 

I get a quick response and it's usually constructive. I manage to fix my own problems a lot of the time using the community forums and information from there. I haven't had too much interaction with UiPath tech support.

We did not previously use a different solution. 

I personally implemented the solution at my company. 

We currently have it running, so some internal processes. And, we're looking to expand that into the customer landscape.

The setup is simple. They deliver it in a cloud environment, I didn't need to do any installs or make any arrangements.

You need to make an account and get started and watch a couple of training videos that will help you through it. The adding of the robots is very well documented in the forum, in the community, and in the training sessions. They have made it really easy to get started and to get the information you need to take the first step.

The deployment question is a tough one as I started out at this company while already having a communicators subscription on my own account. Therefore, I started out using that one and then gradually shifted toward using more automated resources. I don't have a clear overview of how much time it took to deploy. It might have been a couple of weeks overall, however, I was doing different things at the same time, and I never took a metric of how much time it took. I'd say starting out if the prerequisites are in place at the company, it could be a matter of days.

Tasks such as setting up an account, getting some service, et cetera, if you know what you're doing and you know what to ask a few questions before starting, it's a couple of minutes or hours. That said, in reality, there are always things you forget or things that they didn't do, so it always takes a little extra time.  

My implementation strategy was basically to figure it out as I went, which is not the best strategy, however, it was the best we could do due to the fact that the company didn't really know what they wanted to do with RPA. I was figuring out my own place in the company and then their wishes with robotics with RPA. There were a lot of things at the same time, so there was not a closed strategy other than to start up quickly, as soon as possible, get feedback, and then try again.

For now, I alone handle deployment and maintenance tasks. That will be the case until our trainees finish training.

We did not use a third-party service such as an integrator or a consultant.

We have not yet seen an ROI and have no concrete plans for any in the near future.

While I have one or two sheets from old presentations that have pricing information, they are over a half year old. I have no current insights. I wasn't included in discussions between the company and UiPath in relation to licensing. 

The company might have looked at other options. However, they did this before I was hired. Ultimately, they did want to choose UiPath, and I was hired based on my experience with the product. They chose UiPath at that time as they were working together with Oracle and that company has always been very Oracle-minded.

I use the community Studio and the Cloud Platform. I take the cloud from UiPath. I'm not sure where they host their solutions. I use the automation cloud from UiPath.

End-to-end coverage is not too important to my work at this time. Maybe if they were more closely integrated, I would be able to offer it more easily to my customers. However, now, due to the fact that I often go in at the first interaction with a customer or at a company, I have to introduce the concept of RPA, I have to introduce the product of UiPath, and I have to introduce or orchestrate the Cloud Platform and Studio. What I've seen is that that's enough for the first steps, usually, the company will have a pretty clear vision of what they want to start out with in terms of automation. However, introducing the process mining capabilities would add an extra step to the start-up that we have to do and what they want to see is faster results in the early phase. It's short the time from when I come in to initiate the first value, so they can appreciate the value and start the business cases and go from there. Maybe, once they are a couple of steps further on and they have a couple of automations, then they go look at the process of task mining as they have the infrastructure, they understand what the process automation is about, and then they start to see the value process or task mining. Therefore, the end-to-end factor, for my job, for now, is not too important as I don't truly use the end-to-end approach. I do the start by myself with the customer and then we go from there. Then, in the next phase, I will build them practices and they will start to automate the beginning of the process discovery as well. There is not something that I have initially do. Once companies start beyond that first phase and the first steps, then process discovery and process mining can be really important in automation. In a later stage, it becomes more important. However, in my case, I work a lot in the early phases and haven't seen too much of the process discovery products in that phase.

Attended automation hasn't really helped us scale RPA benefits as we are a rather small company and there's only a small group that works with the product, and therefore, we haven't been able to use the assistance in the same way a larger organization such as a bank or insurance company might use it.

We don't use the staff solution yet and we have not taken advantage of the AI functionality. While I have played with AI, I haven't had any use cases to implement the AI sensor.

Overall, I am quite satisfied with the product.

I'd advise new users to start by doing instead of only reading. Start small, like finding small processes or if you're an individual, look at your own work. Find something you could do and automate that as it gives you the best appreciation of the value. Try it out in your own environment and just explore how it goes as that gives you the best insights. For me, when I started, it was a great feeling to watch your screen and watch your cursor follow the screen without doing anything. 

Keep asking questions when talking to users. When translating the biggest use case into other processes, spend more and more time talking to the users and going through the processes, and defining and understanding what happens. Otherwise, it's going to cost you a lot of extra time figuring out why you've got all these weird exceptions that you didn't expect. Everyone always talks about how easy robotic process automation is. However, only once you understand your processes from a user's perspective, you'll run into a wall. It's never standardized. It's never the same. I need to warn my customers more frequently about this pitfall, due to the fact that, yes ultimately, it's very fast, but it only is once you know exactly what you want to automate and that's why most of the time it's time-consuming.

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

Earlier, there was no integration of PagerDuty. In any process, we had been working with many stakeholders and many other clients, however, sometimes if any process needed to be done at a particular time, for example, 8:00 AM in the morning, and was not running at that time, we would get a failure message. Now, we instantly get an alert on our phone, or we get an alert on Teams or Slack. This UiPath integration, with all the features, is very beneficial as it is keeping us up to date and on schedule. If there are any failures the production support team can know and handle them immediately.

All the features, all the packages, everything, have been great. All of the artificial intelligence which we are getting is super-useful, as are all the needed updates.

All the features are valuable as, much like any application, it cannot work without just one feature. For example, we have PDF automation, we have Excel automation, Citrix, SAP, and we have SharePoint automation - which makes it so that we can automate anything. All the features combined allow us to work on multiple projects or one specific project. 

The ease of building automation using this solution is good. I really enjoy the flexibility. It's also very easy. We do need a few coding skills with languages like C# or Power Automate. However, it's got a good UI, with drag and drop functionality. That makes it easy compared to other tools, like Prism automation. UiPath is much better and it's highly recommended.

Scaling automation without worrying about the infrastructure was easy. I simply did some googling and looked to see which automation tools were out there and which was the leader. There were multiple training portals - including UiPath Academy, where I was able to pull all of these tutorials and insights. There's also a free forum where queries are answered. It made everything quite easy. 

The solution enables us to implement end-to-end automation starting with process analysis, and robot building. This end-to-end coverage is important to me as we follow an agile methodology. We have an RPA development life cycle. This product gives us all the tools and everything we need. The requirement gathering and document preparation come as standard models. We have UiPath Studio for testing and UiPath test features for maintenance. We have the Orchestrator where we can maintain everything as well. We can see where things are working or not. In fact, we have integration with PagerDuty that gives alerts if something is failing or not working. It's really important that UiPath has integrated across all the life cycles, and that all the phases are working properly.

UiPath has helped to minimize our on-premises footprint, which has been very important to me. It's very important due to the fact that we can build a robust and scalable solution for an enterprise and have security in UiPath. It's very important that customer satisfaction is there, no matter what we are developing. It's very important to our organization.

It's a very fast solution. It can provide a result or automation to a business process within seconds. If we have an API, we can integrate EPS as well instead of using the UI. Basically, we can get any solution we need within seconds. It's very fast.

I have noticed that the solution reduces the cost of digital transformation as we are saving on manual hours. It's reducing them. We don't have to hire more people to do these manual jobs, which has helped us reduce the cost.

We did require application upgrades and IT application support. We wanted to update and get all the latest features that UiPath often releases. I've seen every month or every year we get all of these new packages. It's better to include the latest version to get all the latest features.

With UiPath, we have reduced human error. Humans are prone to making errors that they can make at any time. The bot does not. It's continuously given proper feedback. The lack of human errors has affected business a lot. The bot allows for complete confidence that perfect work is being done. It has also freed up employee time. We've saved thousands of hours. We have ten processes that are running in production. Up to this point, with those running, we have saved up to 1,918 hours from the automation. On top of that, employees can now focus on higher-value work. It has improved work satisfaction. There is more self-motivation that boosts the work, which we are doing.

The solution has reduced costs overall via automation. However, I cannot speak to exact cost savings. As a whole, it's saved our organization money.

Right now, we don't have many use cases in the field of NLP, natural language processing, or artificial intelligence. There are not many tutorials or any videos or enough insights shared by the UiPath Academy. If we could get more insights, that would be great.

With artificial intelligence or natural language processing, we need to get in touch with the servers, however, we cannot do it without getting a proper license. Maybe a mode of artificial intelligence and natural language processing should be included without needing a different license.

I've been using the solution for the past three years. I am currently working in Rackspace Technology. It's been two years looking at it now and one year in my previous organization, which was essential.

The solution is very stable. 

It is scalable. So far it's not been getting into trouble, and we haven't tested the boundaries, however, it's scalable.

I've been using the solution for the past three years myself. We also have a developer and some bigger production staff. There might be a few people who use it here and there. 

It's been extensively used in our organization. We are getting in touch with many internal clients, internal business units, and getting more projects. We are in the process of expanding it. Right now, we have five to 10 business units, such as accounting, et cetera, and we are trying to expand further out to other departments. 

I've never used UiPath technical support.

I did not previously use a different solution. 

The initial setup was easy. We basically had to install UiPath Studio and the tool, as well as the orchestrator. It was quite straightforward and easy.

The deployment process was just a couple of minutes. It was maybe five minutes. Not more than that.

We didn't have much of an implementation strategy beyond setting it up and working with a model via the deployment team. 

We handled the implementation ourselves. 

While I have noted an ROI, I cannot share specific data points.

I don't know much about the buying, the pricing, and other cost-related details. 

I did evaluate other options, such as Automation Anywhere, however, I have found that UiPath has a better interface and all the activities can be seen more visibly on the screen.

We are just a customer. 

At this time, we have not automated departments or role-specific processes that require human-robot collaboration. Mostly, we have unattended automation such as NOMA inclusion. We do not use the AI functionality in our automation process just yet and we do not use the solution's automation cloud offering. We also have not used the UiPath apps feature.

I would advise users considering the solution to try it once. The community edition is free. You can explore and download the community edition and take note of all the features which UiPath offers. If it suits the company, I would advise users to go contact the UiPath technical team or support team and get more information on how to implement UiPath.

The more you explore, the more you'll learn. It's not just the straightforward drag and drop functionality. Many people say that UiPath is just for a person with no technical knowledge. However, the more knowledge you have of the technical side, with an understanding of languages like Java, Python, C#, the more you'll excel as it's based on a .NET framework. 

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

I'm using the product primarily for building automation projects for shared services users. It's for internal customers. It's a shared services center for finance, HR, IT, and all processes like that.

UiPath enables you to implement end-to-end automation starting with process analysis, then robot building, and finally the monitoring of automation.

I use UiPath mainly for building a robot. I always use unattended bots. However, I also use it for task capture. I use the Task Capture feature a lot. It's pretty much a game-changer since Task Capture has become available, as creating documentation takes a lot less time than before. As for UiPath, I'm using it for building a solution and then testing using not only UiPath but also Orchestrator. In the end, we also use some document templates from UiPath. It's pretty much present all the way through the life of a project.

UiPath has sped up or reduced the cost of digital transformation in our organization.

For me as a professional developer, this is an obvious fact, however, people can notice that the robot can do their job a lot faster and they can concentrate on completely different things. They don't have to do simple tasks, repetitive tasks, and that's when they realize that this transformation is happening. Some people did not believe that it would happen so fast, yet, by using UiPath, we can prove to user that a process can be transformed into an automated one in a really short time.

It's reduced human errors in our company as well. I can use an example as a VAT declaration. That's one error that would cause some financial consequence for our business. After creating an automated project process, it is impossible for a declaration to be submitted with an error. It's basically eliminated typos or human errors in the case of VAT declarations and financial consequences.

The solution has freed up employee time. It's difficult to estimate how much as there are a lot of projects and I'm not the only developer on. However, thanks to my bots, we could free up, so far in half a year in this company, two FTEs, two full-time employees. Obviously, it doesn't mean that these people were let off. They are doing their job, however, they've just got different tasks, more complex tasks to do.

Mostly I'm using Studio. This is my main tool for work, and, for Studio, I can say that this is my favorite out of all the automation platforms. 

I like the fact that you can use and customize activities from the marketplace. The fact that even though the built-in activity sometimes cannot cope with some tasks, you can still find solutions outside of UiPath, internal kinds of built-in functions. You can use the third-party package marketplace. 

I like the way it handles debugging as it's very comfortable and it keeps the project under control. 

I'm also using Orchestrator. The newer version of Orchestrator is really very user-friendly and it's easy to manage projects there.

For basic automation, it's very easy to learn and it's easy to use. It's intuitive for basic functions. However, for more complicated automation, it gets more complicated. This is expected. The more advanced the project, the more advanced the skills you need. That said, as a basic product for simple automation, it's very easy to use.

The solution is user-friendly and has great training materials available.

I use the solution for automating my own work sometimes. I work at building small robots to make work go faster. For example, I'll create a robot that will help to create documentation. For example, analyzing arguments and workflows inside a project and outputting them in a DXC file or things like that. It's small ad hoc automation that makes life easier.

At the moment, I'm pretty satisfied with it. Thinking about UiPath, I can't see any downsides and the downsides are in like companies' infrastructure.

At this point, debugging, for me, is lacking the ability to edit on the go. It lacks the ability to stop the process on a breakpoint and being able to edit or even go a step back. At the moment when I'm debugging I'm only able to stop the process, check the locals etc. It is not possible to change anything in the code, go step back and try the changed code. You have to start the debugging process from the beginning. It is just slightly annoying and it was there since I started with version 2016. It's not a showstopper at all, just adds some time to development. I'm not even sure it could be done technically, it's just a wish.

I've been using the solution for about four years at this point. I've used it for a while. 

There are occasional errors happening, which cause the software to freeze up. However, this is not more than once every two weeks and I'm always able to recover the project. I would say it's stable. Regarding working automation, I also have no problems as the errors that we have on ready robots never result from UiPath's issues. They result more often from infrastructure issues or robot problems.

Regarding UiPath scalability, it's great. It's one of the biggest advantages. Over the years, you're able to build a library of modules that sometimes make your work a lot faster. You can use a few modules and you will have 70% of the project done. Every module that you work on, which is new and can be reusable, is very easy to make into libraries and to reuse.

In my organization, closest to me, there are only about five or six people on the solution. However, we also use external contractors and consultants who use UiPath and there are even UiPath MVPs there. That said, in my company, it's only developers, operators, and a project manager.

We have plans to employ more developers and to increase usage. 

We have an RPA department, which is using it and it's cooperating with all other departments in terms of creating automation. We have specialists that are specializing in using UiPath for automation. We create automation projects for every department that requires it. The people who are using UiPath are using it pretty much full-time. It's a full-time development. We are planning to increase the size of the development team as the projects are flowing and the backlog is growing. From the business side of our company, the satisfaction is high. The demand is growing.

The solution has exceeded my expectations over the last few months and technical support overall has been great. The way they approach customer service and help us through issues has been great.

The initial setup is pretty straightforward. I'm not a system admin or anything like that and I was able to set up UiPath on the server. It's pretty good.

How long it takes depends on the database that I'm working on. That said, last time it was not even the one full working day. It depends on how much data you have to back up. Usually, it's a few hours.

While I'm not the correct person to ask about ROI, I can say that UiPath has reduced the cost of our automation operations by making it 30% faster. 

I don't know the exact prices, however, I know that compared to other companies, other solutions, it's the best value for money, at least in our country.

I tried Automation Anywhere and also Blue Prism. At that time, there were only these three available for us. That was four years ago.

We are customers and end-users of the solution.

We use the enterprise edition of the solution.

At the moment we are not using the newest version. It's 2019.

It was not my choice to use UiPath. At the beginning of my automation career, it was chosen for me. However, I was able to test other automation software and give my feedback to the employer and UiPath was the winner for me. At that time I was a finance worker. I was not a developer, a professional developer yet. For me, it was the user-friendliness and the way that you could very easily start your adventure with it, and then learn as you go. I have to say that the training packages for UiPath were very good and are enough to make you start working with it.

In my experience, I would say that it is the best platform for people who are willing to learn to automate. Also, if you want to use automation software, you have to consider hiring someone who has experience in it. Even though UiPath is so user-friendly and so intuitive, you still need to have a professional who has some experience.

It's very important to educate people to make them aware of what the RPA is. To be honest, from my experience, humans are the weakest link here, and people who are submitting, for example, input data for robots, cause the most problems. It is important to invest in the education of people and to raise awareness about RPA. 

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