This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
Try Clew
Product tours and popups you test without a developer
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.
I build kust.io 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?
About Try Clew on Product Hunt
“Product tours and popups you test without a developer”
Try Clew was submitted on Product Hunt and earned 2 upvotes and 1 comments, placing #151 on the daily leaderboard. 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.
On the analytics side, Try Clew competes within User Experience, SaaS and No-Code — topics that collectively have 419.1k followers on Product Hunt. The dashboard above tracks how Try Clew performed against the three products that launched closest to it on the same day.
Who hunted Try Clew?
Try Clew was hunted by Andrei Davydov. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of Try Clew including community comment highlights and product details, visit the product overview.
Andrei Davydov
Hi Product Hunt! I'm Andrey, the maker of Clew.
I build kust.io 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?