UiPath Platform Reviews

We have done a lot of things with UiPath for different customers. I have done Java application automation and PDF automations. We use it for all kinds of automation. For example, for one client, we're working on invoice processing, supply-chain automation, and their technical services.

Going with automation is really helpful for our customers, saving them time which they can use for other processes.

For example, I'm working for a customer that has 16 different processes to deal with. For every customer, they had to spend at least three days a month to process everything. The bot is processing everything in three hours and our customer doesn't need to monitor it. They are saving many hours for every customer every month. Automation is saving them around 2,000 hours per year.

UiPath is helping us to implement end-to-end automation in many cases and in many ways. We have implemented a lot of ERP automation and we are now working on SAP auto-creation for supply chain and invoice posting, processing, and payment clearance.

It is also helping our clients to speed up digital transformation a lot. They're coming to us with more processes.

The feature that I like the most is the Document Understanding for extracting information from PDFs. I also really like the human-in-the-loop concept.

The main disadvantage that I have identified in the Document Understanding is in table extraction. If the table size is large and goes to the next page, we are unable to extract it with Document Understanding. I hear that there is a solution for that but I have to find it.

There are other extraction features that Document Understanding doesn't have and clients go for ABBYY Vantage or Google document AI and it becomes expensive for them because they have to purchase a UiPath license and the other solution's license.

With the competition in the market, they have to improve. They can't settle and say, "We are at the top." They have to improve invoice processing, that is the most important thing, and that's where Document Understanding comes in. We need to get to the point where a customer does not look at any other OCR engines. They have to improve Document Understanding for invoice processing.

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

It is a stable product.

UiPath support is very good. I don't think we have raised a technical support question, only deployment support. My experience with the UiPath team is that they have been really helpful. They have connected with me within a short time and have done a lot for me. I irritated them a lot, but they still did a lot for me.

Positive

The setup of UiPath is easy. Two months back, we did a server migration where we not only migrated the unattended and attended bots, but the whole Orchestrator setup. We moved everything and we did it within seven days. We had some queries and raised a couple of tickets, and the guys connected with us even after 12:00 AM and 1:00 AM. They stayed with us and helped us complete it. The server migration itself was easy for us, with three years of development experience, even though we had never done anything regarding server migration.

The initial setup itself takes about two hours. In the last three months, we have done that for a number of customers. Depending on one's experience the setup can be done by one person. I do it myself.

Deployment of bots is easier than that. You set up an attended bot and publish it to Orchestrator and it will work. It is very easy. Even if you Google it, you can easily find information on it.

For me, with three years' experience, it's very easy. For a newcomer, like someone with only three months' experience, it will be a little harder because he will need to do some research but everything is available on Google. And even if he doesn't find what he needs there, he can raise a request and the guys will be very helpful. They'll connect with him within eight hours and they'll fix it.

The ROI depends on the complexity of the process that a client identifies for automation. The license costs around $10,000 per year, although I'm not very sure about that number. People are buying the license but they're not completely automating everything. They have to identify where they're struggling and give that to a bot. They need to use unattended bots on a 24-hour basis. When they utilize it all 24 hours, it is helpful. If they're going for only one or two bots, the return on investment will definitely be less.

In India, where I am from, UiPath is expensive. But customers in other regions, like Europe or the US, will not find it so expensive.

Every time we have a proposal call with a client regarding UiPath, most of our Indian customers are not okay with the cost. They can't afford it. They want alternatives, but they still often end up with UiPath because of the efficiency.

I haven't used any other solution, but I have explored Power Automate. I also opened Automation Anywhere and attended one class for it and I decided I'm not going to go to Automation Anywhere. You can't compare anything with UiPath. UiPath is the top.

It is the customers who have to identify the things that they can automate. We have to promote our tools and RPA capabilities and when they understand these things they can come back to us and use us for what they need. Most customers don't know what automation and an RPA automation bot are. But when I do my first bot and show a demo, they understand: "Oh, this is how it works." And then they come up with more processes for us to work on.

Regarding UiPath Academy courses, I have done some but I haven't had a chance to do the paid certification course because I'm continually working on projects. I did a couple of basic RPA developer courses and then the SAP, Document Understanding, and Action Center courses. I haven't had a chance to explore the new features there.

To use UiPath there are no coding requirements, like knowledge of Python, but you need to have good problem-solving skills. You need to understand loops, flowcharts, and how to develop conditional actions.

Our customer had one attended robot and wanted to scale up. We used UiPath to identify possible processes that could be automated and also required the ability to scale up the architecture.

The ability to use end-to-end automation with UiPath is the key to success but it takes a lot of work.

UiPath has absolutely helped minimize our on-premises footprint by automating.

The solution has helped speed up and reduce the cost of digital transformation.

I believe UiPath has reduced human error.

The solution has freed up employee time through the automation provided. 

If we go into every specific role in every specific use case, depending on the role, we have the capacity to free up over 50 percent of employee administrative time. 

The solution enables us to implement end-to-end automation.

The entire training support package provides different paths we can follow according to different roles. Automating basic processes is very easy. The setup phase is very quick.

The possibilities with process mining are fantastic.

They offer new vendors UI Academy courses and the four-hour BA course gave me the basic knowledge I required.

The vendor can improve the solution by building up the BA path included in the UI Academy courses. There's too much focus on development, but not enough on BAs, scrum masters, and project managers alike. 

I am interested in low code as a general concept and would like to have a better methodology for how BAs and other IT professionals can be closely connected with professional developers and included in the automation process.

I would like to have integration with other programming languages. We primarily need to know Visual Basic or C Sharp to develop using more traditional development. For example, for front-end automation, it would be helpful to use Javascript instead.

I used the solution for a few months.

The stability is good. I did not encounter any issues with UiPath.

We conducted a pre-study using the solution and we saw the possibilities to scale up.

I give the solution a nine out of ten.

Building automation using UiPath requires some level of technical expertise. As a BA, I have some programming experience, but not in-depth programming knowledge and that is enough for me to automate some basic processes, following the training. I worked together with senior developers who would be able to automate more advanced processes, but we didn't get to that level in the project.

We prepared the information and I was involved in the UiPath training, but we didn't get to actually scale up and automate new processes because the project was never completed.

I'm currently working on a pre-study for a large company in the public sector, and they are not using UiPath presently. The organization is currently using NICE but UiPath is one of the solutions that I'll advise them to continue evaluating.

In Sweden, there are a lot of issues and different regulations around GDPR, so we always deploy on-premises.

I would recommend that anyone thinking about using UiPath should have knowledge of the entire ecosystem in order to get the full experience. The concept of intelligent automation is the track that UiPath is on right now with integrating AI solutions for identifying processes. A new user should take a more holistic approach. Focus on identifying, assessing, and not just automating processes. 

We started out with a lot of unattended use cases and then moved into using attended bots to help users. I've been with two separate companies. One was a financial services company. However, there was a lot of support for external clients. In the company now, we're doing a lot around the back office, HR, finance, and supply chain. UiPath just runs the gamut of all different kinds of use cases.

It's definitely made it easy to build automation. We have a team of about four or five developers. One of them was straight out of school, and they had never really had professional experience. We've also taken a couple of developers that were more into custom code and converted those over to using UiPath. It's interesting to see the level of excitement when you use a tool like UiPath from someone who is straight out of school and can convert over. 

We enjoy the constant innovation. It's coming out with new things that we can use and new features all the time. RPA has been around for a while now; however, the fact that we're adding integration services, adding apps, and all these other features, makes it possible to expand our use case.

We use UiPath to automate processes that deal with a good environmental cause. For example, for the company, however, we get invoices for bulk fuel. Our company sends out a lot of trucks, and a lot of customer engineers to actually service equipment. All this was manual, and a lot of not knowing how much we were paying. We automated that, and then the next step of that process is, "Okay. Can we start figuring out exactly how much money we spend on fuel, now, let's try to figure out ways to lessen that?" I could see how that could be environmentally friendly as we're trying to reduce consumption.

The user community is interesting. I've met a couple of people here and had really good conversations. It's interesting in the virtual world that we live in now, where everybody's just a face on a screen.

We've used UiPath's Academy. Being a solution architect, I'm not hands-on with code every day. I got certified as an RPA associate so that I could better understand what the developers are working on and using. When I'm designing solutions, I have a better knowledge of what's possible. I've taken a lot of the courses on UiPath Academy.

We're actually looking into a document to understand the use case. It's essentially car titles, and we're struggling. We've used several different OCR engines to try to train the model and try to improve it. For us, a little more direction on how to actually achieve this would be useful. We've been struggling for a couple of months now trying to get it working and getting it to the level we need it.

I've been using the solution for five or six years. 

The stability is great. I compare it to what I would think the best in class is. It's like Microsoft releasing patches. I've had fewer issues with UiPath updates than I do with my Office client on my computer. Therefore, it's very stable. 

We've had it where we had an update, and it did break some of our robots, and we had to go and do some troubleshooting, yet that's only been one time. It's pretty good overall. 

It remains scalable for us. We're not a huge shop yet as far as the number of bots, so it remains to be seen. It will be interesting when we try to reorganize our Orchestrator to make it more scalable. I can't really answer that one yet, as we haven't really tried to scale a lot.

Technical support is great. It's easy to reach out to them. It's easy to get feedback. As with any organization, a lot of times, the first answer is, "Go read the FAQ." I usually respond, "Well, I've already read the FAQ. That's why I'm asking." This is normal. Once you get past that, they're really ready to jump in and help.

Positive

I started out in 2016 looking at what was the best solution for the company. We looked at several of the top options. They're still the top ones today if you look at Gartner, Forrester, and publications like that. I used some of them. I've used Power Platform and other low-code tools like Pega and Appian. There are a lot of different tools in this space, and they all bleed into each other. 

I've been with two companies that focus on UiPath. It's just the constant way they try to keep up and keep innovating has made them a bit different than other options.

I was not involved in the initial deployment of the platform. I came in about a year ago. Since then, we've done things like automating month-end close processes, automating a lot of manual processes from moving from an old legacy HR system to Workday, and integrating with Workday. There have also been several other different smaller use cases like that. That said, for the implementation of the main platform, I wasn't here for that part.

The deployment of automation depends on how it's built and how you structure your UiPath Orchestrator, which has changed a lot in the last one or two years. They've got this concept of modern folders now in UiPath.

It's taken a lot of effort to transform what we did previously into what we're trying to do today. We very much had one tenant for one automation or a group of automation. Now, we're trying to do more. We ended up with a lot of tenants. Now, we're trying to consolidate into fewer tenants with these modern folders and trying to understand how that all works.

We have definitely seen an ROI. The team has talked about a million hours returned back to the business for other activities. It took a few years to get there, however, now it's every year. 

The pricing changes every day, however, it's not unlike any other SaaS platform. Sometimes it's hard to understand. That said, I'm more on the technical side. Some of the big questions are unattended versus attended since there's a lot more cost to unattended. When we get into document understanding, it's the number of OCR models, and the models you use that increases cost.

I looked into the other two big ones in this space. One of them, and this was in 2016 or 2017, didn't have a concept of attended automation. They thought it should all be unattended and no one should touch it. It should just run. That was really a barrier for us since one of the big value propositions is just automating those small tasks that people do to free up more time. Attended automation eliminated them.

One of the other ones we looked at couldn't support us. It was a proof of value, proof of concept type exercise, and they couldn't give us the support we needed to execute it. It was pretty easy to disqualify them when they couldn't go through that pre-sales motion to really get us. Why would we want to sign a contract? Why would we want to move forward? 

Potential new users should focus on the business driver or the business use case and find the best tool. UiPath lives in this space of RPA, low-code, AI/ML. There will probably always be three or four of these tools to choose from at any enterprise or sizable company. How do you pick the right one? It's really about what the business is trying to do.

I'd rate the solution eight out of ten.

Support is good, reliability is good, and innovation is great. There are just some things they could get better on to catch up with some of the other players in surrounding technologies. UiPath started as RPA. Other companies started as integration platforms. I know we're getting into connectors and things like that. It just keeps moving in that direction.

Our client wants to reduce their manual work, so they feel an automated solution would work better. The company has one staff member who is well-versed in automation, but they wanted us to suggest more solutions. We decided we should stick with UiPath since they are familiar with it. It's a local community bank with many feeds at the end of each business day. They have about 50 agents handling those feeds.

The client caters to poor people in the community who tend not to trust banks. The community bank sends agents into the fields and shops. They show them a card and suggest that they save a certain amount of money each day. They collect it and take it in a book. They then have to bring the book back together with the money. They're helping the poorest of the poor to save money. Based on what they've saved, they can get a loan. 

The bank encourages customers to save, so they collect daily. They were bringing this data back to the office and entering it by hand. We showed them that UiPath could do all that for them.

We prefer a cloud-based solution because we are a digital-transformation company. However, the client wanted to keep everything on-premises, so we needed to show the benefits of migrating to the cloud. In Africa, power is a problem. Energy costs a lot, and power outages can disappoint customers. In the end, we won them over by showing them the advantages of the cloud, so UiPath is deployed on the cloud. It's highly available, and they want their data to be accessible all the time.

We have about 30 UiPath users, most of whom are IT Administrators. We use the generic term IT Administrators. The company is structured so anyone can be deployed anywhere at any time. We use UiPath extensively in the particular scenario that necessitated our initial use. If we get more clients seeking to reduce repetitive tasks, I believe we will continue to expand our usage. 

With UiPath, we could automate many of our client's data entry tasks, making the process easier and more efficient. I would estimate it helped us to eliminate about 80 percent of repetitive tasks. The Automation Cloud helped us reduce costs and ensured the solution was always available. In the event of downtime or disaster, everything can still be recovered from the cloud.

We would recommend cloud solutions from Azure, AWS, etc. Using UiPath made us see that we should not just rely on cloud-native tools alone; we should look outside the box. Because of our experience with UiPath, we are more open to tools that will help the client work more efficiently. This made the client's life easy because it enabled them to reduce hiring costs and become more efficient.

UiPath handles all the infrastructure, eliminating the maintenance burden because we don't have clients constantly calling us about technical problems. UiPath helped us achieve our objectives faster than we would've normally. The project was supposed to be delivered in 10 months. However, because we eliminated repetitive tasks, we delivered the project in about six months, saving time and costs. UiPath Automation Cloud also reduced the total cost of ownership from infrastructure, maintenance, and updates.

Automation Cloud helped us handle as many customers as possible because the vendor takes care of the maintenance and everything. We can spend more time focusing on the work we're supposed to do to handle as many customers as possible. UiPath provides a preconfigured solution, which offers more value to our clients because we do not need to configure anything. 

It reduced our team's workload by enabling end-users to create their apps. We can easily walk them through the process over a Zoom call. Instead of throwing the whole backload at us, we can give them instructions over Zoom in an hour or two, and they can pick it up from there. It has dramatically reduced the stress on the IT department.

We've used the UiPath Academy courses. Sometimes, a client will call you, "Your company recommended this to us, and now we're having problems." They expect us to know everything, so we need to get information from the academy. The most significant benefit of UiPath Academy is that I don't look like an idiot in front of my boss and the customers. It makes me much smarter and more authoritative.

The UiPath community is also a valuable resource. When I have an urgent question, I post it on the community forum, and someone who has had a similar problem will respond quickly. I don't need to spend time researching. Product support is better with the UiPath community. 

UiPath reduced the costs of digital transformation. Digital transformation would always involve some costs, whether you like it or not, but when you look at it holistically, it's still cheaper than doing things the other way around. It also reduced the cost of automated operations by an estimated 65 percent and overall costs by about 45 percent.

The solution dramatically reduced human error. No one on my team or my boss would ever want to return to when we weren't using these solutions. We've discovered that it saves money on hiring costs and reduces many problems. It has freed up employee time. We delivered a 10-month project in six months. A technician gets assigned to a client for a specific number of months. If you finish earlier, you can spend time on another fun project you want to take on in the company.

It had a positive impact on employee morale. We were excited because we had four extra months. My colleague began attending an online school that his work usually would not give him time to focus on. He used that time to finish his master's degree, so he's happy. 

I like the fact that UiPath makes everything fast, and you don't need to employ as many people to do all the dirty work. All of our clients only used UiPath. I've never tested Automation Anywhere, but UiPath is excellent. They are doing a lot to stay ahead of the competition. I feel that if they continue doing what they're doing, the competitors would always have a lot of work to do because they will always be on top of the league. It helps with end-to-end automation. We discovered that we don't want to do tasks manually, so automating the entire workflow helped to achieve that.

The attended automation feature has been helpful in my experience because my company works on other companies' projects and solves their problems. If I'm assigned to a particular company, and I feel that this would be the easiest way to get the work done, I'll use any of the automation possibilities that we have.

The AI functionality makes life easier for everyone because it helps us deal with complex processes. We use machine-learning models for the most difficult problems. At the end of the day, the solution understood the problems because we had already created models. It understood what the problems were and could follow through to solve them.

What I'd like to see is more tutorial videos on YouTube. Maybe they could have a YouTube channel, and the community could empower more content creators to make how-to videos. When clients call us with issues, we wouldn't have to explain. 

If a client using Azure has an issue, we assign an engineer. Let's say you still have a problem after the engineer has consulted with you and referred you to the official documentation. It would be helpful if there were a content creator on YouTube to explain the problem in an accessible way.

I began using UiPath a little over a year ago. I work at a consulting company, and one of our clients uses UiPath. They needed advice about how to undergo a transformation. 

UiPath is stable.

UiPath is super scalable. We are a company that always likes to think outside the box. We invest in research and development to stay ahead of the market and our competitors.

I rate UiPath support eight out of ten.

Positive

In the beginning, we had some issues. We found it complex initially, but it became simpler over time. The deployment didn't take much time. It was less than a week. There was a learning curve, so that's why it took us so long. Maybe it would only take a day if we knew what we do now.

No matter how much you complain about the price of a SaaS product, it's still cheaper than building your own data center and other infrastructure. That's my perspective as someone who works for a company that does digital transformation. The price is cheaper than building and deploying your own solutions. 

I rate UiPath 10 out of 10. I recommend trying it for a month. We tried it, and now we are hooked and still use it. I don't think anyone on my team or my boss wants to switch solutions anytime soon.

Our company is in the dairy industry and uses the solution for automating 25 processes. 

We started with financial items such as utility invoices, vendor invoices, accounts payable, and accounts receivable. 

We are also simplifying the processes for creating recipes and food manufacturing. 

For example, we were able to use machine learning to read invoices for utilities at all of our factories and from 50 dairy vendors. All the invoices look different and AI is able to recognize where important data is located. The AI technology is amazing and we use it for three of our biggest processes. 

We estimate that the solution has saved us 10,000 hours per year. We only have three developers who are dedicated to the solution but have netted huge time savings. 

In total, since implementing the solution we have saved 19,000 hours across 25 processes. We are very happy with the results and will continue to expand. 

The solution's AI technology and machine learning models are huge for our company and the biggest contributor to saving time because we teach the model to read invoices. 

We are above a 97% success rate on all transactions. Our company is growing, but we are not increasing staff because robotics allow us to keep up with work flow.  

We use the solution to keep up with demand. Our staff is relieved and happy because robotics handles small but tedious items, allowing staff to free up their schedules and focus on more important things. We used to have to beg for projects but now staff ask us to help. 

The solution's OCR engine is lagging behind Power Automate a bit. 

It would be nice to have a knowledge base for C# that includes scenarios specific to the solution. 

I have been using the solution for one year. 

The solution is stable with no problems. 

The solution is scalable and depends on the speed of development. 

Technical support is good and has been able to solve issues any time I contact them. There might be a bit of back and forth with support emails, but all problems get resolved. 

The solution's community and forums are important and very helpful. I can reach out at any time to get answers. Everyone I have communicated with in the forums has been great. 

I rate technical support an eight out of ten. 

Positive

I was an intern on the company's data management team and was looking for ways to automate my own job out of curiosity.

I started with Power Automate and created a process to show my boss. He indicated that the company was already exploring AI and asked me to create the process again using the solution so I could compare the two. 

The solution was code based and more complicated than Power Automate so I took advanced and fundamentals courses on my own time. There is a learning curve because the solution uses DB strings and C#. But in a few months, I was building automations and ERFs on the citizen developer platform.

The advantage of Power Automate is its ease and simplicity but it is mostly meant for their Office software. 

The solution is more difficult to learn but is extensive and capable of more because it is able to interact with websites and UI elements themselves.

The solution was already in place when I joined the team. 

I do not know pricing but the solution uses a licensing model. We have three licenses to manage 25 processes. 

The solution is the only one our company has ever used.

The solution has been in place for five years and has expanded across seven different departments. Three licenses are in place to manage 25 processes.

The Academy's courses are used when onboarding new staff to ensure self-sufficiency with the solution.

There are many packages available that are extensive, including the community package. Look at the functionality because it is possible to automate any process that is repeatable. 

You can interact with any broker not just Excel or SQL. The options are wide open. 

I rate the solution a nine out of ten. 

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.

Positive

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 are using this product to develop automation in the billing section of our website. We are integrating bots so that they can do the basic listing and then our salesperson can take it from there.

The biggest improvement has been in cost. We have been operating it for about eight months for about $8,000. Earlier, it was taking us somewhere around $30,000 to $40,000, so that is a big improvement.

The other part has been accuracy. Before, when we had employees for the same process, there were some minor errors, as well as some time issues. But with this system, I believe the accuracy has been at par, although there are several times when we have had to reframe or do some minor modifications in the AI to make the model work for a new set or variety of clients.

The reduction in human error means we get more leads into the hands of the right salespeople who can work on them. Fewer errors means time savings.

With time, the AI automation has improved. Specifically talking about the kind of business that we do, which is putting things into the right sections so that the right people are taking the right leads, even in some complex cases, we have seen accurate results from automation. AI is doing its job.

AI has also enabled us to automate more processes. Earlier, we had different sets of protocols for differentiating among the different kinds of inbound information we were receiving. Since deploying this automation, we have automated a large chunk of the reception. The accuracy has been maintained and the time has been reduced significantly. We are able to convert the leads in a way that gives us more to work with from the leads we get.

The automation-creation process is quite easy and the accuracy is quite good. That last aspect is critically important because we have used RPA to replace one of our employees and we are taking on a lot of responsibility. The most important thing that we require is accuracy and we have been getting that so far.

The end-to-end coverage is important because each and every part of the input we are receiving from our customers—and they're highly valued customers—is information that goes into our software via automation, and we do not want to miss out on any types of leads.

The UiPath Academy courses have been great at giving an overview of the solution and allowing employees to learn things at their own pace. Other users out there also helped our technical staff, so they have added value. The biggest benefit was that at the time our technical staff was getting used to the product, they felt that there was a scarcity of people who knew about how to execute things. Having this UiPath course was a little helpful because it gave them the initial confidence they needed to start doing things, whether it was right or wrong, and they kept getting feedback and improving.

The only concern is it's a bit tough to understand the first time, and you have to invest in the technical improvement of your team in general.

About 6 Months.

There's no need to worry about the stability.

The only concern is as we move towards scaling it. What happens if the system goes off? Although it's not a big concern, we have been getting reassurance from UiPath that they have a solid backup of everything.

With RPA, scaling is not an issue at all. Once a bot has been trained to do a specific thing using ML, multiple bots can be added for the same automation process, as many times as we want. Scaling is not a concern.

We have not used technical support.

Positive

In terms of our decision to go ahead with this product, although we had received a recommendation that we should be moving forward with it, we were severely concerned about whether doing things over and over would take us the same amount of time, in terms of the technical ability and the workforce, or whether it would be easier. After having a technical call with UiPath, we quickly knew that it would be easier. That was a crucial part of our decision.

The initial setup was easy, but making the AI understand, and using the machine learning algorithms in it, took a long time. It took more than we expected it would take. The UiPath team had us understand that it would be functional after one or two months, but it eventually ended up taking about four months. That was more time than we expected, but the initial setup was easy and straightforward.

We used a consulting firm. There were three meetings over the duration of the two-month contract. The advices we received we about our model selection with regards to pricing and data storage capability.

We have been using it for eight months. For the first four months, I do not believe we were saving time because we had to intervene a lot of times with help from the vendor as well. But from that moment onwards, once the integration was operating smoothly, we started saving time.

We do a regular analysis each month and we have been seeing constant growth. A month is a good amount of time to see the progress of a newly implemented solution.

Previously, we were not using automation operations. I believe we have now reduced costs significantly, which justifies the cost we are paying for the service.

Pricing is good if your venture is looking for growth in 1-10 million size of customer domain.

yeah we got in touch with the IBM team for their automation tool.

Building automation takes some time. The first time, it took us a month, but after that, it was easier. The next time we build an automation, it's a kind of reciprocal of what we did the previous time. The first time involved some help from other resources, but from that time and onwards it has been going well.

The innovation did not happen as fast as we thought it would for the first half. We had to recruit some IT guys to our technical team so that our entire team could become familiar with the process. The innovation potential is there. It helps to get very familiarized with the solution. But for the first few months, the innovation part was delayed. The technical level required to handle it smoothly was not there on our team.

UiPath provides a platform for building, managing, scheduling, and monitoring automated processes. We use it for various processes, such as cost analysis, repairing permissions, and manipulating Excel data. 

UiPath enables us to build end-to-end automations, improving efficiency, enhancing customer service, and creating a human focus. The solution helps us reduce human error. UiPath saves us time because it's flexible and makes deploying processes easy. 

It's easy to build automations in UiPath. It has a simple drag-and-drop interface.

UiPath has an active user community covering a variety of applications and use cases. The forum acts as a central hub for community members to ask questions, share knowledge, and seek help with different issues.  

UiPath has added more artificial intelligence to the full version of the product. There are many options for developers to integrate AI capabilities like natural language processing and optical character recognition.

UiPath should expand its coding options and reduce its dependency on third-party resources. There should also be more flexible licenses for smaller businesses. It's hard for small companies to estimate the cost of adding users in their final budgets. UiPath could also improve error handling and capture a little more information about the execution of your processes. 

I have used UiPath for the last four or five years. 

UiPath is robust and always available. 

I have used Automation Anywhere. The solutions are similar. UiPath has advantages in scheduling and analytics, but Automation Anywhere supports all the LoadRunner requirements. 

Deploying UiPath is straightforward. The installation can take from a few hours to a day, depending on the project. You need to implement the architecture, create a data server, and integrate it with the solution.

I rate UiPath nine out of 10. It helps to learn a little coding in languages like SQL and Python. You should also take time to learn the platform with hands-on experience, instructor-led training, and online resources.  You can start with a foundational UiPath course if you're new to the platform and learn about the fundamentals of RPA processes. Then, you can create a simple automation project to reinforce what you've learned. I also recommend joining the UiPath community and asking questions on the forum. Once you have the basics down, you can try some of the more advanced programs on UiPath Academy.