AI Project Showcase: Journey Mapper (Customer Journey Mapper)

Section 1 — Product Overview

1.1 Product name and tagline

Name: Journey Mapper (Customer Journey Mapper)
Tagline: Visual customer journey mapping with AI-assisted path planning and persona management [CLAUDE NOTE: inferred from CLAUDE.md planned features]
Current status: Early stage — requirements defined extensively; no code written
First commit / project start: Pre-March 2026 (first monorepo snapshot of this path is e65fdaf2, Mar 27, 2026, “pre-migration: commit full ITI workspace before n8n+Dify migration”; the 11 CJM Requirements documents predate that commit but ITI/products/journey-mapper has no product-local .git)

1.2 What it is

Journey Mapper is a WordPress plugin for building, visualizing, and managing customer journey maps. It provides three interconnected modules — Personas, Journey Maps, and Content Hub — that allow marketing teams and consultants to map customer experiences across touchpoints, identify content gaps, and plan editorial strategies. The tool is designed as a multi-client WordPress Multisite deployment with potential as a productized offering. It features AI-assisted path planning and milestone tracking, with planned Claude integration for intelligent journey suggestions.

1.3 What makes it meaningfully different

• Purpose-built for journey mapping: Unlike generic tools (Notion, Trello) adapted for journey mapping, this is architecturally designed for personas, journey stages, touchpoints, and content mapping
• Three interconnected modules: Personas ↔ Journey Maps ↔ Content Hub with bidirectional relationships — content gaps surface automatically when journey stages lack mapped assets
• Multi-client architecture: WordPress Multisite with per-client data isolation, 5 user roles (Network Admin, Consultant, Client Admin, Client Editor, Client Viewer), and white-labeling
• AI-assisted journey planning: Planned Claude integration for intelligent path suggestions, pattern detection, and content recommendations
• Content gap analysis: Automated identification of journey stages without mapped content assets — a workflow that typically requires manual spreadsheet analysis

1.4 Platform and deployment context

Platform: WordPress plugin (WordPress 5.8+, PHP 7.4+)
Deployment: WordPress Multisite for consulting use; single-site for direct client use
Primary interface: WordPress admin with custom menu structure (Dashboard, Personas, Journey Maps, Content Hub, Reports & Analytics, Settings), Gutenberg blocks, shortcode system

---

Section 2 — User Needs and Problem Statement

2.1 Target user

Primary user: Marketing teams and consultants using the tool for client engagements (multi-client deployment)
Secondary users: Client administrators and editors who create and manage their own journey maps within assigned workspaces
User environment: Marketing teams and consultants working in WordPress who need structured customer journey mapping with persona management, touchpoint tracking, content planning, and exportable deliverables

2.2 The problem being solved

Customer journey mapping is critical for marketing strategy but currently relies on disconnected tools: Miro/FigJam for visual mapping, spreadsheets for content inventories, Google Docs for persona documentation, and manual processes to connect them. No purpose-built WordPress tool exists for creating structured journey maps with integrated persona management, content gap analysis, and multi-client workflows. Teams waste time recreating journey map structures for each client and manually tracking which content exists for each journey stage.

2.3 Unmet needs this addresses

Need	How the product addresses it	Source of evidence
Structured journey mapping in WordPress	Custom Post Types for personas, journeys, stages, and content with proper taxonomies and relationships	CJM Requirements/WP Plugin Initiial WP Plugin Requirements
Content gap identification	Journey stage → content asset mapping with automated gap analysis showing stages without mapped content	CJM Requirements/WP Plugin Customer Journey MVP Features
Multi-client data isolation	WordPress Multisite with per-client subsites; 5 user roles with capability-based permissions	CJM Requirements/WP Plugin High-Level Features
Exportable client deliverables	PDF, JSON, CSV, WordPress XML export with client branding; presentation-ready formats	CJM Requirements/WP Plugin Initiial WP Plugin Requirements
Persona-driven content strategy	Bidirectional linking between personas, journey stages, and content assets; editorial calendar integration	CJM Requirements/WP Plugin Content Marketing Additions

2.4 What users were doing before this existed

• Miro / FigJam / Lucidchart for visual journey mapping (no data structure, no content linking, no persona integration)
• Spreadsheets for content inventories and gap analysis (disconnected from journey maps)
• Google Docs / Notion for persona documentation (not linked to journeys or content)
• Trello / Asana for editorial calendar management (no journey mapping context)
• PowerPoint for client-ready deliverables (manual recreation from other tools)

---

Section 3 — Market Context and Competitive Landscape

3.1 Market category

Primary category: Customer journey mapping and content strategy tools (WordPress plugin market)
Market maturity: Fragmented — many generic tools adapted for journey mapping; no purpose-built WordPress solution
Key dynamics: Growing demand for customer experience (CX) tools; content marketing maturity driving need for journey-aligned content strategies; WordPress powers 40%+ of websites, creating a large addressable market for WP-native tools

3.2 Competitive landscape

Product / Company	Approach	Strengths	Key gap this project addresses	Source
Miro / FigJam ⚡	General-purpose visual collaboration	Flexible canvas, real-time collaboration	No structured data model; no content mapping; no WordPress integration	[CLAUDE NOTE: inferred from requirements context]
UXPressia ⚡	Dedicated journey mapping SaaS	Purpose-built UX, templates	SaaS-only; no WordPress integration; no content gap analysis; no multi-client consulting workflow	[CLAUDE NOTE: inferred]
Smaply ⚡	Journey mapping + persona + stakeholder maps	Strong visualization, research repository	SaaS-only; no content hub integration; expensive for agency use	[CLAUDE NOTE: inferred]
Notion / Airtable ⚡	Flexible database + wiki tools	Infinitely customizable	No journey-specific structure; requires user to build everything; no gap analysis	CJM Requirements context
Trello / Asana ⚡	Project management / Kanban	Good task management, editorial calendar	Not designed for journey mapping; no persona integration; no touchpoint tracking	[CLAUDE NOTE: inferred]

3.3 Market positioning

Journey Mapper is a purpose-built customer journey mapping tool for WordPress. It targets two use cases: (1) teams and agencies who need multi-client journey mapping with data isolation and exportable deliverables, and (2) individual companies using WordPress who want integrated persona management, journey mapping, and content planning within their existing CMS. [CLAUDE NOTE: inferred from requirements documents]

3.4 Defensibility assessment

• WordPress-native architecture: CPTs, taxonomies, and WordPress API integration create a tool that lives inside the client’s existing workflow — no context-switching to external SaaS
• Multi-client infrastructure: Multisite deployment with 5 user roles, white-labeling, and per-client data isolation serves a specific, underserved agency workflow
• Content gap analysis automation: The bidirectional persona ↔ journey ↔ content linking with automated gap detection is a workflow that currently requires manual spreadsheet analysis
• ITI Shared Library integration: Planned Claude AI integration for intelligent journey suggestions leverages ITI’s existing AI infrastructure

---

Section 4 — Requirements Framing

4.1 How requirements were approached

Requirements were developed iteratively through 11 structured requirement documents covering: initial WordPress plugin requirements, high-level features and user roles, customer journey MVP features (journey variables and methodology), content marketing additions, persona features, role mapping, internal tool features, UX design, modules architecture, plugin template, and overall plugin requirements. The documents reflect conversation-style requirement exploration with progressive refinement.

4.2 Core requirements

1. Custom Post Types: cjm_persona, cjm_journey, cjm_journey_stage, cjm_content with custom taxonomies
2. Persona management: demographics, goals, pain points, behaviors with template system
3. Journey mapping: stage builder with touchpoints, customer emotions, pain points, opportunities, and backend operations
4. Content Hub: content asset management with editorial calendar, journey/persona mapping, and gap analysis
5. WordPress Multisite for multi-client deployment with per-client data isolation
6. 5 user roles: Network Admin, Consultant, Client Admin, Client Editor, Client Viewer
7. Export system: PDF, JSON, CSV, WordPress XML with client branding
8. Shortcode system and Gutenberg blocks for frontend display
9. Reports & Analytics dashboard with content gap analysis visualization
10. AI-assisted journey planning with Claude integration (planned)

4.3 Constraints and non-goals

Hard constraints: WordPress 5.8+ compatibility; PHP 7.4+; WordPress Coding Standards; GPL-compatible licensing; must work with popular page builders and caching plugins
Explicit non-goals: NOT FOUND — add manually (no explicit non-goals documented)

4.4 Key design decisions and their rationale

Decision	Alternatives considered	Rationale	Evidence source
WordPress Multisite for multi-client	Single site with taxonomy isolation; hybrid approach	Complete data isolation; separate admin areas per client; most secure for multi-client use	CJM Requirements/WP Plugin Initiial WP Plugin Requirements
CPTs for main entities	Custom database tables; ACF/Pods	Leverages WordPress ecosystem (search, revisions, REST API, media); lower maintenance	CJM Requirements/WP Plugin Initiial WP Plugin Requirements
Freemium distribution model	Fully premium; open-source only	Core features free on WordPress.org for adoption; premium features (multisite, reporting, integrations) for revenue	CJM Requirements/WP Plugin Initiial WP Plugin Requirements
Journey stages as CPT vs. post meta	Post meta (simpler); custom tables (more performant)	Decision documented as open — CPT gives flexibility but increases DB complexity; post meta is simpler but harder to query	CJM Requirements/WP Plugin Initiial WP Plugin Requirements

---

Section 5 — Knowledge System Architecture

5.1 Knowledge system overview

KB type: Journey mapping methodology documentation embedded in requirements; planned knowledgebase directory
Location in repo: CJM Requirements/ (11 requirement documents)
Estimated size: 11 requirement documents covering journey mapping methodology, persona frameworks, content strategy, and WordPress architecture

5.2 Knowledge system structure

CJM Requirements/
├── WP Plugin Initiial WP Plugin Requirements    # WordPress architecture, CPTs, taxonomies, security, export
├── WP Plugin High-Level Features                # User roles (5), documentation, training, collaboration
├── WP Plugin Customer Journey MVP Features      # Journey variables, methodology, touchpoints, metrics
├── WP Plugin Content Marketing Additions        # Content hub, editorial calendar, gap analysis
├── WP Plugin Personas Addition                  # Persona management requirements
├── WP Plugin Role Mapping                       # User role definitions and permissions
├── WP Plugin Internal Tool Features             # Internal consulting workflow features
├── WP Plugin Customer Journey Mapping UX        # UX design requirements
├── WP Plugin Modules                            # Module architecture
├── WP Plugin Requirement Template               # Requirements template format
└── WP Plugin Requirements                       # Overall requirements summary

5.3 Knowledge categories

Category	Files / format	Purpose	Update frequency
WordPress architecture	WP Plugin Initiial WP Plugin Requirements	CPTs, taxonomies, database, security, performance, export	Per-release
User roles & permissions	WP Plugin High-Level Features, WP Plugin Role Mapping	5 user roles, capability matrix, documentation plan	Per-release
Journey mapping methodology	WP Plugin Customer Journey MVP Features	Journey variables, phases, touchpoints, emotions, metrics, evidence	Reference document
Content strategy	WP Plugin Content Marketing Additions	Content hub, editorial calendar, gap analysis, persona-content mapping	Per-release
UX design	WP Plugin Customer Journey Mapping UX	Interface design, onboarding, navigation, form design, accessibility	Per-release

5.4 How the knowledge system was built

The knowledge system was built through iterative requirements exploration, drawing on customer journey mapping methodology (awareness → consideration → purchase → use → loyalty → advocacy), content marketing best practices, and WordPress plugin architecture patterns. The documents progressively refined requirements from initial concept to detailed specifications.

5.5 System prompt and agent configuration

System prompt approach: Planned Claude integration for AI-assisted journey planning; no system prompts authored yet
Key behavioural guardrails: NOT FOUND — add manually (no AI guardrails defined yet)
Persona / tone configuration: NOT FOUND — add manually
Tool use / function calling: Planned use of ITI Shared Library Claude API Client, Token Budget, Base Agent, and Orchestrator components

---

Section 6 — Build Methodology

6.1 Development approach

Requirements-first approach with extensive upfront specification. 11 requirement documents define architecture, features, user roles, methodology, UX, and distribution before code is written. WordPress Multisite chosen for multi-client deployment. Claude AI integration planned through ITI Shared Library components.

6.2 Build phases

Phase	Approximate timeframe	What was built	Key commits or milestones
Requirements	Pre-March 27, 2026	11 requirement documents covering all aspects of the plugin	First captured in monorepo snapshot e65fdaf2 (Mar 27, 2026)
Implementation	Not started	No code written yet (no .php/.js/.swift source under /products/journey-mapper/; only plugin-installs/ contains zipped artifacts from unrelated ITI plugins)	—

6.3 Claude Code / AI-assisted development patterns

• Requirements documents drafted through AI-assisted conversation (iterative exploration of features, architecture, user roles)
• ITI Shared Library components planned for Claude API integration
• ITI Agent System available for development guidance (Orchestrator, Pattern, API Integration, Database, QA agents)
• WordPress Coding Standards and plugin architecture patterns documented

6.4 Key technical challenges and how they were resolved

Challenge	How resolved	Evidence
Multi-client data isolation	WordPress Multisite with per-client subsites; network-activated plugin; shared templates but separate data	CJM Requirements/WP Plugin Initiial WP Plugin Requirements
Journey stage data model	Open decision: CPT (flexible, more complex) vs. post meta (simpler, harder to query) vs. custom table (best performance)	CJM Requirements/WP Plugin Initiial WP Plugin Requirements
Non-technical user onboarding	Welcome screen, role-based intro, sample data/demo mode, progressive disclosure, achievement indicators	CJM Requirements/WP Plugin High-Level Features

---

Section 7 — AI Tools and Techniques

7.1 AI models and APIs used

Model / API	Provider	Role in product	Integration method
Claude (planned)	Anthropic	AI-assisted journey planning, intelligent path suggestions, content recommendations	ITI Shared Library class-iti-claude-api.php (planned)

7.2 AI orchestration and tooling

Tool	Category	Purpose
ITI Claude API Client (planned)	API wrapper	Standardized Claude API calls
ITI Token Budget (planned)	Context management	LLM context window management
ITI Base Agent (planned)	Agent framework	Single Claude-powered agent pattern
ITI Cache Manager (planned)	Performance	WordPress transients caching

7.3 Prompting techniques used

• [ ] AI-assisted journey planning (planned — not yet implemented)
• [ ] Content gap analysis with AI recommendations (planned)
• [ ] Persona generation from input data (planned)
• [ ] Journey stage suggestion based on industry templates (planned)

7.4 AI development tools used to build this

Tool	How used in build
Claude Code (Opus 4.6)	Requirements exploration and documentation through conversational AI-assisted specification
Cursor IDE	Requirements authoring (planned: development)
ITI Agent System	Available for development guidance when implementation begins

---

Section 8 — Version History and Evolution

8.1 Version timeline

Version / Phase	Date	Summary of changes	Significance
Requirements Phase	Pre-Mar 27, 2026 (first in monorepo e65fdaf2)	11 requirement documents covering WordPress architecture, user roles, journey methodology, content strategy, UX, modules	Complete product specification

8.2 Notable pivots or scope changes

The project evolved from a simple journey mapping visualization tool to a comprehensive three-module platform (Personas + Journeys + Content Hub) with multi-client infrastructure. The addition of the Content Hub module and content gap analysis automation significantly expanded the scope beyond traditional journey mapping tools. The multi-client Multisite architecture was added to support agency-style deployments.

8.3 What has been cut or deferred

• Gantt-style project timeline view (V2)
• CRM integration (HubSpot, Salesforce) for customer data import
• Google Analytics API integration for content performance data
• Social media API integration for content distribution tracking
• AI-assisted persona generation and journey suggestions (implementation deferred)
• Instacart-style one-click integrations

---

Section 9 — Product Artifacts

9.1 Design and UX artifacts

Artifact	Path	Type	What it shows
Admin menu structure	CJM Requirements/WP Plugin Initiial WP Plugin Requirements	Menu hierarchy specification	Dashboard, Personas, Journey Maps, Content Hub, Reports, Settings
Plugin file structure	CJM Requirements/WP Plugin Initiial WP Plugin Requirements	Directory layout	admin/, includes/, public/, templates/, languages/
Meta box organization	CJM Requirements/WP Plugin Initiial WP Plugin Requirements	Edit screen layout	Persona tabs, journey stage builder, content mapping

9.2 Documentation artifacts

Document	Path	Type	Status
CLAUDE.md	CLAUDE.md	Development context	Complete
Initial WP Plugin Requirements	CJM Requirements/	WordPress architecture, CPTs, taxonomies, security, export, multi-client	Complete
High-Level Features	CJM Requirements/	User roles, documentation plan, training, collaboration, permissions	Complete
Customer Journey MVP Features	CJM Requirements/	Journey mapping methodology, variables, touchpoints, metrics	Complete
Content Marketing Additions	CJM Requirements/	Content hub, editorial calendar, gap analysis	Complete
Persona Addition	CJM Requirements/	Persona management requirements	Complete
Role Mapping	CJM Requirements/	User role definitions and permissions	Complete
Internal Tool Features	CJM Requirements/	Internal/agency workflow features	Complete
Customer Journey Mapping UX	CJM Requirements/	UX design requirements	Complete
Modules	CJM Requirements/	Module architecture	Complete
Requirements Template	CJM Requirements/	Requirements format	Complete
Requirements Summary	CJM Requirements/	Overall requirements	Complete

9.3 Data and output artifacts

Artifact	Path	Description
CPT definitions	CJM Requirements/WP Plugin Initiial WP Plugin Requirements	cjm_persona, cjm_journey, cjm_journey_stage, cjm_content with taxonomies
Role/capability matrix	CJM Requirements/WP Plugin High-Level Features	5 roles × capabilities mapping
Export format definitions	CJM Requirements/WP Plugin Initiial WP Plugin Requirements	JSON, CSV, PDF, WordPress XML with client branding

---

Section 10 — Product Ideation Story

10.1 Origin of the idea

The product originated from the observation that customer journey mapping is a core marketing deliverable often assembled manually across disconnected tools. The manual process of creating journey maps in Miro, maintaining persona docs in Google Docs, and tracking content inventories in spreadsheets creates inefficiency and data fragmentation. A WordPress-native tool that integrates all three workflows would improve efficiency for teams and agencies. [CLAUDE NOTE: inferred from requirements framing]

10.2 How the market was assessed

Research approach used: Analysis of existing journey mapping tools, WordPress plugin ecosystem, and consulting workflow pain points
Key market observations: No purpose-built customer journey mapping WordPress plugin exists; generic tools (Miro, Notion) require manual structure creation; existing SaaS journey mapping tools (UXPressia, Smaply) don’t integrate with WordPress or content management workflows [CLAUDE NOTE: inferred]
What existing products got wrong: Separation of journey mapping from content planning; no automated content gap analysis; no multi-client infrastructure; no WordPress integration

10.3 The core product bet

If you build a structured journey mapping tool inside WordPress — where the content already lives — you can automate the connection between journey stages and actual content assets, surfacing gaps that currently require manual spreadsheet analysis. Multi-client teams need isolation infrastructure that generic tools don’t provide.

10.4 How the idea evolved

The concept progressed through 11 iterative requirement documents:

1. Started as a basic WordPress plugin for journey visualization
2. Added persona management as a first-class module (not just a reference doc)
3. Added Content Hub with editorial calendar and gap analysis — the key differentiator
4. Expanded to multi-client Multisite architecture for agency-style deployments
5. Defined 5 user roles for team collaboration (Network Admin → Client Viewer)
6. Planned AI integration via Claude for intelligent suggestions and path planning
7. Added comprehensive documentation, training, and onboarding requirements for non-technical users

---

Section 11 — Lessons and Next Steps

11.1 Current state assessment

What works well: Extremely thorough requirements (11 documents); well-defined user roles and permissions; clear module architecture (Personas ↔ Journeys ↔ Content Hub); multi-client features (Multisite, white-labeling, export) fully specified
Current limitations: No code written; no UI mockups or wireframes; journey stage data model decision unresolved (CPT vs. post meta vs. custom table); AI integration not specified beyond “planned”
Estimated completeness: 15% (thorough requirements; no implementation)

11.2 Visible next steps

1. Resolve data model decision: journey stages as CPT, post meta, or custom table
2. Create WordPress plugin scaffold with CPTs, taxonomies, and capability definitions
3. Build persona management module (create, edit, list, template system)
4. Implement journey map builder with stage creation and touchpoint tracking
5. Build Content Hub with content asset management and journey/persona mapping
6. Implement content gap analysis visualization
7. Create export system (PDF, JSON, CSV with client branding)
8. Set up WordPress Multisite infrastructure for multi-client deployment
9. Integrate Claude AI for journey suggestions and content recommendations
10. Build Gutenberg blocks and shortcode system for frontend display

11.3 Lessons learned

_Manual input required — this section cannot be populated automatically._

---

Section 12 — Claude Code Validation Checklist

• [x] Every placeholder has been replaced or marked NOT FOUND
• [x] All externally-sourced competitive data is marked with ⚡
• [x] All inferences are marked with [CLAUDE NOTE]
• [ ] Version history is derived from actual git log where available — no git history found for this product
• [x] Knowledge system paths reflect real directory structure
• [x] AI tools are confirmed from code/config, not guessed
• [x] Section 11.3 is left blank for manual input
• [x] Document header shows today’s date and files examined

---

Sources Examined

File / Path	What it contributed
CLAUDE.md	Project overview, development status (early stage), planned features, related projects (Career Coach), ITI Shared Library integration
Journey Mapper/CLAUDE.md	Duplicate of root CLAUDE.md with same content
CJM Requirements/WP Plugin Initiial WP Plugin Requirements	WordPress architecture: CPTs, taxonomies, database, roles, security, performance, file structure, multi-client options, export, deployment, distribution, testing
CJM Requirements/WP Plugin High-Level Features	User roles (5 defined), documentation structure, training approach, UI/UX requirements, collaboration features, permission granularity, onboarding
CJM Requirements/WP Plugin Customer Journey MVP Features	Journey mapping methodology: customer characteristics, journey phases, touchpoints, emotions, context, operations, metrics, opportunities
CJM Requirements/WP Plugin Content Marketing Additions	Content hub requirements, editorial calendar, content-journey mapping, gap analysis
CJM Requirements/WP Plugin Personas Addition	Persona management requirements (referenced but content not fully read)
CJM Requirements/WP Plugin Role Mapping	User role definitions and capability mapping (referenced)
CJM Requirements/WP Plugin Internal Tool Features	Internal/agency workflow features (referenced)
CJM Requirements/WP Plugin Customer Journey Mapping UX	UX design requirements (referenced)
CJM Requirements/WP Plugin Modules	Module architecture (referenced)
CJM Requirements/WP Plugin Requirement Template	Requirements format template (referenced)
CJM Requirements/WP Plugin Requirements	Overall requirements summary (referenced)

---

Addendum — April 2026 Competitive Landscape and Roadmap Update

1. Industry Context

The customer journey mapping category is being reshaped by two forces: the AI capability explosion in purpose-built SaaS tools, and the democratization of software creation through vibe coding platforms. UXPressia, Smaply, and JourneyTrack all shipped AI-powered journey generation features in early 2026, which means the “AI-assisted journey planning” that Journey Mapper listed as a planned differentiator is now table stakes. Any product entering this space without AI journey generation from natural language prompts will feel dated on arrival.

The vibe coding dynamic cuts both ways for this product. On one hand, tools like Cursor, Claude Code, and Bolt.new make it faster than ever to build a complex WordPress plugin — which is good, since Journey Mapper is 15% complete with zero code written. On the other hand, the same tools make it possible for any agency or consultant to build their own journey mapping tool in a weekend. The barrier to entry has dropped. What hasn’t dropped is the barrier to building a good journey mapping tool — one with a sound data model, proper multi-client isolation, and bidirectional content-journey-persona relationships that actually surface useful gaps. That requires the domain judgment that comes from building audience-facing products for three decades.

LLM convergence also matters here. Claude, GPT-5, and Gemini 2.5 can all generate plausible journey maps from a text prompt. The model is not the differentiator — the data model is. UXPressia’s AI generates journey stages, but those stages live in UXPressia’s SaaS. Journey Mapper’s bet is that agencies and consultants working in WordPress want journey data that lives alongside the content it maps to, in a CMS they already manage, with client data isolation they control at hosting cost rather than per-seat SaaS pricing.

2. Competitive Landscape Changes

Journey Mapper’s requirements were written before most of these competitive shifts. This is the first competitive analysis for the product.

New entrants since requirements were authored:

Competitor	Category	Key Capability
JourneyTrack	Purpose-built journey management	G2 4.8 rating; AI journey creation from prompts; Qualtrics/Medallia/Forsta integrations; Jobs-to-be-Done opportunity scoring; Jira integration
cxomni	Enterprise journey intelligence	G2 4.8; connects journey data to business metrics
CausalFunnel (WP plugin)	WordPress journey tracking	AI-powered heatmaps and user journey tracking with cookie-less technology; updated Feb 2026
Pathmetrics (WP plugin)	WordPress conversion attribution	Maps customer journeys from first click to conversion (€79-499/yr); GDPR-compliant
Content Camel	Content enablement	Visual kanban boards organized by funnel stages; content-to-journey-stage mapping

Features competitors added in early 2026:

Feature	Who Added It	Impact
AI Journey Assistant (in-tool Q&A about maps)	UXPressia (Feb 2026)	Conversational AI about journey data is now expected
AI journey map generation from prompts	UXPressia, JourneyTrack, Smaply	Auto-generating journey maps from natural language is table stakes
AI persona generation from raw data	JourneyTrack (Emergent Personas), EdenPersona, HubSpot	AI persona creation from CSV/CRM data is expected
Real-time journey pulse tracking	TheyDo	Shifts maps from static documents to dynamic monitors
Workshop-to-map conversion	JourneyTrack	One-click workshop output to journey map
20+ external data source integrations	Smaply	CRM, analytics, feedback tools feeding journey maps
Jira integration for engineering handoff	JourneyTrack	Journey context visible in engineering tickets

Eroded differentiators:

Originally Planned as Unique	Current Status
AI-assisted journey planning	UXPressia, Smaply, JourneyTrack, Miro all now offer AI-generated journey maps
Persona management as first-class module	Smaply, JourneyTrack, UXPressia all have robust persona modules
Multi-persona journey comparison	UXPressia supports persona comparison; Smaply supports persona layers
Multi-format export (PDF, JSON, CSV)	Smaply, UXPressia, JourneyTrack all offer this

What remains genuinely differentiated:

• WordPress-native architecture — no SaaS competitor offers this
• Content Hub with automated content gap analysis tied to journey stages — SaaS tools map personas to journeys but don’t connect to actual content inventory
• Multi-client Multisite infrastructure for agencies at hosting cost, not per-seat SaaS pricing
• Bidirectional persona-journey-content linking with gap prioritization

3. Our Competitive Response: Product Roadmap

The roadmap prioritizes shipping an MVP that establishes the WordPress-native journey mapping position before the market window closes.

Tier 1 (next build cycle, 7 items) is entirely about getting code written and shipped. The WordPress plugin scaffold with CPT architecture (L) resolves the outstanding data model decision — the recommendation is custom tables for stages and touchpoints (query performance) with CPTs for personas, journeys, and content. Persona management (L) and the journey map builder with drag-and-drop stages (XL) are the core interaction. The Content Hub with journey-stage mapping (L) and content gap analysis dashboard (L) are the features no competitor has — this is where the product earns its position. AI journey map generation via Claude (L) is a parity requirement given what UXPressia and JourneyTrack shipped in February. Basic JSON/CSV export (M) completes the MVP.

Tier 1 comes first because without a shipped product, competitive analysis is academic. The XL journey map builder is the highest-risk item and needs to start early.

Tier 2 deepens the content gap differentiator: AI persona generation from data import (M), AI content brief generation from identified gaps (M), PDF export with client branding (L), editorial calendar with journey context (M), industry-specific templates (M), emotional curve visualization (S), and an admin dashboard (M).

Tier 3 enables agency scale: WordPress Multisite multi-client infrastructure (XL), AI journey assistant for conversational Q&A (L), real-time collaboration (M), white-labeling (M), cross-client pattern detection (L), Gutenberg blocks and shortcodes (L), and version history (M).

Tier 4 explores Google Analytics integration, CRM integration, Jira integration, AI sentiment analysis, AI storyboard visualization, presentation mode, WordPress.org distribution, and a REST API.

4. New Capabilities Added Since Last Build

These Skills from the April 2026 roadmap cycle are directly relevant to Journey Mapper’s development:

• customer-journey-methodology — Journey phase design (awareness through advocacy), touchpoint identification, emotional curve mapping, pain point analysis, and opportunity scoring. This skill codifies the methodology embedded in Journey Mapper’s 11 requirements documents into a reusable reference for AI-assisted development.
• content-gap-analysis — Methodology for mapping content against journey stages and personas, scoring gaps by business impact, and generating content briefs from identified gaps. Directly supports the Content Hub differentiator.
• multi-client-wordpress-architecture — WordPress Multisite deployment patterns for multi-client products: subsite provisioning, per-client data isolation, white-labeling, and client onboarding automation. Supports the Tier 3 agency infrastructure.
• kanban-board-builder — Drag-and-drop card management using dnd-kit (React), HTML5 Drag API, or native SwiftUI. Relevant to the journey stage builder and editorial calendar components.
• agentic-task-execution — Patterns for Claude tool use to execute real-world tasks with safety guardrails. Relevant to the AI journey assistant and content brief generation features.

5. Honest Assessment

Current strengths: Journey Mapper has the most thorough requirements documentation in the ITI portfolio — 11 documents covering WordPress architecture, user roles, journey methodology, content marketing integration, persona management, and UX design. The product’s core bet is sound: no purpose-built journey mapping plugin exists for WordPress, and the content gap analysis tied to journey stages addresses a workflow that 60%+ of teams currently do manually with spreadsheets. The WordPress-native positioning avoids the per-seat SaaS pricing that makes tools like Smaply (€19+/month/user) expensive for multi-client agency use.

Acknowledged gaps: No code has been written. The product is 15% complete — requirements only. The journey stage data model decision (CPT vs. post meta vs. custom table) remains unresolved. There are no wireframes or UI mockups. AI integration is described as “planned” without specification. Every competitor that matters has shipped AI journey generation since these requirements were authored. The market is moving fast, and Journey Mapper is standing still.

What we’re watching: The speed at which SaaS journey mapping tools are adding AI capabilities. UXPressia’s AI Journey Assistant (Feb 2026) and JourneyTrack’s AI journey creation set the expectation that any new entrant must offer AI generation out of the box. We’re also watching whether the two WordPress journey-tracking plugins (CausalFunnel, Pathmetrics) expand from tracking visitor behavior to designing journey maps — that would close our WordPress-native positioning advantage. The content enablement space (Content Camel) is also worth monitoring, since content-to-stage mapping overlaps with our Content Hub differentiator.

This product demonstrates how we approach complex product requirements — with deep domain research, structured specification, and a realistic assessment of competitive dynamics. It also demonstrates what we’ve learned about the risk of over-specifying before building: the market shifted significantly while 11 requirements documents were being authored.