Microsoft bought my company and then killed the product. If you had asked me in the first month how I felt about that, I would have given you a wounded founder answer. If you ask me now, with two decades of hindsight, I will tell you it was the correct outcome and I am glad they did it.
The product was never the point
I built MVC. I was proud of it. So when the standalone product wound down after the acquisition, the first instinct was the one every founder feels: they are killing my baby, the suits do not understand, integration ruins everything good. That instinct is almost entirely ego. Here is what I missed in the moment. Microsoft did not acquire us for the standalone product. It acquired the capability, the thing the product proved we could do, so it could put that capability inside a platform that reached orders of magnitude more developers than we ever would. The product was the demonstration. The capability was the asset.
Once you see that, killing the standalone stops looking like vandalism and starts looking like focus. Why keep running a separate product, brand, roadmap, and support surface when the entire value is now sitting inside a machine that reaches a thousand times more people? The standalone was overhead. The kill was the parent concentrating the value where it would actually compound.
Distribution beats roadmap, almost always
When the acquirer's distribution matters more than your roadmap, killing the standalone is the right call. Run the math on my case. The standalone reached a certain audience. The platform it got absorbed into reached a staggeringly larger one. If I had won the political fight to keep the product alive separately, I would have protected my brand and my pride and starved the capability of the exact distribution that made the acquisition worth doing. Most founders make that trade, win a hollow version of the fight, and spend the earnout years running a side product nobody at the parent cares about, slowly losing the influence they could have kept by championing the integration instead.
The honest test
There is a comfortable industry story: big company acquires startup, big company ruins startup, founder leaves bitter. Sometimes it is true, when a great product with its own real distribution gets killed by a clumsy parent who then fails to integrate the capability either. But far more often the "ruined" product was a wrapper around a capability, the capability survived and scaled inside the parent, and the only thing that died was the founder's name on the door. The honest test is the one nobody wants to run on their own deal: after the kill, did the value reach more customers or fewer? Not did the brand survive, not did the founder feel respected. Did the actual thing customers wanted reach more of them? In my case it was not close.
The same logic now governs AI features absorbed into platforms, and the same ego resists it. At Falkster.AI I am building with this fully internalized: the listening agents and same-day prototypes are capabilities, and if the right outcome someday is to push a capability into a partner's distribution and retire a standalone surface, that is a win for the customer, not a wound to my pride. This week, take the product you are most attached to and run the honest test: if a platform with ten times your distribution absorbed the capability and killed your standalone tomorrow, would the value reach more customers or fewer? Write the answer down.