--- title: "Product Portfolio Strategy: The Difference Between a Product List and a Portfolio Decision" description: "Product portfolio strategy is not the list of what a company sells; it is the written record of why each item is retained and at what threshold it would be removed. Diligence does not reward breadth. It looks for evidence that additions and discontinuations run through a measurable mechanism rather than through founder judgment exercised case by case." url: https://www.beirek.com/en/blog/product-portfolio-strategy-due-diligence canonical: https://www.beirek.com/en/blog/product-portfolio-strategy-due-diligence published: 2026-07-30 modified: 2026-07-30 category: "Strategy & Business Plan" category_url: https://www.beirek.com/en/blog/category/strategy-business-plan language: en-US reading_time_minutes: 8 publisher: BEIREK LLC publisher_url: https://www.beirek.com license: "© BEIREK LLC — citation with attribution and link permitted" keywords: ["product portfolio strategy","investment readiness diligence","per-product profitability","founder dependency","valuation discount","product rationalization","activity-based cost allocation"] topics: ["Portfolio governance and discontinuation authority","Cost allocation and per-product economics","Valuation multiple and deal structure impact of unmanaged complexity","Investment readiness review dimensions: existence, documentation, execution, measurement, ownership, continuity"] alternate_language_url: https://www.beirek.com/tr/blog/product-portfolio-strategy-due-diligence --- # Product Portfolio Strategy: The Difference Between a Product List and a Portfolio Decision > **In short:** Product portfolio strategy is not the list of what a company sells; it is the written record of why each item is retained and at what threshold it would be removed. Diligence does not reward breadth. It looks for evidence that additions and discontinuations run through a measurable mechanism rather than through founder judgment exercised case by case. *In most companies the product portfolio is not a chosen structure but a residue left behind by past sales opportunities. The diligence table arrives looking for that distinction: why each product exists, at what threshold it would be withdrawn, and in whose authority that decision actually sits.* --- When the product portfolio reaches the agenda of a board presentation, nearly the whole of the discussion is built around what should be added; what should be withdrawn either goes unmentioned or sits at the bottom of the list as a heading to be reached if time permits. Plotted across several years, the product count in the same company traces a curve that runs in one direction only — upward. Engineering capacity, the size of the commercial team, and the supply chain's tolerance for complexity have not, over that same period, expanded at anything like the same rate. To the extent that the portfolio grows while the carrying capacity holds steady, every new item draws a measure of attention, a measure of shelf space, and a measure of selling time away from the items already there; because this transfer appears as a line in no report, no one records it as a cost. The first question asked when the portfolio heading is opened in an investment review is usually the question the company has never put to itself: why is this product here? The answer, more often than not, describes the item's origin rather than its continued existence — a customer asked for it, a tender required it, a supplier relationship brought it in. That distinction between an origination rationale and a continuation rationale is precisely what the review is looking for, since origination is a one-time event while continuation is a decision requiring renewal on a recurring basis. Asking whether a portfolio strategy is formally defined is, in substance, asking whether that renewal has been attached to a structure; an intention to focus, expressed verbally, is at this stage an aspiration rather than a strategy. The mechanism beneath this one-directional accumulation rests in the asymmetric narrative burden that additions and removals carry inside an organization. A proposal to add is presented in the language of growth, customer proximity, and market responsiveness; the person bringing it is credited with commercial initiative, and even where the decision proves wrong, the cost disperses across time and loses visibility. A proposal to discontinue is spoken in the language of loss, retreat, and a prior investment written off; the person bringing it must be prepared to stand in front of teams who built the product and to imply that a decision taken earlier was mistaken. Sunk cost fallacy — the determination of a forward decision by expenditure already incurred — operates here not as an individual cognitive defect but as rational behavior produced by the firm's own incentive structure. No one proposes closure, because the personal return on proposing closure is negative. The second layer of the mechanism sits on the measurement side. A portfolio decision can be taken only to the extent that per-product economics are accessible, yet in most companies cost accounting is constructed around plants or business units rather than around products. Where shared costs — changeover time, quality inspection hours, after-sales support, engineering revisions, documentation load — are allocated on revenue weight, low-volume, high-complexity items appear systematically profitable while high-volume standard items absorb burden they do not generate. The allocation convention looks like an innocuous accounting choice; its consequence is to reverse, quietly, the direction of the portfolio decision, so that the item warranting closure reads as profitable and the item warranting protection reads as marginal. The institutional cost of these two mechanisms accumulates not in the portfolio itself but across the operational surfaces surrounding it. Inventory turns slow almost without exception as the product count rises, since every item demands a minimum safety stock, a minimum spare parts commitment, and a minimum footprint, none of which scale proportionally with volume. On the manufacturing side, setup and changeover time expands, the planning horizon shortens, and variance against delivery commitments widens. On the commercial side the cycle lengthens, because training a salesperson able to carry a broad portfolio takes materially longer than training one who carries a narrow portfolio, and the knowledge lost on departure grows in the same proportion. None of this appears in the income statement attributed to a portfolio decision; it sits dispersed across working capital requirements, liquidated damages, and commercial staff turnover. Transmission to the valuation table then occurs through two separate channels. The first is the multiple itself: in a company unable to demonstrate per-product economics, the buy side cannot identify which items carry the consolidated margin, and its model consequently pulls that margin toward a historical mean while framing growth assumptions conservatively. The second channel is deal structure, and it is typically the more expensive one — where portfolio decisions are found not to be institutionalized, part of the consideration is shifted into an earn-out, representation and warranty coverage is extended on a product-line basis, and the rationalization or carve-out of specified items enters the conditions precedent. For the seller, the consequence is not merely less cash at closing; it is the obligation to perform, after closing, against a measurement discipline the seller did not design. Ownership is, in this picture, the dimension most easily skipped and most decisive of the outcome. The decision to add a product can in most companies be taken in distributed fashion — by a sales director, a regional manager, or by the founder personally through a customer relationship. The decision to remove one is in practice concentrated in a single individual, and that individual is almost invariably the founder. The asymmetry means that the portfolio scales in the direction of expansion and fails to scale in the direction of contraction; the company can add products by itself, but cannot close one without the founder at the table. In diligence, the condition surfaces through a single question: over the last three years, has any discontinuation decision been taken, and actually executed, in a meeting the founder did not attend? Continuity is measured at exactly this point. Evidence that a company holds institutional capacity in portfolio management is not a well-drafted strategy document but a decision that document compelled and that was implemented notwithstanding personal preference. Where the document, the threshold, and the cadence are in place, closure ceases to be a confrontation and becomes a calendar item; no one is required to persuade anyone, because the threshold was fixed in advance and in the abstract, that is, without knowing which product would eventually fall against it. The distance between a threshold set beforehand and one set at the moment of decision determines whether the entire mechanism functions, since any threshold set at the moment of decision will be calibrated to route around the product intended for protection. BEIREK's intervention in this area does not begin with the delivery of a strategy document; it begins by mapping where the portfolio decision is in fact made. Per-product economics are rebuilt first, with shared cost allocation moved off revenue weight and onto activity drivers — changeover counts, revision volumes, support tickets, inspection hours — a step that alone tends to render the true shape of the portfolio visible for the first time. The portfolio decision is then separated into three written components: (a) the thresholds a product must satisfy in order to remain, together with the data source against which those thresholds are measured; (b) the review calendar and deciding authority triggered when an item falls below threshold; and (c) the party responsible, and the period allowed, for executing the operational consequences of closure — inventory run-off, spare parts commitments, customer migration. Taken together, these three convert portfolio management from a matter of opinion into an operating procedure. The second layer of intervention concerns cadence and record. A portfolio review embedded in the annual budget cycle drifts inevitably toward the addition side, because a budget conversation is a conversation about constructing next year's revenue; the review is therefore run on a separate cadence, with a separate agenda, and held apart from addition decisions. For every addition, the expected volume, the expected margin, and the date on which that expectation will be tested are entered into the record at the moment of decision rather than afterward; when the date arrives, the record is opened and compared against outcome. The function of that record is not to adjudicate past decisions but to remove the closure discussion from the register of personal confrontation and place it against a measure agreed in advance. Resolving founder dependency becomes possible only where such a measure exists, since authority can genuinely be delegated only where the delegated decision rests on an objective basis. Building these mechanisms does not imply that the portfolio will necessarily narrow. In some reviews the finding is that breadth genuinely operates as a customer lock-in lever and that the cost of complexity is being paid deliberately; demonstrating that is as valuable as pruning, since what the diligence table seeks is not a narrow portfolio but a selected one. The difference lies not in the number of products but in whether each product's presence is tied to a stated rationale and an exit threshold. The distance between a company asserting that it operates with a broad portfolio and a company quantifying the cost of that breadth and electing to carry it regardless is a distance written directly into the valuation multiple. Product portfolio strategy is, in the end, an indicator less of what a company is able to do than of what it is institutionally able to refrain from doing. The capacity to add is a natural product of the market and the sales organization and exists to some degree in nearly every company; the capacity to subtract exists only where it has been designed, and in the absence of design it never emerges on its own. That is what the portfolio heading is genuinely measuring in a review — the company's capacity to revisit its own past decisions independently of the continued presence of the people who took them. Taking the items currently in the portfolio one by one, can a continuation rationale valid as of today be written for each; or is the only thing that can be written the account of how that item once entered? ## Key Points - In most companies the portfolio is accumulated rather than selected, each item being the residue of a reasonable yes given at some point to a specific customer request. - The absence of a portfolio decision shows up not in the product count but in slowing inventory turns, lengthening changeover time, and a sales cycle that stretches without anyone attributing the cause. - The diligence table is looking less for strong per-product margins than for the ability to compute per-product margin at all; where that computation is unavailable, consolidated margin is read conservatively. - Discontinuation is structurally harder than addition because addition is presented in the language of growth while removal is presented in the language of loss and retreat. - The only verifiable proof that portfolio management is independent of the founder is a discontinuation decision taken, and actually executed, in a meeting the founder did not attend. ## Questions ### Are a product portfolio strategy and a product roadmap the same thing? No. A roadmap sets out which products will be developed and when; a portfolio strategy defines why each product is retained and at what threshold it would be withdrawn. The roadmap operates in the direction of addition only, while portfolio strategy operates in both directions. Investment reviews test the two separately, and the existence of a roadmap carries no implication that the portfolio decision has been institutionalized. ### How does an investor establish that a product portfolio strategy is genuinely applied? Proof of execution is a decision, not a document. The review side typically looks for items withdrawn in recent periods, the data on which those withdrawals rested, and the authority under which they were taken. Where no discontinuation decision can be found, the written strategy is treated as unimplemented however detailed it may be, since a portfolio that grows in one direction only is the outcome of accumulation rather than of decision. ### Why does a high product count depress valuation? The count is not itself the problem; the problem is that the cost of complexity goes unmeasured. Unmeasured, it appears as slowing inventory turns, longer changeovers, extended sales cycles, and rising support load, none of which are attributed back to the portfolio decision. Unable to see which items carry the margin, the buy side reads consolidated margin conservatively and narrows its growth assumptions accordingly. ### In a smaller company, how is the portfolio decision made independent of the founder? Delegation presupposes that the delegated decision rests on an objective basis. In practice this means fixing retention thresholds — volume, margin, shared cost burden — in writing before it is known which product they will apply to, and separating the review calendar from the budget cycle. Where the threshold is set in advance, a closure ceases to be a confrontation and becomes an item on a schedule. --- Source: https://www.beirek.com/en/blog/product-portfolio-strategy-due-diligence Publisher: BEIREK LLC — https://www.beirek.com