IBM Robotic Process Automation (RPA) vs Jiffy.ai Automate comparison

"IBM Robotic Process Automation is very easy to use."

"The most valuable feature is the ability to automate mundane tasks. This improves efficiency, reliability, etc. You can form critical operations which can be highly automated."

"It's user-friendly; even non-technical people can program bots using drag-and-drop functionalities."

"It's not inclusive, in terms of automation, you can just do it standalone, in its own silo. It's not going to force your existing system or teams, your admin teams, to create new IDs for you or even force them to create new services or APIs for you or expose something from there. They can just keep the way they are doing it right now, but you still automate it."

"The solution’s performance is good."

"I think simplicity is key. One of the things that we've noticed is how our developers have been able to quickly adopt the platform; but not only the developers or the techy people, also the business."

"The solution's ease of use is its most valuable aspect."

"We can connect with different database types, and they have included a different package for a terminal connection to, for example, AS400. When it comes to UI development, it's not using the drivers or anything. It's not a selector-based development like UiPath."

"It is a one stop solution for automating process. The modular way that is assigned and works together follows a certain logic, and it encompasses a wide range of processes in a very structured and logical manner."

"The biggest driver was the cost savings. We wanted to improve productivity and save costs. Therefore, we gave most of the mundane tasks currently being done by a human to a bot. Some of the mundane tasks were reading invoices and keying in the data. We are talking about 15,000 documents every day. That is a huge volume that needs a lot of people. With the bot, it is just a fraction of the cost, because there is a huge savings in terms of manpower."

"I found the invoice data extraction very exciting. It is really good."

"The most valuable feature is the computer vision or OCR. That has a lot of use cases in real life. A lot of man hours can be saved, as we've seen in the finance processes... The feedback I have gotten from the team is that the OCR is quite powerful."

"Its initial setup process was quite efficient."

"With the customization option, we can write custom expressions using its compatibility with Python or other programming languages."

"It removes the burden of having to do some tasks manually. However, we are just using it in production for a single project. It saves us a lot of time in terms of extracting that information. So far, it has made a big impact."

"The way Jiffy.ai integrates into existing infrastructure has been great for us. Our company is pretty stringent when it comes to cyber security and integrating with our apps... We've definitely had very strong scrutiny over this platform and this work, and even within that, it's been really successful at being able to integrate."

"There are certain limitations in the solution for screen reading."

"We can use its inbuilt activities, and it's a complete package, but just like ElectroNeek, a limitation is that we have to depend on its inbuilt activities. We can't include our own activities or we can't introduce other activities."

"This RPA should be under the umbrella of BPM. This is what the future should be."

"I would like to improve the efficiency of this solution and the Surface Level Agreement."

"IBM should provide specific solutions for specific problems, like templates for invoicing processes, or general templates for creating efficient processes."

"One of the things I would definitely like to see is more of the machine-learning and cognitive capabilities. For example, now that we're starting to automate more and more tasks, there are some things that still require us to go back and modify the robots when we need to. But if we had more of the machine-learning integrated into it, I believe it would be easier to maintain, so that we wouldn't have to go back and adjust every time."

"Stability could be better."

"I would like it to do pretty much everything out-of-the-box without any need for any customization. However, that is not the case right now. We absolutely have to do some amount of customization with the solution in order to use it out-of-the-box as-is."

"The UI or the UX has room for improvement. The approach for designing the workflow is not that straightforward. It's quite difficult."

"When using UiPath automation, we could just Google issues if we were stuck with something. In the initial days with Jiffy.ai, we could not get that type of information from Google because there wasn't much of a community."

"The setup process could definitely be better."

"Initially, in version 3, Jiffy.ai did not have support for containerization. In our environment, we are heavy users of containers and container illustrators. So, the initial deployment option was running based on individual hosts that we deployed in the cloud. That created a singularity in the way that we deployed services in our system."

"I believe this is also being addressed, but a lot of the platform work, as we were putting in new versions or making some updates, was, ironically, very manual. It's improved greatly, but I would imagine that's an area that they're probably still working on, on the backend, to help when it comes to what we need to do for platform support."

"The solution's support services need improvement."

"The solution has just not closed the gap of being accessible to non-IT users. If you are a non-IT person, then this all looks like gobbledygook. Maybe that is something that can be improved upon."

"They are still new in the market. Or, at least, they are still a small player. They require a lot of improvement in terms of learning material as well as the community developers. If you compare Jiffy.ai to an established solution, like UiPath, you can go to YouTube and find a lot of learning material posted by UiPath, partners, and other people in the community. However, for Jiffy.ai, you won't find that available in the market. Because of this it is very hard for us to find talent in the market. Most of the developers in the market are used to the bigger players. For Jiffy.ai, if you search a resume because you are trying to find someone who has used Jiffy.ai, you won't be able to find it. So, when we onboard a new person, we want them to learn this new system, but it is a bit hard for them to pick up because there are no external learning materials on the Internet."

"The product has a yearly licensing fee."

"The license is paid annually."

"IBM RPA is cheaper than other tools."

"The pricing is reasonable for this solution."

"The product is reasonably priced compared to other tools."

"I rate the pricing ten out of ten. So, the pricing is very good for me."

"IBM licensing is annual and based on Virtual Processor Cores (VPC). This provides flexibility as part of the containerization environment."

"The pricing is reasonable."

"If cost is of concern, then start with Jiffy. If cost is not your main concern there are a few premium products out there, but they come with a huge price tag."

"The pricing and license make sense. They have a model based on the concurrency of the workforce, which is very suitable in our case. The savings are great on the licensing cost."

"The solution's price is reasonable."

"I like that it is very cost-efficient."

"The licensing is not expensive; it is quite cheap. The expensive part is to support and maintain it. Understandably, we engage them to do a lot of work that could have been done by our own staff, if we had an RPA team. I wouldn't hold that against them. It is just that the cost of support is on the higher side for us."

"The pricing is quite competitive. As a small player in the market, they are quite aggressive in their pricing. With the features that they offer, it is quite worth the value."

"Its license is yearly. There are no additional costs to the standard fee. It is a standard license."