Writing Event Descriptions
A guide and template for writing event listing descriptions for Applied AI Live events on Luma, Meetup, Eventbrite, or any event platform.
Principles
These principles were extracted from the Applied AI Live #1 Luma description (preserved in full below).
Lead with the value prop, not the org
The first paragraph should explain what attendees get, not who's hosting. "A workshop series for people who want to make money by practically applying AI" tells the reader immediately whether this is for them. Org details come later.
Name the format explicitly
Set expectations early. "Workshop series" is better than "event." "People who want to make money by practically applying AI to real-world business problems in valuable industries" filters for the right audience and repels the wrong one.
Speaker bios = credential + current work + what they'll share
Don't just list titles. Show why this person is credible right now:
- Credential: "creator of NumPy and SciPy"
- Current work: "founder of OpenTeams"
- What they'll share: "will speak on the importance of applied AI practitioners and what his team is building"
Each speaker should earn their paragraph.
Highlight the signature format
The live problem-solving element gets its own paragraph because it differentiates the event from every other AI meetup. If your event has a unique format element, give it space. Don't bury it in a list.
"Who Should Attend" uses specific roles, not generic language
Good:
- "Engineers and developers who want to build a career (or side income) helping businesses integrate AI"
- "New grads trying to stand out in a dramatically changed job market"
- "Business owners curious about what's actually possible"
Bad:
- "Anyone interested in AI"
- "Tech professionals"
- "AI enthusiasts"
Specificity helps people self-select. If someone reads the list and thinks "that's me," they're more likely to RSVP.
Co-host descriptions earn their space
Each hosting org gets a paragraph with mission + credibility signals. AITX's description mentions concrete numbers (50+ startup demos, chapters in three cities, running since 2022). Antler's description explains what they do and links to their application. These aren't filler; they give attendees context on who's behind the event.
Sponsor acknowledgment is grateful and brief
State what sponsors do, why it matters, and move on. No hard sell. The Live #1 description thanks OpenTeams and OT Incubator by explaining their mission (infrastructure for applied AI, sovereignty over data) and connecting it to why the Society exists. One paragraph, done.
Tone: direct, warm, practitioner-focused
No hype words. No "revolutionary," no "cutting-edge," no "game-changing." Just what's happening and why it matters. The description reads like it was written by someone who does the work, not someone marketing to people who don't.
Section-by-Section Template
Use this structure when writing a new event description. Adapt the details, but keep the order and tone.
About This Event
This is [the Nth installment of / a new installment of] a workshop series for people who want to make money by practically applying AI to real-world business problems.
The goal is to create a Schelling point for practitioners who are actually making a living helping businesses integrate AI, sharing exactly how they do it.
Then introduce each speaker in their own paragraph:
[Speaker Name] [credential]. [Current work]. [What they'll share at this event].
Then call out the signature format:
[Description of the live problem-solving element or other unique format]. This live problem-solving format is a core part of the series: real problems from real people in industry, solved in real time.