Scoping call
Thirty minutes, and you leave with numbers
Not a discovery call and not a pitch. We ask the four or five things that decide what an event costs, and tell you what we would run. If we are the wrong fit we will say so on the call rather than send a proposal.
What we cover
The half hour, in order
We keep to this because the last five minutes are the useful ones, and they only work if the first twenty happened.
0–5 min
The event
Date, city, venue if chosen, expected headcount, number of halls.
5–15 min
The arrival curve
How people actually turn up. If you have last year's registration timestamps, this is where they earn their keep.
15–25 min
What we would run
Counter sizing, access control, streaming or translation if relevant — and what we would talk you out of.
25–30 min
Money and dates
An indicative range, what would move it, and when we would need a decision to hold kit.
Worth having to hand
Five things that make the call useful
None of it is mandatory. Approximate answers are fine — we would rather model from a range than wait for certainty.
- The show dates, and build/derig days if you know them
- Expected delegate count, even as a range
- How many halls run in parallel
- Last year's registration export, if this is a repeat event
- Any languages you need covered
How to arrange it
Email is fastest
Send the dates and headcount and we will come back with two or three slots, IST business hours, usually the same working day. Calls run on whatever you already use — we do not make you install anything.
For engineering work rather than an event, go direct to the ZebIQ team.