Run a 3-day, 4-track conference
the way Cvent does it.
Sessions with dates, tracks, capacity, waitlist, and speakers. A branded public agenda. A private schedule every attendee can add to Google Calendar in one tap.
Built for real conferences, not just registrations.
Six fields on the session form. That's the whole setup for a talk with a speaker, a capacity, a track colour, and a live stream link.
Three taps from ticket to calendar.
Session management is the part most tools skimp on.
Most event platforms treat sessions as an afterthought. You get a text block for "agenda" on the landing page and that is that. Fine for a single-track meetup. Painful for a real conference.
The moment you have three tracks running in parallel, or a workshop with capped seats, or a two-day event where day-two seats depend on who showed up on day one, that text block breaks down. Attendees end up on WhatsApp asking "which room is the founder track in", speakers arrive at empty halls because their session moved, and volunteers scan every ticket at every door because there is no session-level check-in.
We built sessions as a first-class object, not a description field. A session has its own date, time, room, capacity, speaker list, and check-in scanner. Attendees pick sessions from the public agenda and build a personal schedule that survives across days. Organisers see per-session attendance numbers in real time, so if the AI track is full and the fintech track is empty, someone can move a panel.
A day-in-the-life of the agenda module.
4 weeks out. You draft the agenda in the organiser panel. Ten sessions on day one, eight on day two. Speaker profiles go in first because every session needs at least one speaker. Sessions that need signup separately from the main ticket get a capacity number.
2 weeks out. Agenda goes live at yourdomain.com/agenda. Attendees who bought tickets can log into their pass and start picking sessions. You watch the numbers. The keynote fills first — that is fine, it has no cap. The AI workshop, capped at 40, hits 40 within six hours and starts a waitlist. You quietly add a second run on day two.
Event day. Every session door has a volunteer with a phone open to /session/{token}. Attendees walk in, scan their pass, done. If they wander into a session they did not sign up for and there is space, the scanner marks them checked in and adds them. If it is full, the scanner shows a polite decline.
Between sessions. A panellist calls in sick. You open the session, swap the speaker, and every attendee who RSVPed to that session gets a push notification and an email. If you use the live polls module, the polls stay attached to the session and follow the room, not the speaker.
After the event. Session-level attendance shows up in the same dashboard as headline registration numbers. You can see the drop-off between day one and day two by track, which is the number sponsors actually care about.
The stack a lot of Indian conferences currently glue together.
| Job | Typical current tool | Rough per-event cost |
|---|---|---|
| Public agenda page | Notion or a subpage in Squarespace | Free but manual |
| Session signups | Google Forms per track | Free, no capacity control |
| Attendee schedule | Sched.com starter | ₹6,000 – ₹15,000 |
| Session check-in | Extra Zkteko turnstile rental | ₹4,000 per door per day |
| SignupDesk sessions | All of the above, one module | Included |