Show them where to click#

A user opens your admin screen. Eighteen columns. Four menus. A button hiding behind a dropdown inside a collapsed row. They know what they want to do. They cannot find the door.

Click Guide puts a help layer over your product. It answers questions from your own documentation, and when the answer is a task, it highlights the exact control and waits while your user clicks it.

One script tag. One key. No redeploy.

Try it right here#

This is a pretend admin screen. The overlay below it is the real thing: same resolver, same masked spotlight, same rule that it points and you click.

The help was always there#

Your product already explains itself. The field labels, the validation messages, the empty states, the guide your support lead wrote last March. All of it sits in different places, and none of it reaches the person staring at the screen right now.

Click Guide gathers that material and puts it one keystroke away. A user asks a question in their own words. The overlay searches what you approved, answers in two sentences, and shows the source it used. If it does not have the evidence, it says so. An honest "I do not know" beats a confident wrong answer every time.

Three things happen#

You install it. A script tag and a publishable key. The loader runs after your page renders, so nothing you shipped gets slower.

You record a guide. Open your own application, click through the task once, and write the copy. No JSON. No CSS selectors. No developer.

Your user follows it. The screen dims. One control stays lit. A short instruction sits beside it. They click, the guide advances, and they finish the job they came to do.

What it will not do#

Click Guide never clicks for your user. It does not submit forms, buy things, delete records, or change permissions. It points, and your user decides.

That line is not caution. It is the product. An overlay that acts on someone's behalf inside a system holding their payroll, their stock, or their customers is a liability wearing a helpful face. Click Guide highlights the button. The human presses it.

The same discipline runs underneath. The overlay never reads passwords, never captures payment fields, and never stores the contents of your page. It learns where your controls are, not what your users typed into them.

Built for the products people actually run#

Not every application is a fresh single-page app with clean data attributes. Most are server-rendered, ten years old, and carry a table with duplicate ids on every row.

Click Guide was tested against one of those first. It finds controls by what a person sees on screen, not by a generated CSS path that breaks the next time somebody sorts a column. When a target goes missing it stops and reports which one, rather than stranding your user mid-task.

Your guides survive your next release. That is the whole job.

Click Guide is in development. See how it works, or read the install contract for the shape of the integration.