Key Stakeholders in a Strategic Acquisition

Not all stakeholders carry equal weight. Founders instinctively think they need to reach the CEO, but in practice most deals are shaped by two people: the internal champion and the corp dev lead.

The internal champion

The most important person in any acquisition. The champion (sometimes called the business sponsor) is the senior leader inside the acquirer who owns the business case for the deal. They might be a business unit head, a VP of Product, a CTO, or a GM. It depends on the acquirer's structure. What matters is that they have the authority and motivation to push the deal forward internally.

They build the internal business case, articulating why buying is better than building. They secure budget and resource commitment from their division. They shepherd the proposal through the acquirer's internal investment committee, fielding questions and handling pushback from other senior stakeholders. They make sure corporate development has everything they need to evaluate and execute the deal. And once it closes, they are typically accountable for making the integration succeed. In many cases the champion and the integration lead are the same person.

Without a champion willing to do all of this, a deal stalls or dies.

Corporate development

The process engine. Corp dev's mandate is to identify, evaluate, and execute acquisitions on behalf of the business. They manage the pipeline, run due diligence, negotiate terms, and coordinate across internal stakeholders.

A strategic approach can come from either direction: the corp dev team reaching out, or a potential champion making direct contact. Either route can lead to a deal. A good signal that a strategic is genuinely interested is that by the second or third meeting, the champion joins the conversation. If meetings stay confined to corp dev without a business leader getting involved, that is typically a sign that internal conviction is lacking.

Other key stakeholders

Which other stakeholders get involved depends on the size of the strategic relative to the startup and the acquirer's internal playbook for how they evaluate and execute deals.

CFO plays a pressure-testing role on valuation and deal structure. They can slow or block a deal on financial grounds, but they rarely drive one.

CTO evaluates technical architecture, code quality, and integration complexity. On technology-driven acquisitions, their endorsement can be decisive.

CEO involvement varies. On smaller deals relative to the acquirer's size, the CEO may not be closely involved at all. The decision may sit with a divisional leader or the champion's own leadership chain.

Integration lead is relevant in strategics that regularly acquire companies and have a structured playbook for doing so. A dedicated integration lead may be involved before the deal closes to assess complexity and plan the transition. In acquirers without a dedicated role, this responsibility typically falls to the champion or someone from the business unit inheriting the acquired company.

Serial vs infrequent acquirers

This framework applies regardless of how experienced the acquirer is, but the process looks different depending on whether they do this regularly.

A serial acquirer will have a dedicated corp dev team, an established investment committee process, clear evaluation criteria, and a structured integration playbook. The process is more predictable but also more formal. There are defined steps and the founder should expect to follow them.

An infrequent acquirer may not have a dedicated corp dev function at all. The CFO, head of strategy, or CEO may be playing that role alongside their day job. The process tends to be slower and less predictable, because the acquirer is figuring it out as they go. The champion becomes even more integral here. Without a dedicated corp dev function or established playbook, they are often wearing all the hats: building the business case, driving the evaluation, coordinating stakeholders, and navigating an unfamiliar process internally.

Multi-threading

Founders should aim to build relationships with both the champion and the corp dev team at their priority acquirers. These two stakeholders serve different functions, and being dependent on a single contact creates risk. If that person changes roles or leaves, the relationship can disappear overnight.

Having both threads means the relationship can survive personnel changes on either side, and it mirrors how the acquirer itself operates: the champion provides the conviction, corp dev provides the process. A founder who has a strong relationship with both is in a fundamentally better position than one who knows only a single person inside the building.