Event software, built from backstage reality.
A producer-first event platform. The MVP focuses on the operational spine of an event — events, locations, agendas, sessions, speakers, showflow and an audience front-end. The long-term vision includes AI-assisted imports and live cue support, but those are goals rather than shipped features. In active build.
The problem
Most event tools are built for one clean slice of the job. Registration sits in one system. The agenda sits in another. Speaker data is buried in email threads. The showflow lives in a spreadsheet. The website is edited somewhere else. Files are in a folder nobody can find. The stream is handled by a separate team with its own version of the truth.
Backstage, that is a mess. The producer becomes the glue. Last-minute changes get retyped into four places. Speakers get briefed from the wrong version. The public agenda drifts from the showflow. I have lived this on enough shows to know the issue is not one missing feature. It is a missing point of view: most event SaaS is built for marketing teams first. EventBlok is being built for the people who actually have to run the event.
Why I am building EventBlok
EventBlok is being built by a producer, not a generic SaaS team trying to discover events from a spreadsheet. I have produced live, hybrid and broadcast events for almost three decades. I have showcalled, vision mixed, run streaming, built motion graphics, programmed QLab and architected a hybrid event platform with Munib Quzabi for JATO Dynamics. That platform supported livery streaming, voting, polling, speaker bios, a social wall and access from China.
EventBlok is the product version of that experience. The goal is to take what usually gets custom-built in panic and turn it into a proper system: structured, reusable, editable and designed around the real pressure of show day.
What the MVP focuses on
These are the areas the MVP is scoped around. Some are in active build, some are still being shaped. EventBlok is not open for general signup yet.
Events: the top-level container, with the metadata everything else hangs from. Locations: venues, rooms and stages, so sessions sit in real space. Agenda: the public-facing schedule, connected to the production-side data so the website and showflow do not drift apart. Sessions: structured records for each talk, panel, awards moment or content block. Speakers: one source of truth for bios, headshots, contact details and session links. Showflow: a backstage run-of-show view designed to be readable by a showcaller under pressure. Audience front-end: a public web layer generated from the same data the production team is using. Embeds and a mobile-friendly experience that works on a phone in a venue with poor signal.
What the long-term vision includes
These are longer-term goals, not current features. Treat them as direction of travel, not a shopping basket of promises.
File management for speaker decks, video assets and run-of-show documents. Speaker prep flows, so speakers can upload assets and confirm details themselves. AI-assisted spreadsheet import, turning a client agenda in Excel into structured sessions. AI showflow generation from a draft agenda, as a first pass for a human producer to edit. Live cue support for the showcaller during the event. Voice-commanded showflow control. An AI teleprompter tied to session data. Sponsor tools. Audience engagement features: voting, polls and Q&A in the same look and feel as the rest of the audience layer.
If you are evaluating EventBlok today, evaluate the MVP scope and the direction. Do not evaluate it as if every future feature is already shipped.
Roadmap
- MVP
Run an event end to end
Events, locations, agenda, sessions, speakers, a showflow readable under pressure, an audience front-end generated from the same data, embeds and a mobile-friendly experience. In active build.
- VISION
AI-assisted production
AI spreadsheet import, AI showflow generation from a draft agenda, live cue support for the showcaller, voice-commanded showflow control and an AI teleprompter tied to session data. Direction of travel, not shipped.
- VISION
Speakers, sponsors & engagement
File management for decks and run-of-show, speaker prep flows, sponsor tools, and audience engagement — voting, polls and Q&A — in the same look and feel as the rest of the audience layer.
Why this connects to my live event work
EventBlok is not a random side project that happens to use the word “event”. It is the product version of systems I already build by hand.
When I architected the JATO Dynamics hybrid platform and led the build with Munib, the brief involved a global launch with livery streaming, speaker bios, awards, voting, a social wall, polling and access from China. It worked because the platform was shaped around how the event actually ran, not bolted on after the production plan was finished. When I showcall MCM Comic Con sessions in the ICC Auditorium, including the Cosplay Central Crown Championships in front of around 3,000 in the room, the same pattern repeats: the data, agenda, cues, graphics, speaker information and audience view all need to agree. EventBlok is the attempt to make that agreement normal instead of heroic.
Where websites fit in
EventBlok also connects directly to my web work. Event pages, agendas, speaker profiles, private portals, embeds and audience tools are still websites. They need to be fast, clear, mobile-friendly, editable and connected to the right data.
That is why the stack matters. The public site should not be a decorative skin floating separately from the production database. The content the audience sees should come from the same structured records the producer trusts backstage.
EventBlok — common questions
No. EventBlok is in active build. The MVP is not yet open to general signup. The honest status is: in development, with a small number of pilot conversations under way.
I am not committing to a public date yet. I would rather ship the MVP when it is solid for a first cohort of pilot events than hit a date with something half-built. If you want to be told when it is ready, get in touch and I will keep you on the list.
Possibly. I am talking to a small number of producers and event teams about pilot events. Pilots need to be real events with real constraints, not a soft demo. If that sounds like you, ask about EventBlok and we can have a proper conversation.
The intent is a producer-first product, not a marketing-first one. Most event SaaS is strong on registration and weak on the run of show. EventBlok is being designed from the showflow outward, with the public-facing layers generated from the same data.
That is the direction of travel. Live cue support and tighter links to streaming and showcalling tools are on the long-term vision list, not in the MVP. If you have a specific workflow you want EventBlok to fit into, tell me. Real use cases shape the roadmap.
That is part of the point. The audience front-end, agenda, speaker pages and embeds should come from structured event data, not from someone copying text into a separate marketing site at midnight. EventBlok is being designed so the production system and the public event website stay connected.
Two ways to engage
Ask about EventBlok
If you run events, produce events or buy event tech, I would like to hear from you. Honest input on the MVP shapes what gets built next. The MVP is not yet open to general signup — I would rather ship it solid for a first cohort than hit a date half-built.
Ask about EventBlok
Discuss a pilot event
I am talking to a small number of producers and event teams about pilot events. A pilot needs to be a real event with real stakes, not a demo. If that sounds like you, let's have a proper conversation — pilots feed real constraints into the build.
Discuss a pilot event