For the team showing the thing working
A demo is judged before it starts: people decide in ten seconds whether the hour is worth it. An agenda they can read, one named speaker, and a join link that never appears on the page.
Nobody reads a demo invitation as a promise; they read it as a guess about how the hour will go. Will someone show the product, or talk about the market for forty minutes and open a slide at the end? The only way to settle that guess in advance is a page with a running order on it, so the visitor can see the shape of the session before deciding to give you their evening.
That is what a webinar page gives you: one public registration page for one live session. Attendees leave a name and an email, the page holds your agenda and your speaker, and the reminders go out on their own afterwards. You bring the meeting room yourself by pasting in the join address and naming the platform you present on.
Chapters with durations and a takeaway line each: what the product does, where it fits, a live walkthrough, then the closing. Written as chapters, the promise is checkable; written as a paragraph, it is not.
A name, a title, a photo and a short biography. On a demo this section carries more weight than on most sessions, because the person is the reason an attendee trusts what they are about to see.
The meeting address is never published openly. Each registrant gets their own private access link in the confirmation email, so the room holds the people who signed up rather than whoever found the link.
There is a specific failure mode for demos: the meeting link gets posted alongside the invitation, travels into a forwarding chain, and someone uninvited spends the session watching a product walkthrough. The page is built against that. What you advertise is the registration address; the join route stays private to each attendee through their own link, and the page itself only ever shows one button.
If the demo is for a named list rather than the public, add the optional password to the page and send it with the invitation. Then the address on its own opens nothing, and the door stays shut until someone has the word.
Worth being plain about the follow-up, because demo invitations overpromise here constantly. There is no recording made on your behalf, no question feed, no poll and no scoring of who looked interested. What exists is your registrant list with statuses, a message you can broadcast to a chosen segment, and the links you supply yourself: the replay, the deck, the pricing page, the next session.
That is usually enough. Send one follow-up to the people who registered and a second to the ones marked as no-show, with your own replay link in the first and a short line in the second asking whether the next date suits them better. The list updates as replies come in, and the export gives you the same names in a file for whoever does the work afterwards.
How it works
Four chapters with a duration and one line each on what the attendee gets. If you cannot write that, the demo is not planned yet and the page will not fix it.
Send the agenda and the speaker details to Jitabi, or fill them in the web app. The draft carries the headline, the chapters, the start time with its zone label and the sign-up button.
The meeting address and the platform are fields you complete. Registrants receive their own private access link, so the address stays out of the public page entirely.
Cap the places, switch on the waitlist if you want it, then publish. After the session, broadcast to the registrant segment with the replay and slides links you are supplying yourself.
Questions
No integration exists, and that is deliberate. You paste your own join URL into the page settings and write the platform name attendees should expect. We send registered people to whatever that link is; nothing here creates or opens a meeting.
They ask however you run your own meeting. The invitation product has no question feed, poll or chat of its own, so save time in the agenda for it and send the answers you could not reach in the follow-up message to registrants.
The cap holds. Once the places are gone the page says so, and anyone arriving after that joins the waitlist if you turned one on, where they are told an email will come if a spot opens.
If you record it, that is your work on your platform. The product does not host or produce a replay; you supply the link yourself and send it to a chosen segment of the registrant list, or leave it on the page as a link you wrote.
No. One page is one session, so each date gets its own page and its own link to send. The previous list is the natural first audience for the next one, which is the part that makes repeat demos manageable.
Get Started
Say exactly what happens in the hour, name the person who answers for the product, and keep the join route private to the people who signed up. The rest is a link you send once.
