In its current iteration this demo might net discourage your future clients rather than encourage them.

I like the idea in general as an alternative to needing to book with a BDE. I'd always prefer to just self serve for a new product; anything that gates my time (sales calls, popover walkthroughs, etc) is something I'd prefer to skip. But I know non-engineering customers really love these calls to see the power of a new platform. I wonder if they'll be as engaged during an AI walkthrough versus when there's a person on the other end of the phone.

finally, i kept asking it to show me whatever it needs to show me to get to the point and it was like "have a nice day" and ended the call LOL.

that said, it's impressive what is there.

congrats on the launch and i'll definitely be telling my new company (https://natural.co) about you guys!

I can use the scrub bar to skip around, make it faster or slower. An AI agent for this purpose is pretty close to a scripted demo and so this gives you sort of the worst of both worlds: it almost like a video but you can't skip around, it's almost like a demo but you are talking to a brainless robot.

I think your business model is probably in making it easier for people to generate demo videos. That would be more useful. I've created those, and it's challenging.

  > Don’t make your prospects wait–ever again
  > [...] where prospects receive personalized demos, in a video call, instantly.

  > We are preparing the demo for you...
  > Setting up your experience...
  > We are experiencing very high demand
  > Almost there...

I'm not super sure what architecture is in use that means that 16 minutes of being on the HN frontpage leaves it stalling out and unable to respond to requests after 60 seconds, but... it doesn't feel connected with the homepage messaging.

I absolutely appreciate (and have been subject to!) the HN traffic influx before, but for the nature of the product, when doing an _intentional_ Launch HN (not posted by someone else), it's fairly confidence-eroding to see the architecture fail to handle it in this way.

Really hoping that it's something transient and one-time that can be fixed – but surprised that there exist loading screens for this situation.