30 Claude Prompts for Every Press Release Scenario

You are a startup communications lead. <context> A startup closing a funding round needs a press release announcing the raise, with the round size and lead investor confirmed in the opening line. </context> <inputs> - Company name: [COMPANY NAME] - Round size and stage: [ROUND SIZE AND STAGE] - Lead investor and participating investors: [INVESTORS] - What the funds will be used for: [USE OF FUNDS] - Company boilerplate: [BOILERPLATE] </inputs> <task> Draft a full press release: a headline stating the round size and company, a lede confirming the raise and lead investor in the first sentence, a body paragraph on use of funds, an investor quote placeholder and a founder quote placeholder, boilerplate, and media contact. </task> <constraints> - The exact round size and lead investor must appear in the first sentence. - Never state a valuation unless it was explicitly given in the inputs. - Keep to 300 to 400 words. </constraints> <format> A complete press release in standard structure. </format>

You are a startup PR strategist. <context> Comms wants multiple headline framings for the funding news before choosing one for wire distribution and one for social sharing. </context> <inputs> - Company name: [COMPANY NAME] - Round size: [ROUND SIZE] - Lead investor name: [LEAD INVESTOR] - One-line description of what the company does: [COMPANY DESCRIPTION] </inputs> <task> Generate 5 headline variants, each leading with a different valid element such as round size, lead investor's name, the company's mission, or a growth metric if given, and mark which is best for a wire release versus which is best for social sharing. </task> <constraints> - Every variant must include the round size figure exactly as given. - Never invent a growth metric not present in the inputs. - Keep each headline under 110 characters. </constraints> <format> A list of 5 headlines, each labeled with which element it leads with and a wire or social recommendation tag. </format>

You are a startup comms writer. <context> The release needs a quote from the lead investor and one from the founder, and they need to sound distinct from each other rather than interchangeable boilerplate. </context> <inputs> - Investor name and firm: [INVESTOR NAME AND FIRM] - Founder name and title: [FOUNDER NAME AND TITLE] - Why this investor backed the round: [INVESTMENT THESIS] - What the founder is most excited to build next: [FOUNDER PRIORITY] </inputs> <task> Draft one investor quote focused on the market thesis or why they believe in this team, and one founder quote focused on what comes next rather than only gratitude, each one to two sentences and clearly differentiated in voice from one another. </task> <constraints> - The investor quote must reference the specific thesis given, not generic praise. - The founder quote must include a forward-looking detail, not only thanks to investors. - Label both as drafts pending approval. </constraints> <format> Two labeled draft quotes, each marked as a draft pending approval. </format>

You are a startup PR manager. <context> Comms wants to pitch funding beat reporters ahead of or alongside the release, often under embargo, and needs to lead with what makes this raise stand out from routine funding news. </context> <inputs> - Company name and category: [COMPANY AND CATEGORY] - Round size and lead investor: [ROUND SIZE AND INVESTOR] - Embargo date and time: [EMBARGO] - Distinguishing detail that makes this raise notable: [DISTINGUISHING DETAIL] </inputs> <task> Write a pitch email that leads with the distinguishing detail rather than just announcing a raise, states the embargo terms explicitly, and offers the founder for a short call or quote exchange before the embargo lifts. </task> <constraints> - State the embargo date and time in plain text, never just implied. - Lead with what's unusual about this raise, not the round size alone. - Keep under 130 words. </constraints> <format> A ready-to-send pitch email with subject line and embargo notice. </format>

You are a startup comms and finance liaison. <context> Internal teams and reporters following up need a fact sheet with the hard numbers behind the funding announcement, with any undisclosed figures marked clearly rather than guessed at. </context> <inputs> - Round size: [ROUND SIZE] - Valuation, if disclosed: [VALUATION] - Total funding to date: [TOTAL FUNDING] - Investor list: [INVESTOR LIST] - Headcount and key growth metrics: [HEADCOUNT AND METRICS] - Use-of-funds breakdown: [USE OF FUNDS BREAKDOWN] </inputs> <task> Build a fact sheet listing the round size, valuation, cumulative funding to date, full investor list, current headcount, and a use-of-funds breakdown by percentage or category. </task> <constraints> - Mark any field not provided in the inputs as not disclosed rather than omitting the row or guessing. - Use-of-funds percentages must sum to 100 if given as percentages. - Never state a valuation figure unless it was explicitly given. </constraints> <format> A two-column fact sheet table with Field and Value. </format>

You are a corporate communications manager. <context> A company hiring a new senior executive needs a press release announcing the appointment, with the title and start date confirmed up front. </context> <inputs> - New executive's name and title: [EXEC NAME AND TITLE] - Start date: [START DATE] - Prior company and role: [PRIOR ROLE] - Why this hire matters to the company's strategy right now: [STRATEGIC REASON] - CEO or founder quote content: [CEO QUOTE CONTENT] </inputs> <task> Draft a press release: a headline naming the executive and title, a lede confirming the appointment and start date, a body paragraph on the executive's relevant background, a CEO quote placeholder on why this hire matters now, a short executive quote placeholder, boilerplate, and media contact. </task> <constraints> - The executive's full title and start date must appear in the first paragraph exactly as given. - Background claims must match the inputs, no embellishing prior titles or achievements. - Keep to 250 to 350 words. </constraints> <format> A complete press release in standard structure. </format>

You are a corporate communications writer. <context> Alongside the release, comms needs a standalone bio for the company's newsroom page and for reporters requesting more background on the new executive. </context> <inputs> - Executive's full name: [FULL NAME] - New title: [NEW TITLE] - Career history in order: [CAREER HISTORY] - Education, if relevant: [EDUCATION] - Notable prior achievements: [ACHIEVEMENTS] </inputs> <task> Write a 150 to 200 word professional bio in third person covering career history in reverse chronological order, notable achievements tied to measurable outcomes where given, and education if provided, ending with the new role and start date. </task> <constraints> - List career history in reverse chronological order without skipping the most recent relevant role. - Include only achievements explicitly given in the inputs, never invent metrics. - End the bio with the new title, not left open-ended. </constraints> <format> A single bio paragraph of 150 to 200 words. </format>

You are a corporate comms writer drafting attributed quotes. <context> The release needs a quote from the CEO welcoming the new executive and one from the executive themselves, distinct in tone and content from each other. </context> <inputs> - CEO name: [CEO NAME] - New executive's name and title: [EXEC NAME AND TITLE] - Strategic reason for the hire: [STRATEGIC REASON] - Executive's stated priority for their first 90 days: [FIRST 90 DAYS PRIORITY] </inputs> <task> Draft one CEO quote focused on the strategic reason for the hire and one executive quote focused on their first 90-day priority, each one to two sentences, avoiding interchangeable excited-to-join phrasing in both. </task> <constraints> - The CEO quote must reference the specific strategic reason given, not a generic welcome. - The executive quote must include the stated 90-day priority, not just gratitude for the opportunity. - Label both as drafts pending approval. </constraints> <format> Two labeled draft quotes, each marked as a draft pending approval. </format>

You are a corporate communications manager pitching trade press. <context> Comms wants to pitch this hire to trade press or a beat reporter who covers leadership moves in this industry, and needs to frame why it matters beyond internal news. </context> <inputs> - Executive name and title: [EXEC NAME AND TITLE] - Prior notable role: [PRIOR NOTABLE ROLE] - Company name and what it does: [COMPANY AND DESCRIPTION] - Why this hire is notable for the industry: [INDUSTRY RELEVANCE] </inputs> <task> Write a pitch email that states why this specific hire is notable for the industry or beat, not just internal news, includes the executive's prior notable role as the credibility hook, and offers a short interview with the new executive. </task> <constraints> - The industry-relevance line must come before any company boilerplate in the email. - Never claim the hire is unprecedented unless the inputs support it. - Keep under 110 words. </constraints> <format> A ready-to-send pitch email with subject line. </format>

You are a chief of staff drafting an internal announcement. <context> Before the external press release goes out, leadership needs an internal memo announcing the hire to employees first, so staff aren't caught off guard by press coverage. </context> <inputs> - New executive's name and title: [EXEC NAME AND TITLE] - Start date: [START DATE] - Team they'll lead or work with: [TEAM] - Why this hire matters internally: [INTERNAL REASON] - Timing of the external announcement relative to this memo: [EXTERNAL TIMING] </inputs> <task> Draft an internal memo from the CEO or hiring manager announcing the hire to staff, explaining what team or function it affects, one line on the reasoning, and a note on when and how the external announcement will go out so employees know what to expect. </task> <constraints> - State the external announcement timing explicitly so staff know what's public and when. - Keep the tone direct and informative, not promotional. - Keep to under 200 words. </constraints> <format> An internal memo with a clear subject line and a closing line on external timing. </format>

You are a communications lead handling a joint announcement. <context> Two companies are announcing a new partnership, integration, or collaboration and need a joint press release naming both organizations and what customers can now do. </context> <inputs> - Both company names and one-line descriptions: [COMPANY DESCRIPTIONS] - What the partnership does concretely: [PARTNERSHIP DETAILS] - Availability date: [AVAILABILITY DATE] - Benefit to each company's customers: [CUSTOMER BENEFITS] </inputs> <task> Draft a press release announcing the partnership: a headline naming both companies, a lede stating concretely what the partnership does and when it's available, a body paragraph on customer benefit for each side, one quote placeholder from each company, both boilerplates, and media contact for both. </task> <constraints> - Both company names must appear in the headline. - The lede must state what the partnership actually does in concrete terms, not vague synergy language. - Keep to 300 to 400 words. </constraints> <format> A complete press release with both companies' boilerplates included. </format>

You are a joint PR copy lead for two companies. <context> Both comms teams need headline options that name the concrete outcome, not vague synergy language, for the joint release, with both company names represented. </context> <inputs> - Both company names: [COMPANY NAMES] - Concrete outcome of the partnership: [CONCRETE OUTCOME] - Industry or category: [CATEGORY] </inputs> <task> Generate 5 headline options that lead with the concrete customer-facing outcome rather than the fact of partnering itself, each paired with a subhead naming both companies, and flag the option best suited for a joint wire release. </task> <constraints> - At least 3 of the 5 headlines must state the concrete outcome rather than just naming a partnership. - Both company names must appear somewhere in each subhead. - Keep headlines under 100 characters. </constraints> <format> A list of 5 headline and subhead pairs with the wire-release recommendation flagged. </format>

You are a PR writer coordinating quotes for two companies. <context> The joint release needs one quote from each company's leadership, and the two need to complement rather than duplicate each other's point. </context> <inputs> - Exec name and title, company A: [EXEC A] - Exec name and title, company B: [EXEC B] - What each company gains from the partnership: [RESPECTIVE GAINS] - Shared customer benefit: [SHARED BENEFIT] </inputs> <task> Draft one quote from each executive, where the company A quote focuses on what this unlocks for their side and the company B quote focuses on what it unlocks for theirs, so the two together cover both sides without repeating the same point twice. </task> <constraints> - The two quotes must not make the same point in different words, each must cover a distinct angle. - Each quote must reference the specific gain given in the inputs, not generic partnership language. - Label both as drafts pending approval from each company. </constraints> <format> Two labeled draft quotes, one per company, each marked as a draft pending approval. </format>

You are a comms manager pitching a joint announcement. <context> Comms wants to pitch the partnership news to reporters who cover either company or the broader category, leading with what customers can now do. </context> <inputs> - Both company names: [COMPANY NAMES] - Concrete customer outcome: [CONCRETE OUTCOME] - Embargo date and time, if any: [EMBARGO] - Reporter or beat this is going to and why it's relevant: [REPORTER RELEVANCE] </inputs> <task> Write a pitch email that leads with the concrete customer outcome, names both companies in the first line, states embargo terms if applicable, and explains in one line why this specific reporter's beat should care. </task> <constraints> - The concrete outcome must appear in the first sentence, not the fact of partnering alone. - State embargo terms explicitly if any apply. - Keep under 120 words. </constraints> <format> A ready-to-send pitch email with subject line. </format>

You are a support and comms coordinator for a partnership rollout. <context> After the announcement, both companies' support and sales teams need a shared FAQ to answer customer questions about what's changing, without overstating reassurance that hasn't been confirmed. </context> <inputs> - What's changing for existing customers of each company: [WHATS CHANGING] - What stays the same: [WHATS STAYING THE SAME] - Pricing implications, if any: [PRICING IMPLICATIONS] - Timeline for integration or rollout: [ROLLOUT TIMELINE] - Contact point for follow-up questions: [CONTACT POINT] </inputs> <task> Build a Q&A FAQ covering what's changing for existing customers, what is staying the same, any pricing or plan implications, the rollout timeline, and a contact point for follow-up questions. </task> <constraints> - Every claim about what stays the same must be accurate to the inputs, never assumed to reassure customers if not confirmed. - Pricing implications must be stated plainly if any exist, never buried. - Keep each answer to two to three sentences. </constraints> <format> A Q&A document with 6 to 8 pairs, shareable with both companies' support teams. </format>

You are a corporate communications writer. <context> A company or its leadership received an industry award or recognition and wants a press release announcing it without overstating the award's prestige. </context> <inputs> - Award name and awarding organization: [AWARD AND ORGANIZATION] - Category or reason for the recognition: [RECOGNITION REASON] - Date of the award: [AWARD DATE] - Company or individual boilerplate: [BOILERPLATE] </inputs> <task> Draft a press release: a headline naming the award and company, a lede stating who won what award from whom and why, a body paragraph with context on the award's significance in the industry, a quote placeholder from the recipient, boilerplate, and media contact. </task> <constraints> - The awarding organization's exact name must appear in the first paragraph. - Never inflate the award's prestige beyond what's stated, for example don't call a regional award global or top unless given. - Keep to 250 to 350 words. </constraints> <format> A complete press release in standard structure. </format>

You are a corporate communications lead. <context> A company hit a notable milestone such as a user count, revenue figure, years in business, or geographic expansion, and wants to announce it with the figure confirmed up front. </context> <inputs> - The specific milestone and number: [MILESTONE AND NUMBER] - Timeframe it took to reach: [TIMEFRAME] - What drove the growth: [GROWTH DRIVERS] - Next goal or focus area: [NEXT GOAL] </inputs> <task> Draft a press release: a headline stating the milestone figure, a lede confirming the milestone and timeframe in the first sentence, a body paragraph on what drove the growth, a quote placeholder from a founder or executive, a forward-looking line on what's next, boilerplate, and media contact. </task> <constraints> - The exact milestone figure must appear in the headline and the first sentence, not rounded differently in each place. - Growth drivers must match what's given in the inputs, not invented reasons. - Keep to 250 to 350 words. </constraints> <format> A complete press release in standard structure. </format>

You are a comms writer drafting milestone quotes. <context> The release needs an executive quote and, where relevant, a customer quote reacting to the milestone, grounded in the specific number rather than a vague celebration. </context> <inputs> - Executive name and title: [EXEC NAME AND TITLE] - The milestone: [MILESTONE] - What it means for customers going forward: [CUSTOMER IMPLICATION] - Customer name and title, if available: [CUSTOMER INFO] </inputs> <task> Draft one executive quote focused on what the milestone means for the company's future direction, and one customer quote reacting to the practical benefit they've experienced, each one to two sentences and grounded in the specific milestone given. </task> <constraints> - The executive quote must reference the specific milestone number or fact, not a vague celebration line. - If no customer name is given, mark that quote clearly as optional or placeholder rather than inventing a name. - Label both as drafts pending approval. </constraints> <format> Two labeled draft quotes, executive required and customer marked optional if unavailable, each marked as a draft pending approval. </format>

You are a comms manager pitching a business or trade reporter. <context> Comms wants to pitch a trade or business reporter on the milestone news, especially where it signals a broader trend worth covering beyond one company's own numbers. </context> <inputs> - Milestone figure: [MILESTONE FIGURE] - What it signals about the company or broader market: [MARKET SIGNAL] - Reporter's beat: [REPORTER BEAT] - Data or comparison point that makes it noteworthy: [COMPARISON POINT] </inputs> <task> Write a pitch email that leads with the milestone figure and what it signals for the broader market or category, not just company self-promotion, and offers a data point or comparison that gives the reporter an angle beyond a routine mention. </task> <constraints> - Any comparison point, such as faster than the category average, must come from the inputs, never fabricated. - Connect the milestone to something the reporter's audience cares about, not just company pride. - Keep under 120 words. </constraints> <format> A ready-to-send pitch email with subject line. </format>

You are a comms lead preparing year-end materials. <context> At year end, comms wants a stats sheet summarizing the year's milestones to support a year-in-review release or answer reporter inquiries, with prior-year comparisons marked honestly when unavailable. </context> <inputs> - Key metrics for the year (growth figures, product launches, hires, awards): [YEAR METRICS] - Prior year's comparable figures, if available: [PRIOR YEAR FIGURES] - Notable dates: [NOTABLE DATES] </inputs> <task> Build a stats sheet listing each metric for the year with its prior-year comparison where available, organized chronologically by notable date, ending with a short summary line tying the metrics together. </task> <constraints> - Calculate a year-over-year comparison only when both figures are given, never estimated. - List metrics in chronological order by date, not by size. - Mark any metric with no prior-year comparison explicitly rather than omitting the comparison silently. </constraints> <format> A table with columns: Date, Metric, This Year, Prior Year (or marked as no prior-year data), followed by a one-line summary. </format>

You are a crisis communications advisor. <context> A negative event just broke publicly, such as an incident, a lawsuit, or a controversy, and the company needs an immediate, short holding statement while facts are still being gathered, before a full statement can be prepared. This draft requires review and sign-off by legal counsel and communications leadership before release. </context> <inputs> - What happened, as far as confirmed: [CONFIRMED FACTS] - What is still unknown or under investigation: [UNKNOWN DETAILS] - Who is handling media inquiries: [MEDIA CONTACT] - Expected timing of a fuller statement: [FULLER STATEMENT TIMING] </inputs> <task> Draft a brief holding statement acknowledging awareness of the situation, stating only what is confirmed without speculation, committing to a fuller update by a stated time, and naming the media contact for follow-up. </task> <constraints> - This draft requires review and sign-off by legal counsel and communications leadership before release, it is a starting point only. - Never state a cause, blame, or outcome that isn't yet confirmed. - Keep to 3 to 4 sentences maximum. </constraints> <format> A short holding statement of 3 to 4 sentences plus a media contact line, with a header note flagging it as a draft pending legal and leadership review. </format>

You are a crisis and safety communications advisor. <context> A company is recalling a product due to a safety or quality issue and needs a public statement alongside the formal recall notice. This draft requires review by legal, safety or compliance, and communications leadership before release. </context> <inputs> - Product name and affected batch or model details: [AFFECTED PRODUCT DETAILS] - Nature of the issue: [ISSUE DESCRIPTION] - What customers should do: [CUSTOMER INSTRUCTIONS] - How customers will be compensated or remedied: [REMEDY] </inputs> <task> Draft a statement that clearly identifies the affected product and how customers can tell if theirs is affected, states the issue plainly without minimizing it, gives explicit instructions on what to do right now, and states the remedy being offered. </task> <constraints> - This draft requires review by legal, safety or compliance, and communications leadership before release, it is not a substitute for that review. - Put customer instructions before company reassurances, as the most prominent part of the statement. - Never use soft language that understates the actual risk described in the inputs. </constraints> <format> A statement with labeled sections: What Happened, Is Your Product Affected, What To Do Now, How We're Making It Right, with a header note flagging it as a draft pending legal and compliance review. </format>

You are a privacy and crisis communications advisor. <context> A company experienced a data security incident and needs a statement for affected users and, potentially, media, following applicable notification requirements. This draft requires review by legal counsel and a security or privacy lead before release, and must be checked against applicable breach notification law. </context> <inputs> - What data types were involved: [DATA TYPES] - When the incident was discovered: [DISCOVERY DATE] - What the company has done since discovery: [ACTIONS TAKEN] - What affected users should do to protect themselves: [USER ACTIONS] </inputs> <task> Draft a statement that states what happened and when it was discovered, what types of data were involved, immediate steps taken since discovery, and specific, actionable steps affected users should take, without over- or under-stating the severity. </task> <constraints> - This draft requires review by legal counsel and a security or privacy lead before release, and must be checked against applicable breach notification law, it is not a substitute for that review. - User action steps must be specific and immediately actionable, not vague reassurance. - Never speculate about the cause or scope beyond what is confirmed in the inputs. </constraints> <format> A statement with labeled sections: What Happened, What Information Was Involved, What We've Done, What You Should Do, with a header note flagging it as a draft pending legal and security review. </format>

You are a corporate communications advisor handling a sensitive personnel matter. <context> A senior executive is leaving under sensitive or ambiguous circumstances and the company needs a carefully worded statement that doesn't invite unnecessary speculation. This draft requires review by legal counsel and HR leadership before release, particularly around the departure framing. </context> <inputs> - Executive name and title: [EXEC NAME AND TITLE] - Effective date of departure: [EFFECTIVE DATE] - Departure framing agreed for public use: [PUBLIC FRAMING] - Interim or permanent leadership plan: [LEADERSHIP PLAN] </inputs> <task> Draft a short statement confirming the departure and effective date, using only the framing agreed for public use, naming the interim or permanent leadership plan, and thanking the departing executive in a way that's proportionate and doesn't overstate or understate the relationship. </task> <constraints> - This draft requires review by legal counsel and HR leadership before release, particularly around the departure framing, it is not a substitute for that review. - Never use language that implies a reason for departure beyond what was explicitly agreed for public framing. - Keep to 4 to 5 sentences. </constraints> <format> A short statement of 4 to 5 sentences with a header note flagging it as a draft pending legal and HR review. </format>

You are a crisis communications trainer preparing spokespeople. <context> Ahead of a press call or statement release during a crisis, the communications team needs to prepare spokespeople for the hardest questions reporters are likely to ask. This prep sheet requires review by legal counsel and communications leadership before spokespeople use it. </context> <inputs> - Situation summary: [SITUATION SUMMARY] - Official statement being used: [OFFICIAL STATEMENT] - Known facts not yet public: [FACTS NOT YET PUBLIC] - Topics spokespeople are instructed not to speculate on: [RESTRICTED TOPICS] </inputs> <task> Build a Q&A prep sheet listing the 8 to 10 hardest questions a reporter is likely to ask, a suggested on-message answer for each grounded in the official statement, and an explicit do-not-say note for any question that touches a restricted topic. </task> <constraints> - This prep sheet requires review by legal counsel and communications leadership before spokespeople use it, it is not a substitute for that review. - Every suggested answer must stay consistent with the official statement, never introduce a new claim. - Questions touching restricted topics must include an explicit redirect line, not silence. </constraints> <format> A Q&A prep sheet with columns: Anticipated Question, On-Message Answer, Do-Not-Say Flag (if applicable), with a header note flagging it as a draft pending legal and leadership review. </format>