Enterprise DNA

Instead of UXPressia

Stop renting UXPressia. Own your customer journey system.

We build your version around how you review customer experiences, map the agreed UXPressia exports and run it for you. Keep your steps, evidence and decisions together.

UXPressia Business lists US$95 per user per month on monthly billing. Pro lists US$36. Your total depends on your users, billing term and plan.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What the subscription buys

A recurring user bill around your journey records

UXPressia sells visual mapping and collaboration as well as records. If your weekly work is reviewing evidence and following through on improvements, build that work around your own database.

people

A price for each user

Business is listed at US$95 per user per month on monthly billing. The team size changes the total.

route

Journey maps and shared material

Paid plans include unlimited maps, personas and reusable pieces. Your customer steps are the information behind the view.

download

Portable exports on paid plans

CSV and scalable PDF exports are included in Pro and above. Keep an export and check what it contains before switching.

analytics

Reports and branding on Business

Business adds workspace reports and branded exports. Your owned version produces review briefs in your business name.

account_tree

Visual organisation of the work

Business includes board and hierarchy views. The owned base shows the customer sequence and improvement queue as read-only reports.

settings

A higher tier for enterprise controls

Enterprise pricing is custom. Its access and security options need an explicit replacement plan when those are part of your current service.

The work after the workshop

A journey that leads to a recorded decision

Evidence

Know which findings still apply

A step change makes earlier evidence stale. A new review date alone cannot make old findings describe the revised step.

  • check Sources attached to findings
  • check Review dates visible beside evidence
  • check Changed steps linked to their earlier findings
  • check A list of steps with no current support

Decisions

Choose improvements with the evidence in view

Compare the impact and effort your team has recorded, then save the owner decision and its reason.

  • check Impact and effort scored by your team
  • check Current evidence count beside every priority
  • check Approval held when evidence is missing
  • check Decision notes and the person who made them

Follow-through

Check what happened after the change

Completion needs two dated measurements of the same measure and unit. The record distinguishes an observed change from a claim about its cause.

  • check An owner and due date for each improvement
  • check Overdue and unassigned work surfaced
  • check Before and after readings kept with their sources
  • check A weekly review across journeys and owners

Ownership

Keep the record and shape the rules

The original export columns stay available while your team agrees what they mean in the new system.

  • check Test the import before saving records
  • check Original export values retained for checking
  • check Private review briefs in your brand
  • check Your own checks across evidence age, step changes and decisions

Make it yours

Design your own UXPressia replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from UXPressia. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your UXPressia replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your UXPressia data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Customer Journeys for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Customer Journeys for Claude Code

Connected to your own database

What needs our attention before the next customer journey review?

kind | reference | owner | reason evidence | EV-OLD | | Evidence expired, withdrawn or tied to an older step journey | ONBOARD | Mere | Review overdue or missing opportunity | OP-DOCS | | Action overdue opportunity | OP-DOCS | | Owner missing

Ask it anything

Questions UXPressia cannot answer

Every one of these is a real question the demo answers today. Yours will be different, and that is the point.

chat_bubble Which steps have no current evidence?
chat_bubble Which findings describe an older version of a step?
chat_bubble Which improvements need a decision?
chat_bubble Which high-impact actions lack supporting evidence?
chat_bubble Who owns the overdue work?
chat_bubble Which owner has the largest overdue workload?
chat_bubble Did the same measure change after the improvement?
chat_bubble Which personal findings need a retention review?
chat_bubble What did a record say before it changed?
chat_bubble Which journeys have both overdue actions and evidence gaps?

Switching

How to switch from UXPressia

The time depends less on loading the export than on mapping your fields, checking the records and deciding which history needs separate migration work.

  1. 1

    Export the records you need

    Choose the journey records, evidence and improvement decisions you want to carry over. UXPressia has a paid CSV journey export with a vendor example. If that export is not available in your account, export what your account allows, usually CSV or Excel, and check with UXPressia which records and fields it includes. Keep a copy of the original export.

  2. 2

    Test, then load the records

    Start with one export and have the import run as a test, without saving changes. Check the counts and column mappings before you load the records for real. The importer supports the row layout in UXPressia’s vendor CSV example and agreed column mappings. If your map has stages across the top, it needs a mapping step first.

  3. 3

    Check the import results

    Review any rows or fields the import marks for attention, then compare the imported records with your export. Confirm that key journey steps, evidence and improvement decisions are present, and that fields landed in the right places. Original export columns are retained, so you can agree further mappings where needed. Images, comments, access rules and historical approvals need separate migration work.

  4. 4

    Run both side by side

    Keep your UXPressia workflow in place while you check the imported records and read-only reports in Customer Journeys for Claude Code against what your team relies on. Confirm that the steps, evidence, owners and decisions you need are there. Use this overlap to identify missing mappings or history that needs separate work before you stop using UXPressia.

  5. 5

    Switch off UXPressia

    Once you have confirmed the imported records and decided how to handle anything that did not transfer, switch off UXPressia if you no longer need it. Keep in mind that the system provides read-only journey reports, not a collaborative visual canvas. If your team still needs a shared visual workspace, discuss that requirement before agreeing the switch.

construction

Where the real effort goes

Most of the work is usually mapping your own fields and rules, checking the records, and deciding how much history to bring across. The importer can retain original columns, but images, comments, access rules and historical approvals need separate migration work. If Enterprise DNA runs the system for you, they map the agreed exports, check the result and build your fields, rules and documents.

Not ready for a call?

Get your UXPressia switch plan by email

We will send you the step-by-step plan for moving your business off UXPressia, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Start yourself, have it customised, or have us run it

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and run npm install and npm run demo
  2. 2 Open it with Claude Code, Codex, OpenCode or Cursor and run /weekly-review
  3. 3 Export your UXPressia CSV and follow the replace guide, starting with a dry run
  4. 4 Check the mapping and counts, then add your real evidence and decisions
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your customer steps, fields and review rules
  • check Your agreed UXPressia exports mapped and reconciled
  • check Your brand on review briefs and decision records
  • check A web front end or different stack when your team needs one
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed with agreed access and backups
  • check Your weekly review and overdue action list prepared
  • check Your sources and business systems connected within the agreed scope
  • check Operated through Omni by Enterprise DNA as your process changes
Book 30 minutes with Sam

Questions

Instead of UXPressia, answered

Does this replace the visual mapping workshop? expand_more

The free base handles the customer steps, evidence and improvement decisions after the workshop, with read-only journey reports. If your team needs a shared visual workspace, Enterprise DNA scopes that into your custom version. We check how you use UXPressia before agreeing the switch.

Will our UXPressia export load without re-entering it? expand_more

The free importer accepts the row layout in the vendor example and supports agreed column mappings. Original columns are retained. A map arranged with stages across the top needs a mapping step first. Images, comments, access rules and historical approvals need separate migration work. We test your actual export before promising the scope.

How do we know an improvement was based on real evidence? expand_more

Each finding records its source and the step version it describes. Old or expired findings stop supporting new approvals. Completion needs dated measurements, and the decision history records who changed what. A human still judges the quality of the evidence.

Can it check research privacy obligations? expand_more

It flags personal findings with missing collection purposes or overdue retention reviews, with New Zealand and Australian source references. Your team decides the applicable rules and review dates. These checks do not certify compliance or automatically erase information.

What do we pay Enterprise DNA, and what remains ours? expand_more

There is one setup fee, then a retainer for the agreed work. We map your records, build your rules and operate the system through Omni by Enterprise DNA. The database and open-source base remain yours. Hosting and any services you choose have their own costs.

Bring your UXPressia bill and one journey to Sam

Spend 30 minutes with Sam. We review the user bill, the work your team actually does and a sample export, then agree what an owned version would need. If the visual workshop is the part you value most, we factor that into the decision.

Book 30 minutes with Sam Get the free version

Customer Journeys for Claude Code is free and open source, published by Enterprise DNA.

Done paying for UXPressia?

Get your version built