Run the whole show from one file.
Agenda, showflow, autocue, speaker prep and the audience front end — one record, one timeline. Built by people who have called shows, for the people who call them.
Launch benefit — white-label on the first fifty events.
Lena leads risk at Northwind, where she rebuilt the real-time fraud stack now scoring 1.2M transactions a minute.
Adeyemi shapes payments policy at BankCo and sits on two industry working groups on open banking.
Novak designs detection systems for high-volume marketplaces, focusing on model drift in production.
Every person here is downstream of one running order.
The audience, the speaker walking to the wing, the operator on cue 48 and the phone in somebody's pocket. Build the programme once, then give each of them the right live view of it.
Plan your branded event →One event spine. Many live views. The same record, read four different ways at the same moment.
Good morning. Before we start, two things about the next ninety minutes…
The programme you can see on your phone is the one we are running from.
One event spine. Many views. Build the programme once, then give every person the right live view of it.
01Plan the event
- Give it what you know about the event, plus the spreadsheets and documents you have been sent.
- It builds the programme and structures the speakers, resolving what it can safely resolve.
- What it cannot resolve, it asks you about — with the source attached, so you can check it.
- You get a Candidate Draft to approve. Nothing becomes the event until you say so.
02Publish the programme
- Give attendees a searchable event portal with programme, speakers and venue detail.
- They filter sessions, save a personal agenda and export it to their calendar.
- Speakers get their session, their time, their room and their preparation material.
- Change the event and every published view changes with it — no republish step.
03Run the show
- Turn the published programme into a cue-by-cue showflow with timings and departments.
- Show callers, operators and crew work from connected views that stay in step.
- The prompter follows the same running order, with operator control and voice-following.
- Ask the event, or a single file, a question and get an answer you can check.
Six documents, drifting apart.
The organiser’s spreadsheet, the public website, the speaker pack, the showflow, the script and the sign at the end of the corridor. All describing one afternoon, all maintained separately.
Everything gathers onto one record.
Sessions, times, rooms, people and production detail live in one structure. Nothing is a copy, so there is nothing to reconcile.
One change, and the whole stack moves.
Move a session and every surface reading from it is already correct. No republish step, no screenshot in a group chat, no version that still says 14:00.
Each person gets the view they need.
An attendee, a speaker and a vision mixer need completely different screens showing exactly the same truth. That is the whole product.
- 01 — Today
Six documents, drifting apart.
The organiser’s spreadsheet, the public website, the speaker pack, the showflow, the script and the sign at the end of the corridor. All describing one afternoon, all maintained separately.
- 02 — Build once
Everything gathers onto one record.
Sessions, times, rooms, people and production detail live in one structure. Nothing is a copy, so there is nothing to reconcile.
- 03 — The spine
One change, and the whole stack moves.
Move a session and every surface reading from it is already correct. No republish step, no screenshot in a group chat, no version that still says 14:00.
- 04 — Many views
Each person gets the view they need.
An attendee, a speaker and a vision mixer need completely different screens showing exactly the same truth. That is the whole product.
Eight parts of one system. Each is useful alone. Wired to the same timeline, they replace the whole spreadsheet stack.
Describe the event. Approve it into existence. The builder drafts the venue, agenda, speakers and showflow — you sign off each piece.
Nothing is created behind your back. Every generated item waits for an operator to approve, edit or reject it.
- ✓Brief in plain language, structured event out
- ✓Item-by-item operator approval
- ✓Everything editable afterwards like any record
Already have a spreadsheet? Drop it in. Any CSV or Excel, any columns — it finds the sessions, checks the times, builds the event.
One import produces a full agenda, a starter showflow per session, and a page for every speaker it spots.
- ✓No template — it adapts to your file
- ✓Times normalised, overlaps flagged
- ✓Speaker pages created with draft bios
| raw time | raw title | room |
|---|---|---|
| 09:30 | Opening keynote | Main Stage |
| 11:00 | Panel — Real-time payments | Main Stage |
| 1:30 PM | parsing. | studio |
| 15.00 | Workshop – fraud | hall2 |
| source column | mapped to | state |
|---|---|---|
| col C | start time | ✓ confident |
| col D | session title | ✓ confident |
| col F | room | ✓ confident |
| col H | speaker | pending |
Move one session, the day re-times itself. Durations, gaps and clashes are modelled — not typed into a cell.
Multi-track, multi-day, multi-venue. Drag a session and every downstream time and cue follows it.
- ✓Downstream re-timing on every change
- ✓Same-room clash detection
- ✓Venues, rooms and days as real structure
| start | session | room | track |
|---|---|---|---|
| 09:30 | Opening keynote | Main Stage | A |
| 11:00 | Panel — Real-time payments | Main Stage | A |
| 13:45 ⟲ | Fireside — Regulators | Studio | B |
| 15:15 | Workshop — Fraud models | Hall 2 | B |
| 16:45 | Closing remarks | Main Stage | A |
Call the show, and drive the autocue from the same file. The prompter is built into the showflow, not bolted beside it.
Presenter view mirrors to the operator with voice-locked scrolling and live drift. Mouse shortcuts, and webhooks for Stream Deck via Companion — built for broadcast, not a text scroller.
- ✓Cue-level runsheet with GO / standby states
- ✓Presenter view + mirrored operator view
- ✓Voice-synced scroll, drift meter, Stream Deck webhooks
| cue | action | dept | state |
|---|---|---|---|
| 47.0 | House to half | LX | done |
| 47.1 | VT roll — opener | A/V | done |
| 48.0 | Keynote walk-on | LX | ● GO |
| 48.1 | Lower-third: name | GFX | stby |
| dept | last call |
|---|---|
| FOH | standing by on 48.1 |
| LX | house at half, holding |
| A/V | VT armed |
| GFX | lower-third loaded |
Speakers write prose. You get cues. They describe the session in plain text and the showflow assembles in the background.
No forms to learn. And when a speaker never preps, the analyzer builds a baseline running order from what it already knows.
- ✓Plain-English prep → departmental cues
- ✓Baseline showflow for every session, guaranteed
- ✓Producer keeps the final edit
| slide | content | cue |
|---|---|---|
| 1–4 | Title + agenda | — |
| 9 | Demo clip · 0:48 | 03 |
| 17 | Revenue chart | — |
Lena leads risk at Northwind, where she rebuilt the real-time fraud stack now scoring 1.2M transactions a minute. A former regulator, she writes and speaks on model governance.
Ask the event anything. It answers from the agenda and the showflow — and shows you exactly which records it read.
"When is Lena on?" "What happens before the closing remarks?" "Which sessions have video?" Answers with citations, not guesses.
- ✓Answers cite the agenda or cue they came from
- ✓Reads the live event, not a stale export
- ✓Same brain across every venue and day
| question | answer |
|---|---|
| When is Lena on? | Day 1 · 09:30 · Main Stage |
| Which sessions have video? | 3 sessions · cues 47.1, 52.0, 61.4 |
| Who is on after lunch? | M. Adeyemi · 13:45 · Studio |
| record | type | read |
|---|---|---|
| Day 1 agenda | agenda | live |
| Showflow 47.x | cues | live |
| Speaker profiles | speakers | live |
Know what's in the deck before it hits the screen. Slide count, videos, polls, charts and builds — inventoried automatically.
The surprises that break a show are in the deck. The analyzer finds them, and the flagged slides import straight into the showflow as cues.
- ✓Counts slides, videos, polls, charts, animations
- ✓Flags anything needing an operator cue
- ✓Imports flagged slides as showflow cues
| slide | content | note | cue |
|---|---|---|---|
| 1–4 | Title + agenda | static | — |
| 5 | Market map | build ×6 | animation |
| 9 | Demo clip | 0:48 video | video |
| 12 | Live poll | audience | |
| 17 | Revenue chart | animated |
The front end your attendees actually use. Live agenda, save-to-my-agenda, locations, speaker galleries and bios — on your own domain.
It reads the same record your producers run. Move a session and every attendee's phone updates — no republish, no stale PDF.
- ✓Custom domains, fully branded
- ✓Save to my agenda · locations · speaker galleries
- ✓Live streaming and awards voting landing soon
The agenda drives the showflow. The showflow drives everything else. Change the plan and the run follows; call the show and every downstream surface follows that.
Late ripples forward
A session runs seven minutes over and every downstream time recomputes instantly — cues, room turnarounds, the lot.
Decide with the impact visible
Push the break, trim the Q&A, or cancel a slot — you see what each option does to the day before you commit.
Every surface follows
Signage, prompter, comms and every attendee's agenda update the moment the decision is made. Nobody re-publishes anything.
The rest of the toolkit. Quietly doing the work nobody wants to.
Ask a PDF or a video
Upload the deck, the rider, the VT. Ask how a video starts and ends for the showflow, or get a summary of a 40-page brief.
One event, many places
Venues, rooms and days are first-class. Filter the whole programme to one hall for the crew working it.
One record, every surface
Edit once and embeds, the audience app and the running order follow in under 30ms. No publish step to forget.
Two things we're building now.
Both extend the same record you're already running — no new tool, no second source of truth.
Run your next show on one timeline.
Launch your first event with white-label branding included. Import your spreadsheet, or describe the event and let the builder draft it.