unDavos Summit

unDavos is the open community summit that runs alongside the World Economic Forum in Davos — 70 sessions, 300 speakers, and 3,000 delegates, organized by a distributed volunteer team rather than a conference corporation.

Thrivbe serves as community coordinator and designed the collaboration architecture that lets a core team of four coordinate a summit of this scale: Telegram as the community platform where the organizing itself happens, a conference platform built no-code on Glide, Notion as the operational hub, n8n automation stitching the systems together, and a CRM for partners and sponsors — with organizational processes automated end to end. It was also where the agentic event system began: the seed that later grew into the full AI festival team at Katapult Future Fest.

The collaboration architecture

A small team running a 3,000-delegate summit can’t afford friction between tools, so the tools were designed as one system. Telegram is the community platform where the summit self-organizes — not just the core team, but 300 speakers, moderators, and sponsors coordinating in structured groups. The conference platform itself was built no-code on Glide. Behind them, Notion serves as the shared operational hub for tasks and projects, n8n automations move data between the systems, and Pipedrive runs the partner and sponsor pipeline. Recurring organizational processes — follow-ups, status syncs, data hygiene — were automated away, so four people could spend their time on judgment calls instead of coordination overhead.

Data pipelines

Four systems feed one coherent operations view: Luma (events and guest rosters), Pipedrive (partner and sponsor CRM), Google Drive (session recordings auto-transcribed and summarized), and Notion (the task and project hub) — all synced into local databases the agents can query. Guest matchmaking merges event data with enrichment and consent extraction.

The early beginning of an agentic event system

On top of the collaboration architecture, the first agentic layer took shape: directives (operational blueprints in plain Markdown), an AI orchestration layer (Claude agents that route work and handle exceptions), and deterministic execution scripts that talk to the APIs. A custom CLI assistant gives the team instant answers from their Notion workspace — active tasks, project status, institutional memory — without anyone hunting through pages. This three-layer pattern later matured into the full agentic operating system that co-ran Katapult Future Fest.

Feedback at scale

Debriefing a hundred-plus organizers in real time breaks every standard tool, so we designed a “lobby and breakout” system: a main collaborative document linking into ten parallel feedback workspaces, structured so every voice lands and nothing gets lost. The summit’s lessons become next year’s directives.

What we built

• — Telegram community platform where 300+ speakers, moderators, and sponsors self-organize
• — No-code conference platform on Glide
• — Operations backbone for a core team of four — Notion + n8n + Pipedrive CRM
• — Automated organizational processes (follow-ups, syncs, data hygiene) via n8n
• — First iteration of the three-layer agent system (directives → orchestration → execution)
• — CLI assistant over the Notion workspace
• — Luma, Pipedrive, and Google Drive transcription pipelines
• — Guest matchmaking with enrichment and consent handling
• — 100+ person real-time debrief system

Relevant services

Digital Collaboration & Community Systems · Phygital Events and Facilitation