For buyers
Sourcing you can defend, at the speed events actually run
Define the requirement once, invite the suppliers you trust, and compare what comes back on equal terms. The governance comes with the workflow instead of being assembled afterwards.
Structured sourcing without the bureaucracy
A small request stays small. Controls appear as value, risk and complexity increase, so a requester booking one AV crew does not meet enterprise procurement machinery.
Approved panels and frameworks
Import the suppliers you already trust, with panel status, categories and service regions. Invite from the panel, from the wider network, or by controlled external invitation.
Offers you can actually compare
Structured quote headers, line items, options, exclusions, tax treatment and terms — normalised side by side at total, lot and line-item level.
Approval routing that reflects your policy
Route by spend, category, department, risk class and exception flags. Comments, decisions, delegations and escalations are recorded as they happen.
An audit trail that reconstructs the decision
Every invitation, clarification, submission, evaluation, approval and award is written to an immutable log. Nothing depends on someone remembering.
Award that becomes a delivery record
The awarded scope, timeline, contacts and documents become an operational handoff record. The delivery team does not re-key anything.
The process
What a sourcing round looks like
- 01
Request
Build an event-native brief: dates, venue, delivery windows, lots, specifications and required documents.
- 02
Source
Invite suppliers from an approved panel, the wider network, or by controlled external invitation.
- 03
Compare
Read normalised offers side by side at total, lot and line-item level, with exclusions and options visible.
- 04
Approve
Route the decision by value, category and department. Comments and decisions are recorded as they happen.
- 05
Award
Award a whole request, selected lots or partial quantities. Award and decline notices go out from the record.
- 06
Hand off
Produce an operational record with final scope, timeline, contacts and documents for the delivery team.
Governance
Roles that match how procurement decisions are really made
Permissions are scoped by organisation, workspace, project, request and lot. On higher-risk procurements, request ownership, evaluation and award authority can sit with different people — and in a small team, one person can hold several roles.
| Role | What it does |
|---|---|
| Requester | Creates and manages requests, invites suppliers, handles clarifications. |
| Procurement manager | Publishes requests, controls the process, runs comparison, recommends award. |
| Approver | Approves, rejects, requests changes, or delegates where policy allows. |
| Finance reviewer | Reviews budget, cost codes, payment terms, tax and supplier readiness. |
| Evaluator | Scores and comments on offers without holding award authority. |
| Viewer or auditor | Read-only access to approved records and the full activity history. |
Start with one real request
A pilot does not begin with a rollout. It begins with one live sourcing round, your existing suppliers, and a decision you needed to make anyway.