How to Make the Commercial Case for Experience Investment in a Boardroom That Only Speaks Revenue

There is a moment most experience teams will recognise. You walk into a board meeting with research findings, behavioural data, and a clear recommendation. The work is solid. The case feels obvious. And then someone across the table asks what it will do for revenue, and the room shifts. Not because the question is unreasonable, it is entirely reasonable, but because the answer you prepared was framed in the wrong language. You talked about friction. They think in margin.

The experience team knows the work matters commercially, but the board does not yet have the framing to see why.

This gap is a translation problem, and it is one that falls on experienced practitioners to solve. Boards are responsible for the financial health of the organisation, and any investment case that arrives without a clear line to commercial return is, from their position, incomplete. The frustration runs both ways: the experience team knows the work matters, and the board does not yet have the framing to see why.

What follows is a working guide to building that framing from the ground up. The structure comes from real projects where we have had to make exactly this case, sometimes successfully and sometimes only after the board had already seen the cost of not acting. Both types of experience are useful.

Why the Boardroom Dismisses Experience Findings

The board does not dismiss experience work because it is indifferent to users. It dismisses it because the findings typically arrive in a form that requires translation the board does not have time to perform. A finding that says "users find the checkout flow confusing" places the cognitive burden on the listener to calculate what that confusion costs, how often it happens, and whether fixing it is worth the investment. Most board members will not do that calculation in the room. They will move on.

There is also a measurement problem rooted in how experience data is usually collected. NPS and self-reported satisfaction scores tend to look healthy because they are gathered after the fact, when users are calm and reflective rather than in the middle of a frustrating moment. Those scores reflect well when reported upward through the organisation, which creates a structural incentive to keep using them. The board sees a positive number and concludes the product is performing. The in-context behavioural data that would tell a different story rarely makes it into the same deck.

This is a failure of structure. The experience team reports what it found. The board needs to hear what it costs. Until those two things speak the same language, the findings will keep landing softly and then disappearing.

Tie Every Finding to a Revenue Mechanism

Every experience problem connects to one of a small number of revenue mechanisms. The work is identifying which one applies and making that connection explicit before you walk into the room.

• Conversion rate: friction in a purchase or sign-up flow reduces the proportion of users who complete it
• Average order value: a confusing upsell or unclear pricing suppresses spend per transaction
• Retention: a poor early experience shortens the customer relationship and reduces lifetime value
• Referral: a product that does not create emotional connection generates fewer organic recommendations
• Support cost: a confusing flow increases inbound contact volume, which has a direct cost per ticket

On a travel booking product we worked on, we initially wrapped the platform's Stripe booking fee into the total price, reasoning that travellers want to see one clean total. What we found instead was that users expected to see a platform fee as a line item, because that matches their mental model of how apps and platforms work. By not showing it, we created a fear that a hidden fee would appear later.

When we switched to breaking out all fees transparently, user confidence rose even though they were seeing more information. The relevant revenue mechanism there was conversion: users were dropping out of the checkout before completing a booking, and the fix was a display change, not a pricing change.

Users had more confidence seeing more information, not less, because transparency removed the fear of a hidden fee.

That framing, a display problem causing checkout abandonment causing lost revenue per booking, is a board conversation. "Users found the fee confusing" is not.

Reframe the Finding Before You Walk In the Room

The reframe happens before the meeting, not during it. If you arrive hoping to translate the finding on the fly, you will lose the thread under questioning. The preparation is the work.

The structure we use, which draws on the principles of app planning and strategy, starts with the behaviour, then the mechanism, then the number. What are users doing or not doing? Which revenue line does that behaviour affect? What is a defensible estimate of the cost at current volume? Each step is a discipline, and the discipline is in being specific rather than approximate.

Turn every research finding into a one-sentence commercial statement before you prepare your slides. If you cannot write the sentence, the finding is not yet ready for the boardroom.

A useful test is to take the finding and ask what a finance director would need to know to evaluate it. They would want to know how often the problem occurs, what proportion of users it affects, and what the unit economics of fixing it look like. Those three questions shape the preparation. A finding that survives all three is board-ready. One that collapses at the first question needs more work before it leaves the team.

Language matters here too. Boards think in exposure and return, not in usability scores. "The flow has a high drop-off rate" becomes "we are losing approximately X transactions per month at a value of Y." The finding is the same. The framing is entirely different, and it changes what the board is being asked to decide.

Quantify the Exposure, Not Just the Opportunity

Experience teams typically present upside: fix this and you will gain. Boards respond more readily to downside: do not fix this and you will continue losing. These are not the same argument, and they land differently.

Quantifying exposure means putting a number on what the current state is already costing, in terms the board can compare against the cost of the fix. If a checkout flow is losing 40% of users at a particular step, and the average transaction value is known, then the monthly exposure is calculable. You do not need a precise figure. You need a defensible range that makes the cost of inaction visible.

On the genetics wellness app we worked on, early testing showed that comprehension scores were low. Users were falling into error states because the product contained a great deal of content and the copy did not pre-frame what was coming. The exposure was not just a usability problem. Users who hit those error states without context were interpreting unexpected genetic results as something being wrong with them, rather than as normal variation. That emotional state carries a retention cost: users who feel confused or anxious in a product do not stay. We reframed the copy to create a more narrative experience and ran a second round of user testing, and clarity, sense of purpose, and retention all rose measurably.

Build a simple table for each finding: current state cost, cost to address, projected improvement, and payback period. A board that can see those four numbers in one place can make a decision in the room.

The exposure framing also sidesteps a common boardroom objection, which is that the opportunity might not materialise. Losses that are already happening are the current run rate.

The Smallest Change That Tests the Hypothesis

One reason boards hesitate on experience investment is that the ask often arrives at full scale. A complete redesign, a new design system, a multi-quarter programme. The commercial case for that level of investment is genuinely hard to make without data, because the return is theoretical until the work is done.

A more productive framing is to identify the smallest change that would test whether the hypothesis is correct. If the hypothesis is that priming users before a long flow will reduce drop-off, that test does not require a redesign. It requires a copy change and a measurement window.

On a health and wellbeing product, we tested two versions of a multi-step flow. One showed users a progress bar and started the process immediately. The other primed users upfront with what to expect before they began. Without priming, drop-off rates ran at around 80 to 85%, typically within the first three or four questions. After introducing the upfront explanation, completion rates rose to approximately 95%. That was a copy and sequencing change, not a structural rebuild, and it produced a result the board could verify in a short window.

Starting small also changes the nature of the investment conversation. A board being asked to fund a four-week test at a defined cost, with clear success criteria, is a different conversation from one being asked to approve a six-month programme. The test proves the principle. The programme follows from the proof.

Behavioural Flow Changes as Revenue Levers

Some of the most commercially significant changes in a product are sequencing changes: moving when something is asked, or what is shown first, or how a disclosure is framed. These changes are cheap to implement and testable quickly, which makes them the natural place to build early boardroom credibility.

We redesigned the location-sharing flow on a fitness social network. The original flow asked users to share their precise location early in the process, before any real relationship had formed with the other person. Conversion from sign-up to a user successfully meeting another person was running at roughly 20%. We introduced approximate proximity rather than precise location, and sequenced conversation before location disclosure, so the relationship had a chance to form before the more sensitive ask arrived. Conversion rose to around 60 to 70%, roughly a threefold improvement from a single flow change.

That kind of result translates directly into board language. The product's core value proposition was connecting people. A 20% conversion rate meant four in five users never experienced that value. The flow change addressed the behavioural barrier, and the commercial outcome followed. According to Forrester, every dollar invested in UX can return up to a hundred in commercial value, and flow-level changes with measurable conversion outcomes are exactly the kind of work that earns that return efficiently.

Map your product's core value moment, the action that makes the product worth having, and then trace every step between sign-up and that moment. Each unnecessary step or poorly sequenced ask is a potential conversion leak with a calculable cost.

When Completion Rates Are the Business Case

For products where value delivery depends on a user completing a process, completion rate is the business case. A survey that is not finished returns no data. A health assessment that is abandoned mid-flow serves no purpose. An application that is not submitted cannot convert. In each case, the completion rate is a direct proxy for the product doing its job at all.

We worked on a surveying app for performance coaches where the original design required the audience to download a native app before they could participate. We felt that was too high a barrier for what was essentially a simple interaction. A coach presenting to a room full of people cannot wait for an audience to navigate an app store. We proposed a QR code approach instead: the presenter creates the survey in the native app, a QR code appears on screen, and audience members scan it to reach a fully branded, mobile-responsive page. The feel of the experience was preserved, but the friction of the download was removed entirely, and completion rates rose significantly.

The board case there was not about user experience in the abstract. It was about whether the product could fulfil its purpose at all. A surveying app with a 40% completion rate is not doing its job. The fix was not cosmetic. It was the product working versus the product not working, and that framing makes the investment case straightforward.

Making Retention Legible to a CFO

Retention is one of the most commercially valuable outcomes an experience investment can produce, and one of the hardest to communicate to a finance audience. A CFO thinks in customer acquisition cost, lifetime value, and payback period. Retention affects all three, but the connection is rarely made explicit in experience reporting.

The framing that works is simple. If a customer stays for twelve months instead of six, lifetime value doubles at the same acquisition cost. If a 5% improvement in retention can drive up to 95% growth in profit over time, according to Bain and Company, then the CFO needs to see the current retention rate, the gap to a realistic improvement, and what that gap represents in revenue terms at current volume.

We saw this play out on an art-based auction game with real money prizes. Early retention ran in the mid-sixties to low seventies. As the quantity of available games declined, retention dropped to around 30 to 35%. The team kept adding features rather than addressing the underlying supply problem. When retention finally hit that low point and we refocused on the core user journey, ensuring enough games were available consistently, retention recovered to the mid-sixties to low seventies again. The lesson was that no feature addition compensates for a product that has run out of its core value. The CFO conversation should have started when retention first began to drop, not after it had halved.

Building a Repeatable Case-Making Structure

Making the commercial case once is a skill. Making it every quarter, across different findings and different audiences, requires a structure that the team can apply without rebuilding from scratch each time.

The structure we use has four components, which can be applied to almost any experience finding.

1. Behaviour: what are users doing or failing to do, and how often
2. Mechanism: which revenue line does that behaviour connect to directly
3. Exposure: what is the current cost at existing volume, expressed as a range
4. Test: what is the smallest investment that would confirm the hypothesis and produce a measurable result

This structure also helps the team prioritise internally, before anything reaches the board. Not every finding has a clear mechanism. Some findings are genuinely about user experience without a direct revenue connection, and those belong in a different conversation. The structure forces the team to be honest about which findings are board-ready and which need more development.

In lower-maturity organisations, the vast majority of research findings never result in a documented product change, according to Nielsen Norman Group. A repeatable case-making structure directly addresses that gap by giving findings the commercial framing they need to survive the journey from research to decision.

What to Do When the Board Still Will Not Act

Sometimes the case is solid, the framing is right, and the board still does not move. This happens, and understanding why it happens is more useful than assuming the case was flawed.

When inaction is structural

In some organisations, the barrier is structural rather than evidential. The board may have competing priorities, a capital allocation process that does not accommodate small tests, or a cultural tendency to treat experience work as a cost rather than an investment. In those cases, the right move is to find an internal sponsor who can carry the case through the right channels, rather than continuing to present to the full board without traction.

When the data is being dismissed

In others, the board is dismissing findings because it does not trust the measurement. This is worth taking seriously. If the experience team's metrics are session length and satisfaction scores, and the board's metrics are conversion and retention, there is a gap in the evidence chain that the team needs to close. Building a small body of work that connects experience changes to commercial outcomes in a way the board can verify is more effective than arguing about the value of qualitative data.

We walked away from one engagement where a founder had deep industry experience and strong pre-existing views about how the product should work. The research process became a box-ticking exercise. Even when we showed compelling evidence that a large portion of the target user base did not want certain features, the founder did not move. The product launched largely unchanged roughly a year later and did not succeed, for the same reasons the research had identified. The lesson is that evidence without receptivity has no commercial value. Knowing when to redirect effort is part of the work.

Conclusion

The commercial case for experience investment is the same argument as the experience argument, expressed in the language the board uses to make decisions. A checkout flow that erodes trust costs real revenue per day it remains. An onboarding process that drops 80% of users in the first four questions is a revenue problem. A retention rate that halves because the core product ran short of content is a financial exposure that compounds every month.

The work is translation, and it requires the experience team to be fluent in both languages. Not because commercial framing is more important than user wellbeing, those things are connected, and the board case rests on that connection, but because fluency in both is what gets the work funded, and unfunded work does not reach users.

The projects we have described here, from the 95% completion rate achieved through upfront priming, to the threefold conversion improvement on the fitness network, to the retention recovery on the auction game, each became board conversations only when they were framed as revenue conversations first. The experience insight was the reason the change worked. The commercial framing was the reason it got made.

If you are sitting on findings that have not moved the room yet, the gap is almost always in the translation, and that is a solvable problem. Let's work through your commercial case together.

Frequently Asked Questions