Appian Reviews

I primarily use Appian for digital remittance, storing information, processing transactions, and regulatory reporting, and I mainly use it for the digital remittance register.

Whenever we receive an MT103 from our corresponding bank, we upload the messages into our Appian-based digital remittance register. Appian extracts data from different fields of MT103 or even MT202, and that information is cleaned and segregated into different fields and columns. After that, we process the remittance, and subsequently, after completing the transaction, we report it to our central bank. Appian generates the report, which is quite handy and useful. My team can interact with peer members while using Appian; for example, when a maker uploads a transaction, the checker reviews it. If there is any discrepancy or error, the checker can directly reject the transaction so that the maker can rectify and reprocess it. If everything looks good, then the checker can approve the transaction directly, making it quite time-saving and reducing errors while ensuring pure compliance.

Appian is quite smooth by nature. We have used other software and tools, but most often we used to get lags and disruptions; however, Appian is quite smooth and we did not notice any major issues. The best feature would be its reliability and smoothness. While using it, we can store data, extract data, download, and generate reports anytime, which makes it quite handy.

Remittance is a crucial part of my integral operation, so any disruption would majorly impact our clients. After switching to Appian, we never faced any disruption as it is reliable and we can generate data at any point in time, quite faster than other tools in my personal opinion. Regulators can ask for data from us at any time, and with Appian, we download data from our Appian tools to share it with them whenever they ask. I would share a real-life example: a customer's transaction processed more than a year ago. Suddenly the customer came back asking for all the details. In our previous tool, it was quite difficult to generate transaction details from over a year ago; however, while using Appian, we can pull up data using different key search fields, such as a customer's cell phone number, remittance tracking number, or MT103 reference number. We shared it with the customer instantly, and the customer was surprised we could provide all the details in such a short time. It added reputational value for our organization, thanks to Appian.

You have pointed out two major things: time-saving and reduction of error, which are key points while processing remittance. Previously, while using another tool, it was quite time-consuming to process remittance, but after switching to Appian, it can extract data from MT103, eliminating the need for manual data entry. The process has become fully automated. Previously we could process only five to ten transactions within an hour, but now, after switching to Appian, we can process about 100 transactions in an hour, making it 10 times faster. In terms of error detection, since Appian extracts data from MT103, the extraction rate is quite good, and the error rate is negligible, lower than 0.001%. We can share accurate, error-free data with the regulator, which is essential for us. Appian benefits us significantly. After receiving an MT103, we check what the remitter is, the amount, if it is under threshold for processing, and if it is from a high-priority remitter or client. Since Appian extracts data from MT103 messages and identifies top-level clients from the database, it can notify us to process their transactions with priority. Due to automated data extraction, there are fewer instances of error. In our previous tool, we reported regulatory data to the central bank manually and often received complaints about invalid purpose codes due to manual data entry. Appian handles this automatically, and after switching, our error rate has dropped significantly, resulting in positive feedback from the Central Bank of Bangladesh regarding our reduced error rates. This has greatly enhanced our organization's reputation.

Appian is fully on-premises, and we have our own system.

Appian can be improved by adding a geo-location tagging feature, which would be really helpful for identifying remitter addresses. If Appian can suggest the country based on that address, it would significantly decrease error rates in processing remittance. So far, Appian is excellent, but this addition would be a revolutionary improvement.

If Appian can handle geo-location tagging, it will increase our speed by 20 times. I suggest this improvement and hope for the best.

I have been using Appian for more than two years.

Appian is absolutely stable and reliable in my experience.

We have tested Appian during peak usage and off-peak times, and we have not experienced any issues such as lagging or system disruptions. It is running smoothly, and we hope it will continue to provide us with the same support and reliability in the future.

In terms of scalability, we have not encountered any major issues. Our volume has increased by 20% in the two years since using Appian, and it can handle the increased volume effectively.

While deploying Appian, we reached out to customer support, and their assistance was great. They were very helpful, friendly, and their professional attitude impressed us tremendously.

I would give Appian's customer support 10 out of 10 due to their next-level support.

Positive

We previously used different tools such as Finastra and Oracle for data extraction and report generation. After switching to Appian, we realized we made the right choice, as it is much faster and more helpful than those tools, including some Microsoft products we tried previously.

It was really easy to deploy Appian for our organization; it is user-friendly and we deployed it without any major difficulties. Our development team thoroughly enjoyed the deployment process, and we completed the entire system rollout within 15 days, which was remarkably fast.

I was part of our Appian deployment team, and we deployed it for our organization.

Appian has increased our remittance processing speed by 10 times. It allows us to process a large volume of remittance in a short time, improving customer service. Using Appian is saving us five full-time employees, which is significant since we currently have only four team members. The manual processing we used to require would necessitate an additional five employees, so Appian has truly been a miracle for us.

Compared to other tools, which I prefer not to name due to privacy, Appian provides value for money, is easy to use, has a straightforward setup procedure, and offers great support from the Appian team. Therefore, my overall experience has been quite impressive.

We evaluated some Microsoft products before choosing Appian, although I cannot name them due to an NDA. After thorough assessment and testing, we found that Appian was faster and would provide the most benefit compared to the other options we considered.

On a scale of 1 to 10, I would rate Appian a 7.5. If the geo-location tagging feature gets added, then it will be a 9.5.

I choose 8, because of its reliability, smoothness, error-free report production, and its data extraction capability.

The integration capability of Appian is quite good; we have integrated it with our core banking software, and the integration is fast and reliable. The API works exceptionally well, so in terms of integration, I would rate Appian 9.5 out of 10.

If I compare it with other tools, our team members really enjoy using Appian. It is straightforward and user-friendly, leading to positive feedback and making it highly recommended for new users due to its ease of learning and use.

Appian's security features are quite top-notch as it has a user verification system that verifies users before granting access to the whole system. In terms of regulatory compliance, it is quite helpful since it enables authentic and error-free reporting, which leaves us satisfied.

Appian's documentation is quite helpful; while deploying the system, it assisted us greatly. I would recommend these resources to other users and development teams considering deploying Appian.

Appian's automation capability is excellent; it extracts data automatically, and the scheduler runs smoothly, generating reports in a timely manner. Therefore, Appian is quite effective and helpful in terms of automation.

I highly recommend using Appian to others. My overall review rating for Appian is 7.5 out of 10.

On-premises

Other

A common use case for Appian is intelligent automation, where companies wanting to transform and have the latest technologies such as robotic process automation, fintech, AI, and artificial intelligence under the same platform use Appian to automate their business workflows.

There could be multiple industries that could benefit from this, including investment banks, retail companies, manufacturing companies, and healthcare companies. There's a variety of use cases for implementation.

The features of Appian that have proven to be the most beneficial are its capability to create processes and integrate with external systems while ensuring data consistency across all the systems.

The latest features of Appian are quite useful around the UI/UX design and the artificial intelligence integrations.

Appian is aiding in leveraging AI technologies in multiple ways: one way is for developers, as they make development efficient and quick by enabling developer co-pilots across various phases of the application, which helps design Appian quickly and provides suggestions along the way.

Another way is through AI Skills, which can be integrated anywhere in the process model to leverage artificial intelligence for tasks such as extracting data from documents, summarizing information from documents or long paragraphs, and building custom prompts with Appian.

Appian also utilizes AI for business users, providing a feature called process each view, enabling business users to create their own dashboards, reports, and gain insights from their data and processes using artificial intelligence. It's multi-fold and always growing.

Appian could improve in terms of how it approaches external use cases.

Appian is a great tool for internal use cases where the users are company employees, but it has room to improve for use cases where the users are public facing, where anonymous users could come to a site and run a business workflow or interact with some data.

I have approximately nine to 10 years of experience working with Appian.

I have faced challenges while integrating Appian with existing systems, as there might be challenges around the integration systems not being stable or having many exceptions.

However, if the integration systems are stable and their process of integrations and the APIs are well documented, there are no challenges to integrate with Appian; it's fairly simple.

The stability of Appian would rate as nine, as it's a stable environment.

Appian is scalable. On a scale of one to 10, Appian rates as a nine for scalability.

The technical support for Appian rates as 10 out of 10 because they have a great support team.

Positive

I have experience with Appian, not SAP solution.

The initial setup of Appian has two ways of setting up the environments: one is on-premise, and the second is cloud environments.

The cloud environment is very easy to set up, as the Appian Cloud support team does everything for you end to end, and you will have the environments available where you could have the platform in about 24 hours, which is very quick.

This is preferred by about 95% of clients, as they would have Appian on Cloud.

The remaining 5% opt for Appian on premise due to data privacy issues or compliance challenges, where they manage the infrastructure themselves, which requires a couple of weeks for an infrastructure administrator to set up Appian on their own service.

I'm a reseller and a partner, and my relationship with Appian is that we implement Appian for our customers.

The majority of our clients see the return on investment in about one year after implementation.

They see return on investment in terms of cost savings, time savings, more efficient processes, and more efficient employees.

The price of Appian, on a competitive landscape, is a little bit on the higher side for companies, rating maybe a 6.5.

I would recommend Appian to especially large to medium, medium to large companies looking to automate their business processes, as it's a great tool. I would rate the whole solution as a strong 9.5.

Public Cloud

Amazon Web Services (AWS)

I have been using Appian for customers. My customers bought Appian directly from Appian.

The features I find most valuable in Appian are the IDP and the Composer. We do use Appian's drag-and-drop interface. This helps in creating the UI and simplifies my workflow design.

I think Appian could improve by adding its own native GenAI and agentic capabilities. I would like to see additional features in the future such as native GenAI and agentic capabilities.

I have been dealing with Appian for the last two or three years.

My customer did not face any problems with the integration with third-party solutions.

It is not applicable for me regarding the technical support by Appian since it is ultimately provided to their client. I can only provide limited information about that.

I do not look for new solutions.

It requires Appian expertise for the initial setup and configuration. However, once people who have been accustomed to designing Appian take on this role, they can do it easily.

I am not an end user of Appian. I am more of a service provider.

The pricing of Appian is competitive.

I would assess Appian's integration with my customer's IT infrastructure as good, seven out of ten at least. The data fabric feature is good. I rate this review a seven overall.

I mostly use Appian for internal applications in the firm.

The most beneficial aspect of Appian is its data management capabilities and the process engine in general. It allows for a seamless transition from process-centric to data-centric operations. Additionally, the zero-code integration feature is remarkable, allowing for ease of data transfer and workflow enhancement.

I would like to see more enhancement in the user interface to allow more freedom in designing the sites and pages. The user interface should be updated for a more modern and appealing look.

I have been working with Appian for around fifteen years.

So far, I find Appian reliable and stable.

Appian is scalable, but it depends on how you build your applications. With a proper setup, Appian is scalable.

The technical support is generally good. Though I have had some issues in the past, overall, I consider it effective.

Neutral

I have experience with Microsoft Power Apps and have seen OutSystems. However, most of my experience has been with Appian.

The initial setup of Appian was very easy.

No implementation strategy was used. We simply built different platforms like development, testing, UAT, and production.

Appian is very efficient, allowing us to build a lot of applications within a financial year, making it cost-effective.

The pricing of Appian is based on the number of users and generally ranges from 70 to 100 USD per user per month. I would like it to be more flexible, not solely based on the number of users.

As alternatives, I have worked with Microsoft Power Apps and have explored OutSystems.

I would recommend looking into data management, reporting, and process capabilities of Appian. Overall, I rate Appian as a nine.

On-premises

I am working with all of these products: Pega, Appian, and OutSystems. I use Appian as a process orchestrator for workflow and rule-based routing, and it is preferred when I am developing an enterprise-wide application. The application is mobile-friendly, allowing me to use it across any device, whether mobile, laptop, or desktop.

It is easy for me to define the process and create configurable workflows. Additionally, they have provided inbuilt integration points and services, which facilitates integration with external services.

If there is a very complex process that includes a lot of data transitioning and memory-centric processes, it consumes a lot of memory. For those use cases, Appian needs to optimize memory utilization. AI-related features should also be more integrated.

I have been in this ecosystem for quite some time. For Pega, it is 20 years, and for Appian, it is more than ten years.

I would rate the stability as eight out of ten. As a product, there are no issues. It depends on how it has been designed and how it has been configured.

Appian is scalable in its architecture.

Their customer service is responsive, and the team is very prompt for support. The response depends on the kind of partnership vendors have and their relationship with them. For step one issues, which impact most of the business on that workflow, I get quick support from the Appian team.

Positive

Whenever there is a production deployment, it involves the Appian development team. However, if other systems are also involved, representatives from the integration teams of different systems are needed as well.

There are two buckets. On the pricier side, both Appian and Pega are enterprise-level solutions, placing them on the slightly higher side. 

However, the robustness of the products, their features, and their availability justify the pricing.

I have considered Appian, Pega, Uncorp, and Mendix as alternate solutions.

Overall, everything is eight out of ten. 

I am a little bit biased towards Pega. Pega has a lot more standardized processes, which take less time to go to market compared to Appian. Appian provides a platform. 

I use Appian for creating applications, including BPM applications.

Appian allows us to manage the entire database. I can create tables, perform database-related activities, and create multiple tables. I can directly create foreign keys, connect tables, and manipulate data using expression rules. This feature replaces data workflow from on-premises.

Since I have just started using Appian for three to four months, I haven't explored every part of it, so there might be areas that need improvement that I am unaware of.

I have been using Appian for the last three or four months.

The deployment process is very easy. I create a package for the component I work on and deploy that package to another environment.

Appian is a stable product and works very well.

Initially, without much coding, I can easily handle five thousand records. However, for more than five thousand records, I have to manage with some coding.

Appian has a community where I can put my questions. I haven't had a chance to contact the support team directly.

Positive

My experience with the initial setup is normal as I didn't get a chance to work on it. I started directly with creating features after the initial setup.

I would rate Appian nine out of ten. I would definitely recommend it to others. Being an initial user, I haven't had a chance to explore it much. I rate the overall solution nine out of ten.

Public Cloud

Other

The solution is used to automate internal operations. We had industrial and equity-based financial clients.

The product improved our operational efficiency. The deployment takes one or two weeks. The rollout takes two to three weeks.

The solution’s turnaround time for development is better compared to other tools. The solution enables fast development. The traceability of the processor is good. There is much more governance and regulations on the processers. The tool reduces the time of the processes by 30% to 40%. The solution’s low-code aspect has greatly impacted the development and deployment speed.

One of the major reasons we are using the product is that we can reuse the modules. The developers can reuse all the modules. It enables us to make subsequent developments in less time. The prebuilt modules can be deployed within two to three weeks. The tool is very flexible. Compared to other platforms, the Appian product team was agile in quickly customizing things for us.

It is difficult to set up the on-premise version.

I used the solution for more than three years.

The solution is very stable. I've never faced any downtime. The response time is also great.

It is easy to scale up the product for a large number of users. We can scale up to 100 users within 20 to 30 minutes. I rate the scalability a nine out of ten. Our customers are enterprise businesses.

The technical support is not excellent, but it is good.

Positive

The initial setup of the cloud version is quite easy. I rate the ease of setup of the cloud tool a nine out of ten. It is difficult to set up the on-premise version. I rate the ease of setup of the on-premise tool a five or six out of ten.

The tool is quite costly. It's not affordable to the general public and most companies. People would prefer a low-cost version that comes with reduced functionalities. The solution would be more accessible to the users if the vendor provided it at half the cost. I rate the pricing eight and a half out of ten. The price is quite high.

I haven't faced challenges with new implementations. If an organization has a long-term goal of automation and wants to explore automation, Appian is a good choice. The product is quick, agile, and very robust. It provides everything we need. It's not like the other platforms where we have to buy multiple things on top of the actual product. It is a holistic automation tool. Overall, I rate the solution a nine out of ten.

Appian is a good workflow solution. So, I use it for workflow and low-code application development.

Workflows can basically be embedded in any domain. For example, we use Appian as a workflow solution primarily in chunks. We have a couple of use cases that we have built.

From a personal marketing perspective, it basically supports the end-to-end building of an awesome product, wherein you can use it primarily for data orchestration, and then for building process workflows, and then for building approval workflows. 

So, you can set it all together. You can bring in the data through Appian, and then I use this to integrate with different solutions, different products, and different platforms that exist in the company. It brings them all together. It can then be automated. We have a couple of new steps available to us.

For one of the clients, we've used this to build a complete end-to-end claim cycle, where we built a portal that integrates into various systems. 

We get emails that get processed. From there, a claim is received. It goes through the entire claim designation lifecycle. It goes through different people, different approvals, and then finally, there's some integration with the payment system. 

Once the claim is approved, the payment happens. And it is one seamless process. And then if any litigation is required, it can be directed to the finance team and so on. So, there is an end-to-end claim cycle that has been automated using Appian.

So, this is just an example of a workflow we've optimized using Appian.

From a feature perspective, Appian has quick development, given it's a low-code platform; you can quickly use it to build a solution.

And then, if we need to make changes, we don't need to do a lot of coding.

With low-code, we don't need a lot of coding, and then from the plumbing perspective, there is a complete CI/CD pipeline that exists within Appian that can be leveraged for open deployment. 

We can manage versions, do field deployment, and manage all these smaller incremental changes that need to be done. It's self-sufficient, from my perspective.

From a product perspective, it's good. There are some restrictions with respect to using external components within Appian. 

So, for example, if we do not have a particular feature available, there's a long cycle of getting approvals and all of that. That does not offer flexibility, which definitely can be improved on.

Another area of improvement is pricing. 

I have been using it for two years now. 

It is a stable product. I would rate the stability a ten out of ten. We have not faced any challenges with respect to the platform in the last two years. 

Since it is on the cloud, it is easy to scale. 

There are around 200 end users using this in our company. The usage depends on the end user. 

Appian is scalable, especially from an integration standpoint. It offers low-code integration capabilities, eliminating the need for external integrators. 

It comes with many components and connectors that facilitate system integrations.

The customer service and support are very responsive. We haven't faced many issues, but when we have, the support team has been very helpful.

The Appian community is strong and open. You can often find solutions or discussions relevant to your issues. Consulting with community members through platforms.

The initial setup is straightforward and easy to use.

Deployment is quick.

We did it in-house. It depends if you have the skills in-house, it can easily be done.

So, there are not many things that you have to do. The solutions can be built in Appian itself, there's a pipeline that exists. You just have to kind of tag the components that need to go into deployment and use them to deploy easily.

It is a little bit expensive when compared to other platforms, it is somewhat expensive.

The license is not very cheap. It's on the expensive side.

The licensing is on an annual basis.

Overall, I would rate the solution a seven out of ten. 

I would recommend it, especially if you're looking to quickly develop workflow solutions with low-code integrations. Among similar platforms, I'd place Appian in the top tier.

Public Cloud

I've done a lot of personal projects, but we haven't yet implemented anything at an enterprise scale. We're just toying around with it and seeing if we can find a good solution for our needs. What we're focusing on is bringing apps to market faster than what a typical application development team takes, which can be a six-month to a year timeline. We want to see if we can do more proof of concepts, prove ideas, and provide value to our business as they ask for it.

It has good integrations. We were looking for out-of-the-box integration with both on-prem and publicly accessible data sources. We needed integration with the cloud, OData, our REST API feed, and then on-prem passthrough to go to a SQL database or on-prem APIs through Azure local deployment, etc.

The tool itself is pretty good, but the main area that we struggled with was the backend. The frontend development is really good, but the backend modeling can be streamlined a little bit. There are good integrations, but tying them through the data layer and then up into the frontend could be improved a little bit. It does read/write on the data source, and you can configure it to just write or just read, but there is a little bit of work involved. 

I have been using it for less than a year. We started around December of last year looking into it.

It is as stable as you make it. If you're following good software development practices throughout the process and you're doing good checks and balances and maintaining solid architecture principles, then it is pretty stable. If you don't do that coming into it and you don't establish COE in standards, you can definitely get yourself into trouble.

The way Appian manages its software makes it directly scalable to new systems. Especially with the cloud distribution, Appian is going to integrate with any new hardware architecture that comes out, and you don't have to do any updates for code. If you're on the cloud, then deploying it is very easy, and scaling that outwards for capacity is also very easy. One limiter that we had for scalability was on our side. Our on-prem data had to feed through that, and there were scalability issues with the demand on the server, but that was more on our side, not on Appian's side.

In terms of its usage, right now, we are exclusively looking at it from our analytics and intelligence standpoint, and we don't have anybody dedicated to Appian. We have more teams who focus on low code efforts and are playing around with it to figure out the capabilities and the standards that we want to work with it. We are building out the integrations that we need to scale it up. So, there is nobody fully dedicated to it, but there are definitely people playing around with it. There are only a handful of people right now. There are probably four to five at most at any given time.

We don't have a plan in place to increase its usage because we don't know. We haven't really found an incredible use case where we can deploy it. Once we set up the infrastructure and get business buy-in with a few demos, we can talk about scaling.

I did not go through tech support too often, but when we reached out to more of a technical account managing team, from an enterprise level, the support that we got was pretty solid.

We didn't have a BPM in place beforehand. 

Its initial setup is a little bit more on the complex side. It takes more of a data engineer mindset to set it up the right way. The benefit of a low code tool should be that you can put it in the hands of business users and let them scale with it. From the frontend perspective, it is really good, but when you have to go into the data and actually integrate it, it takes a dedicated IT team to really set it up. I'm not sure if there is much they can do to fix that because it really takes domain expertise to set up data sources, but that's the blocker that we've seen.

I'm sure it is cost-effective, but right now, we're just toying around with it. So, I don't have any hard numbers.

We were looking at other solutions as competitors when we did our initial investigation. If I recall, we talked to Creatio. They're a smaller name in the space. We talked to LANSA. We also talked to Pegasystems, but we didn't really get much of a response from them. We talked to Retool as an option. They're not much on the BPM side. They're more on the frontend development side. So, we factored them out pretty quickly.

We didn't really come into it looking for a BPM solution. We came into it looking for a low-code application development solution. All of those fit the bill, and they had various benefits and drawbacks. Where Appian stood out was the full stack integration. They have the data integration layer for both on-prem and public sources, and then there is the full stack, including RPA integration, integration with different systems, frontend development, and data modeling. They also offered a BPM solution, which was really nice.

I would advise setting up your standards beforehand and identifying which teams are going to be responsible for the governance side of things. You need to identify a tech focus team that's going to be handling that. Once you have that built pretty solid, going from there, if you're targeting a citizen development model, then you can start pouring out into citizen development. If you're sticking within IT and app development and building a low code team, you have to set standards beforehand and make sure everybody is on the same page.

I would rate it a seven out of ten. It is a pretty good solution. I haven't yet seen any major drawbacks. There are other competitors that offer more specialized solutions, but as a general solution, it takes the lead.

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.