Progress-Domo deal is the latest test of CIO software assumptions

On September 22, Progress Software completed its acquisition of substantially all the assets of Domo's AI and data platform business. For a CIO whose company relies on Domo, the software still worked the next morning. That's what makes the deal interesting.

The acquisition does not, by itself, say anything specific about what Domo will look like two or three years from now. It is too early to tell. But the ownership change gives CIOs a reason to ask a familiar question: Are the assumptions that supported the original technology decision still the same?

The hard part isn't knowing that acquisitions can matter. CIOs already know that. Instead, it is deciding what to do before the consequences are clear.

Recent reporting provides several different versions of that problem. Domo gives us the immediate case, where ownership has changed but customer outcomes are largely unknown. Nearly three years after Broadcom acquired VMware, customers are still making stay-or-leave decisions as contracts expire and the consequences of Broadcom's licensing, pricing and product changes have become clearer. Dynatrace offers another variation, using acquisitions to expand the role it wants to play for existing customers.

Different companies, different deals and very different points on the timeline. But they all raise a version of the same question: Is this still the technology and vendor relationship we originally chose?

Ownership can change before the software does

Before the acquisition, Domo was a relatively focused data, analytics and AI firm. Its platform and employees now sit inside Progress Software, a much broader company.

When the transaction closed, Yogesh Gupta, CEO of Progress Software, said Domo would strengthen its strategy to provide the "context and control" enterprises need for trusted AI and agentic systems. That sounds like a plus for Domo customers. It also remains the buyer's stated intention.

There is no indication that Domo is about to disappear. Quite the opposite: Progress Software has described Domo as complementary to and a significant expansion of its existing data platform offerings. But that still does not tell a CIO exactly what happens next: Does Domo remain a distinct platform? Does Progress integrate it more tightly with its other data and AI products? Does investment increase? Do pricing, support or product direction eventually change?

When the deal was announced in July, analysts interviewed by TechTarget saw both upside and uncertainty. Donald Farmer, founder of TreeHive Strategy, questioned how aggressively Progress would invest in keeping Domo independently competitive. William McKnight, president of McKnight Consulting Group, saw the deal as reducing Domo's financial uncertainty and creating the possibility of a more integrated platform. Analyst Kevin Petrie, vice president of research at BARC, saw strong potential synergies.

That disagreement is useful. The acquisition changes the questions before it necessarily changes the answers. A CIO should try to understand what Progress wants from Domo and where it fits into Progress Software's larger strategy.

But buyer intention is not an outcome; it's a signal to investigate.

The acquisition changes the questions before it necessarily changes the answers.

Reassessing isn't deciding to leave

A vendor changes owners. Maybe pricing changes. Maybe it doesn't. Maybe product investment slows. Maybe it increases. Maybe support suffers. Maybe customers end up with a better-integrated platform.

The CIO cannot know all of that when the deal closes. What the CIO can understand is the company's exposure if the relationship eventually changes in a way that matters.

VMware shows why. Broadcom completed its VMware acquisition in November 2023. Since then, some customers have dealt with higher costs, licensing and product changes, and support complaints. This year, as more contracts wind down, enterprises have been increasingly looking to act on alternatives they have spent years evaluating. But leaving a deeply embedded platform can itself be a multiyear project. That is why "rip and replace" is often the wrong mental model. There can be migration labor, retraining, new tooling, operational risk and a period when an enterprise pays for both the incumbent environment and its replacement.

The harder a platform is to replace, the earlier a CIO may need to understand what replacing it would actually require -- even when there is not yet evidence that replacing it is necessary. That is not a decision to leave; think of it as due diligence after a software vendor acquisition: How difficult would an exit be? How long would it take? Where are the hardest dependencies? What would have to run side by side? What important capabilities might disappear in a move? Knowing those answers can matter, even if the enterprise never leaves.

Worse terms don't automatically mean the wrong technology

VMware also demonstrates why reassessment cannot simply be code for "prepare to migrate." Broadcom substantially consolidated VMware's product portfolio around VMware Cloud Foundation (VCF), while also ending perpetual licensing and increasing costs for some customers. Yet recent reporting shows a different side of the VMware story: Some customers still see value in the consolidated platform.

In August 2026, Broadcom said 70% of VMware's 10,000 largest customers had migrated to VCF and 3,000 customers had moved to VCF 9. Jeffrey Ericson, chief information security officer at MedRisk, described the consolidated platform as the "bedrock" of the company's data center infrastructure and said the company benefited from both the product consolidation and Broadcom professional services.

A CIO can, therefore, end up in what appears to be a contradictory position: The commercial relationship might be less attractive, while the technology might fit the architecture better. Staying can still be the rational decision.

Worse terms do not automatically equal the wrong technology decision. The switching cost, business risk and value of the incumbent platform might still make staying the better enterprise choice. And this is exactly the kind of tradeoff CIOs are expected to navigate. It is also why they know they are rarely the only arbiter once the decision involves enough money, operational risk and business disruption. Procurement, finance, legal, architecture teams and business leaders all have something at stake.

The vendor you chose might be changing, too

There is another version of the same problem: What if the company you already use is expanding its functionality by acquiring other vendors with the stated goal of broadening what it can offer customers like you? Does that give the CIO a signal to perform the same kind of due diligence?

Yes and no. And when the answer is yes and no, lean toward yes -- not because the expansion is necessarily bad, but because a vendor's promise of a more integrated, useful and broader platform does not mean it will make sense for a particular customer.

Dynatrace is a current example: The observability vendor acquired DevCycle in January 2026, adding feature management and progressive delivery capabilities, and Bindplane in April, extending into telemetry pipeline management. Then, in August, Dynatrace acquired Arize for $915 million, adding AI evaluation and observability capabilities from development through production. That is a substantial product expansion -- and it might be exactly what a customer wants.

Dynatrace's third acquisition this year is part of its move from pure observability toward "systems of control." It could reduce tool sprawl. It could make integrations easier. It could give development, platform and operations teams a more consistent environment. But an enterprise might already have vendors it likes for feature management, telemetry management or AI evaluation. Moving those functions onto a single platform can carry migration costs, retraining, disruption and new dependencies -- even if the combined license package looks cheaper.

For the same reason that a VMware customer might decide paying more to stay is less costly than leaving, a Dynatrace customer might decide a cheaper, more integrated platform is not worth replacing systems that already work. There are advantages to having one supplier own more of the architecture and operating processes, but a CIO could also find the opposite is true.

The question is not whether a vendor becoming broader is good or bad, but whether that broader vendor relationship is better for this enterprise than the mix of vendors and tools it already has.

Know what would actually change your mind

None of this requires IT leaders to predict what Progress Software, Broadcom, Dynatrace or any other vendor will do next. They can't. What they can do is decide what evidence would cause them to reconsider the original technology decision.

Maybe it is a material change in the roadmap. Maybe pricing or licensing changes enough to alter the economics. Maybe product investment slows or support deteriorates. Maybe the new owner wants to pull the product further into its own stack than the enterprise wants to go. Or the evidence could point the other way. The new owner might invest more heavily, improve integration, eliminate financial uncertainty or turn a group of disconnected products into a platform that fits the enterprise better than what it originally bought.

Reassess because ownership changed. Prepare because future options may be expensive or slow. Act because something material shifted.

The acquisition itself does not have to tell IT leaders what to do. It gives them a reason to reopen the file -- and to know what would have to change before the original technology decision no longer makes sense.

James Alan Miller is a veteran technology editor and writer and Lead Editor for CIO News at Informa TechTarget. He directs coverage of enterprise technology strategy, AI, software, data, infrastructure and the decisions shaping how CIOs manage increasingly complex IT environments.