Case 18
First 100 Days Integration Plan
Scenario
Your firm has just completed the acquisition of a smaller consultancy. You are the integration lead and must present a first 100 days plan to the steering group in two weeks.
Why this framework
Uses full PINPOINT because the consequence is higher: adds a professional stance, examples, self-checks, your own review before use, and a plan to tweak and test.
Example context
Deal summary: We are acquiring Harbourside Accounting (110 staff, 340 clients) and combining it with our firm (190 staff, 520 clients). Completion is on 1 December. Overlap is mostly in tax and payroll services; Harbourside has a strong audit team we lack. Combined revenue about £38m. Integration principles agreed by the board: 1) No client-facing changes in the first 60 days unless the client asks. 2) No redundancies announced before day 60. 3) Keep both brands until a review at day 100. 4) One finance system by month 9, not earlier. 5) Retention conversations with key people within 14 days. Key people list: Priya Nair (Harbourside audit partner), Tom Eckersley (Harbourside head of payroll), Hannah Doyle (Harbourside IT manager), Marcus Reid (our integration sponsor, finance director), plus six senior managers flagged as flight risks across both firms. Steering group meets fortnightly.
Prompt
Purpose: Draft a first 100 days integration plan for the steering group, protecting clients and key people while we combine the two firms.
Context: Use the attached deal summary, the integration principles agreed by the board, and the key people list. The integration principles are the final word if anything conflicts.
Narrow the ask: Phases for days 1 to 30, 31 to 60 and 61 to 100. For each: goals, key actions, owners by role, and risks. Add a "do not change yet" list. Stop and ask if the principles do not cover something important.
Persona and role: Act as an integration lead who has seen deals fail because people and clients were neglected.
Check your work: For each material claim, label it as [Verified Source], [Inference], [Assumption], or [Unverified]. Cite the source where available. If an unverified or assumed point could materially change the conclusion, flag it for review rather than guessing. Flag any action that relies on information we do not yet have.
Before I use it: I will review the plan with HR and both client leads, and version it so changes can be tracked.
Tweak and test: after the first steering meeting, I will update one phase at a time based on feedback.
Materials (pasted here in place of the attachments):
Deal summary: We are acquiring Harbourside Accounting (110 staff, 340 clients) and combining it with our firm (190 staff, 520 clients). Completion is on 1 December. Overlap is mostly in tax and payroll services; Harbourside has a strong audit team we lack. Combined revenue about £38m.
Integration principles agreed by the board: 1) No client-facing changes in the first 60 days unless the client asks. 2) No redundancies announced before day 60. 3) Keep both brands until a review at day 100. 4) One finance system by month 9, not earlier. 5) Retention conversations with key people within 14 days.
Key people list: Priya Nair (Harbourside audit partner), Tom Eckersley (Harbourside head of payroll), Hannah Doyle (Harbourside IT manager), Marcus Reid (our integration sponsor, finance director), plus six senior managers flagged as flight risks across both firms. Steering group meets fortnightly.Example output from ChatGPT
First 100 Days Integration Plan
Harbourside Accounting Acquisition | Version 0.1 - Draft for Steering Group | 2 November 2026
Integration objective: Protect client relationships, retain critical people, maintain service continuity and build the foundations for a combined firm without rushing changes prohibited by the board.
Overall approach: Stabilise → Align → Prepare.
Combined workforce
300 190 + 110 staff
Combined clients
860 520 + 340 clients
Combined revenue
~£38m Deal summary estimate [Verified Source] Deal summary. Combined client figure is the sum of reported client counts; unique-client overlap has not been assessed.
- Integration roadmap
Days 1-30
1-30 Dec
Stabilise
Protect clients, reassure staff, complete retention conversations and establish reliable governance.
Days 31-60
31 Dec-29 Jan
Align
Map systems and capabilities, resolve operating risks and prepare integration proposals without changing client-facing services.
Days 61-100
30 Jan-10 Mar
Prepare and selectively execute
Consider approved internal changes, assess client impacts and complete the day-100 brand review.
Dates assume completion on 1 December 2026 is Day 1. [Assumption] Calendar-day counting; confirm with the transaction lead. 2. Detailed phase plans Phase 1: Days 1-30 - Stabilise
Goals: No avoidable disruption to clients, immediate attention to retention risks, and clear accountability across both firms.
| Key action | Owner by role | Main risk |
|---|---|---|
| Establish integration governance, decision log and fortnightly steering meetings. | Integration Sponsor - Marcus Reid | Unclear decisions or slow escalation |
| Conduct confidential retention conversations with all identified key people by Day 14. | HR Leads, supported by relevant Partners | Departure of critical staff |
| Reassure clients through existing relationship owners, without changing services or client-facing arrangements. | Both Client Leads | Confusing or inconsistent messages |
| Identify critical tax, payroll and audit delivery commitments and service dependencies. | Practice Leads | Missed deadlines or delivery failures |
| Document IT access, data protection, business continuity and service dependencies without forcing migration. | IT Leads, including Hannah Doyle | Hidden system vulnerabilities |
| Establish a confidential issue and escalation process for employees. | HR Leads | Rumours and disengagement |
Evidence and dependencies
[Verified Source] The board requires retention conversations within 14 days and no client-facing changes in the first 60 days unless requested by the client.
[Verified Source] The key people list identifies Priya Nair, Tom Eckersley, Hannah Doyle and Marcus Reid, plus six unnamed senior managers at flight risk.
[Inference] Retention conversations should cover these nine individuals other than Marcus; his inclusion as a retention priority remains to be confirmed.
[Assumption - review required] HR leads, client leads and practice leads are available and have decision authority. Their names and reporting lines are not provided.
Day-30 exit criteria: Retention conversations documented; critical service dependencies mapped; client escalations tracked; major risks reviewed by the steering group.
Phase 2: Days 31-60 - Align
Goals: Build an evidence-based integration design while maintaining the board's client and employee protections.
| Key action | Owner by role | Main risk |
|---|---|---|
| Map duplicate and complementary services across tax, payroll and audit. | Practice Leads, with Priya Nair and Tom Eckersley | Premature assumptions about synergies |
| Assess the technology landscape, integrations, cybersecurity and data migration dependencies. | IT Leads, including Hannah Doyle | Unsupported integration design |
| Prepare finance-system consolidation requirements and a month-9 roadmap. | Finance Director - Marcus Reid; Finance Systems Lead | Rushed or expensive consolidation |
| Review staff retention signals, capacity and skill gaps. | HR Leads | Loss of critical skills |
| Develop options for the future operating model, including organisational implications, without announcing redundancies before Day 60. | Integration Sponsor and HR Leads | Uncertainty and premature workforce decisions |
| Establish baseline measures for client service, retention and delivery performance. | Both Client Leads; Integration PMO | Decisions without reliable evidence |
Evidence and dependencies
[Verified Source] Harbourside brings a strong audit capability that the acquiring firm lacks; overlap is concentrated in tax and payroll.
[Verified Source] One finance system is required by month 9, not earlier.
[Inference] Mapping operational overlap before making organisational changes reduces the likelihood of losing valuable specialist capabilities.
[Assumption - review required] Baseline service, staff-turnover and client-retention data can be accessed. The materials provide no baseline measures.
Day-60 exit criteria: Service mapping completed; technology dependencies reviewed; proposed operating model documented; workforce implications assessed but not prematurely announced.
Phase 3: Days 61-100 - Prepare and selectively execute
Goals: Implement carefully approved changes, maintain retention and complete the board's scheduled brand review.
| Key action | Owner by role | Main risk |
|---|---|---|
| Present operating-model options with people, client and financial impacts. | Integration Sponsor - Marcus Reid; HR Leads | Decisions driven only by cost |
| Consider internal process alignment where approved and operationally safe. | Practice Leads | Reduced service quality |
| Assess proposed client-facing changes individually before implementation. | Both Client Leads; Steering Group | Client dissatisfaction or loss |
| Produce detailed finance-system migration plan, testing approach and controls for delivery by month 9. | Finance Director and IT Leads | Premature migration or control failure |
| Review retention outcomes and continue engagement with specialist teams. | HR Leads and Practice Leads | Delayed departures after initial reassurance |
| Present both-brand performance and strategic options at the Day-100 review. | Integration Sponsor, Marketing Lead, Both Client Leads | Premature rebranding |
| Submit Day-100 results and the next integration roadmap for approval. | Integration Sponsor | Unclear accountability beyond Day 100 |
Evidence and dependencies
[Verified Source] Both brands must be retained until the Day-100 review.
[Verified Source] The board prohibits announcing redundancies before Day 60; it does not require redundancy announcements after that point.
[Inference] Continuing retention engagement is important even after the initial Day-14 deadline.
[Assumption - review required] The steering group can authorise internal operational changes. Its delegated approval powers are not specified.
Day-100 exit criteria: Brand review completed; future operating model and client-change proposals presented for approval; retention risks reassessed; month-9 finance-system delivery roadmap approved.
- Do not change yet
Board-mandated restrictions
| Item | Restriction |
|---|---|
| Client-facing arrangements | No changes in Days 1-60 unless requested by the client |
| Redundancy announcements | None before Day 60 |
| Brands | Keep both until the Day-100 review |
| Finance system | Do not consolidate before month 9 |
[Verified Source] Board integration principles.
Additional precautionary holds - subject to approval
Do not change audit leadership or specialist team responsibilities before reviewing delivery and retention risks.
Do not merge payroll processes or migrate client data before control and continuity assessments.
Do not consolidate client relationship ownership before both client leads approve the transition.
Do not announce organisational structures before HR assesses their people implications.
[Inference] These protections are recommended, not explicitly required by the board. Steering-group confirmation is needed. 4. Steering group oversight
Fortnightly meetings should cover five measures:
| Indicator | Proposed measure | Accountability |
|---|---|---|
| Key-person retention | Conversations completed by Day 14; unresolved flight risks | HR Leads |
| Client protection | Complaints, escalations, lost clients and delivery incidents | Both Client Leads |
| Service continuity | Missed deadlines and material disruptions | Practice Leads |
| Technology readiness | Critical risks, dependencies and migration readiness | IT Leads |
| Integration governance | Overdue actions, decisions and board-principle exceptions | Marcus Reid |
[Inference] These are proposed measures, not existing reported KPIs. Targets and data sources remain to be agreed.
- Material gaps requiring steering-group clarification
The principles address four critical protections and one retention deadline, but do not establish the full integration governance or control framework.
| Unresolved matter | Why it matters | Status |
|---|---|---|
| Authority to approve exceptions or post-Day-60 client changes | Determines who can authorise potentially disruptive activity | [Unverified] |
| Regulatory, professional and contractual obligations affecting audit, payroll and client data | May require actions that conflict with a board restriction | [Unverified] |
| Confidentiality and terms of the six senior managers' retention arrangements | Could materially affect retention | [Unverified] |
| HR consultation and communications requirements | Affects timing and handling of organisational changes | [Unverified] |
| Month-9 finance-system deadline interpretation | Clarifies whether month 9 means start, end or a specific date | [Unverified] |
Flag for review: Do not assume that board restrictions override any applicable legal, regulatory, professional or contractual obligations.
- Decision requested at the first steering meeting
Approve this as Version 0.1 for planning purposes, subject to HR, both client leads and the relevant control functions confirming the unresolved matters above. Do not authorise client-facing, workforce or technology changes solely through approval of this plan.
The first revision should focus on Phase 1, with feedback and decisions recorded in a change log. Revisit Phase 2 and Phase 3 at subsequent fortnightly meetings.
One clarification is essential before operational sign-off: Do the board's integration principles permit urgent changes required by law, professional obligations, security incidents or continuity risks during the first 60 days, and who has authority to approve them? The supplied principles do not address that exception.
