The conference app for technology companies
A software company holds its customers to a standard on design and then hands them a conference app with somebody else's logo in the App Store listing. That is the gap this page is about.
A planning figure for a growth-stage software company's annual customer event, with several tracks and a roadmap session.
Four events, one company, one app
A technology company's event programme is usually four things: an annual user conference, a sales kickoff, internal all-hands, and launch or developer events. event67 covers all four with a branded app published to the App Store and Google Play under the company's own name. It has no single sign-on, no documented public API and no video streaming, which are the three integration questions a technology buyer asks first.
The user conference, which is the brand event
Admin, developer and executive tracks with different audiences, a roadmap session that is the reason many customers travelled, and hands-on labs with hard seat limits. The app carries the personal agenda, the upvoted roadmap Q&A that gives product managers the most valuable feedback of their year, and RSVP capacity enforced on the server with automatic waitlist promotion for labs.
The sales kickoff
The internal counterpart, in January, with tracks by segment, enablement workshops, a leadership panel and a distributed sales team meeting in person for the first time in a year. Nothing an SKO needs is on our missing list, which makes it the cleanest fit in the whole catalogue.
All-hands and engineering forums
Each town hall is its own event, so quarter-on-quarter participation is comparable rather than remembered. Q&A opened a week early gives executives a ranked list and time to prepare a real answer, and the unanswered list is the best available read on what the company is worried about.
Developer events, hackathons and launches
Hackathon timelines with scheduled deadline announcements, mentor office hours with real capacity, and a participant directory that helps teams form. Launch events get the running order, reactions during the reveal and a poll immediately after it. Note the boundary: no project submission and no judging.
Partner and customer advisory boards
Small, senior, invite-only. Private by default, since event sites are not indexed and invites reach only imported addresses. Moderated Q&A, a directory members actually browse, and a logged record of what was raised.
What changes for a product organisation
The store listing says your product's name
Branded apps ship to the App Store and Google Play under the client's own name, which is why the white-label claim here is literal rather than a theme. For a company whose customers judge it on product craft, the app is a surface it should own.
The roadmap session becomes an asset
Every roadmap question, with its upvote count, stays in the reports archive. Over three annual conferences that becomes the clearest longitudinal record of customer demand a product organisation has, and it costs nothing to produce.
Labs stop overselling
Server-enforced RSVP capacity with automatic waitlist promotion. The hands-on lab seats what the room seats, and a drop-out is replaced without anyone administering a list.
The bill matches turnout, and stops
You are billed on customers who claimed their invite and opened the app, past the first fifty, up to a per-event ceiling. Registrations who never attend cost nothing, which for a free developer event is most of the list.
The events team stops being a bottleneck
In most software companies one person owns the event tooling and every field marketer waits on them. Per-event moderator roles let a regional marketer run their own customer dinner or developer meetup without touching the flagship conference, and each of those small events carries its own free fifty activated attendees. The flagship stays controlled; the long tail stops queueing.
The integration questions, answered as no
Technology buyers evaluate integrations before features. Every answer here is no, and none of them is a roadmap hint.
- No single sign-on. No SAML, no OIDC, no identity-provider integration.
- No documented public API or webhooks for customer use. The supported integration path is a CSV import of the attendee list.
- No CRM integration. QR connections are attendee to attendee and never reach a CRM, and there is no lead retrieval for sponsors.
- No video streaming, so hybrid conferences and streamed keynotes run on a separate platform.
- No ticketing, registration or payments. Sell through a registration platform and import the list.
- No call for papers, abstract submission or speaker portal.
- No interactive floor plan, and no exhibitor badge scanning for sponsors.
- No project submission, judging or leaderboards for hackathons.
What an 850-customer conference costs
Eight hundred and fifty customers activate. Fifty are free and the rest are billable once for the whole conference, regardless of how many days, tracks or labs each person attends.
- activated attendees
- 850activated attendees
- billable, after the first 50 are free
- 800billable, after the first 50 are free
- for the whole event, at $5.00 each
- $4,000for the whole event, at $5.00 each
The sales kickoff, the all-hands and the developer day are separate events, each with their own free fifty.
Roles, records and what we will not claim
Stated as mechanisms rather than as badges, because a technology buyer will check.
| Control | What exists |
|---|---|
| Tenancy | Multi-tenant from day one, with organizations and events inside them. |
| Roles | Four levels: super admin, organization admin, moderator and attendee. Scope is per event. |
| Audit | Team chat and billing carry audit trails. Moderation actions are not logged. |
| Identity | Email invite, claimed by the attendee. No SSO. |
| Certifications | Not asserted on this page. Ask directly and we will describe exactly what exists rather than imply more. |
| Attendee deletion | By request through a published address and a web page. There is no in-app deletion, and that is a known gap. |
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
Will the app really be listed under our product's name?
Yes. The apps we publish go to the App Store and Google Play under the client's own name, with the client's icon and identity. That is what makes the white-label claim literal rather than a theming option.
Is there an API?
Not one we document or support for customer use. The supported path for getting an attendee list in is a CSV import, and there is no webhook or export API to build against. If your evaluation depends on programmatic integration, treat that as a no.
Do you support SSO for internal events?
No. There is no SAML or OIDC support and no identity-provider integration. Employees receive an email invite and claim it, the same way customers do.
Can sponsors at our user conference capture leads?
No. Sponsors get tier-ordered pages with logos, descriptions and websites, and can be attached to sessions. There is no badge scanning, no lead retrieval and no CRM sync. Confirm this before your sponsorship prospectus goes out, because it is the most common late surprise.
Can we run a hybrid user conference?
Partly. event67 carries the agenda, Q&A, polls and announcements for remote attendees as it does for the room, but it does not stream video. Run the broadcast on your existing platform.
What happens to the roadmap questions afterwards?
They stay in the reports archive with their upvote counts. Nothing is deleted at the end of the event, so the questions from three consecutive conferences are directly comparable.
How do we get the delegate list out of our registration platform?
As a CSV export, imported into the event. There is no integration to build and none to maintain, which is the upside of the same limitation that makes an API impossible. Delivery is then tracked per recipient, so a bounced invite to a major account is visible before the conference rather than at the registration desk.
Can we test it on something small before the user conference?
That is the sensible sequence and it costs nothing: an internal all-hands or a developer meetup under fifty activated attendees is free with the complete feature set. It also exercises the store submission, which is the only part of a branded app rollout with a queue in front of it.
Keep reading
The events you run
The features that carry them
Adjacent industries
Ship your conference under your own name
Both stores, your icon, your colours. The integration answers are all no, and we would rather you knew now.