Skip to main content

Buyer workspace · this week · ranked by community votes

Sign in
List your SaaS

Questions to Ask in a SaaS Demo

Evaluating · 10 min read ·

A demo shows a tool at its best. These questions and exercises make it show what you need to see: your data, your workflow, its limits and its failures.

Illustration: An indigo scoring sheet with a compact grid: rows for Scenario steps, columns for Vendor A, B, C and a Notes column, small circles for scores

A good demo is a pleasure to watch. The presenter is fluent, the data is tidy, every click lands where it should and the product looks like the answer to everything. You leave with a warm feeling and a vague list of things to check.

The warm feeling is not an evaluation. A demo is designed to show a product at its best, and your job is to find out what it is like at its ordinary. This guide gives you questions, exercises and habits that turn a sales presentation into evidence you can use.

Prepare before the call

The best demos are won beforehand.

Share your requirements. Send the vendor your ranked list of must-haves and ask them to address those. If you have not written one, do so first. A requirements list is the foundation of a fair evaluation.

Write a scenario. Describe a typical piece of work in your team, step by step. "A new request arrives by form, is assigned to an owner, receives two comments, changes status and appears in the monthly summary." Ask the vendor to walk through exactly that.

Prepare sample data. Bring a small, realistic, anonymised sample, with awkward cases: a long name, a missing field, a duplicate. Do not use real personal data.

Choose attendees. A daily user to judge usability, an administrator to judge set-up, someone for security and data, a decision-maker and a note-taker.

Agree the length and shape. Tell the vendor you want most of the time on your scenario and room for questions.

Prepare a scoring sheet. Rows for your requirements, columns for each vendor, a simple scale and a notes box. Use the same sheet for every demo.

During the demo: control the pace

Politely take control of the session.

  • Let them introduce, briefly. Then say: "Could we move to our scenario?"
  • Ask to see, not hear. "Please show us that, rather than describe it."
  • Ask for the real product, not slides, a mock-up or a special demo environment. If it is a demo environment, ask what differs from production.
  • Ask to use our sample data. See how it handles messy input.
  • Ask for a user, not the presenter, to drive, at least for part of it. Watching your own team try it reveals usability better than watching an expert.
  • Take notes of what was shown and what was only claimed.

Questions about your workflow

Start with the work.

  • Can you show the first step of our scenario, from a blank account?
  • How many clicks and screens does that take?
  • What happens when someone makes a mistake? Can they undo it?
  • How do we handle exceptions, such as a request that changes owner midway?
  • Can we adjust fields, statuses and rules without help from you?
  • What can end users do without an administrator?
  • What happens on a phone?
  • How does it look for someone using only a keyboard or a screen reader? Ask for evidence of accessibility, such as how the product relates to the Web Content Accessibility Guidelines, rather than a bare assurance.

Questions about data

  • What data does the tool hold, and can we limit it?
  • Can we import our existing data? Show us with our sample.
  • What fields can we add?
  • How does it handle duplicates?
  • Can we export everything, in what format? Show us now.
  • Can we delete data completely, and how do we confirm it?
  • Where is data stored?

Questions about administration

  • How do we add and remove users?
  • How do roles and permissions work? Can we restrict who sees what?
  • What audit trail exists? Who did what, when?
  • How do we handle a person leaving?
  • How do we set up single sign-on?
  • What reports can administrators see?
  • How long does set-up usually take for a team our size, and what do customers usually find hardest?

Questions about security and reliability

Draw on recognised guidance. The UK National Cyber Security Centre's cloud security principles can structure your questions, including how data is protected, how customers are separated, how access to your data by the vendor's staff is controlled, how identity is handled and what auditing is available.

  • How is our data protected, and who can access it at your end?
  • What independent assessments exist, and when were they last done?
  • What happened in your last significant incident, and how did you handle it?
  • What is your uptime record, and where can we see it?
  • What are your backup and recovery times?
  • How do you tell customers about problems?

Ask for documents, not just answers.

Questions about limits

Every product has limits. Ask for them directly.

  • What can this tool not do?
  • What do customers most often ask for that you do not provide?
  • Which features are new or in beta?
  • What are the limits on records, storage, users, API calls or file sizes?
  • What slows down at scale?
  • What do customers complain about?
  • Is there anything on your roadmap that we should not rely on?

A vendor who answers frankly is a better partner than one who insists there are no limits.

Questions about integration

  • Which tools do you connect to natively? Show us one.
  • Is there an API? What can it do, and what are its limits?
  • How do webhooks or automations work?
  • What happens when a connected system changes?
  • Who maintains the integrations?

Questions about price and terms

Pricing is where demos often get vague. Be specific.

  • What is the price for our team size and use, in writing?
  • What is included, and what costs extra?
  • What counts as a user? Are there free or read-only users?
  • How are prices set for next year, and what notice do you give of increases?
  • What do implementation, training and support cost?
  • What is the minimum term? How do renewals work?
  • What happens if we want to reduce seats?
  • What is the total cost over three years, including everything?

Total cost of ownership, the purchase price plus the other costs of owning and operating something, is the number that matters, not the headline price.

Do not accept verbal answers. Ask for a written quote and compare it with the vendor's pricing page.

Questions about support and success

  • What support is included, and what hours?
  • What are your response targets by severity?
  • Who will be our contact?
  • What training is available?
  • How do you handle feature requests?
  • Can we speak to a customer like us?

Watch for warning signs

Be cautious when you see:

  • Slides instead of the product.
  • Refusal to use your scenario or data.
  • Evasive or generic answers.
  • A tool that only works with perfect data.
  • "That's on the roadmap" for core requirements.
  • Pressure to sign quickly, with a deadline that conveniently ends soon.
  • Reluctance to share documents or references.
  • Inconsistent answers between people.
  • Vague claims such as "bank-grade security" with no detail.

None is proof of a bad product. Together they suggest caution.

Score straight afterwards

Within an hour of the session, with the team still together, fill in the scoring sheet.

  • Score each requirement: met, partly met, not met, not shown.
  • Record who said it, and what was actually demonstrated.
  • Note usability impressions from the person who drove.
  • List follow-up questions and who will ask.
  • Rate your overall confidence.

Scores recorded later are coloured by memory and by the last thing the vendor said.

Follow up in writing

Send the vendor a short email.

  • Thank them.
  • List the questions they did not answer or only claimed.
  • Request the documents promised.
  • Ask for a written quote and draft terms.
  • State your timeline.

Their quality and speed of response is itself evidence.

Compare fairly

When you have seen several vendors:

  • Put the sheets side by side.
  • Compare against the requirements, not against the best demo you saw.
  • Discount anything not demonstrated.
  • Weigh usability feedback from real users.
  • Mark deal-breakers.
  • Shortlist two for a pilot, not one.

A pilot, with real users and real work, is the next step, and it is where demo promises meet reality.

After the demo

Resist the urge to decide on the glow. Wait a day. Read the scores. Talk to the users. If you remain unsure, ask for a trial.

On this site

The categories and search pages help you find products to demo, the launches page shows new entrants and the submit page is where vendors list theirs. The blog has further guides for buyers and teams.

A short worked example

A team of eight books demos with three vendors for a request-tracking tool. Beforehand they send each vendor the same six must-haves and a scenario with five steps, plus ten anonymised sample requests, one with a very long title and one with a missing field. In the first demo, the vendor refuses to use the sample data and shows slides for twenty minutes. In the second, the vendor follows the scenario but the long title breaks the layout, which the vendor acknowledges and explains. In the third, the presenter lets a team member drive and the tool handles the awkward data well, though single sign-on is shown only as a slide.

Scored the same afternoon, the second and third vendors go forward to a pilot, with a written follow-up asking for the single sign-on evidence. The first is dropped, not because its product was bad but because it would not show the team what they needed to see. The method did what it was designed to do: it made the vendors compete on the buyer's terms.

The short version

Prepare a scenario, sample data, a requirements list and a scoring sheet, then take control of the demo: ask to see, not hear, and have a real user drive. Ask about workflow, data, administration, security, limits, integration, price and support, press for written answers and watch for slides, evasion and pressure. Score straight afterwards, follow up in writing and compare against your requirements. A demo shows the best day; your questions find the ordinary one.

Questions and answers

How do I get more than a sales presentation from a demo?
Send your requirements and a sample scenario beforehand, ask the vendor to follow it with your data, and ask to see failures as well as successes.
Who should attend the demo?
A daily user, an administrator, someone who handles security or data, and the decision-maker, with one person taking notes.
What should I ask about pricing?
What is included, what costs extra, how prices can change, what counts as a user and what happens at renewal.
How do I compare several demos fairly?
Use the same script and the same scoring sheet for each, and score straight after each session.
What should make me cautious?
Evasive answers, features shown only as slides, refusal to use your scenario and pressure to sign quickly.

Sources

Related guides

Need help?