Most advice on demo forms gives you a number. This guide gives you a method instead, because the right count depends on three things specific to your company: what sales needs to know before the call, what your tools can fill in on their own, and how leads get routed. Work through those three and the number follows. For the wider flow, from page to confirmation, start with our guide to the book-a-demo page.
How many demo form fields does a demo request form need?
A demo request form needs one contact field plus one field for each routing decision your team makes before the call. For a team with one sales queue, that can be work email and name. For a team that routes by company size and product line, it's those two questions on top.
That's why a fixed number misleads. Our general landing page form guide suggests three or four fields for most B2B lead forms, and a demo form often lands in that range. But a demo form differs from a content download: someone on your team will spend their time on the call, so the form also has to protect that time. The method below helps you balance completion against fit.
What does sales actually need before the first call?
Sales needs enough to decide who takes the call, whether it's worth taking and what to prepare. Ask your reps which answers change those three things, and you'll find most form fields change none of them.
- Needed to route. Answers that send the lead to a different person, team or path: company size, region, product line, existing customer or not.
- Needed to qualify. Answers that decide whether the call happens at all, such as a minimum team size for an enterprise-only product.
- Needed to prepare. Answers that change what the rep shows, such as the main use case or current tool. These are valuable, but can often be asked after booking.
- Nice to know. Job title, phone, budget, timeline and "how did you hear about us" usually change nothing before the call.
Only the first two groups belong on the form by default. Preparation questions can move to the scheduler or the confirmation page, where the buyer has already committed and is more willing to answer. Nice-to-know fields belong on the call or nowhere.
Which demo form fields can enrichment fill in instead?
Enrichment tools look up company data from the work email domain, so fields like company name, size and industry often don't need to be asked. Tools such as Clay and Apollo, and the enrichment built into some CRMs, do this after the form is submitted.
Field | Can enrichment fill it? | Watch out for |
|---|---|---|
Company name | Usually, from the email domain | Personal email addresses |
Company size | Often, as a range | Stale data for fast-growing startups |
Industry | Often | Broad categories that don't match yours |
Location or region | Often, at company level | The buyer may sit in another office |
Job title | Sometimes, from public profiles | Low match rates for small companies |
Use case | No | Only the buyer knows it |
Current tool | Sometimes, via technology data | Partial or outdated coverage |
The catch is timing. If routing has to happen the instant the form is submitted, for example to show the right rep's calendar, enrichment has to finish first. Check that your tool returns data fast enough for real-time routing, and decide what happens when it finds nothing, such as falling back to a single question. Our Clay integration page covers how we wire enrichment into site forms.
How does lead routing change the number of fields?
Lead routing sets the minimum number of demo form fields, because every routing rule needs an input. A single shared queue needs only contact details; size, territory or product routing each adds one question, unless enrichment can answer it reliably in time.
Routing model | Fields it needs | Can enrichment cover it? |
|---|---|---|
One queue, any rep | Work email, name | Not needed |
Self-serve vs sales by company size | Plus company size | Often |
Territory or region | Plus country or region | Often, at company level |
Product line or use case | Plus use case | No |
Existing customer vs new | None extra if matched in CRM | Yes, from the CRM record |
Instant booking raises the stakes. When a scheduler such as Chili Piper shows a calendar right after submit, the routing questions decide whose calendar appears, so they must be on the form. Our guide to embedding a calendar on your demo page covers that trade-off, and the Chili Piper integration page covers the setup.
How do you decide demo form fields one by one?
Decide each field with a short audit run with sales in the room. The aim is a form where every visible question has a named owner and a named action, and everything else is enriched, deferred or dropped.
List every field and its owner
Write down each field, including hidden ones, and who asked for it. Fields without an owner are the first candidates to cut.
Name the action each answer triggers
For each field, ask what changes based on the answer: a different rep, a different path, a declined call. If nothing changes, it isn't a routing field.
Check enrichment coverage
Run a sample of recent leads through your enrichment tool and see which fields it fills reliably for your buyers.
Move preparation questions later
Put use-case details and current tools in the scheduler, the confirmation page or a short pre-call email.
Make the survivors quick
Use radio buttons or a short dropdown for routing questions, with ranges that match your routing rules exactly.
Set a review date
Routing rules change as the team grows. Review the form whenever they do.
Hypothetical example: auditing a seven-field demo form
For example, suppose a B2B SaaS company's demo form asks for first name, last name, work email, phone, company, company size and job title. Sales routes companies over 500 employees to enterprise reps and everyone else to a mid-market team, and never calls before the meeting.
The audit keeps work email and a single name field, keeps company size as three radio options matching the 500 threshold, and removes phone and company. Job title moves to the scheduler step. The team checks that enrichment fills company name for most leads and tracks held meetings for a month to confirm fit hasn't dropped. This illustrates the method; it isn't a measured result.
Should a demo form use progressive fields or multiple steps?
Progressive fields and multi-step layouts can help a demo form, but they don't change the underlying question of which fields you need. Use them to make a necessary form easier, not to hide an oversized one.
- Progressive profiling. Some form tools, including HubSpot on plans that support it, can hide fields a returning contact has already answered and show new ones instead. It suits sites where buyers convert more than once. Check the current HubSpot integration details and plan pages for availability.
- Multi-step forms. Starting with an easy question, then asking routing questions on a second step, can feel lighter. It adds a step to track and test, so measure drop-off at each step.
- Conditional fields. Show a follow-up only when an answer needs it, such as a region question only for companies above your threshold.
How do you know your demo form fields are right?
You know your demo form fields are right when good-fit buyers finish the form and turn up to the call, and sales isn't declining many meetings. Track the whole path, not just submissions.
- Form starts and completions. A big gap points to fields that put people off. Session recordings help here; see our guide to rage clicks and form abandonment.
- Drop-off by field. Field-level analytics show which question people stop at.
- Meetings booked and held. A shorter form that produces fewer held meetings isn't a win.
- Sales acceptance. Ask reps to flag poor-fit calls, and check whether a routing question would have caught them.
For what good looks like at each stage, see our demo request conversion rate guide. If you want a second pair of eyes on the whole flow, our CRO service audits the form, routing and follow-up together.
