An acquisition meeting can make four years of product work disappear because buyers often value the customers, licenses and migration path more than the software itself. A founder who understands that early can negotiate around what the buyer needs, protect what still matters and avoid defending code that has already lost the room.
At 9:12 on a Monday morning in Accra, Kwame sat opposite three people who had spent the weekend inside his data room. He had brought a product roadmap, a laptop charged to 100 percent and a marked-up architecture diagram. The buyer’s first slide contained none of them.
Kwame is a composite founder, but the decision in front of him is familiar. He had spent four years building compliance software for small financial companies across West Africa. The product handled awkward workflows his larger competitors treated as edge cases. His team knew why one verification path needed a human check and why another could be automated safely.
The slide reduced the company to three lines: active customer contracts, regulatory permissions and the date those customers could move to the buyer’s platform.
The proposed migration deadline was close enough to make the meaning clear. The buyer wanted the market access Kwame had assembled. His product was being priced as temporary infrastructure.
The moment code stops carrying the valuation
Kwame’s first instinct was to correct the room. He opened the architecture diagram and explained why replacing the workflow engine would take longer than the buyer expected.
Nobody challenged the technical case. That made the situation worse.
The buyer’s product lead agreed that parts of the system were better suited to local conditions. Then the finance lead returned to customer retention during migration. The deal could proceed without preserving the product, provided enough customers stayed and the licenses transferred cleanly.
Kwame now faced a bad ending he had never included in his fundraising deck. He could sell the company, watch the product close and ask his engineers to help dismantle what they had built. If he resisted, the buyer could walk, leaving him with limited runway and a team that already knew acquisition talks were happening.
For one beat, neither choice looked like winning.
Founders often assume a buyer will see value where the team invested the most effort. Buyers use a different ledger. They pay for whichever asset changes their position: revenue, distribution, regulatory access, specialist knowledge, defensible data or time saved entering a market. Sometimes the product carries that value. Sometimes it carries customers to the real asset.
This is the acquisition version of a problem I see while building and shipping products: effort has no automatic claim on strategic value.
Read the deal through the migration plan
The turn came when Kwame stopped arguing for the whole product and asked a narrower question: which workflows had to survive for customers to remain after migration?
The answer exposed more than the valuation model had. Two customer segments depended on approval logic the buyer’s platform did not support. Moving them on the proposed schedule could interrupt work they performed every week. Those contracts were part of the deal’s attraction, yet the migration plan put them at risk.
That changed the conversation. Kwame no longer needed everyone to admire four years of engineering. He needed the buyer to recognise that one part of the product protected the customers they wanted to acquire.
This distinction matters. “Keep our platform” sounds like founder attachment. “Preserve this workflow until these customers can complete the same job safely” sounds like deal protection.
The same discipline applies before acquisition talks begin. If your company description depends on a tour of the feature set, the underlying value may still be unclear. I explored a related problem in Should I Pause the Roadmap When No One Can Explain What My Company Does?. A product can work well while the company remains difficult to understand.
A migration plan forces the issue. It reveals what the buyer believes can be removed, what must remain and what they fear losing.
Decide what you are protecting
Kwame used the remaining meeting time to separate three things he had previously treated as one.
The first was code the buyer could replace without changing the deal. The second was operating knowledge required to keep customers through the transition. The third was a small set of workflows whose removal could weaken retention and create avoidable compliance risk.
That separation gave him something concrete to negotiate. He could discuss a staged migration for the dependent customers, roles for the engineers who understood those workflows and clear conditions for shutting down the old platform. He could also stop spending credibility on components that were no longer commercially important.
This did not rescue the original product intact. It gave Kwame a way to protect the parts carrying real obligations and to be honest with his team about the rest.
There is a parallel here with profitable contracts that pull a company away from its roadmap. The difficult part is identifying what deserves protection before momentum makes the choice for you. I wrote about that tension in What Happens When a Profitable Contract Threatens Your Product Release?.
Write the disappearing-product memo now
On Tuesday morning, Kwame replaced the roadmap on his desk with a one-page memo. It named the customers who depended on specific workflows, the knowledge required to move them and the consequences of rushing the transition. The architecture diagram became an appendix.
That is a useful exercise even when nobody is buying your company.
Write down what would remain valuable if your interface, codebase and brand disappeared on Monday. Then identify which parts of the product protect that value today. If the answer is only “the technology,” push further. Name the contract, permission, behaviour, dataset, relationship or hard-won operating judgment that another company would struggle to reproduce.
Four years of work may still vanish from the buyer’s slide. Your job is to know which line cannot disappear with it.
Comments
No comments yet.