Claude Prompt Library

Webinar Scripts You Rehearse and Deliver Live

30 copy-paste prompts

Paste into Claude. Fill [PLACEHOLDERS]. Get spoken opens, teaching blocks, demo talk tracks, offer closes, Q and A, and the follow-up email. You still rehearse and deliver live. Not HTML. Not a slide deck.

In short: This page contains 30 copy-paste ready prompts, organized into 6 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Hand-curated and tested by the AI Academy team.

Louis Corneloup
By Louis Corneloup ยท Founder, Techpresso
Last updated ยทHand-curated & tested by the AI Academy team

Open

5 prompts

First Ninety Second Live Open

1/30

โœจ What it does

Claude writes five spoken first-90-second webinar opens for [WEBINAR TOPIC] with a hook, a one-line credibility beat, and the promise the teaching blocks must pay. You still rehearse two opens out loud and deliver the one that fits your mouth.

You are a webinar scriptwriter who writes the first 90 seconds a host can deliver live, not slide titles and not HTML. <context> I need spoken opens for a live webinar. Each open must hook late joiners, plant one promise the teaching blocks will pay, and work if someone is still joining audio. Do not write the teaching, the demo, or the offer. Written script only. </context> <inputs> - Webinar topic and unique angle: [WEBINAR TOPIC] - Who is in the room and why they came: [AUDIENCE] - The one outcome if they stay: [OUTCOME] - Teaching blocks I will actually cover: [BLOCK LIST] - Host voice: [WARM / DIRECT / CALM] - I have a waiting room and late joiners: [YES / NO] </inputs> <task> Write 5 first-90-second opens. For each: exact spoken words with pause marks, a 5-second late-joiner recap line, the unanswered promise, and which teaching block pays it. Rank the top 2 to rehearse first. Do not write block 2 or the CTA. </task> <constraints> - No welcome-everybody-thanks-for-being-here filler that lasts 40 seconds. - Do not resolve the promise in the open. - Every line must be speakable on the first rehearsal. - The tease must match a real block in [BLOCK LIST]. - This is a live webinar, not a YouTube open, not a VSL, and not HTML. </constraints> <format> Return a ranked table: spoken open, seconds, late-joiner line, paying block. Name the two I should rehearse and deliver first. </format>

๐Ÿ’ก

Pro tip: Say each open on a timer with your waiting-room music off. If you need a breath before the promise, cut words, do not talk faster.

Proof Before Welcome Open

2/30

โœจ What it does

Claude writes four proof-first webinar opens that put [PROOF I CAN SHOW] on screen before any welcome, then the first spoken line and an agenda tease. You still rehearse the proof line and deliver it live before you greet the room.

You are a webinar opener who starts on proof, not on a host greeting. <context> I need visual-first live opens that put [PROOF I CAN SHOW] on the shared screen in the first 20 seconds, then one spoken line and an agenda tease. Spoken script plus screen cue only. Not a full webinar and not HTML. </context> <inputs> - The proof I can show live: [PROOF I CAN SHOW] - Webinar topic: [WEBINAR TOPIC] - What attendees expect to hear first: [EXPECTED OPEN] - First teaching block this proof belongs to: [BLOCK ONE] - Screen I will share: [SLIDE / TAB / PRODUCT] - Spoken line after the proof: [8-20 SECONDS] </inputs> <task> Write 4 proof-before-welcome opens. For each: first screen, what I say while it is up, the first welcome sentence after, and the teaching-block title that later explains the proof. Do not write the demo after the reveal. </task> <constraints> - Do not invent proof I cannot show live. - No 60-second bio after the proof. - The spoken line cannot be anyway, thanks for joining. - Live webinar only. Not a recorded YouTube smash cut. Not HTML. </constraints> <format> Return first screen, spoken line, seconds, paying block. Pick two I should rehearse. </format>

๐Ÿ’ก

Pro tip: Have the proof tab ready before you unmute. A welcome slide while you hunt for the screenshot kills the open.

Agenda as Stakes Open

3/30

โœจ What it does

Claude writes a spoken agenda open for [WEBINAR TITLE] that names three teaching blocks as stakes, not a syllabus read-aloud. You still rehearse the map in one take and deliver it without looking down at the slide.

You are a webinar retention writer who turns a block list into a spoken open, not a slide dump. <context> I need 45 to 75 second spoken agenda opens that preview three teaching blocks as reasons to stay, including through the demo and into Q and A. I may put the same titles on a slide. Do not write the full script. Written lines only. Not HTML. </context> <inputs> - Webinar title: [WEBINAR TITLE] - Ordered blocks I will teach: [BLOCK LIST] - The block people usually zone out on: [RISKY BLOCK] - Audience: [AUDIENCE] - Voice: [DIRECT / WARM / DRY] - I will show an agenda slide: [YES / NO] </inputs> <task> Write 6 agenda-as-stakes opens. Each names three blocks as stakes or payoffs, not as a numbered syllabus. Flag [RISKY BLOCK] with a one-clause reason to stay. Give optional slide labels (max 4 words each). Do not write the body of any block. </task> <constraints> - Do not read every block if I listed more than five. Pick the three that hold. - No in this webinar we will cover filler. - Block names must match [BLOCK LIST] so the slide stays honest. - Not a YouTube chapter map and not a course outline. </constraints> <format> Return spoken open, seconds, three block promises, slide labels. Star two to rehearse and deliver. </format>

๐Ÿ’ก

Pro tip: Name blocks as payoffs, not labels. If the map sounds like a course outline, people open email.

Who Stays Who Leaves Open

4/30

โœจ What it does

Claude writes six who-this-is-for opens for [IDEAL ATTENDEE] that also name who should drop, plus one reason to stay. You still rehearse both lines and deliver the honest pair live.

You are a webinar opener who qualifies the room out loud so the right people lean in. <context> I need spoken opens that name [IDEAL ATTENDEE], name who this hour is not for, and give one reason to stay through the demo. Open only. Not a sales page and not HTML. </context> <inputs> - Ideal attendee: [IDEAL ATTENDEE] - Who should skip or drop: [NOT FOR] - Why staying pays: [STAY REASON] - Webinar topic: [WEBINAR TOPIC] - Tone: [KIND / BLUNT / CALM] - I will offer something later: [YES / NO] </inputs> <task> Write 6 who-stays-who-leaves opens (40 to 70 seconds). Each names [IDEAL ATTENDEE] in the first 15 seconds, names [NOT FOR] without insult, and lands [STAY REASON] before any bio. If [YES], do not pitch the offer in the open. Rank 3 that sound like a host, not a landing page. </task> <constraints> - Do not mock the people you send away. - Do not invent a persona I did not list. - No long origin story. - Live webinar spoken script only. Not HTML. Not a YouTube hook. </constraints> <format> Return spoken open, seconds, stay line, leave line. Star the two I should rehearse. </format>

๐Ÿ’ก

Pro tip: Say the leave line kindly and fast. If you apologize for five seconds after it, the stay line dies.

Contrarian Promise Open

5/30

โœจ What it does

Claude writes seven contrarian webinar opens for [CLAIM I WILL DEFEND] with a proof tease the first teaching block must pay. You still rehearse two claims and deliver only the line you would stand behind in chat.

You are a webinar opener who starts on a specific, defensible contrarian claim. <context> I need spoken cold opens that state [CLAIM I WILL DEFEND], tease proof, and point at the teaching block that argues it. Hooks plus honesty checks. Not a rant script and not HTML. </context> <inputs> - The claim I actually believe: [CLAIM I WILL DEFEND] - Who is in the room: [AUDIENCE] - Proof I will show later: [PROOF I HAVE] - Teaching block that defends the claim: [DEFENSE BLOCK] - Voice: [DIRECT / DRY / WARM] - Spoken length: [20-45 SECONDS] </inputs> <task> Write 7 contrarian opens that lead with [CLAIM I WILL DEFEND] in the first sentence. For each: exact words, a one-beat proof tease that points at [PROOF I HAVE] without explaining it, the block title for [DEFENSE BLOCK], and a note on who this would lose. Rank 3 that sound like a person, not a landing-page headline. </task> <constraints> - No empty shock (most webinars waste your time) without a concrete claim. - Do not invent proof I did not list. - Do not write the argument. Open only. - No thanks-for-coming throat clearing. - Honest enough that a chat question cannot call it bait. </constraints> <format> Return spoken line, seconds, proof tease, paying block, bait risk. Star the two I should rehearse and deliver. </format>

๐Ÿ’ก

Pro tip: The claim has to be one you can defend when chat pushes back. Drop any line you would not say to a buyer on a call.

Teaching Blocks

5 prompts

Three Block Teaching Script

6/30

โœจ What it does

Claude writes a three-block teaching script for [TOPIC] with spoken lines, a poll or chat check-in, and a bridge into the demo. You still rehearse each block on a timer and deliver it live without reading paragraphs.

You are a webinar teaching writer who scripts three live blocks a host can deliver, not a course module and not HTML. <context> I need a complete three-block teaching script as spoken lines with optional slide cues, one poll or chat check-in per block, and a bridge into the demo. Live webinar. Not a YouTube tutorial and not a slide deck file. </context> <inputs> - Topic and what they will leave able to do: [TOPIC] - Audience and skill level: [AUDIENCE] - Target teaching time before demo: [MINUTES] - The three blocks I will actually teach: [BLOCK LIST] - Host voice: [VOICE] - Poll or chat I can run: [POLL / CHAT / NONE] - Demo that follows: [DEMO PROMISE] </inputs> <task> Write the three-block script as a table (minutes, spoken lines, slide or screen cue, poll or chat line). Open each block with a one-sentence stake. Teach only [BLOCK LIST]. Put a check-in before the hardest block. Close block three with a spoken bridge into [DEMO PROMISE]. Do not write the demo clicks or the offer. </task> <constraints> - Spoken lines must sound conversational. No jargon dumps. - Word count must fit [MINUTES] at a live pace, not a read-aloud essay. - Do not invent blocks I did not list. - No HTML. No slide markup beyond a short cue. - Not a VSL and not a YouTube chapter script. </constraints> <format> Return the script table, a rehearsal timer per block, the check-in line, and the one minute most likely to lose the room. </format>

๐Ÿ’ก

Pro tip: Time each block standing up. If block two runs long in rehearsal, cut a story, do not speed through the demo.

Named Framework Teach Block

7/30

โœจ What it does

Claude writes one named-framework teaching block for [FRAMEWORK NAME] with a definition, three uses, and a check-in question. You still rehearse the three uses and deliver them from notes, not a wall of text.

You are a webinar teaching writer who turns a working method into one live block. <context> I need a single teaching block that ships [FRAMEWORK NAME] so attendees can steal the name and the three parts. Spoken script. Not a white paper, not a carousel, not HTML. </context> <inputs> - Framework name I will stand behind: [FRAMEWORK NAME] - The three parts, in my words: [PART A / PART B / PART C] - A real situation it explained: [SITUATION] - Audience: [AUDIENCE] - Voice: [TEACHER / PEER / BLUNT] - Time I can spend on this block: [MINUTES] </inputs> <task> Write one live teaching block that fits [MINUTES]. Structure: 15-second stake, one-sentence definition, three parts with a spoken example each tied to [SITUATION], when NOT to use it, then a chat check-in question. Mark pause points so I can look at the room. </task> <constraints> - Do not invent a fourth part or a fake origin story. - Do not write the rest of the webinar. - No academic citations unless I pasted them. - Speakable. Not HTML. Not slide paragraphs. </constraints> <format> Return the spoken block with timestamps, the check-in question, and a 5-line speaker note card I can glance at. </format>

๐Ÿ’ก

Pro tip: Use the names you already say on sales calls. If the framework needs a footnote, attendees will not repeat it in chat.

Mistake Then Fix Block

8/30

โœจ What it does

Claude writes a mistake-then-fix teaching block on [COMMON MISTAKE] with the failure, the cost, and the fix you will demo next. You still rehearse the failure story and deliver the fix in your own words live.

You are a webinar teaching writer who autopsies one mistake without humiliating the room. <context> I need one teaching block that names [COMMON MISTAKE], shows the cost, and hands the fix to the demo. Spoken lines. Not a roast and not HTML. </context> <inputs> - The mistake: [COMMON MISTAKE] - Why it happens: [CAUSE] - What it costs: [COST] - The fix I will show in the demo: [FIX] - Audience: [AUDIENCE] - Voice: [KIND / DRY] - Block length: [MINUTES] </inputs> <task> Write a [MINUTES] spoken block. Open by naming [COMMON MISTAKE] as something [AUDIENCE] might still be doing. Cover [CAUSE] and [COST]. Walk [FIX] at a teaching level only, then hand the clicks to the demo with a one-sentence bridge. Add one chat prompt that asks for their version of the mistake. </task> <constraints> - No dunking and no you-idiot tone. - Do not invent a horror story I did not provide. - Do not write the full demo talk track. - Keep the fix specific to [FIX]. - Live webinar script only. Not HTML. </constraints> <format> Return spoken script with timestamps, the demo handoff line, and a dunk-risk note (low/med) I will edit before I deliver. </format>

๐Ÿ’ก

Pro tip: Use a mistake you have made or seen this month. If the autopsy only dunks on the room, rewrite the open in first person.

Story Then Rule Block

9/30

โœจ What it does

Claude writes a story-then-rule teaching block from [STORY NOTES] that lands one rule attendees can use before the demo. You still rehearse the story out loud and deliver the rule without turning it into a speech.

You are a webinar story teacher who starts mid-scene and stops after one rule. <context> I need a teaching block from [STORY NOTES] only. Open inside the charged moment. Land one rule they can use before the demo. Spoken script. Not a memoir and not HTML. </context> <inputs> - Raw notes: [STORY NOTES] - What I got wrong or saw go wrong: [FAILURE] - The one rule I will stand behind: [RULE] - Audience: [AUDIENCE] - Details I will not share: [OFF LIMITS] - Voice: [QUIET / BLUNT] - Block length: [MINUTES] </inputs> <task> Write a [MINUTES] spoken block. First line is action or dialogue from [STORY NOTES], not a date. Honor [OFF LIMITS]. The turn is visible in 4 to 8 spoken sentences. State [RULE] in one sentence they can type in chat. Close with a one-line handoff to the next block or demo. Do not write the offer. </task> <constraints> - Do not invent dialogue, numbers, or a happier ending. - First line cannot be I want to share a story. - No TED closer. One rule only. - Not a YouTube storytime. Not HTML. </constraints> <format> Return the spoken block with pause marks, the one-sentence rule, and a chat line that invites their similar moment. </format>

๐Ÿ’ก

Pro tip: Start mid-scene, not last quarter we learned. If the first sentence is a calendar, rewrite before rehearsal.

Block Change Recap Bridge

10/30

โœจ What it does

Claude writes recap bridges for each break in [BLOCK LIST] so the next teaching block opens on a new reason to stay. You still rehearse those bridges and deliver them at the real marks on your run of show.

You are a webinar retention writer who writes mid-hour recap bridges at block changes, not full blocks. <context> I need 20 to 40 second spoken bridges at each break in [BLOCK LIST]. I will also use these as the spoken lead-in if I change slides. Do not rewrite the blocks. Written script only. Not HTML. </context> <inputs> - Ordered teaching blocks: [BLOCK LIST] - Webinar topic: [WEBINAR TOPIC] - Typical drop for me: [WHERE PEOPLE LEAVE] - Voice: [SAME AS OPEN / SLIGHTLY SHARPER] - What comes after the last block: [DEMO / OFFER / Q AND A] </inputs> <task> Write one recap bridge per block break. For each: spoken line (under 40 seconds), what I recap in one clause, the new loop, and the next block title as I should say it. Add a stronger rehook at [WHERE PEOPLE LEAVE] if I named one. Skip writing the block content. </task> <constraints> - Bridges only. Not a full script. - No empty stay with me. - The loop must be paid by the next real block I listed. - Block titles must stay honest to [BLOCK LIST]. - Not a YouTube mid-roll cliff. </constraints> <format> Return a table: after block, spoken bridge, loop, next title. Star the two riskiest breaks I should rehearse first. </format>

๐Ÿ’ก

Pro tip: Park the recap on the slide change, not after a dead pause. Dead air is when people open Slack.

Demo

5 prompts

Click Path Demo Talk Track

11/30

โœจ What it does

Claude writes a click-by-click demo talk track for [SOFTWARE TASK] timed to the shared screen, with pause marks if a click lags. You still rehearse the clicks on a clean account and deliver the track live while you share.

You are a webinar demo writer who times spoken lines to live clicks, not a software course and not HTML. <context> I need a click-by-click talk track for [SOFTWARE TASK] inside a live webinar. Pause marks, expected screen, and a line if the UI is slow. Not a 45-minute tutorial and not a recorded YouTube insert. </context> <inputs> - Task: [SOFTWARE TASK] - App and version: [APP] - What attendees should be able to repeat: [OUTCOME] - Viewer level: [BEGINNER / INTERMEDIATE] - Minutes I can spend: [MINUTES] - Clicks I will actually do live: [CLICK PATH] - UI I must keep clear of my face: [SAFE ZONE NOTES] </inputs> <task> Write a demo talk track: timestamp vs spoken line, click or key, expected screen, pause if lag. Mark one common error and a 10-second recovery line. If the honest click path is longer than [MINUTES], say so and cut clicks or add spoken time. Do not write the offer. </task> <constraints> - No skipped clicks. Assume they follow live. - Do not invent UI that [APP] does not have. Mark [VERIFY] if unsure. - Spoken lines stay short so I can click without reading a paragraph. - No HTML page. No recorded-video B-roll cues. </constraints> <format> Return the click table, the recovery line, and the one click I should rehearse twice. </format>

๐Ÿ’ก

Pro tip: Rehearse on a clean account with the same zoom level you will use live. A click you cannot find in rehearsal will freeze the room.

Live Build Checkpoint Script

12/30

โœจ What it does

Claude writes a live-build demo script for [WHAT I WILL BUILD] with spoken goals, checkpoints, and a recovery line if you go long. You still rehearse the build once cold and deliver only the steps you can finish live.

You are a webinar demo writer who scripts a live build with checkpoints a host can abandon cleanly. <context> I will build [WHAT I WILL BUILD] live. I need spoken goals, checkpoints, and a recovery if I go long. Written script. Not HTML. Not a recorded timelapse. </context> <inputs> - What I will build: [WHAT I WILL BUILD] - Starting point on screen: [START STATE] - Checkpoints I can hit: [CHECKPOINTS] - Finished backup I can switch to: [BACKUP TAB / NONE] - Minutes: [MINUTES] - Audience level: [AUDIENCE] - Voice: [CALM / PLAY-BY-PLAY] </inputs> <task> Write a live-build script with a 15-second goal line, spoken lines at each [CHECKPOINTS] item, a narrated skip if a checkpoint slips, and a close that still teaches if I jump to [BACKUP TAB / NONE]. Include one chat prompt at the halfway checkpoint. Do not write teaching blocks or the offer. </task> <constraints> - Do not invent a finished result I cannot show. - If [BACKUP TAB / NONE] is NONE, write a verbal recap close instead of a fake finish. - Keep lines short enough to speak while typing. - Live webinar only. </constraints> <format> Return the timed script, skip lines, backup close, and the checkpoint I should rehearse first. </format>

๐Ÿ’ก

Pro tip: Rehearse once with a stopwatch and a finished backup tab. If minute 12 is still setup, cut the build before you go live.

Before After Screen Reveal

13/30

โœจ What it does

Claude writes a before-and-after screen demo script from [BEFORE STATE] to the after you can show, with the spoken reveal line. You still rehearse the switch and deliver the reveal only after the after is on screen.

You are a webinar demo writer who scripts a before-and-after reveal on a shared screen. <context> I will show [BEFORE STATE] then the after I can actually show. I need spoken lines for the hold, the switch, and the reveal. Not a case-study PDF and not HTML. </context> <inputs> - Before they can see: [BEFORE STATE] - After I can show live: [AFTER STATE] - The one change that matters: [THE MOVE] - Constraint I must name: [CONSTRAINT] - Minutes: [MINUTES] - Voice: [CALM / SHARP] </inputs> <task> Write a [MINUTES] reveal script: 20 seconds on [BEFORE STATE] with what is wrong, a spoken setup for the switch, the exact reveal sentence once [AFTER STATE] is up, then 3 short lines on [THE MOVE] and [CONSTRAINT]. Add a chat question that asks which side they are on today. Do not invent a second after. </task> <constraints> - Do not invent a bigger after than I listed. - Do not pitch the offer during the reveal. - The reveal sentence cannot start until the after is on screen. - Spoken script only. Not HTML. Not a YouTube smash cut. </constraints> <format> Return before lines, switch cue, reveal sentence, after lines, and a rehearsal note for the tab switch. </format>

๐Ÿ’ก

Pro tip: Put before and after in two tabs. Reveal after the after is visible. Talking over a loading spinner is not a reveal.

Demo Failure Recovery Lines

14/30

โœจ What it does

Claude writes failure-recovery demo lines for [LIKELY FAIL] so a live miss becomes a teaching beat instead of a freeze. You still rehearse the recovery once and deliver it if the click actually breaks.

You are a webinar demo writer who scripts recovery lines for a live miss. <context> [LIKELY FAIL] might happen on the shared screen. I need spoken recoveries that turn the miss into a teaching beat. Not a joke reel and not HTML. </context> <inputs> - Likely fail: [LIKELY FAIL] - What I can still show: [BACKUP] - The teaching point if it breaks: [TEACHING POINT] - Voice: [CALM / DRY] - I have a moderator: [YES / NO] - Seconds I can spend recovering: [15-40] </inputs> <task> Write 6 recovery scripts. Each: first sentence (no panic), what I do with the screen, the teaching beat using [TEACHING POINT], and the line that restarts the planned path via [BACKUP]. If [YES], add one sentence I can throw to the moderator. Keep each recovery inside [15-40] seconds. </task> <constraints> - No sorry-this-never-happens loops. - Do not invent a funny story. - Do not abandon the webinar or jump to the offer. - Speakable while you click. Not HTML. </constraints> <format> Return 6 recoveries with seconds and a restart line. Star the two I should rehearse out loud. </format>

๐Ÿ’ก

Pro tip: Rehearse the fail on purpose once. If you have never said the recovery out loud, you will apologize for 40 seconds live.

Follow Along Pace Script

15/30

โœจ What it does

Claude writes a follow-along demo script for [TOOL] with slower spoken steps, a wait-for-chat beat, and a catch-up line. You still rehearse the pace and deliver it while watching chat for lost attendees.

You are a webinar demo writer who paces a follow-along so live attendees can click with you. <context> I need a slower talk track for a follow-along on [TOOL]. Wait-for-chat beats and a catch-up line. Spoken script. Not a self-paced course and not HTML. </context> <inputs> - Tool: [TOOL] - Steps they will do with me: [STEPS] - Minutes: [MINUTES] - Chat phrase that means they are lost: [LOST PHRASE] - Catch-up I can offer: [RECORDING / SCREENSHOT / SKIP] - Voice: [PATIENT / DIRECT] </inputs> <task> Write a follow-along script for [STEPS] that fits [MINUTES]. After each step: a wait line, what I watch for in chat, and a catch-up using [CATCH-UP I can offer]. Include one line I say if [LOST PHRASE] appears. End with a 10-second recap of what they now have on screen. Do not write the offer. </task> <constraints> - Do not skip a step they need to stay in sync. - Do not invent tool features. - Waits must be real pauses in the script, not I will go fast. - Live webinar. Not HTML. Not a YouTube tutorial. </constraints> <format> Return the stepped script with wait marks, the lost-phrase line, and the recap. Note the step most likely to desync the room. </format>

๐Ÿ’ก

Pro tip: Build in a real wait. If you say I will give you a second and immediately click, the follow-along people are gone.

These prompts give you the what. Tutorials give you the why.

Learn when to use extended thinking, how to build Claude Projects, and workflows that compound. 300+ tutorials and growing.

Try AI Academy Free

Offer

5 prompts

Teach to Offer Spoken Bridge

16/30

โœจ What it does

Claude writes five teaching-to-offer bridges for [OFFER NAME] that recap the last block, then make the ask without a hard cut. You still rehearse the bridge and deliver it only after the teaching actually landed.

You are a webinar offer writer who bridges from teaching into an ask without a hard cut. <context> I just finished teaching or a demo. I need spoken bridges into [OFFER NAME]. Bridge plus first ask sentence. Not a landing page and not HTML. </context> <inputs> - Offer name: [OFFER NAME] - What they just learned or saw: [LAST BLOCK] - Who the offer is for: [BUYER] - Who should skip: [NOT FOR] - Voice: [CALM / DIRECT] - I already showed a price slide: [YES / NO] </inputs> <task> Write 5 bridges (30 to 50 seconds). Each recaps [LAST BLOCK] in one sentence, names why [OFFER NAME] is the next step for [BUYER], names [NOT FOR] in one clause, then the first ask sentence. If [NO], do not say the price in the bridge. Rank 3 that do not sound like a bait and switch. </task> <constraints> - Do not invent bonuses or prices I did not list. - Do not rewrite the teaching. - No limited-time scream in the bridge. - Spoken live webinar script. Not a VSL cut. Not HTML. </constraints> <format> Return spoken bridge, seconds, first ask line, bait risk. Star two I should rehearse and deliver. </format>

๐Ÿ’ก

Pro tip: Recap a result they just saw, not a new benefit. A hard cut from teaching to price is when people leave.

Offer Stack Live Pitch

17/30

โœจ What it does

Claude writes a spoken offer-stack pitch for [OFFER] with what they get, what it costs, and who should skip the buy. You still rehearse the stack out loud and deliver the price only when you can say it clean.

You are a webinar offer writer who speaks a stack a host can deliver live, not a sales page. <context> I need a spoken offer-stack pitch for [OFFER]. What they get, what it costs, who should skip. Written script. Not HTML and not a checkout page. </context> <inputs> - Offer and what is in it: [OFFER] - Price and terms I can say: [PRICE] - Bonuses I will actually give: [BONUSES OR NONE] - Who should buy: [BUYER] - Who should skip: [NOT FOR] - Guarantee I can stand behind: [GUARANTEE OR NONE] - Voice: [PLAIN / WARM] - Minutes I can spend: [MINUTES] </inputs> <task> Write a [MINUTES] spoken pitch. Order: who it is for, the stack in the order I would unwrap it, [PRICE] in a full sentence, [GUARANTEE OR NONE], [NOT FOR], then the next action (URL or chat keyword I will name). If a bonus is NONE, do not invent one. Include a 10-second version I can use if I am short on time. </task> <constraints> - Do not invent price, bonuses, or proof. - Do not dunk on people who will not buy. - No fake countdown unless I put a real [DEADLINE] in the next prompt. - Speakable. Not HTML. Not a landing-page dump. </constraints> <format> Return the full spoken pitch with timestamps, the 10-second cut, and the exact price sentence I should rehearse first. </format>

๐Ÿ’ก

Pro tip: Say the price in rehearsal until your face does not change. If you flinch in the bedroom, you will flinch on camera.

Objection Then Ask Close

18/30

โœจ What it does

Claude writes pre-ask objection lines for [TOP OBJECTION] that name the doubt, answer it, then make the live ask. You still rehearse the answer and deliver the ask after you have handled the real doubt.

You are a webinar closer who handles one real objection out loud, then asks. <context> I need spoken pre-ask lines for [TOP OBJECTION]. Name it, answer it, ask. Not a FAQ page and not HTML. </context> <inputs> - Objection in their words: [TOP OBJECTION] - Honest answer I can stand behind: [ANSWER] - Proof I can name: [PROOF I HAVE] - The ask after: [ASK] - Second objection if I have one: [SECOND OR NONE] - Voice: [CALM / DIRECT] </inputs> <task> Write 5 objection-then-ask scripts (40 to 70 seconds). Each quotes or tightly paraphrases [TOP OBJECTION], answers with [ANSWER] and only [PROOF I HAVE], then delivers [ASK] in one sentence. If [SECOND OR NONE] exists, add a 15-second optional extra. Flag any line that overclaims. </task> <constraints> - Do not invent case studies or numbers. - Do not mock the objection. - The ask must come after the answer, not before. - Live spoken script. Not a help-center article. Not HTML. </constraints> <format> Return each script with the quoted objection, the answer, the ask, and an overclaim flag. Star two to rehearse. </format>

๐Ÿ’ก

Pro tip: Name the objection the way chat types it. If you polish it into a straw man, the real doubt stays in the room.

Live Bonus Deadline Close

19/30

โœจ What it does

Claude writes a bonus-and-deadline close for [DEADLINE] with spoken bonus lines and one honest scarcity beat. You still rehearse the close and deliver only the deadline you will actually keep.

You are a webinar closer who writes an honest bonus-and-deadline close. <context> I need spoken close lines for a real [DEADLINE] and bonuses I will actually deliver. Not fake scarcity and not HTML. </context> <inputs> - Real deadline and why it is real: [DEADLINE] - Live-only bonus I will honor: [LIVE BONUS OR NONE] - Bonus that also exists later: [ALWAYS ON BONUS OR NONE] - Offer name: [OFFER] - Ask: [ASK] - Voice: [CALM / URGENT] </inputs> <task> Write 4 close scripts (35 to 60 seconds). Each names [OFFER], speaks [LIVE BONUS OR NONE] only if it is real, states [DEADLINE] with the reason it is real, and ends on [ASK]. If a bonus is NONE, skip it. Write one extra close with no deadline language for if I decide not to use scarcity. </task> <constraints> - Do not invent a deadline or a bonus. - Do not call an always-on bonus live-only. - No scream punctuation. - Spoken webinar close. Not an email. Not HTML. </constraints> <format> Return 4 timed closes plus the no-scarcity alt. Mark any line that would be a lie if the replay page matches the live page. </format>

๐Ÿ’ก

Pro tip: If the bonus will also sit on the replay page, do not call it live-only. Chat will screenshot it.

Soft Ask and Hard Ask Pair

20/30

โœจ What it does

Claude writes paired soft and hard offer closes for [OFFER] so you can match the room after the demo. You still rehearse both closes and deliver the one that fits how chat is reacting.

You are a webinar closer who writes a soft ask and a hard ask for the same offer so the host can match the room. <context> I need paired spoken closes for [OFFER]. Soft = next step without pressure. Hard = clear buy ask. Same facts. Live script. Not HTML. </context> <inputs> - Offer: [OFFER] - Price I can say: [PRICE OR LATER] - Soft next step: [SOFT STEP] - Hard next step: [HARD STEP] - Chat signal I treat as warm: [WARM SIGNAL] - Chat signal I treat as cold: [COLD SIGNAL] - Voice: [WARM / DIRECT] </inputs> <task> Write 3 pairs. Each pair: a 25-40 second soft close aimed at [SOFT STEP], a 25-40 second hard close aimed at [HARD STEP], and a one-line rule for when to use which based on [WARM SIGNAL] and [COLD SIGNAL]. Keep facts identical. If [PRICE OR LATER] is LATER, the hard close still must not invent a number. </task> <constraints> - Soft cannot hide that an offer exists. - Hard cannot bully or shame. - Do not invent urgency. - Spoken live lines only. Not a landing page. Not HTML. </constraints> <format> Return pairs labeled Soft/Hard with seconds and the chat rule. Star the pair I should rehearse first. </format>

๐Ÿ’ก

Pro tip: Decide in the last teaching minute, not while the price slide loads. Rehearse both so either one is in your mouth.

Q and A

5 prompts

Pre Submitted Answer Pack

21/30

โœจ What it does

Claude writes answer scripts for pre-submitted questions on [WEBINAR TOPIC] with a 30-second version and a 90-second version. You still rehearse the short answers and deliver the long ones only if the queue is thin.

You are a webinar Q and A writer who scripts answers a host can deliver live from pre-submitted questions. <context> I have or expect pre-submitted questions on [WEBINAR TOPIC]. I need a 30-second answer and a 90-second answer for each. Spoken. Not a blog FAQ and not HTML. </context> <inputs> - Webinar topic: [WEBINAR TOPIC] - Questions I already have: [QUESTION LIST] - Extra questions I expect: [EXPECTED QUESTIONS] - Answers I can stand behind: [ANSWER NOTES] - What I will not discuss live: [OFF LIMITS] - Voice: [PLAIN / WARM] </inputs> <task> For each question in [QUESTION LIST] and [EXPECTED QUESTIONS], write: a 30-second spoken answer, a 90-second spoken answer that uses only [ANSWER NOTES], and a park line if it hits [OFF LIMITS]. Rank the five I should rehearse first. Do not invent facts I did not give. Mark [VERIFY] on thin answers. </task> <constraints> - Do not open a new teaching block inside an answer. - Do not pitch the offer unless the question is about the offer. - Honor [OFF LIMITS]. - Live spoken answers. Not HTML. Not an email. </constraints> <format> Return a table: question, 30s answer, 90s answer, park line, verify flag. Star five to rehearse. </format>

๐Ÿ’ก

Pro tip: Print the 30-second lines. If you always deliver the 90-second version, you will skip the live queue.

Live Queue Thirty Second Answers

22/30

โœจ What it does

Claude writes live-queue answer scripts for [LIKELY QUESTIONS] with a one-sentence answer, a proof beat, and a park line. You still rehearse the one-sentence versions and deliver them without opening a new lesson.

You are a webinar Q and A writer who keeps live-queue answers short enough to clear the list. <context> I need 30-second spoken answers for [LIKELY QUESTIONS] with a one-sentence core, an optional proof beat, and a park line if it is too big. Not a second webinar. Not HTML. </context> <inputs> - Likely questions: [LIKELY QUESTIONS] - Proof I can name in one clause: [PROOF I HAVE] - Deep items I will park: [PARK TOPICS] - Offer I may mention only if asked: [OFFER OR NONE] - Voice: [DIRECT / WARM] - Moderator will read questions: [YES / NO] </inputs> <task> For each item in [LIKELY QUESTIONS], write: a one-sentence answer, a 20-second proof beat using only [PROOF I HAVE], a park line if it matches [PARK TOPICS], and a thank-you-to-name line I can use if the moderator read it. If [OFFER OR NONE] is NONE, never pitch. </task> <constraints> - One question, one answer. No stacked lessons. - Do not invent proof. - Do not argue with the attendee. - Spoken live. Not a help doc. Not HTML. </constraints> <format> Return question, one-sentence answer, proof beat, park line. Mark the three I should rehearse until they are automatic. </format>

๐Ÿ’ก

Pro tip: Answer in one breath, then stop. A live queue dies when every answer becomes teaching block four.

Hostile Question Redirect

23/30

โœจ What it does

Claude writes redirect scripts for a hostile or off-topic question on [SENSITIVE TOPIC] that stay calm and park the fight. You still rehearse the redirect once and deliver it if that question actually lands.

You are a webinar Q and A writer who redirects a hostile or off-topic question without a fight. <context> Someone may push on [SENSITIVE TOPIC] or go off-topic. I need calm spoken redirects I can deliver live. Not a roast and not HTML. </context> <inputs> - Sensitive or off-topic area: [SENSITIVE TOPIC] - What I will say that is true: [TRUE LINE] - What I will not debate live: [OFF LIMITS] - Parking lot I can name: [FOLLOW UP CHANNEL] - Voice: [CALM / FIRM] - I have a moderator who can mute: [YES / NO] </inputs> <task> Write 6 redirect scripts (20 to 40 seconds). Each: acknowledge without agreeing to a fight, say [TRUE LINE], decline [OFF LIMITS] in one clause, and park to [FOLLOW UP CHANNEL] or the next question. If [YES], add one sentence I can say to the moderator. Rank by calm first, firm second. Do not write a takedown. </task> <constraints> - No sarcasm and no well-actually open. - Do not invent facts to win. - Do not pitch the offer as the redirect. - Spoken live. Not a community-guidelines page. Not HTML. </constraints> <format> Return spoken redirect, seconds, park line, tone (calm/firm). Star two I should rehearse once out loud. </format>

๐Ÿ’ก

Pro tip: Rehearse once with a friend who is rude on purpose. If your first word is well actually, rewrite the open.

Parking Lot to Email Lines

24/30

โœจ What it does

Claude writes parking-lot lines that move [DEEP QUESTIONS] into the follow-up email without sounding like a dodge. You still rehearse those lines and deliver them when the clock says stop teaching.

You are a webinar Q and A writer who parks a deep question into the follow-up email without sounding like a dodge. <context> I will run out of live time. I need spoken parking-lot lines for [DEEP QUESTIONS] that name the follow-up email. Not a brush-off and not HTML. </context> <inputs> - Deep questions I should not fully answer live: [DEEP QUESTIONS] - What the follow-up email will actually include: [EMAIL CONTENTS] - When I will send it: [SEND TIME] - Voice: [WARM / DIRECT] - I can take one more live question after parking: [YES / NO] </inputs> <task> Write 5 parking-lot scripts (15 to 30 seconds). Each names the question type from [DEEP QUESTIONS], says why the email is the better place, names [EMAIL CONTENTS] and [SEND TIME], and thanks the asker. If [YES], add a line that invites one shorter question. Do not pretend the email will answer something I did not list. </task> <constraints> - Do not invent a resource I will not send. - Do not say I will get back to you with no vehicle. - Do not open the deep answer live after parking it. - Spoken live lines. Not the email itself. Not HTML. </constraints> <format> Return spoken line, seconds, what I promised in the email. Star two I should rehearse at the 5-minute warning. </format>

๐Ÿ’ก

Pro tip: Name what you will send and when. I will get back to you is a dodge. The recap will cover that question is a plan.

Quiet Chat Seed Questions

25/30

โœจ What it does

Claude writes seed questions and host lines for [TEACHING POINTS] so a quiet chat still gets a real Q and A. You still rehearse the seeds with your moderator and deliver one if the queue stays empty.

You are a webinar Q and A writer who seeds a quiet room so Q and A still happens. <context> Chat may stay empty after teaching. I need seed questions tied to [TEACHING POINTS] plus host lines if I have to ask myself. Spoken. Not fake engagement bait and not HTML. </context> <inputs> - Teaching points I can answer: [TEACHING POINTS] - Audience: [AUDIENCE] - Questions I hope they ask: [HOPEFUL QUESTIONS] - Moderator can drop a seed: [YES / NO] - Voice: [PEER / TEACHER] </inputs> <task> Write 8 seed questions a moderator or attendee could paste, each tied to [TEACHING POINTS] or [HOPEFUL QUESTIONS]. For each: the seed text, a 30-second spoken answer, and a host line I say if I have to introduce it (I got this a lot in registration). Write 2 host-only lines if the queue stays at zero. Do not invent a person who asked. </task> <constraints> - Seeds must be questions I can actually answer from [TEACHING POINTS]. - No comment if you agree bait. - Do not pitch the offer inside a seed unless the point was the offer. - Live webinar. Not HTML. Not a survey. </constraints> <format> Return numbered seeds with answers and host intros. Star the two the moderator should have ready. </format>

๐Ÿ’ก

Pro tip: Hand the seeds to the moderator before you go live. A host answering a question nobody asked looks like a skit.

Most people use 10% of Claude. Tutorials unlock the rest.

AI Academy: 300+ hands-on tutorials on Claude, ChatGPT, Midjourney, and 50+ AI tools. New tutorials added every week.

Start Your Free Trial

Follow-up

5 prompts

Same Day Thank You Email

26/30

โœจ What it does

Claude writes a same-day thank-you email for [WEBINAR TITLE] with a recap, the replay promise, and a single next step. You still rehearse the recap against what you said live, then deliver the send the same day.

You are a webinar follow-up writer who drafts the same-day thank-you email, not a newsletter and not HTML. <context> I just delivered [WEBINAR TITLE] live. I need a thank-you email: recap, replay promise, one next step. Plain text I can paste into my ESP. Not a landing page. </context> <inputs> - Webinar title: [WEBINAR TITLE] - Three things I actually taught: [TAUGHT] - Replay status: [LIVE NOW / COMING AT TIME] - Single next step: [NEXT STEP] - Offer I may mention once: [OFFER OR NONE] - Voice: [WARM / PLAIN] - Words I never use: [BANNED PHRASES] </inputs> <task> Write 2 thank-you emails (120-180 words) with subject lines (under 45 characters) and preview text (under 90). Recap only [TAUGHT]. State [REPLAY STATUS] honestly. One CTA for [NEXT STEP]. If [OFFER OR NONE] is NONE, no pitch. If it exists, one sentence late. No HTML. Mark [VERIFY] on any recap that is not in [TAUGHT]. </task> <constraints> - Do not invent a teaching point I did not list. - Do not write a 5-email sequence here. - No thrilled to recap or unlock your potential. - You write the email. I still send it after I check the recap against the live hour. </constraints> <format> Return subject, preview, body for Email A and Email B, plus a one-line note on which recap is safer. </format>

๐Ÿ’ก

Pro tip: Write the recap from your run of show, not from the promo page. If you promise a replay that is not up, wait an hour.

Replay and Offer Email

27/30

โœจ What it does

Claude writes a replay-plus-offer email around [REPLAY LINK] that restates the teaching, then repeats the offer without a new pitch. You still rehearse the offer paragraph and deliver the email once the replay is actually up.

You are a webinar follow-up writer who pairs a working replay with the same offer they heard live. <context> I need one email that sends [REPLAY LINK] and restates [OFFER] without a new pitch. Plain text. Not HTML. Not a new VSL. </context> <inputs> - Replay URL or placeholder: [REPLAY LINK] - How long the replay stays up: [REPLAY WINDOW] - Offer as I said it live: [OFFER] - Price and next action: [PRICE AND ASK] - One teaching they should rewatch: [REWATCH BEAT] - Voice: [DIRECT / WARM] </inputs> <task> Write 2 emails (140-200 words) with subject and preview. Open on [REWATCH BEAT] or the replay, not on I hope you enjoyed. Put [REPLAY LINK] early. Restate [OFFER] in the same facts as live. State [REPLAY WINDOW] honestly. If the link is a placeholder, write [PASTE REPLAY URL] and do not invent a domain. </task> <constraints> - Do not invent a new bonus or a new deadline. - Do not write HTML or buttons. Tell me where a link goes in brackets. - Do not recap the whole hour. - I still send this only after the replay plays. </constraints> <format> Return subject, preview, body for both, and a checklist: link works, window is true, offer matches live. </format>

๐Ÿ’ก

Pro tip: Paste the real replay URL before you send. A button that 404s is worse than sending an hour late.

No Show Catch Up Email

28/30

โœจ What it does

Claude writes a no-show catch-up email for [WEBINAR TITLE] with the one teaching they missed and a replay CTA. You still rehearse the subject line out loud, then deliver the email to the no-show list.

You are a webinar follow-up writer who writes a no-show catch-up, not a guilt trip. <context> They registered for [WEBINAR TITLE] and missed it. I need an email with one teaching, the replay, and one next step. Plain text. Not HTML. </context> <inputs> - Webinar title: [WEBINAR TITLE] - The one teaching worth the replay: [ONE TEACHING] - Replay link status: [REPLAY LINK OR COMING] - Offer they would have heard: [OFFER OR NONE] - Voice: [KIND / DIRECT] - What I will not say: [NO GUILT LINE] </inputs> <task> Write 2 no-show emails (110-170 words) with subject and preview. Open on [ONE TEACHING], not sorry you missed it as the only hook. Give [REPLAY LINK OR COMING] honestly. If [OFFER OR NONE] exists, one sentence. Never use [NO GUILT LINE] or a you-missed-out close. Include a 6-word subject alt that does not say missed. </task> <constraints> - Do not invent the recording if it is not ready. - Do not write a full recap of all blocks. - No shame. No you had to be there. - Plain email. Not HTML. Not a landing page. </constraints> <format> Return both emails plus the 6-word subject alt. Tell me which list this must NOT go to (attendees who stayed). </format>

๐Ÿ’ก

Pro tip: Send to no-shows only. If you blast attendees the same copy, people who stayed feel like they were absent.

Buyer Versus Attendee Split

29/30

โœจ What it does

Claude writes two follow-up emails for [OFFER], one for attendees who bought and one for attendees who did not. You still rehearse both versions and deliver the right list after you export the room.

You are a webinar follow-up writer who splits buyers from attendees who did not buy. <context> I need two emails after the live offer for [OFFER]: one for people who bought, one for people who did not. Plain text. Not HTML. Not a CRM lecture. </context> <inputs> - Offer they heard: [OFFER] - What buyers get next: [ONBOARDING STEP] - What non-buyers can still do: [NEXT STEP] - Deadline if real: [DEADLINE OR NONE] - Replay link: [REPLAY LINK] - Voice: [WARM / PLAIN] </inputs> <task> Write Email Bought (90-140 words): thanks, [ONBOARDING STEP], what happens in the next 48 hours, no more pitch. Write Email Did Not Buy (120-180 words): one recap, [REPLAY LINK], [NEXT STEP], and [DEADLINE OR NONE] only if real. Give subjects and preview text for both. Do not mix the lists in the copy. </task> <constraints> - Do not thank a non-buyer as if they paid. - Do not upsell the buyer in this email. - Do not invent a deadline. - Plain text. Not HTML. </constraints> <format> Return both emails labeled BOUGHT and DID NOT BUY, with a one-line send rule for the export. </format>

๐Ÿ’ก

Pro tip: Export buyers before you send. A thanks-for-buying note to someone who did not buy is a trust leak.

Three Email Post Webinar Nurture

30/30

โœจ What it does

Claude writes a three-email nurture after the webinar that moves [NEXT STEP] without repeating the live pitch three times. You still rehearse email one against the recording, then deliver the three sends on the schedule.

You are a webinar follow-up writer who writes a three-email nurture, not three copies of the live pitch. <context> I need three emails after the webinar that move [NEXT STEP]. Different job each time. Plain text. Not HTML. Not a 12-week drip. </context> <inputs> - Webinar title and what I taught: [WEBINAR TITLE] / [TAUGHT] - Next step I want: [NEXT STEP] - Offer if I still have one: [OFFER OR NONE] - Replay window: [REPLAY WINDOW] - Send days I can do: [DAY 0 / DAY 2 / DAY 5 OR CUSTOM] - Voice: [PLAIN / WARM] </inputs> <task> Write 3 emails with subject, preview, and body (110-180 words each): 1. Same-week recap + replay, one CTA 2. Deepen one item from [TAUGHT] they did not get in email 1, then [NEXT STEP] 3. Decision email: [OFFER OR NONE] or a non-offer ask if NONE, plus [REPLAY WINDOW] if it still matters Do not repeat the same first line. Do not invent a fourth email. </task> <constraints> - Do not paste the live pitch three times. - Do not invent proof or bonuses. - No HTML. Tell me link placement in brackets. - I still schedule and send after I check email 1 against the recording. </constraints> <format> Return Email 1-3 labeled with send day, subject, preview, body, and the one line that must not repeat across them. </format>

๐Ÿ’ก

Pro tip: Email 1 recaps, email 2 deepens one block, email 3 asks. If all three are the same pitch, they will mute you.

Free tool

Transcript Summarizer

Turn a meeting or video transcript into a summary with action items.

Try it free โ†’

Frequently Asked Questions

The video scripts page writes recorded artifacts for YouTube, TikTok, Reels, and ads. This page is a live webinar: waiting-room opens, teaching blocks, a screen-share demo, a spoken offer, Q and A, and the follow-up email. You rehearse and deliver in a room. You do not upload a cut.
No. Every prompt asks for spoken lines or a plain-text email. Claude does not build the deck, the registration page, or an HTML file. You still make slides if you use them, host the room, and send the email from your own ESP.
You can draft them that way, but live rooms punish reading. Rehearse until you can deliver from notes. Cut any sentence you would not say to a buyer on a call. The prompt is the draft, not the hour.
Yes. Offer is the live pitch after teaching: bridge, stack, objection, deadline, soft versus hard ask. Follow-up is the same-day thank you, replay plus offer, no-show catch-up, buyer versus attendee split, and a three-email nurture. You still send every email.
Not if you fill the placeholders with your proof, rehearse out loud, and cut lines you would not say. A first draft read cold will sound like a draft. Rewrite until it sounds like you, then deliver live.

Prompts are the starting line. Tutorials are the finish.

A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.

7-day free trial. Cancel anytime.