The organisation needed one event experience platform for attendees, organisers, and event operations teams. The existing journey divided programme discovery, session suggestions, speaker profiles, registration, tickets, reminders, venue guidance, and check-in between separate tools and informal follow-up, so the project had to solve the operating model as well as the interface.
A complete event experience platform shaped around attendees, organisers, and event operations teams
The organisation needed one event experience platform for attendees, organisers, and event operations teams. The existing journey divided programme discovery, session suggestions, speaker profiles, registration, tickets, reminders, venue guidance, and check-in between separate tools and informal follow-up, so the project had to solve the operating model as well as the interface.
Discovery followed the full journey from the first customer or staff action to its operational and commercial close. That exposed the handoffs between event discovery, registration, and attendee operations, including the exceptions that a feature list would have missed.
- Map the people, decisions, and records across the whole event experience platform.
- Separate firm events and ai rules from habits created by the old tools.
- Agree what the first release must complete from end to end.
The product joined event discovery, registration, and attendee operations without blurring roles
Keep registration and event operations deterministic while using AI only for explainable discovery, recommendations, and content assistance.
In the event experience platform, each audience receives a focused home while the underlying state remains shared. The interface shows what needs attention, who owns the next action, and why work is blocked, while secondary detail stays available for review without crowding everyday tasks.
- Design the primary journey for every audience named in the brief.
- Give exceptions, corrections, and cancellations an explicit route.
- Use realistic records to test the complete flow before widening the surface area.
Next.js, Python AI services, PostgreSQL formed one supportable event experience platform
The architecture follows business ownership rather than the navigation menu. Next.js, Python AI services, PostgreSQL share versioned contracts, server-side permissions, observable integrations, and one authoritative record for the decisions behind registration.
In the event experience platform, slower or external work runs through durable jobs with idempotent handling and visible failure states. Logs retain the organisation, actor, and product record needed to investigate a problem without guessing from a generic error message.
- Next.js supports the primary product surface.
- Python AI services owns a bounded part of the product journey.
- PostgreSQL keeps operational data and handoffs reviewable.
The release had to prove the whole event experience platform, not one polished screen
Attendees can plan a useful visit and organisers can manage the full event journey from one operating view. The release plan therefore followed representative work across every audience and the complete path through event discovery, registration, and attendee operations.
Acceptance for the event experience platform included ordinary work, missing inputs, repeated requests, failed integrations, permission boundaries, and the route back to a trustworthy state. The team checked whether staff could understand and recover from a problem without direct database help.
- Run the busiest realistic journey from start to operational close.
- Rehearse a failed integration and a repeated customer action.
- Confirm that every role sees only the work and data it owns.
- Trace a management result back to the records that produced it.
What the work established
Attendees can plan a useful visit and organisers can manage the full event journey from one operating view.
- 01
The event experience platform now gives attendees, organisers, and event operations teams one shared operating record.
- 02
Event discovery, registration, and attendee operations follow the same product rules.
- 03
The system makes ownership and exceptions visible instead of hiding them in manual follow-up.
- 04
The product can grow from clear workflow, data, and service boundaries rather than isolated features.