ewentFour surfaces. One job.
Everything in ewent exists to move one number: the share of people who registered who actually turn up. Here is what each part does and who touches it.
01 · Attendee
The checklist page
The centre of the product. One signed URL per attendee per event — no password, no account wall. It knows who they are, what phase the event is in, and what they have already done.
Header
Event name, countdown, and the start time in the attendee’s own timezone.
Phase tabs
Prep, live, post. The page changes as the event moves; retired steps get out of the way.
Step cards
A link and a tick. 67,000 ticked so far across 73 events.
Calendar
A real .ics, offered early rather than buried.
Graceful exit
Cancel in a click so the seat recirculates.
Preferences
Unsubscribe lives on the page itself, not only in a footer.
02 · Organizer
The checklist builder
Where an organizer turns the things they currently repeat in emails into steps that send themselves. Start from a template for the event type, edit, preview as an attendee, done.
Steps by phase
Write once per event, or once per recurring series and let every occurrence inherit it.
Templates
Conference, webinar, meetup, workshop — a sensible starting list rather than an empty screen.
Cadence
Eight touchpoints, configured once. Each fires against the attendee’s local clock.
Dashboard
Who is prepared, who is drifting, who cancelled — per event and across a series.
03 · Public
The event page
A shareable page per event, with speakers, sessions, exhibitors and sponsors rendered from the same data the checklist uses. It is what an attendee sends to a colleague.
Event
Details, agenda, location, registration hand-off.
Speakers
A page per speaker — the most-shared artifact an event produces.
Sessions
A page per agenda item with local start time and add-to-calendar.
Exhibitors
Booth pages with canonical URLs, for events that have a floor.
04 · Platform
The embeddable widget
If you would rather keep attendees on your own site, the checklist ships as a drop-in embed that renders and ticks in place.
<div id="ewent-checklist" data-event="EWENT_TOKEN"></div> <script src="https://ewent.ai/widgets/checklist/checklist.js" defer></script>
What ewent deliberately does not do
A short list, because knowing the edges is more useful than another feature grid.
| Not this | Because |
|---|---|
| Ticketing & payments | You already have one. Replacing it is the migration we exist to avoid. |
| A generic content platform | The object here is an event, not a post. Scope discipline is why the checklist works. |
| A messenger or social graph | Live rooms hand off to your existing tooling; we don’t compete with it. |
| Attendee accounts | Signed links mean no password and no signup wall between a person and their own checklist. |
Stop losing the people who already said yes.
Connect the registrations you already collect. We handle the rest — per-attendee checklists, timezone-local reminders, and a live nudge when the room opens.