Overall Satisfaction with Appian
We used Appian to build a prototype. The prototype focuses on a subset of the hospitality sector (namely, setting up a cafe). It pulls information through from the New Zealand Business Number register about the business to create a profile for the business entity, and uses this information as part of the service request for that business customer to apply for their alcohol and food licenses for their cafe. Currently the process for applying for food and alcohol licenses is lengthy (usually a paper form of around 11 pages often completed by hand, plus a bunch of documents to attach to the application). We re-use information that has been supplied in previous applications to pre-populate the new service request, saving the business customer tons of time.
We wanted to support business customers when they need to get permits or licences to run their business by enabling them to use and re-use information and data that government holds, making requests for permits and licences easier and more efficient, by joining up services and sharing information that spans multiple government organisations, including local bodies.
We wanted to support business customers when they need to get permits or licences to run their business by enabling them to use and re-use information and data that government holds, making requests for permits and licences easier and more efficient, by joining up services and sharing information that spans multiple government organisations, including local bodies.
- The team we had to build the prototype (including the consultants from Appian) was fantastic. We implemented the prototype in three short Agile sprints (6 weeks in total), and the resulting prototype was high quality with lots of functionality of excellent quality.
- Because Appian is a product suite, all the components worked seamlessly together - we had no issues with integration and could focus on the experience for the business customer, the concepts to prove and the problems we were there to solve.
- We had such a short timeframe for implementing the prototype that we did not get an opportunity to explore the drag and drop business process modelling functionality - this is available in the Appian product, and would enable low code development, but I can't really comment on how good it is.
- Our objective to reduce customer effort when dealing with government by 25% was exceeded. In the process of applying for an alcohol licence renewal alone, we saw approximately 80% reduction in time and effort for the business customer - and that was just a prototype! Imagine the possibilities when this is taken into a live environment!
We went through a light-touch Request for Proposal process, explaining the problem we were trying to fix and giving lots of examples of the current process and pain points. Appian was one of 10 respondents but stood out as having all of the components that would make putting the customer first, sharing information across multiple government agencies, workflow, low code and speed to build a working prototype that would work on multiple devices (pc, mobile, table) out of the box.
Appian understood the problem we were trying to fix, and their response answered the majority of our concerns about how to solve the problems for the business customer by using and re-using information.
Other providers could do some parts of the functionality needed, or offered to build the prototype from scratch, or couldn't meet our timeframes (due to length of delivery or lack of resources). Some of the respondents missed the point entirely and simply did not meet the requirements we set.
Another factor was the cost estimate presented by the respondents - Appian was not the cheapest, but they were definitely not wildly expensive (unlike a couple of other respondents)!
Appian understood the problem we were trying to fix, and their response answered the majority of our concerns about how to solve the problems for the business customer by using and re-using information.
Other providers could do some parts of the functionality needed, or offered to build the prototype from scratch, or couldn't meet our timeframes (due to length of delivery or lack of resources). Some of the respondents missed the point entirely and simply did not meet the requirements we set.
Another factor was the cost estimate presented by the respondents - Appian was not the cheapest, but they were definitely not wildly expensive (unlike a couple of other respondents)!