On eleven well-known B2B demo request pages we checked on 25 October 2026, the first screen of the form asked for between one and ten fields, with a median of four. Only two put a calendar straight after the form, although Chili Piper's analysis of nearly 4 million form submissions found that qualified visitors who can schedule on the spot book a meeting 66.7% of the time, against an industry average it puts at 30%.
This guide covers the page itself: what the eleven examples ask and show, what the form-length research supports, and what earns a place next to the form. Funnel benchmarks are in our post Demo Request Conversion Rates 2026, and speed-to-lead data in B2B SaaS Demo Request and Lead Form Statistics 2026.
The 11 demo request pages we checked
We opened each page in a desktop browser at 1,440 pixels wide on 25 October 2026, counted the visible fields on the first step and noted what sat beside the form. We submitted nothing, so later steps on the email-first pages are unknown. The sample mixes product-led companies with a sales tier and sales-led platforms.
| Company | First-step fields (required) | Site nav on page | Next to the form | After submit, as stated |
|---|---|---|---|---|
| Notion | 1 (1), email first | No | Customer logo strip | Further steps |
| Gong | 1 (1), email first, plus consent box | No | Three benefit tabs, logos, review scores | "Book your demo" |
| HubSpot | 1 (1), email first | No | Three G2 badges, logo carousel, chat | Further steps |
| Chili Piper | 3 (3): email, CRM, country | No | Capability list, named customer result, G2 score | "Pick a time on the next screen" |
| Deel | 3 (3): email, first and last name | No | Outcome headline, three benefits, review scores | Calendar button |
| Linear | 4 (3): name, email, company size, requirements | Yes | Three reasons to talk, sales email address | Not stated |
| Vercel | 5 (5): name, email, country, website, use case | Yes | Five customer outcome figures | Not stated |
| Rippling | 7 (7), including phone and product | No | Five review-site ratings | Not stated |
| Asana | 8 (6), including phone | Logo and one button | What the call covers, customer quote | Reply within a business day |
| Webflow | 9 (8), phone optional | Yes | Customer logo wall, then a customer quote | Not stated |
| monday.com | 10 (8), including phone | Yes | What the call covers, customer quote, ROI figures | Not stated |
Source: Octo Agency check of each live page, 25 October 2026; raw file research/OB-0102-demo-pages-2026-10-25.csv
Two patterns stand out. The shortest first steps belong to companies with heavy traffic and enrichment behind the form: an email is enough to look up company size and route the lead. The long forms belong to companies selling to every size of business, where the form does the routing a rep would otherwise do by hand.
What the form-length research supports
The common claim is that every extra field costs conversion. The evidence is thinner and more specific than that.
| Source | Sample | Finding |
|---|---|---|
| HubSpot, Dan Zarrella | Over 40,000 landing pages | Conversion falls as fields are added, but "not as steeply" as expected; multiple text areas and dropdowns hurt most |
| RevenueHero, 2026 | Over 1 million B2B SaaS submissions | Top performers book 77% of qualified requests with two fields, 76% with thirteen |
| Zuko, field research | 1,362 forms, 12 months | Mean abandonment: name 5.27%, email 6.41%, phone 6.28% |
| Zuko, form type benchmark | Zuko customer forms | Enquiry forms convert 42.7% of viewers, lowest of the types listed; contact forms 47.4% |
| Navattic, 2026 | Over 40,000 interactive demos | When a demo is gated, 75% of gates use one field |
Sources: HubSpot, RevenueHero, Zuko, Navattic
Short fields cost little. Fields that need effort, such as a free-text box or a forty-option dropdown, cost more. And the stage measured changes the answer: RevenueHero's figure is qualified request to booked meeting among the top 10%, where the fields do the qualifying. It says nothing about how many visitors abandon a long form before submitting.
The email-first pattern. Notion, Gong and HubSpot ask for one field and reveal the rest after. This captures a partial lead even if the visitor stops, and lets enrichment fill company size and country. We found no published controlled test of email-first against a single-screen B2B demo form, so treat it as plausible, not proven, and test it on your own traffic.
Phone numbers. Four of the eleven ask for a phone number on the first step, three as required. Zuko ranks phone among the most abandoned fields. If sales does not call within the hour, make it optional, as Webflow does, or drop it.
Which fields to keep, and which to cut
The test for every field: does sales use it to route, prioritise or prepare for the call within the first day? If not, it belongs in the CRM later.
| Field | Keep when | Cut or defer when |
|---|---|---|
| Work email | Always | Never |
| Name | Always, as one "full name" field | Split only if the CRM demands it |
| Company size | It routes to different teams or plans | Enrichment returns it from the domain |
| Country or region | Sales is split by territory | One team covers the world |
| Phone | Sales calls within the hour | Follow-up is by email |
| Job title | Different reps take different roles | It is only used for reporting |
| Product interest | The product line is wide, as at Rippling | One product, one demo |
| Free-text requirements | Deals are large and the call needs preparation | It is required on a self-serve product |
Source: Octo Agency reading of the eleven pages and the studies above
Linear requires the free-text box and keeps everything else short, which suits a product where the call depends on the team's setup. Vercel asks for the company website, so a rep can look at the stack first. Both fields are used. The form to avoid collects ten fields because the marketing automation tool has ten.
What to put next to the form
The space beside the form answers the questions a visitor has while deciding whether to hand over an email. Five kinds of content recur across the eleven pages.
1. What the call covers. Asana and monday.com list three things the call will do, such as which pricing tier fits. Linear gives three short reasons to get in touch. This matters because buyers would rather skip the call: Gartner's survey of 646 B2B buyers, fielded in August and September 2025, found 67% favour a rep-free experience, as reported by Digital Commerce 360. Tell them what they get for their time.
2. What happens after submit, and when. Asana says the sales team "will get in touch within a business day". Chili Piper says the form "Takes 30 seconds" and the visitor picks a time on the next screen. Deel's button reads "Choose a date & time". The other eight pages say nothing. Clay's September 2026 experiment submitted 6,346 demo forms and found two-thirds of companies never replied, so visitors have learned to expect silence. A stated response time is a reason to trust your page over the next one.
3. One named customer with one result. Webflow quotes a named manager at NCR; Chili Piper quotes Gong's director of marketing automation reporting a 70% lift in demo form conversions, a vendor's own customer claim. A name, a role and a number can be checked, which a wall of logos cannot.
4. A short trust line. Seven of the eleven show review scores, G2 badges or customer logos near the form. One line is enough; Rippling's five ratings under the button say the same thing five times.
5. A route out for the wrong visitor. Linear, Webflow, Asana and monday.com link support next to the form, which keeps existing customers with a billing question out of the sales queue.
Trust badges are everywhere. A stated next step and a calendar are rare, and they are the elements tied to the strongest booking numbers in the research.
Navigation, layout and labels
Navigation. Six pages remove the site navigation and keep a logo, the classic landing page rule for paid traffic. Linear, Vercel, Webflow and monday.com keep it, which suits visitors arriving from the site header who may want to check pricing first. Our rule of thumb: ad landing pages drop the nav; the main demo page keeps a route to pricing.
Layout. Ten of the eleven use two columns on desktop, reassurance on one side and the form on the other. Rippling centres a single column. Both work; a form pushed below the fold by a long hero does not, and none of the eleven do it.
Labels. Rippling and Deel use the placeholder as the label. The Nielsen Norman Group advises against this: placeholder text vanishes once the visitor types, strains memory and makes errors harder to check. The guidance dates from 2014, reviewed in 2018, and still holds.
Product tours. Navattic's 2026 report finds 66% of top-performing interactive demos do not start with a form gate. If you offer a tour beside the form, leave it ungated.
The order we would make the decisions in
When we build a demo page in Webflow as part of a four-week marketing site, we would settle these before anyone opens a design file:
- List every field and the person in sales who uses it. Delete any field without a name.
- Decide whether enrichment can replace company size and country; if so, test email-first.
- Decide what happens in the first minute after submit, and write that sentence on the page.
- Pick one customer with a name, a role and a number.
- Add the support link.
- Set navigation by traffic source.
The button label comes last. Among RevenueHero's top performers, 29% use "Book a demo" and 21% "Get a demo": worth a test once the rest is right.
What this means for your demo request page
The form-length debate is mostly a distraction. The pages we checked range from one field to ten, and the research says short fields cost little while text areas, long dropdowns and phone numbers cost more. The cheaper gains sit either side of the form: saying what the call covers and what happens next, showing one named result, and letting a qualified visitor book before they leave. Most of the pages we checked do the first poorly and the last not at all. Our marketing website service covers demo pages built in that order.
