Generated in Claude

Claude Plugin · Customer Experience Maps + Service Blueprints

Build the right thing. Not just a thing.

CX Maps generates customer experience maps and service blueprints inside Claude, and tags every insight with where it came from. Research, stakeholder belief, or AI inference. Your team finally knows what to trust before shipping.

Buy on Gumroad
$49  ·  One-time  ·  No subscription
  user-onboarding-journey.html
Discover
Sign Up
First Use
Activate
Pain Points
Unclear value prop on homepage
research
Too many required fields
stated
Feature discovery overwhelming
assumed
Drop-off before first value
research
Emotions
Skeptical, comparing alternatives
research
Cautious, unsure of commitment
stated
Excited but uncertain
assumed
Frustrated, considering churn
stated
Opportunities
Social proof above the fold
research
Progressive field disclosure
stated
Interactive onboarding checklist
assumed
Triggered re-engagement
assumed
Research = real user data
Stated = stakeholder input
Assumed = AI inference

§01 / The Problem

AI experience maps lie with confidence.

Every AI-powered mapping tool outputs the same authoritative tone whether it's synthesizing real user interviews or filling gaps with plausible-sounding inference. You can't tell the difference by looking at the map.

That's not a design problem. It's an epistemic one. A map that doesn't distinguish between what users told you, what stakeholders believe, and what the AI guessed is a map you can't make decisions from.

Most mapping tools render beautiful outputs. They don't tell you which insights are solid and which ones you still need to validate. CX Maps does.

§02 / See The Difference

Two maps. Same data. Only one tells you what to trust.

The same four insights, rendered two ways. The version on the left is what most AI mapping tools give you. The version on the right is what CX Maps gives you.

Typical AI Output No tagging
Pain Points / Onboarding
  • Unclear value prop on homepage
  • Too many required fields at signup
  • Feature discovery feels overwhelming
  • Drop-off before first value moment
The trapEvery insight reads the same. You cannot tell which ones came from real interviews and which ones the AI invented to fill gaps. Your team builds from all of them equally.
CX Maps Output Source-tagged
Pain Points / Onboarding
  • research Unclear value prop on homepage
  • stated Too many required fields at signup
  • assumed Feature discovery feels overwhelming
  • research Drop-off before first value moment
The shiftTwo insights are validated research. Build from those first. One is internal belief. Test it. One is AI inference. Treat it as a research question, not a fact.

§03 / The Differentiator

Every insight knows where it came from.

CX Maps tags every pain point, emotion, opportunity, and touchpoint with its evidence source, so your team knows exactly what to trust and what to validate before shipping anything.

No incumbent does this. It's the difference between a map that documents what you know and a map that pretends you know everything.

Research

Sourced from real user interviews, usability studies, surveys, or analytics data. Your most trustworthy inputs. Build from these first.

Stated

Sourced from stakeholder belief, product team assumptions, or customer support themes. Real inputs, but filtered through an internal lens. Validate before acting.

Assumed

Inferred by the AI to fill gaps in coverage. Plausible but unverified. Treat as hypotheses, not facts. These are your next research questions.

§04 / Output Types

Four map types. Pick the right one for the question you're trying to answer.

◆ Current State

What actually happens today.

Documents the real experience as it exists. Friction, workarounds, and all. The baseline before you design anything. Use this when you need to make the invisible visible to stakeholders.

◆ Future State

The experience you're designing toward.

Maps the aspirational journey once your product or service changes are in place. Use this to align a team on what "good" looks like before anyone writes a line of code.

◆ Day-in-the-Life

Full context beyond your product.

Zooms out to show how your user's full workday or workflow intersects with your product. Use this when context outside the product is driving the problems inside it.

New
◆ Service Blueprint

Backstage added to the map.

Layers in the organizational systems, teams, and handoffs that run behind each stage of the user journey. Use this when the user's experience is being broken by something the user never sees.

§05 / Sample Outputs

See what the maps actually look like.

Three real examples generated by the plugin. Open any of them in your browser. They're fully self-contained HTML, no login required.

Current State · Freelance/Consulting
Maya R. Creator Weekly Workflow

A freelance creator navigating content sourcing, curation, and newsletter delivery across a 6-stage weekly cycle.

View Map →
Service Blueprint · Freelance/Consulting
Maya R. With Backstage Layer

Same journey as above, extended with the tools, systems, and handoffs running behind the scenes. The service blueprint format.

View Blueprint →
Current State · B2B SaaS
Enterprise CS Onboarding

An enterprise customer success manager navigating a new client onboarding, from kickoff through first value delivery.

View Map →

These files open directly in any browser. No login, no app, no account required.

§06 / How It Works

From intake to polished map in one Claude session.

01
Intake

A structured conversation, not a form.

CX Maps starts by asking for any materials you already have. Interview notes, persona docs, empathy maps, support tickets, transcripts. Paste them in and it reads them. Then it asks targeted questions: who's the persona, what's the specific scenario, which map type, which industry. It flags where your coverage is thin before generation starts, not after.

At the end of intake, you see a full summary: persona, stages, confidence level, and a list of everything it knows vs. everything it'll have to infer. You confirm it before anything generates. No surprises.

02
Structure

Claude builds the data model.

CX Maps generates a structured JSON data model (persona, stages, actions, touchpoints, emotions, pain points, and opportunities) with a confidence source tag on every item. It selects from six industry-specific stage libraries (SaaS, AEC, Film/TV, Freelance, B2B Services, General) or derives custom stages from your scenario. Review it before the HTML renders. Change anything.

03
Render

Get a self-contained HTML map.

One clean HTML file. No login required to view. Send it to any stakeholder, embed it in Notion, drop it in a Figma handoff. The confidence tags are visible throughout. Not hidden in metadata, not stripped on export. Service blueprints include the full backstage layer automatically.

§07 / What's Included

A serious tool for serious strategy work.

//
Claude Plugin

Runs inside Claude. No separate app, no new login, no extra tab. Built for Claude Desktop (Cowork) and compatible with Claude Code. If you're already using Claude, you're set.

[ ]
Self-Contained HTML Output

The exported map is a single HTML file. Anyone can open it in a browser. No app required, no account, no expiring link. It belongs to you.

Three-Skill Pipeline

Intake, data model, and render are three discrete Claude skills. Not a black box. You can intervene, edit, and redirect between each step.

Multi-Persona Synthesis

Run journey maps for multiple personas, then generate a synthesis report that finds the common needs across all of them. The shared truths underneath your segments. Useful when you're prioritizing and need to know what every persona has in common, not just what makes them different.

6 Industry Stage Libraries

SaaS, AEC, Film/TV, Freelance/Consulting, B2B Services, and General. Each with domain-accurate stage names. Or derive custom stages from your specific scenario. The tool picks the right library from your intake answers.

No Subscription

Buy once. Run as many maps as you want. You're paying for the logic, not paying per map or per month.

§08 / Pricing

One price. No tricks.

$49 to save four weeks of work. That's the math. A real customer experience map takes a strategist a month of interviews, synthesis, and stakeholder alignment. CX Maps gets you to a defensible draft in a single Claude session, with the confidence tags showing exactly where you still need to validate.

Hire a strategist
$15k+
4 weeks of synthesis work
Buy CX Maps
$49
One Claude session, kept forever

Not a SaaS subscription. Not a per-seat license. Not freemium. Buy once, run as many maps as you want, own the output.

One-Time Purchase
$49
One-time payment · No subscription
  • Customer Experience Maps plugin for Claude
  • Three-skill pipeline (intake → data model → render)
  • Confidence tagging on every insight
  • Self-contained HTML output
  • Runs inside Claude. No extra setup
  • Multi-persona synthesis report
  • Lifetime access. No future charges
Buy on Gumroad

7-day refund through Gumroad. No questions.

§09 / Common Questions

Answers before you ask.

Do I need a Claude subscription?

Yes. Customer Experience Maps is a Claude plugin and requires an active Claude subscription to run. It's built for Claude Desktop (Cowork) and also compatible with Claude Code. If you're already using Claude, install the plugin and you're ready to go.

What inputs does it accept?

Anything text-based: interview notes, workshop outputs, empathy map exports, support ticket themes, stakeholder briefs, survey summaries. The richer your input, the fewer ASSUMED tags on the output.

Can I share the output with people who don't have the plugin?

Yes. The rendered map is a standalone HTML file. Open it in any browser. No account needed to view it.

What does "assumed" actually mean in practice?

It means the AI inferred that content to fill a gap in the journey, because you didn't provide direct evidence. It's not a warning, it's a research prompt. Those are your next user interviews.

Why one-time pricing, and are there recurring costs?

$49 once. Nothing recurring. You'll need an active Claude subscription to run the plugin, but that's a separate bill you already have if you're considering this. Subscriptions are the wrong model for a tool you install and run locally. You're buying the logic, not renting access to a server.

What if it's not for me?

Gumroad handles a 7-day refund window. If the plugin isn't working for your needs, request a refund through Gumroad inside that window. You won't need to message me to get one.

§10 / From The Maker

Built by

Alison Grippo

Three decades building products for other people.

I've spent thirty years building products for other people. Most of that time, the hardest part of the job wasn't the design or the engineering. It was watching teams ship from journey maps that looked authoritative but quietly fudged half their data. Stakeholders signed off. Engineers built. Then the assumptions surfaced as bugs in production.

CX Maps is the first of an arsenal of tools I'm releasing to make the heavy lifting of product design and validation light and fast. A month of synthesis work in a single Claude session, with the gaps marked so you know where the real risk is.

A map that's honest about itself is a map you can actually build from. That's what's in the box.

More on how I think about AI product work →

Stop shipping from maps that hide their gaps.

Buy the plugin once. Know exactly what your journey map knows, and exactly what it's still guessing at.

Buy Now / $49