Jiffy.ai Automate Review

The willingness to partner with us and understand our needs was key, as are the time and cost savings from automation


What is our primary use case?

We have a number of use cases. We've intentionally started with a focus in our finance controller organization as well as our supply chain organization. The bulk of our bots that have been deployed are in those two areas, doing a number of different business processes across those areas.

How has it helped my organization?

We've seen really good productivity gains. For the areas where we've chosen to automate, it's not that we have freed up 30 heads in one area with one project. It's more an aggregation of 20 heads across all of the different bots that have been developed. But we've seen tremendous value, especially in the pandemic. As an airline, we have had to cut costs and we were able to go through some pretty strong voluntary separation efforts and redistribute resources and cover things because of the automation work that we've been doing.

It has definitely reduced manual processing efforts in our company. We've automated about 10 percent of the work within particular areas that we're working on. I'm sure, across the company, there's a lot more opportunity. We have chosen to start small and get our bearing before we go too far. It has also reduced errors in our organization although I can't put a specific number on that right now. We haven't had as much focus on that front as we have around how much we've been able to automate.

It has also saved us time with the amount of manual work that has been addressed. The time savings are around 5 to 10 percent in the areas where we've been focused. And the automations have helped to save us money, in the $2 million to $3 million range, in annual savings.

What is most valuable?

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. For every automation that we do, we have our technical architects involved especially since, when we implemented this a few years ago, it was really something of a new technology, knowing that you've got "robots" accessing systems and updating records and altering information. It's a little bit daunting if you're not familiar with it. 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.

You still have to integrate with, or at least access, the systems that you're automating within. For example, if you're doing something within SAP, you're still going to need to access data or screens or APIs or something to interact with that system. But the fact that the solution incorporates intelligent document processing, among other features, means we don't have to integrate with another document processing capability or technology. That's a big reason we chose Jiffy.

What needs improvement?

It has gotten better over time, but some of the training and product documentation could be better. 

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.

For how long have I used the solution?

We've been using Jiffy.ai for two years now. We are on version 3.2. We're in the process of working through the upgrade to the newest version of 4.2. So we're on the prior version to what is current right now.

How are customer service and technical support?

Their support is fantastic. They're a startup, they're a young company, and the product has things that can be improved on and worked on, but they have been nothing but there for us, and ready to help solve, and ready to help fix.

Some of those things, early on, were with security. Our cybersecurity positioning and stance on what we expect and what we allow and don't allow, are pretty advanced. It was a pretty tall order to meet a lot of our cybersecurity constraints, so that's an area where we had to do quite a bit of work. The very first bot we put into production fell into the PCI realm. We actually have two environments, one that has to be PCI-compliant, and a regular environment, and Jiffy has been fantastic from a partnership perspective.

A lot of the challenges that we uncover are really internal to our environment, as opposed to the platform. There's a little bit of both, and that's where it really comes back to the partnership with Jiffy. They are always super-responsive in addressing any challenges with the product or the platform and supporting us as we work through how to integrate or automate a certain homegrown application of ours that is probably an outdated legacy application. We've run into challenges along the way, but we partner with our internal folks and then with Jiffy to work through the challenges.

How was the initial setup?

Our deployment was over a period of about three to six months. That was because we were working through internal challenges in getting it set up.

I can't speak to the actual architecture, but organizationally we have a center of excellence which is my responsibility and under my leadership. We partner with, and act as more of a matrixed team with, our technology organization. They help with the platform and all of the configuration management, the change management, migration, and production through the different environments. 

With every area that we're developing a bot for, the business area that we're working with—whether that's finance or pricing, etc.—we have engagement and involvement and leadership involved from that side. It's really like a three-legged stool with our center of excellence making sure that we're working on the right things with a good RPA fit, making sure that we're developing in the right way, following the standards and all the things that we need to do from a good-hygiene perspective. Then, our technology organization makes sure we're security-compliant, and they oversee the change management and the architecture, and make sure we're not doing any harm to existing systems that we're trying to access. And, of course, the business is driving where the opportunities are and what are the business processes that we're trying to automate.

What about the implementation team?

Jiffy helped us with the implementation. We leveraged their professional services for the implementation support as well as ongoing development and for RPA architecture-type support as well.

Which other solutions did I evaluate?

We looked at Blue Prism and Automation Anywhere. 

When we were looking at the other platforms and tools, Jiffy's willingness to partner and work with us and truly understand our needs stood out.

It is also more user-friendly. The understanding of the business process, and how that translates into what you need to develop and code within the platform, was more intuitive than what we saw in some of the other platforms.

We also liked something that's in the new version, the version we're not using yet, which is the AI, the artificial intelligence capabilities, including document processing and OCR. We knew those features were coming and didn't require getting individual licenses. The strategy of some of the other product platforms was, "Yeah, we can integrate with any other tools," but we liked the idea of having that capability built-in, and part of the actual platform itself.

What other advice do I have?

Lean into Jiffy as a partner for their expertise and knowledge. Be respectful of the partnership and the relationships, and our experience has been that they will really jump in to help and be there for you. You have to be honest and you have to just make sure you've got good communication in place as you're working through things.

We've definitely automated end-to-end business processes, but you have to find the right level of granularity where you can do it all. We haven't explored an end-to-end process for a major value stream within the company. But within large-grain, end-to-end processes, we've definitely identified many sub-processes, and their entire end-to-end workflows, that we have been able to automate.

We haven't used Jiffy's Natural Language Processing yet. It is something that we would like to explore, among many of those capabilities in the next version. We've just got so much on our plate right now, trying to implement in the current version, that we're trying to figure out that time to cut over.

There is definitely some human intervention, but it's really not Human In The Loop. That's another of those things that will be in our next release and that we've got planned for the future. We wanted to crawl-before-we-walk-before-we-run, so we've started with some more basic automations. I'm sure the capability is there. We just haven't taken advantage of it yet.

A lot of the challenges that we uncover are really internal to our environment, as opposed to the platform. There's a little bit of both, and that's where it really comes back to the partnership with Jiffy. They are always super-responsive in addressing any challenges with the product or the platform and supporting us as we work through how to integrate or automate a certain homegrown application of ours that is probably an outdated legacy application. We've run into challenges along the way, but we partner with our internal folks and then with Jiffy to work through the challenges.

In the beginning, I'll admit, I had some concern about Jiffy's stability as a company. They were working through some additional rounds of funding. They were a small startup when we first selected them, but they've gone through some additional rounds of funding. They've done some hiring. They've done some solidifying. I feel really confident about it now. They're in a good spot, and they've made a lot of good progress this year.

Which deployment model are you using for this solution?

On-premises

Which version of this solution are you currently using?

3.2
**Disclosure: IT Central Station contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
More Jiffy.ai Automate reviews from users
...who compared it with Automation Anywhere (AA)
Learn what your peers think about Jiffy.ai Automate. Get advice and tips from experienced pros sharing their opinions. Updated: July 2021.
522,281 professionals have used our research since 2012.
Add a Comment
ITCS user
Guest