Your AI Action Plan

Write a client message from these notes.
Client context: [CONTEXT]
Goal: [UPDATE / ASK / EXPLAIN / FOLLOW UP]
Notes: [PASTE NOTES]
Tone: professional, warm, and concise.
Include: clear answer, next step, owner, and deadline if relevant.

Create five client-message templates for my role: status update, request for missing info, delay explanation, decision explanation, and follow-up. Each template should include placeholders, tone guidance, and a checklist for facts I must verify before sending.

Use this client context and draft to prepare a final message.
Context: [PASTE]
Draft: [PASTE]
Check for: factual accuracy, unclear promises, missing deadlines, tone risks, and next step. Return the revised message plus a send/no-send checklist.

Build a client communication style guide for [ROLE / COMPANY]. Include: approved tone, banned phrases, claims that require review, escalation triggers, examples of good messages, and a checklist before sending AI-assisted messages.

Summarize this meeting.
Notes or transcript: [PASTE]
Return: 1. short summary, 2. decisions made, 3. action items with owner and due date, 4. risks, 5. follow-up message draft.

Review this meeting transcript and create a follow-up note. Separate exact decisions from discussion points. Flag anything unclear. Transcript: [PASTE TRANSCRIPT].

Convert this meeting transcript into project tasks. For each task include owner, due date, dependency, priority, and a follow-up email paragraph. Transcript: [PASTE].

Create a meeting memory template for [TEAM / CLIENT]. For each meeting, capture decisions, action items, repeated themes, unresolved questions, stakeholder commitments, and items to revisit next time.

Write a weekly [TEAM / CLIENT / PROJECT] report.
Period: [DATE RANGE]
Metrics: [PASTE METRICS]
Highlights: [WHAT WENT WELL]
Risks or blockers: [WHAT NEEDS ATTENTION]
Next actions: [3-5 BULLETS]
Audience: [MANAGER / CLIENT / TEAM]. Keep it factual, concise, and easy to scan.

Analyze this report data before drafting the summary.
Data: [PASTE TABLE OR METRICS]
Return: 1. Top 5 changes, 2. likely explanations, 3. questions to verify, 4. what should be highlighted, 5. what should not be overclaimed.

Turn this exported data into a decision memo.
Audience: [WHO WILL READ IT]
Data: [PASTE CSV OR TABLE]
Return: executive summary, key changes, likely causes, recommended action, risks, and a short appendix explaining assumptions.

Create a reusable monthly review template for [ROLE / TEAM]. It should include: required inputs, KPI table, variance analysis, stakeholder narrative, recommended actions, risks, and a quality checklist before sending.

Analyze this data for trends, outliers, and practical next steps. Return: 1. top 5 findings, 2. possible explanations, 3. questions to verify, 4. recommended next actions. Do not assume causes without evidence.

Data:
[PASTE]

In this workbook, analyze [TABLE/RANGE] and answer: What changed most, what looks unusual, which rows need attention, and what chart or pivot would best explain the result?

Use these spreadsheet findings to write a decision memo. Include: headline insight, supporting numbers, likely drivers, caveats, recommended action, and what data should be checked next.

Findings:
[PASTE]

Create a recurring analysis checklist for [DATA TYPE]. Include: required inputs, cleaning checks, metrics to calculate, outlier rules, interpretation questions, caveats, and the final memo format.

Write a [TYPE - cold outreach / follow-up / proposal / status update] email.
From: [YOUR ROLE] at [COMPANY]
To: [RECIPIENT ROLE] at [THEIR COMPANY]
Context: [1-2 sentences of background]
Goal: [what you want them to do]
Tone: [professional / friendly / direct]
Length: [short = 3 sentences / medium = 1 short paragraph / full = structured email]

Write a weekly marketing performance report.
Period: [DATE RANGE]
Metrics to include: [list your KPIs]
Highlights: [what went well]
Issues: [what underperformed and brief reason]
Next week priorities: [3 bullet points]
Audience: [manager / team / client]
Tone: factual, no fluff. Use bullet points for metrics, short paragraphs for narrative.

Turn these rough notes into a clear [EMAIL / STATUS UPDATE / REPORT].
Audience: [WHO WILL READ IT]
Purpose: [DECISION, UPDATE, REQUEST, OR ESCALATION]
Raw notes:
[PASTE NOTES]

Return:
1. Suggested subject line
2. Short summary
3. Main message in my tone: [DIRECT / WARM / EXECUTIVE]
4. Action items with owners and dates
5. Risks or open questions

I'll share 3 examples of emails I've written. After reading them, identify:
1. My typical sentence length and structure
2. Words or phrases I use often
3. My tone (formal / casual / direct / warm)
4. Things I never say

[PASTE EMAIL 1]
[PASTE EMAIL 2]
[PASTE EMAIL 3]

Now write a [TYPE] email using my style. Here's the context: [CONTEXT]

Create a renewal-risk summary for this customer.
Account context: [PASTE]
Usage/adoption notes: [PASTE]
Support issues: [PASTE]
Commercial context: [PASTE]
Return: risk level, evidence, missing information, likely root causes, customer questions, and next best action. Separate facts from assumptions.

Build a 30-day success plan for an at-risk customer.
Health signals: [PASTE]
Customer goals: [PASTE]
Known blockers: [PASTE]
Return: success outcome, risk drivers, customer-facing actions, internal owner actions, timeline, and proof that risk is improving.

Use this account-health export to create a renewal rescue packet.
Data: [PASTE]
Return: 1. risk summary, 2. evidence table, 3. 30-day recovery plan, 4. internal escalation note, 5. customer-facing email draft, 6. fields that must be verified before sending.

Create a renewal-risk playbook for customer success. Include risk signals, evidence needed, first response, escalation trigger, customer-facing message, internal owner, and proof that the risk is improving for each risk type: usage drop, sponsor change, unresolved support issue, adoption gap, and missing business value.

Turn these kickoff notes into a customer onboarding checklist.
Notes: [PASTE]
Return: onboarding goal, milestones, customer owner, internal owner, due date, dependency, risk, and first follow-up email draft.

Create an onboarding resource pack for this customer.
Customer goals: [PASTE]
Plan: [PASTE]
Known questions: [PASTE]
Return: resource list, training agenda, success criteria, reminder schedule, and first-week message.

Create an onboarding operating pack from this kickoff transcript.
Transcript: [PASTE]
Return: customer goals, milestones, owners, risks, unanswered questions, customer portal update, and internal CSM notes.

Design a reusable onboarding plan generator for [CUSTOMER SEGMENT]. Include intake questions, default milestones, training modules, success metrics, stakeholder map, risk triggers, and message templates for weeks 1, 2, 4, and 8.

Cluster this customer feedback into product themes.
Feedback: [PASTE]
Return: theme, customer quotes, affected segment, frequency, business impact, urgency, and suggested product-team question.

Create a product feedback brief from these customer issues.
Issues: [PASTE]
Return: problem statement, evidence, customer impact, affected accounts, workaround, suggested fix area, and priority rationale.

Convert this support export into product tracker entries.
Export: [PASTE]
Return: theme, evidence, customer examples, severity, affected plan/segment, suggested product owner, and tracker-ready ticket text.

Design a monthly voice-of-customer loop for customer success. Include: data sources, tagging rules, theme scoring, customer quotes, product-team routing, escalation criteria, and monthly evidence-pack format.

Turn these customer metrics into a QBR value story.
Metrics: [PASTE]
Customer goals: [PASTE]
Return: executive summary, wins, risks, adoption gaps, recommended next steps, and questions for the customer.

Create a QBR outline for this customer.
Account data: [PASTE]
Customer goals: [PASTE]
Return slide titles, key message per slide, supporting evidence, and talk track. Keep claims tied to the data.

Create a QBR operating pack from this usage and account data.
Data: [PASTE]
Return: QBR deck outline, speaker notes, risks to discuss, customer asks, post-meeting action plan, and follow-up email.

Design a QBR template library for customer success. Include templates for onboarding review, adoption review, renewal risk, expansion opportunity, and executive sponsor review. Each template should include inputs, slide outline, proof points, customer questions, and follow-up format.

Create an expansion opportunity summary.
Usage signals: [PASTE]
Stakeholder notes: [PASTE]
Current plan: [PASTE]
Return: possible expansion area, evidence, objections, questions to verify, and suggested next conversation.

Prepare a sales handoff packet for a possible expansion.
Customer context: [PASTE]
Evidence: [PASTE]
Return: opportunity summary, customer value, timing, risks, open questions, suggested sales next step, and what not to say yet.

Build an expansion coordination packet.
Inputs: [PASTE]
Return: account opportunity, evidence, customer outcome, stakeholders, risk, internal owner actions, customer-facing next step, and a 5-bullet Slack brief.

Create an expansion-readiness scorecard for customer success. Include usage growth, feature depth, stakeholder engagement, business outcome proof, unresolved support risk, renewal timing, and customer sentiment. Add rules for when to involve sales and when to wait.