Problems we fix

Companies after an acquisition

Customers lost while an acquisition is put together

In the year after a deal the customers notice before the books do: a new invoice, a different rep, a service call that slipped while two teams worked out who owns it. Nobody decides to lose them, and nobody sees it until renewals come in short.

The combined customer list, read every week for the accounts going quiet, is how a growing company keeps what it paid for.

$200K

per $10M of combined revenue

At $50M of combined revenue: about $1M revenue at risk in the year after the deal. On McKinsey's published range for merging companies and a revenue figure you can change. Your numbers change it, below.

What it costs

  • 2%

    of combined customers a merging company typically loses in year one (McKinsey, low end)

  • 5%

    at the high end of the same range

  • $200K

    at risk for every $10M of combined revenue

  • $1M

    at risk at $50M combined revenue, our starting point

On McKinsey's published range for merging companies and a revenue figure you can change.

Where the money goes

Exhibit 1

Each point of customers lost costs about $500K a year

$0$750K$1.5M$2.3M$3.0MMcKinsey, low end: $1.0MHigh end: $2.5MCustomers lost in the year after the deal (%)06
  1. The curve

    • Combined annual revenue, both companies at $50M, our assumption: a starting point; enter your own.

Source: Drivingseat model on the inputs in the model below; every default sourced or labeled an assumption there.

Exhibit 2

Run it on your own numbers

$1.0M

revenue at risk in the year after the deal · an estimate

Nothing you type leaves this page.

Source: Revenue at risk = combined annual revenue × the share of customers a merging company typically loses. The share is the low end of McKinsey's range, so it is a floor, not a forecast; the revenue is yours to put in.

It counts only customers who leave, not the ones who stay and buy less.

What gets built

  1. Join both companies' customers and orders, matched account by account.

  2. Watch every account each week for the signs it is going quiet: orders down, tickets up, a new rep, a disputed invoice.

  3. Hand the accounts at risk to the people who can keep them, with the reason, before a renewal says so.

How the outcome is proven

The number

Revenue kept from accounts flagged at risk

On your combined customer data: which accounts are already going quiet, what they are worth, and who should call them this week. You see it on day ten, before you decide anything.

Ten days

Frame · days 1–2

We map the process and name the one doubt that keeps the project from being funded. You get a written go or no-go, and it can be an honest no.

Prove · days 3–10

A working slice that answers that doubt on real inputs. You leave with the prototype, the number, the full project map and a quote for the build.

Ten days fits inside your deadline, not after it.

How we work: the ten days, the fixed fee and the two ways to start

Fair questions

Our customers are loyal. Does this apply?
Then the number is a floor you can check in a week: the combined customer list, read for who ordered less since the close.
Is this an integration project?
No. It is ten days on your own customer data to show who is going quiet, before a renewal says so.

Sources

  1. where mergers go wrong (mckinsey.com)

See this on your own company

Tell us your company and we will build this page on what we can read about you, within a week. Or put your real numbers in with us in 25 minutes.

hello@drivingseat.co