Why Heike
Built for a year of events, not a single one
Heike runs several events a year for a team small enough that everyone does more than one job. That shapes what is in it, and what is deliberately not.
Who this is for
Heike suits some organisations and not others. Here is where the line sits.
It fits if
- You run several events a year rather than one
- The team running them is small enough that everyone does several jobs
- Presenters and sponsors are a large part of the work
- You need to know where the money went, per event and across the year
- You want to keep the ticketing platform you already use
It does not fit if
- You run a single large trade show with a department behind it
- You need exhibitor floor plans and booth sales, which are not in it
- Your procurement requires a signed multi-year agreement
Fifty seven of 101 recurring tasks are looking after people
Our delivery recipe has 101 recurring tasks in a year of events. Fifty seven of them are presenters, sponsors and attendees. The rest are budgets, schedules and logistics.
22
Presenters
Chasing bios, headshots, slides and contracts
21
Sponsors
Proving what a partner actually got
14
Attendees
Registration, comms and the day itself
Counted from our delivery recipe.
Heike runs The Outlook
The Outlook runs a festival, a conference, an awards night and a partner program each year, and Heike is the production system behind them. It is not a demo environment.
