Appian Reviews

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.

Our client, a telecom company, has use cases related to the telecom domain, and it's around workflow management kinds of use.

Their workflow, which can be easily built into a BPM, is one of the best features.

The development time for Appian is far less than high code languages, like .NET, Java, or some other languages. 

We delivered the first application within 12 weeks, and that was a really big project. If we went with some high code tools, definitely it should have taken more than 15 or 18 sprints, and every estimate, in that case, would be a two-week sprint. It took only around 40% of the typical development time.

The initial setup is easy.

It's very stable.

You can scale the product well.

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.

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.

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.

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. 

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.

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.