A demo request form covers contact details plus the demo requirements, data access needs, roles and approvals to show, and expected budget and timeline.
Someone asks for a demo because they need proof before they commit, and the risky part is the first call where requirements get skipped and the demo turns into theatre. The Demo Request Form collects the details that usually decide whether a demo will hold up under real questions, in an indigo and fired-tile layout under Syne headings and Inter body text.
The opening note explains what happens after submission, then the questions move from basic contact info into Demo details about what the demo has to prove. The form pins down whether the request is for a live production product or a prototype, what you’ll need to demo on their data, which roles and approval flows have to show up, and the expected timeline and monthly budget if the next step is a build.
- Demo Request Form A short intro that sets expectations for what happens after the request comes in and what the requester should include.
- Contact details Name and email are required, and phone number is optional, so you know where to send next steps.
- Demo details The written prompt frames what the demo must show and what you can use to run it.
- Product status A required choice captures whether the demo is for a production product with live data or a prototype or mock.
- Requirements to prove Three required questions cover data needs, roles and approval flows, plus an optional timeline and monthly budget for what happens after the demo.
Once the form is in Plutio, answers land as responses you can review and reply to, leaving the follow-up call focused on evidence instead of backfilling basics.
We went from spending hours on every proposal to creating fully customized ones in under 5 minutes. That's not an exaggeration - we timed it.
What to include in a demo request form
| Part | What it covers |
|---|
Demo Request Form | A short written intro that explains what the form is for and what happens after submission. |
Your name | A required name field so the follow-up message has the right contact. |
Email address | A required email field for sending next steps and questions. |
Phone number | An optional phone field in case the demo needs a call-back. |
Demo details | A written prompt that asks what the demo must show and what materials you can use. |
Is this a production product or a prototype? | A required choice between production product and prototype or mock to set expectations for what can be shown. |
What do I need from you to demo on your data? | A required text answer that captures access, exports, sample data, or anything else needed to run the demo on their side. |
Which roles and approval flows must the demo show? | A required text answer that spells out permissions, handoffs, and approvals the demo should include. |
If we proceed, what timeline and monthly budget do you expect? | An optional text answer that records the requester’s expectations if the conversation moves past the demo. |
Who it is for
SaaS and product teams, b2b saas vendors, and developer tools or marketplace platforms that need a demo request to capture data, roles, and constraints up front.
The form in full
Demo Request Form
Use this form to request a demo for a SaaS product build. I will review your answers and reply with the next steps and any items I need.
- Your name (required)
- Email address (required)
- Phone number
Demo details
Tell me what the demo must show and what I can use.
- Is this a production product or a prototype? (required)
- Production product (live data)
- Prototype or mock (not final)
- What do I need from you to demo on your data? (required)
- Which roles and approval flows must the demo show? (required)
- If we proceed, what timeline and monthly budget do you expect?
