A teacher inside your product.
Guidr learns how your software works, then guides users through it on their screen, step by step. They do the work themselves, instead of reading docs or watching videos.
A customer asks how to set up a project. Guidr's pointer moves to the project template field, explains which template to choose, and waits while the customer does it.
Every “quick question” interrupts someone building your product.
A customer gets stuck. They message your team. Someone explains the same workflow they explained yesterday. Your docs may have the answer, but the customer needs help with the screen in front of them, right now.
“Where do I start?”
“Which template do I choose?”
“What happens after I submit this?”
Show Guidr how your product works.
Bring the workflows and documentation your users need. Guidr learns your product's steps and terminology, not just the labels on its buttons.
Your users ask where they are.
They ask in their own words, by voice or text. Guidr responds while pointing to the relevant part of their screen. It explains the step, then lets them do it.
See which tasks still need help.
Look at group-level patterns to find confusing workflows. Improve the product and the guidance without tracking individual performance.
See Guidr guide a task, start to finish.
A completed task is good. A user who can do it again is better.
A tooltip can get someone through a screen. Guidr explains what they are doing and why, then gives them space to do it themselves.
The guidance gets lighter as they learn. After the second time, Guidr stops explaining unless asked.
The goal is confidence, not dependence.
First time
Second time
Third time
Your product has its own logic.
A generic answer can define a button. It cannot explain why a particular choice matters in your workflow. Guidr learns the context you give it and uses that context while helping a user.
Your product changes.
Hand-built walkthroughs need updating when screens move. Guidr reads the screen in front of the user, so guidance does not depend on a fixed trail of highlighted clicks.
Find the friction. Don't watch the person.
See which tasks people need help completing and where your guidance needs work. Guidr shows group-level totals, not a list of individual users.
Small groups are not displayed. You see what needs improving, without watching the person doing the work.
Start with the task your users keep asking about.
Pick one workflow in your product and the outcome you want to improve. We'll learn it with you, run a focused two-week pilot, and look at whether users can get through it with less help from your team.
Questions
No. Guidr points and explains; your users do the clicking.
No. Bring what you have and tell us which task matters. We can start with a short call.
No. They can type instead.
Yes. Arabic and English, including switching between them mid-sentence.
No. Reporting is at the group level; Guidr does not show individual performance. Groups of fewer than ten people are not displayed.
Guidr captures the screen only when a user invokes it, not continuously. We don't store screenshots or recordings. Our AI providers process them under zero-retention terms.