Demo Request Form Template
Book better demos, not just more of them — seven quick answers that tell sales who is calling, what they use today, and how soon they need it.
Let's make the demo about you, not our slide deck. A few quick answers and we'll come prepared with your use case, not a generic tour.
A demo request is the most expensive form your company runs — every submission books thirty minutes of a human's calendar. The design goal is therefore not maximum submissions; it is maximum prepared demos. Each field here exists because it changes what happens on the call.
Why these fields. Name, company email, and company name are the meeting invitation. The team-size question is the router: "just me" and "more than 200" deserve different sales motions, and most teams route the former to a self-serve nudge and the latter to their most senior rep. "What are you using today?" is the single best question in B2B qualification — the answer tells your rep whether to sell against a competitor, against spreadsheets, or against inertia, three completely different demos. The timeline question sets follow-up tempo: "this month" leads get called today; "just exploring" leads get nurtured without pestering.
The field that only appears when it matters. The procurement-and-security question is wired to conditional logic: it stays invisible unless the visitor selects "more than 200" users. Small-team buyers never see an intimidating enterprise question, while enterprise buyers get to flag SSO, DPAs, and security reviews before the first call — which routinely saves a full week of back-and-forth later. This is the Logic panel doing sales-ops work: one rule, "when team size is 200+, show the procurement question," built in a few clicks.
What we left out. Phone number — replies start over email, and demanding a phone number up front reads as "prepare to be cold-called," which suppresses exactly the thoughtful buyers you want. Budget questions are absent too; nobody answers them honestly before seeing the product.
Who uses this. B2B SaaS teams behind their "Book a demo" button, agencies qualifying discovery calls, and developer-tool companies who route "just me" answers into trial invitations instead of calls.
Make it yours. Tune the team-size brackets to your actual pricing tiers so routing maps one-to-one to your sales stages. Point a webhook at your CRM or Slack so a "this month" enterprise lead pings the team within seconds — speed-to-lead is the strongest predictor of demo show-rate, and a signed, auto-retrying webhook is the shortest path. If your funnel needs it, add a second logic rule that shows an extra question (say, compliance region) for the same 200+ segment. And check the responses view weekly: when "what are you using today" keeps naming the same competitor, your demo script should already know.
Frequently asked questions
Why does an extra question appear for large teams only?
A conditional logic rule shows the procurement/security question when "More than 200" is selected. Everyone else gets a shorter form, and enterprise deals surface their blockers before the first call.
How fast can my sales team hear about a new request?
Instantly — enable email notifications in Settings, or add a webhook that POSTs each submission to Slack or your CRM the moment it arrives, cryptographically signed and retried on failure.
Can I route small teams away from booked calls?
Use the team-size answer: filter or webhook-route "Just me" submissions into a trial-invite flow, and reserve live demos for the segments where a call changes the outcome.
Should the current-solution question be required?
We left it optional — some visitors genuinely have nothing in place. It still gets answered by most respondents, and an empty answer is itself a signal that you are selling against inertia.