Item: Qlik Sense
Rating: 7
Author: Verified User

Use Cases and Deployment Scope

We are using Qlik Sense to provide insight to what is happening with insurance claims. We have 2-4 million claims a day and run reporting in batches every morning.
We also use it as an ETL tool but are attempting to move away from that and get our users to perform their analysis in the apps.

Pros and Cons

Easy for users to understand.
Great security.

Code gets complicated after much development.
Qlik makes you pay for every feature.
Expensive.

Return on Investment

Helped gain insight into our data.
Moved us away form SQL reports.
Gotten rid of most CSV exports.

Alternatives Considered

Microsoft Power BI

We wish we would have selected Power BI as our solution. The main reason for that is that in order to view a visualization in Qlik Sense you need a license. With Power BI that is not required.

Other Software Used

Python IDLE, Microsoft Visual Studio Code

Likelihood to Recommend

Qlik Sense is well suited for summary analysis and finding answers quickly. If the data grows beyond 10 million records or so the performance begins to suffer.
If you do not have a good understanding of the data structure then Qlik sense will not help you much.
Their ODAG (On Demand App Generation) feature is great when your data becomes too large.

Great for a lot of Use Cases

Software Version

Overall Satisfaction with Qlik Sense