Introduction
Tell us the task you want to solve and who will attend. We will plan the walkthrough around the parts that matter to you.
A demo request form asks a prospect what they want to see in a product walkthrough, so your team can prepare a focused session instead of a general tour. It needs to capture their goal, how they work today and who will attend, along with a time that suits everyone. The key judgement is to ask about the task to solve rather than the features they expect, because a demo built around a feature list rarely matches the decision the prospect is making.
Demo request form: 70 average monthly searches.Google Ads Keyword Planner · 2026-10-09 · United States
Tell us the task you want to solve and who will attend. We will plan the walkthrough around the parts that matter to you.
Thanks. Your request is in, and someone on our team will get back to you about a time.
One concrete task is enough. The details come up during the session.
Include anyone who makes the decision, and say whether they will join.
Choose the closest option. You do not need to name a contract or vendor.
| Field | Type | Required | Why you ask it |
|---|---|---|---|
You and your team | Section header | Identifies the people in the session before the questions about the work they need done. | |
Full name | Short text | Required | The name the team uses on the calendar invitation. Confirm the spelling before the session. |
Work email | Required | The calendar invitation and the session link go here. Check the domain against the company name, because a typo means the invitation never arrives. | |
Company | Short text | Required | Lets the team check the account and choose examples that fit the business, without starting from nothing. |
Your role in the decisionDecision-makerInfluencer or evaluatorEnd userOther | Dropdown | Required | Tells the presenter whether to focus on business outcomes, daily use or setup. |
The problem | Section header | Moves from the people to the work the demo should address. | |
What do you want to see?For example: how a weekly report is built from the tasks we already track. | Long text | Required | A concrete task tells the presenter what to show first. |
What do you use today?A spreadsheetAnother software productPaper or emailNothing yetI would rather describe it | Dropdown | Optional | Shows how far the prospect is from your product, so the session can explain the change rather than repeat the basics. |
Team size1 to 56 to 2021 to 100More than 100 | Dropdown | Optional | Sets which examples fit. A walkthrough for a five-person team looks different from one for a hundred. |
Number of other people attendingEnter 0 if it is only you. | Number | Optional | Tells the presenter how much to narrate and how much time to leave for questions. |
Preferred session windowMorning, before noonAfternoon, noon to 5 PMAnother time, I will explain | Single choice | Required | Offer only windows you can keep, since a missed session costs time on both sides. |
Your time zoneEasternCentralMountainPacificOutside the US | Dropdown | Required | Shows which clock to use for the session window, so the invitation lands at the right hour. |
Anything you must see before deciding? | Long text | Optional | Flags a must-have, such as an access question or a reporting need, so the presenter can prepare evidence instead of guessing. |
Example only, not a real submission
The scheduled job that handles new requests runs hourly in production. The creator receives the notification after that run, so allow for the wait when you offer session times.
Start the agenda with the task the prospect named, then list the people attending and their roles. Keep it to a few steps and leave time for the questions they listed.
Use the grid's CSV export to plan the week's sessions. Keep the export with the account record rather than in a shared folder that anyone can open.
The optional Customer Care setting opens a case for each request, which can hold a priority and an assignee. That keeps the demo and its follow-up questions with one named person.
A tour of every feature runs long and answers no particular question. Build the session around the task the prospect named, and skip features nobody asked about.
A confirmation that names a capability the presenter cannot show leads to an awkward call. Name only what the session will show, and check it before the invitation goes out.
A prospect moving from a spreadsheet needs a different session from one replacing another tool. The answer changes the demo, so read it before you plan the session.
Ask for the person's name and work email, the task they want to see, what they use today, the size of the team and the times they can attend. Keep budget and contract questions for the sales conversation, unless the demo genuinely depends on them.
Plan around the task the prospect named and leave room for questions. A short session that answers one clear need usually beats a long tour. State the planned length in the confirmation, so attendees can block the time.
The field list above can be copied into your form tool or a document. Adapt the windows and the role options to the people who actually run demos, and keep the prospect's own task at the top of the form.
Choose a category and a form type in the wizard. Answer three Atty Suggestions questions, then give the form a title. Atty builds the fields in the background. Edit the fields and ask Atty to refine them, then publish and share the /f/ link.