A CFO who looks past the wireframes wants one thing: a defensible number connecting design work to the bottom line. Storyboards do not supply it, and the era when a short pitch could substitute for an actual case is over. Winning budget and backing now requires the design to be provably good for the business as well as for the people using it — which means understanding how the organization defines value, how it measures that value, and where the line between a design initiative and a business outcome can honestly be drawn.

The fictional mid-size B2B SaaS company Meridian carries one worked example through the whole process below: goal-setting, cost accounting, causal testing, and a final ROI figure share the same numbers throughout, because a framework only becomes tangible once the numbers connect. Each step is one you can rerun inside your own organization.

Why Vagueness Loses The Room

Executives are not hostile to UX; they are hostile to imprecision. A case built on “users will find it easier” loses to the department promising 12% more sales in Q3, every time. The difference is the one between a streamlined checkout flow that reduced cart abandonment, with completed purchases up 22%, and the same work rewarded with “the QA testers like it.” One version earns budget; the other does not.

When No Usable KPIs Exist Yet

Most ROI writing assumes the organization already has clean business goals and KPIs to hook work onto. Real companies are messier. Plenty run on ambitions like “grow faster” or “improve the customer journey” that were never broken into anything measurable, and a case built on that ambiguity collapses the moment somebody scrutinizes it. The first job, then, is often helping the organization define what success looks like at all.

Interview stakeholders across departments: ask product what a good quarter looks like, ask customer success where users struggle, ask sales where deals stall. Themes that resurface across conversations are the company’s latent business objectives. The OKR model (Objectives and Key Results) works as a forcing function here, since it tolerates no vagueness.

Meridian’s stated ambition was to “improve the rate of new users’ adoption of the platform” — not something you can design toward or measure against. Interviews exposed the real problem: trial users needed a median of 14 days to reach first value, most churned before arriving there, and onboarding questions were burying the support queue. The resulting OKR had edges: reduce median time-to-first-value from 14 days to 7 via a guided setup flow, and lift trial-to-paid conversion from 8% to 9.5%.

Formalize KPIs from inside the UX team alone and leadership will suspect the field has been rigged in your favor — co-create them with whoever owns the outcome. Meridian’s head of product agreed that setup-completion rate was a fair proxy for onboarding usability, and customer success signed off on time-to-first-value, which already sat on their own dashboard.

A KPI ladder that ends at a metric somebody already watches buys you credibility before any design work starts.

The Denominator Is Where Teams Go Wrong

ROI needs a denominator, and cost usually gets counted as designer salaries or consulting hours and nothing else. A finance team will find the rest whether or not you counted it, so count it first.

Direct costs are only the visible layer. Meridian’s redesign ran $45,000 in design and research labor plus $8,000 in tooling and participant incentives. Licenses for Figma, UserTesting, Hotjar, analytics platforms, research incentive spend — all of it belongs in the total, and that is before the vendor lock-in every UX team eventually runs into. Engineering belongs in the same column, because a UX redesign does not stop at the mockup: building the guided setup took two frontend sprints plus a QA pass, $38,000. The project also generated about $4,000 of coordination overhead in new syncs and shared dashboards.

The commonly missed line item, and the one worth taking from this example if nothing else, is stakeholder time. Workshops, design reviews, and feedback sessions pull senior people away from primary work; a VP of Product spending four hours a week in UX reviews is not spending those hours on roadmap planning or partner negotiations. Log attendance — who, how long, at what seniority — and price it at fully loaded cost: salary plus benefits divided by productive hours. A quarter of workshops, reviews, and interviews at Meridian priced out at $22,000.

The total: $45,000 design labor, $8,000 tooling, $38,000 engineering, $22,000 stakeholder time, $4,000 coordination — $117,000. Saying that number out loud beats saying “we spent $45K on design,” precisely because it already contains everything finance would have dug up independently.

Separating Causation From Correlation

This is where most UX pitches die. Conversions rose after the redesign, yes — so how did you rule out the new pricing, the seasonal traffic bump, and the campaign that shipped the same week? Without an answer, the ROI story crumbles.

A/B testing remains the gold standard for proving causation: old experience against new, even traffic split, run until the sample means something. Onboarding suits a phased rollout, so Meridian ran one. For eight weeks, half of new trial signups received the guided setup and half stayed on the legacy flow. Control converted to paid at 8.0%; the variant hit 9.4%. With roughly 6,100 trials in the window the gap was statistically significant, though a single 1.4-point result deserves a second look before anyone builds a budget on it — part of why the team attributed conservatively. Where a split is not feasible — too structural a change, too small a user base — fall back on a time series: measure steadily for weeks before the change, implement, then keep measuring against the baseline.

Documenting everything else happening around the same time is the unglamorous half of causation. Meridian’s marketing team ran a pricing-page test overlapping weeks five through eight of the rollout. The UX team noted it, confirmed it hit both cohorts evenly, and still attributed only 70% of the observed lift to the redesign. That number comes from no formula — treat it as an illustrative assumption for this example. The team asked how much of the lift the pricing test could plausibly own if it had favored one cohort slightly, settled on a ceiling of about a third, and rounded the redesign’s share down to 70%. What matters is that the figure is written down and argued for before results arrive, not fitted to them afterward; that restraint is worth money in a skeptical room. “We attribute roughly 70% of the lift to the onboarding change, with the remainder likely influenced by concurrent pricing work” survives cross-examination; claiming everything does not. Cohort analysis backed it up: the lift held across acquisition channels and tenure bands, leaving skeptics little to work with.

Leading and lagging indicators belong on the same slide, each covering the other’s weakness. Meridian’s leading indicators moved first — setup completion from 62% to 89%, median time-to-first-value from 14 days to 6.5 — and the lagging trial-to-paid number followed. Mechanism first, business outcome second; presented together they form a causal chain harder to poke holes in than either alone.

Running The Numbers End To End

Meridian sees about 40,000 trial signups a year. Lifting conversion from 8.0% to 9.4% adds roughly 560 paying customers annually; at an average $1,800 in annual recurring revenue per account, that is about $1,008,000 in new ARR. Applying the 70% attribution trims the defensible figure to roughly $706,000. Against the full $117,000 investment, first-year ROI lands near 5:1, with payback in roughly two months. A second line stands separately: onboarding-related support tickets fell about 30%, some 3,600 fewer a year, worth another $54,000 annually at $15 per resolved ticket. Keep it as its own line rather than folding it into one swollen headline number — the case reads as more honest and loses none of its force.

Three assumptions carry that result, and each belongs on the slide beside it. The 40,000 signups and the $1,800 average ARR are last year’s actuals held flat, so a growth or pricing change moves the outcome in either direction. The 70% attribution is the illustrative assumption from the causal work, not a measured quantity. And the two-month payback counts new ARR as it lands rather than revenue recognized net of churn, which flatters the timeline — on a net basis payback stretches to roughly a quarter. Stated plainly, a finance team can adapt the example to its own numbers; hidden, the whole thing starts to look like marketing math no matter how careful the experiment was.

What The Final Presentation Needs

Sophistication is not what persuades. Open with the baseline — what stalled trials and support volume were already costing. Show the delta in metrics leadership reads fluently, conversion rate uplift chief among them. A chart of setup completion climbing from 62% to 89% beats a paragraph of UX jargon, and a translation like “each abandoned setup costs us 0.3 support tickets” beats the chart. Above all, keep every figure identical from the first slide to the last: a room full of finance people forgives many things, but never numbers that wobble between slides.

One Set Of Numbers, Several Audiences

Budgets get released by coalitions, not individuals. A CFO may cast the deciding vote on something like adding AI to the checkout process, yet marketing, product, and customer success each pull on that decision — and each means something different by “value.”

Cost, revenue, and risk are what a CFO listens for. Conversion and acquisition cost are what a CMO listens for, since UX is a lever for increasing marketing ROI. Product tracks support tickets; customer success tracks retention. The numbers underneath stay put — only the framing rotates, because a CFO wants a projection, not a moodboard. At Meridian, the CFO slide read “the onboarding redesign protects roughly $706,000 in new ARR a year against a $117,000 investment,” while the CMO deck opened on what a 9.4% trial conversion rate does to blended acquisition cost.

Two registers of evidence belong in the same proposal, which is essentially what social proof is for: the labeled case, alongside screenshots, impact graphs, and user quotes. Cultivate internal allies who can repeat the ROI narrative in rooms you will never sit in, and write the playbook down — repeatable ROI is what earns recurring investment.

When The Return Isn’t A Dollar Figure

Certain UX outcomes will not translate cleanly into revenue, and forcing them to only undermines the parts of the case that do hold up.

The trick with qualitative evidence is collecting it rigorously enough that nobody can wave it off as anecdote.

NPS, CSAT, and Customer Effort Score already live inside most reporting cadences, so borrowing them costs little. Segment wherever the data allows: saying NPS among trial users hit 51 on the redesigned onboarding against 34 on the legacy flow is far more persuasive than any blended average. Verbatim material — survey comments, support transcripts, app store reviews — supplies the emotional weight scores can’t carry.

Internal tooling deserves identical discipline, since employee experience is increasingly recognized as a business driver. Handing account managers 45 minutes a day back through a dashboard redesign is simultaneously a productivity gain, a satisfaction gain, and a retention lever.

Brand perception is harder to pin down, but it leaves tracks: repeat visits, organic referrals, social sentiment. It weighs more in trust-sensitive industries like finance or healthcare, and it forms quickly — UX design influences the first impressions of a whopping 94% of customers.

Collect systematically or not at all. Pre- and post-surveys with consistent question sets, structured usability testing with task-based scoring, and qualitative findings placed directly beside quantitative ones at presentation time.

“Setup completion rose from 62% to 89%, and in post-test interviews 8 of 10 participants called the new flow intuitive, against 3 of 10 for the old one” — a pairing like that is much harder to dismiss than either half on its own.

Speak The Board’s Language

UX loses the budget battle unless it’s mapped to company-wide objectives, so the proposal should be phrased in the vocabulary of this year’s board presentation. Nobody at Meridian pitched “simplify the onboarding UI.” The pitch was a redesigned trial experience worth 1.4 points of upgrade rate — roughly $1M in annual recurring revenue, before attribution.

A seat at the table is not won through beauty or novelty, but through measurable, defensible impact, which asks UX leaders to drop the artist’s posture and take up the strategist’s: outcomes over outputs, pixels tied to profit. When the numbers get challenged, the response is the controlled experiment, the cohort analysis, the before-and-after metrics — every figure identical from first slide to last, as Meridian’s were, with customer quotes and employee-satisfaction data sitting beside the revenue impact. Prove the work does more than delight users, defend the ratio line by line, and design stops being optional.

Further Reading

Smashing Editorial