An acquisition approval memo should make a decision easier to examine, not merely easier to approve.
It is the point where Corporate Development converts months of conversations, models and diligence into a record of what management believes, what remains uncertain and who will own the outcome.
A strong memo allows a decision-maker to understand the case without attending every workstream. It also preserves the original thesis so the company can test it after closing rather than rewriting it around the result.
Start with the decision being requested
The first page should state exactly what management wants approved: continued evaluation, an indication of interest, exclusivity, signing authority, financing or the transaction itself.
It should then connect that request to a strategic need:
- 01What must the company be able to do?
- 02Why does it matter now?
- 03What happens if the company does nothing?
- 04Can the capability be built internally?
- 05Could a partnership or commercial agreement solve enough of the problem?
- 06Why would ownership create additional value?
This separates enthusiasm for a target from the decision in front of the company. It also gives internal functions a common question: is acquisition the best route to the required outcome?
Put the alternatives on the same page
“Do nothing” is rarely the only alternative.
The company might build, partner, license, invest, hire a team, enter a joint venture or wait. Each option has a different cost, speed, risk and degree of control.
The acquisition case should compare them explicitly.
| Route | Main advantage | Main limitation |
|---|---|---|
| Build | Control and internal learning | Time and execution risk |
| Partner | Speed and lower commitment | Dependency and limited control |
| License | Access to defined capability | Weak strategic ownership |
| Minority investment | Relationship and option value | Limited operating control |
| Acquire | Control, team and assets | Price, integration and irreversible risk |
The target should not win because the presentation spends 30 pages on acquisition and one bullet on every alternative.
Record each function's answer, not its attendance
Listing a function in the diligence process does not show what it concluded. The memo should record the question each function owned, its answer, remaining uncertainty and any condition attached to its support.
Each function should own a specific question.
Product
Does the acquisition change the roadmap in a way customers will value? Which product should survive? What integration is necessary, and what should remain separate?
Engineering and security
Can the technology operate at the required scale and security level? What technical debt, data exposure or architecture conflict could change the plan?
Finance
What assumptions create the return? Which are measurable? How much depends on cost reduction, revenue synergy, financing or a terminal value that the operating team does not control?
Human resources
Which people create the value? What will make them stay? Does the buyer's compensation, culture, location policy or decision structure undermine retention?
Legal
What duties, approvals, consents, restrictions and transaction risks affect whether the structure is executable?
Business-unit leadership
Who will own the result after closing? Does that person believe the operating plan, and have they accepted the resources and accountability it requires?
The point is not to collect votes. It is to discover where the thesis breaks.
Label facts, assumptions and commitments
Acquisition models often make uncertain claims look equally solid.
Corporate development should label them.
Facts are supported by current evidence: contracted revenue, headcount, customer concentration, technical performance.
Assumptions are beliefs to test: cross-sell potential, customer retention, product migration, future market growth.
Commitments are actions an internal owner agrees to deliver: integrate a product by a date, retain a team, remove duplicate cost, fund a go-to-market plan.
This distinction changes the approval conversation. A synergy without an owner is not a commitment. A management estimate is not a fact. A plausible idea is not yet part of the price the company should pay.
Put integration economics inside the valuation case
Integration is often presented after the valuation model, as though it begins once the financial decision has been made.
It belongs inside the model.
If the buyer must migrate customers, combine infrastructure, retain specialized employees and change the sales motion, those are not implementation details. They determine cost, timing and whether the revenue thesis survives.
The approval materials should identify:
- 01the integration owner;
- 02the first 100-day decisions;
- 03the critical people and customers;
- 04the systems that must connect;
- 05the parts of the target that should remain independent;
- 06the earliest measures showing whether the thesis is working.
If nobody is prepared to own the integration plan, the company is not ready to approve the acquisition.
Show how the recommendation reached this gate
The memo should show the gates already passed and the evidence required for the next one:
- 01Strategic need and alternatives
- 02Initial target fit
- 03Permission to invest in evaluation
- 04Valuation and structure range
- 05Material diligence findings
- 06Integration ownership and plan
- 07Management recommendation
- 08Board consideration and required approvals
Not every company needs this exact sequence. The record should nevertheless show when exploration became evaluation, when evaluation became recommendation and what evidence supported each move.
Early engagement does not mean allowing every function to negotiate the deal. It means preventing a late veto from an issue that could have been identified when there was still room to change course.
Preserve material disagreement
An approval memo should not manufacture unanimity. It should state where responsible leaders disagree and why. Finance may consider the revenue case too optimistic. Product may believe delay carries a larger strategic cost. Security may view remediation as possible but expensive.
Management and the board can weigh those views only if they remain visible.
A red-team section can help:
- 01Why should the company not complete this acquisition?
- 02Which assumption is most likely to be wrong?
- 03What would make the target worth materially less?
- 04What does the seller understand that the buyer may not?
- 05What will the company wish it had asked one year after closing?
The strongest corporate development leader is not the person who gets every proposed acquisition approved. It is the person whose recommendations remain credible because they are willing to stop.
End with owners and review dates
The final page should name the executive owner for each material commitment and state when the company will revisit the thesis. Thirty days may be appropriate for operating stability. One hundred days may reveal retention and integration progress. Revenue and product outcomes may take longer.
The review should compare actual performance with the assumptions used to gain approval. It should not rewrite the original thesis after the outcome is known.
This closes the learning loop. It improves future target selection, diligence and integration. It also changes the culture of approval: sponsors know the company will later examine what was promised.
Open Future Forum's existing Corporate Development events guide covers where acquisition leaders can learn across the lifecycle. This article has a narrower job: define the decision document that carries a transaction from internal recommendation to accountable execution.
Last updated: September 2, 2026
Frequently Asked Questions
Where corporate acquirers sharpen the work
Open Future Forum convenes the General Counsel, CFOs and private equity leaders who sit across from Corporate Development, and is exploring a senior in-house Corp Dev forum. Global, founded in Silicon Valley.