UiPath Platform Reviews

We use UiPath to make processes. In addition to UiPath Studio, the platform that develops processes, UiPath includes other applications like Orchestrator, AI Center, Test Suite, Action Center, etc. 

I had the opportunity to work with UiPath Studio to develop and deliver processes to clients and scheduled them in production using the Orchestrator. I had the chance to automate many platforms in Excel, emails, et cetera. I developed around 20 processes.

I work with many medium-sized and large enterprises and a few small ones. Typically, the clients send us their PCs, and we work on their infrastructure. My clients usually have many departments, and all of them use UiPath. I use Orchestrator in the cloud, but clients, like banks, prefer the on-prem version because of security constraints. For me, there is no significant difference between the Orchestrator in the cloud and on-prem. We can schedule and maintain robots. They have essential common functionalities.

I work with many clients who recognize the impact and return on investment from using UiPath to develop automated processes. We always use the UiPath Academy courses. You can get a certification, and when we have questions that can't be answered on the forum or YouTube, we return to the courses. The courses are a way for the developers to understand the nuances of the product or do some workshops. The Academy combines theory and practice for each application, and in the end, we get a certificate. 

The AI Center can optimize many hours and lines of code. You can train your data on the Orchestrator in place with patent code, which takes more time. I compared the custom AI model and UiPath's presets, and we saved many hours. For example, my client had a difficult process that took lots of time to develop with Python and integrate into UiPath Studio. At first, they decided not to create this process with UiPath, but ultimately, they could develop it using Document Understanding with OCR and AI Center.

UiPath cuts down on human error and has included many updates in the latest release to reduce errors. Generally, our robots are rules-based so that we can see an important reduction in human errors. Automation generally speeds up tasks by about 50% because a person can control the robots in place to do all the jobs that robots do.

The amount of employee time saved depends on the bot. For example, if the robot is scheduled daily, and the task takes three hours, it frees up three hours. It depends on the complexity of the job and the time an employee spends on it. 

Enterprise clients can potentially save millions of dollars or euros per month. It depends on the client and the complexity of the process. We have a center of excellence that develops around 100 processes in large organizations. Smaller enterprises save a little bit less. In terms of cost savings, it's about 60 percent.

UiPath has a large user community that shares information. We can help each other find solutions, and the community publishes custom open-source libraries to help other UiPath developers. Members of the community also organize many events. Throughout the year, people from UiPath present new products and updates to the community, and community members help educate us about the latest features and how to use them in our existing robots.

I like the structure of the selectors. They're robust. With other software like Automation Anywhere, we always have problems with recorders, plugins, et cetera. UiPath is more powerful and efficient. UiPath Studio has features like the Excel package, selectors, and recorders. 

There are also many types of recording features. UiPath Studio's most interesting feature is the REFramework. UiPath's frameworks help developers handle exceptions efficiently.

Another critical feature of UiPath is end-to-end automation, starting with the design part of the process with many applications like Automation Hub, Task Capture, and Task Mining. We can use Task Capture in the community version, and they help with the design and conception of products at the start of the project. 

Then, we can use UiPath Studio, UiPath StudioX, or UiPath Web to develop the process. Afterward, we can use Orchestrator to schedule and maintain our developed processes. Finally, we have other products that can help us integrate business end users, such as UiPath Insights or UiPath Apps. With UiPath, we can assist automation in many industries or areas of applications.

I used the Document Understanding feature and developed a custom model to use in the community version. I had the opportunity to test the AI Center. The AI Center can make our robotic process classic RPA. 

AI Center allows us to evaluate and add intelligence to our classic RPA developers. We can add our custom classification model with drag-and-drop functionality in UiPath Studio. I like the integration between AI Center and UiPath Studio. Many of our clients are mature in RPA and want to use the AI Center or integrate artificial intelligence into their IT code.

The reporting part of Orchestrator could be improved. For example, UiPath could automatically email us if there are errors. Adding this feature would help us.

I have used UiPath for three years.

UiPath is stable. 

UiPath is scalable.

I rate UiPath support eight out of 10. They're available when you need them, and you can schedule meetings with them, too.

Positive

I also use Automation Anywhere for other clients, but I prefer UiPath because of the robust selectors and AI elements. UiPath can handle exceptions better, whereas Automation Anywhere lacks REFrameworks, which helps us handle exceptions. It's more difficult. 

UiPath has end-to-end automation, with a suite of other products that help us digitize internal and enterprise processes. UiPath has other advantages, like the community and the forum. 

Deploying UiPath is easy. It takes about 20 minutes or less to get UiPath running. You find the AI and download the latest version, then you start. The newest version is connected directly with the Orchestrator. 

One person can usually install it by themselves, but it depends on the number of computers. If you install it on one computer, that takes 30 minutes, but if we have more, you might need more people and more time. After deployment, UiPath requires some maintenance. The number of people necessary varies. For example, in some sectors, we have a team for maintenance and one for development, but developers might maintain their own processes in some instances.  

I don't have hard numbers on hand, but our clients generally see a 50-60% ROI. 

The UiPath license is a little expensive, but we get a lot of good features for the price. 

I rate UiPath eight out of 10. UiPath is the leader. It's the best automation software I've used. UiPath has rich documentation and a large user community. Developers can always find help in the forum. UiPath is a robust software solution that yields a high return on investment.

I recommend first trying UiPath Studio and UiPath products in general to experience all the features. Sometimes, we don't realize all the available features to help us solve our problems.

We use it for admissions policy and also for other financial items such as 1099 reporting from the IRS and things of that nature. There are some manual refreshes of systems and Excel documents that we have automated.

It is currently deployed on-prem, but we are looking at the cloud option. We are using version 2019, which is probably one of the oldest ones. It's pretty old. We're looking from a perspective of whether we upgrade it before we move to the cloud or whether we move to the cloud and upgrade.

We have seen quite a bit of benefit. We used to hire temp staff labor in order to do our admission policy, and now, we don't have to hire them. That would be five part-time people that would come in seasonally. For three or four months, we would have five people just cranking away the admission work. We don't need that anymore because of automation.

There have been time and financial savings. On the other side of the house, some of them are attended bots. We've saved the organization about 140,000 clicks. People don't have to click 140,000 times anymore. As a small estimate, we saved the organization about 250 hours last year. If everything goes to plan, this year, we're looking to save about 450 hours from the financial side of the house. We're only scratching the surface of it, and there is always room to grow.

We're still working through it. We recently stood up our system developer space. We have about 16 processes. We're still new at it and still in the beginning phases. We're really looking forward to pushing that envelope. Currently, we have a hybrid of attended and unattended automations. It's about an even split.

The GUI is valuable, and it's extremely stable. I've had six or seven Studios open at the same time working on different things and nothing has crashed on it. It's very stable software.

I love the community. The community is awesome. That has been very helpful. It provides value in terms of just being able to bounce ideas and understand. Sometimes, I try to do one thing, and I just want to know how to do one thing, but that's where the community can help broaden and look at it from a different perspective.

They say that everybody can do it, but not everybody can do it. You need to have some form of technological understanding about it, and just because we can automate something doesn't mean we should automate something. That's where I think there's a marketing thing. I understand where they're going with it, but it's not necessarily how real life is in my perspective.

I am not looking for any additional features. I haven't even used all the features. I'm still learning the platform as it stands and figuring out what's still available. 

I have been using it since 2019.

From a system perspective, it's stable on my end. It just works. That's the best part about it. It just works.

Scalability gets a little bit sticky. That could be just because of where we sit in the organization, I don't manage that relationship of licenses. I only get so many licenses and I'm like, "Well, can I get more?" It's definitely a limiting factor, but I don't know if it's us limiting it from a cost perspective. 

I haven't had to use their support. I go to the UiPath community for most of my questions. 

We used Microsoft Power Automate. It was okay. I totally prefer UiPath.

I was involved in its initial setup. UiPath was not complex, but we, as an organization, made it complex. 

We used a partner AKOA that got bought out by Roboyo not too long ago. So, we did use a partner to implement it. In terms of whether it was smooth or not, it was okay. Our school made it hard.

Our experience with them was good and helpful. It was a good way to go through it. Now that we know more, I would've changed the engagement slightly to get a little bit more consulting in the sense of the COE, governance, and other similar things around it. That's because for the most part, getting the system up and running was relatively simple, but now, with the whole other pieces of it, we're starting to feel some of that effect. It's now about how do we look at it from a different angle.

We definitely have a return on investment in terms of hours and soft cost perspective. We are saving 250 hours and don't have to hire five temps. I can't give the metrics for ROI, but from a time savings perspective, ROI is definitely huge.

We did evaluate other options. We evaluated Automation Anywhere, Blue Prism, and UiPath. It was about a year-long evaluation period between all of them, and UiPath was clearly the winner. It was clearly out there as the leader in that space, and that's why we chose them. 

From our perspective, the GUI was really helpful and very different from the others. Automation Anywhere touted more of just invoicing, but we didn't want it for invoicing. We wanted it for multiple things. UiPath really showed the breadth of what you can expand across.

To someone evaluating UiPath, I would definitely advise finding a partner. Find a partner with whom you can partner and who understands the use cases of what you're trying to do and achieve from an organizational perspective. Without that, you're not going to get an ROI. 

I would also advise managing expectations. It's fairly easy to use, but it still requires technical abilities. Don't think that it's something that you can just plug and play and do whatever you want. It's not going to work that way. It's more about the person and the change in mindset. If a person is open to an automation mindset, RPA is a really cool function, and UiPath solves that particular mindset. Without it, it's an uphill battle. Even from our perspective, from an education side of the house, getting our educators to be okay with automation is tricky.

We haven't yet used UiPath's AI functionality. We are definitely looking into it to see how we can start taking advantage of the AI pieces of it and advance that side of the house. Currently, we are trying to change the automation mindset. I'm a big RPA evangelist in our organization, and I am trying to promote things like automation. People are on board with the thought of it but not necessarily on board with the action of it. So, we really have to understand their process when we get into their process, and some people are apprehensive to share that information. It's the other parts of the piece that we have to deal with.

We have used UiPath Academy courses. It was useful to know the use of the product, the use of the GUI, understand how things move and change, where the checkmark boxes you need to check are, and all other uses. Now with the new versioning, it looks like a more curated function. It's a lot nicer. Previously, UiPath Academy was just a bunch of courses, and you didn't know where to start. The curation for developers or users is going to help people navigate through the UiPath Academy.

Overall, I would rate UiPath a nine out of ten.

We mostly use it for unattended bots. We are a construction company. Our RPA team does more of the complex processes for users. We take high-end complex items, that are redundant, off of the users' hands, then we host it on our servers.

We have a bunch of unattended processes, about 284 processes.

RPA isn't necessarily taking away tasks from employees, but rather moving them from processing-type employees to analysts. For example, if we had billers doing a very redundant task, then we moved that to RPA. Then, the billers do more customer face-to-face work and analysis, e.g., solutions through Salesforce. So, we have those employees who were previously billers move up to better positions where they can do more analysis and human interaction.

The solution has reduced human error. We don't need to go back and fix stuff. Customer representation is also huge. Quality of work is one of our mission statements. Having that repetitive test always being 100% every single day, month, and quarter, and whenever we send specific invoices from our server support, has been really helpful. It increases that quality formation.

There are a lot of job positions that we never really thought that would get created. Freeing up those experienced employees from sitting down and processing a lot of stuff throughout the whole day and moving them up to customers, we started discovering new talents and skills, especially with the younger employees since you are basically freeing up their time to discover new skills that they weren't even aware of. You are investing in them, showing customers that you have a new generation of fine employees who can do a bunch of new skills out-of-the-box.

The orchestration is the most valuable feature, e.g., how stuff can be organized. This is in addition to the fact that we try to move stuff to an unattended base where there is no user interaction. We are moving more to 100% automation rather than putting a human in the loop.

The UiPath Academy is mostly used only by technology associates and power users in each department who show interest in RPA. The academy has improved on the onboarding system that we have for RPA. So, if we see potential with someone, whether it is interns, power users, or even IT professionals around our department, then the UiPath Academy is definitely a good way to go. It kind of eases up the onboarding when determining who is outstanding or could potentially join our RPA teams.

The biggest value of the UiPath Academy is the ease of use. A lot of different platforms can be too complex. The user-friendly platform definitely helps with the ease of its steps. 

While it is the best tool ever, we decided that the user interaction might not actually be the greatest thing ever. 

I have been using the solution for three years.

I am very happy with the stability of it. 

I wish that there might be a better, easier method of updating our platform, especially for on-prem. I believe most of their customers are cloud-based. So, they don't have to worry about updating their Studio versions or Orchestrator. Being on-prem, it can be difficult because we must reach out to have that version. We can't just plan on our own. We are always at least a six-month step back versus the current version.

We have been scaling it as much as we can, especially with how we are trying to scale how big our team is as well as trying to control that specific workspace and workforce that we have.

There are currently five developers using it.

There were a couple of times with the on-premises version that there were complications, since it is not on UiPath's cloud. We have had a lot of complications where we are dead in water. There were a couple of conditions where we weren't able to get someone up to speed on whatever. The support is not as quick to respond as we had hoped. 

We did talk to our account executives about this. It is definitely a work in progress. I know that they have recommended that we move to the cloud, but it is not attractive enough for us to see if it is actually worth moving to the cloud.

We have been with UiPath from the start. We used to have a lot of in-house C# libraries that we curated. RPA was like overpowered macros similar to what we already had. That is why we knew how to deal with it. 

The initial setup was straightforward. We did it through the on-premises by connecting our SQL database, etc. 

The deployment took around three hours.

The initial setup was with their tech support, and that was definitely great. After that, if we had any hiccups, that was where the complications happened.

The main focus was improving efficiency. Once you focus more on redundant paths, having a bot doing it over and over again, that eliminates human error every now and then. There is definitely a huge ROI in that. Our main focus was low-hanging fruit. By low hanging fruit, I mean the redundant processes that users are just annoyed by when they go in every day and have to do it. There has definitely been a huge ROI because we are trying to free up a lot of the project managers for construction to do more focused stuff there rather than job cost details.

We have probably saved the time of 10 full-time employees. For daily tasks, we are saving an average of four hours per employee.

It is one of those things where you pay for convenience. Pricing-wise, UiPath is definitely way more expensive than other solutions that we have seen, especially since we also have Microsoft Power Automate, which is one of the latest tools. UiPath is on the higher end, but it is one of those decisions, "Is it worth the investment? How much are you getting as an ROI?" That is usually how the conversation goes.

Back then, the main competitor was Automation Anywhere, who wasn't necessarily as user-friendly. The main idea was that UiPath was more user-friendly with more forums. It seems like there was a community for it. Whereas, Automation Anywhere was a bit more complex. 

We are using a bunch of other tools to also see the differences. Everything runs so quickly that technology always needs to be up to speed. Companies, like UiPath, are always running so fast to compete in this area. We are also trying to see who is actually the best. UiPath has definitely shown us that, but it also comes with its price.

They are always trying to look for, as much as possible, in-house creation of back-end processes. This means less clicking and tapping on the keyboard for the robot, which is always better. UiPath definitely blends all that together, which is great. It is literally bridging all our platforms together, which is what I love about it.

With UiPath and RPA, the sky's the limit. There is potential for a bunch of things that you can do. When we started, as a construction company, we were thinking that RPA might not be as useful as we might think and make a bigger difference than our in-house solutions. When RPA came out, we thought it was mostly for companies like EY and PWC, e.g., more for financial auditing since there is so much data. However, we definitely benefit from it as a construction company. There is so much potential, whether it is low-hanging fruit or high complexity. It is definitely a win-win for any company, whatever industry you are working in.

I would rate UiPath as eight out of 10.

My use cases for UiPath Platform involve starting with simple robots, as I saw in my company that I need to handle many paychecks. First, we scan the paycheck and the robot does the job in our system and sends emails of notifications that these paychecks are entered correctly in our system. From that, we started complex robots where some interact with two software systems: our system and another program that does the work orders, leading us to develop a robot that helps the technical team in our company by synchronizing the work orders.

What I appreciate most about UiPath Platform is the Use Application feature, which is new and helps with interacting with programs and websites more easily, a convenience we did not have in the past.

The downsides of UiPath Platform include that running an Orchestrator is a bit complicated. I implemented it but did not do it more because it requires money, and here, we do not have sufficient funds to buy some features. I would request a new feature that can interact with emails more easily in the future.

I have been using UiPath Platform in my career since 2020.

Regarding stability, I do not see lagging or crashing in UiPath Platform very often. I have seen this a couple of times, but it is not frequent.

In terms of scalability, I think UiPath Platform is good and performs adequately.

There is a website for UiPath Platform where I can ask questions about implementation, but I have not contacted the team directly.

Positive

The initial installation of UiPath Platform is easy. It took me about three, four, or five minutes to set it up for the first time; it is not complicated.

Regarding the pricing of UiPath Platform, I wish for a lower price here in North Africa. When I speak with my boss about prices, he blocks me, saying there is no way to buy and to just use the community license. While I see many features in videos and want to learn, videos do not allow for practice. It gives you two months, and although I tried to get the certification and watched some videos, I could not practice because it requires payment.

UiPath Platform requires updates, especially when there are functions that do not run, so we perform updates, particularly on the very old robots.

On a scale from one to ten, with ten being the best, I would rate UiPath Platform a nine for everything.

For two years, I have focused on automating workflows related to processing documents in formats like PDF, Excel, and CSV. Using the document understanding feature, we have handled forecast orders and purchase order invoices. 

If you use input files like Excel, PDF, and CSV, we can automate file validation, such as checking data accuracy, format compliance, or missing information. It's integrated with Boomi, so after the files are validated, they're sent to Boomi for further processing. 

Boomi provides us with the RTF file, and we use UiPath to validate its contents and correctness. It automates the process of converting the RTF file into an Excel file. Another process is remittance, where we can get files from clients, validate them, and submit them to the credit managers for correction.

UiPath reduces human error by eliminating manual work and intervention. Some human intervention is still necessary, but it has been reduced. Realizing UiPath's benefits takes some time because you may have some issues after the initial deployment. The UiPath Academy was helpful. I took some courses and achieved developer certificates. I'm still learning. 

It hasn't saved time in my work because I'm still spending a lot of time learning the software. It was new, so learning and implementing those things in my work takes time.

My favorite feature is Document Understanding. I haven't used most of the new features, such as AI-enhanced document processing and process mining. The document understanding feature is especially valuable because I can use it to extract and process invoice data efficiently. It enables the quick and accurate handling of structured and unstructured data. 

The flexibility to work with templates and machine learning models for document extraction has been helpful when dealing with various invoice formats and forecast orders. Data extraction from PDF has been smooth, especially with UiPath's capability to handle scanned documents using OCR and AI-based models. 

The taxonomy manager lets you define the structure and categorize data from multiple document types. AI center integration allows continuous improvement in document extraction accuracy by training models based on historical data. I have utilized AI and machine learning models in UiPath specifically for processing complex PDF and Excel documents. 

UiPath's AI capabilities, such as pre-trained invoices and receipts models, have effectively extracted structured and unstructured documents. For example, when processing purchase orders, the AI model identified key fields, such as invoice numbers, dates, line items, and currency details, with high accuracy. I have found the machine learning models to be especially useful when working with documents that have different formats. In some cases, additional training or validation was required to fine-tune the models for complex or irregular documents. Overall, AI models and document understanding are my favorite features.

UiPath is highly user-friendly because it has drag-and-drop functionality to design and develop complex workflows without much coding knowledge. This has been particularly beneficial when working with different document formats. UiPath's built-in tools and integration capabilities simplify the automation process, leading to greater efficiency.

We have end-to-end automation and integration with other applications. For example, we have portal automation that's end-to-end. We use it to log in to the website and sign in to different accounts. It enters the CAPTCHA, downloads the files, and logs out. It can complete the automation without human intervention. 

UiPath has many resources online. We use its academy and online documentation. If we face any challenges, we can find an answer on the forum or one of these resources. I've never had a problem finding solutions to problems. They have the best resources.

I would love more integration with Third-Party applications. Expanding the library of pre-built, plug-and-play connectors to include more industry-specific applications.

I have worked with UiPath for two years. 

I've never experienced lagging or crashing with UiPath. The app has never given me trouble. 

Installing the community version of UiPath was easy and only took five to ten minutes. 

I am using the free community version. The enterprise version is obviously a little expensive. 

I am a consultant working on RPA solutions in general. UiPath is one of the solutions that I am using.

The use cases depend on the clients. I have done automation of sending mail with invoices in it. We have used it for analyzing PDF documents, getting information out of these documents, preparing in three different languages depending on the client, and sending invoices by email.

We are also checking VAT numbers on the EU side to validate the client's VAT numbers and related data. We have automated the generation of reports out of SAP for two different managers and teams. We have also automated including specific signature images within PDF documents and sending them to the related service or email address.

We have mainly used UiPath to focus on processes related to the finance department. The targeted processes are the ones that are the most repeatable and require a lot of effort but there is no real focus and attention from the user. Because of its repeatable nature, the risk is that users do not pay attention to the process itself and make mistakes.

Generally, we do not implement end-to-end automation. The idea is not to automate an end-to-end process but to automate a part of the process that takes a lot of time and resources. That is the focus point, so it is not a matter of having an end-to-end process implemented. It may occur, but often, it is a part of the process where the focus needs to be reliability or time and resource consumption.

The benefit for our clients is time and reliability. They quite often see the benefits in terms of the reliability of executing the process, even reporting mistakes or errors that happen during the execution of the process. That is something quite valuable for them.

Usually, it takes our clients at least one month to realize the benefits. If the processes are executed on a daily basis, then it is quite fast, but there are processes that are triggered every month or every quarter. In that case, it will take at least a month or a quarter to see the benefits. Once it is executed, there is quite an immediate benefit. On the other hand, it takes time to analyze the process because often processes or procedures that are written are not in sync with what is executed by the user. We have to modify them. Often, by questioning the end user, you end up finding the shortcuts and implementing them, so the analysis takes more time, and the implementation takes less time.

UiPath reduces human error. That is one of the main reasons why automation is done for customers. Two main reasons for automation are reliability and resource availability. 

UiPath saves time for our customers, but it is hard to know how much time it has saved because it varies from process to process. For example, the process of validating the VAT numbers on the EU website used to take two or three resources every quarter, whereas now, it is reduced to less than half an hour. These time savings are valuable, but the added value is reliability.

UiPath has not had a lot of impact on the digital transformation because the processes that are requested to be automated are already digital. The reason for automation is to speed up the process or make it more reliable. There is no real impact on the digitization of processes.

In terms of the reduction in the on-premises footprint, I am not always aware of the eventual use of the processes that I am implementing for the clients with the bots. I see that some of the bots are not used anymore because they have their own application that includes a big part of what has been automated on their side. It depends on the way they use it and how often they use it because I have bots that are running every day, and I also have bots that are running once a quarter. The ones that are running every quarter are harder to evaluate because people are not always able to see the resources released from executing those processes. Because they are executed every quarter, they are usually not measured. Our clients generally go for automation for reliability.

Specifically in the recent versions, the ability to change the interface is valuable. One of my clients had to upgrade the SAP version and move to a web-based UI. This was handled by isolating the UI interaction within the library for the targeted SAP on the client side. I upgraded that library to handle the web-based, and the bots worked fine after that without modifying anything in them. The usage of libraries is very important for me because it helps a lot in this kind of upgrade, specifically because SAP is used across the company. It is impacting a lot of different businesses within the company.

It is quite intuitive and fully handled by a visual interface. It is no big deal for me. I have been a developer in the past, and I have used Visual Basic and C#. If I need to specify something exceptional, it can be done. It is not a big deal. For me, it is very easy. There is a competitor with an open-source solution called OpenRPA, but for me, UiPath is far better and more intuitive.

There should be the ability to customize the building blocks instead of having to specify everything in every step. We should be able to combine these building blocks to make specific processes faster.

There should also be some kind of templates, similar to Power Automate. Power Automate provides templates for a specific context.

I have been using UiPath for two and a half years.

I am absolutely satisfied with its stability.

I did not have to worry about it so much because usually, my clients want to take control of their bots. They want to execute it when they want, so I have had no experience with the scalability of UiPath. 

I have not contacted their support. When I am developing, I try to make a bot quite stable. I am aware of what is happening and what it is doing, and I can notify people with logs or names of different events that are occurring during the process execution. I know exactly what is happening and where. It is quite easy and fast to diagnose and fix if there is an issue, but it is not often that I have to intervene in production. If a process is designed correctly and safely, not much intervention is required. Clients look for this kind of stability because that will save the time that they will have to spend fixing things in the production environment.

They have a UiPath Community, but I have not used it often. If there is something blocking, I go over there, but generally, I find the solution to the issues through my colleagues.

It has always been on-premises. The setup is quite straightforward. If there is some kind of Orchestrator to be installed, it is more difficult, and it takes more time. Usually, they want to have someone internally to handle the Orchestrator. I am more focused on the bots and the triggers for these bots to be executed. I am not that often involved in the implementation of the infrastructure of UiPath for the operational side.

Bot development duration varies. It depends on the process, but it can take a few weeks to several months. I have bots that were developed in two or three weeks, and I also have bots that took at least six months because they were quite heavy and complex. Generally, it does not take longer than that because then it will not be as valuable to the clients. If it takes more than six months, it is better to have it developed in their own software.

Bot deployment is quite straightforward for most of my clients because, during development time, I take care of environment parameters. So, deployment is quite straightforward. It is a matter of deploying and pressing a button to have the package deployed. We then set parameters in config files, but it does not take a long time to have it deployed.

Bots usually do not require any maintenance, but if the source of data has been upgraded or modified or the UI has been modified, they might require some maintenance. Usually, once the process is running and every source is stable, there is no need for maintenance. When the data source changes or the infrastructure changes, such as the main server being moved or renamed, then there is a risk over there, but it is not a big deal to adapt.

Generally, two or three people might have to investigate the cause of the issue. If the issue is inside the bot, it is not a problem. One person is enough. If it is related to external data sources or infrastructure, it may take two or three people depending on the segmentation of the clients' people in their departments and services.

I do not know about the exact price because I am not selling anything. I propose several solutions to the clients, and the client does choose one of them. If UiPath is chosen, they contact the official reseller in the country. In one case, I had the prices in front of me, and it was not expensive for the service it was providing.

I would recommend it depending on the needs. UiPath can do a lot of things, and I have covered only 20% of UiPath functionality. Based on my experience and the needs that I had so far, UiPath has been quite valuable.

I would advise defining your use cases. That is the rule for everything. Once you have the use cases analyzed, you can specify what is needed, how you would do it, and what is the best solution to have it implemented. One thing that I am doing is that I am mixing solutions, where, for example, UiPath interacts with Python processes that I have developed. Python processes provide information in files. Web scraping is not difficult in UiPath, but it is quite heavy. In Python, it is faster to develop and use than with UiPath. It also depends on the number of iterations and resources available to execute it. It is a matter of the quality of a particular functionality in UiPath. UiPath relies on the .Net framework, and it has its own limitations. It has quite a heavy set of libraries and frameworks. It is a matter of balancing what you are expecting of it.

I would rate UiPath an eight out of ten. It is a good product. It is well-designed and well-executed.

I find the solution easier to use than other platforms and it's a user-friendly way to automate.

I work with Excel files, and I find it helps make it easier to work with the files.

The ease of building automation is okay. I just use the community version, however, I have found it's much better than others. Their community version is more user-friendly than many options. I really appreciate the useability of document processing. I mostly use the solution for document processing and invoice comparisons. It's simple. 

I've used the user community and have been in touch with one person who was very helpful. They've helped guide me. I've gotten positive responses and good answers. It's helped me learn how to do comparisons between two Excel files, for example. 

I've enrolled in UiPath Academy courses. I've also enrolled in Coursera courses. I'm still in the learning process. They have good tutorials.

I've used some of the AI processes. It is very efficient to use the AI functionality. We've gotten very good responses and results so far. We have found the responses we're getting are good. It helps with creating more efficiencies. 

It has helped speed up digital transformation. 

UiPath has helped to reduce human error. We're able to build effective automation. We're creating software boards where the bot will do what we say and pull what we are trying to pull.

The solution does help us save time.

I'm still learning the solution; it has yet to help me save money.

I'm not sure how UiPath is at data scanning. I need to look into this further.

They need to work on security.

I have used the solution for about one month.

I haven't faced any stability difficulties, at least on the community version. 

I've never contacted technical support.

I've used Power Automate and ElectroNeek. I found there were a lot of issues with ElectroNeek and Power Automate. For example, they are not good with ChatGPT or data scraping. They are also not as user-friendly.

The solution was very easy to set up.

The implementation took only ten to 15 minutes. It was my first attempt to set it up. Aside from an internet issue, I had no problems. 

I handled the initial setup myself. 

I don't have any insights into the pricing of the solution. I'm using the community version. If I like it, I will buy the paid version.

I'm an RPA developer who started working with the solution. I recently worked with Power Automate. I'm familiar with the UiPath community version. I'm not extremely familiar with UiPath as I haven't used it for very long.

I'd rate the solution nine out of ten - at least, for the community version. 

We use it for various purposes like account management, finance, HR, and procurement.

We can complete all tasks within a single, unified platform. Whether it's documentation or deliveries, there's no need for multiple tools—it's all streamlined and straightforward. There's been a decrease in human errors which means we can skip the manual revalidation process. It's remarkably efficient, freeing up more than fifty percent of employees' time.

The standout features are data scraping and data analysis. It enables us to implement automation seamlessly from start to finish. It is user-friendly and significantly speeds up the development process.

The primary concern revolves around the high costs of licensing. It would be beneficial for them to develop plans or packages, especially for countries where people are more budget-conscious. Adjusting the pricing strategy could make the platform more accessible to a broader audience. It would be beneficial if there were options to extend the data storage period, coupled with dashboard views and analytic features for a more comprehensive and streamlined experience.

I have been working with it for seven years.

I would rate its stability capabilities eight out of ten.

Scalability is a strong suit; it can effortlessly expand its capacity and functionality to meet specific needs.

Support is somewhat dependent on the presence of a distributor in our region. Dealing with issues often involves going through video communication numerous times. The current setup, due to security reasons, makes troubleshooting challenging without direct access. Having direct access to support through the account holder would make things more convenient. I would rate it four out of ten.

Neutral

We utilized Automation Anywhere, Blue Prism, and similar options before settling on UiPath. Initially, the prices were acceptable, but lately, they've hiked up.

The initial setup might seem complex at first, but once you get used to it, it becomes more manageable and straightforward.

The deployment time varies, usually taking half a day to two or three hours, contingent on the infrastructure. Maintenance typically requires only one person.

It is quite an expensive solution.

We transitioned from WorkFusion to UiPath due to the superior functionalities offered by UiPath.

It's crucial to evaluate not only the technological aspects but also the pricing structure when choosing a platform. Overall, I would rate it eight out of ten.