Domo vs Tableau

10-Q Financial Filing Analysis for Domo (2026-09-03)

For the second quarter ended July 31, 2026, Domo reported total revenue of $76.8 million, down 4% year-over-year, and a GAAP net loss of $9.6 million compared to a net loss of $22.9 million in the prior-year period. Subscription revenue represented 92% of total revenue at $70.4 million. The company faced severe liquidity and covenant compliance issues, remaining in breach of its credit facility's minimum annualized recurring revenue covenant as of April 30, 2026, and July 31, 2026, resulting in substantial doubt about its ability to continue as a going concern. To resolve its debt default and secure liquidity, Domo entered into a definitive Asset Purchase Agreement on July 22, 2026, with Progress Software Corporation. Progress will acquire substantially all operating assets, the platform, customer contracts, and subsidiaries for $400 million in cash. Domo will use the proceeds to repay its $137.2 million debt obligations in full, retain its net operating loss (NOL) carryforwards, and transition into a debt-free holding company trading under a new ticker symbol.

• Domo signed a definitive agreement on July 22, 2026, to sell substantially all operating assets and business to Progress Software for $400 million in cash.
• The company remained out of compliance with its debt covenants as of July 31, 2026, operating under a forbearance agreement requiring sale completion by November 30, 2026, to pay off $137.24 million in debt.
• Q2 revenue reached $76.78 million (down 4% YoY) with a net loss of $9.62 million and cash/cash equivalents of $25.07 million.

8-K Financial Filing Analysis for Domo (2026-09-22)

On September 22, 2026, Domo, Inc. completed the sale of substantially all of its business assets and transferred its operational employees to Progress Software Corporation pursuant to the July 22, 2026 Asset Purchase Agreement. Domo received approximately $221.0 million in net cash proceeds upon closing, retaining its net operating loss (NOL) carryforwards. Concurrently, the company terminated and fully repaid its Amended and Restated Loan and Security Agreement with Obsidian Agency Services and Wilmington Trust, while also repurchasing outstanding warrants for approximately $10.0 million. Following the divestiture, the corporate entity was rebranded as Huckleberry.ai, Inc. via a short-form subsidiary merger, and its Class B Common Stock ticker on the Nasdaq Global Market will change from 'DOMO' to 'HUCK' effective September 24, 2026.

• Completed the asset sale of Domo's core BI and analytics software business to Progress Software Corporation for approximately $221.0 million in net cash proceeds, retaining tax NOL carryforwards.
• Repaid in full and terminated the August 2023 Amended and Restated Loan and Security Agreement, releasing all associated liens and discharging outstanding debt obligations.
• Rebranded the corporate entity to Huckleberry.ai, Inc., repurchased outstanding warrants for $10.0 million, and announced a Nasdaq ticker change from 'DOMO' to 'HUCK' effective September 24, 2026.

New Product Features and AI Announcements Shared at Domo Connections 2026

Domo announced new product features and AI capabilities at its Domo Connections 2026 event, as highlighted in a blog post dated September 18, 2026.

How to Build a Tableau Dashboard and Story

Step-by-step tutorial showing how to create a published Tableau dashboard and a three-point narrative story from a real dataset. The guide uses the Telco Customer Churn dataset (7,043 customers) and a public GitHub repo for data-shaping code. It stresses shaping data upstream (one row per entity, 1/0 outcome column, readable names, ordered buckets), creating a single calculated field for rates (Churn Rate = AVG([Churned])), building four focused worksheets (one point each), assembling them into a dashboard, and sequencing three story points (problem, mechanism, action). It explains Tableau Public publishing requirements (workbooks must use extracts) and gives practical UI steps and common error fixes. The guide also covers visual rules (one-accent color, bar chart accuracy) and advises documenting limitations when publishing.

• Worked example uses the Telco Customer Churn dataset on Kaggle with 7,043 customers (one row per customer).
• Author provides a public GitHub repository (telco-churn-analysis) containing the Python script that shapes the data for the example.
• Recommended calculated field for the rate: Churn Rate = AVG([Churned]) (1/0 column average).