Appian Reviews

We primarily use the solution for approvals. 

The data types that we've built in Appian are very vast. We can customize the solution or point to predefined data sources. That makes it very unique.

The reusability is great. You can build it in one place and use it in many places. 

It is stable and reliable.

The solution can scale well.

Technical support is helpful.

It is easy to set up.

There is no UI customization possible. We'd like it to be more flexible for branding purposes. 

I've been using the solution for almost two years. 

The solution is stable. There sometimes is downtime during upgrades, however, it is reliable. I'd rate it eight out of ten.

The solution is scalable. I'd rate it eight out of ten. 

We have about 500 users right now, and we expect to expand usage in the future. 

We've had good support from the Appian team. They have a good support model and are easy to reach. 

I'm not sure if there was another solution used previously.

The initial setup is very straightforward. It's not overly complex. It's a cloud-based tool which makes it very light. There's not a lot of overhead.

We had basically a one-click deployment. The implementation is deployed via predefined screens. It makes it very simple.

There are also good import/export features that are helpful. 

Appian mostly manages the deployment, and one or two people are required to manage the overall platform once deployed. 

We did not use any outside assistance. 

It does take time to get an ROI. Depending on the licensing type, chances are you will begin to see an ROI, especially for time to market.

I don't deal with licensing. I'm not sure of the exact cost. 

I'm an end-user. 

We are using the latest version of the solution. 

While there are a lot of factors when it comes to choosing a solution like this, Appian is a very robust platform, and it does offer advanced use cases. If you are more into Microsoft, however, Power Apps may be a better option.

I'd rate the solution eight out of ten. 

I am working in a software house, and we are using Appian to build a custom-made application while trying to fulfill our client's requirements.

I don't think we currently have any applications for our internal processes, which include a set of Oracle APEX products or applications, especially custom-made applications, which is something we need for ourselves. However, we have many use cases for our clients.

Workflow Engine is a valuable tool. Besides the resource kit, I believe both tools are very, very convenient for our clients.

I don't think I have anything to comment on the areas that need improvement in the solution, but I can refer back to my technical team. As the solution architect, I don't have hands-on experience with both products.

If you ask me about my thoughts on what is missing in Appian or my opinion on what I would want the vendor to add in the future, I would say that the product is in a state of perfection. However, we can't really guess what AI and big data models might sell us in the near future.

I am currently using Appian and Oracle APEX, and I will soon start to use Appian Version 23.1. Also, our company has a partnership with Appian.

I won't be complaining near the client. Stability-wise, everything is okay.

It is definitely a scalable tool. I would rate its scalability not less than eight and a half out of ten.

Even with an on-premise implementation, the scalability is still high, so it is easy to scale up.

I don't have any experience with it personally, but our team that practices on Appian uses the technical support very frequently, maybe on a daily basis or so.

We have been using APEX in our organization for some time now, and I was checking the comparison between Oracle APEX and Appian on peerspot.com for an unbiased opinion. Presently, we are implementing both Oracle APEX and Appian almost equally for small to medium purposes. However, for enterprise needs, I think we will choose Appian.

It depends on the functionality that we are using. For instance, having an LMS solution for our clients is a bit straightforward. Sometimes, clients expect us to implement ERP using Appian, which is very complicated. In such cases, I don't believe that Appian is a good tool for that.

When it comes to pricing, it's definitely not affordable. However, it really depends on the requirements that you're seeking from the solution. If you're looking for an on-premises distribution, it can be a bit expensive. But this is usually the case with on-premises solutions. That's why we have a cloud solution available, which is more cost-effective.

Additionally, the cost is justified by the use cases, and Appian is a good solution overall.

In terms of hidden or extra costs for additional features beyond the standard license, I don't think we've had any exposure to such scenarios, except for the resource kit. From a technical standpoint, I'm not sure if it's paid for separately or included in the license cost. As you may be aware, we've partnered with Appian, so I believe we have an official case here.

I suggest that those planning to use Appian take care of the practice lead because many resources claim to have solid and vertical knowledge of Appian. We are not sure why there is a risk of resources being unavailable during this trip. Additionally, we have a shortage of Appian resources, so finding a good practice lead could be a challenge. Overall, I rate this solution a nine out of ten.

The solution is used for automating software processes for creating internet sites for internal usage. The solution can also be used to make the process easier for external entities. Appian can be deployed on the cloud and on-premises.

The solution helps by providing an automated out-of-the-box process that helps us quickly publish applications within six weeks without requiring any customizations.

The most valuable features are the low coding and low code data.

The solution needs more features. For example, a way to connect to our viewing database, to record, and more interface and component design.

The cost of the solution has room for improvement.

I have been using the solution for 20 years.

The solution is stable.

The solution is scalable.

The technical support for Appian was just expanded to support multiple regions.

I previously used APEX Oracle Application Express and OutSystems. From a local perspective between the two solutions, I prefer to go with OutSystems. Overall I prefer Appian because it has a VPN engine compared to OutSystems which is just a workflow engine.

The initial setup is straightforward. The average deployment takes around two days and requires around 30 percent of our developers.

We complete the implementation for our customers.

In general, our customers are satisfied with the return on investment.

The price is high.

I give the solution a nine out of ten.

We have multiple environments. We can move our application from one environment to another environment through a governance process and approval through the application manager.

The solution is easy to maintain and very configurable.

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.

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.

There are multiple use cases of Appian. A banking customer uses it more for agent onboarding; we are working on contract management for a manufacturing customer; and we are working on an incident management system for an airport. There are almost seven to eight use cases, as of now. 

We don't use Appian, we are partners and we implement this solution for customers. I'm working on both on-premises and cloud-based deployment. Appian's deployment is hybrid. 

Appian has many valuable features, the first being the ease of development—rapid development. Second, the process of learning the product and tool is faster when compared to its peers in the market. It's closer to low-code, and while it's still not very easy, it's more low-code than other products in the industry. Appian has a good user interface, a seamless model user interface, which comes without additional coding. It can also integrate with multiple systems. 

There are four areas I believe Appian could improve in. The first is a seamless contact center integration. Appian does not have a contact center feature. The second is advanced features in RPA. The third would be chatbot and email bot integration—while Appian comes with chatbot and email bot, it's not as mature as it should be, compared to the competition. The fourth area would be next best action, since there is not much of this sort of feature in Appian. These are all features which competitors' products have, and in a mature manner, whereas Appian lacks on these four areas. I see customers who are moving from Appian to Pega because these features are not in Appian. 

I have been working with Appian for three years. 

The stability and performance are good. Appian is focusing a lot on this because they recently came out with a Kubernetes system acquisition, which is providing them the ability to scale as well as an expansion model that can be as stable as required. The performance is very good, as this solution is available across multiple cloud systems. 

As far as maintenance, it's pretty straightforward because Appian, as a company, comes with very mature hotfixes when required, as well as seamless upgrades. As long as you do not do any customizations—which is not recommended—it is pretty easy and straightforward to maintain, and does not take much effort. 

Appian is definitely easy to scale, especially if you understand the requirements. It's a good architecture. 

Of our customers who use Appian, I would say most of them are medium-sized. Next would be large-sized, and then there are not many small-sized customers. Medium- and large-sized companies mostly go for Appian. 

I would rate the technical support of Appian about a seven out of ten because there is definitely room for improvement when compared to the other product support we are seeing. 

The initial setup is a simple process. If it's on cloud, it does not take much time. If it's on-premise, you have to have all the required hardware. It takes around four hours. 

We implement this solution for customers. 

Appian is very flexible in their pricing. In general, Appian's pricing is much, much lower when compared to competition like Pega or other products. Appian also has a flexible licensing model across geographies. Pega usually goes with a single licensing cost—which is a US-based cost—for all global customers, and it's costly. Whereas Appian has a different regional licensing cost model and it can be cheaper, depending on geography. So Appian's licensing is very flexible, and cheaper when compared to other competition. 

The pricing is pretty straightforward. If you're going for a cloud-based deployment, there are no additional costs because you're just going to be on the cloud. However, if you're going to deploy it on-premise, you would need to install software, so you might have to procure your own database and servers and everything. The current recommendation, and what most customers are going for, is the cloud because it's easy to maintain. There aren't really any costs except for the licensing. 

Pega and Appian are both good BPM platforms. The area where Appian has the advantage is that it's really low-code. It takes much less effort when compared to Pega, both for developing and for setup and implementation. Within about 30 days, maximum, you can build out a product in Appian, whereas it will take you much longer in Pega. However, in regard to the four areas in which I believe Appian is lacking, Pega has all those features in a mature manner: seamless contact center integration, advanced features in RPA, mature chatbot and email bot integration, and next best action.

I would rate Appian an eight out of ten. 

If you are looking for a fast, rapid rollout of applications and you have multiple medium-scale and small-scale processes that you want to roll out at a faster pace, with ease of maintenance, then Appian is a good product to go with. Appian can also be leveraged for large-scale implementation—for example, financial service customers, for loan origination or claims organization—but you would really need to understand your requirements in order to achieve this with Appian. Whereas with Pega, it has framework for loan originations and everything, which Appian doesn't come with. Appian is a plain vanilla product, and if you go for a large-scale core implementation, then you should have enough information and requirements to capture it. Appian is best suited to mid-scale and small-scale processes and a rapid rollout.