Domo vs ThoughtSpot

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.

Put Your Data to Work with ThoughtSpot in ChatGPT Work

New blog post: 'Put Your Data to Work with ThoughtSpot in ChatGPT Work' (Sep 10, 2026). Also new: '2026 Best Books on AI and Data' (Sep 10, 2026), 'Introducing SpotterCode in Developer Playground' (Sep 9, 2026), 'Trust, Tested: What Consumers Really Think About AI in Retail' (Sep 2, 2026), and 'Employee Recognition: Meet This Quarter's Icon Award Winners' (Sep 1, 2026).

ThoughtSpot Named a 2026 Gartner® Magic Quadrant™ Leader for Analytics and BI Platforms

ThoughtSpot has been recognized as a Leader in the 2026 Gartner Magic Quadrant for Analytics and BI Platforms, with a dedicated report available for download.

Postgres pattern to query row state as of a time

The article presents a Postgres schema pattern for answering point-in-time questions like “what did this row look like at T?” by keeping a history table alongside the main table (SCD Type 4) and using a row-level trigger to mirror INSERT/UPDATE/DELETE operations into that history table. The author contrasts common alternatives — event sourcing, in-place versioning (SCD Type 2), and periodic snapshotting — and provides concrete SQL: history table creation (LIKE ... INCLUDING DEFAULTS), a trigger function that stamps valid_from/valid_to and writes tombstone rows on DELETE, a point-in-time SELECT that picks the version valid at :as_of, and a backfill pattern for pre-install rows. The piece also warns about operational concerns such as schema drift when adding columns and recommends automating schema migration for history tables.

• The article describes using an SCD Type 4 pattern in Postgres: a records_history table that mirrors records plus valid_from, valid_to and operation columns.
• A row-level trigger function mirrors every INSERT, UPDATE and DELETE on records into records_history, stamping valid_from/valid_to and writing tombstones for deletes.
• The point-in-time query uses WHERE valid_from <= :as_of AND (valid_to IS NULL OR valid_to > :as_of) with DISTINCT ON (record_id) and ORDER BY record_id, valid_from DESC to return one row per record as of :as_of.