# How to read a demo

Guide, 8 Nov 2026, read 8 Nov 2026

**The short answer.** A demo has three layers: what was said, what was shown on vendor data, and what was done on yours. Only the third layer is evidence. Read a demo by counting the minutes spent in each layer, the number of times the engineer left the product for a slide, and the questions that were answered with a follow-up.

## The three layers

The first layer is the narrative: the market, the roadmap, the customer logos. It takes fifteen minutes of a sixty-minute demo on average and proves nothing. The second layer is the product on the vendor's demo company, which proves the feature exists. The third layer is the product on your file, which proves the feature works for a company shaped like yours. Set a timer and record the minutes in each layer; a demo that spends forty minutes in the third layer is a bake-off, and a demo that spends forty minutes in the first is a pitch.

## Six tells

- 'Let me show you a slide on that' means the feature is not in the build the engineer has.
- 'We can configure that' means a professional services line. Ask the price before the call ends.
- 'That's on the roadmap' is scored as none found on this site, and should be in yours.
- 'Most customers don't need that' is an answer to a question nobody asked.
- A demo company with one entity and one country cannot show a per-office policy. Ask for a second entity to be added live.
- An engineer who types a sentence and gets a report has shown the build criterion. An engineer who opens a report builder and clicks for four minutes has shown the old product.

## What to write down

For each of the fifteen Demo Script questions, write the layer in which it was answered and the elapsed time. Then write the one sentence the engineer said that the vendor's website does not say; that sentence is either a fact the site has not caught up with or a claim to verify. On this site a vendor claim stands alone when it is labeled as one and caps the criterion at 7; your notes should apply the same rule.

Two demos read this way produce a table, and a table is a bout. The Scorecard on this site shows what the published pages say about the same pair; the bake-off guide shows how to score the demos; where the two disagree is where your company differs from the weights.

## Sources

- Shapes Vibe Views: https://shapes.co/vibe-views (read 8 Nov 2026)
- Rippling AI reports from a prompt: https://www.rippling.com/platform/ai (read 8 Nov 2026)
- Workday Launch deployment: https://www.workday.com/en-us/customer-experience/deployment.html (read 8 Nov 2026)

Last reviewed 8 Nov 2026. Canonical: https://hriscomparison.com/guides/how-to-read-a-demo/
