Agencies
Presenting results to a client without losing the meeting
What to show first, how to explain a bad month, what to do when the client asks for a metric that doesn't matter, and how to close with a decision.
Also available in: Português · Español
The results meeting is almost always lost in the first two minutes, and for the same reason: it starts with what the team did instead of what the client wants to know.
Open with the number that decides
The client has one question in their head before the meeting starts: is this worth it?
Everything said before answering it is heard as preamble. And if the answer arrives at minute twenty, attention is already gone.
Opening with that number — cost per result, return, number of sales, whatever fits the business — changes the tone of the whole meeting. If it's good, the rest is heard with an open mind. If it's bad, it gets discussed while there's still time.
The structure that works
One: how it went. The headline number, against the previous period and against target.
Two: why. The concrete cause of the movement. Not "the algorithm", not "the market" — the decision, the creative, the audience, the budget change.
Three: what was done. The period's actions and their effect.
Four: what's next. The plan, with a verifiable commitment.
Five: the discussion. And there has to be real time left for this.
The first four parts should take less than half the meeting. A presentation that consumes all the available time left no room for the only part that produces decisions.
The bad month
This is the relationship's stress test, and the right answer is counterintuitive: say it first, not last.
A client who discovers the bad result at minute thirty, after twenty slides of metrics that went up, doesn't conclude the month was average. They conclude someone tried to hide it — and that does more damage than the result.
The formula that holds trust has three parts: what happened, why it happened, what's being done. All three concrete, none generic.
And a warning: if the cause was a team mistake, say so. Clients tolerate admitted mistakes far better than explanations that don't add up.
When they ask for a metric that doesn't matter
It happens often: the client asks about reach, followers, impressions. Metrics that move a lot and decide little.
Refusing to show them is a relationship mistake. The client asked for something and got a no, with the feeling that information is being withheld.
What works is showing them and placing them: what they measure, what they relate to, and why they aren't the number governing decisions. "Reach rose forty percent because we widened the audience; what that tells us is that more new people are entering, and we'll judge it by what happens to cost per lead over the next two weeks."
Over time, that explanation repeated reshapes the conversation better than any head-on argument.
What not to show
The Ads Manager screen. Hundreds of columns with no hierarchy, and a guaranteed question about the least relevant number on screen.
Every campaign. Including the ones that barely spent. They dilute attention and hide the ones that matter.
Screenshots as proof. If you need to demonstrate the numbers are real, an accessible dashboard does it better than an image.
Unnecessary jargon. CBO, ABO, lookalike, ThruPlay. Every term the client doesn't use is a moment where they stop listening to decode.
Close with a decision
A results meeting that ends with "let me know if anything comes up" produced nothing.
What should remain at the end is at least one jointly made decision: raise the budget or not, try the new channel or not, change the offer or not. Even if the decision is to keep everything the same, it has to be explicit.
That also protects the team: a decision agreed in the meeting is a shared decision. A change made without mentioning it is a decision the team answers for alone.
When the client compares you to another agency
It comes up eventually: "someone I know pays half that cost per lead." The defensive reaction is automatic and almost always goes badly.
The better move is the opposite: take the data seriously and ask for context. What product, what ticket, what channel, what definition of a lead. Nine times out of ten the comparison collapses on its own — different market, different conversion, or a figure from two years ago.
And the tenth time it's real and there's something to learn. Treating the comparison as information rather than an attack produces better conversations and, occasionally, a concrete improvement.
The dashboard between meetings
Much of the client's anxiety between meetings comes from not being able to look. That anxiety turns into after-hours messages asking for isolated numbers.
Giving access to a dashboard with current data solves more than it seems: a client who can look whenever they want asks less, not more. What generates the question isn't curiosity, it's lack of visibility.
It also changes the meeting's character: it stops being the moment the numbers are revealed and becomes the moment they're interpreted, which is where the value actually is.
Three phrases that quietly do damage
Some very common expressions erode trust a little at a time.
"The algorithm changed" — sometimes true, and it always sounds like an excuse; save it for when there's concrete evidence.
"That's within the industry average" — the client isn't investing to be average, and the average is rarely verifiable.
"We should see an improvement soon" — with no concrete action beside it, it's an empty promise that gets collected next month.
All three share the same flaw: they explain without committing. A concrete cause, even an uncomfortable one, holds the relationship far better.
Don't promise a result in the meeting
Under the pressure of a bad month, the temptation to commit to a specific number for next month is strong. Resist it.
What can be promised is actions: three new creatives, an audience review, separating the brand campaign. What can't be promised is the number an auction market will produce.
Promising a result turns the next meeting into a judgment on a promise, rather than a conversation about a business.
To separate what decides from what merely moves, see vanity metrics.
For the document that accompanies the meeting, see the monthly marketing report. And for the dashboard that updates itself, see the paid traffic report.
Frequently asked questions
Which number should open the meeting?
The one the client uses to decide whether to keep investing: almost always cost per result or return, not reach or impressions.
What if the client asks for an irrelevant metric?
Show it and explain what it measures and what it doesn't. Refusing creates distrust; showing it without context creates bad decisions.
How long should the presentation run?
Short enough to leave room for conversation. A meeting with forty minutes of talking and five of discussion decided nothing.
Should I share the Ads Manager screen?
Rarely. Ads Manager has too much information and no hierarchy; it invites questions about numbers that don't matter.