They Were Getting Ready to IPO. Then Something Changed.

A question comes up surprisingly often in my work with product leaders:

“If a company was preparing to go public and then gets acquired instead, does that mean something went wrong?”

It is a reasonable question. We tend to tell company stories as if there is a predictable progression: raise venture capital, grow, reach profitability, IPO.

And if the IPO does not happen, it is tempting to assume the company failed to reach the destination.

But companies do not have one destination. They have strategic options.

Stash is a particularly interesting example of this.

You may know Stash as the consumer financial platform that made investing more accessible to everyday Americans. It was founded in 2015 and grew into a subscription business offering investing, banking, saving and financial guidance.

But the part of the story I find much more interesting as a product leader is what happened behind the product.

In 2021, Stash was valued at approximately $1.4 billion, and reports emerged that the company was exploring ways to go public, including a traditional IPO.

Then the environment for fintech companies changed dramatically.

Stash did not IPO.

Instead, the company spent the following years improving its economics, evolving its product and strengthening the business. In 2023, management talked publicly about becoming “public market ready” without putting itself in a position where it needed an IPO to raise capital.

By 2025, Stash had raised another $146 million. It had approximately $4.3 billion in assets under management and was moving toward profitability.

And then the destination changed again.

In 2026, Grab announced that it was acquiring Stash.

Grab is a much larger Southeast Asian technology company operating across mobility, delivery and financial services. It already had payments, lending, banking and insurance capabilities.

What it did not have at the same scale was investing and wealth management.

Suddenly Stash looked different.

Not simply as a standalone consumer fintech company, but as a strategic capability inside a much larger financial-services ecosystem.

This is where the story gets interesting for product leaders.

Before the acquisition, your job was ultimately to help increase the value of Stash as an independent company.

Of course you would think about customers, retention, product adoption and growth.

But at the executive level, those things ultimately connected to the economics of the company: subscription revenue, assets under management, profitability, cash generation and enterprise value.

And if becoming a public company remained one possible destination, you would also need to understand what increasingly sophisticated investors would expect from the business.

Now imagine coming to work after Grab announces the acquisition.

Your customers have not suddenly changed.
Their financial problems have not disappeared.
Your product may still be performing well.

But the context in which you are allocating product and engineering capital has changed considerably.

That means a roadmap that made perfect sense before the acquisition may no longer be the best roadmap afterward.

The easy response would be to wait for the new parent company to tell you what to build.

The slightly more sophisticated response would be to start looking for “synergies.”

I would do something different.
I would go back through every significant investment on the roadmap and ask:

What has changed about the business assumptions behind this investment?

Take Stash's AI Money Coach.

Before the acquisition, you might have justified investing in it because it improved engagement, retention or the value of a Stash subscription.

Those outcomes still matter.

But Grab specifically highlighted Stash's investing technology and AI capabilities when it announced the acquisition, and talked about the possibility of bringing Stash's investing solutions to Southeast Asia.

The same capability can therefore have a completely different strategic value.

It might improve retention inside Stash and become technology that Grab could eventually leverage across a much larger financial ecosystem.

If that hypothesis is true, you might invest more heavily in making that technology portable, modular, compliant across different environments and capable of supporting multiple markets.

That is a different roadmap decision.

There is another mistake I see product leaders make when thinking about M&A.

They assume acquisition automatically means consolidation.

Merge the platforms. Integrate the products. Share the technology. Eliminate duplication.

Sometimes that creates value. Sometimes it destroys the thing you just paid hundreds of millions of dollars to acquire.

Grab publicly said that Stash would continue operating as an independent US brand.

If I were leading Product at Stash, that would make me very cautious about prematurely optimizing the roadmap around integration.

Instead, I would think in stages:

That is very different from immediately rebuilding the product around the parent company.

I don't think that is the useful question.

There is no public evidence that Stash formally filed for an IPO and then cancelled it. What we know is that it explored public-market options and deliberately worked toward becoming public-market ready.

Eventually, another strategic option won.

That distinction matters.

An IPO is not the definition of success. Neither is an acquisition.

They are different paths for creating liquidity, accessing capital and determining who owns the next chapter of the company's growth.

The executive question is:

You cannot answer that from the product roadmap alone.

This is the exercise I would give any product leader.

Take your current roadmap and imagine that tomorrow your company is acquired by a much larger business.

Then ask yourself:

And then ask the uncomfortable question:

If the answer is “no,” I would want to know why.

Because major changes in ownership, capital structure or strategic direction can change what a good product investment looks like, even when the customer problems themselves have not changed.

That is one of the differences between managing a roadmap and exercising executive-level product judgment.

Most product leadership programs teach strategy as something you do inside Product.

I am much more interested in what happens when the business changes around Product.

An acquisition happens. Capital becomes more expensive. The board changes its expectations. An IPO becomes a possibility - or stops being one. A new owner has completely different assets and strategic priorities. Suddenly, yesterday's reasonable roadmap needs to be questioned.

These are the kinds of cases we work through in my Executive-Level Product Judgment cohort: learning how to read the business context, understand the economics, make better product investment decisions and communicate those decisions at the executive level.

The next cohort opens in September.

I am deliberately keeping this one very small: no more than five people, and it will be application-only because I want participants who are ready to work through real business decisions rather than simply consume another product course.

Once those seats are filled, I will close the cohort.

If you want to be considered for one of the five seats, apply here.

Until next week,
Elena Leonova