Realising synergies post-M&A in the electronic components business

The electronic components industry is in constant motion. New application fields emerge while others disappear, and players along the value chain are continuously reorganising themselves. Distributors realise economies of scale via buy-and-build strategies; component manufacturers acquire competitors or expand their business with dedicated product lines. Behind almost every one of these transactions lies the same business case — a combination of operational (cost) synergies and cross-selling (revenue) synergies promised by the deal model. Whether a good deal ultimately turns into a disappointing one is usually decided by whether these synergies are actually captured — and whether this can be proven.

The part of the deal model that rarely arrives on time

Cost synergies behave predictably. They are easier to estimate, they impact the P&L relatively soon after closing, and industry benchmarks place their realisation at 70 to 85 percent of the target. With revenue synergies, it is a different story. McKinsey's cross-selling study shows that the majority of revenue synergies take three to five years to materialise, that the average gap between target and result is around 20 percent, and that fewer than one in five of the surveyed companies actually achieved their cross-selling goals. In electronic component distribution, top-line synergies often land at only a quarter to a third of what the deal model had accounted for.

This gap is not a rounding error — it is the point where the return on investment of a buy-and-build platform quietly drains away. The model credits cross-selling revenues to years one and two; reality delivers them in years three to five, if at all. Within a typical PE holding period, every quarter of delay works against the exit multiple. The critical question after closing is therefore less about whether the synergies exist, and more about how fast the combined organisation begins converting them into revenue.

Why cross-selling stalls — and why it is structural

The classic approach to capturing these synergies is well known: consolidate portfolios, train the sales force on the newly added lines, create collateral, conduct enablement, and wait for the pipeline to reflect it. Each of these steps is sensible. In total, however, they have a long lead time — often many months before the first cross-selling effect becomes a reality.

In the meantime, a sales representative sitting in front of an unfamiliar line card with an existing quota to meet does the obvious thing: they sell what they already know how to sell. This is usually described as inertia, making it sound like a motivation problem that could be solved with a short-term bonus or a pep talk. It is not. The knowledge that would make the newly acquired portfolio sellable — which acquired component fits which existing customer, which design-in is worthwhile — resides in two places that the representative cannot easily access: in the transaction histories of two still-separate systems and in the heads of a handful of experienced Field Application Engineers. McKinsey's own analysis of sales capacity puts it in a nutshell: as long as you do not provide the sales force with tools that expand what they can sell, no additional cross-sells are generated — you merely displace existing ones. The barrier is structural, not personal.

This is also why waiting for full IT consolidation is such an expensive standard path. Harmonising two ERP or CRM environments — two system landscapes that have grown over years and are set up differently — routinely takes 18 to 36 months. Postponing commercial growth until the backend is unified means leaving the most valuable time window of the holding period to competitors who are already actively pitching to the combined customer base.

Making the combined portfolio visible early after closing

The alternative is to completely decouple commercial execution from system integration. Guided selling achieves this by merging the transaction history of both entities, using predictive analytics and machine learning to identify the patterns that historically preceded a won deal, and mapping these patterns onto currently open customer opportunities. The effect: newly acquired lines become visible within the context of a customer's specific buying behaviour — not as an abstract catalogue for the representative to memorise, but as a concrete recommendation attached to an account they are already managing.

Crucially, the two backends do not need to be merged first. It does not require a unified ERP or CRM and tolerates common data quality issues — missing attributes, inconsistent formats, and part numbers that do not quite match. What it needs is a lean mapping layer: matching parts between both catalogues via the Manufacturer Part Number, linking customers via a shared identifier, and sorting products into a common taxonomy. This master data harmonisation remains inevitable anyway — the point is not to avoid it, but to bring forward the commercially relevant part of it: a lean, early-prioritised step that represents a fraction of full consolidation and unlocks commercial value while the remaining harmonisation continues on its own timeline. This is precisely what turns "we will cross-sell once the systems are merged" into "we can make cross-selling opportunities visible early after closing". Where exactly this shortcut reaches its limit is an open question: if both entities carry truly poor master data — free-text manufacturer info, no clean part numbers — the mapping itself can turn into a project rather than a matter of a few weeks. The threshold where the effort tips is real, and it should be addressed honestly.

Maximising the BOM in every opportunity

The same logic extends from which line to introduce to how much of a specific design to win. In electronic components, a design-in during a customer's new product introduction secures multi-year production revenues with defensible margins — making every incoming BOM a synergy opportunity, not just a quoting transaction. When recommendations are proactively generated in the context of an opportunity, a quote becomes more than a single-line reaction: it is an opportunity to highlight likely pin-compatible second sources from the newly acquired supplier line, flag a plausibly functional equivalent part with a better margin profile, or suggest a recently released component family that fits the electrical and footprint specifications — each subject to approval by the technical expert. Executed well and played against the combined portfolio, this increases the share of every BOM that the merged business wins — without having to get the sales force fully up to speed on tens of thousands of new part numbers first.

The operational side — what the approach touches and what it does not

A clarification upfront: the bulk of cost synergies in a distribution merger does not lie here. It lies in the warehouse and logistics network, in back-office consolidation across finance, HR, and IT, and in purchasing leverage through pooled procurement volumes. This approach does almost nothing to affect any of that. What it addresses is a narrower, often neglected area — the commercial-technical operations between sales and portfolio.

In this area, the greatest impact is on capacity in Applications Engineering. FAEs spend a significant portion of their time — by most estimates, well over half — on manual research: reading datasheets, checking parametric suitability, verifying stock, and cleaning unformatted customer BOMs. If the data layer instead presents them with commercially validated options for evaluation, this time is transformed into customer-facing work. None of this replaces technical judgment. These recommendations are based on past transactions and expert experience in a specific context that is never identical to the concrete design-in — the value is therefore not a validated answer, but a ranked, pre-filtered shortlist that the expert must still sign off on. What changes is where the expert's time goes: from gathering options to evaluating them. It is not about a smaller team, but about more technical throughput from the same capacity — and that is precisely what allows the combined business to handle higher project volumes without a corresponding increase in engineering headcount.

At the same time, it mitigates something that buyers usually leave untouched: because verified substitution logic and application experience are now stored centrally rather than in the heads of a few senior engineers, the departure of a key person costs significantly less — and a capacity consolidation assumed in the deal model becomes responsible rather than negligent. The knowledge that made the target company worth buying in the first place no longer leaves the building with individual people.

The same shift shortens the onboarding of new and younger employees. Bringing an inside sales representative or a junior FAE in component sales to productive autonomy normally takes months of absorbing implicit knowledge; if the system delivers customer context and verified recommendations, this curve flattens — which matters especially when teams are restructured after a deal.

Two other levers are worth mentioning. Proactively matching the active BOMs of both entities against EOL and PCN notices turns end-of-life events from a last-minute scramble into managed substitution, reducing the costs of short-term emergency procurement and obsolescence risks. Furthermore, the consolidated transaction base reveals where the portfolios of both entities overlap — as overlapping franchise lines for the distributor, or as intersecting product lines for the manufacturer. This is the foundation for proactive portfolio management: where the same demand is served twice, lines can be consolidated in a targeted manner — and for the distributor, purchasing volumes can be bundled for better terms. This final lever is more strategic than day-to-day, but it is truly data-driven — and difficult to leverage without a consolidated view of both companies. None of this dictates where the boundary between what a data layer should decide and what remains with the commercial team should lie — this boundary is drawn differently in every organisation, and it is perhaps a more interesting question than the technology itself.

What cannot be measured cannot be managed

The final advantage is that all of this can be tracked. Cross-selling conversion, design-in win rates, margin on optimised lines, and revenue per employee are observable at the level of the individual prompt and its outcome. This is not reporting for reporting's sake — it is what allows commercial leadership to track progress against the Value Creation Plan and give a board something more credible than a narrative. McKinsey's study points in the same direction: commitment correlates most strongly of all factors with cross-selling success, and sustained commitment depends on early, visible wins that dashboards can show and leadership can recognise. Measurability and momentum reinforce each other.

None of this suggests that the classic integration approach was wrong. It was the rational response to the tools available at the time. What has changed is that the data both companies generate anyway can now be utilised much earlier in the holding period — shifting the real question: no longer whether these synergies can be captured, but when, and how early is early enough for a specific deal. This answer depends on the alignment of both portfolios, the state of the data, and the length of the holding period — and that is exactly the kind of question that should be thought through on a case-by-case basis before the window of opportunity that the deal was meant to exploit closes.