Strategic Acquisitions

In meetings where an acquisition is discussed the flow is almost always the same: first the target's product, customers and team are presented; then a slide appears saying “this much synergy once combined.” That slide should prompt one question: three months after closing, who is responsible for this company?

The answer is often silence. The decision to acquire is made with strategy, but the value is created or destroyed by integration. Most teams learn this after the signature.

This piece is about the bolt-on deals that small and mid-sized companies do: acqui-hires, technology purchases, customer-base acquisitions. The merger processes of large corporations are a different game.

When you need it

There are healthy reasons to put an acquisition on the table. Time: building a capability yourself takes twelve months and the market window is six. Talent: there is a small, excellent team you need and you cannot assemble through hiring. Customer base: a complementary product's customers are also your target audience, and buying that company is the cheapest way to reach them. Defense: if a competitor buys that asset, your position weakens.

It is too early if your core business is not yet stable, there is no owner to run integration, and your cash flow cannot absorb a mistake. An acquisition does not remove the weaknesses of the existing business; it magnifies them.

What most teams miss

The decision is usually framed as “build or buy” and the comparison is usually cost. What needs comparing is something else: what exactly you are buying. A product, a team, customers, a market window? Value disappears differently in each.

The value of an acquired company is not in the assets on the balance sheet on signing day. It is in what is still in your hands after integration.

If you bought a product, the code stays but the people who understand it can leave. If you bought a team and nobody stays, you are holding a contract. If you bought a customer base, first-year churn can be far higher than you assumed, because those customers were attached to the old founder. So the process must answer clearly: which value am I acquiring, and what carries it?

The second thing teams miss is culture. Small teams work with their own speed and autonomy. The buyer's approval processes, reporting rhythm and priorities slow that down. The best people leave in the first six months, and the reason is usually not pay; it is the loss of autonomy.

Third, the alternative teams rarely think through: a partnership. An integration or distribution agreement that delivers the same value with no transfer of ownership often gives you most of the value of the acquisition while carrying a fraction of the risk.

The playbook

1. Reduce the rationale to one sentence

“We are acquiring this team with this capability so that we reach this customer segment six months earlier.” If the sentence carries more than one value proposition, the deal has too many purposes and later nobody will know what counts as success. The sentence is also a gatekeeper: every candidate you evaluate has to serve it.

2. Put build, partner and buy side by side

Compare the time, cost and difficulty of reversal of reaching the same goal in three ways, on one page. Acquisition stays on the table only if the other two fall short on speed or control. This step often halves the deal list.

3. Identify the value carriers

Who in the target carries the value? Which three people, if they leave, make the product or the customer relationship collapse? A retention package and role clarity for them should be part of the deal. Plan introduction calls with critical customers, before signing if possible.

4. Don't make due diligence only financial

Financial and legal review is mandatory but not enough. Add technical debt, code quality, transfer terms in customer contracts, revenue quality (recurring or project-based) and customer concentration. If half the revenue comes from two customers, you are not buying a company, you are buying two contracts.

5. Design integration before signing

Write a hundred-day plan: who is responsible, which systems merge, which live separately for a while, when and how customers are told, which three outcomes count as success in the first hundred days. The integration owner can be someone other than the person who ran the deal, but must be in place before signing.

6. Return to the rationale sentence after a year

Re-read the sentence: did what we said happen? If not, why not? This reckoning is what shapes the quality of later deals. Most companies skip it and make the same mistake twice.

What to measure

• Key-employee retention. At six and twelve months; a leading indicator of whether the value carriers stayed.
• Net revenue retention (NRR) of the acquired customer base. The most honest lagging measure of whether the revenue assumption held.
• On-time completion of integration milestones. Fidelity to the plan and early drift.
• Time to reach the goal in the rationale. If the claim was “six months earlier,” how much earlier was it in reality?

Pitfalls

Buying the synergy. Synergy slides are almost always optimistic. Weight revenue synergy low and cost synergy realistically, and check whether the deal still makes sense in the worst case.

Getting carried away by price. If you create a competitive process, the price climbs and the rationale gets forgotten. Set a price ceiling and keep to it.

Leaving integration for “later.” If the acquired company stays ownerless for two or three months, that is exactly when its best people start looking elsewhere.

Turning the target founder into an ordinary employee overnight. Remove the founder's autonomy all at once and you remove the product's real engine. Narrow autonomy gradually and with explicit rules.

Start this week

1. For an acquisition idea you have, write the rationale in one sentence, and if it contains two purposes, delete one.
2. Put the partnership or integration option for the same target on half a page, comparing cost, time and reversal difficulty.
3. List the three value carriers at the target and the conditions that would keep them, and write the name of the integration owner next to the list.