UiPath Reviews

I've used it to automate different types of processes. My first project was to automate PDF documents. The process was a bit lengthy for the client. The client actually used to enter the information into the PDF templates and get them submitted to the government websites. And once they submitted their documents, the government released grant payments or other stuff. Previously, they hired people to do the data entry. However, it was taking too long, and some crazy errors. They had to have a pretty formatted, clean Excel sheet.

With UiPath, the bot would choose the data, get the data from there, and then put it into PDF files, save them with the sort of renaming schemes, and then upload them to the drive and then to the portal. That's the first use case I got. I built up workflows in it and automated the whole process. 

I keep exploring it and now have other use cases coming in as well. There are more than 150 or 200 use cases for different types of projects. 

The process management is great.

The orchestrator is helpful. And they have something called live monitoring. If you have an unattended bot set up on someone's system or in a virtual private server, when the bot gets executed, you can actually monitor it in the live stream. You can open up the live stream, keep checking it, and look at the automation, and how the board progresses, and you can take control of the live stream in between as well if you want to. 

The ease of building automation is relatively very good. Most of the programmers and developers get hectic while writing scripts. However, they get bored. Now we can just create a sequence of processes. That way, we can train some colleagues, and it's pretty easy.

I've used the solution for a good cause, for a client trying to gather information from the Internet in Switzerland to reduce carbon emissions. They were trying to get a lot of information to raise awareness regarding emissions and businesses. I helped the organization implement a use case.

The product enables us to implement end-to-end automation. There are certain scenarios in cases where integration is required. It is important based on certain scenarios or use cases.

The user community is great. When I was starting out, I really got a lot of help from the forum. The community is very good. The most common questions are already being answered there, and everyone is engaged. The community is pretty strong. You can just post your question in theory and get a reply real quick.

The solution has helped to minimize our on-premises footprint. You can just get it all done on the cloud. They have recent updates coming in in which you don't need to install any tool on your system. You can just develop your workflow on the cloud as well. 

It really helps non-technical people. I don't need to go through the hassle of installation. I just go to the cloud and start developing the basic workflow.

The UiPath Academy is good. I didn't have a chance to do a lot of the Academy yet. I have had one or two trainings for the implementation methodologies. That said, mostly I've learned through real-time projects or through my self-learning, plus the content we have on the Internet. 

The AI functionality is used in our automation programs. It has documented understanding. It has built-in trained models that help understand the document. You simply go to the document, scan, install the package, and just train your invoices and the data you have with similar invoices. It helps you to identify the invoices and extract information from the structured data. 

UiPath has helped speed up digital transformation and significantly reduced the cost of digital transformation.

It's helped reduce human error. Being able to have RPA enter information again and again really helps solve the problem of dealing with random errors. 

UiPath frees up employee time for other stuff. It helps optimize time and make everything efficient. Whether it's attended or unattended mode, it really helps employees. We can save a lot of hours. The automation hub that they offer can upload all the stats. It will take a process and tell you how many hours you could save. The cost savings are directly proportional to the time savings.

I used to have some workflows that were a bit lengthy, and I just see that some of the time, they crash. It's unstable if the workflow is long. Sometimes you'll run an update, and it will make a workflow crash. 

They could make it more user-friendly. 

I've been using the solution for around four years.

The solution does crash sometimes. 

In one instance, I was trying to read a file, and the file itself was a bit larger. It's hard to read a large number of files.

The scalability is good. I would rate it eight out of ten. 

I haven't contacted technical support that often. I only reached out to get more information on a certain case. 

Positive

I did not use any alternative previously. However, since using UiPath, I've also used Power Automate and Selenium. Selenium is not a direct competitor. However, I have used it a lot. Power Automate doesn't have the robust community or forums that UiPath has. That said, it costs less. 

I'm an implementor. I deploy solutions for my clients. 

The cloud implementation of UiPath is straightforward. If you are knowledgeable of the process and you're good in tech technology, you can handle it. If you are non-technical, then it could be a bit of a lengthy process to learn first and then go ahead and do it.

The deployment can be handled by a single person, depending on the use case. If it's more complex, you may need a team to deploy.

There is maintenance required. If there's a change to the website, process, platform, or data point then you have to go in and adjust. 

The licensing cost is pretty expensive compared to competitors. 

The community edition, however, is pretty good for developing automation. You can have one unattended product as well, which you can utilize. 

A developer license may be around $420 or $450 a month, which is really expensive. 

I'm a reseller.

I'd rate the solution nine out of ten. 

I would advise others, if they mean to use the product, to be specific and look at the cost structure. A small business will always need to be mindful of the cost structure. For a smaller business, the community version might be an option. 

Overall, the orchestrator, the cloud management, and a lot of their features are great. 

We do a lot of claims processing for healthcare providers. We handled the billing, and it was very beneficial for us to use automation to perform those claims management and submit the claims for those various providers.

We utilize Orchestrator, the robots, both attended and unattended, and team sites.

Our organization was trying to achieve better accuracy and better throughput with this AI-powered automation initiative. We were just getting all the claims processed that we needed to because we just couldn't keep up with the workload. Using automation was a requirement.

It is very important that UiPath has orchestration. Without Orchestration, we wouldn't be able to do anything we do. My team specifically manages the Orchestration, and after the automation goes live, they come to my team to manage. 

Without Orchestration, I couldn't comprehend how we could do it. We have 360 machines running over a hundred processes with thousands of transactions a day. Without Orchestration, I don't see how we would be able to use the function.

Unattended robots with Orchestrator are our bread and butter. We don't do very many attended automations. It just seems that they are much more resilient when we run a program in a way that doesn't involve any users. 

We did have insights at one point, but that was prior to it being re-engineered by UiPath. We have to pick that back up because it didn't really work for us back in the day, but I've been told that they've changed the vendors that they've used for that product. We've re-licensed it, and we're in the midst of reimplementing it.

We are working with a vendor, Namica, the UiPath vendor and we are starting with task discovery processes. We're just touching more on task capture instead of process mining.  

We would like to see better connectivity with different technologies. We found credential management to be something that is a real problem for us, especially working with third-party systems. 

Being able to manage those credentials and have a product that could help us with that would be nice to have. We've ended up using CyberArk WPM for this purpose. But it's not something that's prepackaged; we've had to do it ourselves.

I have been using this solution for five years.

I have no issues with stability. UiPath improves how the infrastructure works and how stable everything is. I haven't had many problems. There are a couple of quirks that different product levels will address or resolve, but it's documented pretty well on the support side.

Scalability is pretty good. We did scale. Our initial rollout was 65 machines within Orchestrator, and we have since gone to 360 with one Orchestrator and one tenant. It's pretty good—I don't have any complaints about the scalability.

When I need support, I need them to respond. I actually had an instance last week where Orchestrator was not performing well. There were a lot of locks on the database, and it was bringing the Orchestrator trigger down. 

I opened a ticket and marked the criticality level as high. There's only one above that, and I didn't get a response back for a few hours. 

I had to go back to my sales personnel and explain to them that it was unacceptable. There was a problem with support.

In that particular instance, it was pretty poor, but I hope they saw that it was a problem and are working to address it.

Negative

We used Microsoft Power Automate very briefly because it's just part of our Office 365 package. We've used it very sparingly. It was more of a means to an end than a plan. 

We're actually looking to use it with a UiPath automation that we've created because it's Microsoft-centric, and it'll work quicker and do what we need it to do without having to invest a lot of time in the development. It might just be a subset of what we do.

We're currently on-prem, but we're looking to change that. We're up for renewal in January and are already discussing that shift over to the cloud. We can utilize AI better if we shift to the cloud. 

I manage the infrastructure and the deployment of all the processes. I have a pretty solid background in infrastructure, so it seemed pretty straightforward.

We have a lot of departments within our organization that can do the implementations. But personally, I'd rather just do it myself and make sure it works.

We have an admin team that makes sure that the ROI is there before we even start.

The pricing is competitive. I like the solution's pricing structure. However, the development tools can have a better discount because we'd like to have more developers be able to do the work. 

In the long term, running the product and running the automation unattended, I completely understand the pricing structure there, but on the Studio side of it, UiPath can come down a little bit on the pricing.

The product is leading the way toward AI, and there's some onus to make sure that we stay current with what UiPath is doing. It's the other way around too, where they need to understand where we are and help support us and our program. It's a two-way street. They need to make sure we understand where they're going, and they need to understand where we are. 

Overall, I would rate the solution a seven out of ten. 

I would recommend making sure your process discovery is done correctly because no matter how many automations you can put in place if you don't have a good understanding of your processes, it's not going to do anybody any good. 

Process discovery and getting buy-in from management are key.

Our primary use case is more of a reactive ad hoc use case to solve business problems on the fly. We can build automations to update thousands of records. 

We're putting a little bit more money and resources into it, and we're starting to go down more of the unattended automation path to actually do more end-to-end processes. 

The use of AI has freed up time and resources for other tasks in our company. We are a little bit more of an ad hoc approach right now. I just finished up a new cross-set of processes about two weeks ago that allowed us to onboard a client. I wouldn't have been able to without this automation. It would have taken a couple of months of several people's time to get them to get all this work done in the back end. 

It is helping. It provides value where we wouldn't be able to do certain things without it.

The broad functionality is the most valuable feature because it can interact with many different factors, and there are several ways to solve a problem. 

There's not just one cookie-cutter way to achieve what you need to achieve. You can get there in various different ways. That's a key aspect for me.

From the UiPath product perspective, this might be a problem because we're on-prem, but they add new functionalities pretty rapidly. It feels like there are releases constantly, and I don't want to update it too often. 

I feel like I'm behind even though I might not be. Sometimes, we'll go a year without doing any major upgrade to Studio or Orchestrate or anything. 

That's more of a personal problem, but that's because there are frequent updates to understand.

We started using UiPath about three years ago. We're a small company, an 80-employee bank, in Denver, Colorado. 

We're smaller than a typical RPA client. Our development is probably underutilized compared to larger institutions. Still, we thought it was important to get in the game early and start establishing the foundation of an RPA environment.

The stability is good. We have run into some issues that they believe are more related to their environment than to the application itself.

We're in the process right now of scaling. It is a scalable solution.

The customer service and support have been amazing. It is honestly the best product support. 

I have no complaints about the support. I don't even get worried when I have a situation. I might need to open a case. I like partnering with them. It's a good experience.

The initial setup was difficult because I didn't have a lot of past experience setting up a new program. This was a whole new program for us. Not only was it installing things, but it was also wrapping your head around how to set up properly so that we can get out of this.

It was a little challenging, especially with the on-prem solution and working in Citrix, to make sure these different servers were talking to each other properly, but overall, it was not too bad.

We're on-prem right now, so we're not even in the automation cloud. We're looking into that in probably the next year. The UiPath platform has been great for getting to understand those products a little better.

I see a return on investment. Even with underdeveloped automation, we definitely have a good ROI. 

If people don't understand the benefits, they might think it's a bit pricey, but for me, it's very cost-effective.

We looked at Automation Anywhere and Blue Prism. It was three years ago.

I work in banking. We are highly regulated in our server infrastructure, so we decided to do a VDI environment that works in Citrix. 

At the time, UiPath seemed like the best product to work with Citrix which was a large reason why we chose UiPath. 

We wanted to make sure we were getting something that was going to play nicely with our environment. It has proven to be true to this day. 

We feel like we chose the right vendor.

Overall, I want to give it a ten out of ten. I have to give it an honest nine just because I haven't used other RPA solutions. But I love UiPath.

If you're going to go in, go all in. We didn't go all in at the beginning, and we should have. We're playing a little bit of catch-up because of that. My advice would be to go all in and be organized with your approach.

We use UiPath for robot authentication. We primarily use the software for accounting, particularly in our financial department, where we place some details from the client site, put them on a particular website, download the details, and then send those to a specific client.

I work for a big organization with many team members who access UiPath. On the client side, mostly enterprise clients, UiPath also has many users.

We've seen many benefits from UiPath, particularly from the client side.

The first benefit is manpower reduction, or reducing the number of people required to do the work.

Another benefit of UiPath is the reduction of errors. Sometimes, you'll notice errors from human intervention, but when the work is done via UiPath, you won't see any errors, so the solution has improved the success rate.

What I like most about UiPath is that it significantly reduced the amount of human intervention, which means that what usually takes people to do in ten to fifteen minutes would only take the robot one to two minutes.

I also like that UiPath runs 24/7.

I find the ease of building automation in UiPath valuable. It's easier to do that in UiPath versus other platforms, such as Blue Prism and Automation Anywhere. My organization has a lot of activities and needs to give specific details and accesses, and I found that UiPath works in the final product.

UiPath enables my organization to implement end-to-end automation. Sometimes, it's required for the user interface, but implementing end-to-end automation still depends on the product and agenda.

The solution helped minimize the on-premises footprint of my organization, mainly because it allows you to do a significant amount of work remotely, so UiPath is the best way to minimize your on-premises footprint.

My team has utilized UiPath Academy, precisely the basic course, then the development course, and then the advanced certification. You have to start with the basic course that shows you how the platform works, then move on to the development course, and then the advanced course or certification.

What I like best about UiPath Academy courses is that you see several maintenance scenarios you don't get to observe daily. You'll see perfect examples of different scenarios in the videos plus the instructor has a good teaching style, so my team was able to understand the lessons easily.

I also found that UiPath has helped in significantly reducing the cost of digital transformation.

In terms of reducing human error, UiPath has helped decrease it by twelve to fifteen percent. Sometimes, humans working for five to ten hours become tired, while the robot can work twenty-four by seven without getting tired, complete the work on time, and ensure that all details it encodes are correct.

Because of UiPath, my organization doesn't need so many people, but you still need to manage the robot, monitor it, and ensure that reporting works fine. It's not like my team has to do another project after utilizing UiPath. Still, the solution requires managing routers, which now requires one person with UiPath versus ten people without UiPath, so that's one example of what the solution has helped reduce. UiPath helped free up about thirty percent of employee time.

I like the most recent update that was completed for UiPath because it helped solve the clustering case, and then the modern authentication is good.

What needs some improvement in UiPath is its Document Understanding functionality. It should be simplified because, right now, it's a little complicated to use, as you have to give it data or details, so in the future, I hope that could be improved.

I have been using UiPath for more than four years now.

UiPath is a stable solution.

Currently, we find UiPath scalable, but we still need to observe and monitor it for an extended period to check its scalability.

We have not had any issues with UiPath technical support. They've helped us a lot and have provided a lot of input, and we are satisfied with how they've handled different types of issues.

Our rating for them would be seven out of ten.

Neutral

I've used Blue Prism and Automation Anywhere.

In my organization, my team previously used Excel Automation, which means the team uses scripts and macros to automate tasks. However, there was a lot of limitation, while in UiPath, there was none, so my organization switched to UiPath.

Deploying UiPath wasn't as complex. My organization has a lot of members who can access everything. There wasn't any issue with deploying the solution.

At the moment, I haven't seen ROI from UiPath, but maybe in the future, I will.

I find UiPath a reasonably priced solution.

My organization currently doesn't use UiPath to automate processes that deal with good causes, but there is a possibility in the future.

The organization I belong to has not implemented the AI functionality of UiPath in its automation program.

UiPath is currently deployed on-premises, but the team is considering moving it to the cloud.

Sometimes, the solution requires maintenance, specifically on the server side, as that runs 24/7, so you need to integrate and do some checks to maintain UiPath.

I recommend UiPath versus Blue Prism and Automation Anywhere. If you are using other platforms, I suggest moving to UiPath.

My rating for UiPath as a solution is eight out of ten.

My organization is not a UiPath customer. My organization is an integrator that creates the robots and recommends UiPath to businesses.

I work on database automation. We just delivered a dynamic workflow in an Excel automation as well. We work on many types of formulas. In addition, we develop physical automation. For example, we created a process that posts many photos at once on many groups.

We are able to produce output with UiPath in less time. Where a manual process takes one to two hours, we can develop a UiPath solution that takes 15 minutes. In terms of saving time, one bot has saved 60 to 70 percent of the time the task used to take. We have also seen human error reduced by about 60 percent. 

We have automated processes with 20 to 25 bots, and our organization is very happy with UiPath.

It's easy to go with UiPath. It's user-friendly, and any IT person will find it easy to use. It can be learned in six months to one year.

Also, we can use Orchestrator with Action Center for end-to-end automation. With Orchestrator, we can schedule automations.

I would like to see the setup improved. First we install it, then we log in with Orchestrator, and then we have to log in to the UiPath website. I would like all this to be merged into one setup.

I have been using UiPath for 2.7 years.

The stability of UiPath is a nine out of 10.

The scalability is between eight and nine out of 10.

Support can take a lot of time, two to three days to receive a response.

Neutral

I have developed Excel automations with Power Automate.

We are using the Community Edition of UiPath and it is deployed on our servers. We use it in one location in one department. It was not a complex process to install it, although there was a little bit of complexity to it.

If there is any activity or anything changes in the environment, maintenance of UiPath can be required.

We have saved both time and money and have definitely seen return on our investment.

The price of UiPath is not too expensive or too cheap. It's in between.

We have four people involved in deploying automation: one developer, a team lead, and two DevOps developers.

My recommendation is to learn flow development.

We can't disclose our exact use cases, but we do intelligent automation with UiPath.

It reduces human error and most bots are able to generate 50 to 60 percent savings in terms of employee time. It's definitely helping our organization to save costs. We are able to do work at one-sixth of the cost. Even after adding an FTE for bot support in the back end, UiPath saves us significantly on costs.

The Task Mining is one feature that is very helpful to any business analyst. I do business analysis, and the info that I produce goes to our UiPath team to develop automations. Task Mining is the only part I leverage.

UiPath is pretty flexible and offers security aspects as well. It helps us do intelligent automation, providing multi-language support. It can also integrate with any kind of application, such as Java or legacy-based applications. We can call APIs when needed, and it can be scheduled. We can even manage UiPath licenses for multiple uses.

It has certain built-in Excel features, so if you want to pick data from Excel or crunch data in Excel without using Excel macros, you can use UiPath and take that data to any type of ERP application. In that way, it's quite flexible. It has very good features that help you process data across different technologies and platforms.

The UiPath Academy courses are also very useful. I became certified in UiPath business analysis training, and have also done UiPath technical architect courses. It helps you kick-start your career in UiPath. It's very helpful.

UiPath helps with digital transformation at the outset, but I focus on the amount of runtime support needed for managing bots. If a bot is going to save four to six onshore resources, at least one offshore resource is needed to support it. That is one area where UiPath, Automation Anywhere, and every automation software has to focus. A lot of bots are highly sensitive. Even the slightest change in screen behavior or a small change in the process and, many times, they are not intelligent enough to run on their own. That means there is a high level of dependence on the support team. Automation software providers need to improve on this.

Also, UiPath could bring in a type of low-code or no-code automation so that it can be used by the masses instead of only by technically proficient people to develop solutions. Low-code or no-code automations would be really helpful. 

In addition, for intelligent automation to become really robust, a lot of features need to be added, and the accuracy of the model has to be improved. Right now, if I am going to implement any UiPath or AI solution, in the beginning, it will only be 30 to 40 percent accurate. It doesn't get to 70 to 80 percent.

These are the types of things that need to be improved in UiPath.

I have been using UiPath for between six and seven years.

It is a stable environment. It doesn't encounter any errors on its own, unless there are system or functional exceptions.

It has good scalability. We can even redeploy an existing use case to a new use case. Or when a new migration takes place, we can use UiPath by modifying it and making it work in the new enrollment.

Our support team handles technical support. I haven't contacted them.

The price is reasonable, although Orchestrator is really costly. Not many organizations will be able to afford that, but without Orchestrator, you can't do bot management. It becomes pretty difficult. UiPath has to focus on orchestration pricing. They need to bring in some innovative pricing.

From the business analysis angle, refine your use cases and make sure you are identifying the right ones, before deliberating about any automation platform, whether it is UiPath or not.

I create robots for clients of our company. We have an insurance client that asked us to help with sending letters by email and extracting documents related to insurance, between their insurance agencies.

We also do e-signatures using an API with a server to get digital signatures for all the customers of a bank. And with other banks, we have worked on onboarding clients. We have all the information about them and we do subscriptions for them.

We also have a lot of clients that ask for filters and updates in Excel files.

Employees who were doing the same tasks every day are happy to have time to do innovative things and stop doing tasks that a robot can do. They feel free from those unwanted tasks. These kinds of tasks are often boring, and employees can make mistakes. They spend a lot of time doing them without any benefit, because it's something they do every day. There is no innovation when they have to do those tasks. The most important part is that we can help employees in these situations.

The benefits include managing employees' time. A robot can work at night or even on the weekend, whenever you schedule it to run. It's helpful because employees can let it do their jobs when they are at home. There are also fewer errors because when you give a robot a formula, it does all the iterations in the same way. Even if there is a special situation or an exception, the robot can help itself get through it. So it helps with an employee's time and efficiency, and they are happy about that.

There are two kinds of robots that we deliver. One type of robot works independently, giving our client's employees time while the robot does its work. And there are other robots that do work but need a human to verify things. But even that type of robot reduces the work, leaving only the validation.

And when we start discussing RPA with a client, we can see the difference in the costs. We ask them how much they spend on a task or how much time it takes, because even hours have a cost. We then give them the difference. If a robot does that task, it will spend X amount of time on it and you will save this much money. It depends on the project, but sometimes we save them 30 or 40 percent of their time or even more.

The scraping for data extraction is very important. There is also a connection with all Microsoft tools, like Outlook, Excel, Word, et cetera. And OCR, the Document Understanding feature, is important because we have clients that ask us to read data from scanned documents.

UiPath Orchestrator is also important to help us schedule our bots.

In addition, UiPath is a low-code solution, which is very useful and helpful. Given the features and solutions it offers, it's quite easy. The ease is a seven out of 10, or even more. The challenge for us is connected to the demands of the client. Sometimes we work with banks, sometimes with insurance companies, and the challenge is to know what they really require before we start developing. We need to know the exceptions that we might face. But the development part is quite easy thanks to the UiPath Academy and the forum. It's not that hard.

We can even teach our clients a little bit about the use of the UiPath. It's easy and doesn't require an IT engineer. They get excited to use it.

I started my use of UiPath with the UiPath Academy and I'm still learning there because there are updates and new features to learn about. The Academy is very helpful with its videos and explanations, and with the questions at the end of the lessons. I like that it allows me to learn on my own time. It's very constructive because things are explained well and I like that I don't have to be at a school to learn it.

Also, the UiPath community is very good. Anytime I have a problem, or something blocks me, I post a question on the forum and people spend a lot of time helping me. Even if the first solution doesn't work, they come up with another one. When I started working with UiPath, there were only a few people who knew the platform and I had to wait days and days to get an answer, and sometimes I wouldn't get one. But over time, I feel the difference because there are more people in the community and they are more responsive and very helpful.

We have the new license, the Flex Plan with Automation Suite, but we don't have practical examples and we have found it a little bit difficult when dealing with it. We could use more specifications about it and practical examples. Sometimes clients ask us questions, but, even on the UiPath forums,  we don't have answers. We have to spend a lot of time trying to find them. Practical responses about installations and the differences between the kinds of installations would be helpful.

I have been working with UiPath for almost three years.

It's very stable. I haven't faced a problem with UiPath Studio. I would give it a 10 out of 10 for stability.

It's scalable. I would rate it a nine out of 10 on this aspect.

I have needed their help too many times but they have been so helpful. They respond with emails, and sometimes I even talk with them on Google Meet. They are responsive.

Positive

We have worked with UiPath on-premises, on Azure, and on a private cloud. That's where we use it the most. An on-premises setup is easy to do, and on a private cloud, it's not complicated. But with the Automation Suite, it is complicated and we asked UiPath to help us.

When we deploy it for our customers, we ask them to prepare the production environment for us so that it is already ready. For deployment, we have an architecture and an infrastructure engineer. Sometimes we need the infrastructure engineer if something is complicated about the infrastructure. We work with the IT department of the client and our infrastructure engineer.

For unassisted robots, we take the robot from the development machine or the test machine to the deployment machine. For clients using Orchestrator, we create the robot, the job, and we execute the robots from Orchestrator.

Maintaining UiPath is not difficult. One engineer can handle it, for now.

I did some research on Power Automate, but I haven't worked with it. I only saw the interface and some examples. We are planning to learn more about Power Automate and the differences between it and UiPath, but for now, we are only working with you UiPath.

My advice is to use the UiPath Academy and do some practical exercises. And when working with your client, ask all the questions that you have, including exceptions and real cases. Technically, everything is good. Just attend the Academy and use the forums and everything will be okay.

We use it mostly for our sales and for our clients, with relatively simple, stand-alone robotic solutions. Some are attended and some are unattended. We use it for reporting in our finance and HR departments. 

We have automated processes for our clients that, before, took somebody three days to do, and now they're done in minutes. That says everything. It's extremely useful for saving time and avoiding mistakes. Those are the two main efficiency factors that we have seen with our clients. Repetitive projects, where someone has to copy a lot of data from one place to another and then work with the data, are very prone to mistakes. We can completely eliminate mistakes and save people a lot of time so that they can do more interesting tasks. We have developed programs that reduce human error by 100 percent. There are no errors, once they are automated.

And it absolutely accelerates the process of digital transformation. There is no doubt that it is getting faster and faster. We are thinking about combining RPA solutions from UiPath with ChatGPT or whatever else comes along, to see if we can make them work together. This will be the future.

It enables us to implement end-to-end automation. We have projects where it automates the entire process from one end to the other. Very often we have "human-in-the-loop" within them, because some decisions have to be made, but they are almost end-to-end solutions.

End-to-end automation is extremely important. Usually, when we start with a new client, we start with a smaller process as a type of proof of concept, so that they can see what is possible. Then, we extend it up and down until we have an end-to-end solution. We have seen that it's better to develop a process step-by-step, and not try to do everything at once. But in the end, we have an end-to-end solution.

The UiPath community is used by our developers. They ask questions and receive responses. They are definitely active there.

We have had issues with Ingram Micro. It happened that we ordered licenses and we received something else. It takes a relatively long time, two and sometimes even three weeks, after the order until we receive licenses, and clients are sometimes a little bit impatient. This is something that should be accelerated.

I have been using UiPath for almost four years.

UiPath is a stable solution. One of the reasons we left the Foxtrot solution was that it was unstable. If we had the same process running 10 times, we could get three different results. But with UiPath, we have never had any issues regarding stability.

It's scalable.

We have discussions sometimes with people from UiPath about solutions and things that we have done already. That is working quite well. The support is very good.

We participate quite frequently in UiPath webinars, especially when they are presenting new versions or components or pricing models for the software, so that we keep everybody up to date on the latest developments. They develop things very quickly. It's difficult to keep up with the speed at which they are developing new solutions.

Positive

It is very straightforward to implement. The setting up of a license is something that is done within an hour. It's the development that takes more time. Most of our clients are large, multinational companies.

UiPath itself does not require any maintenance, but solution maintenance is required if something changes for one of our clients.

Everybody is afraid of the licensing fees in the beginning, and because we are in Romania where salaries are still significantly lower than in Western Europe, that means that licensing fees have a bigger impact on costs for the company. But we are also working more and more for companies outside of Romania, where that is less of an issue.

When we come up with an offer in which the licensing fees are getting a little bigger, clients are more reluctant. That is another reason that we prefer to start with something a bit smaller until they get acquainted with the solution and see the advantages.

We looked at other solutions. We started with something called Foxtrot RPA, which didn't work well at all. We also compared UiPath with Automation Anywhere. But UiPath offers a better variety of possibilities, it's more flexible, and it's very easy to program if you are a developer and know other programming languages. UiPath offers StudioX for people who do not have any experience with development, but it's still a little too complicated.

We are not using a lot of the abilities that UiPath offers. We have made some attempts to use Document Understanding and we would very much like to do project mining, but we haven't had a client that is interested in that yet.

I would recommend that you start by implementing a small, standalone process, something that is not part of a big process. Automate that small process first to get used to how it works and see what can be done with RPA in general. And only then start with more complex processes. The latter take more time to develop, and clients don't like to wait.