Demo Request Form Optimisation: A Field-by-Field Guide

The short answer

For each field, ask: "What do we do differently depending on the answer?" If the answer is "nothing", remove the field or collect it later. Then fix the three things most demo forms get wrong regardless of length: a vague promise ("Request a demo"), silence about what happens next, and a slow or generic reply.

Start with what happens after the form

A demo form is the moment a buyer chooses to talk to you, and by then they have usually done most of their research. In 6sense's 2024 Buyer Experience Report, buyers initiated first contact more than 80% of the time, when they were nearly 70% through their purchasing process¹. The form should make that step easy, not restart qualification from scratch.

Before touching the fields, write down your follow-up process in three lines:

Who responds, and how is the request routed to them (by region, company size, product)?
How: an email, a call, or a meeting the buyer books straight away?
How fast can you reliably respond, in working hours and outside them?

Every field you keep should feed one of those decisions. Response speed matters as much as the form itself; our speed to lead statistics page collects the research.

The field-by-field audit

Forms tend to collect fields over time, because each team adds one and nobody removes any. Baymard Institute's ecommerce research shows the pattern in checkouts: in 2024 the average checkout had 11.3 form fields, while Baymard found most sites need only 8². That is checkout research, not demo forms, but the lesson transfers: audit what each field is for. GOV.UK's design guidance puts it simply: know why you are asking every question, and only ask for information you really need³.

Field	Why sales asks for it	Recommendation
Name	To address the reply	Keep. One "Full name" field is quicker than two, unless your CRM needs them split.
Work email	To reply, and to identify the company	Keep. Label it "Work email"; accept free addresses rather than blocking them.
Company	Routing and preparation	Keep, or derive it from the email domain and ask only if it is a free address.
Phone	To call back	Only if the next step is a call, and say so. Otherwise optional or removed.
Job title	Seniority and routing	Optional, or ask on the call. Free text is easier than a long dropdown.
Company size	Routing to the right team	Keep if it changes who responds, as a short set of ranges. Otherwise remove.
Country	Territory routing, time zones	Keep only if you route by region.
"What would you like to see?"	Tailoring the demo	Often the most useful field. Keep it, optional, as free text.
Budget, timeline, authority	Qualification	Remove from the form. Answers given before any conversation are often guesses; ask on the call.
"How did you hear about us?"	Attribution	Optional, free text. Self-reported answers can usefully supplement analytics, but should not block the request.
Marketing consent	Permission to send marketing	A separate, unticked, optional checkbox (see the consent section).

If sales needs more information than the form collects, ask for it after the request is made: on the confirmation page, in the booking step, or on the call itself. A buyer who has committed to a meeting is far more willing to answer a question than one who is still deciding whether to bother.

Required and optional fields

Make every field you keep required, except those that really are optional. GOV.UK's guidance is to add "(optional)" to the labels of optional fields and never to mark mandatory fields with asterisks³.
Never ask for the same thing twice. If someone gave their email on a previous step, do not ask again. WCAG 2.2 makes this a level A requirement within a single process, with some exceptions⁴.
Explain any field whose purpose is not obvious, in a short hint below the label: "So we can show you the integrations you use".

The page around the form

The words around the form often matter more than the form. A buyer is deciding whether 30 minutes with you is worth it, so answer that directly:

A specific heading and button. "Book a 30-minute demo with a product specialist" tells the buyer more than "Request a demo", and a button that says "Book my demo" is clearer than "Submit".
What the demo covers, in three or four bullet points, and how long it takes.
Who they will talk to: a specialist, a founder, an account executive.
What happens next, and when: "We reply within one working day to agree a time". Only promise what you can keep.
One relevant proof point, such as a named customer quote used with permission.
An alternative for buyers who are not ready: pricing, a recorded walkthrough or documentation.
A plain privacy line linking to your privacy notice, saying how you will use the details.

Most demo forms sit on solution and services pages too. Our services page optimisation checklist covers the rest of those pages.

Labels, input types and errors

These are small details that make a form faster for everyone and usable for people with disabilities:

Use visible labels, not placeholder text. Nielsen Norman Group found placeholders used as labels strain memory, make it harder to check and fix entries, and can be missed by some screen readers⁵.
Set the right type and autocomplete values, so phones show the right keyboard and browsers can fill the form: type="email" with autocomplete="email", autocomplete="name", autocomplete="organization", autocomplete="organization-title" for job title, and type="tel" with autocomplete="tel"⁶. WCAG 2.2 success criterion 1.3.5 asks for input purposes like these to be identifiable⁴.
Write error messages that say how to fix the problem, next to the field, such as "Enter an email address in the correct format, like name@example.com", not "Invalid input". GOV.UK's guidance also says to keep what the user typed, passing and failing answers alike, when showing errors⁷.
Make targets easy to tap. WCAG 2.2 sets a minimum of 24 by 24 CSS pixels for pointer targets at level AA, with some exceptions⁴; on a phone, larger is kinder.
Use one column. Fields side by side are easy to miss and awkward on a phone.
Test it on a phone, with the keyboard only, and with a screen reader, before and after every change.

Spam without punishing buyers

Demo forms attract bots and junk. Defend against them in ways a real buyer never notices before reaching for a puzzle CAPTCHA:

A hidden "honeypot" field that people never see and bots fill in.
Server-side checks: rate limits, and rejecting submissions that arrive faster than a person could type.
Validating email domains for a working mail server, rather than blocking free email providers outright.
Reviewing the junk that does get through before tightening anything, so you fix the actual problem.

If you do add a challenge, choose one that is usually invisible, and check that it works with a keyboard and a screen reader.

After the submit button

The confirmation is part of the form. The weakest version is "Thanks, we'll be in touch." Better versions:

Let the buyer book a time straight away, either embedded on the confirmation page or as a link, if your team can take meetings that way.
If someone must review the request first, say who, and by when.
Send a confirmation email with the same information, from a named person the buyer can reply to.
Ask one useful follow-up question on the confirmation page, optionally: "Anything we should prepare?"
Check the route end to end every month: submit a test request and confirm it reaches the right person, in the CRM, with every field intact.

Consent and privacy in the UK

Replying to a demo request is not marketing; sending marketing emails afterwards is. Under PECR, the ICO treats emails to corporate subscribers (such as limited companies and LLPs) differently from emails to individual subscribers (such as sole traders and some partnerships). Corporate subscribers do not need to consent under PECR, but you must identify yourself and offer a way to opt out; individual subscribers need to have consented, unless the soft opt-in applies. If you cannot tell which you have, the ICO advises treating the person as an individual⁸. UK GDPR still applies whenever you process a named person's details⁸.

If you ask for marketing consent, use a separate, unticked checkbox. The ICO is clear that pre-ticked boxes and other default settings are not valid consent⁹.
Do not make marketing consent a condition of getting the demo.
Link to your privacy notice next to the button.

This is general guidance, not legal advice. Check the ICO's current guidance for your situation.

Measuring the form

Submissions alone can mislead: removing every qualifying field may raise submissions while sales spends its week on poor-fit calls. Track a short chain instead:

Measure	What it tells you
Visits to the demo page	How many buyers reach the step
Form starts and submissions	Whether the form itself puts people off
Errors by field	Which field causes trouble
Meetings booked and held	Whether requests become conversations
Qualified opportunities	Whether the right buyers are coming through

A demo page with a few dozen requests a month is too small for a conventional A/B test to detect anything but a large change. Our guide to CRO for low-traffic B2B websites explains the alternatives: fix clear defects without testing, make one substantial change at a time, and compare equal periods before and after, reporting "inconclusive" when that is the honest answer.

What to change first

Fix anything broken: the form on a phone, error handling, and routing to the CRM.
Rewrite the heading, button and "what happens next" text.
Remove or defer the fields that do not change your response.
Add a booking step or a clear response promise to the confirmation.
Then measure, one change at a time.

For where the demo page sits in the wider conversion process, see our B2B CRO guide.

Where Artiweave fits

Artiweave proposes specific improvements to the pages you already have, such as clearer wording around a call to action, from crawl, Search Console and performance evidence. Your team approves, edits or rejects each one, approved changes are published with automatic rollback, and outcomes are reported honestly, including "insufficient traffic". It does not add or replace your forms. It is in private beta.

Frequently asked questions

How many fields should a demo request form have?

As few as you need to respond well. For most B2B teams that is a name, a work email, the company and one question that decides how you follow up. There is no reliable universal number: count the fields you actually use, and remove or defer the rest.

Should I block free email addresses on a demo form?

Usually not outright. Some genuine buyers, including founders, consultants and sole traders, use free email addresses. Ask for a work email in the label, accept other addresses, and qualify the lead in follow-up instead.

Should a demo form ask for a phone number?

Only if you will call, and then say so. If the next step is an email or a booked video call, a phone number adds effort without helping the buyer. Make it optional if sales wants it but the follow-up does not depend on it.

Do I need consent to email someone who requests a demo?

Replying to the request itself is not marketing. Adding the person to marketing emails is different: under UK rules the answer depends on whether the address belongs to a company or to an individual such as a sole trader, and consent must never be collected with a pre-ticked box⁹. Check the ICO's guidance for your case.

Sources

Improve the pages buyers act on, with every change approved and measured.

Artiweave proposes specific changes from evidence, your team decides what is published, and outcomes are reported honestly. It is in private beta.

Join the waitlist