My use case involves using the UiPath Studio and the Orchestrator the most, but I also use the document understanding from UiPath Platform, as well as the UiPath AI Center and UiPath Insight.

The best features of UiPath Platform include the UiPath Studio itself, which is the most used tool from UiPath Platform. It also has other features that make a lot of sense, such as the UiPath Orchestrator and the new feature, the UiPath Agent Builder, which was released two months ago. I believe that's the future of automation, and UiPath Platform encourages users to learn and build new AI agents from these tools. The deployment is easy; it can be implemented in new ways within a week.

In UiPath Platform, I see room for improvement in document understanding, which I feel is a bit old-fashioned because building capabilities with various documents and layouts requires excessive time for training and classification of documents; however, other areas of UiPath Platform have perfect solutions.

I have been using the UiPath Platform for four years.

I would rate the stability of UiPath Platform as a nine because it's an excellent product and a very good tool to work with, despite the need for some improvements in certain features.

I would assess the scalability as very high, giving it a nine on a scale from one to ten.

The technical support, especially when contracted on a large scale with a technical account manager, would rate as a nine or ten, and even without large-scale contracts, support remains around eight and a half to nine.

I believe the development of a project can save about twenty to fifty percent of the normal time needed, which is usually around one month to one and a half months.

Approximately, we have forty developers using the UiPath Platform.

I would recommend the UiPath Platform to other users because it is a complete solution and a full ecosystem of automation that connects all parts seamlessly. The pricing remains the weakest aspect, as it is the highest in the market. Although the offerings may justify the cost, the pricing is still very high. I would rate the solution overall as a nine.

My current use cases for the UiPath Platform include web development, web automation, desktop automations, and using document understanding, along with PDF automation using document understanding.

The most favorite feature in the UiPath Platform is the document understanding, and I appreciate the ability to automate the web part when applications do not have API access. The document understanding feature is based on ML technology, which extracts fields from a PDF document even when they are semi-structured or unstructured, based on the training models.

I use the UiPath Platform overall, including UiPath Studio and everything associated with it. Knowledge without scripting helps my colleagues who do not have any experience with scripting, as the UiPath Platform allows basic automation without requiring such knowledge. For some complex automations, we can integrate with VBScript and Python scripts if necessary, however, initial automation does not require in-depth programming knowledge.

There is scope for improvement in the UiPath Platform, particularly with the Web Studio feature that has been launched recently. They could enhance the object repository feature, which allows maintaining selectors externally, as there are challenges associated with changes in selectors that require updating the library and the version in the code. The Web Studio works when there are APIs involved, but it could be made more user-friendly and developer-friendly. It currently works only in cases where it is not dependent on a machine.

My total experience with the UiPath Platform is around 4.5 years.

Crashing from the tool end is very rare; only during upgrades might some issues arise. Overall, the occurrence is minimal. Proper exception handling in the code also ensures a low exception rate.

For technical support, I would rate it around eight or seven out of ten, mostly leaning towards seven plus. Most of the time, when we reach out, we have calls with the UiPath team, and we usually end up finding the solution or alternative methods.

I have used Power Automate as well. In Power Automate, it's easy to integrate with all Microsoft applications because it has direct integrations where all you need to do is change the URLs and authentication part, making it very simple to integrate with SharePoint or any Microsoft product. I also have basic insights into Automation Anywhere.

The initial deployment using the UiPath Platform was actually easy. Everything is organized in UiPath, and there is a forum available for support where users can post questions and get replies. The courses are also well-structured, making it easy for beginners to understand.

I took around two weeks to learn the basics of UiPath automation since I come from a CSE background.

The number of people required for this type of deployment depends on the timelines and project length. A basic UiPath bot would typically require one person for development.

I don't have any insights into the licensing at the enterprise level.

When considering alternatives to the UiPath Platform, options we looked into include any scripting language or similar solutions.

I have used the AI integration features of the UiPath Platform, specifically the integration concept with the LLM model where we provide a prompt to get results that we extract and send over email. This is typically used to analyze resumes for our HR team, which receives numerous resumes. Using the AI integration concept in the UiPath Platform, we read resumes uploaded to the LLM model, extract relevant data, and filter out the necessary resumes.

I rate the UiPath Platform a nine out of ten, based on my experience compared to Power Automate and basic knowledge of Automation Anywhere. I've found UiPath to be well-organized and well-structured for beginners.

Clients usually use UiPath Platform for the automation of use cases in departments like HR, Finance, and IT support.

UiPath Platform can handle very complex processes. We have implemented various complex use cases using UiPath, and they are performing very well.

UiPath Platform integrates with several systems, whether they are ERP systems such as Oracle or SAP, as well as other systems.

UiPath Platform utilizes AI features. They recently released a new platform called Agentic Automation, which exposes AI and RPA in one platform, making it something fresh and new.

The most important features of the UiPath Platform are the UI automation capabilities and Document Understanding.

UiPath Platform is doing a good job with enhancements; they are releasing new features almost every six months. However, I would recommend that they improve their ability to be a low-code, no-code platform, as this would be a great feature for their platform.

I have been working with UiPath Platform for about six years.

I would rate UiPath Platform's support a seven out of ten. They need to work on improving their response time for open tickets and handling complex support cases, as I have seen some cases take a very long time to troubleshoot and get to the source of the problems. Therefore, they need to improve their response time as well as increase the teams in their support team, especially when handling complex support cases.

Deploying UiPath Platform takes a couple of weeks.

The price of UiPath Platform in the Middle East region is a little bit high; having a lower price for the Middle East region would make it more attractive.

It suits big enterprise customers. However, if the customer is of medium to smaller size, UiPath Platform may not be a suitable choice.

It is an expensive tool. When compared to competition, such as Microsoft's Power Automate platform or IBM Cloud Pak, UiPath is expensive. Both of them are much lower in terms of pricing than the UiPath Platform, so they need to consider this in the enterprise scheme.

I would rate UiPath Platform a nine out of ten.

The UiPath Platform is used to automate business processes, mainly task automation and process automation that requires manual repetitive tasks. It is similar to Blue Prism, with additional integration capabilities such as Salesforce, CRM, and a better ecosystem. It is a low code, no code development tool for rule-based process automation.

The UiPath Platform helps enable end-to-end automation, but it is not suitable for all processes. The product is designed for rule-based automation. The machine follows the same instructions every time to automate manual repetitive work. If your pathway changes, considering the difference between deterministic versus non-deterministic or stochastic automation, the UiPath Platform is more deterministic. It performs the same exact actions every time. If the work requires different paths each time with dynamic decision-making capabilities, you would need to look beyond the UiPath Platform or integrate it with AI agents.

Some of the most valuable features of the UiPath Platform are its ease of use. It is low code, no code, and they are the leader in RPA software. They have a head start in integrating agent automation into their framework. There is agent process automation, which is still yet to be proven, but they are making progress compared to other RPA providers who are not as advanced as the UiPath Platform in terms of their agent adoption.

The areas where the UiPath Platform could be improved are in how most companies are adopting agent-tech AI. We will have to monitor how they are integrating it with agent-tech AI. Based on the literature, the UiPath Platform is taking concrete action, as they released their agent-tech framework last week. It is very difficult, so we will need to assess that and see how the product evolves into the agent-tech feature API integration.

I have about two years of experience with the UiPath Platform.

I have dealt with the support and customer service at the UiPath Platform. They are very comparable. Blue Prism got acquired, but the UiPath Platform remains its own entity and is growing compared to its two main competitors, Blue Prism and Automation Anywhere.

The UiPath Platform has a strong user community. It is very adept and has extensive training available. The user community is mature, and users receive proper support from the community to complete their work.

At my previous company, we used Blue Prism extensively because it was our standard product. We evaluated the UiPath Platform but did not use it for any use case implementation. We used it only for comparison and analysis purposes. We had already decided to use one tool, so we never saw the value of adding another RPA tool within the organization.

The UiPath Platform helps reduce human error. When a task needs to be done by 10 people, those individuals might do things differently. If a human has to enter data, they may mistype or forget something. These tasks can be automated. It can be integrated with auto-correction and auto-population of the screens presented to the digital worker. Over time, as automation matures, errors can be fixed, ensuring consistency or improvement in work processes. Every transaction is processed with the same exact logic or steps configured, which helps bring consistency and reduces human errors over time.

The UiPath Platform saves costs for organizations, saving about 30 to 50% per business process. When comparing to manual processing, if 10 people were needed before automating the process with the UiPath Platform or Blue Prism, it can be reduced to three to four people per process, resulting in huge savings in manual effort.

The UiPath Platform speeds up digital transformation and reduces its cost. For simple processes that are well-defined and have significant manual effort, automation can be implemented, which reduces costs. Machines are more cost-effective than humans. From that perspective, it reduces the operational costs of business processes.

The main differences between Blue Prism and the UiPath Platform are that UiPath is easier to learn based on my research. There is abundant material available, and it has many out-of-the-box integrations, allowing for more operational capabilities. Blue Prism is solid but became stagnant around 2017-2018 when focus shifted toward the UiPath Platform. Blue Prism was once the leader, but since 2018, the UiPath Platform has improved. I haven't used the UiPath Platform extensively to provide a firsthand assessment, so my knowledge comes mainly from literature.

I do not use the agent-tech automation with any platforms. The agent-tech is a new feature within the UiPath Platform, and they started integrating it in the last six months. I have not seen their offering, but based on documentation, they have developed a framework for agent development and automation integration.

Regarding the ease of building automations using the UiPath Platform, end users still need some specialist skills to build. It is not as end-user friendly as some other tools, but it does not require deep technical knowledge. It is low code, no code, and everything is drag and drop. Configuration management using their studio is effective.

The UiPath Platform does not necessarily replace existing systems but connects to different systems already in place. It creates a layer on top that reduces the need for human intervention, enabling machines and robots to do most of the work.

The time saved due to the UiPath Platform depends on the employee. It reduces the workload for end users whose work is now performed by robots. The saved time can be used for other tasks. When processes have seasonal variance, such as quarterly, monthly, or year-end processing, the transaction volume increases, so workload can be better managed by adjusting digital workers.

I rate the UiPath Platform an eight out of ten.

My use case for their products is the regular automation use cases, and I am trying with some Gen AI use cases.

The most valuable functions in UiPath would be that it's easily integrated with multiple applications. The cost is annual. It's not based on transactions for the products.

It has good documentation that we can follow.

It's also easily built; you can do it with low-code/no-code, making it quite simple to build. Some coding experience is needed, however, if you are good at it, it's a good tool to use.

UiPath provides a scalable solution and well-secured. Since we are on SaaS, we have more flexibility, and because we know the products, we can evangelize about it. It's quite user-friendly, scalable, and secure, so that's good for us.

The solution helps reduce human error.

It saves employee time absolutely. When we automate manual or recurring tasks, employees have free time, so they are looking at picking up other creative tasks instead of doing redundant ones.

For UiPath maintenance, I give it ten out of ten.

We use the Academy for courses. I do use UiPath Academy courses; we study from that, however, learning doesn't stop.

The UiPath user community is fantastic. We get to learn a lot about various solutions, and gain access to a good knowledge base. There's nothing particularly special from an evangelization perspective. The MVPs do have access to product support, and from them, you can get most of the information coming out in the community. The community is quite engaging, and we do get to know each other a lot in terms of solutions.

There is a drawback that the new products getting launched are not well documented, and the information only sits with the product team, not with the support team. That is where they are falling apart.

They should focus on the customer needs as their license cost is currently quite large. Compared to Microsoft, their cost is too much for automation, and their support has not been up to the mark. The customer-centric focus has reduced; they're more towards licensing and getting new sales, new business. They cannot maintain the existing products once delivered.

Regarding additional functionality for UiPath, I believe that additional features will only come into play when you start talking to the customers, accept feedback, and work on it. I haven't experienced that, so honestly, my answer is negative. The product needs a lot of enhancements, and whenever we get a chance, we share feedback with the UiPath insider program.

I have been working with UiPath for almost five, six years now.

I'd rate stability ten out of ten.

In terms of scalability, I rate it ten out of ten.

Technical support is good. They should know more about the technicalities of the product. That can be lacking.

I don't use Automation Anywhere anymore. I moved to UiPath. I'm also familiar with Microsoft, which is cheaper.

The initial setup for UiPath was simple.

We have used a UiPath integrator.

In my opinion, if both UiPath and Automation Anywhere solutions are available for me to work with, Automation Anywhere is a history, and UiPath is a modern tool.

We do not yet use the agentic automation device? It is quite nascent. I don't know why people are falling for it. Agentic automation end-to-end still does not exist. It exists with big, big, big, big players like Salesforce. There are certain OpenAI tools which give you end-to-end big automation. What UiPath is giving as of now is agent building and now agentic, which is still in a preview mode. So it's not generally available.

The solution reads messages in real-time and predicts what could be the type of a message; that is what Comms Mining does.

Comms Mining doesn't prioritize the messages. Its job is to identify the emails, categorize them, and label them as per the training provided by humans. It categorizes unstructured data such as emails with the right type, helping the end user or downstream automation work on it. It can work on IT tickets, emails, chats, and so on.

We don't trust the monitoring capability of Comms Mining; it's not up to the mark. I'd rate it six out of ten. So, we have built our own Power BI dashboard, looking at logs from bots as well as Comms Mining, and we're doing our own analysis and insights. However, their training GUI is quite helpful since it tells you which labels are underperforming and which labels need action if the F1 score has decreased.

The solution enables me to implement end-to-end automation under certain conditions.

If I evaluate UiPath as a total product, I would give it an eight out of ten.

I have automated a few basic business workflows. They were simple automations.

In terms of complex workflows, generally, we have some kind of system to interact with over a browser. There are specific sites such as SAP or other HR applications that usually have browser UIs. Browser interactions are the best I have found with RPA solutions.

We have tested the Document Understanding feature, which seems promising. Although I haven't developed a proper workflow for that use case, it looks useful. The framework seems to help set up the development process without needing extensive programming knowledge.

We also use UiPath in our Microsoft environment, particularly for core applications such as Excel, Word, and Outlook. Excel activities are very useful, so it has become a core element of our workflows. As a developer, I enjoy using Visual Studio to create custom activities based on specific business workflow requirements.

There are also a few use cases for agentic automation. A core element is processing the source document, whether it's Microsoft Word, PDF, JSON, or XML. It parses the documents, retrieves required data, and pushes the data into a target system, such as a database or Excel table. The automation acts as an automated interface, moving data from a source system to a target system.

UiPath helps speed up digital transformation and ideally reduces associated costs. Though there are instances where the frequency of automation has decreased, impacting overall effectiveness, generally, our automations operate ten to hundreds of times faster than manual processing.

There's a notable reduction in human error. Partners are often surprised that the automated process doesn't make mistakes. While we can't predict all unexpected issues, business-related errors are virtually non-existent once a process is automated.

When considering specific features of UiPath that streamline operations, the management part of UiPath Orchestrator for unattended automation is helpful. The scheduling is very nice, easy, and simple to manage, allowing me to oversee workflows and their schedules effortlessly.

It saves time for the development team. The agentic automation from UiPath is user-friendly. It's definitely one of the stronger points. It's really easy to handle, even for someone who has never heard about RPA. It's generally simple. Once I install the system, I show them how to start and stop the processes, and that's basically all there is to it.

What I appreciate about UiPath is that, compared to the competitors, it has pretty much everything. There are so many out-of-the-box solutions that it's difficult to find a match. I have tried to compare it to free alternatives, and the difference is night and day.

It's simple to develop and use for developers and end-users as well, so I would say that's probably the most important aspect for us. The development time is very fast once a UiPath developer learns the basics of development. It usually takes a few days to automate a business process, which is mind-blowing compared to other options.

There is one major feature I feel is missing from UiPath. When someone starts an automation, there should be some notification window on the screen to provide information about the flow's status and progress. Currently, users can see if the flow is running and some basic information, but there's no core notification window that fully informs users. Incorporating such a feature would greatly enhance user experience.

I faced one issue with UiPath Studio where when automating a workflow takes several hours and the application remains open, it can consume an immense amount of memory, sometimes up to six gigabytes of RAM. Restarting UiPath Studio usually resolves this. I'm uncertain if this is a common issue or specific to my environment.

I usually use the UiPath Community, which is pretty much my primary resource. I occasionally explore the marketplace for specific activities that may already exist. However, I primarily rely on forums. Most of the time when I have a specific question, I find the proper answer there. About 90% of the time, I find relevant forum threads where someone has encountered the same issue or question.

I utilized the UiPath Academy heavily in the first two years, completing most developer-related lessons. It's challenging to keep track of all the lessons nowadays, so in recent times, my learning has shifted more towards forums and YouTube videos rather than strictly relying on the academy.

I haven't worked with any RPA product before UiPath. We did explore other options back in 2019 and compared various competitors when we had a project in 2023. However, my development experience has solely been with UiPath.

If our partner requires an on-prem RPA solution, we create a compact UiPath architecture. We have several partners with on-prem orchestrators and associated servers. It's really simple to assemble. I know because it took just a weekend to set up all the servers. If someone prefers cloud solutions, it's even easier since much of the configuration is pre-set. Overall, I would say that it's not difficult to develop an on-prem architecture.

On paper, I believe there are cost savings thanks to UiPath. However, I don't have access to exact conversion numbers. I can see saved time and reduced FTEs, but I can't specify how that translates into actual money. Some workflows don't pay off the license due to infrequency, but overall, I believe it does contribute positively.

I would definitely recommend UiPath, although the major concern is that it's not super cheap. Despite its higher price, I understand the complexity behind it since it's the most comprehensive RPA solution.

The cost can be a barrier in Hungary, making it difficult for me to persuade others to invest, especially when unattended robots come at a significant price point.

When we were trying to implement UiPath in our environment about four or five years ago, things were totally different than they are today. Many automation solutions didn't exist back then, making it challenging to get familiar with the product and its capabilities initially. Since then, the RPA ecosystem has expanded significantly. Document Understanding wasn't a feature in 2019 or 2020, but now, it is much improved.

We haven't really used the communication mining feature. I've checked it a few times, but we usually handle manual interviews with key users. As for task mining, I used it for documentation purposes when creating workflow documentation. It supports generating document templates, which is very useful for us, but we haven't used it for deeper automated workflow steps.

I would rate UiPath an eight out of ten.

I have worked on Adi FlexiCapture, and my reviews are good about it because the automation that I had to end up using is still running fine, the document is in proper format, and it works fine. For Microsoft, I have tried using Form Recognizer for some passport extraction, and at that point in time, the extraction was not good.

The solution speeds up digital transformation, but the cost is on the higher side.

The biggest benefits I have seen from the UiPath Academy include getting familiarized with whatever products they have, as whenever they release a product, they also release a course in the academy along with it. This helps users get familiarized with the tool and understand the capabilities of that particular solution they are putting forward.

The features I have found most valuable in UiPath are the robots, and now they have started implementing more in the intelligent automation space. This is a good step because the document understanding when it got added with Gentry T AI is working very well.

However, the Orchestrator setup and the licensing model are aspects I don't like, though their automation cloud is good.

The solution enables me to implement end-to-end automation, and I always do this, as any automation should be end-to-end.

The solution has reduced human error. The solution has freed up employee time.

An area where UiPath can be improved is the pricing. The licensing model is confusing.

I have almost seven years of experience working with UiPath now.

UiPath is not that stable. It has many issues sometimes. Sometimes selectors may not work properly, and I think UiPath should also have some models for when other applications apart from replication are supposed to automate it, as the automation trips. There should be some sort of mechanism to override that, and many efficiency issues are still there, which need to be addressed properly.

The scalability of my iPaaS is scalable enough, but the problem is that since the license cost is high and most of our solutions are deployed in Azure VMs, hosting Azure VM is also expensive. The customers are hesitant to invest in more bots or solutions.

I would rate technical support from UiPath around six or seven, as it is average. The importance of end-to-end automation is significant for me, and I always want it to be that way.

Before using UiPath, I was a Dartmouth developer, so it's more of a generic thing.

We are not very happy with how the pricing is, as most of the UiPath products are priced on the higher end compared to the competitors.

My relationship with the vendor is that my current company is a UiPath partner. We are a Diamond partner. We have used the vendors' UiPath Academy courses.

I cannot definitively state if this solution has saved costs for our organization, but most of the solutions are cost-effective as we did some automations for accounting in our old organization, and now most of the accounting staff are just doing monitoring rather than doing things manually.

I am uncertain about where we deployed in the cloud. We are not very happy with how the pricing is, as most of the UiPath products are priced on the higher end compared to the competitors.

Building automations using UiPath is much easier than using Power Automate or any other tools because I have most of my experience with UiPath, and they have tried to fine-tune the automation experience over time. It's much easier compared to other tools.

Minimizing my on-premises footprint is about migration to the cloud, and we are currently not using the on-premise version of UiPath. We have migrated to the cloud, and the migration process itself was very easy because they have a tool called the Cloud Migration Tool.

It has more capabilities and is much easier for us to maintain when migrated to the cloud because we don't have to update the orchestrator after every release.

The approximate number of end users in my organization of UiPath are more than twenty to thirty.

To someone evaluating this solution, I would say that it is good and it is a product that is evolving along with the current trend, looking into AI and moving into Accent Tech, so the future is still there.

On a scale of 1-10, I rate this solution a 6.5.

I am in consulting, and I implement UiPath for my clients across various use cases.

Immediate benefits include faster operation and the ability to run overnight, which clients value since the work is already completed when they start their day.

From my point of view, it is visual, making it easy to learn. It is super easy for me to learn and handle the automation, then replicate it, rather than using traditional code.

Everything is embedded. It is not only automation. It also includes document understanding and communications mining, with all add-ons in the same organization.

We use Agentic automation. It's very good at automating processes. We're still at an early stage. We have access to the alpha version. I like what it is doing, however, it is not production-ready yet. I see its potential. Initially, I started playing with it via demos only. I've built a few things I have shown to clients, although I have yet to use it.

We had a few use cases for Agentic. One use case was as an HR assistant, including providing invitations to candidates to say they are a fit for "x" roles and to set up interview times. Another use case was as a document extractor. I created an agent that could extract information from documents and provide a stable output and learn for itself. The third use case was for account payables, which is the one I've been demoing. I've created an agent that can read an invoice and provide recommendations, such as approving payments.

I have experience with UiPath's communication mining features. It can be used in real-time if you link it to a mailbox, for example. I don't see the power of linking to a mailbox. However, I see the power of using them to send an email and then get in return what the tool understands. I'm able to automate actions and responses. I have a demo on that. For example, I have an automation that scans the email, and it can tell what documentation the email is about. I can understand, for example, if the email or document is about a policy claim and then ask further questions or make further recommendations based on that.

It's fairly easy to build automation. I'd rate it overall a seven out of ten. It can get super-complex, however, it's fairly easy.

We can handle end-to-end automation for the most part. Now, with Agentic, it's easier, since you can connect automation. You just need to keep in mind there's a different approach.

I do use the UiPath forum. If I don't know something or if I'm facing an issue. Maybe someone has already faced it. 90% of the time, someone already has. I can ask questions and try to solve problems.

UiPath helps the team have less work. People, initially, when they use automation, fear they will lose their jobs. However, that's not the case. Now, people see that they can properly focus on other stuff. Their job isn't taken. They can focus elsewhere. Depending on the use case, UiPath has freed up 50% to 90% of a person's time.

The Academy is free, and there is a lot of content. For new joiners, they have to be certified, so for the first two to three weeks, we put them in full training mode.

Licensing needs improvement. Licensing in UiPath is a bit confusing. They are already working on that, however, from my perspective, it is what I feel least safe discussing because the product changes two or three times a year.

Additionally, it is confusing to understand the packages available, the number of packages, and updates with new versions. Therefore, from my perspective, licensing is an area for improvement.

The Agentic tool has a lot of noise. However, we have to get hands on to understand what the tool is capable of and what the tool is not capable of. That's one of the things that I am spending time with.

I have used all the platforms for five and a half years overall.

I have personally never experienced downtime. I'd rate stability nine out of ten.

Sclability is quite good, perhaps an eight out of ten. It depends on how the development is executed. If done properly, scaling is straightforward; otherwise, it can be challenging. However, the issue lies with the implementation, not the platform.

Every time I work with the official UiPath support, they are slow and might not have read my request thoroughly before responding, leading to incorrect answers.

If you know the right person, partner support can be good. I tend to not ask anything when I am trouble. The support in Australia is better for partners.

I have used Blue Prism at a beginner level and Automation Anywhere at a beginner level. As of now, I would not consider them competition. Blue Prism, for example, has not kept up with changes, and Automation Anywhere is making efforts, however, I am biased and would naturally choose UiPath. The main competitor would be Microsoft Power Automate.

Cloud deployment took me 15 minutes. A few years ago, most deployments were on-prem. Overall, the safe answer to fully deploy would be weeks, however, depending on the use case, it could be longer. The largest deployments I have done took four months due to complex automation. Typically, it takes three to four weeks, maximum.

We have around 500 UiPath specialists. Our clients are medium to enterprise.

The solution absolutely needs maintenance. If the applications change of something becomes unstable, you need to have maintenance to make changes. The same is true if a website updates, for example. It can affect an automation.

We are already undertaking this at the regional level, so if UiPath has any activity in Australia, they will reach out to me.

I do not have the numbers at hand, however, there is clearly a return on investment when the automations are done properly, which is hopefully every time we develop anything for production.

From my discussions with clients, they normally find it expensive. This expense is generally not in terms of the bot or developer license. It's rather when it comes to AI units. Enabling document understanding, communications mining, or agents is considered expensive.

I'd rate pricing seven out of ten, with ten being the most expensive.

We are UiPath partners.

The tool is already proven, so starting a proof of concept is a good idea. Users should create a POC that can scale. Automate steps one and two, for instance, so that you trust the tool and see what it can do. Then, quickly transition to phase one if phase zero was the initial step to see its scalability and impact on previously good information.

I'd provide an overall product rating of seven out of ten.

I initially used UiPath for repetitive and structured or mechanical types of automation. I was a software engineer, and I handled maintenance processes for applications, whether it involved starting up servers, generating reports, or conducting health checks. These repetitive operational maintenance tasks were handled with UiPath. It was a tool for creating workflows to handle such menial tasks.

Automation must be present in an organization. Without it, you are stuck with manual processes that require lots of manpower for menial tasks. Automation allows large companies to scale their services efficiently, focus on more strategic tasks, and serve their customers efficiently. Its benefits can be seen immediately after the deployment. Your staff does not have to do repetitive tasks anymore.

Communications mining happens at the intake part of an internal process. It helps to classify information coming from various channels, such as an email or a ticketing system. It is useful for triaging and actionable insights. You can action that using a downstream automation. It can help with any process, whether it is a finance, IT, HR, logistics, or healthcare process. They also have IXP which combines Communications Mining with Generative Extraction. Tone or sentiment analysis in documents helps with better redirection or triaging. It goes hand in hand with the capability to classify documents.

Communications mining can help save time for your resources. If about 80% of your incoming communication is related to order management, with automation, the return will be direct. There will be hard savings in terms of people needed to work on the order entry processes. Instead of ten resources, you might need just three resources. The savings depend on the use case or the volume of a particular use case.

A key strength of UiPath is that you can easily and quickly build automation. If you are familiar with UiPath, you can automate simple to medium processes in a few hours. If you do not have any technical background, you can get started with UiPath and be up and running in one week with the help of a foundational course. I had a colleague with a background in political science. He did the foundational course and was able to build a project on his own in just one to two weeks. He is now a successful technical project manager working with UiPath.

UiPath helps to reduce human errors if the process, requirements, and exceptions are properly defined and the process is fully optimized before being automated. The ideal target is 100% accuracy, but that is usually not possible for most processes. About 90% or more accuracy is more realistic.

We have started to gather use cases where we can leverage agenting automation. It opens up more capabilities or coverage on the existing use cases as compared to before where we could only automate an end-to-end process to a limit. For example, we could only automate entering an invoice into a system using UI or API automation and downloading a report. With Intelligent Automation, they have added the capability to read from structured and unstructured documents and then classify the content.

Agentic automation now allows us to handle complex tasks like invoice dispute investigations, which wasn't possible with traditional RPA. Using UiPath Agent Builder and Agentic Orchestration, we can automate and manage end-to-end processes across applications and provide meaningful resolutions. This makes workflows more dynamic and flexible compared to rigid, structured automation.

From the early days, UiPath stood out because of its intuitive interface and ease of use, enabling the automation of complex processes without requiring technical knowledge related to development. UiPath has since expanded from simple automation to Intelligent Automation and Agentic Automation. The coverage of more complex use cases has increased, making it more robust. Processes not capable of automation five or six years back can now be automated easily. We can read from documents using Document Understanding or create complex workflows that require many decisions using agents. They are moving towards Agentic Automation.

The UiPath community offers a lot of value for sharing knowledge and networking. It helps you build knowledge and grow professionally within the same company or land your dream job in this space. Many large companies are using UiPath as the main automation tool.

UiPath Academy was my first point of entry when I started using UiPath. With its help, I was able to build my first robot. It has also helped me to be up to date with the latest and greatest features of UiPath.

Now that UiPath is moving towards BPMN as part of agentic orchestration on Maestro, there is a need to make it easier for newcomers in the BPMN space to understand the components of a BPMN workflow. More awareness is needed since even technically inclined individuals are not very familiar with BPMN.

I have probably used UiPath since 2017.

Our clients are large enterprises and small to medium businesses. We are both a partner and a customer. About 90% of our resources are working with UiPath. We are a small company with 200 to 300 employees.

Sometimes the technical support team gets repetitive with the questions they ask, and for complex issues, it drags on too long.

Some of our customers are on-prem, and some of them are on the cloud.

If you are on the cloud, you do not need to worry about deployment. On-premise, it is similar to other software where you need to provision an infrastructure, either AWS or any of the hyperscalers. It might require more steps and effort, but it is doable.

For complex cases, it could take an average of three months. Simple ones can take less than a month.

In terms of maintenance, any solution requires some sort of support and maintenance.

UiPath Autopilot saves 20% of my time. Most of my time goes into building projects for customers and not for personal productivity. The only automations that I leverage are the prebuilt ones for my personal use, such as UiPath Autopilot.

There is always an opportunity to improve. They have been trying to improve pricing by consolidating some of these SKUs together. They are trying to bundle more capabilities with the same set of licenses, which is good. However, because things are always changing, it leads to some confusion. They can make it more streamlined and consistent.

Compared to Blue Prism and Automation Anywhere, UiPath is more user-friendly and constantly innovating to lead in agentic capabilities.

Overall, I would rate UiPath an eight out of ten.