Valuation and Portfolio Economics

Portfolio economics tests whether the acquisition program creates value after purchase prices, integration costs, and the cost of running the program. Use consistent models across deals, then examine how the deals interact.

Finance owns valuation methods, discount rates, funding assumptions, and model approval. The framework here organizes that work; the numbers are hypothetical teaching examples, not return targets or investment recommendations.

Keep value and funding on separate schedules

At a consistent enterprise-value level, compare the target's standalone value and buyer-specific benefits with the price and costs. Discount cash flows to the same date and use compatible tax and financing assumptions.

Net value created = standalone enterprise value + present value of buyer-specific benefits − enterprise purchase price − present value of transaction and integration costs.

Do not add a benefit already included in standalone cash flows. If using equity cash flows instead, build a consistent equity model rather than mixing enterprise and equity values. Finance reconciles debt, cash, debt-like items, and other agreed adjustments when bridging to the consideration paid.

The funding schedule answers a different question: how much cash is needed, from which sources, and when? Include purchase consideration, fees, integration spending, and liquidity reserves. Avoid adding financing costs twice through both cash flows and a discount rate that already reflects financing.

Charge the program for its own costs

The following simplified example uses present values in hypothetical USD millions. Central program costs are incremental costs not already included in the deal models.

If incremental central program costs have a present value of $4 million, net program value is $5 million. Allocating those costs to deals and subtracting them again centrally would double-count them.

Now test a shared downside. If all buyer-specific benefits fall by 50%, their present value drops by $12 million. The program's net value becomes negative $7 million, before any further downside changes. The common dependency deserves more scrutiny than three isolated “base cases.”

Price the capacity constraint through scenarios

Model what actually changes when integration is delayed: benefits start later, transition costs continue, or customers leave. Do not invent a generic capacity penalty and add it to a model already reflecting those effects.

Compare sequences and identify the constrained role or system. A smaller deal with a ready integration path may create more near-term value than a larger deal competing for the same engineers.

Calculate net present value from dated cash flows. Do not average deal internal rates of return to produce a program IRR. Aggregate the relevant cash flows and calculate the program measure on that schedule.

Treat AI-driven improvements as testable assumptions

An AI-enabled roll-up may propose labor savings, better conversion, or higher service capacity. Model a specific operational change: eligible work volume, adoption, quality, exception handling, and the cost of the new process.

Time saved becomes cash savings only if staffing or external spending changes. Redeployed time needs a separate capacity or revenue case. Include model usage, data licenses, integration, security, supervision, and ongoing evaluation in the cost base.

Use pilots to inform assumptions. A successful demonstration on clean examples does not establish production economics across the acquired businesses.

Reverse the case from the seller's price

A reverse valuation shows what must happen to justify the proposed price. Run separate break-even tests for adoption, margin improvement, and timing. Change one input at a time, holding the other approved assumptions fixed. A combined scenario must state the chosen inputs; several combinations may reach the same result.

In a hypothetical model, the price might require 70% adoption by month six, with other assumptions fixed. If the pilot supports only 30%, the next decision is whether to test adoption further, revise price, or change the plan.

Finance should reproduce each result from the listed input cells. Check formulas, units, period alignment, and sensitivity direction. Keep the reverse case with the approval pack, then compare actual adoption and timing with the threshold the price required.

Continue with valuation methods and measurement and learning.