Nintex RPA Reviews

Our primary use case for Nintex RPA involves getting documents from emails, reading those documents, and transferring them from the IRD to finance. We are also exploring the LP and Intech features for more advanced use cases.

Nintex RPA helps our government and public sector customers with automation. It is especially useful for operational tasks like handling statistics and services.

While we have only explored the simple use cases so far, Nintex RPA has good integration capabilities, such as working well with Gmail and Outlook to automate document handling and notifications.

We need better training and community support in Indonesia. It would be helpful to have more representatives who can provide training and share knowledge, as our team lacks the deep skills required for RPA.

We have been working with Nintex RPA for one to two years. During this period, we have been collaborating with our internal team for various use cases.

On a scale from one to ten, I would rate the stability of Nintex RPA as an eight out of ten. It is quite stable.

I would rate the scalability of Nintex RPA as a nine out of ten. It is quite scalable.

The support from Nintex is very good. I would rate it as nine out of ten.

Positive

The initial setup was managed by our distributor as we do not have the expertise to handle it ourselves.

Our implementation was done in collaboration with a local distributor in Indonesia who handled the installation due to our lack of specialized skills.

Although Nintex RPA is expensive, it is somewhat affordable considering its features. I would rate the cost aspect as an eight out of ten.

We are also partnering with other vendors such as Microsoft, Oracle, and IBM.

I'd rate the solution eight out of ten.

We're predominantly focused on the contact centre because that's our primary core business, and a lot of RPA use cases are in the back offices. The challenge for contact centres over the years for all RPAs has been that it's hard to establish the business case. The complexity of that environment includes determining and prioritizing which process you want to automate first.

We have done quite a number of back office stuff, but our vision is to link the back office to the front office in terms of customer experience. We are a speech analytics company, and we specialize in that area. We have challenges with corporates because every vendor comes in with a return on investment equation, but there's only so much that our customers will do. We saw that combining our capability with what RPA can do would really help with the business case for automation.

The full-service automation aspects and the process discovery are the most valuable features of Kryon RPA. The process discovery is where you spend most of your time in RPA. We're not a big professional services company and don't want to build a massive team. So, the more we can automate on the front end, the better it will be for us.

Kryon RPA's automation, process discovery, exit deployment, bots management, and change control management are really good.

The process discovery tool of Kryon RPA could be improved because of its limitations. I'm looking forward to the new release, which will fix these limitations.

I have been working with Kryon RPA for about three years.

Kryon RPA has decent stability. Once you've built your bot, they run really well. With RPA, you're always a victim of what the client does. The biggest challenge in RPA is managing the customer. A customer might do a version upgrade on something that's out of our control. However, from what we can control, Kryon RPA is a stable solution.

I rate Kryon RPA an eight out of ten for stability.

Most of my deployments have been pretty small. On average, they're about 50 users at the end of the solution. We don't have thousands of users sitting at the end of these things. The console that manages all the bugs you deploy is really good. The chances of our company getting involved in a big telco are very, very small. We're using Kryon RPA mainly for organizations with 200 users and below based on per division. Kryon RPA is well suited and well priced for organizations with 200 users and below based on per division.

Currently, the two customers that use Kryon RPA are in maintenance mode with us regarding change control and management. Our clients are medium sized businesses.

Based on my experience with other RPA products, I rate Kryon RPA an eight out of ten for scalability.

Kryon RPA’s technical support is very good.

Positive

I rate Kryon RPA a six or seven out of ten for its initial setup.

The pilot phase we did the first time went really well. The deployment with Kryon RPA is ongoing, and there are always improvements. We are pleased that we were able to deal with the security aspects of managing and dealing with customer data. We're dealing with tier-one organizations in terms of managing their data and getting through security.

Compared to its competitors, Kryon RPA's pricing is very competitive. We've priced Kryon RPA based on the use cases that we're getting and the return on investment. Its list price is one dollar, but we got it for 30 cents because the pricing was negotiated.

Along with licensing, we paid Amazon to set up the Amazon infrastructure to support the software. We also got the whole environment certified as an ISO-certified environment. Additionally, there are resourcing costs because we set up a fully managed service proposition around it.

We had to pay about 30% additional cost in addition to the standard licensing fees while using the solution.

I rate Kryon RPA a four out of ten for pricing.

The reason we selected Kryon RPA was because of the automation capability of the process discovery. It's a little bit immature, but the new release will fix a few bugs in the product. The product has the potential to speed up the discovery process. The new version will overcome some of the solution's limitations and make it a better product. The automation capability or the RPA aspects of the solution are pretty much the same as what I've found in most RPA tools. It all depends on the environment you're integrating into.

Kryon's gone through some changes because they got acquired by Nintex. In that period of acquisition by Nintex, it's been a bit uncoordinated in terms of support and other things. But Nintex is getting its act together and integrating the product into its portfolio. That's a natural thing that happens following an acquisition.

Overall, I rate Kryon RPA a seven out of ten.

I use Kryon RPA to make bots for the telecommunication and banking industries. 

I like Kryon RPA's ability to use automated and manual processes with any bot.

Kryon RPA's integration with other solutions could  be more seamless. 

I've been using Kryon RPA since 2019. I started at my previous company about four years ago, then I took another position at Banco Pichincha Ecuador. I'm a development architect working as an independent consultant at the bank. 

Kryon RPA is scalable. It's easy to create bots and schedule when they should run.

Kryon RPA's interface isn't as developer-friendly as UiPath's. I'd also like to see more seamless integration with other solutions. For example, with UiPath, we can use a lot of APIs. I also like Orchestrator from UiPath. We can control all of the robots that we're developing in the machines in the bot runners. UiPath Apps is a new tool that I like.

Microsoft also has some amazing tools, like Power Automate Desktop, Power Apps, and Power Automate Online. These tools can integrate with bots on Power Automate Desktop.

I Kryon RAP 10 out of 10. I recommend starting with easy processes. You should discuss the processes with the client, and go over things like cost, tools, time, and other things that are critical for the business.

We're looking to discover routine processes that our users do and ultimately automate those processes and deploy them to robots.

We've really been looking at just about any of processes. We've initially used it for processes that update invoices or update data on our system. We've used it for processes to send emails such as notification emails. We've used it to run scripts and to run data updates, and as a scheduling tool as well.

We've already automated about 40 hours' worth of weekly savings. It has definitely helped us to implement some of the workflows that I've shared with you and to take that work away from our partners so they can focus more on other, more valuable work.

The thing that we find the most value in is the Process Discovery component and the ability to really see what users are doing on a day-to-day basis. We're starting to make sense of the processes that they're doing and getting visibility into what they're doing. Overall, the Process Discovery is very good. The product is very new to the market so there have been some issues here and there but Kryon support has been great in working through that. It has really helped us drive understanding of what's happening. It certainly helps us understand the work the users are doing, the like things they're doing, and it helps us filter some of that work.

The product requires some more time in development. It still has some bugs and some things to work out. They're constantly releasing. They need to continue working out the general issues of using the product at scale, first and foremost.

I've talked with some of their product teams about features that I would like to see. With the Process Discovery, they're collecting a lot of data and they're spending a lot of time in the algorithms of the data. But one of the things we've talked about very recently is being able to aggregate or summarize what a user is doing in a day. That summary wouldn't necessarily be in the context of a process, but in terms of the applications they're using, the timeline of what they're doing, the number of clicks per hour. That sort of information could be very valuable.

We've been using Kryon for about for about four months or so. We are using version 19.4 of Process Discovery and 19.1 of the RPA solution.

The stability has been pretty decent. There are certainly opportunities in terms of stability, but with each subsequent release it gets more and more stable.

The product is becoming more and more scalable. On the Process Discovery side, you can collect a lot of data very quickly, so there is opportunity there. But overall, it's working pretty nicely.

We want to deploy Process Discovery across the majority of our company, which consists of about 1,200 or so people, to identify what they are doing. Over the next year, we are likely going to be deploying it on at least a couple of hundred users' machines.

Tech support is great. They've been really good and very responsive. We submit our tickets via our portal. We feel that we get really good support from them.

Our interactions with their customer service are great. Really great. We've had a variety of people off and on, not a specific person. We've probably worked with half-a-dozen people, and all of them have been able to help us pretty successfully. We do have an account rep who manages our account from a higher level, and she has been consistent with us and has been really great.

We did not have a previous solution. We came across Kryon from an RPA consultant who wrote a book on RPA. He used it a while back and recommended it to us.

The initial setup was pretty complex. The install is certainly not for the faint of heart. There are a lot of options and a lot of ways you can install. Given that we were installing in the cloud too, it took some time and it took some troubleshooting and work, but we got there.

It took somewhere in the neighborhood of a month for us to get the AWS environment up and running and then figure out all the nuances and dependencies of the install.

Our implementation strategy was to work side by side with Kryon and our network teams and get it installed. They gave us some initial pre-reqs and things to install and things to look at. We were one of the first to get everything operating in the AWS environment, so there were some specific things to us that we had to figure out on our own.

For the deployment, we had the equivalent of one dedicated person for a month. And we have the equivalent of two people maintaining it. They are RPA developers who work on setting up RPA jobs and configuring Process Discovery, etc. We have five users in total.

We've done it all internally thus far.

We have absolutely seen return on investment. We felt that we had to get to between 40 and 80 hours of weekly savings to get our ROI and we're already almost there, and that's good news overall. So far it's saving us about $80,000 annually. We expect that number to grow.

In terms of business analyst hours, it hasn't saved time there yet, but it will over the long haul for sure. It has definitely increased operational efficiency and has reduced human error by a pretty great degree, for the things we've automated. It does what it needs to do pretty routinely and pretty flawlessly.

The cost is fairly similar to its competitors' costs. It might have been a little bit more reasonable than the others, and that cost was with Process Discovery in addition.

There were no other licensing costs, but there are our hosting costs and our own AWS cost.

We evaluated Automation Anywhere, Blue Prism, and UiPath a little bit.

The biggest difference was that Kryon had Process Discovery and the ability to discover your processes across your base, and the others did not. That was a big differentiating factor for us. Automation Anywhere was starting to come out with its cloud deployment so users won't have to deploy everything internally. That was something that sticks. But in terms of the rest of the capabilities, they were relatively at parity.

Spend time focused on standing up your center of excellence around the solution. Kryon gave us some great advice on that in the sales process regarding defining what we're trying to do with it. Get key sponsors and then get a key team that works through the implementation, together.

What we're learning from using the solution and what we're really still trying to figure out is what is a good candidate for an RPA process, versus the other ways we could automate, whether it's process elimination or deploying some of our core engineering teams to write different tools. We're still trying to figure out what the framework is for picking the best processes.

The processes that lend themselves to RPA are processes that are highly repetitive, high volume, low-judgment types of processes, where you can write down the process in a Word document, write down the logic, and then turn that into an RPA solution.

We haven't been able to make that leap yet, in terms of Kryon's full cycle of automation from the discovery of our processes to turning on the automation and scaling it up, but we see the potential there. We haven't quite gotten to that point yet, given how early on we are in our journey.

When it comes to using the solution, for both business users and developers, you do have to have some technical background to use it. It's unlikely that you would deploy it to somebody who doesn't have any background in it. But people who are somewhat technical have been able to use it pretty successfully.

I would rate Kryon at eight out of ten. It has a lot of potential and we see that potential. It needs a few more iterations for me to bump that score up higher. It has been a good experience so far and we're looking forward to the future.

We're automating a lot of shared services tasks within our homegrown system: payroll, billing, and things like that.

As a company that places temporary employees, we have talent globally. In the UK there are GDPR requirements. Before Kryon, when one of our field employees reached out to us saying that we needed to remove their records, that was all done manually. Now, that’s something done by the robot, giving people time back and reducing possible entry mistakes. It’s the same thing with fee entries within our system. That is something that might take somebody ten hours, whereas a robot will be able to take that off somebody’s hands and ideally reduce the time to complete.

In terms of embracing the digital transformation, there is the question of whether people are going to be accepting of tasks being taken away from them and what they're going to do with that time. But a lot of people have really embraced it, especially people who were taking ten hours to put fees into our system and who will be able to use that time for more productive and less mindless tasks.

The advanced Excel functionalities are really convenient because we work a lot with spreadsheets. It’s also easy to use the HTML selectors on most major sites. It’s just a click and it picks it up. There’s not a lot of no hard-coding with it.

While I have some technical background, everything is self-taught. I'm not necessarily a developer myself, but picking up the tool, with the training they provided, has been pretty easy. I’m currently the only person using the tool in our company.

We use Google Drive a lot. If somebody sends us a spreadsheet or a document, it's going to be in Google’s format. It's not going to be in Microsoft Office format. But currently, there's no integration with Google’s documents. That would be a huge plus to have.

The same goes for, using Chrome natively. There's an extension but it doesn't necessarily always work. We have to close Chrome and reopen it to get it to pick things up sometimes, depending on the page and the IFrames and things like that.

I’m not sure yet what I think about the stability of Kryon because we haven't been able to get things constantly running and working. We initially had the server issue. And then, there have been issues with Chrome crashing and the extension.

Right now our usage of Kryon is limited to our shared services team. We're taking care of those processes first. But we have plans to automate as many processes as we can get on our plate and get through.

We have room to grow. We just have to figure out where we need to go from where we're at now. Right now it's a waiting game to get things fixed and running.

Customer service gets a rating of 100 percent. They’re fantastic. They're always really quick to respond. If we have a problem or if we put in a ticket that is more high-priority, our rep will jump on it and get things escalated. They’re happy to work through issues and take as much time as needed to resolve everything.

The Kryon team has definitely helped prioritize processes that are ripe for automation. It's an ongoing process, but they give us a good understanding of what to expect and how to figure those processes out; what can and can't be automated. It was mostly through the training. Going through that with them gave us a better understanding of what sorts of processes make sense.

We didn’t have a previous solution. We went with Kryon because of

• the ease of use
• the user interface seemed a lot better, more usable
• some advanced features that others didn't have
• the price - can't beat the price.

We had somebody within our department doing the initial setup, although I was on the calls. It was a little bit complex, because there were some issues we ran into with Server 2016. When we tried to run an unattended bot on there it wasn't working so we had to switch operating systems. We've had to go back and forth to get things truly set up and ready to go. We're still working on the deployment, but that's not necessarily because of Kryon issues. It took some time to figure out the issue with the server, going back and forth with screen-sharing, etc.

And it seems that the size of the virtual machine that they provided with us might not be enough. We're trying to figure that out. Chrome keeps crashing on us. Once that is resolved, we have three or four processes that are pretty much ready to go. I just have to get through the actual testing of the running the unattended bots on the virtual machines.

In terms of an implementation strategy, we are working with our shared services teams to identify the processes. We have a daily “stand-up” and a weekly planning session to figure out and prioritize our processes. Then it's just a matter of building and testing and getting them out.

I expect that Kryon will save us money. It's too early to tell, but I would say that once it starts running there are going to be cost savings.

There are different pricing levels for every bot or unattended bot. You can buy however many you want. You'll need an additional virtual machine for it to work on. You can get multiple attended bots if you have users who have Windows machines. You can run those locally on their machines.

Automation Anywhere was one of the solutions we looked at. There were others but it’s been a while since we went through all of them.

Make sure that you have your processes in a good place and that you have them written out. Make sure that you have your stakeholders onboard. And make sure that your bot works on the right server.

We don't use the process-discovery functionality of the tool. We're identifying our own processes by polling various stakeholders to see which processes make sense to automate. But it seems like it's pretty easy. We've hit a couple of snags with our virtual machines and the OS they are running and with the Chrome Extension. We're doing everything with unattended bots since we're primarily a Mac-based company. We're not able to run them on people's local machines other than the machine I use to create the Wizards.

In terms of operational efficiency, it might be a little too early to tell because we're stuck right now. But in the big picture, not only are we identifying processes, but we're also figuring out how to improve the processes, whether somebody is currently still manually doing them or a bot is doing the improved process.

Our company buys products from vendors and sells services to end-users. Most of the RPA processes done in Kryon are related to order raising, as well as retrieving reports. We have automated processes involve SAP, Pegasus, ITSM tool, Words, and Excel.

It takes a lot of work and time to complete the business processes manually. When the users utilize the Kryon solution, it cuts off more than 50 percent of the processing time as the logic has been pre-built. There are less orders being delayed. Adopting Kryon solution has significantly improved the turnaround time.

The image recognition in recording actions is very helpful. It runs stably as long as the graphics on the applications are not changed.

The environment of storing the variables could be defined as local, which will only be accessible within the wizard itself and cannot be read by the embedding wizard.

It will be good if Kryon has a function to find/replace the keywords and collapse/expand the groups.

We did encounter some issues regarding to trigger often but our support team is able to resolved it later. Other than that, it is quite stable.

It is very scalable. All we need to do is to set up the robot accounts and assign the access to it. Once it is done, we have to configure the trigger for the robot. Scaling up and down can be done in just a few steps.

The customer support is outstanding. They are very responsive and will accommodate with our schedules.

No, we started with Kryon.

Setup for Studio and Robot is pretty straightforward. We have to install the Studio and Robot on the machines, create accounts for the users and assign access rights. Then login Studio to develop wizards and Robot to run the wizards.

The initial setup of server was done together with vendor. Subsequently, vendor team came down to help us with the upgrade. They are very helpful and knowledgeable.

I am not too sure how much cost was saved. But there are a few people in the department were redeployed when one of our processes is up and running fine.

I am not involved in any of those.

We are using UiPath in conjunction with Kryon. I feel that Kryon has a better image recognition than UiPath.

I have tried a few solutions and Kryon is the most user-friendly.

The solution is easy to use. Although I felt the solution is a little restricted sometimes as I could not call any external libraries, I am able to use the advance commands, which are the built-in functions in Kryon, to program the RPA solution by changing my initial idea. It makes me think out of the box and test how good my logical thinking is.

We use Nintex RPA in a complex environment and for working with legacy systems as well as with open systems and outside the company environment. We use the tool in order to do daily tasks that replace employees. 

It has improved operational efficiency, reduced manual workloads, and increased accuracy in repetitive tasks. The platform’s user-friendly design and automation capabilities contribute to streamlining processes and achieving overall productivity gains.

The solution can be good, but suffers from some unexpected flows. Sometimes it sticks or stops - which requires some manual intervention. In newer versions it will likely work better. 

Initially, it improved operational efficiency, reduced manual workloads, and increased accuracy in repetitive tasks. The platform’s user-friendly design and automation capabilities contribute to streamlining processes and achieving overall productivity gains. 

Nintex RPA’s drag-and-drop design interface, automation capabilities, and integration with some systems are helpful. Its ease of use and ability to automate repetitive tasks efficiently contribute to its popularity. Helpful aspects include:

1. Visual Design Interface: The drag-and-drop interface allows users to design automation workflows graphically, making it accessible for those without extensive coding backgrounds.

2. Cross-Platform Integration: Nintex RPA supports integration with a wide range of applications and systems, enabling automation across diverse platforms and enhancing its versatility.

3. Reusable Components: The ability to create and reuse automation components (such as workflows and actions) helps streamline the development process and maintain consistency.

4. Scalability: Nintex RPA is known for its scalability, allowing organizations to scale their automation initiatives as per their needs, from simple tasks to complex business processes.

5. Error Handling and Logging: Robust error handling mechanisms and detailed logging features assist in identifying and resolving issues, enhancing the reliability of automated processes.

6. Community Support: The availability of a supportive user community and resources can be valuable for users seeking assistance, sharing best practices, and staying updated on the latest developments.

7. Security Features: Nintex RPA often includes security features, including encryption and user access controls, which ensure the protection of sensitive data and compliance with security standards.

Improvement areas and additional features for Nintex RPA should include:

1. Enhanced AI Integration: Integration of more advanced AI capabilities for improved data recognition, natural language processing, and decision-making within automation workflows.

2. Expanded Library of Connectors: Continuously adding connectors to popular applications and systems ensures broader compatibility and facilitates smoother integration with a variety of platforms.

3. Collaboration Tools: Introducing features for collaborative development and version control can enhance automation developers' teamwork and streamline automation project management.

4. Mobile Accessibility: Improving mobile accessibility for monitoring and managing automation workflows on-the-go can be beneficial for users who require flexibility in their work environment.

5. Low-Code Enhancements: Further simplifying the low-code development process can attract a broader user base by making automation accessible to those with minimal technical skills.

6. Machine Learning Integration: Integrating machine learning capabilities directly into the platform could enable more intelligent and adaptive automation, allowing processes to evolve based on patterns and insights.

7. Community-Driven Content: Encouraging and facilitating a community-driven platform where users can share custom components, templates, and best practices could enhance the overall user experience.

I've used the solution for five years (I also used older versions).

Stability depends on versions and the amount of robots. In newer versions it is more stable as long as you use about two to three robots. 

The solution is not scalable.

I don’t have enough experience to speak to support services. 

Neutral

I didn’t use other solutions previously, however, I have since used UiPath and found it more stable (but it costs much more).

The initial setup is usually easy. 

We worked with a vendor - a very experienced one. 

The ROI is good, however, it depends on implementation.

It is one of the cheapest in the market for small businesses.

I have evaluated:

• IBM RPA
• UiPath
• Microsoft’s Power Platform

If you need up to two to three bots it is a great solution.

Our primary use case is two back-office processes from a specific area, an area which was very complicated. In the credit card world, there is a process called a chargeback, when the customer says he didn't do a specific transaction, or it's not the right amount. This process has a very long, complicated and regulated process behind the scenes, after the conversation with the customer. We used a robot to automate a lot of the process, to make it shorter, easier, and to save a lot of agents working on the process.

Every week or two weeks we are bringing on a new process with the robot. We are still in the middle of the automation move; we have a very big roadmap for what comes next. We are still on this trail.

The process I noted above is a main business area with a lot of very specific processes inside - we have now more than 15 specific processes in this business area. All of them, as of now, have saved us almost six FTEs. That's a lot of money. The savings are great and they will increase every month.

In the last month, we achieved 11,000 activities done by robot. Before Kryon, we did 500 each month. When we started with automation ten months ago we did a few hundred. Each month we have added more and more processes and more and more activities. It's quite dramatic, because we took a very complex business area, and every activity in it which can be done automatically is being replaced by the robot instead of people working on them.

In terms of Kryon helping us embrace digital transformation, we are very advanced in this area. More than 70 percent of our interactions with customers are digital. But Kryon helped us with some of the processes which are more complicated, where we had people doing things in the back-office after the digital process. Now we can do more of them automatically. It's another step in the same direction for us.

What we are lacking is OCR, the ability to read text. We would like it to have the ability to take a page which is free text and analyze it, and then for the robot to know what to do next. This ability does not exist in Kryon products, so our company is now trying another tool which has this specific feature - an IBM tool which combines RPA and OCR together.

Also, when the robot stops working for any reason - it doesn't matter if it's something in our systems or our infrastructure - it does not know to go back to the same point it was at when it stopped. We have to start from the beginning or to delete the report. It cannot continue from the same point. We would like the robot to know how to continue.

It's quite stable. Most of the difficulties are coming from the changes on our side.

The scalability has been good enough for our needs.

Prior to Kryon, we didn't work with another solution. But we are now starting to work with another solution because of OCR.

On the technical side, the setup was done mostly by HMS. The issues we dealt with were mostly to do with the connection to our organization's system. The authorization issue was difficult for the system and many other aspects, but I know part of it was from our side. We also had some information-security issues. I don't think it was too complicated, but it took us about a month-and-a-half, to do the first at set up, and then it was much easier.

We learned a lot. We learned what we need to prepare for each process so the process will be the most effective and quick. We learned about the abilities of the tool and that helped us in thinking about the next processes and how to do things more efficiently.

We are also using BI to help us with more complex business logic. Instead of doing it in the robot, we are doing it in BI and giving the robot more direct reports to work on. It makes our process much smarter and efficient.

In terms of deployment and maintenance, we have one full-time employee working on it, and one of our business persons, a project manager, is working on it half-time. He's involved in building the business process, deciding what will be the next step, and helping close all the details on our side.

The maintenance is not high. It's just that each time the system is changing, we need to teach the robot the process from the beginning. This is the only maintenance we have. The other work is really to in developing the next process each time.

We have a supplier doing the implementations for us, HMS. They are more involved in the technical details and issues. But next month, we are planning to do Kryon's course. We are bringing it here, and then eight people, both business and tech people from our organization, will learn the tool and then we will be able to use it by ourselves.

Our experience with HMS has been very good. We like working with them. We are continuing with them but from a budget point of view we would also want to learn to be more independent. But we'll definitely continue working with them.

Now that the process is cheaper for us, we have been able to change our business rules a little bit and save more money by automating. To give a simple example, if it was worthwhile for us to do a specific activity only if it was more than 50 shekels, now, when the robot is doing it and it's cheaper for us, we're doing it from the first shekel. We are saving more money by changing the business rules because the process is costing us less money.

It has also helped to reduce employee errors. This is also very important. And it has helped us in terms of monitoring because we need to do less monitoring of the employees. That's another area of savings, another improvement. In the beginning, we did need to monitor the automated process, but after seeing it and becoming comfortable with it, we were able to reduce our monitoring of employees.

The first robot was very expensive.

For us, there are the additional implementation costs that we paying to HMS.

We have a lot of people coming to us to learn from our process, so we've been providing advice already. First of all, it's important to do a very smart business analysis, from the business side, and not automate exactly the way it was done before. Really think about ways you can improve and make the business logic, the business rules behind the scenes, more effective. This is very important.

It's also important to look at becoming independent with the solution from the beginning. We have only started to plan for that now.

The authorization issues within our company also took a lot of time, so I would suggest getting those dealt with in advance.

Part of the difficulty in embracing the tool is on our side, due to bureaucratic issues that we have in our organization. Every change we make which results in a new version of the system the robot is working on means we need to teach the robot from the beginning to do the process.

For example, when we would have a new version of the system, we would ask our people, "Has anything changed?" They would say, "No. Nothing is new." Only after would we find out that something moved from the right to the left. Just one button. For the employees, it didn't matter. For the robot, of course, it does. And then we needed to teach the robot to do it again. So we have learned to prepare ourselves better before a new version is released. We receive all the screens. We teach the robot to do everything again. We're checking ourselves. We test more. These are things we learned along the way, "on-the-job learning." We wasted a lot of time on this because we did not prepare for it properly.

In terms of the prioritization process, we are working with a business analyst to decide exactly what the next process should be, what has the biggest number of activities per month and that the business case is important. We also look, from an implementation point of view, at whether we can do it. Is it accessible for us and not something very complicated which will not be possible? We take all of this into account and we decide which process to put in next. We already did the main business area and now we're continuing to another business area and doing the same process. One of the things on our roadmap is to optimize part of our monitoring processes.

From a business-analyst point of view, we are using a lot of analytics to make it very smart and efficient. So it's not saving us money in business analytics, it's the opposite. But it's worthwhile for us. The discovery process in our methodology is very important because each case is a little bit different, so we need to find the right rules, the logic.

The first process was the most difficult. We needed to learn how to work with it. But by using it more and more, we have achieved a very easy and quick process. The delivery time, now, is very good for us. We are adding a new process every two weeks. Now it's good, but the first time was more difficult.