Domo Reviews

I use Domo BI as a back-end business API to build a bot. We are not currently using the entire Domo system. It's an external API for us. We are building another layer on top of it and not interacting with Domo itself that much. Our client is a Fortune 500 company that is actually using it. We were provided with read access to build a product on top of it.

Other than the SDK, it is a basic tool where you can create cards and charts. I mostly see it as an ETL which has many system connectors. It does a good job of ETL. 

I also use some of the visualizations but they are pretty standard across the industry. There is not much difference between Domo or Power BI or Qlik. All of them provide the same types of charts.

The basic analytics are okay. They show some information on what's happening with the system.

Their SDK is not up to date and you can't access it on their website. They have a private SDK to access resources in Domo. I'm not sure why. We were shocked to find out that they have an SDK but it is not available worldwide.

They have come out with the Domo Store but I have yet to explore it thoroughly. I checked the store but I couldn't find some of the apps, so I had to make my own.

Amazon has come out with QuickSight and there is Tableau which has a desktop version, and that is something Domo doesn't have as of now. Qlik also has a desktop version. There are other aspects that Domo has to work on.

I would like to be able to drill down more when there is a particular area where there is a problem. I don't clearly see that in Domo at the moment.

It's pretty stable. With the APIs, I haven't encountered major issues with Domo.

We contacted technical support at Domo. We talked with the engineering team there regarding the SDK. They said that they only have a Java SDK right now. They said they're trying to build more. I believe they might come out with something in the third quarter of 2019.

Communicating with them was fine.

Implementing Domo depends on the project, how much time it will take to build the dashboards, how many KPIs you are looking at, and how much of your data will come into the system. It also matters how many data sources there are. If you have ten to 15 sources every time it is a lot of work because you need to join all those tables and combine them into one to build the dashboards on top of it.

There is a difference between working with Domo and working on top of Domo. The major difference is that if you are working with Domo, you would rather use ETL and work with connectors; build the database and then dashboards for internal systems, sales, HR, marketing, and the website. That is working with Domo. But working outside of Domo, you just the APIs to push the data or the dashboard data, and you work on it on top of it.

In our organization, I am the one who works with Domo the most. Our organization is pretty small. We are a startup still. For startups, there is no discount. There is a trial version but that is only for 30 days. If you want to use a basic system, go with AWS QuickSight because it is available with pay-as-you-go and it is way less, in comparison, because it is new in the market.

I would rate Domo at six out of ten. I'm not in love with Domo. I have some issues with it. In my opinion, it is not that secure. I feel it is exposed a little. I also feel the ETL is a little outdated. They're not up to the mark on updating and don't have support for multiple languages. For example, they only support for Java right now. They don't even support Python or .NET.

On reflection, one of Domo’s strongest qualities was that the end result was extremely accessible to non-computer-literate users. It’s therefore particularly suitable for larger scale roll-outs across companies where the skill level of the end users is very varied.

No – It was implemented at the behest of the CEO who left the company during the implementation and there was little interest in BI in any form elsewhere in the company.

This is a difficult question to answer because the biggest shortfall for me was data management, but that would probably not be an issue for many people. I used a mix of on-premise data sourced mainly from SQL Server, with some from Excel; and cloud based data from SalesForce and NetSuite. The biggest issue I had with Domo was that I could not effectively combine data from different sources into a single dashboard. Ultimately I got round the problem by acquiring linked servers for both SalesForce and NetSuite so I simply sucked in the data I needed from both into SQL Server and built my combined data sources there.

After working for half a year with Tableau, I’d say one of Domo’s biggest weaknesses is the inability to display multiple charts simultaneously. Their mapping capabilities are also very unsophisticated.

I used the product for nine months, from January to September 2014, and I don't know the version number I was using.

No issues encountered.

Not really. Since everything is cloud based, we were entirely dependent on their servers and I learned not to try to work on certain types of views in the afternoons. Their servers simply couldn’t handle it. As this dates back to last year, it may no longer be a limitation.

No issues encountered.

After initial implementation, we were entirely dependent on the quality of the CSM, and we were not fortunate in that respect.

Very mixed. Our initial implementation manager was absolutely first class in every way, but once we were up and running and were handed off from him, I found technical support very difficult to get anything out of by email or by using DomoTalk. When I had an urgent problem, I short-circuited their system and just picked up the phone. When I did that, I usually managed to get hold of a real person quickly and they tended to be pretty good. I also stayed in touch with our initial implementation manager to some extent.

I’d say that – at least as of late last year – Domo were way under-resourced but the resources they had tended to be at least good, ranging to excellent.

This was our first foray into BI tools.

We were vastly over-sold. Domo was sold as an easy-to-implement-yourself product, but this is completely unrealistic.To be fair, I know that their approach has changed since then, and they now recognize the need for a proper implementation resource, whether internal or external.

I did it in-house with support from their implementation manager.

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.

Expect to invest in a proper implementation.

Our primary use case for the solution is creating operational reporting to help us make decisions that go live executive dashboard. We deploy the solution on cloud.

We find the ease of using the solution valuable.

The price of the solution can be improved.

We have been using the solution for three years.

The solution is stable.

The solution is scalable, and 40 users are currently utilizing the solution in our organization.

The customer service and support team is responsive. They answer our questions once we submit tickets. I rate them an eight out of ten.

Positive

I was not involved in the initial setup.

The solution has a standard license with some embedding. It is expensive so I rate it as three out of ten.

I rate the solution a seven out of ten. The solution is good, but the price can be improved.

Once the data source has been uploaded to Domo, making graphs is quite easy. The data/graph is also displayed without any wait and we can change filters very easily on our view.

We have been able to create countless KPI metrics, so now we have hundreds of DOMO cards that display different KPIs.

• Improve help resources
• Descriptive error messages should be displayed
• Domo should enable users to sort cards on any given page
• It is geared mainly towards SalesForce –especially the out of box apps. Before offering apps to customers, Domo team should be careful of how the data in ERP’s other than SalesForce will map with the code for their apps
• The site is cluttered with hundreds of KPIs which make navigation difficult and is confusing to the eye

I've used if for about six months.

We initially tried using the SQL connector but it did not work out well. We had to go with the workbench too which is probably the best way to upload data sources.

Overall it’s a stable product.

No issues encountered.

It's good - the customer service teams are friendly and responsive.

It's good.

We used SSRS reports. The company president wanted a better data intelligence platform with a more sleek design and better user experience.

The initial set up was pretty straightforward after we were told that it’s best to use the Domo workbench instead of the SQL connector. The SQL connector did not work at all.

I am the one who implemented Domo at my company. I installed Domo workbench, learned to upload data, created data sources and graphs in a short time. I viewed the educational videos and also was given some basic demos by the Domo team.

Our company president wanted this product.

This is a good product for giving an overall picture of the business. Not a good idea to use it if you are looking for minute details in your reports or if your end users like to play with data in excel. Overall it is a useful tool but I don't think our company is using it the way it is supposed to be used.

In the end nothing, but upfront, we were very intrigued by the ability to get four to six complicated reporting tools into one aggregated dashboard.

Unfortunately, no. We never were able to make it work. We were initially promised a one month setup with the four tools of our choice. It took them two months to setup Google Analytics alone, and that merely replicated what we could do.

• Ease of use for clients
• The ability to live up to the promises of its sales staff

We worked with Domo for one year. At no point would I define it as a "solution."

Absolutely. We never were able to get all promised channels plugged into the system.

No issues with stability.

Significantly. When we signed our initial agreement, they told us that we could use it.

They were very responsive, but never actually were able to help us.

I dealt very little with the technical team. However, they were constantly behind on our initial setup.

We had multiple complex internal systems providing our reports. We wanted to get all of our reporting into one place. This turned out not to be feasible.

It was highly complex. They had to connect to the APIs of various systems which was beyond the ability of a layperson to do. Clearly, it was complex for their team given that we only got two of our four promised systems implemented over more than six months. And those took more than two months each.

We worked with the vendor on implementation. We were constantly told that the development team was behind on getting even simple tools like Google Analytics and Omniture implemented. I do not know how much this is a reflection on their entire team, or maybe just specific to our account rep.

It was zero. We paid for a year's contract and made no money from its use.

I can't be specific, but it was well into five figures. It also took up a significant portion of my time, which I value as well.

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've dealt with worse companies that take the money and run. Domo continued to stay involved, it just never got to where they said we were going. The tool has some potential, but - as of two years ago - it was still a long way from fulfilling on the promise.

If you have a very simple implementation and a competent account rep, Domo might work for you - although I think it's an overpriced option to handle that. For our purposes, it proved much more feasible to have an Analytics/JavaScript guru customize GA & Omniture to get multiple data points into the same system.

We use this solution for Advanced Marketing Performance Data for a $3B in revenue cloud-company.

This solution allows us to change our performance metrics and tracks our goals in real-time.

The most valuable features are merging datasets, getting quick visualizations, and creating PowerPoint presentations instantly.

I would like to see more dashboard creation options.

I have a few sample datasets that I have uploaded to try out different use cases. Domo has an integrated ETL so I'm trying out its ETL solution.

One feature which I have found to be very interesting is the Beast manager, where you can create calculated fields. They are shared in one common repository so someone else can use the same calculated fields; they don't have to rewrite or reinvent the APIs. They can take them from the common repository of Beast Mode. That is quite an interesting feature.

It's too early for me to say that something needs improvement, but there are times when there have been some flexibility issues with Domo. Maybe I still need to explore more, but we don't have any window functionality in Domo. Tableau has a window function which can be integrated into a calculated field. That is missing in Domo so you have to make changes to the data set using ETL or SQL. Only then you can bring it into the report. The window functionality that is missing is something that Domo can work on.

I'm trying out Domo as a PoC for our company. I have been using it for about three weeks to a month.

It's too early to tell about scalability because I have not worked on huge data sets as of yet. I've heard there are certain apps that you bring in, if you have millions of records, to get them into the cloud. But I have not tried that out myself.

The setup of Domo was straightforward. Their online resources are quite extensive, which was something I wasn't expecting. They have a Knowledge Base and a lot of online learning materials.

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.

It's too early for me to comment in detail because there may be some functions which I have not explored yet, especially in terms of windows and fixing a formula. LODs and windows are one thing, but I'm not sure if there are other functionalities which I have yet to come across.

But if you are looking for a very quick solution, and if you also want some ETL activities — if you don't have a dedicated ETL team — definitely go for Domo, rather than Tableau. Domo gives you that ETL advantage. Also, in terms of mobile usage and visualizations, Domo has an advantage. If you already have a dedicated ETL team and you want to go into specific reports and some customization of reports, Tableau would be the choice.

If I had to choose something of value, I suppose I would have to say it's the ease of making graphs. The problem is that I rarely use graphs.

I don't see that it has. I think it has only complicated things. Perhaps it will get smoother as we set things up to rely on them, but I'm a little nervous about that.

All of it.  Sometimes it doesn't calculate correctly, it runs slowly, and doesn't offer a solution to things I'm used to doing. An example of something I'm used to doing that Domo doesn't, is fixing data. When you upload data to Domo, you have three options: 

1. Overwrite everything in the table
2. Append
3. Create a new table

We can't append the data and update a record (most efficient and accurate). My work around has been to overwrite everything in the table, but my query is limiting it to a 35 day viewing period. I then plan on making a new table to keep data older than 35 days in, and recreate all the cards for that data. Any corrections passed the 35 days will just stay as bad data. To be clear, I do not like this, but it appears to be my only work around at this time.

I have been using Domo for about two months.  I have been told that we have a beta version, but cannot locate any version numbers.

The only issue I seem to encounter that has to do with deployment is that Domo sometimes doesn't calculate correctly (Beast Mode calculations).

It seems to be mostly stable. I have run into a few problems with the workbench not updating as scheduled, but I think it has only given me two errors which were resolved by refreshing the page.

We used MS Excel and web based reporting (PHP and JAVA). We were looking to streamline our reports by making them all web based and using only one platform, ColdFusion. We chose Domo to cut the cost and time of development.

I think it was pretty straight forward. When I got stuck, I was able to find some documentation. The hardest part was knowing what the tools are called for the tasks I was trying to perform (Workbench, Beast Mode, DataFusion, etc.).

I believe we implemented through a vendor, but I was not involved. I do not know what level of support we received.

I don't know the exact numbers, but I keep hearing that it is expensive

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

It's not for everyone and it doesn't do everything. It's flashy and mostly useful if you are wanting to analyze one metric at a time, leaving you with several cards of all the metrics you are wanting to look at.
Example: Just to look at Pay vs. Login (PVL), I have to use 5 cards.

1. Productive PVL
2.  Pay vs Login (actual PVL)
3. Phone productive hours
4. and 5 Show me errors

I can't just look at all the data at once, use conditional formatting to highlight things of interest, and sort/filter to drill down to what I really want to look at. Nor can I quickly drop a formula to answer immediate questions. If, for example, I wanted to do a head count with certain criteria (hours worked, PVL%, etc.), I would then have to make another card for each count and criteria. I can't see it all in one shot to tell the complete story at a glance.