Our buyer intelligence is informed by ongoing conversations with senior enterprise leaders through roundtables and leadership communities.
Customer experience technology is usually sold with a promise of simplicity. Faster service. Fewer steps. Better personalisation. Smoother journeys. More self-service. Less waiting.
The uncomfortable reality is that digital innovation can make the customer work harder when it is designed around the organisation’s structure rather than the customer’s objective.
Recent discussions with senior US marketing leaders surfaced this tension directly. Teams described excessive handoffs, complicated customer journeys, automation that still needs a human escape route and the limits of relying on broad satisfaction scores to identify where friction actually occurs.
For CX vendors, this creates a useful contrarian buying signal: the enterprise buyer may be less impressed by the number of capabilities in the platform than by how many unnecessary decisions, transfers and repeated explanations it removes from the customer’s path.
Digital transformation can digitise the friction
A broken process does not become customer-centric because it moves online. If the customer still needs to repeat information between teams, wait for an internal approval, navigate an organisational boundary or understand which department owns the problem, the friction remains. It may simply be wrapped in a cleaner interface.
This is one reason transformation programmes can disappoint even when the technology works as designed. The product automates the existing process faithfully instead of challenging whether the process should exist in that form.
Vendors should therefore demonstrate where the platform removes work, not only where it digitises work. Which step disappears? Which handoff becomes invisible? Which piece of context follows the customer automatically? Which exception can be resolved without restarting the journey?
A polished interface does not reduce customer effort if the organisation’s complexity is still leaking through it.
The customer does not care about your org chart
Customers experience one brand, even when the business is divided into marketing, product, sales, operations, service, finance, legal and regional teams. They do not understand why a data field belongs to one system or why a request must be transferred because another department owns the next step.
Every internal boundary that becomes visible to the customer creates potential effort. The customer waits, repeats, re-authenticates or learns the structure of the company simply to complete their task.
This makes cross-functional design a buying requirement. A CX platform may sit inside marketing, but the journey usually crosses systems and teams outside marketing’s direct control. Vendors that ignore those boundaries in implementation may deliver a technically successful tool that leaves the customer experience largely unchanged.
Handoffs are where friction compounds
One handoff can be manageable. Several handoffs create cumulative uncertainty. Context can be lost. Ownership can become unclear. The customer may receive different answers from different teams or be asked to repeat information they already provided.
Journey mapping becomes valuable because it makes those transitions visible. Senior leaders described discovering missing steps only after multiple functions reviewed the same map. That is a reminder for vendors: the buyer’s first journey model is probably incomplete.
A strong CX implementation should therefore include collaborative mapping and validation, not simply import a process map built by one department. The platform needs the version of the journey customers actually experience, including failure states and workarounds.
Automation needs an escape hatch
Self-service and automation can reduce effort when the customer’s need fits the expected path. The problem appears at the edges. Customers have unusual circumstances, incomplete information, emotional needs, accessibility requirements or requests the original workflow did not anticipate.
A rigid bot or digital form can turn a simple exception into a frustrating loop. Senior leaders explicitly discussed the need for escape routes so customers can move from automated support to human intervention when necessary.
For vendors, human escalation should not be treated as failure. It is part of a resilient experience design. Show how context moves with the customer, how the system recognises low-confidence cases and how a human can intervene without forcing the customer to start again.
Personalisation can create effort too
Personalisation is intended to make experiences more relevant, but poor personalisation can create cognitive and emotional friction. A customer may see too many choices, receive recommendations based on stale data, feel tracked too aggressively or be pushed into a path that no longer matches their intention.
The enterprise buyer therefore needs more than a promise of “next best action”. They need to understand the decision logic, the data recency, the confidence threshold and what happens when the recommendation is wrong.
The best personalisation often feels like less. Fewer irrelevant messages. Fewer repeated questions. Fewer steps. Less explanation required from the customer.
NPS can miss the friction that matters
Broad relationship metrics such as NPS can help track sentiment, but they may not reveal the exact task that creates effort. Senior marketing leaders discussed supplementing high-level measures with customer effort and more journey-specific feedback.
This is commercially important for CX vendors. If the product claims to reduce friction, the measurement model should observe friction directly: task completion, repeated contacts, transfers, abandonment, time to resolution, re-entry, error recovery or Customer Effort Score in relevant moments.
A buyer is more likely to fund a CX improvement when the vendor can show which piece of customer work will become easier and how that change will be observed.
| Buyer question | Weak vendor answer | Stronger proof |
|---|---|---|
| How does this reduce customer effort? | It creates a seamless digital experience. | Name the steps, handoffs or repeated inputs that disappear and measure them before and after. |
| What happens when automation fails? | Our AI resolves most enquiries. | Show confidence thresholds, escalation routes and how context follows the customer to a human. |
| How do you map the real journey? | We provide journey templates. | Run cross-functional discovery that includes failure states, offline steps and frontline evidence. |
| How do we measure CX improvement? | Track NPS and CSAT in our dashboard. | Match measures to the task, including effort, completion, repeat contact, transfer and abandonment. |
| How does personalisation help? | We deliver next-best actions. | Show the data, recency and decision logic, plus what happens when the recommendation is uncertain. |
| How do departments collaborate? | Everyone can access the same platform. | Define ownership, handoff rules and shared outcome measures across the journey. |
Journey mapping should expose operating reality
The most valuable journey map is not the most attractive one. It is the one that exposes where customers wait, switch channels, seek help, repeat information or abandon the task.
Vendors can strengthen the buying process by using discovery to identify those moments before configuration begins. This creates a clearer implementation priority and avoids turning the platform into a container for every possible touchpoint at once.
It also helps the internal sponsor defend scope. Instead of asking the organisation to “transform CX”, the buyer can point to three or four high-friction journeys and explain exactly what will improve.
What will slow a CX technology deal
- The demo showcases features without showing which customer task becomes easier.
- The implementation assumes the current process is correct and simply digitises it.
- Automation has no clear exception path or human escalation model.
- Customer context is lost when a journey crosses systems or departments.
- The measurement plan relies on one broad satisfaction score.
- The vendor treats cross-functional ownership as the buyer’s problem after go-live.
The strongest CX proposition is often subtraction
Innovation teams naturally focus on what they can add: channels, features, recommendations, automation, interfaces and data. Customers often experience value through what disappears: a form they no longer complete, a transfer they no longer endure, a question they no longer repeat or a wait they no longer notice.
That is the opportunity for vendors. Do not only show the buyer what the platform enables. Show what it makes unnecessary. In enterprise customer experience, subtraction can be the clearest proof of sophistication.
Friction is not the same as the number of clicks
Digital teams sometimes treat friction as a UI problem: too many fields, too many screens, too many clicks. Those are important, but customer effort can also be emotional, informational and organisational.
A customer may complete a form quickly yet still feel uncertain about what happens next. They may receive a fast chatbot answer that does not address the real issue. They may move through a short flow only to discover that the organisation needs additional evidence later. Reducing visible steps while increasing uncertainty can make the experience feel worse.
CX vendors should therefore define the customer objective first and measure whether the person reaches it with confidence, not only whether the interface is shorter.
Employee effort often becomes customer effort
A surprising amount of customer friction begins behind the scenes. Employees search across systems, copy information between tools, wait for approvals or ask another department for context. Those delays eventually surface as slower responses, inconsistent answers or repeated questions to the customer.
This gives vendors a broader discovery lens. Map the employee workflow behind the customer journey. If a service agent needs five systems to resolve one request, the customer may experience that complexity even if the front-end design is clean.
The strongest CX technology can reduce both forms of effort at once by bringing context to the employee and reducing the number of internal transitions required to complete the task.
Service recovery can create more loyalty than perfect automation
No journey will be frictionless for every customer. The enterprise therefore needs a strong recovery path when something goes wrong. A failed payment, incorrect recommendation, delayed order or misunderstood request becomes a test of the experience design.
Vendors should show how the system detects failure, preserves context and empowers a human to resolve the issue quickly. Recovery should not force the customer back to the beginning or require them to prove the problem again.
This is especially important for AI-supported experiences because errors can feel arbitrary. A clear, respectful recovery path protects trust when automation reaches its limit.
Accessibility is a friction test, not a compliance footnote
An experience can look elegant to the design team and still create unnecessary effort for customers with different visual, motor, cognitive or language needs. Accessibility therefore belongs in the core friction model.
Enterprise buyers should ask vendors how interfaces work with assistive technology, how content adapts to device and input differences, and whether automated journeys provide alternatives when the standard path is not usable. These questions improve experience quality for a wider population and reduce the risk of excluding customers from the journey.
A vendor that treats accessibility as a design principle rather than a final compliance check is likely to inspire more confidence in mature enterprise teams.
Procurement should ask for a friction baseline
Before approving a CX platform, the buyer should be able to name the friction it expects to reduce. That may be repeat contact, transfer rate, abandonment, time to resolution, repeated data entry, support escalations or a specific customer-effort score.
The vendor should then show how the product changes the mechanism behind that friction. This prevents the business case from collapsing into a list of features and creates a measurable post-launch test.
The strongest enterprise CX sale is therefore not “buy our platform to transform the journey”. It is “here is the customer work we will remove, the internal work we will simplify and the evidence we will use to prove it”.
Friction reduction can become a business case, not only a CX ambition
Customer effort often has an operational cost attached to it. Repeated contacts consume service capacity. Failed self-service creates escalations. Abandonment wastes acquisition spend. Manual handoffs slow revenue and increase the chance of error. That gives the internal buyer a route from experience improvement to economics without pretending every CX change can be tied directly to revenue on day one.
Vendors should help quantify the avoidable work around a high-friction journey. If the organisation can reduce repeat contacts, unnecessary transfers or re-entry, it can measure both the customer benefit and the operational capacity released. This makes the programme easier to defend with finance and operations because the value is visible on both sides of the experience.
The enterprise CX buyer is therefore not asking for simplicity as an aesthetic preference. They are increasingly looking for simpler journeys because complexity costs customers time and costs the organisation capacity.
Frequently asked questions
How can customer experience technology create more friction?
It can digitise broken processes, add rigid automation, expose internal handoffs, personalise from poor data or require customers to navigate more tools and choices without reducing the underlying work.
What is customer journey friction?
Customer journey friction is unnecessary effort, uncertainty or delay a customer experiences while trying to achieve an objective. It can include repeated information, transfers, waiting, confusing choices, re-authentication, errors or failed automation.
Is NPS enough to measure digital customer experience?
NPS can be useful for broad relationship sentiment, but it may not identify task-level friction. Enterprise teams often need journey-specific measures such as Customer Effort Score, completion, abandonment, repeat contact and resolution time.
What should CX vendors demonstrate in an enterprise sale?
They should show which customer steps or handoffs will be removed, how context will persist across channels, how exceptions escalate and how reduced effort will be measured after implementation.
Speak to The Leadership Board
If you sell CX, journey, service, automation or customer-feedback technology, enterprise buyers are increasingly testing whether innovation actually removes work for the customer. Speak to The Leadership Board to understand the friction points and proof questions forming before the technology decision is made.