<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0"><channel><title><![CDATA[The Industrialist: Target Selection & Diligence]]></title><description><![CDATA[How uncertainty is managed before a deal closes. This section examines target selection as a design decision under constraint, focusing on fit, distance, integrability, and sequencing—long before integration begins.]]></description><link>https://www.theindustrialist.ca/s/target-selection-and-diligence</link><image><url>https://substackcdn.com/image/fetch/$s_!yIZh!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F16d1b5d2-add7-4321-b44b-3c22086f05c1_512x512.png</url><title>The Industrialist: Target Selection &amp; Diligence</title><link>https://www.theindustrialist.ca/s/target-selection-and-diligence</link></image><generator>Substack</generator><lastBuildDate>Sat, 04 Jul 2026 08:34:15 GMT</lastBuildDate><atom:link href="https://www.theindustrialist.ca/feed" rel="self" type="application/rss+xml"/><copyright><![CDATA[David Carr]]></copyright><language><![CDATA[en]]></language><webMaster><![CDATA[industrialist@substack.com]]></webMaster><itunes:owner><itunes:email><![CDATA[industrialist@substack.com]]></itunes:email><itunes:name><![CDATA[David Carr]]></itunes:name></itunes:owner><itunes:author><![CDATA[David Carr]]></itunes:author><googleplay:owner><![CDATA[industrialist@substack.com]]></googleplay:owner><googleplay:email><![CDATA[industrialist@substack.com]]></googleplay:email><googleplay:author><![CDATA[David Carr]]></googleplay:author><itunes:block><![CDATA[Yes]]></itunes:block><item><title><![CDATA[Fit Is Not Compatibility]]></title><description><![CDATA[Why familiar targets often increase integration risk rather than reducing it. Fit as interaction risk under constraint, not as similarity to the platform.]]></description><link>https://www.theindustrialist.ca/p/fit-is-not-compatibility</link><guid isPermaLink="false">https://www.theindustrialist.ca/p/fit-is-not-compatibility</guid><dc:creator><![CDATA[David Carr]]></dc:creator><pubDate>Thu, 25 Jun 2026 14:02:17 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!yIZh!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F16d1b5d2-add7-4321-b44b-3c22086f05c1_512x512.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Target selection discussions frequently revolve around fit: is the target culturally compatible, does it operate in a familiar way, will it integrate smoothly with the platform? Those questions feel sensible, they appeal to experience rather than abstraction, and they reassure decision-makers that complexity is being managed rather than invited.</p><p>In practice, target selection rarely begins with a blank slate. Most acquisition decisions get made from a narrow, time-bound <a href="https://industrialpatterns.com/add-on-density-atlas">set of available options shaped by market conditions</a>, seller readiness, and timing more than by strategic ideals. Within those constraints, fit becomes less about choosing the perfect company and more about interpreting imperfect options correctly, which is where compatibility starts becoming dangerous in ways that are hard to see at the time.</p><h2><strong>The seduction of familiarity under constraint</strong></h2><p>Compatibility is attractive precisely because it feels legible. When options are limited, familiar operating models, overlapping customers, similar leadership profiles, and shared language provide a sense of orientation that reduces cognitive load at the moment decisions have to be made.</p><p>From the outside, these deals appear prudent, described as &#8220;low-risk,&#8221; &#8220;obvious,&#8221; or &#8220;clean.&#8221; From inside the platform, they also lower resistance: leaders expect fewer surprises, teams assume integration will be incremental. In constrained environments, familiarity feels not just safe but responsible. That is exactly what makes it risky.</p><p>Compatibility reduces visible friction while quietly increasing what&#8217;s worth calling structural coupling, the degree to which two organisations become dependent on shared decisions, shared timing, and shared judgment earlier than <a href="https://www.theindustrialist.ca/p/integration-capacity-is-the-binding">the system can reliably support</a>. Fit is about how the two interact once joined, not about how similar they look beforehand.</p><h2><strong>Fit as interaction risk</strong></h2><p>Because acquisition choice sets are constrained, the critical error is usually less in which target gets selected than in how that target gets framed in the room where the decision is made. In buy-and-build systems, fit is better understood as <a href="https://www.theindustrialist.ca/p/from-identification-to-selection">interaction risk</a> than as compatibility. The questions that matter are different:</p><blockquote><ul><li><p>How tightly will decisions become coupled after close?</p></li><li><p>Where will autonomy disappear in practice, even if it remains nominally?</p></li><li><p>Which assumptions about pace, priorities, and performance will collide?</p></li></ul></blockquote><p>Highly compatible businesses tend to integrate more deeply and more quickly &#8212; not because they must, but because they can. Systems merge before assumptions are tested, informal coordination replaces explicit governance, and decision rights collapse into habit. That accelerates alignment, and it also eliminates insulation. When strain emerges, it propagates faster; when <a href="https://www.theindustrialist.ca/p/leadership-is-a-constraint-not-a">leadership bandwidth</a> tightens, there are fewer buffers; when priorities shift, reversibility is limited.</p><p>Fit is therefore a function of how much strain the combined system can absorb at this moment in its development, not of how similar the two organisations appear on a fact sheet.</p><h2><strong>The quiet failure mode of &#8220;easy&#8221; deals</strong></h2><p>Most integration failures I&#8217;ve watched closely originated in deals that everyone perceived as easy. Those deals rarely fail dramatically, they erode quietly. Because compatibility masks interaction risk, early warning signs get interpreted as noise rather than signal. Teams assume issues will resolve once systems are fully aligned. Leaders tolerate temporary overload in the belief that scale or synergy will soon simplify the environment.</p><p>Deep compatibility often front-loads commitment rather than deferring it. Integration outpaces learning, decisions become entangled before trust is established, and small misalignments cascade because there&#8217;s no longer separation to contain them. By the time strain becomes visible, it&#8217;s no longer localised, the system is already carrying it everywhere. The problem isn&#8217;t execution; it&#8217;s interpretation under constraint.</p><h2><strong>Compatibility and the illusion of knowing</strong></h2><p>Compatibility also creates an illusion of understanding. When organisations look alike, leaders believe they know what they&#8217;re buying. That belief compresses diligence, narrows interpretation, and accelerates commitment, not because the information is better, but because the uncertainty feels lower.</p><p>This is particularly dangerous in serial acquisition environments, where prior success with similar targets reinforces confidence. Experience gets mistaken for predictability, and similarity hides uncertainty rather than eliminating it.</p><p>Fit gets revealed not by how little changes at close but by how the system behaves <a href="https://www.theindustrialist.ca/p/the-first-3090-days-what-actually">months later</a> &#8212; when leadership attention is divided, integration work is unfinished, and performance pressure returns. At that point, selection decisions are no longer adjustable.</p><h2><strong>Reframing fit as a constraint question</strong></h2><p>A more useful way to think about fit is to ask three questions of the system, not the target:</p><blockquote><ul><li><p>Where will interaction demand exceed leadership capacity?</p></li><li><p>Which interfaces will require ongoing judgment rather than one-time alignment?</p></li><li><p>How much coupling can the platform absorb now, given everything it&#8217;s already carrying?</p></li></ul></blockquote><p>These are questions of constraint rather than compatibility. A target that&#8217;s less familiar may fit better if it preserves boundaries, slows coupling, and allows learning to occur before deeper integration is attempted. A target that feels perfectly aligned may fit poorly if it collapses too many decisions into the same time horizon and the same <a href="https://www.theindustrialist.ca/p/leadership-is-a-constraint-not-a">leadership bandwidth</a>.</p><p>Fit is a dynamic property of the system under load, not a static property of the target. The same target might fit one platform well and another platform poorly. The same platform might absorb one target cleanly at one moment and the same target poorly six months later.</p><h2><strong>Why this matters upstream</strong></h2><p>Because target universes are constrained, the danger isn&#8217;t choosing imperfect options, it&#8217;s misreading what those options will demand of the system once they arrive. Fit is a design judgment under uncertainty, applied with the platform&#8217;s current state in view.</p><p>Treating compatibility as a proxy for fit biases selection toward faster integration, deeper coupling, and earlier irreversibility, often without anyone naming that those commitments are being made by default. Understanding the distinction doesn&#8217;t simplify target selection, it makes it more honest about what the selection is actually committing to.</p><p>The question to put on the table before any target moves into <a href="https://industrialpatterns.com/pe-diligence">deeper diligence</a> isn&#8217;t whether it feels easy. It&#8217;s: what kinds of interaction is the system prepared to live with next?</p>]]></content:encoded></item><item><title><![CDATA[How Platform Calls and Add-On Calls Get Made Differently]]></title><description><![CDATA[What the first add-on reveals about whether the platform decision was right &#8212; and why most operators learn the difference the hard way.]]></description><link>https://www.theindustrialist.ca/p/how-platform-calls-and-add-on-calls</link><guid isPermaLink="false">https://www.theindustrialist.ca/p/how-platform-calls-and-add-on-calls</guid><dc:creator><![CDATA[David Carr]]></dc:creator><pubDate>Sat, 25 Apr 2026 16:56:29 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!yIZh!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F16d1b5d2-add7-4321-b44b-3c22086f05c1_512x512.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>In most platforms I&#8217;ve looked at carefully through their first add-on, the same pattern shows up: the diligence <a href="https://industrialpatterns.com/industry-structure">framework that worked for the platform decision</a> gets applied &#8212; sometimes consciously, sometimes by inertia &#8212; to the add-on, and the framework picks an add-on the platform isn&#8217;t actually ready to absorb. The deal makes sense in the abstract. It doesn&#8217;t make sense for this platform, in this state, at this moment.</p><p><a href="https://www.theindustrialist.ca/p/platform-selection-and-add-on-selection">Platform Selection and Add-On Selection Are Different Decisions</a> covers the conceptual distinction: <a href="https://industrialpatterns.com/pe-diligence">platform selection is an industry-and-resource decision</a>, add-on selection is an interaction-with-platform decision, and the criteria that should dominate each are nearly opposite. This piece is about how that distinction shows up &#8212; or fails to &#8212; in the actual room where the calls get made.</p><h2><strong>What changes between the platform call and the first add-on call</strong></h2><p>The platform call is, in practice, made by deal-team thinking. Industry analysis dominates, resource fit gets attention, and diligence centres on the target as a stand-alone asset &#8212; because that&#8217;s effectively what it is. There&#8217;s no platform yet for it to interact with. Management quality, customer concentration, contract risk, market position: standard PE diligence, applied well.</p><p>The first add-on call is the first time that framework has to start including the platform&#8217;s current state as a primary input. In most rooms I&#8217;ve watched, that input doesn&#8217;t enter the analysis cleanly. The deal team frames the add-on the way they&#8217;d frame any small acquisition in this space. The integration team frames it through their current load. The two views often don&#8217;t reconcile, and the reconciliation happens implicitly &#8212; usually by deferring to the deal team, because the deal team has the rhythm and the deck.</p><p>The result is a yes that gets made on platform-style criteria when the decision actually being made is an add-on decision. That asymmetry compounds quietly across the next several deals.</p><h2><strong>The signals operators read differently</strong></h2><p>There&#8217;s a small set of signals that should weigh more heavily on add-on decisions than on platform decisions, and most of them are rarely on the standard diligence checklist:</p><blockquote><ul><li><p>Where the platform&#8217;s <a href="https://www.theindustrialist.ca/p/leadership-is-a-constraint-not-a">leadership bandwidth</a> currently is. Not an org chart question &#8212; a Thursday-afternoon question.</p></li><li><p>What the <a href="https://www.theindustrialist.ca/p/integration-capacity-is-the-binding">integration team is actually carrying</a> right now, and from which prior deal.</p></li><li><p>Whether the platform&#8217;s <a href="https://www.theindustrialist.ca/p/operating-cadence-is-a-leadership">operating cadence has stabilised</a> after the last absorption, or is still in transition.</p></li><li><p><a href="https://www.theindustrialist.ca/p/integration-capacity-is-the-binding">How much &#8220;cushion&#8221; exists in the calendar</a> of the people who&#8217;ll have to actually run the new integration.</p></li><li><p>Whether the <a href="https://www.theindustrialist.ca/p/integration-capacity-is-the-binding">add-on creates capacity for the next add-on or consumes it</a>.</p></li></ul></blockquote><p>None of these show up well in a deal memo. They show up in conversations with operating partners, in calendar audits, and in honest answers to &#8220;how&#8217;s the last one going?&#8221; The operators I know who are good at add-on selection ask different questions than the deal team, and they ask them earlier in the process, not at the end.</p><h2><strong>The temporal mismatch</strong></h2><p>Platform decisions and add-on decisions also operate on different time horizons, and the framework rarely makes that explicit.</p><p>A platform decision is effectively a 7- to 12-year decision. The thesis has to hold against an exit window most of the way out. <a href="https://industrialpatterns.com/industry-structure">Industry structure</a>, competitive moat, the trajectory of multiples &#8212; these matter because they have to compound over the full hold period.</p><p>An <a href="https://industrialpatterns.com/add-on-density-atlas">add-on decision is more like a 2- to 3-year decision</a>. The relevant horizon is the period across which the platform has to absorb the acquisition and stabilise enough to either consider another one or run more cleanly into exit. The interaction effects show up over months, not years. Applying platform-decision discount rates to add-on decisions makes everything look better than it should. The same valuation that&#8217;s reasonable for a stand-alone industry bet becomes aggressive once the platform&#8217;s actual integration capacity is priced in.</p><h2><strong>The first add-on test</strong></h2><p>The first add-on a platform completes is usually the one that reveals whether the platform decision was right.</p><p>Not because the add-on itself is the test &#8212; the add-on is just a normal acquisition. The test is what the platform&#8217;s response to integrating the first add-on shows about the bet that was made on the platform itself.</p><p>If the integration goes cleanly, the platform team gets confident, integration capacity feels abundant, and the next deal usually arrives on the calendar early. If it goes poorly, the platform team learns something the deal team didn&#8217;t: the resource bundle wasn&#8217;t quite what the thesis assumed, the operating model has more friction than the diligence captured, and the sequencing has to slow down.</p><p>I&#8217;ve watched both outcomes. The platforms that got the first add-on wrong rarely admit it as a platform-decision error &#8212; they treat it as an integration execution problem and try to fix it through more process. That&#8217;s almost always wrong. The error usually sits at the interaction between the platform&#8217;s actual capacity and the add-on selection criteria, and the fix is to recalibrate the criteria, not to add governance.</p><h2><strong>The question to put on the table</strong></h2><p>Before any add-on closes &#8212; particularly the first one &#8212; the question worth asking out loud is narrower than the deal memo usually frames it: given the state this specific platform is actually in, with these specific people carrying this specific load, is this the add-on we should be doing right now, or is it the add-on the deal team would be doing if they had a clean platform to drop it into?</p><p>If the answer is &#8220;yes, this one, now,&#8221; proceed. If the answer is &#8220;well, the platform is still finishing the last thing, but the deal team has been working on this one for six months,&#8221; the framework is doing the work the platform itself should be doing &#8212; and the framework is wrong for the job.</p><p>That recalibration is one of the cleaner ways to tell whether the deal team and the operating team are reading the same platform.</p>]]></content:encoded></item><item><title><![CDATA[Platform Selection and Add-On Selection Are Different Decisions]]></title><description><![CDATA[Why the same diligence framework that picks platforms well doesn&#8217;t pick add-ons well &#8212; and where the asymmetry actually lives in the criteria.]]></description><link>https://www.theindustrialist.ca/p/platform-selection-and-add-on-selection</link><guid isPermaLink="false">https://www.theindustrialist.ca/p/platform-selection-and-add-on-selection</guid><dc:creator><![CDATA[David Carr]]></dc:creator><pubDate>Sat, 25 Apr 2026 16:44:26 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!yIZh!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F16d1b5d2-add7-4321-b44b-3c22086f05c1_512x512.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Most platforms run their first add-on through the same diligence framework they used for the platform itself. The deal team is mostly the same. The materials look broadly similar. The criteria carry over. And in most cases I&#8217;ve watched up close, the team is surprised when the framework that picked the platform well doesn&#8217;t pick the add-on well &#8212; or worse, picks an add-on that looks attractive on every metric the framework tracks and still turns out to be the wrong add-on for the platform that just bought it.</p><p>The error sits one layer earlier than the framework. Platform selection and add-on selection are different decisions, governed by different logics, and the criteria that should dominate each are nearly opposite to one another in places that matter.</p><h2><strong>What platform selection is actually deciding</strong></h2><p><a href="https://industrialpatterns.com/buy-and-build">Platform selection is, at root, an industry decision</a>. It is a bet on the <a href="https://industrialpatterns.com/industry-structure">structural attractiveness of a sector</a> and on the <a href="https://industrialpatterns.com/operating-benchmarks">long-term economics of operating inside it</a>. This can&#8217;t be emphasised enough. The question being answered is whether this is an industry where a focused, well-capitalised platform can compound advantage over a 7- to 12-year horizon, against the realistic competitive set.</p><p>That question has a long pedigree in strategy. Porter&#8217;s Five Forces (<a href="https://doi.org/10.2469/faj.v36.n4.30">Porter 1980</a>) is the canonical framework for thinking through it: competitive intensity, threat of new entrants, buyer power, supplier power, and substitution dynamics. The resource-based view (<a href="https://doi.org/10.1002/smj.4250050207">Wernerfelt 1984</a>, <a href="https://doi.org/10.1177/014920630102700602">Barney 1991</a>) adds the resource lens &#8212; what does the platform need to control to make the industry economics actually work for it? Picking a platform means picking an industry-position-resource bundle that has to hold up under conditions you can&#8217;t yet describe.</p><p>Other inputs at the platform stage: the availability of attractive add-ons in the sector (a platform with no plausible add-on path is a single-asset bet, not a buy-and-build); the structural moat or scale advantage the platform can build over time; and the exit landscape 7&#8211;12 years out &#8212; who buys these in size, at what multiples, under what conditions.</p><p>Platform decisions are slow, expensive to reverse, and rare. A typical PE platform thesis gets built over months and lived with for the better part of a decade.</p><h2><strong>What add-on selection is actually deciding</strong></h2><p><a href="https://industrialpatterns.com/add-on-density-atlas">Add-on selection is a fundamentally different question</a>. It is a bet on the interaction between this specific add-on and the specific platform that already exists, given the integration capacity that platform currently has and the sequencing of what&#8217;s already been absorbed.</p><p>The question being answered isn&#8217;t &#8220;is this a good business?&#8221; &#8212; that question is mostly settled by the time an add-on reaches diligence. The question is whether, given everything the platform is already carrying, it can absorb this one well, and whether absorbing it improves the platform&#8217;s position for the next add-on.</p><p>The criteria that matter at this layer are nearly the inverse of the platform layer: operational overlap with the platform (how much capacity will integration consume?), integration burden relative to current load (what&#8217;s already in flight?), leadership bandwidth in the platform team (who has to actually run the absorption?), sequencing (what does this one make easier or harder for the next?), and cultural and process compatibility &#8212; not just industry fit. Add-on decisions are governed more by <a href="https://www.theindustrialist.ca/p/integration-capacity-is-the-binding">integration capacity</a> than by industry structure, and they are faster, more frequent, and partially reversible (add-ons can be divested cleanly more often than platforms can).</p><h2><strong>Where the framework misfires</strong></h2><p>The conflation usually goes one direction. Deal teams that selected a platform on industry-and-resource grounds keep using industry-and-resource framing for the add-ons. The add-on diligence centres on customer concentration, contract risk, financial performance, and management quality. Those things matter &#8212; they are necessary conditions, but they are not sufficient ones.</p><p>What the framework misses, when it&#8217;s the wrong framework, is the question that actually drives outcomes at the add-on layer: how much of the platform&#8217;s <a href="https://www.theindustrialist.ca/p/integration-capacity-is-the-binding">absorptive capacity</a> will this acquisition consume, and how much will it leave in reserve for the one after this? The <a href="https://www.theindustrialist.ca/p/why-we-acquire-motives-before-targets">original acquisition motive</a> tells you why this kind of add-on is on the list at all; it doesn&#8217;t tell you whether this one is the right next one for the platform.</p><p>That question doesn&#8217;t appear in a Porter-style analysis because Porter is about the industry, not about the platform. It appears only when add-on diligence is built around the buying platform&#8217;s current state, not just the target&#8217;s stand-alone characteristics.</p><h2><strong>Why this matters</strong></h2><p>Both decisions are real, and both deserve rigorous diligence &#8212; but they need different rigour. Platform selection needs to ask whether the industry and the resource bundle can hold up over a long horizon. Add-on selection needs to ask whether the platform that already exists can absorb this one well now.</p><p>Conflating them produces a recognisable failure pattern: the deal team approves an add-on on platform-criteria grounds; the integration team is left with a target that fits the industry but not the platform&#8217;s current state; and twelve to eighteen months later the post-mortem identifies &#8220;integration challenges&#8221; &#8212; when the real problem was the criteria the add-on was approved against in the first place.</p><p><a href="https://www.theindustrialist.ca/p/how-platform-calls-and-add-on-calls">How Platform Calls and Add-On Calls Get Made Differently</a> takes up the operator side of this &#8212; how the call gets made differently in the room, and what the first add-on usually reveals about whether the platform decision was right.</p>]]></content:encoded></item><item><title><![CDATA[The Limits of Diligence]]></title><description><![CDATA[Why diligence reorganises uncertainty rather than resolving it. The category of uncertainty diligence can&#8217;t reach, and what experienced teams do anyway.]]></description><link>https://www.theindustrialist.ca/p/the-limits-of-diligence</link><guid isPermaLink="false">https://www.theindustrialist.ca/p/the-limits-of-diligence</guid><dc:creator><![CDATA[David Carr]]></dc:creator><pubDate>Wed, 08 Apr 2026 15:01:17 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!QFGD!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe5997aae-e9bc-4840-aa6c-adab41b2b499_1024x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Diligence is often described as the moment uncertainty gives way to clarity. Data gets gathered, assumptions tested, risks surfaced, confidence rising. In practice, diligence rarely resolves uncertainty, <a href="https://industrialpatterns.com/pe-diligence">it reorganises it</a>. Some questions get answered, others get reframed, and a meaningful portion of what actually matters remains stubbornly unknowable until long after the deal closes.</p><p>This isn&#8217;t a failure of diligence. It&#8217;s a limit of what diligence can do, and one that isn&#8217;t acknowledged often enough in the rooms where deals get approved.</p><h2><strong>What diligence is actually designed to address</strong></h2><p>Most of the literature on target selection frames diligence as a response to information asymmetry, the idea that sellers know more about their businesses than buyers, and that diligence exists to close that gap. The framing is directionally correct, and the work follows from it. Diligence is well suited to uncovering historical financial performance, contractual obligations, customer concentration, legal and regulatory exposure, and operational processes as they exist today. These are important, and in many cases they are decisive.</p><p>They represent only one category of uncertainty, though: verifiable uncertainty, facts that can be reasonably approximated through investigation.</p><h2><strong>The uncertainty diligence cannot resolve</strong></h2><p>The more consequential uncertainties in buy-and-build are usually emergent &#8212; produced by the deal rather than hidden by it. They show up as: how leaders respond under <a href="https://www.theindustrialist.ca/p/leadership-is-a-constraint-not-a">sustained integration load</a>, how cultures adapt when routines collide, how decision-making changes as complexity accumulates, how systems behave once stretched beyond familiar limits. None of these exist fully formed before the deal. They get produced by it.</p><p>No amount of pre-close diligence can observe how an organisation will behave in conditions it hasn&#8217;t yet experienced. The most diligent firm in the room still has to decide what it is willing to find out.</p><h2><strong>Why this gap persists</strong></h2><p>Several mechanisms in the academic literature on M&amp;A help explain why some uncertainty stays out of reach.</p><h3><strong>Prior relationships.</strong> </h3><p>Prior interactions, alliances, or partial ownership reduce uncertainty, but only in narrow domains. Familiarity improves confidence; it can also create blind spots that diligence doesn&#8217;t catch because it isn&#8217;t looking for them. Experience teaches patterns more than it eliminates surprise.</p><h3><strong>External signals.</strong> </h3><p>Market reactions, advisor endorsements, and reputational cues help narrow options, but they&#8217;re indirect proxies for future performance. They tell you how others have interpreted the target, which is a useful piece of information about the market, and a much weaker piece of information about how the target will behave inside your platform.</p><h3><strong>Networks and intermediaries.</strong> </h3><p>Board interlocks, shared advisors, and financial intermediaries increase transparency and trust, and they reduce coordination costs. Trust speeds the deal; it doesn&#8217;t make outcomes more predictable. Governance alignment helps the relationship between buyer and seller; it doesn&#8217;t make the operating overlap any more compatible than it actually is.</p><p>Together, these mechanisms reduce some uncertainty while leaving the more important kinds untouched.</p><h2><strong>Judgment in the presence of irreducible uncertainty</strong></h2><p>Because diligence can&#8217;t eliminate all uncertainty, target selection ultimately depends on judgment. Judgment, in this context, is the ability to distinguish material uncertainty from background noise, to recognise which unknowns the organisation is equipped to handle, and to decide when more information no longer improves the decision.</p><p>Experienced teams often appear comfortable proceeding with &#8220;known unknowns&#8221; while less experienced teams keep searching for certainty that won&#8217;t arrive. The difference between them is calibration, not confidence &#8212; knowing which uncertainties are worth pricing, which are worth tolerating, and which are tells that <a href="https://www.theindustrialist.ca/p/why-we-acquire-motives-before-targets">the deal is wrong even when the financials look fine</a>.</p><h2><strong>The diminishing returns to diligence</strong></h2><p>One of the least-discussed dynamics in target selection is what happens when diligence runs longer than it usefully can. As diligence expands, new information increasingly confirms existing beliefs rather than challenging them. Effort shifts from learning to justification. The emotional and political cost of walking away rises with every week of work invested.</p><p>This is how diligence becomes a mechanism for commitment rather than discovery. The decision hasn&#8217;t necessarily improved; it has simply become harder to reverse. The deals I&#8217;ve watched go furthest sideways were rarely the ones with the thinnest diligence; more often they were the ones where diligence ran long enough to become consensus, and the consensus made the right answer (walk) costlier to produce than the wrong one (proceed).</p><h2><strong>What diligence is actually doing</strong></h2><p>Seen this way, diligence is a sensemaking activity. It helps teams understand what kind of uncertainty they&#8217;re facing, where <a href="https://www.theindustrialist.ca/p/why-integration-fails">integration strain</a> is likely to surface, and whether the organisation has the capacity to absorb the consequences. It doesn&#8217;t predict what will happen, it helps the team decide what they are willing to live with, with their eyes more open than they would otherwise have been.</p><p>That&#8217;s a narrower job than the diligence-eliminates-risk framing suggests. It&#8217;s also a more honest one, and the one that actually matches what experienced operators do with diligence findings in the room where the decision gets made.</p><h2><strong>Why this matters in buy-and-build</strong></h2><p>In buy-and-build, the limits of diligence matter more than they do in one-off M&amp;A. Because acquisitions are repeated, small misjudgments compound. Early tolerance for unresolved uncertainty becomes precedent. Over time, the organisation inherits not just businesses, but assumptions about what can be figured out later &#8212; and those assumptions are rarely revisited until they break.</p><p>This is how buy-and-build platforms drift from deliberate to reactive. Understanding the limits of diligence shifts where you look for risk, usually somewhere downstream of where the diligence team was working. (<a href="https://www.theindustrialist.ca/p/integration-capacity-is-the-binding">Integration Capacity Is the Binding Constraint covers this dynamic from the platform side</a>.)</p><h2><strong>The right question to hold</strong></h2><p>The most useful question diligence can answer isn&#8217;t &#8220;is this target safe?&#8221; It&#8217;s &#8220;given what we know and what we cannot know, is this uncertainty appropriate for this organisation right now?&#8221;</p><p>That question can&#8217;t be outsourced or solved analytically, and it can&#8217;t be answered without an honest read of what the organisation can actually carry. It&#8217;s the question that separates deliberate growth from accidental accumulation, and it sits squarely in the space <a href="https://www.theindustrialist.ca/p/from-identification-to-selection">this piece walks through</a> on fit, distance, and uncertainty.</p>]]></content:encoded></item><item><title><![CDATA[From Identification to Selection: Fit, Distance, and Uncertainty]]></title><description><![CDATA[Why most of the acquisition decision is made before diligence begins. Fit, distance, and uncertainty get priced earlier than the formal process suggests.]]></description><link>https://www.theindustrialist.ca/p/from-identification-to-selection</link><guid isPermaLink="false">https://www.theindustrialist.ca/p/from-identification-to-selection</guid><dc:creator><![CDATA[David Carr]]></dc:creator><pubDate>Wed, 11 Feb 2026 16:01:07 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!QFGD!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe5997aae-e9bc-4840-aa6c-adab41b2b499_1024x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>By the time a deal reaches diligence, most of the decision has already been made. Targets have been identified, screened, discussed, and quietly validated by the people who matter. Time and attention have been invested. Momentum has formed. What remains often feels like confirmation rather than choice &#8212; and in most of the deals I&#8217;ve watched up close, that feeling was accurate.</p><p>This isn&#8217;t a failure of rigor. It&#8217;s a feature of how the pre-deal phase actually works, and one of the reasons most of the interesting errors in target selection get made before anyone formally writes a deal memo.</p><h2><strong>Where strategy narrows</strong></h2><p>Recent academic work on M&amp;A increasingly emphasises the pre-deal phase &#8212; the period before exclusivity, before confirmatory diligence, often before formal approval. Welch and colleagues (<a href="https://doi.org/10.1177/0149206319886908">Welch et al. 2020</a>) describe this phase as one in which firms search for opportunities, interpret incomplete information, and progressively narrow their option set under uncertainty.</p><p>Crucially, that narrowing isn&#8217;t purely analytical. It is shaped by cognition, prior experience, organisational routines, and social interaction. Target selection is therefore less a discrete decision and more a process of progressive commitment &#8212; a cumulative narrowing of what counts as a serious option, often invisible to the people doing the narrowing.</p><h2><strong>Target identification frames the choice set</strong></h2><p>Target identification defines the space within which selection occurs. It answers a quieter set of questions than selection itself: <a href="https://industrialpatterns.com/industry-reference">which kinds of companies count as &#8220;plausible,&#8221;</a> which dimensions of fit get emphasised, where uncertainty is tolerated, where it isn&#8217;t. These judgments are often implicit. They are embedded in sourcing strategies, advisor relationships, and internal narratives about &#8220;what we&#8217;re looking for.&#8221; The motives that shape that frame are the subject of <a href="https://www.theindustrialist.ca/p/why-we-acquire-motives-before-targets">Why We Acquire: Motives Before Targets</a> &#8212; this piece picks up where that one ends.</p><p>Once a target fits the identification frame, it begins life with a presumption of legitimacy. Selection then becomes a question of whether to stop, not whether to start. The default is yes; objections must be earned. This is why identification deserves as much scrutiny as selection &#8212; and usually gets less.</p><h2><strong>Fit is about interaction, not resemblance</strong></h2><p>Fit is often treated as similarity &#8212; same industry, similar customers, adjacent products. These similarities can matter, but they are proxies for the thing that actually matters: how the target and platform will interact once combined.</p><p>Interaction-based fit asks how many interfaces must be managed, how interdependent operations will become, how much coordination is required to realise value, and where ambiguity will concentrate. Two businesses that look similar can generate disproportionate strain if their interaction points are dense or poorly understood. Two businesses that look different can integrate smoothly when their interactions are limited and well-defined.</p><p>Fit, in this sense, is a property of the relationship between target and platform &#8212; and the relationship is governed by <a href="https://www.theindustrialist.ca/p/integration-capacity-is-the-binding">integration capacity</a>, not by surface similarity.</p><h2><strong>Distance is multidimensional</strong></h2><p>Distance is often discussed narrowly, usually as geography. In practice, distance is multidimensional. Operational distance &#8212; processes, systems, cadence &#8212; is the most visible. Cultural distance &#8212; norms, decision styles, tolerance for ambiguity &#8212; is the least diligent-able. Cognitive distance, which is how problems are framed and solved, is the easiest to underestimate. Institutional distance &#8212; regulatory, labour, and market structures &#8212; is the most often outsourced to advisors, and the least often understood internally.</p><p>Each dimension adds uncertainty, and the dimensions interact. A platform that can manage geographic distance may struggle with cultural distance. Another may tolerate product variation but not governance differences. Distance isn&#8217;t inherently bad; it has to be priced into the organisation&#8217;s capacity to absorb it, and that pricing is rarely done explicitly enough.</p><h2><strong>Why diligence calibrates uncertainty rather than eliminating it</strong></h2><p><a href="https://industrialpatterns.com/pe-diligence">Diligence is often described as a process of risk reduction</a>. In practice, its more useful role is uncertainty calibration. Some uncertainties can be resolved: financial performance, customer concentration, contractual exposure. Others cannot.</p><p>The ones that can&#8217;t be resolved are the ones that usually matter most: leadership adaptability, cultural response under pressure, <a href="https://www.theindustrialist.ca/p/the-first-3090-days-what-actually">integration friction that only appears once routines collide</a>. Welch and colleagues note that firms rarely enter deals with complete information; they rely on heuristics, experience, and social cues to decide when uncertainty is &#8220;acceptable enough.&#8221; That&#8217;s the work diligence is doing when it works &#8212; narrowing what&#8217;s unknown to a level the organisation can carry. (<a href="https://www.theindustrialist.ca/p/why-integration-fails">Why Integration Fails covers what happens when this calibration is wrong</a>.)</p><h2><strong>Selection as judgment under constraint</strong></h2><p>Target selection happens at the intersection of strategic intent, organisational capacity, and irreducible uncertainty. The decision is rarely &#8220;is this target perfect?&#8221; It is more often &#8220;is this target good enough given what we know, and what we can handle?&#8221;</p><p>Experienced teams differ from less experienced ones in what they recognise rather than what they eliminate. They are better at noticing which uncertainties matter most at their stage of development &#8212; which signals are worth investigating, which are worth tolerating, and which are tells that the deal is wrong even when the financials look fine.</p><p>That recognition is mostly learned by getting it wrong, once or twice, in a context where the stakes were high enough to remember. Which is one reason early mistakes are so costly: they are also where most of the durable judgment gets formed.</p>]]></content:encoded></item><item><title><![CDATA[Why We Acquire: Motives Before Targets]]></title><description><![CDATA[The most important decisions in target selection happen before any specific company is evaluated. Four motives that pre-select every target list.]]></description><link>https://www.theindustrialist.ca/p/why-we-acquire-motives-before-targets</link><guid isPermaLink="false">https://www.theindustrialist.ca/p/why-we-acquire-motives-before-targets</guid><dc:creator><![CDATA[David Carr]]></dc:creator><pubDate>Wed, 14 Jan 2026 16:01:03 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!QFGD!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe5997aae-e9bc-4840-aa6c-adab41b2b499_1024x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Most post-mortems on failed acquisitions focus on diligence or integration. The post-mortems I&#8217;ve read run something like this: we missed signals during diligence, we underestimated integration load, we picked the wrong integration partner, the team we bought wasn&#8217;t what we thought. All of those can be true. None of them is usually the root cause.</p><p>The decisions that most shape whether an acquisition works are made earlier, before any specific target is evaluated. They are made when leaders decide what they are actually trying to build &#8212; and more specifically, what the firm is trying to build that it cannot build easily on its own.</p><h2><strong>Acquisition is a strategic act, not a transactional one</strong></h2><p>Acquisitions are almost never opportunistic in the pure sense. Even deals that arrive unexpectedly get interpreted through an existing strategic lens, and that lens is shaped by a prior judgment about what the firm needs that it doesn&#8217;t have.</p><p>The resource-based view of the firm (<a href="https://doi.org/10.1002/smj.4250050207">Wernerfelt 1984</a>, <a href="https://doi.org/10.1177/014920630102700602">Barney 1991</a>) is useful here &#8212; not as theory, but as orientation. The core insight is that firms secure durable advantage by controlling resources and capabilities that are valuable, difficult to imitate, and not easily acquired through markets alone. From that angle, an acquisition isn&#8217;t a faster-growth path; it is a way to reconfigure the firm&#8217;s resource base. What gets acquired and why should be legible as a specific bet on a specific capability gap.</p><p>Seen this way, target selection doesn&#8217;t start with targets. It starts with capability intent.</p><h2><strong>Four common acquisition motives</strong></h2><p>Most acquisition programs I&#8217;ve looked at trace back to one of four recurring motives. Each quietly shapes what &#8220;fit&#8221; means long before diligence starts.</p><h3><strong>Capability or product complementarity</strong> </h3><p>The firm buys to add capabilities it lacks &#8212; technologies, products, or expertise that would take too long or be too uncertain to build internally. The question here isn&#8217;t whether the target is attractive in isolation, but whether its resources can actually be integrated and leveraged inside the existing platform.</p><h3><strong>Customer or channel expansion</strong> </h3><p>Some acquisitions are about access rather than capability &#8212; new customers, new end markets, or new routes to market. Value in these deals depends less on integration depth and more on whether cross-selling and coordination will actually happen in practice, or whether they&#8217;re being assumed into existence by the synergy model.</p><h3><strong>Geographic expansion</strong> </h3><p>Geography is usually framed as a surface-level motive, and it isn&#8217;t. Geographic acquisitions test the firm&#8217;s ability to replicate its operating model, manage distance, and absorb institutional and cultural variation &#8212; all of which are harder to diligence than a map suggests.</p><h3><strong>Density and scale economics</strong> </h3><p>The fourth common motive is deepening presence inside an existing footprint &#8212; <a href="https://industrialpatterns.com/add-on-density-atlas">more customers per route, more utilisation per facility</a>, better bargaining power. These deals usually look safer on paper than cross-geography or cross-capability deals. They still alter operating cadence and integration load; the size of the shift is just smaller.</p><p>Each motive carries a different theory of value creation &#8212; and, critically, a different tolerance for complexity and uncertainty. Two firms that look at the same target and reach opposite conclusions are usually not disagreeing about the target. They are trying to build different things.</p><h2><strong>Motives pre-select targets</strong></h2><p>Once the acquisition motive is set, the universe of plausible targets narrows dramatically &#8212; and most of the narrowing happens implicitly. <a href="https://industrialpatterns.com/industry-structure">Certain industries become &#8220;strategic.&#8221;</a> Certain business models get written off as incompatible. Certain risks become tolerable while others become disqualifying. By the time a formal target list is assembled, the real selection work has already substantially been done. The list is shorter than it could have been, and the criteria are tighter than anyone has written down.</p><p>This is where selection stops being purely evaluative. It is interpretive. The person reading a deal memo is reading it through the motive the firm entered the process with, whether or not that motive is stated anywhere.</p><h2><strong>Why this matters for the rest of the work</strong></h2><p>Most post-mortems focus on diligence failures or integration breakdowns (the kind of breakdowns I covered in <a href="https://www.theindustrialist.ca/p/why-integration-fails">Why Integration Fails</a>). Less attention is paid to whether the acquisition motive itself was coherent, stable, and matched to the organisation&#8217;s actual capacity. When motives are unclear, selection drifts &#8212; the list starts broadening mid-process. When motives are overly broad, diligence loses focus &#8212; every concern becomes a possible deal-killer. And when motives are mismatched to what the platform can absorb (the central problem in <a href="https://www.theindustrialist.ca/p/integration-capacity-is-the-binding">Integration Capacity Is the Binding Constraint</a>), even the &#8220;right&#8221; target strains the system once it arrives.</p><p>Understanding why you are acquiring doesn&#8217;t eliminate risk. It sharply improves the quality of the risks you choose to live with &#8212; which is what diligence is actually for.</p><p>The next essay in this section takes this thinking forward. <a href="https://www.theindustrialist.ca/p/from-identification-to-selection">From Identification to Selection</a> looks at how firms move from target identification to target selection, and where judgment enters that transition. Whatever motive a firm starts with, it eventually has to be translated into a choice about a specific company &#8212; and that translation is where most of the interesting errors get made.</p>]]></content:encoded></item><item><title><![CDATA[Target Selection & Diligence]]></title><description><![CDATA[Target selection isn&#8217;t only about finding the right company. It&#8217;s about deciding what kind of complexity the organisation is going to live with next.]]></description><link>https://www.theindustrialist.ca/p/target-selection-and-diligence</link><guid isPermaLink="false">https://www.theindustrialist.ca/p/target-selection-and-diligence</guid><dc:creator><![CDATA[David Carr]]></dc:creator><pubDate>Wed, 24 Dec 2025 16:01:44 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!QFGD!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe5997aae-e9bc-4840-aa6c-adab41b2b499_1024x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Most of the serious failures I&#8217;ve read through carefully happened long before the integration ran into trouble. They happened at target selection &#8212; not because the wrong company was chosen, but because the right company was chosen for the wrong reasons, or under an implicit theory of fit the system couldn&#8217;t actually deliver on.</p><p>Target selection is usually presented as an analytical funnel. A long list becomes a short list; attractiveness is scored, risks are diligenced, and a choice is made. From the outside the process looks orderly, and in many respects it is. Modern PE and corporate development teams have become highly sophisticated in how they evaluate businesses.</p><p>From an operating vantage point, though, target selection is one of the most consequential design choices in buy-and-build &#8212; because it determines how much uncertainty, complexity, and integration strain the organisation will inherit before it has any chance to manage it. That is what this section is about: target selection less as a question of which company is best, more as a question of which company the system can actually absorb, given its current capabilities, leadership bandwidth, and stage of development.</p><h2><strong>Target identification and target selection are not the same activity</strong></h2><p>In practice and in much of the literature, target identification and target selection get treated interchangeably. They are different activities with different logics.</p><p>Target identification expands the opportunity set. It determines which potential acquisitions become visible to the organisation through networks, intermediaries, thematic searches, or inbound interest. Target selection constrains that set &#8212; it determines which of those visible opportunities get advanced toward diligence, negotiation, and eventual ownership.</p><p>Identification is shaped largely by market exposure and information flow. Selection is shaped by internal judgment about feasibility, fit, and capacity. In buy-and-build strategies, selection does most of the work in shaping outcomes.</p><h2><strong>Selection as design under constraint</strong></h2><p>Target selection happens under conditions where information is incomplete, signals are noisy, and most of the important integration challenges are not yet observable in financials or diligence materials. Selection decisions inevitably embed assumptions about how much complexity the organisation can absorb next, which routines can be disrupted without destabilising performance, and how leadership attention and integration effort will be allocated.</p><p>Seen this way, target selection functions less like optimisation and more like design under constraint. It is an early commitment about what kinds of problems the organisation is prepared to live with, and which ones it is not.</p><h2><strong>Why diligence cannot do this work alone</strong></h2><p>Diligence plays a critical role in reducing risk. It also has limits. Many of the factors that determine post-acquisition outcomes &#8212; trust, decision clarity, cultural friction, leadership saturation &#8212; are not fully knowable at the point of diligence. They are revealed only once the organisation begins to integrate and operate as a system.</p><p>Strong target selection, in that light, works by reducing uncertainty to a level the organisation can carry without degrading judgment, execution, or learning. Selection absorbs what diligence cannot resolve.</p><h2><strong>What this section examines</strong></h2><p>The essays in this section approach target selection as a strategic act of commitment rather than a mechanical filtering step. They work through how fit and distance shape integration difficulty long before close, why platform selection and add-on selection are asymmetric decisions, and how early signals, timing, and sequencing influence outcomes after an acquisition. The focus is on how organisations decide what complexity to introduce next, and why that decision often matters more than price or structure. (If you&#8217;re new here, <a href="https://www.theindustrialist.ca/p/how-to-read-this-project">How to Read This Project</a> lays out the full structure and the recommended reading paths across sections.)</p><p>What the essays share is a single question: what is the organisation being asked to carry, and is it ready to carry it? That question governs most of what matters about a target long before diligence begins &#8212; and it is bounded, always, by <a href="https://www.theindustrialist.ca/p/integration-capacity-is-the-binding">integration capacity</a> rather than by the deal memo.</p>]]></content:encoded></item></channel></rss>