Tuck-in versus new platform brand: how we decide which a deal is.

We have written in concentration is the strategy about why a five-brand portfolio is the right shape for the firm, and in integration anti-patterns about the things we deliberately refuse to consolidate across the portfolio. The tuck-in versus new-platform decision sits inside both frameworks and is the place where, in practice, the discipline gets tested most often.

What a tuck-in actually requires

The tuck-in label is over-applied in lower-middle-market M&A. A real tuck-in requires three conditions to hold simultaneously, and the conditions are restrictive enough that most deals labeled as tuck-ins are not.

1. Customer base overlap

The target's customer base has to be substantially coverable by the parent brand's existing go-to-market motion. Not the same industry — the same buyer, in the same role, with the same procurement process. When the overlap is real, the tuck-in collapses two customer-acquisition motions into one and the cost synergies are immediate. When the overlap is industry-level rather than buyer-level, the tuck-in is a new motion pretending to be a synergy and the cost structure does not improve for years, if ever.

2. Workflow overlap

The target's product has to live in the same workflow the parent brand's product lives in. Adjacent workflows in the same industry do not count. The test is whether the same end user, in the same week, would naturally use both products in sequence to complete the same end-to-end job. If yes, the tuck-in compounds because the bundled product is genuinely more useful than the sum of its parts. If no, the tuck-in is a multi-product bundle the customer did not ask for, and we have written about when bundling compounds and when splitting is the honest answer.

3. Data model overlap

The target's data model has to be reconcilable with the parent brand's data model in a sensible amount of engineering time. Reconcilable means the two systems can ship a meaningful joint feature within a year of close without a full data-platform rebuild. When the data models are genuinely close, the joint feature compounds inside the workflow and the integration is worth doing. When the data models diverge in their core abstractions, the integration becomes a permanent engineering tax that the joint feature never pays back.

When all three conditions hold

When all three conditions hold, the tuck-in is the right structure and the economics are excellent. The integration ships fast, the go-to-market is unified, the customer feels a better product, and the cost structure flattens. The single brand that emerges is stronger than either of the two it absorbed, which is the entire point. The tuck-ins we have done where all three conditions held cleanly were among the best capital deployments in the portfolio.

When the three conditions hold, the tuck-in is the easiest deal we ever do. When they do not, it is the deal we will regret most.

When even one of the three conditions does not hold

When even one of the three conditions does not hold, the right structure is a new platform brand. The target stays its own brand, runs its own go-to-market, and sits on the shared services platform alongside the other platform brands. The economics are different, slower in the first year because there is no cost synergy to harvest, and stronger over the long hold because the operating team and the customer base are not being asked to absorb a tuck-in that does not fit. Cobalt Glacier's default is to err on this side. The cost of treating a new platform as a tuck-in is operator continuity, which is the asset we are most unwilling to spend.

The conversation with the founder

Founders almost universally prefer being a new platform brand to being a tuck-in. The reason is straightforward: a tuck-in usually means the founder's company name goes away, the founder's team is absorbed into a parent team, and the founder's role shifts from CEO of a company to a senior leader of a product line. None of those are unreasonable outcomes when the tuck-in fits, but they are real and the founder feels them immediately. We are explicit in every deal conversation about which path the target is on, and we are explicit that the default is new platform unless the three conditions above hold cleanly.

The economic difference

• Multiple paid. Tuck-ins justify a slightly higher headline multiple because of the synergies. New platforms are underwritten standalone, with no synergy assumption in the model.
• First-year operating plan. Tuck-ins carry an integration plan as a board commitment. New platforms carry the same first-100-days plan we run on any acquisition, with no integration overlay.
• Brand and product continuity. Tuck-ins usually involve a planned brand retirement and a product migration. New platforms keep both permanently.
• Operating team integration. Tuck-ins consolidate functions where the parent brand has clear strength. New platforms keep the operating team intact and lean on the shared services platform only where the brand asks.

The common mistakes

The most common mistake is calling a deal a tuck-in because the synergy story is easier to underwrite. The deal team knows the synergies are aspirational. The operating team that has to deliver them knows it too. The integration starts, the synergies do not arrive, and the brand spends years untangling decisions made for a story that was never accurate. The fix is to hold the three-condition test honestly and to walk if the test is being failed.

The second most common mistake is the inverse: treating a real tuck-in as a new platform out of an excess of caution. When the three conditions hold cleanly, the tuck-in is the structure that produces the most value for the customer, the team, and the holding company. Being conservative when the conditions hold is leaving compounding on the table.

How we evaluate the three conditions in practice

The three conditions look clean on the page and are messier in practice. Customer base overlap is evaluated by running the target's customer list against the parent brand's existing pipeline and active accounts; an overlap above forty percent of total contract value usually clears the bar, and below twenty percent usually does not. Workflow overlap is evaluated by sitting with three real users of the target's product and walking them through the parent brand's product in the same session; if the users naturally describe the two products as part of the same job, the bar is cleared. Data model overlap is evaluated by having a senior engineer from each product draw the core entities on a whiteboard together; if the entities collapse to a shared model with a week's worth of work, the bar is cleared. The on-paper diligence is suggestive, the in-room diligence is decisive, and we do not sign on a tuck-in until all three of the in-room sessions have happened.

The bottom line

Every acquisition after the initial platform brands are in place is either a tuck-in or a new platform brand, and the choice is determined by whether the customer base, the workflow, and the data model materially overlap with an existing brand. Cobalt Glacier's default is new platform. Tuck-ins are the exception we do when the conditions hold cleanly. The discipline is in protecting operator continuity even at the cost of headline synergies, because the operator continuity is the asset that compounds for the rest of the hold.

If you are an investor evaluating how Cobalt Glacier allocates capital across the portfolio over time, start a conversation with our investor team. The tuck-in versus new-platform decision is one of the most consequential allocation decisions the firm makes, and the framework above is how we keep the decision honest.