Built by the person who has to call the show.
Every producer knows the same evening: a change comes in, and the next twenty minutes go on making five documents agree instead of making the show better. EventBlok is the attempt to drain that.
Events are usually rebuilt five times.
The organiser has a spreadsheet. The audience sees a website. Speakers receive separate documents. Crew work from another showflow. The presenter uses a different script.
None of those are wrong on their own. The problem is that they are copies. By the time the doors open, the same information has been retyped, reformatted and rechecked in five places, and at least one of them is out of date — usually the one on a screen in front of an audience.
Then something moves. A speaker lands late, a session overruns, a room changes. The change is easy. Propagating it to five documents, three teams and a published programme is what actually costs the day.
EventBlok keeps them connected. Build once. Publish where it matters. Update everywhere.
The programme, the audience portal, the speaker material, the locations, the showflow and the prompter script all read from the same event structure. Change the event and the views change with it — because they were never separate copies to begin with.
From live production to software.
EventBlok comes out of nearly three decades of live production — conferences, global hybrid events, main-stage entertainment, multi-camera streaming, speaker management and show control. Enough years to see the same failure repeat in different buildings with different budgets.
An early AWS-supported proof of concept, developed with Devoteam, explored how AI could make the most repetitive part of event planning faster: turning messy source material into structured sessions, speakers, timings and locations that a producer could then review.
The aim was never to let AI run an event. Live events need judgement — someone who understands the room, the crew, the presenter, the audience and the inevitable change five minutes before doors open. That principle survived into the product: AI can organise, suggest and accelerate; people approve.
What was left after the proof of concept was the more useful idea underneath it. An event should have one connected structure. Build the programme once, then use it to power the audience agenda, speaker preparation, locations, production showflow and presenter tools.
Multi-camera, live audience — the room EventBlok was designed backwards from
Why I am building this.
I have spent years producing live events, calling shows, directing multi-camera productions and working with the people who have to make an event work when the clock is running. I have also built the websites and platforms behind those events, which means I have watched the same information get rebuilt on both sides of the wall.
Every producer I know has a version of the same evening: a change comes in, and the next twenty minutes are spent making five documents agree instead of making the show better. That is not a tooling gap anyone celebrates. It is just the water we swim in.
EventBlok is my attempt to drain it. Not another isolated agenda tool, and not another production spreadsheet — a connected workspace for the people planning the event, publishing the programme and running the show.
If you run events and something here is wrong, tell me. I would rather hear it from an operator than discover it at 14:00 on a show day.
Nicolae Ciobota — Founder, EventBlok · producer, showcaller, technical director
Six rules the product is held to.
The event is the record, not the document
A programme is not five files that happen to agree. It is one structure that every view reads from — the portal, the speaker pack, the showflow, the script.
Built for the person holding the comms
Show callers, operators and crew are the hardest users to satisfy and the easiest to ignore. If it does not work at five to doors, it does not work.
AI proposes, a producer decides
Event Brain can structure, suggest and accelerate. It does not approve, publish or run anything. Every suggestion stays reviewable.
Boring where it matters
Timings, rooms and cues should be dull, exact and current. Save the personality for the audience-facing pages.
One event, many views
An attendee, a speaker and a vision mixer need completely different screens showing exactly the same truth.
Made by people who have run the show
Every feature has a specific bad night behind it. That is the test: would this have helped that night?
The shape of the platform.
MVP 1 — The connected event workspace
Events, locations, agenda, sessions, speakers, showflow, prompter, the audience portal and embeds — the full path from first programme draft to the final cue.
MVP 2 — Out to the room and the wider crew
Venue signage driven by the same record, and a producer dashboard that shows the state of the show rather than the state of a document.
API — The event spine, addressable
Read and write the event structure from the systems you already run: registration, ticketing, CRM, streaming platforms and your own tooling.
In public, with operators.
Features are shaped in conversation with the people who will be holding the comms when they get used: producers, show callers, operators, speaker managers and the organisers who have to publish the thing. If a feature cannot survive a real running order, it does not ship.
The work is written up as it happens in the Journal — what was built, what broke, and what a live show taught us that a roadmap could not.
Real running orders
Every view is tested against events that actually happened, not a demo dataset with three tidy sessions.
Build notes in the open
Decisions and trade-offs published as we go, including the ones that turned out to be wrong.
The person who built it
During early access, support comes directly from the founder. The Founding Five keep that direct line as EventBlok grows. No ticket queue between you and the answer.
Build your first event with me.
EventBlok is in early access. Bring the real event you have coming up: an hour together in the Event Wizard turns it into a working programme, and then the platform is free for that event — up to 1,000 named attendees, 5 editors and 50 production devices. Stream credits are separate. During early access you are talking directly to the founder, and the Founding Five keep that direct line as EventBlok grows.
A better event experience should still look and feel like your event. Publish your first event under your own brand — your logo, colours and event identity — at no charge at all. Build the event, create the programme, run the show and publish an agenda attendees can use, all under your event brand.
Where we are.
Based
United Kingdom — working across the UK, Europe and internationally.
Founder
Press
Build the programme once.
Then give every person — attendee, speaker, show caller, operator — the right live view of it.