Multiple clients. Multiple events. One workspace.
Nine briefs. Four producers. Clients who all expect their event to be the only one. Nine live briefs, four producers and a client who wants their own branding on the attendee portal. EventBlok holds every event as its own structure inside one workspace, so nothing bleeds between accounts and nothing is rebuilt per client.
- 9
- live events, one workspaceDescribes how EventBlok works — not a measured statistic.
- 1
- branded portal per clientDescribes how EventBlok works — not a measured statistic.
- 0
- templates rebuilt per briefDescribes how EventBlok works — not a measured statistic.
- ∞
- events per accountDescribes how EventBlok works — not a measured statistic.
Agencies pay the rebuild tax nine times over. Every client gets the same spreadsheet, the same speaker pack and the same showflow, built again from nothing because the last one lived in a folder for a different account.
Every event is its own record. Shared nothing, except the way you work.
Client A cannot see Client B. Your producers can see both. The house style, the formats and the department conventions carry across without the content ever mixing.
- ✓Separate events per client, one workspace
- ✓Roles decide who sees which account
- ✓Your conventions travel between briefs
The portal looks like the client, not like software.
Colours, type and logo per event. The attendee sees the client’s event, and you are not explaining to a marketing director why their conference is wearing someone else’s branding.
- ✓Per-event branding on the audience portal
- ✓Embeds that sit on the client’s own domain
- ✓First five agencies: fully branded platform
Last year’s event is this year’s starting point.
Duplicate a whole event and shift the dates. Or hand the new brief’s spreadsheet to Event Builder and get a Candidate Draft back to edit rather than a blank page to fill.
- ✓Duplicate an event and shift its dates
- ✓Import the client’s files into a draft
- ✓Formats and department conventions reused
Nine events, and one producer holding four of them.
One place to lookOn the roadmap
Every live brief, its dates and where it has got to. Not nine folders and a shared drive nobody has opened since Tuesday.
09:00Opening keynoteMainstage · Hall AConfirmed10:30A field guide to honest interfacesCraft · Studio 2Confirmed13:30Fireside with regulatorsSystems · Hall ADraft15:00Workshop: writing a run of showCraft · Studio 1The programme itself — every session with its track, room and speaker. The same rigour per clientOn the roadmap
Cue-level showflows, speaker prep and prompter on every account, because it is the same product rather than the effort of setting it up again.
09:30Opening keynoteAida OkaforLive09:45Panel: honest interfaces3 speakersNext10:15BreakFoyer10:30Payments deep-diveSystems trackVIDEOVT-2AUDIOMic 4LXState 3The running order the crew calls from — one cue live, the next one staged. Handover is a linkOn the roadmap
Clients and freelancers get a view rather than an attachment. Current when they open it, whoever they are.
AOAida OkaforOpening keynote · slides inReadyLOL. OrtizPayments panel · bio missingChasingMKM. KwanCraft workshop · slides inReadyRBR. BaptisteFireside · headshot missingChasingWhat each speaker still owes you, without the chasing thread.
The agency parts.
Crew who come and go
On the roadmapGive a freelancer the one event and the one department they are on, for the days they are on it.
Show the work
On the roadmapA structured programme in a pitch is more convincing than a slide of a spreadsheet.
What actually ran
On the roadmapEach event keeps what happened, not the plan. Useful evidence when the client asks next year.
