For the first screen a visitor sees
Above the fold a good page settles four questions in seconds: what is this, who is speaking, when exactly, is there room. Then one button. Three shapes worth taking as a starting point.
Sketches in words, each built from parts the product genuinely renders: description, agenda chapters with durations, speaker card, time with its zone, seat count, one action.
Tax returns for freelance designers — a workshop. Four chapters, ninety minutes, with the worked example taking the middle third. Led by Anna Lindqvist, who has filed these returns for eleven years. Thursday 6 November, 18:00 CET. Seats capped at the room we can actually teach in; places left shown while they last.
What changes in the supplier process, and what your week looks like after it. Twenty-five minutes plus questions, one chapter per team, each with the decision it ends on. Hosted by Tom, who wrote the process. Tuesday 14 October, 09:30 EEST. Sign-ups close at the head of the list we can brief one-to-one afterwards.
Six people, one manuscript, two hours. Each chapter is a page of your own work, read aloud and rewritten together. Led by Marta, editor of eleven books and the reason this exists. Saturday 8 November, 10:00 GMT. Six seats, one session, a waitlist for the next date.
Nobody scrolls before they decide. A visitor from your email gives the top of the page a look that lasts three seconds: is this the thing that was promised, who is running it, when, and whether a seat is still there. The register action appears when those four settle favourably, which is why pages that lead with a twenty-paragraph biography convert worse than pages that lead with a chapter list and a time.
The parts are all real fields on the product's page: the webinar-or-workshop label, the start time with the zone you picked beside it, the agenda built as chapters each with a duration and takeaways, the speaker card with name, title, photo and biography, the seat count the page holds, and the form. Copying these shapes is not inventing layout; it is deciding what goes into fields that already exist.
One honest paragraph naming who the session is for and what they can do afterwards. There is a reason it lives in the description: separate audience and outcomes blocks are stored by the product but not shown to guests, so put that text where it actually appears.
Sixty minutes reads better in four blocks with times against them than as a sentence. Takeaways per chapter do the convincing; a wall of prose does the opposite.
Name, title, photograph, biography — three sentences of standing and nothing else. Achievements and method fields exist if the session really needs them.
A cap set to the room, places left while they last, a waitlist when it runs out, and one unmissable action. The seat number is the line that makes the button feel like a door rather than a form.
How it works
Title, the webinar-or-workshop label, a description that carries the promise and the audience line. In-app AI drafting can prefill the sections from your notes; you keep the final sentence.
Four blocks with durations and a takeaway each beats paragraphs. If the worked example is the reason people come, give it the middle chapter and its minutes.
Cap sign-ups to the room, switch on places left and the waitlist, and enter the start time with its zone label chosen beside it.
Open the page on a phone: promise, speaker, time, seats, button. Publish, share one link, and watch the sign-up rate tell you whether the fold worked.
Questions
The audience line and the outcomes belong inside the description or an agenda chapter's takeaway, where guests genuinely see them. The product stores separate what-you'll-learn text but does not render it for visitors, so building around that block wastes writing nobody reads.
Use the truth: the page can show places left against the limit you set, and says so when the room is full. That is real scarcity tied to a real room, not a countdown sticker, and the fold reads it as information rather than theatre.
It needs fewer parts and more specificity. Six seats, one session, a named speaker and a clear reason the six exist. The password-protected page option suits the invite-only shape, so the address can live in a group chat without leaking further.
No, and resist the temptation. One webinar page holds one session; a second date gets a second page. The upside is that a page that worked is a shape you can copy into the next one in an afternoon.
Get Started
Promise, chapters, speaker, count, one button — settled above the fold and repeated below. Build it in the web app or shape it with Clara, and let your own registration numbers be the critique.
