The Programmatic M&A Operating Model

A programmatic M&A operating model assigns people, decision rights, and recurring work to the acquisition strategy. The central team keeps the process consistent. Business leaders remain responsible for the performance of the companies they buy.

Build around the decisions that recur: where to search, when to advance, how much to commit, and whether the organization can deliver another integration.

Assign one accountable owner per decision

Different organizations distribute execution differently. A central team may run every transaction, business units may lead deals, or both may share the work. In each model, make accountability explicit.

The AI product owner needs an engineering counterpart. A prompt library without someone responsible for access, failures, and version changes becomes an unmanaged dependency.

Make each gate a real decision

Use the same basic gates across the program, with evidence requirements suited to the deal. A small acquisition can have a shorter pack without losing its decision owner.

Before outreach, confirm fit and relationship ownership. Before an indication of value or letter of intent, confirm the thesis, valuation range, and authority to communicate. Before signing, resolve critical diligence issues and confirm funding and integration readiness. Before closing, confirm the agreed conditions and Day 1 responsibilities through the relevant owners.

Record the decision, approver, conditions, supporting document versions, and expiry or reopening trigger. “Approved subject to customer reference checks” remains conditional until the owner confirms those checks.

Plan the calendar around scarce people

Count demand by skill and time period. Deal count alone hides the work. One acquisition may need a specialist engineer for twelve weeks; another may need payroll and finance support for two.

In this hypothetical capacity review, the bottleneck is technical migration.

The shortfall is seven engineer weeks. Hiring, sequencing, or reducing scope may resolve it. The sponsor must choose a funded option before both deals depend on the same capacity. Do not average the shortfall across a year when the work collides in one quarter.

Give each meeting one decision to make

A weekly pipeline meeting assigns the next action and clears stalled decisions. A monthly program review reallocates research effort, capital, and integration capacity. A quarterly strategy review examines completed, declined, and abandoned opportunities and proposes changes to the thesis.

Use a shared decision log. Meeting minutes capture conversation; the decision log records what changed and who must act. Link issues to the relevant gate instead of copying them into several disconnected trackers.

Compare each request with the last approval

Before a revised request reaches the committee, compare it with the last approved pack and its recorded conditions. Check price, funding, customer assumptions, integration timing, and key people. Name the decision owner for every change that requires renewed approval.

This hypothetical comparison turns small edits into explicit decisions.

Check for separate authorization before reopening a decision. Attach the comparison and any existing approval to the revised request. Track which assumptions repeatedly change before signing; those may need earlier diligence on the next deal.

Continue with AI system architecture, approval gates, and integration planning.