Try Clew
Product tours and popups you test without a developer
Start new thread

Try Clew - Product tours and popups you test without a developer

by•
Clew adds product tours, tooltips, popups, onboarding checklists and two-step rating popups to your web app. Paste one script once, then build on your live UI in a visual editor. Target by page, trigger and user properties; A/B test any tour and see if the lift is significant before making B the main version. Health checks flag steps whose element is gone. On Pro, an MCP server lets Claude, Cursor or Codex build tours for you. EU cloud or self-hosted, free plan.

Add a comment

Replies

Best
Hunter
📌

Hi Product Hunt! I'm Andrey, the maker of Clew.

I build and work as CPO at salesei.ai, and both products needed the same layer on top of the interface: walk a new user to the first action, point out a new feature, ask a quick question. Every time it became a ticket for a developer and waited for the next release. Onboarding copy shouldn't need a deploy.

So Clew is one script tag. After that the product person opens the live site, clicks the element they mean in a visual editor, writes the text and publishes. Formats: step-by-step tours, single tooltips, modals, onboarding checklists and a two-step rating popup.

What we think is different:

  • A/B tests that tell you when to stop: a p-value, a 95% interval and a planned sample. When B has really won, one click makes it the main version.

  • - Broken steps flag themselves. When a front-end release moves a button, you see it in Health instead of weeks later.

  • - An MCP server (Pro and above): Claude, Cursor or Codex can create draft tours, read stats and fix broken selectors. Drafts only, and every change is in the audit log.

  • - EU cloud (Amsterdam) or self-hosted on your own servers.

  • - A free plan with no time limit, priced by sites and seats, not by monthly active users.

In kust.io, our own product, activation went up 30% after we launched onboarding built with Clew. That's our internal data, and the case study on the site explains the caveats.

What I'd love feedback on: is the editor clear the first time you use it, and which format or trigger is missing for your product?