For the form between the page and the list
Every field on your form is a small tax on the person about to say yes. Name and email pay for themselves; the next three questions have to earn their place, and everything after that costs you completions.
A registration form is a trade. Each field buys you information and sells a little of the visitor's patience. Two fields — name and email, which the product always asks for — buy the whole interaction: a row on your list and a mailbox to send the confirmation and the reminders to. Beyond that, every question needs a balance sheet. If the answer will change something you do — the emphasis of a chapter, the depth of an example, the segment a follow-up goes to — it is earning its keep. If it will sit unread in a column, it is costing you the people least willing to pay it.
There is no hidden score here and no analytics dashboard to consult; the honest test is simpler. Before the session, glance at the answers on the list. A question you did not look at is a question to delete before the next page you build.
The product lets you add your own questions as text, select, number and similar fields, with some marked required. These four tend to pay rent.
Turns a wall of names into a picture of who actually came, and lets the follow-up after the session go to the right segment of the list instead of everyone.
Tells you the depth to pitch at. A room of practitioners and a room of directors need different first chapters, and you would rather learn that on the form than at minute nine.
The closest thing to a request line. Read a dozen of these and you know what to lean on when the agenda runs short, and what to say in the invitation for the next date.
Only when you will genuinely use it — a workshop with materials to post, a session with a practice line to test. As decoration it is the heaviest field on most forms.
Visitors arrive from an invitation that promised a session, not a job application, and the form is where that promise gets audited. A short form says: we respect the hour you are giving us. A long one quietly rewrites the arrangement before the first chapter starts.
The practical shape that holds up across sessions: name and email as always, two or three custom questions with one required at most, and a select wherever you can — tapping an option is cheaper than remembering a word. The Lindqvist family run their software house's customer sessions this way and, when they changed a question, changed one out rather than adding one in. That discipline is the whole feature.
How it works
Before touching the form, write down the decisions you will make on the session: pitch depth, an example that lands, the follow-up wording. Questions exist to feed those decisions.
Build the webinar page with the description, chapters and speaker, then attach each decision as a question — text, select or number — marking required only where the answer is genuinely load-bearing.
Publish, open your own link, and fill it on a phone. Anything you hesitated on for more than five seconds is a candidate for optional or deletion.
The custom answers arrive attached to each row on your list. If you never looked at one question's answers, remember that for the next page you build.
Questions
Yes. Company, job title, phone, country, industry, experience, website, LinkedIn and hoped-for takeaways are the usual ones, but the form takes your own questions as text, select, number and similar types. The examples are a shortlist, not a menu limit.
It can only add friction; it cannot subtract it. Nobody has a number for how much, and the product does not pretend to. What you can do is watch your own sign-up rate against page views across two sessions, and see which shape of form suited your audience.
Name and email are always collected, and you can mark your own questions required. The safe pattern is one required custom question at most — the one whose answer genuinely changes the session. Required fields are a locked door; use them once.
They arrive attached to that person's row on your attendee list, which lives on your dashboard and is yours to export. Attendees see the form's fields, not each other's answers.
Get Started
Two always-on lines, three questions that change your session, and the discipline to cut one before adding one. Build the form on the page and let the list prove it out.
