Demo Request Form Template
Book demos your team can prepare for. Seven quick answers tell sales who is calling, what they use today, and how soon they need it.
Let's build the demo around you. Answer a few quick things and we'll show up prepared for your use case instead of a generic tour.
A demo request is the most expensive form your company runs, because every submission books thirty minutes of a human's calendar. That makes the goal prepared demos rather than a big pile of submissions. Each field here exists because it changes what happens on the call.
What each answer changes on the call. 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, so most teams send the former to a self-serve nudge and the latter to their most senior rep. "What are you using today?" is the strongest question in B2B qualification. The answer tells your rep whether to sell against a competitor, against spreadsheets, or against inertia, three different demos in one field. The timeline question sets follow-up tempo: "this month" leads get called today, and "just exploring" leads get nurtured without pestering.
The question that hides until it fits. The procurement-and-security question runs on conditional logic: it stays invisible unless the visitor selects "more than 200" users. Small-team buyers never meet an intimidating enterprise question, while enterprise buyers get to flag SSO, DPAs, and security reviews before the first call, which 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 off, and why. Phone number goes first: replies start over email, and demanding a number up front reads as "prepare to be cold-called," which suppresses the thoughtful buyers you want. Budget questions are absent too, because nobody gives a truthful answer before seeing the product.
Route it, then read the responses. B2B SaaS teams run it behind their "Book a demo" button, agencies qualify discovery calls with it, and developer-tool companies route "just me" answers into trial invitations instead of calls. Tune the team-size brackets to your pricing tiers so routing maps one-to-one to your sales stages, and 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 to it. If your funnel needs more, add a second logic rule that shows an extra question, say a compliance region, for the same 200+ segment. Then read the responses view every week: 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?
Within seconds. 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, since some visitors have nothing in place yet. Most respondents answer it anyway, and an empty answer is itself a signal that you are selling against inertia.