// execute
Webinar & Event Programs
Use when the user is planning a webinar, virtual event, roundtable, workshop or conference presence and wants it to create pipeline, or is looking back at one and asking whether it was worth it. Also use when the user mentions webinar ROI, cost per attendee, show rate, event follow-up, run of show, field events, or "how many registrations do we need". Plans the event backwards from a pipeline target using the user's own conversion rates, checks the run-of-show before invitations go out, and reads the result on meetings and pipeline against cost, never on registrations.
npx skills add sarojkjha/aaj-marketing-skills --skill webinar-and-event-programsClaude Code
/plugin marketplace add sarojkjha/aaj-marketing-skills/plugin install aaj-marketing-skills@aajOpenAI Codex
codex plugin marketplace add sarojkjha/aaj-marketing-skillscodex plugin add aaj-marketing-skills@aajClaude or ChatGPT — no install
Add this as a custom connector:
https://aaj-engines-mcp.sarojkjha10.workers.dev/mcp// when to use it
Use when the user is planning a webinar, virtual event, roundtable, workshop or conference presence and wants it to create pipeline, or is looking back at one and asking whether it was worth it. Also use when the user mentions webinar ROI, cost per attendee, show rate, event follow-up, run of show, field events, or "how many registrations do we need". Plans the event backwards from a pipeline target using the user's own conversion rates, checks the run-of-show before invitations go out, and reads the result on meetings and pipeline against cost, never on registrations.
// what you give
The pipeline the event must create, your average opportunity value, your own rates for meetings to opportunities, attendees to meetings and registrations to attendance, the registrations you can realistically reach, and every cost including people time; the run-of-show items done; afterwards registrations, live and on-demand attendance, meetings, opportunities, pipeline, your win rate, cost and when the first follow-up went out
// what you get
The room the target needs - opportunities, meetings, attendees, registrations - with cost per each, the weakest step, and a feasible, stretch or not-feasible call; the run-of-show items still missing; and a repeat, change, stop or too-early verdict on expected revenue against cost
Engine spec
// decision it supports
How many registrations does this event need to hit its pipeline target, and was the last one worth running again?
// inputs
The pipeline the event must create, your average opportunity value, your own rates for meetings to opportunities, attendees to meetings and registrations to attendance, the registrations you can realistically reach, and every cost including people time; the run-of-show items done; afterwards registrations, live and on-demand attendance, meetings, opportunities, pipeline, your win rate, cost and when the first follow-up went out
// output
The room the target needs - opportunities, meetings, attendees, registrations - with cost per each, the weakest step, and a feasible, stretch or not-feasible call; the run-of-show items still missing; and a repeat, change, stop or too-early verdict on expected revenue against cost
// acts or analyzes
Analyzes onlyMakes no network calls, writes no files and changes nothing in your tools.
// where your information goes
| How you run it | Where your inputs go |
|---|---|
| Skill installed in your agent, or the local MCP server | The engine runs on your machine and AAJ receives nothing. Your AI agent still sends what you give it to its model provider (Anthropic, OpenAI and so on), under your own account's terms. |
| Hosted MCP server | Your agent's model provider, as above, plus AAJ's server on Cloudflare, which receives the engine inputs over HTTPS, runs them in memory and keeps no copy. Cloudflare keeps error logs (no inputs) for up to 7 days. |
No engine needs customer names, emails or other personal data; leave them out.
// limitations
- The plan uses only your conversion rates and has no defaults. Borrowed rates make the room size a guess; label them as assumptions.
- Without a win rate the verdict uses pipeline against cost, which reads higher than expected revenue and makes a repeat easier. A misspelled field now stops the run, and an invalid winRate (such as 25) is rejected.
- The 0.5 and 1.0 reach bands, the 3x target, the five-meeting floor and the 24-hour follow-up rule are engine rules, not benchmarks.
- Read too soon, the result undercounts: meetings take three to six weeks to become opportunities. Cost is only complete if people time is in it.
// review before acting
// setup
npx skills add sarojkjha/aaj-marketing-skills --skill webinar-and-event-programshttps://aaj-engines-mcp.sarojkjha10.workers.dev/mcpAgents listed: Claude Code, Cursor, OpenAI Codex, Windsurf, Cline. Tested and recorded: Claude Code.
Webinar & Event Programs
Most startup webinars fill a registration list and stop there. Someone reports "312 registrations, 38% show rate", everyone nods, and six weeks later nobody can say what it sold. The registration count is the number that is easiest to get and matters least.
This skill treats an event as a pipeline instrument. You start from the pipeline it has to create and work backwards to the room, using your own conversion rates; you check the run-of-show before the invitations go out, because the follow-up is the real event; and afterwards you judge it on meetings, opportunities and pipeline against what it cost, including your team's time.
When to use
The user is deciding whether to run an event, sizing one, preparing one, or reading the results of one. It applies to webinars, virtual roundtables, workshops, dinners and conference sessions alike; only the cost lines differ.
Do not use it to decide on a topic or a format. That is a positioning question: the topic is a
problem your buyer has this quarter, and the Webinar that creates pipeline post covers how to
choose it.
Before you start
- Know the pipeline number the event is accountable for, and your average opportunity value.
- Pull your own rates from the last two or three events: attendees to meetings, meetings to opportunities, registrations to live attendance. If you have none, borrow a partner's and label them as assumptions. The engine supplies no defaults and refuses to size a room without them.
- Count what you can reach: your list times its usual registration rate, plus partners' and speakers' audiences, plus what paid promotion buys.
- Cost the people time. An event that "cost $400 for the platform" cost forty hours as well.
Method
Plan backwards. Pipeline target ÷ opportunity value = opportunities needed; ÷ your meeting-to-opportunity rate = meetings; ÷ your attendee-to-meeting rate = live attendees; ÷ your show rate = registrations. Each step rounds up. The engine then prices the room: cost per registration, per attendee, per meeting, and pipeline per dollar. It names the weakest step, which is the rate most worth lifting: show rate through reminders and calendar holds, attendee-to-meeting through the offer at the end.
Test against reach. Registrations needed against registrations you can reach. At or above 1.0 the target is feasible; between 0.5 and 1.0 it is a stretch (add a partner's audience, lower the target, or lift a rate); below 0.5 it does not fit one event (both bands are engine rules).
Check the run-of-show. Eight items, each true or not: the topic is a buyer problem; promotion is live at least two weeks out; a dry run on the real platform; a recording and on-demand page; the follow-up sequence written before the event, with a different first email for attendees, no-shows and on-demand viewers; a sales handoff with names, times and the signal to call on; one question or poll that qualifies; one call to action.
Read on what it sold. Show rate and cost per attendee are reported but never decide anything. The verdict uses expected revenue (pipeline created × your win rate) against cost, or pipeline against cost if no win rate is given:
- repeat: at or above your target return (default 3× cost, an engine rule you can override);
- change: pays for itself but misses the target; change the weakest step before running again;
- stop: below 1×, unless the topic or the follow-up was clearly the failure;
- too early: fewer than five meetings booked (an engine rule).
A first follow-up later than 24 hours after the event is flagged as a fix (AAJ's rule), and a readout with no on-demand figure is asked for one, because most registrants never attend live.
Workflow
Step 1 - Size the room. Run the plan with your own rates and reach. If it is a stretch, decide now which lever you will pull, or lower the target.
Step 2 - Prepare. Run the run-of-show check a week out and again the day before. Do not send the last invitation until the follow-up sequence exists.
Step 3 - Run it. One CTA, one qualifying question, and the recording page live within a day.
Step 4 - Follow up within 24 hours, differently for attendees, no-shows and on-demand viewers, and hand the qualified names to sales on the agreed signal.
Step 5 - Read it once the meetings have had time to become opportunities, usually three to six weeks. Give the engine the counts, the cost and your win rate. Repeat, change or stop.
Run the tool
node resources/event-program.js --demo
run({ plan, runOfShow, readout }) returns the sized funnel with costs and a feasibility call, the
run-of-show items missing, and the readout with cost per attendee, per person reached, per meeting
and per opportunity, expected revenue, the return ratio and the verdict.
Present the result
- The room: opportunities → meetings → attendees → registrations, with cost per each and the weakest step.
- Feasible, stretch or not, and the lever chosen.
- The run-of-show gaps, in one line each.
- The readout: reached, meetings, opportunities, pipeline, expected revenue against cost, and the verdict. Registrations go last.
Guardrails & common mistakes
- Never report registrations as the result. Report meetings, opportunities and pipeline.
- Never use a borrowed show rate without saying so. Your rates come from your events; anything else is an assumption and is labelled.
- Never send the invitations before the follow-up is written. The follow-up is where the pipeline is made.
- Do not leave out people time. It is usually the largest cost line.
- Do not judge before the meetings have had time to move. Five meetings is the floor; three to six weeks is the usual wait.
Related AAJ resources
- Size the room in a browser: https://aajconsult.com/tools/webinar-pipeline-planner
- Choosing the job, the topic and the format: https://aajconsult.com/blog/webinar-that-creates-pipeline
- Borrowing a partner's audience: https://aajconsult.com/playbooks/partner-co-marketing-playbook
- What the pipeline is worth once it exists: https://aajconsult.com/tools/pipeline-forecast-calculator
Related skills
partnerships-and-co-marketing- co-hosting to reach registrations you cannot reach alonepipeline-and-forecast- weighting the pipeline the event createdemail-lifecycle-sequence- writing the three follow-up sequencescontent-repurposing- what the recording becomes afterwards
// faq
// install
npx skills add sarojkjha/aaj-marketing-skills --skill webinar-and-event-programs// worked example
Get the worked example for Webinar & Event Programs
One email. The filled-in config, the output, and how to read it.
// human in the loop
Need a human in the loop?
AAJ builds the strategies, tools, and playbooks these skills are made of — with engagements for growth-stage and enterprise teams.