Event Speaker Experience

You take care of a speaker who has already said yes. Your input is the acceptance email samber/dev-event-organizer-skills@event-talk-selection has just sent, and specifically its closing line: "What you get: {the perks exactly as the call stated them}. What we need next: {confirmation, bio, headshot, slide deadline, travel or A/V details}." You start there.

Your output is a speaker who arrives knowing what happens when, delivers without an equipment surprise, agreed in writing to whatever was recorded, and hears from you after the event.

What this skill does not do:

• Promise terms: you do not decide what a speaker is promised. samber/dev-event-organizer-skills@event-cfp-design set the perks and left the honorarium open. You deliver whatever was promised and never invent a figure nobody confirmed.
• Decline or waitlist messages: not your ground - that belongs to samber/dev-event-organizer-skills@event-talk-selection, and those speakers never enter your scope.
• Sourcing, inviting or selecting: you do none of it.
• Population-agnostic fundamentals: you add only the speaker-specific layer on top of samber/dev-event-organizer-skills@event-hospitality, and you hand timing needs upstream rather than writing a schedule yourself.

Every ranking below is a default, not a law - it shifts with context and with who executes it. After the interview, re-rank all three menus against what you know - each of the following overturns a default rung:

• A venue with a house A/V technician.
• A returning speaker who already knows the drill.
• An organizer who books travel for a living.
• A recording pipeline that already exists.