What Should a Demo Request Page Actually Look Like?

What should a demo request page actually look like?

Short, specific, and honest about what happens next. The form should ask for the fewest fields your sales team can genuinely act on, the page should say who the demo is for and how long it takes, and nothing on it should try to sell the product again. The selling already happened.

Most B2B demo pages do the opposite. They repeat the homepage pitch, add a nine field form, and say nothing about what the next hour of the visitor's life will involve. The page treats a person who has already decided as though they still need convincing.

We have an opinion here and this piece argues it rather than surveying options. A demo request page is a confirmation page, not a sales page, and designing it as a sales page is why the conversion rate disappoints.

Why is this page different from a landing page?

Because the intent is already formed. Someone who clicked Request a Demo has made a decision and is now performing an administrative task. Interrupting that task with more persuasion adds friction to a process that needed none.

Compare it with a paid landing page, where the visitor arrived cold and the page has to do the whole job. Those pages earn their length. A demo page inherits its visitor from the rest of your site.

That distinction changes every decision on the page, and it is why we treat these as separate design problems rather than variants of the landing page pattern.

How many fields is too many?

More than five is usually too many, and the direction of travel in adjacent research supports cutting. Baymard Institute's study of checkout flows, published on June 26, 2024, found the average checkout used 11.3 form fields in 2024, down from 11.8 in 2021 and 12.7 in 2019, and concluded that most sites need only 8 in total.

Be careful with that comparison, because it is ecommerce checkout rather than B2B demo requests, and the two differ. A checkout genuinely needs an address. A demo request does not need a phone number before anyone has agreed to talk.

What transfers is the pattern. Forms accumulate fields because each one was requested by somebody, and nobody is ever assigned the job of removing them. Left alone, every form grows.

Which fields actually earn their place?

Work email, name, and company. That is the honest core. Everything else should have to justify itself by naming a decision it changes, today, for a real person.

Company size and role usually pass that test, because they genuinely route the lead. Phone number usually does not, because it is collected to enable a call the prospect has not agreed to and often filled in falsely. Budget almost never does.

Our rule: if the field's purpose is to let sales prioritise, ask for it. If its purpose is to let marketing report, enrich it afterwards instead. Enrichment tools can infer company size from a work email domain. They cannot infer a person's willingness to fill in a form.

What does the usability research say about the form itself?

Nielsen Norman Group's ten recommendations, written by Kathryn Whitenton on May 1, 2016, still hold and are mostly ignored. The first is simply to keep it short, with the observation that "eliminating unnecessary fields requires more time, but the reduced user effort and increased completion rates make it worthwhile."

Three more matter here. Present fields in a single column, because "multiple columns interrupt the vertical momentum of moving down the form." Avoid placeholder text as a label substitute. And limit the form to only one or two optional fields, clearly labelled as optional.

The error guidance is the one most B2B forms fail. NN/g recommends signalling errors through several cues at once rather than colour alone: outline the field and use red text and a heavier font. A thin red border on its own is not an error message, and it is invisible to a meaningful share of users.

What belongs on the page besides the form?

Four things, and they are all about the meeting rather than the product. How long it takes. Who will be on the call. What they will show. What happens if the visitor is not a fit.

That last one is unusual and we recommend it seriously. A sentence saying you will tell them plainly if the product is wrong for them costs nothing and changes the character of the page. It signals that the call is a conversation rather than a pitch.

Add one piece of proof, not five. A single named customer with a specific outcome does more than a logo wall at this stage, because the visitor is no longer evaluating credibility in general, and we made that argument in how social proof actually works.

Should you show the calendar directly?

Usually yes, and it is the single biggest improvement available on most of these pages. Letting someone pick a time immediately removes an entire round trip of emails, and it converts intent into a commitment while the intent still exists.

The objection is qualification, and it is real. If you genuinely cannot afford to meet unqualified prospects, route by company size after the form and offer the calendar only to the segment you want, with a different path for everyone else.

What you should not do is hide the calendar behind a form and then email a link to the same calendar an hour later. That is friction with no filtering benefit.

What about the thank you page?

Treat it as part of this design, not an afterthought. The moment after submission is the highest attention moment in the whole journey and most companies spend it on the word Thanks.

Use it to set expectations precisely. Name the person who will be in touch, say when, and give them something genuinely useful to read in the meantime. A specific case study relevant to their industry beats a generic resource list.

It is also where you should confirm what was submitted, so somebody who mistyped an email can act on it immediately. That detail is covered further in designing a thank you page that does something.

What are the mistakes we see most often?

Five, and they are remarkably consistent. Repeating the homepage hero. Asking for a phone number. Marking every field required with asterisks so nothing stands out. Hiding the form below a long scroll. And offering a chat widget that competes with the form on the same screen.

The chat one is worth dwelling on. A visitor on a demo page has chosen their channel. Popping a chat window over the form asks them to choose again, and a second choice on a page designed to end choosing is pure friction.

The asterisk problem is subtler. NN/g's guidance is to eliminate optional fields first and mark the remaining one or two as optional, which is better than marking eight fields required. Marking everything required marks nothing.

How do you know whether yours is working?

Look at form starts against form completions, not just page views against submissions. A page where most visitors start the form and then abandon it has a form problem. A page where nobody starts the form has a page problem. They need opposite fixes.

Then check what your sales team does with the fields you collect. If nobody has opened the budget field in three months, delete it. That audit is the fastest conversion improvement available on most B2B sites and it costs one conversation.

Do not run an A/B test on a page with low volume. Most B2B demo pages do not get enough traffic for a trustworthy result, and a test you cannot power is just a slower way of guessing.

What would we build if we started over?

One screen. A heading naming who the demo is for. Three or four fields in a single column. A sentence on duration and who joins. One named proof point. A calendar immediately after submission. Nothing else.

It looks almost too plain in a design review, which is why it rarely survives one. The page that survives the review is the one with the hero image, the feature grid and the logo wall, and it converts worse.

We build these as part of B2B site projects and the demo page is usually where we have the most disagreement with clients, which is how we know it matters. If you want a candid read on yours, including which fields to delete, we are happy to look. You can find us at phoenix.studio, and the mechanics of the form itself are covered in our guide to form design.