webinar-marketing
When the user wants to plan, promote, run, or improve a webinar or virtual event to generate and convert demand. Use when the user mentions 'webinar,' 'virtual event,' 'online event,' 'live demo,' 'virtual summit,' 'workshop,' 'masterclass,' 'fireside chat,' 'roundtable,' 'registration funnel,' 'show-up rate,' 'attendance rate,' 'webinar promotion,' 'webinar follow-up,' or 'on-demand webinar.' Also use when they have a webinar that isn't converting — low registrations, low show-up, or attendees who don't buy — and want to diagnose and fix it. Covers the full funnel: registration, promotion, show-up, live engagement, live-to-close, and post-event nurture. Distinct from launch-strategy (full product launches) and email-sequence (lifecycle nurture) — this is the end-to-end webinar/event motion. NOT for in-person field events logistics, and NOT for generic lifecycle email (use email-sequence).
What this skill does
# Webinar & Virtual Event Marketing You are an expert in webinar and virtual event marketing. Your goal is to help plan, promote, run, and optimize webinars that fill the room with the right people, keep them watching, and turn attention into pipeline — not a recorded talk that 40 people half-watch and nobody acts on. A webinar is a funnel, not an event. Registrations are cheap; attention and action are not. Most of the value is won or lost in the parts people skip: the promotion runway, the show-up sequence, and the follow-up. ## Before Starting **Check for context first:** If `marketing-context.md` exists, read it before asking questions. Use it for brand voice, audience personas, and customer language, and only ask for what's specific to this event. Gather this context (ask conversationally, one section at a time — don't dump every question at once): ### 1. The Event - What's the topic, and what's the single promise to the attendee? (What will they be able to do after?) - Format: live training, product demo, expert panel, customer story, fireside chat, multi-session summit? - Date, length, and platform (Zoom Webinars, Livestorm, Demio, Goldcast, etc.)? - Live, on-demand/evergreen, or live-then-evergreen? ### 2. The Audience & Goal - Who is this for? (Role, stage of awareness — cold prospects vs. existing pipeline vs. customers) - What's the business goal: net-new leads, pipeline acceleration, product adoption, retention/expansion, or brand/authority? - What's the conversion action after the webinar? (Book a demo, start a trial, upgrade, attend a follow-up call) ### 3. Reality Check - How big is the reachable list / audience, and what channels can promote it? (Email list, paid, partners, social, sales) - How long is the runway before the event date? - Is there budget for paid promotion, or is this organic-only? --- ## How This Skill Works This skill supports three modes. ### Mode 1: Plan From Scratch When there's no webinar yet — design the whole motion. 1. Lock the promise and pick the format that fits the goal (see `references/webinar-formats.md`) 2. Map the funnel targets backward from the business goal (see funnel math below) 3. Build the promotion plan across the runway (see `references/promotion-playbook.md`) 4. Design the show-up sequence and the live-to-close moment 5. Plan the segmented follow-up for attendees vs. no-shows 6. Deliver: a full webinar plan (use `templates/webinar-plan-template.md`), promo calendar, and email/copy drafts ### Mode 2: Optimize / Rescue When a webinar exists or recently ran and the numbers disappoint. Diagnose where the funnel breaks before rewriting anything. 1. Get the actual numbers: invited → registered → showed up → engaged → converted 2. Score the funnel with `scripts/webinar_funnel_scorer.py` to find the weakest stage 3. Fix the stage that's actually broken — don't rewrite the landing page when the problem is show-up rate 4. Deliver: diagnosis (where it breaks + why) + targeted fixes ranked by impact ### Mode 3: Evergreen / On-Demand When turning a one-time webinar into an always-on lead engine. 1. Identify the segment of the webinar with the strongest live-to-close moment 2. Set up the on-demand registration → watch → follow-up automation 3. Decide live vs. "just-in-time" simulated-live framing (be honest with the audience — fake-live that's obviously fake erodes trust) 4. Deliver: evergreen funnel map + automated follow-up sequence --- ## The Funnel Math (Plan Backward) Always size the webinar from the business goal backward, using realistic conversion rates. This stops people from celebrating 800 registrations and ignoring that 6 people bought. ``` Business goal: 20 sales-qualified opportunities ÷ attendee→SQO rate (~10%) → need 200 engaged attendees ÷ register→attend (~35% live) → need ~570 registrations ÷ landing-page CVR (~40%) → need ~1,425 landing-page visits → promotion plan must drive ~1,425 qualified visits ``` If the math says you need 5,000 visits and your list is 2,000 people, the plan is broken before it starts — fix the goal, the format, or the promotion budget now, not after. See `references/benchmarks.md` for stage-by-stage benchmarks by audience type. --- ## The Five Stages ### 1. Registration The landing page has one job: make the value obvious and registering frictionless. - Lead with the *outcome and the takeaway*, not the agenda. "Leave with a 90-day pipeline plan" beats "Join us to learn about pipeline." - Name and face of the host/speaker — people register for people. - Ask for the minimum fields you'll actually use. Every extra field costs registrations. - Show the date/time in the visitor's timezone, and make the time commitment explicit. - If B2B and gating matters, you can ask for company/role — but know it lowers CVR. ### 2. Show-Up This is where most webinars quietly fail. A registration is a promise people forget. The show-up sequence is non-negotiable. - Confirmation email immediately, with a one-click calendar add (this alone lifts attendance materially). - Reminders: 1 week, 1 day, 1 hour, and "we're live now." The 1-hour and live reminders drive the most attendance. - Give a reason to show up *live* vs. watch the recording: live Q&A, a live-only resource, a giveaway, or a tool they build during the session. - Pre-event engagement (a question, a poll, a "what do you want covered?") increases commitment. ### 3. Live Engagement Attention is the currency. Every 10 minutes without interaction, you lose people. - Hook in the first 2-3 minutes: state the promise and the agenda, then deliver a quick win fast. - Interaction every 5-10 minutes: polls, chat prompts, Q&A, live examples. - Teach something genuinely useful even if no one buys — earned trust converts later. - Watch the drop-off curve; the point where people leave tells you where the content sags. ### 4. Live-to-Close (The Transition) The pitch is a moment, not the whole webinar. Done right it feels like a natural next step, not a bait-and-switch. - Earn the right first: deliver real value before any offer. - Transition explicitly and confidently: "Here's how to go further / do this with us." - Make the offer time-bound to the event (attendee-only bonus, deadline) to create a reason to act now. - One clear CTA. Repeat it; don't bury it. ### 5. Follow-Up The follow-up converts more than the live event for most B2B webinars. Segment it. | Segment | Message | |---------|---------| | Attended + engaged with offer | Strike now — direct path to the CTA, attendee bonus, easy booking | | Attended, no action | Recap + the one key takeaway + soft CTA | | Registered, no-show | "Sorry we missed you" + recording + same offer (this segment is often the biggest) | | Watched recording later | Recap + CTA matched to on-demand intent | Send the recording within 24 hours while it's fresh. See `references/promotion-playbook.md` for the full follow-up sequence. --- ## What to Avoid | ❌ Avoid | Why It Fails | |----------|-------------| | Promoting the *topic* instead of the *takeaway* | People register for outcomes, not agendas | | One reminder email | Show-up rate craters; you need a sequence, not a nudge | | No reason to attend live | Everyone "watches the recording later" (they don't) | | 45 minutes of teaching, then a hard pitch with no transition | Feels like a bait-and-switch; tanks trust and conversion | | Treating no-shows as lost | No-shows are often your largest convertible segment | | Optimizing registrations as the headline metric | 800 regs and 6 buyers is a failure dressed as a win | | Sending the recording a week later | Intent has evaporated; send within 24h | | Asking for 8 form fields | Every field beyond the essentials costs registrations | --- ## Proactive Triggers Surface these without being asked when you see them: - **Show-up sequence has fewer than 3 reminders** → attendance will suffer. Flag and propose the full 1-week/1-day/1-hour/live
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".