Can a guided demo teach an unfamiliar product before signup?
Building the six voices in The Room was hard. The problem I'm trying to solve now is different: helping someone understand what the product actually is before they create an account.
The Room is a structured multi-perspective discussion tool. You bring a topic, six AI voices develop it together, and they respond to each other instead of only to you. It's closer to a thinking environment than a chatbot.
The risk is simple: if the product doesn't click before signup, most people will never reach the part where it makes sense.
My hypothesis was that The Room can't be explained. It has to be demonstrated.
So I built a guided demo into the landing page: one question, six minds. Before signup, you watch a single question unfold through six distinct perspectives, one voice at a time, on a topic where the voices genuinely diverge. It ends with a CTA that takes you into the product, where the discussion is already waiting.
The thing I'm testing isn't the page. It's whether watching one discussion before signup is enough for someone to understand the product.
I think it works. I need 3 people to prove me wrong.
The flow: https://theroom.chat/, watch the demo, sign up with code IH-2026, and continue the discussion from inside the product.
The question I care about most: at what point did the product click for you? Before the demo, during it, after signing up, only after continuing inside the product, or not at all?
If something felt confusing or unnecessary, I'd especially like to hear that.
And after that first flow, did you want to start a second discussion on your own topic?
If you stop somewhere in the flow, that's as useful to me as finishing. I want to know where the product lost you.
There's an assumption here that I think is worth protecting: some products can't be understood through explanation alone.
The interesting question isn't whether the demo teaches the interface. It's whether it gives people the moment where they think, "I know exactly what I'd use this for." That's usually the point where curiosity turns into intent.
That's a much sharper way to frame it.
A demo can make the mechanics clear and still fail if it doesn't create that "I know what I'd use this for" moment. That's really the thing I'm trying to test, not just whether the interface is understandable.
Did you get a chance to watch the demo, or was this mainly a reaction to the framing? If you did watch it, I'd be curious whether a specific use case came to mind, or whether it still stayed abstract.
Mainly the framing.
Your question actually made me realize I'd want to explain the reasoning with your product in mind rather than in the abstract, and I don't think a public thread is the right place to do that.
If you're open to it, what's the best email to reach you on?
Thanks, I appreciate that. For this test I'm trying to keep feedback in the thread so I can understand where the demo does or doesn't make sense for people seeing it cold.
If there's one high-level thing you noticed about the product or the demo, feel free to share it here.
One high-level thing I noticed is that the demo seems to assume people have already identified a use case before they watch it.
I suspect the more important moment is when someone discovers a use case they hadn't considered until the demo showed it to them.
That's the distinction I'd keep testing.
Thanks, that's a fair distinction: whether the demo just explains the product or actually surfaces a use case someone hadn't considered. I'll keep that in mind.