UiPath Platform Reviews

We primarily use the solution for legacy data transfer, UI automation, CRM and ITSM automation, and call centers. Specifically, in call centers, using UiPath forms and form render has been really helpful.

I love developing in Studio. For my clients, the approachability of the orchestrator is really valuable. It takes a little bit to learn the licensing structure and layout at first, however, once they get it, it's pretty smooth sailing from there. The modern folders have become a great thing for any enterprise that's looking to automate using an orchestrator as a server.

I like to automate in Studio as I'm familiar with it. I honestly just like the platform so I like automating with Studio.

I really enjoy Document Understanding. I like how it all integrates together. Some of the stuff I've seen now with just the connectors and the way you can scale implementations is really exciting. While I do like Studio, I also like how it works with the rest of the platform.

We most recently built an unintended bot that saves them about $500,000 a year worth of GS 14 labor.

UiPath saves costs for our customers’ organizations. That would just be the cost savings from RPA bots. I haven't really dug into the cost savings of the ancillary products, however. I know that one of my clients is using the test suite now after I had built a proof of concept for it, and they've fully implemented it. I'm sure there's going to be a lot of cost savings there as well.

In terms of ease of building automation, it depends on the process. For anything that's ultra-low or a low-level complexity, it's very simple. Once you start getting sprawled out into larger automation that very much becomes object-oriented programming and is basically making a workflow. That's when you really need to take hold of programmatic concepts. You need to be a strong scriptor to be able to make the best RPA bots.

Our clients have reduced human error. That's one of the things that I tend to talk about the most. The bots can get work done faster, however, the reduction of human error is probably more valuable in some cases than just speeding up work.

In terms of UiPath Academy, everybody's used it. I've used it myself. My entire team has used it. All of our engineers are some sort of Pearson VUE certified now. Most of us have the Advanced Developer. A few of our younger junior developers have the associate, the RPA associate, however, they're working on getting the Advanced Developer and they lean on the Academy pretty heavily.

The biggest value in the Academy is the videos, which are pretty helpful. Sometimes you have to slow it down, however, for the most part, the way it goes through concepts, especially for somebody that doesn't have much programming experience, the videos tend to go through some of the more elementary things like variables arguments. That can get a little bit boring for programmers since they've been through that 100 different times. That said, that’s really where the strength lies as it does target a large group of different employees. As an engineer, I might pass by some of the boring stuff, however, I will still find things later on in the training where I'm like, wow, I actually never knew that.

The license model changing every year can be a little bit frustrating. It's hard sometimes when things go from being robot-based to being runtime-based.

Some federal users are still on the 2019 orchestrator or even a 2018 orchestrator. However, by being on them, they can't take advantage of modern folders. This issue is, once they get upgraded to 2020, and they start using modern folders, essentially you shouldn't really be using plastic folders anymore. Some of their frustrations aren't really long-term frustrations. Orchestrators have gotten really popular over the last few years. There are certain things that have made it so much better. That said, we're still in that transition where clients have been using classic folders and then they upgrade and they're going to have to change everything. Hopefully, they don't have to do it more than when they upgrade past 2020.

One of my clients upgraded their production environment from the 2019 orchestrator to the 2020 and everything was in plastic folders and I advised them to switch to modern folders and it was a pain. Once it was taken care of, it was great. It's just that it took a lot of convincing to tell them why it was better.

I've been using the solution for three years. 

It's pretty stable. The biggest issue is just that more companies need to really adopt a change management system, whether that's through Service Now or is built-in change management, those alerts need to be going to the RPA center of excellence. 

There are things that will change or break the UiPath bot sometimes. They're very stable and they've become more stable if there's a change management system. Automated testing can make it so you can catch things that have changed with applications with RPA testing before they've occurred and then you can fix things quickly.

The scalability was tough a few years ago, however, now it's exponentially easier with modern folders and the orchestrator.

I've worked with UiPath support. I would put them at a seven out of ten as they need to be a little bit more timely. There have been issues with a client where support has taken a really long time to get back to us or they haven't updated our support ticket, even though we've advanced. Maybe it was an isolated incident. I have worked with support before where that hasn't happened. I felt like I got in a bad run of working with the support folks and the client was definitely not pleased.

I actually don't have experience with other RPA solutions. I came from a web development background and I went straight into UiPath and now the way that it's scaled out and now that I work in the federal government, UiPath has such a large piece of the market share. I've never really seen a need to learn any other automation solutions. I may learn Power Automate at some point, however, I would really prefer to stick with UiPath.

The solution is pretty straightforward. I've run through complex issues, mostly the NuGet package and it's different with every customer. As far as the UiPath platform goes, it's pretty straightforward to deploy bots. It all depends on how an agency has its group policies set up for security and sometimes that causes issues. It's just about learning new ways to solve different problems that may be unique to an agency or may not be.

In the government, deployment takes a little longer. I would like to think development usually doesn't take that long, however, it's like going through ATO, especially if it's an unintended bot. Sometimes it can take like a few months. It just depends if they've got a center of excellence stood up or not. For example, if they've got an CI/CD pipeline or just a standard development life cycle, a lot of people don't have that set up and then it ends up taking longer as they have to go through ATO. It’s variable. Unfortunately, it's just a lot slower to get them deployed than in the private sector I think.

That’s no fault of UiPath. It's usually group policy security systems and things like that. I've had to talk to a lot of security folks and help walk them through things that need to be changed.

We've been implementing our UiPath as well.

I don't really have too much to offer about the pricing part of it. I don't really work on that side of the business. I would say my only gripe about the pricing would be something like a Studio Pro license being more expensive than a Studio license, just to essentially get something that links Test Manager. Some people might've found that a little bit hard to swallow. From what I've heard, Studio Pro is going away and Test Manager is just going to come into Studio. That would be the only thing I've noticed that I thought was a little silly. Everything else is typically not really my side of the business.

We have everything on-prem in our demo environment and the customers I work with typically have the on-prem offerings as well.

I have used UI path apps in our demo environment. I do not have any clients that are using it.

We have an AI center in our demo environment, however, I don't have any clients that are using it. I do have a client that's actually in the process of installing it right now and getting it through their governance model. That's as close as it would've come for our customers using the AI center.

To those considering UiPath, I would say, just go ahead and do it. RPA is pretty awesome. It's easy to get solutions out. There still needs to be a good bit of work done on the Citizen Developer Model, however, at the same time, as far as getting a team of engineers in there to automate things, if you get good RPA developers, you can get things automated really quickly. People can help you with your standard development life cycle. You just need to jump in.

I would rate UiPath solutions at a nine out of ten. The only reason I wouldn't give it a 10 is that, in terms of the installation of the product, sometimes the documentation leaves a lot to be desired. Sometimes it's tough to work through installation issues without actually contacting support. I do wish that was a little bit more streamlined.

I work at a financial firm where we do trade settlement activity. We are using UiPath for cleaning up data, doing reconciliation, and finding where the trade breaks and trade files are. It helps us lay the groundwork for the value add work, which comes later.

It allows us to grow our business. The use case that we have is a huge time saver because we do not have a lot of volume right now. We are looking to sell part of the business and get more clients onto it. The only way we could do that or even open that door for possibility is to automate and go through a lot more volume. 

Our teams are under huge pressure because trade volume has gone up over the past year. UiPath is just getting us back to the status quo and then also opening the pipeline for more volume to go through. We have a very strong program that encourages people to get trained up on tools. 

StudioX is going to be a big game changer for us. We found with the other tools that we use that as soon as we put UiPath in the hands of everyday users and ops users, they will be able to quickly learn it. This will make a big impact because we will get big volumes and projects coming through.

UiPath has done a good job coming up with the broadest use cases. However, I would like to see them dive into more industry-specific use cases. For example, checked OCR and brokerage statements are common. Anything unique to the financial industry would be useful for us.

We have using UiPath since February when it got brought into our team. We just had our first box go live about two weeks ago. We have had three go live so far; one using StudioX and two using Studio.

So far, I haven't heard any issues. We are always going to expect issues, but so far so good and I hope the stability is good. Alteryx had issues at times, which created some pretty big problems. Hopefully, UiPath will not do that as much, because we are expecting to lean on it.

I have not used them directly. 

It was not so much a switch for us. We are still using Alteryx. UiPath is a much better automation tool than what we were using before because it was self-service. We didn't have to have our COE build it and related solutions for us. We have similar functionality with Alteryx. Anyone can learn it and start building and go through our governance process. Doing so, they can have a huge impact on their team.

We are a large company and the initial setup took our COE quite a few months. However, I believe their experience was positive overall. A lot of the issues we had were internal and concerned how we were going to do our governance. We were very strict about that. 

Getting people access was easy and so was learning to build. Everything on the UiPath side went smoothly.

We're a mature automation team. Over the past four years, we've delivered well over 150 FTE. We're always looking for new tools and to pick up some of that automation that we couldn't do before. 

UiPath has helped with data scraping and plugging into websites and combining that with Alteryx. We can attack 90% of our use cases now. We can not deal with the other 10% for internal governance reasons and not so much capability.

The three use cases we have implemented with UiPath have saved about half an FTE. 

I know that the reason we went with UiPath is because it is a lot cheaper than the other vendor we were using. It is of a better quality as well, but it is less expensive to run on an ongoing basis. 

I'm not sure if we evaluated other options. My team does not look into the suite of options. We have a separate COE that sets everything up for us. We are tasked with implementation. 

My advice is to first build a good team that you can trust. Because great tools are useless if you don't have any builders or people that know how to use the tools. That is what we have been focused on. Also, have very specific support for your team.

We have multiple accounts sellable, accounts payable, corporate finance, and supply chain use cases. We have started some use cases at the factory floor automation as well.

There are so many benefits to using UiPath, but getting the buy-in is very important from the end users. We are seeing many hours saved with respect to automation. Automation should be on every project's agenda. 

Scaling at pace with regards to the industry has been the most valuable UiPath feature for us. I would also add that there are so many features in RPA. 

We are leveraging the UiPath Academy for our citizen developer program. We are asking them to train at their own pace. The courses are straightforward.

The adoption rate for this program is low, however. Out of the 150 citizen developers that started, only 10 decided to continue the process.

One way to improve the UiPath Academy, I think, would be to add some real-life use cases and take the students through the automation process. These would be good for citizen developers to start with.

We started our UiPath journey early last year. It has been a year and six months. 

UiPath is stable. The automations we have in place right now are stable. 

Over the past two years, I've reached out to them maybe twice. 

The initial setup was straightforward. When we started this automation journey, instead of going with complex use cases, we picked three simple ones. We started with the accounts receivable processes. 

Deployment took us six weeks. 

As of now, we have automated 160 processes using UiPath and saved many hours. We have saved around 60,000 hours. Although we are not directly reducing costs, we are avoiding the cost of hiring new people.

The solution is very expensive. It's getting harder for me to convince my management about licensing costs. 

Yes, we considered Blue Prism and Automation Anywhere. We created an automation using both of these and UiPath and ultimately decided on the latter. UiPath is more compatible with the other applications we were already using. Oracle's JD Edwards EnterpriseOne is our ERP and they partner with UiPath, so that was a major plus for us. Also, UiPath has very straightforward coding courses.

It is usually not easy to build a complex automation. The whole process takes about four to six weeks for a complex automation. Most of the time is spent on gathering the requirements. The development itself does not take much time.

We used it to orchestrate the transfer of data across authorized systems of record, such as Salesforce and we use it to authorize systems or artifacts like Google Sheets and Spreadsheets. We also use it to have a dashboard view and to automate manual user behavior to cut down the time it takes to process specific transactions.

UiPath has reduced human error. With the very manual nature of formulas in Google Sheets and Excel that now can be performed using UiPath and so Spreadsheet controls have been tightened.

The automation cloud offering helps to decrease the solution's total cost of ownership by taking care of things such as infrastructure maintenance and updates.

We were able to significantly cut down time and hours on some of the key processes which then frees up people to focus on their day jobs as opposed to manual routines with predictable processes. We see 75% time savings. 

The use cases revolve around polling data from multiple systems, but when that has been automated using a bot then that takes that time away. You spend less time gathering the data points and more time doing exception management and reviewing the data.

Those manual hours translate to cost savings and that definitely can help us scale and grow. We were able to see at least one full-time employee equivalent savings.

Saving employees' time has allowed for employees to focus on higher-value work. Rather than spend 80% of their time looking for data, they are now spending 80% of their time really addressing the nature of the data, like what went wrong and trying to gain actionable insights as opposed to trying to figure out whether the data was complete, to begin with.

This has impacted employee satisfaction. One of the key challenges with remote, work from home has been the higher probability of employee turnover and burnout. Also, as part of job satisfaction, working on the right things at the right time and marrying professional and personal endeavors and aspirations, from that respect, UiPath has freed up a lot of employee hours spent on manual routine tasks. That really gave them a human element in everyday work, which revolves around getting value as opposed to merely collecting data.

AI helps to automate processes that are more complex. Part of it is that it is very precise with attended versus unattended elements and it also really understands that the key is not to give everything away to the bots, but it's almost always trading off and achieving a balancing act. Where human intervention is still needed by only at the right time and looking at a small sample as opposed to the entire population.

The AI functionality enabled us to automate more processes overall. We've been able to venture from beyond regular G&A processes to more HR processes. From applicant to hire, it elevates the employee experience and does not just look at scaling.

I'm a big fan of the Academy because it has let me self-serve in a way that I was quite accustomed to.

The point-and-click approach is a great sell. I'm not proficient with Studio but I found it easy to spin up a concept, prototype a demo with stakeholders, and be able to demonstrate value add right away.

Venturing more outside of our Windows environment and more towards OS will help. 

It should be less focused on the howtos and more on demonstrating business value add. A business outcome should be that I was able to approve something in however many days or hours compared to my peers when I benchmark across my peers. That would be a business outcome as opposed to a technical outcome, which is all about how many hours did you save? What were the exceptions you saw? Were you able to shut the bot down? They're very different paradigms. UiPath needs to flush out that business element because a lot of us make decisions on ROI. It's hard to convince executives and management if we only focus on the technical.

It's a hard place to balance because there are people who are business savvy, who are looking for ROI, and then there are other people who are just getting into these programs and these solutions. I need to understand the technical aspect of it.

The other part of it is understanding how UiPath plays out in the ecosystem of available cloud applications and other enterprise software used. A lot of the software out there in the market, such as Workday, has native automation, point and click customization, and automation, potential, and capability. UiPath may want to think about how it plays with these other products as opposed to in place of. We have built teams that have developers who are really proficient, including me in NetSuite and other products. Every day we want to make sure we're using UiPath the right way so that we're not squandering or wasting resources because the same time spent on UiPath could be spent redirecting UiPath elsewhere. That application is inherently not sophisticated enough to handle customization. 

We've been using UiPath for one and a half years.

The initial setup was fairly straightforward for us. We actually worked with a partner. We ultimately put it on AWS just for continuity and it was pretty straightforward for us. We don't really have too many bots going anyway.

The actual deployment didn't take a lot of time. A lot of work was spent only because a lot of work was already invested in building out the prototype which mirrored all of the manual processes. We recorded the manual processes and attempted to replicate as much as we could. We did the proof of concept demo without key stakeholders. So by the time we came to building out the actual work in production, it was just replicating what we already had in the prototype.

We are fine with licensing and pricing. We just need to see where we are in our adoption. I don't have enough of a sense of what the different levels of usage could be.

We evaluated other solutions. Back then the community platform was easy to download and it had a couple of ways of gaining access to software from having access credentials to tokens which is a lot more secure for us. There were also managed packages in UiPath that were readily available that spoke to NetSuite, Salesforce, and Excel. It was a no-brainer.

We only have two developers on it, they support it. We don't have citizen developers. The plan is to continue to see if we can get value add and go beyond the processes that we've addressed and maybe put out a team.

My advice would be to be open; it doesn't have to be all or nothing. I've seen users get tripped up over the fact that every time they think that providing value add through manual intervention, through exceptions, they almost always think it's 100% unattended.

At the end of the day, we are not taking away anyone's jobs. Almost always, there will be an attended piece. It's like driving the car on a freeway. You have the ability to put it on cruise control and the ability to put your foot on the brakes. That's what most users forget. They ask about audit internal controls and on our end, UiPath recently attained SOC 2 type two certification in June of this year, which is great. The reality is there's always a manual human compensating review element, so there shouldn't be a risk if it's built right.

I would rate UiPath a seven out of ten. 

Our primary use cases are for any financial business process. Primarily for myself, I was with an organization that did a lot of back-end middle office, and front office automation for many midsize banks and credit unions.

We saw anywhere from three to five times ROI, based on the business processes that we were able to automate, and its ability to enable the organization to do more with less.

It increases operational capacity. We noticed that it even helped a lot of the C-levels with employee morale and to keep their retention as well. If you enable your FTEs with the tools that they need to do their day-to-day operations, that's naturally going to create growth.

Our clients have absolutely seen a reduction in human error and time savings. As long as the accuracy of your data is there, the bot can learn the business process, based on how you develop it. It's emulating human behavior within graphical user interface automation. We've definitely seen an incredible amount of ROI on that.

The most valuable features are the ease of use and the amount of resources and community that are out there for UiPath. They have all of the information that you would generally pay for with other providers. It's a very easy-to-learn solution as long as you put time and effort into it.

UiPath has a low-code and no-code approach; the user interface is intuitive. It's something that can generally be used by either a business user or anyone that has a high-level understanding of IT.

We use UiPath's Apps feature. Depending on the applications that we're looking to build and connect users with, or any of the existing connectors or apps that exist with the UiPath, we definitely utilize this.

The Academy is a huge catalyst for allowing your business users or your IT users to learn the solution at their pace. It's a very intuitive Academy that's provided free of charge. It's something that really enables the organization to help them develop citizen developers. Enabling users is the biggest hurdle that a lot of RPA users or anyone that's looking to implement RPA is going to be facing. UiPath has a tremendous amount of training and information that's out there through their Academy. It's definitely attracting a lot of organizations to lean towards UiPath.

The biggest value we've seen from the Academy is the amount of operational capacity that it allows for organizations to do more with less. Anytime you look into or embark on an automation journey, you're really looking to drive efficiency through automation. That is something that's really needed as you start to go into 2022 and post-pandemic.

There should be a little bit of a longer trial version. I know that their existing trial version is around 30 days. I think it would be very beneficial to make that a 60 day trial for active POCs.

We have been using UiPath for three and a half years,

The stability of the solution is really improving itself from where the organization really started to embark on automation. Year over year, they've added new features, and really what made automation more of an omnichannel approach.

It's not just another tool to develop bots, but it's a tool that has process mining and tax task capturing. It's something that only comes in with an end-to-end approach, rather than other RPA tools in the market that only have point solutions just for development and really don't have an end-to-end solution.

Scalability is something that is quite remarkable at this point with their cloud solution. Growing your RPA footprint doesn't really propose a tremendous amount of a challenge anymore. Their cloud approach is going to definitely help them move forward in 2022 with a good amount of growth.

I found the initial setup to be fairly easy. If there were any complexities, I know that they have great support, resources there internally to again guide you through that automation journey.

The form of engineers that they have, as far as the level of understanding and so forth, is quite remarkable. That is where they're really leading the market.

They should provide a clearer and more of a definite approach for any organization that wants to sign beyond a one-year, two-year, or three-year contract.

A little more visibility and more clarity would help, even for the partners. There should be more visibility into the price measure.

Compared to Blue Prism and Automation Anywhere, in terms of the pros, UiPath has built a great community around the solution. The amount of training provided by their Academy is something that is really helping them scale the organization. That's where Blue Prism and Automation Anywhere can take some notes from UiPath, as far as what they're able to provide to the market.

Ease of use is something that is definitely moving the business users into adapting UiPath at a much greater scale. Simply because it requires less technical knowledge.

Someone without an actual IT background can come in and start developing their own bots to help them from a day-to-day basis. Those are the pros. Obviously, the cons are that those other organizations can start providing a little bit more information to their prospects. Even as a partner, sometimes it becomes challenging.

The number one piece of advice that I can give anyone that's embarking on automation is that automation is something that's been proven. It comes down to why wait and automate today, and whether it's going to be a low, medium, or high complexity bot. That's something that organizations need to embark on it now, instead of waiting. 

I would rate UiPath a nine out of ten. To make it that 10 they should provide a little more clarity on their subscription and pricing market.

We work with TMS, a technology-management resolution division. We use UiPath to read the PDF documents that we get. We manage a business service for TMS and as part of that business contract, we read the PDFs and enter that information. We get that information out via documents from the templates where we have to enter information related to that particular case. 

These are the use cases that we are currently working on, but we are also looking to use this for quality assurance of all the steps because this is a highly visible, very critical process for TMS. We have to make sure that everything is done on time and that all of the information is relevant and responsive. Quality assurance is a big deal for us, and we are looking to use UiPath quality checks at different stages in the process.

We are in the initial stages, so I can't really say that we have achieved a whole lot of efficiencies using UiPath yet. We hope to achieve a whole lot of efficiency when it comes to the documents. Right now it takes about 45 minutes to do this process manually, to read that entire form. It is going to be reduced to two minutes. That is a huge efficiency gain, and that is the value that it will add.

When it comes to the ease of building automations, UiPath offers many libraries for developers to use. It's fairly easy to code it. 

We definitely expect that it will save us costs and human error. There is a lot of critical information in these forms and there is a human error because we process huge volumes. Obviously, when a robot is doing it, that human error will be reduced to a minimum.

The hope is that employees will be able to allocate their time to different work.

We use the Academy. We are enrolled in the partner program, and we have used a lot of courses from the Academy. It keeps us up to date and up to speed with the solution. Although, our needs right now are very focused and limited because we are just starting. I'm sure as we grow and as we advance in our RPA journey, there will be enough documentation and courses for our needs. 

Most of our PDFs are scanned PDFs and the OCR does not always capture all the information correctly. That's why the document understanding feature will be good for us. 

We have been using UiPath for about four months now. 

We haven't seen any issues with stability. It's definitely been good.

We have used technical support when I had some issues installing the system. 

I am looking for ways to get the technical support we need faster. 

I think that the pricing for the basic attended robot Studio is great. I think that all of the new features that they are rolling out if they are reasonably priced, they'll be useful because for people like the ones working on our projects who are funded by the government, they have a cap on how much they can spend.

Keeping the price in a reasonable range would be beneficial, and it'll be more usable and more in reach for people.

We considered Blue Prism, but through our research, we chose UiPath because of what they've already achieved with CMS. We thought it would be the best solution. 

The UiPath website has a lot of information and the Academy offers a lot of courses. I heard from different people in different industries and markets that this is the best solution. It's worth a try. There is more work in the beginning when you are getting it set up. But there are a lot of benefits, and you don't have to wait months and months to see them. You can start seeing the benefits early on.

I would rate UiPath a nine out of ten. 

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 have four robots. One we're sending out shipping labels as our members do returns. Once they create a return, we used to have someone that was manually entering in and creating the shipping labels. That was like the first robot that we built. The cost savings on that alone covered the costs of UiPath in total. We have a few other ones that we've been playing with, however, that first one was a big one that covered the cost of UiPath. 

UiPath has freed time for our employees. With the shipping label robot, for example, we basically replaced two jobs and now they're able to do other things. They can take on other more vital responsibilities.

I'm really excited about task capture. We haven't started it yet, however, that's going to really help capture the processes that we want to automate. We're excited about that.

The solution is just opening our eyes to what is possible. There are a lot of people in our company who hate doing mundane repetitive things. It's giving enough hope that we can replace those jobs that people hate with automation. We're excited about that.

I'm not a developer, however, the two developers that are under me, like the shipping label bot and found it easy to build. A developer was able to create that in one day and it replaced two positions. I'm sure we can build it better and faster with what we're still learning. With a partner coming on to guide us I foresee that we will definitely get better at it.

We’ve used UiPath's Academy courses. I don't think we would be where we are today without it. My two developers had zero experience with UiPath. They went to the Academy and learned as much as they could and started building right away.

Its biggest value is the continual learning on offer. We're pretty overwhelmed right now with what it can do, however, the Academy just teaches us how or where we can go with it. It’s great.

The setting up of the cloud was a little bit confusing for us. We expected someone to walk us through that process and we just did it ourselves and weren't sure if we were doing it right. We thought that getting assistance with the setup would just be kind of a given or they would at least lay out the steps. We didn't have that. We were asking a lot of questions and trying to figure it out with our salesperson. She was likely not the right person to help us with that. If there were directions on how to set it up, that would have been helpful.

We've had the solution for three months. 

In terms of stability, the robots have been running well. That said, we've had a few failures that we had to go in and fix, however, it was a pretty minimal effort to fix them. I'm not sure of the exact reasons. I remember my developers were telling us one failed and we needed to go figure it out.

It wasn't like an all-day fix. It was just a pretty quick fix which required simply stopping it and restarting it and then it worked. 

In general, for stability, it's been so far so good.

We have the goal of scaling, however, we are still just barely with our heads above water. We're just trying to figure it out as we go. Our biggest asset is bringing a partner on to help us and allow us to build up that scalability. Without their help, we would be lost. We would build without having a good foundation. The partner is coming on for a three months contract to train us and get us up to speed to make sure that we're building a good foundation so that we can scale.

We first created a technical support ticket when we had the issue with the trial license versus our actual license. It was hard for my developer as he didn't have the URL for the cloud. He really couldn't diagnose the issue as we thought it was all on the one referred to us, yet there was that disconnect. We went back and forth over several days trying to figure that out and the tech person couldn't help us. We were lost there. That was a little confusing.

This feedback isn't against the technical team. Maybe it was just the way we didn't get the correct training we needed to set up correctly. UiPath should've killed those trial licenses or transferred them and they never did and that first robot we built was on a trial license. 

It would have been helpful if they told us to import the robot or something over to the real licensing. 

We did not use a different RPA solution previously.

I'm not a tech person, therefore, the setup was a little outside of my wheelhouse. It was a little bit harder for us. We've been trying to figure it out. 

The issue that we've found is we had a trial license and my two developers were on the trial. Then, when we got the actual licenses, a developer was still building under the trial. The trial was allowing them to do things and build over there, however, it wasn't under our automation path. It took us a while to figure out what the disconnect was as I just didn't know how to set everything up. That was a little bit confusing.

We realized ROI on our first robot. 

The automation cloud offering did not decrease the total cost of ownership of UiPath. It was a little bit more, however, we didn't have to set up our own server and maintain that.

We bought the starter package and we were able to cover the full cost of it with one robot within two days. It definitely paid for itself.

We were also looking at Automation Anywhere and it was a pretty close tie between the two.

We chose UiPath as a colleague who had worked with UiPath at his last job and he was a little bit more familiar with it. We thought the security was a little bit better in UiPath as well. Those were the two main reasons that kind of pushed us towards UiPath.

We haven't used the UiPath apps feature yet. We've signed up with someone that is going to be our partner to help us learn all the new aspects. Hopefully, in the next couple of months, we'll be setting everything up, including the automation hub, and trying out apps and task mining.

We do not yet use UiPath's AI functionality.

Based on my lack of knowledge, I would probably rate the solution at an eight out of ten. We've been super happy with it this far and from all the things I've seen, we're excited about where we can go with it.

Our primary use case is to document image processing. We're six months in, so our first case was sorting and filtering the data, extracting the image, and determining if it's a certain type of document. If it is, it starts putting it into different buckets, which ultimately we'll run something to extract and put those into our data source. 

Our second use case is for the healthcare industry. We're looking at catalog data and a customer might want to know about a product. Is this product safe? Who provides this product? Is it on a contract somewhere? We go out to multiple different web sources to look up information about that document, put it back in our database, save it for that customer, then save it for any future customer that asks the same question.

We're looking at other things like taking snapshots of the image of the product. We also want to automate other basic automation, low-hanging fruit type functions, like automating uploads of data to sites, spreadsheets, contact-center, and Salesforce.

Longer-term, we want to take what we're doing in the document image and apply it to other areas of our business. We have purchase orders, invoicing, shipping documents, compliance documents, credential documents, a lot of images in this particular space. We'll go as deep as we can in the data processing side of things.

We're going through a culture shift to get to an automation-thinking platform as opposed to a lot of our business relying on BPO humans to do the work. Making that paradigm shift is taking time because we're only a week-plus live. If we prove the value, they'll give us more opportunities to make those big changes. But it's good that the business is thinking that they need this. Now it's just getting the community aspects of it.

The automation cloud offering helps to decrease the solution's total cost of ownership by taking care of things such as infrastructure, maintenance, and updates. 

Although we don't use it, document understanding for our use cases is very compelling, but it was a little cost prohibitive just out the gate. We are looking at it long-term now that we have the data filtered if we can more strategically apply it to the best data to fit it. But overall, the platform is very innovative. I don't think I can call out one particular feature. The ease of use of integrating to and from Amazon components, being a cloud-native application ourselves, has been really helpful in the development and the ease of transferring documents between our internal systems and platform.

The ease of building automations using UiPath depends on the use cases. Overall, the development is really easy. Where you run into challenges is in workloads that are highly rule-based. So we abandoned one use case where it had 50,000 different decision points. It wasn't worth the time. It wasn't a product thing. It was just too time-consuming of a process, something like that.

There have been some limitations as far as how do we execute our bots, when? This new release that they just mentioned today actually addresses a lot of our concerns around the integrations component that they recently released. If we could find an email instead of waking up and checking the email inbox. That's a big improvement we're looking to, but it wasn't a limiting factor.

I have used the Academy. It was really just myself and as well the one IT guy who's supporting the platform. Our office partner came in with the knowledge, but the course was really good. We came in with no RPA experience, and it covered everything from the basics of RPAs to the processes of identifying.

They recently addressed a major problem of kick-off processes for the integration function. That addressed a lot of the community concerns around that. If you are using queues, their queue system isn't as reliable as I would like it to be. 

One of our concerns is that we were not a Microsoft shop at all before bringing this in. That was actually my limiting factor in bringing in the software. We lost it below the party lines. The ability to address other workloads, Mac, Linux, etc., is going to be a game-changer.

From a new customer, new investment perspective, there are a lot of cost-prohibitive aspects that we decided not to add to our initial investment. We weren't sure if or when we'll figure things out for use cases.

I have been using UiPath for six months.

We want to triple our capacity and triple our workflows. 

I've only had to use support once, and it was more of a documentation problem. I didn't understand what I was seeing, and they worked it out within an hour. So far, they've been good. 

The cloud was up two days after we signed. Then to get our bot infrastructure up because it's Windows and we're in a Windows environment, it took us about a month to run through that and get the IT people and security.

Cloud solutions will save you a lot of headaches and time. We broke halfway through and decided we're going to cloud, not on-prem.

Reputation was a big reason we went with UiPath, as well as the growth and the ability to integrate specifically to the cloud which was missing in other solutions. That was a big plus. The ability to use something like document understanding and the ability to interact with internal APIs were also key features. It's not just web scraping and doing things in Excel or other things like that. We wanted it to work with our internal native applications.

UiPath has not yet saved costs for my organization. We're still going live and we're anticipating about a two-year ROI.

Make sure to understand your use cases before you sign your agreement. That way you're not idle for six to nine months trying to figure out what it is you're trying to automate.

I would rate UiPath an eight out of ten. 

We use UiPath for OCR, for our subrogation department to analyze credit report organization letters that come into our company to identify whether they're identity theft, fraud, or any other type of keyword phrase within the document. It also extracts the information coming out of the CRO to properly assign it to accounts associated with our subrogation department. 

Another use case is navigating through one of our third-party clients in order for us to get documents out of their system and into our system so that we can analyze and package them.

We see benefits from the AI side of doing OCR and in order for us to do onscreen recognition of documents. It increases the efficiency of our agents in order for them to get back to working accounts, rather than reading through document after document every single day in order for them to pick out one or two words into the document and assign a smart code. The automation does all of that for them now.

UiPath has saved us costs. It's thousands of documents per day that we're OCRing and then that reduces it to around five to 10 minutes per document. It's around 50,000 minutes per agent, per day.

It has reduced human error because there would be some different document types. It's able to detect multiple types versus a user finding one document type when there could be multiple document types that are associated with a letter, while the user is browsing over it that can be missed in the second document type. But when you're looking at machine learning and at the text, it'll be able to easily pick out those keywords from a document that has multiple document types.

It has also freed up employee time. It frees up their time to do other work.

We are currently using the AI function in order for us to do Task Mining to be able to pull out of a couple of our key groups that we're trying to add additional automation to. That's what we're using AI Center for at the moment.

We have done UiPath Academy courses. I got certified in the advanced RPA Academy. I need to renew that because they expire every year. Another developer has his associates, so we use that every year where we can get some training. It helps keep people up to speed. It makes sure that you're doing the latest and recommended in the RE framework and what you have initially designed.

Building automations can be difficult at times with some of the activity packages and documentation being out of date, but we have a TAM that we work with that is very helpful in making sure that RRGs are known and that we get the results within the UiPath structure.

They need to deprecate their previous versions on their website or their documentation. It should just point to the newest version rather than when you go to Google if you're just trying to find UiPath and then it points you to a solution that was a couple of years ago. Or it points to a form that someone randomly has posted to their code. That needs to be cleaned up.

We've been using UiPath since 2013. The Orchestrator is on the cloud and the robots are on-prem.

It's pretty stable. We haven't run into any issues with operating totally different packages. There have been some things where I wish there were more restrictions in access groups that could be applied within Orchestrator, but other than that, it's pretty good.

We are still working through scalability. There are a couple of things that we've run into that were an issue with trying to use machine templates and getting them to connect properly with the robots. Another scalability issue that we have is that we have a non-static environment where some machines get deleted after they log off and get back on, they have to reconnect to it. We had issues with that, but those are for our attended robots.

We have unattended bots. We have four of them and it's a total of seven automations, but they run every 15 minutes.

We used to use OpenScan before I got hired and then eventually moved off of OpenScan because the product was too cumbersome and difficult to navigate. So we moved to UIPath.

They saw UIPath and they saw that it was going down a good road. So that's what they chose it. 

The initial setup was pretty easy for us. Getting into the Studio is pretty simple to get us set up and going. There are a couple of issues with mixed environments for DLLs. You do get packages for UFS that I've run into trying to use one of our older DLLs that hasn't been updated, but all in general, getting it working, and being able to figure it out was pretty simple.

We have seen ROI. 

The subscription models that they have out there need to be simplified.

I've talked to a couple of our partners and talked about the 49 pages of subscriptions. It needs to be more streamlined for what they offer and packages because we run into issues where we're signing up for Task Mining, but they didn't include AI Center, which is a requirement of Task Mining in one of the factories. If the subscriptions got simplified and got it down to a couple of pages, they would see tremendous growth. That way customers don't need to hire somebody to figure out what the licensing model was versus going for a third-party vendor.

My advice would be to start in the cloud. Cloud is the easiest way for us to get started versus trying to get our internal environment set up. We had on-prem orchestrator and on-prem servers, but it was easier to implement the cloud and get it up and running and scale versus our internal environment, as well as keeping the data secured within our robots on-prem. 

I would rate it an eight out of ten.