3 things you should stop doing manually in 2026
Stop rewriting important emails, chasing action items across notes, and staring at a blank slide deck. Copy a prompt. Paste your messy input. Edit the draft — AI drafts; you decide.
For: Non-technical professionals and small-team leads
Requirements: An approved text chat assistant · A short draft, meeting notes or a presentation goal with confidential information removed
Pick the task. Start where you're stuck.
Copy the prompt. Replace the placeholders.
Review the draft. AI drafts; you decide.
Executive Email Rewriter
Turn a messy draft into a concise, executive-ready email without losing facts or commitments.
You have a wordy, emotional, or unclear draft and need something concise, confident, and executive-friendly — before you hit send to a manager, client, or leadership thread.
- Your messy draft (or bullet notes of what you need to say)
- Audience (who you're writing to)
- Goal of the email (inform / ask / unblock / decide)
Jump to prompt ↓ · Find the example ↓
Steps
- Replace the placeholders with relevant, non-sensitive source material.
- Paste the prompt into your approved chat assistant.
- Compare every fact, owner, number and date against the input. Edit before using.
Rewrite the draft below into a concise, confident, executive-friendly email. Constraints: - Keep the final email under 100 words - Lead with the point / ask in the first 1–2 sentences - Keep a professional, calm tone (no fluff, no apology stacking) - Preserve every factual commitment, date, number, and name - End with one clear next step or ask Audience: [who this is for] Goal: [inform / ask / unblock / decide] DRAFT: [paste your messy draft or bullets] - Do not add new commitments, causes, meetings or deadlines. Preserve uncertainty. - Keep proposals separate from agreed actions; mark missing information as TBD.
Saves stay in this browser. Cross-device syncing is planned.
Limits, compatibility & evidence
- The response is a draft; it can omit or misread details.
- Do not add commitments, infer decisions or treat proposed actions as agreed.
- Use an employer-approved tool and remove confidential or personal information.
ChatGPT · Claude · Gemini · Microsoft Copilot (and similar general chat assistants). Paste as one message; no special plugins required.
Evidence
Illustrative example reviewed for fidelity on 18 September 2026. No recorded execution in external AI tools; compatibility is a text-format expectation, not a tested-model claim.
ExampleSee a realistic input → output +
Audience: VP of Customer Success Goal: ask DRAFT: Hey, just wanted to loop you in because we've been seeing some noise on renewals and I think we should maybe look at the Q3 onboarding friction again? The team mentioned a few tickets and I talked to Sarah and she said customers are confused about the new dashboard. Not sure if this is urgent but maybe we can put 30 mins on the calendar next week if you have time? Also John from support flagged two enterprise accounts. Thanks so much sorry for the long note!!
Subject: Q3 onboarding friction — review request Sarah reports that customers are confused about the new dashboard. The team mentioned several tickets, and John from Support flagged two enterprise accounts. Could we schedule 30 minutes next week to review the Q3 onboarding friction and renewal concerns?
Advanced versionAdd role + risk framing when the stakes are higher: +
You are an executive communications editor. Rewrite the draft below for a time-poor VP. Also provide: 1) Final email (≤100 words) 2) One-line subject options (3) 3) Risk if we wait 2 weeks (1 sentence, factual only — no invented stats) Audience: [who] Goal: [goal] DRAFT: [paste]
Meeting → Action Plan
Turn scattered notes into decisions, owners, next steps, and a send-ready follow-up.
Meeting notes are scattered (bullets, chat paste, half-sentences) and you need decisions, owners, deadlines, plus a short follow-up email you can send in minutes.
- Raw notes (messy is fine)
- Meeting context (topic + date if known)
- Default timezone / “this week” meaning if deadlines are vague
Jump to prompt ↓ · Find the example ↓
Steps
- Replace the placeholders with relevant, non-sensitive source material.
- Paste the prompt into your approved chat assistant.
- Compare every fact, owner, number and date against the input. Edit before using.
Turn these meeting notes into a clear action plan. Output exactly these sections: 1) Decisions made (bullets; say “None explicit” if unclear) 2) Action items — each with: Owner | Task | Deadline | Status (Open) 3) Open questions 4) Follow-up email — short, send-ready, under 120 words, summarizing decisions + asks Rules: - Do not invent owners, dates, or commitments that aren’t in the notes - If owner/deadline is missing, mark as TBD and list under Open questions - Use names exactly as written in the notes - Prefer verbs that start with action (Send, Draft, Schedule, Confirm) Meeting context: [topic + date] Notes: [paste messy notes] - Do not add new commitments, causes, meetings or deadlines. Preserve uncertainty. - Keep proposals separate from agreed actions; mark missing information as TBD.
Saves stay in this browser. Cross-device syncing is planned.
Limits, compatibility & evidence
- The response is a draft; it can omit or misread details.
- Do not add commitments, infer decisions or treat proposed actions as agreed.
- Use an employer-approved tool and remove confidential or personal information.
ChatGPT · Claude · Gemini · Microsoft Copilot (and similar). Best when you paste the full note dump in one go.
Evidence
Illustrative example reviewed for fidelity on 18 September 2026. No recorded execution in external AI tools; compatibility is a text-format expectation, not a tested-model claim.
ExampleSee a realistic input → output +
Meeting context: Retention standup — 2026-09-05 Notes: - dashboard confusion coming up a lot in onboarding calls - Sarah: will pull top 10 ticket themes by Wed - John: two enterprise accounts at risk — Acme + Northwind — needs CS briefs - decide: pause new feature emails until onboarding FAQ ships - team to draft FAQ outline this week? - follow up with VP next week on renewals noise
1) Decisions made - Pause new feature emails until the onboarding FAQ ships. 2) Action items - Sarah | Pull top 10 ticket themes | Wed (exact date TBD) | Open - TBD | Follow up with VP on renewals noise | Next week (exact date TBD) | Open 3) Open questions - Who will prepare the CS briefs for Acme and Northwind? John reported the need; no owner was assigned. - Is drafting the FAQ outline this week agreed? The notes phrase it as a question. - Who owns the VP follow-up and what is the exact date? - What counts as the FAQ being shipped? 4) Follow-up email Subject: Retention standup follow-up We agreed to pause feature emails until the FAQ ships. Sarah will pull the top 10 ticket themes by Wed. CS briefs are needed for Acme and Northwind; ownership is unconfirmed. Please confirm whether the FAQ outline is agreed for this week and who owns the VP follow-up next week.
Advanced versionAsk for a tracker-ready table + escalation indicator: +
Same rules as the Meeting → Action Plan prompt, plus: 5) A markdown table: Owner | Task | Deadline | Dependency | Escalation? (Yes/No) 6) Escalation = Yes only if notes imply revenue risk, blocked launch, or executive ask Meeting context: [topic + date] Notes: [paste]
Presentation Builder
Turn a goal and rough notes into a structured executive deck outline — without inventing data.
You need a first-draft executive slide structure from a blank page — not polished design. AI outlines; you refine story, data, and visuals.
- Presentation goal / topic
- Audience
- Desired slide count (default 8 to match Day 1 demo)
- Any must-include points (optional)
Jump to prompt ↓ · Find the example ↓
Steps
- Replace the placeholders with relevant, non-sensitive source material.
- Paste the prompt into your approved chat assistant.
- Compare every fact, owner, number and date against the input. Edit before using.
Create an 8-slide executive presentation outline for the goal below. For each slide provide: - Slide title - 3–5 speaker bullets (outcome-focused, no filler) - Suggested visual (chart, table, diagram, or simple layout note) Structure preference (adapt only if the goal truly needs it): 1) Executive Summary 2) Current Snapshot 3) Key Drivers / Problems 4) Opportunity Map 5) Playbook / Approach 6) Quick Wins 7) Metrics 8) Next Steps / Ask Rules: - Do not invent statistics, quotes, or case studies - Use placeholders like [metric] or [customer example] where data is needed - Keep language executive-clear and global-English friendly - This is a structured first draft, not finished slide design Goal: [e.g., improving customer retention] Audience: [e.g., leadership team] Must include: [optional bullets] - Do not add new commitments, causes, meetings or deadlines. Preserve uncertainty. - Keep proposals separate from agreed actions; mark missing information as TBD.
Saves stay in this browser. Cross-device syncing is planned.
Limits, compatibility & evidence
- The response is a draft; it can omit or misread details.
- Do not add commitments, infer decisions or treat proposed actions as agreed.
- Use an employer-approved tool and remove confidential or personal information.
ChatGPT · Claude · Gemini · Microsoft Copilot (and similar). For slide apps, paste the outline into your deck tool; do not claim auto-designed finished slides.
Evidence
Illustrative example reviewed for fidelity on 18 September 2026. No recorded execution in external AI tools; compatibility is a text-format expectation, not a tested-model claim.
ExampleSee a realistic input → output +
Goal: improving customer retention Audience: leadership team Must include: onboarding friction, enterprise risk accounts, FAQ + pause on feature emails
1) Executive summary - Goal: improve customer retention. - Focus: onboarding friction, enterprise risk accounts, FAQ and feature-email pause. - Decision required: [confirm the specific ask]. Visual: goal and three focus areas. 2) Current snapshot - Retention baseline: [data needed]. - Enterprise risk: [account evidence needed]. - Onboarding friction: [observations needed]. Visual: table with unfilled metric cells. 3) Onboarding friction - Describe observed issues: [evidence needed]. - Affected users: [data needed]. - Avoid asserting a cause without evidence. Visual: evidence list. 4) Enterprise risk accounts - List accounts: [names needed]. - Explain risk signals: [evidence needed]. - Confirm review owners: [TBD]. Visual: risk table. 5) FAQ and feature-email pause - Clarify the intended FAQ scope. - Confirm the status and scope of the pause. - Identify dependencies: [TBD]. Visual: dependency diagram. 6) Proposed next actions — not agreed - Validate the source data. - Ask for owners. - Agree dates before committing. Visual: draft checklist. 7) Measurement proposal - Candidate measure: retention [baseline TBD]. - Candidate measure: onboarding completion [baseline TBD]. - Confirm availability and definitions. Visual: blank scorecard. 8) Next steps - Confirm the decision sought. - Assign owners only after agreement. - Set dates only after confirmation. Visual: open questions list.
Advanced versionAdd a one-page narrative + anti-hallucination check: +
Using the Presentation Builder rules above, also deliver: A) A 90-second verbal narrative (what you’d say if slides fail) B) A “Data needed” list — every placeholder that must be filled before presenting C) Explicit line: “No statistics were invented in this outline.” Goal: [goal] Audience: [audience] Must include: [optional]
Pro sample · free to use
Connect the whole task.
Try the meeting follow-through pack: agenda, action register, follow-up and weekly update. The sample is available now; the paid pack library is planned.
Pro proposal: US$7/month or US$70/year. No card or payment today.
Stop starting from zero.
Pick the task slowing you down. Copy the exact prompt. Replace the placeholders with your real context. Run it in the AI assistant you already use, then review and edit the result before acting on it.
Works with general-purpose chat assistants in the ChatGPT / Claude / Gemini / Microsoft Copilot class. No single-vendor endorsement. Results vary with input quality and model; treat outputs as drafts, not guarantees.Illustrative examples reviewed for fidelity on 18 September 2026.
- Examples are drafts, not verified statements about your business.
- Tool output may vary. No external AI execution evidence is available for this edition.