Organisation & Workforce

Post-merger integration

Compares two organisations' structures and roles for post-merger integration, extracting overlaps and metrics into a scored risk plan for the people workstream.

  • Organisation & Workforce
  • Traceable reasoning
  • Runs anywhere
Preview methodology

4–6 weeks ~40 minutes

Including the external research pass

No coding required

Input
Structure, role and headcount documents from both entities
Output
A people and organisation integration plan
Runs in
Skillsize · ChatGPT · Claude · Copilot
Export
SKILL.md · MCP
Time saved
~4–6 weeks per run

— USE CASES

What people use Post-merger integration for

Day-one and day-100 planning

Structure the people and organisation integration plan against evidence from both entities.

Overlap and duplication analysis

Identify duplicated roles and functions across the two structures with coverage analysis.

Integration risk reporting

Score and report the people risks that most threaten synergy delivery.

What it works from

  • Structure, role and headcount documents from both entities
  • Deal rationale and synergy targets
  • Integration principles and constraints

What you get back

  • A people and organisation integration plan
  • Overlap, duplication and coverage analysis
  • Scored integration risks with actions

— HOW IT BEHAVES

How Post-merger integration produces its result

The mechanics behind this specific template — what it reads, what it calculates, and where a human stays in the loop.

Scored against your criteria

Assessment happens against criteria you control and weight, so the same standard applies on every run.

Coverage, both directions

A coverage pass shows what is supported and what is not — including requirements with nothing behind them and material that supports nothing.

Numbers pulled from documents

Metrics buried in narrative documents are extracted as data you can compute with.

Live external research

Current external sources are researched during the run rather than recalled from training data, and the sources travel with the output.

Branching on the evidence

The path taken depends on what the analysis found, so thin cases and strong cases are handled differently by design.

Composed as work product

Findings are written up as a document that reads like professional output rather than raw model text.

Why this is expensive by hand

Every organisation & workforce team needs post-merger integration — and almost none of them do it the same way twice. In practice it shows up as day-one and day-100 planning: structure the people and organisation integration plan against evidence from both entities. The value sits in the rigour, not the typing — yet the rigour is exactly what gets traded away when there is only 4–6 weeks of capacity for it.

How this Skill produces it

Here the same job runs as a Skill. Your material goes in; a people and organisation integration plan comes out, alongside overlap, duplication and coverage analysis. What sits between input and output is the codified method: thresholds, sequencing and the points where a human confirms a call — all of it visible and editable in the Skill. The practical effect: 4–6 weeks of manual work becomes a ~40 minutes run, held to an identical standard on the tenth engagement as on the first.

Who it's for

  • Independent consultants codifying their own methodology
  • Strategy and transformation teams standardising delivery
  • Internal advisory functions under pressure to produce faster
  • Operators who need defensible output, not a one-off chat answer

Run it in Skillsize — or export it anywhere

Post-merger integration exports as a structured SKILL.md file and is MCP-ready, so the same method runs in ChatGPT, Claude, Copilot or your own AI products. Adapt it to your methodology, and the intelligence stays yours — not locked to one vendor.

ChatGPTClaudeCopilotAI Products (MCP)

More Organisation & Workforce Skills

Browse the full library →