UiPath Reviews

When I started at my company, they were building their RPA journey. I was the first person to help them do that. As no one in my company was aware of what RPA is, we needed to showcase and publicize what UiPath is and what RPA is.

I work for an insurance company and there are handwritten scripts that need to be scanned in, and this was the first use case that I had to work on. We used the OCR technology to scan handwritten documents and its capabilities are evolving day by day. When I initially started, it was not as robust as it is today. We had some challenges with the OCR technology, but today we are able to do it successfully with validations.

Right now, there are 24 automations of which 22 are in production and two are being built. These are all unattended bots. I also use this solution in a personal capacity to delete all the junk emails I receive as I usually get 20,000 junk emails a week. This saves me a lot of time. 

The UiPath's user community, in terms of the value that we gain by being part of it, is very helpful. If I'm stuck with coding, that is the place I go to get assistance. The ideas and the solutions that they provide are very helpful. There are a few people in the community who are very accurate and their solutions always work.

I have also made use of the academy. Currently, I'm taking the certification training and planning to get my certification done by the end of this year. It has taught me new ways of doing things including dynamic selectors. Previously, the bots used to break because of a selectors issue, but the dynamic selectors solved this. 

We have an internal process that is manual and takes three days. The first day involves pulling in the data, the second day involves validation and the third day involves delivering it to the relevant system. We automated this process using UiPath.

The errors have been minimized. Whenever something goes wrong, we immediately get an Outlook notification. This is when our business customers get to know that there's something wrong with the input data that they're getting. They can directly deal with the input information data team and get that information corrected and this usually happens within three hours. 

The OCR technology within this solution has been most valuable. We are able to scan handwritten documents and scrape their contents to be captured within the system. 

When I first started using this solution, the OCR technology was not that good, but it has since improved. Most of the handwritten documents are easily read by the OCR technology. 

I have been using this solution for three years. 

The stability does depend upon the applications we are using but overall the stability is good. 

This is definitely a scalable solution. 

The first time we had issues was during the setup and we haven't needed to contact the support team since then. Their support is really good and the solutions that they provided really worked from our side. They provided step-by-step instructions that really helped us a lot and saved a lot of time. Our initial estimate to get that UiPath deployment was two and a half weeks, but we finished that in three days. This was made possible by the support and the instructions received from the support team. 

I would rate the support for this solution an eight out of ten. 

Positive

I was the one who did the deployment. During the deployment, we had some challenges but received assistance from UiPath support. Even though we had some hiccups in the initial days, we were able to still overcome those with the help of UiPath support. The deployment took two to three days for an on-premises installation. 

Our business has been highly satisfied with the RPA solutions that we are providing thanks to UiPath.

The pricing for this solution is reasonable. 

We evaluated Blue Prism but felt UiPath is easier to use and offers better performance.

I would rate this solution an eight out of ten. I would rate it a ten out of ten if this solution worked better with our other applications. 

I would definitely advise others to consider UiPath because it is easy to learn how to use. A lot of documentation is available and accessible to facilitate learning including YouTube videos. 

When I was evaluating Blue Prism versus UiPath, the training materials were not the same for Blue Prism. Coding using UiPath is really easy and is mostly drag and drop. 

We use the solution to speed up automation. We were looking to overcome the challenge of handling vast amounts of data, and we use UiPath to create bots to handle that. Tasks can be automated, and human error is reduced.

UiPath improved our organization as it has many benefits; it's straightforward and quick to use, has excellent third-party integration, and simplifies all our task automation.

The software has an excellent UI; it's very user-friendly. The drag-and-drop options are some of my favorite tools, as they speed up the process, and I find that UiPath offers a solution for all kinds of automation.

The solution saves a lot of time via automation; a task that took over an hour now takes around two minutes, and it's all handled by bots.

We use the drag-and-drop options, and they speed up our workflows.

The pricing could be more friendly. 

We have been using the solution for one year. 

The solution is stable, it's a reliable software. 

The product is scalable; it has very good third-party integration and scalability options within the software.

We use the solution in our office, so there are slightly under 100 total users.

The community support and documentation are helpful. I required some training initially, and was able to learn using UiPath websites and YouTube videos. 

Positive

I wasn't directly involved in the initial setup, but it took our team one to two months to get to know the product well.

I'm not directly involved in the financing, but the IT team considers this product costly.

I would rate this solution a nine out of ten. It's an excellent product, but there is always room for improvement. 

I highly recommend UiPath as it's easy to learn and offers significant advantages for all kinds of automation. 

The solution is perfect for our requirements. 

We have multiple accounts sellable, accounts payable, corporate finance, and supply chain use cases. We have started some use cases at the factory floor automation as well.

There are so many benefits to using UiPath, but getting the buy-in is very important from the end users. We are seeing many hours saved with respect to automation. Automation should be on every project's agenda. 

Scaling at pace with regards to the industry has been the most valuable UiPath feature for us. I would also add that there are so many features in RPA. 

We are leveraging the UiPath Academy for our citizen developer program. We are asking them to train at their own pace. The courses are straightforward.

The adoption rate for this program is low, however. Out of the 150 citizen developers that started, only 10 decided to continue the process.

One way to improve the UiPath Academy, I think, would be to add some real-life use cases and take the students through the automation process. These would be good for citizen developers to start with.

We started our UiPath journey early last year. It has been a year and six months. 

UiPath is stable. The automations we have in place right now are stable. 

Over the past two years, I've reached out to them maybe twice. 

The initial setup was straightforward. When we started this automation journey, instead of going with complex use cases, we picked three simple ones. We started with the accounts receivable processes. 

Deployment took us six weeks. 

As of now, we have automated 160 processes using UiPath and saved many hours. We have saved around 60,000 hours. Although we are not directly reducing costs, we are avoiding the cost of hiring new people.

The solution is very expensive. It's getting harder for me to convince my management about licensing costs. 

Yes, we considered Blue Prism and Automation Anywhere. We created an automation using both of these and UiPath and ultimately decided on the latter. UiPath is more compatible with the other applications we were already using. Oracle's JD Edwards EnterpriseOne is our ERP and they partner with UiPath, so that was a major plus for us. Also, UiPath has very straightforward coding courses.

It is usually not easy to build a complex automation. The whole process takes about four to six weeks for a complex automation. Most of the time is spent on gathering the requirements. The development itself does not take much time.

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

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

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

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

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

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

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

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

We've had the solution for three months. 

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

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

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

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

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

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

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

We did not use a different RPA solution previously.

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

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

We realized ROI on our first robot. 

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

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

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

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

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

We do not yet use UiPath's AI functionality.

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

Our primary use case is to document image processing. We're six months in, so our first case was sorting and filtering the data, extracting the image, and determining if it's a certain type of document. If it is, it starts putting it into different buckets, which ultimately we'll run something to extract and put those into our data source. 

Our second use case is for the healthcare industry. We're looking at catalog data and a customer might want to know about a product. Is this product safe? Who provides this product? Is it on a contract somewhere? We go out to multiple different web sources to look up information about that document, put it back in our database, save it for that customer, then save it for any future customer that asks the same question.

We're looking at other things like taking snapshots of the image of the product. We also want to automate other basic automation, low-hanging fruit type functions, like automating uploads of data to sites, spreadsheets, contact-center, and Salesforce.

Longer-term, we want to take what we're doing in the document image and apply it to other areas of our business. We have purchase orders, invoicing, shipping documents, compliance documents, credential documents, a lot of images in this particular space. We'll go as deep as we can in the data processing side of things.

We're going through a culture shift to get to an automation-thinking platform as opposed to a lot of our business relying on BPO humans to do the work. Making that paradigm shift is taking time because we're only a week-plus live. If we prove the value, they'll give us more opportunities to make those big changes. But it's good that the business is thinking that they need this. Now it's just getting the community aspects of it.

The automation cloud offering helps to decrease the solution's total cost of ownership by taking care of things such as infrastructure, maintenance, and updates. 

Although we don't use it, document understanding for our use cases is very compelling, but it was a little cost prohibitive just out the gate. We are looking at it long-term now that we have the data filtered if we can more strategically apply it to the best data to fit it. But overall, the platform is very innovative. I don't think I can call out one particular feature. The ease of use of integrating to and from Amazon components, being a cloud-native application ourselves, has been really helpful in the development and the ease of transferring documents between our internal systems and platform.

The ease of building automations using UiPath depends on the use cases. Overall, the development is really easy. Where you run into challenges is in workloads that are highly rule-based. So we abandoned one use case where it had 50,000 different decision points. It wasn't worth the time. It wasn't a product thing. It was just too time-consuming of a process, something like that.

There have been some limitations as far as how do we execute our bots, when? This new release that they just mentioned today actually addresses a lot of our concerns around the integrations component that they recently released. If we could find an email instead of waking up and checking the email inbox. That's a big improvement we're looking to, but it wasn't a limiting factor.

I have used the Academy. It was really just myself and as well the one IT guy who's supporting the platform. Our office partner came in with the knowledge, but the course was really good. We came in with no RPA experience, and it covered everything from the basics of RPAs to the processes of identifying.

They recently addressed a major problem of kick-off processes for the integration function. That addressed a lot of the community concerns around that. If you are using queues, their queue system isn't as reliable as I would like it to be. 

One of our concerns is that we were not a Microsoft shop at all before bringing this in. That was actually my limiting factor in bringing in the software. We lost it below the party lines. The ability to address other workloads, Mac, Linux, etc., is going to be a game-changer.

From a new customer, new investment perspective, there are a lot of cost-prohibitive aspects that we decided not to add to our initial investment. We weren't sure if or when we'll figure things out for use cases.

I have been using UiPath for six months.

We want to triple our capacity and triple our workflows. 

I've only had to use support once, and it was more of a documentation problem. I didn't understand what I was seeing, and they worked it out within an hour. So far, they've been good. 

The cloud was up two days after we signed. Then to get our bot infrastructure up because it's Windows and we're in a Windows environment, it took us about a month to run through that and get the IT people and security.

Cloud solutions will save you a lot of headaches and time. We broke halfway through and decided we're going to cloud, not on-prem.

Reputation was a big reason we went with UiPath, as well as the growth and the ability to integrate specifically to the cloud which was missing in other solutions. That was a big plus. The ability to use something like document understanding and the ability to interact with internal APIs were also key features. It's not just web scraping and doing things in Excel or other things like that. We wanted it to work with our internal native applications.

UiPath has not yet saved costs for my organization. We're still going live and we're anticipating about a two-year ROI.

Make sure to understand your use cases before you sign your agreement. That way you're not idle for six to nine months trying to figure out what it is you're trying to automate.

I would rate UiPath an eight out of ten. 

There are lots of use cases. Mostly, there are many gaps in organizations that buy a lot of software and a lot of automation platforms like ERPs, however, they don't know how to actually create an end-to-end process and connect those systems. In those cases, they end up like small islands in a big organization. What I started doing was filling those gaps. After that, we use the RPA to fulfill that. For me, a lot of processing in Excel or some processes that needed multiple users to interact is what we use the solution for. We just capture those tasks and convert them to RPA bots. Basically, we've automated a lot of manual tasks.

We do not use UiPath in the contact center environment. In our case, contact centers here are really dependent on CRMs. Even using chatbots in contact centers is still very new in Iran. These foreign branches, these foreign companies that are in Iran, do not see any potential to use RPA in this scenario. 

Mostly, UiPath has improved my career. I am an RPA Developer, and without UiPath my job wouldn’t exist. UiPath changed my career. Due to UiPath (not Automation Anywhere or not Blue Prism), there’s a noticeable increase in the speed of development. I was a C# Developer and it's helped me a lot. Generally, UiPath is in the top 10 and has offered a lot of new technological shifts and people are talking about it more. When people are talking, there are great opportunities. There are now new voices that can be heard. 

UiPath is constantly listening. That's a good point for UiPath - it's always listening from its community to its top customers and interacting with comments. Due to the fact that it listens, it integrates new software, goes into end-to-end automation, and changes for the better. Someday they will have Autonomous RPA, a real Autonomous RPA that can actually decide like a true robot, not just a robot that works on a script. One day they will offer a true robot that can finally decide what to do in certain situations, not by just using something like document understanding that we call Machine Learning. UiPath is very, very good at giving true innovation to people. It’s a win-win for everyone.

RPA is actually something that can be executed, that can be used side by side with many programming technologies.

The speed of development in UiPath is very fast. For example, sometimes you want to do many frameworks and the budget is low, with the timeline being very crucial. With UiPath Studio and with the whole UiPath platform, it can be very fast to develop and deploy. That's the main advantage for me personally - that the speed of development is great.

UiPath enables us to implement end-to-end automation starting with process analysis, then robot building, and finally monitoring. They are all there. The one exception I’ve noticed is that end-to-end automation is still lagging, I have reasons for that. However, the monitoring of the robots or even using insights is there. They are the prerequisites for an RPA platform. They are great suites. They are necessities.

I like parallel processing. I like that a robot can do some parallel stuff while the user continues to do their own thing. If it needs interaction, we can just pop up a clear window or apps, for example, or through email, in order to inform the user about the robot's request.

AI Automation overall has enabled us to automate more processes. However, when we go forward and move forward, we see that we can digitalize those documents before it needs to be processed by an image machine-like OCR or even Machine Learning. For example, there are still handwritten documents. We’ve convinced many organizations to drop those handwritten documents and use digital products for us. Those are immediate time savings for the process. We are not using document processing anymore, for example, in a specific organization. For processes that still need to have handwritten or printed out documents, document understanding could be fine. I really hope, however, that they shift to AI, which is what RPA lacks. RPA lacks Autonomous Automation, that's something that everyone is waiting for. We’d like to have a robot that's actually using the computer with its own mind, not just the workflow we give it.

For end-to-end scenarios, UiPath is still growing. I'm not saying that UiPath isn’t good. There is a lot of potential. They're using UiPath Actions or Apps, for example. Dashboards ensure that end users can interact in a new way with robots or with the whole end-to-end automation. RPA is a technology that hasn't maxed out yet.

Someday, there will be no legacy software or very intelligent processes that will use APIs. It’s my understanding that UiPath bought some company that specializes in API Automation. For end-to-end automation, UiPath needs to integrate all those components, rather than task automation to process automation, real process automation. With RPA, if you read the HFS report, you see that the process version is actually not a process. It's tasks. Perhaps in their next LTS release, UiPath will actually gain to that point.

There are minor bugs. Every major software has bugs. That said, all are solvable, all are resolvable, and it's not a very bad thing.

Mostly, licensing must be improved somehow. Licensing is very expensive. Even in many industrial countries such as the USA or UK, UiPath is still very expensive. For example, Microsoft now owns its own RPA, Power Automate, and the pricing is much more reasonable than UiPath. UiPath licensing is very vague and expensive. There are some ways that they can reduce the cost to make everyone benefit from an RPA.

UiPath needs a lot of maintenance. Every RPA vendor, every RPA on-premise software, needs a lot of maintenance. The cloud version has reduced that, as far as I know. It’s resolved the maintenance issue so that users can focus more on other things. Every new feature will be first on the cloud version and eventually, we can benefit from that.

We use document understanding. For English documents, it helps, however, for Persian documents, due to the fact that the models, the Machine Learning models, that are pre-built, are based on English or other common languages. If we want to actually use Persian, we need to use AI Fabric and build our own models. It's now out of our budget to do something like that here.

It's almost been three years since I first started using UiPath.

I don't like the stability very much as it has minor bugs.

You see that processes break without any reason. When you check the system, check every log, even view robot logs or logs in the network level and you see that it has, it's only then that you realize the issue was a bug from the UiPath platform. Once that happens, you must go to the community and explain the situation to each other. The good thing is, there is a community right there and you can learn from each other. 

Scalability is great. UiPath has many capabilities. Anyone, via a simple search, can go through UiPath and even try the enterprise version and just see for themselves that there are many, many, many capabilities. You can use .NET and there are many NuGet packages that you can use or you can even design your own custom package. There are many great platforms, such as Insights, Action Center, UiPath platforms, and so many different types of robots.

In terms of technical support, I do not have the opportunity to speak with them, as we are in Iran, and, due to sanctions, we do not have a direct opportunity to speak directly to UiPath's support. Therefore, I cannot have an opinion on their services.

I'm familiar with other RPA solutions such as Automation Anywhere and Blue Prism.  

I saw a lot of people that are going to RPA. I put myself in their shoes. However, from my perspective, UiPath has a great community. The UiPath forum is very good compared to Automation Anywhere and Blue Prism. Every technology can be learned, sooner or later. That said, the first thing that any kind of technological software needs to have is a good community to facilitate that learning. Without community, you cannot spread the word, you cannot spread the knowledge. It's the first thing that UiPath has over both of these other solutions. 

And the second thing is, as a technological matter, UiPath is much better. The other two lack the connection, lack the integration. The user interfaces of both Automation Anywhere and Blue Prism are terrible. I do not like them. They're not very intuitive and they are not easy to learn. UiPath is using Workflow Hosting Foundation from Microsoft and great integrations with .NET, which is so much better than the other ways that other vendors are approaching things.

I'm typically involved in the setup. I'm involved in every phase of the process. 

The setup is straightforward. They're using .NET Core now and before that, they were using ASP.NET's Standard Framework. The company has relied on default application configuration as far as, for example, in web.config or .JSONs. Most configuration must be done in the UI itself. I don't really like to just manipulate files at the system level just to do something. I believe that's the way now, however, that can be improved. It could be just in the UI and the certainty would be much better.

The length of time it takes to set up a robot deployment depends on the project itself, however, for a small project, it can be in one month to 45 days.

The initial deployment of UiPath is not more than three days.

Setting up UiPath doesn't have any standard process. There's just documentation. We are always using its documentation.

We do not have any relationship with UiPath directly. We are just a contractor doing RPA for foreign companies that are based in Iran.

Iran has sanctions against it, and there are a few companies that are local branches of foreign companies, and those that have licenses from UiPath all use on-premise deployments. We're always using the latest versions of the solution. Right now, we are on version 19 and it's in the 2010 LTS.

I didn't have the opportunity to use UiPath Cloud. I'm in Iran and I don’t have access. There are some capabilities that are still in the cloud version, like Apps.

While it depends on the project requirements, much of our work is on attended automation. I see attended automation as a gateway to an RPA solution as users are very busy and we cannot just pop-up in some programs, random programs, and stuff so they end up having to wait. I do not believe that attended automation helps users as much as an unattended version can help. This is due to the fact that at some point, someone still has to be involved in the process.

RPA is a new technology and a new shift that there's no good book on how to manage. Maybe there are some, however, they can be obsolete rather quickly, as the technology is changing and with every new version. That's why hands-on experience is the best way to learn. Even for UiPath, without any practice, without any hands-on experience, and without any good community, you cannot do anything.

If someone wants to learn UiPath, first they must sign up within the community and then go to UiPath Academy. Start there. Practice. Get in touch with people in the community, and then create a small use case and do some hands-on work. Practice is very crucial in RPA. Don't forget to review official documentation as well, as it will save you lots of time. 

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

We are a UiPath customer, working with them to develop some products. It is a bit of a mixed thing where we are developing some products with them from scratch, but they are acting as the provider. We develop things, and if they're useful for others, then others can use them.

We are doing some pretty bespoke things to help us develop some solutions, but also help them develop their UI solutions in the legal area. We are working on a few things with UiPath to develop some search robots, some solutions to automatize subcontracts, and some timekeeping entries. These are several things that we are doing right now.

We are doing three things with them:

1. A robot to help us with software for time management, automating time entries. 
2. A robot to help us with filling in our engagement letters (contracts). 
3. A robot to help us with various public searches, i.e., the automation of searches of the public record.

We are adjusting robots from similar things that they do. The robots are not yet in production. 

The most valuable feature is its ability to save time with a task. In general, it improves accuracy as well.

UiPath's ease of use for automating our company's processes is a five out of five. We have found it very easy to talk to them, identifying what can be done along with the potential use cases. They have been very good at guiding us through what is realistic at this point, how their robots could help us save time and improve accuracy, and how our users can engage with their robots, e.g., ensuring that users engage with the robots and use their product. 

When we started to talk about practical implementation, their team was extremely switched onto identifying and fitting their product to our needs. They explained to us how we can use their products, what can be done to adapt their product, and what may happen sometime in the future, not necessarily now. I found this very helpful and straightforward.

What we have in mind in terms of what the robots could do for us is significantly more than what UiPath does now, but it takes more work. From my perspective, there is just a wide scope of implementation that goes beyond what we're starting right now. That is essentially the improvement. While I have nothing negative to say about our experience with them so far, I think we can work to develop more complex products with them. They are already working to develop something for our use cases, but what I would like is if we could develop more things for more complex needs, e.g., where we start with simpler stuff, then we can add things to what we're doing now.

We are in the development phase.

It is too early. We are still in development.

During the development phase, there are five people involved in the development phase. The users will be about 100.

We have not used their support.

We were not previously using something in this area. 

We have been thinking about ways to streamline our activities using technology. It happens that we knew UiPath, so we started to engage with them about what they could do for us. We had something like 20 ideas that we could implement, then we just started the easier ones which were closer to the products that they have. As things go, we will see whether we expand to other things.

We have known UiPath quite well and for a long time. They are also the leaders in the field, so it was a very easy choice.

The initial setup was quite straightforward. We started to discuss potential solutions, then we met with parts of their team, developing that business area. After that, we met with the technical people designing the product. We had a couple of initial conversations and did some testing. It has been extremely simple and straightforward.

We are supposed to review some of their proposals and provide feedback. We are probably a week or two away from production.

UiPath could have probably implemented the solution in a couple of weeks. We had some delays on our side.

We did the initial setup ourselves.

It is important for whatever we implement that it's cost effective in a sense that the robots will replace some human time. If human time costs less than the robot, then that's not a good deal. Normally, human time will cost more than a robot, and that's what we're trying to displace: the human time. We want to replace it with a cheaper robot. 

We only looked at UiPath, because we know them quite well.

So far, the experience has been excellent. I would rate the solution 10 out of 10, but we haven't finished the implementation.

Look internally what your needs are. Try to identify what you could improve with software robots, ensuring these needs are clearly identified and the product is fit for purpose. Also, you should make sure there will be buy-in in the organization, so people will actually use the product.

I have been using UiPath to develop automations for my company. We are a manufacturing company that uses SAP as our primary enterprise application. We are currently meeting with many different business areas and hearing about all of the different processes that they would like us to automate for them. Since UiPath works within SAP, it should help us get some easy wins!

UiPath has allowed us to remove tedious work from our daily process, saving us hundreds of hours. We are currently using it to process separations for people leaving the company. This was a 100% manual process before UiPath and it was required to be completed hundreds of times each month. The team doing the work was extremely overworked and UiPath has allowed them to see a little bit of light at the end of the tunnel. 

Orchestrator is essential, but I love how Studio includes so many activities that are pre-programmed to do what is needed.

Who doesn't love the recording feature? A recording is great to use when doing the first build of new automations!

The most important feature of all is the UiPath community and the forums, as they have helped me with countless questions!

One of the problems with UiPath is that it doesn't interact with some programs, such as AD and Chrome, and it would be great to have even more included!

We have been using UiPath for six months.

So far we have not had any issues with the stability.

We have not scaled, but from what I've read it should scale easily.

We did not use another solution prior to UiPath.

Understanding how everything connects was a little difficult, but UiPath offers classes that walk you through the setup. With the classes it was much easier. 

We implemented using our in-house team.

Do your research, the infrastructure piece is important to understand before purchasing. Also, you need Orchestrator to implement UiPath properly, so don't let anyone tell you different!

Finally, you don't need to start with 100 bots... my advice is to start small and then scale. 

We looked at Automate Anywhere and writing scripts, but UiPath seemed like the best path.

There isn't much that I don't like about the product. I love all of the new features and products they are releasing this year, and I can't wait to see where this goes in the future.