Introduction: The promise and reality of portfolio standardisation
Open with the case that PE firms and multi-brand groups see in technology standardisation: reduced costs through vendor consolidation, operational leverage through shared services, better data visibility across the portfolio, and faster integration of acquisitions. Acknowledge that the logic is sound but the execution is where most efforts stall or destroy value.
Frame the article as a practical guide to identifying where standardisation genuinely helps and where it creates more problems than it solves.
Where standardisation genuinely helps
Shared services: security, identity, and infrastructure
Describe the high-value, low-disruption standardisation targets: shared security operations, centralised identity management, common cloud infrastructure, and pooled DevOps capability. Explain why these work well because they sit below the application layer and can be adopted without changing how portfolio companies operate their businesses.
Vendor leverage: aggregating spend for better terms
Cover how consolidating vendor relationships across a portfolio creates significant negotiating leverage. Provide examples: enterprise agreements for cloud infrastructure, volume discounts on SaaS platforms, and preferred partner rates with systems integrators. Explain that this is often the fastest path to measurable portfolio-level value.
Data visibility: consistent reporting without platform convergence
Explain how standardising data definitions, reporting frameworks, and KPIs across portfolio companies enables meaningful comparison and portfolio-level dashboards without requiring everyone to use the same systems. Cover the importance of a common data layer or warehouse that aggregates from diverse source systems.
Knowledge sharing and talent mobility
Describe the softer but significant benefit of creating a technology community across the portfolio: shared lessons learned, internal talent mobility, and collective problem-solving on common challenges like integration, data quality, or vendor management.
Where standardisation creates friction
Forcing platform convergence too early
Explain why mandating that all portfolio companies adopt the same commerce platform, ERP, or CRM is typically a mistake. Cover the reasons: different companies have different scale requirements, market positions, and technical maturity levels. Forced convergence disrupts operational teams, consumes disproportionate capital, and often delivers a worse outcome than the systems it replaced.
One-size-fits-all governance
Describe how overly prescriptive governance frameworks create resistance and slow down portfolio companies without delivering proportional value. A startup-stage company and a mature mid-market retailer need fundamentally different levels of process and oversight.
Underestimating migration costs
Warn about the tendency to underestimate the cost and disruption of migrating portfolio companies to standardised platforms. Cover hidden costs: data migration, integration rebuilds, retraining, lost productivity during transition, and the opportunity cost of technology teams focused on migration rather than commercial delivery.
A phased approach
Phase 1: Assess the landscape (months 1 to 3)
Describe the essential first step: conducting a structured technology assessment across the portfolio. Cover what to evaluate: platform inventory, integration landscape, technical debt levels, team capability, vendor contracts and renewal dates, and data architecture. Emphasise that you cannot prioritise standardisation without this baseline.
Phase 2: Quick wins through vendor consolidation (months 2 to 6)
Explain how to identify and execute vendor consolidation opportunities. Cover the process: map vendor overlap, identify contracts approaching renewal, aggregate volume, and negotiate enterprise or portfolio-level agreements. Highlight that this phase often self-funds subsequent standardisation efforts.
Phase 3: Introduce shared services selectively (months 6 to 12)
Describe how to stand up shared services where there is genuine duplication and clear value: centralised security monitoring, shared data platform, common CI/CD infrastructure, or pooled specialist skills. Emphasise the importance of making these services genuinely useful rather than mandated.
Phase 4: Establish governance and reporting frameworks (months 6 to 18)
Cover how to implement lightweight governance: a portfolio technology council, standardised health metrics, investment review processes, and architectural guidelines that set guardrails without dictating implementation choices. Stress that governance should enable speed, not create bureaucracy.
Governance models that work
The portfolio technology council
Describe how to structure a cross-portfolio technology governance body: composition (portfolio CTO, company CTOs, operating partner representative), cadence (quarterly with ad hoc for major decisions), scope (standards, shared services, major investment review), and authority (advisory rather than directive for most decisions).
Guardrails, not mandates
Explain the difference between setting architectural guardrails (API standards, security baselines, data privacy requirements) and mandating specific technology choices. Argue that guardrails enable autonomy within boundaries, which generates less resistance and better outcomes than top-down mandates.
Balancing autonomy and alignment
Provide a practical framework for deciding which decisions should be made at the portfolio level (security standards, vendor negotiations, data definitions) versus at the company level (platform selection, team structure, delivery methodology). The principle is: standardise where there is genuine portfolio-level value; leave operational decisions to the people closest to the business.
Measuring portfolio technology health
A consistent assessment framework
Propose a lightweight framework for assessing technology health across portfolio companies: platform currency, technical debt levels, integration maturity, team capability, security posture, and delivery velocity. Explain how consistent measurement enables comparison and prioritisation without requiring uniform systems.
Leading indicators vs lagging indicators
Cover the importance of tracking leading indicators (deployment frequency, technical debt trend, team retention) alongside lagging indicators (incident count, cost, project delivery). Leading indicators reveal problems before they become crises.
Using health metrics to guide investment
Explain how portfolio-level technology health metrics inform capital allocation decisions: which companies need investment in technical debt reduction, where shared services could reduce cost, and which acquisitions carry technology risk that needs to be priced into the deal.
Conclusion: Standardise the outcomes, not the tools
Reinforce the core message that effective portfolio standardisation focuses on shared outcomes (visibility, security, cost efficiency, delivery quality) rather than shared tools. Encourage operating partners and portfolio CTOs to resist the allure of platform uniformity and instead invest in the connective tissue that makes a portfolio more than the sum of its parts.
What to read next
If you found this useful, these related pieces go deeper on specific aspects:
- The retail operating model nobody talks about addresses the company-level operating model changes that portfolio standardisation often requires at the individual business level.
- Post-acquisition technology playbook: the first 100 days covers how to approach technology in the immediate post-acquisition period, before standardisation becomes the primary focus.
- Technology due diligence: what investors actually need to know examines how to assess technology risk and readiness at the point of acquisition, which directly informs the standardisation strategy.
Next steps
If you are developing a technology strategy across a PE portfolio, get in touch to discuss how an advisory engagement might support the work.
What to read next
- Technology due diligence: what investors actually need to know — The assessment framework that informs which portfolio companies need standardisation investment and where to prioritise.
- Post-acquisition technology playbook: the first 100 days — The operating rhythm that creates the foundation for effective portfolio-level standardisation.
- The retail operating model nobody talks about — The product-led technology model that makes standardisation sustainable across a portfolio.