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

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
- 01When should you send a QBR invitation email?
- 02What should a QBR invite actually contain?
- 03The templates
- 041. First-ever QBR with a new account
- 052. The routine quarterly
- 063. Exec-sponsor invite
- 074. Pre-read attachment note
- 085. Reschedule
- 096. Async QBR instead of a meeting
- 10The hard version of this situation
- 11What to do if there's no reply
- 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.
| Element | Why it's in the email | What happens if you skip it |
|---|---|---|
| Decisions needed | Turns a status update into a meeting they're accountable for | Reads as optional; gets declined or no-shown |
| Named attendees + role | Client can staff the room correctly the first time | Wrong people show up, real decision-maker is absent |
| Date + one alternative | One round-trip instead of a scheduling thread | Three emails just to land on a time |
| Pre-read attached | Lets them walk in with an opinion, not cold | Meeting becomes a data dump instead of a conversation |
| Stated duration | Sets expectations against a full hour they don't have | Assumed to be 60 minutes; declined on sight |
Lead with the decision, not the word 'review'
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.
2. The routine quarterly#
For an account where the QBR is expected and the relationship is healthy — keep it short.
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.
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.
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.
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.
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.
Lead with the decision, not the pattern
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.

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
Wait 3–4 business days
Give the original invite time to surface in a normal inbox rhythm before assuming it was missed.
- 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
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
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
See it in AI Emaily
Keep reading

Written by
Nafiul HasanNafiul 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.