UiPath Reviews

I am a developer, and I use UiPath to extract PDFs for invoices and logistics in the banking industry. 

UiPath can be deployed either on-premises or in the cloud, depending on the customer's requirements.

There are times when the logic is difficult, but the majority of the time, it is easy to build automation using UiPath.

UiPath enables us to implement end-to-end automation, which is essential for our customers. We gather all the requirements from the customer, analyze their feasibility, and proceed to the development phase where we build bots according to the customer's needs. After that, we move on to User Acceptance Testing to ensure the bots meet expectations. Finally, we deploy the automation into production.

UiPath aids in enhancing organizations by cutting down costs and saving time. Without UiPath, a task like collecting and uploading information that typically takes humans around 40 minutes can be completed by the UiPath bot in just ten minutes.

Our customers primarily use UiPath for cost savings.

In addition to saving time, UiPath also eliminates human errors by consistently processing 100 percent of the tasks each time without requiring any human intervention.

UiPath helps reduce our customer's on-premises footprint.

UiPath Academy is excellent for learning about the solution's capabilities and how it works, especially in the beginning. It provides end-to-end courses and certifications for both beginners and advanced users.

UiPath accelerates digital transformation and reduces costs by eliminating the human element. However, this transformation does require IT application support for configurations and security.

UiPath's most valuable feature is its ability to view and extract any data throughout the entire development process in the automation framework.

The document understanding has room for improvement. 

I have been using UiPath for three years.

UiPath is extremely stable and that is why customers ask for the solution.

I rate UiPath's scalability a nine out of ten.

The technical support is good.

Positive

I previously used Microsoft Power Automate. When comparing it with UiPath, one significant difference is that we can use UiPath on a local machine to easily build a process, upload it, and create schedules effortlessly. Microsoft has an advantage in the cloud, but it is not as effective on-premises.

The number of people required for each deployment depends on the complexity of each project. For more complex projects, two to three people are required, and it can take up to three weeks to complete.

Our customers experience a return on investment when using UiPath, owing to the time saved in performing tasks and the improved accuracy compared to manual efforts.

We can start to see value after one month of using UiPath.

There are two versions of UiPath; the first is the free community version, which is limited, and the second is the premium version which requires payment but is recommended for large-scale productions.

UiPath's cost is acceptable.

I would rate UiPath a nine out of ten. UiPath is reliable and accurate.

The maintenance is easy. We only need one person to monitor and maintain UiPath.

I recommend trying the free community version first to ensure that it meets the organization's requirements and then consider upgrading to the premium version in order to handle larger projects.

We use the solution as an automation platform that even those without coding knowledge can use for automation-related tasks, such as PDF and Excel extractions. We're an IT services provider and use the tool for insurance data and other client requirements.

UiPath significantly improved our organization's productivity and strengthened our client relationships.

The solution reduces the cost of digital transformation, and we can now expect to see a 300-400% ROI. Doing so did not require expensive or complex application upgrades or IT support. The complexity of performing automations depends on the project size and ranges from very easy to moderately difficult on larger projects.    

The product reduced human error, improving the quality of service we can offer our clients and resulting in higher output accuracy. 

UiPath freed up employee time due to reduced errors, less human involvement, and less manual work. The time saved depends on the project size, but generally, it's approximately 40-50%.  

UiPath is straightforward and easy to use, even for those without coding knowledge. 

The solution's drag-and-drop functionality and templates save a lot of time.

We can easily build automations, removing humans from the loop, reducing human error, and saving time, to deliver positive outcomes for our clients.  

The solution enables us to implement end-to-end automation, which is excellent for reducing human error as there is no human involvement. It also reduces our dependency on humans and rapidly provides us with extracted data without manual work. End-to-end automation is essential because it allows us to carry out projects even if no team members are present, making it easier to conform to client deadlines.    

It would be good if the product could work locally, without depending on the internet, as connectivity issues can cause problems.

We have been using the solution for two years. 

The solution is highly stable; I rate it 10 out of 10 for stability.

UiPath is very scalable; I rate it 10 out of 10 for scalability.

The technical support is excellent and responsive. 

Positive

UiPath is the first RPA solution I've ever used. 

I was involved in the development, testing, and deployment. The initial setup was neither remarkably straightforward nor complex; it was moderate.

Our ROI is in the region of 40-50%. 

The product is very affordable, not costly at all.

The solution is very cost-effective for us.

We evaluated a few options, including Microsoft Power Automate, but it's a little more expensive than UiPath. UiPath also looks more modern, has a vast developer community, and excellent customer support.

I rate the solution 10 out of 10. 

Being a part of the UiPath user community is valuable; sometimes, when we encounter issues or have queries, we can quickly get a response from the community.  

My team and I have used the vendor's UiPath Academy courses to improve our skills and knowledge of the solution. This was especially useful when I first started to use the tool, as I needed to gain experience in RPA. Anyone can take a UiPath Academy course and learn to use the platform without any additional hassle or training, regardless of coding skills and previous experience.  

My advice to others evaluating the solution is that I rate it very highly, and it's great for automating manual work. 

I use UiPath to automate getting the relevant data from Excel and PDF files and for normalizing the data.

It helps reduce human error in data retrieval from PDFs and Excel documents. We get accurate output that is easy for us to make decisions on, helping us move forward to next steps. It makes us more productive.

End-to-end processes are useful for us because they give us positive output and increase our business productivity as well as staff availability. It saves a lot of time and human resources.

The amount of time an automation saves depends on the complexity of the task. Some save a lot, some save less, but it works well for us.

Automating tasks makes them more scalable and makes our client relationships better. We are able to provide solutions in less time than we expected.

The most valuable feature is the ability to retrieve data from Excel files, including filtering the data. It is also straightforward and easy to navigate when building automations and makes our tasks easy to perform. It is very easy to use without any prior coding knowledge.

Another important aspect is the UiPath community. It's critical when you face an issue. You can post it to the community and there are always people there who are ready to solve your issues. It works well in every scenario, and I would give a 10 out of 10 to the user community.

The UiPath Academy also helps a lot. I did a course last year because I wanted to know more about the new features. For anyone who wants to improve their skills related to UiPath, they should do courses from the UiPath Academy. It's very helpful.

The user interface needs a little bit of improvement because it looks a little cheap due to being a very old tool. Otherwise, it works well.

I would also like to see the ability for applications to work offline. Currently, they only work when online. If that is possible, that should be included in a future release.

I have been using UiPath for the last two and a half years.

The stability is good, a 10 out of 10.

The scalability is also good. I give it a 10 out of 10 for scalability.

Last year I faced an issue related to UiPath and I posted a question on the developer community forum. After approximately two to three hours I got a response and that was all I required to resolve the issue.

Positive

I used Microsoft Power Automate. I switched because UiPath is cheaper and it has a large developer community.

It gives a great ROI. If you invest $1,000 in a project, it returns approximately two to three times, or $2,000 to $3,000. 

The time it takes to set up an automation depends on the project size or complexity. It can take 15 or 20 minutes, and sometimes, it takes hours or a whole day.

Sometimes maintenance is required because it slows down due to new features or an upgrade going on. 

We have about 10 to 15 people maintaining things, doing testing or helping when anyone faces an issue. We have 200 to 300 end-users in our organization.

Our company uses the solution for financing, accounting, and commercial operations. Right now, we are automating the lowest-hanging fruit. We look at people or personal productivity and automate their desktop tasks. 

We currently do not use AI functionality. 

The solution saves our company 10,000 hours annually. Automations have removed menial tasks from people's desks so there is instant gratification.

Studio and StudioX are really powerful tools. From the development side, business users have realized much success and have made great strides with StudioX because it is easy to use.

Automations are really easy to build with a minimal technical background. For example, my background is in accounting and finance but I am the manager of an automation team so that speaks to how easy it is to learn and develop. 

It would be useful to have co-authoring because we have many staff members working on the same project. 

I have been using the solution for four years. 

The solution is fairly stable. We have to perform maintenance on things we are doing and see some infrastructure issues for on-premises users. Many of these issues would be addressed if we switched to the cloud so that is under consideration.

I can see the solution's scalability. I think you need the right organizational buy-in for scaling but there isn't anything that the solution should be doing differently. 

The community is great and we learn so much there. We would like the community to bring back in-person user groups because we found a lot of value in knowing and connecting with other customers in our area. But, the community as a whole is awesome and invaluable. 

When we started our journey with the solution, we utilized the Academy for training. Since then, we have used the Academy to train three new team members because it quickly gets them up to speed so they can start developing. 

Technical support is good and we utilize it a lot. Sometimes it takes a little while to hear back from support. Though we understand, it also causes us heartache when tickets are automatically closed without a response. For example, sometimes we contact support on a Friday and the ticket closes on a Sunday which does not give us time to review our email and can be difficult. Otherwise, we like the technical support provided and rate it seven out of ten. 

Neutral

Our company did not previously use another solution. 

I was not involved in the initial setup. 

The price is high in comparison to Power Platform that Microsoft provides as part of its enterprise license. 

The pricing can be a bit confusing because many new products have been added. We just renewed our licenses and got all new SKUs because products have changed so much since our initial implementation.

I was not on the evaluation team but I do not believe other options were evaluated. The solution was chosen because it was a known leader in the industry.

The solution is great, works well, and is learnable. Users will be able to pick it up easily. People who are interested in change will find a way to make it happen, so you might as well give them a good tool.

There is nothing comparable in the industry that provides the same ease of use, great community, and good products.

I rate the solution an eight out of ten. 

We have a lot of use cases. A lot of them are based on SAP transactions. From SAP to SAP, or SAP to local documents, or local documents to transfer information to SAP.

The main benefit is to save manpower in-house. The second benefit for me is avoiding printing on paper. That is the second KPI that I am working to reduce in the company, reducing paper usage. In one project, for example, we managed to save more than 1,000 pieces of paper daily.

The UiPath Studio has been very necessary for us. 

Orchestrator is a vital feature. We have a sizable infrastructure, so it is necessary to have Orchestrator deploy all of the robots in all of our servers. It is not possible to work only with one computer. Therefore, that is an essential feature for me.

We've been able to save on man hours. We save around 60 manhours daily per department. For example, the maintenance department works with many people, and we can save on labor.

All departments use automation; however, mainly the logistics department benefits. The finance department comes in second, and after that, production. We've created more than 40 automation so far. We use both attended and unattended robots. 

Even if you are just on a laptop, you can have UiPath. 

I've used the UiPath Academy. It's necessary to have credentials for the infrastructure. It helps us understand the features of UiPath properly.

I use the UiPath community a lot. When I have a job, I can write a question about it and get a response from an expert. It's quite a valuable service. With the community, we can reduce the time to resolve issues. We can learn from other people who have faced similar challenges. 

Setting up automation can be easy or complex, depending on the project. 

All documentation and transaction areas can always be improved. 

We'd like to see mobile robots in the future. We have a lot of cell phone tasks, and it would be ideal to replicate automation from the iPhone, for example. If you were at a certain location, you maybe could set up an automation that could send a message or open a cart. 

I've been using UiPath for four years. My company has worked with the solution for longer. 

The solution has been 95% stable. 

It's a very good tool, and it's easy to expand in terms of infrastructure. If we need more space or more servers, it's easy to just deploy more. 

I have no experience with direct UiPath support, however, getting help from the community has been great.

I did previously use Auto ITX. It's a library from C# Program. It was only local. I don't know if was a standardization. I'm not sure why the company ultimately decided to begin using UiPath. This product is easy. It's drag-and-drop and very simple to use. 

I have developed automation and uploaded Orchestrator. That's it. I didn't handle the initial implementation. 

I'm a developer and therefore do not handle the licensing aspects of the product.

We're UiPath customers. 

I'm not sure which version we are using. I know it is not the last one. 

I do not use the AI functionality just yet. That's new to me and very interesting. 

While I would recommend the solution to others, it is necessary to have a good developer who understands the tool's value. Technical knowledge is necessary.

I'd rate the solution ten out of ten.

We have multiple use cases for this solution. We have applications built on Microsoft platforms and we use UiPath for our automation and automation testing. Being able to do this means that we do not need to keep reverting back to test every use case when we complete upgrades. 

We also use this solution for the automation of responses to support tickets. Any tickets that come through that can be automated, rather than it being done manually. 

UiPath has improved the ease of building automations. We were using SeleniumBase testing which is a legacy application and required a lot of manual work to maintain it. 

UiPath has made a significant difference on our staff's workload capacity and freed up team members to take on new endeavors versus getting stuck with manual tasks. 

This solution has been most valuable for our support ticketing processes. This has created efficiencies within our team and freed up time for them to focus on project work. It has prevented the need for them to stop what they are doing to complete a mundane task and then get back to what they were doing. 

We previously built automation repositories before it was offered by UiPath. There's no smooth migration from what we built to the newer studio that they have at the moment. This is the biggest hurdle we are facing. We would also need to rebuild all previous automations built in another solution called SeleniumBase.

I have been using this solution for one and a half years. 

We experienced some performance issues because our libraries are growing and we experience crashes from time to time. This usually means we need to reboot. The stability could be improved in this regard. The ability to handle large-scale applications or multiple applications could be improved as our operations and libraries are going to continue to grow. Currently, our libraries need to be split and this creates more maintenance for us. 

We are satisfied with the scalability. We are aware of new features coming in the future and we will be able to adapt and expand our applications based on these new features. 

The technical support for this solution could be improved. They take longer to respond than I would expect. We would like a 24 to 48-hour SLA in place to manage expectations. 

I would rate their support a six out of ten. This is not due to their ability to resolve an issue. It is due to their lack of transparency and keeping us updated on how issues are being resolved. They are not good at communicating when we can expect our issue to be resolved. 

Neutral

We used SeleniumBase. We needed a solution with enhanced technical capabilities and this is why we switched to UiPath. UiPath offered us a lot in terms of functionality. 

I was a part of the implementation team in our organization where I made sure there were no roadblocks. I was working with UiPath's points of contact and they were coordinating and making sure the implementation happened as planned.

The initial setup was complex. It happened three years ago and we still have some questions about the setup. In order to get answers to these questions, we need to raise a support ticket. I feel like the knowledge of the support individuals could be elevated so we could receive answers right away. 

We implemented this solution in-house. 

We have not yet experienced ROI using this solution as we have only been using it for a year and a half. We don't have control over the domain to see the metrics and KPIs at the moment. We are hoping that once some of our core applications are in operation, we will be able to assess the ROI. 

UiPath has reduced our manual effort and improved the overall efficiency of our team. 

We considered Microsoft's Power Platform which does offer very similar functionality to UiPath including a Desktop AI Builder. However, this solution had limitations that UiPath does not. UiPath is focused on automation and offers a lot of support in this regard whereas Microsoft focuses on so many different areas. 

I would advise others to hang in there for the first six to eight months as the initial learning curve can be frustrating. Once you get a hang of it, you will clearly see the benefit of using this solution. 

I would rate this solution an eight out of ten. Our test automations need to be improved for migration purposes and overall performance could be improved. If those two were resolved, I would give it a ten out of ten. 

We implement automation for clients to create savings by cutting the number of FTEs. We've used UiPath for various kinds of automation, including mainframes, browsers, Excel, account payables and receivables, fixed assets, healthcare projects, HR projects, reporting robots, and IT services projects. 

Recently, we did a massive US taxation project that spanned eleven months and covered enterprise and individual taxation extensions. It was a huge project that yielded a lot of savings. 

If I want to leverage a specific UiPath use case, I build small use cases around that particular feature and try to envision a product out of it. I've had several hackathons and general discussion calls because I'm a solution architect. Everybody wants to work on apps, and UiPath is comparable to the blank canvas apps that Microsoft PowerApps provides. 

When we had an automation program that involved 200-plus automations, we created around 100-plus libraries, saving us thousands of hours of development time. UiPath is designed to save time. The object repository was liberating because it enabled us to move from simple to extendable libraries. UiPath's apps increase our business by helping us leverage the UI layer in a way we couldn't in the past.

It gives us the ability to share data between systems in healthcare applications.. However, it's still tricky because so many system controls are in place. That's not a limitation of UiPath per se, but every department has restrictions on passing data to other departments. They have their own due diligence in place, limiting data flow from one system to another. UiPath gives us the fluidity and freedom to do it, but the limitations within each domain often get in the way.

Let's use claims data, for example. The data regulation team won't be too keen on allowing the marketing department to use data from the claims division to generate new business. The data flow from one department to another isn't that fluid. Organizational controls rather than system controls bind it.

We should look at each separately in terms of AI and machine learning. If we want to do data analysis, we have to call an inverse Python script, which is a little difficult. However, we can host our own model, and that's good. The ability to use that opened some doors. 

At the same time, it's helpful to have out-of-the-box features like Document Understanding and an ML passer there. The integration is quite fluid. We can directly call a Document Understanding model and then give it to ML passer and then get the results out. It's smoother for integration. The client has to focus on one particular software or multi-stack that they're comfortable with. UiPath has opened some opportunities in that sense. It made life easier because the capability is sitting inside the platform itself. 

UiPath is a separate solution, but it can talk to other services and doesn't restrict you to the passer, but that's how the ML features within Document Understanding help us. Custom model hosting and the AI center also help. We don't have to host the custom model somewhere else and call that service then pass it and do the post-processing within the system. It isn't a third-party service, so we know it's sitting within the system. If any issues are also there, we know where to diagnose and deposit them.

UiPath Orchestrator is a treasure, and UiPath Studio includes various packages to integrate with solutions like Salesforce, ServiceNow, and Excel. They also have mainframes, web automation, and the API package. 

Orchestrator contains a lot of useful apps, data services, and machine templates. From a usability perspective, the most valuable aspects are its custom activities, libraries, and object repositories. In terms of integration, I like the ability to use APIs and call automations from UiPath apps. The most valuable feature from a human-in-the-loop perspective is the action center. 

Our customers appreciate the support that UiPath provides, and they don't want to go with a third-party vendor like Microsoft Visio, Form Recognizer, or Google Cloud. They're hesitant because some integration is required. The lead times for closing queries are longer with third-party vendors. For instance, it takes me about two or three weeks to set up Document Understanding in my project. But it took us three months to establish Form Recognizer with a client.  

In addition to the out-of-the-box functionality UiPath provides, it can host our custom models. That's something that comes in handy when we need a custom model. So far, we haven't taken it to production yet, but we are still baselining the technology. At the moment, we are doing a baseline project where we try to perform four POCs simultaneously. We are baselining Google Cloud Platform, Azure, and AWS with UiPath's AI center and machine learning services and comparing the four.

UiPath's performance could be improved. UiPath's framework was built on top of .NET Core. It was a 32-bit platform initially, but they recently introduced a 64-bit version. Let's say I have a huge machine with 64 gigs of RAM. If I have a server machine and want to use multi-threading to extend my automation and multitask, the design won't allow me. I can't separate things into multiple processes. 

The platform is designed to go step by step. Parallel activities are not truly parallel, but it creates the impression that it's running in parallel. For example, if you're on the left segment within a parallel activity, and there is some wait time, it doesn't stay there. It goes to the middle and then to the right. It schedules tasks based on a time-to-completion window and then takes them from end to end. 

UiPath optimizes the time and doesn't let the CPU idle, but it doesn't give you multi-threading or asynchronous methodologies. These are available in the C# and .NET framework but absent in this platform. It's a step-by-step process where you go through each activity. A casual developer or coder who wants to leverage UiPath should be able to. I'm not saying that the working code is not there, but it's quite basic. It doesn't support functions or asynchronous methodology. 

UiPath is attempting to make it easier for a citizen developer to automate processes. They don't have to know how to code, but a citizen developer can't do it when the use case becomes more complex. When they advertise that one doesn’t need to know coding to program bots, that's only true for easy or intermediate use cases. We still need a programmer for anything beyond medium complexity.

The marketing could be improved because the methodologies went from waterfall COE to an automated operation model. However, people are trying to do automation in an Agile model, but it's not exactly executable that way. When customers see the demos from UiPath, they expect that the results will be significant, and they are. However, we might try to automate something, and we’re unsure whether it can be automated because there's a gray area. There's always a 20 to 30 percent chance automation might fail. And that gray area is something that I want UI to focus on.

They have tried this with StudioX by adding checklists. The industry is not following this practice, though. I'm not sure how they should ensure that it gets followed within the platform, but the delivery model needs to improve. It's still niche. 

Another thing to consider is the work-life balance of the developer and the solution architect. The overall challenge of automation tends to become exponentially complex over time. For example, let's look at one aspect: the account tables. I can go to the account tables from a simple PDF perspective. The PDF is readable by the board, and the solution can extract all the data and do the account tables within SAP or Ariba and mix all of it and then submit a report to the business.

This can be extended to intelligent document processing using form recognizer and custom models, then passers, pre-processing, post-processing, and sending the report to the business. The complexity of it can be extended quite a lot. There should be a framework or methodology in place to hedge the bet so that it's not too complex and doesn't disrupt the life of a developer, solution architect, or business analyst. 

If the automation becomes too complex and challenging, our support team won't be able to sustain it in the long run. Once the development team is gone, the automation will die two or three months down the line. It's a balance to manage the complexity and extent of our automation.  

We've been using UiPath for a little more than four years. 

Resource utilization is one area where UiPath is lacking. UiPath says that the solution will run fine on a machine with four gigs of RAM, and they recommend horizontal scaling, but I suggest a mix of horizontal and vertical scaling. 

I've seen implementations on giant machines with high-density VMs and five users logged into the same VM. Therefore, the resource utilization isn't optimal. The RAM and CPU are not completely utilized. It only executes processes on a segment of the resources. I think that can improve. 

I rate UiPath's support nine out of ten. UiPath's support is excellent. They triage issues based on severity, and there is a clearly defined close time and lead time. Their support engineers will follow up with you 24/7 over phone, SMS, or email. 

The scope of support isn't limited to problems with the UiPath platform. We can reach out to UiPath if we are having problems automating a third-party application. They will help us if they have experience with the app. If they don't have experience, they baseline the issue and go through the log to do whatever they can to help us. We've had a great experience with UiPath's support, and our clients feel the same. Support is one reason UiPath is dominating the market. 

Positive

Most of the RPA solutions are fairly similar. The inspiration for UiPath's object repository was taken from Blue Prism. UiPath's integration services are like the connectors in Microsoft Power Platform. I'm not saying that UiPath is exactly copying everybody, but they're taking the best features from every solution and bringing them in-house. 

Other platforms are dominating in some areas. For example, Power Apps is more mature than UiPath Apps. I'm trying to add value based on my experience, and Power Platform's connectors should also bring value to UiPath. In the end, it shouldn't be redundant.

Every time we deploy the solution, we use an automation operation model. It's a massive document with policies defined on every level, from design to development, UATS, prods, escalations, business, teams, team leads, Agile boards, and reporting. 

All of that is documented from the start. We use that model to layout deliverables needing to be fulfilled. Once deployment progresses from one step to another, we have a way to document our progress. We've gone from a theoretical model to a UI model. It's not purely Agile or KanBan, though Agile framework and KanBan breakdown structures are there. However, it doesn't follow a scrum methodology. 

We're not on a two or three-week release cycle. One sprint is the entire use case from build to development and then from development to UAT to production. It's a custom delivery model, and it's working. Still, I feel it can be improved. 

Our clients have seen significant returns using UiPath, but their marketing could be improved. 

I'm aware of how UiPath's pricing compares to other tools, but it's hard because the offerings are different. It's not apples and oranges per se, but it's comparing an average tool to an excellent one. UiPath provides enormous value, so the licensing is justified.

I rate UiPath nine out of ten. It isn't perfect, but they constantly improve and surprise me. At the moment, I give it a nine, but it might be eight in the future. If you feel like some process will cause a lot of headaches, position it later in the cycle of automation. If you can save resources by automating, you should go for it, but you should be smart when deciding your use cases.

If you're thinking about implementing UiPath, I recommend having a design team that understands automation. You need people with some experience who know how automation is done. It requires some business analysts with at least a month of experience on UiPath from a citizen developer perspective. It would help quite a lot in terms of establishing automations that are relatively complex. Try an 80-20 approach operating principle when planning your automation.

We have four robots. One we're sending out shipping labels as our members do returns. Once they create a return, we used to have someone that was manually entering in and creating the shipping labels. That was like the first robot that we built. The cost savings on that alone covered the costs of UiPath in total. We have a few other ones that we've been playing with, however, that first one was a big one that covered the cost of UiPath. 

UiPath has freed time for our employees. With the shipping label robot, for example, we basically replaced two jobs and now they're able to do other things. They can take on other more vital responsibilities.

I'm really excited about task capture. We haven't started it yet, however, that's going to really help capture the processes that we want to automate. We're excited about that.

The solution is just opening our eyes to what is possible. There are a lot of people in our company who hate doing mundane repetitive things. It's giving enough hope that we can replace those jobs that people hate with automation. We're excited about that.

I'm not a developer, however, the two developers that are under me, like the shipping label bot and found it easy to build. A developer was able to create that in one day and it replaced two positions. I'm sure we can build it better and faster with what we're still learning. With a partner coming on to guide us I foresee that we will definitely get better at it.

We’ve used UiPath's Academy courses. I don't think we would be where we are today without it. My two developers had zero experience with UiPath. They went to the Academy and learned as much as they could and started building right away.

Its biggest value is the continual learning on offer. We're pretty overwhelmed right now with what it can do, however, the Academy just teaches us how or where we can go with it. It’s great.

The setting up of the cloud was a little bit confusing for us. We expected someone to walk us through that process and we just did it ourselves and weren't sure if we were doing it right. We thought that getting assistance with the setup would just be kind of a given or they would at least lay out the steps. We didn't have that. We were asking a lot of questions and trying to figure it out with our salesperson. She was likely not the right person to help us with that. If there were directions on how to set it up, that would have been helpful.

We've had the solution for three months. 

In terms of stability, the robots have been running well. That said, we've had a few failures that we had to go in and fix, however, it was a pretty minimal effort to fix them. I'm not sure of the exact reasons. I remember my developers were telling us one failed and we needed to go figure it out.

It wasn't like an all-day fix. It was just a pretty quick fix which required simply stopping it and restarting it and then it worked. 

In general, for stability, it's been so far so good.

We have the goal of scaling, however, we are still just barely with our heads above water. We're just trying to figure it out as we go. Our biggest asset is bringing a partner on to help us and allow us to build up that scalability. Without their help, we would be lost. We would build without having a good foundation. The partner is coming on for a three months contract to train us and get us up to speed to make sure that we're building a good foundation so that we can scale.

We first created a technical support ticket when we had the issue with the trial license versus our actual license. It was hard for my developer as he didn't have the URL for the cloud. He really couldn't diagnose the issue as we thought it was all on the one referred to us, yet there was that disconnect. We went back and forth over several days trying to figure that out and the tech person couldn't help us. We were lost there. That was a little confusing.

This feedback isn't against the technical team. Maybe it was just the way we didn't get the correct training we needed to set up correctly. UiPath should've killed those trial licenses or transferred them and they never did and that first robot we built was on a trial license. 

It would have been helpful if they told us to import the robot or something over to the real licensing. 

We did not use a different RPA solution previously.

I'm not a tech person, therefore, the setup was a little outside of my wheelhouse. It was a little bit harder for us. We've been trying to figure it out. 

The issue that we've found is we had a trial license and my two developers were on the trial. Then, when we got the actual licenses, a developer was still building under the trial. The trial was allowing them to do things and build over there, however, it wasn't under our automation path. It took us a while to figure out what the disconnect was as I just didn't know how to set everything up. That was a little bit confusing.

We realized ROI on our first robot. 

The automation cloud offering did not decrease the total cost of ownership of UiPath. It was a little bit more, however, we didn't have to set up our own server and maintain that.

We bought the starter package and we were able to cover the full cost of it with one robot within two days. It definitely paid for itself.

We were also looking at Automation Anywhere and it was a pretty close tie between the two.

We chose UiPath as a colleague who had worked with UiPath at his last job and he was a little bit more familiar with it. We thought the security was a little bit better in UiPath as well. Those were the two main reasons that kind of pushed us towards UiPath.

We haven't used the UiPath apps feature yet. We've signed up with someone that is going to be our partner to help us learn all the new aspects. Hopefully, in the next couple of months, we'll be setting everything up, including the automation hub, and trying out apps and task mining.

We do not yet use UiPath's AI functionality.

Based on my lack of knowledge, I would probably rate the solution at an eight out of ten. We've been super happy with it this far and from all the things I've seen, we're excited about where we can go with it.