For teams that ship often

In-app guidance that keeps up with every release

Every release can break a tour and outdate a help article, and someone has to notice before users do. Skavelo re-learns your app on a schedule or after each deploy, rereads only what changed, and tells you what it couldn’t reach.

Start freeTry it on your own product before you add any code.

Why guidance goes stale

Tours point at elements

Rename a button or move a menu and a tour step can point at the wrong thing, or stop showing.

Articles drift

Screenshots and steps in help articles describe the product as it was when someone wrote them.

Nobody owns the upkeep

Fixing guidance after each release is everyone’s job, so it waits until a user complains.

How Skavelo helps

  • Re-learns after each deploy

    A step in your deploy pipeline calls the Skavelo API with an API key. Weekly or daily schedules work too.

    How self-learning works
  • Rereads only what changed

    Pages that haven’t changed are skipped, so a run after a deploy is quick and cheap to call every time.

  • Builds walkthroughs from the app as it is

    Walkthroughs are drafted from what it learned, and built for a question when none fits, from the screens as they are today.

    How walkthroughs work
  • Finds elements more than one way

    Each step is matched by its place in the page, its accessible name and its text. If nothing matches well, it won’t highlight the wrong thing.

  • Tells you what needs attention

    Each run lists screens it couldn’t reach, and the Monday summary names the walkthrough steps people stop at, often a button that moved.

    How insights work

What you can track

Each learning run shows what it opened on every screen and lists anything it couldn’t reach. The Monday summary includes those screens, along with walkthroughs people left early and the step most of them stopped at.

Runs started from your deploy pipeline are marked in the run history, so you can see which release they followed.

Questions

How do we re-learn after each deploy?
Create an API key in Skavelo and add a step to your deploy pipeline that calls the learning API. Unchanged pages are skipped, so it’s cheap to call on every deploy.
Which plans re-learn automatically?
Starter and above: weekly by default, daily if you choose, or after each deploy. On Free, you can re-learn once a month with Learn now.
What if a screen changes between runs?
Each step is matched by several signals, so small changes often still match. If nothing matches well, the step is shown without highlighting the wrong element, and the next run picks up the change.
Do we still need help docs?
They help. Skavelo learns from the screens, and docs, files and notes add what screens can’t show, like policies or why a setting exists.