What Should a Demo Request Form Actually Ask?

What should a demo request form actually ask?

Only what changes who runs the demo or whether it happens at all. In practice that is a work email, the company, and one question about the problem the buyer is trying to solve. Everything else is either available after the form or costs you more requests than it earns.

Demo forms attract extra fields the way a fridge attracts magnets. Someone in sales wants company size. Someone in marketing wants the channel. Someone in finance wants the budget. Each addition is individually reasonable and collectively fatal.

The way out is to decide what the form is for, which is a routing decision rather than a research project.

Why does every extra field cost you more than it looks?

Because the buyer is paying attention, not filling in a survey. Each question asks them to judge whether answering is safe, relevant, and quick, and every judgement is a chance to stop. The cost is not typing time, it is doubt.

I will not quote you a conversion percentage per field, because the numbers that circulate for that are rarely traceable to a source you can check. What I can tell you is the mechanism, and the mechanism is enough to design around.

The fields that cause the most hesitation are budget, timeline, and headcount, because they feel like qualification rather than help. A buyer who has not decided yet will simply decline to be sorted.

What does the buyer already know before they arrive?

More than your form assumes. G2's 2026 Buyer Behavior Report found that 82 percent of buyers sourced software recommendations from an AI chatbot in the last 24 months, which means the person filling in your form has usually read about you, your category, and at least one competitor.

That changes the job of the form. It is no longer the start of an education. It is the moment a buyer who has already done the reading asks to talk to someone, and the design should respect how far along they are.

The practical consequence is that questions which imply they know nothing will annoy them. Asking whether they are familiar with your category, at the point where they requested a demo, reads as a form written before the internet.

Which three questions earn their place?

A work email, because it identifies the company and filters casual traffic. The company name, because it is the unit your team actually works in. And one open question about what they are trying to do, because it is the only field that changes the quality of the conversation.

The open question is the one people cut, and it is the one that matters most. A single sentence from the buyer in their own words tells your team more than five dropdowns, and it lets them prepare something specific.

Keep it genuinely optional and genuinely short. What are you hoping to solve, in one line. Most people answer it, and the ones who do not are still qualified.

What should you never ask on this form?

Budget, on a first request. Phone number, unless someone will actually call and the buyer has chosen that. And anything you can look up yourself, including company size, industry, and website, all of which are derivable from the domain in the email address.

Budget is the worst offender because it is both intrusive and unreliable this early. The honest answer is usually that they do not know, and forcing a guess produces a number that then anchors the whole conversation in the wrong place.

Phone number is the second. Asking for it when nobody calls is a trust cost with no benefit, and asking for it when someone does call should be framed as a choice rather than a requirement.

How do you qualify without interrogating?

Move the qualification after the form rather than into it. Enrichment from the email domain, a routing rule, and a short confirmation step give you most of what a long form would have told you, without making the buyer prove themselves first.

If you genuinely need one qualifying field, make it the one that changes who takes the call rather than whether you take it. Team size or region usually does that job, and neither feels like a gate.

Progressive profiling is the other option worth using. Ask the second question on the second visit, once a relationship exists, rather than stacking everything into the first interaction. This is the same instinct behind choosing between motions in a self serve trial versus a demo request.

What happens immediately after they submit?

Something specific, within minutes, that confirms a human is coming. A scheduling link is the strongest version, because it converts intent into a calendar entry before the buyer's attention moves on. A generic thank you page is the weakest.

If you cannot offer instant scheduling, say when they will hear from you and then beat that time. The promise is what reduces the anxiety of having filled in a form and received nothing.

Make the confirmation page useful rather than decorative. A link to the pricing page, the security page, or a short customer story gives the buyer something to do while they wait, and those are the pages they were going to look for anyway.

How do you tell whether the form is the problem?

Compare the number of people who reach the form with the number who complete it. If reaching is strong and completing is weak, the form is the problem. If reaching is weak, your page is, and no amount of field trimming will fix that.

Then read the submissions themselves. If most open answers are one vague word, the question is badly worded. If most are three specific sentences, your form is doing exactly what it should.

Watch for silent failures too. Validation that rejects legitimate email domains, or a submit button that fails quietly on mobile, will look identical to disinterest in your analytics. I have seen this cost more leads than any field ever did, and it is the subject of why a Webflow contact form quietly loses leads.

Does the answer change for enterprise buyers?

A little. Enterprise buyers expect a slightly more formal process and will tolerate one or two extra fields, particularly around region and team size, because those genuinely affect who should attend. They will not tolerate budget questions any better than anyone else.

What changes more is what happens next. An enterprise request should reach a person who can bring the right colleagues, and the routing matters more than the fields. That is also a decision about ownership, which I covered in who should own the demo, the founder or a rep.

If you sell to both, run one form and route on the back end rather than making buyers self select into a segment they may not identify with.

What should you do next?

Open your demo form and delete every field that does not change who runs the call. Add one open question if you do not have one. Then confirm that submitting it produces a scheduling link or a specific promise within minutes.

Give it a month before judging it, and read the open answers rather than only the count. The quality of those sentences is the real measure of whether the form is working.

If you want someone to review the whole path from page to booked call, reach out. It is usually a short piece of work with an immediate effect. Let's chat.