UiPath Platform Reviews

We use AI mainly around sales processing and document understanding. Our current use cases involve traditional automation, processing different orders, order formats, languages, and language translation, and creating actual orders in any ERP solution.

We've done a Communications Mining POC, and we think that's promising, but we haven't used UiPath's process mining because we have another solution for that. 

We were already using a competing automation platform when we implemented UiPath. UiPath is a more cloud-based solution. We're biotech regulators, so we're trying to adopt new innovations as quickly as they are released. Regarding challenges, we're trying to simplify and automate processes to achieve a higher value and make problem-solving more seamless.

We engage our employees in automation in two ways. At the enterprise level, it's more about making it easy for there to be a centralized intake of opportunities and focus on the value of what comes through. Citizen automation is about empowering and training them on how to use it so they can build more. 

Our organization has experienced productivity increases, financial savings, error reductions, and streamlining of many processes in finance and accounting with UiPath automation. It has helped free up staff time so that they can focus on more value-added work, and when automations don't function as expected, employees can be upset because they don't want to return to previous manual methods.

I don't know about shareholders, but employees who learn to build automation can do more value-added work. It makes them happy. Customers within the company can have people in their teams spend their time on more value-added work, and they have better transparency.

RPA is always good, and UiPath's Document Understanding is interesting. We used the old model, but the new modern Document Understanding is much easier.

UiPath could offer better support for operations. It has all these cool features, but when you still need to build and run these bots. You need to have more features that make it easier to run bots, and they require fewer people to maintain. 

We have used UiPath since 2020, so it has been nearly four years.

The solution is stable, with, for example, only a thirty-minute outage in three years.

It is scalable, but successful scalability depends on how you build automations.

We have premium support, which provides excellent customer service. Our technical account manager is amazing, and that's one reason we keep paying for premium support. 

We previously used Automation Anywhere and switched to UiPath because it was easier for developers to use and could integrate with more products.

It was complex because UiPath didn't have a biotech-specific offering. We were the first biotech company to use this, so we had to develop a product that would work for companies under regulation. We needed something called delayering. We had to educate UiPath on what it means to do this for health care and biotech.

UiPath helped us save around 500,000 thousand hours. Over our entire automation journey, that amounts to an estimated $25 million worth of productivity hours.

The pricing is very expensive, making it challenging to continue using UiPath when competitors like Microsoft offer cheaper alternatives like Power Automate. Why continue to use UiPath when you're paying three to five times more? 

I would rate UiPath a nine out of ten.

One of our simpler UiPath use cases involves running an SQL query, copying the results into a spreadsheet, and then emailing them to the appropriate people. 

We also have a third-party system for parking at the hospital. Visitors need to fill out a web form, and the automation process kicks in once the web form is filled out. The data is input into a database and then automatically processed in bundles. The form is filled out automatically for them, and it batches every thirty minutes. 

UiPath helps us automate many tasks people do daily that they don't want to do. They can spend that time on tasks that humans are better at, such as being creative and thoughtful instead of copying down information, filling up databases, making spreadsheets, sending emails, etc. I have one automation that normally takes me about four hours to do. 

Automating certain tasks can potentially save employees approximately 60 hours per week. This was particularly true in our parking pass processing. People used to get overwhelmed with that task, so automating it saves significant time.

Computer Vision helps us read and process handwritten documentation. That will be incredibly important. The unique aspect about UiPath is the robustness of the Academy that's built into it.

UiPath could be more intuitive in how it formats strings, variables, or databases. This can sometimes be difficult, even for someone with a computer science background. Additionally, some tasks require a team effort as one person can get overwhelmed or discouraged.

We are only about a month or a month and a half into using the solution.

The stability is generally good, but it can't really be driven without support for prolonged use.

Scaling UiPath is easy. You just purchase more bots.

Previously, we used Power Automate and a proof of concept for Automation Viewer, but we decided to switch to UiPath because it has a better deployment model. We use the Orchestrator. It's a server that we can add our robots to and configure them. 

UiPath is good at handling the sequential flow of processes. The way it breaks down sequencing is commendable. It was shocking how disorganized some of the other solutions we reviewed were.

We are seeing a good return on investment potential, but we haven't fully realized it yet since we are only a month and a half in.

I rate UiPath eight out of 10. 

I have used UiPath for very few projects. My go-to tool when it comes to automation is Power Automate. The reason for that is that I work in the Microsoft 365 environment, so Power Automate is better connected than UiPath.

With UiPath, I helped some organizations in my company automate tasks like data entry into systems such as SAP. 

I like UiPath. I enjoy working on UiPath. It has a lot of different features to control, especially related to desktop flows. I helped some organizations in my company automate tasks like data entry into systems such as SAP. They had Excel files, and all that data needed to be input on standard screens in SAP. It was taking a fair amount of time to do it by hand. We created a flow that transfers all that data, interacting with the screens in SAP, and uploads that information where another alternative, like an API or mass upload tool, was not available.

It is pretty easy to build automation in UiPath. We could easily implement end-to-end automation. I was consulting a group within my company. I was helping them build the flow. For them, it was a game changer because they would have spent several man-hours trying to transfer all that data into SAP, creating all those SAP items. After that, they were not only able to complete the task at hand; they were also able to replicate and create more automations on their own because they knew how UiPath works. They learned a little bit more and were able to continue to expand the other processes they had.

We were able to realize its benefits quickly. It took us a couple of weeks to finalize the flow, but once it was built, we were able to start seeing the benefits. It definitely saved time.

I like the way that I can reference specific objects on the screen, like a specific text box, and add a value to it. The capability that UiPath has to recognize elements on the screen is what I found most useful at that time.

UiPath has a lot of courses for easy learning. There were several courses that I offered to the organization I was helping. I myself went through several online resources that UiPath offers to figure out things.

UiPath should be less sensitive to changes in the existing UI of the system we are trying to manipulate. If it was more intelligent in adapting to changes in the user interface and the tools we are trying to manipulate, it would be beneficial. If the UI changes or a label is changed, sometimes the whole flow breaks. Identifying where the flow breaks requires going into edit mode and making modifications. It might be quite extensive work with the new, updated UI.

I have been using UiPath here and there for at least two years. It is a part of the solutions that my company offers, but I have not used UiPath as much as Power Automate.

It performs well. I do not see any issues there.

I use Power Automate on a daily basis. 

It was easy. It took us about a few weeks for ideation, selecting UiPath as a tool, getting everything set up, building the flow, and testing.

In terms of maintenance, users continually review and upgrade their flows. They can reuse the existing flows to create new ones.

I am not familiar with the pricing. I worked for an organization where the UiPath was available, so I do not know what the pricing is.

It was through an internal community that I connected with the organization for which I did the automation, and that is a great advantage. They were looking for people to help create automation. I was curious about UiPath, and I wanted to learn. I raised my hand to build that for them. An external community or a learning community is something that has proven its value by creating synergies between people who do not know and people who already know a little bit, allowing them to get together and grow.

In my opinion, RPA solutions are alternatives to digital transformation. Digital transformation is a big project. When you do not have access to those big budgets or the structure to get into new capabilities on an existing system or implement a future system, that is when you go to RPA to supplement the digital transformation. If the use case is not eligible for the big capital investment or the big project investment, you go through the route of RPA.

I would rate UiPath a nine out of ten.

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.

Positive

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.

We use UiPath Platform for automation. We implemented automation across departments with this solution. We use robots to automate a process. 

We handle both attended and unattended automation with UiPath Platform. We do not use any AI integration features in UiPath Platform.

UiPath Platform is easy to use, and the user interaction is good.

UiPath Platform allows for code-free use, but I mostly write code.

The support process of UiPath Platform can be improved. When we get stuck somewhere and need help from UiPath people, it takes considerable time to receive assistance.

I have worked with UiPath Platform for around two years.

I have not experienced any stability issues with UiPath Platform.

The scalability of UiPath Platform is good. We deployed the automation in departments, which helped us save resources, money, and improve quality.

The support needs improvement. 

I also worked with Blue Prism. When comparing UiPath Platform to Blue Prism, the main difference is the user-friendly aspect. UiPath Platform is easier to use.

UiPath Platform helps save time, increase performance, and decrease human errors. While quality is not always accurate, time and money savings are significant.

UiPath Platform is a cost-effective tool.

In terms of the learning curve, it was initially difficult but became manageable once we learned the tool and started working with it. It takes some time and effort in the beginning, and then you get the results. It saves a lot of time and also reduces costs.

I would rate UiPath Platform an eight out of ten.

We are primarily looking to solve business challenges related to processing unstructured documents.

Currently, we have not realized the business outcomes as we have not implemented the solution yet. The goal is to increase efficiency, throughput, and accuracy. UiPath AI and automation have not yet helped free up staff to work on other projects or tasks. In terms of environmental, social, and governance solutions, it is not applicable.

The Studio and the Test Manager have been valuable as they made testing with QA easier. We've been able to rerun numerous test cases quickly. From the UiPath platform overall, I find these features valuable.

The product documentation needs improvement as it tends to be self-contradictory and sometimes hard to access since we are on an older version. 

There is also a need for more consistency in product support and customer service.

I have been using UiPath for five years.

UiPath has been pretty stable since we are mostly on-premises. However, the stability is to be determined when we move our full infrastructure to the cloud. Outages could occur with SaaS solutions.

It has scaled with us efficiently despite the initial complexity in understanding licenses, runtimes, and utilization. No significant issues have been encountered yet.

There have been ebbs and flows with customer service. We are at Premium Plus, now called Enterprise Success. Initially, there wasn't much value, but there has been some improvement. Dedicated support provides more assistance and better outcomes.

Neutral

I'm familiar with Automation Anywhere and Blue Prism, each of which offer different pros and cons. UiPath, being the market leader, differentiates itself with its capabilities and portfolio. It is easy to use from day one, flexible, and their vision is helpful.

I can't provide specifics as to ROI. That said, in general, we achieve financial benefits and a positive ROI on our implementations most years.

Pricing and licensing are challenging as they can be difficult to understand. They make it hard to determine utilization and necessary licenses for runtimes. Comprehensive components need to come together for a clear picture, making renewals and contract negotiations complex.

We have considered Automation Anywhere and Blue Prism as alternate solutions.

I would rate UiPath a seven out of ten.

I use this solution for automating customer processes. I have been working with this for almost seven years and am responsible for automating various business processes across different industries such as finance, telecommunications, and airlines. I have experience working with numerous sectors and do not use it for personal reasons.

Document Understanding allows me to track information not only from structured documents but also from unstructured documents through artificial intelligence and machine learning techniques. These are excellent tools. Additionally, the process understanding enables me to track and manage document processing effectively. Ease of building automation includes utilizing tools to record the process and generate the initial process design document.

I have just generated the default pilot. I believe another option for the tool could be voice interaction. For example, similar to using assistants like Alexa, it would be beneficial to integrate voice commands with the UI to create an Excel spreadsheet and populate a data table.

I have been using the solution for seven years.

I have experienced stability issues.

I have experienced scalability issues.

I would rate customer service a ten out of ten.

Positive

The number of solutions we select depends on client needs. My company uses various software platforms without preference, and it depends on client requirements and objectives.

The initial setup is efficient if all infrastructure requirements are met, faster than Azure's requirement. It could take about an hour.

We have our checklist that describes every document. We ensure everything is checked. We are a consulting company, and we have expertise in this field.

If you lose higher Wi-Fi parameters, it saves additional time. The license cost is slightly higher compared to other providers, yet the benefits are justifiable.

The developers are very client-focused, always looking for feedback and adding additional value in every version. I was one of the first UiPath MDPs, and it enables a lot of learning opportunities. If you're keen on learning, you can benefit greatly.

UiPath is accessible with various language options, breaking down communication barriers. Many developers benefit from this, especially since it's free. Fatigue can lead to errors, but automation helps reduce such issues, particularly in financial processes. In terms of digital transformation, UiPath accelerates the process and reduces costs. 

Overall, I believe UiPath is the best tool available. I rate the overall solution ten out of ten.

We currently use UiPath to process birth certificates. One of my tasks was to apply OCR to the birth certificates and use a named entity recognition model to extract details like the names of the individuals, parents, and the place of birth. The project requires us to handle certificates from all 50 states, and every state uses a different format. 

We're supposed to be doing intelligent automation, but we're not there yet. I work in the applied analytics and statistics section, and we're supposed to find ways to inject more advanced analytical methods into some of these places where we can automate. Our IT department has a CoE that conducts intake processes. They use Automation Hub to review each process, and the executive governance board votes on it. I don't know how they decide internally because I'm not part of that. 

Automation through UiPath provided a framework and a low-code solution, which generally improved the process. It reduced the burden on the workers, freeing them to do what they wanted. 

It is also utilized in identity governance, especially within IT environments. For example, say I want to install a particular piece of software on my computer. There's a process to request access, and it goes through an approval chain. Ultimately, it gets to someone who has to click a button or provision an account. Someone will get an email and copy-paste the stuff from the email into another system and click "provision." 

And when an employee leaves or switches job roles, they no longer need access to a particular system anymore, so you must remove that access as soon as possible. Automation helps. Governance is one area that we would like to use it in more.

UI automation is helpful for interacting with legacy systems, mainframe systems, and various web applications. Someone might use all those things during their jobs, and many of them don't necessarily have APIs, either.

Although improvements have been made, such as auto-healing, there is room for improvement. Changes in the UI can break automations. If you upgrade from Windows 10 to 11, you may need to rewrite some of those UI selectors completely. That is probably the biggest weakness that I can think of.

I have been using UiPath for four or five years.

The solution can be fragile, but there have been significant improvements over the years. The unified target framework, which considers strict, fuzzy, and image matching, helps to stabilize the application somewhat.

UiPath has been able to perform as our organization grows or as the demands on UiPath increase.

In my previous job, I interacted directly with UiPath support, and they were always effective. Currently, support is accessed through IT, which escalates issues if needed, so I have less direct interaction with customer support.

Positive

I've used Python and VBA and experimented minimally with Selenium, but they're not as strong when it comes to UI automation. I've also used Power Automate for Microsoft products. Sometimes, I want to automate Outlook, but I don't want to ask the security to enable the UiPath activity to pull emails. 

We've saved time and reduced human error. 

I rate UiPath eight out of 10.

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.

Positive

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.

We primarily use UiPath to move data and consolidate data formats efficiently. We are involved in claims management within healthcare. We are also exploring DevOps tooling and CI/CD pipelines, and automated testing.

UiPath has significantly improved how we claims. We provide this product for our customers directly, so we want to ensure they reap the benefits of the automation program. We serve as a product team and make sure that our products are directly open to the customers. Although we are not extensively using AI yet, there is significant interest in the org. We aim to recommend automations to users and intend to develop AI capabilities down the line.

Our teams are heavily using integration service, especially following our cloud migration. Having further insights and program visibility is crucial for longevity.

It would be helpful to be able to double-click and drill down into the data we see in the APIs and get a little more interactivity, especially in the Studio and Studio Web. I want to be able to pull in fields dynamically.

I have used UiPath since 2021, so it has been about three years.

UiPath is relatively stable. I've seen a few bugs in some of their newer tools and Integration Service. There are some issues with feature clarity across platforms, but it's not necessarily a stability problem. Occasionally, cloud may experience downtime, but stability is always reliable. 

Most of the scalability issues from an implementation fall on the customer's side because they don't understand how to scale out their VM presence or set up systems in a way that relies on siloed teams. They're using it on-premises and have to manage the instance with teams outside of their automation team. I haven't had any scalability issues in the cloud. The cloud might go down once a year, but I haven't had issues scaling it, and if it has an outage it's normally not long enough to make a dent.

I rate UiPath support seven out of 10. UiPath's support is quite reliable and significantly better than most alternatives. Some competitors don't get back to you or have meaningful solutions.  

There's room for improvement. They could make their online support pages easier to navigate. They're integrating support with Automation Cloud, which will make raising a ticket more seamless. When you open the ticket, it should automatically provide them information about your deployment.  They're good about following up with you, but getting solutions for some products takes time. 

Neutral

I have always worked with UiPath, sometimes using other platforms such as Salesforce and Power Platform when they better fit specific needs. However, they are not as suitable for making enterprise scale automation.

The on-premises deployment when we started in 2019 was somewhat complex. It's different for every customer, whereas the cloud is consistently distributed the same way, and you can customize it for your business.  

We work with an implementation partner for staff augmentation and architectural support, with a proactive offshore development team experienced in best practices. 

I rate UiPath eight out of 10.