By Mehdi HassanWhat is a book a demo page, and why do most underperform?
A book a demo page is the page where a prospective buyer asks to see your product with someone from your team. On a sales-led SaaS site it's usually the most valuable page you have, because almost every new customer passes through it.
Most of them underperform for one reason: they're designed as forms, not flows. Our research into how teams write about demo pages found that few guides connect the page, the form, the scheduler, the confirmation and the show rate. Yet a buyer experiences all five, and a leak at any one of them loses the meeting.
Picture the common version. A heading that says "Request a demo", a form with nine fields, a "Submit" button and a message that says someone will be in touch. The buyer then waits a day for an email, replies with times, waits again, and often never makes it to the call. Each of those steps is fixable, and none of them is about colors or button placement.
- Steps in the demo flow: page, form, scheduler, confirmation, reminder
- 5
- "Watch a Demo" vs "Get Started" in an Optimizely CTA test
- 1.59% vs 0.91%
- Designify's fixed price for a landing page, copy to Next.js build
- $6,000
This guide walks the whole flow in order. Each section links to a deeper article in this cluster, from book-a-demo page examples to inline scheduling and the question of whether you should even lead with a demo at all.
What should a demo request page say above the fold?
Above the fold, a demo request page should answer three questions: what will I see, how long will it take, and is it worth my time. Buyers hesitate to book because they fear a long, pushy sales call, so the copy's job is to make the meeting feel specific and safe.
- A headline that names the outcome of the call. "See how your team would close the books in 3 days" tells the buyer what they'll learn. "Request a demo" only tells them what you want.
- What the call covers. Three bullets: what you'll show, what you'll ask, what they'll leave with.
- Length and format. "30 minutes on video with a product specialist, not a sales script." If the first call is a short discovery call before the demo proper, say so.
- Proof that fits the buyer. Logos from their industry or size band, and one testimonial about the buying experience itself rather than the product.
- The form, visible. On desktop, put the form in the right column next to the copy. On mobile, the form follows a short intro, not a long scroll.
One honest line about pricing also helps. If you have a published price or a starting point, link to it. If you don't, say the call will cover pricing for their size. Our guide to SaaS pricing pages covers when to show numbers and when to route to sales.
How should a demo page design handle navigation and layout?
Good demo page design removes everything that pulls the buyer away from booking, while keeping enough context that they don't feel trapped. That usually means a simplified header, a two-column layout on desktop and a single column on mobile.
Element | Keep it | Cut or reduce it |
|---|---|---|
Header navigation | Logo link home, maybe pricing | Full mega menu |
Hero | Outcome headline, what the call covers | Generic product slogans |
Proof | Logos and one quote from similar buyers | Award badges and every logo you have |
Form | Visible without scrolling on desktop | Pop-up or a separate step to reach it |
Footer | Privacy link, security or compliance note | Full sitemap footer |
Chat widget | Only if staffed during business hours | Bot that asks the same questions as the form |
If buyers arrive at the demo page from many places, add a short line that confirms they're in the right spot: "Talk to us about the Business plan for teams of 50+." Sales-led sites with several buyer types often benefit from a small selector that changes the bullets, rather than one generic page. We cover the wider site structure in our guide to the sales-led SaaS website.
How many fields should a demo request form have?
A demo request form should have only the fields that change what happens next: who handles the lead, how fast, and what they prepare. For most B2B teams that's work email, name, company size and one question about the use case. Everything else can be enriched from the email domain or asked on the call.
Think of each field as a routing decision. Company size decides whether an account executive or a self-serve flow handles the lead. Use case decides which specialist runs the call. Phone number, job title and "how did you hear about us" rarely change routing, so they're the first to cut.
Pros
- Short form: more buyers start and finish it, especially on mobile
- Short form plus enrichment: sales still gets company data without asking for it
- One use-case question: lets you assign the right specialist and tailor the demo
Cons
- Very short form: more poor-fit bookings reach the calendar
- Long form: researchers and busy buyers abandon it halfway
- Free-text "tell us about your needs" boxes: lower completion and often unread
Our landing page form guide goes through each common field and when to keep it. The rule of thumb for demo pages: if a field doesn't change routing or preparation, it costs you bookings and gives you nothing back.
Deep dive: should you block free email addresses?
Blocking Gmail and other free domains raises the share of business leads, but it also blocks consultants, very small businesses and buyers who don't want sales emails at work before they're ready. If your product sells to companies above a certain size, a block can be reasonable.
A softer approach is to allow any email and use the company-size field for routing. Free-domain submits with small company sizes go to a nurture sequence or a self-serve path; everything else goes to sales. You keep the occasional real buyer who used a personal address.
Should the demo page let visitors book a time immediately?
Yes, for most qualified visitors the demo page should let them pick a time immediately after submitting the form. Waiting for a sales rep to email back is the slowest and leakiest step in most demo flows, and it's the one buyers find most annoying.
There are three common patterns, and the right one depends on how much qualification your sales team needs before spending time on a call.
Pattern | How it works | Best for |
|---|---|---|
Form, then email | Rep reviews the submit and emails times | Very high-touch enterprise sales with few leads |
Form, then routed calendar | Qualified submits see a calendar for the right rep | Most B2B SaaS with a sales team |
Calendar only | Visitor books directly with no form | Founder-led sales and services businesses |
Routed scheduling tools such as Chili Piper or Calendly's routing features show a calendar only to submits that match your rules, and send everyone else to a different path. We compare the options and their trade-offs in inline scheduling for demo pages.
What should the confirmation page and reminders do?
The confirmation page should turn a booking into a commitment: confirm the time, say who they'll meet and what to prepare, and give them something useful to look at before the call. This is the step most teams leave as a generic "Thanks, we'll be in touch" message.
Confirm the details on screen
Date, time in the buyer's time zone, length, who they'll meet (with a photo and name if possible) and how to join.
Say what to prepare
One or two questions to think about, or a short list of what to have ready, such as current tools or team size. It makes the call better and raises commitment.
Give them something to watch
A short product walkthrough video or a relevant customer story. Buyers who arrive informed have better calls.
Send a calendar invite and a reminder
An invite they can accept, plus a reminder the day before or a few hours before, from a real person's name.
Make rescheduling easy
A reschedule link in every email. A moved meeting is better than a no-show.
Our guide to thank-you pages covers confirmation pages in more depth, including what to show when a submit doesn't qualify for a live call.
How do you measure a demo request page?
Measure a demo request page as a chain of stage-by-stage rates, from page visit to qualified opportunity. A single "demo conversion rate" hides where the leak is: a high submit rate with a poor show rate can produce fewer opportunities than a stricter page.
Stage | Rate | What fixes it |
|---|---|---|
Reach | Demo page visits per site visitor | Clearer CTA labels and placement site-wide |
Submit | Form submits per demo page visit | Better copy, fewer fields, proof that fits |
Book | Meetings booked per submit | Instant routed scheduling |
Show | Meetings held per booking | Confirmation page, reminders, near-term slots |
Qualify | Opportunities per meeting held | Better targeting and routing rules |
For benchmark context, Unbounce's report puts the median SaaS landing page conversion rate at about 3.8%, but demo pages vary widely by traffic source and product price. Our articles on demo request conversion rate and SaaS conversion rate benchmarks break the numbers down by stage and source.
One warning on testing: most startup demo pages don't get enough traffic for clean A/B tests. Detecting a 15% lift at a 2% baseline takes roughly 15,000–20,000 visitors per variant, according to Spotler's guidance. Below that, fix the obvious problems in the flow and track stage rates over time instead.
Should you lead with a demo, a free trial or a waitlist?
Lead with a demo when the product needs setup, involves several stakeholders or sells on annual contracts; lead with a free trial when a single user can get value alone in one session. Many SaaS companies offer both but make one the primary CTA everywhere, which keeps the site's message clear.
The choice changes the whole site, not just a button. A demo-led site needs strong proof, pricing guidance and a page like this one. A trial-led site needs a frictionless free trial signup page and onboarding that delivers value fast. Our free trial vs demo comparison gives a verdict by price point, setup complexity and buyer.
Before launch, neither applies yet. That's where a waitlist landing page fits: it collects demand, segments it and tells you who to call first.
Which demo, trial and launch pages should you read next?
This cluster covers every page a SaaS team uses to turn interest into a conversation or a signup. Start with the one that matches the page you're working on this month.
If you're working on | Read |
|---|---|
Studying how others do it | |
The scheduler step | Inline scheduling: Calendly or Chili Piper on your demo page |
Choosing the primary CTA | |
A trial signup page | |
A pre-launch page | |
Pre-launch inspiration | |
Testing an idea before building | |
Launch day |
If your product is AI-based, buyers tend to be more skeptical about what it actually does, so the demo itself often belongs higher on the page. Our guide to AI landing page design covers demo-first layouts. And if the demo page is fine but the homepage isn't sending people there, a homepage-only redesign may be the faster fix.
What's a practical checklist for a demo request page?
Use this checklist to audit a demo request page end to end. Work through it in order, because the early items affect every stage after them.
- The CTA label across the site names the outcome of the call, not "Request a demo".
- The page headline says what the buyer will learn on the call.
- Three bullets say what the call covers, how long it is and who runs it.
- Proof on the page matches the buyer's industry or company size.
- The form has only fields that change routing or preparation.
- Qualified submits see a calendar with slots in the next few working days.
- Unqualified submits get a useful alternative path, not a dead end.
- The confirmation page shows the time, the host and what to prepare.
- Calendar invites, reminders and a reschedule link go out automatically.
- Each stage rate is tracked from page visit through to qualified opportunity.
If you can tick all ten, the page is in good shape and further gains will come from the product story and the demo itself. If you can't, the unticked items are usually cheaper to fix than a redesign.
