Alfred AnyanInsights
← All insights

What Happens When a Buyer Changes Your Product Beyond Recognition?

Confident businessman sitting at desk, working on computer in modern office.

Aathif Aarifeen

An acquisition offer forces a founder to decide which asset carries the future: the product’s purpose or the company’s independence. Preserve the product when the buyer can fund, distribute and protect the work; preserve the company when the buyer’s incentives would change the work beyond recognition.

In April 2012, Facebook agreed to acquire Instagram, then a small photo-sharing company led by Kevin Systrom and Mike Krieger. The deal gave Instagram access to Facebook’s resources and audience, while Facebook said Instagram would remain independently branded. At that moment, the choice was live: accept a larger company’s infrastructure and give up control of the company, or keep building alone with the uncertainty that came with it.

The New York Times documented the acquisition as Facebook’s largest deal at that point. What matters for founders is the shape of the decision, not the eventual headline value. Instagram’s team had built a product people were already using. Facebook had distribution, capital and its own strategic reasons for wanting it.

Name the thing you are protecting

Founders often say they want to “protect the business” when they mean different things.

Sometimes they mean the product must keep solving a specific customer problem. Perhaps an AI workflow for small lenders in Accra needs to remain explainable, even if a buyer wants a broader automation suite. Sometimes they mean the team needs jobs and a payroll path. Sometimes they mean their ability to set the roadmap without another company’s quarterly priorities.

Those are separate assets. An acquisition can preserve one while ending another.

Write down the part of the business that would be damaged first if the deal closed. Is it the product’s data policy? The customer relationship? A roadmap that depends on learning from a narrow market? The team’s ability to say no to a large client request?

If you cannot name that asset, you cannot negotiate for it.

Read the offer as an operating plan

The price matters. The operating assumptions matter more.

A buyer may say they want the product, then remove the team that understands why customers chose it. They may promise autonomy, then make the roadmap serve a market you never intended to enter. They may offer enough cash to keep everyone employed while moving the product away from the users whose problems made it valuable.

Ask for the answer in terms that survive the closing meeting:

  • Who owns product decisions after the transaction?
  • Which customers, markets and integrations remain in scope?
  • What happens to the people who maintain the product?
  • Which commitments are written into the agreement, and which exist only in conversation?
  • If the buyer changes direction, can the product team object, leave, or keep any part of the work?

This is where an overseas buyer can look especially attractive to a founder building between Africa, Europe and the US. The offer may solve a real constraint: distribution, hiring capacity, compliance work, or access to customers who would take years to reach alone. It can also turn local customer knowledge into a feature request inside someone else’s roadmap.

The relevant question is not whether the buyer is bigger. It is whether their plan gives your product a better chance of remaining useful.

Keep the decision tied to customer evidence

A product with paying users, repeat use and a clear reason for existing gives a founder more choices. A product still searching for demand can make any offer feel like rescue.

That distinction changes the negotiation.

If your customer map is thin, do the work of identifying who depends on the product before you accept a deal. Look at active accounts, renewal conversations, implementation notes and the requests your team keeps declining. The customer map an AI startup cannot afford to lose is useful here because acquisition discussions can make founders focus on the buyer before they understand the customers they are handing over.

The evidence may point toward selling. If users need reliability and reach that the buyer can genuinely provide, preserving the product can be the responsible call.

It may point toward declining. If customers chose you because you stayed close to their workflow, and the buyer needs you to become a generic feature, the company may be the only place that product can survive intact.

Decide before urgency decides for you

By 2018, Systrom and Krieger had left Instagram. Their departure was widely reported amid growing tension over Instagram’s independence within Facebook. The original transaction had preserved Instagram’s product and accelerated its reach, but it did not preserve permanent founder control.

That outcome does not make the 2012 decision wrong. It makes the trade explicit.

A founder should enter an acquisition conversation with two documents: a list of the product commitments that must survive, and a cash plan for continuing without the deal. The first clarifies what to negotiate. The second prevents urgency from pretending to be strategy.

Apollo 13 is a useful reminder that constraints can make an imperfect solution necessary, as I wrote in The Square Canisters Apollo 13 Needed, and What Debt Can Cost Founders. An acquisition can be a practical answer to a real constraint. Treat it with the same discipline: identify what must keep working, then choose the path that keeps it alive.

Comments

No comments yet.