Our use case involves using the UiPath Platform to automate processes for customers, as I work with different customers. We use it to automate repetitive tasks, such as daily business team tasks that typically take one to two hours.

We have not utilized the AI integration features yet but plan to implement them with the latest version next year.

We use both attended and unattended automation options in the UiPath Platform. These options have helped in meeting our diverse business needs because before, the business was using manual processes to do tasks, and with attended and unattended automation, they save significant time. We primarily use unattended automation, with customers using it 90% of the time.

The UiPath Platform has improved organizations by saving significant time and money, with approximately 50% return on investment, though this varies by customer.

The analytics in the UiPath Platform help in making decisions, as I am an architect who builds the platform for customers and helps the business team choose which processes will be automated.

They have free training and it is very easy to use. They provide training through their platform or through partner-led training sessions. Training with a partner in the UiPath Platform takes three days to introduce the platform, while self-paced training takes approximately one to one and a half months.

In the UiPath Platform, reporting is an area that has room for improvement. I would like to improve reporting by having more detailed information, including logs and robot logs.

I have been using the UiPath Platform for nine years.

The stability of the UiPath Platform is excellent, rating a ten out of ten.

The scalability of the UiPath Platform rates a ten out of ten.

The number of users varies by customer, with one customer having 100 users and another having 200 users. In my organization, I work alone with the UiPath Platform as the architect and process builder, though we have a developer.

The technical support of the UiPath Platform is very active and excellent, deserving a rating of ten out of ten.

The deployment can be either on-premise or cloud-based, depending on customer preferences. I have deployed it on-premises for nine years. For me, it's easy, but it takes time to deploy it.

A complex architecture can take two to three weeks. A simple architecture can take a few days.

The solution requires minimal maintenance, with major updates annually and minor updates every two months.

The UiPath Platform has saved approximately 50%, though this depends on the customers, with an average 50% return on investment.

It's expensive.

Comparing the UiPath Platform with other automation tools such as Blue Prism, UiPath is significantly better. Power Automate works only with Windows Microsoft products, which is limiting, but the UiPath Platform is the best for automation. Though it is expensive, it remains the superior choice.

I would recommend the UiPath Platform to other users because it is very robust, easy to use, and offers abundant information on the internet along with free training.

I would rate the UiPath Platform a ten out of ten.

Currently, we do not have any AI use cases. I work for a healthcare system. Our main use case is using UiPath to replicate what medical coders do. We input codes from certain medical systems into another, and it automates our billing cycle. This allows us to input the codes directly into the insurance billing cycle, speeding up our payment process.

Our hospital does not get paid if we are slow to get the codes to the payers. By automating this process with UiPath, we wanted to speed up the process of getting paid by the insurance companies. It has been amazing. Just this year, we probably saved 45 million dollars, and the next year, it will be upwards of 80 million.

In health care in America, many processes are still paper-based. Document processing is valuable as it allows doctors to have documents processed in advance, making it easier to access and ask questions. Additionally, UiPath has freed up staff time significantly, to the point where some staff had to be laid off. Our use of automation sped up the process of getting paid from insurance companies, saving us substantial amounts of money.

We're looking to add AI, specifically generative AI, but it's a matter of our organization implementing it. With autopilot features like Microsoft's Copilot or ChatGPT, users can start chatting immediately. However, with UiPath, one needs the UiPath Assistant installed on every machine, which is unrealistic as many people use the same machine in the hospital.

My enterprise has been using UiPath since 2021. My team inherited it in 2023, so it has been about 11 years.

The solution just went live yesterday, so I don't have feedback on its stability yet.

The solution is scalable. We previously had an older solution, and UiPath helped us revamp and upgrade our systems, making them more scalable.

The customer support from UiPath is amazing. We are part of the hypercare, and I would rate it as a nine out of ten.

We use Power Automate a lot and still incorporate it alongside UiPath. Some hospital systems require us to be all on-premises, so we use both UiPath and Power Automate to get our systems working as needed.

Some automations were built in-house by our team of developers. We also worked with an external partner and UiPath to implement some other solutions.

We have seen a 100% return on investment. The process is night and day when compared to paying employees over time for the same work.

It is more expensive than other automation services, but I don't deal with the financial details much.

As automation software, I would rate UiPath a ten out of ten.

UiPath is used to automate processes, eliminating the need to increase headcount.

There was an increase in both quality and quantity while not having to increase admin simultaneously. We have successfully automated the majority of our automation projects.

The UiPath automation has helped us to keep our bottom lines down across the board.

UiPath has helped our organization with its environmental and social initiatives.

It has freed staff time for other tasks, improved their work quality, and saved hundreds of hours per month.

UiPath is the best automation solution available today. The process and task management are the most valuable features.

UiPath's Unassisted Task Mining has room for improvement.

I have been using UiPath for four years.

UiPath's stability is reliable, especially now that we've moved to the cloud.

UiPath scales well. We have not had any issues.

UiPath support has been responsive to us.

UiPath has successfully met our expectations by reducing project costs through automation, demonstrating a strong return on investment.

I would rate UiPath ten out of ten.

I have used UiPath in my last three companies.

Currently, we use UiPath in multiple types of use cases and build innovations for our clients to improve their system operations. We don't plan to implement AI in our automations in the near future. We're interested in that market, but it's a long journey, and it's a little advanced for us right now.

UiPath is helping our organization with its environmental, social, and governance automation space. Though it's currently at a beginner stage, it is progressing, and we expect to see improvements. UiPath has helped us free up staff for other projects. We have engaged our employees in working with UiPath through presentations.

UiPath's integration features are highly valuable to us. We are able to achieve a lot with them.

For the moment, I don't see any explicit areas for improvement. However, having UiPath come up with unique features or advancements would be beneficial.

I have used UiPath for five years.

I don't see any drawbacks because our content is not down over time. We keep it updated consistently.

As our environment has grown, I haven’t encountered any specific issues or limitations.

I rate UiPath support nine out of 10. It's great, but sometimes we see delays. We ask a question, and they have to get back to us later with an answer. Otherwise, I don't see any drawbacks.

We previously tried out another automation app, but it didn't meet our expectations for handling exceptions and managing complex workflows.

Deploying UiPath was straightforward.

UiPath is the best tool, but the price is challenging from a management perspective. The cost-benefit equation might not work out favorably for some smaller organizations.

I rate UiPath 10 out of 10.

We started using AI in Document Understanding by leveraging it against our models for different documents from our customers, primarily in the finance space. We have also used AI to train models for land management documents, helping them learn as we receive new document types.

Recently, we've used it to analyze documents and articles online to understand sentiment toward our company. We analyze and summarize things people say in articles or posts elsewhere, which allows us to collect industry trend data. We are considering using Clipboard AI for smaller, ad-hoc data processing tasks because it can sometimes be more effective than Document Understanding.

We get a lot of projects that are on relatively short notice for the workload that comes with them. Historically, we would rely on leveraged services or contractors to do that work manually, which is costly. You can save tons of money by automating data entry, transcription, etc. Nowadays, as we get busier and busier, the work seems to bog people down more and more with tasks. UiPath gives them opportunities to free themselves up and focus on themselves.

We initially focused on time savings and how we could free people up more. We achieved that over time, but it took a while to get there in the first few years. We came in with some use cases that we later learned were not great fits for automation. We learned through trial and error and got better at identifying better use cases for automation. We've succeeded, and it's worked out for the better.

But aside from saving people time, we also wanted to ensure that we brought in new technology to leverage some of those processes. UiPath forces you to look at the process from a high level and take a step back. You might have had the same person doing the same process for 10 years or more without thinking about how you can use new technologies to eliminate the process or make it more efficient. UiPath forces you to look at the process as a whole and the systems it's tied to. When you step back and look at it, especially with new people coming in, they start offering suggestions, like "Wait. You've been sending this email every time? That's something we can automate now. Oh, you've been trying to pull this information from a document and copy and paste it? That's something we can automate, too."

If it's not automation, it's something else. We can look at other tools and applications our company brought in. There's usually some other solution they can use, automation or not. The natural way to work with it is by lining out a process and laying out all the steps on a workflow diagram. It allows you to rethink your process as you're doing it.

Instead of just following step-by-step documentation or the way you've done it all the time, it gives you a chance to see it from a new perspective, and that's just part of working with the tool. As you build that out in UiPath using task capture or anything else, you will see that naturally and start thinking about ways to handle it better.

Automation has freed up employees for other tasks. That's something that they like about it. The other thing it's done is build some excitement about IT and solutions in general. They're always looking at the new function that's coming out. They want to see what else we can do for them. Automation isn't always the answer, but we can get them to engage and talk to us during office hours to attempt to solve their problem with UiPath. We can also learn more about what they do.

We're getting closer to our customers, talking more about their work, and they're feeling a closer bond with us. They're feeling like they trust us more in IT and are starting to see what other tools we have. Maybe automation wasn't the right fit, but we will always find better opportunities by building a report that sends an automatic email and an application for them in low-code software. UiPath has helped create a much better and fluid engagement process for us and our customers.

Since it's a low-code tool that's easier for them to approach and understand, they're also more involved in the design process. The learning curve is shorter. When Studio first came out, it wasn't as user-friendly as they had hoped, but StudioX came out in 2020 and was approachable for most of our users. That's what our citizen developers use most of the time now. We have far more citizen developers with StudioX than unattended developers with Studio.

Within UiPath Cloud itself, UiPath Insights has been excellent. Insights is one of the newer features we were excited about because we built custom reports, captured all that data in one place, and leveraged it in different areas. That was a challenge for us and created a support burden. We're automation developers, not report developers. When leadership wanted a new metric or anything, figuring it out was always a pain.

Insights has built-in mechanisms for tracking time savings, usage reports, and the overall health of your automation program. Having that functionality built in by default is critical. I click it and tell it the report that I want to generate. It'll build it for me automatically, and I can share it with people who need it. It has made a huge difference for people administrating the platform and reporting success to leadership over time.

UiPath needs work on the governance side. For example, they released Studio Web this year and have started work on its governance, but it initially lacked control from an administration standpoint. You could not lock down third-party libraries or other applications and integrations it had built in.

For example, people could use a Google account, but we might have concerns about that from a security standpoint. Cybersecurity is taking a more significant place in IT, and we're mindful of that. Having explicit governance over what our users can do inside those technologies is essential. We hope to see that more over the next few years. We've given a lot of that feedback as customers to UiPath, and they've been working hard to get that into the pipeline and implement those changes.

I have been using UiPath for about six years now.

UiPath can grow with us, especially since they developed a cloud environment. When we started, we had to make many changes in Orchestrator and other areas as we scaled up. We scaled up fast and automated dozens of automations in the first few years.

However, we found that the default setup for the UiPath Orchestrator in 2018 didn't have all the features we needed to administer it to our customers. We had to build custom solutions in-house, but they've released many new features in UiPath Cloud that simplify management.

I rate UiPath 10 out of 10. The executive support team and customer success team have been great. All of them play a role, and they're super knowledgeable. If they can't solve your problem, they know who can and connect you with them quickly. We've leveraged them extensively and will use them more over the next couple of years as we finish our cloud implementation.

There are still many features we don't use, and we constantly go to them for guidance and help on how to use them best and what they've done with other customers. They provide tons of great insight and have a solid network.

We didn't have a low-code automation platform. We developed most of our automations using PowerShell. We didn't have citizen developers, but most business users would use Power Automate. Back then, it was known as Flow on the Power Platform.

Our corporate leadership decided to bring in UiPath. It wasn't an IT decision. They wanted something they could start using for their daily tasks. They didn't think we had something that could automate things well, and PowerShell is limited from a scripting and API standpoint. They wanted to automate things in SAP, and the APIs and other things are locked down in a custom shop like ours. We can't integrate with our environment in any way we want, so we need something that can interact through the interface. UiPath does that. It can click and type everything through the interface.

The leadership started the process. IT got involved and supported it. Since then, we've helped it grow throughout the company. It's not just finance anymore.

The initial setup was complex because UiPath didn't have many pipelines built in. We had to build custom pipelines for the technology we use. It was TFS at the time, and now we use Azure DevOps. I helped with the VDI setup. For unattended automations, you must have a platform or system they can run on. We had looked at doing HDRs—high-density robots—that UiPath.

Due to applications such as SAP, it couldn't run on a server-side setup. It had to be on a desktop, so we used a VDI for every bot we created, and I helped create the user policies for our accounts and device policies for each VDI. I also set up all the installations and the presets. I helped set up a framework for that over the first year, from 2018 to 2019. We smoothed out the process from there. That was something we had to do on our side. It will be unique for a customer depending on their environment.

We used a partner during the initial setup.

The leadership is pleased with the outcomes. With Insights, we can show them how much time we're saving with each process. We document savings in hours rather than monetary terms.

I rate UiPath 10 out of 10.

Our primary use case involves automating low-hanging fruit processes such as daily reporting, order entry, and AP invoice processing. We are a printing company with 33,000 to 34,000 transactions a year, and 70% of these are repeat orders that we aim to automate.

Implementing UiPath has increased speed and accuracy, freeing up staff to focus on higher-level tasks requiring creativity and attention. It has resolved the issue of order entry delays, reducing a process that could take two to four days to just five minutes.

The document understanding feature has been particularly valuable as it recognizes and extracts data from invoices and purchase orders, greatly saving time.

The fast growth of UiPath can be difficult to keep up with, so more informative sessions or webinars showcasing potential returns on investment for specific industries would be beneficial.

We started using UiPath in 2018.

In general, the stability of the solution has been positive.

UiPath has been able to keep up as our environment grows.

The customer service and support have been great, consistently providing answers or guidance.

We did not use a different solution previously. We chose UiPath for its user-friendly Studio and comprehensive resources.

We initially partnered with a company that was not the best fit, and have since switched to a more suitable partner, greatly improving our experience.

We have yet to realize a significant return on investment due to initial partnership challenges. However, we are now on track with a new partner.

Pricing is fair. That said, it requires justification for returns due to a tight budget.

I would rate UiPath a ten out of ten.

Our primary use case for UiPath revolves around document imaging, specifically scraping data off documents and digitizing them. We only use it in our accounting department and haven't expanded it to the rest of the company. We've seen some success with the projects on the financial team, but we might be resource-constrained to get other departments involved. It's hard for them to adapt to new technologies.

UiPath has improved the accuracy of data entry from our invoices. Processing thousands of invoices is time-consuming. One outcome we've achieved is expanding the data collection from the invoices. They were only capturing dollar amounts, but these invoices have tons of other information that was just going to waste and could be analyzed. Now, we're capturing the data and analyzing it. It will be a significant benefit, considering how we do business.

We've advanced our green initiatives by recycling invoice paper after digitizing it and reduced the costs of pulling this information into our system.

The most valuable feature is the general automation that UiPath offers, especially in improving data collection which allows for a more comprehensive analysis of information on invoices.

There is a need for better autopilot features to enhance the functionality of UiPath.

I have been using UiPath for about a year.

UiPath is stable so far.

UiPath can scale as our business grows.

Customer service and support have been excellent. I would rate it highly for their responsiveness and supportiveness.

Previously, we used a service that scanned documents and sent them back in EDI format. We switched to UiPath because the previous solution couldn't handle certain document images unless they were in native PDF form.

The initial setup seemed straightforward.

We used corporate for the setup. Corporate used UiPath as a partner for support.

While there hasn't been a financial return on investment yet, the team is happier not having to manually enter invoices, which is a qualitative benefit. However, I foresee a financial return in the future.

UiPath's licensing seems straightforward, and the pricing is comfortable for the corporate leadership. They made an outright purchase, knowing the full cost and expectations.

I rate UiPath 10 out of 10.

I currently work for a data center company serving real estate clients. Our primary use case for UiPath involves large-scale automation using Document Understanding to process invoices.

I have two models running. One is for our general invoices, including everything we pay for people coming on-site at all data centers worldwide. There's a separate model for utilities. Accuracy in our utilities spending is crucial for our data center business, where power costs are passed on to customers.

Currently, we still use traditional machine learning from when we initially developed these models three years ago. However, we are creating a company strategy to implement GenAI and deal with the legal implications. GenAI is something we're considering as an enhancement to our document processing and data collection. We're still trying to figure out how that happened. We're figuring out which documents and data to include in an internal model and draw conclusions from.

When working with data, our top priority is ensuring that the data is updated, accurate, and well-maintained. There's a structure involved because a ton of our information is in SharePoint, which is a mess. We have two SharePoint sites for every employee.

Some large-scale invoice-related tasks were overwhelming our existing processes and attempts to handle them manually. We are in the data center industry and dealing with all these technology companies, but many processes in the real estate business are a bit more outdated. Many of our people are comfortable working in Excel, and some teams are highly siloed. One significant challenge I've faced as a UiPath developer is acting as an evangelist within the company. We want to demonstrate the platform's capabilities and get buy-in from these different teams across the enterprise to raise the level of what we're trying to do.

UiPath has been helpful with that first step of getting the information off the invoice. I've been learning and expanding my skill set on the workflow side. Many of our automations have a workflow with a human in the loop doing manual review. I look forward to automating between different departments, and that's one thing I want to develop at this conference.

We used to bring on seasonal contractors during peak seasons, and now we no longer need to do that because the existing staff have more capability. That was a big thing when we started. Our accounting team was so busy for the two weeks before and the one week after closing. There was a tiny window when they could engage with any process improvement or look ahead at what we could change because they were so busy keeping up with how things work. We've freed up these people who are intimately familiar with our business and give them more time to apply that knowledge instead of filling out forms.

We were processing about 2,000 invoices a month when I started. Now we're up to about three thousand. It took about 15 minutes per invoice to process because there were so many different elements. Working with Yardi is challenging. There was a big issue with getting these into Yardi and uploading them in batches. If one invoice in the batch failed, it would kick them all out. We spent all this extra effort troubleshooting and doing all of this.

Now, the bot can execute this work and upload them individually. If there's a single error, it can be isolated and kicked out as an exception. Someone can manually review it, and the bot can keep putting the rest of the invoices into the system. We've also had a great ROI on the monthly reporting. We generated reports from around 50 sites every week and then distributed them to a long list of different people on different projects. It's straightforward to do and only requires 10 clicks for each report, but it saves massive amounts of time for people. Now, all I need to do is maintain a list of who should get the emails and what projects need reports to run.

I love developing automations. I often directly help people by improving the part of their job that is time-consuming and dull. In addition to saving time, we reduce errors caused by manually typing things in. I've demonstrated that in different departments at our company.

We won an award for our ESG efforts. I developed an automation to help us report our ESG metrics because all of these customers want reports to give their shareholders about green initiatives. We wanted to take all the data on energy reductions in data centers and distribute it to each of our customers. We had a very complex template that we wanted to iterate on until we delivered the report. I developed a bot that could generate the source data and template of these files for our customers by data center and aggregate them.

Before I joined the company, they had no automation solution. They tried to do this with mail merge, which struggled because of the variability across our sites. We wanted to achieve greater complexity and offer this table of information when it's available or update it when the final file we're generating varies significantly. We wanted to be able to convert a Word doc into PDF format and aggregate all of those different PDFs at the site level and aggregate those per customer.

UiPath's Object Repository was huge. I could build these libraries because our industry works with many of the same systems. It's hard to integrate with Yardi's core CRM, and many of our automation efforts focus on getting information in and out of that system. The ability to build these libraries of reusable selectors has dramatically benefited me over the past couple of years.

I'm excited about all the new stuff around document understanding because I think that is a large area. We can continue expanding and delivering large-scale automations.

The messages and alerts that Orchestrator generates are a little overwhelming. I'd like them to be filtered down to the most actionable things I need to look at. For many things, we set up an automation that will send an email summarizing things to the stakeholders for the automation. With any of these types of things, you're generating notices, emails, and things, so you want to focus on some things that need your attention.

I started using UiPath while interning and pursuing an MBA. I've always been a huge fan of Excel, Visual Basic, and automation in general. I've been in my current role for about three and a half years, but I began tinkering with UiPath for a couple of years before that.

I have not experienced any performance or uptime issues with UiPath.

In my current role, it's been challenging to demonstrate the need to grow and bring on more developers. We're processing a high volume of invoices, but the rest of the business has around 200 employees. We have large capital expenditures building these data centers but not a high volume of back office processes.

I have not necessarily been able to evaluate what it would look like to grow with 20 automations. We could keep a steady pace of new smaller-scale processes and look for new large-scale opportunities, especially with some of these new technologies. However, I don't think we'll be a large enough business to need these massive deployments.

I rate UiPath support 10 out of 10. I have submitted tickets periodically for a specific issue, or when I'm trying to solve a new problem, I haven't faced before. I am the only UiPath-focused employee at my company. I can work on iterating, researching, and troubleshooting.

I've always been able to put in a ticket and get on a call with some people. They're able to connect me with someone and help me understand either the problem I'm facing or the fact that we've been able to have more calls recently about new potential. The online community is also an excellent resource for finding ways to approach and solve problems. Their support has been great.

Prior to UiPath, there was no different solution implemented at my current company. At a previous company, we conducted a comparison between Automation Anywhere and UiPath and opted for UiPath due to its greater flexibility, capabilities, and entry offerings. At the start of my career, UiPath was one of the first to offer free online training and a lower entry point for businesses just starting out.

Automation Anywhere followed suit. While reviewing them, I built the same process in both systems and presented it to our executives. Automation Anywhere seemed focused on the financial industry. It had some excellent features if that's what you were what you cared about, but I greatly preferred the UiPath's general flexibility, capabilities, and breadth of integration. I've done some small-scale things with Microsoft Power Automate. That tool is hard to work with. They try to make it easy for non-technical people, but it means that I have a hell of a time trying to get it to do what I want.

The initial setup was straightforward, and it was conducted in-house. We host our own virtual machines for running automations and we are a cloud customer.

The implementation was done in-house.

We've seen the greatest ROI from large-scale invoice processing, but small-scale operations have had great returns. Before automation, we were processing 3,000 invoices monthly, which took 15 minutes each. It still requires time to review them in the Action Center manually.

UiPath's pricing and licensing have been reasonable and manageable for us. Despite challenges in constantly monitoring SharePoint folders, UiPath has worked well within our resources. We have a fully dedicated, unattended license for our invoice processing, which needs to be a top priority and is always running throughout the day. We have another one for all of our other scheduled automations, and we've been pleased with that so far.

I rate UiPath 10 out of 10. I'm incredibly impressed with the pace of new features that have come out. I have been working with UiPath for six years since I graduated college, and I'm blown away by what's coming out every year.

The primary UiPath use cases are document processing and using automation solutions to eliminate repetitive tasks in administrative data entry.

Automation has helped our CoE understand the administrative structure and returns. It's a promising tool. We've already seen returns on the automation side, and we're beginning to explore GenAI. It helped us free up staff by taking them off repetitive tasks and transferring their focus to more important tasks.

The automation and the significant return on investment it provides are valuable.

I want more flexibility in licensing and how we can use AI units.

UiPath seems pretty solid.

UiPath has grown with us. We started on-premises and switched to the cloud, giving us greater flexibility.

I rate UiPath support eight out of 10. UiPath support is pretty good. It's adequate when needed. Fortunately, they have UiPath Academy and other information out there, so you don't need to use it often.

We were using ABBYY, but I can't compare the two solutions because I joined when we were transitioning to UiPath, so I don't have much experience.

UiPath provides a significant ROI in saving time and improving the employee experience.

I rate UiPath 10 out of 10.

We primarily use UiPath's AI features to pull information from chatbot conversations with insurance providers and identify decisions made.

Implementing AI and automation has allowed us to collect information quickly. We have deadlines that we must meet for our clients, and AI has enabled us to get that information without manual intervention. There are delays while we wait for insurance to pay for claims, and taking humans out of the equation enables us to be as productive as we want.

We've been testing this emerging technology, and we're excited to see it continue to grow. So far, we've been successful in connecting, having interactions, training a language model, getting responses, and using that information to make decisions in the workflow.

The most helpful features are human-assisted and unattended bots. These features help us drive the workflow in the direction we want it to go. It allows staff to utilize their talents and the information they need. We can remove this small conversation and let them focus on the more important work.

Data integration is the biggest opportunity for improvement. We need quick connections to our complex in-house databases to set up automations more efficiently. It's time-consuming to connect those large databases.

I have been using UiPath for about a year, while our organization has been using it for about four years.

UiPath's stability is excellent, and its ability to forecast stability is improving. We have a lot of stable automations running.

Scalability is a challenge as we're a large enterprise, but task mining helps identify issues and pushes automation into the enterprise effectively.

I rate UiPath support nine out of 10. We have strong contacts with UiPath, and an in-house team managing implementations has built a really good relationship with them.

I am not aware of any solutions we used prior to UiPath. We developed our own home grown tools and UI automation.

We've seen a significant ROI by reducing the number of full-time employees. We haven't calculated a precise figure, but it has been pretty successful, and we believe it is promising.