Tell the Client About the Bad Month Before They Find It

A bad month almost never costs you the client. But the silence around it sure does.

Work with enough clients and you’re going to hit a rough patch. A campaign stuck in the learning phase. Conversion rates that don’t pan out against your model. Pipeline that comes in softer than you forecasted. Growth never moves in a straight line, and after enough of these you quit acting surprised.

The dip isn’t the problem. What you do in the days around it is.

The damage happens in the gap, not the data

Here’s where account teams trip up. They keep the bad news in their own head. The campaign’s soft, they know it’s soft, and they decide to sit on it until they’ve got a fix to pair with it. It feels responsible. It’s the opposite.

Because the client has a dashboard too. And the worst version of this is the one where they find the dip before you mention it, where they’re the ones forwarding you the screenshot asking what’s going on.

That’s the moment the relationship takes the hit. Not the soft month. The fact that they saw it first.

And it compounds in a way that’s hard to walk back. The next quiet week gets read as something being hidden, whether or not anything is.

Once a client catches a problem before their agency flags it, every report after that gets read differently. They stop trusting the narrative and start auditing the numbers. You’ve trained them to look over your shoulder.

Set the range before you need it

The fix is almost boring. You name the rough patch before it happens.

When a strategy meeting ends with a timeline that bakes in a slow ramp and a range of outcomes, your team comes off like they’ve done this before. The client hears month three might be bumpy, and when month three is bumpy, you’re not delivering bad news. You’re confirming a forecast. That’s a completely different conversation.

When it doesn’t, a few weeks of soft numbers turns into a fire drill. Same data. Wildly different client experience. The only variable that changed is whether anyone said it out loud first.

Not every dip needs a phone call

The reasonable objection here is that if you flag everything, you sound like you’re always making excuses, and you train the client to panic at noise.

That’s a real risk, and it’s why the range matters more than the alert. Pre-negotiating a band of expected outcomes is what earns you the right to stay quiet inside it. If you said month three runs soft and month three runs soft, you don’t owe anyone an emergency call. You owe them a line in the regular update confirming you’re where you said you’d be.

The call is for when you leave the band, or when you know you’re about to. That’s a much smaller number of moments than “every time a metric moves down,” and it’s the difference between a team that’s on top of it and a team that cries wolf.

This is why strategy can’t sit a department away

You can’t run this play if the people who read the early signals aren’t in the room.

If your specialists and contractors get the info five days late and take two more to respond, the dip is already a week old before anyone with authority weighs in. You’re on your heels before your team can get back to the client. The lag isn’t a staffing detail. It’s the whole problem.

With strategy embedded alongside account management, your team catches the dip early and the client gets the fix before they ever feel the problem. The bad month becomes a non-event because it was handled while it was still small.

There’s nothing clever about any of this. It’s just how you run client services after you’ve been thrown into the fire more times than you’d like to admit.