Several portfolio companies need finance support, technology talent and stronger reporting.
Each is considering an India team.
For a private equity sponsor, bringing those requirements together can look attractive. A shared India platform may reduce duplication and give smaller businesses access to capabilities they would struggle to build alone.
But there is a practical complication.
Portfolio companies have different customers, leadership teams and growth plans. They may also be sold to different buyers at different times.
The decision therefore needs to go beyond the cost of running one centre versus several.
It needs to consider how the model will work today—and how each business could operate independently later.
Start with what you want to share
“One India platform” can describe several arrangements.
It could mean a common service provider, shared facilities, a recruitment function, or a separate entity delivering services to multiple companies.
These choices do not all require the same level of integration.
Similarly, separate GCCs do not have to duplicate every supporting activity. They may use common vendors or facilities while retaining distinct teams and systems.
Define the options before comparing them.
Be specific about which activities, people, technology and legal arrangements would be shared.
Otherwise, one stakeholder may be discussing shared office costs while another assumes a fully integrated operating model.
Those are very different decisions.
Compare the work, not just the function names
Two companies may both need finance support while having very different requirements.
One may process high transaction volumes through a standard system. Another may need specialist revenue accounting and close attention to customer contracts.
The same applies to engineering, analytics and customer operations.
Look for similarities in processes, tools, skills, service expectations and risk.
Repeatable work with common requirements may be easier to share. Activities closely tied to a company’s product, customers or intellectual property may need dedicated ownership.
This assessment should happen at the activity level.
A broad label such as “finance” or “IT” can conceal differences that will later make shared delivery difficult.
Make accountability clear from the beginning
A shared platform needs a clear way to handle competing demands.
What happens when two portfolio companies need urgent support at the same time? Who decides which request takes priority?
Agree on service expectations, capacity planning and escalation before launching.
Each participating company should understand what it is buying, who is accountable and how performance will be reviewed.
Dedicated teams inside a shared platform may be appropriate where business context matters.
The sponsor can set common expectations while still giving portfolio company leaders a meaningful say in service priorities.
Without that balance, the platform can become a source of frustration for both the companies and the people delivering the work.
Test the economics with a full cost view
A comparison based mainly on salaries and rent will miss important differences.
Include leadership, systems, security, transition effort, coordination and company-specific requirements.
Then consider how costs would be allocated.
A flat percentage may be convenient but difficult to justify if one company consumes substantially more support.
The OECD’s Transfer Pricing Guidelines discuss intra-group services, including the benefits received and appropriate charging approaches. Whether particular rules apply depends on the entities, relationships and jurisdictions involved.
Have the relevant advisers assess the structure rather than assuming common sponsorship creates one uniform tax group.
Operationally, the charges should be understandable enough for company leaders to see what drives their bill.
Keep data and intellectual property boundaries visible
Shared delivery does not require unrestricted access across portfolio companies.
Identify who can access each company’s information, where it is stored and how its use is controlled.
Consider dedicated environments or other appropriate separation where the work requires it.
Ownership of code, models, documentation and other intellectual property should also be explicit.
NIST’s guidance on cybersecurity requirements across suppliers and partners is a useful reference when defining responsibilities within a shared delivery arrangement.
The practical test is whether a company can explain who has access to its information and why.
That clarity matters during normal operations, incidents and future due diligence.
Design the exit path before committing
Imagine one portfolio company is sold next year.
Can its people, data, licences and processes be separated? Which services would it still need from the platform?
Estimate the time and cost of moving to a buyer’s systems or establishing independent support.
Also examine what happens to the remaining companies.
A departing business may leave unused capacity or fixed commitments behind. Someone will need to bear those costs.
If temporary support could be required after a sale, consider how a transition services arrangement would work.
A shared platform should have a credible separation plan, even when no sale is imminent. The ability to separate should be tested through identified dependencies rather than assumed from a clause in an agreement.
Choose the structure that fits the portfolio
A shared platform may suit common, repeatable work where companies can agree on service standards and maintain clear boundaries.
Separate GCCs may fit businesses with distinct capabilities, sensitive information or a strong need for independent control.
A hybrid can combine shared support with dedicated delivery teams.
Evaluate each option against service quality, total cost, leadership needs, security and separation effort. Then test the preferred model with a limited scope before expanding it.
At Enorbe, we believe India operating models should reflect both the portfolio’s immediate needs and each company’s longer-term direction. If you are comparing shared delivery with separate GCCs, mapping one company’s journey into—and eventually out of—the proposed structure can be a useful place to start.
