Integrate an acquisition by deciding who runs each company first, then bringing both onto one way of running the business, step by step. This guide is for the owner of a founder-led company who has bought, or is about to buy, a second company while continuing to run the first. Whether to buy at all, and the risks a deal carries, is covered in growing by acquisition. Here we set out the work after closing, using the four stages of the Founder Blueprint: Diagnose, Blueprint, Install and Sustain. If your company already runs on a management system of its own, apply the same responsibilities through it, and adjust the order to whatever the acquisition needs first.

Who runs each company while the integration happens?

Decide who runs your existing business before deciding how much of your time goes into the acquired one. Two companies now draw on one founder, and the first risk is that you become the bottleneck for both. Give that leader authority over routine operating decisions, and write down which decisions still need you and how an urgent exception reaches you.

If that person is your second-in-command, confirm what they can carry while the integration takes your attention. Keep the existing company's weekly meeting and scorecard running. Agree in advance which slip in its results would make you pull back from the integration and return to it.

The acquired company needs its own accountable operating leader. Separately, one integration owner coordinates the changes between the two companies and resolves the dependencies. One person can hold both roles if their current responsibilities leave the capacity, so write down the work being taken off their plate before adding the integration to it.

Keep yourself responsible for direction and for decisions above the integration owner's authority. If every disagreement still comes to you, both companies end up waiting for the same person. Agree before closing who settles a conflict over shared people or budget. If you have already closed, make that decision this week.

What should you diagnose before changing the acquired company?

Diagnose starts with what still depends on the seller. Ask the acquired company's leader to list the customer relationships the seller carries, the approvals that stop when the seller is unavailable, and the operating knowledge employees still have to ask the seller for.

Review the promises made to customers and staff during the sale. Record who made each commitment and who owns the response now. Take questions about contracts, employment terms or benefits to your attorney before confirming any change.

Carry the open findings from your diligence into the operating plan. Ask the people doing the work to show how a customer request travels from order to delivery to payment, and compare their account with the records you bought.

Then establish what can be measured every week. Where a figure is unavailable, give someone the job of finding its source. An unfamiliar process may be serving a customer requirement you have not yet understood, so learn why it exists before you change it.

How do you build one accountability map across both companies?

In the Blueprint stage, build one accountability map for the combined business. The Founder Blueprint works with five to eight critical functions, each with one owner and three key responsibilities. Spend most of the effort on the work that crosses between the companies: for each piece, record who can commit resources and who resolves conflicting instructions.

Mark which functions combine now and which stay separate for the time being. Finance reporting might have one owner while service delivery continues under each company's own leader. Where work stays separate, record each leader's scope and the person accountable for the function overall. "Both teams" is never an owner.

Our guide to mapping critical functions explains how to write responsibilities that can be checked. Apply it first where the two companies depend on each other. If a shared employee receives competing instructions, the map should say who resolves them.

The Blueprint also names six to ten core processes. Identify them once ownership is clear, and keep the differences in how the acquired company delivers where its customers need them. Ask each process owner to record every handoff between the companies and how completion is confirmed.

What should you install before combining systems?

In the Install stage, set up a weekly scorecard for the acquired company and a view of the combined business. Keep the existing company's results visible on their own, because a combined total can hide a decline in either company.

The Blueprint's weekly scorecard carries five to twelve metrics, with cash first. Give each metric an owner and a written definition, and agree one reporting cutoff for both companies so leaders compare figures from the same week. Mark missing data openly and assign its correction.

Build the rolling 13-week cash forecast with the acquisition's own obligations in view: financing payments and any deferred payment to the seller, each as its own line next to operating payments. Ask your accountant how the agreed obligations should enter the forecast, and take tax questions to your tax adviser. Show which company makes each payment and the cash available to it. Add the expected cost of the integration itself, including any period of paying for overlapping staff or software, and name the person who approves that spending. Ask your advisers about any limits on moving cash between the companies. Update the forecast every week against what was paid and received.

Bring the acquired company's leader into the weekly leadership meeting. Review cash first, then the scorecards. The integration owner brings the decisions that need coordination, each with a recommendation and a named owner for the action.

Which decisions belong in the first weeks?

We recommend leaving what customers experience unchanged in the first weeks unless a specific problem requires action. Some things should not wait. Check who controls the bank accounts, payroll and administrator access to the acquired company's systems, and confirm the team can make authorized payments. Get cash visibility, settle who decides what, and tell employees and key customers whom to contact.

Use the table to give each decision an owner and a review date set by its urgency. The roles are placeholders for names on your plan. Take any proposed change to employment terms, benefits or contracts to your attorney, and the accounting or tax effects to your accountant or tax adviser.

Integration decisionSettle earlyRevisit by the first quarterly reviewWho owns itWhat to avoid
Customer communicationWho contacts key customers and handles their concernsWhether contact arrangements should changeCustomer relationship ownerPromises the team cannot keep
Employee communicationConfirmed changes and where questions goAnswers to open questions and further updatesAcquired company's leaderAssurances about future roles nobody has decided
Reporting linesEach person's manager and escalation routeWhich responsibilities combineIntegration ownerOne person taking instructions from two managers
Pay and titlesWho answers questions, with your attorney reviewing termsAny proposed change, reviewed by your attorneyPeople ownerPromising changes before review
Systems and dataAccess, and which sources the weekly figures come fromMigration scope and how it will be testedSystems ownerMoving records nobody has checked
PricingCurrent commitments and who approves exceptionsAny proposed change, with contracts reviewed by your attorneyPricing ownerChanging prices before you understand delivery costs
The seller's roleWho receives each handover, and the scope your attorney has reviewedEvidence of completion and what still depends on the sellerIntegration ownerInformal approval authority that never ends
The brand or nameHow the change of ownership is explainedWhether a change serves customersFounderRenaming before you know how customers will read it

We would leave familiar customer contacts and delivery routines that work in place at first, and keep existing software where it can support reliable weekly reporting while you assess a migration. Give every deferred decision an owner and a review date, so waiting is a decision someone made.

Before combining sales teams, settle who owns any overlapping accounts and resolve conflicting commitments made to the same customer. The sales system itself, compensation plans included, is the work of Performance Edge, our sales-system pathway.

What do you need from the seller's handover?

Carlos's own line from his banking years: "Your valuation scales only when your absence doesn't threaten the business." Where the company you bought still depends on the seller, the value you paid for depends on them too, until those responsibilities move to leaders inside the company. Unless the agreement keeps the seller in an operating role, give each one to a named leader with the authority and support to carry it, and check that none of them has landed on you.

Turn each seller dependency into a handover with a named recipient. A customer relationship needs an introduction, followed by contact led by the person taking it over. An approval needs a successor with the authority to make the decision, and knowledge needs to reach someone who will use it in the work.

Agree how you will recognize that a handover is complete: the receiving leader handles the responsibility without asking the seller to step in. Have the integration owner check that evidence before marking it done.

If the seller stays on as an adviser, set out how requests reach them and who decides after hearing their advice, and take the role and any change to its scope to your attorney. Our guide to staying on after selling covers the seller's side of that agreement.

What should the first quarterly review decide?

The first quarterly review is the Sustain checkpoint. Check both scorecards against the priorities agreed after closing. Ask whether each company is running with clear ownership and whether the seller's handover has reduced what depends on them.

Then decide what combines next. A proposed change should name the operating benefit and the owner who will deliver it, and its demands on the existing business should be checked before it is approved. Keep a function separate where combining it would disrupt service or stretch its leader past their capacity.

Review the accountability map for any owner who should change. Set the priorities for the next quarter and define the evidence that will show each one is done. Record what stays separate, with the reason and a date to reconsider it. Shared reporting can be complete while delivery stays separate by choice, and the review is where you make that call on purpose.

What should change if the integration is behind?

If the existing company's scorecard slips, find the cause with its operating leader. Where the integration has drawn people away from existing commitments, defer the integration work that can wait and give that capacity back. Act when the evidence appears, even if the quarterly review is weeks away.

If the acquired company's leader still sends routine decisions to the seller or to you, check the authority they were given and find what stops them deciding. Where the assigned owner cannot carry the responsibility, change the assignment and tell the team affected.

If the cash forecast keeps surprising you, trace each surprise to its source with the finance owner, whether a missing obligation or a receipt that arrived later than assumed. Revisit the pace of the integration against the corrected forecast before approving more work.

At the quarterly review, reset the remaining scope against these findings and keep the original commitments visible, so the team can see what changed and why. A new deadline on its own leaves the cause of the delay in place.

What should you do this week?

If you have just closed, or are about to, start here:

  • Confirm who runs what. Write down who runs each company and who owns the integration. Settle any gap in authority with those people before giving them more work.
  • Hold the first combined weekly meeting. Bring current cash figures and a separate scorecard for each company. Assign every missing figure to an owner and put the acquisition's obligations into the cash forecast.
  • Book the quarterly checkpoint. Ask the integration owner to bring the accountability map and the list of open seller handovers, and agree now how you will judge progress at that review.
Key takeaways
  • Name the leader of your existing business before committing your own time to the integration.
  • Give one person the job of coordinating the integration across both companies.
  • Build one accountability map and a weekly scorecard, cash first, before combining systems.
  • Give every seller handover a named recipient and a test for completion.
  • Use the first quarterly review to decide what combines next and what stays separate.

How much integration you can take on depends on how much your existing company still depends on you. The Leadership Scorecard takes ten minutes and shows where that dependence sits.