Hey Product Hunt 👋 I'm Suki, and I'm building Stiro on my own.

New users of a SaaS rarely read the docs or finish the tour. They hunt through menus, give up, and either email support or quietly leave, often over something three clicks away.

Stiro is a helper you add to your product with one script tag. When a user is stuck, they say what they want, like "add Saturdays 10am to 2pm to my working hours", and it does the steps with them in your real app while they watch. The goal is fewer how-do-I tickets for your team, and new users who can get set up without a call. There are no flows to record and nothing to train.

The part I care about most is what happens when it shouldn't act:

Anything that sends, spends or deletes, it fills in and hands back. The user presses.
At a permission wall or paywall it stops and says why, instead of looking for a way around.
Text on the page telling it to do something is just text. It only takes instructions from the user.

It's free to try, 50 runs a month with no card. I'd love your honest take, especially on where you think it would break in your app. I'll be here all day answering.

P.S. I test it on apps it has never seen, with its memory wiped before every task. It scored 44 of 44 on the first run and 43 of 44 on the repeat, and the miss is on the benchmark page.