Share your experience using Nintex RPA

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 use it for discovery on desktops to understand what operations are actually doing. Using task mining capabilities allows us to record activities and identify efficiencies and potential process improvements.

Kryon RPA has improved our operational efficiency. 

It has helped us identify areas where frontline staff aren't following standard procedures or using unexpected systems, giving us better insight into our end users' workflows.

The process discovery feature of Kryon RPA enhances our automation strategy.  It reveals activities on the user's desktop, capturing hidden knowledge not mentioned in interviews.

The task mining aspect has been the most valuable for us. That's why we actually bought it. 

Extracting meaningful data requires significant effort. You need a dedicated business analyst who can understand the output.

We used it for two years. We use the latest version. 

I would rate the stability an eight out of ten. It is very stable. 

It's reasonable enough. I didn't notice any major issues.

To analyze and make sense of the data generated by Kryon process discovery can be a lot of effort. It's not as automatic as some might think. It really depends on how many processes you have and how actively you use them. 

But the scalability aspect isn't necessarily about deployment or technical maintenance. It's really about how you analyze and gain insights from the data gathering.

I'd rate the scalability a seven out of ten because the solution has been scaling well for a long time. It's very easy to deploy. But getting value out of it at scale can be a challenge, just like with any deployment.

We use it mainly for process discovery. We actually proceed it from different teams. So, we have 15 licenses that we rotate with different people, actually through different teams. 

So, we do discovery for the online team; we gather the results after about two weeks to a month. We analyze those results, and then we deploy them again on the analytics team.  We regularly deploy it to different teams. So, it's in constant use.

It just runs on the systems through discovery mode most of the time.

The customer service and support are quite good. I'm quite happy with it.  

We are happy with the support we get. 

Positive

We have our own RPA. We have other RPA tools, but for process discovery, we didn't have anything. We saw Kryon before other RPA options.

I would rate my experience with the initial setup an eight out of ten, with one being difficult and ten being easy to setup. It wasn't very difficult.

It was relatively straightforward, though aligning it with our security protocols took some effort.

We deployed it on the cloud. 

The cloud here means the clients reside on our physical machines, and we connect back to the cloud that stores the data. I'm not sure where the cloud is located, but we feed the data back to the Kryon Cloud.

We did it in-house. The number of people required for deployment varies. A normal project team suffices, depending on the aspects of deployment. 

It depends on the scope. We mainly used Kryon process discovery in a very limited manner. So, a team of five could manage it and redeploy when needed.

From the proof of concept to production use, the entire process took maybe four months. That was because we had to go through a lot of compliance reviews and checks.

It is very cheap. I would rate the pricing a three out of ten, with ten being expensive. 

You just have to pay for your own people to analyze the output from the tool.

We evaluated others, but they were significantly more expensive.

So, the price was the major deciding factor. Moreover, Kryon got more capability in certain areas, but the price was just limited.

Overall, I would rate the solution an eight out of ten. 

I would definitely recommend using this solution. Decide what you need from the solution. It's not generic. So understanding the purpose why you're buying this product exactly.