Enquiry to event day, on one board.
Carry one event record from first enquiry through approval, production, check-in, and live execution.
An event company’s operating system: a sales-to-delivery pipeline, a deep per-event workspace, live event-day screens for the door and the show caller, and registration sites your guests actually see.
For event operators coordinating sales, proposals, vendors, guests, and show-day delivery.
This is Events.
Built from the product's own components and design tokens — the spacing, density, and status colours here are the ones you get after signing in.
Pipeline
- Product launch · 12 Sept180 guests · proposal approved · vendors briefedS$46,800In production
- Annual dinner · 4 NovCosting in progress · venue heldS$88,000Quoting
- Roadshow · 22 AugRun sheet live · check-in openS$31,400Show day
- Conference · Q1Lost — budget moved to next financial yearLost
Sell it on the board. Deliver it on the run sheet.
Carry one event record from first enquiry through approval, production, check-in, and live execution.
Enquiry
Brand launch · 180 pax
New brief
Proposal
Gala dinner · 320 pax
Client review
Production
Conference · 2 days
14 tasks open
Stop rebuilding the event at every handoff.
A quick enquiry card is enough to begin; gated stages reveal the next decisions without demanding the full plan upfront.
Capture the enquiry
A card on the board in thirty seconds.
Quote and win
Costing to proposal to client approval, tracked.
Deliver
Vendors, budget, run sheet, and tasks in one workspace.
Run the day
Check-in at the door, mission control backstage.
The mechanisms behind Events.
Not features — the guarantees. Each one is enforced in the product rather than promised in a policy.
- One record, every stage
- The enquiry, the costing, the proposal, the vendors, the run sheet, and show day are all the same event row. Nothing is re-created at a handoff.
- Gated progression
- Stages unlock as the information that makes them meaningful arrives, so a quick enquiry card is enough to start without demanding the full plan.
- Loss reasons are required
- Closing a deal as lost requires a reason, which turns the pipeline into a record of why business is won and lost rather than a list of dead cards.
- Live from the same plan
- Guest check-in and backstage mission control read the current run sheet and task state — not an exported copy that stopped being true on Thursday.
Better together.
The modules share one organization record — connections are built in, not integrations to configure.
Deliver the event without rebuilding its story at every stage.
Put Events to work inside the same platform as the rest of your operation.