Many test ideas stall between the insight and the code. Someone has to brief the change, a developer has to build it in the testing tool, and the result rarely looks like the rest of the site on the first try. Henkan Variant shortens that path. This post describes what Variant does today, in beta, without the roadmap.
Describe the change on your own page
Variant starts in Chrome. Open a page of your site, open the Variant side panel, select an element or circle an area, and describe the change in a sentence. You can also dictate it or attach a Figma mockup. When a request is ambiguous, Variant asks a clarification question with suggested answers before it writes anything.
The extension then gathers what Claude needs to write the change in your design: the page's CSS variables, fonts and colours, the structure of the visible page, the HTML of what you selected and a screenshot of the tab. Claude writes the CSS and JavaScript, and the change runs in your browser so you see it at once. The extension does nothing on a page until you open the panel and make a request.
Variant then checks its own work. It looks at the result, spots what it missed, such as text that overlaps or gets cut, and corrects it. Steps fixed that way are marked as corrected after visual review, so you know what was adjusted.
Your site's design, not a generic one
A change that looks foreign to the site is a bad test. Two features address that. Site profiles keep one design profile per site or brand: the extension scans up to six page types in your own browser (it never submits a form and never opens checkout, payment or account pages) and records colours, type, spacing and the components the site already has, with their real classes. Claude receives that profile with every request for the site in the Studio. References let you keep a component you like from another page and ask for something like it, taking its structure while keeping your site's look.
When you know which page to improve but not what to test, Ideas proposes up to five ideas for it, each with a hypothesis and a visual, informed by web searches when useful.
A shared place for every variant
Every variant made with a personal token is saved to your workspace in the web app at variant.henkanpartners.ai: before and after screenshots, the steps, the conversation, the code, notes and status. The variant page reads like a test file, from the idea to a ready-for-test checklist.
The web app also has a Studio for image mockups, to see an idea quickly; nothing made there goes into the test. A mockup you like goes to the extension in one click, and is coded there on the real page, with the same visual check.
From variant to A/B test
Each variant ends as one JavaScript snippet that bundles all its steps. You copy it or download it as a file, and paste it into the variation code of your testing tool: Kameleoon, AB Tasty, Optimizely, VWO and others that accept JavaScript. Variant does not connect to those tools itself, and the code should be reviewed before a test reaches your visitors. Use Variant only on sites you are allowed to modify.
Variant is in beta and available to the teams of Henkan's clients; access is managed by Henkan, and your consultant decides what is worth testing. If you already have access, the documentation covers the extension, the Studio and the export step by step. If not, talk to Henkan.
