Appian Reviews

My clients use Appian for workflow automation that spans many verticles.

The solution can be deployed on-premise and on the cloud. Customers that use cloud deployments typically use Amazon AWS and on-premise deployments are typically used for financial institutions.

The most valuable features of Appian are the VPN engine, it is fast, lightweight, and easy to set up business rules. Business teams can do it by themselves. That is a very good feature.

Occasionally, certain pre-made modules may not be necessary and customers may desire greater customization options. Instead of being limited to pre-designed features, they may prefer a more flexible version that allows for greater customization.

In a future release, they should add more connectors with the new upcoming integrations and data platforms.

I have been using Appian for approximately nine years.

Appian is a highly stable platform.

I rate the stability of Appian an eight out of ten.

Cloud deployment of the solution is highly scalable.

My clients are typically enterprise-sized businesses. They can have various sizes of users up to 20,000 VMC.

I rate the scalability of Appian a nine out of ten.

We provide support to some of our customers. However, some of my customers have not had satisfactory support.

We have a strategic partnership with Appian. We have different routes to receive support because we know people in order to contact them directly. We have had a good experience.

I rate the support of Appian a seven out of ten

Neutral

Not everyone can do the implementation of the solution, it requires specialized people. It is easy for qualified people.

The duration it takes to implement the solution depends on a lot of factors, such as how many workflows are required. A typical implementation can take four to six weeks.

I rate the initial setup of Appian a six out of ten.

We set up the solution in the customer's environment.

The price of the solution is reasonable and is paid annually. The price of the solution depends on how many users use the solution. It can range from $50,000 to $200,000. For example, for 20,000 users the price can be approximately $200,000.

There is an additional implementation cost.

I rate the price of Appian a seven out of ten

To determine whether a platform, such as Appian, is suitable for your domain industry, you must first assess whether it offers any out-of-the-box features relevant to your needs. If it does, utilizing that platform would be the best option since it already has the required functionalities. If the available features do not align with your requirements, consider choosing a platform that can easily build such services. Attempting to modify pre-existing features on a platform is a challenging task, and any upgrades to the platform could pose further issues for users.

The solution has high performance but the main issue is the lack of customization after deploying it.

I rate Appian an eight out of ten.

I work on the system administration side. I have customers who develop their applications on it for sourcing and procurement. In the past, it has been mostly related to nuclear facility management and risk applications.

The low code functionality and being able to get applications faster to customers or to the market are valuable.

There should be more flexibility for the developers to choose the look and feel of the UI. They should have a better ability to design their widgets and customize them with different colors, shapes, and sizes. That is a limitation that could be improved upon.

I would like to be able to integrate Appian and store various codes in external repos rather than just having everything within the Appian platform. 

It should integrate with open source a little bit more. There should be more flexibility and integration with various other tools in the organization, such as Jira and Confluence for release tracking, bug tracking, and being able to automatically tag items related to bug fixes and things like that. It is currently a little bit difficult to do in Appian. If it opens up to external integrations, it would be great.

I have been using this solution for about 10 years.

It is pretty stable.

It is scalable. You can horizontally scale the servers to add more nodes and have a clustered and high-availability environment.

Currently, we have about 20,000 users in the company. For maintenance, we have a big team of about 50 people, but they don't maintain just this environment. There are a couple of other environments that they maintain.

I have interacted with them several times. They're pretty good, pretty helpful, and knowledgeable. So far, it has been great.

I didn't use any other BPM solution prior to Appian. Appian was my first solution. Prior to that, I was basically developing applications from scratch using J2EE. In that aspect, Appian has been very helpful in getting the applications out very fast.

Its initial setup was not complex. It has been a pretty straightforward installation for the most part. There have been a few changes over the years in the support of app servers, and they've improved the functionality. Initially, it needed more work, but recently, they have added a lot of functionalities to be able to deploy quickly and migrate the code between environments. There used to be a few more steps previously, whereas now, it takes just a few clicks to get the code from one environment to another and finally into production.

It was implemented in-house.

I don't work on that side of things, but I have worked with various implementations of Appian in various organizations. Everybody seems to be liking it very much. They seem to be sticking with it for a long time and adopting it for more and more applications and different organizations within the company. I've seen good success with Appian across organizations.

I would advise starting small and developing applications in phases and adding as you grow. It is a pretty scalable environment, and it is easy to start small and learn along the way to be able to develop high-performance, complex applications.

I would rate it an eight out of ten.

Our customers are medium and enterprise companies.

Recently, we added Appian Process Mining, Appian Portals, and now Appian RPA.

There have been a lot of improvements, and Appian is now claiming to be a low-code platform with other market leaders, like OutSystems and Mendix.

One room for improvement is the ease of UI UX development, like in OutSystems and Mendix. I'd like to see Appian develop some kind of interface in their platform where the wireframes can be developed.

If Appian could have a partnership with leading platforms like Salesforce or Oracle, I think that would be beneficial for them.

I would also like to see Appian develop an interface to speed up development for business analysts. That sort of an interface is lagging in Appian right now.

I'm a solution architect and have been dealing with Appian for 10 years.

Appian is stable. 

It's scalable.

Technical support is very good. As a partner, we receive very good support from Appian.

I have previously worked with IBM BPM, OutSystems, Mendix, Unqork, Quickbase, and Pega.

Initial setup was fine. It was user friendly. Appian has the Appian Cloud, so development is fairly easy on the cloud platform.

The cost is a bit higher than other low-code competitors, OutSystems and Mendix. The price needs to be more competitive. 

With solutions like OutSystems and Mendix, you can implement headless commerce. For a B2C mobile app, Mendix is pretty good. For customers that have SAP, they have Mendix because it has been acquired by Siemens, and Siemens and SAP have a very good handshake. If they want to implement a low-code platform, they're going with Mendix.

I would rate this solution 8 out of 10.

Being able to model requirements in BPMN 2.0, get agreement from business and IT, and then have Appian BPMN 2.0 compliant engine execute the diagram. This has created executable requirements and speeds up the SDLC process greatly.

• Transparency of process flows, including number of instances of the process in-flight
• Identification of bottlenecks,
• Average time to completion of tasks and process, etc.

The employee onboarding process went from a mass email saying who is arriving for their first day, and just hoping all the things necessary got set up: phone, computer, badge, desk, login accounts, role specific access and accounts, etc. The Appian platform took from a blind mass email to full transparency with reporting, and greatly improved efficiency and effectiveness, as well as making continuous improvement possible.

Form creation and SAIL proprietary language still basically require programming. The claim a BA type can do everything is hogwash. They should be honest and say a developer is needed for web service integrations, etc. and complex forms; and a BA type can do the rest - requirements, architecture (collaborating with architects), design, process model, testing, deployment, and support. That is incredible powerful, but to say a developer is never needed is a lie.

Two years.

Very few.

No.

Poor. Very helpful at times and willing to go above and beyond, but very expensive, so overall poor.

Yes. IBM, Oracle, and Activiti open source. A different organization I was with selected Appian.

Complex: Data strategy and authorization to push data to the cloud was a big hurdle. How organizational data is going to be pushed to Appian, updated by Appian, and pushed back to the organization with or without approval steps needs to be planned and executed strategically.

It is expensive, but powerful. I would recommend comparing against cheaper licensing products and open source.

No.

Have 20% of a programmer as a resource, plan the round trip data integration, and get all approvals needed.

We use Appian for the automation of processes. The solution is typically used to automate case management.

The most valuable features of Appian are workflow management and the ease with which you can build the UI.

One of the areas that Appian is working on is to improve its UI capabilities and give more flexibility to the UI.

I have been working with the solution for around seven years.

Appian is a very stable solution. We've never faced any huge glitches or bugs with the solution.

I rate Appian ten out of ten for stability.

Appian is a scalable solution. However, we have to be a bit cautious if large volumes of data are being exchanged and if there are any use cases to transform the data in between.

I rate Appian a six out of ten for scalability.

Appian's technical support is pretty decent. The support team responds on time and sticks to their SLAs, which is good. Appian provides good support from an infrastructure and platform perspective.

Positive

Appian's deployment is pretty good. To run your deployment processes, it has separate built-in utilities and tools to deploy packages across the environment. I work for a services company, and I have built applications for some of our clients leveraging Appian as a platform, which is used probably every day.

I am using the latest version of Appian. Appian is deployed on Appian's own cloud in our organization.

Appian has a very strong workflow engine compared to other solutions like OutSystems and Mendix. I would definitely recommend Appian to someone who is looking for strong workflow and process capabilities. However, I recommend other platforms like OutSystems and Mendix to someone looking to build their own mobile app or looking for a lot more flexibility with respect to user experiences.

Appian is a pretty good tool. It's a low-code platform where you can start building your applications pretty fast. It has got really good workflow capabilities and a very good process engine. The solution has started integrating with cognitive services, RPA, and other services, which are probably at their initial stages, but the platform's roadmap is really good. Appian is definitely a platform to explore if you are considering a low-code platform to be part of your tech portfolio.

Overall, I rate Appian a seven out of ten.

I work for the largest distributor of Toyota Lexus in the Middle East. My area is related to car motors. I'm an IT senior general manager and we are customers of Appian. 

The workflow engines are a valuable feature. We use them to bridge the gaps of processes within our core systems that are either too difficult or too costly to develop within the core system. We bridge those gaps using Appian. 

We'd like to see the employee experience improved, something we can integrate with SharePoint. Right now we're looking at the Power BI which belongs to Microsoft. It has a lot of good features for low-code no-code development kinds of things. I'd like to see the ability of the software itself to integrate with the core systems. It's a gap that Appian hasn't fulfilled. 

I'd like to see integration with Microsoft products as an additional feature. Microsoft Team, or something like that. It's not there or if it is, it requires some work to enable easy integration with SharePoint. 

I've been using this solution for eight years. 

The scalability and stability of this solution are good. 

I'd say that the technical support is good. 

We visited the workflows that are provided within SharePoint but they did not fulfill the kind of things that we were looking for, or the problems that we were trying to solve at that point of time. We were planning to work on specific domains, specific areas, but you cannot make it work for complex things. 

The setup is not completely straightforward but not too complex either. The deployment itself wasn't too difficult, but this is something where features evolve and the things within it over time start moving. Adapting to any new feature while continuing to work is not simple. It makes things more complex. There are around 5,000 people using the product and we have five people dealing with maintenance. 

The price should be lower. It's not too expensive but I believe the price could be better. 

The product needs to be supported by top management for it to work. This is one of the things that we faced at the very beginning. Second, from a technical point of view, you need to have a dedicated team taking care of this from a product management point of view, not necessarily from a technical point of view because that can be outsourced. I recommend not doing the development in-house, rather to outsource it with one or two partners and the corporate team. I recommend going for the full cloud-based solution architecture rather than having part of it inside and part of it outside. If there is no issue with data sharing then I would recommend going for a fully cloud-based solution. It gives an advantage and reduces a lot of management headaches. 

I would rate this solution a nine out of 10. 

Our organization uses Appian for content management for our documentation. We are also using the solution for endpoint authentication in our clinic for clinical trials. In terms of banking, we use Appian for contract and access management.

Over the past 13 years, we have implemented Appian for 53 customers.

Appian is easy to install and set up, and it does not come out with your audit. It has accessible process orchestration and process management. With Appian, the time to market is much faster.

We are anticipating a few improvements from Appian. The product competes well with peer platforms, however, when you compare past that scale, there is room for improvement.

I would like to see more features for enterprises. They would also benefit from adding documentation and training on their site. 

I have been working with Appian for 13 years.

Appian is stable because it is on the cloud and it has options, actions, and latency. 

The solution is scalable when compared with the support of the infrastructure. It has proven to be scalable as far as the authentication time has been procured.

Technical support with Appian is good, however there is room for improvement.

Positive

The initial setup is straightforward. When compared with other solutions, Appian is much faster. It is easy to install. It is simple to transfer from the cloud, allowing you to get started immediately with the solution.

The process took us two days. If someone were implementing on-premises, it may take longer.

The licensing of Appian is less expensive when compared to other BPMs in the market. 

Appian is a good solution if you are going to implement BPM or automation into your organization. It can work on a small scale and scale larger afterward. 

I would rate Appian an eight and a half out of ten overall.

We primarily use the solution for application creation and process automation. 

We have 15 different applications running from CRM applications to case management applications, and we are using some RPA functions. We have a big stack of applications we are using. 

The quick development cycle is great.

The ease of development is great.

It's a stable product.

The solution scales well.

There is no issue with setting it up. It's easy.

Pricing is very competitive.

Technical support has been amazing overall. 

There needs some improvement related to the chatbot features.

The performance could improve. If we could calculate the amount of data that will be realized, it would help us a lot. 

I've used the solution for three years. I've used it for a while. 

We'd had no issues in the past three years. It is stable. 

I'd rate the scalability ten out of ten. It's excellent.

We have the maximum license, and we do not plan to increase usage as we do not have plans to increase our workforce. 

Techncial su[port is excelelnt. It's one of the best companies offering support right now. 

The initial setup is straightforward. It's pretty easy. It's not complex. 

We have witnessed an ROI while using the solution. 

The pricing is very competitive. It is not overly expensive. 

We have the solution implemented in our firm. 

New users need to understand the technical aspects of the product in order to take full advantage.

I'd rate the solution ten out of ten.