Skip to content
Add to Chrome, freeGet ClickableEmail me the link

Product

Accelerate onboarding across every web application

Why learning new work software costs more than it looks, why recorded walkthroughs go stale, and how live step-by-step guidance helps people on any web app.

Clickable on an example expense app: a blue ring around the New report button, with Clicky the pointer beside it, and the side panel saying Click New report.
An illustration on an example expense app, not a real product. You make every click.

Key points

  • Most "how do I…?" questions end up as an interruption, a ticket, an outdated wiki page or a guess.
  • Recorded walkthroughs describe yesterday's screens. Live guidance reads the screen in front of the person.
  • A short pilot with a before-and-after ticket count shows whether it works for your team.

New software usually arrives with a launch email, a training session and a wiki page. Then the real questions start: where is the button, which option is right, why did the form not save. This post looks at where those questions go today, why recorded walkthroughs only partly solve them, and what live, step-by-step guidance changes.

Why software onboarding costs more than it looks

A question about a button rarely gets logged as a cost. It shows up as a colleague interrupted, a ticket in a queue, time spent searching a wiki, or a mistake fixed later.

Four cards showing where a how-do-I question goes today: asking a colleague interrupts two people, a ticket waits in a queue, the wiki shows outdated screens, and guessing leads to rework.
Each route has a cost, even when nobody counts it.

These costs grow with every new tool and every new hire. They are highest in the tools people use only now and then, such as expense reports, time-off requests and procurement forms, because nobody remembers the steps between one use and the next.

Why recorded walkthroughs go stale

Digital adoption tools let a team record a walkthrough of each process and replay it as an overlay. That helps, but someone has to record every process, and every update to the software can break the steps.

Two flows side by side. Recorded walkthrough: someone records each process, it is published, the software updates its screens, the steps break and must be recorded again. Live guidance: the employee says what they need, Clicky reads the page as it is now, highlights the next step, and nothing needs updating when the screens change.
A recorded guide describes the screen on the day it was made.

What live, step-by-step guidance looks like

With Clickable, the employee opens the side panel in Chrome and says what they need in their own words, for example “submit my Lyon expenses”. Clicky reads the page, rings the next thing to click and explains it in one short line. When the page changes, it looks again.

It asks instead of guessing

Many work tools offer options with almost the same name. When the right choice depends on the person’s situation, Clicky asks a short question first.

Clickable on an example expense app: the panel asks whether the trip was by train or plane or by the person's own car, with two answer buttons and a box to type a different answer.
Illustration on an example app: Clicky asks before choosing between two similar options.

It recovers when a suggestion is wrong

If Clicky points at the wrong thing, the employee presses Not this. The step is marked as skipped and Clicky looks for a better match on the same page.

Clickable on an example expense report: the panel lists done steps and one skipped step, Add line, and now rings Attach receipt with a short reason.
Illustration: after Not this, Clicky skips that suggestion and rings the right button.

The employee finishes the task themselves

Every click, every value typed and every submission is the employee’s. Clicky never acts for them, which matters most in finance, HR and other tools where a wrong click has consequences.

An example expense app confirming the report was submitted for approval, and the Clickable panel saying Done.
Illustration: the employee submits the report; Clicky confirms the task is done.

How the options compare

Training sessions, recorded walkthroughs and live guidance each have a place. The difference is how much content they need and how well they keep up with changing screens.

A comparison table of training sessions, recorded walkthrough tools and Clickable across content to create, what happens when screens change, help at the moment of need, who clicks, and central reporting, which Clickable doesn't offer yet.
Clickable needs no content, but it has no central reporting yet.

What it reads, and what it never sends

IT and security teams usually ask this first. Clickable reads a page only when someone asks for help, and only what it needs to find the next step.

Two cards. Reads: the page address and title, up to 15 headings, buttons, links and labels with their state, and a visible-text excerpt of at most 1,500 characters. Never sends: what people type, passwords, email bodies, chat boxes and code editors, and sign-in pages, where it pauses.
The full details are in the privacy policy.

The privacy policy lists the providers and retention periods, and the rollout guide explains what IT can and can’t control.

How to run a pilot that proves the savings

The honest way to know whether it saves time is to measure it on one team. Count first, then compare.

A six-week pilot in four steps: weeks 1 to 2 count the how-do-I tickets for one team; week 3 IT installs Clickable; weeks 3 to 6 people ask Clicky first while tickets are still counted; week 7 compare before and after.
Use your own help desk's numbers, counted the same way before and after.

Where to start

About Clickable

Clickable is a free Chrome extension that shows people where to click on any website, one step at a time. You ask in your own words and Clicky highlights the next thing to click. You make every click yourself: Clickable never clicks, types or pays for you.

Questions about this news

Do we need to create any content before people can use it?

No. Clickable reads the page someone is on when they ask for help, so there are no walkthroughs to record or keep up to date.

Does it work on our internal tools?

It works on most web applications in Chrome, including internal ones. It doesn't yet read content inside embedded frames, so a few apps work only partly.

Can it do the task for employees?

No. Clickable highlights the next step and the employee makes every click. It never types, submits or approves anything.

How do we roll it out?

IT can install it for a whole team with Chrome's admin policies, and each person signs in once. The rollout guide has the steps.

Stuck on a website? Let Clicky show you.

Type what you want to do and Clicky highlights each step. You make every click.

Add to Chrome, it’s freeEmail me the link

Get Clickable

Clickable works in Chrome on a computer. Leave your email and we’ll send you the link to add it there.

Who
King Jensen Perez, who runs Clickable.
Why
To email you the install link (or reply about a call) and, only if you tick the box, occasional news.
Legal basis
Your request; your consent for the news.
Shared with
Our email provider, Resend. Never sold.
Your rights
Access, correct or delete your data, and withdraw consent, at any time.

More in our privacy policy.