I sold a company to Microsoft. People assume that means Microsoft wanted my product. Microsoft did not especially want my product. It wanted what the product proved we could do, and it wanted the people who could do it again. Understanding the difference is the single most valuable thing I know about M&A, and almost no founder believes it until the term sheet contradicts their pitch deck.
Founders sell the deck. Acquirers buy the thesis.
When you go into an acquisition conversation, you bring your story: the product, the vision, the traction, the revenue ramp. You assume the product is the asset on the table. The acquirer is running a different calculation. A strategic buyer does not think "I want to own that product." It thinks "what specific gap in my position does this close, and is buying you cheaper than building it myself." The product is just evidence you can close the gap. The gap is the thing being bought. The founder is selling the painting. The acquirer is buying the ability to paint, the painter, or the guarantee a rival never gets it.
The four things they actually buy
Strip every strategic acquisition down and it is one of four theses, sometimes two stacked. A capability: you can do something the acquirer cannot do fast enough or well enough internally, and they are buying time-to-capability. This was a large part of the MVC deal, because the work demonstrated something Microsoft wanted to absorb into a bigger platform, and absorbing it was faster than reinventing it. A team: the company is a wrapper around a group the buyer wants intact and pointed at a new problem, and the product might get retired the week after close. A defensive block: you are dangerous to someone, and the value is entirely in denial, keeping a competitor from having you. And time: in a market where being early decides the winner, the buyer purchases the months or years you would cost them to catch up, which drives most of the frantic AI acquisitions right now. What is not on the list: the standalone product as a product, and the revenue as revenue. Those are inputs to the thesis, not the thesis.
The mistake and the AI shift
Here is the trap I have watched good founders walk into. They sense they are heading toward an exit, so they pour everything into the product and the revenue ramp. But if the acquirer's thesis is the team or the capability, they just spent their last two years over-investing in the asset the buyer is most likely to retire. If you are a capability play, make the capability undeniable and hard to replicate, not add features. If you are a team play, keep the team tight, senior, and retainable. If you are a defensive block, understand exactly whose nightmare you are. If you are a time play, race.
AI moves the acquirable asset away from the codebase and toward the team and the taste. The codebase used to be a moat because it took years to build. A strong team on an AI substrate can rebuild most products fast, so the code depreciates while the judgment, customer understanding, and taste appreciate. At Falkster.AI the substrate is rebuildable; the listening agents, the outcome-to-prototype loop, and the judgment encoded in how we decide what to build are the parts that would survive any acquisition thesis. This week, write down the one-sentence thesis your most likely acquirer would actually have, force yourself to pick one of the four, and check whether your last quarter built that asset or a different one.