--- 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: 1. **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. 2. **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.) 3. **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. 4. **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`. Answer using only the relevant section — don't dump the whole guide. ## Step 4 — Actionable guidance - **Present all pricing and plan limits as best-effort** and point to `uxpressia.com/pricing` — per-seat billing and free-plan caps (3 documents each, PNG-only export, 1-user share) change. - **State plainly that UXPressia has no public API, no webhooks, and no confirmed Zapier app.** If the user wants personas/journeys in Jira, Productboard, or a warehouse, the only path out is **manual export** (PNG free; PDF/CSV on Pro; PPTX on Business) — there is no programmatic export. Of those, **CSV (Pro+) is the only machine-readable format** worth parsing (PNG/PDF/PPTX are presentation formats). Do not invent endpoints. To automate persona *generation*, call an LLM API directly instead. - **Note that integrations are inbound/embed only**: GA/Mixpanel/Sheets/Qualtrics feed data *into* a journey map; Slack/Teams send notifications *out*; Figma/Miro/LucidChart/Power BI embed *into* a map. None of them export UXPressia's own persona/journey data. - **When the user treats a persona or journey map as validation, correct it**: it aligns a team and communicates a hypothesis; demand proof is a stranger taking an action (waitlist, click, pre-sale). Send them to `/sales-idea-validation` for the go/no-go. - **For AI features, flag the monthly request caps** (Free ~30 persona requests; higher tiers more) and that AI-generated personas/journeys are drafts to edit, not researched findings. If you discover a gotcha or workaround not in `references/learnings.md`, append it there. ## Gotchas *Best-effort from research (2026-07) — re-verify plan-gated features and the integration surface, which drift.* - **No public API / no webhooks / no confirmed Zapier app.** This is the #1 developer complaint — you cannot pull persona or journey data out programmatically. Export is manual files only. - **Free plan is tight**: 3 journey maps + 3 personas + 3 impact maps, 5 tags, **PNG export only**, share with **1 user**. Real team use needs Pro (PDF/CSV) or Business (PPTX + integrations). - **Per-seat pricing** — cost scales with every collaborator, a common "too expensive for a small team" complaint. The value only pays off if you actually have a team to align. - **Integrations feed IN, not OUT.** GA/Mixpanel/Qualtrics import metrics into a map; there's no connector that syncs a persona to your CRM/roadmap. Insights-tool users often want a Dovetail link that doesn't exist. - **A persona/journey is not demand.** UXPressia makes it easy to produce a polished, convincing customer artifact for an audience that may not exist. Validate separately. - **Large maps get unwieldy** and editing is limited on mobile — build on desktop. ## Related skills - `/sales-idea-validation` — validate-before-building method + the full persona/idea-tool landscape (personas here align a team, they don't prove demand). Install: `npx skills add sales-skills/sales --skill sales-idea-validation -a claude-code` - `/sales-delve` — analytics-connected persona generator (data-backed personas from real GA4 traffic). Install: `npx skills add sales-skills/sales --skill sales-delve -a claude-code` - `/sales-instantpersonas` — fast prompt-only persona generator. Install: `npx skills add sales-skills/sales --skill sales-instantpersonas -a claude-code` - `/sales-do` — Not sure which skill to use? The router matches any sales objective to the right skill. Install: `npx skills add sales-skills/sales --skill sales-do -a claude-code` ## Examples - "I need to map our onboarding customer journey with the whole product team — is UXPressia the right tool?" → Yes for team alignment; walk through journey-map + shared library, and flag it's per-seat. - "Can I export my UXPressia personas via API into our Productboard roadmap?" → No API/webhooks; the only path is manual PNG/PDF/CSV/PPTX export (format depends on plan) — automate persona *generation* with an LLM API instead. - "I built three personas in UXPressia — does that mean my idea is validated?" → No; a persona is a hypothesis for aligning the team, not demand. Run `/sales-idea-validation` and test with a smoke test/pre-sale. ## Troubleshooting ### "There's no way to get my persona/journey data out into another tool" UXPressia has no public API, no webhooks, and no confirmed Zapier app. Export is **manual**: PNG on Free, PDF/CSV on Pro, PPTX on Business. Embeds (Figma/Miro/Power BI) and connectors (GA/Mixpanel/ Qualtrics) only bring data *in*. To feed a downstream roadmap/CRM programmatically, generate personas with an LLM API you control instead. ### "It's too expensive / the free plan won't let me do real work" Per-seat billing and a capped free tier (3 documents each, PNG-only, 1-user share) are the top pricing complaints. Decide by team size: solo/idea-stage → a free persona generator (`/sales-instantpersonas`) or a data-backed one (`/sales-delve`); a cross-functional team that needs one shared source of truth → Pro/Business is where UXPressia earns its cost. ### "I want to connect it to Dovetail / our insights store and can't" There's no native connector to research repositories like Dovetail. Bring quotes/metrics in manually or via the supported inputs (Google Sheets, Qualtrics, GA, Mixpanel). Treat UXPressia as the presentation/alignment layer, not the system of record for research.