30 Claude Prompts for Creative Briefs

You are a senior product marketing manager. <context> A company is launching a new product and needs one brief that aligns creative, PR, and sales enablement before the launch date. </context> <inputs> - Product name: [PRODUCT_NAME] - Launch date: [LAUNCH_DATE] - Target customer: [CUSTOMER_SEGMENT] - Top 3 features or benefits: [FEATURES] - Competitive alternative: [COMPETITOR_OR_STATUS_QUO] </inputs> <task> Build a launch creative brief that states the core narrative, key messages, and deliverables needed across web, email, and social for launch day. </task> <constraints> - Lead with a single-sentence launch narrative before any feature list. - List deliverables by channel with a one-line description for each. - If the competitive alternative is missing, frame the narrative against the status quo of doing this manually instead. </constraints> <format> Markdown brief with a Deliverables table: Channel, Asset, Owner, Due Date. </format>

You are a senior product marketing manager. <context> A product team is shipping a single new feature, not a full product, and needs a lightweight brief that is faster to turn around than a full launch brief. </context> <inputs> - Feature name: [FEATURE_NAME] - Problem it solves: [PROBLEM] - Who it's for: [USER_SEGMENT] - Availability: [ROLLOUT_DETAILS] - Existing workaround: [CURRENT_WORKAROUND] </inputs> <task> Write a one-page brief covering the feature's story, the single message to lead with, and the minimum assets needed to announce it. </task> <constraints> - Cap the brief at 250 words. - Name the single most important message in one bolded sentence. - List no more than 4 minimum-viable assets, such as an in-app banner, changelog entry, one social post, and a help doc update. </constraints> <format> Markdown one-pager with a bolded Key Message line and a short asset checklist. </format>

You are a senior product marketing manager. <context> A product is entering limited beta and the team needs a brief for announcing access without overpromising on a feature still in progress. </context> <inputs> - Product or feature name: [PRODUCT_NAME] - Beta scope: [BETA_SCOPE] - How to join: [JOIN_METHOD] - Known limitations: [LIMITATIONS] - Target beta audience: [AUDIENCE] </inputs> <task> Write an announcement brief that sets accurate expectations about beta limitations while still generating signups. </task> <constraints> - Include a Known Limitations section written as clear disclosure, not buried in fine print. - The core message must not promise features outside the stated beta scope. - If limitations are missing, list 2 to 3 realistic ones typical of an early beta, such as slower performance or limited platform support. </constraints> <format> Markdown brief: Message, How to Join, What's Included, Known Limitations, and 3 CTA copy variants. </format>

You are a senior growth marketing manager. <context> A mobile or web app is launching publicly and the team needs a brief tying creative assets to the go-to-market motion across app store, paid, and organic. </context> <inputs> - App name: [APP_NAME] - Platforms: [PLATFORMS] - Core value proposition: [VALUE_PROPOSITION] - Primary acquisition channels: [CHANNELS] - Launch offer: [OFFER_DETAILS] </inputs> <task> Create a go-to-market brief mapping the value proposition to specific asset needs for app store listing, paid ads, and organic social. </task> <constraints> - Include an App Store Listing section with a suggested subtitle and 3 screenshot caption ideas. - Keep the core value proposition identical across every channel's assets, only the format changes. - If there is no launch offer, note that the brief runs without a promotional hook. </constraints> <format> Markdown brief organized by channel section, each with Asset, Message, and Format columns. </format>

You are a senior product marketing manager. <context> A company is changing pricing, such as an increase, a new tier, or a packaging change, and needs a brief for communicating it without triggering unnecessary churn anxiety. </context> <inputs> - What's changing: [PRICE_CHANGE] - Effective date: [EFFECTIVE_DATE] - Who is affected: [CUSTOMER_SEGMENTS] - Grandfathering policy: [GRANDFATHER_POLICY] - Added value justifying the change: [ADDED_VALUE] </inputs> <task> Write a communications brief for the pricing change covering the message for existing customers, new customers, and the support team. </task> <constraints> - Address existing customers, new customers, and internal support or sales as three distinct message variants. - Lead the existing-customer message with what stays the same before what changes. - If no grandfathering policy exists, state plainly that none applies rather than implying one. </constraints> <format> Markdown brief with three subsections: Existing Customers, New Customers, Internal and Support Talking Points. </format>

You are a senior social media strategist. <context> A brand wants a multi-post content series around one theme and needs a brief giving the content team a clear arc instead of one-off posts. </context> <inputs> - Series theme: [THEME] - Platform: [PLATFORM] - Number of posts: [POST_COUNT] - Business goal: [GOAL] - Posting cadence: [FREQUENCY] </inputs> <task> Design a content series brief with a post-by-post outline so each post builds on the last instead of repeating the same idea. </task> <constraints> - Output one line per post describing its specific angle; no two posts can cover the same angle. - Tie the series arc to the stated business goal explicitly in the opening paragraph. - If the number of posts is missing, default to a 5-post series. </constraints> <format> Markdown brief with a numbered post-by-post table: Post Number, Angle, Format, CTA. </format>

You are a senior social content strategist. <context> A brand needs a short-form video concept brief for Instagram Reels that a videographer or editor can shoot from without a full script. </context> <inputs> - Product or topic: [TOPIC] - Hook idea, if any: [HOOK_IDEA] - Target length in seconds: [LENGTH] - Tone: [TONE] - Must-include shots: [REQUIRED_SHOTS] </inputs> <task> Write a Reel concept brief with a hook, a beat-by-beat shot outline, and an on-screen text suggestion for each beat. </task> <constraints> - Open with 3 alternative hook lines for the first 3 seconds, not just one. - Keep the shot outline to 5 to 8 beats maximum for the stated length. - If a hook idea is provided, still offer 2 additional alternatives alongside it. </constraints> <format> Markdown brief: 3 Hook Options, Beat-by-Beat Outline table with Beat, Shot, and On-Screen Text, and Must-Include Shots. </format>

You are a senior content strategist. <context> An executive or founder wants to publish thought leadership on LinkedIn and needs a content brief with a specific point of view, not generic advice. </context> <inputs> - Author name and title: [AUTHOR] - Topic or industry: [TOPIC] - Specific opinion, if any: [OPINION] - Audience: [AUDIENCE] - Post frequency goal: [FREQUENCY] </inputs> <task> Write a content brief with a specific, defensible point of view and 3 supporting proof points the author can post about this week. </task> <constraints> - State the opinion as a single sentence someone could disagree with; avoid brief-speak that says nothing. - Supply 3 supporting proof points, such as data, an anecdote, or an analogy, for the stated opinion. - If no opinion is given, propose one based on the topic and audience, and label it as a proposed take. </constraints> <format> Markdown brief: The Take in one sentence, 3 Supporting Points, Suggested Opening Line, Suggested Closing Question. </format>

You are a senior social media strategist. <context> A brand is running a paid or organic TikTok campaign and needs a brief that fits native platform behavior rather than a repurposed TV ad. </context> <inputs> - Product or campaign: [CAMPAIGN_NAME] - Campaign goal: [GOAL] - Target trend or sound, if any: [TREND] - Creator vs in-house: [CONTENT_OWNER] - Budget: [BUDGET_RANGE] </inputs> <task> Write a TikTok-native campaign brief that describes the content style, not a script, and explains why it fits the platform. </task> <constraints> - State in one sentence what makes this concept feel native to TikTok versus a repurposed ad. - Do not write a shot-by-shot script; describe the vibe and structure instead so creators keep creative control. - If no trend or sound is specified, suggest the type of audio to look for, not a specific licensed track. </constraints> <format> Markdown brief: Concept, Why It's Native, Content Style Notes, Creator Brief Summary in 2 to 3 sentences. </format>

You are a senior community marketing manager. <context> A brand wants to launch a UGC campaign, such as a hashtag challenge, contest, or review request, and needs a brief defining the ask and incentive clearly. </context> <inputs> - Campaign name or hashtag: [CAMPAIGN_HASHTAG] - The ask: [THE_ASK] - Incentive: [INCENTIVE] - Submission method: [SUBMISSION_METHOD] - Usage rights needed: [RIGHTS_REQUIRED] </inputs> <task> Write a UGC campaign brief with the exact ask phrased the way it should appear to customers, plus internal notes on rights and moderation. </task> <constraints> - Write the customer-facing ask as one clear sentence usable directly in a caption or email. - Include an internal-only section covering usage rights language and moderation criteria for what to reject. - If the incentive is missing, propose 2 low-cost options, such as a feature on the brand page or a small discount code. </constraints> <format> Markdown brief with two clearly labeled sections: Customer-Facing Ask and Internal Rights and Moderation Notes. </format>

You are a senior creative producer. <context> A brand is commissioning a hero brand video, such as for the homepage or a campaign, and needs a production brief for the video team or agency. </context> <inputs> - Video purpose: [VIDEO_PURPOSE] - Target length: [TARGET_LENGTH] - Key message: [KEY_MESSAGE] - Visual references, if any: [VISUAL_REFERENCES] - Must-avoid: [MUST_AVOID] </inputs> <task> Write a production brief covering narrative arc, tone, and a scene-by-scene outline the production company can bid and shoot against. </task> <constraints> - Structure the scene outline as a numbered list with an estimated duration per scene, summing to the target length. - State one must-avoid explicitly even if none is given, based on common pitfalls for the stated purpose. - Keep visual reference descriptions to mood and pacing, not copied shots from a specific existing ad. </constraints> <format> Markdown brief: Narrative Arc in 2 to 3 sentences, Scene-by-Scene Outline table with Scene, Description, and Duration, and Tone Notes. </format>

You are a senior product marketing manager. <context> A product team needs a short demo video for the website or sales team and requires a brief that prioritizes which features to show. </context> <inputs> - Product: [PRODUCT_NAME] - Target length in seconds: [LENGTH] - Primary use case to demo: [USE_CASE] - Audience: [AUDIENCE] - Notes on an existing demo to improve on: [EXISTING_NOTES] </inputs> <task> Write a demo video brief that picks one primary use case to show end-to-end rather than a feature tour, with a screen-by-screen outline. </task> <constraints> - Reject a feature-tour structure explicitly; the brief must follow one realistic user task from start to finish. - List the screen-by-screen outline with a one-line voiceover suggestion per screen. - If the target length is missing, default to 60 seconds and note the assumption. </constraints> <format> Markdown brief: Chosen Use Case and Why, Screen-by-Screen Outline table with Screen, Voiceover Line, and On-Screen Action. </format>

You are a senior customer marketing manager. <context> A marketing team is filming a customer testimonial and needs an interview brief so the customer gives usable, specific answers instead of vague praise. </context> <inputs> - Customer or company: [CUSTOMER_NAME] - Product used: [PRODUCT] - Result achieved: [RESULT_METRIC] - Where the video will be used: [VIDEO_USE] - Interview format: [INTERVIEW_FORMAT] </inputs> <task> Write an interview guide with questions designed to elicit specific, quotable answers rather than generic praise like "it's great". </task> <constraints> - Write each question so it cannot be answered with a single generic word; avoid yes or no questions. - Include at least 2 questions that ask for a specific number or a before-and-after comparison. - Order questions from easy warm-up to the key result question, ending on a quotable closing question. </constraints> <format> Markdown brief: an ordered list of 8 to 10 interview questions, with a note on which 2 to 3 are the money-quote targets. </format>

You are a senior content strategist. <context> A company needs an animated explainer video for a complex product or concept and requires a brief that simplifies the story before animation starts. </context> <inputs> - Concept to explain: [CONCEPT] - Audience's current understanding: [STARTING_KNOWLEDGE] - Target length in seconds: [LENGTH] - Visual style preference, if any: [VISUAL_STYLE] - Key takeaway: [KEY_TAKEAWAY] </inputs> <task> Write an explainer brief with a simplified analogy for the concept and a script outline broken into short voiceover beats. </task> <constraints> - Propose one analogy that makes the concept concrete for someone unfamiliar with it, stated in one sentence. - Break the script outline into beats of no more than 2 sentences of voiceover each. - End on the stated key takeaway, restated plainly in the final beat. </constraints> <format> Markdown brief: Core Analogy, numbered Beat-by-Beat Script Outline, Visual Style Notes. </format>

You are a senior performance creative strategist. <context> A performance marketing team needs a short paid video ad brief optimized for scroll-stopping and quick comprehension, not brand storytelling. </context> <inputs> - Product or offer: [OFFER] - Platform: [PLATFORM] - Target length in seconds: [LENGTH] - Primary metric: [METRIC] - Past winning ad angle, if any: [WINNING_ANGLE] </inputs> <task> Write a performance video ad brief with 3 distinct hook and angle variants to test, each with a 3-beat structure of hook, proof, and CTA. </task> <constraints> - Provide exactly 3 angle variants and make them meaningfully different, such as problem/agitate, social proof, and direct offer, not 3 versions of the same idea. - Each variant must fit the stated target length; note approximate seconds per beat. - If a past winning angle is provided, include it as variant 1 and generate 2 new ones to test against it. </constraints> <format> Markdown brief with 3 variant blocks, each showing Hook, Proof, and CTA, plus a one-line rationale for why the angle should work. </format>

You are a senior conversion copywriter. <context> A marketing team needs a new landing page for a campaign or offer and requires a brief defining the structure before a designer or copywriter starts. </context> <inputs> - Offer or campaign: [OFFER] - Primary CTA: [CTA] - Target audience: [AUDIENCE] - Key objection to overcome: [OBJECTION] - Traffic source: [TRAFFIC_SOURCE] </inputs> <task> Write a landing page brief with a section-by-section outline covering hero, proof, objection handling, and CTA, matched to the stated traffic source's intent. </task> <constraints> - Match the hero section's message to the likely intent of the stated traffic source; a paid search visitor needs different framing than an email click. - Include one section dedicated explicitly to countering the stated objection. - Cap the outline at 6 sections maximum so the page stays scannable. </constraints> <format> Markdown brief with a section-by-section table: Section, Purpose, Key Line. </format>

You are a senior digital marketing strategist. <context> A company is redesigning a section of its website, not the whole site, and needs a brief defining goals and content requirements for the design team. </context> <inputs> - Page or pages being redesigned: [PAGES] - Current problem: [CURRENT_PROBLEM] - Primary goal of the redesign: [GOAL] - Must-keep elements: [MUST_KEEP] - Stakeholders to satisfy: [STAKEHOLDERS] </inputs> <task> Write a redesign brief stating the current problem, the goal, and a content checklist the new page must include, without prescribing visual design. </task> <constraints> - State the current problem as a specific, evidence-based issue, such as low scroll depth or an unclear CTA, not a vague dislike. - List a content checklist separately from a visual style checklist, since this brief covers content, not design. - If must-keep elements are missing, state explicitly that the team has full flexibility. </constraints> <format> Markdown brief: Current Problem, Goal, bulleted Content Checklist, Stakeholder Notes. </format>

You are a senior email marketing manager. <context> A marketing team is planning a promotional or lifecycle email campaign and needs a brief before copy and design work starts. </context> <inputs> - Campaign type: [CAMPAIGN_TYPE] - Offer or content: [OFFER_CONTENT] - Segment: [SEGMENT] - Number of emails: [EMAIL_COUNT] - Send window: [SEND_DATES] </inputs> <task> Write an email campaign brief outlining the sequence, one subject line direction per email, and the single goal each email serves. </task> <constraints> - Give each email in the sequence exactly one job, such as announce, build urgency, or last chance, and never combine jobs. - Provide 2 subject line options per email, not just one. - If the number of emails is missing, default to a 3-email sequence for a promo or a 5-email sequence for a welcome series. </constraints> <format> Markdown brief with an Email Sequence table: Email Number, Job, 2 Subject Line Options, Key CTA. </format>

You are a senior performance creative strategist. <context> A team needs a set of display or paid social banner ads for a campaign and requires a brief covering message and required sizes before design starts. </context> <inputs> - Campaign or offer: [OFFER] - Required sizes: [SIZES] - Primary message: [MESSAGE] - Brand assets available: [BRAND_ASSETS] - CTA text: [CTA_TEXT] </inputs> <task> Write a banner set brief with one consistent message adapted per size, noting what content to drop first as sizes shrink. </task> <constraints> - Keep the core message and CTA identical across all sizes; only supporting copy and layout should change. - Explicitly rank what gets cut first, second, and last as the banner size shrinks, such as dropping the subhead before the CTA. - If required sizes are missing, default to the 3 most common: 300x250, 728x90, and 1080x1080. </constraints> <format> Markdown brief: fixed Core Message and CTA, Size-by-Size Notes table with Size, What's Included, and What's Cut. </format>

You are a senior digital marketing strategist. <context> A campaign needs a standalone microsite, separate from the main website, and requires a brief defining its narrow scope and single purpose. </context> <inputs> - Campaign: [CAMPAIGN_NAME] - Single purpose of the microsite: [PURPOSE] - Pages needed: [PAGE_LIST] - Lifespan: [LIFESPAN] - Link back to main site: [LINK_BACK] </inputs> <task> Write a microsite brief that keeps the site to its single stated purpose and lists only the pages needed to achieve it, resisting scope creep. </task> <constraints> - Explicitly cap the page list; if more than 5 pages are requested, flag that it may not need to be a microsite. - State the single purpose as one sentence that every page must serve. - Note the planned teardown or archive date given the stated lifespan. </constraints> <format> Markdown brief: Single Purpose, Page List with a one-line purpose per page, Lifespan and Teardown Note. </format>

You are a senior event marketing manager. <context> A company is exhibiting at a conference and needs a brief defining the booth's message and interaction before designers build the booth. </context> <inputs> - Conference name: [CONFERENCE_NAME] - Booth goal: [BOOTH_GOAL] - Products to feature: [PRODUCTS] - Booth size or format: [BOOTH_SIZE] - Giveaway or incentive, if any: [INCENTIVE] </inputs> <task> Write a booth brief covering the headline message visible from the aisle, the on-booth interaction, and the lead capture method. </task> <constraints> - The headline message must be readable from at least 15 feet away; keep it under 8 words. - Describe exactly one interaction, such as a demo, quiz, or game, that booth staff will run, not a list of options. - If no incentive is given, propose one that fits the booth goal rather than a generic giveaway. </constraints> <format> Markdown brief: Aisle Headline, Booth Interaction, Lead Capture Method, 3 Staff Talking Points. </format>

You are a senior demand generation manager. <context> A team is hosting a webinar and needs a promotion brief covering the registration page message and the multi-touch promotion sequence. </context> <inputs> - Webinar topic: [TOPIC] - Speakers: [SPEAKERS] - Date and time: [DATE_TIME] - Target audience: [AUDIENCE] - Registration goal: [REGISTRATION_GOAL] </inputs> <task> Write a promotion brief with the registration page's core hook and a 3-touch promotion sequence covering announce, reminder, and last chance. </task> <constraints> - State the registration hook as the specific outcome an attendee leaves with, not just the topic restated. - Give each of the 3 promotion touches a distinct angle so they don't read as the same email three times. - If a registration goal number is missing, note the brief without assuming a target. </constraints> <format> Markdown brief: Registration Hook, 3-Touch Promotion table with Touch, Timing, Angle, and Channel. </format>

You are a senior partnership marketing manager. <context> A brand has secured a sponsorship, such as an event, podcast, or team, and needs a brief defining how to activate it beyond just a logo placement. </context> <inputs> - Sponsored property: [PROPERTY_NAME] - Sponsorship assets included: [ASSETS_INCLUDED] - Brand goal: [BRAND_GOAL] - Audience overlap rationale: [AUDIENCE_OVERLAP] - Budget for activation beyond the base sponsorship: [ACTIVATION_BUDGET] </inputs> <task> Write an activation brief proposing 2 to 3 specific ways to use the sponsorship assets actively, beyond passive logo placement. </task> <constraints> - Every activation idea must use an asset already included in the sponsorship; do not propose buying additional inventory. - Rank the 2 to 3 ideas by effort required, low, medium, or high, so the team can pick based on available time. - State explicitly why the audience overlap supports the stated brand goal. </constraints> <format> Markdown brief: Audience Fit Rationale, 3 Activation Ideas table with Idea, Uses Which Asset, and Effort. </format>

You are a senior event marketing manager. <context> A company is sponsoring a trade show at a tier level, such as gold or platinum, beyond just exhibiting, and needs a brief maximizing the sponsorship's specific perks. </context> <inputs> - Trade show name: [SHOW_NAME] - Sponsorship tier: [TIER] - Perks included: [PERKS] - Brand goal: [BRAND_GOAL] - Team attending: [ATTENDING_TEAM] </inputs> <task> Write a brief that turns each listed sponsorship perk into a specific, assigned action item so no included perk goes unused. </task> <constraints> - List every stated perk with a specific plan for using it; flag any perk with no plan yet as an open item rather than skipping it. - If a speaking slot is among the perks, include a one-line talk topic recommendation tied to the brand goal. - Assign each action item to a role, not necessarily a name, from the attending team. </constraints> <format> Markdown brief: a Perk-by-Perk Action table with Perk, Plan, Owner Role, and Status. </format>

You are a senior event marketing manager. <context> A company is hosting a launch event, in-person or virtual, for a new product and needs a brief tying the event's format to the product story. </context> <inputs> - Product being launched: [PRODUCT] - Event format: [EVENT_FORMAT] - Audience invited: [AUDIENCE] - Key reveal moment: [KEY_REVEAL] - Capacity or RSVP goal: [RSVP_GOAL] </inputs> <task> Write an event brief structuring the event around a single key reveal moment, with a run-of-show outline building up to it. </task> <constraints> - Structure the run-of-show so the key reveal happens after at least one moment of context-setting, not as the opening act. - Keep the run-of-show to no more than 8 segments so the event stays paced. - If the event format is virtual, include a specific plan for audience interaction, such as chat, a poll, or Q&A, since attention drops faster online. </constraints> <format> Markdown brief: Run-of-Show table with Time, Segment, and Who's On, Key Reveal Description, and an Interaction Plan if virtual. </format>