UiPath Reviews

Our primary use case for it right now is in human resources. We are using it as a recruiting capability where we receive resumes in from recruiters, one in particular. Then, we're looking at the emails, pulling data off the resumes, and loading it into a database. We are also identifying resumes which might need some additional clarification. This saves a lot of time, so somebody doesn't have to go through each email, evaluate them, and pull the resumes down.

Our customers are the DoD, mostly, and some civilian agencies.

• The ability to integrate easily within our IT environment.
• The ease in which we are able to program and tie it into our various applications.

I would like more defined processes for around use cases. This might be helpful, as it is more general at the moment.

We have not experienced a whole lot of issues with UiPath at all internally. 

In some of the pilots that we are developing for our partners or for our customers, we haven't seen any major big issues or bugs.

We are still in the initial phases of deploying different bots, one bot at a time. Once we get into the Orchestrator area, we are looking at more of shared, multiple Unattended bot deployments. Then, we will have a better feel for it.

The support has been excellent and very helpful. We have received a lot of great information and assistance from the UiPath engineers and partner alliance people, who has been very helpful and responsive.

It took us only about two days of man-hours to build it out. Thus, it is easily implemented, programmed, and deployed. The ease of use and implementation together are a huge value-add and time saver to any organization. 

The ease of use did exceed our expectations. We heard it was easy. We had been trained up and had certified people. However, this was our first endeavor, in terms of deploying it internally, and it went extremely well. 

We have seen a huge benefit time-wise, in terms of the repetitive type of activities that we do. Now, we have automated those and can do the more hardcore analysis of the resumes. In the human resources area, it would take 27 minutes to process 20 emails. With UiPath, we are doing it in about two minutes, which is a huge time savings.

Given how cheap it is to initially buy the product, the licensing methodology that they have in terms of renewing every year is appropriate. Later on, if they start charging more early on, for deployment, buying the license, and deploying it initially, then having a lower maintenance fee might be more appropriate. Now, with the scale they are at, it is an appropriate way to do the licensing.

We are a partner. We are totally onboard with UiPath. We did not look into different partners to use as a product internally.

It is the market leader, particularly in the federal government. It is getting the widest use right now.

The product is extremely helpful. In terms of usability, capability, and functionality, it's one of the best products that we have used in terms of being easily implementable and cost-effective.

We find that all the materials out there for partner use are extremely effective and organized extremely well. They are very detailed and helpful.

Gone are the days when you have to deploy 100s of people for repeated tasks. We regularly update invoices of different channels and merchants to our workflow. Capturing each invoice requires some human attention. There are chances of using OCR or text-based extraction of invoices. We easily automate each type of invoice extraction to our spreadsheet. This reduces one hour (max 1.5 hr) of 100 employees in our organization.

Majorly replacing all the remote freelancers who were doing the copy-paste work for us to fetch invoices at low pay; they are now set free. We do not hire them, rather our UiPath robot does that, thus reducing the cost.

The best part of UiPath is you do not need to check anything manually. Whatever error comes, the robot automatically gets stopped rather than infiltrating absurd values in the next process.

We have deployed the technology for six months. We are facing a major challenge in front of us. The invoice automation can only be done when the invoices are on the website. Usually, we fetch invoices from partner websites as PDF. Thus we are doing extra work of converting the pdf to RPA readable file. If we had dedicated channel of PDFs then it would have worked but it is not like that. 

The primary use case of UiPath in our company is to automate rule-based processes with easy decisions.

UiPath improved our company through flexible IT solutions, which offers a fast solution to different problems.

The most valuable feature of UiPath, in my opinion, is that the intuitive handling of the tool offers the chance to learn how to automate processes in an easy way.

In my opinion, the product could be improved in the area of scraping features like OCR. Sometimes, the success-quote is not very good with these features.

The stability of the solution is mostly good. Sometimes there are bugs.

The scalability of UiPath is great. Orchestrator offers many options to scale the business.

The support of UiPath is very fast and competent.

No, I didn't use any other solution before.

The initial setup was a surprise because it was very easy to start.

I am implementing in-house for my own company.

I have no information about this.

The costs of UiPath are very high in my opinion. Small companies may not be able to get many licenses.

UiPath was chosen by the head of our company.

No.

Be it any mundane tasks like invoice processing, document management, document extraction, and migration, order processing, KYC filling, application integration, Citrix automaton, or any such rule-based tasks can be automated with RPA technology. 

Among all RPA solution providers, UiPath is the best choice and market disrupter, from our hands-on experience with the top three RPA vendors while shortlisting UiPath as our RPA vendor. With its intuitive visual coding drag and drop and Microsoft SharePoint workflow foundation technology and open platform capability, code development and debugging are a cakewalk for anyone with minimal or even no coding background.

The software is very effective, and ROI on businesses is very high even from a short period of time. In our company itself, UiPath automation helped different teams to automate their tasks by being within the compliances of end clients with its non-intrusive front office and back office automation. Thus it frees up employees for more productive and creative tasks.  

• UiPath has a Community Edition for learning and trialing out, available free of cost. 
• UiPath also has several dedicated online academies with video tutorials and various courses, which can make you a hero from zero in RPA, again free of cost. 
• UiPath community forum has a lot of active members and helps developers to resolve any query/tips to handle challenges related to development, deployment, and production. 
• The UiPath support desk replies and resolves all of our tickets/issues within a business day and even helped us by coming to our office, for tasks like license renewal, migration of bots, etc.  
• UiPath also has a dedicated marketplace serving as an open platform for sharing different packages by developers around the globe. This helps the developer community with reusability and scalability of features by sharing their own individual packages.

Image resolution affects Citrix automation. Means, the resolution of BOT system and development system should be same in order to successfully run Citrix automations. This drawback is getting resolved in Computer Vision backed selector automation feature for Citrix in 2019 version of UiPath. Also, unknown runtime errors mainly due to application integration issues can cause issues, although it's a very rare scenario. This issue can be resolved to a great extend by using RE Framework in your development, which is also integrated in UiPath in the latest version.

We tried Automation Anywhere also, but shortlisted UiPath based on it's ease of use and the customer support.

Although cost is little high ROI is also too good. Thus my recommendation is go for UiPath!

Yes, Automation Anywhere

UiPath is bringing up a lot of new features and which the competitors have never thought off, maybe releasing in the 2019 last quarter.

I work in finance functions, so typically implementing it within our finance accounting hub that we have out in Manila when most of our processes are stabilized and globalized experts. So, it's a very good fit to have our processes automated out in Manila.

We are in the early stages of implementing our robots, but at this stage, you already see things like our customer satisfaction, so we're supporting your finest teams, so they are already getting benefiting it, and very much tedious tasks that sitting with the team, they're actually find they don't need to do the tedious tasks. 

Funny enough, that out in the Philippines, they are actually welcoming robotics because it creates capacity for them in order to bring more work into our accounting hub, so that would be where I can see a real benefit in our organization already. 

I think we very much focus on traditional development opportunities, so API to API connectivity and those type of things are very much the way that we're doing things. We have development teams out around the world that develop, and I specifically work with financial functions and develop our finance systems, typically more of a traditional development focus rather than using robotics opportunities, but we are starting to see robotics becoming a bit more prominent. People are more interested in it, and people are starting to engage a bit more with the robotic side of things. I think the benefit of using robots is actually becoming a bit more visible within the organization.

We are making use of attended bots. Unattended bots are of course a huge benefit. I can see the future if I use the 80/20 rule; I can see probably 80% of our bots will be unattended when we will implement 20% into attended bots for our organization at the moment. I don't know how that will look like if we say everybody in organization using bots, then of course attended bots will become very prominent, but where we are right now, I can see unattended bots will become very attractive for us right now, so probably seeing the bigger opportunities at the moment, and those big opportunities, unattended bots will be well suited for.

It is difficult to get your head around attended and unattended bots, but once you get to understand the differences, I think yeah. I can see benefits and pros and cons on both sides, but typically where we are now, we use attended bots. I can see us moving with our big opportunities into unattended bots, and where the future takes, I don't know. I'll let you know then.

I think it's the ease of use for the developer, so we can actually make use of people within subject matter experts rather than having fully fledged developers, so that's one of the main features. And, I think, based on that, it is actually the speed in which we can deliver some of these automations, so the delivery and the build of the box is actually much quicker than your conventional development, so those will be my two top points at this stage.

We've created a bot within our collections team. We are doing a reconciliation, and since implementing the bot, which was at the beginning of this year, we hadn't needed any changes onto the bot. 

Scalability very much so, so exactly that reconciliation bot we were able to apply to different reconciliations within our collections team, and they fall. Yes, it's very much scalable as well, so we are running four different bots at this stage for our collections reconciliation process.

I think we will probably make use of the community more, so asking questions within the community forum. I've not really had to engage with technical support directly apart from our sales person that we could ask questions from, etc., but generally, the technical questions are more posted onto the discussion forum and answers being given and taken from there.

Our proof of concept was done using PwC, and they've helped us build our proof of concept. The reason for that is they've delivered a piece of work where we wanted to see whether this has already been delivering a piece of work where this really fell into, so we engage with them often to help us deliver a proof of concept, and that was very successful, and of course that helped us roll up more into the business and taking a little bit more on internally rather than continuous support from PwC.

Coming from a person that doesn't' know much of robotics or anything of that, as it's a new technology. I think it was quite difficult to get your head around that first. Setting it up, installing the software's very easy on occasion, but getting a grasp and understanding of the difference between the studio and the difference between the robots in that regard was quite difficult to get your head around not only for us who's been setting up the center of excellence but also for explaining to the business the different components and then just understanding what the different components does, and I think it's maybe more around terminology. We're building a bot that's running on a bot, but the building of the bot is in studio.

It's a very easy concept, but it makes it difficult for the business to understand what you're talking about and what we're working in and what actually runs the bot and those type of things.

We are starting to see a return on investment. I won't be able to answer that right now, probably only be able to answer once I start analyzing it, but we are starting to see a return on investment. I think it will probably take a good few months before I can analyze how well we're doing. I think fairly soon we see a return on investment.

Does it fit in with the business, what they expect? I don't know. That's a given that the solution absolutely does, so if I come back to our original example of the reconciliation bot within our collections area. I think there's almost 100% human errors reduced. The bot doesn't make any errors, so we've seen it running smoothly for the last since the beginning of the year, so last nine, 10, 11 months.

Citrix environments are quite difficult. It takes more time to develop the bot itself. Accuracy's maybe a bit of an issue there, so from a Citrix type of environment, I'd probably try to avoid it from my side, but it's just because I don't like to work with the images. I'd rather work directly within hotkeys or whatever.

I think I would rate the product probably at about an eight, which is coming down to the usability. It's really easy to use. It is easy to implement and roll out getting people involved. I think there is drawbacks in terms of the understanding of where the process is, so it's maybe on our side, understanding the process and which processes are suitable for the bot and what the bot will be able to do then with those. I think taking a subject matter expert and giving them the expertise to build bots limits your ability to understand the full capacity of the product. I think there's a lot of things changing within the product very quickly and to keep up with all of the enhancements that you're making makes it a little bit difficult, but over all, it is very good, and if you apply correctly to your processes, you will definitely seen an improvement in your process and return on your investment.

We're specializing in law and local government, so that's our target market at the moment. Obviously it's usable everywhere, but that's our market, and we find that that's where there's a lot of opportunity for sale.

In one of our legal scenarios, we had a situation where they were trying to deduplicate their database. They worked out that the man-hour cost for deduplicating that database was 11 man-years. We got that down to 30 days with a saving of 3.89 million pounds in what they would've expected their cost of that process to be.

As a sales-based operation, we get a lot of inquiries through our own website. We were finding that we were extrapolating that information, putting it into an email, I think into a spreadsheet, putting it into Salesforce, whatever. We've now got our own robot, which we've built, which opens up the backend of Wix, which is our website building tool. It receives all those inbound inquiries. It then goes out and looks at the public domain. We'll use that email address, or use a name against LinkedIn, against Facebook, against Twitter, to find out any more information we can find about job titles, maybe phone numbers or email addresses if they're missing. Get all that data out, build up a real case for that client, then the robot would enter that data into Salesforce, it will send them a welcome email to say, "Thanks for you inquiry, please find attached the information you've requested." Bring them straight into Salesforce, set up a reminder, and then send me an email to say, "Follow up this client, they've downloaded some information from our website." We've automated that whole process, and we can then use that for events, and seminars, and webinars, everything else that we hold, because they're genuinely interested clients, and we get around that GDPR issue.

For us, it's the ability to offer as a subscription model. We looked at the other competitors to UiPath, and we found that the way of delivery that we offer is a subscription model. It's a very, very small upfront fee and a monthly cost, and UiPath gives us the flexibility to do that. Some of the other vendors don't do that because they sign you up for ten licenses over three years, and it's just not practical for us.

From a cost perspective, it's not really relevant. It's really about the processes they're trying to automate. A lot of people are doing data deduplication and data onboarding, so an attended robot is absolutely fine. Whereas when we're trying to do things like answering an email, an inbound email, set up a process, respond to that client, then a 24/7 unattended robot is the way to go. We use a mix of that with our client base.

We've had some serious issues with clients that are running in Citrix environments, and we've got a couple clients that have moved away from other competitors to UiPath and to us because they just cannot do that screen scraping technology. Yeah, we're finding a lot of it in a Citrix environment, and a Citrix environment, on an Azure cloud, on a virtual machine. So there's various steps, and UiPath's the only one we've found at the moment that will actually enable us to deliver that.

I think the AI question is being raised everywhere, and there certainly needs to be a lot more intelligence involved in that. The ability for the robots to start thinking for themselves is coming out in the later versions. There are very few limitations at the moment, because we tend to pick relatively mundane, tedious, repetitive tasks, and it's all about number crunching. Really, RPA globally is all about number crunching. But in the next six to 12 months, there'll be more intelligence added, and there'll be more stuff going on that brings it closer to the AI environment that everyone's spouting about at the moment.

We've been involved in automation for ten years or so, and UiPath for about two or three. We've had no major issues from a stability perspective.

Very much so, and more so with the later revisions of the software. But we tend to start off with one project, one workflow, and then we're all about scale. But it's a land and expand approach for us.

We always say that any idiot can build a robot. In reality, it's working out the workflow, working out what's involved, making that process lean that takes all the time. That's where we get involved. Actually setting the robot up itself is very simple. Some of the discussions we've had today talk about clients setting up their own robots. It is a relatively simple, drag and drop, point and click type setup for us.

We're averaging three to six months ROI, because we offer this subscription based model. There's no massive upfront cost. I think the biggest ROI we've seen is the one I mentioned with the law firm, where we estimated 3.9 million pounds of saving, and we actually realized 3.899 million pounds of saving. That was by far the biggest ROI, but as we start working with bigger councils and bigger law firms, those ROIs can only increase.

Not sure about percentages, but one of the anecdotes I always say to my clients is we've all managed to write our own name incorrectly on a web form, so if we cannot spell our own name correctly, what chance have we got of spelling the name of a client that may be from overseas? The reduction of errors is phenomenal, especially in that mundane, workaround environment that everyone seems to be in.

The model that we offer, as I say, is a subscription model. The idea is that we land and expand. We charge a very small fixed setup fee with a monthly subscription, and a minimum commitment to us is three months. We believe that we have to prove to the client that robotics is the way forward. If you go to one of the competitors, such as Blue Prism, they will insist you buy ten licenses, you sign up for a three year deal, you do a 50,000 pound proof of concept, and then at the end of the proof of concept, they build you a live, working robot. Our argument is that we've already built you a live, working robot to do that trial with real data, with real cases and scenarios, and with real workflows, and we just make it from a dumb environment to a live environment. Yeah, we absolutely compete with those on a very different level.

We're very, very happy with the product. It does exactly what we want it to do, and it allows us to sell UiPath, or sell RPA in the way that we want to. We're not being dictated by the manufacturers to how we have to sell their product. We know our customers best, and we believe that our methodology is the way forward. That's the flexibility we get with UiPath.

We use UiPath for backend office automation and website integration. 

UiPath increases the dependability of our operations team and simplifies the coding process for novice developers.  It has freed up your staff time to work on other projects.

It's easy to automate rote tasks with UiPath. 

UiPath Studio could offer alternative coding methods. You could invoke the code with VB or C#, but I'm unfamiliar with either of those languages, and I don't have time to explore them. 

I have used UiPath for a little over a year.

My impression of the stability of UiPath is decent.

The scalability performance is yet to be fully assessed as the environment grows.

The documentation is not impressive, warranting a rating of five out of 10. It is neither bad nor great.

Neutral

I did not use a different solution before UiPath. The acquisition happened before my time.

I do not know of any alternate solutions evaluated as the acquisition was before my time.

I rate UiPath five out of 10. 

We primarily use UiPath for RCM and it can handle most tasks effectively, especially when dealing with data extraction from PDF files. There might be more complex scenarios where AI could be more suitable, although the implementation might be challenging. We are in the process of evaluating these AI-powered use cases.

We have found UiPath to be quite valuable as we actively deploy and use bots, which have become a significant asset to our operations. 

We were able to achieve the savings. It has freed up around ten thousand hours of time and resources for other tasks.

Improving financial and recording operations through the use of charts would be advantageous.

I have been using UiPath for approximately two years.

The stability is excellent.

Scalability is impressive, and it only requires the appropriate licensing.

The support is quite commendable, and they are very prompt in addressing issues. I would rate it eight out of ten.

Positive

The initial setup is straightforward.

ROI is significant when the use case results in substantial cost savings, but it's important to note that not all use cases deliver such hard savings.

The cost is on the higher side.

My recommendation is to thoroughly assess use cases and choose the right tools to prevent possible setbacks. Overall, I would rate it nine out of ten.