UiPath Platform Reviews

We primarily use the solution for the typical banking and transactional use cases. An example could be something such as homeowner's association transactions. That incorporates multiple departments in a bank, including treasury management accounts and opening an ACH. All of those areas are very transactional in terms of the rules-based processes that they follow.

We also use the solution for wire transfers. We have a lot of those. Then, from a business perspective, we look at lines of business as well. It can be used for residential and commercial lending. It's very process-driven and very transactional. We're able to incorporate automation in those areas very easily.

The solution allows us to do more with less. If we have a relationship with a third-party bank to onboard with a thousand accounts with a 15-day turnaround time, depending on what the relationship is, without automation, without RPA, you'd have to hire at least 10 or 15 contractors to get that done. That’s from a contractual perspective, to make sure that you meet the deadlines. However, automation just allows you to scale. You can save the same scenario in multiple areas. The scalability and the time to scalability on offer are key. And that's where we see the value as an organization.

The time to value is excellent on this solution. It is incredible. Unlike any other technology, which is really generally workflow-related, this RPA will give you quick wins, as demonstrated by the return on investment.

The solution has saved costs for our organization. We look at it from different lenses. We look at it from an actual savings perspective. We forecast it and then we annualize it to understand where the product will be or what it will bring us in the long and not just short term. For us, it’s very ROI-driven.

I’ve been with the bank for nine months now, and we went from having two processes automated to now having actual savings of about a little over $300K. It's not bad. There are about 30 processes in production. If we annualize that and forecast out we can see how we can continue to grow.

We have been able to reduce human error. I would call that the cherry on top. You don't really track that until you have it automated. However, if the alternative is having end-users upset that mistakes happen, having the level reduction we’re getting is great.

The solution has freed up employee time by a lot. We see it wherever it's very transactional heavy, where we had multiple team members. Now the teams are built by bots and people. Where you had three people before, now you have a person and a bot executing. So far, we have likely saved, in these nine months, a little over 11,000 man-hours. That's quite a win.

This additional time enabled employees to focus on higher-value work. That’s the whole purpose. We tend to look at ROI, not just money. It's also what else are the employees doing. We’re saving money from a man hours perspective, and, from a cost avoidance perspective, we’re not having to hire. The folks that work for us actually can do valuable work. They can focus on better decision making, more time with the customer, better relationship making, et cetera.

My team has started to utilize the UiPath Academy. My team is composed of multiple different skill sets from PMs to BAs to engineers, and so forth. Even at the level of IT, with the teams that manage infrastructure, sometimes I have them taking some of the infrastructure courses in the Academy. The Academy works well due to the fact that they prep you to grow quickly. If you don't understand how the technology operates, it could be a little bit difficult. You do have to train a little bit to understand it a little bit, however, it's not very difficult, especially when you have access to the Academy.

Having the Academy has affected the process of getting employees up to speed big time. Their appetite to get better and better is just enormous - not just due to the fact that the product is good and it's providing that information to do that, but also due to the fact that they're seeing results. That's helping them want to do it better and faster. It’s a win-win situation there.

The Academy has a really good curriculum for very particular skill sets. It's hard to be an engineer and have to learn a bunch of different stuff that won't necessarily concern you. UiPath has been able to really compartmentalize that learning capability so that it makes sense to different groups and speaks to their level of expertise. That’s probably the most valuable aspect of it.

In the world of NextGen technology, it would be ideal if they could speed up their beta products. My team handles all next-generation technologies that we implement in the bank. For example, we're looking at task mining right now. It's theoretical, however, that product is going to be tremendous. That said, it's still a bit in beta. For us, if they were trying to get new items a little bit quicker out there, that would be ideal. They're running with it, therefore, I'm not overly worried. They also want to provide a good platform for its users, and so I understand why they want to make sure it's good. The competition, in reality, even though it's growing, is not as strong. The feedback is just me being picky at this point.

We've been using the solution since 2015.

So far, we have had very few issues and the issues really have been around very complex knowledge. We have reached out to UiPath to get advice, and they responded, and it hasn't been bad at all.

Scalability has not been an issue. It's not even a topic of concern. The concern is more on the business side and can you manage the growth from a business perspective. The technology's there and I want to automate more. However, with automation, the question is if you can manage it.

We do have plans to increase usage. 

We have about 30 automations in place. That means about 60 to 70 people are using it. They work in shifts and they'll come in and they'll use their bots to process stuff while they do other stuff. 

Technical support is great. In the times we've used it, they've come back relatively quickly.

I started with UiPath a long time ago and I actually worked for Automation Anywhere. I was head of their cognitive product. Therefore, I used them for a while. They're not a bad product at all. They're really good, however, their scalability is a little bit of concern. For us, coming back to UiPath was probably a good decision.

The initial setup is complex. However, that's okay. It's also not supposed to be easy. You have to learn a little bit about what you're doing. Any technology would be a little bit complex. Once it's in, you can get that learning curve moving. With the actual users, that's where the trick of the implementation piece comes in. Once you're through it, however, that's where UiPath becomes really tremendous.

The deployment was maybe 60 days, however, it wasn't necessarily just because of UiPath. In banking, there's red tape. It takes time to get certain aspects approved. It takes time to get the right infrastructure in place. The enterprise has to be willing to put the time in just as UiPath has to put a certain time. It's a blend. As we were implementing, we were still putting things together and setting up governance. It was not just the technology. You still have to prep on the business side.

In terms of maintenance, on my team, I have about seven people, three engineers, a couple of business analysts, and a couple of PMs.

The pricing could be a little bit better for document understanding. I ran the pricing scheme for intelligent documents. With understanding at Automation Anywhere, there's room to maneuver. They can do a little bit better in making it easier for customers to dive in. I know it's available, however, it is what it is.

The organization evaluated Blue Prism, Automation Anywhere, and UiPath. 

We went with UiPath due to the fact that they gave us a good deal and we wanted to try it out. We started little. At the hedge fund, we're actually now at over three bots in production. Automation Anywhere's a little bit pricey at the moment. We just kind of pulled the trigger on UiPath and it was a blessing. 

We're just customers and end-users.

While we are on-premises, we're starting to use the cloud including some of the modules from the cloud, document understanding, task minding, et cetera. We're using the latest version of the solution. 

I'd advise those considering the solution that there's a secret sauce to it. It's not just the technology. People need process systems and a really good partner. That's how you get it done.

I'd rate the solution at an eight out of ten.

We were with the Air Force and had really a lot of different use cases including finance, credit card transactions, flight authorizations for training missions, et cetera. There are a few hundred use cases.

UiPath has improved the way our company functions. For our customers, for the Air Force, they've seen a lot of enthusiasm around the ability to develop their way out of mundane work. For those individuals, it's been a good cultural improvement. That's really been the biggest thing for them.

The developers like the studio interface better than other RPA providers that they've used in the past and find it easy to use and can provide a lot of impact.

The ease of building automation using UiPath has been great. We actually have done them with airmen, with people that are in the Air Force. We've done training and workshops such as one-week workshops with about 250 airmen. Most of them, 80% to 90%, have built bots that work in production with basically little to no training. They can do a lot without any development experience whatsoever going into the solution.

The solution has saved costs for our customers. Overall, it's tens of millions of dollars there for a potential return. They're still working on scaling that out. However, bots that have currently been built could be spread out across the entire Air Force, which is 650,000 employees, and would have about $30 million worth of potential benefit.

UiPath has reduced human error. With one particular use case, we did with flight authorizations, they had to compare your names off of a PDF to a 40,000-row spreadsheet. That not only saves time, it also reduces that error dramatically as the bot can go and find the row in the spreadsheet and then match it exactly as opposed to somebody looking for it manually.

It has saved time for our customers, equally likely $30 million in potential savings and allowing for a shift to higher-order work.

We’ve used UiPath Academy courses. We actually have a new employee training right now using UiPath Academy, and we recommend it to our customers as well. It's fantastic due to the fact that we're not spending very much time onboarding new employees. We're letting them go do the academy and then help them in assisting where needed. That's a huge benefit for us as we can continue to do our job rather than focusing on onboarding. Users can also self-lead, and new developers can go and utilize it without a lot of interaction from others or a lot of help from others.

The functionality where you can quickly convert your code from Studio X to Studio is really nice.

The StudioX interface is too different from Studio. We have a lot of people and we'll go in and start people with StudioX and they have trouble mapping to StudioX from Studio.

I've been using the solution for 18 months.

The stability has been very good. We've had no issues with stability at all.

I haven't seen any issues surrounding scaling. We're looking at one of the larger implementations of UiPath that exists right now. We were looking at a 250,000-user solution, however, we haven't done it yet. Therefore, it's hard to really comment on that.

In terms of technical support, our people have used it, and I haven't heard any complaints, although I have not used it directly.

We did previously use Blue Prism and Robocorp.

I prefer UiPath due to the sales support for this specific Air Force opportunity. We started with Blue Prism. We switched over to UiPath due to the fact that they were getting some traction inside the air force, and then we got really tightly in the line with UiPath. For me, it's not as much a software bake-off to determine which software is better or worse. It's really the attraction the customer has, and UiPath is the market leader. That support is really what's driven us to UiPath.

UiPath has a good attendance solution, which helps to ease the adoption. Our developers' feedback is that the user interface and development methodology are better in UiPath. That's why they don't want to go back to the others.

I am usually involved in the initial setup of UiPath. Our initial setup is really unique due to the fact that we're installing it in a government cloud. That is fairly complex, however, that’s very specific to that use case. Therefore, there are lots of challenges with that, however, that's more of a government problem than UiPath.

On average, for us, the setup takes a long time. It's taken us months as we have to get through these approval processes and things like that. In terms of the actual setup itself, it’s pretty fast and takes maybe half a day.

In terms of pricing, UiPath is fine. It is what it is, and I don't find it unreasonable.

Our situation is really unique due to the fact that we're trying to sell an enterprise license agreement through the Air Force. It's a pretty unique licensing situation.

It's my understanding that we are using the 2020.10 version.

We are just using the studio and the automation. Due to the fact that it's the Air Force, we're really focused on just the pure RPA piece of UiPath.

Our clients do not use AI functionality from UiPath right now.

I'd advise anyone considering the solution to go fast. What we see a lot is a lot of go fast and plan for scalability from the beginning. There's a ton of potential out there, however, we see people getting bogged down in a lot of different things instead of really just automating and developing automation as quickly as possible.

I'd rate the solution at an eight out of ten. Any software product is really difficult to be a ten, to be perfect. An eight is probably as high as I would go for any software product. It does a really good job and it's easy to use and scalable. I've had no complaints about any of it.

I own the robotics process automation program for our life safety segment. I also own the mergers and acquisitions project management for our life safety segment. We've started out by using UiPath specifically for mergers and acquisitions when migrating customer data from the acquired companies to our standard ERP. We're also implementing sales and use tax, filings, and things like that as well.

With our most recent robot, we transfer information from acquired companies to our ERP. Typically, it would take about six temp associates for about four to six weeks to clean the data and move it into the ERP. About three weeks of that would be actual data entry. With this product, we took that three weeks of data entry, times six people, and rolled it down to 12 hours of robot running. It was a pretty significant amount of savings for us.

Citizen development is great. With it, it's easy to develop or have self-developed robot intelligence. For example, instead of having to hire a developer, you can make the robots do what you need using the UAPs studio tool. This has been the most valuable aspect. StudioX specifically for our newer citizen developer is useful and I really like using Studio for myself.

We have seen a reduction in, for example, time, and not necessarily in human error. For example, we did an interesting analysis. We wanted to see what the human error rate was for entering data, and, due to the fact that our ERP is Microsoft Dynamics 2012, capturing some of that data is a little bit harder. We structured error rates based on entry. What we did was we created a robot to go back and check all their entries to see if they were missing anything. Oddly, the errors that people were making were nominal. I don't see any data that showed that we necessarily reduced error rates. It was really the people aspect of the process where there were time-savings based on the needed amount of human input. We've been able to reassign workers to more valuable tasks where we can't assign robots yet.

We do about four to five acquisitions a year and those are typically six-week processes for each one of them. We could say that we save about 25 weeks of labor in a year, and that robot will be about a week's worth of labor. Therefore, we save about 24 weeks of labor.

We've been taking some UiPath Academy courses. We've actually found it more helpful if we chose UiPath South American Developers to teach us to build as we're building. For my team specifically, it's been really helpful to have an expert involved to say "this is the use case that we want to do" and have them walk us through building a specific robot. That way, it's real-life experience versus a video-based session. While the academy is helpful, hands-on experience is just much more valuable.

UiPath Academy courses affected the process of getting employees up to speed. It affected it a little bit. It probably more affected our decision to use UiPath over Automation Anywhere, or even the Microsoft RPA program. Just the fact that there was so much available content that we could lean on if we needed to was huge. The others had content, however, not anything close to UiPath's capacity.

The on-prem orchestrator was an issue for us. When we bought it, it was a mistake. Our IT team thought it would be the best option for us, however, it's way more complicated to use. Out of the box, it feels more complicated. That said, once you get to know it, it's fine, however, it was incredibly hard to set up on our enterprise systems. Whereas, with the cloud deployment, we were live and up and running in an hour.  The initial setup took us about two weeks. That was a little bit of heartburn. It would be helpful if UiPath could offer some sort of support outside of a ticketing system.

I've been using the solution for about three months.

I've been pretty impressed with the stability. We've had a couple of minor issues that our developers helped us figure out. It's programming and nobody on my team are programmers. Some of it could be just user error, however, overall it seems like a very stable platform.

The scalability is really unlimited. It boils down to the organization's ability to implement a governance model quickly and successfully. I know UiPath has a governance tool or some kind of a framework, however, it is one of those pieces where it's way more expensive than us using our regular service channel tool that we already have implemented to do those submissions and approvals, et cetera.

In our organization, the users include two developers - me and then one of my assistants.

The only interaction we've had with technical support was during installation. The ticketing system and not being able to physically talk to somebody were difficult to deal with during the implementation process.

The on-premises implementation was a bit difficult. We knew that we were going to have to pay developers to help us develop the robots, however, getting stuff installed, our only method of support was submitting a ticket and the turnaround time on that took a while. Our UiPath rep helped escalate what she could. It would be ideal if there was a setup hotline or something that we could call right away. Sometimes it's just easier to talk to somebody than emailing back and forth. That's probably the biggest area for improvement.

We handled the initial setup ourselves. We do almost everything internally. We have our own IT team, including myself. Our solutions architects set it up with us. What we ran into in terms of problems was that the instructions were really not very good. We weren't able to appropriately install it as the instructions that came with it just weren't comprehensive enough. In terms of the instructions that were published online, we found a couple of instances where they were saying to use functions that didn't exist. These might have been a little out of date. Eventually, the ticket team was able to help identify that. I would grade the setup probably a C-minus, and everything else an A-plus.

We're so early into the implementation, the ROI is a wash right now. That said, our one robot has paid for our development time, and then someone will be able to use it on future acquisitions. We will likely see ROI within a year.

You can buy enhanced support, however, it's an additional $30,000 USD a year or thereabouts. That's just too expensive, honestly. The competition didn't charge for that. We also felt pretty confident in our IT team's ability to be able to dissect the instructions and install it. However, the instructions just weren't that good. We had one of our top engineers working on it and it took a lot of effort to get it installed correctly.

The pricing, in general, is fair. It's a little bit more than some of the competitors, however, it's a little bit more flexible than some of the others. There's value there. The OCR pricing is out of market. We need it, however, we're actually going to use some third-party bolt-ons due to the fact that UiPath is way too expensive.

We looked at Microsoft and Automation Anywhere. We also looked at help systems and Brick is one that we currently use and one of our segments, however, they're only a five-person company, which is pretty small. I wouldn't even put them on the same level. We were looking for shared services. We were looking for the best in class so we could take a solution enterprise-wide. In the end, we boiled the options down to Automation Anywhere, UiPath, and Microsoft, and UiPath was the winner.

In terms of Brick, they don't have a citizen developer model at all, so their developers have to do it. They are less expensive and they're a little bit more turnkey where they do it for you, however, they're really novice. The methodology that we've really bought into it was the community developer, as we want to empower our associates to figure out what works for them to improve their work-life balance. Using a service like theirs takes that away as we have to do the due diligence and figure out what fits in the bucket, what doesn't, as opposed to just empowering the person to do it. That was the key to why we chose UiPath.

The sales process was way better with UiPath. Our UiPath rep was far more knowledgeable about the product than the other options in that we ultimately had more confidence, knowing that whatever we needed, UiPath would help take care of, which was huge. My organization's a little bit disjointed. We try to go after what we feel is going to be impactful without a whole lot of due diligence. That's why, with UiPath, having that resource to lean on was helpful.

We use attended automation right now. Primarily this is due to the fact that the ERP system that we have really can't function unintended. It's a Citrix space environment and it has some odd security protocols where it'll shut down or refresh out for so many hours and it's not planned refreshes. It's hard for us. It's almost random. It's hard for us to build an unattended robot to deal with that. I'm sure we could, however, right now, we want to start with attended robots as we know what functions we need. We decided to go that route and eventually we'll add unattended.

I'd advise new users to make sure they have team buy-in for the concept. That doesn't mean necessarily getting the team to know exactly what they're going to be automating. You just need to make sure that they understand it's not about replacing people. Rather, it's about making their jobs easier. That was key for us. That said, most of my team was overworked, and they were glad to take on the project of lightening their load. Most organizations would benefit from making sure the communication is solid in that regard, however. 

I'd rate the solution at a nine out of ten. With better technical support, I would give them a perfect ten.

I am a software developer and I am a full-time RPA developer for my company. We create automation for internal purposes as well as for our clients.

I have implemented 15 to 16 processes end-to-end that cover use cases including Excel, front-end web-based applications, backend Windows applications, and sometimes Citrix. I have also done some Adobe Flash Player automation.

The REFramework (Enhanced Robotic Enterprise Framework) is what we use for most of our use cases.

We are using Studio for development on-premises and we use Orchestrator in the cloud.

UiPath has helped to improve our organization in several ways. Prior to UiPath, the company was using legacy methods of automation. These were time-consuming and required that more code be written. With the ease of use and speed at which automations can be developed using UiPath, the company is bringing on new clients and therefore, more business.

UiPath and the automations that we create help us to better utilize our resources. For example, a manual task that used to take between seven and eight days can be completed in one or two days with automation.

This product is bringing new clients to the business and nowadays, all of our clients require something to be done in the domain of robotic process automation. 

With respect to ease of use and building automations, UiPath is very good. I would rate them at least a four out of five in that regard, especially when compared to other products on the market. The ease of building automations makes them quick to create and it can be accomplished by people in the business sector.

UiPath enables and helps us to create end-to-end automations, and it divides all of the subtasks up in a good way. For example, monitoring processes is different from developing code, and each of these is separated such that they are independent, but we can link them together for the benefit of the process. This is important because I am a complete process developer, so having all of the different subtasks available in one tool allows me to best develop automation for our clients.

This solution has helped to decrease our time to value, which is something that is evident when you look at the automation we were doing previously. Our technologies included Python, VBScript, and other ways. These approaches took more time to develop and are a little bit more complex. With the help of this tool, it takes less time to build the same automation. It allows us to focus on building the logic and algorithms, without having to deep-dive into things like syntax. By allowing us to focus on the business logic for each process, it leads to significant time savings.

We use the attended automation feature and it helps us when it comes to tasks that require interaction between user and application, such as the necessity to enter credentials. It is quite helpful, in particular for BPM processes, and this is something that is important to us. The typical case is when somebody is doing repetitive work as part of their task. In other words, they are working on one task, and the bot is working beside them but needs the occasional input from the user. In these processes, the bot is doing 80% of the work and the user is doing the remaining 20%.

We use the AI functionality because it makes it feasible to automate processes that are quite complex. For example, Document Understanding and NLP from the UiPath Cloud are things that we use. 

The AI features enhance UiPath's capabilities and allow us to automate more processes overall. Previously, when we were doing a specific task, we may not have been able to fully automate it. With the help of AI, we can do more.

In previous iterations of our bots, before the AI features were used, we were not able to get all of the information that we needed from PDF files. This is specific to certain use cases, to present an example. The AI functionality generally gives us more data, whether from document understanding, computer vision, or otherwise.

UiPath has helped to reduce human error because the bot is doing everything and eliminates the opportunity for people to make mistakes in the process. UiPath has had a positive impact in this regard, although we have had successes with other similar tools as well.

UiPath and automation have helped to free up employee time and nowadays, they are more creative because of it. With many of their tasks automated, they have time to work on things that are more creative and have a higher value.

For example, for a task that used to take an employee 10 hours, they are now spending between three and four hours on it. In the remaining six hours, they can be more productive and work on more important tasks. This not only helps the employee but adds value to the company as well.

The selectors work to help automate at the front-end or backend of applications, and they are quite useful. If you use selectors correctly then the automation can be done in a systematic way. For example, selectors can be used for clicking tabs in an application, and what we do is create an algorithm with the correct logic to go with them.

UiPath has good recording features that help to create automations.

We use the REFramework as a template, which divides things such as the opening of applications, applying the business logic, using the queues, and closing applications. As part of this framework, UiPath provides a systematic architecture to us. We just have to understand and work with it by applying our business logic and coordinating effectively to create end-to-end automations.

I would like to see more AI-related features added. Improvements could be made to the models so that they are more compatible with data science and machine learning.

Better support for databases should be included. For example, interacting with SQL Server and SQL Developer would be beneficial features.

I have been working with UiPath for more than three years. The company started using it before that.

Stability is something that UiPath is working on. The new versions have added more stability and important features like test suites and the workflow analyzer. Adding features and improving stability is a continuous process.

In my previous company, which is a large MNC, there were between 700 and 800 people working regularly with UiPath. In my current company, we have between 400 and 500 people working with RPA using UiPath. As we continue to take on more clients, we will expand our usage.

There are a variety of roles for the people that work with UiPath. Some are developers, whereas others are set up or support teams. Our company is very heavily focused on this domain.

The number of people required for deployment and maintenance depends on the size of the process. A larger and more complex process requires a larger support team to maintain it. For example, a simple process can be deployed and maintained with a two-person team, whereas four people are required for a medium-sized process, and a six-person team would be used to handle a complex process.

I would rate the technical support between seven and eight out of ten.

In general, we express whatever concerns we have and then within a few days, we get updates from them. However, sometimes we have to elaborate a lot before we receive an answer. The documents and repository that they use for analyzing and improving our processes could be organized in a more systematic fashion.

We were using a variety of legacy tools that were more time-consuming and needed code development to a greater degree. These included things like Python code and Visual Basic scripting. There are still other tools that are being used, in addition to UiPath.

Prior to UiPath, approximately 80% of our costs were spent on developing automations. With the benefits that come with UiPath, the RPA costs are now only 45%. As the costs have decreased and the volume of automations increased, it improves company profit.

I have worked with Blue Prism and Automation Anywhere, and I find that UiPath is easier to use. However, to capture more market share, UiPath has to continue expanding its machine learning and AI features.

Automation Anywhere and Blue Prism are still being used for some processes in the company. We have switched away from them in some cases, opting instead for UiPath, because in general, it is easier to implement automation tasks using UiPath.

We have a setup and deployment team in-house that is responsible for implementation. They take care of the deployment for our clients and bring things into their production environment. 

The team does their best to keep updated on what UiPath features are available and what the current version is. If updates are pending then they will be aware of them.

The company is experiencing quite a good return on its investment in UiPath.

I began learning UiPath with the Community version, which is available free of charge.

Before choosing UiPath for any particular job, the company examines the process to see how complex it is. Based on the time that it will take to implement it, as well as the number of resources, whether in UiPath, Blue Prism, or something else, the decision is made. Different tools are used for different processes based on these assessments.

I started my UiPath journey using the Community Edition, version 2018.4. After I spent some time learning UiPath personally, I began using it full-time in my company.

We have several different teams that use UiPath in different ways. First, we have the developers, who do the coding and create the bots. Then, we have the testing team, who ensure that the bots perform correctly. Next, we have the deployment team and after that, there is the support team.

My advice for anybody who is implementing UiPath is that they need developers who are good with logic. They should come from a coding background with experience in logic, algorithms, have some knowledge of C#, and have some knowledge of HTML tags.

The biggest lesson that I have learned from using UiPath is that technology can be made more efficient by using these tools.

UiPath has all of the features that are required to make automation successful. It is currently just ahead of other similar tools on the market and if they continue to add features then it could be the market leader.

I would rate this solution an eight out of ten.

It's on multiple platforms like Oracle EBS and other IT applications. We have a few of the local government applications that the client uses. We have worked on multiple use cases with all of these applications. All of the client's major work is all through Oracle EBS. We have finance-related use cases. They have Seabridge applications, which are one of the applications that we are automating using UiPath.

Oracle itself has been very helpful when using this solution, thanks to the redundant task they've currently defined. All those are being automated. We mostly use the UiPath Assistant, Video, and Orchestrator. These are the only three products that we use day-in and day-out for our clients.

The ease of building automation using UiPath is great. It technically provides good features in order to develop, automating different kinds of applications using UiPath.

UiPath enables you to implement end-to-end automation, starting with process analysis, then robot building, and finally monitoring automation. It's usually very important. In some regulation cases, redundant cases, it’s been very useful. Instead of avoiding human intervention digitally, we are utilizing the UiPath to build up automation and run those in unattended mode.

If we could use the UiPath Apps feature, it would increase the number of automation and reduce the time it takes to create them. That said, at this time, I do not use this aspect of the solution.

UiPath has reduced human error in some cases. For example, a client has monthly payroll activities, which have to be done for multiple entities and in multiple in order to ensure the reports to be pretty good. It's a huge asset, having these multiple entities. It takes a lot of time for a human to execute the task. Here, automation plays a key role and it creates everything automatically through unattended mode. Of course, when a human is involved, there are chances for errors, such as missing the entities and updating the parameters. All of these things are instead being taken care of by automation. The likelihood of error is removed when the human intervention is.

The product has freed up employee time. It’s likely freed up more than a day, an average of 12 hours at least. That’s 12 hours per day. It allows our employees to focus on more high-value work.

We do use the Apps feature, however, it hasn't really helped reduce any workload. Everything is dependent upon the client's local language, which is Arabic. That is the major reason why we could not implement or utilize much of the Apps. It's not able to recognize Arabic versions properly. That is the challenging area which we are observing currently.

The solution is helpful in terms of speeding up or reducing the cost of digital transformation for our clients, however, the license cost is a little high. We are facing some challenges in the form of money. The license is costly. 

While employees can now focus on more high-value work, I would not go so far as to say it has improved employee satisfaction.

In UiPath, we have multiple products and recently there have been many product videos. There are videos around customization, deployment, et cetera. are all scattered all over. There are different products and different server setups and various other things, however, it is not organized. If it was simplified, it would be much better.

It could be more user-friendly. There are so many offerings and configurations and customizations that make things a bit complicated. Streamlining it would be ideal.

There are a few small things that should be included in UiPath. There are a few, although I can’t remember all. One, for example, is, when we are sending an email, we should be able to set up options and customize it a little bit. At this point, we need to create custom code and then go through APIs if we want to customize. It should be a built-in functionality, however.

I've been using the solution for two years now.

Stability-wise UiPath is good, however, it releases twice yearly. Therefore it will be a little hard for people to upgrade in-house each and every time. Clients also question why it's necessary every six months to upgrade. It won't be reasonable for the management. Every time when an upgrade is available, we have to complete the regulation for the previous use cases and whatever we already have deployed at production. 

When redeploying, everything is kind of a hectic task. Once in a year is okay, however, multiple releases in a year is a bit much. Clients would not be aware that yearly this many releases are happening and every release will have something more to add, that there are changes. Having to adapt to changes is something that is very difficult to make the client understand.

The solution can scale. 

You can use the application to automate any kind of application or any kind of use case. A few of them require some customization, using other technologies. 

Already we have some 25 bots running in production and a few of them are about to deploy to production and the client is looking for some more use cases. We are looking into a few more use cases that are in the discussion stage as of now. We are increasing our use cases and expanding usage.

The technical support is very helpful, however, there have been cases where we have had some urgent issues and support seems to move at its own pace. They won't rush for you. They don't seem to understand our concerns and they seem to only focus on their own timelines. 

Our SLA expectations are not always matching theirs. Even when we mark something as urgent, still there's a timeline of two to three hours. In that time it'll be hard to hold on.

Our clients did not use a different RPA solution before UiPath.

I do not have any other RPA solution experience beyond UiPath.

I am the solution architect who setups.

I was working on the 2018 version of UiPath. The 2018 and 2019 versions are very easy and very straightforward. There were not many changes or many complications in order to set up or upgrade. However, when it comes to 2020, from 2020 onwards it's very complicated.

Now there is an IAS. There is no connection string update. We cannot update any connection strings, and yet we could in the 2019 version. From 2020 we're not able to do the changes at all unless we go further and do another upgrade or something like that.

Earlier it was straightforward. Maybe there was a little bit of conflict, fine, however, now that it's split into multiple things with a conflict DLL file, orchestrated DLL file, identity server file, then an app setting the adjacent file. That is gathered completely into all of these things, where until and unless you have both end-to-end documentation understanding, you cannot go ahead and do anything.

On top of that, there is the SSL certificate. Until 2019 we didn't require each and every robot or a development machine to have the same SSL certificate. Now, we have to export and import to all the machines and add the user's perspective.

From the licensing perspective, licenses were straight, and there was no migration required for the license to be utilized in any of the versions. From 2020, there is a license migration required from the UiPath end. We now need to contact UiPath for that in order to get this migration done.

All of these changes, as well as the identity server database creation, everything has a kind of impact on the ease of deployment.

Upgrading doesn't take much time, however, users deploying the solution should have a ton of knowledge about each one of the steps. They need to remember everything in order to perform the upgrade or else something might be missed. Even if you miss one step you will have to spend hours and hours in order to rectify that.

For the 2020 version, for the initial deployment, I did not actually do it from scratch. I just upgraded. That said, if a user wanted to do it, I would estimate it takes more than a day to complete.

The implementation strategy depends upon the requirements of the client. For example, if it is on-premises versus if it is on cloud and/or if the client is looking for Elasticsearch or Insights or test automation, et cetera. All of these things will be dependent on the other. If you ask for Insights, you need to have an extra server setup for that. The same thing follows with the test automation and SQL database. What we call roles and responsibilities also will be dependent.

The unattended licenses are a little costly. That's the challenging part for us. That said, with the continuous support to the client, as we are increasing the use cases, it will lessen the cost probably by the middle of next year. At least, that’s what we are hoping for. We hope to see an ROI then.

The license cost is a little high. Unattended modes are really costly. If it's not as costly, then we could propose and purchase the licenses. Of course, we get discounts from UiPath, however, just for 10 bots, not even 10, if we load 5 to 10 unattended bots within the production orchestrator with the three development licenses, we have to pay for them twice. I'm not sure how much it is exactly in terms of the dollars, however.

My company does not have a business relationship with UiPath.

We do not use UiPath in a contact center environment.

We use completely unattended automation. 

We do not use attended automation at this time, or AI, although we are aware those are options. We're looking forward to AI and it is part of the reason we recently upgraded to the 2020.10 version.

It's one of the best tools where you can work for automation. If you have more redundant work, then it is very helpful.

Except for this upgrade and installation initial steps, apart from that, the solution is pretty easy to use.

I would rate the solution at an eight out of ten.

We deal in banking and finance. The use case is based on the transaction dates. For example, how customers are using credit cards, net banking, transactions, and what components they are buying. We gather this information in order to provide a CIBIL score. 

We do have multiple applications, which are provided to the banks so that they can work without taking much time. We have a set of test cases that need to be automated and we'll run it up. 

As of now, we test and we usually have a CSED pipeline as well. We are not only restricted to any one of the features in UFR. We are using Citrix, among others. 

The solution makes it easy to build automation. Earlier, we used to collect the data and create a hard copy. Now, these are all processes that are automated. There are fewer human interventions that are required to collect the data from the email or collect the data from the hard copy. It is auto-generated through auto-generated mail. It will collect all the details and save them to a repository. Based on that, our support team is providing the solution to the customer, and it's much easier.

UiPath enables us to implement end-to-end automation. These processes are very complete. Where there's not a single person is in practicum, however, it's only deployed in our productions. 

They have included the chatbot. Therefore, if the customer is having any issues related to any of the products, they will raise their queries. We will log these queries through a bot system, and this will get notified to the escalation team. They will locate into it through banking domains or through the solution of it and providing the solution on emails. It's very helpful.

End-to-end coverage is one of the best features. If their service display is not good enough, or if they are facing any issues, we can sort things out faster, which makes customers very happy. They are getting the solution on time, and they are running 24/7. Human workers are not able to provide each and every solution on an immediate basis, however, by using the solutions, we have got a solution for the end-user that responds immediately so that they are satisfied and their needs will be fulfilled much faster.

As of now, we are using attended automation, however, we also have created some of the use cases, which are going to be linked through unattended automation. Attended automation helped to scale RPI benefits in our organization, by automating department or all specific processes that require human-robot collaboration.

For example, in one project, which we used as a test, typically the turnaround would have been 15 days, however, with UiPath, we were able to churn out this product in 30 minutes.  It's amazing how much we are saving in terms of time. We've been able to shrink timelines.

We do use UiPath's AI functionality in your automation program. The complexities are always a part of the banking industry as data is from many places and over a large amount of time. However, when we talk about the calculations, it's when human beings are involved where it really takes a while to get a task completed. With automation, we can shrink that down to 15 or 20 minutes and know in that short amount of time a person's complete financial background and if they are credible or not. This customer doesn't have to wait so long to get the results they need. 

UiPath's AI functionality has enabled us to automate more processes overall. Now, for example, it's feasible to process data, and, if we have to, get the data explained very simply to calculate a score and find out if a person is genuine or not. We can look at credit histories, transactions, et cetera, and based on that, be able to process requests in order to enable users to get loans in seconds instead of days or weeks. 

UiPath both speeds up and reduces the cost of our digital transformation; it increases processing speed and saves costs that would otherwise be taken up in longer-term tedious tasks.  

I've used the UiPath apps feature, however, I cannot say it's fully required for our processes. That said, it was very helpful when we did use it. 

UiPath has helped us reduce human error. We can achieve our goals, as mentioned, in 30 minutes, without having to manually go from one stage to another, which may cause errors. It frees up our employee's time as well, to help improve their focus. That, and, within a week's time, we can save 30 hours on a single resource. It allows those employees to really focus on higher-value work. Employees are happier as they now have the time and space to build their skills.

Overall, UiPath has reduced the cost of our automation operations. This reduction is around 30% savings. 

The product is well-integrated with different tools that can help with logging, et cetera.

The task capture is great in that we have all of this data we are receiving that's automated and we don't need to invest much time in creating documents.

For a few of the projects, we have saved money, however, on a few of these projects we've noticed less revenue. The orchestration cost is a bit higher when we are working on smaller projects.

From the improvement perspective, I am from the testing background, and UiPath has recently released some announcements related to scrums. I would be happy to see their products be involved with scrum teams.

Just like they have data for the JIRA automation, maybe if they can include some of these options in the Rally solution. It's a tool that is used locally for various projects and having automation activity included there would be useful to us. 

From a migration perspective, if we can get something better than the manual process that would be great. It would be nicer if it was smoother for those doing implementations. 

I've been using the solution for five years. 

I can say it's a very good tool from the RP perspective. It is helping us to get our work faster, saving time as well as offering multiple functionalities. We haven't had any issues with it. 

Everything is good - except the capture part. They could improve on that as we are getting less accuracy as compared to the other functionality. Other than that, the rest of the components are fine.

The scalability is very good. 

On my team, somewhere around 14 people are working on the UiPath product. There are several other teams also on it. Likely, there are around 50 plus people in total on the solution.

We are regularly using this product. I cannot say I'm not using a single day. 365 days a year this solution runs, as these processes are basically used on the weekends as well. Based on the schedule, it is pretty much always running in the UAT or QA environment. 

How much we use it depends on the products. If we get more products, we will increase usage. 

The customer support is very nice. Most of the time, we are getting a resolution from there.

I would rate them at more than eight out of ten. Over the last three years, I've been interacting with the web team on customer support. I tend to get an immediate response from their team for the assignment of my ticket, and they schedule a call. However, in some of the operations, it's not possible to directly interact on the WebEx.

It's important for us to have them extend their communications or extend their environment. Not every organization can get support as they offer it. Using Microsoft Teams or Zoom or a more popular platform may be helpful.

We did not use another solution that is similar. We previously used an automation tool that was purely used for the testing perspective. We decided to move to UiPath as it was an easy-to-use solution. However, I was not a part of the RPA tool decision-making process. 

Earlier, it was a bit complex as we had to configure our robot with the orchestrator or the studio that was providing details. Now, when we are installing, everything is taken synchronously. We don't need to enter the required areas. It is automatically catching that from that environment.

The time it takes to deploy depends on the system resources or the system specifications. Usually, it will take around 23 to 40 minutes for the installation, however, now that they have improved their installation time as well, it may only take 20 to 30 minutes.

For us, the deployment plan is basically to focus on the data perspective. We don't want to lose any of the aspects of the data, which is already running, so we do take a backup first. The orchestrator has a different environment structure, which has already been configured like a development rather than a UAT.

These are the phases that we are using on a regular basis. Once it is certified for the first stage, only then does it move to the next phase.

We require 22 people to maintain the product. They are largely comprised of the DevOps team. 

While the solution is a bit expensive, we do see ROI. When we compare the ROI with the expenses differently, ROI is on the higher side. Of course, for the organizations who have a small product base, who may have less automation required, will find that expenses are higher. The more you automate, the more you save.

However, in relation to sharing actual data points, that's a bit tricky.

As compared to the licensing costs or the pricing of other tools like Automation Anywhere or Blue Prism, it's a bit cheaper, however, when we talk about the open-source tools such as Robocorp or Robot Framework, the cost is on the higher side. Microsoft Power Automate is also cheaper.

There are no other costs beyond the licensing. 

We are just customers and end-users. I'm an RPA lead.

We are using an operating system related to Microsoft and several other features related to Microsoft. If they offered this type of product on a regular basis, that was less costly and had the same compatibility, security, and features, we'd likely adopt it. 

I'd advise those considering the solution to check the processes and compare them to their potential ROI. A company needs to consider if the tools will help them based on their environment and goals. It's important to first analyze the internal capabilities before jumping in. If they don't think they'll be getting the ROI they desire, they should look at another tool. 

I'd rate the solution at an eight out of ten.

I have worked on two UiPath use cases. The first use case is for the IT Infrastructure team for submitting server requests. They receive a request from a third-party portal through email, and then my bot reads the email and fills in the details in the company portal.

The second use case is the data extraction from Word documents. The team receives Word documents with some important contract information. I extract those paragraphs and put them in the CSV format given by the customer.

We are using UiPath Studio 2020.10.2, and the Orchestrator version is 2019.

I heard about UiPath RPA in December 2019, and I went to the UiPath Academy website and completed their learning plans. Till March 2020, there was free certification, and I completed the free certification and kept on practicing. I showcased my skills to the management in my company, and I got into RPA projects. The certification has helped me in getting good projects. It has also helped me with my work for the use cases. My position is now better as compared to the previous years, and my work is also good. 

They provide end-to-end solutions. They have UiPath Studio for the development, and they have Orchestrator for package deployment. We can also monitor the performance and execution in Orchestrator. All these are helping us in managing end-to-end automation.

All UI automation activities in UiPath Studio and REFramework are useful. UiPath Orchestrator is also valuable. These features help me a lot in my projects. 

UiPath Studio's UI automation activities help me in easily developing automation. It is difficult for RPA developers to write complex code because no one knows everything about all automation areas. For UI automation, it is not mandatory for a developer to know how to write the code for the element on the screen that needs to be clicked or typed into. The UI automation packages of UiPath provide built-in activities, and developers can directly drag and drop and indicate the element on the screen that needs to be clicked or typed into. 

REFramework is a template using which we can prepare quality workflows for the transactional processes. It has very good error handling, retry, and logging mechanisms.

We can monitor robots in Orchestrator. We can check logs, monitor the performance of each robot, and divide robots into different environments. These features are very helpful for me in managing my work. If I have two or three robots on a set of machines and I want to define my process only for these robots, I can add that process into the environment. My process will be executed only on those robots. This is a good functionality.

For every transaction, there is the queue functionality in Orchestrator. I can go to a queue and add each transaction item to the queue. For every transaction, I can check the logs. I can also check their logs based on the jobs executed. We also have triggers, so we can schedule our jobs with the help of triggers. These features are helping me a lot in managing the performance of my robot and understanding how my robot is performing.

They have UiPath Forum where I can ask any questions. Many UiPath Most Valuable Professionals are on that forum, and they help us a lot. We get quick replies. If anyone is having any challenges, they post their challenges on the UiPath Forum. I can go through them, and if they are already solved, I gain knowledge by reading those solutions. If not, I try to answer them. In addition to gaining the knowledge, I'm getting some visibility in the UiPath Forum. All these things have really helped me a lot in increasing my technical level and expertise and getting good work.

UiPath Studio supports three types of workflows: sequence, flowchart, and state machine. Flowchart and state machine are good. Sequences are also good, and they're for linear workflows. However, in a sequence, as we keep on dragging and dropping the reusable components, the size of the screen increases. If we drag and drop the conditional or looping activities on the site, the screen size increases in length and breadth, and it becomes too complex for a developer to navigate between activities. 

All programming languages, such as C, Java, Python, or Visual Basic, have script-level support. So, we can reuse their functions because they support scripting. For example, if we want to use any reusable components, Python has modules, and there is a way to import packages. For complex automations, if we can write a script, it makes it easy to manage and know the line on which we are getting a syntax error or a runtime error and how is the structure. If I want to modify the logic, it makes it easier to know in which block I need to make the changes. So, it is easy to navigate in the program. Instead of the drag-and-drop blocks, UiPath should have support for scripts such as VBScript and PowerShell. It should support scripting even for complex automation.

The user interface for logging should be improved in Orchestrator. Currently, the logs in Orchestrator show how many hours ago the execution is completed, but it doesn't say how much time it took for a particular execution to complete. It just gives you a rough idea that it started three hours or one hour ago. It doesn't tell you exactly when a particular execution started, and at what time, it stopped. To get a clear idea, I need to click one more button and go to the details of the log. I need to check the start time of the first log and the end time of the last log in the same job, and then I need to calculate the difference to know the exact time it took for completing the job. Instead of doing all that, there should be a column that gives me the exact amount of time in minutes and seconds. It will help me in understanding how much time each execution took and what I should do to improve the speed of the execution.

In my current project, there are no intelligent automation requirements, but I have learned it recently. Just today, I completed the UiPath AI Center course. I also have some basic knowledge of machine learning. They're giving us options to use the out-of-the-box models developed by UiPath and their third-party vendors. With our internal data science, we can also develop our models, integrate them through UiPath AI Center, and deploy them. They're giving us an option to use them as a part of our RPA workflows with the help of the UiPath Studio activity called ML Skill. So, it becomes very easy for RPA developers to integrate machine learning models into their automation workflows, which is very nice, but I feel there should be some more improvement. They should give more visibility into how much time a model takes to finish the training and on how many algorithms it is running. They should also give visibility into which algorithm is best suited for my requirement and which algorithm is giving the best results for my requirement. If they can also give such insights in the same UiPath AI Center, it will help me in picking up the correct model and algorithm for my requirements.

When it comes to intelligent automation, machines use machine learning. No machine learning model can reach 100% accuracy or give 100% accurate output, which is a limitation. However, there is a possibility to increase the accuracy by tuning the parameters. So, UiPath should give more visibility into their models, how the pipeline is running in the AI center, and which factors can improve the accuracy of my model. Such insights will be useful for me in improving the accuracy of my intelligent automation.

In December 2019, I started learning UiPath, and I became an RPA developer in November 2020.

Until now, I have seen good uptime. There were no disruptions in data. I've seen the services running properly 99% of the time. Their logging mechanism, job schedules are also running properly in Orchestrator. So, it is a stable environment.

We're getting good support from UiPath. I would rate them 75 out of 100. Most of the time, I get fast and good replies from the support team. Sometimes, I receive late replies, or they don't understand the question properly, and I need to explain multiple times, but they are mostly good. 

I have worked on different IT process automation tools in the past. Their support did not respond as fast as UiPath's support, and they put the tickets in the suspended mode for a long time. They also didn't understand the question a lot of times and took too much time to analyze the issue. 

I also have the advantage of talking to my Infra team because we've deployed it on-premise. They can act as the first level of support and check if there is anything wrong with the on-premise server. If it is related to UiPath functionality, then we raise a ticket with UiPath support.

It was already set up when I moved to this team. I was working in IT process automation, and I moved to the UiPath development team. The setup and licenses of UiPath Orchestrator are managed by our Infra team members. They provided me with the licenses and links to the UiPath Orchestrator. So, I make use of the resources already deployed by my team. I just build and publish the packages to UiPath Orchestrator.

I have not deployed anything in the live environment, so I cannot comment about the return on investment. I've seen my colleagues deploying it, and with the help of data automation use cases, they have reduced around 10 hours per month for each support team. For my use case, we will be able to reduce at least one or two FTE for the support team when it goes live. I'm able to predict this because I have developed and tested many test cases for my use cases.

I only know about the community version. They give us two robots as a part of the community version, and they are enough for my practice and personal automations. For the office work, my Infra team checks the licenses needed for a particular use case, and my management team manages the pricing and licenses. 

Nine times out of ten, I would recommend others to use UiPath. I have also worked on other IT process automation tools, and none of them provides the functionality, support, and community like UiPath. I had conducted a survey on LinkedIn and asked about the RPA tool that people preferred. I got 60% of the votes for UiPath.

From the development perspective, I've seen a lot of improvement in the UiPath services in the last one year. They're giving more out-of-the-box models for the AI Center, and they are also improving their courses. They are also introducing new functionalities such as the orchestration processes in which you can use persistent activities, and your robot can wait for the human task to finish, and then it can continue its job. If they make any enhancements required for our current automation, we will make use of new UiPath functionalities to enhance our automation.

They have released two new versions of their certifications. One is UiPath Associate Certification, and the other one is UiPath RPA Developer Advanced Certification. I have completed the Associate certification. For these certifications, we have learning plans. There is recommended training, and everything is given on the UiPath Certification Program website. We have the option to check their recommended training and do the practices. They also guide us about how to book the exam from the Pearson website. Going through the recommended training and doing the Associate certification has increased my credibility. I've gained more trust in the company. It has changed my career. So, UiPath has played a prominent role in my career.

It can reduce errors by 100% because a machine can give 100% accuracy and work faster than humans. Just like all RPA tools, UiPath can provide 100% automation accuracy for rule-based automation. You also get better speed because machines are faster than humans. When it comes to intelligent automation, machines use machine learning, so there is a limitation. No machine learning model can reach 100% accuracy in automation.

I would rate UiPath an eight out of 10. 

We are a communications company who works with a lot of clients in our country. Now, we started using automation when working with business clients. Many processes were being done manually, e.g., activation of numbers. In order to alleviate the work of our sales team, this process was automated.

I haven't automated any of my work because the queue for processes that need to be automated is large.

My company uses Studio for our developers and StudioX for attended robots.

It is very important that we can scale automations without having to pay attention to the infrastructure. After one year, we have already automated almost 200 processes. Since the number of automated processes was large, a lot of people's time was freed. This solution is very important because we have a large subscriber base in our country, so we have become very efficient.

UiPath enables us to implement end-to-end automation, starting with process analysis, then robot building, and finally monitoring of automation. This is very important to my company because in the future we will have contracts with UiPath to sell licenses and provide the same experience to other companies, helping them automate their process. Therefore, it was very important to implement the entire end-to-end process in our company.

Attended automation has helped to scale RPA benefits in my organization by automating department or role specific processes in sales and HR that require human robot collaboration. This is important to my company. The department who works on automation of internal processes has had a lot of meetings with our employees. They realized that employees could be against their automation processes and sabotage them. This didn't happen, but they have effectively implemented the attended robots for our employees' work by explaining to them that the robots are not a threat to their job. They would only be helping them, allowing employees to do something more important than doing repetitive tasks on their computers.

UiPath has helped reduce human error. We are working with clients where it is very important to provide them their necessary services. We are a telecom company, so we are providing activation of numbers, etc. If people are doing this manually, it can cause inconveniences for our clients, but it might also put the reputation at stake. For example, because when people do it manually, they can send out the wrong invoice. This is a huge reputation risk, because sometimes we are working not only with just a person, but with a business. When we work with other companies, it is important to do things accurately. When the robots do things, there is almost a 100% probability that they won't make any mistakes, like typos.   

The most important feature of automation is it can automatically detect things where people are doing things repetitively and spending a lot of time. So, people can actually do their real tasks, like making decisions and talking to clients. Therefore, people's time, which was busy with doing manual tasks, is free now. They can spend it on more interesting and valuable work where they can apply their valuable skills.

UiPath Academy starts at the very beginning with how to set up and navigate in UiPath. I noticed that the Studio and StudioX are both user-friendly. It is suitable for people of different existing levels of programming skills, even with those with zero background.

The process mining feature is not being used because my company had some difficulties with it.

UiPath could improve integration with other platforms, like the SAP platform. I heard that SAP has their own automation processes in their platform and they are trying to avoid integrations with RPA platforms. Sometimes, that can be difficult. UiPath's room for improvement is having the ability to integrate with as many platforms as possible.

I have been using it for about three weeks. I have been practicing some tasks and just started learning, but I don't have any advanced development skills.

My company has been using it for a year.

We have automated hundreds of processes.

There are about 30 people on our sales team who are using it. The HR team also uses it.

We didn't use another automation before UiPath.

The initial setup is straightforward, based on what I have seen from UiPath Academy. On the platform, there are videos which describe how to set up. You just go to the platform and download the setup package. You have to set it up on your PC, then open the application. Once the application has been opened, you need to sign in with your email. For the first step, you need to add your email to the application, so email is sent automatically to you when you sign in and the signup is complete. Then, you can start using the Studio and StudioX. It is very convenient because both of them are in the same application, like an all in one software. You don't have to set them up separately because everything is in one place. You can just switch between them in settings, which is very easy and straightforward.

We have people studying how to work on UiPath who are developers. Therefore, we have a whole department doing the setup in our company. I don't think that they are asking a third-party to come in and help. 

We freed up a lot of our sales team's time. For example, they can now spend more time with clients. We have successfully implemented attended robots for our sales team. They now spend half the time doing the job which has been automated. This has made our sales team happy. 

It is very costly to implement RPA. However, I think the benefits outweigh the costs over a long-term period.

Building automations is doable. I understand that it is hard. Some processes need to be adjusted to be automated. Even though sometimes it can take time to create processes for automation, it is still possible and useful to apply automation for many processes. 

I didn't have any background in programming previously. I chose the learning plan for beginners in UiPath Academy. It was very convenient that they divided their learning plans for people with different backgrounds, e.g., beginners or developers. The course is very well-structured and concise. It works perfectly for me and I have the ability to study in the solution without any background experience.

Because we managed to successfully implement it in our company, we now want to help other companies to implement their automation processes.

For my country, UiPath is progressive. It is important for people's mindset that they are able to work with robots and understand they are helpful.

A lot of companies in our country refuse to implement it, or they think it is very expensive, and they don't need this thing, but they should definitely go for it.

My biggest lesson was not to be afraid that robots will do my job. I learned that they are very helpful and can save me time that I can spend on something more useful, like obtaining new skills.

I would rate it as eight out of 10 because of its integration limitations with other platforms. It is also expensive.