The starting point
A coordinator copied the guest list, looked up attendees across several spreadsheets and checked for changes in role or company. Briefings took days to prepare for each event. Updates rarely reached every sheet, so hosts arrived with conflicting details and nobody planned introductions.
What we built
Connected member records
Member, guest and partner records moved into one system, with each team keeping the fields it owns. Engineers resolved conflicting entries with each team before switching over.
Guest briefing drafts
When a guest list is confirmed, an AI agent drafts a briefing for each attendee from the shared record and recent public updates, ready for the host team to edit.
Suggested introductions
Each briefing suggests who a guest should meet and why, based on what members are building and looking for. Hosts choose which introductions to make.
Changes reach every team
An update to a member’s role, company or interests is made once and shows everywhere it is used.
The result
Hosts now arrive with the same details on every guest and a short list of introductions to make.
- Drafted when the list closesEvery guest briefing is drafted from the shared record as soon as the guest list is confirmed.
- Ready before the eventThe host team reviews and approves briefings ahead of each dinner and summit.
- Introductions suggestedEach briefing suggests who a guest should meet and why, for the hosts to choose from.
Where people stay involved
Briefings stay as drafts until a named host approves them, and nothing is sent to members automatically. Each team edits only the fields it owns. The agent reads only the fields a briefing needs.
