My job is to build dashboards from scratch to end, from data integration and data modeling, using Magic ETL for data transformations, and creating cards by using data analyzer, and building cards using multiple cards such as charts, line charts, multi-line charts, and bar charts. My job combines everything from scratch to end for implementing securities such as row-level securities, PDP (Personalized Data Permissions), and giving access to end users, managers, or stakeholders. This is the end-to-end process which I have done for my clients.

I have worked on multiple BI tools, including Domo, Power BI, and Smartsheet. When it comes to Domo, we have one platform for data integration as well as for data modeling, transformations, and creating visualizations such as charts, graphs, and cards, which is beneficial because in Power BI we have multiple modules for these functions. Inside Domo, we don't have too many modules for creating visualizations, which I have noticed while using it. When it comes to sharing reports or dashboards, with Domo, we can customize dashboards as per the requirement and share them with other stakeholders.

These are the advantages because it saves our time. In Power BI, if we want to build a dashboard, we have to go to another site, log in, and create the dashboard. In Domo itself, we can build the dashboard, and if someone wants to change something on the dashboard, they can simply log into Domo, make changes, and pass the information to the required person. In Power BI, it takes more time because we need to log in, change information on the report, and share it again.

I have mostly used data table, bar chart, and line chart features, as these are the ones I have used in most cases.

When using a data table, if I want to visualize or get more data onto the dashboard with a large number of columns, using a bar chart or line chart can make the dashboard look clumsy. I have used a data table because it gives the complete information of required columns, such as sales or expenses.

To optimize the report or dashboard, I have used methods to limit the cards and data sets. If we have unwanted data in our data set as raw data, we need to cleanse and structure it first. I have limited the data as per the requirement because having excessive data in Domo will increase loading time and occupy large amounts of space. By limiting the data and cards on the dashboard, it optimizes the dashboard and improves performance.

Since I haven't used AI in Domo while using it, I need to improve my skills in AI and integrate AI knowledge into Domo, which I think will save time and give accurate data.

AI as a feature can be improved or enhanced in Domo.

Currently I'm not working with Domo, but I have two years of experience using it.

I have faced some challenges because previously I was working on Power BI. When I switched companies and started using Domo, transforming knowledge from Power BI to Domo came with difficulties. I overcame these hurdles and gained knowledge through my colleagues, Domo University, and Domo Palooza by learning from articles.

The implementation part involves logging in with credentials into Domo.

For other organizations, they have to get trained. If someone is working on another tool, they need to learn how Domo works, what Magic ETL is, how to drag the data onto the integration part, and learn about the data sources. Training is essential because without it, they might face issues that could lead to escalations. Getting training and support from colleagues is important to gain experience on Domo.

The admin team and manager take care of licensing, but I do not have any information about the prices of the license.

I have used Domo University and Domo Palooza for learning. I don't have access to the mobile version as only managers have access. I am currently working as a Power BI developer with Aregano Technologies. I have four years of experience in BI and would categorize myself as a freelancer or consultant. My review rating for Domo is 9 out of 10.

I use Domo for multiple projects. I have created various projects in Domo directly through their website. Currently, I'm working for Movid Technology in India. We have created multiple projects in Domo. The major part is invoicing, and we have BT reports, incorporating sales reports. Overall, we are working in telephonic domains.

My favorite feature in Domo is Beast Mode, and we have Insights. When asking insights on the right side of the dashboard, we create insights. If I ask questions in segments, they provide more information regarding the dashboard and data set.

The main agenda of working in Domo involves sales and developing.

The downsides of Domo are that we don't have a feature in the same column. When data comes in a time format, text format, and number format, we cannot segregate and create conditional formatting in that column. If in the future they develop this feature, it will benefit more users.

Domo requires maintenance on my end, such as updates. I am maintaining some dashboards on a weekly basis and monthly basis daily reports. Because we need to upload in SFTP, we cannot schedule or auto-schedule due to rate purposes. We manually handle the data sets. If there were an option to reduce the cost, it would be easier to access.

I have been using Domo in my career for the last three years.

Regarding stability, sometimes the Domo server goes down. I experienced this last week. The server was down for one or two hours, from midnight 2:30 to around 4:30. During that time, we faced issues from the project side as Domo was not visible in our portal. I could not reach out to the Domo team at that time. We had to wait until 5:00, when it automatically resolved.

The server capacity is currently good, but there are limitations. We can only access limited data sizes. When fetching files larger than 100 MB from SFTP or any other portal, Domo becomes slow due to the heavy file size. This area needs improvement.

I have contacted their customer support two times. In one instance, we discussed the issue of having time format, text format, and percentage in the same column format that needed segregation. They mentioned they would develop that facility in the future. Support-wise, they are good.

As alternatives, I work with Tableau and Power BI. I have created multiple dashboards. Domo is better to use as it offers more scheduling options on its platform.

The initial deployment cost in Domo is higher compared to Power BI or Tableau. That's one difficult aspect of Domo. Otherwise, it is very good.

The initial deployment was very easy for me when I started working with Domo three years ago. Though I was new to the Domo platform, I knew some SQL coding basics, so I could easily access ETL and Beast Mode. I learned quickly in a short period of 20 days.

The pricing of Domo is too high. Six months ago, Domo increased their prices. We suffered because we could not maintain the old data in the old data set in Domo. We are creating multiple backups on our server and showing only six-month data because of the cost. They quoted approximately one dollar per KB.

I am working in a good company as a customer and user of Domo, without any partnerships. We have two professional consultants working with us.

Domo can contact me regarding this review through their community platform, where I directly chat and sort out issues. Many people are active in community chats, and I search for details there when needed.

On a scale of 1-10, I rate Domo an 8.

I have used Domo at various organizations. I was a very early adopter of Domo at one of my early organizations when Domo was still in stealth mode as a startup. It has progressed since then, and I worked closely with the Domo team to help build different product capabilities before bringing it into other organizations.

Currently, I use it for my own small business to perform general analytics. I also implement embedded pipelines where I use machine learning and AI to understand consumer intent and action.

The flexibility and usability are probably the best features. I really appreciate what they're doing now with workflow and AI agents, allowing users to build that kind of agentic flow where data analytics and traditional ETL can quickly and easily embed AI capabilities, which is extremely powerful.

As a cloud-hosted platform, scale is not an issue aside from cost, which relates to credit consumption. Scaling is Domo's concern, not mine. I've never had an issue with scaling it, and I've scaled it rapidly in multiple organizations. The only concern has always been the budget and licensing tier.

There's room for improvement in their focus on enterprise clients. As a small business owner, there's nothing as powerful as Domo available for smaller organizations. I understand it's a business focus for them as they're looking to expand in that direction, but there's an opportunity to capture the SMB market by creating more capabilities. It's not necessarily about technical capabilities, but rather pricing that's geared towards the small business market.

Capability-wise, it's very robust. If I had to stretch, I would suggest more integrations to other common tools, such as Zapier and operational tools like Mailchimp, where you can build and extend ETL in a no-code environment. While there are capabilities you can build from Domo's open APIs, having more native integrations in a no-code, low-code environment would be beneficial. Domo has many native integrations, but better tools for the SMB operational pipeline would be valuable.

I have been using Domo for about 10 years, maybe longer.

Every platform has some issues. I've experienced outages, though they are few and far between and are usually dealt with quickly. As new features get released, there can be some quirkiness and bugs. Depending on the scope and scale, some issues get addressed quickly, while others may require workarounds, but in terms of overall stability of the platform, it's very stable.

It's very easy to get technical support from Domo. They make it readily available with chat functionality right within the platform. Even on a lower tier, you get technical support, though response time differs based on the tier. Getting technical support is straightforward - you can chat within the Domo platform when you're stuck, and someone will reply. On a freemium tier, responses might take an hour, two hours, or next day, but support always responds.

Premium support, which I've had in the past, has been excellent. I would rate their support as eight or nine out of ten.

I have used almost all the tools available. I worked at Siebel Systems with their product Enquire, which Siebel Systems bought before Oracle acquired Siebel, becoming what is now OBIEE. I'm familiar with Google's tools, Google BigTable, and Tableau. I've been in the BI space my entire career for 20 plus years.

What differentiates Domo is that it goes beyond analytics, though they don't market themselves that way. They are essentially a development platform - a data and AI and analytics development platform that is robust in terms of what you can build. Whether it's Looker, Oracle Analytics, MicroStrategy, or any other dozen tools, they're hyper-focused on business analytics, and customization becomes more narrow compared to Domo's powerful capabilities.

The setup is very simple with a completely service-based model. It's very easy to use, starting from uploading Excel files or simple data files to begin analytics and then building in capabilities.

When I ran data strategy for Rakuten, which was early on when I was working with Domo during their stealth mode, I scaled Domo from no user base to 50% of the organization, over 6,000 users, in a year. This was accomplished by creating a governed area for corporate data, and Domo's structure allows business users to perform their own analytics without needing BI teams and dedicated analytics teams. This results in a low barrier for rapid adoption.

It depends on how maintenance is defined. From an infrastructure and operational perspective, it requires minimal maintenance. However, from a data pipeline, data quality, and data governance perspective, maintenance is necessary. Any system pulling data requires some level of maintenance, whether it involves systems of record, data expansion and retention, or user governance.

The pricing structure isn't straightforward and depends on the type of organization. In my small business, I was grandfathered into their freemium model, which they've since phased out. On an enterprise scale, I've had licenses ranging from tens of thousands to hundreds for my small business, each with different constraints and objectives.

Domo has moved to a consumption pricing model, which can be both advantageous and challenging. For long-time users, it can become expensive, but the trade-off is access to the entire platform instead of licensing different components separately. The consumption basis requires discipline but provides more access and freedom. While this pricing model allows exploration of Domo's product features, it can become costly if you only use one or two product features, requiring some re-education.

I'm a strong advocate for Domo. I never give anybody a perfect score, but I rate them a solid 8.5 out of 10.

We are using Domo from the product aspect, and whatever dashboards and things we have built on Domo, we have actually achieved business improvement. Our team has obtained the ROI. I'm not sure if it is helpful for other teams or not because eventually, it's not about the feature, it's about how you actually use it, what questions you are asking, and what matrices you are plotting.

Domo is a visualization tool used to build dashboards and share them across teams. We don't need to share manually as we can give access and all team members can review the dashboard and examine the matrices. We can schedule reports from Domo, enabling team members to receive updates about changes from the past day or month, depending on the frequency settings.

What I appreciate most about Domo is that it's the simplest visualization tool, not complex at all. These tools are majorly used by BI teams and data analysts who are proficient in SQL. The majority of calculations performed on Domo are SQL-based, making it easier for teams to adopt. Additionally, it has a very simple interface.

I have utilized Domo's collaborative features. The collaborative feature is beneficial because sometimes team members don't have access to particular visualizations where they find issues or insights. They can comment directly, and other team members get notified about these observations. This is a crucial feature that many other visualization tools don't offer.

Domo's self-service analytics tools can fetch insights effectively. Domo has predictive capabilities where non-technical users can access predictions and related functionalities.

In Domo, sometimes it takes too much time to upload data. If improvements can happen in this area, that would be better.

Currently, I don't have anything specific missing in Domo, but an AI chatbot could be beneficial. If a non-technical user wants specific insights from any dashboard, they could input their prompt and get insights, which would be a great feature going forward.

I have worked on Domo for almost two years.

I haven't escalated any questions to Domo technical support because whenever I had any query, it was resolved through the FAQ section. I didn't need to contact technical support.

I have experience working with other BI products and data visualization solutions such as Tableau, Power BI, and QuickSight.

The initial setup of Domo is straightforward and not particularly difficult. When compared with other tools Power BI and Tableau, it is somewhat more complex, but it remains reasonably straightforward.

I am aware of Domo's pricing aspect, and it is competitive compared to other companies with no fluctuation. It is on the higher pricing side and expensive, but the cost is justifiable.

Mobile accessibility to Domo provides significant benefits as mobile features make it simpler to review visualizations. If any bug occurs or a critical situation arises at odd times, our product team can examine the dashboard and confirm the situation, making it feasible to discuss across teams.

If organizations are considering Domo, they should proceed with implementation. It is very simple to use, has a simple interface, and teams will find it easy to adopt. That would be my recommendation. On a scale of 1-10, I rate Domo an 8.

I am a customer in the sense that the company I work for uses Domo for business intelligence reporting.

In my line of work, we support decision makers in visibility for the products that we're selling, and so we use Domo for integrating not only the data warehouse but also other inputs such as Excel sheets that perhaps some people are trying to run hypothesis testing or pilot projects. We use Domo as the hub where we have inputs either from the data warehouse or from spreadsheets. Then we're able to build pipelines, and these pipelines power dashboards. These dashboards are used by decision makers for visibility on matters, customer retention, churn rate, as well as acquisition of customers.

The most valuable feature of Domo is the fact that you can connect multiple inputs and you don't have to have a data warehouse. When we started using Domo, we only had different data sources in the database. In Postgres, we had a couple of databases that we would pipe into Domo using Domo Workbench. You don't need to have a well-structured data warehouse to start using Domo. It allows you to have any source of input. You can input spreadsheets, Excel, CSV, as well as any other live sources of data.

In addition to this, you're able to build pipelines. Building pipelines is simply integrating and coming up with the data wrangling steps. You want to filter, select certain columns, and then create outputs that you're able to build cards on. This data infrastructure is not limiting in the sense that you're able to do all that you can think about. Recently, they're also enabling the use of R and Python capabilities in the Domo pipeline, which is something I really enjoy.

The positive impact I've seen from working with Domo has been being able to wrangle data. As long as you have the logical flow of what you want to do and you're an analyst, you're able to pick up skills quite fast because the Domo ETL, especially where you're building the pipeline, is quite logical and easy to interpret. The tiles are quite elaborately explained: this is a filter, this is a select, this is a join, and as long as you know what join does and how you want to do it, it's quite good and easy to learn.

Domo's self-service analytics tools have helped non-technical users in my organization greatly. Recently, we launched key datasets that are able to cut across several departments. We are able to share these with key stakeholders and they are able to do their own wrangling. These tables on customers, transactions, and other items enable them to understand what to do with this data given that it doesn't have PII information. It is granular enough for them to make any sort of analysis. They can figure out how many transactions a given customer has done, and that enables them as stakeholders to do their own analysis without relying on my department and putting in a request for us to do the analysis on their behalf.

I have not used Domo's collaborative features extensively.

Regarding Domo's AI-driven insights in uncovering trends and forecasting outcomes, the limiting factor is that you need to define all of your columns before you're able to do any AI or feature engineering. That's quite a lot of work, especially on our end, given that we have huge datasets and sometimes we don't have updated data dictionaries. My wish would be for Domo to learn on its own and figure out column types without necessarily having to build that data dictionary.

One of the areas where we've had frustrations with Domo is the aesthetics. The aesthetics are quite limited compared to other BI tools such as Tableau and Power BI. The aesthetic feel, especially when building dashboards or apps, needs improvement. While Domo Apps is almost a Domo dashboard with more features and a better feel, I would hope for an investment in the aesthetics area. Being able to swipe right or left, instead of just scrolling down would be beneficial, as most Domo dashboards only allow downward scrolling. Some of our stakeholders find the dashboards very long and wish they could scan through them more efficiently.

I have been working with Domo for over three years.

If I were to give a score on how stable and reliable Domo has been for me so far, I would give it an eight. There were issues at some point, maybe more than two years ago, where sometimes access issues or reloading issues would occur where the server was hanging. But in recent years, I haven't had such cases. It's quite stable and I don't have any reservations on its stability.

Domo is quite scalable. The fact that you're able to easily identify the pipelines or flows that have errors, and it notifies you when you're building a pipeline where you can run previews and tell where to fix issues, is helpful. As the data grows, you're able to identify failures and fix them. This enables you to think long-term, and so even as your data grows, you're able to work with it.

We had an issue earlier this year where an ETL was running and it had multiple triggers. Unfortunately at some point, having multiple triggers would break the run. Reaching out to Domo, they were quite helpful in helping us fix that. However, for that specific run, it had flagged the error as a different tile in the preview, which was quite problematic. Their willingness to work with us and fix solutions even as we build up is quite impressive and worth mentioning.

I find Domo's technical support team to be quite professional and prompt. When I sent the email and copied our customer representative, it helped hasten the resolution. They were quite professional and in around three to five working days, they had identified where they suspected there was an issue and I was able to fix it.

I would rate the technical support from Domo a seven because there's room for improvement, for instance, on being able to flag exactly where the issue was. I can only dream for a faster resolution maybe using AI or being able to chat through this and not having to wait for a resolution that's coming three or five days later on email, as it delays our outputs.

I have not used a different solution for these use cases before Domo. When I joined this current company, they were just launching Domo. However, I've used Power BI before, and in comparison, I would say Domo is a good and easy-to-use tool, especially behind the scenes. This is particularly true in the preparing of the workflows and preparing of the pipeline. However, its front-facing interface needs some work and can be improved compared to Power BI.

Regarding Domo data visualization features, I don't find anything in particular to be the most valuable because I use bar graphs and line graphs. It's more dependent on what I'm trying to visualize. If it's a trend, then I'll use the line graphs. If it's just the distribution of people, then I'll use the bar graphs. All of them are quite good.

Regarding the pricing of Domo, I'm not too privy to the current contract we have. However, I do know that our pricing model changed since last year. We are on a consumption model, which means that you're given credits and those credits allow you to build a certain number of datasets, build a certain number of ETLs and run them a given number of times. This is limiting in the sense that once you exhaust these credits, you begin paying or start getting charged, which can be expensive. However, this has led to us cleaning up our datasets and data flows, and setting ETLs periodically with more thought.

I don't have extensive information on how mobile accessibility to Domo data insights has influenced our business outcomes as I've not used the mobile features. However, I know that there's a specific stakeholder who has access and they've been taking screenshots and sharing in their leadership forums. They're able to access Domo dashboards using their phone and quickly browse through to get the key insights they're keen about.

Based on everything described about Domo, I would rate this product a solid eight out of ten.