Blog/ Email writing & templates

QBR Invitation Email to a Client: 8 Templates That Get a Yes

Nafiul HasanNafiul Hasan· 9 min read
A QBR invitation email open in an inbox, with a calendar and a decisions-needed list beside it

The short answer

A QBR invite that gets accepted leads with the decisions on the table, not the word 'review.' Name [DECISIONS NEEDED] in the subject or first line, attach a short pre-read, propose one time with an alternative, and list who needs to be in the room and why. Send it 10–14 days out, and follow up once by email before you ever pick up the phone.

8 QBR invite email templates: first review, routine, exec sponsor, pre-read, reschedule, async, and the skipped-QBR version.

On this page
  1. 01When should you send a QBR invitation email?
  2. 02What should a QBR invite actually contain?
  3. 03The templates
  4. 041. First-ever QBR with a new account
  5. 052. The routine quarterly
  6. 063. Exec-sponsor invite
  7. 074. Pre-read attachment note
  8. 085. Reschedule
  9. 096. Async QBR instead of a meeting
  10. 10The hard version of this situation
  11. 11What to do if there's no reply
  12. 12How does AI Emaily fit into QBR scheduling?

Most QBR invites get skipped for a reason that has nothing to do with scheduling: the subject line says "Q3 Business Review" and the client reads that as an hour of you talking at a deck. Nobody clears their calendar for a review. They clear it for a decision they're on the hook for.

The eight templates below swap the framing — decisions and dates up front, review second — and cover the situations that actually come up: the first QBR with a new account, the routine quarterly, the one where an exec sponsor needs to be in the room, the pre-read note, the reschedule, the async version for a client who won't take another meeting, and the harder invite to someone who's ghosted the last two.

When should you send a QBR invitation email?#

Send it 10–14 days before the proposed date. That's enough runway for a client-side calendar with three or more stakeholders, and short enough that the date doesn't drift before anyone confirms it.

Two exceptions: if the account is at renewal risk, send the invite the moment you decide a QBR is the right venue, even if that's three weeks out — a contentious renewal conversation needs more lead time than a routine check-in. And if the client has skipped the last two QBRs, don't lead with a new invite at all; that's a different email, covered below.

  • 10–14 days out: the default for a routine or first-time QBR
  • 3+ weeks out: renewal at risk, multiple exec stakeholders, or a contract decision on the agenda
  • Anytime you have news that changes the account's trajectory — don't wait for the calendar quarter

What should a QBR invite actually contain?#

Five things, in this order: the decision(s) you need from them, who needs to attend and why, the proposed date with one alternative, what you're bringing (the pre-read), and how long it actually takes. Everything else is optional.

ElementWhy it's in the emailWhat happens if you skip it
Decisions neededTurns a status update into a meeting they're accountable forReads as optional; gets declined or no-shown
Named attendees + roleClient can staff the room correctly the first timeWrong people show up, real decision-maker is absent
Date + one alternativeOne round-trip instead of a scheduling threadThree emails just to land on a time
Pre-read attachedLets them walk in with an opinion, not coldMeeting becomes a data dump instead of a conversation
Stated durationSets expectations against a full hour they don't haveAssumed to be 60 minutes; declined on sight

Lead with the decision, not the word 'review'

"Need your call on [DECISIONS NEEDED] before renewal" gets opened. "Q3 Business Review" gets archived for later and forgotten. Same meeting, different subject line.

The templates#

Eight versions below. Swap the bracketed fields — [QUARTER], [ATTENDEES], [DECISIONS NEEDED], [PRE-READ] — for the real ones before you send. None of these need a signature block spelled out; use whatever you already sign off with.

1. First-ever QBR with a new account#

The first QBR sets the tone for every one after it, so this version explains what a QBR with you looks like before asking for the meeting.

Subject: Setting up our first quarterly review — 45 min, [DATE]
BodyHi [NAME], We're coming up on your first quarter with us, so I'd like to set up a short quarterly review — partly to walk through what's landed so far, partly to get your read on [DECISIONS NEEDED] before we plan Q[NEXT]. Proposing [DATE/TIME], with [ALT DATE/TIME] as a backup. 45 minutes, and I'll have a one-page pre-read over to you a few days ahead so we're not spending the meeting on background. Who else from your side should be in the room — anyone who owns [RELEVANT AREA]? Let me know which time works.

2. The routine quarterly#

For an account where the QBR is expected and the relationship is healthy — keep it short.

Subject: Q[QUARTER] review — need your input on [DECISIONS NEEDED]
BodyHi [NAME], Time for our Q[QUARTER] review. I'd like your take on [DECISIONS NEEDED] while we're both looking at the numbers, so let's put 30 minutes on the calendar. [DATE/TIME] or [ALT DATE/TIME] — whichever's easier. [ATTENDEES] plan to join from our side; happy to keep it to the two of us if that's simpler for you. Pre-read coming [X] days before.

3. Exec-sponsor invite#

When a decision needs sign-off above your usual contact, invite the executive directly and give them a reason to actually attend — not a courtesy CC.

Subject: [DECISIONS NEEDED] — need 30 min with you and [CONTACT NAME]
BodyHi [EXEC NAME], [CONTACT NAME] and I have been working through [CONTEXT], and it's reached the point where we need your call on [DECISIONS NEEDED] before we move into Q[NEXT]. I'd like to bring this to a short quarterly review — 30 minutes, [DATE/TIME] or [ALT DATE/TIME] — with [CONTACT NAME] and [ATTENDEES]. I'll send a one-page summary beforehand so the meeting is just the decision, not the background.

4. Pre-read attachment note#

Send this 3–5 days before the QBR, separate from the original invite, so the pre-read doesn't get buried in a calendar description nobody reopens.

Subject: Pre-read for Thursday's review — 5 min
BodyHi [NAME], Attached is the pre-read for our review on [DATE] — [PRE-READ]. It's four pages: what shipped this quarter, the two metrics that moved, and [DECISIONS NEEDED] laid out with our recommendation. If you can skim it beforehand, we'll spend the meeting on your questions and the decision rather than walking through it live. Flag anything that's missing and I'll fold it in before we meet.

5. Reschedule#

Own the reschedule in the first line, offer two new times immediately, and don't make the client do the work of finding a replacement slot.

Subject: Need to move Thursday's review — two new options
BodyHi [NAME], Something's come up on my end for Thursday's review — apologies for the short notice. Could we move to [DATE/TIME] or [ALT DATE/TIME] instead? Everything else stays the same: [DECISIONS NEEDED] is still the main item, and I'll get the pre-read to you regardless of which day we land on.

6. Async QBR instead of a meeting#

Not every quarter needs a live meeting. If the account is stable and the decisions are low-stakes, propose the written version and offer a call only if they want one — this respects a busy client's calendar more than defaulting to 45 minutes on the books.

Subject: Skipping the meeting for Q[QUARTER] — written review instead
BodyHi [NAME], Given how steady things have been, I don't think we need a full meeting for this quarter's review. I'll send a short written summary covering what shipped, the two numbers worth flagging, and [DECISIONS NEEDED] by [DATE]. Reply with your thoughts, or if you'd rather talk it through live, say the word and I'll set up 20 minutes.

The hard version of this situation#

A client who's skipped the last two QBRs isn't going to accept a third invite that looks like the first two. Naming that directly, without blame, and shrinking the ask usually works better than repeating the same invite louder.

Subject: 15 minutes on [DECISIONS NEEDED] — no full review needed
BodyHi [NAME], I know the last two quarterly reviews didn't happen — no worries there, calendars get away from everyone. I'd still like your call on [DECISIONS NEEDED], since it affects [WHAT IT AFFECTS], so let's skip the full review format. Could we do 15 minutes on just that one topic? [DATE/TIME] or [ALT DATE/TIME]. If neither works, tell me your week and I'll fit around it.

Lead with the decision, not the pattern

The brief for this situation is specific: name what you need a call on, not how many times they've skipped. A client who feels called out declines faster than one who's just given a smaller, easier ask.

That's the shift across every template above: the review is the vehicle, the decision is the reason to show up. A client scanning a crowded inbox has to see the decision to justify clearing 30 minutes.

Before and after comparison of a QBR invite subject line — a generic review title versus one naming the decision needed
The subject line is where most QBR invites lose the client before the body is ever read.

What to do if there's no reply#

One follow-up by email, three to four business days later, then a different channel if that goes quiet too. Don't send a third identical email — it reads as nagging and trains the client to skim past you.

  1. 1

    Wait 3–4 business days

    Give the original invite time to surface in a normal inbox rhythm before assuming it was missed.

  2. 2

    Follow up once, shorter than the original

    Restate only the decision and the two proposed times. Don't re-explain the whole agenda.

  3. 3

    Switch channel if still quiet

    A Slack message, a call, or asking a secondary contact to flag it — email has clearly stalled at this point.

  4. 4

    Propose the async version

    If live scheduling keeps failing, offer the written-review format from template 6 instead of a fourth meeting request.

How does AI Emaily fit into QBR scheduling?#

Writing the invite is one email; chasing the reply, drafting the follow-up, and re-sending the pre-read reminder is three more, and that's the part that actually eats a CSM's afternoon across a full book of accounts.

AI Emaily drafts QBR invites, reschedules, and no-reply follow-ups in your voice from a short brief — one that reads "nudge the Acme QBR, they've gone quiet" and gets a draft matching the tone of your last five emails to that contact, using a Personal Context brain and per-client profiles rather than pattern-matching your raw sent mail. Every draft sits for approval before it sends — nothing goes out to a client without you reading it first.

We build AI Emaily. It won't decide what belongs on your QBR agenda, but it will stop the invite, the reschedule, and the third follow-up from being three separate 10-minute interruptions to your day.

Frequently asked

Nafiul Hasan

Written by

Nafiul Hasan

Nafiul Hasan is an entrepreneur and AI automation system builder with 10+ years of experience turning messy, manual workflows into reliable automated systems. He designs and ships AI enterprise solutions end-to-end — the agent logic, the data plumbing, and the product people actually use — and founded AI Emaily to give busy professionals their attention back. He writes here from the builder's seat: what works, what breaks, and how to put AI to work without giving up control.

EntrepreneurAI Automation System BuilderAI EnthusiastBuilds AI Enterprise Solutions10+ years experience
More from Nafiul
Ready when you are

Stop rewriting the same QBR invite every quarter

AI Emaily drafts invites, reschedules, and follow-ups in your voice, waiting for your approval before anything sends. Start a 7-day free trial.

  • 7-day free trial
  • Cancel anytime
  • Every provider