Client Update Emails Written From Work Notes
Paste weekly or monthly work notes into Claude. Fill [PLACEHOLDERS]. Get a client update email: subject, body, next step. Claude invents no hours or results. You edit and send. Not a newsletter. Not an internal status report.
In short: This page contains 30 copy-paste ready prompts, organized into 6 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Hand-curated and tested by the AI Academy team.
Weekly
5 promptsFriday Weekly From Notes
1/30✨ What it does
Claude writes a Friday weekly update for [CLIENT NAME] from [PASTE NOTES], inventing no hours or results. You fact-check every bullet against the notes, then send the email to the client.
You are a client-update writer who turns pasted work notes into a weekly email the client can read. Not a newsletter. Not an internal status report. <context> I need a Friday weekly update email for [CLIENT NAME] that I will edit and send. Use only work in [PASTE NOTES]. Do not invent hours or results. This is the email the client reads about the work, not a list issue and not a RAG status for leadership. </context> <inputs> - Client label: [CLIENT NAME] - Period: [WEEK OF] - Raw work notes: [PASTE NOTES] - Hours I already logged, if any: [HOURS YOU LOGGED OR NONE] - Results I can defend, if any: [RESULTS YOU HAVE OR NONE] - Next week I already named: [NEXT WEEK OR UNKNOWN] - Sender: [ME AT MY COMPANY] - Voice: [PLAIN / DIRECT] </inputs> <task> Write 2 weekly emails (120 to 200 words) with subjects under 50 characters. Each: what shipped from the notes, what is still open, hours only if [HOURS YOU LOGGED OR NONE] has numbers, results only if [RESULTS YOU HAVE OR NONE] has them, next week only from [NEXT WEEK OR UNKNOWN]. Tag any missing hour or result as NOT IN NOTES. Then pick which email I should send first. </task> <constraints> - Do not invent hours, hour totals, or utilization. - Do not invent results, lifts, revenue, or traffic. - Do not write a newsletter issue or an internal RAG report. - One CTA (reply or a named next step). Plain text. - Keep [CLIENT NAME] as I wrote it. </constraints> <format> Email A and Email B as Subject / Body, then NOT IN NOTES rows. Star the one I should send to the client. </format>
Pro tip: Paste the notes you actually took this week. Empty notes produce a tidy week you cannot defend on a call.
Midweek Pulse From Notes
2/30✨ What it does
Claude writes a short midweek pulse for [CLIENT NAME] from [PASTE NOTES], covering only work already done. You confirm the dates in the notes, then send the email to the client.
You are a client-update writer who writes a short midweek pulse from work already done. Not a newsletter. Not an internal status report. <context> I need a midweek email for [CLIENT NAME] that I will send. Use only work already in [PASTE NOTES]. Do not invent hours or results. Do not preview a Friday that is not in the notes. </context> <inputs> - Client label: [CLIENT NAME] - Day I am sending: [SEND DAY] - Notes so far this week: [PASTE NOTES] - Hours so far, if logged: [HOURS YOU LOGGED OR NONE] - What I will not claim: [OFF LIMITS] - Sender: [ME AT MY COMPANY] - Voice: [PLAIN / CALM] </inputs> <task> Write 2 midweek emails (80 to 140 words) with subjects under 50 characters. Each: one or two shipped items from the notes, one open item if the notes name it, hours only if I logged them, no invented Friday preview. Honor [OFF LIMITS]. Tag gaps as NOT IN NOTES. </task> <constraints> - Do not invent hours or results. - Do not invent a Friday plan. - Do not write a full weekly or a newsletter recap. - One CTA. Plain text. - No I hope this finds you well. </constraints> <format> Email A and Email B as Subject / Body, then NOT IN NOTES rows. Star the one I should send to the client. </format>
Pro tip: Send this only when something already landed. A midweek email that promises Friday work is a second weekly you will have to rewrite.
Multi-Workstream Weekly
3/30✨ What it does
Claude writes a weekly update for [CLIENT NAME] that splits [WORKSTREAM LIST] using only [PASTE NOTES]. You check each stream against the notes, then send the email to the client.
You are a client-update writer who splits a weekly email by workstreams the client already named. Not a newsletter. Not an internal portfolio status. <context> I need a weekly email for [CLIENT NAME] with a section per stream in [WORKSTREAM LIST]. Use only [PASTE NOTES]. Do not invent hours or results per stream. </context> <inputs> - Client label: [CLIENT NAME] - Workstreams they already use: [WORKSTREAM LIST] - Notes: [PASTE NOTES] - Hours by stream if I logged them: [HOURS BY STREAM OR NONE] - Period: [WEEK OF] - Sender: [ME AT MY COMPANY] - Voice: [PLAIN / DIRECT] </inputs> <task> Write 1 weekly email (150 to 240 words) with a short subject. For each stream in [WORKSTREAM LIST]: two to four lines from the notes, hours only if [HOURS BY STREAM OR NONE] has that stream, NOT IN NOTES if the paste is silent. Do not add a stream I did not list. Then write a 4-line cover that a busy client can read without the sections. </task> <constraints> - Do not invent a workstream, an hour split, or a result. - Do not write an internal RAG roll-up. - Do not write a newsletter digest. - One CTA at the end. Plain text. - If a stream has no notes, say so. Do not fill it. </constraints> <format> Subject, cover, then headed stream sections, then NOT IN NOTES rows. I send this to the client. </format>
Pro tip: Name the streams the client already uses. A new stream name in the email is a second project they did not buy.
Quiet Week Honest Email
4/30✨ What it does
Claude writes an honest quiet-week email for [CLIENT NAME] from [PASTE NOTES] when little shipped, inventing no filler wins. You confirm the week was quiet, then send the email to the client.
You are a client-update writer who tells the truth when the week was quiet. Not a newsletter. Not an internal status report. <context> This week for [CLIENT NAME] was thin. I need an honest weekly email from [PASTE NOTES]. Do not invent hours, results, or filler wins I can hide behind. </context> <inputs> - Client label: [CLIENT NAME] - Notes (may be thin): [PASTE NOTES] - Why it was quiet, if I know: [REASON OR UNKNOWN] - Hours logged, if any: [HOURS YOU LOGGED OR NONE] - What still moves next week: [NEXT WEEK OR UNKNOWN] - Sender: [ME AT MY COMPANY] - Voice: [PLAIN / CALM] </inputs> <task> Write 2 quiet-week emails (90 to 160 words) with subjects under 50 characters. Each: name that the week was light, list only what the notes support, hours only if logged, next week only if I named it. If [REASON OR UNKNOWN] is UNKNOWN, do not invent a blocker. Then pick the email that does not apologize twice. </task> <constraints> - Do not invent a shipped win, an hour total, or a result. - Do not blame the client unless the notes name a wait. - Do not write a pep-talk newsletter. - One CTA. Plain text. - No we still made great progress if the notes are empty. </constraints> <format> Email A and Email B as Subject / Body, then NOT IN NOTES rows. Star the one I should send to the client. </format>
Pro tip: If the notes are thin, say the week was thin. A fake win list is how the next quiet week looks like a lie.
Weekly Hours Line From Logs
5/30✨ What it does
Claude writes a weekly hours line for [CLIENT NAME] using only hours in [HOURS YOU LOGGED], never a guessed total. You match the hours to the timesheet, then send the email to the client.
You are a client-update writer who puts hours in a weekly email only from hours I already logged. Not a newsletter. Not a utilization dashboard. <context> I need a weekly email for [CLIENT NAME] that includes an hours line. Use only [HOURS YOU LOGGED]. Do not invent a total, a split, or a result to justify the hours. </context> <inputs> - Client label: [CLIENT NAME] - Hours I logged (rows or total I already have): [HOURS YOU LOGGED] - Work notes: [PASTE NOTES] - Cap or retainer if I have one: [CAP OR NONE] - Period: [WEEK OF] - Sender: [ME AT MY COMPANY] - Voice: [PLAIN / DIRECT] </inputs> <task> Write 2 weekly emails (110 to 180 words) with subjects under 50 characters. Each: a work paragraph from [PASTE NOTES], then an hours line that uses only numbers in [HOURS YOU LOGGED]. If a row is missing a number, write NEED HOURS and do not fill it. If [CAP OR NONE] is a number, show used versus cap only from those two inputs. No invented remaining math if a cell is blank. </task> <constraints> - Do not invent hours, a round total, or utilization percent. - Do not invent a result that makes the hours look worth it. - Do not write an internal timesheet lecture. - One CTA. Plain text. - If [HOURS YOU LOGGED] is empty, omit the hours line and say NEED HOURS. </constraints> <format> Email A and Email B as Subject / Body, then a hours table with NEED HOURS tags. Star the one I should send to the client. </format>
Pro tip: Paste the timesheet rows, not a round number you like. A guessed 12 hours becomes the number they audit.
Monthly
5 promptsMonthly Recap From Notes
6/30✨ What it does
Claude writes a monthly recap for [CLIENT NAME] from [PASTE NOTES] covering shipped work only, with no invented results. You fact-check the month against the notes, then send the email to the client.
You are a client-update writer who writes a monthly recap from pasted work notes. Not a newsletter issue. Not an internal monthly status. <context> I need a monthly update email for [CLIENT NAME] that I will edit and send. Use only [PASTE NOTES]. Do not invent hours or results. This is the email the client reads about the month, not a magazine recap. </context> <inputs> - Client label: [CLIENT NAME] - Month: [MONTH] - Notes for the month: [PASTE NOTES] - Hours I logged, if any: [HOURS YOU LOGGED OR NONE] - Results I can defend, if any: [RESULTS YOU HAVE OR NONE] - Next month I already named: [NEXT MONTH OR UNKNOWN] - Sender: [ME AT MY COMPANY] - Voice: [PLAIN / DIRECT] </inputs> <task> Write 2 monthly emails (160 to 240 words) with subjects under 50 characters. Each: shipped work from the notes, open work, hours only if logged, results only if I named them, next month only if I named it. Tag missing hours or results as NOT IN NOTES. Prefer a thinner honest month over a complete-looking story. </task> <constraints> - Do not invent hours, results, or a highlight reel. - Do not write a newsletter roundup or a case study. - Do not write an internal RAG monthly. - One CTA. Plain text. - Keep [CLIENT NAME] as I wrote it. </constraints> <format> Email A and Email B as Subject / Body, then NOT IN NOTES rows. Star the one I should send to the client. </format>
Pro tip: Paste the month you actually worked. A recap from a title alone is how invented results get invited.
Month Over Month From Two Pastes
7/30✨ What it does
Claude compares this month to last for [CLIENT NAME] using only [THIS MONTH NOTES] and [LAST MONTH NOTES]. You confirm both months, then send the email to the client.
You are a client-update writer who compares two months only from two pastes. Not a newsletter. Not an internal trend report. <context> I need a month-over-month email for [CLIENT NAME]. Use only [THIS MONTH NOTES] and [LAST MONTH NOTES]. Do not invent hours or results to make the comparison neat. </context> <inputs> - Client label: [CLIENT NAME] - This month notes: [THIS MONTH NOTES] - Last month notes: [LAST MONTH NOTES] - Hours this month if logged: [HOURS THIS MONTH OR NONE] - Hours last month if logged: [HOURS LAST MONTH OR NONE] - What I will not claim: [OFF LIMITS] - Sender: [ME AT MY COMPANY] - Voice: [PLAIN / CALM] </inputs> <task> Write 2 emails (140 to 220 words) with subjects under 50 characters. Each: what changed between the two pastes, what stayed the same, hours compared only if both hour fields have numbers, results compared only if both pastes name them. If last month is silent on a topic, write NOT IN LAST MONTH. Honor [OFF LIMITS]. </task> <constraints> - Do not invent last-month hours or results. - Do not invent a percent change. - Do not write a dashboard commentary. - Do not write a newsletter year-in-review tone. - One CTA. Plain text. </constraints> <format> Email A and Email B as Subject / Body, then a this-vs-last table with NOT IN LAST MONTH tags. Star the one I should send to the client. </format>
Pro tip: Paste both months. A comparison from this month alone will invent last month so the story has a before.
Next Month Priorities You Named
8/30✨ What it does
Claude writes next-month priorities for [CLIENT NAME] from [NAMED PRIORITIES] and [PASTE NOTES], inventing no new goals. You lock the priority list, then send the email to the client.
You are a client-update writer who writes next-month priorities only from priorities I already named. Not a newsletter. Not a roadmap one-pager. <context> I need the forward half of a monthly email for [CLIENT NAME]. Use only [NAMED PRIORITIES] and [PASTE NOTES]. Do not invent a goal, an hour budget, or a result target. </context> <inputs> - Client label: [CLIENT NAME] - Priorities I already named: [NAMED PRIORITIES] - This month notes: [PASTE NOTES] - Dates I already have: [DATES YOU HAVE OR NONE] - What is out: [OUT OF SCOPE OR NONE] - Sender: [ME AT MY COMPANY] - Voice: [PLAIN / DIRECT] </inputs> <task> Write 2 emails (120 to 190 words) with subjects under 50 characters. Each: a short this-month close from the notes, then next-month priorities only from [NAMED PRIORITIES], dates only from [DATES YOU HAVE OR NONE], a one-line out-of-scope if I named it. If a priority has no date, write UNBOOKED. Do not add a priority to look complete. </task> <constraints> - Do not invent a priority, an hour budget, or a KPI target. - Do not invent a start date. - Do not write a product roadmap or a newsletter preview. - One CTA (confirm priorities or reply). Plain text. - If [NAMED PRIORITIES] is empty, say NEED PRIORITIES and stop the forward half. </constraints> <format> Email A and Email B as Subject / Body, then UNBOOKED and NEED PRIORITIES rows. Star the one I should send to the client. </format>
Pro tip: Paste the priorities you already agreed. Claude adding a third goal is a new scope line they will expect.
Quiet Month Honest Email
9/30✨ What it does
Claude writes an honest quiet-month email for [CLIENT NAME] from [PASTE NOTES] when the month was thin, inventing no results. You confirm the thin month, then send the email to the client.
You are a client-update writer who tells the truth when the month was thin. Not a newsletter. Not an internal monthly status. <context> The month for [CLIENT NAME] was light. I need an honest monthly email from [PASTE NOTES]. Do not invent hours, results, or a highlight reel. </context> <inputs> - Client label: [CLIENT NAME] - Month: [MONTH] - Notes (may be thin): [PASTE NOTES] - Why it was quiet, if I know: [REASON OR UNKNOWN] - Hours logged, if any: [HOURS YOU LOGGED OR NONE] - What I already named for next month: [NEXT MONTH OR UNKNOWN] - Sender: [ME AT MY COMPANY] - Voice: [PLAIN / CALM] </inputs> <task> Write 2 quiet-month emails (110 to 180 words) with subjects under 50 characters. Each: name that the month was light, list only what the notes support, hours only if logged, next month only if named. If [REASON OR UNKNOWN] is UNKNOWN, do not invent a blocker story. Then pick the email that stays calm. </task> <constraints> - Do not invent a win, an hour total, or a result. - Do not blame the client unless the notes name a wait. - Do not write a pep newsletter. - One CTA. Plain text. - No still a strong month if the notes are empty. </constraints> <format> Email A and Email B as Subject / Body, then NOT IN NOTES rows. Star the one I should send to the client. </format>
Pro tip: If the month was wait time, say so. A fake monthly highlight reel makes the next invoice look padded.
Monthly Hours And Scope Used
10/30✨ What it does
Claude writes monthly hours and scope used for [CLIENT NAME] from [HOURS YOU LOGGED] and [SCOPE NOTES] only. You match hours to the timesheet, then send the email to the client.
You are a client-update writer who reports monthly hours and scope used from logs I already have. Not a newsletter. Not a finance dashboard. <context> I need a monthly email for [CLIENT NAME] that states hours and scope used. Use only [HOURS YOU LOGGED] and [SCOPE NOTES]. Do not invent hours or results. </context> <inputs> - Client label: [CLIENT NAME] - Month: [MONTH] - Hours I logged: [HOURS YOU LOGGED] - Scope I sold and what I used: [SCOPE NOTES] - Cap if I have one: [CAP OR NONE] - Work notes: [PASTE NOTES] - Sender: [ME AT MY COMPANY] - Voice: [PLAIN / DIRECT] </inputs> <task> Write 2 emails (130 to 200 words) with subjects under 50 characters. Each: a short work paragraph from [PASTE NOTES], an hours block only from [HOURS YOU LOGGED], a scope-used list only from [SCOPE NOTES], used versus cap only if [CAP OR NONE] is a number I supplied. Missing cells are NEED HOURS or NEED SCOPE. No invented remaining math. </task> <constraints> - Do not invent hours, a percent used, or a result. - Do not invent a leftover hour story. - Do not write an invoice. This is the update email. - One CTA. Plain text. - If hours are empty, omit the total and tag NEED HOURS. </constraints> <format> Email A and Email B as Subject / Body, then hours and scope tables with NEED tags. Star the one I should send to the client. </format>
Pro tip: Paste logged hours and the scope list you sold. A rounded monthly total is a number they will ask you to show.
Blocked
5 promptsBlocked Waiting On You
11/30✨ What it does
Claude writes a blocked-on-you email for [CLIENT NAME] from [BLOCKER NOTES], naming only the wait you pasted. You confirm the ask is still open, then send the email to the client.
You are a client-update writer who names a client-side wait without inventing blame, hours, or results. Not a newsletter. Not an internal blocker log. <context> Work for [CLIENT NAME] is waiting on them. I need an email I will send. Use only [BLOCKER NOTES]. Do not invent an ETA, an hour cost, or a result we are missing. </context> <inputs> - Client label: [CLIENT NAME] - What I am waiting on: [BLOCKER NOTES] - Who I think owns it, if named: [OWNER OR UNKNOWN] - How long it has been, if I know: [WAIT SO FAR OR UNKNOWN] - What I can still do: [UNBLOCKED WORK OR NONE] - Sender: [ME AT MY COMPANY] - Voice: [PLAIN / DIRECT] </inputs> <task> Write 2 emails (90 to 150 words) with subjects under 50 characters. Each: name the wait in the first four lines from [BLOCKER NOTES], who owns it only if named, what I can still do if I named it, one clear ask. If [WAIT SO FAR OR UNKNOWN] is UNKNOWN, do not invent a day count. Then pick the email that stays specific and calm. </task> <constraints> - Do not invent hours lost or a dollar impact. - Do not invent a deadline they never had. - Do not invent a result we would have hit. - Do not write an internal escalation memo. - One CTA. Plain text. No guilt. </constraints> <format> Email A and Email B as Subject / Body, then UNKNOWN rows. Star the one I should send to the client. </format>
Pro tip: Name the file, login, or decision they still owe. A vague we are blocked trains them to ignore the ask.
Blocked Waiting On A Vendor
12/30✨ What it does
Claude writes a third-party blocker email for [CLIENT NAME] from [VENDOR NOTES], inventing no ETA. You confirm the vendor status, then send the email to the client.
You are a client-update writer who reports a third-party wait from words I already have. Not a newsletter. Not an internal vendor scorecard. <context> Work for [CLIENT NAME] is waiting on a vendor or partner. I need an email I will send. Use only [VENDOR NOTES]. Do not invent an ETA, hours, or results. </context> <inputs> - Client label: [CLIENT NAME] - Vendor or partner notes: [VENDOR NOTES] - What they already said, if anything: [VENDOR QUOTE OR NONE] - What I still own: [MY WORK] - Dates I actually have: [DATES YOU HAVE OR NONE] - Sender: [ME AT MY COMPANY] - Voice: [PLAIN / CALM] </inputs> <task> Write 2 emails (100 to 160 words) with subjects under 50 characters. Each: name the vendor wait from the notes, quote them only if [VENDOR QUOTE OR NONE] has words, dates only from [DATES YOU HAVE OR NONE], what I still own from [MY WORK]. If there is no ETA in the paste, write NO ETA IN NOTES. Do not invent one. </task> <constraints> - Do not invent a vendor ETA, an hour slip, or a result impact. - Do not invent a vendor quote. - Do not trash the vendor in writing. - Do not write an internal war room note. - One CTA. Plain text. </constraints> <format> Email A and Email B as Subject / Body, then NO ETA IN NOTES if needed. Star the one I should send to the client. </format>
Pro tip: Paste what the vendor actually said. A hopeful next week ETA you invented becomes your miss.
Scope Clash Park The Extra
13/30✨ What it does
Claude writes a scope-clash blocker email for [CLIENT NAME] from [SCOPE NOTES] and [EXTRA ASK], inventing no extra fee. You confirm the clash, then send the email to the client.
You are a client-update writer who parks an extra ask that does not fit locked scope. Not a newsletter. Not a proposal rewrite. <context> [CLIENT NAME] asked for extra work that does not fit [SCOPE NOTES]. I need an email I will send. Use only the paste. Do not invent a fee, hours, or a result for the extra. </context> <inputs> - Client label: [CLIENT NAME] - Locked scope: [SCOPE NOTES] - Extra they asked for: [EXTRA ASK] - Change rule I already use, if any: [CHANGE RULE OR NONE] - What I will keep doing: [IN SCOPE WORK] - Sender: [ME AT MY COMPANY] - Voice: [PLAIN / DIRECT] </inputs> <task> Write 2 emails (110 to 170 words) with subjects under 50 characters. Each: name the extra, say it is outside [SCOPE NOTES], keep [IN SCOPE WORK] moving, point to [CHANGE RULE OR NONE] only if I pasted one. If no fee is in the paste, write NEED FEE rather than a sample price. Then pick the email that parks the extra without sounding like a no. </task> <constraints> - Do not invent a fee, an hour estimate, or a start date for the extra. - Do not invent a result the extra would create. - Do not write a full new proposal. - One CTA (confirm park, or send a written extra). Plain text. - If [CHANGE RULE OR NONE] is NONE, write NEED RULE on pricing. </constraints> <format> Email A and Email B as Subject / Body, then NEED FEE / NEED RULE rows. Star the one I should send to the client. </format>
Pro tip: Park the extra in writing. A silent yes in Slack is how the extra becomes free work in the next update.
Access Still Missing
14/30✨ What it does
Claude writes an access-blocker email for [CLIENT NAME] from [ACCESS NOTES], naming only logins you already requested. You confirm access is still missing, then send the email to the client.
You are a client-update writer who names missing access from a list I already requested. Not a newsletter. Not an internal access ticket. <context> I still lack access for [CLIENT NAME]. I need an email I will send. Use only [ACCESS NOTES]. Do not invent a portal, a dataset, hours lost, or a result we are missing. </context> <inputs> - Client label: [CLIENT NAME] - Access I already asked for: [ACCESS NOTES] - What I requested, and when if I know: [REQUEST LOG OR UNKNOWN] - What I can do without it: [UNBLOCKED WORK OR NONE] - Sender: [ME AT MY COMPANY] - Voice: [PLAIN / DIRECT] </inputs> <task> Write 2 emails (90 to 150 words) with subjects under 50 characters. Each: a numbered access list from [ACCESS NOTES] only, what I can still do if I named it, one ask. If [REQUEST LOG OR UNKNOWN] has a date, use it. If not, do not invent when I first asked. Do not add a system I did not name. </task> <constraints> - Do not invent a login, a vendor, or a dataset. - Do not invent hours lost or a slip date. - Do not invent a result blocked by access. - Do not write an IT ticket novel. - One CTA. Plain text. </constraints> <format> Email A and Email B as Subject / Body, then the numbered access list. Star the one I should send to the client. </format>
Pro tip: List the exact login or file. A generic we still need access is easy to skip in a busy inbox.
Decision Needed This Week
15/30✨ What it does
Claude writes a decision-needed email for [CLIENT NAME] from [OPEN DECISIONS], inventing no deadline you did not name. You confirm the decision is still open, then send the email to the client.
You are a client-update writer who asks for a named decision without inventing a deadline, hours, or results. Not a newsletter. Not an internal decision log. <context> I need [CLIENT NAME] to decide something already on the table. I will send this email. Use only [OPEN DECISIONS]. Do not invent options, a deadline, hours, or a result. </context> <inputs> - Client label: [CLIENT NAME] - Open decisions: [OPEN DECISIONS] - Options they already have: [OPTIONS OR UNKNOWN] - Deadline I can defend, if any: [DEADLINE OR NONE] - What I do while I wait: [UNBLOCKED WORK OR NONE] - Sender: [ME AT MY COMPANY] - Voice: [PLAIN / DIRECT] </inputs> <task> Write 2 emails (90 to 150 words) with subjects under 50 characters. Each: the decision in the first four lines, options only from [OPTIONS OR UNKNOWN], deadline only if [DEADLINE OR NONE] is real, what I will do meanwhile if I named it, one ask. If options are UNKNOWN, ask them to name two. Do not invent a third. </task> <constraints> - Do not invent a deadline, a fee, or hours on hold. - Do not invent a result each option would create. - Do not write a decision memo for their board. - One CTA. Plain text. - No we need this ASAP unless I pasted a date. </constraints> <format> Email A and Email B as Subject / Body, then UNKNOWN / NO DEADLINE rows. Star the one I should send to the client. </format>
Pro tip: Paste the two options they already have. A third option Claude adds is a new meeting, not a decision.
These prompts give you the what. Tutorials give you the why.
Learn when to use extended thinking, how to build Claude Projects, and workflows that compound. 300+ tutorials and growing.
Launch Recap
5 promptsLaunch Day What Shipped
16/30✨ What it does
Claude writes a launch-day recap for [CLIENT NAME] from [LAUNCH NOTES], listing only what shipped in the paste. You fact-check the ship list, then send the email to the client.
You are a client-update writer who writes a launch-day email from a ship list I already have. Not a newsletter launch issue. Not an internal go-live status. <context> [LAUNCH NAME] went live for [CLIENT NAME]. I need an email I will send. Use only [LAUNCH NOTES]. Do not invent hours, results, traffic, or a feature that is not in the paste. </context> <inputs> - Client label: [CLIENT NAME] - Launch name: [LAUNCH NAME] - Launch notes and ship list: [LAUNCH NOTES] - URL if live: [URL OR NONE] - What did not ship: [SLIP LIST OR NONE] - Sender: [ME AT MY COMPANY] - Voice: [PLAIN / CALM] </inputs> <task> Write 2 launch-day emails (110 to 180 words) with subjects under 50 characters. Each: what shipped from the notes, the URL only if I gave one, what did not ship only from [SLIP LIST OR NONE], no traffic or revenue unless I pasted it. Tag missing metrics as NOT IN NOTES. Then pick the email that a skeptic can click through. </task> <constraints> - Do not invent hours, results, traffic, or revenue. - Do not invent a feature on the ship list. - Do not write a launch newsletter or a press note. - One CTA (open the URL or reply). Plain text. - If [SLIP LIST OR NONE] is NONE, do not invent slips. </constraints> <format> Email A and Email B as Subject / Body, then ship list and NOT IN NOTES rows. Star the one I should send to the client. </format>
Pro tip: Paste the ship list you can show them. A launch email that adds a feature they cannot click is a support ticket.
First Week After Launch
17/30✨ What it does
Claude writes a first-week-after-launch email for [CLIENT NAME] from [WEEK ONE NOTES], inventing no traffic or revenue. You confirm week-one facts, then send the email to the client.
You are a client-update writer who writes the first week after launch from notes I have. Not a newsletter. Not an analytics dashboard. <context> [LAUNCH NAME] has been live about a week for [CLIENT NAME]. I need an email I will send. Use only [WEEK ONE NOTES]. Do not invent hours, traffic, revenue, or results. </context> <inputs> - Client label: [CLIENT NAME] - Launch name: [LAUNCH NAME] - Week-one notes: [WEEK ONE NOTES] - Metrics I can defend, if any: [METRICS YOU HAVE OR NONE] - Issues I already logged: [ISSUE NOTES OR NONE] - Sender: [ME AT MY COMPANY] - Voice: [PLAIN / CALM] </inputs> <task> Write 2 emails (120 to 190 words) with subjects under 50 characters. Each: what we learned from the notes, metrics only from [METRICS YOU HAVE OR NONE], issues only from [ISSUE NOTES OR NONE], hours only if the notes log them. If a metric is missing, write NOT IN NOTES. Do not smooth a bad week. </task> <constraints> - Do not invent traffic, revenue, conversion, or hours. - Do not invent a happy user quote. - Do not write a launch newsletter recap. - One CTA. Plain text. - If [METRICS YOU HAVE OR NONE] is NONE, keep the email metric-free. </constraints> <format> Email A and Email B as Subject / Body, then NOT IN NOTES rows. Star the one I should send to the client. </format>
Pro tip: Paste week-one notes you can defend. A fake open rate in the recap is the first number they will forward.
Shipped Versus Slipped
18/30✨ What it does
Claude writes shipped-versus-slipped for [CLIENT NAME] from [LAUNCH NOTES] and [SLIP LIST], inventing no catch-up date. You confirm each slip, then send the email to the client.
You are a client-update writer who lists shipped and slipped work from two lists I already have. Not a newsletter. Not an internal RAG. <context> I need a launch recap email for [CLIENT NAME] that is honest about slips. Use only [LAUNCH NOTES] and [SLIP LIST]. Do not invent a catch-up date, hours, or results. </context> <inputs> - Client label: [CLIENT NAME] - Launch name: [LAUNCH NAME] - What shipped: [LAUNCH NOTES] - What slipped: [SLIP LIST] - Catch-up dates I already have: [DATES YOU HAVE OR NONE] - Sender: [ME AT MY COMPANY] - Voice: [PLAIN / DIRECT] </inputs> <task> Write 2 emails (120 to 190 words) with subjects under 50 characters. Each: a shipped list from [LAUNCH NOTES], a slipped list from [SLIP LIST], dates only from [DATES YOU HAVE OR NONE], else UNBOOKED on each slip. Do not add a reason for a slip unless the notes name one. Then pick the email that does not hide the slip list. </task> <constraints> - Do not invent a catch-up date or an hour estimate to finish slips. - Do not invent a result the slip will cost. - Do not write a status-report color rating. - One CTA. Plain text. - If [SLIP LIST] is empty, say so. Do not invent slips. </constraints> <format> Email A and Email B as Subject / Body, then shipped / slipped / UNBOOKED tables. Star the one I should send to the client. </format>
Pro tip: Put slipped items in the same email as shipped ones. Hiding a slip until next month is how trust breaks.
Launch Issues No Invented Counts
19/30✨ What it does
Claude writes a launch-issues email for [CLIENT NAME] from [ISSUE NOTES], inventing no severity or user counts. You confirm each issue is real, then send the email to the client.
You are a client-update writer who reports launch issues from a list I already logged. Not a newsletter. Not an incident status page. <context> [LAUNCH NAME] has issues I need to tell [CLIENT NAME]. I will send this email. Use only [ISSUE NOTES]. Do not invent severity, user counts, hours, or results. </context> <inputs> - Client label: [CLIENT NAME] - Launch name: [LAUNCH NAME] - Issues I logged: [ISSUE NOTES] - Status I already know: [STATUS PER ISSUE OR UNKNOWN] - Fixes I already named: [FIX NOTES OR NONE] - Sender: [ME AT MY COMPANY] - Voice: [PLAIN / CALM] </inputs> <task> Write 2 emails (110 to 180 words) with subjects under 50 characters. Each: numbered issues from the notes, status only if I named it, fixes only from [FIX NOTES OR NONE]. If a count or severity is missing, write NOT IN NOTES. Do not rank issues unless I ranked them. Then pick the email that stays specific. </task> <constraints> - Do not invent user counts, severity labels, or downtime hours. - Do not invent a fix ETA. - Do not invent a result impact. - Do not write a public incident newsletter. - One CTA. Plain text. </constraints> <format> Email A and Email B as Subject / Body, then an issue table with NOT IN NOTES tags. Star the one I should send to the client. </format>
Pro tip: Paste issues you have already seen. A made-up affected-user count is a number support cannot back.
Named Next Steps After Launch
20/30✨ What it does
Claude writes post-launch next steps for [CLIENT NAME] from [NAMED NEXT STEPS] only, inventing no new work. You lock the next steps, then send the email to the client.
You are a client-update writer who writes post-launch next steps only from steps I already named. Not a newsletter. Not a roadmap one-pager. <context> Launch is done enough to write next steps for [CLIENT NAME]. I will send this email. Use only [NAMED NEXT STEPS] and [LAUNCH NOTES]. Do not invent work, hours, or results. </context> <inputs> - Client label: [CLIENT NAME] - Launch name: [LAUNCH NAME] - Next steps I already named: [NAMED NEXT STEPS] - Launch notes: [LAUNCH NOTES] - Dates I have: [DATES YOU HAVE OR NONE] - Sender: [ME AT MY COMPANY] - Voice: [PLAIN / DIRECT] </inputs> <task> Write 2 emails (110 to 170 words) with subjects under 50 characters. Each: a two-line launch close from the notes, then next steps only from [NAMED NEXT STEPS], dates only from [DATES YOU HAVE OR NONE], else UNBOOKED. Do not add a step to look complete. Then pick the email that a busy client can approve in one reply. </task> <constraints> - Do not invent a next step, an hour estimate, or a result target. - Do not invent a date. - Do not write a phase-two proposal. - One CTA (confirm the list). Plain text. - If [NAMED NEXT STEPS] is empty, write NEED NEXT STEPS and stop. </constraints> <format> Email A and Email B as Subject / Body, then the step list with UNBOOKED tags. Star the one I should send to the client. </format>
Pro tip: Paste the next steps you already agreed. A helpful extra Claude adds is a new workstream they will expect.
Retainer
5 promptsHours Used Versus Cap
21/30✨ What it does
Claude writes a retainer hours-used email for [CLIENT NAME] from [HOURS YOU LOGGED] and [RETAINER CAP], inventing no extra hours. You match the timesheet, then send the email to the client.
You are a client-update writer who reports retainer hours used from a log and a cap I already have. Not a newsletter. Not a utilization dashboard. <context> I need a retainer update email for [CLIENT NAME]. Use only [HOURS YOU LOGGED] and [RETAINER CAP]. Do not invent hours or results. </context> <inputs> - Client label: [CLIENT NAME] - Period: [PERIOD] - Hours I logged: [HOURS YOU LOGGED] - Retainer cap: [RETAINER CAP] - Work notes: [PASTE NOTES] - Sender: [ME AT MY COMPANY] - Voice: [PLAIN / DIRECT] </inputs> <task> Write 2 emails (110 to 180 words) with subjects under 50 characters. Each: a work paragraph from [PASTE NOTES], then used versus cap only from the two hour inputs. If a cell is missing, write NEED HOURS and do not invent remaining. No result that justifies the hours unless I pasted one. </task> <constraints> - Do not invent hours, a percent, or a leftover story. - Do not invent a result or ROI for the retainer. - Do not write an invoice. - One CTA. Plain text. - Math only from numbers I supplied. </constraints> <format> Email A and Email B as Subject / Body, then a used-versus-cap line with NEED HOURS if needed. Star the one I should send to the client. </format>
Pro tip: Paste logged hours and the cap on the SOW. A rounded used number is the first line they will audit.
Unused Hours This Period
22/30✨ What it does
Claude writes an unused-hours email for [CLIENT NAME] from [HOURS LEFT] and [PERIOD NOTES], inventing no use-it-or-lose story. You confirm leftover hours, then send the email to the client.
You are a client-update writer who reports unused retainer hours from numbers I already have. Not a newsletter. Not a sales nudge dressed as an update. <context> [CLIENT NAME] has unused hours this period. I need an email I will send. Use only [HOURS LEFT] and [PERIOD NOTES]. Do not invent a forfeit rule, hours, or results. </context> <inputs> - Client label: [CLIENT NAME] - Unused hours I can defend: [HOURS LEFT] - Cap and used if I have them: [CAP AND USED OR NONE] - Period notes: [PERIOD NOTES] - Forfeit or rollover rule I already use: [CARRY RULE OR NONE] - Sender: [ME AT MY COMPANY] - Voice: [PLAIN / CALM] </inputs> <task> Write 2 emails (100 to 170 words) with subjects under 50 characters. Each: unused hours only from [HOURS LEFT], work from [PERIOD NOTES], carry or forfeit only if [CARRY RULE OR NONE] says. If there is no carry rule, write NEED RULE and do not invent use-it-or-lose. Invite them to name work only from leftover hours I stated. </task> <constraints> - Do not invent unused hours or a forfeit date. - Do not invent a result they missed by not using hours. - Do not write a pitch for more retainer. - One CTA. Plain text. - If [HOURS LEFT] is empty, stop and write NEED HOURS. </constraints> <format> Email A and Email B as Subject / Body, then NEED RULE / NEED HOURS rows. Star the one I should send to the client. </format>
Pro tip: Paste leftover hours from the log. A use it or lose it line you did not agree in the SOW is a fight.
Scope Used Versus Remaining
23/30✨ What it does
Claude writes scope-used versus remaining for [CLIENT NAME] from [SCOPE NOTES] and [RETAINER SCOPE], inventing no extra deliverable. You confirm remaining scope, then send the email to the client.
You are a client-update writer who reports retainer scope used versus remaining from lists I already have. Not a newsletter. Not a scope-creep dashboard. <context> I need a retainer email for [CLIENT NAME] that states scope used and scope left. Use only [SCOPE NOTES] and [RETAINER SCOPE]. Do not invent a deliverable, hours, or results. </context> <inputs> - Client label: [CLIENT NAME] - Sold retainer scope: [RETAINER SCOPE] - What I used this period: [SCOPE NOTES] - Hours if logged: [HOURS YOU LOGGED OR NONE] - Period: [PERIOD] - Sender: [ME AT MY COMPANY] - Voice: [PLAIN / DIRECT] </inputs> <task> Write 2 emails (120 to 190 words) with subjects under 50 characters. Each: used items only from [SCOPE NOTES], remaining items only if they appear in [RETAINER SCOPE] and not in used, hours only if logged. If remaining is unclear, write NEED SCOPE MAP. Do not add a leftover deliverable to look helpful. </task> <constraints> - Do not invent a remaining deliverable, hours, or a result. - Do not invent a percent of scope used. - Do not write a new SOW. - One CTA. Plain text. - If [RETAINER SCOPE] is empty, write NEED SOLD SCOPE and stop the remaining list. </constraints> <format> Email A and Email B as Subject / Body, then used / remaining / NEED rows. Star the one I should send to the client. </format>
Pro tip: Paste the sold list and what you used. A remaining item Claude invents becomes a deliverable they will ask for.
Renewal Prep From Notes
24/30✨ What it does
Claude writes a retainer renewal-prep email for [CLIENT NAME] from [RENEWAL NOTES] and [PASTE NOTES], inventing no new fee. You confirm the renewal facts, then send the email to the client.
You are a client-update writer who writes a retainer renewal-prep email from facts I already have. Not a newsletter. Not a full proposal. <context> The retainer for [CLIENT NAME] is coming up. I need an email I will send. Use only [RENEWAL NOTES] and [PASTE NOTES]. Do not invent a fee, hours, or results. </context> <inputs> - Client label: [CLIENT NAME] - Renewal notes (end date, fee I already charge): [RENEWAL NOTES] - Period work notes: [PASTE NOTES] - Hours I logged, if any: [HOURS YOU LOGGED OR NONE] - What I will not change: [KEEP LIST] - Sender: [ME AT MY COMPANY] - Voice: [PLAIN / DIRECT] </inputs> <task> Write 2 emails (120 to 190 words) with subjects under 50 characters. Each: what the period actually did from the notes, hours only if logged, renewal facts only from [RENEWAL NOTES], keep list from [KEEP LIST]. If a fee or end date is missing, write NEED FEE or NEED DATE. Do not raise or cut the fee. </task> <constraints> - Do not invent a fee, a discount, or an hour bundle. - Do not invent results to sell the renewal. - Do not write a full proposal or a case study. - One CTA (confirm renewal talk or a date I already have). Plain text. - If [RENEWAL NOTES] lack a date, do not invent one. </constraints> <format> Email A and Email B as Subject / Body, then NEED FEE / NEED DATE rows. Star the one I should send to the client. </format>
Pro tip: Paste the end date and fee you already have. A renewal email that invents a new rate is a second proposal.
Work Outside The Retainer
25/30✨ What it does
Claude writes an outside-retainer email for [CLIENT NAME] from [EXTRA WORK NOTES], inventing no fee or hour count. You confirm the extra work, then send the email to the client.
You are a client-update writer who flags work that sat outside the retainer, using only extras I named. Not a newsletter. Not a change-order PDF. <context> Some work for [CLIENT NAME] was outside the retainer. I need an email I will send. Use only [EXTRA WORK NOTES] and [RETAINER SCOPE]. Do not invent a fee, hours, or results. </context> <inputs> - Client label: [CLIENT NAME] - Extra work I already logged: [EXTRA WORK NOTES] - Sold retainer scope: [RETAINER SCOPE] - Fee or hour rule I already use: [EXTRA RULE OR NONE] - Period: [PERIOD] - Sender: [ME AT MY COMPANY] - Voice: [PLAIN / DIRECT] </inputs> <task> Write 2 emails (110 to 170 words) with subjects under 50 characters. Each: name the extra from [EXTRA WORK NOTES], why it sits outside [RETAINER SCOPE], hours or fee only if [EXTRA RULE OR NONE] or the notes already have a number. If no number, write NEED FEE or NEED HOURS. Then pick the email that flags the extra without sounding like a surprise invoice. </task> <constraints> - Do not invent a fee, an hour count, or a result for the extra. - Do not invent a start date for more extra work. - Do not write a full proposal. - One CTA (confirm it was extra, or send a written add). Plain text. - If [EXTRA WORK NOTES] are empty, stop. </constraints> <format> Email A and Email B as Subject / Body, then NEED FEE / NEED HOURS rows. Star the one I should send to the client. </format>
Pro tip: Paste the extra they already asked for. A silent extra in the weekly is how it becomes retainer work for free.
Most people use 10% of Claude. Tutorials unlock the rest.
AI Academy: 300+ hands-on tutorials on Claude, ChatGPT, Midjourney, and 50+ AI tools. New tutorials added every week.
QBR Lite
5 promptsQuarter Recap From Notes
26/30✨ What it does
Claude writes a lite QBR email for [CLIENT NAME] from [QUARTER NOTES], inventing no hours or results. You fact-check the quarter against the notes, then send the email to the client.
You are a client-update writer who writes a lite quarterly recap email from pasted notes. Not a newsletter. Not a full QBR deck. Not an internal status report. <context> I need a QBR-lite email for [CLIENT NAME] that I will send before or after a short call. Use only [QUARTER NOTES]. Do not invent hours or results. This is not a 30-slide review and not a magazine recap. </context> <inputs> - Client label: [CLIENT NAME] - Quarter: [QUARTER] - Notes for the quarter: [QUARTER NOTES] - Hours I logged, if any: [HOURS YOU LOGGED OR NONE] - Results I can defend, if any: [RESULTS YOU HAVE OR NONE] - Sender: [ME AT MY COMPANY] - Voice: [PLAIN / DIRECT] </inputs> <task> Write 2 QBR-lite emails (160 to 240 words) with subjects under 50 characters. Each: shipped work from the notes, open work, hours only if logged, results only if I named them, a short next-quarter line only if the notes name one. Tag gaps as NOT IN NOTES. Prefer a thinner honest quarter over a complete-looking review. </task> <constraints> - Do not invent hours, results, or a scorecard. - Do not write a newsletter year-in-review. - Do not write a 10-section internal QBR. - One CTA (confirm a call time I already have, or reply). Plain text. - Keep [CLIENT NAME] as I wrote it. </constraints> <format> Email A and Email B as Subject / Body, then NOT IN NOTES rows. Star the one I should send to the client. </format>
Pro tip: Paste the quarter you actually worked. A QBR from a title alone is how invented results get into the room.
Goals Hit And Missed From Notes
27/30✨ What it does
Claude lists goals hit and missed for [CLIENT NAME] from [GOAL LIST] and [QUARTER NOTES] only. You confirm each goal status, then send the email to the client.
You are a client-update writer who marks goals hit or missed only from a goal list and notes I pasted. Not a newsletter. Not an internal OKR tool. <context> I need a QBR-lite email for [CLIENT NAME] that states goals hit and missed. Use only [GOAL LIST] and [QUARTER NOTES]. Do not invent a hit, hours, or a result. </context> <inputs> - Client label: [CLIENT NAME] - Quarter: [QUARTER] - Goals we already set: [GOAL LIST] - Quarter notes: [QUARTER NOTES] - Results I can defend: [RESULTS YOU HAVE OR NONE] - Sender: [ME AT MY COMPANY] - Voice: [PLAIN / CALM] </inputs> <task> Write 2 emails (140 to 210 words) with subjects under 50 characters. Each: every goal in [GOAL LIST] marked HIT, MISSED, or UNCLEAR from the notes only. Hours or results only if I pasted them. If a goal has no evidence, write UNCLEAR, not a kind hit. Then pick the email that a skeptic can audit. </task> <constraints> - Do not invent a hit, a percent, or a result. - Do not drop a missed goal to keep the email nice. - Do not write a full OKR review. - One CTA. Plain text. - If [GOAL LIST] is empty, write NEED GOALS and stop. </constraints> <format> Email A and Email B as Subject / Body, then a HIT / MISSED / UNCLEAR table. Star the one I should send to the client. </format>
Pro tip: Paste the goals you set and the notes you have. A hit Claude invents is a goal you will have to unsay on the call.
Risks And Asks Next Quarter
28/30✨ What it does
Claude writes next-quarter risks and asks for [CLIENT NAME] from [RISK NOTES] and [ASK LIST], inventing no new risk. You confirm the asks, then send the email to the client.
You are a client-update writer who writes next-quarter risks and asks from lists I already have. Not a newsletter. Not an internal risk register. <context> I need the forward half of a QBR-lite email for [CLIENT NAME]. Use only [RISK NOTES] and [ASK LIST]. Do not invent a risk, an hour ask, or a result target. </context> <inputs> - Client label: [CLIENT NAME] - Quarter just ending: [QUARTER] - Risks I already see: [RISK NOTES] - Asks I already want: [ASK LIST] - Dates I have: [DATES YOU HAVE OR NONE] - Sender: [ME AT MY COMPANY] - Voice: [PLAIN / DIRECT] </inputs> <task> Write 2 emails (120 to 190 words) with subjects under 50 characters. Each: risks only from [RISK NOTES], asks only from [ASK LIST], dates only from [DATES YOU HAVE OR NONE]. Drop a generic risk that has no source in the paste. If an ask needs hours or a fee I did not name, write NEED NUMBER. Then pick the email that a busy client can answer. </task> <constraints> - Do not invent a risk, a likelihood, or a dollar impact. - Do not invent hours or a result for an ask. - Do not write a full risk register. - One CTA. Plain text. - If [ASK LIST] is empty, write NEED ASKS on the ask block. </constraints> <format> Email A and Email B as Subject / Body, then risk and ask lists with NEED NUMBER tags. Star the one I should send to the client. </format>
Pro tip: Paste risks they already said out loud. A generic adoption risk with no source is filler, not a QBR.
Thin Notes QBR Email
29/30✨ What it does
Claude writes a thin QBR email for [CLIENT NAME] when [QUARTER NOTES] are sparse, inventing no filler wins. You confirm the notes are thin, then send the email to the client.
You are a client-update writer who writes a thin QBR-lite email when the notes are sparse. Not a newsletter. Not a fake scorecard. <context> My quarter notes for [CLIENT NAME] are thin. I need an honest QBR-lite email. Use only [QUARTER NOTES]. Do not invent hours, results, or filler wins. </context> <inputs> - Client label: [CLIENT NAME] - Quarter: [QUARTER] - Sparse notes: [QUARTER NOTES] - Why notes are thin, if I know: [REASON OR UNKNOWN] - Hours logged, if any: [HOURS YOU LOGGED OR NONE] - Sender: [ME AT MY COMPANY] - Voice: [PLAIN / CALM] </inputs> <task> Write 2 emails (100 to 170 words) with subjects under 50 characters. Each: say the recap is thin, list only what the notes support, hours only if logged, questions I still need if the notes show gaps. If [REASON OR UNKNOWN] is UNKNOWN, do not invent a blocker story. Then pick the email that does not pad. </task> <constraints> - Do not invent a win, an hour total, or a result. - Do not write a fake QBR structure with empty sections filled in. - Do not write a pep newsletter. - One CTA (send missing facts, or book a short call I can keep). Plain text. - Empty notes must stay visibly empty. </constraints> <format> Email A and Email B as Subject / Body, then a gap list. Star the one I should send to the client. </format>
Pro tip: If the quarter notes are thin, send a thin email. A padded QBR is how the next quarter starts on a fake baseline.
Lite Agenda Plus Cover Email
30/30✨ What it does
Claude writes a lite QBR agenda and cover email for [CLIENT NAME] from [AGENDA NOTES] and [PASTE NOTES]. You confirm the agenda, then send the email to the client.
You are a client-update writer who writes a lite QBR agenda and the cover email that sends it. Not a newsletter. Not a 30-slide QBR. Not an internal status report. <context> I have a short QBR-lite call with [CLIENT NAME]. I need an agenda plus a cover email I will send. Use only [AGENDA NOTES] and [PASTE NOTES]. Do not invent hours, results, or extra agenda items. </context> <inputs> - Client label: [CLIENT NAME] - Quarter: [QUARTER] - Agenda topics I will actually cover: [AGENDA NOTES] - Supporting notes: [PASTE NOTES] - Time I can hold: [TIME OPTIONS OR NONE] - Hours or results I can name: [HOURS OR RESULTS OR NONE] - Sender: [ME AT MY COMPANY] - Voice: [PLAIN / DIRECT] </inputs> <task> Write: (1) an agenda of only the topics in [AGENDA NOTES], with one line of support from [PASTE NOTES] each, (2) 2 cover emails (80 to 130 words) with subjects under 50 characters that send that agenda, (3) times only from [TIME OPTIONS OR NONE]. Hours or results appear only if I pasted them. Do not add a fourth topic. </task> <constraints> - Do not invent an agenda item, hours, or a result. - Do not invent a meeting length or a slide count. - Do not write a full QBR script. - One CTA in the cover email. Plain text. - If [AGENDA NOTES] are empty, write NEED AGENDA and stop. </constraints> <format> Agenda, then Email A and Email B as Subject / Body. Star the cover I should send to the client with the agenda. </format>
Pro tip: Paste the three topics you will actually cover. A seven-item agenda Claude adds is a meeting you cannot finish.
Free tool
Prompt Optimizer
Turn a rough idea into a structured, professional AI prompt.
Frequently Asked Questions
Prompts are the starting line. Tutorials are the finish.
A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.
7-day free trial. Cancel anytime.
Related guides