Domo Reviews

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.

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.

I use it for data modeling and data structuring for my clients. An entire data set cannot be utilized for visualization. There are a few data points which can give us exact output, which clients use for their KPIs.

We try to minimize the data and extract the required data for the key performance indicators, which helps us to drive more monitoring results for our clients and to give them exact information, even in the forecasting.

The design dashboard has given us more leverage to customize things. And with the click of a button we can quickly extract the required reports and then share them to the client if the client does not have access to Domo.

It allows our clients to see data on their day-to-day business and to review things at the management level: how the business is performing, what regions are doing good numbers, which region is performing best, and where business is low. They need to find the reasons for differences in performance, whether its marketing or recruitment lapses, etc. They are able to share the insights with their counterparts and this is where the decision-making comes from.

The most valuable features are the

• ETL
• SQL.

ETL is the feature where we can do much of the data structuring, per the client's requirements. With ETL there are things a layman can understand.

SQL is the most used database system and we depend on it for the extraction of required data. However, unlike the ETL, SQL can only be understood by a tenured person who is into the details of SQL coding etc. That's the major difference between the two. Both are highly utilized at my end.

Over the time I have been using Domo, I've seen many updates pushing great features into it in new versions. Every new release has more and more insights. A major improvement was the design dashboards wherein we can customize dashboards with the KPIs that clients want to monitor on a day-to-day basis. And in a significant number of cases, we showcase monthly-review or quarterly-review data. They are quick enough that our clients can download the entire dashboard in a PPT and start their review. Others review things within Domo itself.

The forecasting feature, the regression features, and the Python libraries could all be improved. They're all in beta. It is feasible to go out and extract data from libraries and attach work to the libraries, but with the respect to initial insights, I would like to see more help from Domo. I would like more information on how to utilize those libraries.

I've been using the solution for almost two years.

New releases are communicated with a popup saying a new release will be coming through on a certain date. We definitely check the data to make sure everything went smoothly. We'll reach out to about any bugs through the active community forum. We have received the answers we need there.

I do see limitations with respect to the Domo Appstore. If a client has a specific requirement, we need to reach out to Domo and get things installed for them.

There is the Domo Community which is a live brainstorming session with Domo experts who answer any queries. I make myself available to participate in that, so that I get quick answers to my queries. If there is anything beyond that, we, as an organization, reach out to the community. We will first try solutions if someone else has had the same kinds of bugs. If they have the answers we can finish it up ourselves. Otherwise, we have a BI team that will reach out to Domo and get the insights.

Overall, I would rate their technical support at eight out of 10. 

In the first year, when I joined the organization, I was introduced to Domo. Prior to that I had experience with Tableau. When I started diving into the details of Domo, I got to know it and found it has the best GUI. And it already has an ETL tool embedded in it, for extract, transform, and load. That was not available in the other tool I used.

Traditionally, things were done with Excel, but I don't think it is quick enough to turn things around for our clients.

The setup is simple for someone who knows the system. If it's the first time doing it, the setup will be tricky. 

We go with a four-week implementation strategy, wherein we gather requirements from the clients, we have a brainstorming session to understand what kind of system they are using and what sources they are using. We'll extract and build the dashboards for them. And then we come to the documentation, where we document the details of requirements and then we deliver it, based on the timeline. This is all done within the four-week period, and we give them the standard set of cards.

From our end, for the reporting from Domo, we need just one person involved and that same person handles the day-to-day maintenance.

One of our clients, for example, sees on a monthly basis how much money they are saving, on a cumulative basis. They say a certain type of conversion was only at 40 percent and now it has increased to 65 percent.

The pricing is partnership-based for us. There are no other costs for Domo aside from the standard fees. 

It produces the best output. I'm quite satisfied with the tool.

We take the initiative, on our end, to give the client the best insights on how to use Domo. If they are sharing Domo access, we help them to understand how they can best use the tool and how they can change the chart visualizations, to make them suitable for their review and for understanding. Those are the key factors where we advise clients so that, with the click of a button, they have their own insights coming in.

The end-users at our clients include program managers, in particular, and then the top level, the executive level. Most of our clients have around five users.

The tool is very popular in the Asia-Pacific region. It's spreading its wings. Even in India, I've seen people starting to use this tool. The major advantages are its GUI and that it's in the cloud. The visualization features, with its colors, are friendly to the eye. It doesn't display information in dark colors.

I would definitely be curious to explore Domo more and more because it has features such as data scientist rules. You can apply their forecasting. I intend to explore those areas more.

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.

We currently use Domo for automation of our reports. I'm connected with a large company and I focus on talent acquisition and analytics. We are mostly pulling reports from Oracle BI, reports that are used by our talent acquisition staff. We connect our Domo database to OBI and pull the reports from there. The visualization and the rest of the analytics functions are stored in Domo.

Domo is a great help to our organization because, prior to Domo, we were using an Excel base. We were highly dependent on Excel, including manual entries and encoding of data. We were quite heavy on that. But as we shifted to Domo, most of our reports were automated and displayed real-time for our end users. It's a really great help with our business, here in the Philippines.

It saves a lot of time. Without Domo, we would need more manpower to support our reports. Before Domo, we had a report-focus which required a headcount of two and there are only two of us on this team. Eventually, most of our work time was diverted into the reports: extraction, preparation, and consolidation of all the data coming from individual Excel files. It saves a lot of time as well as cost because we don't need to hire more people to work on the reports.

What really helps us a lot with Domo is that we are able to focus on our core functions. We are heavily dependent on data collection, data gathering, and finalizing data. The clerical functions are being isolated or reduced, as we shift to Domo.

I don't have dollar numbers, but in terms of hours, we have certain reports that were being generated after four to five hours of work a day. But in Domo, we need just 30 minutes to create that report. That report is being published every day, so it really helps us a lot.

What makes me really fond of Domo is the ETL because it enables us to maximize a single platform for pulling reports and automating things. We can send the raw data from a third-party platform and do the rest of the ETL in Domo, including transforming data, adding columns, etc.

There is also a built-in viz mode which is really helpful for us. We can do computations there and, eventually, see the computation results in real-time.

We have been exploring the key functions which, for us, right now, include dashboard creation and using the Magic ETL. We are focused on them because we do a lot of stuff related to ETL. We are also doing some blending, data transformations from different data sources. It's quite helpful because we don't need to do it outside the Domo platform. Before that, prior to discovering the blend function, we used to do it in Excel first and then upload it to Domo. Since discovering that function, we just pull the raw data coming from a system and Domo does the rest of what needs to be done.

In terms of the dashboard that they have created, they can do better. If you are quite new to Domo, and you're not familiar with how to play with the buttons, the options, you might get lost.

They can further help the user by providing better customization and options. For example, for customizations, instead of displaying a dropdown, why not just have a button for selecting which filters to show? That would really help users to explore faster and understand the data better.

I'm also using Domo in mobile and it's quite impressive. However, there are no options to edit using your mobile. That's a limitation. In the future, they should consider adding the edit function in mobile.

In terms of the analytics, there is quite a limited set of options when using Domo. Whereas with Tableau we can perform heavy statistical computations, Domo doesn't have that capability. Domo is quite limited on that side. They may need to consider improving on that in the future.

But overall, what I'm seeing in the system right now is good. It really helps a lot in streamlining our processes and enables us to focus on our core function.

Domo is good, as long as you have a good internet connection. That's one of the challenges here in the Philippines, which is one of the countries with a slow internet connection. When I was working in another company with a good internet connection and bandwidth, we were able to access Domo very easily.

I would rate the scalability at 7.5 out of ten. What differentiates other business intelligence software from Domo is that with other business intelligence software you can find tutorials on YouTube. For example, you can find several tutorials for Tableau on YouTube, but for Domo, I don't believe you can find any. It's difficult to find a training module for Domo, unless you are in the Domo University.

I haven't tried contacting Domo's technical support since I joined this organization.

We were using Excel prior to Domo.

All the organization's data is really important. With data you can measure how you are performing. The challenges in using Excel were, number one, integrity. Maintaining extra spreadsheets over time is really hard. Gathering and updating the data is really hard. Second, of course, is that there is a lot of manual work in Excel, unless you have someone trained to do queries or Visual Basic macros. That can help speed up the reports, but it may take time, again, to develop queries and programming for Excel. The driver for our switch to Domo was to speed things up and be able to deliver reports on time, accurately, and more reliably when compared with Excel.

It's relatively complex to implement. 

One type of ROI is that have been able to reduce the number of staff needed to prepare certain reports. Before using Domo, I would estimate that the company needed at least four people on the team to handle just the reports for our talent acquisition team. Now, we need closer to two staff. And that's just one team.

I'm not sure about pricing, but I believe Domo is quite costly. Prior to joining this organization, I had a Domo license with my former employer and I think that license was around $500 to $600 annually. That was for a single license. I think it varies, depending on the organization that is acquiring Domo.

Domo is a great tool, in my opinion. But the first thing that you need to consider is what kind of return on investment Domo can deliver. There are a lot of things that Domo can deliver. There are a lot of things that I haven't tried yet with Domo and I'm quite excited about trying them. But in terms of the ROI, there's a really great opportunity to save cost and time with Domo, particularly for if you are heavy on reports. If your organization needs certain data or reports in real-time, reports that help you to decide on certain issues, Domo can be helpful.

For the setup, the first thing that really matters to me is the importance of the fundamentals and training for users. If a user has not been well-trained to provide technical explanations to other users who eventually join the organization, it's quite difficult to understand Domo.

When I joined this organization, they had already been using for Domo but for less than a year. In terms of the reports, they are not utilizing it fully because they don't have any dedicated person to handle it. In addition, they don't have any trained personnel here, so there's no one to set up the reports, there's no one to explore the functionality of the system. It's quite a challenging role. We have been working on overcoming those issues.

As for increased usage in the future, we have a mandate from management that we're eventually shifting everything, all the reports, into this platform, because of its usefulness. It's quite good and I think the organization supports it.

It is being used globally in our organization. We have counterparts in other regions including India, Bulgaria, and the US. Our team alone has more than ten people who handle the business analytics. We are the ones preparing our records and data in Domo for all talent acquisitions for this organization.

I would rate Domo at eight out of ten. It's really quite helpful for me to use Domo. Domo helps a lot in terms of reports and streamlining the reporting process. It helps the organization to make decisions quickly.

Our business deals with B-to-B and B-to-C customers. Our main objective is to present an analysis of our business. From our databases we generate a report and we showcase it to our upper management team, showing them the exact analysis that has been done.

Earlier, in terms of analytics and data, it was slow going. We used to manually create the reports. We didn't have any interface or way of presenting any data to the CEO or CIO of our organization. We used to pull out reports by creating them in Excel. Domo has helped us directly present data to the upper management team. We have created particular dashboards on Domo and given direct access to upper management so that they can have a look and strategize for the future. We created the dashboard once to meet the requirements. Now, automatically, as the values of the data change, the job is done. They are able to understand the current status of the business.

On a daily basis, it is saving us four hours per day. We used to spend four hours extracting the data for a report. 

We've worked with all the features of Domo. Among the most important are Pivot and Sumo Cards. We can use drill-down from the top-most level with a click, generating charts.

Apart from that, we are able to connect with MySQL; directly with the database of the internal CRM to fetch data and create reports and present it.

The user interface is quite good. 

It's quite slow. We have about 2,000,000 rows of data. Creating certain reports takes almost a couple of minutes, which should not be the case.

One of the things Domo can work on is the filters it provides. I have created many dashboards and the filters are not that user-friendly. If we have two dates, we are not able to filter it on both, it allows only one date, which is not a nice thing. If they could improve on that, it would be great.

Finally, I would like to publish a dashboard for the employees so that they can also see the performance of our organization. But that is not a feature in Domo, although it's something that Zoho provided. I would request that Domo enable us to share a particular dashboard with the employees, providing the filters with that. Domo doesn't provide anything like that. This is one of the features we want. We are not able to share our data with the employees. We don't want to share all the data. Our objective is to enable an individual to look after his performance in the organization. We are not able to do that. That's why we are stuck with only a few people using it in the upper management team of our organization.

We haven't had any downtime or crashes, it's running absolutely fine. 

The performance should be improved in terms of data fetching from the external application. When you connect it with the database it takes some time to extract the data.

We haven't had to contact technical support. We did communicate with the salespeople. They replied whenever they received our messages.

We were using Zoho. My boss said to me, "We need something that we can use to present our data." We started looking for a tool that would help us. We came up with Domo and directly started the implementation.

The setup was straightforward, easy. You have to directly connect it with the database. We have a database for our internal application and integrated directly with that database and it was good to go. That process took one to two hours.

We started by creating one report, then another report. The initial R&D I did on Domo took me between ten and 15 days, and then I moved on to creation of the reports. After that, I was able to create the dashboards in a month.

I was the only one who developed the entire dashboard in our organization. I am the entire owner of Domo.

We did not use a consultant.

Over the last year we have saved about half of the amount of the subscription. It has reduced our costs more than we expected. It has saved us manpower, money, and made things more efficient. It doesn't require ten people working on it, one person can develop and that's why I am here, to run this entire project.

Pricing was a huge factor. Domo is slightly costly but it's much cheaper than some. If possible, when we renew our subscription we will be requesting a price cut. We can get the same features from competitors. We may have to look for a new subscription.

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.

It's easy to use. There's no need for Google or videos to learn something. You can just explore it and do whatever you want and it's very easy to understand with a good interface.

We have kept the number of users to not more than 15. We have kept it confidential and not made it available to the employees. 

We are planning to increase usage of Domo. We had a lot of negotiations with the team that was helpful regarding the sharing of a particular dashboard with other people. We have a one-user subscription and we want to share this with another one so that they can at least have a look at the performance in the organization. We are planning to share Domo with the employees. We have between 300 and 500 employees. Our target is that by the next financial year we will deploy this product throughout the organization.

I've used it as a platform to bring data together and pull insights out of it. I tried to connect different sources and match them. I'd utilize Google Analytics with data from Salesforce Marketing Cloud to be able to see how email activity in campaigns was impacting user activity on the sites.

It gave us an opportunity to get a closer look at how our campaigns were performing outside of just the email itself and the landing page, to get an insight into how people were interacting with our sites. We were able to look at how successful campaigns were in converting leads. 

We did a few studies where we looked into customers' data, connecting it from all different points, whether it was phone calls or the like. We were able to match it up with what it was that was causing that customer's activity to rise or drop.

It has a really easy platform to create user-friendly data models. It allowed us to click into the data, which was nice. Even though we could step back and see the bigger picture, we could also get into the details. At one point we were merging zip code to zip code data, so we could actually go all the way down to the zip code level and see how well a campaign was performing in a given area.

It definitely gave us the opportunity to figure out where there's room for us to grow or where there was room for our clients to grow. Getting down into that zip code level, we could do a comparison between different markets and say there were a lot of customers in a given demographic whom we could target.

It also let us know which of our campaigns was more successful compared to others.

The ability to create custom connectors was useful because you never know, with customers, what platform they want to utilize or what data they have. It gave us a lot of flexibility in being able to bring data in from different places.

Workbench works well and it uses local files. I had to set up Workbench integrations and it made things so much easier. There was never a point that it was down - and it would be really easy to spot the problem, generally user issues, if there was anything wrong. It was especially helpful during migration when we were trying to get everything into Domo. It can handle a lot.

They do have a feedback feature which is really nice, but it can take a long time to get any responses on that.

It is very difficult too, if we do have specific requests or errors that we can't get figure out - especially when it comes to the development platform, developing custom connectors or doing any kind of API work, custom cards - in that there's a lag in the response time. They do eventually respond, instead of issues getting lost, and they do make those improvements. If they are small improvements they do it rather quickly. If they need a developer then it's slow.

Sometimes it takes data a long time to run, especially when you're connecting data and running SQL queries. Sometimes an error is not caught right off the bat and you have to wait a couple of hours for it to run and then you can catch the error. That part could do with some improvement.

There is coding that you can manipulate data with on the actual card in Beast Mode and that part can get a little messy. It's not something where, if five people are working on one dashboard, each person can go in and edit and make alterations. It's not very collaborative, but it does work and it does wonders when you need to work with very specific data.

It's pretty stable. There hasn't been any downtime that we've ever experienced, any issues that required us to reset or that made us lose data. 

Scalability is pretty good. I didn't have any issues with it. I was able to do a wide range of things. There's a lot of room for growth and the ability to grow on the platform.

Technical support was great. You gave them a call, they put in a ticket. 

If it was something that required a little bit more technical work then it was a lot slower. And their updates could be a little lacking. There's definitely room to grow in their responsiveness. But other than that, with small editing, small issues that didn't require too much technical work on the backend, they were very good and very responsive.

My previous company was looking to grow in business intelligence and Domo was the best option among all of them. But I wasn't there when they made those decisions.

ROI can definitely come from the predictive analysis aspect. You can take any sort of data from any platform and put it into Domo and automate it so you're not wasting time. If you have a monthly analysis or monthly reports, you can automate all of that with this platform, making those processes a lot faster and much more efficient. It also leaves little room for user error that could normally happen in Excel or the like.

It is also good if you're using it internally, especially if you work with billing, to help navigate your resources or to figure out where you can best utilize your employees, etc.

It is on the pricier end.

One thing from my experience that we could have improved was that we had a limited number of technical people on it. You definitely need to be savvy with a lot of heavy SQL as well as API integrations. if you're trying to utilize it the most, the best thing to do is utilize their development platform. They have a developers page that really does wonders and takes it to the next step. If you're investing in it, then invest in being able to utilize that.

They also have a webpage where they show a lot of examples with different data models, showing you how to utilize tools to the best of their capabilities. That is really great as well.

The UI is definitely easy to pick up. If you do have a little bit of SQL experience, it's easier to use, rather than trying your own merge capability. It has its own user interface where you can do what you would initially do with queries or Redshift. That part is pretty good. But I prefer to use Domo's SQL and Redshift capabilities that require a little bit of coding, compared to what it has in its user interface, which allows similar processes.

That being said, everything else has been really easy and very self-explanatory. They do have good documentation and they have user groups and discussion boards that provide a lot of answers to your questions.

I definitely see use of the solution growing. There's so much more that it can be used for. There's a lot of predictive analysis that it can go into, and a lot of connectors that it can work with that allow you to use more and more functionalities and help with that whole predictive analysis aspect. In my previous organization, when I was there, they were growing the team to focus on what they could do with Domo.

Overall, Domo really transformed how we worked with data. Things that would normally take three or four weeks could be set up to take a day or two, if not less. The fact that it was able to take a whole workload off and provide a lot of analysis and even further insight, in that shorter amount of time, was great.

I use Domo mostly for three reasons: 

1. To create connections with several applications and obtain data from those applications, e.g., Google Drive, Google Sheets, or Google Analytics. 
2. With those connections, I love to upload data to Domo and transform that data in different ways. I create ETLs to join the data. 
3. When I join the data, it is transformed into a card where the client can see his data in a graphical way. From this, he can understand how his company is performing, because the data which I upload is from their call center(s). 

Domo is not for fixing errors. We don't fix anything with the database. Domo is for processing data and showing the data to clients. They can see how their company is with calls, and if they are selling well or not. 

For our clients, who have call centers, it is very important. For example, they need real-time data and Domo allows them to obtain data every 15 minutes. It updates the data every 15 minutes with new issues to fix it for the moment and will detect if something is wrong, which is for the client, as they need to ensure their data is okay and everything is working. The client needs to know if their reps are working well and selling their products.

Domo has a lot of connections using APIs where you can use data from different databases, such as NoSQLs, SQL databases, and other connections. These connections exist to obtain data and transform whatever that you want. This is valuable because I work with Postgres.

You can also create two types of ETL: 

1. A graphical ETL.
2. It can be used cold with MySQL and transformed into whatever you want with the code.

It is pretty amazing; the things that you can do with this product.

If your ETL runs more than 24 hours, it always fails because we are logging a lot of historical data, and there is a restriction on the amount of data (in rows) that you can run. The technical support has not found a solution for this yet. Their recommendation is just to run less data, which does not work for us.

I would like the real-time reporting to decrease the range of output from every 15 minutes to every five minutes.

They could add create a card in a timeline to see how calls are going. Domo has a lot of features, but it does not have a timeline.

The stability is pretty good. We have not had a problem with losing data.

There is an issue with Domo's storage because there is a limit with it. In five years, the storage requirements for Domo will not work for companies.

We currently have 50 people using the solution, though we have only about ten full access accounts. The rest of the accounts are preview only versions.

If you have an issue with Domo, their response is less than an hour. Their support contacts you immediately when you send an email for an issue on a database or data set. Then, they follow their process and will always try to solve the problem in less than 48 hours.

We previously had a homegrown application that we used. We switched applications because of iOS limitations. 

Domo was already installed and configured when I started.

It's pretty simple to configure within a database and with another IP, like Google. It provides a step-by-step explanation of how to do something using stickers in the questions. Clicking on the sticker, it tells you more information about what you need to to do to configure something, which is pretty simple. It takes a minute to a minute and a half to set up.

We implemented in-house. 

It takes one person to create the configuration and the data sets to upload the data, then three or four more to create the cards. The cards will be where you will need more time to transform the information, because you need to know what clients need to create the card like the client wants or what they want to see in the card. Therefore, it needs around five to ten people working on the deployment, then maintaining the solution.

When implementing, you need to know what the client really needs and what do you want to create in Domo. 

We are making money from Domo, and all our clients are happy with the information that they receive from it. We have seen our customer base grow due to the product's usage.

Right now, we are trying to use Pentaho.

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

Domo is a good tool, and you won't regret it if you chose it for your company, since it is a very useful tool if you want to check your data constantly and historically. You can compare and create graphics to compare the past with the present and estimate to see how your company is performing. 

Right now, the data is the most important thing in the world. Domo always tries to keep your data protected and available to you and your clients. This is something which  good with Domo. 

As our company increases in size, our usage of Domo will increase.

We use Datadog in conjunction with Domo, but they are two separate tools: Datadog is used for checking issues in the databases and Domo is used for uploading data from the databases. E.g., Datadog will inform you what is going on every second in the databases. It provides information if something is wrong or if one of the processes hasn't finished.