Every edition builds on the last one, even when half the team is new
For festival organisers, event agencies and production companies who build a site from an empty field. We help you plan each edition the AI-first way, with agents that watch deadlines and brief the crew, and Hivemind, our flagship, as the one plan everyone works from.
Built for festival organisers, event agencies, production companies
Read by Claude, ChatGPT, Copilot and your agents · within your permissions
Sound familiar
The permit clock starts early
The municipality wants the safety plan, traffic plan and site drawing weeks before the date, and the risk category decides how much. The person who wrote last year's plan now freelances for another festival.
The debrief gets written and forgotten
Everyone agreed the bar queues at the main stage were too long. Ten months later the new site plan has the same layout, because the notes sat in an email nobody reread.
Suppliers ask the same questions every year
Power per stage, the gate for trucks, when build-up starts. The production office answers them one by one in the week the fencing, radios and toilets arrive.
Everyone works from the same company
What changes once Hivemind, our flagship, is the knowledge under every AI tool and agent your team uses.
Each edition starts ahead
Last year's permit file, supplier list and debrief are where the new team looks. Ask your AI what went wrong at the north gate and get the answer with the fix.
One plan for every team
Production, artist liaison, security and bars read the same site plan and run sheet, through whichever AI tool each of them uses.
Briefings that answer back
Shift leads and crew chiefs ask their AI where to park, who runs their area and what to do in an emergency, and get the answer from the plan.
Agents that do the work
Agents like these we build with you. Each has a toolbox: what it may read, what it may change, and what waits for a person.
Deadline watch
Every Monday · from 16 weeks before the edition
Deadline watch, every Monday · from 16 weeks before the edition: Reads the permit and supplier timeline, posts every deadline at risk to the production channel and prepares reminders for suppliers who are late.
3 allowed · 1 waits for a person
Crew briefing
Two weeks before build-up
Crew briefing, two weeks before build-up: Writes the crew briefing from the site plan, run sheet and emergency plan, and saves it to the edition page for the production manager to approve.
3 allowed · 1 waits for a person · 1 does not exist for this agent
Connects today
- Knowledge base
- Files
- Slack
- Gmail
Next to what you already use
- Ticketing such as Eventix, Paylogic or Ticketmaster
- Crew planning and accreditation such as Lennd or Shiftbase
- Site drawings in AutoCAD or Vectorworks
- Shared drives and a WhatsApp group per team
A system without a connector yet gets one: we build it as part of Build.
We set it up with you
Implement
We interview production, artist liaison and the safety lead, and fill in last year's edition first
Automate
Deadline watches, supplier chases and crew briefings that come back every edition
Build
A supplier portal that collects certificates, power needs and build-up times in one place
Learn
Training for the production office on AI for permit files, run sheets and briefings
Questions
Can it write our safety plan?
It drafts from last year's plan, the municipality's format and your new site plan, and a person checks every line. Your safety coordinator still owns the plan and signs it off. What you save is starting from a blank page.
We are seasonal. Who keeps it current in the quiet months?
The debrief goes in right after the edition, while it is fresh. Agents remind you of permit and supplier deadlines as they come up. When the team grows again in spring, new people ask their AI instead of the one person who was there.
Is visitor and ticket data stored in it?
No. Ticket buyers stay in your ticketing system. The knowledge base holds how the festival runs: plans, suppliers, contacts and decisions. Plans, briefings and deadline checks all work without the personal data of a single visitor.