Domo Reviews

We wanted to bring our data reporting from several different marketing vendors into one avenue, along with onsite company data, to create one customer-facing dashboard. It all falls under that, when it comes to the day-to-day reporting that I've been doing. It includes anything that we did on Excel and could convert over to a dashboard.

I was doing data transformation manually, on my own, for my reports. We were very Excel-based and updating formulas constantly. It helped by only having to build it and set it once. It has helped with productivity and efficiency. I would estimate it's saving me 10 to 15 hours a week.

It's also helped with pushing and sharing information among the team members, physically in the office and outside of the office, across the country. We're getting real-time data. We can refresh reports and not have to wait however long it would have taken. That has been an improvement and results in business decisions being made more efficiently and more accurately, based on accurate information.

The data transformation, the Magic ETL; the whole data cleanup side, where you're able to bring in all of your different sources and clean them up one time and then use that same data flow multiple times over. That's a valuable set of features.

Among the recent changes they've made, the data certification feature, where the admin user can put a certified stamp on a data source so that other users can know that that is the correct and accurate data flow or data source to use, is a good feature.

Also, the data policy permissions, where an admin can decide, based on that data set, who is able to access that data set without having to pull too many strings. That is also helpful. It gives a sense of greater security in what you're sending out and that it is only getting to the people who need it.

I would like to see more flexibility in their pricing structure. The trend is moving from database pricing to a user-license pricing model. That would be a benefit if they wanted to reevaluate their pricing structure. But as far as the actual functionality of what it does goes, I don't really see any improvements needed.

We've been using Domo for about two years.

The stability has been good, in my experience.

The scalability is also good. I think it lends itself well to a small business and can go as big as you want to go. There's scalability to connect to all of their applications and connectors. There is the ability to create custom API connections. The amount of data that can be pulled in is really unlimited. It lends itself well to the big guy and the little guy.

We're working on plans to increase our usage of Domo. As a company, we also have Microsoft Power BI. I'm working through trying to accommodate the two. I lean towards Domo but others are leaning towards Power BI. It's a conversation that's being had.

Domo's tech support is very responsive, very clear, and straightforward. If I had to rank it one through 10, I'd give it a 10.

The only other solution we have had is Microsoft Power BI.

The initial setup was very straightforward. Their team was very helpful in walking us through it and training us. They were willing to come onsite to assist. But the documentation available through their website is very user-friendly, straightforward, and geared towards someone who is a business user and not necessarily an IT-type person. I'm a businessperson and I found it pretty straightforward.

Aside from some structural changes that we've had, it was about a six-month process, but it really depends on what you want to get done. It's a matter of what you consider to be "fully deployed," because I'm still doing things now, years later. So it depends on the scope of the project that you want to implement. We were doing several things at one time so it was a larger project. But if you just want to connect things from one service over to another, I don't even think you need an implementation team for that. It's something that can really be done by business users on their own.

We had a few projects on the table that we wanted to get up and running from the get-go. Because we had a couple of structural changes in our company at the time, my timeline probably isn't reflective of Domo. It definitely didn't have anything to do with them. It was more on our side, so it took a little bit longer.

From our side, it was mainly me involved, and I got some help on a few small things. But it only took me to get it done. On their side, there were four team members assisting.

I'm the only one who deals with maintaining it. The maintenance depends on how much you want to put in there. I could sit here and create new cards all day if I wanted to, but it's pretty straightforward. I set up all of the connections. The only time I have to go in there and modify something is if I think of a new way that I want to display it. It's very easy for one person to be the main admin and set up and monitor everything.

Aside from saving my own sanity, we're working on what the ROI is. I'm trying to equate a dollar amount for the ROI. I'm looking at the marketing information right now. Showing people the value of all the marketing efforts that we're putting forward will be where we see our return on investment.

We have a yearly contract and then we pay, as needed, if we need to add more seats. For about 100 users our cost is $95,800. There are additional costs if you want to have Professional Services hours. If you're going to do a data-shift or implement dashboards, you pay a one-time fee for additional hours to get you set up and running.

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.

Go all-in with it and really let Domo take over and fill it out for you. Don't hesitate. You may think it's a challenge or it's a lot of work to get it implemented. Don't sit on it, don't hesitate. Let them do the work with their implementation services. Ultimately, if you want, they can do everything for you. Get everything upfront.

In my department, Domo is used daily. I represent a small portion of the larger company and we haven't extended outside of our department yet. We're still flushing everything through us.

I rate Domo a 10 out of 10 because of the ease of use and the way that it's geared towards users such as myself. It's not really steeped in IT lingo.

Our primary use case is to use it to show all of the analytics for our retail stores and allow the managers to see their store numbers and compare them to the other stores.

And for employee performance, employees can compare themselves to the rest of the country. That was probably my biggest application of it and it's an interesting use case because we manage all of the data in the backend. We are able to get the users to see a very static view of how they are doing compared to the top ten percent of their region, their state, and the top ten in the country. It creates a pretty cool way for employees and store managers to compete, in a healthy way, with the rest of the stores.

The best improvement is the data availability. For an organization that has over 12,000 users, having data on the cloud for anyone, anytime, to see their live stats is really different. We didn't have that before. That completely changed the way we look at how a store performs and how employees perform.

We had limited visibility into the data previously so I can't tell you that we have seen huge improvements from the data standpoint. But the company really started to focus on performance metrics and, over time, we saw people improve their performance from the time that we got Domo and onward for the next two years. When people started to adopt it, we started to see performance increases, especially in the stores that were more focused on it.

The best thing is that the data storage is pretty much free. I can store as much data as I want, from different sources.

The ETL tools they have in Redshift are pretty awesome. They also have them in MySQL, but I find it really easy to gather data from AWS and work with Redshift all the way through the process. I can work in Redshift to get the data from AWS and work in Redshift, in Domo, to create Transforms and the data structure we need for the remainder of the users.

They could use more charts. They have had a very limited number of charts we can use. I believe, now, there are somewhere around 30 of them, but they could definitely use some more options.

I would also like to see improvements to their drag and drop Magic ETL tool. You can drag and drop your ETL tool, but it doesn't really work for a large amount of data. It struggles with that. In a real-world application, where you're working with 30 million rows or 100 million rows, it takes a bit longer to process the data. If you do it in the Redshift ETL tool, using your own code, it's much faster.

The stability is great. We have been down for maybe a few hours, once or twice, over the four years I've worked with them.

Most of the issues we had were on our side, with our data, rather than with them. That's why I was actually surprised to read other reviews that said that they were having trouble with loading the data or updating the data. I think that may be because of the way they implemented it because I've never had any issues with that.

I have worked with such large businesses with Domo that I think it could scale to any size. We have 12,000 users across the country, 600 stores, and hundreds of gigs of data.

The majority of the users are just looking at their numbers. They're not really doing much analysis or creating their own charts. But about 600 to 1,000 of the users are corporate users who make tables or their own charts or create their own metrics. But most of that runs through me, if they needed data changes.

I'm not sure there's much need for us to grow into it. We have adopted it close to 100 percent of the time. All of our company employees are on it.

I have to give tech support a really good score. They've been great with me. If I have a question, I call them and they answer the phone. They are able to walk me through from the most minimal thing. If I need help with something really complex, something I developed which is customized, they still give me a hand. But ultimately, whatever you build is on you.

I have had to escalate a few things, mostly because I wanted to get them done faster or there was a problem I didn't understand. I just go to my sales rep and he gets it taken care of. He gets someone to call me right away.

We had a custom tool. It was proprietary and it wasn't that great. It was mostly scraping the data and pasting into an Excel-style sheet in the website. I wouldn't say it was a business intelligence tool at all. Rather, it just showed you flat numbers for reports.

The CEO brought Domo in. He saw that we were growing and he thought it was an interesting tool. He showed it to us, we sampled it. We used it for a few demos and we decided to go with it because there wasn't anything else that gave you the cloud space without charging you for it. They're really good about that. You can take up as much space as you want for data and they don't charge you for it.

We needed something more versatile than what we had and something that was managed on the cloud that we didn't have to touch too much. They were able to provide that for us.

The initial setup really depends on your native structure and what you have built previously. If you already have a really good understanding of your data setup, and you have flattened your data a bit for it to be absorbed by any other tool, it's going to be really straightforward, really easy. Users are going to be able to take advantage of it really quickly. 

If you have to go through the process of flattening out all the data and getting everything correct, the prep work could take a couple of months. They do provide a lot of help from their side, if you have questions or for getting the data in. They provide a lot of hands-on from their team. That was good.

For our deployment, to get it out to the 12,000 users, it took about three to four months.

We didn't have an implementation strategy at first. About a month into it, we got a new CIO and he implemented a strategy for us to get it done. A lot of it was guided, before that, by our CEO. He wasn't necessarily great in that area; he was more of a finance guy. Domo also helped a lot, getting us onboard and running as soon as possible.

It was hands-on for me. I had to do a lot of collecting of ideas and what they actually needed. I had to do a little bit of the project management myself, as well. I had to do some pulling of strings everywhere to collect everything that they really needed so we could translate it to what the user needed to see. Half the time I was developing, the other half I was chasing down what exactly was needed.

I was the main developer. We used Big Squid Consulting as extra resources, but I guided most of the actual developmental work.

The Big Squid guys are really good. They provided two consultants and I was able to offload a lot of the work, where I needed help. They took care of a lot of code that, otherwise, I wouldn't have been able to put my hands on as fast.

The deployment was done by the three of us. I worked on it 40 hours a week for three months, and we had each of the other two guys for about five to ten hours a week.

We have seen ROI on the retail side. It brought an openness to the associates who are trying to sell at the storefront. It made them compete a bit harder, being able to see what their commissions were on the fly, live. That really returned most of the investment. I would say within six months of having it implemented it returned its full value.

Domo is expensive compared to some of its competitors but it is well worth it, mostly because the competitors either want you to store the data yourself, or they have similar pricing that isn't really worth it when you compare some of the features that Domo gives you.

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.

Don't complicate it. At first we thought it was going to be a lot more complicated. It just wasn't. Knowing that, next time, would help me a lot, instead of trying to plan so much for every detail. It was a lot easier than I expected and we spent a lot of time testing stuff and figuring out if the tool was updating. If we had trusted what they were saying, we would have finished a lot faster.

If you don't have a lot of data changing, if your structures are not changing - some companies keep changing the way they structure their data and that will take a lot of time - maintenance isn't that bad. I spend about ten hours a week on maintenance of the solution, and we are running a really big implementation. It's mostly answering user questions. There haven't really been any problems. I am able to work on that and on other projects at the same time. I am able to maintain it with very minimal work.

Overall, I'd give it an eight out ten. From easy usability to documentation to pricing, it's pretty much all there.

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.