Customers

When you lose a big customer: the first week decides the damage

By Scavi Company · · 6 min read
When you lose a big customer: the first week decides the damage

It usually arrives as a short, polite message. A large account is going in another direction, effective at the end of the month. What follows in most service businesses is a week of the wrong activity — chasing replacement revenue before anyone has looked at the cash position, which is the part that actually threatens the company.

A cash problem first

The instinct is to start replacing revenue immediately. That instinct costs more than the account did, because it skips the only calculation that determines how much time you have.

Before anything else, three numbers:

  • What is still owed by that customer, and when it will actually arrive
  • Fixed costs for the next ninety days
  • How many weeks of operating expenses you can cover without that revenue

Why the order matters. That calculation is the difference between a difficult quarter and an emergency — and those two situations call for opposite decisions about staffing and spending. Making staffing decisions before knowing which one you are in is how a recoverable loss becomes a permanent one.

The order of the first week

  • Day one and two. Cash position. Collections on anything outstanding, including from that customer, while the relationship is still warm.
  • Day three. Fixed costs. What can be paused without damaging capacity you will need in ninety days.
  • Day four. Capacity. What the crew now has available, and which existing customers have work you have been too busy to take.
  • Day five. Pipeline. Only now — and starting with past customers, which is the fastest revenue available.

Keep reading — free

The rest of this article is worth the 20 seconds

Tell us where to send it and the full piece unlocks right here, along with everything else on this blog.

Rather just talk? Message us on WhatsApp.

The conversation worth having anyway

By the time a decision is communicated it was made weeks earlier and discussed internally. Pushing against it usually confirms it.

What is worth doing is asking, without defensiveness, what drove the decision and what would have had to be different. That answer is the most valuable information you can get, and no customer who is staying will ever give it to you.

Leave the relationship in good condition. A meaningful share of lost accounts return within two years when the replacement disappoints — and they return to companies that handled the exit gracefully.

Measuring the risk before it arrives

No single customer above 20% of revenue; above 30% deserves active attention. The exact threshold matters less than knowing the number, which most owners do not.

Concentration feels like success while it happens. A large steady account smooths the calendar and simplifies operations — and that comfort is exactly what makes the loss dangerous.

A loss in numbers

A company at $1.4M annual revenue loses an account worth $390,000 — 28% of the business.

  • Fixed monthly costs: $62,000
  • Cash on hand: $88,000. Outstanding from that customer: $41,000
  • Runway without the account, before any action: about ten weeks

Ten weeks is uncomfortable and workable. The owner who knows it is ten weeks protects the crew and rebuilds. The owner who does not know it lays off two technicians in week one and cannot take the work that arrives in week six.

Find out how exposed you are to losing one account

Send us your revenue by customer for the last twelve months. We will show you your concentration risk in one number.

Frequently asked questions

What should you do first after losing a large account?

Look at cash, not at sales. The instinct is to start replacing the revenue immediately, and that instinct costs companies more than the account did. Before anything else, calculate three things: what is still owed by that customer and when it will actually arrive, what your fixed costs are for the next ninety days, and how many weeks of operating expenses you can cover without that revenue. That calculation determines whether this is a difficult quarter or an emergency, and those two situations call for completely different decisions. Only after it is done does it make sense to think about staffing, spending and pipeline — because each of those decisions depends on how much time you actually have.

Should you try to win a departing customer back?

Have the conversation, but not as a rescue attempt. Once a decision has been communicated it has usually been made weeks earlier and discussed internally, and pushing against it tends to confirm it. What is worth doing is asking clearly and without defensiveness what drove the decision, because that answer is the most valuable information available to you and you will never get it from a customer who is staying. Ask what would have had to be different, and whether the door is open later. Leaving the relationship in good condition matters more than most owners expect: a meaningful share of lost accounts return within two years when the replacement disappoints, and the ones that return almost always go back to a company that handled the exit gracefully.

How much revenue from one customer is too much?

A common rule is that no single customer should exceed 20% of revenue, and anything above 30% deserves active attention. The exact threshold matters less than knowing the number, which most owners do not. Concentration feels like success while it is happening, because a large steady account smooths the calendar and simplifies operations, and that comfort is precisely what makes the loss so damaging. The useful habit is reviewing revenue by customer quarterly and treating the top one as a risk rather than an achievement. When concentration is high, the responses are the same regardless of trade: build pipeline while things are good rather than when they are not, spread delivery so no single relationship holds all the institutional knowledge, and keep a cash reserve sized against the largest account rather than against average monthly expenses.