The conference app for enterprise event programmes
A large company does not buy one event app. It buys a way to run forty events a year across business units that will not agree on anything, with a security review in front of it.
A planning figure for a large internal conference. The field shows the ceiling: past 1,000 activated employees, nothing more is charged.
How a large company's event programme actually works
An enterprise event app serves an internal events programme: sales kickoffs, all-hands meetings, leadership forums, functional summits and internal conferences, run by different teams under one company brand. event67 provides the branded app, the multi-tenant console with scoped roles, and a per-event price with a hard ceiling. It has no single sign-on, no HR system integration and no video streaming, which are the three things enterprise buyers ask about first.
One brand, many teams, separate events
The console is multi-tenant from day one. A sales organisation, a functional team and a regional office each run their own events under the same company brand, with organization admins and per-event moderators keeping access scoped to the event a person is actually working on. Nobody has to be given the whole account to run a workshop.
The annual kickoff, which sets the pattern
The largest internal event of the year is usually the first one a company runs on a new app. Tracks by segment, capacity-enforced enablement workshops with automatic waitlist promotion, upvoted Q&A for the leadership panel, and push announcements that deep-link to the session that moved. It exercises everything the rest of the programme will need.
Quarterly all-hands, run the same way each time
Each town hall is its own event, so each quarter's questions, polls and attendance stay separate and comparable. Opening Q&A a week early gives executives a ranked list and time to prepare, which is the difference between a real answer and a deflection.
The long tail of smaller events
Team offsites, function summits, regional meetings. Each carries its own free fifty activated attendees, so a great many of them cost nothing. For a programme with dozens of small events a year, prepaid credits pool across all of them and the per-attendee rate falls as the commitment rises.
The reporting that justifies the programme
Activation against the invited list, session ratings, poll results and the full archive of what was asked. An internal events team is asked every year whether the programme is worth its budget, and this is the first time most of them can answer with something other than a satisfaction score.
What changes across business units
The app is the company's, in both stores
Branded apps are published to the App Store and Google Play under the company's own name, so an employee installs the company's app rather than a vendor's. For a business that spends money on brand consistency, this is the difference between an event tool and an event surface.
Access is scoped, and team chat and billing carry audit trails
Per-event moderator roles mean a regional coordinator can run their own Q&A without touching another team's event. Team chat and billing carry audit trails. Nothing else in the console is logged, which an internal review will want to know.
The budget has a ceiling per event
The price per event stops rising at a thousand activated attendees. For a company planning a global town hall against an uncertain turnout, a fixed maximum is a materially easier number to approve than a rate.
Nobody is billed for people who did not come
The meter counts activation: the employee claimed the invite and opened the app. Importing thirty thousand employees and having four thousand engage bills for four thousand. Invites themselves are unlimited and free.
Procurement happens once, not forty times
The pattern that kills internal event tooling in a large company is that every business unit buys its own, and security reviews the same category four times a year. One organisation with scoped roles and per-event billing means the review happens once and the marginal event costs a CSV import. That is usually a stronger argument to an internal platform team than any feature on this page.
What an enterprise security and IT review will find missing
These are the questions that come up in every enterprise evaluation. Answering them here saves both sides a call, and none of these is a roadmap item we are hinting at.
- No single sign-on. There is no SAML, no OIDC and no integration with your identity provider. Attendees are invited by email address and claim their invite.
- No HR or directory integration. The attendee list is a CSV import for each event, with no live sync and no automatic deprovisioning.
- No video streaming, so a hybrid all-hands runs its broadcast on your existing meeting platform.
- No anonymous questions or anonymous polls. Everything is attributed, which some cultures want and some cannot accept.
- No intranet or collaboration-suite integration.
- Certifications are not something we assert on a marketing page. Ask us directly and we will tell you exactly what exists rather than imply more.
- No in-app attendee account deletion. Deletion is handled by request through a published address and a web page.
What a 2,200-employee conference costs
Twenty-two hundred employees activate. Fifty are free and the price stops climbing at a thousand, so twelve hundred of them cost nothing at all. The bill is identical to a conference of exactly one thousand.
- activated attendees
- 2,200activated attendees
- billable, after the first 50 are free
- 950billable, after the first 50 are free
- for the whole event, at $5.00 each
- $4,750for the whole event, at $5.00 each
For a programme running many events a year, prepaid credits pool across all of them and the effective rate falls with the size of the commitment.
The controls that do exist
Described as mechanisms rather than as badges, because a mechanism is checkable and a badge is not.
| Control | What exists |
|---|---|
| Tenancy | Multi-tenant from day one. Organizations, events within them, and users scoped to what they work on. |
| Roles | Four levels: super admin, organization admin, moderator and attendee. Moderator access is limited to a single event. |
| Audit | Team chat and billing carry audit trails. Q&A and photo moderation decisions are not logged. |
| Attendee visibility | Attendees choose what appears on their own profile. The event site is not indexed by search engines. |
| Content moderation | Photos and Q&A each run open, moderated or admin-only. A reported photo auto-hides pending review. |
| Accessibility | WCAG AA contrast checking in the theme editor, which warns and confirms before a save and never blocks one. There is no VPAT. |
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
Do you support single sign-on?
No. There is no SAML, no OIDC and no identity-provider integration. Attendees receive an invite at their email address and claim it. For many internal events this is acceptable; if SSO is a hard requirement from your security team, it is a genuine blocker rather than a configuration question.
Can we sync the attendee list from our HR system?
No. The supported path is a CSV import for each event. There is no live sync and no automatic removal when someone leaves the company. Practically, this means the list is a point-in-time export taken close to the event.
How is access controlled across business units?
The console is multi-tenant with organization admins and per-event moderators. A team running its own offsite gets moderator access to that event only. Team chat and billing carry audit trails. Other console actions are not logged.
Can we run a hybrid all-hands?
Partly. event67 carries the agenda, the Q&A, the polls, the reactions and the announcements for remote employees exactly as for the room. It does not carry the video. Run the broadcast on your existing platform alongside it.
What is the cost model for forty events a year?
Either each event bills separately with its own free fifty activated attendees, which suits a programme of mostly small events, or prepaid credits pool across every event in the year at a lower effective rate. Both are billed to the organisation, not to attendees.
What do we tell employees about their data?
Attendees control what appears on their own profile. The event site is not indexed by search engines and there is no public listing of your events. Account deletion is by request through a published address and a web page rather than inside the app, which is a known gap and worth stating in your internal communications.
Can different business units be billed separately?
Not by the product. Billing is per event to the account holder, so internal chargeback has to be done from the event-level figures rather than by issuing separate invoices. The console shows the activated count and the amount per event, which is the number most internal recharge processes need, but the split itself happens in your finance system.
What is the fastest path from decision to a live internal event?
The event, theme, agenda and invites are a same-day job in the console. What has an external clock on it is publishing a branded app to the App Store and Google Play under your company name, because store review is outside anyone's control. Start that before the agenda is final; the web version covers you if the timing is tight.
Keep reading
The events you run
The features that carry them
Talk to us about your event programme
Bring the security questionnaire. The single sign-on answer is no, and it is better to establish that in the first call.