The conference app for agencies and event producers
An agency's problem is not one event. It is fourteen clients who each want an app that looks like theirs, a team that must not see each other's clients, and a cost per event that has to survive being marked up.
A planning figure for a typical agency-delivered corporate conference. Agencies run a wide spread, from a 60-person board offsite to a 5,000-delegate congress.
Fourteen clients, one console
For an event agency or production company, event67 is a white-label event app you deploy per client: a branded app published under the client's own name, a multi-tenant console with roles scoped to a single event, and per-event pricing with a hard ceiling that makes a quote defensible. There is no reseller portal, no client sub-billing and no margin tooling, so the commercial relationship is yours to manage.
A different brand for every client
Each client's app carries their logo, colours and typography through every screen, and the branded apps are published to the App Store and Google Play under the client's own name. That is what makes the white-label claim literal. The contrast checker warns when a client's palette falls below WCAG AA on a given pair and confirms before saving, so an off-brand approval is a documented decision rather than an accident.
One console, many clients, scoped access
The console is multi-tenant from day one. Organizations hold events, and access is role-based across four levels, from super admin through organization admin to moderator. A freelance producer brought in for one congress gets moderator access to that congress and nothing else. Team chat and billing carry audit trails, which is a narrower answer than clients often expect, so say so plainly.
A repeatable delivery pattern
The build is the same shape every time: create the event, apply the client's theme, load tracks then sessions then speakers and sponsors, set true RSVP capacities, import the delegate list from the client's registration platform, brief the moderators. An agency that runs this ten times gets faster at it, which is the property that makes an app a service line rather than a project.
A quote you can defend
The per-event price stops rising at a thousand activated delegates, and delegates who never open the app are never billed. That means an agency can quote a client a fixed maximum for the app line before registration numbers are known, which is unusual in this category and commercially useful.
Handover, or not
After the event, the reports archive holds every question, poll and photograph. Whether the client gets console access afterwards is an organisation and role decision you make, not a product limitation. There is no automated client handover flow.
What changes for a service line
The app stops being a per-client procurement
One relationship, many client events, each billed on its own turnout. That removes the worst part of reselling event tech, which is negotiating a new contract for every project.
Small client events become free
Each event carries its own free fifty activated attendees. A board offsite, a press day or a training session for forty costs nothing, which lets an agency include an app in proposals where it previously could not.
Team scope is enforced rather than promised
Per-event moderator roles. Audit trails cover team chat and billing only. When a client asks who on your team could see their delegate list, the answer is a configuration rather than an assurance.
Volume lowers the rate
Prepaid credits pool across every event in a year and the effective per-attendee rate falls as the commitment rises. For an agency with a predictable calendar that is the model that makes the margin work.
Small client events become something you can include
Most agencies drop the app from a proposal below a certain event size because the licence cost cannot be absorbed. Under fifty activated attendees an event is free with the complete feature set, which changes what you can put in a proposal for a board offsite, a press day or a training programme, and it gives a client their first experience of the product at no risk to your margin.
What an agency will want and not find
The commercial tooling is the gap here, not the product. Read this before you build a service line on it.
- No reseller or partner portal, no agency dashboard across clients, and no client sub-billing. Billing is per event to the account holder.
- No margin, markup or commission tooling. Whatever you charge your client is a commercial arrangement outside the product.
- No white-labelling of the organizer console itself. The attendee app carries the client's brand; the console does not.
- No automated client handover or account transfer flow.
- No ticketing, registration or payments, so every client event needs a registration platform alongside this.
- No exhibitor lead retrieval, badge printing or floor plans, which are the three things a congress client asks for most.
- No streaming for hybrid events.
- No API. The supported integration path is a CSV import of the delegate list.
What a 650-delegate client conference costs
Six hundred and fifty delegates activate. Fifty are free and the rest are billable once for the whole conference. Because the ceiling is fixed, you can quote a client a maximum before the registration number is known.
- activated attendees
- 650activated attendees
- billable, after the first 50 are free
- 600billable, after the first 50 are free
- for the whole event, at $5.00 each
- $3,000for the whole event, at $5.00 each
Across a calendar of many client events, prepaid credits pool and the effective rate falls with the commitment.
What you can tell a client
The questions clients ask an agency about a tool the agency chose on their behalf.
| Control | What exists |
|---|---|
| Whose brand is in the store | The client's. Branded apps are published to the App Store and Google Play under the client's own name. |
| Separation between clients | Multi-tenant organizations with events inside them, and roles scoped per event. |
| Who could see the delegate list | Answerable from the role configuration. Audit trails cover team chat and billing only, not moderation. |
| Indexing | Client event sites are noindex and nofollow. Nothing about a client's event is publicly discoverable. |
| The record after the event | The reports archive keeps every question, poll and photograph for the event. |
| Accessibility | WCAG AA contrast checking that warns and confirms before a save. No VPAT, which matters if your client is a public body or a university. |
Last updated
What it costs
- Free up to 50
- activated attendees, on one live event
- $5
- per activated attendee beyond 50
- $4,750
- the most one event can ever cost, whatever happens past 1,000
Activated means the person claimed their invite and opened the app. Not when you import them, not when the invite is delivered, and not if they register and stay home.
Questions people actually ask
Is the app really published under our client's name?
Yes. Branded apps go to the App Store and Google Play under the client's own name, icon and identity. Neither your agency's name nor ours appears in the listing, which is what makes this genuinely white-label rather than a theme.
Can we resell it and set our own price?
There is no reseller programme, no partner portal and no margin tooling in the product. Agencies do include it in their fees, but the commercial arrangement with your client is entirely yours to structure. Billing from us is per event to the account holder.
How do we keep clients separated?
The console is multi-tenant with organizations, events inside them, and roles that scope a person to a single event. A freelancer gets moderator access to one event. Team chat and billing carry audit trails.
Can a client take the account over after the event?
There is no automated handover or transfer flow. In practice agencies either keep the event in their own organisation and grant the client access, or run the event in the client's own account from the start. Decide that at the beginning of a project rather than at the end.
What do we tell a congress client who wants lead retrieval?
That event67 does not do it, and neither does it do badge printing or floor plans. Those are the three things a congress client asks for most and they need a separate vendor. Say it during the pitch, not during build.
What is the cost model across a full calendar?
Either per event, each with its own free fifty activated attendees, which suits an agency with many small events, or prepaid pooled credits at a lower effective rate for a predictable calendar. Both bill to your account rather than to your clients.
Do our clients see event67 anywhere?
In the attendee app, no: it carries the client's name and identity in both stores. In the organizer console, yes, because the console is not white-labelled. If your client will have console access, they will see our product, so decide early whether you are presenting this as your tooling or as a product you have selected for them.
What happens if a client wants their data after the event?
The reports archive holds every question, poll result and photograph for the event and stays in whichever organisation the event was created in. There is no export-and-transfer flow, so the practical answer is to decide at the start of a project whether the event lives in your organisation or in the client's, and to run it there.
Keep reading
The events you run
The features that carry them
Talk to us about your event calendar
One relationship, an app per client under their own name, and a ceiling you can put in a quote.