30 Claude prompts for videographers

You are a wedding videographer building the shot list and camera coverage plan before a wedding. <context> You're finalizing prep for a wedding next month and need a coverage plan showing which camera and operator covers each moment, since you're running a two-camera setup. </context> <inputs> - Couple names: [Elena Vasquez & Tom Bradford] - Ceremony and reception times: [Ceremony 4:00 PM, reception 6:00 PM to 11:00 PM] - Crew: [Two operators, Camera A on a gimbal, Camera B on a tripod for wide coverage] - Must-capture moments: [Vows, ring exchange, first dance, father-daughter dance, toasts] </inputs> <task> Build a shot list and coverage plan assigning each must-capture moment to a specific camera and operator, noting movement (static vs. gimbal) for each. </task> <constraints> - Assign every must-capture moment to a specific camera, don't leave any unassigned. - Use the gimbal camera only for moments with real value from movement (processional, first dance), keep the tripod on static coverage for vows and toasts to avoid shake on dialogue-heavy audio. - Flag any moment where both cameras should get different angles of the same moment, not redundant angles. </constraints> <format> A coverage plan table with columns: Time, Moment, Camera, Operator, Movement Notes. </format>

You are a videographer planning a corporate interview shoot with supporting B-roll. <context> You're shooting employee interviews for a recruiting video and need a shot list that pairs each interview with specific B-roll to cut away to during editing. </context> <inputs> - Interview subjects and roles: [4 employees: warehouse lead, software engineer, HR manager, new hire] - Location: [Northfield Logistics warehouse and office] - B-roll available: [Warehouse floor operations, office collaboration shots, loading dock activity, team lunch area] - Video theme: [What it's actually like to work here, day in the life] </inputs> <task> Build a shot list pairing each interview subject with 3 to 4 specific B-roll shots relevant to their role, plus a general B-roll list for the video's opening and closing. </task> <constraints> - Match B-roll to each subject's actual role, don't assign warehouse footage to the office-based HR manager interview. - Include at least one shot per subject that shows them at their actual workstation, not a generic seated interview only. - Keep the opening/closing general B-roll list separate from the per-subject lists. </constraints> <format> A shot list organized by subject, each with paired B-roll shots, plus a separate general B-roll section. </format>

You are a videographer storyboarding a 60-second brand commercial before the shoot day. <context> You're producing a commercial for a local roastery and need a storyboard outline that sequences shots to a rough voiceover script before committing to a shot list. </context> <inputs> - Client and product: [Northfield Roasters, a seasonal coffee blend] - Voiceover beats: [Opening hook about mornings, product hero shot, brewing process, people enjoying it in a cafe setting, closing tagline] - Location and talent: [In-store cafe location, 2 talent extras for the enjoying-coffee scene] - Target length: [60 seconds total] </inputs> <task> Build a shot-by-shot storyboard outline mapping each voiceover beat to a specific shot type (close-up, wide, tracking) and an approximate duration, summing to the 60-second target. </task> <constraints> - The sum of shot durations must equal exactly 60 seconds. - Match shot type to the emotional weight of each beat (e.g., close-up for the hero product shot, wide for the cafe scene). - Note where the 2 talent extras appear and for how long, not just "people in background." </constraints> <format> A storyboard outline table with columns: Beat, Shot Type, Duration, Notes, with a running total column. </format>

You are a videographer scouting a location and prepping equipment before a shoot day. <context> You have a shoot booked at a location you haven't filmed at before, and need a scouting checklist plus an equipment list tailored to what that location will require. </context> <inputs> - Location type: [A working warehouse with mixed natural and fluorescent lighting] - Shoot requirements: [Handheld interview setup plus a tracking shot down a long aisle] - Known constraints: [Limited power outlets, background machinery noise, no elevator to a mezzanine level they want a shot from] </inputs> <task> Build a location scouting checklist covering lighting, power, and sound constraints, then an equipment list adjusted for the stated constraints (e.g., battery-powered lighting given limited outlets, a shotgun mic and possible ADR plan given machinery noise). </task> <constraints> - Address each stated constraint (power, noise, no elevator access) with a specific equipment or workflow solution, not a general note to "be prepared." - Note a workaround for the mezzanine shot given no elevator access (e.g., stairs plan, or cutting that shot). - Separate the checklist into Scouting Questions and Equipment List clearly. </constraints> <format> Two sections: a Scouting Checklist (questions to confirm on-site) and an Equipment List, both as bullet lists. </format>

You are a videographer planning multi-camera coverage for a live event with no retakes possible. <context> You're covering a live conference keynote and panel with three cameras, and since there's no retake option, you need a coverage plan that assigns clear roles before the event starts. </context> <inputs> - Event segments: [Keynote speech, 45 minutes, followed by a 30-minute panel with 4 speakers] - Cameras and crew: [3 cameras: one wide static, one on a slider for the keynote stage, one roaming handheld for audience reactions] - Audio setup: [Lav mic on keynote speaker, table mics for panel, board feed as backup audio] - Priority shot needs: [Clean wide shot at all times as safety coverage, close-ups on whichever panelist is speaking] </inputs> <task> Build a coverage plan assigning each camera a primary role per segment, with the wide static camera locked as continuous safety coverage throughout both segments. </task> <constraints> - Keep the wide static camera on continuous safety coverage for the entire event, it must never be repositioned or left unmanned. - For the panel segment, assign the roaming or slider camera to follow whichever panelist is currently speaking, not a fixed rotation. - State the audio backup plan (board feed) explicitly as a fallback, not just a note. </constraints> <format> A coverage plan table with columns: Segment, Camera, Role, Audio Note. </format>

You are a videographer writing the script for a 60-second brand commercial. <context> A client wants a 60-second commercial with a voiceover, and you need a tightly timed script that fits the runtime exactly, not a script that gets cut down after the fact. </context> <inputs> - Client and product: [Northfield Roasters, a seasonal coffee blend] - Key message: [Small-batch roasted, tastes like a slower morning] - Tone: [Warm, unhurried, not overly energetic] - Call to action: [Visit the new seasonal blend page, mention it's available for a limited time] </inputs> <task> Write a 60-second voiceover script with timestamps every 10 to 15 seconds, matched to the stated tone and key message, ending with the call to action. </task> <constraints> - Include timestamps and confirm the script's spoken length realistically fits 60 seconds at a natural reading pace (roughly 150 words per minute). - Match the unhurried tone, avoid short punchy ad-copy phrasing throughout. - State the call to action clearly in the final 10 seconds, not earlier. </constraints> <format> A timestamped script with a running word count, ending with a total word count check against the 60-second target. </format>

You are a wedding videographer writing a short voiceover script to pair with a highlight reel. <context> A couple wants their 4-minute highlight reel to include a brief voiceover from their vows instead of only music, and you need a script structure pulling from their actual ceremony. </context> <inputs> - Couple names: [Elena Vasquez & Tom Bradford] - Vow excerpts available: [Tom's line "you make ordinary Tuesdays feel like an event," Elena's line "I choose you again, every single day"] - Reel structure: [Opens on getting ready, moves to ceremony, ends on reception dancing] - Music note: [Voiceover should appear over quiet moments only, not compete with the reception music] </inputs> <task> Write a script showing exactly where each vow excerpt should be placed in the reel's structure, timed to the described visual moments, with a note on where music should duck for the voiceover to be heard clearly. </task> <constraints> - Use the couple's actual vow lines verbatim, don't paraphrase or invent new lines. - Place voiceover only over quiet visual moments (getting ready, ceremony), never over the reception dancing section. - Note explicitly where music volume should duck under the voiceover. </constraints> <format> A script/cue sheet with columns: Reel Section, Visual, Voiceover Line, Audio Note. </format>

You are a videographer writing a script for a corporate explainer video. <context> A software company needs a 90-second explainer video that describes what their product does for a homepage, and the script needs to work for a mix of screen recording and light on-camera narration. </context> <inputs> - Client and product: [A project management tool called Flowdesk, aimed at small agencies] - Key problem it solves: [Agencies losing track of client approvals across email threads] - Structure requested: [Problem, solution, one feature highlight, call to action] - Target length: [90 seconds] </inputs> <task> Write a 90-second script alternating between narration lines and on-screen action notes (what the screen recording should show at that moment), structured as problem, solution, feature highlight, call to action. </task> <constraints> - Pair every narration line with a specific on-screen action note, don't leave any line without a visual instruction. - Keep the feature highlight to exactly one feature, not a list of everything the product does. - End with a specific call to action line, not a vague "learn more." </constraints> <format> A two-column script with Narration and On-Screen Action, plus a running timestamp. </format>

You are a videographer writing a creative brief to align a client before scripting begins. <context> A client wants a marketing video but hasn't clearly stated their goals, and you need a creative brief that forces clarity before you write a single line of script. </context> <inputs> - Client and project: [A local gym launching a new class format] - Stated goal (vague): [Want something that "feels energetic and gets people excited"] - Audience: [Current members plus people who've never tried a group class] - Budget and length constraint: [$2,000 budget, 45 to 60 second target length] </inputs> <task> Write a creative brief that translates the vague goal into specific tone, message, and audience notes, and flags any gap between their stated budget/length and what they're describing. </task> <constraints> - Translate "energetic and exciting" into 3 concrete tone descriptors and one specific visual reference style, don't leave it abstract. - Explicitly note if the stated goal risks needing more than the given budget or length, and suggest a scope adjustment if so. - Include a one-sentence single key message the video must land, not multiple competing messages. </constraints> <format> A creative brief with sections: Goal Translation, Audience, Key Message, Budget/Scope Check. </format>

You are a videographer writing a short-form social video script optimized for retention. <context> A client wants a 30-second vertical video for Instagram Reels and TikTok, and you know the first 3 seconds determine whether most viewers keep watching. </context> <inputs> - Client and topic: [A local gym, promoting a new HIIT class format] - Platform: [Instagram Reels and TikTok, vertical format] - Available footage style: [Real class footage, no scripted actors, natural sound] - Target length: [30 seconds] </inputs> <task> Write a 30-second script starting with 3 distinct hook options for the opening 3 seconds, then the body script, timed with on-screen text cues. </task> <constraints> - Provide exactly 3 alternate hook options for the first 3 seconds, each using a different hook style (question, bold claim, visual surprise). - Keep on-screen text cues short enough to read in under 2 seconds each. - Match the script to real, unscripted class footage, don't write lines that require staged acting. </constraints> <format> A script with a "Hook Options" section (3 alternates) followed by the timed body script with on-screen text cues. </format>

You are a wedding videographer building a client-facing pricing guide. <context> You're updating your pricing guide and want three clear tiers that make the mid-tier package the obvious best value. </context> <inputs> - Business name: [Hollow Light Films] - Tiers to build: [Ceremony Only, Classic Film, Premium Cinematic] - Base costs to cover: [Second operator costs $350/wedding, editing takes 20 hours per wedding at a $45/hour internal rate, drone add costs $150 in equipment/insurance amortized] - Target price anchors: [Ceremony Only around $1,000, Classic Film around $2,600, Premium Cinematic around $4,200] </inputs> <task> Build a three-tier pricing guide with hours of coverage, deliverables (highlight film length, ceremony edit, drone inclusion), and price for each tier, then a short paragraph on why Classic Film is the best value. </task> <constraints> - Each price must plausibly cover the stated costs (second operator, editing hours, drone) at that tier's inclusion level. - The best-value paragraph must reference at least two specific included deliverables, not just say "most popular." - List tiers side by side so a client can compare at a glance. </constraints> <format> A three-column pricing table (Ceremony Only, Classic Film, Premium Cinematic) followed by a short best-value paragraph. </format>

You are a videographer building a day-rate sheet for corporate clients. <context> Corporate clients keep asking what a shoot day costs before they'll bring you into a project, and you want a clear day-rate sheet instead of quoting from scratch every time. </context> <inputs> - Day rate and crew included: [$1,800/day, includes one operator and basic lighting/audio kit] - Add-on crew: [Second camera operator $500/day, dedicated sound recordist $400/day] - Editing rate: [Not included in day rate, billed separately at $75/hour, average project runs 8 to 12 hours] - Deliverables per standard day: [Up to 6 hours of raw footage organized and delivered within 3 business days] </inputs> <task> Build a day-rate sheet listing the base day rate and inclusions, optional add-on crew pricing, separate editing rate with a typical hour range, and the raw footage delivery timeline. </task> <constraints> - Keep shoot day rate and editing rate as clearly separate line items, never bundled into one number. - State the typical editing hour range so clients can estimate total project cost, not just an hourly rate with no anchor. - State the raw footage delivery timeline explicitly, not "shortly after." </constraints> <format> A rate sheet with sections: Day Rate & Crew, Add-On Crew, Editing Rate, Delivery Timeline. </format>

You are a videographer building an add-on menu to increase average project value. <context> Clients often ask about drone footage, faster turnaround, or extra editing help after booking, and you want a clean add-on menu instead of answering the same questions one-off. </context> <inputs> - Base package: [Standard wedding film, no drone, 6-week delivery] - Add-ons and costs to you: [Drone operator $200 cost (insurance and equipment), rush delivery requires paying a second editor overtime at roughly $300 extra cost, extra editor for faster turnaround around $250 cost] - Target margin: [At least 2.5x cost on add-ons] </inputs> <task> Build an add-on menu with client-facing prices for drone footage, rush delivery (2-week turnaround instead of 6), and an extra editor option, each priced to hit the stated margin target. </task> <constraints> - Show the math for at least one item (cost times target margin equals price) so the pricing logic is checkable. - Round client-facing prices to clean numbers. - State the specific turnaround time change for the rush delivery option (2 weeks instead of 6), not just "faster." </constraints> <format> An add-on menu table with columns: Item, Client Price, Turnaround Impact, and a short pricing-logic note at the bottom. </format>

You are a videographer building a usage-based licensing rate card for footage and finished video sales. <context> You have unused B-roll and finished project footage that clients occasionally want to license for their own use, and you want a rate card instead of negotiating each request from scratch. </context> <inputs> - Footage type: [Unused B-roll from past corporate shoots, resold with client permission, plus stock-style nature and cityscape clips you own outright] - Usage tiers to price: [Personal/internal use, small business marketing use, broadcast or paid national campaign use] - License term default: [Perpetual for personal/internal, 12-month renewable for commercial use] - Positioning: [Boutique local videographer, not a stock footage marketplace] </inputs> <task> Build a rate card listing pricing per usage tier, with a note on which footage requires original client permission before resale. </task> <constraints> - Flag any footage type that requires the original client's permission before resale, don't imply all footage is freely resellable. - Scale prices so broadcast/national use is meaningfully higher than personal or small-business use. - Keep positioning realistic for a boutique videographer, not marketplace-scale stock pricing. </constraints> <format> A rate card table with columns: Usage Tier, License Term, Price, Permission Note. </format>

You are a videographer responding to a client whose stated budget is below your standard package price. <context> A small business wants a promotional video but their stated budget is well under your usual project minimum, and you want to respond helpfully without just declining or discounting reflexively. </context> <inputs> - Client's stated budget: [$800] - Your standard project minimum: [$2,200 for a comparable promotional video] - What could fit their budget: [A single-location, single-camera shoot with client-provided B-roll, no drone, 30-second cut only] - Your stance: [Willing to scope down, not willing to do full scope at a discount] </inputs> <task> Write a response that doesn't discount the standard package, but proposes a specific scoped-down version that could realistically fit their stated budget. </task> <constraints> - Do not offer the full standard package at a discounted price anywhere in the response. - Propose the scoped-down version with specific tradeoffs named (single camera, client B-roll, shorter cut), not a vague "smaller package." - State the scoped price explicitly and confirm it fits within their stated $800 budget. </constraints> <format> A short, professional email with subject line, ready to send as-is. </format>

You are a videographer sending a kickoff email after a new project is signed. <context> A corporate client just signed off on a video project and you want to send a kickoff email that sets expectations on process and timeline before the shoot happens. </context> <inputs> - Client and project: [Northfield Logistics, a 3-minute recruiting video] - Confirmed shoot date: [March 4, 2026] - Milestone dates: [Rough cut by March 18, feedback due within 5 business days, final delivery within 5 business days of approval] - What you need from them before the shoot: [Confirmed interview subjects and a signed location release] </inputs> <task> Write a kickoff email restating the shoot date, the full milestone timeline, and exactly what's needed from the client before the shoot with a specific due date. </task> <constraints> - State the feedback turnaround expectation (5 business days) explicitly so delays on their end are visible against the timeline. - List what's needed from the client (subjects, location release) with its own due date, not bundled vaguely into "let us know." - Keep the email organized so someone skimming can find the shoot date in 5 seconds. </constraints> <format> A kickoff email with a clearly labeled timeline section and a "what we need from you" section with due dates. </format>

You are a videographer sending a rough cut to a client for review. <context> The rough cut of a project is ready and you need to send it with clear instructions on how to give feedback so you don't get scattered, hard-to-act-on notes back. </context> <inputs> - Client and project: [Northfield Logistics, recruiting video] - Rough cut link: [Frame.io review link] - Feedback deadline: [5 business days from send] - Feedback format requested: [Timestamped comments directly on the Frame.io link, not a separate email list] </inputs> <task> Write a review request email explaining what stage this cut represents (picture lock pending music/color, or similar), how to leave feedback, and the exact deadline. </task> <constraints> - State plainly what is and isn't finished in this cut (e.g., temp music, no color grade yet) so the client doesn't flag issues that are already known and pending. - Specify the feedback format (timestamped comments on the link) as the only channel, and ask them not to also email a separate list. - State the exact deadline date, not "by end of week." </constraints> <format> A ready-to-send email with subject line, review link, and clear feedback instructions. </format>

You are a videographer organizing scattered client feedback into an actionable revision list. <context> A client sent feedback across three separate emails and a phone call, and before you touch the edit you want to consolidate it into one clear, de-duplicated list to confirm back with them. </context> <inputs> - Feedback sources: [Email 1: trim the intro, Email 2: swap the background music, cut the CEO's second answer shorter, Phone call: add company logo at the end, mentioned again wanting the intro trimmed] - Project: [Corporate recruiting video, rough cut stage] - Your goal: [One consolidated numbered list to confirm with the client before starting revisions] </inputs> <task> Consolidate the scattered feedback into one de-duplicated, numbered revision list, and write a short confirmation email asking the client to approve the list before you start. </task> <constraints> - Remove the duplicate "trim the intro" note, don't list it twice just because it was mentioned in two channels. - Number each distinct revision item clearly so the client can approve or amend by number. - Ask for explicit approval of the consolidated list before starting, don't assume it's correct. </constraints> <format> A numbered revision list followed by a short confirmation email requesting approval. </format>

You are a videographer who is behind on a promised final delivery date. <context> You promised final delivery 2 weeks after rough cut approval and you're now 4 days past that with no final file sent, and you need to communicate the delay honestly with a real new date. </context> <inputs> - Client and project: [Northfield Logistics, recruiting video, rough cut approved 18 days ago] - Original promised delivery: [2 weeks after approval] - Reason for the delay: [Color grading and audio mix backlog, being upfront without over-explaining] - New firm delivery date: [Exactly 3 business days from today] </inputs> <task> Write an apology email that states the delay plainly, gives one honest reason without over-justifying, and commits to a specific new delivery date. </task> <constraints> - State the new delivery date as a specific date, not "very soon." - Keep the explanation for the delay to one sentence, don't over-apologize across multiple paragraphs. - Offer one small goodwill gesture (e.g., an extra 15-second cutdown for social media) tied to the delay. </constraints> <format> A short, direct apology email with subject line, ready to send as-is. </format>

You are a videographer responding to a client requesting another revision round beyond what's included in the contract. <context> A client has used both included revision rounds and is now asking for "just one more small tweak," and you need to hold the line on your revision policy without souring the relationship. </context> <inputs> - Contract terms: [2 revision rounds included, $150 per additional round] - Client's latest request: [A third round asking to re-time two cuts and swap one music transition] - Relationship context: [Good client overall, this is their first project with you, likely to book again] - Your stance: [Willing to do this one for the stated additional-round fee, not for free] </inputs> <task> Write a response that acknowledges the request, restates the included-rounds policy plainly, states the fee for this round, and confirms you're happy to proceed once approved. </task> <constraints> - Restate the contract's included-rounds number and the additional fee explicitly, don't imply this one is a one-time exception. - Keep the tone warm and non-punitive, this is a policy statement, not a rebuke. - End with a clear next step (approve the fee to proceed) rather than leaving it open-ended. </constraints> <format> A short, professional email with subject line, ready to send as-is. </format>

You are a videographer building a homepage for your studio's portfolio website. <context> You need a single-page HTML homepage that showcases your video work and makes it obvious how to inquire, without hiring a web developer. </context> <inputs> - Studio name and specialty: [Hollow Light Films, wedding and corporate video] - Sections needed: [Hero with tagline, a 4-project showcase grid with placeholder video thumbnail blocks, a short about blurb, an inquiry call-to-action] - Brand colors: [Deep charcoal background, warm cream text, one terracotta accent color] - Contact action: [A "Start Your Project" button linking to a contact email] </inputs> <task> Build a complete, self-contained single-page HTML homepage with the stated sections, using the brand colors, with placeholder colored blocks (labeled with a play-button icon) standing in for the 4 project thumbnails. </task> <constraints> - Output valid, self-contained HTML with inline or embedded CSS, no external dependencies or broken links. - Use the exact stated color palette, don't substitute different colors. - Make the showcase grid responsive so it doesn't break on a narrow screen. </constraints> <format> A single, complete HTML document that can be opened directly in a browser or previewed as a live artifact. </format>

You are a videographer building a private deliverables page for a finished client project. <context> A corporate client's final video is ready and you want a clean, branded download page instead of just emailing a raw file link. </context> <inputs> - Client and project: [Northfield Logistics, recruiting video] - Deliverables to list: [Final 3-minute video, a 15-second social cutdown, a vertical version for Instagram] - Download links: [Placeholder download buttons for each file] - Usage note: [Personal/internal use license, contact for expanded usage rights] </inputs> <task> Build a single-page HTML deliverables page listing each file with a short description, a placeholder download button, and the stated usage note at the bottom. </task> <constraints> - List each deliverable as its own labeled block with a distinct download button, not one generic "download all" link. - State the usage license note clearly near the bottom, not buried in fine print. - Output valid, self-contained HTML with embedded CSS. </constraints> <format> A single, complete HTML document ready to preview as a live artifact. </format>

You are a videographer building a landing page to showcase your demo reel to prospective clients. <context> You want a focused landing page with a single demo reel front and center, minimal distractions, built to convert visitors into inquiries. </context> <inputs> - Studio name and specialty: [Hollow Light Films, corporate and brand video] - Reel placeholder: [A large placeholder video block with a play icon, 2-minute reel] - Supporting proof points: [Worked with 3 named local brands, one client quote about turnaround speed] - Call to action: [A single "Book a Call" button, no secondary links competing for attention] </inputs> <task> Build a single-page HTML landing page with the reel placeholder as the visual focus, the proof points below it, and exactly one call-to-action button. </task> <constraints> - Include exactly one call-to-action button on the page, no competing links or navigation menu. - Place the reel placeholder above the fold, before any text content. - Output valid, self-contained HTML with embedded CSS, no external dependencies. </constraints> <format> A single, complete HTML document ready to preview as a live artifact. </format>

You are a videographer building a case study page for a completed brand video project. <context> You want a case study page that shows a prospective client the actual problem, process, and result of a past project, not just the finished video. </context> <inputs> - Client and project: [Northfield Roasters, 60-second brand commercial] - Challenge: [Needed to launch a seasonal product with a limited one-week shoot window and a tight $2,000 budget] - Process highlights: [One-day shoot at their cafe location, 2 talent extras, edited and delivered in 8 business days] - Result: [Client reported a stated increase in seasonal product mentions on social media after the video launched, placeholder metric: "40% increase in social mentions in the following month"] </inputs> <task> Build a single-page HTML case study with sections for Challenge, Process, and Result, using the stated details and placeholder metric, ending with a call to action to start a similar project. </task> <constraints> - Present the result metric as a clearly labeled client-reported figure, not implied as independently verified. - Structure the three sections (Challenge, Process, Result) so each is scannable in under 20 seconds. - Output valid, self-contained HTML with embedded CSS. </constraints> <format> A single, complete HTML document ready to preview as a live artifact. </format>

You are a videographer building a short email campaign to generate referrals and testimonials from past clients. <context> You have a list of past corporate and wedding clients who haven't been asked for a testimonial or referral yet, and want a simple two-email sequence to prompt both without sounding transactional. </context> <inputs> - Client segment: [Past corporate and wedding clients from the last 12 months, roughly 25 people] - Incentive offered for referrals: [$100 credit toward a future project for both the referrer and the new client] - Testimonial use: [Website case studies and Google reviews] - Sending cadence: [Email 1 now, Email 2 two weeks later only to non-responders] </inputs> <task> Write a two-email sequence: Email 1 asks for a short testimonial with 2 specific guiding questions, Email 2 (for non-responders) pivots to the referral offer with the credit amount stated clearly. </task> <constraints> - The guiding questions in Email 1 must be specific enough to produce a usable quote, not "how was your experience." - State the exact referral credit amount in Email 2, not "a nice discount." - Make clear Email 2 is only sent to people who didn't respond to Email 1, not the full list again. </constraints> <format> Two labeled emails (Email 1: Testimonial Ask, Email 2: Referral Offer), each with subject line, ready to load into an email tool. </format>