Ideation
Define concept, scope, budget, and feasibility.
The intent
This is where the event gets its shape. Objectives, audience, format, budget, a provisional timeline. We're not building anything yet, we're deciding what's worth building and whether we can deliver it well.
The concept is approved, the provisional programme holds together, and we've flagged anything technical that could bite us later. Nothing moves to Setup until someone's signed off the direction.
The agent → human handoff
Every agent task runs the same governed loop. The agent is triggered, it drafts, a named human reviews, and only then does it publish. Same shape in every phase.
The work, by actor
Craft & judgement
- Event Manager — Define objectives, audience, format, budget and provisional timeline for approval.
- Marketeer — Test positioning, themes and channels; estimate demand and registration targets early.
- Producer — Sketch programme flow, shortlist speakers, draft session titles and briefs.
- Technical Production — Advise on a feasible production approach: remote guests, risks, contingencies.
- Technical Support — Confirm platform capabilities, required features, integrations and constraints.
- Commercial — Draft the sponsor inventory: packages, placements, deliverables.
Scale & speed
- Producer — Pull candidate speakers from the library and pre-fill shortlist.ownerProducer · trigger: on brief
Reliability
What the client gets
A clear event concept they've approved. A provisional programme. An honest early read on what's feasible and what isn't.
The safeguard
We commit to a format that can't be delivered with remote speakers or the translation requirement.
Technical feasibility and risk flags are part of Ideation, not an afterthought. We say no early if we need to.
The thread continues
Phase tokens bound to the Colour Registry · wheel engine v1.3 · multi-actor delivery model.