The demo request page is the last page between a buyer's intent and your pipeline. Visitors who reach it have already decided they want to talk, so the page has a narrow job: keep them from changing their mind. Every extra field, unclear next step and missing reassurance is a chance to lose a lead you already paid to attract. This gallery breaks down 10 live demo and contact-sales pages from well-known B2B companies, focusing on the details that decide whether the form gets submitted.
We visited each page in October 2026 and describe what it showed at the time, including the fields in each form. Pages and forms change, so check the live links before copying anything. Our B2B landing page examples post covers the demo landing page as one of eight page types reached from ads; this gallery focuses only on the request page itself, mostly reached from a site's own navigation and CTAs.
What Decides Whether a Demo Form Gets Submitted
We compared every page on the same five points:
- Form length and order: how many fields are visible before the first commitment, and which come first.
- Steps: single form, multi-step, or a single email field that expands.
- Expectation setting: does the page say what happens after submission and how fast?
- Proof next to the form: quotes, ratings, customer counts.
- Alternatives: a way out for people who are not ready for a call (self-serve demo, support link, email address).
The field question is covered in depth in our guide to the B2B lead capture form. Here the interest is in how real companies balance it.
1. Gong: One Field, Then the Rest
The Gong demo page headline is "Turn pipeline into revenue with Gong," with three short benefits (bet big and win, improve team productivity, close deals more efficiently). The visible form has a single field, work email, and a "Book your demo" button, with a consent line under it. Proof sits right next to the form: a customer count, a share of large companies using Gong, an average review rating, an analyst recognition and a recommendation rate.
What works: asking for only a work email first is the lowest possible commitment. The hidden fields in the page's form suggest the rest of the profile is filled in from enrichment data behind the scenes, so the buyer does not have to type it.
What we would test: the page does not say what happens after the click: a calendar, a call back, an email. A one-line "You'll pick a time on the next screen" would remove the last uncertainty.
2. HubSpot: Product-Specific Demo Page With a Phone Number
The HubSpot demo page is specific to one product. Its headline offers a demo of the marketing software, and the subhead lists popular features (forms, social media, email marketing, automation, campaign management, reporting). The form starts with a single email field and a "Next" button. A sales phone number is shown at the top. A customer count and country count follow, then a section titled "Your top marketing challenges, solved" with tabs for building demand, generating leads and automating marketing.
What works: a separate demo page per product means the copy can talk about the buyer's actual problem, not the whole platform. The visible phone number serves buyers who would rather call than fill a form.
What we would test: the challenges section sits below the form. For visitors who arrive from a specific feature page, we would test reordering the tabs so their feature comes first.
3. Zendesk: A Demo You Customize First
The Zendesk demo page is titled "Customize your free Zendesk demo." It is a multi-step flow: the first step asks which use case the visitor is interested in, and the form also asks for help desk size, work email, name, phone, company name and country. Links to watch recorded video demos are available for visitors who do not want to book.
What works: the framing changes the form from "tell us about yourself so sales can qualify you" to "tell us what you need so the demo is relevant." The questions are the same, but the buyer sees the benefit of answering them.
What we would test: the recorded demo link is easy to miss. For visitors early in their research, we would test making it a visible second option on step one.
4. Notion: Email First, Nothing Else Visible
The Notion contact-sales page starts with a single question, "What's your work email?" and a "Next" button. Nothing else competes with it on the first screen.
What works: one question is the easiest possible start, and once a visitor has typed an email they are more likely to finish the following steps. It also lets Notion route the visitor by email domain before asking anything else, for example sending existing customers to their account team.
What we would test: the first screen gives no reason to talk to sales. A short list of what the conversation covers (security review, migration, pricing for larger teams) would help visitors who are unsure whether they need sales at all.
5. Linear: Short Form, Clear Topics, Direct Email
The Linear contact-sales page lists what a sales conversation covers: get a demo, learn which plan is right, onboarding and migration support. A separate line points technical issues to support. The form has four fields: full name, work email, company size (as five ranges) and a free-text box for requirements. Under the form, the page gives a direct sales email address.
What works: four fields, one of them a click instead of typing. The direct email address is a small but real reassurance that a human reads the request. Sending support questions elsewhere keeps the sales queue clean.
What we would test: the requirements box is open-ended. A placeholder with an example ("We are 80 engineers moving from Jira, need SSO") could improve the quality of what people write.
6. Slack: Three Reasons to Talk, a Quote, a Longer Form
The Slack contact-sales page headline is "Contact our sales team," with three reasons listed: schedule a demo, get pricing information, explore use cases for your team. Product questions are pointed to the help center. A quote from a named sales executive at a well-known company sits beside the form. The form asks for first and last name, work email, role (from CXO to contributor), country, company name, company size, phone, what the sales team can help with, and a comments box prompting "What challenges are you looking to overcome?"
What works: the role dropdown with seniority levels gives sales an immediate routing signal, and the challenges prompt gets the buyer to write the brief for the first call.
What we would test: this is the longest form in the gallery. We would test moving phone, country and comments to a second step after the core contact details are captured.
7. monday.com: Proof-Heavy, Long Form
The monday.com contact-sales page headline is "Talk with our sales team to see how monday.com can fit your needs," followed by three benefits (discuss the best solution, get tailored pricing, see cross-team workflows). A customer quote with a named director appears next to the form. The form asks for first and last name, work email, job title, phone, company name, company size, what the visitor wants to explore, and a description of business needs. Below the form, the page cites results from a commissioned economic impact study and adds more customer stories with named people and companies.
What works: for a buyer who needs to justify the purchase internally, the ROI study and case results are material they can forward. "Get tailored pricing information" is a strong reason to fill the form for anyone who already saw the public pricing.
What we would test: phone number is required. Making it optional and measuring both completion and meeting rates would show whether it is worth the drop-off.
8. Asana: A Response Time Promise
The Asana sales page headline is "Talk with an Asana expert." The copy says the sales team will get in touch within a business day and lists what they can walk through: how Asana helps an organization, which pricing tier fits, and other questions. Existing users are pointed to the help center. A customer quote from a named VP sits beside the form, which asks for first and last name, company email, phone, company size (seven ranges), country and a note about the team and a process to track.
What works: "within a business day" is the only explicit response time in this gallery. It sets an expectation the buyer can plan around, and it puts useful pressure on the team behind the form. If you make that promise, our speed to lead guide covers how to keep it.
What we would test: offering an immediate calendar booking for visitors who match the ideal customer profile, so the business-day wait applies only to everyone else.
9. Atlassian: Topic Picker Before the Form
The Atlassian enterprise contact page starts with "I'd like to discuss" and a set of topics: product features, pricing and quotes, migration options, billing and licensing, technical support. The form asks for company email (with a note that personal email domains will be rejected), first and last name, company, job title, which product the question is about, and the question itself, with guidance on including license identifiers.
What works: the topic picker routes the request before a human sees it, so a licensing question goes to the right team instead of a general sales queue. Saying up front that personal email addresses will fail saves the visitor a failed submission.
What we would test: the product question asks the visitor to choose the product with the most users. A multi-select would capture cross-sell interest without forcing a choice.
10. Intercom: An Interactive Demo Instead of a Form
The Intercom demo page skips the form. It loads a mock company website with the Intercom messenger running on it, and the visitor can try the customer side of the product directly, with a prompt to try the demo and see how customers and teams experience Intercom.
What works: for a product that lives on the customer's own site, letting the buyer use it is more convincing than booking a call to watch someone else use it. It also serves visitors who are not ready to talk to anyone yet, and it can feed a later sales conversation with a warmer lead.
What we would test: a visible "talk to sales" option inside the interactive demo, for visitors who become ready to talk while trying it.
Patterns Across the Examples
- Email first is now common. Gong, HubSpot and Notion open with one field. The rest is either collected in later steps or filled from enrichment.
- Company size is almost always a click. Linear, Slack, Asana and Zendesk ask for size as ranges, which is easier than typing a number and gives sales a routing signal.
- Support is routed away. Linear, Slack, monday.com, Asana and Atlassian send product and billing questions elsewhere before the form.
- Proof sits beside the form. Named quotes (Slack, monday.com, Asana) and ratings (Gong) appear at the moment of decision.
- Few pages say what happens next. Asana's response time promise is the exception. Most leave the buyer guessing whether a calendar, an email or a phone call follows.
- Alternatives for the not-yet-ready. Zendesk's recorded demos and Intercom's interactive demo give early-stage visitors something to do besides leaving.
The same demo page is shown to every visitor in these examples. Yet a known target account, a returning customer and a first-time visitor from a blog post need different amounts of reassurance and different form lengths. That is where personalized CTAs and segment-based forms come in, and why routing the submission to the right rep fast matters as much as the page itself; see lead routing for website leads.
Demo Request Page Checklist
- The headline restates the outcome of the demo, not just "Contact us."
- Three bullets or fewer explain what the conversation covers.
- The first step asks for one to four fields; extra fields move to a second step or come from enrichment.
- Company size is a range picker, not a free-text field.
- Phone is optional unless you have tested that requiring it pays off.
- The page says what happens after submission and how quickly.
- Proof next to the form comes from companies similar to the visitor.
- Support and billing questions have their own route.
- There is an option for visitors not ready for a call (recorded or interactive demo, pricing page).
- Personal email domains are handled with a clear message, not a silent failure.
- The thank-you step offers a calendar or a clear next action, not just "We'll be in touch."
- If you send meeting reminders by text, the form has a separate, unticked SMS consent box (see our B2B SMS marketing guide for the wording).
For related page types, see our galleries of B2B homepage examples and SaaS pricing page examples. If you would like to talk to us about your own demo flow, our contact page has the details.
Frequently Asked Questions
What should a demo request page include?
A headline that states what the demo will show, a short list of what the conversation covers, a form with as few fields as your routing needs, proof from similar customers next to the form, a clear statement of what happens after submission, and a separate route for support questions.
How many fields should a demo request form have?
Ask only for what you need to route and prepare the call. Several examples here start with a single email field and collect the rest in later steps or through enrichment. Linear works with four. Long single-step forms, like Slack's and monday.com's, suit companies whose brand already carries the visitor through.
Should a demo form be one step or multi-step?
Multi-step usually works better when you need more than four fields, because the first step is easy and later steps feel like progress. Gong, HubSpot, Notion and Zendesk all start small. Keep the first step to one or two fields and put the most important routing question early.
Should you require a phone number on a demo form?
Only if your sales process genuinely depends on calling and you have tested it. A required phone field is one of the most common reasons for form drop-off. Make it optional, then compare completion rate and meeting rate between the two versions.
What is the difference between a demo request page and a demo landing page?
A demo landing page is built for a specific campaign or ad and usually has no navigation. A demo request page is the site-wide destination for "Book a demo" buttons and has to serve every visitor type. Our B2B landing page examples post covers the campaign version.