There is a number most product teams never see.

It lives in the support team's inbox. It sits inside the churn report nobody reads carefully enough. It hides in the onboarding drop-off data that gets noted in a quarterly review and then quietly forgotten.

The number is the cost of confusion. And in most digital products, it is significantly larger than the budget that was declined for the design work that would have prevented it.

What Confusion Actually Costs.

A user who cannot find what they need does one of three things.

They raise a support ticket. They abandon the journey. Or they complete it frustrated, carry that frustration into their next interaction with the brand, and eventually leave without telling anyone why.

Each of these has a measurable price attached to it.

The average cost of handling a single customer support ticket, accounting for staff time, tooling, and management overhead, sits between £8 and £15 depending on the organisation. A product with 10,000 monthly users generating even a modest support contact rate of 8% is spending between £6,400 and £12,000 every month on confusion.

Not on product development. Not on growth. On explaining things that should have been clear in the first place.

The research is consistent on the return side of this equation. The Forrester Research figure cited most frequently across the industry puts the ROI of UX investment at 100:1. For every £1 spent on solving a usability problem during design, £100 is saved avoiding the cost of solving it after launch.

"Design is not a line item on a project budget. It is an insurance policy on every line item that follows."

Prevention Versus Cure.

The medical framing is useful here because it clarifies where the cost actually falls.

A GP appointment costs a fraction of an emergency hospital admission. The clinical outcome of catching something early is almost always better than treating it late. Nobody disputes this logic in healthcare.

In digital product development, the same logic is routinely ignored.

A usability test during the design phase costs hundreds. A redesign after launch costs tens of thousands. A confusing checkout flow identified in prototype costs an afternoon's work to fix. The same problem identified after six months of elevated abandonment rates costs a development sprint, a UX audit, a round of stakeholder alignment, and six months of revenue that leaked out while everyone was looking elsewhere.

The cure is always more expensive than the prevention. The only variable is whether the organisation chooses to recognise the cost before or after it has been paid.

Where the Money Goes Without Good Design.

Support volume.

Every unclear label, ambiguous error message, and unintuitive navigation pattern generates a predictable volume of contact. Users do not raise tickets because they enjoy it. They raise them because the product failed to communicate something they needed to know. That failure is a design failure, and it has a direct cost attached to every instance of it.

Churn.

Poor UX does not always produce a dramatic cancellation moment. More often it produces a gradual erosion of confidence. The user who struggles to complete a task the first time approaches the second time with less goodwill. By the third time, they are already considering alternatives. By the fourth, they have found one.

Retention data rarely attributes churn to UX directly. The exit survey says "found a better price" or "no longer needed the product." The real reason is often that the product made them feel slightly stupid, repeatedly, until they stopped.

Conversion.

Every point of friction in a purchase or sign-up journey represents a percentage of users who did not complete it. A/B testing on simplified checkout flows consistently demonstrates conversion lifts of 10-35% from changes that cost a fraction of what the lost revenue represented.

The conversion rate problem is the most legible version of the design ROI argument because the number is immediate and attributable. The others are real but require more honest accounting to surface.

The Reason This Keeps Being Under-Invested.

Design's ROI is front-loaded in cost and back-loaded in return.

The research, the testing, the iteration, all of it happens before launch, before revenue, before any of the metrics that justify the spend are visible. The return, in reduced support costs, improved retention, and higher conversion, accumulates over months and quarters after the work is done.

This makes it easy to cut in a budget conversation and hard to credit in a performance review.

The support team that handles fewer tickets because a redesign reduced confusion does not receive a line in the board report connecting those two facts. The retention improvement that followed a simplified onboarding flow does not automatically attribute itself to the UX investment that produced it.

The organisations that consistently invest in design are the ones that have developed enough institutional memory to connect these dots without requiring the data to be handed to them in real time.

What Good Design Is Actually Preventing.

It is worth being specific, because the abstract case for UX investment is easy to dismiss.

Good design prevents a user from calling support to ask why their account shows the wrong status. It prevents an onboarding flow from losing 40% of new users at step three because the progress indicator was misleading. It prevents a checkout from abandoning 25% of filled baskets because the delivery options appeared too late in the process. It prevents a cancellation flow from working so well at guilt-tripping users that they leave a negative review on their way out anyway.

None of these are edge cases. All of them are happening, at scale, on products that skipped the design investment because the budget was tight.

The Reframe That Changes the Conversation.

The mistake is presenting UX as a quality investment. Quality is subjective, deferrable, and easy to deprioritise.

Present it as a cost reduction strategy, and the conversation changes entirely.

The question is not: can we afford to invest in better design? It is: how much are we currently spending on the consequences of not doing so?

That number, pulled honestly from support data, churn reports, and conversion analytics, is almost always larger than the design budget that would have prevented it.

The design work that never happened is not free.

It just sends its invoice to a different department.