Appian Reviews

Appian is really helpful in automating different processes. Our clients use it for process automation and leveraging updated features like Appian Portal and Appian RPA. The main use case revolves around external application building in nature, making it comparable to other mobile app general interfaces, particularly those heavy in user interface and user exchange. Also, Appian Records integrates all systems, providing a consolidated view, dashboard, monitoring, and report.

Appian helps in consolidating systems within the client's network, correlating data points, and offering visual dashboards to get a real-time view of various factors. Clients can check the functional state of their current infrastructure and monitor it in real-time, which also relates to the financial side of operations with business reports and similar functionalities.

The valuable features include process automation, Appian Portal, and Appian RPA. Appian allows easy integration with other systems, offers a visual dashboard, provides real-time analytics, and is flexible to be used by non-technical users for automating simple process flows. Additionally, Appian's data fabric now helps in correlating data across various systems for consolidated monitoring.

From a reseller's point of view, subscription licensing could be improved to be more cost-effective, especially for new prospects and smaller investments. Appian has new subscription models, but they might not always be feasible for smaller customers. Competitive pricing on the external user side is good, but internal user pricing needs to be adjusted for better market reach.

I have been working with Appian for nearly six years.

In terms of stability, Appian is quite reliable. I have not encountered any major downtime in customer environments. Their support team has been effective, making the solution stable overall.

Technical scalability is generally good, maybe an eight out of ten, however, some clients encounter issues due to high costs, affecting their ability to scale effectively.

Customer service in the Philippines is rated around a seven due to response times and the lack of a direct support line.

Neutral

The initial setup is generally simple and well-supported by the platform's flexibility and ease of use. My technical colleagues find Appian easy to learn, though they need to continuously adapt to new features.

Appian is promising yet the cost can be a barrier. The subscription cost is higher compared to competitors, which can hinder potential market expansion, especially for new prospects.

The main competitors for Appian are Pega and OutSystems. Appian is set apart by its RPA capabilities, though it is still catching up with the likes of UiPath.

Appian is a promising platform with significant functionalities, but it would benefit from more cost-effective pricing for smaller clients. The technical support could also be improved, especially in providing direct and faster response options.

I'd rate the solution nine out of ten.

I mainly use Appian for end-to-end process automation.

We use appian for IT services implementations of our esteemed clientele in CX transformation, process automation ,EX transformation and app modernization areas

Appian's most valuable feature is that we can create end-to-end process cloud ntive  workflows with minimum turnaround.

Appian could be be further improved by making it a strict, no-code platform with in-built process packs.

I've been using Appian for six years.

Appian is stable.

Appian is scalable.

Appian's technical support could improve, especially their response turnaround.

Positive

used multiple options. Since i represent  product agnostic  IT services organization, cant comment furthur on this

The initial setup was relatively straightforward, and deployment took around an hour.

NA

first year itself break even happened.

no

Anybody thinking of implementing Appian should have an enterprise-wide roadmap. If you're doing an enterprise-wide digital transformation, Appian is worthwhile, but not for just one or two use cases because the license costs are higher. I would rate Appian as nine out of ten.

Appian is primarily used for building workflows and low code applications.

Appian helps you do a lot of things. It's easy to configure and build an application platform, and it offers a lot of features. It's flexible so you can reuse it for a variety of use cases.

While Appian is generally flexible, it's rigid in some ways, doesn't allow you lot of options to cutomize. It takes longer to do something that isn't available out of the box. 

I've been using Appian for a couple of years.

Appian is stable.

Appian is scalable. We have a few more ongoing deployments, so the number of users will definitely go up.

There can be some improvement in support, start giving customer more importance than process

Neutral

The cloud version is managed by Appian, so it doesn't take a lot of time. 

The cost of Appian varies depending on the kind of license, and there are no additional costs that I'm aware of. 

I rate Appian eight out of 10.

Using this solution allows us to have faster testing on multiple devices.

The solution is simple to set up.

It's a stable product.

The product is open-source.

The solution needs to have more features. If you compare it to, for example, Katalon, Katalon had more features. 

We'd like improved functionality for testing new devices. For example, the last Apple phone is always a pain. The CEO of the bank has it, however, he wants the application running there. The testing of the latest models needs to be possible.

I've been using the solution for about a year. 

It's my understanding that the solution is stable. We haven't dealt with bugs or glitches and it doesn't crash or freeze.

I've never directly dealt with technical support. I can't speak to how helpful or responsive. 

We find the product simple and straightforward to set up. It's for a mobile application for bank solutions and mobile banking.

We are using the open-source version. We only invested in a couple of tests. However, we are using the open-source version which doesn't cost anything.

We also compared the solution to Katalon, and Katalon had a few better features than Appium. I cannot name each specific feature, however, I know that Katalon had some features that made it even faster.

We are customers and end-users. We don't have a partnership with Appian.

I'm not sure which version of the solution we're using at this time. 

I'd rate the product nine out of ten. We are quite happy with its capabilities. 

They are different zones because we have customers spread across various industries. It's spread across BFSI, manufacturing, and retail. The use cases are multifold. Appian is a solution more for finding solutions within the businesses, which are industry-specific, and business-specific. If it is retail, then we use Appian for onboarding solutions, customer onboarding, case management, and multiple.

Appian's most valuable features are the quick time it takes to develop for the market. It's easy and faster than other BPM solutions. 

I have been using Appian for more than 10 years.

I have found Appian to be stable.

Appian is a scalable solution.

We have premium support from Appian.

I rate the support of Appian a five out of five.

Positive

The initial setup of Appian is straightforward.

The number of people needed for the implementation depends upon the use case, the business area, type of customer, and type of engagement. It varies from a minimum of three to a ten-member team depending on the complexity of the project.

Appian has different models of licenses, such as enterprise-wide or user base. The price is less expensive when compared to other solutions and the various models are an advantage.

More flexibility in the licensing model is still needed because initially there were customers who are looking at only one or two use cases of business areas, but now the business areas are changing and there is a larger scope. One license model may not fit everyone. They need to be a little more flexible on the licensing model.

I would advise others there are multiple solutions in the market, low code solutions, BPM solutions, and case-finding solutions. There are multiple factors that make a good solution, such as ease to use, configuration, faster time to deploy, development and deploy scalability, and manageability. These are all factors that I would consider when purchasing a solution.

I rate Appian an eight out of ten.

We use Appian for some exam results, and related material, as well as some publishing solution material.

The workflow designer is the most valuable feature.

It's pretty good as it stands at the moment.

In terms of usability, there is a learning curve.

Licensing fees could be reduced.

I have been working with Appian for a year.

Appian is a stable solution.

Appian is scalable.

In our company, we have approximately 100 users.

Appian's use may be expanded in the future. It's a bit of a niche on the exam side right now.

According to my understanding, the technical support team is quite impressive.

It's fine; there's no need to improve technical support.

We are also working with Salesforce.

The initial setup is fine once you get your head around it, but there is a steep learning curve.

We have developers to maintain this solution.

We were able to complete the installation ourselves.

The price could always be better.

The full user license is quite expensive. It's cheap if all you want them to do is look at things, but if more people use an Appian app to update their information, it becomes more expensive.

Licensing fees are paid on a yearly basis.

You must consider what your use cases will be and ensure that there is a fit, because it is not a cheap option, you must ensure that you get a good return on investment.

I would rate Appian a seven out of ten.

We use Appian to automate processes that we are currently doing manually. We are working on an agile project. We have 500 people using this solution, most of which are operational.

This particular project started with four cases, or four processes. Next year we plan on doubling this and implementing eight more cases.

Prior to Appian, when we were handling a particular process manually, it took 40 days to resolve. After Appian was implemented, it took only seven days. The improvement in time is amazing.

I find the BPM the most valuable feature. It is easy to develop as it is a local solution. Appian is quick to understand and develop.

Appian could include other applications that we could reuse for other customers, CRM for example. This would make implementation quicker.

I have been using Appian for three years.

We had some concerns with the stability of Appian when we had a lot of cases. During normal operation it is a stable solution.

Scalability depends on how much you want to embrace the capacity of Appian. If you have a lot of cases, 150,000 for example, the stability will not be good because the memory required is so heavy that the RAM that you need is backed in. If you pass a certain number of cases, and the processes are complex, the situation is not suitable for Appian.

I have had no concerns with customer service. 

The initial setup of Appian was straightforward. We have an architect on our team who did the deployment. The deployment depends on the environment. For us, configuration took a day and to deploy no more than an hour.

We use one person, the architect, to maintain the program.

The ROI has been good. Profits increased because of this solution, this is why we are going to implement eight more cases next year.

The cost can be improved, however it is not too high for the customers here in Spain.

My advice before starting to implement this solution you need to consider what you want to do in Appian because everything is not possible. Sometimes when you think BPM process, you think that the interface application is the same, but it's not.

I would rate Appian an 8 out of 10.

Normally, we are building platforms. At the moment, we are running 19 big projects, and we had never used Appian before. One of our customers is a big consulting company, and one of their customers wanted a project with Appian.

They don't have Appian developers, but we have a very good team. They reached out to us and they had some projects in 2022 with Appian, and they asked for our support. I gave my BAs and PMs an introductory level Appian course, and now some of the developers are doing the associate and lead developer part for Appian.

The application life cycle is very clear. I started learning it and giving some workshops to my team. Creating the users and the building is very structured. Documentation is nice and it's easy to learn.

There's a nice fundamentals course that I can ask my project managers to easily learn, while the other local, no-code platforms don't have that option.

The certification is pretty expensive, and it doesn't allow for a tailored UI. I'm a little bit disappointed with the exam. It's different from the preparation, training, and sample exam.

One of my lead developers failed to pass this morning. I'm a bit sad because it's $200. If I ask 10 of my developers to get a certificate, it's $2,000. It's a scaleup company, so we have more than 60 people at the moment, but I can't ask most of my developers to get the certificate.

From a developer point of view, I can't try this in the free version because you can't buy one or two subscriptions. You need to get the minimum package for premium, which is about one hundred seats.

From the first day, I wanted to see the capability of reaching other functions, Google Cloud services, and cognitive services. There is already an OCR, intelligent document that comes in the My Cloud and which Appian gave me as a sample. I can't build it because it uses the Google cognitive services as a backend, and this is the thing that we couldn't try. 

You can't really test the software properly without actually buying the license first.

Something I would like to see improved is an SQL database connection.

We have been using Appian for over a month. We are still on the trial license instead of the full license.

I'm happy about the stability. It looks promising for me.

I can't predict how many developers it requires. It really depends on the type and size of the app and the capability of the developers.

We run a one-hour workshop from scratch. My developer can create the users' data, custom data types, a small UI, and a nice flow and read right from the databases easily. In one hour, he can complete as many tasks that normally take many days.

The scalability is a bit limited for the SQL databases because for some of my cognitive services, I'm using no SQL databases in the cloud. Appian doesn't support it. Appian only supports relational databases. There is no database for the unstructured data.

We are building platforms, but normally we are fully in Azure and the whole platform is in Azure, but because some of our customers and potential customers want to use Appian, I'm preparing my team for such opportunities.

You can't really test the software properly without actually buying the license first. Certification is expensive.

Appian is like a butter knife, not a Swiss Army knife. It will serve the business user's solution. It'll create a very good thing and the application is clear.

I really enjoy it because the PowerApps from Microsoft mature and are internally connected to other platforms inside Microsoft.

However, it doesn't explain the learning part very well non-technical people. There is a separation, but in the Appian fundamentals, this course is just for the BAs and the PMs. If they want to lead a project with Appian, this is the minimum standard that they need to know. At that point, it's easy for me to train project managers and business analysts. I think that's the advantage of Appian.

I would rate this solution 8 out of 10. 

My humble advice to someone who is looking to implement this solution is that they need to replicate. It's a so-called no-code platform, but it's not no-code because it has its own coding site. That's why they need to build one of their own solutions with Appian first to understand the how-to-dos first and become more confident. Luckily, the learning curve is not that steep.