Annual Client Review Email: 8 Templates for the Yearly Recap

An annual client review email is the one message a year that a client actually reads twice. Get it wrong — bury the number, pad it with adjectives, save the bad part for paragraph six — and it reads like you're hiding something even when you're not.

This post has eight ready-to-send templates: the strong-year recap, the spend-versus-outcome summary, the lessons-learned note, the next-year proposal, the renewal-adjacent version, the mixed-results year, the one-page busy-executive version, and the hardest one — the year that underperformed. Fill in [PERIOD], [HEADLINE RESULT], [SPEND] and [RECOMMENDATION] and send.

When to send an annual client review email#

Send it two to four weeks before the renewal or budget-planning conversation, never in the same email as the renewal ask. The review has to stand on its own as an honest account of the year; if it arrives bundled with a price increase, the client reads every good number as a sales pitch instead of a fact.

The exception is a contract with a fixed annual renewal date inside 30 days. There, the review doubles as the renewal-adjacent version (Template 5) — the year's results are the argument, and the ask is explicit in the same message.

Avoid sending it in the first two weeks of January or the last week of December. Both land in an inbox that's either still on holiday reply or drowning in twelve other year-end recaps. The second or third week of January, or whenever the client's fiscal year actually starts, gets read.

What a good annual client review email includes#

Five things, in this order: the headline result, the spend it took to get there, one thing that didn't work, a specific ask or recommendation for next year, and an easy way to react (a reply, not a 45-minute call booking as the only option).

The order matters more than the content. A client scanning on a phone reads the first two sentences and decides whether the rest is worth opening. If the headline result is buried under three paragraphs of context, most readers never reach it.

The 8 templates#

Copy the bracketed version below. [PERIOD] is the year or contract term, [HEADLINE RESULT] is the one number that matters most to this client, [SPEND] is total cost for the period, and [RECOMMENDATION] is the specific next step you're proposing — not "let's chat."

Template 1: the strong-year recap#

Subject: [CLIENT] — [PERIOD] in review: [HEADLINE RESULT]

Hi [NAME],

[PERIOD] closed with [HEADLINE RESULT] — [X]% ahead of the target we set in [MONTH]. The three things that drove it: [DRIVER 1], [DRIVER 2], [DRIVER 3].

Total spend for the period was [SPEND], which puts cost per [OUTCOME UNIT] at [FIGURE] — down from [PRIOR FIGURE] last year.

One thing that didn't go as planned: [HONEST MISS], and here's what we changed because of it: [FIX].

For [NEXT PERIOD], I'd recommend [RECOMMENDATION]. Full numbers are attached — happy to talk it through if useful, or just reply with thoughts.

[YOUR NAME]

Template 2: the spend-versus-outcome summary#

Use this when the client's finance team, not your usual contact, is going to read it — the number they care about is cost per result, not the story.

Subject: [CLIENT] [PERIOD] — spend vs. outcome summary

Hi [NAME],

Here's the [PERIOD] spend-to-outcome breakdown finance asked for:

Total spend: [SPEND]. Total [OUTCOME] delivered: [HEADLINE RESULT]. Cost per [OUTCOME UNIT]: [FIGURE], versus [BENCHMARK OR PRIOR YEAR FIGURE].

[ONE SENTENCE ON WHAT MOVED THE COST — efficiency gain, scope change, or market condition].

For [NEXT PERIOD] at the same spend level, we'd expect [PROJECTION]. At [RECOMMENDATION — higher or lower budget], the expected range is [RANGE].

[YOUR NAME]

Template 3: what we'd change (lessons learned)#

This one earns trust precisely because it isn't a highlight reel. Use it with a client relationship you want to deepen, not one you're trying to close fast.

Subject: [CLIENT] [PERIOD] review — what worked, what we're changing

Hi [NAME],

[PERIOD] result: [HEADLINE RESULT]. Spend: [SPEND]. Two things worked better than expected: [WIN 1], [WIN 2].

Two things we'd do differently: [MISS 1] cost us [IMPACT] — we're fixing that in [NEXT PERIOD] by [FIX 1]. [MISS 2] was a timing call that didn't pay off; next time we'd [FIX 2] instead.

None of this changes the [PERIOD] number, but it's the reasoning behind [RECOMMENDATION] for next year.

[YOUR NAME]

Template 4: the next-year proposal#

Subject: [CLIENT] [PERIOD] wrap + a [NEXT PERIOD] proposal

Hi [NAME],

Quick [PERIOD] summary before we look ahead: [HEADLINE RESULT] on [SPEND], [X]% versus target.

The biggest opportunity we didn't fully capture this year is [OPPORTUNITY] — [ONE SENTENCE WHY IT MATTERS].

For [NEXT PERIOD], I'm proposing [RECOMMENDATION]: [WHAT IT INVOLVES], estimated at [ESTIMATE], with an expected [PROJECTED OUTCOME].

Worth 20 minutes next week to walk through it, or I can send the full proposal first if you'd rather read it cold.

[YOUR NAME]

Template 5: the renewal-adjacent version#

Send this only when the renewal decision is genuinely inside 30 days — bundling the ask any earlier makes the whole recap read as a pitch.

Subject: [CLIENT] [PERIOD] results + renewal for [NEXT PERIOD]

Hi [NAME],

[PERIOD] closed at [HEADLINE RESULT] on [SPEND] — the full breakdown is attached.

Your current term runs through [DATE]. Based on this year's results, I'd recommend renewing at [RECOMMENDATION — same scope, expanded scope, or adjusted terms], which would carry the [DRIVER] that worked this year into [NEXT PERIOD].

If it's easier to review the numbers first and talk renewal after, that's fine too — just flag a date that works before [RENEWAL DEADLINE] so there's no gap in service.

[YOUR NAME]

Template 6: the hard version — a year that underperformed#

Subject: [CLIENT] [PERIOD] review: [HEADLINE RESULT], below target

Hi [NAME],

[PERIOD] came in at [HEADLINE RESULT], which is [X]% below the [TARGET] we set in [MONTH]. I want to walk through why, and what we're doing differently.

Total spend was [SPEND]. The two biggest factors behind the miss: [CAUSE 1] — which affected [X]% of the shortfall — and [CAUSE 2]. Neither is something we're using as an excuse; here's what's already changed: [FIX 1], [FIX 2].

For [NEXT PERIOD], I'd recommend [RECOMMENDATION], which directly addresses [CAUSE 1]. I can send a full diagnostic if useful, or we can get on a call this week — whichever gets you comfortable faster.

[YOUR NAME]

Template 7: the mixed year#

Subject: [CLIENT] [PERIOD] review — mixed results, straight numbers

Hi [NAME],

[PERIOD] was uneven: [METRIC A] beat target at [FIGURE], [METRIC B] missed at [FIGURE]. Full table attached rather than a narrative — the numbers say it better than I can.

The short version: [ONE SENTENCE ON WHAT DROVE THE WIN] and [ONE SENTENCE ON WHAT DROVE THE MISS].

For [NEXT PERIOD], my recommendation is [RECOMMENDATION] — it leans into what worked on [METRIC A] and directly targets the gap on [METRIC B].

[YOUR NAME]

Template 8: the one-page version for a busy stakeholder#

Use this for a CFO, founder, or anyone who forwards the email to someone else to read the details. Three bullets, nothing under them.

Subject: [CLIENT] [PERIOD] — three numbers

Hi [NAME], the short version of [PERIOD]:

• Result: [HEADLINE RESULT], [X]% vs. target
• Spend: [SPEND], cost per [OUTCOME UNIT] at [FIGURE]
• For [NEXT PERIOD]: [RECOMMENDATION]

The hard version, in more detail: presenting a bad year#

Template 6 works because of the order it puts things in, not the words. The number that missed goes in the subject line and the first sentence — not the third paragraph, not after two sentences of context, not softened with "a challenging period." A client who has to hunt for the bad number assumes you were hoping they wouldn't find it.

After the number, the structure is diagnosis, not defense: name the cause, quantify how much of the shortfall it explains, and state the fix that's already in motion — not one you're proposing to think about. "We're evaluating options" reads as no plan. "We've moved [X] to [Y], effective [DATE]" reads as already handled.

Resist explaining every factor. One or two real causes, stated plainly, land better than five, because five reads as a list of excuses regardless of how honest each one is. If there genuinely were five contributing factors, pick the two that mattered most and offer to walk through the rest live.

What to do if there's no reply#

Give it a full week before following up — an annual review often needs to be read alongside a client's own year-end numbers, which they may not have yet. A one-line nudge after seven to ten days ("Wanted to make sure this landed before [budget cycle] — happy to jump on a quick call if that's easier") works better than resending the same email.

If there's still no response after two follow-ups, the read is usually not disinterest — it's that the email asked for more than a reply could give. Offer the shortest possible next step: a yes/no question, a single date suggestion, or an explicit "no action needed, just flagging" if the review genuinely doesn't require one.

A client who reads a strong-year recap and says nothing is not always a bad sign; some stakeholders only reply to bad news. If the relationship is otherwise healthy and the numbers were good, one follow-up is usually enough before moving on to the next scheduled touchpoint.

A faster way to pull the numbers together#

The template solves the writing problem. The slower part is usually upstream of that: pulling twelve months of thread history, prior status updates, and the numbers you promised in January back out of an inbox to check what actually changed. That's the part that turns a 20-minute email into a half-day task done once a year, under deadline.

AI Emaily — we build it — keeps a running brief per client thread rather than a single annual archive, so the headline result, the spend figures mentioned along the way, and the commitments made mid-year are already surfaced when the review comes due, instead of re-read from scratch. Its drafting sits on a Personal Context brain and per-client profile you set, not on scanning your sent history, so a first draft of the recap matches how you'd actually phrase it to that specific client — you edit the number in and the tone stays yours.