Build the app in an afternoon, in a browser
A conference app builder is a console that turns event content into a working app without anybody writing code. In event67 you import your attendee list, enter the programme, set your theme and publish, and the app reads all of it from the backend so a change at eleven at night is live at eleven at night.
What this looks like in the product
Five console pages between an empty event and one you can send invites for.
- Console-built events
- Sessions, speakers, sponsors, rooms and tracks entered in a browser, with no build step.
- CSV attendee import
- Bring the list you already have and send invites with per-recipient delivery tracking.
- Theme editor
- Logo, colours and typography with a live preview and a WCAG AA contrast advisory.
- Per-event feature switches
- Turn photos, Q&A, polls, chat and the directory on or off for this event.
- Publish without a rebuild
- Content and theme are served from the backend, so a change is live immediately.
Setting up an event
- Event details and dates
- Sessions, tracks and rooms
- Speakers and sponsors
- Theme: logo, colours, type
- Import attendees and invite
What a builder actually replaces
The phrase covers two very different products and the difference is worth ten thousand dollars.
A general no-code app builder gives you a canvas and expects you to design an event app on it. You get freedom, and you also get the job of deciding what an event app should contain, which is a job you have never done and a vendor has done four hundred times.
An event-specific builder like event67 gives you the app already shaped. Schedule, connections, photos, Q&A, polls, sponsors and notifications are already there and already work together. What you provide is your event and your brand. What you give up is the ability to invent a screen nobody else has.
For almost every organizer, the second trade is the right one, and the reason is not laziness. The failure mode of a blank canvas is not an ugly app; it is an app that ships two days late because a decision about tab order took a week.
What an afternoon in the console produces: the schedule an attendee opens on the morning of day one, in your colours, under your name.
- The sessions are the ones you typed
- Rooms, speakers and tracks come straight from the console, and a change you publish is on every phone before the next session starts.
- My Picks is the attendee’s own edit
- Anything they star pins above the rest of the day, so they open their programme rather than the whole one.
- Nothing here was designed by you
- The layout is fixed and the brand is not. That is the trade: you choose the logo, the palette and the type, and you do not choose where the star goes.
An afternoon, in order
Create the event
Name, dates, currency. Currency is chosen at creation and locks when the event goes live, so pick the one you will invoice in.
Enter the programme
Sessions with tracks and rooms, speakers with bios, sponsors by tier. Speakers are entities rather than text on a session, so a bio is written once.
Set the theme
Logo, colours and typography, previewed live. The contrast check warns you when a pair falls below WCAG AA and asks you to confirm; it does not block the save.
Choose what is switched on
Photos, Q&A, polls, chat, the directory and connections are per-event. A quiet board meeting and a loud sales kickoff are the same product with different switches.
Import and invite
CSV in, invites out, with delivery tracked per recipient so a bounced address is visible rather than assumed.
What you cannot change, stated plainly
This is the section a builder page usually omits, and it is the one that decides whether you should be talking to us at all.
- The screen layout and the tab structure. You control content and brand, not information architecture.
- The feature set. Features are switched on and off, not invented. There is no plugin model and no scripting.
- The data model. You cannot add a custom field to an attendee or a session and have it appear on a screen.
- Integrations. There is no general-purpose API for you to build against, no webhook catalogue and no Zapier connector.
- The registration flow, because there is not one. event67 does not sell tickets; you bring a list from wherever registration already happens.
If you need a custom screen, a custom field or an integration with the system your organisation runs on, you need an agency and a build, and you should expect to pay build prices for it. That is a legitimate thing to need. It is not what this is.
Who should build it themselves
An organizer with a programme, a list and a brand, four weeks out, who has been quoted a five-figure build and a twelve-week timeline for something their event does not need. A communications team running an internal event with no budget line for software. An association staffer who is the entire technology department.
The honest counter-case: if your event is in nine days and you have not started, build the browser event site and skip the branded app, because the store review queue is the one part of this nobody can accelerate.
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
How long does it take to build a conference app?
The console work is an afternoon for a straightforward event, and a day if your programme is large and nobody has written the speaker bios yet. Add two to three weeks if you want a branded app in the App Store and Google Play, because store review is a queue you do not control. The browser event site has no such wait.
Do I need a developer?
No, and there is nothing for a developer to do. There is no code to write, no build to run and no repository to hand over. What you need is somebody who can organise a programme and a spreadsheet.
Can I add a custom feature or a custom field?
No. Features are switched on and off, not extended, and the data model is fixed. If your event needs a screen that does not exist here, you need a bespoke build and this is the wrong product for it.
What can I change after the event has started?
Content and theme, immediately, without an app update. Sessions, rooms, times, speakers, sponsors, announcements, colours and logo are all served from the backend. The app's name and icon in the store are the exception and need a resubmission.
What does it cost to build one?
There is no build fee. The first 50 activated attendees on an event are free, each one after that is $5, and a single event can never cost more than $4,750. A first event under fifty people costs nothing at all, and you can build it today to see whether you like it.
Keep reading
What you set up
Event types that lean on this
See it in your own event
Your first 50 attendees are free on every event, so the smallest version of this costs nothing to try.