We evaluated Yellowfin, Tableau, Microsoft Power BI, and Domo. Those were the ones we did in-depth evaluations on. We did a little more industry research beforehand, looking at industry reviews. The reason we narrowed it down to those four is that we knew of other companies within our organization that were using one of them. Qlik is great, but we didn't know of any other users of it within our organization at the time and we didn't want to be too rogue.

Tableau is outstanding. It came in at number-two in our evaluation, and I'm sure I'd be sitting here talking to you all thrilled about it, but Tableau seemed to be going in a new direction. There was the on-prem portion, plus the software that had to be installed on every PC using it for creating content, plus the web thing. It was a little more cumbersome and not as tightly integrated. There were all the different pieces you needed to install on your own infrastructure. They were switching to some cloud, but you were still reliant on on-prem, on-client, on-cloud. Other than that, it was close between Tableau and Domo.

We also heard feedback that, while on the surface, if you don't look at the infrastructure and the maintenance, Tableau looks like it's less expensive, when you really add it all up, and consider the lack of ease and convenience of use, it was going to probably cost more than Domo. That was why Domo beat Tableau.

Power BI was our least favorite, and part of that was because of who demonstrated it. They called it in, they didn't come to visit us, and they didn't do a really good job demonstrating it, but it doesn't seem as integrated. There's a client side, and a publishing side, and it doesn't seem to have as appealing a user interface. Power BI was the most confusing. It just was not nearly as elegant or easy to use, and certainly didn't have the integration.

Yellowfin seems very good. It is a web-based interface. We have it on-prem but I don't know if we've switched to its cloud version yet, as a corporation. But it just wasn't nearly as intuitive to use, and it had only a handful of data connections. It just was not nearly as simple for the business to use — and we wanted the business to use it. Yellowfin just wasn't nearly as robust or easy to use, and still would have required a lot of IT support. 

With Domo's competitors, you have to go in separately, buying your own server. The drawback with Domo is it doesn't allow us to work on the UX/UI much because of the layout. You cannot go around doing a full comprehensive view with Domo. If you have seen Tableau or QlikView, they provide very good UX/UI in their products. This makes their dashboard appealing to see. Domo lacks that and was not a product created for storyboarding. It is more for analysis.

The advanced analytic charts are easy to create. If you compare it with other tools in the market, it's very easy to check your data and build charts.

The main difference between Domo and Power BI is that Domo is more geared towards a business user to do all aspects of it: To make the data connections, clean up the data, and create the cards. Whereas with Power BI, you still want to have the assistance of Microsoft training and have a little bit more of an IT background to have it make sense or become second nature, without extensive training. Domo is really set up to help a business user accomplish the same goals, almost in "layman's terms," if you will.

We looked at Power BI, but there really weren't any others that gave us the deal that we got on the amount of data we could store and the support that we needed at the time. When we made the decision, Domo was fresh into the market, and there weren't really many competitors. Looker wasn't around. QlikView was around, but they came in a little late to try to get our business. We had already made our decision.

I'm familiar with Tableau. Tableau is more evolved and has many more features than Domo does, but Domo is still evolving. At some point in time it may be in a parallel position.

One of the major differences between them is the UI look and feel. In that area, Tableau is better. In Domo, you upload the data set and then you create the job which will be NRT — near real-time. You keep on scheduling the job; you can schedule it to run every minute. But in Tableau you can have a data set cached in your system or you can have a live data set from the DB. You can directly connect it from the database.

I've used different ERPs, CRMs, and different types of analytics throughout my career, but I've never invested in anything like this before. This is "next-level."

Birst, Tableau, Crystal, Power BI, GoodData, and Qlik.

Zoho has created very advanced analytics but Domo is far better than Zoho. We looked at Cluvio and Grow. We went with Domo because it is easy to use and easy to understand.

Right now, we are trying to use Pentaho.

Domo has a lot of tools that other software, like Amazon, doesn't have.

We did. I have the most history with Business Objects, but evaluated about 30 different tools before landing on Domo and Birst. In the end, Domo was the better fit for the organization.

• Dundas Dashboard
• Telerik
• SSRS
• Tableau

Before choosing Domo we evaluated other options, including Tableau and QlikView. But the problem with Tableau was that it was very slow. It was extremely slow because of the amount of data that we are trying to push in. It was not efficient and stable.

And the problem is with Tableau and QlikView is that you would need a separate ETL tool altogether, like SQL. With Domo we don't need that. We can directly talk to any kind of data source that is available in the market. That is what separates it from the others.

Not enough comparative experience to judge it against the competition. In the initial discovery, I researched three products, Domo, Birst and one other – I can’t even remember the name. Domo was quite well presented and seemed capable of doing the job. As a user I was pretty happy with its capabilities.

Our company president wanted this product.

Domo was really the first tool we looked at because of our complicated internal systems. It turned out that they over-promised and under-delivered.

I have worked with Tableau for a couple of years. Both Domo and Tableau have their pros and cons. 

• Domo only has a cloud deployment while Tableau has on-premise.
• Domo has a complete, integrated ETL solution built-in, so it is quite powerful. That is something which is different from Tableau.
• In terms of the chart types, I would recommend Domo's charts over Tableau. Domo has charts, out-of-the-box, which are flexible and show many numbers, and it has a couple of year-on-year comparison charts, which you can directly use. With Tableau, you have to create them, which creates a lot of difficulty. So charts are something which are very good in Domo. With the sheer number of charts and visualizations, Domo scores over Tableau. 
• But in terms of user flexibility, in my opinion Tableau has the upper hand, especially because Domo does not have the window functionality. There is a little more flexibility in terms of specific formulas that can be created within Tableau. You don't need to do it in the ETL or using SQL; you can do it within a report. 

But in terms of what I have seen overall, Domo scores over Tableau.

Other options were considered, but not evaluated. I do not know what was considered, other than an in-house ColdFusion development platform.

I was not involved with the initial evaluation. We had some of the leading technologists in the field who did that, and Domo made a good impression and won the day.