Portfolio, Build-Buy-Partner, PMI & Divestitures

Branch: M&A & Corporate Strategy, the Advisory Seat (Consulting galaxy) · Node CN6.02 · Brown belt, Principal rung · ~12 focused hours · Mastery gate ≥85% + mapped case

A CEO does not decide once whether to buy a company. A good CEO, and the advisor sitting beside her, asks a smaller, harder, and far more permanent question, over and over, for as long as the company exists: of everything we currently own, what should we keep funding, what should we grow hard, what needs fixing before we trust it again, and what should we no longer own at all? And when the answer to "how do we get where we want to go" is not sitting inside anything the company already owns, there is a second permanent question behind the first one: build the capability ourselves, buy someone who already has it, or rent it through a partner? The deal-rationale and synergy work taught you to price a single deal, build and stress-test a synergy case, defend or refuse the premium a buyer must pay for control. This module assumes that work is finished, signed, and closed, and picks up everything that happens next: the recurring portfolio logic that decided a deal should happen (or that a business should be sold) in the first place, the mode-choice discipline between building, buying, and partnering, the operating mechanics of actually merging two organizations without destroying the thing you just paid for, and the mirror-image discipline of cleanly separating a business you no longer want.

Here is the sentence worth holding through the twelve hours ahead: a large and consistent body of M&A research (cited for decades across McKinsey, HBR, and academic studies) finds that a majority of acquisitions fail to earn back the premium paid for them, and the reason is overwhelmingly execution, not diligence arithmetic. The synergy case you learned to stress-test is a hypothesis. This module is the discipline that turns a hypothesis into a fact on the ground. Day 1 readiness, a hundred-day plan, a synergy tracker that tells the truth every month, a Transition Services Agreement that is a bridge and not a permanent crutch, or, when ownership no longer makes sense, the mirror-image discipline of getting out cleanly: choosing the right vehicle, planning the carve-out, and protecting the value on both sides of the split. Throughout, you will build and rebuild the portfolio of a single synthetic Indian conglomerate, Vishwas Group, and follow a single synthetic US medical-device acquisition, Thornfield MedTech, from the day its deal closes through its first year of integration, so that by the end you have run every mechanic here on a company whose numbers you built and can defend, not memorized.

One honest note before you start, stated fully in The Consulting Mind and worth a single sentence here: partner-level judgment on live capital-allocation calls compounds from hundreds of real board rooms and deals these pages cannot manufacture. What it can teach (to a real, defensible, advisory-grade bar) is the teachable floor beneath that judgment: the questions a portfolio review must ask, the frameworks that discipline a build-buy-partner call, the mechanics a PMI plan and a carve-out must both get right, and the traps that catch even experienced teams. That floor is what the gate at the end actually tests.

App link. The own/grow/fix/exit scoring and the PMI/TSA planning you practice here are the source material for this branch's mapped Case-Engine entries (CC-MNA-02 (Deccan Cement Consolidation, candidate-led, India, synthetic) and CC-STRAT-01 (Vishwas Group Portfolio Review, candidate-led, India, synthetic)) both authored in a later wave of this same workstream. Until they ship, the Applied mini-project below is the hands-on equivalent, built to the same rubric.

Learning objectives

By the end you can:

1. Run a corporate portfolio review: score a multi-business company on market attractiveness and economic return, classify each business as own, grow, fix, or exit, and defend the classification using economic profit (return − hurdle) × capital rather than a raw ROIC ranking alone, correctly distinguishing a value-destroying business with no path forward from a currently-loss-making one with a real growth option.
2. Make and defend a build-versus-buy-versus-partner decision for a needed capability, using a structured framework (capability-gap size, urgency, cash cost, integration risk, reversibility, and whether the capability is or could become a moat) rather than fashion or imitation.
3. Distinguish legal Day 1 from operational Day 1 and build a Day-1 readiness checklist across the legal, people, customer/supplier, and systems axes for a closing acquisition.
4. Design a 100-day PMI plan with a governance structure (an Integration Management Office), a sequencing logic (quick wins vs. structural moves vs. people/culture), and a synergy tracker that separates timing misses from true leakage, and diagnose a real shortfall against a baseline, initiative by initiative.
5. Explain what a Transition Services Agreement is for, price a TSA's cost and duration, and name the disciplines (a fixed exit date, cost-plus pricing, an owned accountability chain) that keep a bridge from becoming a permanent crutch.
6. Plan a divestiture or carve-out at the advisory level, name the reasons a business gets sold, choose among a trade sale, a spin-off/demerger, and an equity carve-out/IPO, and identify stranded costs, separation costs, and the clean-team/clean-room discipline a competitively sensitive separation requires, while cross-linking, never re-deriving, the finance galaxy's valuation and spin-off mechanics.
7. Choose an integration archetype on purpose (Absorption, Preservation, Symbiosis, or Holding) from the deal's strategic interdependence and organizational-autonomy needs, before close, and explain why the archetype decision is load-bearing for whether a synergy case can actually be realized.
8. (Productivity, R10.) Use AI to accelerate synergy/precedent research and to draft first-pass PMI scaffolds (100-day plans, TSA schedules, synergy trackers), while tracing every figure to a primary source and owning every judgment call yourself.

Prerequisites & connections

Builds on. CN6.01 (Deal Rationale, Synergies & Their Traps) comes directly before this one and isn't re-taught here. It built and stress-tested a synergy case (double-counting, dis-synergies, timing, cost-to-achieve) and priced the value of control from the advisory seat. Now a signed deal (or a diagnosed exit) walks in the door. The next question is how you make it real, or how you get out. CN3.02 (Corporate, Growth & Customer Frameworks) taught the BCG growth-share matrix at the business-unit level. You'll reuse the same growth-versus-position logic here, but from the corporate parent's capital-allocation seat. The question changes to "should we, the parent, keep funding this?" while the two axes stay the same. From the Finance galaxy, M2.03 (Returns on Capital Done Right) supplies the ROIC-versus-hurdle spread and the economic-profit arithmetic, (return − hurdle) × capital, which you'll apply to every business unit without re-deriving it. M4.01–M4.02 (business-model anatomy, unit economics) and M4.03–M4.05 (Porter, value chains, the five moat sources, 7 Powers) supply the competitive-position judgment behind "strong" or "weak" in the portfolio grid. They also give you the skepticism to doubt any claim that an acquired capability is a real moat and not a rentable commodity. M3.09 (DCF/comps/LBO/M&A basics) and E11.02 (M&A, Deals & Special Situations Lab) own the modeling: sources & uses, accretion/dilution, the synergy present-value method, and the full taxonomy of separation vehicles (spin-off/demerger, equity carve-out, split-off, tracking stock) with the Indian scheme-of-arrangement mechanics. M3.10 owns the valuation of a conglomerate discount (sum-of-the-parts, India's holding-company discount and its five causes). None of that math gets re-derived here. What you get instead is the advisory judgment on top of it: when to recommend a separation, which vehicle to use, and how to execute the operational split. No valuation module covers those. E11.03 (The Consulting Case-Interview Lab), the Cycle-2 taster, includes a worked M&A synergy/value-of-control example (Meghna Cement) that's the on-ramp to this whole branch. If that one held your interest, this is the deep treatment.

Feeds forward. CN7.01 (Operating Model & Org Design) and CN7.02 (Transformation Roadmaps, Program Governance & Leading the Client) pick up the general craft of running a steering committee, sequencing a transformation, and managing stakeholders up and down. The Integration Management Office and 100-day plan you'll build here are a specific, time-boxed use of that same machinery, pointed at a just-closed deal or a just-announced separation. Nothing here gates CN7 or is gated by it, because branches never gate each other in the Consulting galaxy. The ordering is only a recommendation. CN7.03 (the Partner Capstone) may hand you a case with a portfolio or PMI thread in it, and you'll have built the muscle for it here. Presenting a portfolio recommendation (the deck, the exhibit design, the storyline) belongs to M10.03 (Minto's Pyramid Principle) and the future Presentation galaxy. What you learn here is the consulting content of the recommendation. Deck craft is taught there, and wherever the line between the two matters, you'll see an explicit hand-off.

The idea to carry. A portfolio is a standing capital-allocation decision that you'll make again and again: own it, grow it, fix it, or exit it. It isn't an inheritance to defend. And every deal or divestiture that follows from that decision creates value only if someone tracks, from Day 1 onward, whether the promised synergies actually show up.

Core teaching content

The hand-off from deal-signed to deal-real

By now you hold a signed transaction and a defensible synergy number. M&A has an uncomfortable record, though, cited for decades across McKinsey, HBR and academic study. A majority of acquisitions never earn back the premium paid for them, and the overwhelming reason is integration execution. It's rarely a diligence-stage arithmetic error. The synergy case is a hypothesis about what could be true if two organizations are combined well.

Everything from here to the end decides whether that hypothesis becomes fact.

Reporting up: the hand-off to presentation and governance

Whatever the portfolio review, the build-buy-partner call or the PMI plan concludes, it has to reach a decision-maker in a form that changes their decision. How to write and structure that recommendation is taught elsewhere. Minto's Pyramid Principle and the future Presentation galaxy cover the answer-first storyline, the exhibit design and the deck craft. The transformation and governance work covers the mechanics of running the steering committee the recommendation gets delivered into (agenda design, pre-wiring, facilitating to a decision). All you need to add here is one point. A portfolio or PMI recommendation gets the same answer-first treatment as any other consulting deliverable. Lead with the own/grow/fix/exit call or the go/no-go. Back it with the economic-profit and strategic-fit evidence. Then state the risks and the next concrete step. Don't bury the recommendation under a story of how you got there.

Common mistakes & how experts think differently

1. Treating the portfolio review as an annual slide ritual. If nothing actually moves after the review (no dollars, no rupees, no headcount), it was theater. Experts insist on a named reallocation before they call the review done.
2. Ranking businesses by ROIC alone and ignoring growth or strategic optionality. Two businesses can both be below their hurdle and still deserve different calls. A young, high-growth one may be a milestone-gated Fix, while a mature, low-growth one with no path forward may be an Exit. Collapsing both into "kill anything with negative economic profit" is a beginner's error, and the own/grow/fix/exit grid exists to prevent it.
3. Choosing build, buy, or partner by imitation ("our competitor just acquired one") and skipping the framework. The right mode depends on your capability gap, urgency and cash position. Above all, it depends on whether the capability is or could become a moat for you. What was right for a competitor with a different starting position is evidence. It isn't an answer.
4. Treating Day 1 as a single celebratory day, when it's the first checkpoint of a multi-month plan. A town hall and a press release are the opening move of an integration. They don't make one.
5. Confusing legal close with operational readiness. That produces the very failures the Day-1 checklist exists to prevent: a missed payroll cycle, an un-novated customer contract, or, in antitrust-sensitive deals, real "gun-jumping" exposure from combining functions before clearance.
6. Letting a TSA run open-ended, with no fixed exit date or milestone plan. It's the most commonly cited real-world PMI and divestiture failure. Every extra month of a TSA is a month of unplanned operational entanglement and unbudgeted running cost, and there's no natural end unless the contract forced one from the start.
7. Tracking synergies only in aggregate, never by initiative. A blended "we're at 78% of plan" hides the difference between initiatives that are merely late and initiatives that are not coming, and those two need completely different management responses. Worked Example 5 is built entirely around this diagnosis.
8. Ignoring stranded costs in a carve-out. The divested unit is no longer there to help fund the shared overhead, so the group's other businesses absorb it without anyone saying so. Unless corporate is actively right-sized, that becomes a permanent, unmodeled margin drag on the businesses you kept.
9. Skipping the clean team/clean room in a competitor-adjacent carve-out. Sharing competitively sensitive data too widely before close risks antitrust exposure and hands away negotiating leverage. A firewalled process planned from signing avoids it entirely.
10. Deciding the integration archetype by culture-fit instinct, without checking what the synergy case requires. If the deal was underwritten on cost synergies, only Absorption delivers them. If it was bought for a team or a culture, heavy-handed Absorption is how you destroy the asset you just paid a premium for.
11. The "boxes-and-lines" trap, applied to PMI. Redesigning the org chart and declaring integration complete, without touching decision rights, systems or incentives, is the same failure the operating-model work warns about. A new chart drawn over old habits changes nothing real.

Look across all eleven and you'll see one thread.

An expert treats a portfolio call, a mode-of-growth choice and a PMI or carve-out plan as decisions with real capital and real people attached. Each one needs its own named evidence and its own named owner. None of them is a template to run on autopilot. A synergy number doesn't get to mark its own homework, and an integration posture gets chosen by what the deal needs to be true. Comfort doesn't come into it.

Worked examples

Worked example 1: Scoring the portfolio: Vishwas Group's four businesses (India, ₹)

Vishwas Group (synthetic, an Indian diversified conglomerate) is running a portfolio review. It owns four businesses, and the group hurdle rate is 12%, the standing India convention used throughout. Consumer Foods earns a 22% ROIC on ₹2,000 crore of capital employed and holds the #1 market position, in a market growing 4%. Specialty Chemicals earns 19% on ₹800 crore and holds a strong #2 position, in a market growing 14%. Auto Components earns 8% on ₹600 crore from a weak #4 position, in a market growing 2%. Digital Payments has ₹400 crore of capital employed and a ROIC of −5%, but its market is growing 30%. It's an emerging #2, and its loss per transaction has narrowed from ₹8 to ₹2 over eight quarters.

Solution. Step 1, economic profit per business, (ROIC − 12%) × capital. Consumer Foods: (22% − 12%) × ₹2,000 crore = +₹200 crore. Specialty Chemicals: (19% − 12%) × ₹800 crore = +₹56 crore. Auto Components: (8% − 12%) × ₹600 crore = −₹24 crore. Digital Payments: (−5% − 12%) × ₹400 crore = −₹68 crore. Now the group's blended ROIC, capital-weighted: (2,000×22% + 800×19% + 600×8% + 400×(−5%)) ÷ 3,800 = ₹620 crore ÷ ₹3,800 crore = 16.3%. That's comfortably above the 12% hurdle at the blended level, and it's the number that would let a lazy reviewer declare victory and stop looking.

Step 2: classify. Consumer Foods has a strong position and low growth, so it's an Own: harvest the cash and use it to fund the rest of the portfolio. Specialty Chemicals pairs a strong position with high growth and a healthy spread, which makes it a Grow. Feed it capital first. Auto Components has a weak position and low growth. Its economic profit is negative and getting worse, and there's no credible path to a stronger position, so it's an Exit.

Digital Payments is the trap.

It holds a weak but improving position in a high-growth market, and right now it's the largest economic-profit drag in the portfolio (−₹68 crore, worse than Auto Components' −₹24 crore). A reviewer ranking by ROIC would exit the worse number first. The right call is the opposite. Digital Payments' loss per transaction has narrowed from ₹8 to ₹2 over eight quarters, a classic J-curve as scale builds, in a market growing at 30%. So don't ask whether it's profitable today. Ask whether the curve credibly keeps bending before the capital runs out. That makes it a Fix, funded to a named milestone and a capital ceiling. It gets neither a blank check nor an exit.

Read it. Total group economic profit is +₹164 crore (200 + 56 − 24 − 68), so the group is positive overall. But that blended number, like the 16.3% blended ROIC, hides two value-destroyers. Auto Components destroys value and has no growth story. Digital Payments destroys more value today, but it has a real, evidenced growth story. Economic profit of the same sign, even of similar size, doesn't imply the same decision. Growth trajectory and a falsifiable path to fixing the spread separate a Fix from an Exit. You'll come back and execute the Exit call on Auto Components in Worked Example 4.

Worked example 2: Build, buy, or partner: Northbeam Software adds embedded payments (US, $)

Northbeam Software (a synthetic US B2B logistics SaaS company) needs an embedded-payments capability. Customers are asking for it, and a competitor just shipped it. Once live, the capability is expected to drive $6.0 million of incremental annual recurring revenue at an 80% gross margin, which is $4.8 million/year of gross profit. There are three options, judged over a 3-year decision window. Build costs $4.0 million of development over 18 months, then $1.5 million/year of maintenance, and goes live at month 18. Buy means acquiring a payments-infrastructure startup for an $18.0 million deal price plus $2.0 million of integration cost. It goes live at month 6, with a 30% chance of losing half a year of the acquired team's output to attrition during integration. Partner means white-labeling an existing payments processor for $0.4 million of integration cost. It goes live at month 3, and Northbeam gives up 35% of the resulting revenue as an ongoing rev-share.

Solution. Step 1. Build's 3-year cash view. Cost: $4.0 million (build) + 1.5 years of maintenance at $1.5 million/year (from month 18 to month 36) = $4.0m + $2.25m = $6.25 million. Benefit: 1.5 years live within the window × $4.8 million/year = $7.2 million. Net 3-year value = $7.2m − $6.25m = +$0.95 million. On top of that, Northbeam gets full, permanent ownership of the capability and any moat it builds.

Step 2: Buy's 3-year cash view. Cost: $18.0m deal + $2.0m integration = $20.0 million. Benefit: 2.5 years live × $4.8 million/year = $12.0 million, less an expected attrition haircut of 30% × (half a year's $4.8 million = $2.4 million) = $0.72 million expected loss. Net = $12.0m − $0.72m − $20.0m = −$8.72 million within 3 years. That's a clear payback loser on a naive cash view, but only if you stop counting at year 3 and ignore whatever else the acquired team and platform could do beyond this one feature.

Step 3: Partner's 3-year cash view. Cost: $0.4 million integration. Benefit before rev-share: 2.75 years live × $4.8 million/year = $13.2 million. Northbeam's captured share after the 35% rev-share = 65% × $13.2m = $8.58 million. Net = $8.58m − $0.4m = +$8.18 million. It's the fastest and cheapest option, and by far the best 3-year cash outcome. But Northbeam permanently gives up 35% of this revenue stream for as long as the partnership runs, and it builds zero differentiation, since any competitor can rent the same thing identically tomorrow.

Read it. In a pure 3-year cash race, Partner wins by a wide margin and Buy loses badly. That doesn't end the analysis. The whole decision turns on the question you keep coming back to. Does owning the payments experience build a switching-cost moat for Northbeam's customers, or is payments becoming table-stakes plumbing that every serious logistics-SaaS competitor will eventually rent identically? If it's a real differentiator, Build's modest positive 3-year value plus permanent ownership is worth far more than the naive cash comparison shows. Buy's negative 3-year payback can still be justified by the acquired team's broader optionality beyond this one feature. If it's table-stakes, Partner is simply the correct answer, and Building "to own our own tech" would mean paying for engineering pride out of the shareholders' pocket. Practice P3 drills the structured scoring version of this judgment call.

{
  "skill": "Stress-testing whether a capability being bought or partnered for is a real moat or table-stakes infrastructure",
  "use": "Ask an AI tool to lay out the moat argument on both sides — why this capability could be a durable differentiator, and why it could be commoditizing infrastructure — as a structured pro/con brief you then judge against the M4.04 moat tests yourself.",
  "tools": ["Chat assistants — Claude, ChatGPT, Gemini"],
  "prompt": "For <CAPABILITY> in <INDUSTRY>, lay out the strongest case that owning this capability builds a durable switching-cost or network-effect moat, and separately the strongest case that it is becoming commodity infrastructure every competitor will eventually have. Cite any public examples of companies that built vs. rented this kind of capability and what happened, and flag which claims are inference rather than a cited fact.",
  "verify": "Any company example or outcome claim must be traced to a named, checkable primary source before it enters your recommendation; an AI's confident moat argument is a starting hypothesis, never itself evidence. Recompute the build/buy/partner cash comparison yourself with your own numbers (Guardrail 1-5).",
  "diy": "You must be able to run the M4.04 moat tests (does the numbers test show a persistent spread; is this a real source or a false-moat imposter) yourself, unaided, before using AI to widen the argument — otherwise you cannot tell a genuinely sharp AI-drafted case from a plausible-sounding but wrong one.",
  "market": "US"
}

Worked example 3: Thornfield MedTech's Day 1 and hundred-day plan (US, $)

This one picks up where the synergy-case work left off, once a deal is signed. It's a fresh company, built to the same standard as the case you worked before. Thornfield MedTech (a synthetic US medical-device maker) has just closed its acquisition of a smaller device rival, Calibra Diagnostics (synthetic). The diligence case underwrote $28.0 million of annual run-rate synergies (cost savings plus limited cross-sell) achievable by month 24. The one-time cost-to-achieve budget is $9.0 million. Antitrust clearance has come through in most markets, though not all, so full sales-force integration is deliberately held back in the remaining markets under an interim hold-separate arrangement. Calibra's finance and payroll systems will run on a 9-month TSA from Thornfield at $0.4 million/month while the migration to Thornfield's own ERP is built.

Solution. Step 1, the cost-to-achieve budget, built up. Systems migration: $2.1 million. TSA bridge: 9 months × $0.4 million/month = $3.6 million. Severance/restructuring: $2.4 million. Advisory and legal fees: $0.9 million. Total = 2.1 + 3.6 + 2.4 + 0.9 = $9.0 million, which reconciles exactly to the diligence budget. That's the first useful habit. Treat cost-to-achieve as a sum of named line items you can track separately, and count the TSA as one of them. You don't want to discover it mid-integration as a surprise add-on.

Step 2, the synergy ramp, phased not linear. The diligence case models an S-curve: month 0, $0; month 6, $9.0 million run-rate (about 32% of the $28.0 million target); month 12, $18.0 million (about 64%); month 24, the full $28.0 million. The Day-100 checkpoint, at roughly month 3.3, targets $7.0 million run-rate, which is exactly 25% of the full target. It was picked because it's early enough to catch a problem while there's still time to fix it. Nobody chose that date for its own sake.

Step 3, Day 1 and the hundred-day sequencing. Legal Day 1: closing conditions are satisfied, and the hold-separate order is in force in the markets not yet cleared. Operational Day 1: the TSA guarantees payroll continuity, so Calibra employees are paid without interruption on Calibra's own system while the migration is built. A joint town hall is held and named leadership announced. Key customer accounts are contacted directly before any public announcement reaches them secondhand. Days 1–30: the IMO is staffed and workstream leads are named. Quick wins get done (vendor-contract consolidation, decommissioning an obviously duplicate internal tool) while the harder systems-migration and sales-force-integration work is planned in detail. Day 100: the first synergy-tracker checkpoint against the $7.0 million target, reported to the steering committee.

Read it. Every number in this plan traces to a named line item. The cost-to-achieve budget sums to what was underwritten, the TSA runs on an explicit 9-month clock, and the Day-100 checkpoint is a defined fraction of a defined target, where a weaker plan would have a vague "check-in." That traceability is what lets Worked Example 5 diagnose a real shortfall twelve months later without guessing.

Worked example 4: Executing the exit: Vishwas Group divests Auto Components (India, ₹)

Back to Vishwas Group from Worked Example 1. The group has called Auto Components an Exit. It has ₹600 crore of capital employed and a ROIC of 8%, so NOPAT = 8% × ₹600 crore = ₹48 crore, and economic profit is −₹24 crore/year. A strategic buyer agrees to an enterprise value of ₹660 crore. It's a scale auto-components consolidator that can realize procurement and logistics synergies Vishwas can't.

Solution. Step 1: stranded costs. Auto Components currently absorbs ₹40 crore/year of shared corporate overhead (group IT, HR, treasury, brand). Only ₹15 crore of that is unit-specific and separable, such as a dedicated plant IT team and the unit's own sales back-office. The remaining ₹25 crore (₹40 crore − ₹15 crore) was shared cost, and the rest of the group still has to bear it after Auto Components leaves. The group's remaining revenue is Consumer Foods ₹1,200 crore + Specialty Chemicals ₹500 crore + Digital Payments ₹250 crore = ₹1,950 crore. Against that, the ₹25 crore stranded cost is about 1.3% of remaining revenue. That's small enough to manage, but only if corporate is explicitly right-sized within a stated window, say twelve months. Left alone, it becomes a permanent, silent margin drag on the businesses Vishwas kept.

Step 2: separation costs and net proceeds. The buyer bears its own ₹18 crore IT stand-up cost after close. Vishwas, the seller, bears ₹6 crore of advisory/legal fees and ₹4 crore of key-employee retention bonuses, which guarantee a clean handoff of the plant managers the buyer needs to keep. That's ₹10 crore of total seller-side separation cost. Net proceeds to Vishwas = ₹660 crore − ₹10 crore = ₹650 crore.

Step 3, the seller-side TSA. Vishwas agrees to give the buyer's newly carved-out entity a 6-month payroll/IT TSA at ₹1.2 crore/month, priced cost-plus. That's ₹7.2 crore of fee income to Vishwas over the bridge period. Keep it on its own line, separate from the sale proceeds.

Step 4, redeploy the proceeds and close the loop from Worked Example 1. Vishwas puts the ₹650 crore of net proceeds into Specialty Chemicals, the Grow business from Worked Example 1, which earns a 19% ROIC against the 12% hurdle. Incremental economic profit = ₹650 crore × (19% − 12%) = +₹45.5 crore/year. Add the −₹24 crore/year drag that disappears with Auto Components, and the total annual economic-profit swing to the group is +₹69.5 crore (₹45.5 crore gained + ₹24 crore no longer lost). That's before you even count the one-time ₹650 crore of cash realized.

Read it. Notice why the buyer can justify ₹660 crore, which is 13.75× Auto Components' ₹48 crore NOPAT. In its hands, the same assets are expected to earn a materially higher ROIC, through synergies Vishwas could never realize on its own. That's the value-of-control argument seen from the seller's seat: sell to whoever's hands make the assets most valuable, and don't just take the first bid.

Notice too that "freeing capital" doesn't get double-counted. What actually gets redeployed is the cash proceeds of ₹650 crore. The capital-employed figure you give up isn't what moves, and Practice P2 drills that distinction again with fresh numbers.

Worked example 5: Diagnosing a synergy shortfall at month 12 (US, $)

Twelve months after close, Thornfield MedTech's synergy tracker (Worked Example 3) shows a blended run-rate of $14.0 million against the $18.0 million month-12 plan. That's a $4.0 million shortfall. Here's the initiative-level detail. Procurement/vendor consolidation was planned at $8.0 million and came in at $8.5 million, ahead of plan. Facility/back-office consolidation was planned at $6.0 million and came in at $3.0 million. The planned facility closure slipped from month 9 to month 18, because a lease-break clause took longer to negotiate than modeled. Cross-sell revenue synergy was planned at $4.0 million and came in at $2.5 million. The sales-force integration meant to cross-sell Calibra's diagnostics through Thornfield's channel hit an unmodeled dis-synergy. Overlapping territories caused comp-plan disputes between the two sales forces and delayed rep buy-in. Two named enterprise accounts churned in the confusion.

Solution. Step 1, reconcile the variance, initiative by initiative. Procurement: +$0.5 million (ahead). Facility: −$3.0 million (behind). Cross-sell: −$1.5 million (behind). Sum of variances: +0.5 − 3.0 − 1.5 = −$4.0 million, which matches the blended shortfall exactly (18.0 − 14.0 = 4.0). Always run that first check, so you know the initiative-level detail actually adds up to the headline number.

Step 2, split each shortfall into timing versus true leakage. The facility variance is entirely timing. The closure is delayed but still happening, so the full −$3.0 million is expected to land once the lease is broken. The cross-sell variance splits in two. $1.0 million is timing, because rep buy-in is delayed while the sales-force conflict is actively being resolved. The other $0.5 million is true, permanent leakage. Those two churned accounts are gone, and they won't come back however well the rest of the integration goes.

Step 3, the revised forecast. Total recoverable-but-delayed synergy = $3.0 million (facility) + $1.0 million (cross-sell timing) = $4.0 million. These should land by month 18, when the facility closure completes. Then $14.0 million actual + $4.0 million delayed = $18.0 million, so the group reaches the original month-12 target, just six months late. The one real casualty is the $0.5 million of permanent leakage. It should trigger a formal, modest downward revision of the month-24 target, from $28.0 million to $27.5 million (98.2% of the original). More important than the half-million dollars itself, it should trigger a root-cause review of why the sales-comp conflict happened. An unmonitored dis-synergy of this kind can compound if nobody fixes it at its source.

Read it. Without the initiative-level breakdown, a $14.0 million-versus-$18.0 million blended miss looks like an undifferentiated "we're behind." That invites either needless panic or dangerous complacency. The timing-only facility slip isn't a crisis. Meanwhile the $0.5 million of true leakage, and the process failure behind it, could easily get lost in an aggregate number that's "only" 78% of plan. The initiative-level tracker that Worked Example 3 set up from Day 1 is what makes this shortfall something you can act on.

Worked example 6: Choosing the integration archetype: Talwar Fintech acquires PayLoop (India, ₹)

Talwar Fintech (a synthetic Indian digital-lending platform) acquires PayLoop (a synthetic 22-person payments-API startup). Talwar is buying it for its engineering team and its real-time settlement technology. There's no cost-synergy or scale case at all. Together they give Talwar an 18-month shortcut to market compared with building the capability in-house. The acquisition price is ₹42 crore, with ₹10 crore held back over two years. That holdback pays out only if at least 80% of the 22 engineers stay employed and named milestones are hit.

Solution. Step 1, place the deal on the interdependence-versus-autonomy grid. Strategic interdependence needed is high. Talwar needs PayLoop's settlement engine woven into its core lending product soon, and it can't be left standing alone. Organizational autonomy needed is also high. The 22-person team's value is inseparable from how it works today, and a heavy-handed Day-1 org-chart merge risks the very attrition the ₹10 crore retention earnout was structured to prevent. High interdependence and high autonomy puts the deal in the Symbiosis quadrant, the hardest of the four to execute. There are two wrong calls here. One is naive Absorption, merging the org chart immediately. The other is naive Preservation/Holding, where you leave PayLoop alone and hope the technology integrates itself.

Step 2, quantify the cost of getting it wrong. Suppose a rushed Absorption triggers 40% attrition among the 22 engineers within six months. That's a real risk for a tight-knit team suddenly folded into a much larger organization, and it means losing roughly 9 engineers. Replacement cost is ₹35 lakh each (recruiting plus ramp-up, realistic for senior fintech engineers). So 9 × ₹35 lakh = ₹3.15 crore in direct replacement cost alone.

Step 3, see why the direct cost is the smaller number. The ₹3.15 crore replacement cost is real, but the strategic cost dwarfs it. The settlement expertise of those engineers was the entire ₹42 crore deal rationale. Lose them and you delay or kill the capability Talwar paid for in the first place. That loss is much larger and harder to price than the replacement bill, and it's the one the retention earnout was specifically structured to prevent.

Read it. Symbiosis is the right call. Integrate the settlement engine's specific technical interfaces quickly, since that's the interdependence Talwar needs. Leave the team's management structure and day-to-day working rhythm substantially intact for twelve to eighteen months, and let the two converge gradually as trust and shared results build. The example also shows a design point beginners miss. A retention earnout only works if the integration archetype actually protects the conditions the earnout assumes. People tend to stay because their environment didn't change abruptly out from under them. A bonus on the table isn't enough by itself. Choosing Absorption here would sabotage the very retention mechanism the deal structure was built around.

Practice set

Work each problem fully before you read its solution. Currency figures are synthetic and internally consistent unless a real filing is explicitly named. India uses a 12% hurdle rate throughout, the standing convention, unless a problem says otherwise.

P1 (guided). Classify a fresh portfolio. Malhar Industries (synthetic, India) owns three businesses at a 12% hurdle: Textiles (capital employed ₹500 crore, ROIC 9%, market growth 3%, weak position), Packaging (capital employed ₹700 crore, ROIC 17%, market growth 6%, strong position), and Renewable Power (capital employed ₹900 crore, ROIC 13%, market growth 20%, emerging but improving position). Compute each business's economic profit and classify it as Own, Grow, Fix, or Exit.

Solution. Textiles: (9% − 12%) × ₹500 crore = −₹15 crore. Its position is weak and its growth low, with no offsetting growth story, so it's an Exit. Packaging: (17% − 12%) × ₹700 crore = +₹35 crore. A strong position, moderate-to-good growth and a healthy spread make it a Grow, so fund it first. Renewable Power: (13% − 12%) × ₹900 crore = +₹9 crore. The spread is thin, but growth is high (20%) and the position is improving, so it's also a Grow, funded to build position while the market is still forming. It's different from a blank-check Fix because the spread, thin as it is, is already positive.

P2 (guided). Redeploy the exit proceeds. Malhar sells Textiles (from P1) for a ₹400 crore enterprise value, less ₹20 crore of seller-side separation costs. It redeploys the net proceeds into Packaging (17% ROIC, 12% hurdle). Compute the net proceeds, the incremental economic profit from redeployment, and the total annual economic-profit swing versus keeping Textiles.

Solution. Net proceeds = ₹400 crore − ₹20 crore = ₹380 crore. Incremental economic profit from redeploying into Packaging = ₹380 crore × (17% − 12%) = ₹380 crore × 5% = +₹19 crore/year. Textiles' −₹15 crore/year drag also goes away, so the total annual swing = ₹19 crore + ₹15 crore = +₹34 crore/year. That's before you count the one-time ₹380 crore of cash realized.

P3 (independent). Score a build-buy-partner decision with weights. An Indian NBFC needs a video-KYC capability. It weights the decision Speed 30%, Cost 20%, Control/Differentiation 25%, Integration risk 15%, Reversibility 10% (1–5 scale, 5 = best). Scores: Build (2, 3, 5, 5, 2); Buy (4, 2, 4, 2, 1); Partner (5, 5, 1, 4, 5). Compute each option's weighted score and recommend. Then re-weight with Control/Differentiation raised to 40% (Speed cut to 20%, Cost to 15%, others unchanged) and recompute. What does the shift teach you?

Solution. First weighting: Build = 0.30(2) + 0.20(3) + 0.25(5) + 0.15(5) + 0.10(2) = 0.6+0.6+1.25+0.75+0.2 = 3.40. Buy = 0.30(4) + 0.20(2) + 0.25(4) + 0.15(2) + 0.10(1) = 1.2+0.4+1.0+0.3+0.1 = 3.00. Partner = 0.30(5) + 0.20(5) + 0.25(1) + 0.15(4) + 0.10(5) = 1.5+1.0+0.25+0.6+0.5 = 3.85. Partner wins. Re-weighted (Control 40%, Speed 20%, Cost 15%): Build = 0.20(2)+0.15(3)+0.40(5)+0.15(5)+0.10(2) = 0.4+0.45+2.0+0.75+0.2 = 3.80. Buy = 0.20(4)+0.15(2)+0.40(4)+0.15(2)+0.10(1) = 0.8+0.3+1.6+0.3+0.1 = 3.10. Partner = 0.20(5)+0.15(5)+0.40(1)+0.15(4)+0.10(5) = 1.0+0.75+0.4+0.6+0.5 = 3.25. Build now wins. So the framework won't hand you a mechanical answer. The weights themselves are a strategic judgment call about whether video-KYC is table-stakes infrastructure (favoring Partner) or a differentiator worth owning (favoring Build). Getting the weights wrong before you score is a more dangerous error than any arithmetic slip in the scoring itself.

P4 (independent). Size and time-box a TSA. A carve-out needs an IT migration that will cost $1.4 million and take a minimum of 5 months to build no matter what. A TSA to bridge the gap costs $0.25 million/month. Compute the cost of running the TSA for exactly the 5 months migration requires, and explain why the TSA contract should be capped near that duration and not left open-ended.

Solution. 5 months × $0.25 million/month = $1.25 million. That's cheaper than the $1.4 million migration build itself, which confirms the TSA is clearly worth running for the unavoidable 5-month build window. But every month beyond month 5 costs another $0.25 million with zero migration progress to show for it. The migration is either done by month 5 or it isn't, and a TSA extended past that point is pure unbudgeted cost. It's no longer building a bridge to anything. So the contract should fix an exit date at month 5–6, or just past it to allow a buffer for slippage. Leaving the relationship open-ended defeats the purpose.

P5 (independent). Compute a stranded cost. A divested unit currently absorbs ₹18 crore/year of shared corporate overhead; only ₹7 crore is unit-specific and separable. The remaining group's revenue after the divestiture is ₹2,600 crore. Compute the stranded cost and express it as a percentage of remaining group revenue.

Solution. Stranded cost = ₹18 crore − ₹7 crore = ₹11 crore. As a percentage of remaining group revenue: ₹11 crore ÷ ₹2,600 crore = 0.42%. That's small in isolation, but it's a real, permanent drag on the businesses that remain unless corporate overhead is explicitly right-sized within a stated window.

P6 (independent). Diagnose a second synergy shortfall. By month 9, a PMI plan targeted IT consolidation $5.0 million, headcount consolidation $3.0 million, and cross-sell $2.0 million (total $10.0 million). Actuals: IT $5.2 million, headcount $1.5 million (the delay is a known timing issue, a facilities lease renegotiation), cross-sell $1.0 million (of which $0.6 million is timing and $0.4 million is judged permanent leakage). Reconcile the variance and state the revised near-term forecast.

Solution. Variances: IT +$0.2 million (ahead); headcount −$1.5 million (behind, all timing); cross-sell −$1.0 million (behind, split $0.6 million timing / $0.4 million leakage). Sum: 0.2 − 1.5 − 0.6 − 0.4 = −$2.3 million, which matches the actual-versus-plan gap ($7.7 million actual vs. $10.0 million plan). Recoverable/delayed total = $1.5 million (headcount) + $0.6 million (cross-sell timing) = $2.1 million. Once it lands, the tracker should reach $7.7 million + $2.1 million = $9.8 million. That's just short of the original $10.0 million plan by exactly the $0.4 million of true leakage. The leakage is the number that should trigger a target revision and a root-cause review. The headline $2.3 million gap shouldn't.

P7 (independent). Bucket a Day-1 checklist. Sort these six items into the four Day-1 axes (legal/regulatory, people, customer/supplier, systems/finance). (a) Send a direct communication to the ten largest customer accounts before any public announcement. (b) Confirm the hold-separate order's exact scope with counsel. (c) Verify the first post-close payroll cycle will run without interruption. (d) Announce the go-forward leadership names, even if not every seat is filled. (e) Confirm supplier payment terms are unaffected by the change of control. (f) Set up access controls for the newly combined IT environment.

Solution. Legal/regulatory: (b). People: (d). Customer/supplier continuity: (a), (e). Systems/finance: (c), (f). Why bother sorting? A Day-1 plan that's strong on only one axis isn't ready. A great town hall with no verified payroll continuity, say, still fails. All four axes have to clear independently.

P8 (independent). Place two deals on the archetype grid. (i) A packaged-goods company acquires a direct regional competitor purely to shut down duplicate plants and combine distribution routes. (ii) A software company acquires a five-person team for a novel machine-learning technique it needs woven into its core product within two quarters, but the team has already stated they will leave if forced into the acquirer's standard engineering process. For each, name the interdependence level, the autonomy level, and the resulting archetype.

Solution. (i) Interdependence is high, because the entire thesis is combining plants and routes. Autonomy need is low. No distinct culture or team is being preserved for its own sake. That makes it Absorption. (ii) Interdependence is high (the technique must be integrated fast) and so is the autonomy need (the team will walk under standard process). That's Symbiosis: integrate the specific technical deliverable quickly while preserving the team's working structure, the same pattern as Worked Example 6.

P9 (independent). Match the divestiture vehicle to the situation. For each situation, name the best-fit vehicle (trade sale, spin-off/demerger, or equity carve-out/IPO) and say why. (i) A mature, low-growth, weak-position industrial unit the board wants to exit entirely and convert to cash. (ii) A fast-growing, well-differentiated digital unit trapped inside a low-multiple industrial parent, with activist pressure to unlock its value. (iii) A promising but capital-hungry unit the parent wants to keep partial exposure to while raising cash and establishing a market price.

Solution. (i) Trade sale. A strategic buyer can pay a control premium justified by synergies the seller can't realize, and there's no standalone growth story to re-rate as public equity. (ii) Spin-off/demerger. Pure-play re-rating is the whole mechanism of value creation here, and no cash needs to change hands. It's the textbook case of unlocking a conglomerate discount. (iii) Equity carve-out/IPO. It raises cash and sets a market price while the parent keeps control and continued exposure, which is the "test the market, keep the option" case.

P10 (independent). Diagnose a clean-team failure. During diligence for a divestiture, a seller's finance team shares detailed, unredacted customer-level pricing data directly with the buyer's commercial team (a direct competitor of one of the seller's other, non-divested businesses) before signing, with no firewall in place. Name what is wrong and the fix.

Solution. Two distinct risks are live at once. The first is antitrust "gun-jumping" exposure, since competitors are effectively coordinating on commercially sensitive information before any clearance. The second is a loss of negotiating leverage and competitive exposure for the seller's other business, whose sensitive pricing the buyer's commercial team has no legitimate need to see. The fix is a clean team/clean room. A small, named group bound by strict protocols is the only one allowed to access the sensitive data needed to negotiate this deal. Everything else stays firewalled until close, and antitrust-sensitive items stay firewalled until clearance.

P11 (independent). Read a conglomerate discount. A group's market capitalization is ₹45,000 crore; a sum-of-the-parts build using each segment's own peer multiples implies ₹63,000 crore of value. Compute the discount. Then, using the five causes of a holding-company discount, say what you'd check before concluding it's a real, sticky holding-company-style discount that can't be closed.

Solution. Discount = (₹63,000 crore − ₹45,000 crore) ÷ ₹63,000 crore = 28.6%. Before you call it sticky, check the five causes. Cause 1 is whether cash from the segments actually flows up to shareholders, or a promoter/parent structure keeps it. Cause 2 is real tax friction on distribution or on a hypothetical sale. Cause 3 is a governance/agency history of value moving away from minority holders. Cause 4 is an illiquid stock with high insider ownership. Cause 5 is the decisive one: whether there's any credible catalyst (an announced demerger, a buyback, a regulatory push), or whether the discount is open-ended with "no terminal event." A discount with a live catalyst is a spin-off/carve-out candidate. A discount with none of the five causes addressed is a description, and you shouldn't mistake it for a thesis.

P12 (independent). Value of control from the seller's seat. An asset earns 10% ROIC on ₹300 crore of capital under its current owner. Buyer P, a financial buyer with no operating synergies, can only sustain the same 10%. Buyer Q, a strategic buyer with adjacent operations, can achieve 16% ROIC on the same capital through procurement and distribution synergies. Compute each buyer's NOPAT and explain, using the value-of-control logic, why Buyer Q is both the higher bidder and the "right" buyer.

Solution. NOPAT under Buyer P = 10% × ₹300 crore = ₹30 crore. NOPAT under Buyer Q = 16% × ₹300 crore = ₹48 crore, a difference of ₹18 crore/year. Buyer Q can justify paying meaningfully more than Buyer P because, in Buyer Q's hands, the identical assets are worth more. That's the value-of-control argument seen from the seller's seat. The "right" buyer is whoever's hands make the assets earn the most, because that buyer both can and should pay the highest defensible price. A buyer who values the asset the way you currently run it isn't that buyer.

P13 (independent). Decide a retention pool. A 15-person team includes 6 "critical" members. Without a retention plan, an expected 3 of the 6 critical members would leave within a year; replacing each costs ₹40 lakh. A proposed retention bonus pool costs ₹15 lakh per critical member (all 6). Compute the expected replacement cost, the retention pool cost, and recommend.

Solution. Expected replacement cost = 3 × ₹40 lakh = ₹1.2 crore. Retention pool cost = 6 × ₹15 lakh = ₹0.9 crore. The retention pool is cheaper on direct cost alone (₹0.9 crore vs. ₹1.2 crore), so fund it. That comparison even leaves out the harder-to-price strategic cost of losing the very people the deal's thesis depended on, which only strengthens the case. It's the same lesson as Worked Example 6.

P14 (independent). Build a cost-to-achieve budget. Components: systems $1.2 million, severance $0.8 million, advisory $0.5 million, facilities exit $0.3 million. Compute the total and each component's share.

Solution. Total = 1.2 + 0.8 + 0.5 + 0.3 = $2.8 million. Shares: systems 1.2/2.8 = 42.9%; severance 0.8/2.8 = 28.6%; advisory 0.5/2.8 = 17.9%; facilities 0.3/2.8 = 10.7% (sums to 100%, allowing for rounding). Publish the breakdown along with the total. It lets a steering committee spot an overrun in a specific line before it inflates the whole budget unnoticed.

P15 (independent). Explain the "before close" rule. In two or three sentences, explain why the integration archetype (Absorption, Preservation, Symbiosis, Holding) must be decided before a deal closes instead of being allowed to emerge during the first months of integration.

Solution. The archetype decides whether the deal's own synergy case can be realized at all. If the case was underwritten assuming full cost integration, only Absorption delivers it, and drifting into Preservation for comfort means the promised synergies simply never show up. If the deal was bought for a team or culture that needs protecting, an emergent, ad hoc Absorption (the default behavior of most acquirers under time pressure) risks destroying the asset before anyone has decided otherwise. Left emergent, the archetype gets chosen by whoever happens to be loudest in the first messy month, which is backwards, because it should follow what the deal requires.

P16 (timed, 30 minutes: integrative). The full sequence on Bhairav Industries. Bhairav Industries (synthetic, India, 12% hurdle) has three segments: Steel (capital employed ₹1,500 crore, ROIC 7%, growth 2%), Specialty Coatings (capital employed ₹600 crore, ROIC 21%, growth 12%), and Logistics (capital employed ₹900 crore, ROIC 13%, growth 8%). (a) Compute each segment's economic profit and the group total, and classify each segment. (b) Steel faces no antitrust pressure and has no standalone growth story; Coatings is fast-growing and differentiated. If a divestiture is called for, name the best-fit vehicle and why. (c) A strategic buyer for Steel can achieve 11% ROIC on the same ₹1,500 crore of capital through raw-material and logistics synergies. Compute the NOPAT gap between Bhairav's own economics and the buyer's, and explain what it implies about the achievable sale price.

Solution. (a) Steel: (7% − 12%) × ₹1,500 crore = −₹75 crore. It has a weak position in a low-growth market with no path forward, so it's an Exit. Coatings: (21% − 12%) × ₹600 crore = +₹54 crore. A strong position and good growth make it a Grow. Logistics: (13% − 12%) × ₹900 crore = +₹9 crore. With a modest spread and decent growth, it's a selective Grow, or at minimum an Own-and-monitor if capital is scarce and Coatings is the clear priority. Group total economic profit = −75 + 54 + 9 = −₹12 crore. The portfolio as a whole is destroying value right now, entirely because of Steel. (b) Steel, the Exit candidate, has no standalone growth story to re-rate and no antitrust pressure forcing a fast sale. A trade sale to a strategic buyer who can realize synergies Bhairav can't is the right vehicle, mirroring Worked Example 4. Coatings, by contrast, has the profile (fast-growing, differentiated, trapped under a discounted parent multiple) that would suit a future spin-off/demerger if Bhairav ever chose to separate it. Nothing here calls for that yet, since Coatings is classified Grow. (c) Bhairav's own NOPAT on Steel = 7% × ₹1,500 crore = ₹105 crore. The strategic buyer's prospective NOPAT = 11% × ₹1,500 crore = ₹165 crore, a gap of ₹60 crore/year. That gap is why the buyer can justify paying a real control premium above what Steel's economics justify under Bhairav's ownership. The assets are worth more in the buyer's hands, so anchor the achievable sale price to the buyer's prospective economics. Bhairav's own sub-hurdle numbers are the wrong anchor.

Applied mini-project: the portfolio memo

The assignment. Produce a one- to two-page, answer-first memo that runs the full sequence you've learned here on a multi-business company of your choosing. Use Minto's Pyramid Principle for the structure. That craft is taught on its own and isn't repeated here.

Choose one path.

• Path A: extend the synthetic dataset. Vishwas Group (Worked Examples 1, 4, and 6) gains two more businesses for this project: Vishwas Real Estate (capital employed ₹1,100 crore, ROIC 10%, market growth 5%, weak-to-middling position) and Vishwas Renewable Energy (capital employed ₹500 crore, ROIC 6%, market growth 25%, early but improving position, loss-adjusted margin improving each quarter). Combine these with Consumer Foods, Specialty Chemicals, and Digital Payments from Worked Example 1 (Auto Components has already been divested per Worked Example 4) for a five-business portfolio.
• Path B, a real company. Find a real, publicly listed multi-segment company with at least three reported segments. In India that's any BSE/NSE-listed diversified group that reports business segments in its notes to accounts. In the US, use any multi-segment company's 10-K segment footnote. Use its actual disclosed segment revenue and, where available, segment-level margin or capital data as your inputs. Cite the filing, and make sure every number is real and pulled in-session.

Do this, in order. (1) Score each business or segment on market attractiveness and competitive/economic position. Compute economic profit for each using a stated hurdle rate (researched or reasonably assumed and disclosed). Classify each one Own, Grow, Fix, or Exit, and justify any Fix or Exit call with more than a ROIC ranking. (2) For any business classified Exit, name the best-fit divestiture vehicle (trade sale, spin-off/demerger, or equity carve-out). Then name the biggest carve-out risk you'd flag first: stranded cost, clean-team need, or TSA dependency. (3) For any business that needs a new capability to execute its Grow or Fix plan, make the build/buy/partner call with the weighted-scoring framework, and state your weights explicitly. (4) Sketch a Day-1-plus-hundred-day skeleton for one hypothetical deal or divestiture that comes out of your recommendation. Include one named synergy-tracking metric you'd watch monthly, and say whether you expect it to be a real differentiator (favoring Absorption/Build) or table-stakes integration (favoring a lighter-touch archetype or Partner). (5) Write the whole thing answer-first: the governing recommendation in the first line, then the supporting evidence, then risks and the next concrete step.

Grading rubric (score each component 0/1/2: 0 = absent or wrong, 1 = present with gaps, 2 = professional). (a) Classification grounded in economic profit instead of a raw ROIC ranking. (b) Strategic-fit/growth-trajectory reasoning present for any Fix-versus-Exit call, beyond the number alone. (c) Divestiture-vehicle logic correctly matched to the situation. (d) Build/buy/partner framework applied with explicit, defensible weights. (e) Day-1/hundred-day skeleton plausible and correctly sequenced (quick wins vs. structural moves vs. people). (f) Answer-first memo structure, recommendation stated in the opening line. Pass at 9/12 with no zero on any item.

Reading & resources

Use these as anchors to learn from and check your work against. Never cite them as if they were your client's own data. Everything is free unless marked, and level tags run from Beginner to Advanced.

Portfolio and corporate strategy:

• A.G. Lafley & Roger Martin, Playing to Win, the "where to play, how to win" cascade underlying own/grow/fix/exit as a strategic choice and more than a scoring grid. [Paid] [Beginner–Intermediate]
• Michael Goold, Andrew Campbell & Marcus Alexander, Corporate-Level Strategy: Creating Value in the Multibusiness Company, the source of the parenting advantage concept the portfolio lens leans on. [Paid] [Advanced]
• Richard Rumelt, Good Strategy / Bad Strategy, the diagnose-before-prescribe discipline behind refusing to let a portfolio review become a template exercise. [Paid] [Intermediate]
• Kim & Mauborgne, Blue Ocean Strategy, and Christensen's jobs-to-be-done work, useful lenses when a Grow or Fix candidate's real question is whether it is competing in the right market at all (cross-link CN3.02).

M&A execution, PMI, and separation (the modeling and valuation lives in the Finance galaxy; read there for the mechanics, here for the advisory judgment):

• M3.09 (DCF, comps, LBO, M&A basics) and E11.02 (M&A, Deals & Special Situations Lab), the synergy present-value discipline, sources & uses, accretion/dilution, and the full spin-off/carve-out/split-off/tracking-stock taxonomy with Indian scheme-of-arrangement mechanics. [In-program]
• M3.10: sum-of-the-parts and India's holding-company discount, with its five durable causes and the catalysts that have actually closed it. [In-program]
• Paul Haspeslagh & David Jemison, Managing Acquisitions: Creating Value Through Corporate Renewal, the classic Absorption/Preservation/Symbiosis/Holding integration-archetype framework behind the archetypes here. [Paid] [Advanced]
• David Maister, Charles Green & Robert Galford, The Trusted Advisor, the trust-equation discipline behind delivering a portfolio or PMI recommendation the client actually acts on (cross-link CN0.02). [Paid] [Beginner–Advanced]
• John Kotter, Leading Change: the change-management spine behind a hundred-day plan's people/culture workstream. [Paid] [Intermediate]
• Aswath Damodaran's data library: free industry multiples and base-rate references for sanity-checking a build-versus-buy comparison or an SOTP input. [Free] [Beginner–Advanced]
• Harvard Business Review: search "post-merger integration," "carve-out," and "TSA" for practitioner case studies; treat every figure as illustrative until traced to the named company's own filing. [Mixed free/paid] [Intermediate–Advanced]
• McKinsey and Bain's published M&A and PMI insight pieces, free, current treatments of Day-1 planning and separation mechanics; read for the vocabulary and checklist logic, verify any statistic before quoting it.

The canon shared across the Consulting galaxy (Minto, Conn & McLean, Rasiel, Porter, Helmer, Greenwald, Koller) is indexed once, with full free/paid and level tags, in CN0.01. The portfolio and PMI material here draws most directly on Koller's Valuation chapters on mergers, acquisitions, and divestitures. Read those if you want the full modeling detail behind what CN6.02 teaches at the advisory-judgment layer.

Teach it back & journal

Feynman prompt. A colleague has just been told "we're buying this company, and it's a great strategic fit." Explain why that sentence, on its own, tells you almost nothing useful yet. Then walk them through four questions, in order. First, is this a business we should even want to own? That's the own/grow/fix/exit call, and you score it on economic profit instead of ROIC alone. Second comes the capability question: if we need something we don't have, do we build it, buy it, or rent it. Third, once we own it, work out how to make Day 1 and the first hundred days actually work, tracked against a baseline. Fourth, if the answer eventually becomes "we shouldn't own this," plan how to get out cleanly. You'll know it worked if your colleague asks, unprompted, "how are we going to track whether the promised synergies are actually showing up, initiative by initiative?"

Then they've got the payoff: a deal's value is decided after signing, not at it.

Journal prompt. Pick one real, publicly reported acquisition, divestiture, or demerger from the last few years (Indian or US, your choice). Using only what's on the public record, write four short paragraphs. In the first, say what portfolio logic plausibly motivated it (own/grow/fix/exit, inferred from the public rationale). In the second, name the integration archetype the deal's stated rationale implies it should have used, and say whether the public record suggests it got that right. News coverage of the integration, and any reported executive departures or delays, will help here. In the third, describe what you'd have wanted to see in a synergy tracker at the twelve-month mark if you sat on the board. In the fourth, write down what you can't know from public information alone, where judgment that only compounds from being inside the deal room would matter more than anything you've learned here. Don't treat that last paragraph as a hedge. Naming clearly what a floor of structure and mechanics can't give you is itself the advisory instinct this whole galaxy is trying to build.

This module's flashcards and mastery quiz are wired into the app: see the node's Quiz and Reviews.