The conference app for internal corporate events
An internal event has no ticket, no public marketing and no exhibitor hall. It has an agenda that changes, a room full of colleagues who half know each other, and a sponsor in the C-suite who will ask afterwards whether it worked.
A planning figure: the size where an internal event outgrows a single agenda slide and starts needing rooms and tracks.
What an internal event actually asks of software
A corporate event app is the mobile layer for events a company runs for its own people: offsites, department summits, leadership forums, partner days and internal conferences. It replaces the printed agenda, the projector poll and the post-event survey with one branded app, and it does not need registration or ticketing because the guest list is the employee list. event67 publishes that app under your company's own name and bills only for the people who claim their invite and open it.
An agenda that survives contact with the day
Internal events move. A leadership session runs long, the breakout after it slides thirty minutes, and the printed schedule in everyone's folder is now fiction. A live schedule with rooms and speakers, updated from the console, means the correction reaches every phone before people are standing in the wrong corridor.
Candour, on the record, without a microphone
The most useful question at an internal event is the one nobody wants to ask out loud. Upvoted Q&A moves the decision about what gets asked from the bravest person in the room to the room itself, and moderation lets a facilitator sequence questions rather than block them.
Colleagues who work together and have never met
Two departments that have run a shared project for a year meet in person for the first time at the offsite. The attendee directory with profiles, interests and photos makes that findable rather than accidental, and QR connections let two people swap details in the queue for coffee instead of promising to look each other up.
Something to show the executive sponsor
Attendance, session-by-session ratings, poll results and the questions people actually asked. That is a more honest account of an internal event than a satisfaction score, and it arrives while the event is still running rather than three weeks later.
An offsite from invite to debrief
Before
The guest list is already the guest list
There is no registration funnel to build. Import the attendee list from CSV, send branded invites, and track delivery per recipient. Announcements can be scheduled to push at a set time, so the pre-read lands the evening before rather than whenever someone remembers to send it.
Uses scheduled announcements.
Arrival
A desk that does not become a queue
Scan the QR pass at the door and the arrivals count updates live in the console. For an internal event the number matters less for security than for catering, and having it accurate at 09:10 rather than estimated at 08:00 is the whole benefit.
Uses check-in and Wallet passes.
Through the day
Polls that change what happens next
A live poll during a strategy session is not theatre if the facilitator uses the result. Poll and Q&A run from the session screen, reactions stream during the keynote, and moderators approve from a console page rather than from the stage.
Uses live polls and Q&A.
Evening
The photos that would otherwise vanish
Every internal event generates a few hundred photographs across a few hundred phones and almost none of them are ever seen again. The shared album collects them under the event, with moderation set to admin-only, moderated or open, and a photo auto-hides once it is reported.
Uses the shared album.
After
The debrief writes itself
Session feedback and ratings arrive per session while memory is fresh. The reports archive keeps every question, poll and photo, and engagement analytics show which sessions held the room and which lost it. That is the material for next year's agenda argument.
Uses session feedback and analytics.
Standing up an internal event app
Six steps, and the longest one is loading the agenda you have already written.
Create the event
Name, dates, currency. Currency locks when the event goes live.
Build the schedule
Sessions, rooms, speakers and tracks. Tracks are optional for a one-room day and essential the moment there are two.
Apply the company brand
Logo, colour and type. The theme editor checks each pair against WCAG AA and warns you; it confirms rather than blocks, so an off-brand colour is your decision to make.
Import the list and invite
CSV in, invites out, delivery tracked. Nothing bills until people claim and open.
Schedule the pre-read announcement
Write it now, set it to push the evening before. Announcements deep-link to the post rather than dropping people on a home screen.
Name your moderators
Per-event moderator roles for Q&A and photo approvals. Team chat and billing carry audit trails.
What a 260-person offsite costs
Two hundred and sixty people claim their invite and open the app. The first fifty are free and the rest are billable once, for the whole event, however many days it runs.
- activated attendees
- 260activated attendees
- billable, after the first 50 are free
- 210billable, after the first 50 are free
- for the whole event, at $5.00 each
- $1,050for the whole event, at $5.00 each
Billed 48 hours after the event ends. A live meter runs in the console from the day the event is published, so the number is never a surprise.
Where an internal event outgrows us
Internal events are the cleanest fit for event67 because the features they need are the features we built. The boundary is worth knowing anyway.
- No live streaming and no hybrid broadcast. If half your company joins remotely by video, event67 carries their agenda, Q&A and polls but the video itself runs somewhere else.
- No expense or travel booking. The app tells people where to be, not how to get there or how to claim it back.
- No integration with your HR system. The attendee list is a CSV import, so a large recurring programme means re-importing rather than syncing.
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 we need an app for a one-day offsite?
Often not. If it is a single room, one agenda and forty people, a printed sheet is honest and cheap. The app starts paying at the point where the agenda has rooms in it, or where you want the questions ranked rather than shouted.
Can we keep it entirely internal?
Yes. The attendee event site is noindex by default, invites go only to the addresses you import, and there is no public listing of your event anywhere. Nothing about your event is discoverable unless you hand someone the link.
Does it work on company-managed devices?
The branded app ships to the App Store and Google Play, so it installs through the same channel as any other public app and can be pushed by your MDM. Anyone who cannot install uses the web version, which carries the agenda, Q&A, polls and directory.
What does it cost if half the invited list never opens it?
Nothing for those people. The meter counts activation, which is claiming the invite and opening the app. Importing a thousand employees and having three hundred show up bills for three hundred, minus the free fifty.
Can one app cover a series of internal events through the year?
Each event is its own event, with its own free fifty and its own bill. That is usually cheaper than it sounds for a programme of small events. If the calendar is dense, prepaid Season Pass credits pool across all of them.
Keep reading
Other kinds of event
The features this leans on
Put your next offsite in your own app
No ticketing to configure, no registration funnel to build. Import the list, load the agenda, go.