Hire an AI merger integration manager

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A Day 1 readiness checklist that marks each item ready, not ready or unknown
• One owner and one date for each workstream, such as HR, IT, finance and sales
• A list of what depends on what, with the steps that cannot slip
• A 100-day plan in three phases, with the people and customer risks to watch
• A list of the facts and files still needed before the plan can be trusted

How it does the job well

• Day counts in the profile (such as "Day 15" or "Day -30") are starting points. Label every date PROPOSED and tell the user to check each with the named owner.
• The profile's typical timeframes for savings are rules of thumb, not checked facts. Do not state them as outcomes. Use them only if labelled "profile rule of thumb, not checked".
• Never write "ready" for Day 1 unless the user's own documents confirm it. Use Ready (document seen), Not ready, or Unknown.
• Every workstream has one named owner. If the user gave none, write OWNER NEEDED and do not mark the task planned.
• Do not invent savings, headcount, costs or dates. Use only the user's numbers. Mark planned figures separately from confirmed ones.
• Every workstream has one named owner and a date. Shared accountability is no accountability. If a task lacks a single owner, it is not yet planned.
• Track synergies against a baseline, honestly. Report a synergy bridge with realized vs. planned and call out leakage and one-time costs. Never present gross synergy targets as realized value.

Mistakes it avoids

• Planning every workstream before the reason for the deal is clear.
• Shared ownership. One name per workstream.
• Presenting target savings as realised savings.
• Copying the profile's sample tables as if they were the user's facts.
• Losing commitments buried in long notes.
• Mixing confirmed facts with guesses about other people's plans.

What a good result looks like

An example, not your task: You have bought a smaller company and need a Day 1 list so pay, email and customer service do not break.

• Deal snapshot. What was bought, the close date, the reason for the deal and the integration approach.
• Day 1 readiness. Each check in legal, people, finance, systems, customers and communication, marked ready, not ready or unknown.
• Workstream owners. One owner, first milestone and proposed date for each function.
• Dependencies. Which steps block which, with the critical path marked.
• 100-day plan. Three phases of actions with owners, from stabilising to improving.
• People and customer risks. Risks with who is affected, the action and the owner, plus key people to keep.

How the work is checked

• Every action has an owner and a date, or is marked as missing one.
• Each item points to the note or message it came from.
• The output fits where it will be used, such as one screen or one page.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

Capabilities

• Fix the scope. It confirms the deal facts, the close date and which side is which. It asks once for what is missing, then marks it MISSING.
• Set the approach. It asks why you did the deal and picks an approach, such as fold in fully, keep apart, mix some parts or hold.
• Check Day 1. It goes through legal, people, finance, systems, customers and communication, and marks each item ready, not ready or unknown.
• Assign owners and dates. It gives each workstream one owner and a date. A task with no single owner is marked not yet planned.
• Map the dependencies. It finds the steps that block other steps, such as a legal merger before a system move, and puts them first.
• Plan 100 days and list risks. It sets three phases, lists the people to keep and the customer risks, and tracks seller services to an exit date.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id ma-integration-manager only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/ma-integration-manager/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• The deal in a few lines, such as what you bought, why, the close date, and the size of each side by headcount and customers
• The people and teams on both sides, and who runs each function such as finance, IT, HR and sales
• The main systems, such as payroll, email, accounting software and customer tracking, for each business
• Any services the seller will run for you for a time, with the dates agreed (optional)
• The savings or sales gains the deal was built on, with your own numbers (optional)

Helpful context (optional)

• Current org charts for both businesses.
• A list of contracts that need the other party's consent when ownership changes.
• Your top customers and who owns each relationship.

Tools and access

• Claude, ChatGPT or Gemini with file upload: It can read org charts, a systems list and deal terms next to your description and tie each date to a real document.

Functions and deliverables

• Merger integration manager: Plan your first 100 days after buying or merging with a business. Get a Day 1 checklist, workstream owners, dependencies and the risks to watch.
  • A Day 1 readiness checklist that marks each item ready, not ready or unknown
  • One owner and one date for each workstream, such as HR, IT, finance and sales
  • A list of what depends on what, with the steps that cannot slip
  • A 100-day plan in three phases, with the people and customer risks to watch
  • A list of the facts and files still needed before the plan can be trusted
  Source: Michael Sitarzewski and Agency Agents contributors.
• Sales day briefing writer: Get a sales day briefing: today's meetings with account notes, deals about to close, customer emails waiting and your top 3 actions.
  • Today's meetings with notes on each account
  • Deals closing within 14 days, with stale ones flagged
  • Customer emails waiting for a reply, oldest first
  • A short list of your top 3 actions
  Source: Anthropic.
• 90-day action plan builder: Share an approved decision, owners and start date. Get a 12-week action plan with milestones, check-ins, dependencies and risks.
  • A 12-week milestone table
  • A named owner for each stream
  • A check-in schedule
  • A dependency list
  • A risk list with fixes
  Source: Alireza Rezvani.
• Deal watch digest writer: Get a short deal watch digest: quiet deals, slipping close dates and renewals opening soon, ranked by urgency for your pipeline, tier or team.
  • Short alert list ranked by urgency
  • Quiet and slipping deals
  • Upcoming renewals
  • Competitor mentions
  Source: Anthropic.
• me.md builder: Answer a few questions, or let your AI use what it remembers. Get one private file that tells any AI who you are.
  • One me.md file with up to ten dated sections
  • A list of facts taken from memory, for you to check
  • A short note of what it removed for privacy
  • The two next steps, to save it and set it up

Tasks you can use it for

• You have bought a smaller company and need a Day 1 list so pay, email and customer service do not break.
• Two businesses are merging and nobody can say who owns IT, finance or sales integration.
• The seller will run some services for you for a while, and you want an end date for each.
• Your board or lender asks for a 100-day plan after the deal closes.

Limits to check before starting

• You are still deciding whether to buy, or how to value the deal. Use the Finance decision reviewer or the Business Strategist agent.
• You need legal, tax or regulatory advice on the deal. Take the questions to a lawyer and an accountant.
• You want a plan to help staff adopt new ways of working. Use the Change management consultant.
• You have a normal project with no merger. Use the Project planning manager.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Download the pack from this page and add it to your AI as a skill. If you cannot, paste SKILL.md into a new chat, then paste references/source-agent.md.
• Describe the deal and both businesses in plain words. Say the close date, or say it has closed. Paste the org charts, a systems list and the deal terms if you have them.
• Name who runs each function today. If nobody does, say so. The plan will mark those gaps.
• Read the Day 1 checklist first. Anything marked unknown needs an answer from a real person before the close date.
• Check every date and owner with the people named. Treat the day counts as starting points to adjust.
• Take legal, tax and regulatory points to your advisers. Do not send any staff or customer message without reading it yourself.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/ma-integration-manager for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.