The prompts that quietly give you back an hour a day — outreach, status reports, meeting
notes, content briefs and recaps — each copy-ready with an example output.
Most work isn’t the thinking; it’s the writing around the thinking. These prompts handle
that layer: the cold email you keep rewriting, the weekly update to your boss, the meeting
that needs turning into owned action items, the content brief before anyone drafts a word.
Each one is built with real constraints and a guardrail against inventing facts, so the
output is something you can actually send after a quick edit.
The real leverage comes after the draft. If your work is marketing or SEO, the next step is
shipping the technical pieces; if it’s operations, it’s removing yourself from the loop
entirely. The two tools below are where this library hands off.
14 prompts · free to copy · example output on each
ChatGPTGeminiClaude
Cold outreach email to a new lead
Write a short, personalized cold email that earns a reply instead of a delete.
The prompt
You are an experienced B2B sales rep known for cold emails that get replies. Write a cold outreach email to [PROSPECT NAME], the [JOB TITLE] at [COMPANY].
Context:
- What we sell: [ONE-LINE PRODUCT DESCRIPTION]
- The problem we solve for companies like theirs: [PAIN POINT]
- One specific thing I noticed about their company: [TRIGGER / RESEARCH NOTE]
Rules:
- Under 120 words, plain language, no buzzwords.
- Open with the specific observation, not "I hope this finds you well."
- One clear call to action: a 15-minute call.
- Plain text, no markdown. Then give me 2 subject line options.
Example output
Subject A: a quick idea for [Company]'s new office
Subject B: [Company] + faster ramp for new reps?
Hi [Name],
Saw [Company] just opened a second support office — congrats. Scaling support usually means new hires fielding the same 20 questions for weeks.
We give support teams an answer layer trained on your own docs, so new reps ramp in days instead of months. [Similar company] cut their ramp time by about a third.
Worth a 15-minute call next week to see if it'd fit your new office? Happy to work around your calendar.
Thanks,
[Your name]
TipPaste a real LinkedIn or news detail into the trigger line — generic openers are exactly what gets cold emails deleted. Asking for "2 subject line options" gives you something to A/B test.
ChatGPTGeminiClaude
Recap email after a sales call
Send a same-day recap that confirms next steps and keeps the deal moving.
The prompt
Turn my rough call notes into a clean recap email to the prospect. Structure:
- One-line thank you.
- "What I heard" — 3 bullets restating their priorities (shows I listened).
- "Next steps" — who does what, by when.
- A clear ask to confirm the next meeting.
Keep it skimmable. Don't invent anything not in my notes.
My notes: [PASTE NOTES]
Example output
Subject: recap + next steps from today
Hi [Name],
Thanks for the time today — useful conversation.
What I heard matters most to you:
- Cutting new-rep ramp from ~6 weeks to under 2.
- Keeping answers accurate as your docs change weekly.
- A rollout that doesn't pull your leads off the floor.
Next steps:
- Me: send the security overview by Friday.
- You: loop in [IT contact] for the data question.
- Both: 30-min technical review next Wed.
Does Wednesday 2pm still work to lock that in?
[Your name]
TipThe "what I heard" section is the secret weapon — restating their priorities in their words builds more trust than any feature recap. Send it within a few hours while it is fresh.
ChatGPTGeminiClaude
Turn messy meeting notes into clear action items
Convert raw notes or a transcript into decisions, owners, and next steps.
The prompt
Below are raw notes from a team meeting. Turn them into a clean summary for people who weren't there.
Format:
1. **TL;DR** — 2 sentences.
2. **Decisions made** — bullet list.
3. **Action items** — a table: Task | Owner | Due date. If an owner or date wasn't stated, write "unassigned" — do not invent one.
4. **Open questions** — anything left unresolved.
Keep it factual. Don't add advice. Here are the notes:
[PASTE NOTES OR TRANSCRIPT]
Example output
**TL;DR** — The team approved the Q3 pricing test and pushed the mobile redesign to August. Two action items are unassigned.
**Decisions made**
- Run the pricing A/B test on the Pro plan starting July 1.
- Delay the mobile redesign to August to avoid the holiday code freeze.
**Action items**
| Task | Owner | Due date |
|---|---|---|
| Set up pricing test in billing | Priya | Jun 27 |
| Draft August launch timeline | unassigned | unassigned |
| Tell support about the price change | Marco | Jun 30 |
**Open questions**
- Who signs off on the final August date?
TipThe "do not invent owners or dates" rule is what makes this trustworthy — AI otherwise fills gaps with plausible-but-wrong names. Paste a Zoom/Meet transcript directly for best results.
ChatGPTGeminiClaude
Write a weekly status report for your boss
Turn the week's work into a tight update leadership actually reads.
The prompt
You are a senior manager writing a weekly status report. Turn my bullet-point notes into a clean update my director will read in under two minutes.
Format:
1. **This week** — 3–5 bullets of concrete progress (metrics or deliverables, not effort).
2. **Next week** — 2–3 priorities with owners.
3. **Blockers** — anything I need from leadership. If none, write "None."
Rules: plain language, no filler phrases like "we continued to work on," numbers wherever I have them, under 200 words total.
My notes: [PASTE YOUR WEEK'S NOTES]
Example output
**This week**
- Shipped the onboarding email sequence; open rate at 41% vs. 29% baseline.
- Closed two enterprise pilots — Meridian Health and Solis Finance (combined ARR: $84,000).
- Reduced P1 ticket backlog from 34 to 11 by reallocating two engineers from the feature queue.
- Completed Q3 headcount plan; submitted to HR on Thursday.
**Next week**
- Priya: finalize security review for Meridian (due Thu).
- Tom: start sprint 14 with new backlog priority order.
- Me: present Q3 plan to leadership on Wednesday.
**Blockers**
- Need sign-off on the contractor extension for Tom's team by Monday — delays sprint 14 otherwise.
TipForce yourself to write numbers into the notes before pasting — "shipped onboarding emails" is useless; "open rate 41% vs. 29% baseline" is what leadership remembers. The AI can't invent metrics you didn't give it.
ChatGPTGeminiClaude
Delegate a task clearly over email
Hand off a task with context, expectations, and a deadline.
The prompt
Write a delegation email assigning a task to [PERSON NAME]. The email should not feel like a dump — it should give them what they need to succeed.
Include:
- What the task is and why it matters (one sentence of context).
- What "done" looks like (specific deliverable and format).
- The deadline and any key constraints.
- Who to loop in and who NOT to loop in.
- An explicit invitation to flag problems early.
Under 150 words. Plain language. No "per my last email."
Task details: [DESCRIBE THE TASK, DEADLINE, CONSTRAINTS]
Example output
Subject: Meridian security review — over to you
Hi Priya,
Meridian asked for a security questionnaire before they sign — this is the last gate before the contract. I'd like you to own the response.
Deliverable: completed questionnaire + a one-page summary of anything we can't answer today. Google Doc, shared with me and Legal.
Deadline: draft by Tue Jun 24, final by Thu Jun 26.
Loop in: Tom for the infrastructure questions (sections 3–4). Do not loop in Sales yet — I'll brief them after Legal reviews.
If you hit something that looks like a real gap, flag it to me before writing around it — better to surface it early than have Legal catch it.
Thanks,
[Your name]
TipSpelling out "what done looks like" is the single biggest delegation failure point — without a concrete deliverable format, you get back whatever the person assumed you wanted. The "flag problems early" line prevents the quiet struggle that kills deadlines.
ChatGPTGeminiClaude
Write an SEO content brief
Give a writer everything they need to rank: intent, outline, keywords, angle.
The prompt
Write a complete SEO content brief for an article targeting the keyword [TARGET KEYWORD].
Include:
- Primary keyword and 4–6 semantically related terms to weave in naturally
- Search intent classification (informational / navigational / commercial / transactional)
- Target audience and their assumed knowledge level
- Recommended word count range
- Suggested H1, H2 headings, and one H3 example
- One competing article to beat and what it is missing
- Angle that differentiates our piece
- One internal-link opportunity to [RELATED PAGE OR CATEGORY]
Topic area: [TOPIC]. Our product/service: [PRODUCT].
Example output
Target keyword: project management software for agencies
Intent: Commercial investigation (users comparing options before buying)
Audience: Agency ops managers, 30–200 staff; know PM tools, deciding to switch
Related terms to include: agency workflow software, client project tracking, resource allocation tool, retainer management, agency time tracking
Word count: 1,800–2,400
H1: The Best Project Management Software for Agencies in 2025
H2s: What makes agency PM different | How we tested | Top 6 tools | Feature comparison | Who should pick what | Bottom line
Gap in top result: Lacks pricing tiers and doesn't address retainer-based billing.
Angle: Focus on retainer + billable-hour workflow — the agency-specific pain point competitors skim.
Internal link: Link to /agency-time-tracking-guide at first mention of "time tracking."
TipPasting one competing article's URL and asking the model to find its gaps produces sharper angle ideas than asking it to invent them from scratch.
ChatGPTGeminiClaude
Write a marketing newsletter
Draft a newsletter people open and click, from your raw updates.
The prompt
Write a marketing email newsletter using my raw notes below.
Structure:
1. Subject line (curiosity-driven, under 50 characters, no clickbait)
2. Preview text (complements the subject, under 90 characters)
3. Opening hook — one or two sentences that make the reader feel the issue is already theirs
4. Main content — [NUMBER] sections, each with a short header, 2–3 sentences, and one link
5. Sign-off from [SENDER NAME / PERSONA]
Tone: [e.g., direct and warm / conversational / expert but approachable]
Raw updates to include: [PASTE YOUR NOTES OR BULLET POINTS]
Example output
Subject: The report nobody reads (and how to fix it)
Preview: Most client reports answer the wrong question entirely.
---
Hi [First Name],
Every client report answers "what happened?" Most clients want to know "should I be worried?" That gap is why reports don't get read.
THIS WEEK
Reporting fix
Stop leading with traffic. Lead with the metric that decides the month — revenue, leads, or pipeline. One number, then context. [Read the full approach →]
Template we're sharing
We built a one-page weekly client dashboard that fits on a phone screen. No scroll required. [Download it free →]
Quick read
Rand Fishkin on why vanity metrics survive: "Because they're easy to report, not because they matter." Worth 4 minutes. [Link]
---
Until next week,
[Sender Name]
TipWrite the preview text to complete the subject line, not repeat it — together they are one sentence the reader reads before deciding to open. Testing them as a unit beats A/B testing either one alone.
ChatGPTGeminiClaude
Repurpose a blog post into social
Spin one article into a week of platform-ready posts.
The prompt
Take the blog post below and repurpose it into 5 social media posts — one per platform: LinkedIn, Twitter/X, Instagram, Facebook, and Threads.
Each post should:
- Pull a distinct angle or insight from the article (no two posts should make the same point)
- Match the platform's tone and length norms
- Include a platform-appropriate CTA linking back to the article
Blog post: [PASTE POST OR SUMMARY]
Article URL: [URL]
Example output
LinkedIn (professional, ~150 words): "Most agencies blame scope creep for missed deadlines. The data says it's usually something quieter: nobody agreed on what 'done' looks like at kickoff. We analyzed 200 completed agency projects and found that the ones finishing on time shared one habit... [link]"
Twitter/X (~240 chars): "Agencies that finish projects on time don't have better clients. They agree on 'done' before work starts. 3 questions we ask every kickoff: [link] 🧵"
Instagram (caption, visual hook): "The one question that prevents scope creep 👇 (swipe to see all 3) Most agencies never ask it at kickoff. Full breakdown at the link in bio."
Facebook (~80 words conversational): "We looked at 200 agency projects to find what on-time delivery actually had in common. It wasn't better tools or bigger teams. It was one kickoff habit. Worth a read if your deadlines slip more than you'd like. [link]"
Threads (casual, 2 short paras): "Hot take: scope creep is a kickoff problem, not a client problem. Read our breakdown — link in bio."
TipForce each post to pull a different angle by numbering the key insights in the article and assigning one insight per platform — this prevents every caption from recycling the same hook.
ChatGPTGeminiClaude
Recruiter outreach email to a passive candidate
Write a personalized outreach that makes a happy-where-they-are candidate curious.
The prompt
You are a senior recruiter who fills roles candidates actually want. Write a cold outreach email to [CANDIDATE NAME], a [CURRENT ROLE] at [CURRENT COMPANY] who is not actively looking.
Context:
- Role I'm hiring for: [JOB TITLE] at [HIRING COMPANY]
- Why this role is genuinely interesting: [SPECIFIC DRAW — growth, team, problem, comp]
- One specific thing about the candidate's background that fits: [OBSERVATION FROM THEIR PROFILE]
Rules:
- Under 120 words, no recruiter boilerplate.
- Open on the observation about them, not on us.
- Don't reveal comp unless I include it.
- End with a soft ask — a short call, not a full application. Plain text.
Example output
Subject: [Candidate name] — a role that looked like you
Hi [Name],
Noticed your work leading the identity verification overhaul at [Current Company] — that's exactly the kind of gnarly infra problem the team here is walking into next.
[Hiring Company] is a 200-person fintech building a compliance stack from scratch. The engineering org is small enough that your work ships fast, and the domain is the same one you've been doing for the past three years — just with more scope.
Would a 20-minute call next week be worth your time? Happy to share more before you decide if it's a fit.
[Your name]
TipName one concrete thing from their actual work history — not their job title. Passive candidates delete generic outreach instantly; a single specific observation signals you did real homework.
ChatGPTGeminiClaude
Turn interview notes into a debrief
Convert raw interview notes into a structured evaluation.
The prompt
Convert my raw interview notes into a structured debrief for sharing with the hiring team.
Candidate: [NAME]
Role: [JOB TITLE]
Interviewer: [YOUR NAME]
Notes: [PASTE RAW NOTES]
Output format:
- Headline: one sentence on overall impression.
- Strengths observed (bullets)
- Concerns or gaps (bullets)
- Standout moment: one specific exchange worth sharing
- Recommendation: Advance / Hold / Pass — with one line of reasoning
Only use what's in my notes. Don't soften concerns to be polite.
Example output
Candidate: Maya Chen | Role: Head of Growth | Interviewer: J. Park
Headline: Strong strategic thinker, but gave thin answers when pushed on execution specifics.
Strengths:
- Articulated a full-funnel growth model unprompted — showed systems thinking.
- Comfortable with ambiguity; described building a team from scratch at her last role.
Concerns:
- When asked about a campaign that underperformed, pivoted to what the team learned without owning her own call that was wrong.
- No specific CAC or payback period numbers cited in any example.
Standout moment: Her reframe of retention as a growth lever landed well — clear, original, and grounded.
Recommendation: Hold — ask a second interviewer to pressure-test the execution gap before advancing.
TipAsk for a "standout moment" explicitly — it gives the hiring team a concrete anchor for the debrief conversation, rather than a list of bullets they have to interpret on their own.
ChatGPTGeminiClaude
Summarize options into a decision memo
Lay out choices, trade-offs, and a recommendation for a fast decision.
The prompt
Write a decision memo for [DECISION MAKER / AUDIENCE] on the question: [THE DECISION TO BE MADE].
Format:
1. **Context** — why this decision is needed now (2–3 sentences).
2. **Options** — a table: Option | Pros | Cons | Cost/Effort.
3. **Recommendation** — which option you recommend and the one-sentence reason.
4. **What we need from you** — the specific ask (approval, a call, a sign-off).
Be direct. State a recommendation even if the data is imperfect. Under 300 words.
Details: [PASTE OPTIONS, TRADE-OFFS, YOUR PREFERRED CHOICE AND WHY]
Example output
**Decision: Hire vs. Contract for Design Role**
To: [Director] | Date: Jun 17
**Context**
The onboarding project needs a designer by July 1 to hit the Aug 31 ship date. The role has been open for six weeks; the pipeline has two candidates but no offer-ready finalist.
**Options**
| Option | Pros | Cons | Cost |
|---|---|---|---|
| Extend contractor (Lena) | Available now, knows the product | 20% premium, not a long-term fix | $12,000 for 8 weeks |
| Wait for hire | Right long-term | Delays project 3–6 weeks | $0 now, risk of Q3 miss |
| Freelancer via agency | Fast, low overhead | Ramp time, no product context | $8,000–$14,000 |
**Recommendation**
Extend Lena's contract through August. She's already ramped, and missing the August date costs more than the premium.
**What we need from you**
Approval to extend Lena at the current rate through Aug 31. I need this by Monday to give her enough notice.
TipState your recommendation explicitly — "option B" is not a recommendation. Saying "I recommend X because Y" forces you to commit, and it's exactly what decision-makers need to move fast. A memo that hedges everything is a memo that gets no action.
ChatGPTGeminiClaude
Win/loss summary from deal notes
Extract why a deal was won or lost so the next one goes better.
The prompt
Analyze my notes from a closed deal and produce a win/loss summary:
- Outcome: Won / Lost
- Primary reason (one sentence)
- Contributing factors (bullets)
- What the competitor did, if mentioned
- One thing I'd do differently next time
Be honest, not flattering. Only use what's in the notes.
Deal notes: [PASTE NOTES]
Example output
Outcome: Lost
Primary reason: We were brought in too late — they'd already shortlisted two vendors before our first call.
Contributing factors:
- Champion liked us but wasn't the budget owner.
- Our security review took 9 days; competitor turned theirs around in 2.
- We never got a meeting with the CFO.
Competitor: Won on faster procurement, not product.
Do differently: Qualify "where are you in the process?" on call one, and pre-stage the security packet.
TipRun this on both wins and losses — patterns across 10 of these tell you more about your sales process than any single deal. Be ruthlessly honest in the notes or the summary is useless.
ChatGPTGeminiClaude
Summarize a competitor's positioning
Distill a competitor's site or messaging into strengths and gaps.
The prompt
Analyze the competitor messaging I've pasted below and produce a structured summary.
Sections:
1. Core positioning statement (what problem they claim to solve, for whom)
2. Key claims and proof points they use (list the top 4–5)
3. Messaging strengths — what they do well and why it works
4. Messaging gaps or weaknesses — what they underplay or avoid
5. How our positioning should differ — one paragraph on the angle to own
Competitor name: [NAME]
Our product: [DESCRIPTION]
Competitor messaging (paste homepage copy, about page, or ad text): [PASTE]
Example output
Competitor: Whatagraph
1. Core positioning: "One platform to collect, visualize, and share marketing data" — aimed at agencies managing multiple client accounts. Positions on multi-source integration and speed.
2. Key claims: 100+ integrations; auto-scheduled reports; client-ready white-label; no developer needed; "saves 10+ hours per week."
3. Strengths: Integration breadth is credible and specific. "No developer" claim directly removes the biggest agency objection. White-label framing respects the agency relationship.
4. Gaps: No social proof with specific numbers on homepage. Doesn't address accuracy/data freshness. Pricing page buried — creates friction. No mention of what happens when a data source breaks.
5. Differentiation angle: Own data reliability and audit trail. Lead with "reports your clients trust" rather than "reports that build themselves" — shift the value from time saved to credibility earned.
TipPaste the competitor's homepage, pricing page, and one ad into the prompt together — the gaps between what they say on each page often reveal more than any single page alone.
ChatGPTGeminiClaude
Build a 1:1 meeting agenda
Prep a focused agenda for a one-on-one with a direct report.
The prompt
Help me build a 1:1 agenda for a meeting with [DIRECT REPORT NAME], who is a [ROLE].
Context about this person:
- Current project or focus: [PROJECT]
- Any recent wins or concerns I want to acknowledge: [NOTES]
- Open items from last 1:1: [CARRYOVER ITEMS, or "none"]
Generate a 30-minute agenda that:
1. Opens with their update, not mine (2–3 prompt questions, not yes/no).
2. Covers the carryover items.
3. Includes one development or career question.
4. Ends with clear next steps we both own.
Example output
**1:1 — Priya / Jun 17 — 30 min**
**Her update (10 min)**
- How is the Meridian security review going — any surprises?
- What's felt most and least useful to you this week?
- Anything slowing you down I don't know about?
**Carryover (8 min)**
- Decision: timeline for looping in Legal on the data agreement.
- Status: conference talk proposal — did she submit?
**Development (7 min)**
- You've been handling more client-facing work lately — is that something you want more of, or is it pulling you off the work you'd rather do?
**Next steps (5 min)**
- Me: get Legal intro by Wed.
- Priya: send talk proposal link by EOD Fri.
TipOpen with their update, not yours — it signals you're there to unblock them, not broadcast at them, and you'll surface problems that never make it into a status email. Carry the open items from last time in a persistent doc so nothing drops.
Use it for the repetitive writing and synthesis around your job — drafting emails, summarizing documents, turning meetings into action items, writing first drafts of reports — then review and edit. Treat it as a fast first-drafter, not a decision-maker, and never paste confidential data into an unapproved tool.
Is it safe to use ChatGPT for work documents?
Only with tools your employer approves, and without confidential, customer, or regulated data unless your company has cleared it. For sensitive material, work from your own notes rather than pasting source documents.
How do I turn these prompts into automations?
Once a prompt is dialed in, you can run it automatically with workflow tools like n8n or Zapier — for example, auto-summarizing every meeting transcript into your CRM. The automation templates linked on this page show how.
Are these work prompts free?
Yes — every prompt is free to copy with no signup or paywall, and each comes with an example output so you know what it produces.