Automation for event & AV production
Quotes, equipment lists, patch sheets, crew call sheets, rider checks, handover files. If your team rebuilds the same lists in spreadsheets, plots and group chats for every gig, tour or install, we automate it — with software and AI built around the tools you already run.
Today: rebuilt in
Generated, every time
Your work
Pick what fits and jump straight to the examples for your kind of work.
Lighting & stage production 6 examples 2TO2 festival, Batavierhuis 
AV installation 6 examples Setting up CHIME on location 
Rental & dry hire 5 examples Running the show from the floor 
Event agencies 5 examples Night Program, Laurenskerk 
Venues & theatres 5 examples Tropicana, for the Hazard Ensemble 
Every production company 3 examples Testing Vaib at a church concert The problem
It's rarely the show. It's the lists, quotes and messages around it, rebuilt for every gig, tour and install.
Equipment, patch and cable lists start from the last show's spreadsheet and get edited by hand until they almost match the plot.
Every rider and technical brief is checked against your stock and the venue by someone reading a PDF.
Gear, crew, transport and days priced by hand, and again when the client moves the date or changes the stage.
Who's on which call, at what time, in which van — scattered across messages and one person's head.
The plot changed on Tuesday. The cable list, the truck pack and the call sheet didn't.
Installs end with drawings, settings and manuals collected at the last minute, if at all.
Before you build anything
Think of one task in your company and tick what's true. Frequent, repeatable work on digital information is where software pays back fastest — and we'll tell you what we'd do about it.
Score 0 of 9
How much could you save?
Your own numbers, for one repetitive task.
What fits
A proper tool
Weeks of your team's time every year. Worth one source of truth.
Counted over 46 working weeks and 40-hour weeks. This is your estimate of your own process, not a promise; the process review replaces it with a measured number.
How often × how long
Every task in your company sits somewhere on this grid. Wherever yours lands, there's something we can do — except the bottom left, where we'll tell you to leave it.
Tick the questions above and your task's quadrant lights up.
What we build
Most companies need a mix. We start with the smallest thing that gives you back the most hours.
Scripts and connections between the tools you already have.
A private web app with one database for shows, gear and crew, and every document generated from it.
Reading, checking and drafting — with your crew chief checking the result.
Dashboards and reports from your shows, gear, hours and budgets.
Use cases
Real processes from production companies, and what software does with them. Pick your field; company-wide examples apply to everyone.
Fixtures, addresses and cable runs read from your plot. Patch sheets, cable lists and labels are generated, and regenerated when the plot changes.
Replaces · Retyping the plot into spreadsheets after every change
Modes, channel counts and power draw pulled from GDTF files and manufacturer data into your lists and power plans.
Replaces · Looking up DMX charts and wattages one by one
Load per phase and per distro calculated from the patch, with a warning before a circuit is overloaded.
Replaces · Adding up wattages on a calculator
Drawings, device lists, IP addresses, settings and manuals gathered per room into one handover file the client can actually use.
Replaces · Collecting PDFs at the end of the job
Cable numbers, labels and rack layouts generated from one device list, so drawings and schedules can't disagree.
Replaces · Keeping drawings and schedules in sync by hand
Requirements and quantities pulled from a tender or specification into a checklist and a first quote, with every line linked to its source page.
Replaces · Reading 80 pages to find what's asked
A rider or equipment list goes in. A quote comes out with your stock, prices, days and transport, ready for you to check.
Replaces · Pricing every line by hand
Utilisation and revenue per item and category, so you know what to buy, sub-hire or sell.
Replaces · Gut feeling at budget time
Run sheet, suppliers, floor plans, contacts and timings in one place, exported as the production book everyone works from.
Replaces · A folder of versions and a group chat
Quotes from suppliers read and lined up item by item, with gaps and price differences highlighted.
Replaces · Side-by-side PDFs and a calculator
Incoming riders compared with your house rig and stage, with a list of what's missing or needs hiring.
Replaces · Reading every rider against the tech spec
Crew hours, overtime and costs per show in one view, so overruns show while there's still time to act.
Replaces · Finding out when the invoices arrive
Who works which show, when and where, with call sheets sent automatically and changes reaching everyone.
Replaces · Group chats and one person's memory
Ask which show used that truss setup, which venue had that power issue, or what you quoted last year — with links to the files.
Replaces · Asking the colleague who remembers
Quoted against actual hours, gear and transport per show and per client.
Replaces · Finding out at year-end
Company-wide examples are shown with every field.
Your stack
You don't have to replace anything. We connect through exports, file formats, APIs and scripts, so your plotting tool stays your plotting tool and your rental system stays your rental system.
Worked example
How we approach it, drawn from our own stage work and Vaib, our AI lighting platform. Not a client project.
Before
Every show starts with the plot in one tool, the patch in a spreadsheet, the cable list in another, and the desk programmed by hand from all three.
We walk one recent production from rider to get-out and mark every list that gets retyped.
Fixtures, modes, addresses and positions held once, read from the plot or the venue's house rig.
Patch sheets, cable lists, labels and power per phase come out of that record, in your layout.
In Vaib, the software learns the actual rig in the room and lights the show live. Most companies start smaller: AI that reads riders and drafts the quote.
Move a fixture and every list, label and plan follows. The crew get the latest version, not last week's PDF.
After
The plot stays the plot. Everything that was retyped, recounted or re-sent comes from one place.
Data and security
Client budgets, artist riders and unannounced shows are confidential. The setup reflects that from the first line of code.
A dedicated server in the EU, or your own office server.
AI providers configured for zero retention and contractually barred from training on it.
Confidential shows processed by open models on your own hardware. Nothing leaves your building.
Source code, data and documents are yours, with exports in CSV, Excel and JSON at any time.
Process
Nothing is built that you haven't seen first.
We follow one of your real shows or installs from start to finish and map where your hours go. You get a clear scope and price before anything is built.
Every screen and your document layouts, clicked through together and changed before any code is written.
Short build blocks, each ending in a review where your own files go through the real thing.
Training, user and admin guides, the source code and your data. Small changes stay easy afterwards.
Typical ranges from our service pages, not commitments. The process review gives you the real number.
Background
Hola Studio lights concerts, theatre and festivals, and built Vaib, the first AI lighting design platform. Patch sheets, riders and get-outs are our own late nights — we speak your language.
North Sea Round Town, Batafest and others
2026
Lighting design and operation for concerts, theatre, club nights and festivals since 2022 — from a 15th-century church in Rotterdam to a touring orchestra — and the field work behind Vaib, our AI lighting designer.
Internal product
2024
The first AI lighting design platform — it learns the actual rig in the room and lights the show live.
Jeanine Verloop
2024
A kinetic glass sculpture that sings and sometimes shatters, driven by sound below the range you can hear.
Clients include North Sea Round Town · Batafest · Museum Boijmans Van Beuningen
FAQ
No. Your plotting tool and rental system keep doing what they're good at. We connect to them through exports, file formats, APIs and scripts, and move only the retyping, checking and document work.
No. We use EU-hosted AI with zero retention and no training on your data, and for confidential shows the AI can run entirely on your own server.
Yes. A platform can be hosted on a dedicated EU server in your name, or on the server already in your office, with local AI models for confidential work.
Often the first win is small: one script that turns a rider into a quote, or one generated patch sheet that saves an evening per show. Use the check on this page; if a task is frequent, repeatable and already digital, it's usually worth a conversation.
We don't publish prices, because scope decides it. The process review maps one of your real shows or installs and ends with a clear scope and price before anything is built.
Typically 1–4 weeks for a process review, 4–12 weeks for a focused AI tool or automation, and 6–14 weeks for a company platform.
You do. You receive the source code, the data and the infrastructure accounts, with no lock-in.
Yes. We light concerts, theatre and festivals ourselves, and we build Vaib, an AI lighting platform tested at live concerts. We've been the person at the desk at two in the morning.
Tell us how a show or install moves through your company today. We'll tell you honestly what's worth automating, and what isn't.
Hola's studio assistant
Hola — I'm Ola. I know how the studio works: what we build, how we scope it, and what engagements usually cost.
Ask me anything, or tell me what you're trying to make.