Domo Built the Business Dashboard. Now Its $400 Million Exit Is the Real Data Point

The corporate dashboard has a dirty secret: the chart is often the easy part. Behind a clean line showing weekly sales sits a small bureaucracy of exports, formulas, permissions, definitions, and someone named Priya who knows why Tuesday’s number should never be trusted before lunch. Domo built a business by trying to absorb that bureaucracy. It connects the sources, cleans and combines the data, presents it on a phone or browser, and then lets a team trigger a workflow, write a result back, or build an application around it. The ambition was never merely prettier charts. It was to make the chart the front door to work.

That is a more consequential pitch than “business intelligence,” and a more expensive one to fulfill. From its founding in 2010 through January 2026, Domo says it invested just over $1 billion in research and development. The result is a platform that spans more than 1,000 connectors, data transformation, interactive analytics, embedded experiences, low-code and pro-code apps, automation, model management, and AI agents. On a typical business day, its customers may query trillions of uncached rows. Domo says it has generally kept average query response below one second.

01 / The useful ideaA control room that reaches back into the factory

Josh James arrived at Domo with a specific irritation. He had already co-founded web-analytics company Omniture, taken it public, and sold it to Adobe for $1.8 billion. Yet executives still had to ask other people for the current state of their own companies. Domo’s early idea was delightfully blunt: put the business in the CEO’s pocket. Its original name, Shacho - commonly translated from Japanese as company president - made the intended user impossible to miss.

The product moved steadily down the org chart. A modern Domo deployment can start with a marketing leader trying to reconcile Salesforce, ad platforms, and a warehouse. Magic ETL lets a non-specialist blend those inputs with a drag-and-drop interface; SQL and scripting remain available to technical users. A team can publish the result as a dashboard, send an alert when a threshold moves, route an approval, or create a role-specific app. Permissions can extend down to individual rows. The same governed logic can feed an executive, a warehouse supervisor, a customer portal, or an AI agent.

The last step is the point. ESPN used a customer-experience application built on Domo to bring support tickets and fan sentiment into view across marketing, engineering, product, and programming. Reported Android app ratings rose from 3.4 in February 2021 to above 4 by July. TaylorMade’s five-person BI team could not answer every request from more than 1,600 employees; Domo gave executives daily global sales and gave warehouse staff mobile visibility into bottlenecks. Cisco organized a community of 1,500 marketing users around shared pages and cards. These are not stories about admiring a pie chart. They are stories about shortening the distance between evidence and a decision.

Domo provides a single version of the truth that is readily available to whoever needs it.Tom Collard, TaylorMade

02 / The priceUnlimited seats, metered activity, unpublished dollars

Domo’s public pricing page is specific about mechanics and coy about money. A 30-day trial requires no credit card. Paid plans offer unlimited users and charge through credits tied to platform consumption, with custom quotes, volume discounts, support packages, and add-ons. There is no public dollar menu. For a buyer, that changes the budget conversation from “How many people get a license?” to “How much will those people and pipelines do?”

The upside is adoption. A manager does not need to guard seats like rare concert tickets, and an app can reach the entire field team. The downside is forecast anxiety: refreshes, transformation jobs, storage, data movement, and newer AI workloads all create activity. Domo itself warns that customers may consume less than expected, hurting retention, or use AI tools more than expected, raising infrastructure costs. By January 2026, 84 percent of annual recurring revenue was on a consumption-based service, and 76 percent of recurring revenue was tied to multi-year contracts.

The copyable move is to model a real workload before signing. Count the important pipelines, refresh cadence, transformations, storage, users, and bursty jobs. Then compare the full operating cost with the tools and labor it replaces. If Domo removes an ETL product, a dashboard license, hand-built distribution, and hours of spreadsheet maintenance, the platform can earn its keep. If the requirement is six monthly charts for eight people, the control room is probably too much building.

03 / The hard chartThe platform widened while the growth line went flat

Domo was once priced for a much steeper future. Venture investors supplied hundreds of millions of dollars, including $60 million in 2013, $125 million in 2014, $200 million in 2015, and $131 million in 2016. A 2017 extension placed its private valuation around $2.3 billion. It went public in June 2018. The platform kept expanding, but recent revenue did not: $319.0 million in fiscal 2024, $317.0 million in 2025, and $318.9 million in 2026.

What failed first was the growth story, not the product’s ability to do work. Fiscal 2026 subscription revenue increased, gross margin reached 75 percent, and the net loss narrowed by more than $22 million. Yet customer count fell 7 percent; net retention averaged 94 percent; revenue from existing customers declined by a net $10.6 million. New customers replaced that decline and added a little more, but this is a treadmill, not a flywheel.

Leadership reflected the strain. James stepped down in March 2022, handing the CEO role to John Mellor. One year later, after slower growth and a sharp share-price decline, Mellor left and James returned. The strategic language shifted too. Domo began describing itself less as a dashboard company and more as an AI and data products platform, with cloud-warehouse partnerships moving closer to the center. Rather than ask customers to replace Snowflake, Databricks, BigQuery, Redshift, or Oracle, Domo can sit above them and use their data inside transformations, apps, workflows, and AI.

04 / The AI chapterAn agent needs permissions more than personality

Domo’s AI pitch is unusually grounded in plumbing. Its model-management layer can work with third-party models; Agent Catalyst gives builders a path to agents that use company data and tools; an AI Library organizes AI assets; toolkits define what an agent can do; and an MCP server connects those capabilities to outside AI systems. The important feature is the least theatrical one: a human approval point can sit between a recommendation and a business action.

That design fits Domo’s history. An agent asked to explain a sales dip needs the same trusted definitions as a dashboard. An agent asked to email a customer needs permission, context, and a workflow. Without those, fluent prose simply moves bad data faster. Domo’s breadth gives it an honest argument: the connector, governed dataset, analysis, app, and approval flow already live together. The AI does not have to improvise an operating system from loose tools.

05 / The handoffA $400 million answer to the strategy question

On July 22, 2026, Domo’s board announced the decision that makes every earlier chart look different. Progress Software agreed to acquire substantially all of Domo’s operating assets and employees for $400 million in cash, subject to adjustments and closing conditions. That package includes the platform, customer contracts, intellectual property, vendor relationships, and foreign subsidiaries. Progress says Domo will add governed data, context, and control to its AI strategy.

The structure is stranger than a standard takeover. Domo, Inc. is expected to remain public under a new name and ticker, keeping more than $900 million of net operating loss carryforwards and certain retained assets. At announcement, Domo estimated the remaining company would have roughly $246 million of net cash after closing and debt repayment. James would continue to lead that entity while Progress operates the Domo product. As of September 2, the deal was still pending; the parties expected a close before Progress’s fiscal year ends on November 30.

What changed the board’s mind is stated plainly enough: after a strategic alternatives review, it judged the sale the best route for shareholders and a stronger long-term home for the platform. The unspoken arithmetic sits nearby. A company with useful software, recognizable customers, and nearly $319 million of annual revenue had struggled to grow and had not produced an annual GAAP profit. Progress can spread the product across a larger enterprise-software operation. Domo’s shareholders keep a separate wager on cash and tax assets.

06 / What to borrowBuild the habit before you build the empire

The best part of Domo’s playbook is small enough to copy. Do not begin with “digital transformation.” Begin with a question that currently requires a meeting, three exports, and an apology. Give the metric an owner. Connect only the sources required to answer it. Put the answer where the person making the decision already works. Then add the alert, approval, or write-back that completes the loop.

• Land on one painful workflow. Expansion is earned by a visible result, not by a tour of platform features.
• Train champions near the decision. Cisco’s regional editors and Ingo Money’s internal Domo experts made adoption local.
• Define the number once. Shared logic and permissions matter more than the chart style.
• Meter the operating loop. Track refreshes, transformation, storage, AI, and labor saved before scaling consumption.
• Keep a person at consequential edges. Let automation prepare and route; require approval where money, customers, or risk move.

This approach will not fit every shop. A small team with a clean database and a narrow reporting need can buy a lighter BI tool. A company standardized on Microsoft may value the economics and familiarity of Power BI and Fabric. A mature data group may prefer best-of-breed components and accept the integration burden in exchange for control. And no platform will rescue a company that refuses to decide who owns definitions, access, and action.

Domo’s lasting insight is that data work does not end when the dashboard loads. It ends when somebody changes a forecast, fixes an app, reroutes inventory, approves a message, or declines to act because the evidence says wait. The company spent 16 years engineering that last mile. Now Progress is paying $400 million to take it farther. The final outcome remains unwritten, but the current chart is clear.