event67 for agencies
For an agency, event67 is a multi-tenant console where each client's event carries that client's brand and nothing of yours, and where the cost of an event is a number you can quote before you win the work. Every event has its own theme, its own attendee list and its own bill.
Your day with event67
Pitching
You quote a number instead of a range
Pricing is per activated attendee with a hard per-event ceiling, so a proposal can carry a real figure at the client's expected head count rather than the range everyone else quotes. If the client's event under-fills, they pay less; if it over-fills, the ceiling protects the line.
Winning it
You set the client's brand, not yours
Themes belong to events. Each client gets their logo, colours and typography, and the app carries their identity end to end. Nothing on an attendee's screen says which agency built it.
Building
You do it in an afternoon
Sessions, speakers, sponsors, theme, import, invite. No development work, no build, no store submission unless the client wants their own branded listing, in which case add two to three weeks for review.
On site
Your staff hold scoped access
Per-event moderator roles let you put a freelancer on the photo queue for two days without giving them your whole client portfolio. Scope is the control that matters here: moderation actions are not attributed to a person, so a disputed removal cannot be looked up afterwards.
After
You hand the client a record
The end-of-event report archives the Q&A, polls and photos, and engagement analytics give you the numbers for the wash-up deck. Billing runs 48 hours after the event ends, so the cost is known before the invoice conversation.
What you control
- Whose brand appears
- The client's, per event. Themes are event-scoped rather than organisation-scoped, which is the property that makes multi-client work possible at all.
- Who on your team sees what
- Super-admin, organisation admin and per-event moderator. A contractor booked for one event gets one event.
- Which features are on
- Photos, Q&A, polls, the directory and connections are per-event switches, so a conservative client and an extroverted one are the same product configured differently.
- Whose developer account
- A branded store listing can sit under the client's Apple and Google accounts or under ours. Under the client's, the listing is unambiguously theirs, which is usually the right answer for an agency that does not want to hold an asset it will have to hand back.
- The currency
- Chosen when the event is created and locked when it goes live. Local prices are local prices, not conversions, so a Canadian client is quoted in Canadian dollars.
What this costs you, and what you can charge
The commercial shape is unusual enough in this category to be worth spelling out.
There is no platform fee, no seat charge for your team, no per-event licence and no annual minimum on the standard terms. What you pay is driven by activated attendees on each event: the first 50 are free, each one after that is $5, and one event can never exceed $4,750. An event that does not happen costs nothing.
For an agency, the two consequences are direct. Small client events are close to free, which makes it viable to offer an app to the client whose event is ninety people and who would never have paid for one. And the ceiling means the largest client event on your books has a known worst case, which is the number a finance director wants before signing anything.
If your volume is genuinely high, a Season Pass converts credits into a lower effective rate across unlimited events, with credits rolling over for twelve months and overage billed at the standard rate rather than a penalty.
What you charge your client is your business, and we do not police it. What we would say plainly is that the pricing is published, so a client who looks is going to find it, and a margin you are comfortable explaining is a better position than one you are not.
What you cannot promise a client
An agency's risk is different from an organizer's: you make commitments in a pitch document weeks before anybody touches the product. These are the items to keep out of that document.
- No white-labelling of the console. The attendee app carries the client's brand; the organizer console is an internal tool and looks like one. If you have promised a client-branded admin, that is not deliverable.
- No reseller portal, no partner tier, no margin programme and no agency dashboard aggregating clients. Each event is an event.
- No API, no webhooks and no integration with your production or project management stack.
- No custom development, custom screens or custom fields for a client who wants something different.
- No registration or ticketing, so the client's registration platform stays and you import from it.
- No exhibitor lead retrieval, no badge printing, no streaming and no floor plans, all of which appear in client RFPs regularly.
The commonest way an agency gets hurt here is an RFP response that lists lead retrieval or a branded admin as included. Both are firm noes. Everything else in the honest-boundary lists on the feature pages is worth reading before you write a response, not after.
Running several clients without mixing them up
The console is multi-tenant, and the practical unit of separation is the event. Attendee lists do not cross events. Themes do not cross events. Billing is per event and lands 48 hours after each one ends, so a client's cost is attributable to that client rather than pooled into a monthly number you have to unpick.
The piece to be deliberate about is your own team's access. Per-event moderator roles exist precisely so that the freelancer running the Thursday photo queue for one client cannot see another client's roster. Setting that up properly takes two minutes at the start and is the difference between a normal engagement and a difficult phone call.
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
Can we run several clients from one login?
Yes. The console is multi-tenant and the separation unit is the event: attendee lists, themes and billing are all per event. Your team's access is scoped by role, so a contractor booked for one client's event gets that event and nothing else.
Whose brand does the app carry?
The client's, completely. Themes belong to events rather than to your organisation, so each client's app carries their logo, colours and typography, and nothing on an attendee's screen names the agency.
Is there a reseller programme or agency margin?
No. There is no partner tier, no reseller portal and no margin programme. You pay the published per-attendee price on each event and charge your client what you charge them. If your volume is high, the Season Pass lowers the effective rate across unlimited events.
Can we white-label the organizer console for a client?
No. The attendee app is white-labelled; the console is not and looks like an internal tool. If a client expects a branded admin experience, that expectation needs correcting before the pitch rather than after.
What happens to a client's app if they leave us?
If the store listing sits under the client's own Apple and Google developer accounts, it is theirs and stays theirs, which is usually the arrangement worth setting up for exactly this reason. Under ours, the app is tied to the account it was published from.
Can we get a single invoice across all our clients' events?
Billing runs per event, 48 hours after each one ends, which is what makes a cost attributable to a client. A Season Pass is the closest thing to a pooled arrangement: prepaid credits drawn down across unlimited events.
Keep reading
What clients ask about
Where else this is covered
Run one and see
The first 50 attendees on an event are free, so a first event under that costs nothing at all.