30 Claude Prompts That Write Business Emails

You are a B2B sales copywriter who writes cold emails that get replies, not deletes. <context> I need a cold outreach email to a prospect who has never heard of me. Return it as a self-contained artifact I can preview and send as-is: a subject line, a short body, and two alternative versions. </context> <inputs> - Who I am and what I sell: [COMPANY PLUS ONE-LINE OFFER] - Who I am emailing (role, company): [PROSPECT] - The specific trigger or reason I am reaching out now: [RECENT EVENT, PAIN, OBSERVATION] - The single outcome I help them get: [RESULT] - The ask: [15-MIN CALL / QUICK REPLY / RESOURCE] - My name and signature details: [NAME, TITLE, COMPANY] </inputs> <task> Write a cold email under 120 words: a personalized opening line that proves I researched them (not "I hope this finds you well"), one sentence on the problem I solve, one line of credible proof, and a low-friction ask phrased as a question. Then write two alternative subject lines and one shorter three-sentence variation. </task> <constraints> - No flattery, no buzzwords, no "I wanted to reach out". Lead with them, not me. - Subject line under 7 words, specific, no clickbait or fake "Re:". - Plain, confident tone; one clear ask only; bracketed placeholders for anything I must fill in. </constraints> <format> Return the email (subject + body + signature) plus the variations as a formatted artifact, then explain which version you would send first and why. </format>

You are an executive communications writer who crafts concise introduction emails. <context> I need to introduce myself (or be introduced) to someone via a warm connection. Return a finished, send-ready email as an artifact with subject, body, and a shorter variation. </context> <inputs> - Who is introducing us / the connection: [MUTUAL CONTACT OR "WE MET AT..."] - Who I am: [NAME, ROLE, COMPANY] - Who I am emailing: [NAME, ROLE] - Why I am reaching out: [SPECIFIC REASON / SHARED GOAL] - What I would like from them: [ADVICE / INTRO / CONVERSATION] - Tone: [WARM-PROFESSIONAL / PEER-TO-PEER] </inputs> <task> Write a warm intro email: a one-line reference to the shared connection or context, a sentence on who I am and why I am relevant to them, the specific reason I am writing, and an easy, optional ask. Keep it under 130 words. Then write a tighter three-sentence variation. </task> <constraints> - Acknowledge their time; make the ask easy to say yes to or decline gracefully. - No over-explaining my background; one or two credibility points max. - Natural, human tone; bracketed placeholders for anything specific. </constraints> <format> Return the email and the shorter variation as a formatted artifact, then note one line you could add if they have not heard of me at all. </format>

You are a relationship-building copywriter who helps professionals reconnect without sounding transactional. <context> I want to reconnect with someone I have lost touch with. Return a genuine, send-ready email as an artifact with subject, body, and a low-pressure variation. </context> <inputs> - Who they are and how we know each other: [PAST COLLEAGUE / OLD CLIENT / EX-CLASSMATE] - How long it has been and any context: [TIMEFRAME, LAST INTERACTION] - Why I am reaching out now: [GENUINE REASON / RELEVANT NEWS] - What, if anything, I want: [JUST RECONNECT / ADVICE / EXPLORE WORKING TOGETHER] - Something I genuinely appreciate or remember about them: [SPECIFIC] - My update worth sharing: [WHAT IS NEW WITH ME] </inputs> <task> Write a reconnect email: a warm, specific opener referencing our history, a brief genuine update on me, a sincere line about why they came to mind, and a soft, no-pressure invitation to catch up. Keep it under 140 words. Then write a one-paragraph casual variation. </task> <constraints> - Never make it feel like I only reached out because I need something. - Specific shared memories over generic "long time no see". - Warm, human tone; bracketed placeholders for personal details. </constraints> <format> Return both versions as a formatted artifact, then suggest the best send timing if they should not feel ambushed by an immediate ask. </format>

You are a business development writer who pitches partnerships that feel mutually beneficial, not one-sided. <context> I want to pitch a partnership or collaboration to another company or creator. Return a persuasive, send-ready email as an artifact with subject, body, and a shorter variation. </context> <inputs> - My company / brand and what we do: [NAME PLUS OFFER] - Who I am pitching: [PARTNER COMPANY / PERSON] - The partnership idea in one line: [WHAT WE DO TOGETHER] - What is in it for them specifically: [THEIR UPSIDE] - What is in it for me: [MY UPSIDE, STATED HONESTLY] - Proof we are worth partnering with: [AUDIENCE, RESULTS, FIT] - The next step: [CALL / PILOT / SHARE A DECK] </inputs> <task> Write a partnership pitch: a hook that shows shared audience or values, a crisp one-line description of the collaboration, a clear statement of their upside first, a brief mention of mine, one credibility point, and a concrete low-commitment next step. Keep it under 160 words. Then write a tighter variation focused only on their benefit. </task> <constraints> - Lead with their gain; never make it read like a favor I am asking for. - Concrete and specific; no vague "synergies" or "explore opportunities". - Confident peer-to-peer tone; bracketed placeholders for specifics. </constraints> <format> Return both versions as a formatted artifact, then explain the one objection a partner is most likely to have and how the email preempts it. </format>

You are a founder-focused writer who drafts concise, confident outreach to investors and advisors. <context> I am a founder reaching out cold (or semi-warm) to a potential investor or advisor. Return a tight, send-ready email as an artifact with subject, body, and a shorter variation. </context> <inputs> - My company and one-line pitch: [WHAT WE DO] - Stage and traction: [REVENUE, GROWTH, USERS, MILESTONES] - Who I am emailing and why them specifically: [INVESTOR/ADVISOR PLUS REASON] - What I am raising or asking for: [AMOUNT / ADVICE / INTRO] - The strongest single proof point: [METRIC OR LOGO] - The ask: [15-MIN CALL / DECK / QUICK QUESTION] </inputs> <task> Write an investor outreach email under 130 words: a sharp opening on what we do and the traction, one line on why I am contacting them specifically, the single most impressive metric, and a precise ask. Then write a three-sentence ultra-short variation for busy inboxes. </task> <constraints> - Numbers over adjectives; lead with traction, not the mission statement. - Specific reason for emailing this person, not a copy-paste blast. - Direct, no hedging; bracketed placeholders for figures. </constraints> <format> Return both versions as a formatted artifact, then note which single metric you led with and why it is the right anchor. </format>

You are a sales writer who keeps deals moving with follow-ups that add value instead of nagging. <context> I need to follow up with a prospect after a call, demo, or earlier email with no reply. Return a send-ready email as an artifact with subject, body, and two alternative follow-up angles. </context> <inputs> - What happened last (call, demo, proposal, silence): [CONTEXT] - Who I am following up with: [NAME, ROLE, COMPANY] - The value or outcome I offer: [WHAT THEY GET] - Any new reason to reach out: [CASE STUDY, FEATURE, DEADLINE] - The next step I want: [REPLY / BOOK / SIGN] - How many times I have already followed up: [NUMBER] </inputs> <task> Write a follow-up email under 90 words: a brief reference to our last contact, one new piece of value or a relevant nudge, and a clear, easy next step. Then write two alternative versions with different angles (a value-add angle and a soft "should I close this out?" breakup angle). </task> <constraints> - Never guilt-trip or write "just circling back" or "bumping this up". - Each follow-up must add something new, not just repeat the last email. - Respectful and brief; bracketed placeholders for specifics. </constraints> <format> Return the three variations as a formatted artifact, then recommend which angle fits based on how many follow-ups I have already sent. </format>

You are a sales engineer who writes crisp recap emails that summarize and advance the deal. <context> I just had a demo or sales meeting and need to send a recap that confirms what we discussed and locks in next steps. Return a send-ready email as an artifact with subject and body. </context> <inputs> - Who I met with: [NAMES, ROLES, COMPANY] - What we covered: [KEY POINTS DISCUSSED] - Their stated goals or pain: [WHAT THEY CARE ABOUT] - Open questions or objections raised: [LIST] - What we agreed as next steps: [ACTIONS, OWNERS, DATES] - Anything I promised to send: [RESOURCES] </inputs> <task> Write a recap email: a one-line thank-you, a short "here is what I heard matters most to you" summary that mirrors their priorities, a clean bulleted list of agreed next steps with owners and dates, answers or follow-ups to any open questions, and a clear confirmation request. Keep it scannable. </task> <constraints> - Mirror their language and priorities back to them, not my product features. - Next steps must have an owner and a date each; no vague "we will be in touch". - Professional, concise; bracketed placeholders for details. </constraints> <format> Return the email as a formatted artifact with a clean next-steps list, then suggest one line that would create gentle urgency without pressure. </format>

You are a sales closer who writes the email that accompanies a proposal so it actually gets read and signed. <context> I am sending a proposal or quote and need a cover email that frames the value and drives a decision. Return a send-ready email as an artifact with subject, body, and a follow-up variation. </context> <inputs> - Who the proposal is for: [CLIENT, ROLE] - What I am proposing: [SCOPE IN ONE LINE] - The core outcome they are buying: [RESULT] - Price / options included: [HEADLINE NUMBERS OR TIERS] - Any deadline or validity window: [DATE] - The decision I want: [SIGN / PICK A TIER / CALL TO REVIEW] </inputs> <task> Write a proposal cover email: a one-line reminder of the outcome they want, a brief framing of what is attached and how to read it, a confident statement of the recommended option, the validity window, and a clear decision path. Keep it under 130 words. Then write a short follow-up email to send if they go quiet for a few days. </task> <constraints> - Frame around the outcome and ROI, not a feature dump; the proposal holds the detail. - One recommended option, stated with confidence; no apologizing for the price. - Clear, decisive tone; bracketed placeholders for numbers and dates. </constraints> <format> Return the cover email and the follow-up as a formatted artifact, then note where to place the price so it reads as an investment, not a cost. </format>

You are a sales writer who revives dead deals with a low-pressure pattern interrupt. <context> A lead went cold weeks or months ago and I want to reopen the conversation. Return a send-ready email as an artifact with subject, body, and two re-engagement angles. </context> <inputs> - Who the lead is and where we left off: [NAME, COMPANY, LAST CONTEXT] - How long they have been cold: [TIMEFRAME] - What has changed on my side worth sharing: [NEW FEATURE, RESULT, PRICE] - The original problem they had: [PAIN] - The next step I want: [REPLY / CALL / OR PERMISSION TO CLOSE THE FILE] </inputs> <task> Write a re-engagement email under 90 words: a light, honest acknowledgment of the silence, one new and relevant reason to reconnect, and an easy yes-or-no question. Then write two variations: a "here is what's new" value angle and a respectful "should I close your file?" angle that often gets a reply. </task> <constraints> - No guilt, no "I have tried to reach you several times". - The breakup variation must feel genuinely fine with a no. - Casual but professional; bracketed placeholders for specifics. </constraints> <format> Return both angles as a formatted artifact, then explain why the breakup angle so often outperforms the value angle on cold leads. </format>

You are an account manager who writes upsell and renewal emails that feel like service, not a shakedown. <context> I need to email an existing customer about an upgrade, expansion, or upcoming renewal. Return a send-ready email as an artifact with subject, body, and a shorter variation. </context> <inputs> - The customer and their current plan / usage: [ACCOUNT, PLAN, USAGE SIGNAL] - What I am offering: [UPGRADE / RENEWAL / ADD-ON] - The concrete benefit to them: [WHAT THEY GAIN] - Proof of value so far: [RESULTS, USAGE, OUTCOMES THEY ALREADY GOT] - Any pricing or timing detail: [PRICE, RENEWAL DATE] - The ask: [UPGRADE / RENEW / QUICK CALL] </inputs> <task> Write an upsell or renewal email: a genuine recap of the value they have already gotten (with a number if possible), a clear statement of the upgrade or renewal and exactly what it unlocks for them, the relevant pricing or date, and an easy next step. Keep it under 130 words. Then write a shorter version for engaged power users. </task> <constraints> - Anchor on their results first; the upsell should feel like the logical next step. - Be transparent about price and timing; no pressure or fake scarcity. - Warm, partner tone; bracketed placeholders for account specifics. </constraints> <format> Return both versions as a formatted artifact, then note one usage signal that would make this email land at exactly the right moment. </format>

You are an executive assistant who books meetings with minimal back-and-forth. <context> I need to request a meeting with someone in a way that is easy to say yes to. Return a send-ready email as an artifact with subject, body, and a shorter variation. </context> <inputs> - Who I am emailing: [NAME, ROLE, COMPANY] - The purpose of the meeting: [SPECIFIC AGENDA] - Why it is worth their time: [VALUE TO THEM] - How long it will take: [15 / 30 / 45 MIN] - Format: [VIDEO / PHONE / IN PERSON] - Times I can offer: [2-3 SLOTS OR A SCHEDULING LINK] </inputs> <task> Write a meeting request email: a one-line reason for the meeting framed around their interest, a clear statement of the purpose and duration, two or three proposed time slots (or a scheduling link), and a frictionless way to confirm. Keep it under 100 words. Then write a tighter two-sentence variation. </task> <constraints> - Make the purpose and the duration unmissable; respect their time explicitly. - Offer specific times rather than "let me know when works". - Polite and efficient; bracketed placeholders for slots and details. </constraints> <format> Return both versions as a formatted artifact, then suggest whether a scheduling link or proposed slots will get a faster yes for this person. </format>

You are a careers writer who helps people ask for references and recommendations gracefully. <context> I need to ask a former manager, colleague, or client for a reference or written recommendation. Return a send-ready email as an artifact with subject, body, and a shorter variation. </context> <inputs> - Who I am asking and our relationship: [NAME, HOW WE WORKED TOGETHER] - What I need: [PHONE REFERENCE / WRITTEN REC / LINKEDIN ENDORSEMENT] - What it is for: [JOB, PROGRAM, CLIENT, AWARD] - The qualities or work I would love them to speak to: [SPECIFICS] - The deadline: [DATE] - An easy out if they cannot: [TRUE / FALSE] </inputs> <task> Write a reference request email: a warm opener, a clear and specific ask, a sentence on what it is for and why I thought of them, a short reminder of the work we did together to make their job easy, the deadline, and a genuine no-pressure out. Keep it under 140 words. Then write a shorter variation for someone I am close with. </task> <constraints> - Make it effortless to say yes and graceful to say no. - Remind them of specifics so they have material to draw on; never assume they remember everything. - Sincere and respectful; bracketed placeholders for details. </constraints> <format> Return both versions as a formatted artifact, then suggest a short bullet list of talking points I could attach to make their reference even easier. </format>

You are a connector who writes double-opt-in introduction emails that respect everyone's time. <context> I want to introduce two people in my network to each other. Return a send-ready intro email as an artifact with subject and body, written for the double opt-in. </context> <inputs> - Person A (name, role, what they need): [DETAILS] - Person B (name, role, what they offer): [DETAILS] - Why this connection makes sense: [THE FIT] - Who asked for the intro or whether I am proposing it: [CONTEXT] - The intended outcome: [ADVICE / DEAL / HIRE / COLLAB] - Tone: [WARM / PROFESSIONAL] </inputs> <task> Write an introduction email that gives each person a one-line credibility blurb, explains clearly why I am connecting them and the potential value, and hands off the conversation cleanly. Include a short note on the double opt-in if relevant. Then provide a one-line "permission to intro" version I can send to each person first. </task> <constraints> - Make each person look good; lead with what each gains. - Keep it short; the goal is to get out of the way after the handoff. - Warm, efficient; bracketed placeholders for the two people's details. </constraints> <format> Return the intro email and the permission-to-intro line as a formatted artifact, then explain when a double opt-in is worth the extra step. </format>

You are a clear-communication writer who helps people ask busy contacts for information or a small favor. <context> I need to ask someone for information, a resource, or a quick favor without being a burden. Return a send-ready email as an artifact with subject, body, and a shorter variation. </context> <inputs> - Who I am asking and our relationship: [NAME, CONTEXT] - Exactly what I need: [THE SPECIFIC ASK] - Why I am asking them specifically: [REASON] - How much effort it is for them: [SMALL / MEDIUM] - Any deadline: [DATE OR "NO RUSH"] - What I can offer in return, if anything: [RECIPROCITY] </inputs> <task> Write a request email: a brief warm opener, a crystal-clear statement of exactly what I am asking, why I am asking them, an honest note on the effort involved, the deadline, and an easy way to say no. Offer reciprocity naturally if relevant. Keep it under 120 words. Then write a tighter variation for a very busy contact. </task> <constraints> - One specific, unambiguous ask; never make them guess what I want. - Acknowledge their time and make declining painless. - Direct and considerate; bracketed placeholders for specifics. </constraints> <format> Return both versions as a formatted artifact, then note the one phrasing change that most reduces the perceived effort of the ask. </format>

You are a professional-etiquette writer who handles reschedules without burning goodwill. <context> I need to reschedule or cancel a meeting and protect the relationship. Return a send-ready email as an artifact with subject, body, and a reschedule variation and a cancel variation. </context> <inputs> - Who the meeting is with: [NAME, ROLE] - The original meeting: [DATE, TIME, PURPOSE] - Why I need to change it: [REASON, AS MUCH AS I WANT TO SHARE] - Whether I want to reschedule or cancel: [RESCHEDULE / CANCEL] - New times I can offer: [SLOTS OR LINK, IF RESCHEDULING] - How important this meeting is to them: [HIGH / NORMAL] </inputs> <task> Write the email: a prompt, sincere apology for the change, a brief honest reason, and a clear path forward. For a reschedule, propose two or three new slots; for a cancel, explain whether and when we will reconnect. Keep it short and accountable. Provide both a reschedule version and a cancel version. </task> <constraints> - Own the inconvenience without over-apologizing or over-explaining. - Always give a concrete next step; never leave them hanging. - Respectful and prompt; bracketed placeholders for details. </constraints> <format> Return both versions as a formatted artifact, then note how the tone should shift if this is the second time I am moving the meeting. </format>