How is customer experience different from UX design?

UX design usually covers one product or screen. Customer experience covers the whole relationship across channels and teams: the call, the visit, the invoice and the renewal, and the internal processes behind each of them.

How do you build personas that teams actually use?

From behavior rather than demographics. We use interviews, support tickets and product data, keep each persona to one page, and tie it to the decisions it should change. See our note on personas.

Do we need a headless architecture?

Not always. It pays when several front ends share the same content and data, or when the website and apps need to change faster than the systems behind them. For a single website with a small team, a well-run traditional platform is often the better choice.

How do you handle personalization and privacy?

We work from first-party data that customers have agreed to share, keep the rules explainable, and design consent into the customer profile. Your legal team signs off on what data is used and how.

Research and strategy are a fixed fee per phase, agreed after a scoping call. Builds such as a headless platform or personalization engine are fixed-price releases, like our web apps and automation work.

Customer experience

We find the moments where customers stall, call or leave, map the journey behind them, and fix it: personas built from real behavior, personalization you can measure, and a platform that serves every channel from one source.

Start a conversation Read the FAQ

Facilities manager, cold-storage clientGoal: stock safe, fault fixed, paperwork that matches.

Stage NoticeReportWaitVisitInvoiceRenew Doing Freezer alarm at 6:40Calls the service line, then emailsChecks for an arrival timeLets the technician in at Dock 3Matches the invoice to the POReviews the contract at year end Feeling

Moment that matters No one knows yetOn hold, then no replyNo arrival timeFixed on the first visitNo PO numberNo record of visits Fix Alarm opens a ticketOne number, a reference in secondsLive arrival time by textReport and photos on the spotPO on every invoiceA year of visits at renewal

NoticeFreezer alarm at 6:40No one knows yetAlarm opens a ticket
ReportCalls the service line, then emailsOn hold, then no replyOne number, a reference in seconds
WaitChecks for an arrival timeNo arrival timeLive arrival time by text
VisitLets the technician in at Dock 3Fixed on the first visitReport and photos on the spot
InvoiceMatches the invoice to the PONo PO numberPO on every invoice
RenewReviews the contract at year endNo record of visitsA year of visits at renewal

Use case A facilities manager at a cold-storage client reports a freezer fault. The repair itself goes well. The hold queue, the missing arrival time and an invoice without a PO number are what they remember. The people and steps are illustrative.

Where we help

Customer experience strategy: Where the experience wins or loses customers today, sized in revenue and cost to serve, and the two or three journeys worth fixing first.
Personas from real behavior: Built from interviews, support tickets and product data, so each persona changes a decision: what to build, what to say, what to stop doing.
Journey maps and service blueprints: One journey mapped end to end from the customer's side, then the blueprint behind it: the people, systems and handoffs that make each step work or fail.
Personalization you can measure: The right content, offer or next step for each segment, starting with clear rules, tested against a group that sees the standard version.
Headless architecture: Content, products and customer data behind APIs, so your website, apps, portal and email draw from one source and each can change on its own.
Change management: Training, new roles and a rollout plan for the people who deliver the experience, with adoption tracked every week after go-live.

How it fits Headless means the screens customers see are separate from the systems behind them. The website, apps, portal and email all read the same content, prices and customer data through one set of APIs, so a new channel or a redesign does not mean rebuilding the back end.

How we keep it grounded

Real customers in week one: We talk to customers and sit with the teams who serve them before drawing anything. Assumptions go in a ledger and get tested, not presented.
One journey at a time: We start with the journey where the most value is at stake, fix it end to end, and only then move to the next.
A baseline before any change: Completion rate, repeat contacts, time to resolve, conversion: we agree the numbers first, so improvement means something.
A control group for personalization: Every rule or model runs against customers who see the standard version, so you know what the personalization actually changed.
Adoption is part of done: A release is finished when the people using it have changed how they work. We track that weekly, with the team leads who own it.

We also work on AI assistants and agents, iOS and Android apps, web apps and automation, and management consulting. Most projects use more than one. See how a project grows.

v1One journey mapped You see where customers stall and what it costs, in your own numbers.
v2The worst moment fixed Fewer repeat calls and complaints on the journey that matters most.
v3Personalization with a control group Each customer sees the next best step, with proof of what it changed.
v4One platform behind every channel Web, app, portal and email show the same content and prices.
v5Your team runs the research and tests New journeys are mapped and improved without waiting for us.

Each release is a chamber: in use, measured, and carried forward by your team.

Common questions

How is customer experience different from UX design?: UX design usually covers one product or screen. Customer experience covers the whole relationship across channels and teams: the call, the visit, the invoice and the renewal, and the internal processes behind each of them.
How do you build personas that teams actually use?: From behavior rather than demographics. We use interviews, support tickets and product data, keep each persona to one page, and tie it to the decisions it should change. See our note on personas.
Do we need a headless architecture?: Not always. It pays when several front ends share the same content and data, or when the website and apps need to change faster than the systems behind them. For a single website with a small team, a well-run traditional platform is often the better choice.
How do you handle personalization and privacy?: We work from first-party data that customers have agreed to share, keep the rules explainable, and design consent into the customer profile. Your legal team signs off on what data is used and how.
How is this priced?: Research and strategy are a fixed fee per phase, agreed after a scoping call. Builds such as a headless platform or personalization engine are fixed-price releases, like our web apps and automation work.

What are you building?

Tell us what you are weighing. We reply personally, usually with a few questions or a time to talk.

Start a conversation

A nautilus shell cut in half, its pearly chambers spiralling inward against black.