Demo request form
A demo request from a prospect is time-sensitive. This form captures the minimum needed to qualify and schedule: name, email, company, company size, what they are hoping to solve, and preferred time. It flows straight to Slack or a webhook, so the request reaches your team while their interest is fresh — no back-and-forth over email to establish whether the call is worth having.
The form beside this text is live. Fill it in and submit it — it validates exactly as it would for a real respondent, and saves nothing.
Qualify before you call
The use-case textarea forces the prospect to articulate their problem in a sentence or two, telling you whether the product is a fit before you invest an hour on a call.
Real-time notification to your system
Send the request to a webhook or Slack channel and your team sees it the moment it arrives, rather than hours later when someone checks email.
No card required.
Demo Request
Live previewHow to build this form
5 steps in the editor. Nothing here needs a paid plan.
- Add name and email fields for the prospect.
- Add a text field for company name and a dropdown for company size, so you can segment by scale.
- Add a textarea for what they are hoping to solve — this is where qualification happens.
- Add an optional text field for preferred demo time.
- Send each request to a webhook or Slack channel so it reaches your team immediately.
Fields in this form
6 fields, using 4 of the 19 field types available.
| Question | Field type | Required |
|---|---|---|
| Full name | Short text | Yes |
| Yes | ||
| Company name | Short text | Yes |
| Company size | Dropdown | Yes |
| What are you hoping to solve? | Long text | Yes |
| Preferred demo time (optional) | Short text | Optional |
What goes wrong with this form
Specific to a demo request form, not general advice about forms.
Asking too many qualification questions
Company size, use case and preferred time do the work. Ask about budget or integrations on the discovery call instead, once the use case looks promising.
Making the use case optional
Mark it required — it is the one field that separates a qualified lead from someone browsing. Without it you have no signal on whether the call is worth an hour of your time.
Forgetting to set a destination
Without a webhook or Slack destination, a demo request sits unseen in your dashboard until someone happens to check it, losing the moment while interest is hot.
Questions about this form
What should I ask in a demo request form?
Name, email, company, company size, and what they are hoping to solve. The use-case question does the real work of separating a qualified lead from a tire-kicker; preferred time is a nice optional extra.
Can the form schedule the demo automatically?
No. The form collects the request and sends it to you or your CRM. You review it, confirm the prospect is qualified, and reply with available times — the form filters, you schedule.
Should I ask for a phone number?
Only if you need it. Email is enough to reply and schedule; phone adds friction for a prospect who just wants to book a call.