The deal is signed, or about to be. You now have two finance teams, two ways of onboarding a customer, two sets of systems and an integration list longer than anyone can read. Every item on it needs one answer for the combined company.

Your people are doing their normal jobs and the integration on top. Each side also arrives with its own AI subscriptions and its own habits with them. Some of you use ChatGPT, some Claude, some Copilot or Gemini, and nobody has yet said what any of it is for. That is the opening. Decide what AI does for each team now, and the two companies get to the same way of working faster, and bring their best habits with them.

Why AI belongs in the integration plan, not after it.

Integration already asks you to choose one way of doing each recurring piece of work. Each choice is a workflow waiting to be written down. Four reasons to do both at once.

  • One way to do each thing, written once.When finance agrees how the month-end close will run, that agreement is the instruction a workflow needs. Write it once and it serves the integration and the workflow. Write it only in a memo and it serves neither for long.
  • The acquired team’s know-how is most exposed in the first months.The people who know why a customer is handled a certain way are in the room and willing to explain. Capture that while they are there. Their way of working becomes part of the combined company’s, with their name on the good ideas.
  • Both teams have no spare hours.They are running the business and the integration together. A workflow prepares the first draft of a recurring task, so the people in it can give their attention to the decisions the merger puts in front of them.
  • Leaders need one picture.Two org charts and two sets of habits make it hard to see who does what. One plan of teams, roles and work across both companies gives you the picture, and shows where each side already does something well.

What to decide.

The plan answers six questions. You can answer them in a week of focused conversations.

  1. Which teams are coming together?List each team on both sides and the team it joins. Some become one. Some stay two for now, and that is fine to write down.
  2. Which roles carry new work?Name the roles that take on integration tasks, such as the person who now onboards customers from both companies.
  3. Which work repeats enough to become a workflow?Anything done weekly or monthly, where the two companies currently do it differently, is a candidate.
  4. Which way do we adopt?For each, choose the better of the two ways, or a blend. Ask the person who does it which one works.
  5. What should each role be able to do with AI first?Pick one or two things per role, so people start with something they will use on Monday.
  6. Who owns each workflow?One named person decides what it should do and checks what it produces. The workflow prepares. A person decides.

The plan lives in FullyPowered Planner. You set out your teams, their roles and the work between them, and choose what to build first.

One company, two teams of everything.

Illustrative example.

Take a 90-person services company that has just acquired a 30-person firm in the same line of work. Both have a finance team, a customer onboarding team and an operations team. The leadership group builds one plan across all six.

Start with onboarding. The acquirer sends a welcome pack, a checklist and a kickoff call. The acquired firm has a shorter process that customers like, built around one question asked on the first call. The leaders sit the two onboarding leads together and agree one sequence that keeps that question. That agreed sequence becomes the first workflow: it prepares the welcome pack and the call notes for each new customer from the intake form. The onboarding lead from the acquired firm owns it, and she decides what the pack says and approves every change.

Next is finance. The two teams close the month on different calendars and with different checklists. The finance manager from the acquiring side owns the combined close. The senior bookkeeper from the acquired firm takes on the reconciliation steps and writes down how she has always matched the two systems’ exports. A workflow prepares the reconciliation summary each month from the accounting system’s export, and a person reviews every line before it goes anywhere.

In operations, the role that changes most is the scheduler, who now plans work for both companies’ customers. The first workflow for that role prepares a weekly view of upcoming work across both calendars. The head of operations owns it. She notes the three cases the acquired firm handles by phone and the workflow does not, and adds them to the next version.

Who decides what is simple. Each team lead chooses the way of working for their area. Each workflow owner decides what it should do and checks its output. The managing director sees one plan with six teams, eleven roles and the workflows each gets first, and sees which of the two original companies each way of working came from. Each role takes on more, with a workflow behind it.

Where to start this week.

Pick the one team where both sides do the same recurring work differently. Ask each side to describe how they do it, choose one way, and write it down. That page is your first workflow, and it is also your integration decision for that team. Then do the next team.

The AI is already paid for, and this plan is how you get 10X the ROI of your existing AI. The related page on acquisitions and integration shows how this looks from the owner’s chair.