UiPath Platform Reviews

My primary use case is for creating custom-specific products based on the customer's needs. The requirements can be received from the customer on emails and then based on it the order can be created. This reduces time, ensuring no human error and on time delivery. 

The total time taken to enter this in the system is less compared to the manual process which is indeed error-prone. This also removes the process of reviewing the order for correctness as the straight-through processing is enhanced. By making this scale on all the other locations and geographies, lots of time and effort can be saved. This also enhances the reputation of the services and organization. 

In addition to this, the confidence created by the successful implementation is a real eye-opener as the big step is taken with great success.

UiPath has taken automation to a pinnacle of excellence by mixing technology, attention to detail, and keen observation. The way UiPath has revolutionized automation with excellent coverage, user-friendliness is helping companies focus on their core areas. Employees can now focus on real problems than spend time on routine jobs.

Feature-rich options to help easy implementation: It's flexible, scalable, and easy to implement. The time taken to create the bot is less. 

The easy drag-and-drop options make it easy to solve the challenges within a short time frame. Another important aspect is the framework and other useful tools and templates available have that makes it easy to document the audit trail and also standardization.

More support for certification is needed to attract professionals. The certification process could be made more interesting.

I find the most valuable features are automation and RPA.

This solution needs improvement, especially in terms of continuing the process that is left in case of any kind of disaster that happens to the trimmers. If there is a state that can be maintained to removing the machines to another location and continue from there, it would be helpful. Right now, this is lacking.

I have not had issues with the stability of the product.

I have not had issues with the scalability of the product.

The implementation is simple.

It is a good product. I think if it could stream, rather than being stateless, it would be appreciated.

I did many small projects in UiPath like PDF extraction, website automation, and translated the data into different languages.

We are able to extract data from the PDF and website, then translate the data into different languages.

Recording and scraping which directly extracts the data from the website and saves it into the excel sheet.

We are not able to extract the data from the same type of PDF which is bulky in number, and scrapping is not so good.

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

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

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

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

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

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

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

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

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

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

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

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

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.

UiPath is a robotic process automation software that helps enterprises automate their workflow.

RPA can improve enterprises' work flow by automating repetitive tasks, time consuming tasks, and basically a value add that can be automated.

We are a partner of UiPath, and we are a consulting company.

We sell knowledge, but we also have other offerings like managed services, everything that is included in an RPA. We are a pure play company meaning that we only do RPA and we are specialized in that.

I am personally very supportive of the new trend, which is the attended automation. I think that the new strategy of UiPath path, the automation for strategy, is very promising because currently what RPA is doing, it is starting from the process, a business process to automate repetitive tasks to bring ROI. Right now, I can see clearly the strategy of UiPath to start from people and to improve them, to augment them, to augment the efficiency. This is totally new, and it's very exciting.

UiPath is bringing into the table a totally new way to automate things. Automation is not something new, but UiPath allows you to automate very easily and without many technical skill requirements. 

I met a lot of customers that didn't have big business processes. Some of our customers are rather small. They have fragmented processes, and they need to automate some tasks. Sometimes they are not big enough to justify the investment of the infrastructure and everything around it.

Attended automation will allow them to target smaller opportunities. This is something which is very appreciated by the customer, to do something small, to grow incrementally. Then you can scale.

Attended automation is definitely something that the customer wanted. I think UiPath understood that. Attended automation was possible before but was reduced and not focused on. 

If you look, even on the academy content of UiPath, there is not much attended content. If you look on the Advanced Training, the Advanced Training is about having back office robots, 

I really looking forward to seeing enterprise grade attended content. I think this will be really something interesting. The feature was existing, but I think now it will explode.

The product itself is relatable. UiPath is a fast growing company. It's incredible how they have grown over time. I remember starting two years ago with UiPath, and it was maybe 400 employees, and now it's very big. The product is stable. They have really improved it. They are very quick on resolving any issue. They are very helped by their community. On the other hand, RPA is not necessarily something easy. You need expertise to do it properly, but UiPath is giving all the resources to make this happen with the Academy, notably, and soon with their academic program.

If today, I'm automating a process in my laptop, I can publish it to the Orchestrator or propagate it in several desktop, for example, in terms of attended automation. We have another way to scale. You might have a process. We developed a robot which will consume transactions, and the UiPath product is scalable because you can have more robots. For example, in accounting closing period. You might need to scale. You might not need all the resources during the month, but at the end of the month, you will need to do the closing for accounting. You can scale for those few days that are critical to your business.

It is a great technologic company, but they are also customer focused. I just drop an email, and during the day, I have an answer and a meeting invitation to help our customer, to help us understand, to show us new features. They always been very exceptional on that. 

If you compare this to coding, this is much easier to get into it. For example, I am today rather technical person, but what if I told you five years ago, I was working in a call center? I discovered that I could automate things with Excel VBA. Today, I know how to code a little bit and i'm using UiPath. I'm automating many companies in the Fortune 1000.

Yes, we have seen ROI. We have seen very big ROI going from one to 10 FTEs even with a very strong solution, with short amount of time. I remember doing a project in Denmark which would be equivalent of about five FTEs in less than a month of development. It is more important to support the solution correctly, to handle change management. You might have saved something, but you need to wait and to maintain the solution. Your customer must not underestimate the cost of the maintenance. RPA is not a silver bullet.

Citrix automation is something complicated. This is something that is a little bit volatile, but UiPath, I think, is one of the best, if not the best in the market to resolve that.

UiPath allowed with database activity to get the SQL to obtain the data directly. Just getting the data we weren analyzing was taking the end user several minutes and 10 seconds for a SQL query to get all the data. Then you can do the checks. This was incredible. Actually, the task was estimated at about 10 minutes, and the robot was doing it in 10 seconds.

I think what makes UiPath so great is not only technology. For me, they have better tech. It's not only about that. The first thing is they are a very open company. They are very open to customers. They have a community version that you can download for free. You can go home and try UiPath yourself. I don't think is as easy to do it with other vendors, other tools.

Most of the competitors did not take the web approach. If you are familiar with the technology, you know you would rather use a web application. Now on my phone, I can go to the Orchestrator and start a job. This is not possible for other competitors as far as I know. 

I would give it nine because perfection does not exist, but they can still try to do it, to reach it.

I work for an SI implementing UiPath for a range of customers in Australia.

As an implementor, we appreciate the rich feature set of UiPath and the strong training provided.

• Extensive overall functionality and integration with Microsoft products
• The studio is easy to use, and 
• The product is feature rich.

• Linux support
• Better cloud integration and stronger auditing for governance. 

But overall, this product is excellent.

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.