What Acquirers Actually Buy in a Startup Acquisition

The short version

What acquirers actually buy is almost never your product, and usually not even your revenue. I sold MVC to Microsoft, and I have watched acquisitions from the inside at Salesforce and elsewhere, and the pattern is consistent: a strategic acquirer buys one of four things, a capability it cannot build fast enough, a team it wants intact, a defensive block to keep you away from a rival, or time in a market where being early is everything. Founders optimize for the wrong asset constantly. They polish the product and chase revenue while the buyer's real thesis is the team or the capability. In the AI era this is shifting harder, away from codebases and toward teams and taste, because a strong team with an AI substrate can rebuild most products quickly. The codebase stopped being the moat. The judgment is.

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 are proud of the product because you built it, so you assume the product is the asset on the table.

The acquirer is running a completely different calculation. A strategic buyer does not look at your company and 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 the evidence that you can close the gap. The gap is the thing being bought.

This is why so many acquisition conversations feel like two people talking past each other. The founder is selling the painting. The acquirer is buying the ability to paint, or the painter, or the guarantee that a competitor will not get the painting. Almost never the painting itself.

“

Founders sell the painting. Acquirers buy the ability to paint, the painter, or the guarantee a rival never gets it. Almost never the painting itself.

”

The four things they actually buy

Strip every strategic acquisition down and it is one of four theses, sometimes two stacked together.

A capability. You can do something the acquirer cannot do fast enough or well enough internally. They are buying time-to-capability. The product is proof, the team is delivery, but the capability is the purchase. This was a large part of the MVC deal. The work demonstrated something Microsoft wanted to absorb into a much bigger platform, and absorbing it was faster than reinventing it.

A team. Sometimes the company is a wrapper around a group of people the buyer wants intact and pointed at a new problem. The product might get retired the week after close. The acqui-hire gets a bad reputation, but a clean team acquisition is often the most rational deal on the board, because talent that has already proven it can ship together is rare and expensive to assemble.

A defensive block. You are dangerous to someone. The acquirer is not buying you because they want you, they are buying you because they cannot afford for a competitor to have you. This is the deal that looks irrational from the outside and is perfectly rational from inside the chessboard. The value is entirely in denial.

Time. In a market where being early decides the winner, an acquirer buys a head start. Not your capability, not even your team specifically, but the months or years you would cost them to catch up. This is most of what drives the frantic AI acquisitions happening right now.

Notice what is not on the list. The standalone product as a product. The revenue as revenue. Those are inputs to the thesis, not the thesis.

Why revenue is a sanity check, not the point

Founders fixate on revenue because it is legible and it feels like the scoreboard. For private-equity roll-ups buying cash flow, fine, revenue is the thesis. But most product founders sell to strategic acquirers, and for a strategic buyer your revenue is a sanity check, not the purchase.

Think about it from their side. A large platform company can usually generate your revenue itself once it has your capability and its own distribution. Your ARR is rounding error against their machine. What they cannot easily generate is the capability, the team, or the time. So they pay for the part they cannot replicate and treat the revenue as evidence the market is real. Optimizing your whole company to add another few points of revenue growth, when the buyer's thesis is your team, is optimizing the wrong asset. This connects to a thing I argue constantly: gross margin and business model are now the PM's job, but only if you know which number the next owner of the business actually cares about.

The mistake: optimizing the asset they are going to retire

Here is the trap, and I have watched good founders walk straight into it. They figure out, consciously or not, that they are heading toward an exit. So they pour everything into the product and the revenue ramp, because that is what they think makes a company attractive. But if the acquirer's thesis is the team or the capability, the founder just spent their last two years over-investing in the asset the buyer is most likely to retire, and under-investing in the asset the buyer is actually paying for.

If you are a capability play, you should be making that capability undeniable and genuinely hard to replicate, not adding features. If you are a team play, you should be keeping the team tight, senior, and retainable, not burning them out on a roadmap that dies at close. If you are a defensive block, you should understand exactly whose nightmare you are and make yourself more of one. If you are a time play, you should be racing, not polishing.

What AI is doing to the answer

Here is where this stops being a memoir and starts being a forecast. AI is moving the acquirable asset away from the codebase and toward the team and the taste.

The codebase used to be a moat. It took years to build, so owning it meant owning a real head start. That is collapsing. A strong team sitting on an AI substrate can rebuild most products fast, which means the code itself is depreciating as an acquisition asset. What appreciates is the thing that cannot be regenerated by a prompt: the team's judgment, the accumulated customer understanding, the taste about what is worth building. This is the same constraint shift I keep returning to in the old PM versus product builder argument. When build capacity goes to near-zero, the scarce, buyable thing is the judgment that aims it.

So the dominant acquisition pattern is tilting toward small, high-taste teams. Acqui-hires of five to fifteen people with a proven sense for a hard problem, where the buyer expects to retire the product and keep the brains. At Falkster.AI I am building with this explicitly in view. The substrate is rebuildable. The listening agents that extract real customer outcomes, the loop from outcome to same-day prototype, the judgment encoded in how we decide what to build, that is the part that would survive any acquisition thesis, because it is the part code cannot regenerate.

“

Code used to be the moat, so code was the asset. AI made code rebuildable. Now the buyable thing is the judgment a prompt cannot regenerate.

”

Pick one thing to try

This week, write down the one-sentence thesis you think your most likely acquirer would actually have. Not your pitch, theirs. "They would buy us for our ___." Force yourself to pick exactly one of the four: capability, team, defensive block, or time. Then look at where your last quarter of effort went and ask whether it built that asset or a different one. If you have been pouring energy into the product and revenue while your real thesis is the team, you are optimizing for an exit that does not match the deal anyone will offer you. Fix the mismatch now, while you still have time to build the thing they are actually going to buy.

Sources: Harvard Business Review, on the real drivers of acquisition value · a16z, on acqui-hires and team-driven M&A in the AI era · First Round Review, on founder exit strategy