Demo Form Design

The demo request form is the highest-intent conversion point on a B2B SaaS website. Every field you add reduces completion rate by 5-10%. Every unnecessary field is a prospect who wanted a demo but didn't finish the form. The form's job is to capture enough information to route and personalize the demo while creating as little friction as possible.

The principle: ask only what you can't get from enrichment. If Clearbit or Apollo can fill a field from the email address, don't ask the prospect to type it.

The Optimal Field Set

Required fields (always include)

Three fields. That's the minimum viable demo form. Everything else is either enrichable or optional.

Recommended fields (add based on routing needs)

Fields to NEVER include on a demo form

Form Field Count and Conversion

The field-count curve

Every field beyond 3 costs you ~10-15% of completions. A 7-field form converts at roughly half the rate of a 3-field form. The data you collect from extra fields is worth less than the demos you lose.

The enrichment trade-off

The play: 3-4 visible fields + real-time enrichment on form submit = maximum data with minimum friction.

Form Design Patterns

Pattern 1: Minimal form (3 fields + enrichment)

Best for: companies with real-time enrichment (Clearbit Reveal, Apollo, HubSpot Breeze).

┌──────────────────────────────────────┐
│ See [Product] in Action              │
│                                      │
│ Work email   [________________]      │
│ First name   [________________]      │
│ Last name    [________________]      │
│                                      │
│ [Request a Demo]                     │
│                                      │
│ By submitting, you agree to our      │
│ privacy policy.                      │
└──────────────────────────────────────┘

On submit: enrich email domain for company, size, industry, title (if available). Route based on enriched data.

Pattern 2: Standard form (5 fields)

Best for: companies without real-time enrichment or needing routing data at submission.

┌──────────────────────────────────────┐
│ Request a Demo                       │
│                                      │
│ Work email      [________________]   │
│ First name      [________________]   │
│ Last name       [________________]   │
│ Company name    [________________]   │
│ Company size    [▾ Select         ]  │
│                 1-50 employees       │
│                 51-200 employees     │
│                 201-1,000 employees  │
│                 1,000+ employees     │
│                                      │
│ [Get Your Demo]                      │
└──────────────────────────────────────┘

Pattern 3: Smart form (3 fields + conditional)

Best for: companies that need one extra qualifying question but don't want to show it to everyone.

Step 1:
┌──────────────────────────────────────┐
│ Work email   [________________]      │
│ First name   [________________]      │
│ Last name    [________________]      │
│ [Continue →]                         │
└──────────────────────────────────────┘

Step 2 (appears after email is entered, enrichment runs):
┌──────────────────────────────────────┐
│ What are you most interested in?     │
│ [▾ Select                         ]  │
│ Outbound automation                  │
│ Inbound lead management              │
│ Pipeline reporting                   │
│ All of the above                     │
│                                      │
│ [Request Demo]                       │
└──────────────────────────────────────┘

Smart form rules:

• Step 1 collects the email. Enrichment fires in the background while the user sees Step 2
• Step 2 asks ONE qualifying question. Not three. One. This question should help personalize the demo, not qualify the lead
• If Step 2 is abandoned, the form still captured the email from Step 1. The lead isn't lost
• The two-step form converts nearly as well as a single-step 3-field form because the prospect has already committed by entering their email

Pattern 4: Embedded calendar (form + booking)

Best for: self-serve booking motions where you want the prospect to schedule immediately.

┌──────────────────────────────────────┐
│ Book a Demo                          │
│                                      │
│ Work email   [________________]      │
│ First name   [________________]      │
│ Last name    [________________]      │
│                                      │
│ Pick a time:                         │
│ ┌────────────────────────────────┐   │
│ │ [Calendly / Chili Piper embed] │   │
│ │  Mon 10am  Mon 2pm  Tue 11am  │   │
│ │  Tue 3pm   Wed 9am  Wed 1pm   │   │
│ └────────────────────────────────┘   │
│                                      │
│ [Confirm Booking]                    │
└──────────────────────────────────────┘

Embedded calendar rules:

• Show the calendar inline, not as a redirect. Redirecting to Calendly loses 20-30% of prospects in the transition
• Show available times immediately. Don't make the prospect pick a rep first. Route to the right rep behind the scenes based on territory/round-robin
• If using Chili Piper: it handles routing + calendar in one step. If using Calendly: route first (via enrichment), then show the right rep's calendar
• Confirmation page should set expectations: "You'll meet with {rep_name}. Here's a brief overview of what we'll cover"

Form UX Rules

Layout and design

CTA button copy

CTA rules:

• Button color should contrast with the page background. If the page is white, the button shouldn't be white. Use your brand's primary action color
• Button width should be at least 200px (desktop) or full-width (mobile). Small buttons are hard to tap
• Button text should describe the outcome, not the action. "Get Your Demo" not "Submit Form"

Validation and error handling

Post-Submit Experience

What happens after the form is submitted matters almost as much as the form itself.

Thank-you page

Thank-you page rules:

• Never show a generic "Thanks, we'll be in touch." Use the thank-you page as a conversion accelerator
• If you can embed a calendar on the thank-you page, do it. Prospects who book immediately show up at 2x the rate of prospects who wait for an SDR to send a link
• The thank-you page should have no site navigation. Don't let the prospect wander away. Keep them focused on booking or consuming content

Post-submit automation

Measuring Form Performance

Form optimization cadence

A/B Tests Worth Running

A/B testing rules:

• Run each test for at least 2 weeks or 200 submissions per variant, whichever comes later
• Measure downstream metrics, not just completion rate. A 3-field form may convert higher but produce lower-quality leads than a 5-field form. Measure MQL rate and meeting rate per variant
• Only test one variable at a time. Changing the CTA AND removing a field in the same test makes it impossible to know which change drove the result

Anti-Pattern Check

• Form has 8+ fields. Every field beyond 3 costs 10-15% of completions. Cut to 3-5 fields and enrich the rest
• Asking for company size as an exact number. Nobody knows the exact headcount. Use ranges: 1-50, 51-200, 201-1000, 1000+. Dropdown, not free text
• Asking for budget on the demo form. Too early. Feels like a qualification trap. The prospect hasn't seen the product yet. Ask on the discovery call
• Required "message" field. Long text fields kill completion rate. If you want to know what they're interested in, use a single-select dropdown with 4-5 use cases, not a text area
• CTA says "Submit." Generic and lifeless. "Get Your Demo" or "See [Product] in Action" converts 15-30% better
• No enrichment on form submit. Asking 7 questions when enrichment can answer 4 of them is pure friction. Install Clearbit, Apollo, or HubSpot Breeze and enrich on email domain
• Generic thank-you page ("Thanks, we'll be in touch"). The thank-you page is the highest-intent moment. Embed a calendar. Show a case study. Open an AI chat. Don't waste it
• No mobile testing. 40-60% of B2B traffic is mobile. A form that breaks on mobile loses half your potential demos. Test on a 375px viewport before launching
• No field-level abandonment tracking. "The form converts at 15%" doesn't tell you which field is the problem. Track where people drop off to identify and fix the friction point
• CAPTCHA on the demo form. CAPTCHAs block real prospects and kill mobile completion. Use a honeypot field (hidden input that bots fill but humans don't) for spam prevention instead