Webinar

webinar

Run the webinar as one conversion event from end to end — from "we should do a webinar" to "we closed deals from it." You own four coupled phases in order: decide the offer, fill the seats, run it to convert, follow up by segment. You do not own the artifacts the specialists make. The slide visuals, the registration page's final words, the recurring content calendar, the standing newsletter — those get handed to siblings. What you own is the funnel and the run-of-show that stitch them into one timeline. A webinar is a sales conversation scheduled in advance; design the conversation, not the talk.

When to use

• Planning from scratch: deciding the offer / single next step before the title or any slide.
• Choosing live vs automated/on-demand for the goal and audience size.
• Writing the run-of-show: hook → teaching → permission transition → stack → offer → close → Q&A.
• Building the 4-week promotion schedule across email + organic + paid social.
• Writing the pre-event reminder sequence (confirmation → 24h → 1h → 5-min) that drives show-up rate.
• Designing the segmented post-event follow-up (attendees vs no-shows vs replay) in the 0–72h window.
• Rescuing a webinar that gets registrations but no-shows, or attendees but no sales — diagnosing which funnel stage leaks.
• "Montar un webinar que convierta" (ES), "fer un webinar que vengui" (CA).

When NOT to use — route instead

The test: if the deliverable is the event funnel, the run-of-show, or the promote-and-follow-up timeline, it is webinar. If it is the slides, that is presentations. If it is the registration page's copy, that is landing-copy.

Decide the offer first

Before the title, before a single slide, write down the ONE thing this webinar sells — or the single next step it asks for. Why: the teaching only lands if you reverse-build it from the offer. A pitch bolted onto a finished talk feels like an ambush; a talk built backward from the offer feels like the obvious conclusion. The opening story plus the teaching should do ~80% of the selling, so the ask at the end is a small step, not a leap (Graham Cochrane $100k webinar template 2025; Best Seller Publishing 2025).

State it in one sentence before anything else:

This webinar sells: [the $1,500 6-week cohort]
The single next step we ask for: [book a 15-min enrollment call by Friday]
The 2–3 false beliefs the teaching must break: [1] ... [2] ... [3] ...

If you cannot fill that in, stop. You are not ready to pick a title. Everything downstream — the hook, which beliefs the teaching dismantles, the stack, the follow-up CTA — is derived from these three lines.

The funnel you're optimizing

You are optimizing five numbers, not one. Anchor every plan to registrants, because roughly half of them never show up live — median live attend rate is ~41.6% of registrants; B2B averages ~35–45% (Univid Webinar Report 2026; ON24 2025 Benchmarks). If you plan for "attendees," you under-fill the top and over-promise the close.

Registrants  →  Show-up (~42%)  →  Engaged  →  Converted  →  Post-event
  reminder         interaction       offer        follow-up      replay/segment
  sequence         (polls/CTA)        + close      0–72h          ~25% of sales

Diagnose by stage when something leaks:

Live vs automated/on-demand

Pick by goal, audience size, and repeatability — not by what feels more "premium."

Default to live for the first run of any new offer (you learn the objections), then automate the winner.

Run-of-show

The skeleton, with the 80/20 selling rule baked in:

1. Hook (0–5 min)        — the promise + the story that earns the room's attention
2. Teaching (5–40 min)   — break the 2–3 false beliefs, one block each, proof per block
3. Permission transition — explicitly ask to switch modes before you pitch
4. Stack + offer         — what they get, framed against the cost of staying stuck
5. Close (the ask)       — the single next step, with a clean deadline
6. Q&A                   — handle the live objections; do NOT re-open the teaching

The transition is where most webinars die — the speaker lurches from "value" to "buy now" with no bridge, and the room feels sold-at. Ask permission and name the shift:

Bad:  "...and that's the framework. So anyway — I've got something to show you.
       For just three payments of $500 you can..."

Good: "That's the whole method. Now — some of you want to implement this alone, and
       these slides are enough to do that. For the rest who'd rather we do it with you
       over the next six weeks, can I take two minutes to show you exactly how that
       works? Then we'll open it up for questions."

The "Good" version gives the room a choice, which lowers resistance — and it earns the pitch instead of springing it. Place a poll roughly every 10–12 minutes so the teaching stays a conversation. The full annotated, timed template — hook block, the per-belief teaching blocks, the stack/offer mechanics, poll placement, and how the stack changes by offer type — is in references/run-of-show.md. Hand the slide visuals for all of this to ../presentations/SKILL.md.

Promote & fill seats

Start promotion ~4 weeks out; email is the dominant channel (~86% of teams), then organic and paid social (Amra & Elma 2025). Earlier start + multi-channel = more registrants. The channel mix, email-led:

T-28d  announce            email to list + organic posts
T-21d  value teaser        what they'll learn (one belief preview) + paid social on
T-14d  social proof        past-attendee result / agenda reveal
T-7d   urgency builds      "one week left", second list email
T-1d   last call           final registration push across all channels

For the registration page itself, write a brief and hand the page to ../landing-copy/SKILL.md — do not write the final page copy yourself. The brief names: the single promise (matches the offer line above), the 3 belief-shifts as bullets, the date/time with time-zone, the host + credibility line, and the one CTA ("Save my seat"). Where this webinar sits in the wider calendar belongs to ../content-engine/SKILL.md. The full dated promotion table lives in references/email-cadence.md.