Before booking a software demo, buyers want to know whether the product fits closely enough to justify an hour of their team's time: what it will cost at their size, whether it connects to the systems they run, what their security and procurement reviews will ask for, and how much work rollout takes. Many also want to know who the product is not built for. Pages that answer those questions in public let buyers arrive at the demo with sharper questions, and they give an assistant something specific to work with when a buyer asks it first.
A demo request costs the buyer something. It means a calendar slot, a form that routes to sales, and often a follow-up sequence they did not ask for. Buyers who can find answers elsewhere tend to do that research before they spend the hour, which means the questions do not disappear when the website skips them. They move to a colleague, a review site, or an assistant.
This is a content-planning question for software marketing and sales teams. It is not legal, accessibility, or procurement advice, and your own counsel and compliance staff decide what your documents may say.
The questions that decide whether a demo gets booked
Different people on the buying side carry different questions, and most of them can be answered in writing before anyone books a call. The table below separates what a public page can settle from what still needs a conversation.
| Question | Usually asked by | What a public page can settle | What still needs a call |
|---|---|---|---|
| Will this work for a team our size? | The person who found the product | Seat ranges per plan and the team sizes the product is built for | Edge cases in their org structure |
| What will year one cost us? | Finance approver | How the bill is calculated and what triggers the next tier | Their final quote |
| Does it connect to what we already run? | System administrator | Which integrations exist, what syncs, and on which plans | Custom fields and unusual setups |
| What will security review ask for? | Security reviewer | Which reports and agreements exist and how to request them | The documents themselves, under the vendor's terms |
| Is it accessible to our staff? | Procurement | Whether a current accessibility conformance report exists | Specific accommodations |
| What happens to our data if we leave? | Administrator or legal | Export formats and the offboarding steps | Contract terms |
The cost and security rows each deserve their own page. See how pricing pages should explain plans and limits and how security and compliance pages should be written.
Answer in writing what every demo repeats
Many solutions engineers spend the opening of each demo on the same ground: what the product is, which plan includes what, how data gets in. A buyer who has to sit through that to learn whether single sign-on is included has paid for information the website could have given away. That is time the buyer does not get back. The better use of the hour is the buyer's own workflow, shown on their own kind of data.
The fastest way to find the gap is to ask the people running demos. A useful prompt for the next team meeting: "What do we explain in the first ten minutes of every demo that a prospect could have read the night before?" Write those answers down, have the product owner confirm them, and publish them on the pages buyers read before the form. Keep the demo form short, too; asking for budget and timeline before the buyer has seen a price explanation tells them the conversation runs one way.
Accessibility documentation buyers request
Some procurement teams ask whether a product has an Accessibility Conformance Report before they will schedule an evaluation. The Information Technology Industry Council publishes the VPAT, which it describes as a free template that translates accessibility requirements into tests for products, and its page explains that once the template is completed with documented testing results it is referred to as an Accessibility Conformance Report. In its VPAT 2.5Rev release (April 2025), ITI offers editions aligned with the Revised Section 508 Standards (the U.S. federal accessibility standard), with EN 301 549 (the European standard for public procurement of ICT), and with the W3C's Web Content Accessibility Guidelines, plus an international edition combining all three. ITI's page also notes that the manufacturer or vendor declares the degree of conformance.
For the website, that means naming the edition, the product version tested, and the date, and saying how a buyer requests the report. A published report is not a passing grade. WCAG 2.2, in the W3C Recommendation dated December 12, 2024, defines "three levels of conformance": A, AA, and AAA. A phrase like "fully accessible" or "WCAG compliant" on a marketing page can say more than the report behind it supports, so match the page to what the report actually states, and have whoever owns accessibility approve the wording.
A fictional pre-demo page
Consider a fictional field inspection app, based in Minnesota, sold to county governments and utilities. Its demo requests kept stalling after the first call because procurement needed an accessibility report, the security team needed a questionnaire answered, and finance needed a price for 60 inspectors before anyone could approve a second meeting. The company publishes a "before your demo" page listing what the demo will cover, the plan that fits teams of 20 to 100 field staff, the documents available on request (with the date each was last updated), and the integrations most county buyers ask about. None of that needed new research. The sales engineers had answered each question dozens of times, so the writer should not have to make up seat ranges or a list of available documents; the engineers supply both and product signs off.
The page does not try to replace the demo. It gives each person on the buying side one place to check their part before the hour is booked, and it gives the sales team a link to send when a prospect asks a question the page already answers. A method for pulling these questions out of call notes and support tickets is in our guide to unanswered buyer questions.
How the four steps apply to demo questions
Hudson South's method runs in one order. Authority Asset collects the approved answers: plan details, documentation, the security and accessibility documents you are prepared to reference, and the explanations your sales engineers give. Hudson Twenty-One documents how your team speaks and writes across 21 dimensions, so a pre-demo page sounds like the people the buyer will meet on the call. Market Intelligence researches the questions buyers in your category ask before they reach out, and which of them competing vendors already answer. AEO Creation turns those inputs into pages that answer first and state their conditions. For the full set of pages a product site needs, see the software and SaaS industry overview.
Find the questions your demos keep repeating
Bring the three questions your sales engineers answer on every first call. We will set them beside what your competitors publish during a free 30-minute call.
Get your free competitor analysisSources
- VPAT. Information Technology Industry Council. Read 2026-10-16.
- Web Content Accessibility Guidelines (WCAG) 2.2. World Wide Web Consortium. Read 2026-10-16.