A Strong Investment Thesis Is Not an Operating Model

What private equity investors and portfolio leaders need to control during the first 100 days after closing.

A transaction can be financially compelling, strategically sound and thoroughly diligenced, yet still begin destroying value shortly after closing.

The problem is rarely the investment thesis itself.

It is the gap between the deal model and the operating reality.

Before closing, attention is concentrated on valuation, financing, legal structure, commercial potential and the value-creation plan. Once the transaction completes, the organisation must suddenly translate those assumptions into decisions, reporting, accountability and operational change.

That is where the real execution risk begins.

Legal ownership can change overnight. An operating model cannot.

The value-creation clock starts immediately

Private equity investors operate within a defined investment period. Every month matters, particularly in leveraged transactions where financial commitments, reporting requirements and performance expectations begin immediately.

This changes the speed of the organisation.

A performance issue that might previously have been tolerated for a quarter may now need to be addressed within weeks. Management teams are assessed. Targets are revised. Reporting becomes more structured. Investment decisions face greater scrutiny.

That pace is not automatically unreasonable or destructive. It reflects the economic reality of the transaction.

But speed creates its own risk.

When decisions accelerate before reliable information, clear ownership and operational control are established, management can move quickly in the wrong direction.

The first priority should therefore not be transformation at maximum speed. It should be establishing enough control to make good decisions quickly.

Why Day 1 is often more fragile than expected

The legal transaction receives most of the pre-close attention. The operational transaction is frequently less mature.

This becomes particularly visible in carve-outs and asset deals, where essential capabilities may need to be transferred or rebuilt:

• Payroll and employee administration

• Banking authorities and financial controls

• Customer and supplier contracts

• Software licences and cloud subscriptions

• Identity and access management

• Devices, networks and security services

• Fleet cards, insurance and physical assets

• Data ownership and reporting

• Vendor relationships and support agreements

• Business-critical passwords and local knowledge

Individually, many of these items appear manageable. Collectively, they create hundreds of dependencies across finance, HR, legal, IT, security and operations.

If one dependency is missed, the impact can be disproportionate. Employees may not be paid. Orders may not be processed. Systems may become inaccessible. Reporting may become unreliable. Customers may notice disruption before management understands its cause.

For the first 30 to 60 days, parts of the organisation may feel broken.

That does not necessarily indicate a bad acquisition. It indicates that operational continuity was underestimated or that too many assumptions remained untested before closing.

Integration needs an owner, not just a plan

Most transactions have a plan. Fewer have one person who is genuinely accountable for the integrated outcome.

Instead, each function manages its own workstream:

• Finance owns reporting.

• HR owns people.

• IT owns systems.

• Legal owns contracts.

• Operations owns continuity.

• The sponsor monitors progress.

The problem is that the greatest risks sit between those workstreams.

Who decides whether a system must be migrated immediately or temporarily retained? Who determines whether local processes represent inefficiency or essential operational knowledge? Who resolves a conflict between rapid standardisation and customer continuity?

Without clear integration governance, those decisions are delayed, escalated inconsistently or made within functional silos.

A credible integration model requires:

1. One accountable integration owner

2. Explicit decision rights

3. Named workstream owners

4. A shared dependency register

5. Defined escalation paths

6. A limited set of operational and financial indicators

7. A regular decision forum, not merely a reporting meeting

More meetings do not automatically create control. In fact, they can hide its absence.

The objective is not to maximise communication. It is to ensure that decisions are made by the right people, using reliable information, before risks become incidents.

A good investor can still build a bad company

One operator described a PE-backed roll-up that went through four CEOs in two and a half years. Excessive spending and poor leadership contributed to a dramatic deterioration in profitability. When the company eventually collapsed, the financing structure also left other equity holders with little remaining value.

It was one case, not a universal verdict on private equity.

But it illustrates an important distinction.

Being good at evaluating investments does not automatically make someone good at assembling leadership teams, integrating companies or building an effective operating model.

The transaction may be correct while the execution is poor.

Value can be destroyed through:

• Replacing leadership too frequently

• Installing executives who do not understand the business

• Standardising processes before understanding why they exist

• Cutting capabilities that appear expensive but protect revenue

• Investing heavily without clear ownership of outcomes

• Forcing portfolio companies into a model that does not fit

• Using unreliable data to drive aggressive performance decisions

• Confusing visible activity with measurable progress

Profit maximisation is only one dimension of value creation. Sustainable value can also come from improved resilience, stronger management, better data, lower risk, greater market share or increased capacity to scale.

That requires operating judgement, not only financial discipline.

What the first 100 days should achieve

A 100-day plan is often presented as a list of initiatives. This makes it look comprehensive, but not necessarily useful.

Its purpose should be much more specific: establish control, protect continuity and create the conditions for value creation.

By the end of the first 100 days, investors and management should have:

• A reliable operational and technology baseline

• Clear accountability across the organisation

• Visibility of material risks and dependencies

• Stable financial and management reporting

• A prioritised integration roadmap

• A defined target operating model

• An agreed approach to standardisation

• A realistic investment envelope

• Retention plans for critical people

• Measurable outcomes for the next phase

This does not mean that integration is complete.

Ninety to 120 days may be enough to stabilise the organisation, validate assumptions and establish governance. Technology, data, process and organisational integration can take substantially longer, particularly across complex platforms or international environments.

Declaring integration complete too early does not reduce the remaining work. It simply removes attention from it.

The questions that should be answered before closing

The first 100 days become significantly easier when the right questions are addressed during diligence and integration planning.

Before closing, investors and management should be able to answer:

• What absolutely must work on Day 1?

• Which operational failures could interrupt revenue or customer delivery?

• Which systems and vendors support critical processes?

• Where does the business depend on undocumented local knowledge?

• Which decisions must be taken immediately, and which can wait?

• Which capabilities should be integrated, separated or temporarily retained?

• Is management information reliable enough to steer the business?

• Which people are critical to continuity and future value creation?

• Who owns the integration across functional boundaries?

• What would cause the value-creation plan to fail?

These are not exclusively technology questions.

Technology connects financial reporting, customer operations, supply chains, employees, data, security and management control. It is often where hidden operational dependencies become visible first.

That makes technology readiness a business issue, not a technical workstream.

Closing is the beginning

A completed transaction creates ownership. It does not create alignment, control or integration.

The strongest investors and management teams recognise this distinction early. They do not assume that a compelling investment thesis will translate itself into operational performance.

They identify what can break, assign ownership before ambiguity becomes delay and establish reliable information before accelerating change.

A strong investment thesis explains why the company should create value.

A strong operating model determines whether it actually will.

Planning an acquisition, carve-out or portfolio integration? Galactus helps investors and management teams identify Day 1 risks, establish integration governance and translate technology decisions into operational control.