We're focusing heavily on document understanding processes. We use it to extract invoices, data tables from PDFs, budget, and PITBULL automation that's heavily focused on UI navigation and PDF manipulation. That's our main focus at the moment.

We've had a few calls with UiPath where they've shown demos on how they use the AI Center, but we've yet to find something that we can look in and see because we are a financial institution. We want to trust AI. We need to build our confidence in that before we actually implement it. It's at an experimental stage for us.

It started off as optimizing redundant processes to make sure that we enhance department abilities. We moved into the research sphere last year, where we focused on taking large datasets and throwing them up into data tables, and getting that data from PDFs or web pages. We started using data extraction and table extraction, and that's what drove our projects from that point.

Document Understanding is a key feature for us. We find that really useful because the OCR technology, the RedJack extraction that it uses, is easy to implement with a very level structure involved, even for unstructured PDFs and structured PDFs.

We mainly use Studio and Action Center.

In some cases, we use Task Capture to build outflows.

We started off as pure RPA, focusing on building out a citizen developer program with low code person-by-person automation that users can trigger by themselves. That then evolved into unattended automation. We started looking into document understanding processes and trying to get involved with the AI Center as well.

From the start of the citizen developer program, it went really successfully. We moved into the unattended sphere, and we're looking into big data.

The document understanding has room for improvement. The handwritten documents need to be optimized further on the OCR extraction, making sure that we extract accuracy above 80% because we do see a lot of failure rates when it comes to handwritten documents. There's a lot of room for improvement there.

UiPath has referred to the fact that they are still building upon OCR and document understanding. But with the use of Generative AI, we're hoping to see improvements. We're hoping that might be something that we start later on.

I have been using UiPath for four years.

The stability of UiPath really depends on who builds the automation.

However, the latest version releases, such as 2023.4.4, have been known to contain bugs. For example, we recently upgraded to 2023.4.4 and faced a lot of studio bugs, which forced us to downgrade to 2023.4.2.

The upgrades on other orchestrators were fine, but there was a bit of a change to the UI that took some time to get used to.

Upon their version releases, there should be a bit more due diligence before they are pushed to customers because almost every time we're given the opportunity to upgrade, there are issues where we have to scale back, wait a while, and then upgrade again.

Scalability depends on the team. It depends on your vision, but UiPath definitely opened the doors for making sure that the framework is in place and that they are aligned with our vision so that they can help us in terms of scaling the automation to the degree that we want.

When we are looking to scale up the automation that we have, the customer support guys are very much on hand to give us the technical support that we require. UiPath's scalability is pretty enhanced.

When you buy the enterprise licenses at the tier that we're on, you're provided a technical or client manager, and we find that we can easily contact them.

We have a weekly call with our team, and any support question is rerouted through them because their portal can be a bit slow at times.

UiPath's endorsement of the community has helped drive the success of UiPath because no other RPA vendor really has the community of support that UiPath has. That's a big one for us.

UiPath does have a good community, but the support portal is probably something that they need to work on.

We use Power Automate as well. It is something that we try to marry with UiPath, especially when it comes to office app integration and things like that. Power Automate is simpler to use.

We previously had some free Prism automation, and then we decided to switch over to UiPath simply due to the fact that the cost savings were a lot better.

Orchestrator was a selling point for us because our control room is something that we would be very interested in in terms of monitoring insights and transactional items. That's why we switched over to UiPath.

We've tried to take both tools and get the best out of both worlds. Anything that any of our automated processes involve Microsoft Teams, SharePoint, Outlook, or anything like that, we tend to use Power Automate simply because of the ease of use.

We're using the local installation. Everything is localized to our premises. We have a lot of strict protocols, being a financial institution, so, we don't really want to open ourselves up to any sort of cloud orchestration.

We tried to utilize Automation Hub to predict our ROI. The reason that we're using automation is to assist teams rather than just kick the task away from them. It's just very robust.

We haven't seen any major cost savings, but we're an early team at Cowen. Maybe later on down the line, we'll get some solid figures.

The pricing is a bit convoluted. We have an overallocation of licenses at the moment. Citizen developer licenses are something that we probably need to refine.

They probably oversell it a bit to the point where we would propose that we may use x amount of licenses but in reality, we're probably only using a fraction of that.

There's room for improvement in how they sell their product.

I would rate the solution a ten out of ten. Out of all the RPA vendors that I've had access to, UiPath is the easiest to use. It's the most in-depth when it comes to being able to have automation and it works in the way that you want it to work. Other vendors like Automation Anywhere, Blue Prism, or Power Automate have rigid models. Some of them are web-based, which we don't really like because we're a financial institution, so we like local installations. UiPath tops them all.

For anyone looking to enter the world of automation, UiPath should be the first point to call. They have a much better idea of how to generate a productive automation team for companies.

We use UiPath for web scraping. We extract data from websites, store them in boxes, and analyze them later.

UiPath fails jobs sometimes and doesn't give you direct instructions on why it failed. A little more insight into failed jobs would be beneficial. It should have more documentation and short training modules.

I have been using the solution for a year.

UiPath is scalable.

The product's installation is easy.

Our business objective for AI automation included making our team members' time more efficient. We didn't want to spend an hour or a day manually downloading the data. We wanted to automate it and save time.

AI-powered automation has fundamentally changed our organization. We can get the data quickly and instantly anytime. It can be uploaded directly without needing someone to check it manually. A bot does it for us. It saves time, speeds up our time in the market, and scales up our business.

Automation has affected us positively. We often focus on data; having them at the right place and time is very important for us. UiPath helps us to achieve it with accuracy.

UiPath has saved us at least five to seven hours a week. We also save money since we don't have to outsource or seek the help of an intern to do the manual downloading task.

I rate the product a seven out of ten.

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.

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.

At Aeyon, we use UiPath to develop custom solutions for our clients that drive innovation and digital transformation within the public sector. We work closely with the US Marine Corps, Army, Navy, Coast Guard, NASA and several other Federal agencies. We have built 50+ automations for a wide range of use cases, but the ones we see most often include financial reconciliation, data extraction using AI/ML Models, data entry, data manipulation/consolidation, downloading/moving files in bulk, data validation, and interacting with various web applications.

The business objective that our organization is trying to achieve with its AI-powered automation initiative is to greatly reduce the time spent on repetitive/clerical tasks and allow the employees more time to focus on the important tasks that grow their business such as collaboration and innovation. Aeyon successfully helps our client achieve this objective by using UiPath to develop solutions that increase efficiency, reduce operating costs, and drive ROI.

Our AI-powered automation initiative has fundamentally changed what our organization is able to achieve. It has made a huge impact on the way we process documents for not only ourselves but our clients as well. It saved a lot of time and money.

We use AI Center for data extraction on structured and unstructured document types. The pre-built models are very versatile and efficient, and the ability to train custom models makes it a great solution for almost any use case. I feel that AI Center and UiPath Document Understanding were pretty easy to learn. It only took me about a week to learn. There are tons of helpful tutorials and other resources online. I like how it has the prebuilt models as well as the option to be able to go and train your own data, so I would give it a ten out of ten.

It has definitely increased the accuracy of our operations. It has reduced the risk of clerical errors. Document processing has allowed us to be able to compare data for that extra layer of making sure that everything is extracted correctly.

It has freed up a lot of time because instead of having to manually go through and find ways to track data or manually look at it, we are able to use different AI technologies to fit pretty much any use case. For most of our clients, it saves them an average of about 100 hours annually on the smaller processes, and then we have some larger ones where they are even saving about 15,000 hours annually, which is a lot of extra free time for them to focus on collaboration and those kinds of things.

A lot of the prebuilt models that are on an AI Center are valuable. Being able to go in there and train your data, give sample data, label the fields, and different OCR methods are also valuable.

The improvement is not necessarily in the product itself. The main difficulty we have usually has to do with pricing and identifying the best solution for each specific use case on a long-term scale. If there was an easier way to track the AI unit usage and determine which pricing plan would best fit the need for each use case, then that would be extremely valuable.

UiPath is very stable. I have not had any issues in terms of that. The only issue we used to have was if a website were to change or an application were to change, but we have found ways to work around that and deal with those types of situations.

I have been using UiPath for about four years.

Overall, it is very stable. There is low technical debt and monitoring. After a process has been deployed, for the most part, it is stable after testing and everything.

It is very scalable. I have had no issues in that department, and I know that they continue to make it more and more scalable, which is awesome to see with each new release.

Their support is great. There are so many resources available online. There is UiPath Academy, and there is the ability to chat with them 24/7. I have never had an issue getting in touch with their representative quickly when I needed help with something. I would rate them a ten out of ten.

I started off using UiPath, and then I got a job a few years back where I used a software called Kofax. I was able to see a lot of similarities, but I still felt that it was very limited in its ability to integrate with third-party software. I remember several use cases where I thought that if this was UiPath, I would know how to do it. I noticed a lot of limitations with Kofax. It was a bit of a learning curve going from UiPath to Kofax, and then I realized that there were a lot of things that Kofax was not able to integrate with in terms of third-party software. Based on my experience with Kofax, I definitely feel that UiPath is superior.

I have used Microsoft Power Automate for a few processes. We use that for some of our smaller projects. We just started looking into that as an option as well for certain use cases. It is important to us that UiPath has orchestration whereas Microsoft Power Automate does not because orchestration gives you a way to run processes in the background rather than on your local machine. You can also do event triggering and time schedules. UiPath definitely gives a lot more options and freedom to be able to do things without having to manually run the process.

I was involved in its initial setup. I pretty much came in when it was coming from the ground up. I have helped install it. I have helped customers set their licensing plans and install everything on their local machines so that they can run the automation and get set up with orchestration and all that.

Its initial setup was pretty straightforward. You need to have UiPath Studio installed. They now offer automation. They have UiPath Cloud. You just sign into that, and you have access to Orchestrator and all of those services just right off the web. It is pretty easy to set up.

Our implementation strategy includes getting on a Teams call with the client so that we are able to look at their screen and walk them step by step through various aspects, such as:

• Where to save specific folders?
• How to get signed in to the appropriate account?
• How to access Orchestrator and the logs in there to see if there are any issues with the process?
• How to monitor it?

We look at their screen and walk them through various things. We keep that communication line open if they ever have issues or questions in the future.

We did not take any external help. Our company did it through our own team members.

We try to calculate ROI for all of our clients for projects that we deploy. We usually calculate it in terms of total cost savings annually and also in terms of how many hours of labor are being saved annually. It is cool to see those numbers continuing to grow.

The licensing is very affordable, especially when you compare its benefits. However, I know that AI units are purchased separately and can be costly depending on the specific use case. We are still trying to figure out how to track our usage and which tier or plan to go with, but overall, it is affordable in comparison to other options.

I evaluated Automation Anywhere as well as Blue Prism. At my last company, we were trying to figure out between those two and UiPath. After comparing everything on a wider scale, we realized that UiPath was going to be the better solution for us.

I would rate UiPath a ten out of ten.

We use UiPath primarily for tracking purposes. We are a logistics provider and have external portals and websites. The tool aggregates information from these systems to our core application.

We leverage the whole platform. The tool's most valuable features are unattended and attended robots.

We have to change our account representative every year, which is frustrating. We have to re-explain our business every year.

I have been using the product since 2020.

UiPath is stable.

The product is scalable.

Support becomes frustrating when the team asks about the cloud and organizational details.

Our implementation strategy involved choosing a small use case first, improving the value, and accelerating.

Two to three partners helped us with the implementation.

The product is worth its money. We have seen an ROI of 274 percent.

UiPath is not cheap.

We evaluated Automation Anywhere and Blue Prism. We chose UiPath because I was familiar with it, and the local representative didn't have a sales pitch tone.

There is a gap in the marketplace for tracking specialized services. UiPath was the only way to achieve it quickly.

AI-powered automation has fundamentally changed our organization. We have repurposed the hundreds of headcounts and enabled them to focus on more meaningful work.

UiPath AI Center has grown and evolved from what it was. We are looking at more opportunities since the person who managed it has left the company.

We are still trying to figure out AI's use in our operations. It brings in efficiency, but we are in the process of validating it.

AI use has sped up our time to about 256,000 hours a year.

We have only started to use process mining.

I develop RPA processes at a financial services company. We use UiPath for tasks like data entry, image processing, and reporting.

The biggest benefits of UiPath are fast implementation and the ability to run unattended bots. When they implemented UiPath, my manager was kind of shocked.

We could run a process to extract every file from the portal each employee needs, which saves almost two hours per employee daily. You could see the benefits immediately. The hardest part of RPA is often convincing management that the expense is justified. The company can hire fewer employees because it's automating repetitive tasks. However, some of that savings is offset by the cost of licenses and hiring developers.

I completed the UiPath Academy course, but I haven't received a certification. It helped me to understand how to implement UiPath processes. The main benefit is that it contains complete information about the tool. I know enough about using UiPath that I don't need to search the knowledge base when I get a new requirement.

Another advantage of implementing robotic process automation is that you can greatly reduce human errors. The RPA process almost never makes mistakes. It increases productivity and frees up employee time. For example, we have a guy who is responsible for creating memos for the checks. It involves 200 checks, but he was reassigned to something else, and now all those checks have been automated. The organization saved the equivalent of about 60 FTEs.

The most valuable feature is image processing. It's something I use daily when I need to do some work on a VM remotely. Image processing enables me to locate the connectors and click to perform my job or task. It's easier for me to develop a process using UiPath compared to Power Automate.

UiPath enables us to set up end-to-end processes. For example, I have a process for taxes that gets a statement from the bank, checks incoming and outgoing transactions, calculates the withholding and exemptions, and files it on the income tax site. If I get stuck when I'm working on any process, I can easily ask the UiPath Community forum, and the public can respond to it.

UiPath's OCR features could be improved. It has to do complex OCR captures with UiPath. I would also like improvements in the dashboard for executing processes.

I have used UiPath for a year and a half.

UiPath is stable, but you need to adjust the process when a web application changes its interface.

UiPath is quite scalable, in my experience. We have a large environment and 150-160 processes.

I rate UiPath technical support nine out of 10. They're always on our level when we contact them about any errors or limitations we face. They respond consistently, and they're available when we need a meeting to discuss something.

I have also worked with Power Automate. UiPath is more flexible and dynamic, whereas Power Automate is a little harder to handle.

The initial installation is straightforward. You install the UiPath enterprise license and apply the license key after completing the task. For unattended bots, you need to deploy the Orchestrator on-premises, which is somewhat complicated, but the overall experience is straightforward.

When we implement it on-premises, we need to take some steps for security. We have to configure some ports and connect all the PCs, but everything is under the control of an enterprise security security solution. During the initial installation, we needed five people, but once it's deployed, a single person can administer the platform.

The pricing depends on whether you're running attended or unattended bots. Unattended processes cost a lot more, and you have to pay cloud costs, too. It's costly. The licensing for the tenant dashboard, developer's toolkit, etc. was reasonable, but unattended bots are quite expensive.

I rate UiPath nine out of 10. I suggest new users study the knowledge base on the UiPath website. Many people get information from YouTube or another source that doesn't cover all the steps of this tool. However, if you study using UiPath Academy, you can gain complete knowledge of the tool.

Our company deals with data analysis and we use the RPA to help with various functions related to data analysis and to keep our operations moving 24/7.

Since we've automated, we've received great results in improved performance and helped increase productivity. Our business has expanded and the solution has made customer service faster. We're also able to respond to various suppliers and stakeholders more efficiently. Whatever they require they can get in just the click of a button.

The biggest benefit so far has been the upward trajectory of our productivity. Our teams have become more efficient and productive.

We're also saving on staff and allowing staff to work more remotely.

It's very easy to deploy and we can use it without any problems. It's easy to learn. We have various staff members using the product. It's easy to troubleshoot if you run into issues. The support team is very efficient.

It's just easy. It streamlines our activities very well. Before acquiring it, we had issues with data loss and record keeping. Now, it automates everything. It's efficient for tracking and acquiring whatever data you are using.

It took us less than a month to automate everything. From there, it's picked up very well and has been super stable. there's no buffering. We have no problems.

We use it for a diverse group of people who come from different departments. It can be used in customer service, bookkeeping, HR, et cetera. It works across diverse projects and staff.

The automation saves time on various tasks. It used to be handled by a human workforce that had to handle repetitive or cumbersome tasks. Now, it can be done efficiently without even using humans. Now, we can run 24 hours a day. Even when shifts are over, the robots keep working.

We can enable end-to-end automation. It's enabled now. We're even thinking of implementing it further and acquiring more products. We want to use it as the core of our automation. We do have processes that are almost end-to-end. Three-quarters of them are almost fully automated. For example, ticketing. How we attend to our customers is very extensively automated using UiPath.

The user community is very efficient. They help us a lot. We can exchange notes. For example, we've used the community to figure out how to implement benchmarking in our company. We get very efficient notes on how to improve our systems.

It's helped minimize our on-premises footprint. It's on the cloud. For example, we can have more staff working remotely. When we had our entire team in the office, our production cost was very high. However, now that we've allowed remote work, we've saved money and found more efficiency.

Some of our staff have used our Academy courses. Some staff that are not so tech-savvy have taken advantage of the courses. It's improved the general knowledge of the platform and has made onboarding more efficient so that other users can learn more about how to benefit from this platform.

It's helped us with digital transformation. It's helped us move away from manual processes and away from analog systems. We're working to be more digitally efficient.

It has helped free up employee time. They are now able to engage in other activities within the company. It's enabled them to complete their work and assigned responsibilities on time. It's likely freed up employee time by 50% to 60%.

From a value perspective, we have seen cost savings. Tasks that have traditionally taken a week take far less time. It helps save money on the organization's part as it all takes less time. We might have seen a cost saving on tasks of 42% to 50%.

It would be nice to have physical support, where UiPath can come to companies and do frequent visits for troubleshooting. It takes a while to respond back and forth when there's an issue.

I've been using the solution for three years.

The solution is stable unless we have a network problem or connectivity issues.

We use it across the organization, and within different departments. We have 500 users, and 12 people using the solution on a daily basis.

The scalability is good. It's easy to scale up.

Support is very friendly. They are amazing people. The time it takes to respond might be a day. When they do reach out they are super-efficient.

We did not previously use a different solution.

We are working with the latest version of the solution.

From what I understand for IT, who deployed it, it's not hard to maintain the solution.

Our IT dealt with the vendor during the initial setup.

We have witnessed an ROI since the production costs have gone down while the productivity has risen overall. Everything across operations is streamlined and staff are working more efficiently.

For small users and startups, the price is a bit high. However, it does give good value for money. For established organizations, it's reasonable.

We did evaluate other solutions, however, we found UiPath very popular and heard good things from people who used it.

We are not currently using the tools' AI functionality. We're just considering adopting it. We're not there yet.

I'd recommend the solution. It helps you realize your automation journey. It's good to get some training or some general knowledge about the product so that you can use it without delay.

I would rate the solution nine out of ten. It's one of the most popular options on the market. It's adaptable across departments, from product to service, to finance - everything. It can be used across the board.

The way I'm using UiPath is to create workflows related to financial services. I work for a company called Cedar Financial here in Pakistan. The workflows are related to our data statements, clients' financial documents, and the like. It mostly involves Document Understanding and creating workflows to generate reports. My use cases are restricted to UiPath Studio, where I use the Activities to create workflows and automate some of my clients' work.

It's very cool to be able to create automations and reduce human effort. It really is a valuable and great tool to be working with. It has improved things immensely because our organization needs fewer human resources. In one department, 40 percent of the time has been freed up for other tasks. The work the bots do is more efficient and reliable. UiPath has reduced human error, which has had great effects: better results and better revenue. It has saved us about 40 percent of our costs.

Another important benefit is that UiPath enables you to implement end-to-end automation. Humans don't have to do repetitive, boring tasks.

The most valuable feature is its screen recording capability, where you tell it what the workflow should do, and it then automatically creates Activities for you.

It's easy to build automations with UiPath help. I have also been a Python developer, and there you need to do hard coding to create an automation. But when you're dealing with UiPath Studio, you have all the modules. You just need to know what to do and which Activities you can use. You get everything right, and the automation is ready for you. You don't need to do hard coding.

And UiPath's user community has been great for me. Every time I'm stuck somewhere, there's always a forum to ask questions and share my knowledge as well. There have been a few main developers, like Michael Jensen and a few others, whom I follow and really admire their work.

They need to keep fixing the bugs and improving the tool. For example, if an Excel file is running and I'm doing an automation on that Excel file, it doesn't complete. There are some bugs, and fixes and improvements are required.

The stability is good.

It's scalable.

Previously, I used Python and its multiple libraries and frameworks to do automation with Selenium and Beautiful Soup. We switched to UiPath because you don't need to do hard coding with it. You have more functionality. You just need to know what to do and keep on importing those activities. Create the workflow, and the automation is almost done.

UiPath is always a good investment.

I have tried Microsoft Power Automate, but UiPath has a lot of Activities and is easy to use.

The UiPath Academy is where everyone starts. I started there and took courses such as the RPA Developer Foundation course, and I still take courses from the Academy. It's very beneficial.

When you have RPA developers, they sometimes require IT support. The application team is also important in this.

The time it takes to implement a solution with UiPath depends on the problem and the workflow. Some might take 30 days, while others might take just one day. It does require some maintenance at times. There may be updates, or an error might appear. We have to provide support as well.

From a company point of view, it didn't take long to identify how beneficial UiPath could be. Every industry these days needs automation tools. If an employee generates the same report every single day, we can build a robot to do that.

It's a good and handy tool to use. Try it, and it will help you greatly boost your business. And your employees will be happy as well when their time is saved. Go for it.

We use the solution for robotic process automation. We use it across the value chain for our business. We've used it in accounts, including cash management, and in HR for management tasks and IT for password resetting.

The automation has been quite useful. It's been helpful in our journey towards transformation.

I've used this solution for a while and I utilize the whole tool and get a lot of benefits out of it.

It helps save time. We've had efforts that would take more than four hours a day, yet, when done through UiPath, it takes less than a minute.

The useability is very good - even for non-technical people. I'm an accountant by education and now I'm also an automation expert by profession. Its interface is user-friendly to those of us who are non-technical.

Anyone who wants to automate any task that is rule-based and repetitive can do it through UiPath.

We can use the solution for automation emails or notifications.

It enables end-to-end automation. We developed a use case where people from different business units have large amounts of data, Excel files, we've made it so that we can combine it and enter it into the ERP system. Everything can be checked via the rule book and can create the report and send back the information to the customer. It simplifies the data and organizes and compiles it for them. Users have gotten the benefit of five FTEs by using UiPath. It saved many man-hours.

I haven't used the UiPath Community too much. I often Google questions to find answers. It is a good place to go for development work, though.

It reduces our footprint. We historically did have many items on-prem. I like it on-prem and on the desktop.

It can reduce the cost of digital transformation. Where processes can have faster response times, UiPath helps with efficiency. However, if the response time of the application is slow, and we need to provide workarounds, it isn't helpful in that it hasn't efficiently helped us save time.

UiPath reduces human error by 100%. Whatever you give to the robot, it will do it correctly. That said, it needs to be programmed correctly - if it's programmed wrong, it will do it 100% wrong. If it's programmed right, it does it 100% right.

It's freed up human time. It's not well-utilized in that sense. It should be available to everyone so that they can find ways to save time by creating their own automation according to what they need.

There are a few shortcomings. For example, even in their latest version, there are still older features even though they've introduced new ones in parallel. They should do something where they update the solution and then close off the older version after a year or something like that. That might help with standardization.

Sometimes it is very useful for automation. However, sometimes it is really, really frustrating when it is unable to manage the more dynamic items. When an element is stable, it's great. When it comes to changes to IDs or the dynamics of the website, it lets us down in front of our customers. It needs to be better at handling volumes of data.

Automation on the cloud has had issues. It can be slower.

The Academy classes could be improved. There should be a portal for use cases. There should be more business examples.

They should offer different licensing tiers, especially for daily individual users.

I've been using the solution since 2016, more than five years.

It is a stable product. There were some issues while interacting with different applications. For example, with Microsoft, we have issues with One Drive. When UiPath is working on a file, it cannot quickly get to the file. We need to move the file to a local drive before processing the data. Microsoft applications seem to give it trouble.

We have multinational business units. Company-wide, maybe 500 people are using it. Where I am, there may be a team of ten people working with it and 50 to 60 automations. The solution is in multiple locations and departments.

The solution is scalable. It depends on how an organization wants to utilize it.

Technical support is very flexible, however, they do not respond quickly. Sometimes they just tell us "this is how it works" and we have to try to explain our framework.

I have also tried Blue Prism. I didn't work with it much; I just studied it theoretically.

I also tried to work with Power Automate. Initially, it wasn't very good, however, later, it began to echo the style and functionality of UiPath.

UiPath is easy to use and easy to get started with.

The deployment was a long journey. I was one of the first people in Pakistan to use it. Now, once you get a license, you can deploy it in two weeks. However, it depends on the complexity of the processes in terms of deploying automation.

We have around ten people maintaining the solution. It requires a lot of maintenance. If anything needs to be changed in the target application, it needs to be incorporated into the robot.

Someone told us you do need three to five years before you get an ROI. However, in our first year, we were able to save more than 8,000 hours.

The solution is on the expensive side.

There should be standardized packages. If an organization already has a license with UiPath, UiPath should offer special licenses to each employee so that each employee has their own UiPath automation capabilities for each of their individual tasks.

There should be regional packages and costs. Different regions cannot necessarily afford UiPath. What is affordable in Europe may not be affordable somewhere else.

We're a UiPath customer. We serve internal customers with robots.

We do not use the UiPath AI functionality, however, we are on a journey towards building our own internal solution.

I'd like to see UiPath cut the cost of their license. For end-to-end automation, for developers, I understand why it needs to be expensive, however, for day-to-day users, it should be cheap.

I'd recommend the solution to new users.

I'd rate the solution eight out of ten. It's still the best out of all related products.