Template Overview

Most software companies run a demo request form that collects a name, an email, and a company, then drops the result into an inbox where someone decides whether it is worth an hour of a salesperson's time. The information needed to make that decision was available at the moment of submission and simply was not asked for. This template asks for it. The same demo booking flow that captures contact details also captures company size and what the prospect actually wants to see, then hands them to your scheduling calendar on the next page.

It is a two-step flow on purpose. Splitting the request from the calendar means the qualifying questions get answered before a slot is held, which is what makes the difference between a booked demo and a booked demo you already understand. The questions on the first page are yours to define: headcount, budget authority, current tooling, the problem they are trying to solve, timeline. Each one can carry a score, and the score can route the prospect to a different calendar, a different sales owner, or a self-serve trial rather than a call.

The part no competing template covers is what happens between the booking and the call. Every request becomes a contact in involve.me's built-in CRM with its answers attached, and an email sequence runs from there: a confirmation with what to expect, a reminder that reduces no-shows, and a different branch for prospects who requested a demo but never picked a slot. Use it as a book a demo form embedded on your pricing page, as a pop-up on high-intent product pages, or as the standalone landing page behind a paid campaign.

Key Features

Qualifying questions in the same flow as the contact fields - company size, use case, timeline, and budget authority sit alongside name and email rather than in a follow-up email, so every request arrives with enough context to prioritize it. Add or remove questions freely, since each one costs completions and only some of them earn their place.
Lead scoring and logic jumps that route the request - score the answers, then send an enterprise-sized prospect to an account executive's calendar and a small self-serve account to a trial signup or a group demo. Nobody else in this category routes at all, and routing is what stops your calendar filling with calls that were never going to close.
A scheduling embed on the second page - Calendly or your calendar of choice loads once the request is complete, so the prospect picks a slot without leaving the funnel and you never have to send an availability email.
OTP verification and email validation on the contact step - verify the email or phone with a one-time code and block disposable and personal addresses, which blocks junk submissions before they enter any workflow. On a form whose output is a calendar slot, a fake address costs you a held slot and a no-show.
Email sequences between the booking and the call - confirmation, reminder, and pre-call material send automatically with the prospect's own answers merged into the body, and open and click tracking feeds back into the workflow so a prospect who ignored every email gets flagged before the call is wasted.

Benefits

Fewer unqualified demos on the calendar - the answers that decide whether a demo is worth running are collected before the slot is held, not discovered on the call.
Fewer no-shows - an automatic confirmation and a reminder go out without anyone remembering to send them, and the prospect who booked a slot has already answered enough questions to be invested in showing up.
Sales gets context instead of a name - company size, use case, and stated problem land on the contact record and sync into your CRM, so the first three minutes of the call are not spent on discovery that a form could have done.
Requests that stall still get followed up - a prospect who completed the form but never picked a slot is a real signal, and an email sequence can chase that specific group rather than treating them as lost.
Runs on your own site and your own branding - embed it inline or as a pop-up, publish it on a custom domain, and remove involve.me branding on Grow and above, so the request looks like part of your product rather than a third-party form.

How It Works

Customize
Open the template and decide which qualifying questions earn their place. Company size and use case are usually worth the friction, budget authority and timeline are worth it for higher-priced software, and anything you would not act on differently should come out. Rewrite the labels in the language your buyers use rather than internal category names, set the required fields deliberately, and match fonts, colors, logo, and background to your product UI so the form reads as an extension of it.
Configure
Attach scores to the answers that predict fit, then use logic jumps to route by that score: a large account to a named calendar, a small one to a trial or a group session. Turn on OTP verification and block disposable and personal email domains on the contact step, since a work email is itself a qualifying signal for B2B software. Add hidden fields for UTM parameters and any product-side identifier so every request arrives with attribution, then connect the scheduling embed on page two to the calendar the score points at.
Connect
In the Connect tab, map every answer to a property on the contact record and push the request into HubSpot, Salesforce, Pipedrive, or your CRM of choice as a lead or a deal. Send a Slack notification for requests above your score threshold so a high-fit prospect reaches sales in minutes. Then build the sequence in the workflow builder: confirmation immediately, a reminder before the call, pre-call material for prospects who named a specific use case, and a separate branch for anyone who submitted the form without booking a slot.
Share
Embed it inline on your pricing page and product pages where demo intent is highest, using a div wrapper plus a script tag, or trigger it as a pop-up from a "Book a demo" button so the prospect never leaves the page. Publish it as a standalone landing page on a custom domain for paid campaigns and outbound sequences. Carry UTM parameters through with hidden fields so booked demos can be traced back to the campaign that produced them.
Analyze
The number to watch is not form completions, it is completions that turned into a held slot, because the drop between those two is where the funnel actually leaks. Partial submission tracking shows which question people abandon on, which is usually the one asking for something they consider premature. Read the distribution of company sizes and use cases to see whether your traffic matches your ICP, then A/B test the question count, the order, and whether the calendar sits on page two or page one.

Frequently Asked Questions

: It is a form a prospect fills in to ask for a live walkthrough of a product. At minimum it collects contact details so somebody can get back to them. A better one also collects the information the vendor needs to decide who should run the demo, what to show, and whether the demo is worth running at all, which turns it from a contact capture into a qualification step.
: In practice the terms are used interchangeably, but the distinction is useful. A demo request form ends with a request that somebody has to respond to. A demo booking form ends with a slot on a calendar. This template does both in sequence: the request and the qualifying answers on page one, the calendar on page two, so nothing waits on a manual reply.
: Name, work email, and company are the floor. What earns the extra friction is company size, the use case or problem they want the demo to address, and for higher-priced software the timeline and whether they own the budget. Phone number and job title are optional and often better inferred than asked. Every field costs completions, so include a field only if a different answer would change what you do next.
: There is no universal number, only a trade-off you can measure. Splitting the questions across pages rather than stacking them in one long form reduces the perceived length, and partial submission tracking tells you the exact question where your own traffic gives up. Start with the fields you will act on, watch the abandonment point, then cut or move whatever sits in front of it.
: Yes. Attach a score to each answer, and the total score classifies the request as it arrives. Logic jumps then route on that score, sending a high-fit prospect to a sales calendar and a low-fit one to a trial signup, a group demo, or self-serve documentation. This is the piece missing from every other demo request template in this category, which capture the same details and hand them all to the same inbox.
: Yes. The second page carries a scheduling embed, so Calendly or your calendar tool loads inside the funnel and the prospect picks a slot without a redirect. Routing by score means different segments can be pointed at different calendars, so an enterprise request lands on an account executive's availability and a small account lands on a shared one.
: Three things do most of the work. Confirm immediately, because a booking with no confirmation feels provisional. Remind before the call, ideally more than once for a slot booked more than a few days out. And verify the contact details at submission with OTP so the reminder actually arrives. All three run as an email sequence off the booking rather than as something a person remembers to do.
: Yes. Turn on OTP email verification to require registrants to confirm a code sent to their inbox before the submission completes, which blocks throwaway addresses. You can also add validation rules to the email field and restrict free-mail domains in the field settings, so only work emails make it through to your sales team.
: They stay a contact with everything they answered attached, which makes them one of the most useful segments you have: interested enough to complete the form, hesitant at the calendar. A dedicated email sequence can chase that group specifically, and open and click tracking tells you which of them are still paying attention.
: Yes. Embed it inline or as a pop-up using a div wrapper plus a script tag, so a "Book a demo" button opens the funnel without leaving the page. It also runs as a standalone landing page on a custom domain with SSL, and branding can be removed on Grow and above so the form reads as part of your own product.
: Every request becomes a contact in involve.me's built-in CRM with company size, use case, score, and any custom answers stored as properties, plus a timeline of what that contact did. From there contacts sync two-way to HubSpot, Salesforce, and Pipedrive, or flow into an email platform, Google Sheets, or Slack, with Zapier and webhooks covering anything else. Requests also export to XLS and CSV.
: Hidden fields carry UTM parameters and any product-side identifier into the submission data, so campaign, source, and medium arrive on the contact record alongside the answers. Combined with the native tracking integrations for Google Analytics, Meta Pixel, Google Tag Manager, TikTok Pixel, and LinkedIn Insight Tag, a held calendar slot can be traced back to the ad that produced it.
: involve.me is SOC 2 Type II audited and GDPR-compliant, with configurable data retention per funnel, password protection, and SSO or SAML2 for enterprise accounts. The consent checkbox on the contact step is there to be edited into wording that matches your own privacy policy rather than left as placeholder text.
: Yes, it is available on the free plan and can be customized and published without payment. Paid plans start at $29 per month billed annually and add more live funnels, custom domains, and branding removal. A/B testing, webhooks, partial submissions, and OTP verification are on the Scale plan.
: Yes. Describe your qualifying criteria, how you want requests routed, and which calendar each segment should reach, and the AI Agent generates the funnel: questions, scoring rules, routing logic, page layouts, copy, and design. It edits an existing funnel the same way, so this template can be the starting point and then reshaped by prompt.