It's not complex. I'm kind of amazed when I see AppPulse do what it does. For instance, the original setup. Like I said, it went really fast, but our web team will change something on our site that will break our script. Our script is predicated on this button being here, that button being there, etc. We're trying to get our change management practices in order so that it doesn't happen, but our team can fix those issues in under an hour.

Deployment's easy. The way it works is that we create a script using one of the tools that they provide, zip it up into a file, and then we go to the AppPulse application, and we create a new application, and upload the file, and it's there. We tell it where we want it to run from. It's very easy. It's very easy to download the script so we can make changes to it. It's a URL we log onto and just create our user ID. We can have a site monitored within minutes.

It takes only minutes to add your first app. Once you select your platform, Apple or Android, download the SDK and start seeing data right away.

Extremely straightforward – step 1, 2, and 3.

It was a very simple and quick setup.

You don't really need too many skills to use AppPulse, or to implement it. It's easy to set up in a customer environment. We spent two two and a half months in a POC and then we implemented it across four individual channels. For electronic banking and the mobile channels, it only took us two months to implement, with three people to make sure that the service is continually working.

Generally it was straightforward.

We did an in-house implementation.

It was straightforward.