50 Prompts I Use Every Week with Claude

Turn my rough notes below into a weekly update for [AUDIENCE, team, boss, client].

My notes:
[PASTE ROUGH NOTES, BULLET POINTS, OR A BRAIN DUMP]

Structure:
- What shipped or got done (specific, not vague)
- What's in progress
- What's blocked, and what I need to unblock it
- One thing worth flagging that isn't an emergency but shouldn't get buried

Tone: direct, no filler, no "just wanted to touch base." Length: whatever it needs to be, don't pad it.

Write 5 opening lines for a cold email to [WHO YOU'RE EMAILING, role/company type], about [WHAT YOU'RE OFFERING OR ASKING FOR].

Rules:
- No "I hope this email finds you well," no "My name is," no generic compliment about their company
- Each opener should reference something specific and true about them or their situation, not something that could apply to anyone
- One sentence each
- Mark which one you'd send and why

Context on me/my offer: [ONE OR TWO SENTENCES]

Write a follow-up message to [WHO] about [WHAT, the ask, the pending decision, the thing you're waiting on].

It's been [TIMEFRAME] since I last reached out.

The message should:
- Assume good faith (they're busy, not ignoring me on purpose)
- Restate the ask in one sentence so they don't have to scroll up
- Make it easy to say no or "not yet" without friction
- Be under 60 words

Tone: [CASUAL/PROFESSIONAL].

I need to apologize to [WHO] for [WHAT WENT WRONG].

Write a message that:
- States what happened in one plain sentence, no excuses baked in
- Says what I'm doing about it (fix, refund, correction, whatever applies)
- Apologizes once, clearly, and doesn't repeat "sorry" five times
- Ends with the next concrete step, not a vague "let me know if you need anything"

Facts: [WHAT HAPPENED, WHAT YOU'RE DOING ABOUT IT]

Write a job posting for a [ROLE] at [COMPANY, ONE LINE ABOUT WHAT YOU DO].

Include:
- A 2-sentence hook that's honest about what the job actually is, not generic corporate-speak
- 5-7 real responsibilities (not copy-pasted boilerplate)
- 3-4 must-haves, separated clearly from nice-to-haves
- One sentence about who this role is NOT a fit for, so the wrong people self-select out
- Pay range if I give you one: [RANGE OR "OMIT"]

Voice: [DESCRIBE YOUR COMPANY'S VOICE IN 3 WORDS]

Rewrite the policy below so a customer or new employee can understand it in one read, no re-reading required.

Policy:
[PASTE THE POLICY OR RULE]

Rules:
- Plain language, no legal phrasing unless legally required
- Lead with what it means for them, not the rule itself
- Use a short example if it helps
- Flag anything in the original that seems unclear or contradictory, don't just smooth over it

Write a message asking [CUSTOMER NAME] for a testimonial or review.

Context: they [WHAT THEY GOT OUT OF WORKING WITH YOU, specific outcome, not "great service"].

The message should:
- Reference the specific outcome, not a generic "thanks for your business"
- Make it easy: suggest 2-3 questions they could answer instead of a blank box ("what changed for you," "what almost stopped you from working with us," "what would you tell someone considering it")
- Be short enough to read in 10 seconds
- Not sound like a template, even though it kind of is one

Below is a rough transcript of me talking through an idea. Turn it into a LinkedIn post.

Transcript:
[PASTE TRANSCRIPT OR ROUGH NOTES]

Rules:
- Keep my actual opinions and specifics, don't flatten them into generic advice
- Cut the rambling, keep the substance
- Short paragraphs, 1-3 sentences each
- No hashtags, no "Thoughts?" at the end
- End on the actual point, not a summary of the post you just wrote

Write a 100-150 word executive summary for a proposal to [CLIENT/PROJECT].

The problem they have: [PROBLEM]
What I'm proposing: [SOLUTION, ONE OR TWO SENTENCES]
Why it's worth it to them: [OUTCOME OR ROI]

Rules:
- Lead with their problem in their language, not your solution
- One sentence on what makes your approach different
- End with a plain statement of the outcome, not a question
- No "in today's competitive landscape" or similar filler

Turn the process below into a numbered standard operating procedure.

What I do (rough, in my own words): [DESCRIBE THE PROCESS, STEP BY STEP, MESSY IS FINE]

Format:
- Numbered steps, one action per step
- Note any tools or logins needed at the top
- Flag any step where judgment is required (not just a mechanical action) and explain what to consider
- End with what "done correctly" looks like, so whoever follows this can self-check

Build a 30-minute meeting agenda for [PURPOSE OF MEETING] with [WHO'S ATTENDING].

What needs to get decided or moved forward: [LIST THE OPEN ITEMS]

Structure:
- One-sentence objective at the top: what does "this meeting succeeded" mean
- Timed agenda items (minutes each) that add up to the total time
- For each item, note whether it's a decision, a discussion, or an FYI
- End with "next steps" as a placeholder to fill in live, not pre-written

Below are my unread emails (subject lines and first lines). Sort them into:
1. Needs a reply today
2. Can wait until this week
3. Can be archived or ignored
4. Needs someone else, not me

For each one in category 1, give me a one-line summary of what they actually need from me.

Emails:
[PASTE SUBJECT LINES + FIRST LINE OF EACH]

Compare these vendors for [WHAT YOU'RE BUYING]: [VENDOR A], [VENDOR B], [VENDOR C IF APPLICABLE].

What matters most to me, in order: [LIST YOUR TOP 3 CRITERIA, e.g. price, support quality, contract flexibility]

Build a table comparing them on those criteria plus anything else relevant you know about. Flag anything I should ask each vendor directly because it's not knowable from the outside. End with a recommendation and the one risk of going with your top pick.

Build a first-week onboarding checklist for a new [HIRE/CLIENT] joining [BUSINESS/ROLE CONTEXT].

Include:
- Day 1 items (accounts, access, intros)
- Week 1 items (context, expectations, first real task)
- Who owns each item (me, them, someone else, mark [OWNER UNKNOWN] where I need to fill it in)
- One thing that gets missed most often in onboarding like this, based on common failure points

Here's a list of things I do every week: [LIST YOUR RECURRING TASKS]

For each one, tell me:
1. Could this be automated with a tool I likely already have (email rules, templates, a simple Make.com/Zapier flow)? If yes, roughly how.
2. Could this be delegated?
3. Could this just stop happening with no real cost?

Be honest even if the answer for something is "keep doing it yourself, it's not worth automating yet."

I'm handing off [PROJECT/RESPONSIBILITY] to [WHO] for [TIMEFRAME/PERMANENTLY].

Build a handoff doc that covers:
- Current status in one paragraph
- Anything time-sensitive or with a deadline coming up
- Who to contact for what (list the key people and what each one owns)
- Where things live (files, logins, tools), mark [FILL IN] where I need to add specifics
- The one thing that would cause a problem if missed

Here's how [PROCESS] currently works, step by step:
[DESCRIBE THE PROCESS]

Play skeptic. Tell me:
1. Where this breaks if one step fails (which step is the single point of failure)
2. What happens if the person running this is out sick or unavailable
3. One edge case I probably haven't planned for
4. The cheapest fix for the biggest risk you found

Don't just validate the process, actively look for the failure mode.

Below are some numbers/metrics from [WHAT, sales, traffic, a report]. Turn them into a short narrative.

Numbers:
[PASTE THE DATA OR KEY FIGURES]

Structure:
1. The headline (the one thing that matters most, in plain language)
2. What's driving it, if you can tell from the data
3. What I should watch next
4. One caveat about what this data can't tell you (don't overclaim)

No jargon. Write it like you're explaining it to someone who doesn't look at spreadsheets for fun.

Here's a problem: [DESCRIBE THE PROBLEM, e.g. "response times went up," "sales dropped in March"].

Walk me through 5 whys: ask "why" about the problem, then ask why about that answer, and keep going until you hit something that's actually actionable, not just a restatement of the problem.

After the 5 whys, give me: the most likely root cause, and the one thing I could test or check this week to confirm it.

Based on what's publicly knowable, give me a snapshot of [COMPETITOR NAME] in [INDUSTRY].

Cover:
- What they seem to be doing well (be specific, not "good marketing")
- What looks weak or outdated about their approach
- One thing they're doing that I should consider, and one thing I should deliberately NOT copy
- Ask me any questions you'd need answered to give a sharper read, don't just guess and present it as fact

Below are open-text survey responses to the question: "[SURVEY QUESTION]"

Responses:
[PASTE RESPONSES]

Group them into 4-6 themes. For each theme:
- Name it in a few words
- Give the rough share of responses that fit it
- Include 1-2 representative quotes (verbatim)

End with the single theme I should act on first, and why.

I'm considering pricing [PRODUCT/SERVICE] at [PRICE].

Context:
- What it costs me to deliver (time, materials, tools): [ROUGH COST]
- What similar things sell for, if I know: [COMPARABLE PRICING OR "UNKNOWN"]
- Who the buyer is: [WHO]

Tell me: does this price make sense given the cost and the buyer? What's the strongest argument I could charge more? What's the strongest argument I'm already charging too much? Don't just agree with my number.

I'm about to start [PROJECT/DECISION]. Imagine it's 6 months from now and it failed badly.

Write the retrospective: what went wrong, in the voice of someone honestly explaining the failure after the fact. Cover 3-5 realistic failure paths, not one dramatic worst case.

Then, for the 2 most likely failure paths, tell me one thing I could do now to reduce the odds.

Here's [TIMEFRAME] of data on [METRIC, sales, leads, engagement, whatever you're tracking]:

[PASTE THE DATA]

Look for:
- Any trend (up, down, flat, cyclical)
- Any single data point that looks like an outlier, and a plausible reason why
- One question this data raises that I should investigate before drawing conclusions

Don't force a story if the data doesn't support one. It's fine to say "not enough here to conclude anything yet."

Read the contract section below and flag anything that looks unusual, one-sided, or worth asking a lawyer about. This is a first pass, not legal advice, treat it that way.

Contract text:
[PASTE THE SECTION]

For each flag: quote the relevant line, explain in plain language what it means for me, and rate how concerned I should be (low/medium/high). End with the 2-3 questions I should actually ask a lawyer, not the whole document.

A customer sent this message: "[PASTE THEIR MESSAGE]"

Context on what actually happened: [YOUR SIDE OF IT]

Draft a reply that:
- Acknowledges their frustration without agreeing to facts that aren't true
- States clearly what happened and what I'm doing about it
- Offers one concrete resolution, not a vague "we'll look into it"
- Doesn't grovel and doesn't get defensive

Brand voice: [3 ADJECTIVES]

A customer is asking for [WHAT THEY WANT] and the honest answer is no, because [REASON, policy, cost, precedent].

Draft a reply that:
- Says no clearly in the first two sentences, no burying it at the end
- Explains the reason briefly without over-justifying
- Offers an alternative if one genuinely exists (don't invent one that doesn't)
- Leaves the door open for future business

Tone: [WARM BUT FIRM / PROFESSIONAL]

Here's a [STAR RATING]-star review for [BUSINESS NAME]: "[PASTE REVIEW]"

Draft a public reply (Google/Yelp/Facebook style) that:
- Is specific to what they actually said, not a template
- If negative: acknowledges the issue, states what's being done, and offers to take it offline (email/phone)
- If positive: thanks them for something specific in the review, not just "thanks for the kind words"
- Stays under 80 words
- Never argues with the reviewer publicly, even if they're wrong

Below are real questions customers have asked us over the past [TIMEFRAME]:

[PASTE QUESTIONS, ONE PER LINE]

Group them into a clean FAQ:
- Cluster near-duplicate questions under one clear phrasing
- Write a plain-language answer for each (use my context if I give it, otherwise draft a placeholder answer and mark it [VERIFY])
- Order them by how often they seem to come up, most common first

Business context for answers: [WHAT PEOPLE NEED TO KNOW ABOUT YOUR PRODUCT/POLICIES]

[CUSTOMER NAME] hasn't [PURCHASED/BOOKED/ENGAGED] in [TIMEFRAME]. They used to be a regular.

Draft a short win-back message that:
- Doesn't guilt-trip them for leaving
- Reminds them of something specific they liked or used before, if I know it: [WHAT THEY USED TO GET FROM YOU]
- Includes one low-friction reason to come back (an update, a new offer, or just "checking in")
- Is under 60 words and doesn't read like a mass blast

Channel: [EMAIL/TEXT/DM]

[CUSTOMER NAME] recently had a good experience with [WHAT THEY GOT/DID].

Draft a short message asking for a referral that:
- Opens by referencing their specific good experience, not a generic ask
- Makes the ask concrete: "who's the first person you'd think of" is easier to answer than "know anyone who needs this?"
- Optionally mentions an incentive if I have one: [INCENTIVE OR "NONE"]
- Doesn't feel like it's only about what I get out of it

I need to tell [CUSTOMER NAME] that [WHAT WAS PROMISED] is going to take longer than expected.

Original timeline: [ORIGINAL PROMISE]
New timeline: [NEW ESTIMATE]
Reason (only if it reflects well or is simply true, don't overshare): [REASON]

Draft a proactive message (before they ask, not in response to a complaint) that states the delay plainly, gives the new timeline, and offers something to make the wait less annoying if appropriate (a discount, a status update cadence, priority next time).

[CUSTOMER NAME] is canceling/leaving after [HOW LONG THEY WERE A CUSTOMER].

Draft a short exit message that:
- Confirms the cancellation without a guilt trip or a hard-sell to stay
- Asks one honest, specific question about why (not a generic "we're sorry to see you go, any feedback?")
- Makes it easy to answer in one sentence
- Leaves the door open without begging

Tone: gracious, not desperate.

My goal for this quarter: [GOAL]

Current reality: [WHERE THINGS STAND NOW]
Constraints: [TIME, BUDGET, TEAM SIZE, ANYTHING ELSE LIMITING]

Build a quarter plan broken into 3 monthly focuses. For each month:
- The one outcome that matters most
- 3-4 concrete milestones (not vague verbs like "explore" or "improve")
- The single biggest risk to that month's plan

End with: the one thing most likely to derail this quarter, and what to watch for early.

Here's everything on my plate right now: [PASTE YOUR FULL TASK LIST, MESSY IS FINE]

Sort it into:
1. Must happen this week (max 5 items)
2. Should happen but can slip to next week
3. Doesn't actually need to be done by me, or at all

For the "must happen" list, order it by what unblocks the most other things, not just by deadline.

Here's a list of things I currently do myself: [LIST YOUR TASKS/RESPONSIBILITIES]

For each one, rate:
1. How much of my specific judgment/expertise does this actually require (high/medium/low)
2. Could this be delegated to someone with less skill/context than me, with clear instructions
3. What it would take to hand this off (a checklist, training, or just trust)

Give me the top 3 to delegate first, ranked by time saved versus effort to hand off.

I'm launching [WHAT] on [DATE/TIMEFRAME].

Build a pre-launch checklist covering:
- What needs to be true 1 week before
- What needs to be true the day before
- What needs to happen on launch day itself
- A rollback or "what if this breaks" plan, even a simple one

Ask me anything you need to know about the specifics before finalizing it, don't assume.

Here's a rough budget for [PROJECT/INITIATIVE]: [LIST LINE ITEMS AND AMOUNTS]

Expected outcome/return: [WHAT THIS IS SUPPOSED TO ACHIEVE]

Tell me:
1. Which line items look high, low, or missing based on what this kind of project usually costs
2. Whether the expected outcome justifies the spend, given what I've told you
3. One question I should be able to answer about ROI before I approve this, if I can't answer it yet

I'm considering hiring for [ROLE] because [REASON, overwhelmed, growth, a specific gap].

Before I post the job, push back on the assumption. Ask me:
1. Is this actually a capacity problem, or a process/tooling problem that a hire won't fix
2. Could this be solved with a contractor, an automation, or redistributing existing work first
3. What does success in month 3 of this hire actually look like, specifically

Then give me your honest read on whether this hire is justified based on my answers.

A new opportunity just came up: [DESCRIBE IT, a partnership, a project, a request]

Run it through a quick filter:
1. Does this move me toward [YOUR CURRENT PRIORITY/GOAL] or away from it
2. What's the realistic time cost, not the optimistic one
3. What am I saying no to if I say yes to this
4. Your honest recommendation: pursue, pass, or "ask one clarifying question first" (and what that question is)

The thing I'm most worried could go wrong with [PROJECT/SITUATION] is: [YOUR BIGGEST WORRY]

Build a simple contingency plan:
- The earliest warning sign that this is starting to happen
- The first action to take if it does
- Who needs to know, and how fast
- What "back to normal" looks like

Keep it short enough that I'd actually follow it under stress, not a 10-page document.

Here's my offer as I currently describe it: [PASTE YOUR CURRENT PITCH/DESCRIPTION]

Tell me:
1. What problem does this actually solve, in one plain sentence (not features, the underlying problem)
2. Who has that problem badly enough to pay for it
3. What's confusing or vague in my current description that a stranger wouldn't understand
4. Rewrite it in one sentence a 12-year-old could repeat back accurately

Write 10 headline options for a landing page selling [PRODUCT/SERVICE] to [AUDIENCE].

The core benefit: [WHAT THEY GET]
What makes this different from alternatives: [YOUR DIFFERENTIATOR]

Mix of angles: 3 benefit-led, 3 curiosity-led, 2 that name the problem directly, 2 that use a specific number or timeframe. Mark your top 2 picks and explain why.

Write 8 subject line options for an email about [WHAT THE EMAIL IS ABOUT].

Constraints:
- Under 50 characters where possible
- No clickbait, no "you won't believe," nothing the email itself doesn't deliver on
- At least 2 should feel like a personal note, not a campaign
- Mark the one you'd actually send

Turn the notes below into a short case study.

Client/situation: [WHO, WHAT THEY DO]
Problem before: [WHAT WASN'T WORKING]
What we did: [WHAT YOU DELIVERED]
Result: [OUTCOME, WITH NUMBERS IF YOU HAVE THEM]

Structure: problem, approach, result, one direct quote (write a plausible placeholder quote marked [VERIFY WITH CLIENT] if I don't have a real one). Keep it under 300 words. No fluff about "partnership" or "journey."

Write 6 ad copy variations for [PLATFORM, Facebook/Instagram/Google] promoting [OFFER].

Audience: [WHO]
Core message: [WHAT YOU WANT THEM TO KNOW/FEEL]

Vary these dimensions across the 6: emotional vs. rational appeal, short vs. slightly longer copy, and question-led vs. statement-led. Include a CTA for each. Note which pairing you'd test against which, and why.

The objection I hear most often is: "[OBJECTION, IN THEIR WORDS]"

Write a response that:
- Acknowledges the concern as legitimate, doesn't dismiss it
- Reframes with a specific fact, example, or comparison (not just reassurance)
- Ends with a question that moves the conversation forward, not a hard close

Give me 2 versions: one for a written follow-up (email/DM) and one for saying out loud on a call.

Below are reviews/testimonials I've collected: [PASTE REVIEWS OR TESTIMONIALS]

Pull out the 5 strongest lines for marketing use. Prioritize lines that are specific (a number, a before/after, a concrete outcome) over generic praise like "great service." For each one, suggest where it would work best (homepage, landing page, social post, sales deck).

I need campaign ideas for [SEASON/HOLIDAY/EVENT] for [BUSINESS TYPE].

Generate 8 angles. Constraints:
- No generic "[Holiday] Sale!" ideas, I can think of those myself
- At least half should tie the season to a real customer need or moment, not just the calendar date
- Mark the top 2 you'd actually run and why

What I sell: [PRODUCT/SERVICE]

My brand voice is: [3-5 ADJECTIVES, e.g. "direct, warm, no corporate-speak"]

Here's a piece of copy I wrote: [PASTE COPY]

Check it against the voice. Flag any lines that sound off-brand (too corporate, too stiff, too different in tone from the rest) and suggest a specific rewrite for each flagged line. Don't rewrite the whole thing, just the parts that don't sound like me.