What is your primary use case for Domo?

My main use case for Domo involves building different tables and different cards so I can look at different data points. A quick specific example of a table I have built or a data point I often look at is churn. I look at churn often to see how things are going.

For a product company, I used Domo. It was my client, and I cannot disclose details, but it was in long storage products. It was purely for marketing.

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.

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.

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.

As a Domo developer for my client, I am working to build multiple ETL, dashboards, and app use which we are using. For the dashboard, the main use case for Domo is the dashboard. Collaborative features in Domo allow team members to work with different dashboards, as different people can work at the same time, and the changes they make are seamless. In other BI tools, team members cannot work on the same dashboard or in ETL simultaneously, but that is not an issue in Domo.

For a company that doesn't already have an electronic data warehouse, has disjointed data, and wants to have a repository and analysis all in one unit, that is what Domo's target market is.

I primarily use Domo for building reports and dashboards against our Snowflake data warehouse. It is utilized in a university setting with a couple thousand students.

We use Domo as a platform for our officials. It is used for high-level data submissions.

We use Domo to implement our end clients' KPI dashboards and various metrics.

We use the solution to create a data visualization of all the business processes.

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.

Our primary use case for the solution is pandemic data and ensuring that the information is de-identified before it is presented to decision-makers.

Our primary use case for using Domo is from the consulting point of view. We use it for unified analytics where they have a lot of batch data and stream data. We want to combine and ensure, particularly that the deliverable side form categories, like real-time dashboard reporting, KPI-driven reports, ad hoc users, ad hoc reporting, as well as advanced analytics and data sets.

The solution was an aggregation of accounting information across the entire organization. Most of the controllers and accountants were using Excel or Access on their desktops in order to create the reports that they were generating. First of all, we parsed and imported all of the Oracle ERP and the other, JD Edwards ERP information into one, into Domo. And then we even imported some of the access database information from the other accountants into Domo and we generated the dashboard and KPI reports out of Domo.

I have run multiple PMO's from a Domo dashboard by importing data from Smartsheet.  One at a Fortune 150 company and another at a startup.  Data types include budgets, projects, project metrics, tasks, and action items.  Easy to get up and running quickly - took me about three weeks on my first try.

Domo is a cloud intelligence software, so it's used in data analytics or analysis. It's a one-stop shop BI tool that handles the entire business intelligence process. Multiple components are involved when giving end-to-end BI solutions, for example, integration, ETL, data warehousing, data analytics, data visualization, data science, and machine learning, which Domo is capable of handling end-to-end. It's a tool that can do everything, and you can pull data from anywhere, from visualizations using advanced AIML concepts through it.

Domo is a data platform that helps us collect different kinds of data. It also allows us to put all the data together, assess it and use it to help work through business processes or workflows.

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 of our internal customers is a capital finance team. Before we reached out to them, they were pretty much handling all their data in Excel sheets. Their data has been expanding rapidly and they needed reporting in a visualization solution. They have different forecast methodologies and cycles, and different metrics within those forecasts types. They have various types of capital metrics. If you are from a finance background, you might have heard of what an IOI or an NPV or an IRR is. They had been doing it in Excel. Ideally, to fulfill their needs, you would need two different solutions. One is a transformation solution. When you are handling huge amounts of data, you certainly need a database and, most commonly, what you prefer is SQL. Once your transmission is complete, you would also need a visualization solution. There are many available in the market. With Domo, we can do everything in one place. We don't need a separate database. We can do ETL and the visualization in one location. It's not on a device. It is completely cloud-based. Since we are a healthcare provider, we chose the secure instance of the public cloud: a PSI-certified instance.

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.

I collated all the reports that we got from Domo's APIs, then performed some ETLs and processing so we could build a final output from which the dashboard would get powered. Then, we created all types of stuff in Domo. At that point, the license let us use all the available jobs in Domo. Therefore, we were using tables and pie charts. For demographics, we are using the geographical charts for Australia and the USA, as the brands we deal with are mainly from Australia and the USA. 31 million rows of data are getting processed every hour within Domo. Domo has their own internal servers and phone apps.

We use it to work on many business problems using the data visualization. Currently, I'm working for a company which deals with title insurance. We use Domo to visualize the data: How many open orders are created, which agent performed better, which region got the most orders, how many were closed or lost. Our company has data related to mortgages so that's what we use it on. In our division, directors and VPs get insight from the data. Workbench is deployed on-premises and then we have a web application, a cloud application, for visualization purposes.

Domo is being used in quite a few areas. We're using it for financial reporting and analytics. Basic financial reports have just the numbers, but those kinds of reports don't answer your questions. Questions like "why?" and "where are the problem areas?" So, we're using it for business analytics to get insight into our financial performance. We're a parts manufacturer, so we're also using Domo for tracking quality, including defects, warranties, and claims against the parts we manufacture. We're using it for sales planning to give business insight into industry trends that might affect our sales. We're also using it to get insight into our sales results. We're using it in our plants now — and this is newer — to track shipments and resources required so we can get the right resources where they need to be to load the trucks, based on when the parts are ready. That's actually an IoT use case. In addition, we're using it to track our patents and our inventions, as a design company. It started out with a couple of small use cases but it has blossomed very quickly. As soon as people see Domo for one case they come knocking on my door and say, "Hey, we'd like to use Domo as well."

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.

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

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.

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.

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.

I use Domo mostly for three reasons: * To create connections with several applications and obtain data from those applications, e.g., Google Drive, Google Sheets, or Google Analytics. * With those connections, I love to upload data to Domo and transform that data in different ways. I create ETLs to join the data. * 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.

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

We used it for data crunching, analytics, and business intelligence to take it to a new level.

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.