Your AI Action Plan

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.

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.

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 research brief on [TOPIC] for [AUDIENCE]. Include: current landscape, 5 key facts, 3 risks, 3 open questions, and source links for every claim that affects a decision.

Review this research draft. Split it into: source-backed facts, reasonable inferences, unsupported claims, and questions to verify. Then rewrite the summary so unsupported claims are removed or clearly caveated.
Draft: [PASTE DRAFT]

Research [OPTIONS / VENDORS / TOPIC], compare them against [CRITERIA], and produce a recommendation memo. Include a table, tradeoffs, risks, source links, and the decision I should make if the priority is [COST / SPEED / QUALITY / RISK].

Create a research intake template for [ROLE / TEAM]. It should capture: decision to support, scope, time period, must-use sources, sources to avoid, comparison criteria, output format, approval owner, and caveats required before sharing.

Write a scheduling email for [MEETING PURPOSE].
Participants: [WHO]
Time options: [OPTIONS]
Duration: [LENGTH]
Prep needed: [PREP]
Tone: [FRIENDLY / DIRECT / FORMAL]
Include a 3-bullet agenda and a clear reply request.

Write a short message that shares my booking link and explains the purpose of the meeting.
Booking link: [LINK]
Purpose: [PURPOSE]
Who should attend: [ROLES]
What to prepare: [PREP]
Keep it under 120 words.

Create intake questions for a [MEETING TYPE] booking page. Then write a prep brief template that summarizes the answers into: context, goal, risks, decisions needed, and agenda.

Build a meeting routing playbook for [TEAM / ROLE]. Include: meeting types, when to book vs handle async, required attendees, intake questions, agenda templates, prep checklist, and follow-up owner.

Create a review checklist for uncategorized bank transactions.
Client: [CLIENT TYPE]
Account: [BANK / CREDIT CARD]
Transaction examples: [PASTE 10-20 ROWS]
Return: likely category, confidence, questions to ask the client, and items that must be reviewed by a human before posting.

Group these unreconciled or unclear transactions into a client question list.
Transactions: [PASTE ROWS]
Return: grouped questions, transaction dates, amounts, likely category, why it is unclear, and the exact answer needed from the client.

Act as a bookkeeping review assistant. For these bank feed exceptions, return: probable category, supporting clue, risk level, client question if needed, and do-not-post warning if the item may affect tax, payroll, or owner draws.
Rows: [PASTE EXPORT]

Build a monthly reconciliation QC checklist for [CLIENT TYPE]. Include: bank feed checks, duplicate checks, unusual category review, outstanding client questions, items requiring accountant review, and final sign-off criteria.

Write a polite payment reminder.
Client: [CLIENT NAME]
Invoice: [NUMBER]
Amount: [AMOUNT]
Due date: [DATE]
Context: [PASTE NOTES]
Tone: professional and calm. Do not invent payment terms. Include a clear next step.

Create four invoice reminder templates: before due, 7 days overdue, 14 days overdue, and final reminder. Include placeholders for invoice number, amount, due date, payment link, and contact person. Keep tone firm but respectful.

Turn this accounts receivable aging report into a follow-up queue.
Data: [PASTE REPORT]
Return: priority, suggested message type, risk note, client-specific context needed, and draft reminder. Do not change amounts or due dates.

Build a collections communication playbook for [CLIENT / BUSINESS]. Include reminder timing, tone by overdue stage, escalation rules, payment-link handling, exceptions that require human approval, and message templates.

Review these extracted receipt fields for bookkeeping risk.
Rows: [PASTE VENDOR, DATE, AMOUNT, CATEGORY, TAX]
Return: likely issues, duplicate risk, missing fields, client questions, and items that require human review before posting.

Create vendor coding notes from this list.
Vendor transactions: [PASTE ROWS]
Return: vendor, usual category, exceptions to watch for, required receipt details, and questions to ask if the pattern changes.

Create an exception queue from these receipt-capture exports.
Data: [PASTE]
Flag: missing receipt, duplicate amount/date, unusual vendor, possible personal expense, tax field concern, and client question needed.

Build a document intake QC system for [CLIENT TYPE]. Include: required fields, vendor coding rules, duplicate checks, missing document workflow, tax-sensitive review flags, and monthly close handoff.

Create a month-end bookkeeping close checklist for [CLIENT TYPE]. Include bank reconciliation, receipts, bills, invoices, payroll inputs, sales tax support, unusual balances, client questions, and accountant review flags.

Review these month-end balances and draft close notes.
Balances and changes: [PASTE]
Return: unusual changes, likely explanation, question to verify, risk level, and whether accountant review is needed.

Build a month-end close pack from this status.
Status: [PASTE TASKS, BALANCES, EXCEPTIONS]
Return: completed steps, unresolved items, client questions, accountant review flags, and final close readiness score from 1-5.

Create a reusable month-end close playbook for [CLIENT TYPE]. Include close calendar, source documents, reconciliation checks, exception thresholds, client-question templates, accountant-review triggers, and final sign-off criteria.

Explain this cash flow summary in plain English for a small business owner.
Data: [PASTE CASH SUMMARY]
Return: what changed, likely drivers, risks, questions to verify, and actions the owner may consider discussing with their accountant.

Analyze these cash flow categories month over month.
Data: [PASTE]
Flag: unusual increases or decreases, likely causes, missing context, client questions, and anything that should be reviewed before sending.

Turn this cash report into a client action memo.
Data: [PASTE]
Return: summary, biggest cash drivers, possible risks, questions for the owner, suggested next conversation, and disclaimer that this is bookkeeping support, not financial advice.

Create a monthly anomaly review pack for bookkeeping clients. Include: data inputs, cash movement checks, category variance thresholds, client questions, accountant-review triggers, and a final owner-friendly summary template.