Turning one subsidiary's capability into an advantage across the group
An operating capability within one portfolio company may address a need elsewhere in the portfolio. Transferring it requires understanding the cause of performance, testing its usefulness in a new setting and protecting the capacity of the team providing it.
A subsidiary may possess a capability that other portfolio companies need: training technicians, diagnosing returns, preparing complex quotes or qualifying suppliers. Yet that capability may remain attached to one team and absent from any shared development plan.
An investor can examine what it already owns before recruiting or purchasing another solution. The task is to identify a transferable capability and establish whether it can create value in a different setting.
Strong performance is a signal, not an explanation. Fewer returns may reflect a better method, but could also result from a simpler product range or a different customer base.
To isolate the capability, compare sufficiently similar situations. Examine the actual work: information collected, decision criteria, tools, expertise required and exception handling. Establish what explains the outcome and what depends on context.
The receiving subsidiary must have a specific problem that the capability can address. An impressive demonstration is insufficient justification for deployment.
Consider an illustration: one service team can distinguish product failure from installation problems. Another subsidiary incurs numerous returns that it struggles to diagnose. A trial could cover a limited set of comparable cases, using a qualified technical specialist and agreed validation criteria.
The test should measure diagnostic quality, time required, errors and total cost. Counting cases processed is not enough.
Transfer takes people's time. Without reserved capacity, it may undermine the performance that made the subsidiary valuable in the first place.
Both companies need to agree on the time involved, who pays for it, who is responsible for the work delivered and what happens if their priorities conflict. Sharing a capability should benefit both companies, without weakening the one providing the help or creating extra costs for it. The contribution should also receive recognition: a subsidiary should not be penalized against its own targets for helping the group.
Depending on the need, the capability may be shared through training, a temporary assignment, a common tool or a shared service. A central structure makes sense only if volume, quality and economics justify it.
Rights to use tools, confidentiality requirements and authorized data access also need checking. Common portfolio ownership does not automatically permit every exchange.
Contact Mirabilys to identify an operating capability in one portfolio company and design a trial in another. The proposed objective is to establish its value and transfer cost before committing to wider deployment.
How can you tell whether a performance is transferable?
By understanding its cause. Strong performance is a signal, not an explanation: compare sufficiently similar situations and examine the actual work to separate what explains the outcome from what depends on context.
How should internal demand be tested before deployment?
The receiving subsidiary must have a specific problem the capability can address. A limited trial on comparable cases, with a qualified specialist and agreed validation criteria, measures diagnostic quality, time, errors and total cost.
How is the team providing the capability protected?
The two companies agree on the time involved, who pays for it, who is responsible for the work delivered and what happens if their priorities conflict. A subsidiary should not be penalized against its own targets for helping the group.
Book a 30-minute discovery call
For owners of 1-20 M$ businesses. A fixed-fee mandate, identical for every client: six weeks, nine components.