HeatMapXHeatMapX
PricingJP
HeatMapXComing Soon 2026

Heatmaps you run from Claude Code.

CLI + CRO as Code. AI captures, analyses, and ships improvement PRs — for growth engineers.

~/your-siteComing Soon
Terminal demo of `claude heatmapx analyze /pricing`

Heatmaps that just sit there.

Insights stay in one person's head

Whoever opens the dashboard knows. Hypotheses and improvement history never make it into the codebase.

No "what to try next"

You see click distributions. Figuring out the next experiment is still on you.

Filters die in the GUI

Segments and filters set up in a dashboard never survive into a PR review.

Run from the CLI. Track in code.

heatmap.config.ts
import { defineHypothesis } from 'heatmapx'

export default defineHypothesis({
  page: '/pricing',
  goal: 'Lift CTA reach rate',
  variants: [
    { name: 'control' },
    { name: 'cta-above-fold' },
  ],
})
  1. 1. Define a hypothesis in heatmap.config.ts
  2. 2. Run claude heatmapx analyze /pricing for capture + AI analysis
  3. 3. Claude proposes fixes and an HTML patch as a PR
  4. 4. Review → merge → next hypothesis

What you get

Heatmap tracking

Click, scroll, and mouse movement captured by a lightweight tracker.

CRO as Code

Define hypotheses in heatmap.config.ts. Keep team knowledge in PR reviews.

Claude Code CLI

claude heatmapx analyze /pricing — Claude analyses, proposes fixes, generates an HTML patch.

Roadmap

  • Live

    Dashboard

    Visualize clicks, scrolls, and mouse movement

  • Live

    Tracking API

    One-line lightweight tracker

  • In progress2026 Q3

    Claude Code CLI

    Run capture, analysis, and suggestions from the CLI

  • In progress2026 Q4

    AI suggestions + HTML patch generation

    Claude turns analysis into PR-ready improvement patches

FAQ

How much does it cost?
Free / Pro $29/mo / Team $99/mo / Enterprise — four tiers, 20% off on annual plans. See heatmapx.com/en/pricing for details.
How is this different from Hotjar / Microsoft Clarity / PostHog?
Those are GUI-first heatmap viewers. HeatMapX manages hypotheses in git via CLI + code, and Claude proposes the actual improvement.
What kind of sites does it support?
Any site you can drop a tag into. Verified on Next.js / Nuxt / Astro / WordPress.
What about privacy?
No personally identifiable information is collected — only click coordinates and an anonymous session ID.
How do I join the beta?
Submit your email below. We'll send invitations in batches.

Get the beta invite

Drop your email below — we'll reach out when the CLI ships.