| name | sales-uxpressia |
| description | UXPressia (uxpressia.com) platform help — a collaborative customer-experience mapping tool for building personas, customer journey maps, impact maps, and service blueprints in one shared canvas, with AI-assisted persona and journey generation. It is the team-alignment (not demand-validation) class of persona tool: personas here align a team around customer needs, they do not prove anyone will pay. Use when building a persona or customer journey map in UXPressia, mapping touchpoints and emotions across a journey, generating an AI persona or journey, pulling Google Analytics/Mixpanel/Qualtrics data into a map, exporting to PNG/PDF/CSV/PPTX, comparing Free vs Pro vs Business plan limits, or asking whether it can push personas into Jira via API (it can NOT — export is manual, no public API/webhooks/Zapier). Do NOT use for comparing persona/idea tools (use /sales-idea-validation), prompt-only persona generators (use /sales-instantpersonas or /sales-personadeck), or analytics-connected personas (use /sales-delve). |
| argument-hint | [describe what you need help with in UXPressia] |
| license | MIT |
| version | 1.0.0 |
| tags | ["sales","persona","platform"] |
UXPressia Platform Help
UXPressia is a collaborative customer-experience mapping platform — personas, customer journey
maps, impact maps, and service blueprints on one shared canvas, built to align a team around
customer needs. It is not an idea-validation tool: a persona or journey map is a communication
artifact, not evidence anyone will pay.
Step 1 — Gather context
If references/learnings.md exists, read it first for accumulated platform knowledge.
Ask only what you can't infer:
- What are you making? A persona · a customer journey map · an impact map · a service
blueprint · CX Chunks (research organizer) · picking a plan · a data/export/integration question.
- Solo or with a team? (UXPressia's whole value is team alignment — a solo founder validating
an idea usually needs a lighter/free persona generator, not this.)
- Do you have real customer data yet (GA4/Mixpanel/Qualtrics/interviews), or are you filling
the map from assumptions? This decides whether the map is grounded or a guess.
- What plan are you on? Free · Pro · Business · Enterprise (limits differ a lot — see Step 3).
Skip-ahead: if the prompt already has enough context, go to Step 2.
Step 2 — Route or answer directly
| If the user's real question is… | Route to |
|---|
| "Is my idea worth building / will people pay?" | /sales-idea-validation |
| "Which persona tool should I even use?" | /sales-idea-validation (persona-tool landscape) |
| "I just want a quick persona from a one-line description" | /sales-instantpersonas or /sales-personadeck |
| "Build a data-backed persona from my GA4 traffic" | /sales-delve |
| "Design the landing page / smoke test" | /sales-funnel |
When routing, give the exact command: "This is a {domain} question — run: /sales-{skill} {question}"
Step 3 — UXPressia platform reference
Read references/platform-guide.md for the full reference — modules, pricing/plan gates, the
(inbound-only) integration surface, export formats, and mapping recipes. For the developer/no-API
surface specifically, read references/uxpressia-api-reference.md.
