In this article: a Beyond the Lab episode featuring Niccolò Palazzoni answering the deceptively simple question - what actually counts as a product demo - and walking through the three tests we use at USP Solutions.
“What is a demo?” sounds like a basic question until you try to answer it for a roomful of marketing and R&D leaders, every one of whom has a different definition. In this Beyond the Lab episode, Niccolò Palazzoni offers a working answer that we use across our briefs.
The three-test definition
For Niccolò, something is a demo only if it passes three tests at once. First, it must visualise a real product property not a metaphor, not an animation, but the actual mechanism or outcome. Second, it must be repeatable: the same input has to produce the same visible result, every time, with whoever is running it. Third, it must be communicable in seconds: a stranger should understand what they are looking at without a script.
Why the definition matters
Brands often label sampling, free gifts or animated explainer videos as “demos” in their marketing decks. None of those pass the three tests. Calling them demos creates internal confusion about what success looks like and weakens the case for investing in real demo development. Tightening the definition tightens the brief.
How we apply this in client work
Every USP Solutions engagement starts with mapping a candidate demo against the three tests. If a concept fails on any of them the property is invisible, the output varies, or the story takes too long to land we either redesign it or recommend a different communication tool. That filter is one of the reasons our hit rate at retail is high.
For more on the cognitive mechanisms that decide whether a shopper believes a demo, read our piece on the psychology of consumer belief in product demos.
How to use this definition internally
The practical value of a tight definition is that it gives your teams a shared filter for deciding what counts as a demo and what does not. The next time someone in the business proposes a "demo", run it through three checks: does it isolate a single claim, can a consumer see the mechanism without a voiceover explaining it, and is the result the same across operators and environments? Anything that fails one of those checks is a piece of brand content, not a demo, and should be briefed and budgeted as such.
Once the definition is shared, it becomes much easier to plan a demo portfolio rather than a pile of one-off assets. Map your active claims against the demos that prove them, and the gaps in the grid become your next brief. This is how categories that take demos seriously, oral care and laundry are the obvious examples, end up with a small, durable set of recognisable proof points that quietly do the heavy lifting across every campaign.
One last habit worth adopting: name a demo owner inside the brand team. Without a clear owner, demos tend to drift, the protocol changes slightly between markets, the props get rebuilt by different suppliers, and within two years the same demo means different things in different rooms. A single internal owner who guards the protocol, signs off on every adaptation, and keeps a master version of the asset is the cheapest insurance a brand can buy against that drift.
The other useful discipline is to test the definition by trying to break it. Walk a sceptical colleague through the demo and ask them to argue that it does not isolate a single claim, or that the mechanism is not visible, or that the result depends on the operator. If the definition survives that scrutiny, the demo is ready to leave the building. If it does not, the failure surfaces in a meeting room rather than in front of a regulator or a journalist, which is the only place that conversation should ever happen.