We are a consulting firm. We started last year, and we are growing pretty rapidly.

We have quite a few document-understanding processes that we are working on. We are a partner of UiPath, so we have various clients in different industries. Currently, we are processing vendor statements to create payments in NetSuite. We also have a three-way match cache application process, and then we have a basic user interface for scraping vendors' websites for payment data and that kind of thing.

We are trying to figure out how to incorporate LOMs with everyday processes and get reliable information back. We are also training a lot of machine learning models to extract data from PDFs along with processing contracts. I hope that those get easier to train and that there are more reliable answers or outputs from the models that we train.

Our AI-powered automation initiative has fundamentally changed what our organization is able to achieve. Document processing has come a long way and become a lot more user-friendly with validations and Action Center. The straight-through processing has increased.

They are constantly making improvements to Action Center where you have more feasibility in assigning tasks. There is a lot more flexibility and data around it. We have been incorporating insights into our automations, which helps us create a business case for future automations based on what we have done in the past.

The use of AI in our automations has definitely increased the accuracy of our operations. It has also increased the ability to process certain use cases that were not available before. It gives us more opportunities to automate processes, and therefore, drive revenue.

The use of AI in automations has freed up time or resources for other tasks for our customers. The time saved depends on the use case, but they are probably saving about a thousand hours a month on the vendor statement processing. They are getting 2,000 to 5,000 statements a month. Each one takes roughly 45 minutes.

Their core platform of Studio is valuable. The ease of use and the ability to build these automations quickly is definitely a highlight for us. Our average process from start to finish takes three to four weeks. We can knock out automations as quickly as we can identify them. That is probably the best feature I see.

In Action Center, saving progress in data validation, specifically for table content, is currently not available. There should be more clarity around the feedback loop along with the auto-update feature when you deploy machine learning packages. They should give some rule-based options so that if the confidence is returned higher than the previous model trained, then it would auto-deploy. If it is less, then it should send you an email rather than auto-deploy.

With task assignment, if there was a round-robin feature within the bucket to automatically assign it to a certain group of people, that would be helpful.

There should be the ability to add custom fields to validation tasks because there is a lot of potential for it. It would be helpful when somebody needs to identify a scenario. For example, we have a customer who is processing rate sheets for trucking, and sometimes, depending on their customer, they have an all-in rate versus an adding fuel mileage rate. If they are able to specify that, even if it does not say it on the rate sheet, it would allow them to process more documents successfully.

We use UiPath's AI Center, but some clarity is missing around when to use AI Center versus when to use the Document Understanding module within Orchestrator. We are trying to figure out the benefit of one versus the other. We have also seen that the out-of-the-box models that we train versus a custom model that we train with the same data end up with the same output result at the end. We are trying to see where these out-of-the-box models are providing value if we are going to take the time to train them.

I have been using UiPath since 2019.

We have run into issues with integration services where we developed something, implemented it, put it into production, and all of a sudden, it does not run unattended. It is a very frustrating situation to be in.

There were some issues with sharing connections between different accounts, and we have learned from that experience to do more upfront testing of new features before we build automation on it.

Event-based triggers not working is probably the biggest stability issue that we have run into, and integration services not working is probably the biggest gray area. Other than that, it is a stable platform.

It is definitely a scalable platform.

Their support is good. I have had good success with submitting support tickets and getting answers quickly. If it is a bug that is identified with the process or with the platform, they resolve it within a matter of a week. There was a production issue. It was a throughput issue for the AI model. We were not able to access a 100-page document because of this exception. They implemented it and fixed it within a week, which I thought was awesome. I would rate their support an eight out of ten.

I did not use any other RPA solution previously. I have only used Power Apps a bit, but it was a very small part that we have looked into. Overall, we are strictly focused on UiPath.

I have probably set up 100 Orchestrators at this point, so it is straightforward. However, the initial setup is confusing for new people who have not done it where they are matching machines to the tenant and plugging it in their machine key, but I am not sure if there is any way to get around that. When you have done it once, it is easy.

The other thing is the licensing aspect of it. You need to assign a license to the machine template and then the machine template to the folder, and then you have to make sure that the machine is connected. There seems to be some confusion amongst our developers on how to make sure it is all set up correctly, and then you have the robot account. You have to make sure that it is also set up correctly to run unattended automations. It is a challenge, but if you do it two or three times, you get the hang of it.

In terms of the implementation strategy, overall, we look for quick wins upfront so that we can build the program and get support behind it, and then tackle the more advanced use cases after we get three or four in production.

We have cloud deployments. We have had different cloud providers, such as Azure, AWS, and GCP.

We are a consultant.

We have definitely seen an ROI in terms of hours saved and quality of work. Once you get off the ground, there are a lot of other departments that end up getting excited and looking forward to future automation. I feel that is a win for morale.

Overall, the model is fine except for AI units. It is usage-based, which makes sense if you are processing documents, and you have one unit per page. It is the hosting cost of the models where there are issues, so we are running into potentially designing poor solutions because we are having to say, "If the documents are very similar but different enough, even though you would prefer to use two models, maybe consider not using two because of the hosting costs."

Power Automate is something we might look at. UiPath has orchestration while Power Automate does not. Orchestration is vital for us.

If you are trying to do in-house development, the user experience is much better than any other platform that we have evaluated. It is easy to pick up. The UiPath academy, training, and forums are great. The biggest selling point for me is that you can pick it up as a business user and learn the platform in a matter of days or weeks as opposed to months or years.

I would rate UiPath a nine out of ten.

We use UiPath for web scripting, data loading, data uploading, desktop application scripting, file uploading, and data downloading.

I am a developer, and I love the tool's easiness with features like drag and drop. The tool is ready to use with some minor updates.

I have had issues with the selectors. I face problems during image capture, and I need to update them. It is not something that I can rely on.

I have been using the solution for three years.

UiPath is stable.

The product is scalable.

I contact the support whenever I am stuck, and they help me.

My director explored a lot of RPA tools and selected UiPath. He convinced the organization that it was a good tool.

UiPath's upgrade is easy.

We evaluated WinAutomation and Blue Prism.

Our business objective for implementing AI-powered automation is to reduce manual work.

UiPath has fundamentally changed what our organization was trying to achieve.

The tool has helped us save 3,000 man-hours.

UiPath has enhanced our accuracy. We do government reporting where we are given templates. The Excel files are locked, and we have to type the data. There are thousands of cells, and we must generate weekly, monthly, and quarterly reports. We have to assign a person for each report. 100-180 such reports have to be generated. We use bots to populate the cells, and there are no errors. We can see that there is 100 percent accuracy.

I rate the product a nine out of ten.

Our use case started with the financial sector. We are expanding it to the navy's other operational aspects, such as HR, legal, procurement, etc.

UiPath's most valuable features are automation and document understanding.

I want our relationship to be better because of the nature of what we do.

I have been working with the solution for four to five years.

The solution is very stable.

UiPath is scalable.

We work very closely with our UiPath representative.

We used Microsoft Power Automate. UiPath suits our cloud environment better than Microsoft Power Automate.

Deployment was complex because of our environment since we needed to get approvals.

We work very closely with Deloitte.

We had evaluated Automation Anywhere.

Our business objectives for AI-powered automation are finding inefficiencies and improving efficiency and ROI.

AI-powered automation has helped our organization to be more efficient and faster. It is working 24/7.

UiPath has enhanced the accuracy of our operations. We were able to recoup funds that we previously knew didn't exist. It has boosted people's morale since they are not working on tedious tasks.

We estimate that UiPath has saved the Navy about 156,000 hours. I rate it a ten out of ten. You need to understand the tool's processes.

We use UiPath for document manipulation. It helps us split PDF files, clean and submit them to the government website.

The tool's most valuable feature is the ability to pull information and manipulate documents.

UiPath should improve its support team.

I have been working with the product for six to eight months.

I haven't had any issues with stability yet.

UiPath is scalable.

UiPath's deployment was complex because we weren't familiar with it.

A partner helped us with the tool's implementation. They did the development work while we focused on back-end activities like getting the servers up.

We have seen ROI with the tool's use. The legal department saves time and money with its use.

I wasn't surprised by the tool's pricing. It was comparable to my expectations.

The business objective we tried to achieve with UiPath was the PDF turnaround times. We needed to meet the deadline for the filings. If we missed the deadline, we couldn't submit them. Hence, the timing of submitting the filings was critical.

I work for a law firm where timing is critical. AI-powered automation has helped our organization unload people from repetitive tasks and instead focus on client and legal work.

UiPath has freed our resources' time. Earlier, eight to ten people needed to work eight hours to complete the filing. We can do it in under an hour without ten people focusing on the task.

I rate the product a nine out of ten. You need to take advantage of the solution's training to help you understand its capabilities. I was new to the product and was surprised by its capabilities. It is a huge benefit to access the training without paying for it.

I use UiPath to reduce any data entry, report generation, or anything where UiPath can help avoid human errors.

The solution is very user-friendly and easy to use. It comes with pre-built automation. The tutorials are very helpful.

I have been working with the product for six months.

The tool is stable.

UiPath is scalable.

The tool's support is helpful.

I use UiPath to reduce human errors during report generation or data entry. Simple errors can cause delays down the stream.

The product has helped us save hours, which can range from a few hours to tens of thousands of hours.

UiPath has helped us increase accuracy. It is helpful in data validation.

I rate it a ten out of ten.

My primary use case is mainframe automation from legacy mainframes that previously hadn't been automated with other automation tools. The product worked like a dream with the mainframe automation.

We're trying to get rid of the boring, mundane tasks that people do every day so that they can spend more time doing more important things like figuring out why there are issues happening rather than just putting a Band-Aid on.

In our first year of jumping into it, we set up the infrastructure and everything, so it's been less of a year of development, but we have saved a hundred thousand hours.

The automation efficiency depends on what the job at hand is and how much it saves. But some of the tasks done constantly throughout the day, even if it's only saving five minutes, add up really fast.

We use Task Capture all the time. We have a bank business analyst who uses it and teaches people how to use it. We're constantly getting process definition documents to review and add to our pipeline.

Studio itself has all its great features and is easy to use.

There are bugs here and there. My only complaint is that each time we open a new ticket, we get someone new and have to explain how everything is set up all over again.

It would be nice if they had that somewhere on record for support.

I have been using UiPath for two years.

It is a stable solution; everything seems to be running pretty smoothly altogether. The biggest issues are not on the UiPath end, but on our company's end like, network issues and issues like that keep popping up every now and then.

The support's been pretty decent. We have a TAM, so we have someone we are constantly in contact with.

We meet with them weekly, and they're very helpful. If we do have to open up a support ticket, there's a bigger issue that they can't help with. They usually help get the ball rolling.

Support has been pretty helpful. Like any other support though, they ask all the basic questions in the beginning just to figure out what has or hasn't been done.

My only complaint is that each time we open a new ticket, we get someone new, and we have to explain how everything is set up all over again. So it would be nice if they had that somewhere on record.

The initial setup was straightforward. There's plenty of documentation that is easy to follow.

The hardest part was more on our company's network and infrastructure, trying to navigate all the hoops that we have to go through just to make sure it's secure and the network's secure. Getting access to what we need to get access to.

We're still kind of new to things and working on migrating to the cloud. We're one small team in the organization. By moving to the cloud, we're hoping we can onboard more and more teams to be able to use it and spread it throughout the company.

UiPath helped us along the way.

There are other automation tools that the company uses, but they can't do everything that UiPath can. All of the potential automations just kept being pushed to the side until we started using it.

We used Microsoft Automate for a very short time. We started looking into it for some tasks. The issue is that we're trying to automate it deep inside our corporate network, so, we haven't really been able to use Power Automate.

Overall, I would rate the solution a nine out of ten. The amount we could do in one year is pretty impressive.

We use UiPath across a diverse range of functions and departments, encompassing accounting, human resources, loan servicing, employee progress tracking, and loan origination.

Our primary objective has always been to navigate the cycles effectively, ensuring that we can manage fluctuations without the need for constant hiring and downsizing. It's all about maintaining a consistent workforce over time.

The most valuable component is Studio—it's the cornerstone of our automation efforts. Recently, we've delved deeply into Insights, which has proven to be incredibly beneficial. Our key focus is on eliminating time-consuming tasks and enhancing reliability, especially in repetitive processes, which is where automation has proven to be a significant asset.

Simplification and adaptability for smaller businesses would be a welcome enhancement.

I have been using UiPath for approximately six years.

It is highly reliable, and we didn't have any issues with it.

When it comes to scalability, one aspect to consider is understanding the licensing for on-demand bots and related components. There have been some challenges, mostly on our side, particularly concerning high-density servers.

The ideal scaling strategy involves adding more instances to these servers. We have opted for standalone virtual machines for each partner, and while this approach offers scalability, it does require the manual setup of additional machines, which can be a slower process for a small IT team like ours.

I contacted customer support only once when we encountered an issue related to changing the institution name within an application. Fortunately, the support team was able to resolve the matter successfully. I would rate them ten out of ten.

We were using a software called Winautomation, which wasn't very robust. So, we made the decision to switch it, which has been a beneficial change.

The initial setup was relatively straightforward. The main challenge we encountered was obtaining security approvals when transitioning to on-cloud.

Initially, there was just one automation tool in place. Our first step was to rebuild that process using UiPath and then we engaged with various business teams to explain the concept of RPA and gather input to create an initial backlog. Afterward, we collaborated with management to prioritize the tasks and determine the order in which we should proceed.

I find the licensing structure to be perplexing, and it frequently changes. The inclusion of AI units, raw document units, and Cloudmont licensing, along with various sub-licensing options, can be quite complex and non-intuitive.

We were considering a few alternatives, such as Blue Prism and Automation Anywhere. The primary goal was to find a solution that we could commit to for the long term. Ultimately, it appeared that UiPath, which is an industry standard, was the best choice. I also had previous experience with it at a previous company, which made the transition more comfortable for me.

Overall, I would rate UiPath ten out of ten.

The process is for background checks. There are all kinds of checks such as academic, criminal, and work as well. We receive all the volume through the queues. We are using the citizen developer, StudioX, to get the cases and understand what are the fields and what are the requirements for each one of the cases. The bot will process them accordingly. For example, for each university or academic, there is a different process around the world.

The industry we use it for is HR. What we do with the backgrounds is providing a confirmation to our clients that people have the qualifications that they say they have. It is for data accuracy and consistency within the HR and talent acquisition departments.

Our AI-powered automation initiative has not yet changed what our organization is able to achieve because the project is still a pilot. We are still working a little bit on the environment. We are working through VDI, so it is not straightforward. We cannot just install or put UiPath to work. So far, we have not seen all the results, but we are looking forward to that in the next quarter.

UiPath would definitely free up time or resources for other tasks. We are a team of six people. We are estimating that two of them will be free for new projects. There is about 30% of resource savings.

Our usage is very simple. We have been getting the text, parsing it, and trying to categorize and analyze it. We are not using it fully, but the OCR is very important. This is a package from StudioX. With OCR, we will implement document reviews to make sure that whatever the applicant puts in the form is consistent with the document provided. For example, in academics, it will be your bachelor's or master's certificate.

The value proposition of implementing UiPath is that if we use UiPath and the RPA functionality, instead of passing the process to a BPO, we will start understanding the process and automating it as much as possible. We will have hybrid workflows between humans and robots. We will create capacity. We will have the same number of workers but increased capacity. We will start having conversations with our stakeholders on how to reinvest all of this capacity that has been liberated.

We have had some issues with StudioX. In terms of features, for now, I am pretty happy with UiPath. The requirements of the process to be automated are covered with the basic functionality. It is not exactly UiPath, but for security reasons, we are not able to download packages and use the functionality provided by the community with their developments. It is not on the side of UiPath.

I was certified as a Citizen three years ago. That is the time frame that I have been using it.

Recently, there was a software update of StudioX. We had some bugs. I would rate it a five out of ten in terms of stability.

We are working on moving to the cloud, so scalability will be good.

We have internal support. I do not speak with the vendor. Our internal support system is pretty consistent. They have quick response times.

From my perspective, I do not think we have been using any other solution. We have been with UiPath for about eight years. I cannot confirm the number, but I know that we have been partners for a long time.

We also use AutoHotkey which is something similar but not a replacement. It is a software solution that allows you to reprogram your keyboard and put some functionality in there to automate some of the things, but it is not a replacement.

I was not involved in its deployment. It is on-prem right now. We are migrating the company to the GCP, so there may be some restraints in regard to that. Everything is currently on-prem, but we are working on going to the cloud.

The ROI would be in regard to the capacity. We estimate two FTEs to be free from this project.

We have not yet used UiPath's AI Center and many other features. We are using StudioX, so we are still in the citizen developer mode. We are not using the full functionality with Studio and all that. We have an RPA COE. They have much more complex processes and projects, but we have not used it for that. This UiPath convention has brought a lot of ideas in terms of how to start leveraging it more.

We have also not used UiPath Process Mining and Task Mining. I am working with one of my colleagues who is like a bridge between operations and IT. We are working together to see how we can better use the technology to improve processes. I have to go team by team, understand the process, and go deeper to see where we can start using this technology. We will have a roadmap of where we need to go.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

We feel like we chose the right vendor.

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

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

I'm a network engineer at a nuclear power plant, and I oversee multiple crews. I use UiPath to automate the voicemail system, send alerts, and run tests. Our company has about 12,000 employees.

UiPath has helped to reduce labor costs.

You can set up processes using macros without basic knowledge of coding.

The hardest part is popularizing UiPath among our employees.

I have used UiPath for around a year.

I rate UiPath nine out of 10 for stability.

UiPath is scalable.

The South Korean team uses Blue Prism. That's a good solution, but it's too hard to use.

Deploying UiPath is easy, and I'm teaching my crews.

It's worth what we pay for it.

The cost isn't important because a good solution isn't cheap.

I rate UiPath nine out of 10. There are still many other RPA solutions we haven't tried, so I can't say it's the best.