Should an advisory board demo be polished?

No -- this is the one context where polish is counterproductive. People give soft feedback on things that look finished, because criticising finished work feels rude. A visibly rough demo with "nothing here is decided" gets a different quality of response.

What questions should you ask an advisory board?

"Where would this fit in your week?", "what would you still do outside this?" and "who else would have to agree?" -- not "what do you think?" or "is this better?", which people answer politely.

How do you keep an advisory board engaged?

Send a follow-up demo showing what changed because of what they said. People give good feedback to someone who visibly uses it, and stop giving it to someone who does not.

← Back to blog

Demos for a Customer Advisory Board

August 23, 2026

A customer advisory board is a small group of people you trust to tell you what is wrong before you ship it to everyone. That only works if they believe the decision is still open.

Which makes production value actively counterproductive here — the one context in this blog where that is true.

Show it unfinished, and say so

People give soft feedback on things that look done, because criticising finished work feels rude and pointless. The same person will be genuinely useful about something visibly in progress.

A rough demo with a caption saying "nothing here is decided" gets a different quality of response from the same room, on the same design.

Ask about their work, not your interface

"Where would this fit in your week?" rather than "what do you think?"
"What would you still do outside this?" — the gaps are the finding.
"Who else would have to agree?" which surfaces buying reality, not just usability.
Not "is this better than the old one?", which people answer politely.

Send it before the call

An hour on a call spent watching someone screen-share is an hour not spent on discussion. A demo link sent two days ahead means the meeting starts with reactions rather than exposition.

It also gets you the reaction of the people who cannot make the call, which in a small advisory group is often half of them.

Close the loop, visibly

The fastest way to kill an advisory board is to collect feedback and never show what happened to it. A follow-up demo showing what changed because of what they said is the single strongest thing you can send that group.

It is also why the board keeps answering: people give good feedback to someone who visibly uses it, and stop giving it to someone who does not.

Frequently asked questions

Should an advisory board demo be polished?: No -- this is the one context where polish is counterproductive. People give soft feedback on things that look finished, because criticising finished work feels rude. A visibly rough demo with "nothing here is decided" gets a different quality of response.
What questions should you ask an advisory board?: "Where would this fit in your week?", "what would you still do outside this?" and "who else would have to agree?" -- not "what do you think?" or "is this better?", which people answer politely.
How do you keep an advisory board engaged?: Send a follow-up demo showing what changed because of what they said. People give good feedback to someone who visibly uses it, and stop giving it to someone who does not.

Keep reading

This is what Demorta does

Click through it — the same kind of demo you can record of your own product.

Try it on your own product

Record your first interactive demo free.

Five demos on the free plan, forever. No credit card, no trial countdown, no sales call. Install the Chrome extension, click through your product once, and you have a shareable link in about ten minutes.

Start free →